You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Welcome to the E release page for the O-RAN Software community.

The E release is currently under development and its source code is maintained within teh master branch of each repo. Once released further instructions related to separate maintenance branches and release image lists will be available here,

        


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 (9-21-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.
    • 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: Matti Hiltunen

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

Status (9-21-21): 

  • RC: Committers identified, design agreed, repo requested
  • LP: Trained ML-model added to the xApp
  • AD: Work on new anomaly type in progress
  • HW: New functionality added to HW-go and HW-python.
  • Bouncer: Bottleneck with E2 Subscriptions identified in RIC platform.
  • Discussions on network slicing use case with HCL, Viavi, UTFPR.

E release source code, container images and deployment instructions

Will be provided when E Release is ready.

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

Mission: E2 updates with first E2APv1.1 support and improvements in E2 subscription handling. A1 reimplementation

Original primary goals: Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (RIC-638, even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces (RIC-640)) // RIC-809 Subscription manager to delete subscriptions in case of E2 disconnect (incl. Xapp changes) // RIC-793 Prevent A1 Job ID conflicts from multiple RICs using the same A1 producer (SMO) // RIC-647 Reimplement A1 mediator in golang to avoid A1 being the only python container in RIC platform // RIC-709 E2 stats exposing individual counters instead of groups // RIC-714 support for DMS REST interface in addition to DMS CLI // RIC-113 DB: SDL CLI for debugging and testing // RIC-110 FindKeys/GetAllKeys SDL API to support glob-style patterns // 34 Epics planned: link and 30 items as stretch goals: link

Achieved E release highlights = high-level release notes (TODO) below (note that the release image list is here (once releases): TODO)

TODO once released

PTL: Thoralf Czichy

Status 2021-09-15: we are working on implementing the planned development items

E release source code, container images and deployment instructions

We again plan to cut a branch from the master branch once the E release is released and goes into maintenance. Also we plan to provide an ready-made container image list.

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:

  • 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

PTL: 

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

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:

  • to be done

O-RAN Central Unit (OCU)

Primary Goals: 
  • In the absence of O-CU, Radisys commercial CU image to be used for E2E testing

D Release Feature Scope: 

  • Radisys Commercial CU being used as a test fixture for E2E testing
PTL:

Status:

Radisys Commercial CU being used as a test fixture.

H/W and S/W requirements have been shared and awaiting the same to be configured.

D release source code, container images and deployment instructions

not applicable

O-DU High

Primary Goals: 

New Feature Development

  • Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)

  • Only slot based round robin scheduling support for multi UE scheduling

  • Support for Multi Bearer

  • Basic RAN slicing support
  • Support for HARQ

Feature Verification

  • Closed Loop Automation Feature Verification
  • 16 QAM and 64 QAM Support Verification

End to End Integration Support

  • TDD/Mu1/100MHz

  • FDD/Mu0/20MHz * (Spillover from D release)

E Feature Scope: 

  • Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)

  • Only slot based round robin scheduling support for multi UE scheduling

  • Support for Multi Bearer

  • Basic RAN slicing support
  • Support for HARQ
  • End to End Integration Support (TDD and FDD stack validation)
  • Closed Loop Automation Feature Verification

PTL: user-30c9d

Status:

Updated:  15th Sept 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities

E release source code, container images and deployment instructions


O-DU Low

Primary Goals:  

—Continue O-DU low and O-DU high pairwise test.

—FAPI P7 message integration -> Ongoing

—Continue O-DU Low and O-RU emulator test.

—Further CU plane testing -> Ongoing

—Continue E2E test with UE simulator.

—Support the UE attachment test

—Development activity for Closed Loop Automation use-case

—Support and test for cell stop and restart within O-DU High layers


E Release Feature Scope: 


PTL: Luis Farias , Alternate: @Chenxi Yue

  • Status

E release source code, container images and deployment instructions

TODO

Simulators (SIM)

Primary Goals:

  • Support rapid prototyping by providing simulated interfaces

E Feature Scope:

PTL: Alex Stancu

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

Status:


E release source code, container images and deployment instructions

Docker container images are described here.

Each repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/sim/o1-interface". Make sure to replace the URL with correct repositories. Note that this branch is in maintenance and all new development is done in branch "master". The complete list of repositories belonging to the SIM project is here.

Deployment instructions here.

Please see:  Use Case Flow tests for E-Release

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   

  • INF-193 - Getting issue details... STATUS
    • 5 sub-tasks:
      • 2 done
      • 2 in-progress
      • 1 not started
  • INF-173 - Getting issue details... STATUS
    • 3 sub-tasks:
      • 1 done
      • 1 in-progress
      • 1 not started
  • INF-215 - Getting issue details... STATUS
    • 7 sub-tasks
      • 4 done
      • 3 not started

Test:

  • TODO

Release Note:

  • TODO once released

E release source code, container images and deployment instructions

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


Integration and Test (INT)

Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases

Feature Scope: 

  • Automated CLM and SonarQube Scanning CI Jobs
  • Improve CI for OSC projects
  • Validate and and Test platform and use cases 


PTL: 

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


E release source code, container images and deployment instructions

not applicable

Documentation (DOC)

Primary Goals: TODO
Bronze Feature Scope: TODO

PTL: weichen ni

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

D release source code, container images and deployment instructions

not applicable

Service Management and Orchestration  (SMO)

Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). 

E Feature Scope: In E-release, SMO will be extended to support network slicing. In particular, RSAC has come up with closed loop automation use case for network slicing which involves the SMO collecting PM counters related to network slicing, and based on them breaching some thresholds will cause a change in the configuration of the network slice. That means the SMO has to have support for PM counters related to network slicing, and an ability to reconfigure the O-DU for the network slice. Separately, AT&T has asked for a disaggregated VES solution that separates the collection of VES events from how it is presented to any application that wants to view them.

PTL: Mahesh Jethanandani 

Status:  

Jira: Count of Epics ( 0 issues ), User Stories,

Tasks:

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

and Issues:  6 issues

E release source code, container images and deployment instructions

Docker image and instruction on how to install SMO O1 interface can be found here.

Docker image for instructions on how to install SMO O1/VES interface can be found here.

For the O1 interface the repository can be found at "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/ves"


  • No labels