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.

PTL: Matti Hiltunen

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

Jira

server	ORAN Jira
jqlQuery	project = RICAPP ORDER BY priority DESC, updated DESC
count	true
serverId	5ec52304-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.

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)
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)
PTL: Thoralf Czichy
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) 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. 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:

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.

Update - 04/November/2020

Initial rApp catalogue is mostly ready for first tests.
A1 Enrivhment 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 implemenation (Internal implemenatation alraeady completed, now ready for release to the community)
Integration of ONAP A1 Controller functions
Extensions & eveloution for NONRTRIC Control Panel & A1 SIM (version update, & gneral improvements)
A1 Policy Management Benchmarking completed ... more info to follow
Other ongoing tasks: documentation, automated integration testing, CSIT, Function Test environment refactoring, etc.

PTL: John Keeney

Jira: Count of Epics (

Jira

server	ORAN Jira
jqlQuery	project=NONRTRIC AND type=EPIC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

), User Stories, Tasks, and Issues:

Jira

server	ORAN Jira
jqlQuery	project=NONRTRIC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%3DNONRTRIC
statType	issuetype
chartType	pie
isAuthenticated	true
serverId	5ec52304-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
- 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

PTL: Martin Skorupski

Status:

Jira: Count of Epics (

Jira

server	ORAN Jira
jqlQuery	project=OAM AND type=EPIC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

), User Stories, Tasks, and Issues:

Jira

server	ORAN Jira
jqlQuery	project=OAM
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%3DOAM
statType	issuetype
chartType	pie
width
isAuthenticated	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

O-RAN Central Unit (OCU)

Primary Goals:

Source code includes RRC, Ng, E1, F1. Platform and OM are provided in dependent libraries.
O-CU-CP is integrated with O-CU-UP, O-CU functions should be complete.

Cherry Feature Scope:

RRC:

support Broadcast of system information；
support RRC connection control；

NG:

support PDU Session Management Procedures
support UE Context Management Procedures
support Transport of NAS Messages Procedures
support Interface Management Procedures

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: user-a934b

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

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-1

F1

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-2

SDAP

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-3

PDCP

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-4

RRC

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-5

Ng

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	OCU-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: 18 November 2020

Jira: EPICS Status below:

https://jira.o-ran-sc.org/browse/ODUHIGH-10 - Done
- As an O-DU L2 developer, I want to implement UE attach procedure with basic scheduling
https://jira.o-ran-sc.org/browse/ODUHIGH-188 - Done
- 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
https://jira.o-ran-sc.org/browse/ODUHIGH-196 - WIP
- 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 merged into dev branch, facing issues with merging into master branch
https://jira.o-ran-sc.org/browse/ODUHIGH-214 - WIP
- 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 dev branch, facing issues with merging into master branch
https://jira.o-ran-sc.org/browse/ODUHIGH-189 - WIP
- 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 to completed aligning with latest FAPI files from Intel for Radio mode
  - Radio mode testing to be planned
https://jira.o-ran-sc.org/browse/ODUHIGH-184 - WIP
- As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  - Design in progress.
https://jira.o-ran-sc.org/browse/ODUHIGH-185 - TODO
- As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
https://jira.o-ran-sc.org/browse/ODUHIGH-186 - TODO
- As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
https://jira.o-ran-sc.org/browse/ODUHIGH-187 - TODO
- As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
https://jira.o-ran-sc.org/browse/ODUHIGH-190 - WIP
- As an O-DU L2 developer, I want to integrate O-DU High with Viavi softwares
  - integration plan discussion begun.

Dependency/Blockers:

HCL unable to merge O1 code into master branch.
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.

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
server ORAN Jira
serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008
key ODULOW-14
successfully do the UE attachment and traffic
Jira
server ORAN Jira
serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008
key ODULOW-11
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

N3000 flash images, both HW/~~SW LDPC can be enabled~~

- - 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
Jira
server ORAN Jira
serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008
key ODULOW-

11

12
O-DU Low and O-RU/RRU emulator integration - in progress

Jira

server	ORAN Jira
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008
key	ODULOW-12

- 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

E2E integration according to RSAC and INT project alignment features and scope – WIP

not start

dependent on above two

Jira
server ORAN Jira
serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008
key ODULOW-13
E2E integration – not start

- support E2E integration with O-DU High

Dependency:

OSC lab availability

O-RU emulator

- , O-CU

and UE availability.

- , O-RU emulator and UE
- align with RSAC and INT project alignment features and scope

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

PTL: Alex Stancu

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

Jira

server	ORAN Jira
jqlQuery	project = SIM AND resolution = Unresolved ORDER BY priority DESC, updated DESC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%20%3D%20SIM%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
statType	issuetype
chartType	pie
isAuthenticated	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

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

PTL: Xiaohua Zhang

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

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%20%3D%20INF%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC%20%20%20
statType	priorities
chartType	pie
width
isAuthenticated	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%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
statType	issuetype
chartType	pie
width
isAuthenticated	true
serverId	5ec52304-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.
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

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:

Jira

server	ORAN Jira
jqlQuery	project = "INT" AND resolution = Unresolved AND fixVersion in ("Bronze", "Bronze-R3", "Bronze-R4") ORDER BY priority DESC, updated DESC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%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
statType	issuetype
chartType	pie
isAuthenticated	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Status (28 Oct. 2020):

CLM scanning jobs:
- done: A1 and python xApp-framework
- Pending: Rest of the projects
SonarQube scanning jobs:
- 21 projects passed
- 7 project failed
OSC Lab internal CI pipeline:
- Initiate works with O-DU-low CI
OSC Lab Testing and Validation
- SMO Yang model tests completed.
- VM created for TS use case validation.

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 formal proposal on the outline of an application package format has been presented to WG1, where it did not receive any objection. However, a formal package definition will not happen before the next release in March of 2021. With that fact, a pre-standard package definition has been developed, and will form as part of the demo for the Cherry release. In addition, the test framework for testing of YANG models has been set up in the OSC lab. A sample Postman script has been checked into Gerrit for users to use to set up their own tests. Finally, a discussion is underway with O-DU team to see if the version of O-DU in OSC can be used for SMO testing of O1 interface.

Jira: Count of Epics (

Jira

server	ORAN Jira
jqlQuery	project=SMO AND type=EPIC
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

), User Stories, Tasks, and Issues:

Jira

server	ORAN Jira
jqlQuery	project=SMO
count	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

Jira Charts

border	false
showinfor	false
server	ORAN Jira
jql	project%3DSMO
statType	issuetype
chartType	pie
width
isAuthenticated	true
serverId	5ec52304-b77c-3ce7-af6a-112cb13e6008

...

Show all results

Page tree

Versions Compared

Old Version 63

New Version 64

Key

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

Page tree

Page History

Versions Compared

Old Version 63

New Version 64

Key

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