M-Release - Highlights:

• Continue push to improve SMO integration - with updated version of a fully integrated SMO deployment blueprint (See Integration & Test project below)

• Pre-built/tested version of SMO Integration Charts & Scripts available

• Improved Topology Exposure & Inventory (TEIV) functions, models & APIs. Expand TEIV data ingestion adapters (See SMO project below)

• Maintained/Supported existing NONRTRIC/SMO platform functions

• Continued development & improvement of SMO/NONRTRIC/rApp use cases

• Improved robustness and specification compliance.

• Improved Testing & End-to-end Integration

• Assisted in Jenkins → GHA migration

M-Release - Tasks:

• Deprecate older functions no longer maintained developed, i.e. those not used in SMO integration

• Improve & Release SMO Integration Charts & Scripts

• Continue improvements for Topology Exposure & Inventory (TEIV)

• Release SMO/NONRTRIC images containing updates / improvements since last release

PTL: @John Keeney (Ericsson EST)

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

Latest Architecture: 

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

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

  • Epics

  • All Issues

Gerrit / Source Code:

• nonrtric : https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric

• nonrtric-plt-a1policymanagementservice: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/a1policymanagementservice

• nonrtric-plt-dmaapadapter: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/dmaapadapter

• nonrtric-plt-dmaapmediatorproducer: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/dmaapmediatorproducer (inactive / deprecated)

• nonrtric-plt-helmmanager: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/helmmanager (inactive / deprecated)

• nonrtric-plt-informationcoordinatorservice: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/informationcoordinatorservice

• nonrtric-plt-ranpm: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/ranpm

• nonrtric-plt-rappcatalogue: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/rappcatalogue (inactive / deprecated)

• nonrtric-plt-sme: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/sme

• nonrtric-rapp-healthcheck: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/rapp/healthcheck (inactive / deprecated)

• nonrtric-rapp-orufhrecovery: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/rapp/orufhrecovery (inactive / deprecated)

• nonrtric-rapp-ransliceassurance: https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/rapp/ransliceassurance (inactive / deprecated)

• portal/nonrtric-controlpanel : https://gerrit.o-ran-sc.org/r/admin/repos/portal/nonrtric-controlpanel

• sim/a1-interface : https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface

• smo/teiv: https://gerrit.o-ran-sc.org/r/admin/repos/smo/teiv

• it/dep: https://gerrit.o-ran-sc.org/r/admin/repos/it/dep (see ./smo-install/)

Sonar / Test Coverage Reports

• nonrtric/*: https://sonarcloud.io/organizations/o-ran-sc/projects?sort=analysis_date&search=nonrtric

• sim/a1-interface: https://sonarcloud.io/project/overview?id=o-ran-sc_sim-a1-interface

Docs:

• nonrtric : https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric

• nonrtric-plt-a1policymanagementservice: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-a1policymanagementservice

• nonrtric-plt-dmaapadapter: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-dmaapadapter

• nonrtric-plt-dmaapmediatorproducer: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-dmaapmediatorproducer (inactive)

• nonrtric-plt-helmmanager: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-helmmanager (inactive)

• nonrtric-plt-informationcoordinatorservice: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-informationcoordinatorservice

• nonrtric-plt-ranpm: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm

  • nonrtric-plt-ranpm-datafilecollector: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm

  • nonrtric-plt-pmlog: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm/en/latest/influxlogger  

  • nonrtric-plt-ranpm-pm-file-converter: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm/en/latest/pm-file-converter

  • nonrtric-plt-pmproducer: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm/en/latest/pmproducer

• nonrtric-plt-rappcatalogue: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-rappcatalogue (inactive)

• nonrtric-plt-manager: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-rappmanager 

• nonrtric-plt-sme: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-sme

• nonrtric-rapp-orufhrecovery: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-rapp-orufhrecovery (inactive)

• nonrtric-rapp-ransliceassurance: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-rapp-ransliceassurance (inactive)

• portal/nonrtric-controlpanel: https://docs.o-ran-sc.org/projects/o-ran-sc-portal-nonrtric-controlpanel

• sim/a1-interface : https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface

Testing:

• Function Tests

Studies

Weekly Meetings:

• Meetings

Release M - Demos

• In progress

Release M - Container images

• In progress.

  • See Release M - Docker Images

Release M - Deployment Instructions

• In progress.

  • See : Release M - Run in Kubernetes

  • See : Release M - Run in Docker

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

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

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

M-Release plan: 

• Maintain existing xApp's to the M 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 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)

M-Release highlights/accomplishments:
Tagging existing xApps to the M release

• hw-rust & RC xApps

• KPIMON-Go & Bouncer xApps

M-Release source code, container images and deployment instructions

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

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

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

Link to planned Jira work items:

https://lf-o-ran-sc.atlassian.net/browse/RIC-1074

Filled in end-of-release checklist: 

PTL: @abdulwahid.w

Status 12-11-2025: 

Near RealTime RIC container images are using ubuntu 22.04 as the base OS. The golang version also upgraded to 1.22.x.

M-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/BgDbKQ

Mapping of new features to O-RAN Spec
No new features from O-RAN Spec is planned.

Primary Goals:

• provide abstract docker services which centralized TLS termination (traefik) and centralized Authentication and Authorization (keycloak)

• alignment with findings and suggestions of IOS-MCN project

• 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/latest/downloads.html)

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

M-Release Feature Scope: 

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

PTL: @Martin Skorupski

M-Release highlights/accomplishments (2025-12-06):

• update of OAM-Controller to OpenDaylight version Scandium-SR2

• moving OAM-controller to JDK21 (OpenJDK 64-Bit Server VM version 21.0.5+11-LTS)

• change CD/CI pipeline (build, test, deploy, publish) from Jenkins to GithubActions (thanks also the @Matt Watkins for outstanding support)

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

• OAM master

• O-RAN-SC OAM Controller

Containers:

• ODLUX (latest - attention might be a snapshot)

• OAM-Controller (latest - attention might be a snapshot)

Integration:

• helm charts

• docker-compose

Primary Goals:

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

M-Release Feature Scope: 

M-Release Feature Scope: 

• NA

PTL: 

NA

Primary Goals:

1. End-to-end integration 

2. OSC-OAI Collaboration

M-Release Feature Scope: 

• Integration of ODU-High with intel L1

  • Status: Spread over multiple releases

  • Epic: https://jira.o-ran-sc.org/browse/ODUHIGH-475

• OSC-OAI Collaboration

  • Status: Spread over multiple releases

  • Epic: https://jira.o-ran-sc.org/browse/ODUHIGH-557

PTL:  @Ankit Barve 

Status on Jul 10, 2025 

M-Release highlights/accomplishments (Dec 14, 2023):

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

source code: 
Release notes: 
Document: 
Code coverage: NA (Unit test framework not available)

Primary Goals:

Improve O2 DMS ETSi profile

M-Release Feature Scope: 

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

M-Release highlights/accomplishments ():

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

source code: 
Release notes: 
Document: 
Code coverage: 

Primary Goals:

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

• Focus on hybrid and hierarchical OAM architecture 

M Feature Scope / Achievements:

Sprint Demos:

PTL: @Alex Stancu

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

M-Release highlights/accomplishments ( ):

• Stabilized the new Python version for the simulated O-RU and simulated O-DU

• Minor bug fixes

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

M-Release source code, container images and deployment instructions

Source code:

• O1 and OFHMP Simulators

• E2 Simulator

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

Primary Goals:

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

M-Release Feature Scope: 

Improve O2 DMS ETSi profile.

improve the NFO K8s profile integration with OSC-INF.

PTL: @Seshu Kumar Mudiganti 

M-Release highlights/accomplishments ():

• Deployment of ODU using the O2 DMS ETSI profile

• Subscription function for fault management using the O2 DMS ETSI profile

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

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

The container images for SMO can be found on the Nexus server, where applicable.
The container images for OpenStack Tacker can be found in OpenStack Kolla repository.

• https://quay.io/repository/openstack.kolla/tacker-server

• https://quay.io/repository/openstack.kolla/tacker-conductor

The OpenStack Tacker container can be started with the steps in the following documentation.

• https://docs.openstack.org/tacker/latest/install/kolla.html

• https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

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.

Primary Goals: 

• Upgrade and maintain 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.