Welcome to the D release page for the O-RAN Software 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 Draft 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 (127-087-2021):
|
PTL: Matti Hiltunen |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
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 (2021-06-10):
- REST interface for xApps towards E2 subscription manager. No need to encode E2AP subscription messages in the xApps anymore. The Xapp framework for Go already supports/uses this.
- Support for A1-EI (Enhancement information) to xApps
- A lot of extra load/scalability testing (using a new bouncer xApp) and functionality testing (E2, ...) was done under RIC-150 using a "bouncer xApp".
- Wider scope of the xapp framework for python (RIC-778, RIC-773).
- We added InfluxDB as optional platform service time series database (RIC-734)
- Support for O2 as per WG6 use case "Deploy xAPP in Near-RT RIC" in O-RAN Orchestration Use Cases v2.0. This also includes a change in how xApps register as part of their startup.
- libe2ap (asn1c-based) can be re-used by components to encode/decode E2AP ASN.1 PDUs (Protocol Data Unit)
- E2 statistics are now visible as VES metrics events
- RMR raises alarms using the RIC alarm system in temporary overload situations
- The Near-RT RIC can be deployed on Kubernetes 1.18 and helm 3. For the first time, this and all robot framework based "end-to-end" tests have also been verified in the O-RAN SC lab.
- The Near-RT RIC project now achieved the CII (Core Infrastructure Initiative) badge "passing": (link).
PTL: Thoralf Czichy
Status 2021-06-11: Work is about to complete for the following 25 (19 epics and 6 "others") items link. 14 of these are already "done". The following 22 items (16 epics and 6 "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
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 applications) to perform Non-RT-RIC tasks.
- Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)
D Feature Scope:
- NONRTRIC Functions:
- Integrated A1 Adapter from ONAP (controller – mediation)
- Integrated A1 Policy Management Service from ONAP (controller – A1 policies)
- OSC A1 Enrichment Information Coordinator (controller – A1 EI Job management)
- OSC Non-RT-RIC Control Panel (GUI – for A1-P & A1-EI Job management)
- OSC A1 Simulator (a stateful test stub to simulate near-RT-RIC end of A1 interface – A1-P & A1-EI)
- OSC (initial) APP catalog (for registering/querying APPs)
- Initial K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC) (new)
- Initial Service Exposure Function (new)
- In D Release: (NONRTRIC Release D Wiki) (NONRTRIC Release D Documentation)
- Improved A1-PMS NBI (REST & DMaaP) (Rest style alignment)
- Runtime configuration API (REST) for A1 Policy Management Service (e.g. add/remove adapters, near-rt-rics, security certs, etc)
- Deployment – Continued improvements for Docker & Kubernetes
- Extended/Easier deployment options with OSC IT/DEP project (SMO/NONRTRIC deployment)
- Improving CI/CD to support include A1 Policy controller dependencies from ONAP
- Multi-version support ( O-RAN A1-AP v1.1, v2.0, v2.1,v3.0 & OSC pre-spec A1)
- Improved status monitoring/notification of A1-EI Jobs
- Further improvement in security cert management (All interfaces can now be secured using TLS)
- Re-architect & improve usability of Non-RT-RIC Control Panel (GUI)
- Extend NONRTRIC Control Panel to edit/create A1 Enrichment Types/Jobs
- Extend NONRTRIC Control Panel to configure A1 Policy Management Service
- Configurable Service Exposure function – Extends/Replaces static exposure gateway in OSC Cherry
- K8S Helm Chart LCM function for App µServices
- Update NONRTRIC demo/test environment (one-click tests/use-cases, docker & single/multi-node K8s env)
- OSC e2e integration use case – O-RU-FH-HelloWorld recovery
- App to instigate O-RU-FH connection recovery after failure – via O-DU
- Multiple implementation options – standalone µService and/or deployable ONAP-PF policy script
- App to instigate O-RU-FH connection recovery after failure – via O-DU
- CII badging – Already achieved Bronze/Passing Grade
PTL: John Keeney
Jira: Count of Epics ( 20 issues ), User Stories, Tasks, and Issues: 455 issues
Operation and Maintenance (OAM)
Primary Goals:
- updates of OAM related interface definitions based on
- YANG from WG4 - O-RAN Management Plane Specification - YANG Models 5.0 - November 2020 (with dependencies to IETF data models)
- status: done
- YANG from WG5 - O-RAN O1 Interface for O-DU 1.0 - YANG Models - November 2020 (with dependencies to 3GPP data models)
- status: after feedback of WG5, related merge request was abandoned - instead a pipline will be establish with O-RAN bitbuckets.
- YANG from WG1 - O1-interface (November 2020 train)
- status: not approved by O-RAN
- VES from ONAP DCAE - VES 7.2
- status: done
- Notification syntax from 3GPP TS 28.532 V16.6.0
- YANG from WG4 - O-RAN Management Plane Specification - YANG Models 5.0 - November 2020 (with dependencies to IETF data models)
- support D-Release use case "O-RU recovery"
- see Feature Scope below
- handover SMO artifacts to new SMO project
D Feature Scope:
- Update to OpenDaylight Silicon
- Support of Callhome via TLS
- CallHome to VES:pnfRegistration
- o-ran-fm.yang/alarm-notif to VES:fault
PTL: Martin Skorupski
|
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. |
Status:
Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues: 166 issues
Integration:
- D-Release Integration (and its sub pages)
- Test Topology
Release notes:
in DOCs: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: |
→ 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: |
- In the absence of O-CU, Radisys commercial CU image to be used for E2E testing
D Release Feature Scope:
- Radisys Commercial CU being used as a test fixture for E2E testing
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 Feature Scope:
|
More detail:
|
PTL: |
Jira:
|
D release source code, container images and deployment instructions
|
O-DU High
Primary Goals:
- O-DU high integration in Radio mode
- Initial access and Attach procedure testing in Radio mode
- DL and UL data path in FDD, 20 MHZ with 256 QAM and 64 QAM respectively
- Static TDD mode support with Numerology =1
- O1 enhancement
- Closed Loop Automation Use case support
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
- Evolve scheduler to support UL and DL scheduling of signaling and data messages on single spectrum in TDD mode
- Expand scheduler to support Frame structure according to numerology = 1
- Updates to cell broadcast for TDD and numerology = 1
3.Development activity for Closed Loop Automation use-case
- Support for cell stop and restart within O-DU High layers
- Support for cell stop and restart towards O-DU Low
- F1AP Enhancements towards O-CU indicating cell stop and restart
4.Integration
- Integration with O-DU Low in Radio mode
- Integration with CU
5.End to end testing support (O-RU<->O-DU-LOW<->O-DU-HIGH<->RSYS CU<->Viavi 5G Core )
6.O1 enhancements - by HCL
- Re-structure O1 module to run as a thread in ODU-High
- CM Support - IP and Port configuration for DU, CU stub and RIC stub via Netconf interface
- Support for Closed Loop Automation use-case
PTL: Sachin Srivastava
Status:
Updated: 2nd June 2021
JIRA: Epics Status below:
- As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
- As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
- As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
- Basic code changes complete. Testing in progress for data path
- As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
- Basic code changes complete. Testing to be done for data path
- As an O-DU L2 developer, I want to add support for Mu1
- Code changes at DU APP completed.
- Resource allocation for SSB to msg5 completed
- Code changes for UE registration flow in progress
- Updates to k0, k1, k2 in progress
- As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
- Code changes at DU APP completed.
- Resource allocation for SSB to msg5 completed
- Code changes for UE registration flow in progress
- Updates to k0, k1, k2 in progress
- As an O-DU L2 developer, I want to add support for TDD mode
- Code changes at DU APP completed.
- Resource allocation for SSB to msg5 completed
- Code changes for UE registration flow in progress
- Updates to k0, k1, k2 in progress
|
- As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
- SSB transmission successful
- Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
- Awaiting inputs from Intel
|
- As an O-DU L2 developer, I want to integrate O-DU High with O-CU
- Using Radisys commercial CU as a test fixture
- New VM to be configured as per H/W and S/W requirements of Radisys CU
- As an O-DU L2 developer, I want to support End to End testing scenarios
- Testing of broadcast messages at O-RU emulator set to begin
- Viavi confirmed receiving at O-RU. Needs verification from UE sim.
Updates from HCL:
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:
|
- As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
- As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- Edit-config implementation for o-ran-sc-du-hello-world YANG (admin state changes), Done.
- Integration with O-DU code for cell down and up scenario in progress
- Integration testing with OAM in progress
Dependency/Blockers:
- O1 configuration for day-1 shall need to be completed to start with CLA. However basic configuration e.g. cell state/operational state/admin state shall be supported initially. Use admin state as unlocked to validate the RU link failure.
- Server(VM) configuration (H/W and S/W) to mount Radisys CU as a test fixture.
- Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.
- SIB1 PDSCH reached L1 but cannot be observed in logs. Awaiting response from Intel.
- Viavi to confirm successful decoding of SSB at UE sim (TM500).
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:
Status
Simulators (SIM)
Primary Goals:
- Support rapid prototyping by providing simulated interfaces
D Feature Scope:
- Enable "Closed Loop Use Case" demonstration by providing O1 interface Simulators for:
- O-DU (containing o-du-hello-world YANG model)
- O-RU (containing O-RAN-RU-FH November 2020 train YANG models)
- O1 Simulator improvements:
- "Blank" simulator, which allows dynamically loading any YANG models of interest, for simulating a NETCONF/YANG interface
PTL: Alex Stancu
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues
Status:
- O-DU O1 Simulator docker image available in Nexus (version 1.3.1)
- O-RU O1 Simulator docker image available in Nexus (version 1.3.1)
- Example docker-compose for deploying O-DU and O-RU simulators: "D" Release - Closed Loop Use Case: Simulation of O-RU and O-DU
- Blank O1 Simulator docker image available in Nexus (version 1.3.1)
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
| ||||||||||||||||||||||||||||
Infrastructure (INF) | ||||||||||||||||||||||||||||
Primary Goals:
| ||||||||||||||||||||||||||||
D Feature Scope:
| ||||||||||||||||||||||||||||
PTL: Xiaohua Zhang | ||||||||||||||||||||||||||||
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
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 applicableStatus (28 Oct. 2020): |
Documentation (DOC) |
---|
Primary Goals: TODO |
Bronze Feature Scope: TODO |
PTL: weichen ni |
Jira: Count of Epics, User Stories, Tasks, and Issues:, 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 |
|
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" |