Primary Goals for Non-RealTime RAN Intelligent Controller (Non-RT-RIC)
|
Overall objective for the F ReleaseIn the 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
|
Non-RT-RIC Control Panel
Graphical user interface to interact with the Non-RT-RIC services.
With the OSC NONRTRIC Control Panel you can:
Please refer this developer guide to set up in your local environment. More information about Non-RT-RIC control panel can be found here.
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 Micro-service architecture. In Non-RT-RIC we build the basic API gateway using spring cloud gateway which then exposes two Non-RT-RIC functions; Policy Management Service & Enrichment Coordinator Service. You can add predicates through code or yaml and in Non-RT-RIC we prefer to use yaml.
NONRTRIC gateway code can be found at:
More information on the Spring Cloud Gateway can be found in the documentation here.
Support Apps to use NONRTRIC, SMO and other App interfaces
A building block for coming releases as the R1 Interface concept matures
Kong is a cloud-native, high performance, scalable & Open source API Gateway. Kong comes in 2 flavors
The NONRTRIC Kubernetes deployment will deploy Kong if the installKong flag is set to true. During uninstallation of nonrtric components it will also remove Kong if it's deployed by nonrtric script.
If the ingress enabled flag is set to true then it will create the ingress objects for A1 Policy & Enrichment Service so the Kong gateway (acts as ingress controller) will expose these functions.
NONRTRIC Kubernetes deployment can be found at:
More information on Kong API Gateway can be found a,
https://docs.konghq.com/gateway-oss/
https://github.com/Kong/charts/blob/main/charts/kong/README.md
A1 Policy Controller Service above A1 Adapter that provides:
Repository and documentation about the service can be found at:
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 near-RT RIC 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:
Repository and documentation about the service can be found at:
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.
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:
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:
This API provides a means to monitor the health of this service.
Configurable mediators to take information from DMaaP (& Kafka) and present it as a coordinated Information Producer
Two alternative implementations to allow Information Consumers to consume DMaaP or Kafka events as coordinated Information Jobs.
These configurable adapters/mediators act producers of Information Coordinator Service (ICS) jobs by polling topics in DMaaP Message Router (MR) or Kafka and pushing the messages to a consumer.
Register for NONRTRIC APPs
Repository and documentation about the service can be found at:
Optional mediation point for A1 Policy interface termination in SMO/NONRTRIC
Documentation about the adapter / controller can be found at:
Stateful A1 test stub
Call-out feature to add applications-specific A1-Policy behaviors (REST & Kafka call-outs supported)
Repository and documentation about the service can be found at:
Onboard, start, stop, and modify Non-RT-RIC App µServices as Helm Charts
A building block for coming releases as the rApp concept matures
Repository and documentation about the service can be found at:
Information about the test platform can be found at:
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:
Repository and documentation about the service can be found at:
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: