The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.
Non-RT-RIC will define and coordinate rApps (Non-RT-RIC applications) to perform Non-RT-RIC tasks.
Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)
E Feature Scope / Achievements:
E Release Priorities:
ONAP Control Loop -> O-RAN rApp : “The rApp-ification of ONAP Control Loops”
Adopt ONAP CL work as a starting point, continue to identify gaps, then extend
Identify & motivate where an rApp is different from a CL
Types of rApps:
Microservice-based rApps
Non-Microservice-based rApps
NONRTRIC Service Exposure/Gateway -> O-RAN R1 : “The R1-ification of Service Exposure”
Service-independent aspects
Types of exposure support in R1:
Microservice-based rApps & Service
Non-Microservice-based rApps & Service
Use cases of rApps & Exposing specific Services via R1
Requirements drivers & demonstrators
O-RU FH recovery (multiple), O-DU Slice Assurance (multiple), Existing Function Tests, various other use cases in ONAP
Implement the O2 interface as the MVP Description: Design and implement O2 IMS and O2 DMS for O-RAN-SC INF project
Realize O2 Inventory API to expose O-Cloud resource to SMO
Realize O2 Subscription API to allow SMO subscribe for notification of resource changes
Realize O2 Deployment Service API (as a PoC) to allow SMO deploy CNF in helm charts to O-Cloud.
Major components upgrade Description: Upgrade the following major components and all dependent packages to align with StarlingX 5.0(more than 200 packages are upgraded):
Configuration Management
Fault Management
Host Management
Software Management
Service Management
Major dependent packages: kubernetes, helm, armada, ceph, etc.
Enable the AIO-DX with additional worker nodes deployment scenario Description: The All-in-one Duplex (AIO-DX) deployment provides a pair of high availability (HA) servers with each server providing all three cloud functions (Controller, Worker, and Storage). In addition, extra worker nodes (providing only Worker function for the cloud) can be added to extend the cloud capacity.
Jira: Count of Epics, User Stories, Tasks, and Issues:
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases
Feature Scope:
Automated CLM and SonarQube Scanning CI Jobs
Improve CI for OSC projects
Validate and and Test platform and use cases
A full integration of all OSC components are not ready yet. Within E release timeframe only limited integration tests were performed across OSC sub-modules, and around the network slicking use case.
