Project Key | Project Name | PTL | Description |
---|
RICNRT | Non real time RIC | John Keeney | 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. |
Matti HiltunenInitial SUNIL SINGH | This includes open source sample xAPPs and platform applications that can we used for integration, testing, and demonstrations. |
RIC |
RIC Platform | Thoralf Czichy | RIC Platform to support xAPPs with limited support for O1, A1, and E2 interfaces. |
OCU | O-RAN |
Centralized O-CU 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. |
ODUTBDHigh Layers | | Focus on initial L2 functional blocks based on seed code contributions. |
ODULOW | O-RAN Distributed Unit Low Layers | peng Lu | Focus on initial L1 |
/2 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 |
TBDTBDLusheng Ji | 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 componentsIn addition, it's a ultimate goal to establish a full end-to-end call flow using OSC components to carry out end-to-end integration tests and/or plug-and-play interoperability tests; but before that will try to perform pairwise tests based on release use cases as much as possible. Another target is to establish a CI/CD/CT pipeline to improve code stablity/quality and adopt modern Dev/Ops methodology. |
DOC | Documentation |
TBDweichen ni | Documentation on contributions and O-RAN SC contents. |
NONRTRIC | Non |
Realtime OAM | Operations and Maintenance | Martin Skorupski | Non-Realtime RIC focus on feature functionality of A1-interface, R1 interface, and support rApp (applications). More ... |
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). |
AIMLFW | AI/ML Framework | subhash kumar singh | Initial AI/ML workflow implementation for O-RAN environment. Need to interact with another project to accomplish a whole life cycle management of the AI model. |
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.