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 Cherry
- Getting Started with Cherry to set up and run O-RAN
- Release Date:
- Source Code:
- Release Tar ball:
- Cherry release docker image list: Release Image List
- Source Code:
- 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). |
Cherry release highlights (12-08-20):
|
PTL: Matti Hiltunen |
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. 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). |
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). |
Cherry release highlights (2020-12-01): We implemented the operator-initiated E2 connection health check. There is now more alignment in the level of support of various xapp framework and SDL features in python, c++ and go. For example: SDL (shared data layer) now also supports notifications in Python. The xApp framework for C++ now supports alarms, statistics and configuration management. xApps can now use SDL notifications for changes in connection states of E2 nodes. By confirming route updates before continuing we increased robustness in management of internal routes. We now also support using existing non-E2 protocols for communication with RAN. We also adapted the scaling implementation for E2 termination to the reversal of E2AP connection initiation introduced by E2AP 01.00. The E2 manager can now reject new E2 connections requests in addition to closing all E2 connections. E2 and A1 now provide platform statistics for their connections. Detailed list of JIRA items that we worked on in Cherry (requires LinuxFoundation login): Remaining open items: link (1 items). Items that are marked as done: link (23 items). Moved out from Cherry: link (24 = 13 stretch goal items and 11 "normal items"). |
PTL: Thoralf Czichy |
Status 2020-12-11: HCL: RIC-360 done. ATT: (e-mail sent): RIC-359 (likely postponed) Status 2020-12-08: 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-33, RIC-126) postponed to later (likelly ZZZ_future). (2) submgr related RIC-76 and RIC-71 were postponed. ATT: (e-mail sent): RIC-359 (likely postponed) Status 2020-11-05: Remaining open items RIC-56: I now moved all sub user storied for actual alarms as separate independent Epics. Can be tested with artiifical alarm or QP driver xApp alarm. The framework is ready. Marking RIC-56 as Done. 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:
Update - 06/October/2020
Update - 04/November/2020
Update - 08/December/2020
|
PTL: John Keeney |
Jira: Count of Epics ( ), User Stories, Tasks, and Issues: Getting issues... Getting issues...
|
OAM (O1 Interface) |
---|
Primary Goals:
|
Cherry Feature Scope:
Please see OAM Cherry page for further details |
PTL: Martin Skorupski |
Status: Jira: Count of Epics ( ), User Stories, Tasks, and Issues: Getting issues... Getting issues...
|
Demo of OAM use cases |
O-RAN Central Unit (OCU) |
---|
Primary Goals:
|
Cherry Feature Scope: RRC:
NG:
E1:
F1:
|
PTL: Yingying Wang |
Jira: Count of Epics, User Stories, Tasks, and Issues: - OCU-1Getting issue details... STATUS F1 - OCU-2Getting issue details... STATUS SDAP - OCU-3Getting issue details... STATUS PDCP - OCU-4Getting issue details... STATUS RRC - OCU-5Getting issue details... STATUS Ng - OCU-6Getting issue details... STATUS E1 |
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:
Dependency/Blockers:
|
O-DU Low |
---|
Primary Goals:
|
Cherry Release Feature Scope:
|
PTL: @Zhimin Yuan |
|
Simulators (SIM) |
---|
Primary Goals:
|
Cherry Feature Scope:
|
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: Getting issues...
|
Status (07 Oct. 2020):
|
Infrastructure (INF) |
---|
Primary Goals:
|
Cherry 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:
|
PTL: Zhe Huang |
Jira: Count of Epics, User Stories, Tasks, and Issues: Getting 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). |
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. |
PTL: Mahesh Jethanandani |
Status: A proposal was made on application package format, and there was some agreement on it following the ETSI SOL 004 specification. The contributions into the SMO project currently validate that part of the agreement, and allow for Network Function, xApp and rApp vendors to validate their package using the tools developed in SMO. 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 ( ), User Stories, Tasks, and Issues: Getting issues... Getting issues...
|
7 Comments
Pavan Gupta
Hello,
I would like to streamline my understanding of OSC. To date I was working on the bronze release and could get SMO, near-RT RIC running. I have been able to run xAPP, O1 & A1 use cases. Kindly help with the following information:
Would truly appreciate if you could share above information.
Regards,
Pavan
Pavan Gupta
Hello,
There is a dependency on Intel C++ compiler for building O-DU and O-High functions. Going by the posts, I believe there are talks happening with Intel to provide a community license. While this is being worked out, are binaries for O-DU low and high available with anyone that can be tried for testing purposes?
Thanking you for your help.
Pavan
Zhe Huang
hi Pavan,
You can find detailed instructions on how to obtain a community license for ICC here.
https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-phy/en/latest/build_prerequisite.html#install-icc
From there you can build your O-DU high and low binary locally.
Felix
Pavan Gupta
Hi Zhe,
I tried following the steps provided in the link you had shared, but it mentions using license.lic file. Where can I get this license file from? Do I need to contact Intel for that? Does anyone have it that I can use.
You help will be truly appreciated.
Thank you.
Regards,
Pavan
Zhimin Yuan
Hi Pavan,
ICC was upgraded to new version, there will be no license needed, while we need some time to upgrade O-DU Low SW to adapt to this new ICC version.
Regard.
Zhimin
Madan Cheemakurthi
The link for deploying the Cherry release Getting Started is taking us to the Bronze Release's deployment.
Kindly, correct this anomaly.
Sindhu Pitta
Hi,
I want to know in end-to-end testing which core did you use and tested?
and also want some guidance in the following query:
I am integrating ODU Low +ODU High +CU +Free5GC for the end-to-end testing.
We are using,
1. Free5GC Core (https://github.com/free5gc/free5gc)
2. Our own CU SIMULATOR
3. Radysis DU(E-release) as ODU-H (github.com/o-ran-sc/o-du-12)
4. O-RAN DU Physical Layer ( https://gerrit.o-ran-sc.org/r/o-du/phy.git)
5. Open source FlexRAN (https://github.com/intel/FlexRAN)
I was able to connect Free5GC+CU+ODU High and test the registration procedure by following the below-given steps to bring up free5gc
https://github.com/free5gc/free5gc/wiki/Installation
But when connecting the whole integrated setup with ODU Low I am unable to see the registration procedure and captured the logs in Fapi and L1 binaries
We are running ODU Low with -e in TIMER mode.
The following link is the one I am using for running the ODU-H, L1, Fapi, CU :
https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/user-guide.html#b-pairwise-testing-with-intel-o-du-low
Attaching the logs captured.
Can someone guide us in how to check the registration procedure wrt ODU Low?
Looking forward to the solution.
Thank You,
Sindhu Pitta.