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 F release page for the O-RAN Software community.

The F release is being worked on and its source code is maintained within the master branch of each repo.

        


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

Primary Goals: 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).

F release plan (<date>):

  • New xApps
    • KPIMON-GO by HCL
  • Improved xApps:
    • RC (RAN Control) by Mavenir - implements subset of E2 SM RC Ver2.0
    • 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.

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

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

F release highlights/accomplishments (<date>):

  • TODO

F release source code, container images and deployment instructions

Code Coverage Reports : Latest reports can be found at the following Link: Projects - O-RAN Software Community (sonarcloud.io).


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

Mission: E2 updates with first E2APv2.0 support and improvements in subscription interface in xapp frameworks.

Original primary goals: TODO

Planned F release highlights

TODO

Status 2022-02-09: TODO

F release source code, container images and deployment instructions


Code coverage: Code coverage reports (current coverage and list of components that need to set up Jenkins job for auto-generation of the reports as part of CI)

Non-Real-time RIC (A1 & R1 Interfaces) (NONRTRIC)

Primary Goals:
  • TODO

E Feature Scope / Achievements:

  • TODO

F release source code, container images and deployment instructions

Code coverage: https://sonarcloud.io/organizations/o-ran-sc/projects?search=nonrtric&sort=name

Jira:

Operation and Maintenance (OAM)

Primary Goals:

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.

F Feature Scope: 

  • Providing and abstract topology for rApp and CNF deployment
  • Enhancing automated test cases validating the end-to-end message flows related to OAM interfaces (O1, OpenFronthaul M-Plane)

F 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:

Release notes:

Code coverage: 

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: 

O-DU new Feature Development

1. HARQ framework support and scheduler enhancement to prioritize retransmission

2. Enhancement of Scheduler

1. Multiple UEs/TTI

3. Mobility mode Support (Intra-CU handover)

4. Support for Idle Mode Paging

Feature verification

1. Closed-Loop Automation

2.16QAM and 64 QAM (Spillover from D release)

End to End Integration support

1.TDD/Mu1/100MHz

2.FDD/Mu0/20MHz * (Spillover from D/E release)

Enhancement

1.E2 AP upgrade 2.0

F Feature Scope: 

  • HARQ framework support

  • Scheduler enhancement
  • Mobility (Inter-DU handover) support
  • Idle mode paging support
  • E2AP upgrade to v2.0
  • End to end integration support


HCL's updates

O1 Enhancements

https://jira.o-ran-sc.org/browse/ODUHIGH-430: In Review

https://jira.o-ran-sc.org/browse/ODUHIGH-431: In Progress 



O-DU Low

Primary Goals:  

The O-DU Low F release adds support for Massive MIMO, URLLC and it is based on the commercial FlexRan 21.11 release. This release is an incremental improvement over the E-maintenance reelase code released on March of this year and that still needs to be integrated with the RSYS O-DU High code.

The F release can be used for end to end testing and it is based on the E maintenance release that was used for the 2021 November US O-RAN Plugfest and tested in conjuction with 2 stack partners and 2 different Test equipment vendors. The Front Haul Interface was also tested for compliance using Keysight's Front Haul Test equipment.

Container images and deployment instructions TBD



E Release Feature Scope: 

O-DU Low  E maintenance release was provided in March, 2022 and it is based on the code used in the November 2021 US O-RAN Plugfest. There are additional changes in the vendor specific portion of the API to support Massive MIMO and URLLC.

Since the code was deployed in the US O-RAN Plugfest using the commercial versions of the stack partners O-DU High code, the open source version from the partners need to be integrated as well. 

The validation done prior to the release used the timer-mode and the test-mac to check all the new features.

Provided O-DU Low E-Maintenance Release on March 2022 to the O-RAN gerrit repo, documentation was updated. Binary blobs for the FlexRan L1 and testmac codes were also provided in github in March.


PTL: Luis Farias , Alternate: @Chenxi Yue
  • E Maintenance O-DU Low code was provided and expecting integration with RSYS.

E release source code, container images and deployment instructions

Source code and documentation including deployment instructions have been provided to the O-RAN documentation siite

Simulators (SIM)

Primary Goals:

  • Keep alignment with latest O-RAN specifications (O1, E2)

F Feature Scope:

  • Provide topology-service image
  • Implement code-coverage tests

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

Status:

  • topology-service docker image available
  • code-coverage in progress

F 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: TODO

Instructions: Network Slicing Use Case TODO update

Code coverage: in progress (sonar for C/C++ code in LF repos)

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.

F release Feature Scope:  

  • Enhance INF O2 implementation
  • Validate integration with various O-RAN SC components in open labs
  • Align with StarlingX 5.0/6.0 add new components
  • Enable the multiple deployment scenarios: Distributed Cloud (stretch goal)

F release highlights/accomplishments (<date>):

TODO

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

Update at  

  • EPICs:
    • INF-265 - Getting issue details... STATUS
    • INF-262 - Getting issue details... STATUS
    • INF-260 - Getting issue details... STATUS
    • INF-230 - Getting issue details... STATUS
    • INF-244 - Getting issue details... STATUS


Test status:

Code coverage:

Release Note:

  • TODO

E release source code, images and deployment instructions


Integration and Test (INT)

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

Feature Scope: 

  • TODO


PTL: James Li

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


F release source code, container images and deployment instructions

not applicable

Documentation (DOC)

Primary Goals: TODO
Bronze Feature Scope: TODO

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). 

F Feature:

  • TODO.

Status:  

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

Tasks:

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

and Issues:  6 issues

F release source code, container images and deployment instructions

TODO-update

Docker image and instruction on how to install SMO O1 NETCONF 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 e-release "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/ves"

  • No labels