Status (5-25-21): 

E Release status

• New xApps:
• Improved xApps:

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

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

Status 2021-07-05: 

Status 2021-03-03: 

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

• 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 applications) to perform Non-RT-RIC tasks.
• Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)

E Feature Scope:

• NONRTRIC Functions: (NONRTRIC Release E Wiki)
• In D Release: (NONRTRIC Release E Wiki)

• For documentation, guides and a full discussion of NONRTRIC D Release see NONRTRIC: Release E

D release source code, container images and deployment instructions

• Source Code:
• Docker Images:
  •  
• Deploy / Run:
• Documentation:

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
• support D-Release use case "O-RU recovery"
  • see Feature Scope below
• handover SMO artifacts to new SMO project

E Feature Scope: 

• Update to OpenDaylight Silicon
• Support of Callhome via TLS
• CallHome to VES:pnfRegistration 
• o-ran-fm.yang/alarm-notif to VES:fault

• 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

D release source code, container images and deployment instructions

not applicable

Primary Goals: 

New Feature Development

• Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)

• Only slot based round robin scheduling support for multi UE scheduling

• Support for Multi Bearer

• Basic RAN slicing support
• Support for HARQ

Feature Verification

• Closed Loop Automation Feature Verification
• 16 QAM and 64 QAM Support Verification

End to End Integration Support

• TDD/Mu1/100MHz

• FDD/Mu0/20MHz * (Spillover from D release)

E Feature Scope: 

• Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)

• Only slot based round robin scheduling support for multi UE scheduling

• Support for Multi Bearer

• Basic RAN slicing support
• Support for HARQ
• End to End Integration Support (TDD and FDD stack validation)
• Closed Loop Automation Feature Verification

Status:

Updated:  15th Sept 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

D release source code, container images and deployment instructions

Release-Notes — o-du-l2 master documentation (o-ran-sc.org)

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: 

E release source code, container images and deployment instructions

TODO

Primary Goals:

• Support rapid prototyping by providing simulated interfaces

E Feature Scope:

Status:

E 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 E-Release

Primary Goals: 

• Implement the O-Cloud reference design, provide the real time performance to allow the O-DU and other components running on top of it.
• Provide interaction capabilities with other components.

E release Feature Scope:  

• Enabe the 2 AIO severs with additional worker nodes deployment scenario
• Major components upgrade
• Implement the O2 interface as the MVP (will defer to next release)

E release source code, container images and deployment instructions

• The repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/pti/rtp.git". Note that this branch is in maintenance and all new development is done in branch "master".
• No container image for INF projrect
• Deployment instruction: Getting Start (verification on Dell R740) /Sample test process

Feature Scope: 

• Automated CLM and SonarQube Scanning CI Jobs
• Improve CI for OSC projects
• Validate and and Test platform and use cases 

E release source code, container images and deployment instructions

not applicable

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

D release source code, container images and deployment instructions

not applicable

E Feature Scope:

Jira: Count of Epics ( 0 issues ), User Stories, Tasks, and Issues:  6 issues