...
- 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
...