I Release

Owned by David Kinsey [AT&T]
Last updated: Jan 24, 2024 by Ankit Barve
10 min read

optimization

Welcome to the I release page for the O-RAN Software community.

The I release is currently in incubation; initiating the definition of the requirements

        

Non-Real-time RIC (NONRTRIC)

I-Release - Highlights:
  • Released first version of rApp manager service
  • Started work on Service Manager service
  • Improvements in RAN PM functions for DME
  • Numerous improvements in Function Test environments
  • Improvements in stability, 3PP vulnerability, test coverage & quality
  • A1 Policy Functions now build using OpenAPI-first approach (ONAP CCSDK)
  • Continued engagement with O-RAN Alliance working groups for standardization alignment

I Release - Tasks:

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

Relevant Epics:

PTL: John Keeney (Ericsson EST)

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

Latest Architecture: Release I Architecture

Components: Release I Components

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 I - Demos


  • I-Release: Demonstration: OSC "NONRTRIC RAN PM Function - Docker compose & Scripts"
    See Video (HD), and summary for more information

  • I-Release: Demonstration: "OSC NONRTRIC rApp Manager"
    See Video (HD), Slides and summary for more information

Release I - Container images

Release I - Deployment Instructions

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

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

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

Enhance the set of open source xApps in support of the RSAC use cases (traffic steering, network slicing) and add new xApps.

New RUST framework based xApp hw-rust will be added in I release. 

New xApp to support E2SM CCC will be added in this release

I release plan: 

  • New HW-Rust xApp to support RUST framework.
  • New ad-cell xApp to detect cell level anomaly.
  • New ccc xApp to support E2SM CCC.

PTL: Sunil Singh 

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

Completed Epics & Story:

RICAPP-232 - hw-rust xApp for i-release

RICAPP-230 - QP xApp (I-Release)

RICAPP-229 - Anomaly Detection xApp (I-Release)

RICAPP-224 - F1AP gnbDuConfigurationUpdate parser

RICAPP-223 - Creating UE/CELL metrics hashmap based upon the KPIS supported by each E2 node

RICAPP-222 - ASN decoders for kpm ran function description and asn encoders for action definition format1 and format3

Completed Tasks

RICAPP-231 - Fix issue of mismatch data type when AD writes data to InfluxDB

RICAPP-228 - Update RMR version and xapp frame to latest version

RICAPP-227 - dynamically adding fields to influxdb and changed the UE KPI parse logic as per indications coming from VIAVI RIC-Test

RICAPP-226 - Update KPM model to latest one

I release highlights/accomplishments:

  • HW-Rust xApp is added to support the new xApp framework
  • AD xApp is upgraded with the python version 3.11 and RMR version 4.9.0 
  • QP xApp is also upgraded with the python version 3.11 and RMR version 4.9.0 
  • KPIMON-Go functionality upgrade. (F1AP gnbDuConfigurationUpdate parser, E2SM KPM RAN function description parser, Automatic creation of action definition format1 & format3 array,  UE KPI parse logic as per indications from RIC-Test tool)
  • KPIMON-Go upgraded to latest RMR version and xApp framework.

I release source code, container images and deployment instructions

The list of container images for the  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 based on contributions from Nokia, Samsung, Capgemini, Alexandre Huff (UTFPR), GS Lab and Abhijit G:

Contributions related to E2 interfaces

  1. RIC-993 (CG): Near-RT RIC conflict management

  2. RIC-933 (CG) : Adding support for CU/DU in E2T/E2M/RNIB

  3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

  4. RIC-994 (S): Support for E2APv3.0

  5. RIC-995 (S): Support for RIC Query

  6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

  7. RIC-387 = ~RIC-383 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this) -

  8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

  9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

Other contributions

  1. RIC-998 (S): K8S operators for deploying/undeploying xApps

  2. RIC-999=~RIC-972 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL)

  3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli)

  4. Already late in H: RIC-985 (UTFPR) IPv6 support for RMR 

  5. RIC-705 (H) update xappframework for c++ to change in xApp registration

  6. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

  7. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
  8. RIC-1027 (S) K8S operators for deploying/undeploying Near-RT RIC
  9. RIC-950 implement test cases for xapp-frame-cpp
  10. RIC-853 Implement subscription delete in Bouncer and E2Sim
  11. RIC-1018 A single helm chart for RIC platform deployment

Support for Integration project's pairwise-testing goals

  1. ODU-high with near-RT RIC: moving from RIC stub to E2 messages with actual RIC
  2. RIC xApp and near-RT RIC: using KPIMon/bouncer xApp or maybe CCC xApp. Maybe xApps can also be used to demonstrate conflict detection
  3. non-RT RIC and near-RT RIC: providing standalone A1 mediator for CI testing of non-RT RIC.

Link to planned Jira work items: link

