...
Primary Goals for Non-RealTime RAN Intelligent Controller (Non-RT-RIC)
|
Overall objective for the F ReleaseIn the E F Release we focus mainly on prototyping building blocks to support Non-RT-RIC Apps ("rApps") and R1 interface concepts from O-RAN. For the R1 interface we will focus on enabling Service Management & Exposure (R1-SME), and demonstrating Data Management & Exposure (R1-DME). |
F Release Priorities
|
F Release Feature Scope
|
Architecture for Release
...
- Deployment, Integration & Configuration– Continued improvements for Docker & Kubernetes
- Extended/Easier deployment options with OSC IT/DEP project (SMO/NONRTRIC deployment)
- O-RAN A1-AP evolution (v3.0)
- Evolution of A1-EI functions to a more generic Information Coordination functions, moving beyond A1-EI
- Further improvement in security management
- Re-architect & improve usability of Non-RT-RIC Control Panel (GUI)
- Extend NONRTRIC Control Panel to sort and filter A1 Policies
- Extend NONRTRIC Control Panel to sort and filter A1 Enrichment Types/Jobs
- Extend NONRTRIC Control Panel to configure A1 Policy Management Service
- Configurable Service Exposure function – Extends/Replaces static exposure gateway in OSC D-release
- K8S Helm Chart LCM function for App µServices
- Update NONRTRIC demo/test environment (one-click tests/use-cases, docker & single/multi-node K8s env)
- OSC e2e integration use case – O-RU-FH-HelloWorld recovery
- App to instigate O-RU-FH connection recovery after failure – via O-DU
- Multiple implementation options – standalone µService and/or deployable ONAP-PF policy script
- App to instigate O-RU-FH connection recovery after failure – via O-DU
- OSC e2e integration use case – O-DU-HelloWorld-SliceAssurance
- Closed loop tuning of RRM policies to assure Slice performance - via O-DU
- Multiple implementation options – standalone µService and/or deployable ONAP-PF policy script
- Closed loop tuning of RRM policies to assure Slice performance - via O-DU
F
NONRTRIC components
Non-RT-RIC Control Panel
Architecture for Release F
NONRTRIC components
Non-RT-RIC Control Panel
- Non-RT-RIC (Spring Cloud) Service Gateway
- Non-RT-RIC (Kong) Service Exposure Prototyping
- A1 Policy Management Service
- Information Coordinator Service
- DMaaP/Kafka Information Producer Adapters
- Initial Non-RT-RIC App Catalogue
- A1 Policy Controller / Adapter
- A1 Simulator (previously called Near-RT RIC A1 SimulatorInterface)
- Initial K8S Helm Chart LCM Manager
- Test Framework
- "Helloworld" O-RU Fronthaul Recovery use case
- "Helloworld" O-DU Slice Assurance use case
...
- "Healthcheck" use case
NONRTRIC Control Panel
Graphical user interface to interact with the Non-RT-RIC services.
With the OSC NONRTRIC Control Panel you can:
- View and Manage A1 policies in the RAN (near-RT-RICs)
- Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema
- View and manage producers and jobs for the Information Coordination Service
- Configure A1 Policy Management Service (add/remove near-rt-rics)
- Interacts with the A1-Policy Management Service & Information Coordination Service (REST NBIs) via Service Exposure gateway
- Implementation:
- FrontendFront-end: 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.
...
NONRTRIC (Spring Cloud) Service Gateway
Support Apps to use A1 Services (May be replaced by Service Exposure function in later releases)
...
More information on the Spring Cloud Gateway can be found in the documentation here.
...
NONRTRIC (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
...
- https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree;f=nonrtric/helm
NOTE: Kong installation done by nonrtric script is 'Without Database'.
More information on Kong API Gateway can be found a,
...
https://github.com/Kong/charts/blob/main/charts/kong/README.mdNOTE:
Kong installation done by nonrtric script is 'Without Database'.
A1 Policy Management Service (from ONAP CCSDK – Istanbul)
A1 Policy Controller Service above A1 Adapter that provides:
...
- https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/a1policymanagementservice
- https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-a1policymanagementservice/en/f-release
- https://docs.onap.org/projects/onap-ccsdk-oran/en/jakarta/
- A1 Policy Management Service in ONAP
...
Information Coordinator Service (ICS)
A service that coordinates Information Jobs, producers and consumers. Also acts as an A1 Enrichment Information Controller.
ICS is a data subscription service which decouples data producers from data consumers. A data consumer can create a data subscription (Information Job) without any knowledge of its data producers (one subscription may involve several data producers). A data producer has the ability to produce one or several types of data (Information Type). One type of data can be produced by zero to many producers.
...
A data consumer can be an R-App using R1 APIs, or a Nearnear-RT RIC , which may use using the A1-E API (where the subscribed data is more specifically called "Enrichment Information").
A data consumer can have several active data subscriptions (Information Job). One Information Job consists of the type of data to produce and additional parameters, which may be different for different data types. These parameters is not defined or limited by this service and may for instance include:
- Parameters related to delivery (Kafka stream, callback URL etc.). These are different for different delivery protocols.
- Filtering information (scope, filter or other discriminators).
- Period-icy
- Other info used for aggregation
Repository and documentation about the service can be found at:
- https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/informationcoordinatorservice
- https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-informationcoordinatorservice/en/f-release
APIs provided by the ICS service
A1-EI
This API is between Near-RT RIC and the Non-RT RIC. The Near-RT RIC is a data consumer, which creates Information Jobs to subscribe for data. In this context, the information is referred to as 'Enrichment Information', EI.
Data producer API
This API is provided by the Non-RT RIC platform and is intended to be part of the O-RAN R1 interface. The API is for use by different kinds of data producers and provides support for:
- Registry of supported information types and which parameters needed to setup a subscription.
- Registry of existing data producers.
- Callback API provided by producers to setup subscriptions.
Data consumer API
This API is provided by the Non-RT RIC platform and is intended to be part of the O-RAN R1 interface. The API is for use by different kinds of data consumers and provides support for:
- Querying of available types of data to consume.
- Management of data subscription jobs
- Optional callback API provided by consumers to get notification on added and removed information types.
Service status
This API provides a means to monitor the health of this service.
...
- A version implemented in Java (Spring) - Supporting filtered DMaaP and Kafka mediation:
- A version implemented in Go - Supporting DMaaP mediation:
(Initial)
...
NONRTRIC APP catalog
Register for NONRTRIC APPs
...
A1 Policy Controller / Adapter (from ONAP CCSDK – Istanbul)
Mediation Optional mediation point for A1 Policy interface termination in SMO/NONRTRIC
...
...
A1 Simulator
Stateful A1 test stub
- Used to create multiple stateful A1 providers (simulated near-rt-rics)
- Supports A1-Policy (A1-P) and A1-Enrichment Information (A1-EI)
- Implemented as a Python application
- Swagger-based northbound interface, so easy to change the A1 profile exposed (e.g. A1 version, A1 Policy Types, A1-EI consumers, etc)
- All A1-AP versions supportedversions supported
Call-out feature to add applications-specific A1-Policy behaviors (REST & Kafka call-outs supported)
Repository and documentation about the service Documentation about the simulator can be found at:
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface
- https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface/en/ef-release/
Initial K8S Helm Chart LCM Manager
...
Use Cases
"Helloworld" O-RU Fronthaul Recovery use case
A very simplified closed-loop rApp use case to re-establish front-haul connections between O-DUs and O-RUs if they fail. Not intended to to be 'real-world'
Information about the use case can be found at:
Code for the use case can be found atfound at:
- https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=test/usecases/oruclosedlooprecovery;hb=refs/heads/e-releaseRelease F: O-RU Fronthaul Recovery usecase
Repository and documentation about the service can be found at:
- https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/rapp/orufhrecovery
- https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-rapp-orufhrecovery/en/f-release
"Helloworld" O-DU Slice Assurance use case
A very simplified closed-loop rApp use case to re-prioritize a RAN slice's radio resource allocation priority if sufficient throughput cannot be maintained. Not intended to to be 'real-world'
Information about the use case can be found at:
Repository and documentation about the service can be found at:
- https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/rapp/ransliceassurance
- https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-rapp-ransliceassuranceenransliceassurance/en/f-release