Architecture for New Delhi Release:
A1 Policy components (subset of 'Non-RealTime RIC'):
- A1 Policy Management Service (In ONAP CCSDK/SDNC)
- SDNC A1 Adapter (In ONAP CCSDK/SDNC)
- Near-RT RIC / A1 Simulator (in O-RAN Source Software Community (OSC)) (Wiki)
- A1 Policy Management GUI / NONRTRIC Dashboard (in O-RAN Source Software Community (OSC)) (Wiki)
Source code &
...
Documentation
- The source code is available in: ONAP CCSDK (O-RAN) Gerrit repo ('master' branch)
- Support functions available in OSC repos: OSC A1-Simulator (Gerrit) & OSC NONRTRIC Control Panel (Gerrit)
- The Official Documentation can be found at https://docs.onap.org/projects/onap-ccsdk-oran
- Additional Non-RealTime RIC functions are developed in the OSC NONRTRIC project - which reuses these A1 Policy components.
...
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CCSDK-3965
ONAP A1 Policy Management Service (ONAP
...
CCSDK)
The Policy Management Service is a micro service which maintains a transient repository of:
- All A1 policies instances in the network. Each policy is targeted to a near-RT-RIC instance and is owned by a 'service' (R-APP e.g., rApps or the NONRTRIC Dashboard).
- All near-RT-RICs in the network.
- All Policy types supported by each near-RT-RIC.
...
- Unified REST API for managing A1 Policies in all near-RT-RICs.
- Compliant with O-RAN R1 specification for A1-Policy Management (R1-AP v5.0, with additional features & fixes)
- Synchronized view of A1 Policy instances for each rAPP
- Synchronized view of A1 Policy instances in each near-RT-RIC
- Synchronized view of A1 Policy types supported by each near-RT-RIC
- Lookup service to find the near-RT-RIC to control resources in the RAN as defined in O1 (e.g. which near-RT-RIC should be accessed to control a certain CU or DU, which in turn controls a certain cell).
- Monitors all near-RT-RICs and maintains data consistency – e.g. recovery from near-RT-RIC restarts
- Support for different Southbound APIs to the near-RT-RICs (different versions of the A1-P and other similar APIs).
- HTTPS can be configured to use a supplied certificate/private key and to validate peers towards a list of trusted CAs/certs.
- HTTP proxy support for tunneling HTTP/HTTPS connections.
- Fine-grained access-control - with new optional callouts to an external auth function
- Fine-grained monitoring metrics, logging & call tracing can be configured
The REST API can be found at
...