Versions Compared

Old Version 6

changes.mady.by.user John Keeney

Saved on

compared with

New Version 7

changes.mady.by.user John Keeney

Saved on

Key

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

Draft

Table of Contents

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

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

  • R1 Service Exposure & Management

    • Continue work of Service execution platform extensions (K8s, Istio, Keycloak, OPA, Gateway) to enable service isolation & exposure
    • Extend Release F prototyping of 3GPP CAPIF-aligned Service Exposure Manager function (& API)

  • R1 Data Management & Exposure

    • Align with emerging proposals for R1-DME where possible
    • R1 DME Data Catalog support in NONRTRIC ICS 
    • R1 Data delivery & filtering (kafka & REST)

  • rApp Manager

    • Build 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)
    • Requirements Drivers for rApp/R1 development
    • High degree of cross-project integration activity

  • 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. Initial Non-RT-RIC App Catalogue
  8. A1 Policy Controller / Adapter
  9. A1 Interface Simulator
  10. Initial K8S Helm Chart LCM Manager
  11. Test Framework
  12. "Helloworld" O-RU Fronthaul Recovery use case
  13. "Helloworld" O-DU Slice Assurance use case
  14. "Healthcheck" use case

NONRTRIC Control Panel (Release

...

G)

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

...

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

...

G)

Support Apps to use A1 Services (May be replaced by Service Exposure function in later releases)

...

More information on the Spring Cloud Gateway can be found in the documentation here.

NONRTRIC (Kong) Service Exposure Prototyping (Release

...

G)

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

...

https://github.com/Kong/charts/blob/main/charts/kong/README.md

A1 Policy Management Service (from ONAP CCSDK –

...

Kohn)

A1 Policy Controller Service above A1 Adapter that provides:

...

Information Coordinator Service (ICS) (Release

...

G)

A service that coordinates Information Jobs, producers and consumers. Also acts as an A1 Enrichment Information Controller.

...

This API provides a means to monitor the health of this service.

DMaaP/Kafka Information Producer Adapters (Release

...

G)

Configurable mediators to take information from DMaaP (& Kafka) and present it as a coordinated Information Producer

...

(Initial)

...

NONRTRIC APP catalog (Release

...

G)

Register for NONRTRIC APPs

...

A1 Policy Controller / Adapter (from ONAP CCSDK –

...

Kohn)

Optional mediation point for A1 Policy interface termination in SMO/NONRTRIC

...

A1 Interface Simulator (Release

...

G)

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-EI)
  • 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-EI consumers, etc)
  • All A1-AP versions supported

  • Call-out feature to add applications-specific A1-Policy behaviors (REST & Kafka call-outs supported)

...

Initial K8S Helm Chart LCM Manager (Release

...

G)

Onboard, start, stop, and modify Non-RT-RIC App µServices as Helm Charts

...

NONRTRIC Test Platform (Release

...

G)

Information about the test platform can be found at:

Use Cases (Release

...

G)

"Helloworld" O-RU Fronthaul Recovery use case

...