/
L-Release

L-Release

Owned by Martin Skorupski
Last updated: Jul 09, 2025 by John Keeney (Ericsson EST)

Welcome to the L-Release page for the O-RAN Software community.

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

        

Non-Real-time RIC (NONRTRIC)

Non-Real-time RIC (NONRTRIC)

L-Release - Highlights:

L-Release - Tasks:

Count of Epics (20 issues), User Stories, Tasks, and Issues:  (455 issues)
Relevant Epics:

  • NONRTRIC-571 - NONRTRIC Cross Release Epic: Information Coordinator Service Done

  • NONRTRIC-648 - NONRTRIC Cross Releases Epic: Long-running maintenance of Helm Charts Done

  • NONRTRIC-670 - NONRTRIC Cross Releases Epic: Engage with ONAP CL Done

  • NONRTRIC-725 - NONRTRIC Cross Releases Epic: Common API framework (CAPIF) Done

  • NONRTRIC-753 - NONRTRIC Cross Release Epic: O-RAN A1 Simulator In Progress

  • NONRTRIC-788 - NONRTRIC Cross Releases Epic: R1 Service Exposure & Management In Progress

  • NONRTRIC-799 - NONRTRIC Cross Releases Epic: rApp Management Done

  • NONRTRIC-818 - NONRTRIC Cross Releases Epic: rApp & rApp Management In Progress

  • NONRTRIC-825 - NONRTRIC Cross Releases Epic: 3PP dependency version update In Progress

  • NONRTRIC-846 - NONRTRIC Cross Releases Epic: R1 Data Exposure & Management In Progress

  • NONRTRIC-896 - NONRTRIC Cross Releases Epic: Deployment and Integration In Progress

  • NONRTRIC-1050 - NONRTRIC L-Release Epic: Testing In Progress

  • NONRTRIC-1051 - NONRTRIC L-Release Epic: Deployment and Integration In Progress

  • NONRTRIC-1052 - NONRTRIC L-Release Epic: Housekeeping In Progress

  • NONRTRIC-1072 - NONRTRIC L-Release Epic: Documentation & Release Tasks In Progress

PTL: @John Keeney (Ericsson EST)

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

Latest Architecture: NONRTRIC Latest Architecture: Release K

Components: NONRTRIC Components: Release K

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

Gerrit / Source Code:

Sonar / Test Coverage Reports

Docs:

Testing:

Studies

Weekly Meetings:

Release L - Demos

Release L - Container images

  • In progress

Release L - Deployment Instructions

  • In progress



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

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

 

L-Release plan: 

  • Maintain existing xApp's to the L Release

  • New ad-cell xApp to detect cell level anomaly. - Moving to next release

  • New ccc xApp to support E2SM CCC. - Moving to next release

 

PTL: @Sunil Singh 

 

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)

 

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

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

  • AD & QP xApp are maintained to support L-release. 

  • KPIMON-Go & Bouncer xApps are maintained to support L-release.

 

L-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

 

L-Release highlights:

  • No new code changes, only bug fixes.

  • Couple of bugs needs to be fixed at xApp side that was found during the e2 testing while supporting the comparison of different RIC in the open source - Moved to next release.

  • Conflict Manager Phase1 is not yet released. Integration with CI is pending - Moved to Next release.
    Filled in end-of-release checklist:  https://lf-o-ran-sc.atlassian.net/wiki/x/VYPX

 

 

PTL: @abdulwahid.w

 

 

 

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

  • aligment with findings and suggetions of IOS-MCN project

    • 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-notes/release-notes-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.

L-Release Feature Scope: 

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

PTL: @Martin Skorupski

L-Release highlights/accomplishments (2025-06-09):

Please see release details:

  • Simplification of deployment by removing ONAP DMaaP

  • Integration of fail based PM in docker compose deployment.

  • Integration of grafana into user management solution by keycloak

  • Status information within topology

  • updates of images used in docker-compose deployments to reduce CVEs in deployments

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

O-RAN Central Unit (OCU)

Primary Goals:

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

L-Release Feature Scope: 

L-Release Feature Scope: 

  • NA

PTL: 

NA



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

L-Release Feature Scope: 

PTL:  @Ankit Barve 

Status on Jun 25, 2025 

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

  • End-to-end integration

    • SIb1 parameter testing on going post Test mac synchronization with TM500 in NTUST lab

  • OSC-OAI Collaboration

    • OAI L1 communication with ODU-High is now active.

    • OAI-CU can also be executed with ODU-High.

    • ODU-High with OAI-L1 works till MSG2. There are few known issues to be resolved after ODU-High sends MSG2 to OAI-L1.

  • Adapting to New ASN.1 encoder decoder

    • New ASN.1 encoder decoder generated codec_utils merged in the main branch

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

source code: gerrit.o-ran-sc Code Review - o-du/l2.git/shortlog
Release notes: Release-Notes — o-du-l2 master documentation
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:

Improve O2 DMS ETSi profile

L-Release Feature Scope: 



