O-Release

O-Release

Welcome to the O-Release page for the O-RAN Software community. – [TODO: THIS IS DIRECT COPY FROM O-Release. Update in progress.

The O-Release is currently in incubation; initiating the definition of the requirements

        

Non-Real-time RIC (NONRTRIC)

Non-Real-time RIC (NONRTRIC)

O-Release - Highlights:

  • <>

O-Release - Tasks:

https://jira.o-ran-sc.org/projects/NONRTRIC/issues

PTL: @John Keeney (Ericsson EST)

Wiki: https://lf-o-ran-sc.atlassian.net/wiki/display/RICNR/

Latest Architecture: 

Components: 

  • Integrated SMO Deployment

  • Topology Exposure & Inventory

  • rApp Manager & Sample/Template rApps

  • Information Coordinator Service

  • DMaaP/Kafka Information Producer Adapters

  • Service Manager

  • RAN PM functions

  • NONRTRIC CAPIF Core (Service Registry)

  • A1 Interface Simulator

  • Non-RT-RIC Control Panel

  • Non-RT-RIC (Spring Cloud) Service Gateway

  • Non-RT-RIC (Kong) Service Exposure Prototyping (Inactive)

  • A1 Policy Management Service (Inactive in OSC / Active in ONAP)

  • A1 Policy Controller / Adapter (Inactive in OSC / Active in ONAP)

  • Initial Non-RT-RIC App Catalogue (Inactive)

  • Initial K8S Helm Chart LCM Manager (Inactive)

  • Authentication Support (JWT Token Fetch)

  • Test Framework (Inactive)

  • "Helloworld" O-RU Fronthaul Recovery use case (Inactive/Deprecated)

  • "Helloworld" O-DU Slice Assurance use case (Inactive/Deprecated)

  • "Healthcheck" use case (Inactive/Deprecated)

Tasks / Backlog / JIRA:

Gerrit / Source Code:

Sonar / Test Coverage Reports

Docs:

Testing:

Studies

  • In Progress:

Weekly Meetings:

  • Meetings (Meeting Series no longer active since Apr 2026)

Release N - Demos / Talks

Release N - Container images

Release N - Deployment Instructions



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

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

Primary Goals: Expand & maintain the community on open source xApps for O-RAN SC. 

 Update and maintain the existing xApps to latest releases (currently N Release).

Enhance the set of open source xApps in support of the RSAC use cases and add new xApps. 

O-Release plan: 

PTL: @Sunil Kumar 

wiki: RIC Applications (RICAPP) - RIC Applications - Confluence (o-ran-sc.org)

Latest Architecture: Architecture - RIC Applications - Confluence (o-ran-sc.org)

Components: 

Tasks / Backlog / JIRA: Near Realtime RAN Intelligent Controller Applications - ORAN Jira (o-ran-sc.org)

Gerrit / Source Code:

Jira: Count of Epics, User Stories, Tasks, and Issues:  Total (10)

O-Release highlights/accomplishments:
Tag existing xApp to the N release

  • HW-Rust xApp is maintained to support O-Release.

  • AD & QP xApp are maintained to support O-Release. 

  • KPIMON-Go & Bouncer xApps are maintained to support O-Release.

O-Release source code, container images and deployment instructions

The list of container images: Link RICAPP (L Release) - Integration and Testing - Confluence/Wiki

Code Coverage Reports : Projects - O-RAN Software Community (sonarcloud.io)



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

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

Original primary goals based on contributions from Nokia, Samsung, Capgemini, Alexandre Huff (UTFPR), GS Lab and Abhijit G:

Link to planned Jira work items: link

O-Release highlights:

 

PTL: @Abdulwahid W (Nokia)

 

O-Release source code, container images and deployment instructions

The list of container images for the release https://lf-o-ran-sc.atlassian.net/wiki/x/E4C9Gw

Code coverage : Code coverage reports

Mapping of new features to O-RAN Spec
None planned in L release





Operation and Maintenance (OAM)

Operation and Maintenance (OAM)

Primary Goals:
[OAM Project is currently on hold, but we plan to resume work shortly]

  • PM-file-transfer from O-DU/O-CU-UP/O-CU-CP/NearRtRic to SMO-OAM

  • update of O-RAN WG10 VES message bodies

  • update of O-RAN WG4 optional VES bodies

  • update of OAM-Controller to OpenDaylight version Scandium-SR2 (https://docs.opendaylight.org/en/stable-scandium/Release-Ootes/Release-Ootes-scandium-sr2.html)

  • update of VES-Collector version to image: nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.12.5

  • support of other O-RAN-SC projects (e.g. SMO, Non-RT-RIC, O-DU, INT, SIM) based on RSAC and other input.

  • support of OAI and nephio integration with O-RAN-SC related to OAM in collaboration with O-RAN OSFG.

O-Release Feature Scope

Please see also project wiki for further details: O-Release

PTL: @Martin Skorupski

O-Release highlights/accomplishments (2026-06-09):

Please see release details:

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-DU High (ODUHIGH)

O-DU High (ODUHIGH)

Primary Goals:

1. End-to-end integration 

2. OSC-OAI Collaboration

3. Adapting to New ASN.1 encoder decoder

O-Release Feature Scope

  •  

PTL:  @Ankit Barve 

Status on Jun 25, 2025 

O-Release highlights/accomplishments (Jun 25, 2025):

  •  

  •  

O-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%2Fl-release
Release notes: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/release-notes.html#l-release
Document: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/
Code coverage: To be planned as UT framework is not available to provide code coverage.



O-DU Low (ODULOW)

O-DU Low (ODULOW)

Primary Goals:

Enable end to end integration

O-Release Feature Scope

Integration with ODUHIGH

PTL: @Peng Lu , Alternate: @ASHWINI BHAGAT

O-Release highlights/accomplishments ():



O-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
Release notes: O-DU Low Project Release Notes — o-du-phy master documentation
Document: O-RAN SC Projects — oran master documentation
Code coverage: 



Simulators (SIM)

Simulators (SIM)

Primary Goals:

[Simulators Project is currently on hold, but we plan to resume work shortly]

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

  • Focus on hybrid and hierarchical OAM architecture 

L Feature Scope:

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

  • Focus on hybrid and hierarchical OAM architecture (O-DU O1 interface simulator and O-RU OpenFronthaul M-Plane interface simulator)

Sprint Demos:

PTL: @Alex Stancu

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

O-Release highlights/accomplishments ( ):

  • Implemented a new Python version for the simulated O-RU and simulated O-DU.

  • Aligned YANG models for O1 and OpenFronthaul M-Plane with November 2024 train (O-RAN.WG4.MP.0-R004-v16.01)

  • Implemented hybrid and hierarchical O-RU simulators. Simulated O-DUs can accept connections from O-RUs.

O-Release source code, container images and deployment instructions

Source code:

Container images are no longer relevant, docker images need to be build locally, because of Copyright issues.

Instructions: no specific instructions.

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



Service Management and Orchestration Layer (SMO)

Service Management and Orchestration Layer (SMO)

Primary Goals:

The primary goal of SMO in the O-Release is to act as glue between the different components of O-RAN.

O-Release Feature Scope

PTL: @Seshu Kumar Mudiganti 

O-Release highlights/accomplishments:

O-Release source code, container images and deployment instructions (and status)

Source Code:

O-Release source code for SMO can be found in the following repositories

Docker Images:

The installation instructions for SMO can be found in the documentation page here.

Status

The status of the SMO project is tracked using jira.



Infrastructure (INF)

Infrastructure (INF)

Primary Goals: 

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

  • Provide interaction capabilities with other components.

  • Provide O2 interface and support integration with SMO.

O-Release Feature Scope:  

  •  

PTL: @Jackie Huang

O-Release highlights/accomplishments (Jun 17, 2026  ):

  • Update INF StarlingX O-Cloud to aligned with StarlingX 12.0

  • Key feature update:

    • Support bare-metal Ceph to Rook migration

    • Centralized IAM (Identity and Access Management) with OIDC compatible MFA

  • OKD 4.20 O-Cloud automation and validation