Versions Compared

Key

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

...

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

The service provides :

  • Unified REST API for managing A1 Policies in all near-RT-RICs.
  • A DMAAP DMaaP API for A1 Policy management.
  • Synchronized view of A1 Policy instances for each R-APP
  • Synchronized view of A1 Policy instances in each Nearnear-RT-RIC
  • Synchronized view of A1 Policy types supported by each Nearnear-RT-RIC
  • Lookup service to find the Nearnear-RT-RIC to control resources in the RAN as defined in  O1 (e.g. which Nearnear-RT-RIC should be accessed to control a certain CU or DU, which in turn controls a certain cell).
  • Monitors all Nearnear-RT-RICs and maintains data consistency  – e.g. recovery from Nearnear-RT-RIC restarts
  • Support for different Southbound APIs  to the Nearnear-RT-RICs (different versions of the A1-P and other similar APIs).

...

  • View and Manage A1 policies in the RAN (Nearnear-RT-RICs)
  • Interacts with the Policy Management Services’s Services NBI (REST API)
  • Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema
  • Frontend: Angular framework
  • Backend Java Springboot application
  • Please refer this developer guide to set up in your local environment.

...

  • Used to create multiple stateful A1 providers (simulated Nearnear-RT-RICs)
  • Implemented as a Java Springboot application
  • Swagger-based northbound interface, so easy to change the A1 profile exposed