Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

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

Table of Contents
        

Non-Real-time RIC (NONRTRIC)

H-Release - Highlights:
  • Consolidated & Improved RAN PM data exposure in new repo for RAN PM functions
    • Adds 4 new services for RAN PM processing
    • Lots of work on deployment scripts/charts, testing, CI, and documentation
  • (R1) Service Exposure & Management (SME)
    • CAPIF Aligned Service Registry & Discovery
    • Continued work of Service execution platform extensions (K8s, Istio, Keycloak, OPA, Gateway) to enable and enforce service isolation & exposure
    • Controlled access & exposure of service to/from rApps
  • (R1) Data Management & Exposure (DME)
    • Small updates to Information Coordination Service – studying alignment with R1 proposals
    • File-based PM data → Kafka/InfluxDB/Minio
      • Including parsing, filtering & delivery
      • ref. PM Data exposure above
  • rApp Management
    • Started work on a new rApp Manager functions – more in next release
    • LCM for rApps: Building on ONAP “Automation Composition” model & platform to implement rApp use cases
      • Added a 'KServe Participant’
        • Inference Services in rApps
        • Now supports KServe-based AI/ML rApps
      • Added an ‘A1 Policy Participant’
    • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled access to and exposure of Services
    • Overlap with Data Exposure work to examine role of an rApp Manager to support controlled access to and exposure of Data types
  • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
    • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
      • Numerous updates to improve security
      • Improved support fine-grained policy-based access control
      • Removed DMaaP NBI
    • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
      • ref. DME work above
  • Demonstrated ASD-based CNF LCM
    • ONAP SO CNFM in standalone mode
  • Sample use cases (rApps)
    • Requirements Drivers for rApp/R1 development
  • Testing, Maintenance & Housekeeping
    • 3PP update – esp. Springboot 3 & JDK 17
    • Function Test & Integration Test environment,
      • Lots of new test cases, and new ONAP L & OSC H test profiles
    • Continue integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration environment.
    • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

H Release - Tasks:

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

Relevant Epics:

  • Jira Legacy
    serverSystem Jira
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-855
  • Jira Legacy
    serverSystem Jira
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-846
  • Jira Legacy
    serverSystem Jira
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-842
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-829

  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-826
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-825
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-818
  • Jira Legacy
    serverSystem Jira
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-799
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-788
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-781
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-753
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-725
  • Jira Legacy
    serverSystem Jira
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-696
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-670
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
    keyNONRTRIC-648

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

Latest Architecture: Release H Architecture

Components: Release H Components

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

Gerrit / Source Code:

Sonar / Test Coverage Reports

Docs:

Testing:

Studies

Child pages (Children Display)
depth1
pageRICNR:Release H: Technical spikes

Weekly Meetings:

Demos:


  • H-Release: Demonstration: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode"
    See Video (HD), Video (SD) and Slides for more information

  • H-Release: Demonstration: "CAPIF for Service Registration & Service Discovery"
    See Video (HD), Video (SD) and Slides for more information

H release: Container images

H release: Deployment Instruction

...

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

Primary Goals:  Expand the community working on open source xApps for O-RAN SC.  Update and maintain the existing xApps to latest releases.

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 xApp hw-rust will be added in this release. 

H release plan:

  • New HW-Rust xApp to support RUST framework.
  • New ad-cell xApp to detect cell level anomaly.
  • RC xApp - GRPC interface support on RC xApp
  • Bouncer xApp - RIC Benchmarking new features addition.
  • KPIMON-GO xApp – New Version

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

Completed Epics:

RICAPP-216:Bouncer xApp upgraded to E2AP 2.0, E2SM KPM 2.0, E2SM RC 1.0.3

RICAPP-215: Anomaly Detection xApp (H-Release) - listens to RMR port and expect A1 policy from non-RT RIC & Process A1 policy message.

Bug:

RICAPP-214 OSC RIC - e2mgr X1 Configuration Update problem - Moved to RICP

Epics moved to next release.

  1. RICAPP-212: Hello World Rust Xapp initial release
  2. ad-Cell xApp
  3. RICAPP-211: RC Xapp - upgrade to E2SM-RC-2.0

H release highlights/accomplishments:

  • Bouncer xApp upgraded to E2AP 2.0, E2SM KPM 2.0, E2SM RC 1.0.3
  • Anomaly Detection xApp:  A1 policy from non-RT RIC & Process A1 policy message.

Gerrit Reviews

https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app%2Fbouncer.git;a=shortlog;h=refs%2Fheads%2Fh-release

Release 1.0.1 (Ie8fc46d2) · Gerrit Code Review (o-ran-sc.org)


H release source code, container images and deployment instructions

The list of container images for the H release:

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, HCL, Capgemini, Parallel Wireless, Alexandre Huff (UTFPR) and Abhijit G:

  • We will deprecate the RMR-based E2 subscription interface and H-release xApps need to use the REST based interface already supported by the the C++, go, and python xApp frameworks (RIC-375). The subscription manager should handle subscriptions for failing xApps (RIC-929) and provide a callback on subscription delete success/failure (RIC-928). We plan to implement the RIC subscription delete required procedure (RIC-851)
  • Update to newer golang version of all components (RIC-881)
  • We will develop a CRD, i.e., a K8S operator on top of the DMS REST API to simplify xApp deployment (RIC-715). Also the DMS Rest interface gets the missing delete API (RIC-954). RIC-717 allows to deploy multiple cooperating xApps together.
  • On E2 side we will implement the E2 Reset procedure from RAN to RIC (RIC-949) and the RIC Subscription Delete procedure (RIC-851). We also implement robustness improvements (RIC-932 for reconnect cases) and troubleshooting improvements (RIC-813, RIC-814).
  • There's work planned to deploy the kserve-based model provisioning from the AI/ML project into the RIC platform (RIC-955)
  • The xapp frameworks for Golang (RIC-930), C++ and Rust (RIC-951) will get some enhancements that are already implemented in the other languages, incl. support for xApp registration in the xapp-framework-cpp (RIC-705).
  • E2T (RIC-813) and E2Mgr (RIC-814) support dynamic changing of log levels for better troubleshooting
  • RIC-953 A1 testing improvements and bug fixes
  • Added to plan during H:
    • Support for policy status notifications in A1 (RIC-973 (incl. RIC-975))
    • Faster timeout in SCTP heartbeats (E2) (RIC-976)
    • IPv6 support in RMR (RIC-985)


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

  • E2 reset (from E2 node to RIC), E2 subscription delete required, A1 policy status notifications
  • Preparation of feature for I release, e.g., include xApps in subscription delete required decision

For the H release of the near-RT RIC we do only limited integration testing: only the use cases: deploy RIC, deploy xApp, make E2 connection, get list of A1 policies has been tested.

Filled in end-of-release checklist: link

Status 2023-06-20: From the 23 epics planned (link) we implemented 11 (link). 12 items have been moved out of the H release, e.g, because of implementation delays (link). Incomplete items: 0 (link). Additionally we fixed 10 bugs and small implementation tasks (link)

H release source code, container images and deployment instructions

The list of container images for the  release (link). A demo video for the H 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 list of components that need to set up Jenkins job for auto-generation of the reports as part of CI)

...

Simulators (SIM)

Primary Goals:

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

H Feature Scope / Achievements:

  • Keep alignment with latest O-RAN specifications (O1, E2)
  • Initial exploration for any integration/alignment with OAI

Sprint Demos:

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

H release highlights/accomplishments ( ):

  • Updated simulated O-RU YANG models according to latest release (March 2023) OpenFronthaul Management Plane specification
  • Implement the Monitoring NETCONF connectivity feature for the O-RUs, according to chapter 6.7 (Monitoring NETCONF connectivity) in O-RAN.WG4.MP.0-R003-v11.00
  • Created a mechanism to locally build simulated O-DU with 3GPP YANG models
  • No new contributions for the E2 Simulator

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

...

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.

H release Feature Scope:  

  • Support integration between INF as O-Cloud with SMO via O2 interface
  • Support integration between INF as O-Cloud with other o-ran sc components.
  • Extend multi arch support: add support for ARM64 on Debian based OS.
  • Aligned INF O2 implementation to the O-RAN Spec 4.0
  • Automate test cases.

H release highlights/accomplishments ( ):

  • Supported integration between INF as O-Cloud with SMO via O2 interface.
  • Extended multi arch support: add support for ARM64 on Debian based OS (POC level)
  • Align INF O2 implementation to the O-RAN Spec 4.0
  • Automated test cases for O2 compliance.
  • Validate O-CU over INF in Taiwan Lab.
  • Plugfest for SMO homing via O2 interface

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

Update at  

  • EPICs:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = INF AND issuetype = Epic AND fixVersion = "H Release"
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb

  • Stories:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues30
jqlQueryproject = INF AND issuetype = Story AND fixVersion = "H Release"
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb

  •  Tasks:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = INF AND issuetype = Task AND fixVersion = "H Release"
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb

  •  Bugs:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues30
jqlQueryproject = INF AND issuetype = Bug AND fixVersion = "H Release"
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb

Test status:

Code coverage:

Release Note:

H release source code, images and deployment instructions


...

Project NameO-RAN specAdditional Notes
Non RT RIC

O-RAN.WG2.Non-RT-RIC-ARCH-TS-v02.01

ORAN.WG2.R1GAP-v02.00

O-RAN.WG2.A1GAP-v03.00

O-RAN.WG2.R1 Use Cases and Requirements.v02.00


RICAPP

O-RAN.WG3.E2SM-KPM-v02.03

O-RAN.WG3.E2SM-RC-v01.03

O-RAN.WG3.E2AP-v02.03


RICPLT

O-RAN.WG3.RICARCH-R003-v04.00

O-RAN-WG3.RICAPI-R003-v01.00

O-RAN.WG3.E2AP-v02.03

O-RAN.WG3.UCR-v02.00


OAMO-RAN.WG10.O1-Interface.0-v08.00
O-DU HighO-RAN-WG3.RICAPI-R003-v01.00
SIM

SMO

INF

O-RAN.WG6.

O2-GA&P-R003-v03.00

O2IMS-INTERFACEv04.00

O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-v02.00

O-RAN_O2_IMS_Spec_Compliance_v3v4_v01.xlsx
AIMLFM