Information regarding Release D for Non-Realtime RIC will be in this page.

Architecture for Release D:

<TBD>

NONRTRIC components:

1. Non-RT RIC Control Panel/ NONRTRIC Dashboard

2. Non-RT RIC (Spring Cloud) Service Gateway
3. Non-RT-RIC (Kong) Service Exposure prototyping
4. A1 Policy Management Service
   
5. Enrichment Information Coordinator
6. Non-RT-RIC Service Catalogue
7. SDNC A1 Controller
8. Near-RT RIC Simulator
9. Test Framework
10. Usecases

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
• Implementation:
  • 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

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 gateway code can be found at,

https://gerrit.o-ran-sc.org/r/gitweb?p=portal/nonrtric-controlpanel.git;a=tree;f=nonrtric-gateway;h=b3ecaa3969ff9122d60cf64b70ec1de4d87b0a4e;hb=refs/heads/master

More information on the Spring Cloud Gateway can be found in the documentation page below,

https://cloud.spring.io/spring-cloud-gateway/reference/html/#gateway-starter

Non-RT RIC (Kong) Service Exposure Prototyping

Kong is a cloud-native, high performance, scalable & Open source API Gateway. Kong comes in 2 flavour

• Without Database
• With Database like PostgreSQL or Cassandra

The Non-RT-RIC 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 deployment can be found at,

https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree;f=nonrtric/helm;h=f47c877aa769640a31596f3afbe845d8862da3a7;hb=refs/heads/master

More information on Kong API Gateway can be found at,

https://docs.konghq.com/gateway-oss/

A1 Policy Management Service (from ONAP CCSDK – Guilin)

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

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

A1 Enrichment Information Job Coordination Service

Coordinate/Register A1-EI Types, Producers, Consumers, and Jobs.

• 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)

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

(Initial) R-APP catalog

Register for R-APPs

• First step towards R-APP management in NONRTRIC
• R-APPs can be registered / queried

More work required in coming releases as the R-APP concept matures

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

Controller / OSC A1 Adaptor (from ONAP CCSDK – Guilin):

Mediation point for A1 interface termination in SMO/NONRTRIC

• Implemented as OSGI Feature/Bundles
• A1 Rest southbound
• NETCONF YANG Northbound
• RESTCONF > NETCONF adapter
• Mapping logic / Provider
• Can be included in an any SDNC/CCSDK persona

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

Near-RT-RIC Simulator:

Stateful A1 test stub

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

https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface/en/latest/index.html