Welcome to the D release page for the O-RAN Software community
...
community.
To download the source code for the D release, please check the section "D release source code, container images and deployment instructions" at the end of each subproject table below for the subproject that you are interested in. The same section - if applicable - also includes a reference to the container images that make up the D release and to deployment instructions.
General D release container image list for all subprojects.
Table of Contents
Near-Real-time |
---|
...
RIC X-APPs (RICAPP) |
---|
...
Primary Goals: Expand the community working on open source xApps for O-RAN SC. Enhance the set of open source xApps in support of the R-SAC use cases (traffic steering, health check, life cycle management) as well new use cases. Update and enhance existing xApps to take advantage of the new features in xApp SDK (implemented by the xApp frameworks in C++, go, and python). |
D release highlights (7-7-21):
|
PTL: Matti Hiltunen |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status (5-25-21): D Release status
|
D release source code, container images and deployment instructions Each repository has a branch named "dawn" that can be accessed using git. For example, the source code for the AD xApp can be retrieved using "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/ric-app/ad". The other xApps in the D release can be found at ric-app/qp, ric-app/ts, ric-app/lp, ric-app/hw, ric-app/hw-go, ric-app/hw-python, ric-app/mc, ric-app/bouncer, and scp/ric-app/kpimon. Note that the other ric-app repos are obsolete. Note that this branch is in maintenance and all new development is done in branch "master". In order to deploy the D release xApps, you can re-use the pre-created container images as defined here and the instructions on testing the xApps can be found here. |
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT) |
---|
Mission: Update to newer O-RAN specs (E2,A1,O2,O1) and related features. Original primary goals: Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces) // support for A1-EI (as per A1APv3.0) // support for O2 as per WG6 use cases // support for RIC-708 O1-CM to xApps // RIC-734 Include time series database into RIC platform (InfluxDB) for usage by xApps // RIC-421 O1 mediator graceful restart with O1 data being persisted over restarts // Concrete alarms from RIC platform (related to message overload): RIC-204, RIC-203 // SDK package, well documented interfaces to be used by xApps via xApp frameworks // Portability SDK (in xApp project) // REST interface for subscription management. 35 Epics planned: link and 11 items as stretch goals: link |
Achieved D release highlights = high-level release notes (2021-06-28) below (note that the release image list is here: Near-RT RIC (D release))
For the D release of the near-RT RIC we did only limited integration testing: only the use case: deploy RIC, deploy xApp and make E2 connection were tested. |
PTL: Thoralf Czichy |
Status 2021-07-05: Work is completed for the following 25 (19 epics and 6 "others") items link. All of these are already "done". The following 24 items (17 epics and 7 "others") we had to move out from Dawn content link. None of the stretch goals (link) has been worked on. See release highlights (above) for what has been achieved. Most notable items that were dropped are support for the E2APv1.1 capabilities "config transfer" and "OID support (i.e., we continue with E2APv1.0), RIC-708 O1-CM to xApps. Discussion on the portability SDK is still work in progress. We continue to support all the existing SDKs via the xapp Frameworks for C++, python and go. Status 2021-03-03: Work started on many items. 31 Epics planned: link and 15 items as stretch goals: link. Start of release snapshot (MS Excel): link For CII compliance (link)we now do some checks every two weeks in the status meeting and have started a Release criteria checklist template that we go through before releasing, Note that we update to E2APv1.1 |
D release source code, container images and deployment instructions Each repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/ric-plt/e2". Make sure to replace the URL with correct repositories. Note that this branch is in maintenance and all new development is done in branch "master". The complete list of repositories belonging to the RIC platform is defined here: Scope of the near-RT RIC platform and its components (summary). In order to deploy the D release of the near-RT RIC platform you can re-use the pre-created container images as defined here. The same instructions as always apply, i.e., follow the general latest instructions: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-ric-dep/en/latest/ → Installing Near Realtime RIC in RIC Cluster, but make sure to use "git clone --branch dawn ..." instead of "git clone ..." when cloning it/dep and ric-plt/ric-dep. |
Non-Real-time RIC (A1 Interface) (NONRTRIC) |
---|
Primary Goals:
|
D Feature Scope:
|
More detail:
|
PTL: |
Jira:
|
D release source code, container images and deployment instructions
|
Operation and Maintenance (OAM) |
---|
Primary Goals:
|
D Feature Scope:
|
PTL: Martin Skorupski |
D 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:
Release notes: |
Please see: Use Case Flow tests for D-Release |
O-RAN Central Unit (OCU) |
---|
Primary Goals:
|
D Release Feature Scope:
|
PTL: |
Status: Radisys Commercial CU being used as a test fixture. H/W and S/W requirements have been shared and awaiting the same to be configured. |
D release source code, container images and deployment instructions not applicable |
O-DU High |
---|
Primary Goals:
|
D Feature Scope: . 1. Achieve UL and DL data flow using FDD mode on 20 MHz Bandwidth, Numerology = 0 2.Support for static TDD mode with pattern “DDDDDDDSUU” on 100 MHz Bandwidth, Numerology = 1
3.Development activity for Closed Loop Automation use-case
4.Integration
5.End to end testing support (O-RU<->O-DU-LOW<->O-DU-HIGH<->RSYS CU<->Viavi 5G Core ) 6.O1 enhancements - by HCL
|
PTL: Sachin Srivastava |
Status: Updated: 7th July 2021 JIRA: Epics Status below:
Updates from HCL:
Dependency/Blockers:
|
D release source code, container images and deployment instructions |
O-DU Low |
---|
Primary Goals: —Continue O-DU low and O-DU high pairwise test. —FAPI P7 massage integration -> Ongoing —Continue O-DU Low and O-RU emulator test. —Further CU plane testing -> Ongoing —Continue E2E test with UE simulator. —Support the UE attachment test —Development activity for Closed Loop Automation use-case —Support and test for cell stop and restart within O-DU High layers |
D Release Feature Scope: |
PTL: @Zhimin Yuan |
|
D release source code, container images and deployment instructions TODO |
Simulators (SIM) |
---|
Primary Goals:
|
D Feature Scope:
|
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
Status:
|
D release source code, container images and deployment instructions Docker container images are described here. Each repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/sim/o1-interface". Make sure to replace the URL with correct repositories. Note that this branch is in maintenance and all new development is done in branch "master". The complete list of repositories belonging to the SIM project is here. Deployment instructions here. Please see: Use Case Flow tests for D-Release |
Infrastructure (INF) | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Primary Goals:
| ||||||||||||||||||||
D release Feature Scope:
| ||||||||||||||||||||
PTL: Jackie Huang | ||||||||||||||||||||
Jira: Count of Epics, User Stories, Tasks, and Issues: Update at
Test: Release Note: | ||||||||||||||||||||
D release source code, container images and deployment instructions
|
Integration and Test (INT) |
---|
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases |
Cherry Feature Scope:
|
PTL: Zhe Huang |
Jira: Count of Epics, User Stories, Tasks, and Issues: 54 issues |
D release source code, container images and deployment instructions not applicable |
Documentation (DOC) |
---|
Primary Goals: TODO |
Bronze Feature Scope: TODO |
PTL: weichen ni |
Jira: Count of Epics, User Stories, Tasks, and Issues: |
D release source code, container images and deployment instructions not applicable |
Service Management and Orchestration (SMO) |
---|
Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). |
D Feature Scope:
|
PTL: Mahesh Jethanandani |
Status:
Jira: Count of Epics ( 0 issues ), User Stories, Tasks, and Issues: 6 issues |
D release source code, container images and deployment instructions Docker image and instruction on how to install SMO O1 interface can be found here. Docker image for instructions on how to install SMO O1/VES interface can be found here. The repository has a branch named "dawn" that can be accessed using git. For the O1 interface the repository can be found at "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/ves" |
Near-Real-time RIC X-APPs (RICAPP)
Primary Goals: Expand the community working on open source xApps for O-RAN SC. Enhance the set of open source xApps in support of the R-SAC use cases (traffic steering, health check, life cycle management) as well new use cases. Update and enhance existing xApps to take advantage of the new features in xApp SDK (implemented by the xApp frameworks in C++, go, and python).
D release highlights (12-08-20):
- Expanded set of xApps from expanded community: Cherry release includes xApps from AT&T (TS, QP-D, QP, HW, MC), Samsung (KPIMON), and HCL (AD).
PTL: Matti Hiltunen
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues
Status (3-1-21):
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)
Mission: Better manageability of, for example, E2 connections, the RIC platform as well as xApps via the xApp frameworks.
Primary Goals: Support operator-initiated health-check via E2 and be able to close all current or reject all future E2 connections. More manageability of the RIC platform and xApps, including, for example, platform statistics from E2 and A1 and more capabilities in the language-specific xApp frameworks and SDL (shared data layer).
Drelease highlights (2020-12-01):
PTL: Thoralf Czichy
Status 2020-12-11:
Non-Real-time RIC (A1 Interface) (NONRTRIC)
- The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
- It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
- Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.
- Non-RT-RIC will define and coordinate rApps (Non-RT-RIC / SMO appliciations) to perform Non-RT-RIC tasks.
- Non-RT-RIC will also host the new R1 interface (between rApps and SMO services)
D Feature Scope:
- Demo available at: 2020-12-04 - OSC NONRTRIC Cherry Demo
PTL: John Keeney
Jira: Count of Epics ( 20 issues ), User Stories, Tasks, and Issues: 455 issues
OAM (O1 Interface)
Primary Goals:
- support of the application LCM use case
- Discussion about the details together with the SMO project
- handover SMO artifacts to new SMO project
D Feature Scope:
PTL: Martin Skorupski
Status:
Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues: 166 issues
O-RAN Central Unit (OCU)
- Source code includes RRC, Ng, E1, F1. Platform and OM are provided in dependent libraries.
- O-CU-CP is integrated with O-CU-UP, O-CU functions should be complete.
Cherry Feature Scope:
Jira: Count of Epics, User Stories, Tasks, and Issues:
OCU-1 - O-CU F1 interface for Release B TO DO F1
OCU-2 - O-CU SDAP TO DO SDAP
OCU-3 - O-CU PDCP TO DO PDCP
OCU-4 - O-CU RRC TO DO RRC
OCU-5 - O-CU Ng TO DO Ng
OCU-6 - O-CU E1 TO DO E1
O-DU High
Primary Goals:
Cherry Feature Scope:
- Implement UE attach procedure with basic scheduling on FDD, mu=1, BW=20 MHz
O-DU Low
Primary Goals:
- Integrate with O-DU High with FAPI interface with cherry release aligned IOT profile
- Integrate with O-DU emulator from Viavi with cherry release aligned IOT profile
- Support E2E integration with O-CU, O-DU High, O-RU emulator and UE for UE attachment
D Release Feature Scope:
Status
Simulators (SIM)
Primary Goals:
- Support rapid prototyping by providing simulated interfaces
Cherry Feature Scope:
PTL: Alex Stancu
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues
Status (07 Oct. 2020):
Infrastructure (INF)
Primary Goals:
- 2 servers. 2 AIO servers with HA (high availability), the controller functionality and storage functionality will be deployed at the 2 servers with standby-active mode managed by "service management". If one server or one service in one server has error, it will be switched from active to standby one to maintain the service availability.
- 2 AIO servers with additional worker node.
D Feature Scope: TODO
PTL: Xiaohua Zhang
Jira: Count of Epics, User Stories, Tasks, and Issues:
Integration and Test (INT)
Cherry Feature Scope:
- Automated CLM and SonarQube Scanning CI Jobs
- Improve CI for OSC projects
- Validate and and Test platform and use cases
PTL: Zhe Huang
Jira: Count of Epics, User Stories, Tasks, and Issues: 54 issues
Status (28 Oct. 2020):
Primary Goals: TODO |
Bronze Feature Scope: TODO |
PTL: weichen ni |
Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). |
D Feature Scope: |
PTL: Mahesh Jethanandani |