Versions Compared

Old Version 5

changes.mady.by.user John Keeney

Saved on

compared with

New Version 6

changes.mady.by.user John Keeney

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 Feature Scope:

  • NONRTRIC Functions:
    • Integrated A1 Adapter from ONAP (controller – mediation)
    • Integrated A1 Policy Management Service from ONAP (controller – A1 policies)
    • OSC A1 Enrichment Information Coordinator (controller – 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)
    • OSC (initial) APP catalog (for registering/querying APPs)
    • Initial K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC)
    • Initial Service Exposure Function functionality
  • 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 fucntions 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 Cherry
    • 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

...

  1. Non-RT-RIC Control Panel

  2. Non-RT-RIC (Spring Cloud) Service Gateway
  3. Non-RT-RIC (Kong) Service Exposure Prototyping
  4. A1 Policy Management Service
  5. Enrichment Information Coordinator Service
  6. Initial Non-RT-RIC App Catalogue
  7. SDNC A1 Controller
  8. Near-RT RIC A1 Simulator
  9. Initial K8S Helm Chart LCM Manager
  10. Test Framework
  11. "Helloworld" O-RU Fronthaul Recovery use-case
  12. "Helloworld" O-DU Slice Assurance use-case

The code base for "DE" Release is in the NONRTRIC, NONRTRIC-ControlPanel, and A1-Simulator,  source repositories (Gerrit) - E Branch: 'e-release' branch)

Non-RT-RIC Control Panel

Graphical user interface to interact with the NONNon-RT-RIC services.

  • 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 Enrichment coordinator service
  • Configure A1 Policy Management Service (add/remove near-rt-rics)
  • Interacts with the A1-PolicyManagementService & A1-EI-Coordinator (REST NBIs) via Service Exposure gateway
  •  Implementation:

Please refer this developer guide to set up in your local environment. More information about Non-RT-RIC control panel can be found here.

Non-RT-RIC (Spring Cloud) Service Gateway

...

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.

Non-RT-RIC (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 

...

Kong is a cloud-native, high performance, scalable & Open source API Gateway. Kong comes in 2 flavoursflavors

  • Without Database
  • With Database like PostgreSQL or Cassandra

...

Kong installation done by nonrtric script is 'Without Database'.

A1 Policy Management Service (from ONAP CCSDK –

...

Istanbul)

A1 Controller Service above A1 Adaptor that provides:

...

...

Information Coordinator Service

Coordinate/Register Information Types, Producers, Consumers, and Jobs.
Coordinate/Register A1-EI Types, Producers, Consumers, and Jobs (A1 Enrichment Information Job Coordination).

  • Maintains a registry of:
    • A1-EI Data Information Types / schemasA1-EI
    • Information Producers
    • A1-EI Information ConsumersA1-EI
    • Information Jobs
  • A1-EI Information Query API (e.g. per producer, per consumer, per types)
  • Query status of A1-EI Information jobs
  • Monitors all near-RT-RICs and recovers from inconsistencies
  • After EIAfter Information-type/Producer/Consumer/Job is successfully registered delivery/flow can happen directly between Information Producers and Information Consumers
  • The Information Coordinator Service natively supports the O-RAN A1 Enrichment Information (A1-EI Producers (in SMO/NONRTRIC domain) and ) interface, supporting coordination A1-EI consumers (Jobs where information (A1-EI)flow from the SMO/Non-RT-RIC/rApps to near-RT-RICs in RAN domain)Being extended to coordinate non-A1 Enrichment Information exchange between NONRTRIC Appsover the A1 interface.

Documentation about the service can be found at:

(Initial) Non-RT-RIC APP catalog

Register for NONRTRIC APPs

...

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/dawn/

A1 Adaptor / Controller (from ONAP CCSDK –

...

Istanbul):

Mediation point for A1 interface termination in SMO/NONRTRIC

...

Near-RT-RIC 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-EnrichmentInformationEI)
  • 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-E1 EI consumers, etc)
  • All A1-AP versions supported

...

Initial K8S Helm Chart LCM Manager

...

A building block for coming releases as the R-APP rApp concept matures

  • Interfaces that accepts Non-RT-RIC App µServices Helm Charts
  • Support basic LCM operations
  • Onboard, Start, Stop, Modify, Monitor
  • Initial version co-developed with v. similar functions in ONAP
  • Limited functionality/integration for now

...

Information about the use case can be found at:

Code for the use case can be found at: