Page tree

Versions Compared

Key

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

Cherry release page for the O-RAN Software community   

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

This page contains all the information specific to the Cherry release

See Requirements and Software Architecture under Committees and Projects for more details on current activities.

Second release capabilities include contributions under the following projects:

Table of Contents

Get Bronze

  • Use the master branch of the repos.

Documentation

  • TODO

Cherry Release Timeline

Cherry Timeline



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

Cherry feature scope:

  • Traffic steering use case:
    • Integrate KPIMON (by Samsung) in the use case. KPIMON uses E2 (KPM SM) to collect data about cells and UEs - the E2SM will be initially implemented by the E2 SIM using data generated by Viavi RAN simulator.
    • Enhance QP xApp with a real ML model trained with Viavi data (AT&T, HCL).
    • Enhance TS xApp to send E2 Control message to trigger handover - E2 message will be handled by the E2 SIM.
  • New xApps:
    • Anomaly Detection (AD by HCL) uses ML model to detect anomalies in data collected by KPIMON.
    • Load Predictor (LD by China Mobile) uses ML model to predict the load of a cell (using data collected by KPIMON)
    • Signal Storm Protection (SSP by Samsung) implements the initial steps towards a realization of the Signal Storm Protection use case (WG-1).
  • Code coverage and updates to use xApp SDK for existing xApps.

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

Jira
serverORAN Jira
jqlQueryproject = RICAPP ORDER BY priority DESC, updated DESC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

Status (9-8-20): Integration of KPIMON in progress, new xApps under design, QP-Driver updated to use new SDK for alarms and metrics.




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

Primary Goals: More manageability of the RIC platform, including platform alarms, platform stats from E2 and A1 and support for direct RMR-to-VES event conversion for VES stats, Support operator-initiated health-check via E2 and E2 connection state, E2 can reject new connection setup requests. REST interface for E2 subscriptions, further xApp framework APIs.

Cherry feature scope: Detailed list of JIRA items that we plan to work on in Cherry (requires LinuxFoundation login): link(28 items)

Status 2020-09-02: (a) I (PTL) am happy to see teams from Samsung and HCL joining the project with them actively working on capabilities related to the E2 simulator (actually in Alex' simulator project), more test automation (using the robot framework), benchmarking, SDL (shared data layer). (b) RIC-372 was the first commit from these new participants (c) we might be aiming for self-certification under LF's CII badge level "basic", (d) work on O1-related functions, like E1 and A1 statistics, or some alarms already done. (e) Adaptation to E2APv1.1 only happening post-Cherry.



Non-Real-time RIC (A1 Interface) (NONRTRIC)

Primary Goals: TODO

Bronze Feature Scope: TODO

Jira: Count of Epics (

Jira
serverORAN Jira
jqlQueryproject=NONRTRIC AND type=EPIC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
), User Stories, Tasks, and Issues: 
Jira
serverORAN Jira
jqlQueryproject=NONRTRIC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008


Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%3DNONRTRIC
statTypeissuetype
chartTypepie
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008



OAM (O1 Interface)

Primary Goals:

  • update OAM projects for latest O-RAN Specifications
    • O-RAN Operations and Maintenance Architecture Version 3.0 - April 2020
    • O-RAN Operations and Maintenance Interface Version 3.0 - April 2020

    • O-RAN Use Cases Detailed Specification 2.0 - April 2020

    • O-RAN Management Plane Specification Version 3.0 and YANG Models Version 3.0 - April 2020

  • support of the application LCM use case
  • handover SMO artifacts to new SMO project

Cherry Feature Scope: 

  • Switch to Java11
  • Switch to OpenDaylight version Sodium (O1 termination NetConf)
  • https only support for  VES-Collector (O1 termination VES)
  • full IPv6 support

Please see OAM Cherry page for further details

Status:

Jira: Count of Epics (

Jira
serverORAN Jira
jqlQueryproject=OAM AND type=EPIC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
), User Stories, Tasks, and Issues: 
Jira
serverORAN Jira
jqlQueryproject=OAM
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008


Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%3DOAM
statTypeissuetype
chartTypepie
width
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008



O-RAN Central Unit (OCU)

Primary Goals: TODO

Bronze Feature Scope: TODO

F1

SDAP

PDCP

RRC

Ng

E1


PTL: Yingying Wang

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

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-1
  F1

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-2
 SDAP

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-3
 PDCP

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-4
 RRC

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-5
 Ng

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyOCU-6
 E1




O-DU High

Primary Goals: 

  • Develop L2 layers to achieve UE attach with UL and DL data on FDD, mu=0, BW=20 MHz
  • Interface with O-CU on F1AP
  • Interface with near RT RIC on E2AP
  • Interface with O-DU Low using FAPI
  • Interface with OAM on O1


Cherry Feature Scope: 

  • Implement UE attach procedure with basic scheduling on FDD, mu=0, BW=20 MHz
  • Implement single UE DL and UL data path and bench-marking
  • Add support for 64QAM modulation scheme in DL and 16QAM in UL
  • Add support for all short PRACH formats
  • Integrate O-DU High with O-DU Low
  • Integrate with Viavi sim/O-CU
  • Explore O1 interface
  • Establish Netconf session for O1 interface for CM
  • Support Health Check use-case

Updated: 23 September 2020

Jira: EPICS Status below:

Dependency:

  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.




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


Cherry Release Feature Scope: 

  • O-DU Low and O-DU High integration according to RSAC and INT project alignment features and scope
  • O-DU Low and O-RU/RRU emulator integration  according to RSAC and INT project alignment features and scope
  • E2E integration  according to RSAC and INT project alignment features and scope
  • O-DU Low integrated with thirty party commercial SW to verify the UE attachment and traffic, update the O-DU Low version accordingly
PTL: @Zhimin Yuan

Status

  • O-DU Low integrated with thirty party commercial SW to verify the UE attachment and traffic, update the O-DU Low version accordingly – Done

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyODULOW-14

  • O-DU Low and O-DU High integration according to RSAC and INT project alignment features and scope --WIP
    • not start
    • OSC Lab environment is installing OS
    • N3000 need flash image

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyODULOW-11

  • O-DU Low and O-RU/RRU emulator integration  according to RSAC and INT project alignment features and scope – WIP
    • not start
    • O-RU emulator is not available yet

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyODULOW-12

  • E2E integration  according to RSAC and INT project alignment features and scope – WIP
    • not start
    • dependent on above two

Jira
serverORAN Jira
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyODULOW-13

  • Dependency:

    • OSC lab availability 
    • O-RU emulator, O-CU and UE availability.



Simulators (SIM)

Primary Goals:

  • Support rapid prototyping by providing simulated interfaces

Cherry Feature Scope:

  • O1 Simulator enhancements
    • Upgrade NETCONF Server framework
  • E2 Simulator enhancements
    • Implement more message types
    • Assess if E2 Simulator can be used for benchmarking
  • Maintain alignment with latest YANG models

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

Jira
serverORAN Jira
jqlQueryproject = SIM AND resolution = Unresolved ORDER BY priority DESC, updated DESC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%20%3D%20SIM%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
statTypeissuetype
chartTypepie
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008




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.

Cherry Feature Scope:  TODO

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

Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%20%3D%20INF%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC%20%20%20
statTypepriorities
chartTypepie
width
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%20%3D%20%22INF%22%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(%22Cherry%22)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC%20%20%20%20%20%20%20
statTypeissuetype
chartTypepie
width
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008


  •  The INF project status update at INF project status for 26-Aug-2020.
  •  The INF project status update at 24-Sept-2020
    • The first major goal of "enable the duplex deployment with HA features" has been done. No block issue in JIRA although there are some issues left.




Integration and Test (INT)

Primary Goals: TODO
Bronze Feature Scope:  TODO

PTL:  Lusheng Ji

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

Jira
serverORAN Jira
jqlQueryproject = "INT" AND resolution = Unresolved AND fixVersion in ("Bronze", "Bronze-R3", "Bronze-R4") ORDER BY priority DESC, updated DESC
counttrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
Jira Charts
borderfalse
showinforfalse
serverORAN Jira
jqlproject%20%3D%20%22INT%22%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(%22Bronze%22%2C%20%22Bronze-R3%22%2C%20%22Bronze-R4%22)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
statTypeissuetype
chartTypepie
isAuthenticatedtrue
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008



Documentation (DOC)

Primary Goals: TODO
Bronze Feature Scope: TODO

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). 
Cherry Feature Scope: SMO entered the Cherry release in the middle of third sprint of code development. As such its scope is fairly modest. They are validation of application packages, assuming that we can agree on the format of the package, on boarding of applications and storing them in a package catalog which also has to be agreed upon, and as a stretch goal, setting up an environment where YANG modules that will be used by O-RAN, whether they are from 3GPP, and O-RAN itself can be used by vendors developing RIC, CU, DU and the RU to test a MVP configuration.

Status: