Versions Compared

Old Version 8

changes.mady.by.user John Keeney

Saved on

compared with

New Version 9

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) - 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)Registration & Discovery service
    • Demonstration: "Enforcing Service Exposure for rApps"

  • R1 Data Management & Exposure

    • 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)
    • Partly demonstrated: "Deploying & Running NONRTRIC platform and rApps"

  • Continued 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.

...