Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release A:


Architecture for Release A:



NonRT RIC components:

  1. NonRT RIC Dashboard
  2. Policy agent
  3. SDNC A1 Controller
  4. Near-RT RIC Simulator


The Initial code base for Release A is at,

Non-RT-RIC


NonRT RIC Dashboard:

The NonRT RIC Dashboard is a graphical user  user interface that enables the user to manage the Policies in the network. The dashboard interacts with the Policy agent via its NBI (REST API).
The dashboard generates its GUI from JSON schemas in a model driven fashion.

The dashboards 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 Dashboard in local.

Policy Agent:

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 NearRT RIC instance and is owned by a 'service' (R-APP or the NonRT RIC Dashboard).
  • All NearRT RICs in the network. This information is configured using the ONAP CDS database (which is using the Cloudify Consul database).
  • All Policy types for all NearRT RICs
  • All configured Policy instances in the network

It provides an NBI for the R-Apps (and for the NonRT RIC Dashboard) for policy management. This is a REST API.
As an option, policy management can also be done via asynchronous messages through ONAP/Dmaap.
The NBI provides support for an R-APP to locate the correct NearRT RIC based on identifiers as defined in O1.

The agent monitors all NearRT RICs and recovers from data inconsistencies, which may happen when (for instance) an NearRT RIC restarts.

The R-APPs can be monitored so that their Policies can be automatically removed when an R-APP is stopped/removed.

On its southbound side the agent can connect to a number of different A1 providers:

  • Directly to the NonRT RIC:
      - OSC API, which is influenced by the A1 standard
      - The NonRT RIC simulator, which supports the A1 standard with a number of not yet approved
        CRs included.
  • To a ONAP style controller.

Detection of A1 provider API type (one of the above) is done automatically in runtime.

SDNC:

This component provides a Northbound interface for policy management calls. An OSGI feature is 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.