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

J release highlights/accomplishments:

• HW-Rust xApp is added to support the new xApp framework.
• AD & QP xApp are maintained to support J-release. 
• KPIMON-Go bug fixes update. (Missing Readiness and Liveness Probes in kpimon-go xApp )
• KPIMON-Go & Bouncer xApps are maintained to support J-release.

J release source code, container images and deployment instructions

The list of container images (Link)

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

Theme: Make the platform more robust in handling E2AP, conflicts and A1

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

• Additional messages: modify src code to be more lenient in ordering of IEs in ASN.1 (RIC-1030, GS)
• tests with mock replies for subscriptions, registrations and alarms in xapp framework for Rust (RIC-1028, AG)
• Handling of E2 Error Indication from E2 node at E2M and Sub manager (RIC-1024, N)
• Graceful Handling of Unsupported E2AP Procedure at E2T (RIC-1023, N)
• Handling of SCTP Abort message from E2 Node (RIC-1022, N)  
• remove leading zeros in gnb, cu, du ID , MCC and MNC (RIC-1021, N)
• Abnormal signaling process cause E2Term crash (Bug RIC-1002, N)
• Handling of RIC Error indication _during_ E2 setup (RIC-997, N)
• E2 Conflict management between xApps (RIC-993, CG)
• implement test cases for xapp-frame-cpp (RIC-950, H)
• Support Startup/Health script demonstrating release capabilities (RIC-926, H)
• A1 mediator testing in nanobot (RIC-926, H)
• xapp testing nanobot enhancements: wider coverage of functionality, e.g., Subscription deletion (RIC-860, H)
• scale-in and scale out using K8S operators (details still open) (RIC-1048, S)

Link to planned Jira work items: link

Completed Items:

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

Contributions related to E2 interfaces

• Graceful Handling of Unsupported E2AP Procedure at E2T (RIC-1023, N)
• Handling of SCTP Abort message from E2 Node (RIC-1022, N)  
• Abnormal signaling process cause E2Term crash (Bug RIC-1002, N)

• Handling of RIC Error indication _during_ E2 setup

• (RIC-

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.

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.

• 997, N)

Achieved J release highlights = high-level release notes (23-06-2024) below (note that the release image list is here: TODO)

• Robustness in E2 AP procedure handling by means of handling unsupported E2AP Procedures, RIC Error Indication and SCTP abort messages.
• Then near real times installation now uses newer k8s version 1.28.x.
• Upgraded kong to newer version 2.38.0

The J release has 7 bugs fixed.

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

Status 23-06-2024: From the 13 epics planned (link) we implemented 3 (link). 10 items have been moved out of the J release, e.g, because of implementation delays (link). Additionally, we fixed 7 bugs (link). One security issue is pending RIC-1001(CVE-2023-41627) to be resolved and will be attempted in next release. 

J release source code, container images and deployment instructions

The list of container images for the release (link). A demo video for the J 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

RIC-1024, RIC-997 relate to correct implementation of ErrorIndication as defined in E2AP in addition to other failure cases that are defined in E2AP.

RIC-993 is an implementation of E2 guidance for conflict mitigation (see RICHARCH 6.0 draft). As WG3 is still in the process of specifying this we may have to adapt later.

Primary Goals:

• update of O-RAN WG10 VES message bodies
• update of O-RAN WG4 optional VES bodies
• update of OAM-Controller to OpenDaylight version Potassium-SR1
• support of other O-RAN-SC projects (e.g. SMO, Non-RT-RIC, O-DU, INT) based on RSAC and other input.
• support of OAI and nephio integration with O-RAN-SC related to OAM

J release Feature Scope: 

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

Primary Goals:

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

J release Feature Scope: 

J Release Feature Scope: 

• NA

Primary Goals:

1. Multi UE (max=2) scheduling per TTI in scheduler UL part

2. End-to-end integration 

3. OSC-OAI Collaboration

4. XML based input configuration enhancement

Primary Goals:

J release Feature Scope: 

Primary Goals:

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

J Feature Scope / Achievements:

• Work on a new Python framework for the O1 Simulator
• Provide datasets to the AI/ML team for training

Sprint Demos:

Primary Goals:

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

J release Feature Scope: 

Improve O2 DMS ETSi profile.

1. Fault management - First take

Develop O2 interfaces and integrate with OSC INF (would expand to multiple releases):

1. FOCOM interfaces to the INF (O-Cloud) Interfaces.
2. NFO K8s profile to Deploy a CNF on top of the cluster created through OSC-INF

Develop a Topology & Inventory (TEIV) registry & exposure capability

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.

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 J release Feature Scope:  

• Update INF Platform to aligned with StarlingX 9.0
• Update O2 implementation to aligned with new Spec Ver 6.0
• Develop OKD as alternative O-Cloud platform

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 and OKD, 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:

INF

Release Notes

INF O2

Release Notes

J I release source code, images and deployment instructions

• Each repository has a branch named "ij-release" that can be accessed using git:
  • For pti/rtp repo[gitweb]: git clone --branch ij-release "https://gerrit.o-ran-sc.org/r/pti/rtp" 
  • For pti/o2 repo[gitweb]: git clone --branch ij-release "https://gerrit.o-ran-sc.org/r/pti/o2"
• Images for INF project
  
  • ISO image for INF: Yocto Debian Based image: inf-image-yoctodebian-aioall-x86-64.iso
  • CentOS based image: inf-image-centos-all-x86-64.iso
  • Debian Yocto Based image: inf-image-debianyocto-allaio-x86-64.isoContainer image for o2:
  • nexus3.o-ran-sc.org:10002/o-ran-sc/pti-o2imsdms:2.0.3
  nexus3.o-ran-sc.org:10004/o-ran-sc/pti-o2imsdms:2.0.3.iso
• Deployment instruction: 
  • INF: INF Installation Guide
  • O2: O-RAN O2 Application
  • OKD: okd_README.md

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

• Successful integration of TM500 with O-DU-high and O-DU-low
• Integration of OSC-OAI
• Expand pairwire tests coverage and improve the level of automation

J release highlights/accomplishments:

• Integration tests with commercial gNBs + SMO + NonRT RIC for Energy Saving use cases
• Preliminary integration of OSC Non-RT +  OSC Near RT  RIC integration and OSC AIML Framework + OSC Non-RT RIC integration
• OAI/OSC interoperability test
• Utilizes the XTesting framework of POWDER Labs to trigger CI/CD processes that covers a wide range of O-RAN projects including

I release highlights/accomplishments:

• Near RT RIC, Non RT RIC,

• AI/ML, xApps, etc

J release source code, container images and deployment instructions：

gerrit (look for the latest changes for H release from the following repositories):

https://gerrit.o-ran-sc.org/r/it/dep

https://gerrit.o-ran-sc.org/r/it/dev

https://gerrit.o-ran-sc.org/r/it/test

I release source code, container images and deployment instructions

Primary Goals: 

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

• Platform upgrade with latest dependencies for kubernetes, kubeflow and leofs.
• Align with O-RAN alliance approaches captured in WG2 specifications.
• Use cases on 
  • UAV path prediction
  • Energy saving use case
• Study on new capabilities e.g. generic training pipeline, model retraining and cloud native support.