...
Architecture for Release D:
<TBD>
NONRTRIC components:
Non-RT-RIC Control Panel/ NONRTRIC Dashboard
- Non-RT-RIC (Spring Cloud) Service Gateway
- Non-RT-RIC (Kong) Service Exposure prototypingPrototyping
- A1 Policy Management Service
- Enrichment Information Coordinator
- Initial Non-RT-RIC Service App Catalogue
- SDNC A1 Controller
- Near-RT RIC Simulator
- Initial K8S Helm Chart LCM Manager
- Test FrameworkUsecases
- "Helloworld" O-RU Fronthaul Recovery use-case
The code base for "Dawn" Release is in the NONRTRIC, NONRTRIC-ControlPanel, and A1-Simulator, source repositories (Gerrit) - Cherry Branch <To be updated>
Non-RT-RIC Control Panel / NONRTRIC Dashboard
Graphical user interface
- View and Manage A1 policies in the RAN (near-RT-RICs)
- Interacts with the Policy agent’s NBI (REST API)
- Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema
- View and manage producers and jobs for the Enrichment coordinator service
- Configure A1 Policy Management Service (e.g. add/remove near-rt-rics)
- Interacts with the A1-PolicyManagementService & A1-EI-Coordinator (REST NBIs) via Service Exposure gateway
- ImplementationImplementation:
- Frontend: Angular framework
- Repo: portal/nonrtric-controlpanel/web-frontend
Please refer this developer guide to set up in your local environment. More information about Non-RT Ric control panel can be found here.
Non-RT-RIC (Spring Cloud) Service Gateway
Support Apps to use A1 Services (May be replaced by Service Exposure function in later releases)
Spring cloud Gateway provides the library to build the API Gateway for Microservice architecture. In Non-RT-RIC we build the basic API gateway using spring cloud gateway which then exposes 2 Nonrtric functions Policy Management Service & Enrichment Coordinator Service. You can add predicates through code or yaml and in Nonrtric we prefer to use yaml.
Nonrtric NONRTRIC gateway code can be found at,
More information on the Spring Cloud Gateway can be found in the documentation page below,
...
Non-RT RIC (Kong) Service Exposure Prototyping
Support Apps to use NONRTRIC, SMO and other App interfaces
A building block for coming releases as the R1 Interface concept matures
- Support dynamic registration and exposure of service interfaces to Non-RT-RIC applications (& NONRTRIC Control panel)
- Extends a static gateway function specifically for NONRTRIC Control panel
- Initial version based on Kong gateway function
- Initial exposure candidates include A1 (NONRTRIC) services & O1 (OAM/SMO) services
Kong is a cloud-native, high performance, scalable & Open source API Gateway. Kong comes in 2 flavourflavours
- Without Database
- With Database like PostgreSQL or Cassandra
The Non-RT-RIC kubernetes NONRTRIC Kubernetes deployment will not deploy Kong but if its already deployed then it will create the Ingress Objects to expose Policy Management Service & Enrichment Coordinator Service.
Nonrtric kubernetes NONRTRIC Kubernetes deployment can be found at,:
More information on Kong API Gateway can be found at , https://docs.konghq.com/gateway-oss/
A1 Policy Management Service (from ONAP CCSDK –
...
Honolulu)
The A1 Policy Management Service is a microservice which maintains a transient repository of:
- All configured A1 policies instances in the network.
- All NearRT RICs in the network.
- All Policy types for all Near-RT-RICs
- All configured Policy instances in the network
- (Optionally deploy without A1 Adaptor to connect direct to near-RT-RIC)
It Controller Service above A1 Adaptor that provides:
- Unified REST & DMAAP APIs for managing A1 Policies in all near-RT-RICs
- Synchronized view of policy instances for each R-APP (soon)
- Operations:
- Query A1 Policy Types in
- near-RT-RICs
- Create/Query/Update/Delete A1 Policy Instances in 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
- Query Status for A1 Policy Instances
- Maintains (persistent) cache of RAN’s A1 Policy information
- Support RAN-wide view of A1 Policy information
- Streamline A1 traffic
- Enable (optional) re-synchronization after inconsistencies / near-RT-RIC restarts
- Added support for multiple near-RT-RICs (& multi-version support)
- Unified REST & DMaaP NBI
- Converged ONAP & O-RAN-SC A1 Adapter/Controller functions in ONAP SDNC/CCSDK
- (Optionally deploy without A1 Adaptor to connect direct to near-RT-RICs)
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/enen/cherry/
A1 Enrichment Information Job Coordination Service
...
- Maintains a registry of:
- A1-EI Data Types / schemas
- A1-EI Producers
- A1-EI Consumers
- A1-EI Jobs
- A1-EI Query API (e.g. per producer, per consumer, per types)
- Query status of A1-EI jobs
- Monitors all near-RT-RICs and recovers from inconsistencies
- After EI-type/Producer/Consumer/Job is successfully registered delivery/flow can happen directly between A1-EI Producers (in SMO/NONRTRIC domain) and A1-EI consumers (near-RT-RICs in RAN domain)
- Being extended to coordinate non-A1 Enrichment Information exchange between NONRTRIC Apps
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/
(Initial)
...
APP catalog
Register for R-APPsNONRTRIC APPs
- First step towards R-APP management in NONRTRIC
- R-APPs can be registered / queried
...
- Limited functionality/integration for now
- A building block for coming releases as the R-APP concept matures
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/
...
A1 Adaptor / Controller (from ONAP CCSDK –
...
Honolulu):
Mediation point for A1 interface termination in SMO/NONRTRIC
- Implemented as CCSDK OSGI Feature/Bundles
- A1 Rest REST southbound
- RESTCONF Northbound
- NETCONF YANG Northbound> RESTCONF > NETCONF adapter
- Mapping logic / Provider
- Can be included in an any controller based on ONAP CCSDK
- OSC Dawn will continue to support both a dedicated A1-controller persona (NONRTRIC) and an SDNC/CCSDK personaSDNR persona (IT/DEP, OAM/SMO)
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/enen/cherry/
Near-RT-RIC Simulator:
Stateful A1 test stub
- Used to create multiple stateful A1 providers (simulated near-RTrt-RICs)rics)
- Supports A1-Policy and A1-EnrichmentInformation
- Implemented as a Java Springboot Python application
- Swagger-based northbound interface, so easy to change the A1 profile exposed (e.g. A1 version, A1 Policy Types, A1-E1 consumers, etc)
- All A1-AP versions supported
https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface/enen/latest/index.htmlindex.html
Initial K8S Helm Chart LCM Manager
Onboard, start, stop, and modify Non-RT-RIC App µServices as Helm Charts
A building block for coming releases as the R-APP concept matures
- Interfaces that accepts Non-RT-RIC App µServices Helm Charts
- Support basic LCM operations
- Onboard, Start, Stop, Modify, Monitor
- Initial version co-developed with v. similar functions in ONAP
- Limited functionality/integration for now