Welcome to the F release page for the O-RAN Software community.
The F release is being worked on completed and its source code is maintained within the master branch of each repo. The release image lists and source code can be found here for each projects.
Table of Contents
...
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>):
|
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>):
|
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 registration and subscription interface in xapp frameworks. Original primary goals: |
Achieved F release highlights = high-level release notes (2022-05-18) below (note that the release image list is here: link)
For the F release of the near-RT RIC we did only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection were tested. Filled in end-of-release checklist : Release criteria checklist - Release F |
PTL: Thoralf Czichy |
Status 2022-0506-0521: From the 28 epics planned (link) we implemented 9 14 (link). 7 14 items have been moved out of the F release, e.g, because of implementation delays (link). Incomplete items: 12 0 (link). Additionally we fixed 18 19 bugs and small implementation tasks (link) |
F release source code, container images and deployment instructions The list of container images for the F release (link). A demo video that shows
Code coverage: Code coverage reports (current coverage and list of components that need to set up Jenkins job for auto-generation of the reports 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:
|
E Feature Scope / Achievements:
|
PTL: |
|
F Feature Scope / Achievements:
|
PTL: |
F release source code, container images and deployment instructions
|
Jira:
|
|
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)
PTL: Martin Skorupski
|
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:
in docs:Code coverage:
- OAM: o1-controller apps, (2022-04-13: 55.5%)
- OAM: o1-controller frame, (2022-04-13: 55.3%)
- OAM: ves-collector, (2022-04-13: 74.4%)
- OAM: message-router, (2022-04-13: 58.4%)
- RIC Dashboard, (2022-04-13: 86.9%) → archived
- O1-TR069-Adapter (2022-04-13: 22.0%) → archived
O-RAN Central Unit (OCU)
|
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 / Achievements::
|
PTL: Martin Skorupski |
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:
|
- 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
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
PTL: user-30c9d
Status on
JIRA REFERENCE
1) Implementation of HARQ feature
https://jira.o-ran-sc.org/browse/ODUHIGH-402
Status: In progress
2) Scheduler enhancement to support multiple UEs per slot
https://jira.o-ran-sc.org/browse/ODUHIGH-403
Status: Todo
3) Support for E2AP version 2.0
https://jira.o-ran-sc.org/browse/ODUHIGH-404
Status: Completed
4) Intra CU Handover
https://jira.o-ran-sc.org/browse/ODUHIGH-405
Status: In progress
5) Idle mode paging
https://jira.o-ran-sc.org/browse/ODUHIGH-406
Status: In progress
Intra CU Handoverhttps://jira.o-ran-sc.org/browse/ODUHIGH-407: Done
https://jira
Code coverage:
|
O-RAN Central Unit (OCU) |
---|
Primary Goals:
|
F Release Feature Scope:
|
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. |
F 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 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:
F Feature Achievement:
|
PTL: user-30c9d |
ODUHIGH-423: Done https://jira.o-ran-sc.org/browse/ODUHIGH-427: Done https://jira.o-ran-sc.org/browse/ODUHIGH-420: Done https://jira.o-ran-sc.org/browse/ODUHIGH-425: Done https://jira.o-ran-sc.org/browse/ODUHIGH-414: Done https://jira.o-ran-sc.org/browse/ODUHIGH-434: Done https://jira.o-ran-sc.org/browse/ODUHIGH-435: Done https://jira.o-ran-sc.org/browse/ODUHIGH-437: Done https://jira.o-ran-sc.org/browse/ODUHIGH-443: In Progress Idle mode paging https://jira.o-ran-sc.org/browse/ODUHIGH-438: Done https://jira.o-ran-sc.org/browse/ODUHIGH-442: In Progress Implementation of HARQ https://jira.o-ran-sc.org/browse/ODUHIGH-436: In Progress https://jira.o-ran-sc.org/browse/ODUHIGH-444: In Progress https://jira.o-ran-sc.org/browse/ODUHIGH-445: In Progress HCL's updates O1 EnhancementsStatus on JIRA REFERENCE 1) Implementation of HARQ feature 402 2) Scheduler enhancement to support multiple UEs per slot |
F release maintenance source code, container images, and deployment instructions TODO Code coverage: To be planned as UT framework is not available to provide code coverage. |
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.
E Maintenance O-DU Low code was provided and expecting integration with RSYS.
O-DU Low |
---|
Primary Goals: Implementation of the O-DU Low Physical Layer functions for a 5G Open Access Radio Network allowing the flexibility of a software implementation coupled with the ability of incorporating hardware accelerators on a selective basis and meets the O-RAN architecture goals of scalablity, mix and match multi-vendor modules that are interoperable and that can be upgraded as the standards evolve by software updates. The O-DU Low physical layer functions follow the 3GPP TS 38 series recommendations for 5G and the 3GPP TS 36 series recommendations for LTE with the 3GPP 7.2 functional split between O-DU Low and O-RU. In 3GPP terms the O-DU Low is referred to HIGH-PHY in the functional split for 5G. Implementation of the Open Front Haul interface to the O-RU per O-RAN WG4 CUS specifications. Integration of this component with multi-vendor implementations of O-DU High and O-RU modules for end to end interoperability and compatibility verification. |
F Release Feature Scope: 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 release code released on March of this year and that still needs to be integrated with the RSYS O-DU High code. The O-DU Low F Release code is an Intel contribution in collaboration with Tieto Poland for the source code releases in the O-RAN gerrit and for the binary blobs contributed via GitHub. For the documentation preparation of this release Intel worked with collaboration from Fransiscus Bimo and Professor Ray-Guang Cheng from National Taiwan University of Science and Technology (NTUST). 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 are to be provided during the F maintenance release cycle |
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. |
|
E release source code, container images and deployment instructions Source code and documentation including deployment instructions have been provided to the O-RAN documentation site |
Simulators (SIM) |
---|
Primary Goals:
|
F Feature Scope / Achievements:
|
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
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 TODO 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) |
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
PTL: Alex Stancu
Infrastructure (INF) |
---|
Primary Goals:
|
F release Feature Scope:
|
PTL: Jackie Huang |
F release highlights/accomplishments ( ):
|
Jira: Count of Epics, User Stories, Tasks, and Issues: |
Update at
|
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:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
F release Feature Scope:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PTL: Jackie Huang | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
F release highlights/accomplishments (<date>): TODO | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jira: Count of Epics, User Stories, Tasks, and Issues: Update at
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Test status: Code coverage:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Note: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
|
Integration and Test (INT) |
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases |
Feature Scope:
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 |
...
Service Management and Orchestration (SMO) | ||||||||
---|---|---|---|---|---|---|---|---|
Primary Goals: The primary goal of the SMO project is to integrate orchestrate and manage different network functions within O-RAN. It supports several interfaces, O1, O2, O1/VES and others. It does this orchestration and management by integrating different software artifacts of existing open-source projects creating to create a fully functional open-source Service Management and Orchestration (SMO). | ||||||||
F Feature: The focus of the F-release is around two major interfaces, O1/VES and O2. O1 continues to be a stable interface with no change requirements.
| ||||||||
PTL: Mahesh Jethanandani | ||||||||
Status:
Jira: Count of Epics ( 0 issues ), User Stories, Tasks:
and Issues: 6 issues | ||||||||
F release source code, container images and deployment instructionsTODO-update
|
...