You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Architecture for Release A:



NonRT RIC components:

  1. Policy Management GUI / NONRTRIC Dashboard
  2. Policy agent / A1 Policy Management Service
  3. SDNC A1 Controller
  4. Near-RT RIC Simulator

The code base for Release A is in the Non-RT-RIC source repository (Gerrit)

Policy Management GUI / NONRTRIC Dashboard

The Policy Management GUI is a graphical user  user interface that enables the user to manage the Policies as defined in A1 in the network. The GUI nteracts with the Policy agent via its NBI (REST API).
The form for policy properties is generated from JSON schemas in a model driven fashion.

The GUI consists of a back end implemented as a Java Springboot application and a fronted developed using the Angular framework.

Please refer this developer guide to set up in local.

Policy Agent / A1 Policy Management Service (“Policy Agent” v1)

The Policy Agent is a micro service which maintains a transient repository of:

  • All configured A1 policies instances in the network. Each policy is targeted to a Near-RT-RIC instance and is owned by a 'service' (R-APP or the NONRTRIC Dashboard).
  • All NearRT RICs in the network. This information can be maintained using the ONAP CDS database (which is using the Cloudify Consul database).
  • All Policy types for all Near-RT-RICs
  • All configured Policy instances in the network

It provides :

  • Unified REST & DMAAP APIs for managing A1 Policies in all near-RT-RICs
  • Synchronized view of policy instances for each R-APP (soon)
  • Synchronized view of policy instances in all near-RT-RICs
  • Synchronized view of policy types in all near-RT-RICs
  • Policy Query API (e.g. per near-RT-RIC, per R-APP (soon), per policy type)
  • Unified nearRTRIC-ID to nearRTRIC-address mapping (e.g. can include mapping to A&A1, CMDBs etc to “find” near-RT-RICs - soon)
  • Placeholder “O1 ManagedElement” mapping database interface to find appropriate near-RT-RIC to address A1 operations for required RAN elements (e.g. connection to A&AI, RuntimeDB, other CMDBs etc - soon)
  • Monitors all near-RT-RICs and recovers from inconsistencies (multiple strategies - soon) – e.g. near-RT-RIC restarts
  • Support for different Southbound connectors per near-RT-RIC – e.g. different A1 versions, different near-RT-RIC version, different A1 adapter/controllers supports different or proprietary A1 controllers/EMSs

Controller / A1Adaptor:

This component provides a Northbound interface for policy management calls.

An OSGI feature was created as part of this implementation with 3 bundles, A1 client, Yang model  & Provider.

Please refer this page to know how to setup SDNC in local.

Near-RT-RIC Simulator:

This is implemented as a Springboot application which simulates the Near-RT RIC A1 operations and is used for testing.

  • No labels