You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

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

        

Non-Real-time RIC (NONRTRIC)

Primary Goals:
  • R1 Service Exposure & Management
    • Continuing work of Service execution platform extensions (K8s, Istio, Keycloak, OPA, Gateway) to enable and enforce service isolation & exposure
    • First version of 3GPP CAPIF-aligned Service Registration & Discovery service available. Will continue integration with related work on rApp management & Service exposure enforcement.
  • R1 Data Management & Exposure
    • Aligning with emerging proposals for R1-DME where possible
    • R1 DME Data Catalog support in NONRTRIC ICS 
    • R1 Data delivery & filtering (Kafka & REST)
      • Investigating approaches for access to stored data
    • Continuing prototyping with PM data exposure, filtering & access control
      • Additional support for stored data access (S3 currently supported) (InfluxDB tbc) .
  • rApp Manager
    • Building on ONAP “Automation Composition” model & platform to implement rApp use cases
    • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp
    • Hope to start work on supporting ASD-based rApps
    • Support KServe App components
  • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
  • Sample use cases (rApps)
    • Requirements Drivers for rApp/R1 development
    • High degree of cross-project integration activity
  • Testing, Maintenance & Housekeeping
    • Function Test & Integration Test environment,
    • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
    • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

H Release - Highlights:

Count of Epics (20 issues), User Stories, Tasks, and Issues:  (455 issues)
Relevant Epics (Draft/Incomplete. Mostly in progress):

PTL: John Keeney

Wiki: https://wiki.o-ran-sc.org/display/RICNR

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

Gerrit / Code:

Sonar / Test Coverage Reports

Docs:

Testing:

Weekly Meetings:

Demos:

  •  ... (In progress)

H release source code, container images and deployment instructions

  • ... (In progress)

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

PTL: SUNIL SINGH 

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

Completed Epics:

H release highlights/accomplishments:

  • TODO

Gerrit Reviews

H release source code, container images and deployment instructions

The list of container images for the H release:

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)


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

  • E2 reset (from E2 node to RIC), E2 subscription delete required, A1 policy status notfications
  • 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: TODO-link

PTL: Thoralf Czichy

Status 2023-05-19: From the 22 epics planned (link) we implemented 4 (link). 11 items have been moved out of the H release, e.g, because of implementation delays (link). Incomplete items: 7 (link). Additionally we fixed 7 bugs and small implementation tasks (link)

H release source code, container images and deployment instructions

TODO

Operation and Maintenance (OAM)

Primary Goals:

  • Provide complete implementation for OAM functions (FCAPS).

H release Feature Scope: 

    • Updates according to O-RAN Operations and Maintenance Interface Specification 8.0 (O-RAN.WG10.O1-Interface.0-v08.00)    October 2022
    • Hardening the solution by introducing a "SMO-gateway".
    • Add a FlowManagement Component.

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

Sprint Demos:

  • TODO

PTL: Martin Skorupski

H release highlights/accomplishments (<date>):


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

H release Feature Scope: 

H Release Feature Scope: 

  • TODO

PTL: 

TODO-deployment instructions (and status)

O-DU High

Primary Goals:

1. Alignment to the ORAN WG8 AAD specification O-RAN.WG8.AAD-v07.00

2. New design with multi-scheduler algorithm support

3. Inter CU Handover

4. E2 interface enhancement

5. End-to-end integration 

H release Feature Scope: 

PTL:  Ankit Barve 

Status on  

H release highlights/accomplishments ( ):

  • TODO

H 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%2Fh-release
Release notes: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/release-notes.html#h-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

Primary Goals:

TODO

H release Feature Scope: 

TODO

PTL:  Luis Farias , Alternate: @Chenxi Yue

H release highlights/accomplishments ( ):

TODO

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

