Versions Compared

Old Version 8

changes.mady.by.user Jackie Huang

Saved on

compared with

New Version 9

changes.mady.by.user Thoralf Czichy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Welcome to the E release page for the O-RAN Software community.

To download the source code for the E release, please check the section "E 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 E release and to deployment instructions.

General E release container image list for all subprojects. 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,

Table of Contents
        

...

Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)

Mission: Update to newer O-RAN specs (E2,A1,O2,O1) and related features. TODO

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 TODO // TODO Epics planned: link-TODO and 11 TOOD items as stretch goals: link

Achieved E release highlights = high-level release notes (2021-06-28TODO) 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.(once releases): TODO)

TODO once released

PTL: Thoralf Czichy

Status 2021-0709-05: Status 2021-03-03: 15: we are working on implementing the planned development items

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-depWe 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:
  • 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)
More detail:
  • For documentation, guides and a full discussion of NONRTRIC D Release see NONRTRIC: Release E

PTL: 

Jira:

D release source code, container images and deployment instructions

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

...