You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Welcome to the D release page for the O-RAN Software community          



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 (12-08-20):

  • Expanded set of xApps from expanded community: Cherry release includes xApps from AT&T (TS, QP-D, QP, HW, MC), Samsung (KPIMON), and HCL (AD).

PTL: Matti Hiltunen

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

Status (3-1-21): 



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


Mission: Better manageability of, for example, E2 connections, the RIC platform as well as xApps via the xApp frameworks.

Primary Goals: Support operator-initiated health-check via E2 and be able to close all current or reject all future E2 connections. More manageability of the RIC platform and xApps, including, for example, platform statistics from E2 and A1 and more capabilities in the language-specific xApp frameworks and SDL (shared data layer).

Drelease highlights (2020-12-01): 

PTL: Thoralf Czichy

Status 2020-12-11:



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

D Feature Scope:

PTL: John Keeney

Jira: Count of Epics ( 20 issues ), User Stories, Tasks, and Issues:  455 issues


OAM (O1 Interface)


Primary Goals:

  • support of the application LCM use case
    • Discussion about the details together with the SMO project
  • handover SMO artifacts to new SMO project

D Feature Scope: 


PTL: Martin Skorupski

Status:

Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues:  166 issues

Demo of OAM use cases


O-RAN Central Unit (OCU)


Primary Goals: 
  • Source code includes RRC, Ng, E1, F1. Platform and OM are provided in  dependent libraries.
  • O-CU-CP is integrated with O-CU-UP, O-CU functions should be complete.

Cherry Feature Scope: 

PTL:

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

OCU-1 - O-CU F1 interface for Release B TO DO   F1

OCU-2 - O-CU SDAP TO DO  SDAP

OCU-3 - O-CU PDCP TO DO  PDCP

OCU-4 - O-CU RRC TO DO  RRC

OCU-5 - O-CU Ng TO DO  Ng

OCU-6 - O-CU E1 TO DO  E1



O-DU High


Primary Goals: 


Cherry Feature Scope: 

  • Implement UE attach procedure with basic scheduling on FDD, mu=1, BW=20 MHz


O-DU Low


Primary Goals:  

  • Integrate with O-DU High with FAPI interface with cherry release aligned IOT profile
  • Integrate with O-DU emulator from Viavi with cherry release aligned IOT profile
  • Support E2E integration with O-CU, O-DU High, O-RU emulator and UE for UE attachment


D Release Feature Scope: 

PTL: @Zhimin Yuan

  • Status



Simulators (SIM)


Primary Goals:

  • Support rapid prototyping by providing simulated interfaces

Cherry Feature Scope:

PTL: Alex Stancu

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

Status (07 Oct. 2020): 


Infrastructure (INF)


Primary Goals: 

  • 2 servers. 2 AIO servers with HA (high availability), the controller functionality and storage functionality will be deployed at the 2 servers with standby-active mode managed by "service management". If one server or one service in one server has error, it will be switched from active to standby one to maintain the service availability.
  • 2 AIO servers with additional worker node.

D Feature Scope:  TODO

PTL: Xiaohua Zhang

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


Integration and Test (INT)


Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases

Cherry Feature Scope: 

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


PTL:  Zhe Huang

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


Status (28 Oct. 2020): 


Documentation (DOC)


Primary Goals: TODO
Bronze Feature Scope: TODO

PTL: weichen ni

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



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 

Status:  

For a detailed workflow and end-to-end test manual of the two parts, refer to Cherry Release Test Plans for SMO.

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



  • No labels