...
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 F
...
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
- Near-RT RIC A1 Simulator
- 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
Non-RT-RIC 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
...
- https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree;f=nonrtric/helmtree;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)
...
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:
...
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'
...
- 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'
...