PTL:  @Lvfarias (Deactivated) , Alternate: @Chenxi Yue

L-Release highlights/accomplishments ():



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

source code: 
Release notes: 
Document: 
Code coverage: 



Simulators (SIM)

Simulators (SIM)

Primary Goals:

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

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

L-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 L-Release is to act as glue between the different components of O-RAN.

L-Release Feature Scope: 

PTL: @Seshu Kumar Mudiganti 

L-Release highlights/accomplishments:

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

Source Code:

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

L-Release Feature Scope:  

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

  • Update O2 implementation to aligned with new Spec

  • Add multi-node support for OKD O-Cloud

PTL: @Jackie Huang

L-Release highlights/accomplishments (Jun 11, 2025  ):

  • Updated INF StarlingX O-Cloud to aligned with StarlingX 10.0

  • Updated OKD O-Cloud to 4.19 for automation and validation

  • Added multi-node support for OKD O-Cloud

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

Update at  Jun 11, 2025

  • EPICs:

key summary type created updated due assignee reporter priority status resolution
Refresh

  • Stories:

key summary type created updated due assignee reporter priority status resolution
Refresh

  •  Tasks:

key summary type created updated due assignee reporter priority status resolution
Refresh

  •  Bugs:

key summary type created updated due assignee reporter priority status resolution
Refresh

Test status:

Code coverage:

Release Note: TODO

L-Release source code, images and deployment instructions

  • Each repository has a branch named "l-release" that can be accessed using git: TODO

  • Images for INF project: TODO

  • Deployment instruction: TODO





Integration and Test (INT)

Integration and Test (INT)

L-Release - Highlights:  Have AIMLFW + SMO + Non-RT RIC + OAM integrated into a single cluster vanilla k8s

L Feature Scope / Achievements:

  • INT-173 - INT: Standardize Kubernetes Test Environment Script for Integration Projects

  • INT-174 - INT : SMO + Non-RT RIC + OAM deployment

  • INT-175 - INT : AIMLFW Deployment

Gerrit / Source Code:

PTL: @bimo fransiscus asisi

Wiki: Integration and Testing

L-Release highlights/accomplishments:

Release K - Demos

L-Release source code, container images and deployment instructions







AIML Framework (AIMLFW)

AIML Framework (AIMLFW)

Primary Goals: 

  • Enhance Pipeline Composability and Reusability: Introduce a generic and composable pipeline framework, breaking down the QoE pipeline use case into reusable components (feature extraction, model training, model storage, model metrics storage).

  • Improve Model Storage SDK Functionality: Enhance the SDK to support data exchange between components, standalone execution without Kubernetes, and abstraction for diverse storage mechanisms.

  • Strengthen Error Handling and API Stability: Implement robust error handling for responses and fix APIs.

  • Address System Failures and Enhance Reliability: Resolve issues related to TM failure and improve overall system stability and reliability.

  • Promote Modular and Extensible Architecture: Enable seamless integration of external models and ensure the SDK supports various storage mechanisms, fostering flexibility and scalability.

EPICs considered for J-release:

PTL: @subhash

Wiki: AI/ML Framework

Tasks / Backlog / JIRA:  https://jira.o-ran-sc.org/projects/AIMLFW/issues

Gerrit / Code:

Sonar / Test Coverage Reports:

Documentation:

https://docs.o-ran-sc.org/en/latest/projects.html#ai-ml-framework

Installation/Demo guides:

AIMLFW: https://docs.o-ran-sc.org/projects/o-ran-sc-aiml-fw-aimlfw-dep/en/latest/installation-guide.html

Demo videos:

Files for L-Release

Release Container images:

  • Training manager component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-awmf-tm-docker:4.0.0

  • Data extraction component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-athp-data-extraction-docker:4.0.0

  • Kubeflow adapter component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-athp-tps-kubeflow-adapter-docker:4.0.0

  • AIMLFW dashboard component: nexus3.o-ran-sc.org:10002/o-ran-sc/portal-aiml-dashboard-docker:4.0.0

  • AIMLFW notebook component: nexus3.o-ran-sc.org:10002/o-ran-sc/portal-aiml-notebook-docker:4.0.0

  • AIMLFW Model Management service component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-awmf-modelmgmtservice-docker:4.0.0

O-RAN specification References:

  • O-RAN AI/ML workflow description and requirements

  • O-RAN R1 interface: General Aspects and Principles v9.0

  • O-RAN Non-RT RIC Architecture

  • O-RAN R1 interface: Use Cases and Requirements

  • R1 interface: Application Protocols for R1 Services v6.0





Documentation (DOC)

Documentation (DOC)

Primary Goals: publish L release document

L-Release Feature Scope: publish L release document

PTL: @Weichen Ni 

L-Release highlights/accomplishments (): publish OSC L- release document, including all projects

publish L-Release document：https://docs.o-ran-sc.org/en/latest/

Release Note:

publish OSC L- release document, introducing new features of all projects



L-Release source code, images and deployment instructions

N/A