Welcome to the E release page for the O-RAN Software community.
The E release is currently under development and its source code is maintained within the master branch of each repo. Once released further instructions related to separate maintenance branches and release image lists will be available here,
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, network slicing) 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). |
E release plan (12-01-21):
|
PTL: SUNIL SINGH (former PTL still helping out: Matti Hiltunen) |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status (12-01-21):
|
E release source code, container images and deployment instructions Will be provided when E Release is ready. |
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT) |
---|
Mission: E2 updates with first E2APv1.1 support and improvements in E2 subscription handling. Original primary goals: Update to E2APv1.1 ( |
Achieved E release highlights = high-level release notes (2021-12-03) below (note that the release image list is here (once releases): link)
For the E release of the near-RT RIC we did only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection were tested. Filled in end-of-release checklist : Release criteria checklist - Release E |
PTL: Thoralf Czichy |
Status 2021-12-03: we are working on implementing the last planned development items below. From the 29 epics planned (link) we implemented so far 11 (link). 12 items have been moved out of the E release, e.g, because of implementation delays (link). We expect 6 items to still complete and one item (RIC-375) is still under discussion what to do with it (link). RIC-113 (DB) - expected to complete by Dec-3 RIC-779 to complete by Dec-7, RIC-790, RIC-816 asked from Sunil. RIC-375 discussion with Anssi+Juha on whether we move this to F RIC-640 Subhash commented: "(likely done by Dec-6) " |
E release source code, container images and deployment instructions Each repository has a branch named "e-release" that can be accessed using git: "git clone --branch e-release "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 E 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 e-release ..." instead of "git clone ..." when cloning it/dep and ric-plt/ric-dep. |
Non-Real-time RIC (A1 Interface) (NONRTRIC) |
---|
Primary Goals:
|
E Feature Scope:
|
PTL: |
Jira:
|
|
Operation and Maintenance (OAM) |
---|
Primary Goals:
See more details on OAM wiki: E-Release |
E Feature Scope:
|
PTL: Martin Skorupski |
E 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:
|
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: New Feature Development
Feature Verification
End to End Integration Support
|
E Feature Scope:
|
PTL: user-30c9d |
Status: Updated: 17 Nov 2021 JIRA: Epics Status below:
Updates from HCL:
Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities Updated: 10 Nov 2021 JIRA: Epics Status below:
Updates from HCL:
Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities Updated: 20 Oct 2021 JIRA: Epics Status below:
Updates from HCL:
Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities Updated: 15th Sept 2021 JIRA: Epics Status below:
Updates from HCL:
Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities |
E 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 message 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 |
E Release Feature Scope: |
PTL: Luis Farias , Alternate: @Chenxi Yue |
|
E release source code, container images and deployment instructions TODO |
Simulators (SIM) |
---|
Primary Goals:
|
E Feature Scope:
|
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
Status: |
E release source code, container images and deployment instructions TODO |
Infrastructure (INF) |
---|
Primary Goals:
|
E release Feature Scope:
|
PTL: Jackie Huang |
Jira: Count of Epics, User Stories, Tasks, and Issues: Update at
Test status:
Release Note:
|
E 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 |
Feature Scope:
|
PTL: |
Jira: Count of Epics, User Stories, Tasks, and Issues: 54 issues |
E 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). |
E Feature Scope: In E-release, SMO will be extended to support network slicing. In particular, RSAC has come up with closed loop automation use case for network slicing which involves the SMO collecting PM counters related to network slicing, and based on them breaching some thresholds will cause a change in the configuration of the network slice. That means the SMO has to have support for PM counters related to network slicing, and an ability to reconfigure the O-DU for the network slice. Separately, AT&T has asked for a disaggregated VES solution that separates the collection of VES events from how it is presented to any application that wants to view them. |
PTL: Mahesh Jethanandani |
Status: Jira: Count of Epics ( 0 issues ), User Stories, Tasks: and Issues: 6 issues |
E 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. For the O1 interface the repository can be found at "git clone --branch e-release (when a release has been created) "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/ves" |