Versions Compared

Old Version 70

changes.mady.by.user user-30c9d

Saved on

compared with

New Version 71

changes.mady.by.user SUNIL SINGH

Saved on

Key

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

...

Near-Real-time RIC X-APPs (RICAPP)

Primary Goals: Expand the community working on open source xApps for O-RAN SC. Enhance the set of open source xApps in support of the R-SAC use cases (traffic steering, network slicing) as well new use cases. Update and enhance existing xApps to take advantage of the new features in xApp SDK (implemented by the xApp frameworks in C++, go, and python).

E release plan (12-01-21):

  • New xApps: RC (RAN Control) by Mavenir - implements subset of E2 SM RC
  • Improved xApps:
    • LP (Load Prediction) by ChinaMobile: Include trained ML model, will populate predictions in inFlux DB
    • AD (Anomaly Detection) by HCL: Will identify a new anomaly type (area anomaly), use geo-location as a feature. Dependency on Data Stream from KPIMON to influxDB. (Currently AD is working on Static data).
    • QP (QoE Predictor) by HCL: Include prediction for current serving cell, incorporate predicted load as a feature, provide sequence of predictions.
    • TS (Traffic Steering) by UTFPR (University, Parana, Brazil): Call RC xApp to trigger UE handover, improvements in traffic steering logic.
    • Bouncer by HCL: Increase performance and functional testing capabilities; continue identifying RIC platform bottlenecks.
    • HW (HelloWorld) demo xApps in C++, go and python by AT&T and Samsung: Add usage of more platform features, update usage of platform features that are evolving.
  • Integration of AD, QP, TS, LP, RC, and KPIMON with Viavi simulator.
  • Extensive performance benchmarking of the RIC platform using Bouncer and E2 Simulator (HCL)
  • Design for xApps to support network slicing use case.

PTL: SUNIL SINGH  (former PTL still helping out: Matti Hiltunen)

Jira: Count of Epics, User Stories, Tasks, and Issues:  165 issues

E release highlights/accomplishments (12-14-21):

  • The release introduces a new xApp RC (RAN Control) from Mavenir. RC implements a subset of the new E2 SM RC to support traffic steering end to end use case.
    The AD (Anomaly Detection) and QP
  •  QP (QoE Prediction) xApps from HCL introduce a new anomaly type and other extensions to support the traffic steering use caseinclude prediction for current serving cell, incorporate predicted load as a feature, provide sequence of predictions.
  • The Bouncer xApp from HCL ....
  • The LP (Load Prediction) xApp from CMCC now includes a trained ML model (and the issue of how to handle large trained ML models was resolved.)
  • The TS (Traffic Steering) xApp maintained by the Federal Technological University of Parana, Brazil includes the ability to call the new RC xApp via gRPC-based interface.
  • The demo HW (HelloWord) xApps in python and go from Samsung include additional functionality.
  • The AD, QP, and TS xApps have been integration tested using Viavi E2 tester.

E release source code, container images and deployment instructions

Each repository has a branch named "e-release" that can be accessed using git. For example, the source code for the AD xApp can be retrieved using  "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/ric-app/ad". The other xApps in the E release can be found at ric-app/qp, ric-app/ts, ric-app/lp, ric-app/hw, ric-app/hw-go, ric-app/hw-python, ric-app/mc, ric-app/bouncer, ric-app/rc, and scp/ric-app/kpimon. Note that the other ric-app repos are obsolete.

Note that this branch is in maintenance and all new development is done in branch "master".

In order to deploy the E release xApps,  you can re-use the pre-created container images as defined here and the instructions on testing the xApps can be found here.


...

Operation and Maintenance (OAM)

Primary Goals:

  • Support of RSAC 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 approach (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"

See more details on OAM wiki: E-Release

E Feature Scope: 

  • Switch to Opendaylight version Silicon-SR2
  • Standard-defined VES for
    • NotifyNewAlarm
    • NotifyAlarmCleared
    • NotifyHeartbeat
    • NotifyMoiChanges
    • PerfDataStreamingMNS (does not include measurements - therefor a O-RAN-SC specific message-body required - ...hello-world.oas3.yaml)

PTL: Martin Skorupski

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:

...

Simulators (SIM)

Primary Goals:

  • Support rapid prototyping by providing simulated interfaces

E Feature Scope:

  • Support of O-RAN-SC E-Release Network Slicing use case by Radisys - support of O-DU projects for end-to-end closed loop use cases for RAN network slicing (implement any message flows in the O-DU Simulator, if needed)
  • Align O1 Simulator with the latest specifications released by O-RAN Alliance.
  • Support of NETCONF CallHome via TLS, for the O1 simulator
  • VES stdnDefined stndDefined implementation

PTL: Alex Stancu

Jira: Count of Epics, User Stories, Tasks, and Issues:  5 issues

Status:

  • Implemented Network Slicing support in the O1 Simulator:
    • support for the new O-DU hello world YANG model from OAM project
    • support for creating VES subscriptions
    • support for creating PM Jobs which send VES PM stndDefined 

E release source code, container images and deployment instructions

Source code: https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fo1-interface.git;a=shortlog;h=refs%2Fheads%2Fe-release

Container images are described here: Simulation (E-Release)

Instructions: Network Slicing Use Case

E release source code, container images and deployment instructions

TODO


Infrastructure (INF)

Primary Goals: 

  • Implement the O-Cloud reference design, provide the real time performance to allow the O-DU and other components running on top of it.
  • Provide interaction capabilities with other components.

E release Feature Scope:  

  • Enable the 2 AIO severs with additional worker nodes deployment scenario
  • Major components upgrade
  • Implement the O2 interface as the MVP

PTL: Jackie Huang

Jira: Count of Epics, User Stories, Tasks, and Issues:

Update at   

  • EPICs:
    • Jira
      serverORAN Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
      keyINF-193
      • 5 sub-tasks:
        • 2 done
        • 2 in-progress
        • 1 not started
    • Jira
      serverORAN Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
      keyINF-173
      • 3 sub-tasks:
        • AIO-SX done: 
          • Jira
            serverORAN Jira
            serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
            keyINF-224
        • AIO-DX done: 
          • Jira
            serverORAN Jira
            serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
            keyINF-225
        • AIO-DX + worker done with defects: 
          • Jira
            serverORAN Jira
            serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
            keyINF-226
          • Jira
            serverORAN Jira
            columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
            keyINF-240
    • Jira
      serverORAN Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
      keyINF-215
      • 8 sub-tasks
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-217
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-218
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-219
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-220
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-221
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-222
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-223
        • Jira
          serverORAN Jira
          serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
          keyINF-231
  • Issues:
    • Jira
      serverORAN Jira
      serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
      keyINF-240
    • Jira
      serverORAN Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
      keyINF-241


Test status:


Release Note:

  • TODO once released

E release source code, container images and deployment instructions

  • TODO once released
  • No container image for INF project
  • Deployment instruction: TODO


...