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 teh 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 (9-21-21):
|
PTL: Matti Hiltunen |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status (9-21-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. A1 reimplementation Original primary goals: Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (RIC-638, even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces (RIC-640)) // RIC-809 Subscription manager to delete subscriptions in case of E2 disconnect (incl. Xapp changes) // RIC-793 Prevent A1 Job ID conflicts from multiple RICs using the same A1 producer (SMO) // RIC-647 Reimplement A1 mediator in golang to avoid A1 being the only python container in RIC platform // RIC-709 E2 stats exposing individual counters instead of groups // RIC-714 support for DMS REST interface in addition to DMS CLI // RIC-113 DB: SDL CLI for debugging and testing // RIC-110 FindKeys/GetAllKeys SDL API to support glob-style patterns // 34 Epics planned: link and 30 items as stretch goals: link |
Achieved E release highlights = high-level release notes (TODO) below (note that the release image list is here (once releases): TODO) TODO once released |
PTL: Thoralf Czichy |
Status 2021-09-15: we are working on implementing the planned development items |
E release source code, container images and deployment instructions We again plan to cut a branch from the master branch once the E release is released and goes into maintenance. Also we plan to provide an ready-made container image list. |
Non-Real-time RIC (A1 Interface) (NONRTRIC) |
---|
Primary Goals:
|
E Feature Scope: D Feature Scope:
|
PTL: |
Jira:
|
|
Operation and Maintenance (OAM) |
---|
Primary Goals:
|
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: 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:
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 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" |