Cherry Release (Dec 2020)
Cherry release page for the O-RAN Software community
Welcome to the Cherry D 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:
- Cherry release D release page for the O-RAN Software community
- Near-Real-time RIC X-APPs (RICAPP)
- Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)
- Non-Real-time RIC (A1 Interface) (NONRTRIC)
- OAM (O1 Interface)
- O-RAN Central Unit (OCU)
- O-DU High
- O-DU Low
- Simulators (SIM)
- Infrastructure (INF)
- Integration and Test (INT)
- Documentation (DOC)
- Service Management and Orchestration (SMO)
Get Cherry
- Getting Started with Cherry to set up and run O-RAN
- Release Date:Source Code:Release Tar ball:
- o-ran-sc-cherry-20201215-part-1.tar.gz
- o-ran-sc-cherry-20201215-part-2.tar.gz o-ran-sc-cherry-20201215-part-3.tar.gz
- Cherry release docker image list: Release Image List
- Maintenance:
- Source Code:
- Release Changelog:
- it/dep: Add A1 STD V2 simulators. Fix bugs in helm 3 installation.
- scp/ric-app/kpimon: Release version 1.0.1. Use SDL library.
- nonrtric: Release new docker images. Fix maven project settings.
- ric-plt/ric-dep: Update alarmmanager helm charts.
- ric-plt/lib/rmr: Release new RMR version, fix multiple bugs.
- ric-plt/e2mgr: Update RMR version to 4.5.2.
- ric-plt/e2: Update RMR version to 4.5.2.
- ric-plt/alarm-go: Update RMR version to 4.5.2.
- ric-plt/o1: Update RMR version to 4.5.2.
- ric-plt/rtmgr: Update RMR version to 4.5.2.
- ric-plt/submgr: Update RMR version to 4.5.2.
- ric-plt/a1: Update RMR version to 4.5.2.
- sim/a1-interface: Update cherry release documents
Documentation
- Developer Documentation
- Highlighted use cases
- Service Management and Orchestration (SMO) [ RSAC LCM call flow ]
- Applications (xApps) [ RSAC Traffic Steering call flow ]
- O-DU
- Non-RT RIC
- A1 Enrichment Interface (A1-EI)
- Wiki
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). |
D release highlights (12-08-20):
|
PTL: Matti Hiltunen |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status ( |
3- |
1- |
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.
Status(11-17-20): ML-xApps (QP,AD) code committed - dealing with merge issues. End to end testing and bug fixes underway. E2AP/SM abstraction work for HelloWorld (C++) xApp completed. New repos created for HelloWorld in go and python (for Dawn).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:
HCL: RIC-360 done.
ATT: (e-mail sent): RIC-359 (likely postponed)Status 2020-12 |
HCL: DONE: RIC-149 (=RIC-362), RIC-509, RIC-109. // delayed into Dawn: RIC-150 // RIC-360: Code submitted & Merged CLOSE once gerrit review in RIUC-678 is done (see open review https://gerrit.o-ran-sc.org/r/c/it/dep/+/5237)
ATT: (e-mail sent): RIC-359 (likely postponed)
Status 2020-11-24:
HCL: RIC-149, RIC-150, RIC-360, RIC-509. Ask if RIC-362 (duplicate of RIC-149) is already implemented by HCL.
Nokia: (1) stats related: RIC-422 posytponed to early Dawn. Related stats-items (RIC- |
ATT: (e-mail sent): RIC-359 (likely postponed)
Status 2020-11 |
: |
RIC-57: two subitems open (for Nune 2020-11-12 reminder sent) and one for Timo (RIC-104). Two e-mails sent. Result: RIC-104 (not yet done, move out of Cherry) Done
RIC-76: e-mail sent as item 6 in bulk mail.
RIC-95: Completed (2020-11-12)
RIC-359: Queried status. 2020-11-12: Reminder sent
RIC-360, RIC-150. RIC-362, RIC-509: Reminder to subteam h1 sent.
RIC-363: e-mail send to Matti. 2020-11-12: reminder sent and Matti will close it with some conclusions. DONE
RIC-365 DONE. and remaining subuser stories (like RIC.429) moved to future work epic (RIC-681)
RIC-367 DONE and two subitems moved to Dawn RIC-682. xapp-framework python. e-mail sent we need to get the E2AP work done, and then we could extract one subitem as own epic and clsoe teh oevrall item.
RIC-422: e-mail send to Nune (bulk mail)
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:
|
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.
Update - 04/November/2020
- Initial rApp catalogue is mostly ready for first tests.
- A1 Enrichment Information job coordination function ready.
- Ongoing work on A1 EI job control in NONRTRIC Control Panel.
- A1-AP v2.0 (A1 Policy) is ready for implementation (Internal implementation already completed, now ready for release to the community)
- Integration of ONAP A1 Controller functions
- Extensions & evolution for NONRTRIC Control Panel & A1 SIM (version update, & gneral improvements)
- A1 Policy Management Bench-marking completed ... more info to follow
- Other ongoing tasks: documentation, automated integration testing, CSIT, Function Test environment refactoring, etc.
Update - 08/December/2020
D Feature Scope:
|
PTL: John Keeney |
Jira: Count of Epics ( 20 issues ), User Stories, Tasks, and Issues: 455 issues |
OAM (O1 Interface) |
---|
Primary Goals: |
O-RAN Operations and Maintenance Interface Version 3.0 - April 2020
O-RAN Use Cases Detailed Specification 2.0 - April 2020
Draft O1 yang models implemented and tested against the SIM implementation - not published in LNF repos
|
D 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
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:
|
Cherry Feature Scope |
: |
- support Broadcast of system information;
- support RRC connection control;
NG:
E1:
- support Interface Management procedures
- support Bearer Context Management procedures
F1:
- support Interface Management procedures
- support UE Context Management procedures
- support RRC Message Transfer procedures
- support System Information Procedures
PTL: |
O-DU High |
---|
Primary Goals: |
Cherry Feature Scope:
|
|
Updated: 16 December 2020
Documentation and release related activities for Cherry release have been completed.
Jira: EPICS Status below:
- As an O-DU L2 developer, I want to implement UE attach procedure with basic scheduling
- As an O-DU L2 developer, I want to add support for all short PRACH formats
https://jira.o-ran-sc.org/browse/ODUHIGH-191 - Done
- As an O-DU L2 developer, I want to explore O1 interface
- Made certain exploration and begun work on CM and health check use-case
- As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
- CM supported limited to IP and port configs for F1 and E2 interface using custom yang files
- Code yet to be merged
- As an O-DU L2 developer, I want to support Health Check use-case
- get-alarm list to be supported i.e., Health Status Retrieval
- Code merged into master branch.
- As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low
- O-DU High successfully integrated with O-DU Low in timer mode
- O-DU High completed aligning with latest FAPI files from Intel for Radio mode
- Radio mode testing to be begin once O-RU integration is complete
- As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
- Design in progress.
- As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
- Design in progress
- PUCCH code changes in progress
- As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
- Code under review for signaling
- As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
- Code under review for signaling
O-DU |
---|
- integration plan discussion begun.
Dependency/Blockers:
- Custom Yang files will be used for Dev activity.
- FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.
Low |
---|
Primary Goals:
|
D Release Feature Scope: |
PTL: @Zhimin Yuan |
|
- 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 - O-DU Low integrated with thirty party commercial SW to verify the UE attachment and traffic, update the O-DU Low version accordingly DONE
successfully do the UE attachment and traffic
ODULOW-11 - O-DU Low and O-DU High integration according to RSAC and INT project alignment features and scope IN PROGRESS
O-DU Low and O-DU High integration – in progress
- OSC Lab environment is installing OSC INF, O-DU Low can build/run in OSC INF
- O-DU Low and O-DU High P5 massage integration using O-CU stub and O-DU low time mode – done
- O-DU Low and O-DU High further P7 integration - not start
ODULOW-12 - O-DU Low and O-RU/RRU emulator integration IN PROGRESS
O-DU Low and O-RU/RRU emulator integration - in progress
- according to RSAC and INT project alignment features and scope – Done
- integration the S-plane, O-DU low and O-RU emulator get synchronized – in progress
- C-plane test, O-RU emulator can parse the C-plane message correctly – not start
- U-plane test, pass SSB, PDSCH, PUSCH, PRACH channel data exchange – not start
ODULOW-13 - E2E integration according to RSAC and INT project alignment features and scope TO DO
E2E integration – not start
- support E2E integration with O-DU High, O-CU, O-RU emulator and UE
- align with RSAC and INT project alignment features and scope
Simulators (SIM) |
---|
Primary Goals:
|
Cherry Feature Scope: |
- Implement more message types
- Assess if E2 Simulator can be used for benchmarking
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
Status (07 Oct. 2020): |
Infrastructure (INF) |
---|
Primary Goals:
|
D Feature Scope: TODO |
PTL: Xiaohua Zhang |
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.
- Status update 28-Oct-2020
- The AIO deployment scenario has been supported. Althought there are some issues/bugs, but it won't affect the functionalities at all.
- For the AIO with additional worker nodes, the codes had been checked into the repo, the verification and test is still ongoing. (it will be delayed to Dawn release).
- Continue to support the integration test.
- Continue to prepare the document of Cherry release.
- Status update 11-Nov-2020
- Already add the packages which were missing during the ODU-High/Low integration.
- Some other issues will be addressed before 14-Nov-2020
- In general, ready to cut-off by 14-Nov-2020
- Status update 09-Dec-2020
- Final image has been generated.
- Finish the integrate test with O-DU Low/High
- Document has been updated into repo for release note and others.
Integration and Test (INT) |
---|
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases |
Cherry Feature Scope:
|
PTL: Zhe Huang |
Jira: Count of Epics, User Stories, Tasks, and Issues: 54 issues |
Status (28 Oct. 2020): |
- done: A1 and python xApp-framework
- Pending: Rest of the projects
- 21 projects passed
- 7 project failed
- Initiate works with O-DU-low CI
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: |
David Kinseyis driving package catalog requirements, which is LCM Step 3. But it was determined that package catalog can be implementation specific, and therefore SMO cannot validate any particular catalog. As such LCM Step 3 will be skipped.
The second part of SMO was the setup of a framework for testing of YANG models that are going to be used by SMO and the Network Functions that constitute the O-RAN solution. Thanks Martin Skorupski, Zhe Huang , and Alex in setting up that framework in the OSC lab.
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 |