Versions Compared

Old Version 6

changes.mady.by.user Xiaohua Zhang

Saved on

compared with

New Version 7

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...


Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)


Mission: Better manageability of, for example, E2 connections, the RIC platform as well as xApps via the xApp frameworks Update to newer O-RAN specs (E2,A1,O2,O1) and related features.

Primary Goals: Support operator-initiated health-check via E2 and be able to close all current or reject all future E2 connections. More manageability of the RIC platform and xApps, including, for example, platform statistics from E2 and A1 and more capabilities in the language-specific xApp frameworks and SDL (shared data layer).
 Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces) // support for A1-EI (as per A1APv3.0) // support for O2 as per WG6 use cases // support for RIC-708 O1-CM to xApps // RIC-734 Include time series database into RIC platform (InfluxDB) for usage by xApps // RIC-421 O1 mediator graceful restart with O1 data being persisted over restarts // Concrete alarms from RIC platform (related to message overload): RIC-204, RIC-203 // SDK package, well documented interfaces to be used by xApps via xApp frameworks // Portability SDK (in xApp project) // REST interface for subscription management.

D release Drelease highlights (2020-12-01): 

PTL: Thoralf Czichy

Status 2020-12-11:


...


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 / SMO appliciations) to perform Non-RT-RIC tasks.
  • Non-RT-RIC will also host the new R1 interface (between rApps and SMO services)

D Feature Scope:

PTL: John Keeney

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



Operation and Maintenance (OAM)


Primary Goals:

Primary Goals:

  • support of the application LCM use case
    • Discussion about the details together with the SMO project
    • updates of OAM related interface definitions based on
      • YANG from WG4 - O-RAN Management Plane Specification - YANG Models 5.0 - November 2020 (with dependencies to IETF data models)
      • YAGN from WG5 - O-RAN O1 Interface for O-DU 1.0 - YANG Models - November 2020 (with dependencies to 3GPP data models)
      •  
      • YANG from WG1 - O1-interface (November 2020 train)
      • VES from ONAP DCAE - VES 7.2
      • VES bodies from 3GPP SA5 V16.6.0 - 
    • support D-Release use case "O-RU recovery"
    • handover SMO artifacts to new SMO project

    D Feature Scope: 

    -

    PTL: Martin Skorupski

    Status:

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

    Demo of OAM use cases

    ...