Achieved I release highlights = high-level release notes (2023-06-20) below (note that the release image list is here: link)

  • E2 Support for disaggregated RAN, i.e., CU-UP, CU-CP, and DU as identified with gNB ID in E2Setup. E2 nodes identified in RNIB, e.g., like this: gnbd_999_999_AAAAAAAA_BBBBBBBBB (longest case)
  • E2 subscription manager supports config parameter to ignore ordering of certain IEs if peer E2 node does not comply with spec.
  • In addition to supporting deployment of RIC platform with existing "install <recipe>" script we now also support (un)deployment via (1) umbrella helm chart and (2) via Kubernetes operator.
  • Kubernetes operator for deploying xApps as alternative to dms_cli
  • Enhancements in xApp framework for RUST to get closer to feature parity with xApp frameworks for other languages.

The I release fixes the following two security issues: RIC-991: "CVE-2023-40997 RMR: Crashes caused by improperly formatted packets", and RIC-989: "CVE-2023-40998 RMR: Negative Packet Size Causes Crash". Additionally we fixed 9 bugs (link) and did 3 small implementation tasks  (link)

Filled in end-of-release checklist: Release criteria checklist - Release I

PTL: Thoralf Czichy

Status 2023-12-05: From the 20 epics planned (link) we implemented 7 (link). 13 items have been moved out of the I release, e.g, because of implementation delays (link). Incomplete items: 0 (link). Additionally we fixed 9 bugs (link) and did 3 small implementation tasks  (link)


I release source code, container images and deployment instructions

The list of container images for the  release (link). A demo video for the I release deployment is available at the top of the demo page and shows

  • how to deploy the near-RT RIC platform,
  • compile connect the E2 (e2 node) simulator from the OSC simulator project and
  • compile the hw-go xapp from the xapp project and use the dms_cli to deploy it and check the E2 subscriptions the xApp created.

Code coverage: Code coverage reports (current coverage and a list of components that still needs to be set up Jenkins job for auto-generation of the reports as part of CI)

Mapping of new features to O-RAN Spec

Compliance with the O-RAN specification is described in the section "External interfaces" in Introduction and guides. This release advanced specification compliance in A1 (RIC-999 URL change, but still bug for maintenance release: RIC-1031. We now also support RIC-933 disaggregated RAN (CU-CP/CU-UP/DU) in E2 connections.

Operation and Maintenance (OAM)

Primary Goals:

  • support of O-RAN WG10 VES message bodies
  • support of O-RAN WG4 optional VES bodies
  • update of OAM-Controller to ODL version Argon-SR1
  • support of other O-rAN-SC projects (e.g. SMO, Non-RT-Ric, O-DU, INT) based on RSAC and other input.
  • intergration of wireshark for api analysis
  • integration of jenkins for test-automation


I release Feature Scope: 

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

PTL: Martin Skorupski

I release highlights/accomplishments (2023-12-06):

  • network generation in kmz and ietf-network-topology for later contribution to AI/ML, INT, SMO O2 and SIM
  • integration of new ODL version: Argon SR2

Please see release details:


I 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 is to be used for E2E testing

I release Feature Scope: 

I Release Feature Scope: 

  • NA

PTL: 

NA

O-DU High (ODUHIGH)

Primary Goals:

1. Alignment to the ORAN WG8 AAD specification O-RAN.WG8.AAD.0-R003-v09.00

2. Alignment to E2 interface specification O-RAN.WG3.E2AP-R003-v03.00

3. Multi UE (max=2) scheduling per TTI in scheduler

4. End-to-end integration 

5. XML based input configuration

I release Feature Scope: 

PTL:  Ankit Barve 

Status on  

I release highlights/accomplishments ():

  • Alignment to the ORAN WG8 AAD specification O-RAN.WG8.AAD.0-R003-v09.00
    • Aligning to the latest WG8 AAD specification O-RAN.WG8.AAD.0-R003-v09.00, raised CR in WG8 for upcoming AAD specification
  • O-RAN.WG3.E2SM-KPM-R003-v03.00.)Alignment to E2 interface specification O-RAN.WG3.E2GAP-R003-v03.00 & O-RAN.WG3.E2AP-R003-v03.00
    (with basic functionalities of service model  O-RAN.WG3.E2SM-KPM-R003-v03.00.)
    • support for global procedures
              E2 Setup
              E2 Node Configuration Update
              RIC Service Update
              E2 Connection Update
              E2 Removal
              E2 Reset
              Error Indication
    • Support for Near RT RIC functional procedures
              RIC Subscription
              RIC Subscription Modification
              RIC Subscription Modification Required
              RIC Subscription Delete
              RIC Subscription Delete Required
              RIC Indication
  • Multi UE (max=2) scheduling per TTI in scheduler (DL part)
    • Enhancing scheduler to schedule multiple UEs per TTI in DL part    
  • End-to-end integration 
    • Integration stopped due to the unavailability of TM500 in the NTUST lab, to be resumed once the TM500 is available.
  • XML based input configuration
    • converting from static configuration to xml file based configuration
  • I 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%2Fi-release
