Welcome to the G release page for the O-RAN Software community.
The G release is currently in incubation; initiating the definition of the requirementshas been released
Table of Contents
Non-Real-time RIC (NONRTRIC) |
---|
Primary Goals:
|
G release planRelease - Highlights: Count of Epics (20 issues), User Stories, Tasks, and Issues: (455 issues)
|
PTL: John Keeney |
Wiki: https://wiki.o-ran-sc.org/display/RICNR Tasks / Backlog: https://jira.o-ran-sc.org/projects/NONRTRIC/issues Gerrit / Code:
Docs:
Sonar / Test Coverage Reports
Testing: Weekly Meetings: Demos:
|
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 RSAC use cases (traffic steering, network slicing) as well new use cases. Update and enhance existing xApps |
G release plan (<date>):
|
PTL: SUNIL SINGH |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
G release highlights/accomplishments (<date>): |
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)
Original primary goals:
- E2T improvements: Support for E2 Reset procedure (from E2 node to RIC (RIC-386, Dec-4) - only E2 node-side simulator implementation and possibly some part in E2M related to E2 procedure model, but not full E2 reset procedure ;
Correct handling of E2 node reconnects and multiple E2 Setups (RIC-932),Support split architecture (CU/DU) in E2T/E2M (RIC-933), test cases of remaining interface types in config update (RIC-911, maybe-Dec-4-subhash),MDC dynamic log level change in E2T and E2M (RIC-814, RIC-813), check existence of SCTP stack during startup (RIC-931) - A1: finalize re-implementation of A1 in golang (from python) (RIC-849, RIC-914, Dec-4)
- Remove support for RMR in E2 subscription interface and only continue with E2 REST subscription interface towards xApps (RIC-375)
- can be done because last missing xapp-framwork (xapp-frame-cpp) supports REST (RIC-641, RIC-705) . Go and python already support E2 REST subscriptions
Subscription delete callback to xApps and subscription cleanup after xApp removal (RIC-928, RIC-929)- Support for DMS via REST in addition to command line tool DMSCLI (RIC-714, Dec-4)
- First version of the xApp framework for Rust (RIC-924)
missing test cases for xapp-frame-py (RIC-917),xapp-frame (go) support readiness and liveness state with appmgr/rtmgr (RIC-930)First version of a RIC CLI (RIC-445)ric-dep cleanup (RIC-918)- E2 check, validate and define how various overload and disconnect case are handled (RIC-704)
Enhancments in A1 mediator testing and in E2 subscription testing via nanobot (RIC-878, RIC-860)- Update of influxDB from 1.8→2.2, incl. adaptations in stslgo module (RIC-919)
- Take go version 1.18 into use in base image (RIC-937)
- bug fixes: RIC-945 e2term crashes occasionally when gNB is disconnected,RIC-944 PlmnId to mnc conversion wrong, RIC-943 alarm-go rmr routing table init failure, RIC-936 reference to gcr -> ghcr, RIC-935 kube-flannel changed namespace, RIC-934 Upgrade sdlgo Golang version to fix CVE-2022-32189 vulnerability,RIC-920 fix translation of 21/22/23 bit gnb ids to hex in E2T, RIC-939 race condition and out of bounds check in RMR
Achieved G release highlights = high-level release notes (2022-05-18) below (note that the release image list is here: TODO)
- TODO
For the G release of the near-RT RIC we do only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection are to be tested.
Filled in end-of-release checklist : Release criteria checklist - TODO
PTL: Thoralf Czichy
Status 2022-11-22: From the 28 epics planned (link) we implemented 2 (link). 16 items have been moved out of the G release, e.g, because of implementation delays (link). Incomplete items: 10 (link). Additionally we fixed 7 bugs and small implementation tasks (link)
G release source code, container images and deployment instructions
The list of container images for the G release (link).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.
G release Feature Scope:
- support of O-RAN WG10 VES message bodies
- update of OAM-Controller to ODL version Sulfur
- Note: team decided to go with Java11 - Java 17 would be possible but is pushed out to next release.
- update to keycloak version 18
- even more secure keycloak configuration
- there is a request for a "bare-metal" deployment which is not in scope of O-RAN, but still useful - also for development and module test
- support of AI/ML based on RSAC and other input.
- support of Tacker team
Please see also project wiki for further details: G-Release
Sprint Demos:
PTL: Martin Skorupski
G 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:
O-RAN Central Unit (OCU)
Primary Goals:
- In the absence of O-CU, Radisys commercial CU image to be used for E2E testing
G release Feature Scope:
G Release Feature Scope:
- Radisys Commercial CU is being used as a test fixture for E2E testing
- This is containerized CU image with following
- Release version 2.5.3
- NG interface with SOCKET mode and veth type
- F1 interface with SOCKET mode and veth type
- E2 interface support
- Software Crypto
PTL:
G release source code, container images and deployment instructions (and status)
O-DU High
Primary Goals:
O-DU New Feature Development
1. Implementation of Discontinuous Reception (DRX)
2. Aligning all modules and interfaces to the latest specification
3. Mobility mode Support (Inter-CU handover)
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)
G release Feature Scope:
DRX support
- Mobility (Inter-CU handover) support
- code clean-up and coverage
- latest specification support for all modules and interfaces (AAD WG8)
- End to end integration support
PTL:
Status on
Implementation of Discontinuous Reception (DRX)
Status: Testing
https://jira.o-ran-sc.org/browse/ODUHIGH-462
Alignment to latest ORAN WG8 AAD specification
Status: Testing
https://jira.o-ran-sc.org/browse/ODUHIGH-464
Testing of odu-high along with intel l1 in different labs
Status: Broadcast message till odu-low
https://jira.o-ran-sc.org/browse/ODUHIGH-475
G release source code, container images and deployment instructions (and status)
TBD
Simulators (SIM)
Primary Goals:
- Keep alignment with latest O-RAN specifications (O1, E2)
G Feature Scope / Achievements:
- keep alignment of the O1 Simulator with latest YANG models
- E2 Simulator improvements (especially to the deployment/build procedures)
- NS3-E2 Simulator integration in Gerrit
Sprint Demos:
PTL: Alex Stancu
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues
G release source code, container images and deployment instructions
Source code: TODO
Container images are described here: TODO
Instructions:TODO
Code coverage: in progress (sonar for C/C++ code in LF repos)
Service Management and Orchestration Layer (SMO)
Primary Goals:
The SMO acts as an uber identity that overlooks the different aspects of the O-RAN deployment. Starting with how solutions are deployed, to how they interact with each other, to how they are managed.
G release Feature Scope:
The focus for the G release in SMO is interoperability. Every sub-project within SMO has at least one item that focuses on interoperating with one other entity outside of SMO. For example,
- On the O1 interface, the focus is on trying to bring-up O-DU using NETCONF and YANG models defined for O-DU.
- On the O1/VES interface, it is ability to generate network slicing PM events in the O-DU, and the ability to receive them in SMO dashboard, and store them in InfluxdB.
- On the O2 interface, it will be the ability to instantiate an instance of a Network Function (NF) like the O-DU in the O-Cloud.
Separate from this, each sub-project within SMO has other features/capabilities it will address as part of the G-release. For details please refer to the minutes of the SMO meeting 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 RSAC use cases (traffic steering, network slicing) as well new use cases. Update and enhance existing xApps |
G release plan (<date>):
|
PTL: SUNIL SINGH |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues Completed Epics: RICAPP-204 - Anomaly Detection xApp (G-Release) RICAPP-207 QP xApp (G-Release) RICAPP-201 -KPIMON xApp (G Release) RICAPP-200 - RC xApp (G-Release) RICAPP-202 - upgrading protofile and modified NodebHandler to build CELL-RAN map (cell_map) |
G release highlights/accomplishments (16-Dec-2022): AD xApp :-
QP xApp :-
Gerrit Reviews KPIMON-GO xApp :-
RC xApp:
Bugs fixes:→
TS xApp:
|
G release source code, container images and deployment instructions The list of container images for the G release (link) 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) |
---|
Original primary goals:
|
Achieved G release highlights = high-level release notes (2022-12-14) below (note that the release image list is here: link)
For the G release of the near-RT RIC we do only limited integration testing: only the use cases: deploy RIC, deploy xApp, make E2 connection, get list of A1 policies has been tested. Filled in end-of-release checklist: Release criteria checklist |
PTL: Thoralf Czichy |
Status 2022-12-14: From the 28 epics planned (link) we implemented 10 (link). 18 items have been moved out of the G release, e.g, because of implementation delays (link). Incomplete items: 0 (link). Additionally we fixed 7 bugs and small implementation tasks (link) |
G release source code, container images and deployment instructions The list of container images for the G release (link). A demo video for the F release still applies to the G release (but with updated references). It 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 as part of CI) |
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. |
G release Feature Scope:
Please see also project wiki for further details: G-Release |
Sprint Demos: |
PTL: Martin Skorupski |
G release highlights/accomplishments (<date>): G 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: |
O-RAN Central Unit (OCU) |
---|
Primary Goals:
|
G release Feature Scope: G Release Feature Scope:
|
PTL: |
G release source code, container images and deployment instructions (and status) |
O-DU High |
---|
Primary Goals: O-DU New Feature Development 1. Implementation of Discontinuous Reception (DRX) 2. Aligning all modules and interfaces to the latest specification 3. Mobility mode Support (Inter-CU handover) 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) |
G release Feature Scope:
|
PTL: Ankit Barve |
Status on Implementation of Discontinuous Reception (DRX) Status: Completed https://jira.o-ran-sc.org/browse/ODUHIGH-462 Alignment to latest ORAN WG8 AAD specification Status: Completed https://jira.o-ran-sc.org/browse/ODUHIGH-464 Testing of odu-high along with intel l1 in different labs Status: Completed till Broadcast message till odu-low (To be continued in next release) https://jira.o-ran-sc.org/browse/ODUHIGH-475 Code clean up Status: Completed |
G release highlights/accomplishments ( ):
G release source code, container images, and deployment instructions (and status) source code: https://gerrit.o-ran-sc.org/r/gitweb?p=o-du%2Fl2.git;a=shortlog;h=refs%2Fheads%2Fg-release |
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. |
G release Feature Scope: The O-DU Low G release is the same as the F Release that added support for Massive MIMO, URLLC and it is based on the commercial FlexRan 21.11 release. The O-DU Low G and 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 the F and G release Intel worked with collaboration from Fransiscus Bimo and Professor Ray-Guang Cheng from National Taiwan University of Science and Technology (NTUST). The G and F release are being 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 later |
PTL: Luis Farias , Alternate: @Chenxi Yue |
G release highlights/accomplishments ( ): The G/F Release has been integrated at NTUST and LTTS with the ODU-High and other O-RAN components with O-RU emulators and Commercial Radio Units. For more details of the current status see the ODU-High End to End Integration support status G release source code, container images, and deployment instructions (and status) source code: https://gerrit.o-ran-sc.org/r/gitweb?p=o-du%2Fphy.git;a=summary |
Simulators (SIM) |
---|
Primary Goals:
|
G Feature Scope / Achievements:
|
Sprint Demos: |
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
G release highlights/accomplishments ( ):
G release source code, container images and deployment instructions Source code: Container images are described here. Instructions: no specific instructions. Code coverage: in progress (sonar for C/C++ code in LF repos) |
Service Management and Orchestration Layer (SMO) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Primary Goals: The SMO acts as an uber identity that overlooks the different aspects of the O-RAN deployment. Starting with how solutions are deployed, to how they interact with each other, to how they are managed. | ||||||||||||||
G release Feature Scope: The focus for the G release in SMO is interoperability. Every sub-project within SMO has at least one item that focuses on interoperating with one other entity outside of SMO. For example,
Separate from this, each sub-project within SMO has other features/capabilities it will address as part of the G-release. For details please refer to the minutes of the SMO meeting here. | ||||||||||||||
PTL: Mahesh Jethanandani | ||||||||||||||
G release highlights/accomplishments (December 12, 2022):
G release source code, container images and deployment instructions (and status) G release source code for SMO can be found in the following repositories
The container images for SMO can be found on the Nexus server, where applicable.
The OpenStack Tacker container can be started with the steps in the following documentation.
The installation instructions for SMO can be found in the documentation page here. Status The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.
|
Infrastructure (INF) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Primary Goals:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
G release Feature Scope:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PTL: Jackie Huang | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
G release highlights/accomplishments ( ):
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jira: Status of Epics, User Stories, Tasks, and Issues: Update at
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Test status: Code coverage:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Note: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
G 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 |
G Feature Scope / Achievements:
|
PTL: James Li |
G release highlights/accomplishments (December 14, 2022): Established and demonstrated a XTesting workflow in RIC platform deployment and can further run test cases against the deployed software module(s). Existing Robot test cases can be re-used in the XTesting framework with minimal work. Created multiple POWDER profiles for automated RIC platform deployment and XTesting setup. G release source code, container images and deployment instructions gerrit (look for the latest changes for G release from the following repositories): https://gerrit.o-ran-sc.org/r/it/dep |
AIML Framework (AIMLFW) |
---|
Primary Goals:
|
G Feature Scope / Achievements:
|
PTL: hoejoo lee |
G release highlights/accomplishments ( ):
G release source code, container images and deployment instructions Source code: Gerrit links to the repositories are mentioned below Container images are described here:
Installation Instructions: https://docs.o-ran-sc.org/projects/o-ran-sc-aiml-fw-aimlfw-dep/en/latest/installation-guide.html Installation demos: Installation of AIMLFW: https://wiki.o-ran-sc.org/download/attachments/63143945/oran%20sc%20install_low_res_with_audio_small.mp4?api=v2 AIMLFW Training flow: https://wiki.o-ran-sc.org/download/attachments/63143945/AIMLFW_demo_for_training.mp4?api=v2 Assist and ML xApp demo: https://wiki.o-ran-sc.org/download/attachments/63143945/qp-aimlfw-demo.mp4?api=v2 Code coverage: https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-tps-kubeflow-adapter https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-sdk-feature-store https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-sdk-model-storage https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-data-extraction https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-awmf-tm |
PTL: Mahesh Jethanandani
G release source code, container images and deployment instructions (and status)
G release source code for SMO can be found in the following repositories
- O1 repository
- O1/VES repository
- O2 repository
- For the O2 Interface OpenStack Tacker project (External repository)
- Source code: https://opendev.org/openstack/tacker
- Code coverage: Coverage report (Latest OpenStack verification results)
- For the O2 Interface OpenStack Tacker project (External repository)
The container images for SMO when G-release is finally available will be found here (for now the images might point to the F-release).
The installation instructions for SMO can be found in the documentation page here.
Status
The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.
G release Feature Scope:
- Extend MultiOS support: add Debian as the base OS
- Enable the multiple deployment scenarios for Debian based image:
- AIO-SX, AIO-DX, AIO-DX + workers, standard, Distributed Cloud
- Align INF O2 implementation to the latest O2 spec.
PTL: Jackie Huang
G release highlights/accomplishments ( ):
- Extend MultiOS support: add Debian as the base OS
- Enable the multiple deployment scenarios for Debian based image
- Verified sample application deployment
- Align INF O2 implementation to the latest O2 spec
Jira: Status of Epics, User Stories, Tasks, and Issues:
Update at
- EPICs:
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
- Stories:
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
- Tasks:
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
- Bugs:
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Test status:
Code coverage:
- INF platform
- Code coverage report: o-ran-pti-rtp - (sonarcloud.io)
- INF is a downstream project of StarlingX and Yocto Project, the above coverage report may not reflect the real code coverage, so we also need to refer to the status from upstream projects.
- O2
- Total coverage: 54%
- Detail report: cov-report_20220609.txt
Release Note:
G release source code, images and deployment instructions
- Each repository has a branch named "g-release" that can be accessed using git:
- TODO: For pti/rtp repo[gitweb]: git clone --branch g-release "https://gerrit.o-ran-sc.org/r/pti/rtp"
- TODO: For pti/o2 repo[gitweb]: git clone --branch g-release "https://gerrit.o-ran-sc.org/r/pti/o2"
- Images for INF project
- ISO image for INF:
- Yocto Based image: inf-image-yocto-aio-x86-64.iso
- CentOS based image: inf-image-centos-all-x86-64.iso
- Debian Based image: inf-image-debian-all-x86-64.iso
- Container image for o2:
- nexus3.o-ran-sc.org:10002/o-ran-sc/pti-o2imsdms:2.0.0
- nexus3.o-ran-sc.org:10004/o-ran-sc/pti-o2imsdms:2.0.0
- ISO image for INF:
- Deployment instruction:
Integration and Test (INT)
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases
G Feature Scope / Achievements:
- To set up test automation with the XTesting framework that can run at release time to verify features and integration (an XTesting work flow demo can be found here)
- Work with OSC open labs (US east coast, US west coast, Asia Pacific) to facilitate community testing. Latest status on the 3 labs are available here
- Explore the POWDER testbed for OSC integration test needs: a POWDER account was created that serves as an umbrella project for the OSC community. Multiple profiles were added for automated RIC platform deployment and automated testing.
PTL: James Li
G release source code, container images and deployment instructions
N/A
AIML Framework (AIMLFW) | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Primary Goals:
| ||||||||||||||||||||||||||
G Feature Scope / Achievements:
| ||||||||||||||||||||||||||
PTL: hoejoo lee | ||||||||||||||||||||||||||
G release source code, container images and deployment instructions Source code: Gerrit links to the repositories are mentioned below Container images are described here:
Instructions: TODO Code coverage: TODO | ||||||||||||||||||||||||||
Wiki: https://wiki.o-ran-sc.org/display/AIMLFEW Tasks / Backlog: https://jira.o-ran-sc.org/projects/AIMLFW/issues Gerrit / Code: aiml-fw/awmf/tm: Training Manager : Training job and model management aiml-fw/athp/tps/kubeflow-adapter: Adapter for Kubeflow aiml-fw/athp/sdk/model-storage: Sdk for accessing Model storage aiml-fw/athp/sdk/feature-store: Sdk for accessing Feature store aiml-fw/athp/data-extraction: Retrieving features for training from Data lake aiml-fw/aimlfw-dep: Deployment scripts aiml workflow portal/aiml-dashboard: GUI for AIML Workflow ric-app/qp-aimlfw: Sample ML Assist xApp for QoE prediction JIRA Status
|
...