|Project Key||Project Name||PTL||Description|
|RICAPP||RIC Applications||Matti Hiltunen||This includes open source sample xAPPs and platform applications that can we used for integration, testing, and demonstrations.|
|RIC||Initial RIC Platform to support xAPPs with limited support for O1, A1, and E2 interfaces.|
|OCU||O-RAN Central Unit|
The OCU should target an initial software deliverable with limited functionality. Focus on aa basic E2 interface to enable initial integration testing between RIC and OCU.
|ODUHIGH||Sachin Srivastava||Focus on initial L2 functional blocks based on seed code contributions.|
|ODULOW||O-RAN Distributed Unit Low Layers||Focus on initial L1 functional blocks based on seed code contributions.|
|ORU||O-RAN Radio Unit||TBD||Out of scope for release "A".|
|OAM||Operations and Maintenance||O1-related sysdev; initial dashboard for monitoring and demonstration of contributions. More ...|
|SIM||Simulations||Alex Stancu||Initial simulators used for testing O-RAN NF interfaces.|
|INF||Infrastructure||Initial building blocks for infrastructure to run O-RAN NF components.|
|INT||Integration and Testing|
The integration and test effort will focus on testing the requirements documented in each release. This will focus on end to end test and use case testing.
NF Testing shall primarily be done on the Akraino-REC (Radio Edge Cloud) blueprint. While Non-RT RIC and O1 interface testing will primarily use ONAP components.
|Documentation||weichen ni||Documentation on contributions and O-RAN SC contents.|
|NONRTRIC||Non-RealTime RIC (RAN Intelligent Controller)|
Non-realtime RIC focus on feature functionality of A1-interface (consumer and provider), and closed-loop use cases. The NONRTRIC project will also work together with the OAM project to align activities on a case-by-case based for O1 interfaces. Project should focus on use cases supported in ONAP. The work should be sponsored in O-RAN and initial code contributions in O-RAN SC. Interoperability with ONAP should be aligned between the standards and will follow initial contributions in this project.
|SMO||Service Management and Orchestration (SMO)||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).|
NOTE: Repositories that are indicated as scp/ repositories are repositories maintained by the O-RAN Alliance and licensed under the O-RAN Specification Code Project under licenses that are different from the licensing of the O-RAN Software Community Project. For questions concerning an O-RAN Specification Code Project code or documentation, please contact the O-RAN Alliance.