Primary Goals for Non-RealTime RAN Intelligent Controller (Non-RT-RIC):

• 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 applications (rApps) 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 define and coordinates rApps (Non-RT-RIC applications) to perform Non-RT-RIC tasks.
• Non-RT-RIC hosts the new R1 interface (between rApps and SMO/NONRTRIC services)

Overall objective for the E Release:

In the E Release we focus mainly on studying and providing some building blocks to support the emerging Non-RT-RIC Apps ("rApps") and R1 interface concepts from O-RAN.
Support and improvement of functions for the O-RAN A1 interface continue.

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
• Continued Evolution & Support for A1 functions

E Release Feature Scope:

• NONRTRIC Functions:
  
  • Integrated A1 Adapter from ONAP (A1 Policy (A1-P) controller – mediation)
  • Integrated A1 Policy Management Service from ONAP (A1 Policy (A1-P) controller)
  • rApp/Control Loop Manager (ONAP & OSC)
  • OSC Information Coordinator (controller – Data Management & Exposure & A1 Enrichment Information (A1-EI) Job management)
  • OSC Non-RT-RIC Control Panel (GUI – for A1-P & A1-EI Job management)
  • OSC A1 Simulator (a stateful test stub to simulate near-RT-RIC end of A1 interface – A1-P & A1-EI)
  • Initial OSC APP catalog (for registering/querying APPs)
  • K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC)
  • Exposure Gateway Functions
  • Coordinated service exposure for R1 interface
  • DMaaP → Information Producer Mediator/Adapter (multiple)

• In E 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
  • 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