Versions Compared

Old Version 7

changes.mady.by.user John Keeney

Saved on

compared with

New Version 8

changes.mady.by.user John Keeney

Saved on

Key

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

Table of Contents
maxLevel2

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.

...

...

APIs provided by the ICS service

...

...

NONRTRIC

...

rApp catalog (Release G)

Register for NONRTRIC APPs (rApps)

  • APPs rApps can be registered / queried
  • Limited functionality/integration for nowA building block for coming releases as the R-APP concept matures

Repository and documentation about the service can be found at:

A1 Policy Controller / Adapter (from ONAP CCSDK – Kohn)

...

Documentation about the adapter / controller can be found at:

...

Initial K8S Helm Chart LCM Manager (Release G)

...

NONRTRIC Test Platform (Release G)

...

Information about the use case can be found at:

Repository and documentation about the service can be found at:

"Helloworld" O-DU Slice Assurance use case

...

Information about the use case can be found at:

Repository and documentation about the service can be found at: