Versions Compared

Key

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

...

Non-Real-time RIC (A1 Interface) (NONRTRIC)

Primary Goals:
  • 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 also host the new R1 interface (between rApps and SMO/NONRTRIC services)

E Feature Scope:

D Feature Scope:

  • NONRTRIC Functions: (NONRTRIC Release E Wiki)
  • In D Release: (NONRTRIC Release E Wiki)
More detail:
  • For documentation, guides and a full discussion of NONRTRIC D Release see NONRTRIC: Release E

Jira:


    • Integrated A1 Adapter from ONAP (controller – mediation)
    • Integrated A1 Policy Management Service from ONAP (controller – A1 policies)
    • rApp/Control Loop Manager (ONAP & OSC)
    • OSC Enrichment Information Coordinator (controller – Data exposure & 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 APP catalog (for registering/querying APPs)
    • K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC)
    • Exposure Gateway Functions
    • DMaaP → Information producer Mediator/Adapter
    • PM File Job Manager (ONAP & OSC) - TBC
  • E Release discussions: (NONRTRIC Release E Wiki)

Jira:

D release source code, container images and deployment instructions

  • Source Code:
  • Docker Images:
    •  
  • Deploy / Run:
  • Documentation:


Operation and Maintenance (OAM)

Primary Goals:

  • Support of RASC VES architecture updates
    • Deployment of VES-Collector and Message Bus at the edge
  • Support of O-DU use case ()
    • Definition of the to be used yang model. 
  • Support of pre-spec PM streaming - VES like approch (see https://wiki.o-ran-sc.org/download/attachments/35881433/E_rel_v3.pptx?api=v2 page #97)
    • creation of a CR to WG10 OAM Interface Specification - "Model-driven PM streaming"

E Feature Scope: 

  • Switch to Opendaylight version Silicon -SR2
  • Standard-defined VES for
    • NotifyNewAlarm
    • NotifyAlarmCleared
    • NotifyHeartbeat
    • NotifyMoiChanges
    • PerfDataStreamingMNS

E release source code, container images and deployment instructions (and status)

Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues:  166 issues

Source Code:

Integration:

  • to be done

Release notes:

  • to be done

...