...
| Project Key | Project Name | PTL | Description |
|---|---|---|---|
| RICNRT | Non real time RIC | TBD | 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. |
| RICAPP | RIC Applications | Matti Hiltunen | This includes open source sample xAPPs and platform applications that can we used for integration, testing, and demonstrations. |
| RIC | RIC Platform | Thoralf Czichy | Initial RIC Platform to support xAPPs with limited support for O1, A1, and E2 interfaces. |
| OCU | O-RAN Centralized Unit | TBD | The O-CU should target an initial software deliverable with limited functionality. Focus on aa basic E2 interface to enable initial integration testing between RIC and OCU. |
| ODU | O-RAN Distributed Unit | TBD | 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 Administration Management Apparatus | TBD | Initial Dashboard for monitoring and demonstration of contributions. |
| SIM | Simulations | TBD | Initial simulators used for testing O-RAN NF interfaces. |
| INF | Infrastructure | TBD | Initial building blocks for infrastructure to run O-RAN NF components. |
| INT | Integration and Testing | Lusheng 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 components. |
| DOC | Documentation | TBD | Documentation on contributions and O-RAN SC contents. |
...