source code: https://gerrit.o-ran-sc.org/r/gitweb?p=o-du%2Fphy.git;a=summary 
Release notes: https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-phy/en/latest/release-notes.html
Document: https://docs.o-ran-sc.org/en/latest/projects.html#o-ran-distributed-unit-low-layers-odulow
Code coverage: To be planned as UT framework is not available to provide code coverage.

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:

PTL: Alex Stancu

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

H release highlights/accomplishments ( ):

  • TODO

H release source code, container images and deployment instructions

Source code:

  • TODO

Container images are described TODO-link.

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.

H release Feature Scope: 

The scope for H-release includes homing. In addition, package management includes inventory and image management.

PTL: Mahesh Jethanandani

H release highlights/accomplishments (June, 2023):

  • TODO

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

 

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

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, like RIC.
  • Extend multi arch support: add support for ARM64 on Debian based OS.
  • Automate test cases.

PTL: Jackie Huang

H release highlights/accomplishments ( ):

  • TODO

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

Update at  

  • EPICs:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  • Stories:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  •  Tasks:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  •  Bugs:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Test status:

Code coverage:

Release Note:

  • TODO

H release source code, images and deployment instructions


Integration and Test (INT)

Primary Goals: Make each OSC projects to adopt XTesting framework and contribute test cases that can be run at release time for validation. Stretch goal would be to write additional integration test cases based on across project interactions.

H Feature Scope / Achievements:

  • Convert existing RICPLT/RICAPP Robot test cases in it/test repo to be executed with XTesting, which should automate the deployment of RIC platform, onboarding an xApp, and execute test cases all together.
  • Wind River may contribute XTesting test cases on the o2 repo
  • Specific to the Asia Pacific Open Lab:
    • Completing E2 setup procedure between OSC Near-RT RIC and OAI gNb.
    • Incorporate E2AP v2 in OAI CU for connection between OAI CU and OSC Near-RT RIC.
    • Verify data exchange between netconf and ves between OAI CU and OSC SMO.
    • Testing C-plane in F1 interface connection between OAI CU and OSC DU.

PTL: James Li

H release highlights/accomplishments (<date>):

TODO

H 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

AIML Framework (AIMLFW)

Primary Goals:

  • Integration training host and inference host with SMO/Non-RT RIC/Near-RT RIC

H Feature Scope / Achievements: 

  • Diversify training data source for Training host
    • Obtaining training data from DME in Non-RT RIC 
    • Creating Feature groups with data source and feature information

  • Kserve adapter

    • Deploy and manage AI models in Near-RT RIC/Non-RT RIC

    • Integrate Inference host with O-Cloud( RICDMS ) and Management Func of RIC. 

  • Training pipeline Enhancement

    • Provide sample pipelines by default

  • AIMLFW feature enhancements
    • Options for edit, retrain and delete training jobs 

Sprint Demo

PTL: Joseph Thaliath 

JIRA

H release highlights/accomplishments (<Date> ):

  • TODO

H release source code, container images and deployment instructions

Gerrit / Code:

aiml-fw/awmf/tm:  Training Manager : Training job and model management

aiml-fw/athp/tps/kubeflow-adapter: Adapter for Kubeflow

aiml-fw/athp/sdk/model-storage: Sdk for accessing Model storage

aiml-fw/athp/sdk/feature-store: Sdk for accessing Feature store

aiml-fw/athp/data-extraction: Retrieving features for training from Data lake

aiml-fw/aimlfw-dep: Deployment scripts aiml workflow 

portal/aiml-dashboard: GUI for AIML Workflow

ric-app/qp-aimlfw: Sample ML Assist xApp for QoE prediction

aiml-fw/aihp/ips/kserve-adapter: kserve adapter for near-RT RIC


Container images are described here: 

  • TODO

Installation Instructions: 

  • TODO

Code coverage: 

https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-tps-kubeflow-adapter

https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-sdk-feature-store

https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-sdk-model-storage

https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-athp-data-extraction

https://sonarcloud.io/project/overview?id=o-ran-sc_aiml-fw-awmf-tm



  • No labels