You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 20
Next »
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
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. |
|
---|
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 (
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
- 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 (
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: user-a934b |
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: EPICS are mentioned below: |
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...
|
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:
|
Integration and Test (INT) |
---|
Primary Goals: TODO |
Bronze Feature Scope: TODO |
|
Jira: Count of Epics, User Stories, Tasks, and Issues:
Getting issues...
|
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: TODO |
Bronze Feature Scope: TODO |
|
Status:
|