Versions Compared

Key

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

...

Interacts with the Policy agent’s Management Services’s NBI (REST API)

Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema

...

A1 Policy Management Service (“Policy Agent”)

The Policy Agent Management Service 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 Near-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 for all supported by each Near-RT RICs

All configured Policy instances in the network

RIC

The service It provides :

Unified REST & DMAAP APIs API for managing A1 Policies in all near-RT RICs.

A DMAAP API for A1 Policy management.

Synchronized view of policy A1 Policy instances for each R-APP (soon)

Synchronized view of policy A1 Policy instances in all each Near-RT RICsRIC

Synchronized view of policy types in all A1 Policy types supported by each Near-RT RICsRIC

Lookup service to find the Policy Query API (e.g. per Near-RT RIC , per R-APP (soon), per policy type)Unified nearRTRIC-ID to nearRTRIC-address mapping to control resources in the RAN as defined in  O1 (e.g. can include mapping to A&AI, CMDBs etc to “find” Near-RT RICs - soon)Placeholder “O1 ManagedElement” mapping database interface to find appropriate which Near-RT RIC to address A1 operations for required RAN elements (e.g. connection to A&AI, RuntimeDB, other CMDBs etc - soon)should be accessed to control a certain CU or DU, which in turn controls a certain cell).

Monitors all Near-RT RICs and recovers from inconsistencies (multiple strategies - soon) maintains data consistency  – e.g. Near-RT RIC restarts

Support for different Southbound connectors per APIs  to the Near-RT RIC – e.g. different A1 versions, different Near-RT RIC version, different A1 adapter/controllers supports different or proprietary A1 controllers/EMSsRICs (different versions of the A1-P and other similar APIs).

Controller / A1 Adapter:

Mediation point for A1 interface termination in SMO/NONRTRICNon-RT RIC

Implemented as OSGI Feature/Bundles

...

Can be included in an any SDNC/CCSDK persona

Near-RT RIC Simulator:

Stateful A1 test stubA1 simulator used for testing purposes

Used to create multiple stateful A1 providers (simulated Near-RT RICs)

...