Versions Compared

Old Version 6

changes.mady.by.user John Keeney

Saved on

compared with

New Version Current

changes.mady.by.user John Keeney

Saved on

Key

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

Table of Contents
maxLevel

...

toc
2

Summary

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

  • 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 host the A1 interface (between NONRTRIC & near-RT RICs )
  • Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)

Release G

Priorities

Highlights

Count of Epics (20 issues), User Stories, Tasks, and Issues:  (455 issues)

  • R1 Service Exposure & Management

Continue
    • Continued work of Service execution platform extensions (K8s, Istio, Keycloak, OPA, Gateway) to enable and enforce service isolation & exposure
Extend Release F prototyping
    • Released first version of 3GPP CAPIF-aligned
Service Exposure Manager function (& API)
Align
    • Aligned with emerging proposals for R1-DME where possible
    • R1 DME Data Catalog support in NONRTRIC ICS 
    • R1 Data delivery & filtering (kafka & REST)
    • Demonstration: "PM Collection & Delivery to rApps"

  • rApp Manager

Build
    • Built on ONAP “Automation Composition” model & platform to implement rApp use cases
    • Demonstrate controlled on-boarding & LCM rApps with & without µService
    • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp
  • Investigate where parts of rApp executes in KNative environment (e.g. ML model part of an rApp)
    • Continue

    • A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

      • A1 Spec evolution
      • Southbound: A1 Interface
      • Northbound: R1-A1(P) & R1-DME Interfaces
    • Sample use cases (rApps)

    • Testing, Maintenance & Housekeeping

      • Function Test & Integration Test environment,
      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.


    Latest Architecture (Release

    ...

    G)


    NONRTRIC Architecture for OSC Release F

    NONRTRIC components (Release

    ...

    G)

    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. Information Coordinator Service
    6. DMaaP/Kafka Information Producer Adapters
    7. NONRTRIC CAPIF Core (Service Registry)
    8. Initial Non-RT-RIC App Catalogue
    9. A1 Policy Controller / Adapter
    10. A1 Interface Simulator
    11. Initial K8S Helm Chart LCM Manager
    12. Authentication Support (JWT Token Fetch)
    13. Test Framework
    14. "Helloworld" O-RU Fronthaul Recovery use case
    15. "Helloworld" O-DU Slice Assurance use case
    16. "Healthcheck" use case

    NONRTRIC Control Panel (Release

    ...

    G)

    Graphical user interface to interact with the Non-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 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:

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

    NONRTRIC (Spring Cloud) Service Gateway (Release F +)

    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.

    NONRTRIC (Kong) Service Exposure Prototyping (Release F +)

    Support Apps to use NONRTRIC, SMO and other App interfaces
    A building block for coming releases as the R1 Interface concept matures 

    • Support dynamic registration and exposure of service interfaces to Non-RT-RIC applications (& NONRTRIC Control panel)
    • Extends a static gateway function specifically for NONRTRIC Control panel
    • Initial version based on Kong gateway function
    • Initial exposure candidates include A1 (NONRTRIC) services & O1 (OAM/SMO) services

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

    • Without Database
    • With Database like PostgreSQL or Cassandra

    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 Management Service (from ONAP CCSDK – Jakarta)

    A1 Policy Controller Service above A1 Adapter that provides:

    NONRTRIC (Spring Cloud) Service Gateway (Release G)

    Enable Apps and the Control Panel to use A1 Services

    NONRTRIC (Kong) Service API Gateway (Release G)

    Support Apps to use NONRTRIC, SMO and other App interfaces through a gateway

    • Support dynamic registration and exposure of service interfaces to Non-RT-RIC applications (& NONRTRIC Control panel)
    • Extends a static gateway function specifically for NONRTRIC Control panel
    • Initial version based on Kong gateway function
    • Initial exposure candidates include A1 (NONRTRIC) services & O1 (OAM/SMO) services

    A1 Policy Management Service (from ONAP CCSDK – Kohn)

    A1 Policy Controller Service above A1 Adapter that provides: