Page tree
Skip to end of metadata
Go to start of metadata

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:

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:  Getting issues...

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

Status (9-30-20): Samsung taking over integration and testing of KPIMON; Viavi simulator producing data - an update in the data content expected this week (UE throughput, UE ID); ML-model building started based on Viavi and other simulated data (QP, AD); new xApp repos requested (Signal Storm Protection, Load Prediction); bug fixes to HelloWorld, E2 AP/SM abstraction layer underway for HelloWorld.


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-30: (a) I (PTL) am happy to see HCL doing work on Sonarqube for repos. Much more work done by HCL in context of benchmarking (simulator work), new helm and k8s version, Redis cluster suppor and testing, JIRA link for team H1  (b)  Samsung also doing key work items, e.g. for RIC-95 health check (with side affect of support for E2 SERVICE QUERY and related) - suffering from simulator support (RIC-372 already mentioned below), work started on demo (aka more elboarte hello world) xApp in go/python. (c) four items moved out of Cherry as already visible that not enough time: link . (d) 28 Cherry items = 4 moved out of Cherry + 10 done + 14 in progress or still to be started (e) Matti and Thoralf gave a presentation on RIC status in the virtual ONeS 2020 (link). Waiting for copyright/licensing results between O-RAN and O-RAN SC.

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 robotframework), 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 E2 and A1 statistics, or some alarms already done. (e) Adaptation to E2APv1.1 (likely released in November) only happening post-Cherry.

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)

Cherry Feature Scope:

  • A1 Policies:
    • A1 Policy Management Service (hosted in ONAP CCSDK)
    • A1 Policy Controller Adapter (hosted in ONAP CCSDK)
    • A1 Simulator / test stub (SIM project)
    • A1 Policy Control-Panel (PORTAL project)
    • Support A1-AP v2.0.
  • A1 Enrichment Information
    • Initial version of A1 EI Job coordination function/service
  • Deployment/Integration
    • Docker-based & OSC Kubernetes deployment & ONAP OOM Kubernetes deployment (Overlaps with SMO project)
  • rApps
    • Very simple hello-world rApp
    • TrafficSteering usecase
    • Healthcheck usecase
  • rApp support
    • Initial rApp catalogue/inventory
    • Initial approach with rApp packaging (overlaps with "common App" usecase, & SMO project)
  • Requirement gathering & initial test/integration with ML supporting functions in NONRTRIC/SMO
  • Requirement gathering & initial test/integration with data collection & coordination functions in NONRTRIC/SMO
  • Requirement gathering & initial test/integration with CMDB (if progressed in ONAP), Topology & Inventory functions in SMO

Update - 06/October/2020

  • Prototyping of the A1 enrichment Information coordination service is in progress.
  • Initial prototype of rApp registration / catalogue function, Very simple hello-world rApp.
  • Ongoing work to support O-RAN WG2 A1-P spec.
  • A1 Policy Management Service and A1 Policy Controller Adapter hosted in ONAP CCSDK are getting ready for ONAP Guilin Milestone RC0.
  • Other ongoing tasks: documentation, automated integration testing, CSIT, Run benchmark test in a cloud instance, Function Test environment refactoring, etc.

Jira: Count of Epics ( Getting issues... ), User Stories, Tasks, and Issues:  Getting issues...


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

    • Draft O1 yang models implemented and tested against the SIM implementation - not published in LNF repos

  • support of the application LCM use case
    • Discussion about the details together with the SMO project
  • 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 ( Getting issues... ), User Stories, Tasks, and Issues:  Getting issues...


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:

OCU-1 - Getting issue details... STATUS   F1

OCU-2 - Getting issue details... STATUS  SDAP

OCU-3 - Getting issue details... STATUS  PDCP

OCU-4 - Getting issue details... STATUS  RRC

OCU-5 - Getting issue details... STATUS  Ng

OCU-6 - Getting issue details... STATUS  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

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

Updated: 14 October 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • in timer mode, Intel expects another prelim msg to be sent from O-DU High before config.REQ. This must be added to O-DU High referring to Intel's test stub(testMac).
  • 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

ODULOW-14 - Getting issue details... STATUS

  • 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

ODULOW-11 - Getting issue details... STATUS

  • 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

ODULOW-12 - Getting issue details... STATUS

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

ODULOW-13 - Getting issue details... STATUS

  • 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:  Getting issues...


Status (07 Oct. 2020): 

  • E2 Simulator - support for new E2 Messages - done
  • E2 Simulator - benchmarking of RIC - in progress
  • O1 Simulator - upgrade of NETCONF Server - in progress
  • OTF integration - TBD

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:


  •  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: 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: Getting issues...

Status (21 Oct. 2020): 

  • CLM scanning jobs:
    • done: A1 and python xApp-framework
    • Pending: Rest of the projects
  • SonarQube scanning jobs:
    • 21 projects passed
    • 7 porject failed
  • OSC Lab internal CI pipeline:
    • Initiate works with O-DU-low CI 
  • OSC Lab Testing and Validation
    • VM created for SMO validation. Access provided for Alex and Martin
    • VM created for TS use case validation.

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:  Have made a proposal on application package format. Further discussion and agreement required for containers. Discussion to continue in F2F. David Kinseyis driving package catalog requirements. In discussion with Martin Skorupskiand Alex Stancuto setup a framework for testing of YANG models using SMO. Still waiting for Gerrit and Jira to be created.


  • No labels