Release notes: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/release-notes.html#i-release
Document: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/
Code coverage: NA (Unit test framework not available)

O-DU Low (ODULOW)

Primary Goals:

Improve O2 DMS ETSi profile

I release Feature Scope: 


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

I release highlights/accomplishments ():

H release includes a patch to our previous F & G Releases with a fix for a PRACH detection bug found by LNT.

I release source code, container images, and deployment instructions (and status)

source code: 
Release notes: 
Document: 
Code coverage: 

Simulators (SIM)

Primary Goals:

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

I Feature Scope / Achievements:

  • Keep alignment with latest O-RAN specifications (O1, E2)
  • Provide datasets to the AI/ML team for training

Sprint Demos:

PTL: Alex Stancu

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

I release highlights/accomplishments ( ):

I 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 primary goal of SMO in the H-release is to act as glue between the different components of O-RAN.

I release Feature Scope: 

The scope for I-release includes enhancing the O-RAN O2 DMS ETSI NFV Profile.

PTL: Seshu Kumar Mudiganti 

I release highlights/accomplishments ():

  • Alignment with O-RAN O2 DMS ETSI NFV Profile.

I release source code, container images and deployment instructions (and status)

H 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 container images for OpenStack Tacker can be found in OpenStack Kolla repository.

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.

[SMO-132] O2 Tacker install script raise syntax error - ORAN Jira (o-ran-sc.org)

[SMO-134] O1 stories under the I release - ORAN Jira (o-ran-sc.org)



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.

I release Feature Scope:  

  • Support integration between INF as O-Cloud with other o-ran-sc components.
  • Support deploy ETSI-DMS (tacker) on INF O-Cloud.
  • Extend multi arch support: add support for ARM64 on Debian based OS.
  • Aligned INF O2 implementation to the O-RAN Spec 4.0

PTL: Jackie Huang

I release highlights/accomplishments (  ):

  • Verified the deployment of ETSI-DMS (tacker) on INF O-Cloud.

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

Update at  

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

I release source code, images and deployment instructions


Integration and Test (INT)

Primary Goals: 

  1. Establish an E2E call session with OSC components
  2. Build a CI/CD/CT pipeline for better integration and/or interoperability tests

I Feature Scope / Achievements:

  1. Pairwise Tests
  2. Lab interconnection
  3. OSC-OAI interaction/integration

PTL: James Li

I release highlights/accomplishments:

  1. 8 different pairwise test areas are defined, and 6 out of 8 are implemented and executed. Essentially it involves tests against Near RT RIC, Non RT RIC, xApps, OAM, SIM, O-DU-high, AIMLFW, and INF projects on E2/O1/A1 interfaces.
  2. Test automation with POWDER testbed for integration and pairwise tests. Recently also established test accounts on Colosseum and ARA testbeds for OSC community use.
  3. Demonstrated integration result between OSC O-DU with OAI FlexRIC .

I release source code, container images and deployment instructions

Most of the code was committed to the it/test repository.

AIML Framework (AIMLFW)

Primary Goals: 

  • Enhance AIMLFW with new features
  • Align with O-RAN alliance approaches captured in WG2 specifications for model management

I release highlights/accomplishments:

  • Model management services aligning with O-RAN alliance WG2.
  • Dynamic selection of multiple data sources for training.
  • Automatically recover AIMLFW after VM restart without need for reinstall. 

EPICs considered for I-release:

AIMLFW-55 - Getting issue details... STATUS

AIMLFW-53 - Getting issue details... STATUS

PTL: Joseph Thaliath 

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 I release

Release Container images:

  • Training manager component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-awmf-tm-docker:1.2.0
  • Data extraction component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-athp-data-extraction-docker:1.2.0
  • Kubeflow adapter component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-athp-tps-kubeflow-adapter-docker:1.1.0
  • AIMLFW dashboard component: nexus3.o-ran-sc.org:10002/o-ran-sc/portal-aiml-dashboard-docker:1.2.0
  • AIMLFW notebook component: nexus3.o-ran-sc.org:10002/o-ran-sc/portal-aiml-notebook-docker:1.2.0
  • AIMLFW Model Management service component: nexus3.o-ran-sc.org:10002/o-ran-sc/aiml-fw-awmf-modelmgmtservice-docker:1.0.0

O-RAN specification References:

  • O-RAN AI/ML workflow description and requirements
  • O-RAN R1 interface: General Aspects and Principles
  • O-RAN Non-RT RIC Architecture 
  • O-RAN R1 interface: Use Cases and Requirements


Documentation (DOC)

Primary Goals: publish I release document

I release Feature Scope: publish I release document

PTL: Weichen Ni 

I release highlights/accomplishments ():

publish I release document：https://docs.o-ran-sc.org/en/latest/

Release Note:

https://docs.o-ran-sc.org/en/latest/release-notes.html

I release source code, images and deployment instructions

N/A