5G RAN-related use cases in Honolulu
Note: Contact persons denote only ONAP contacts as of now. It has to be extended to include O-RAN/O-RAN SC contacts also.
Jira | Description | O-RAN Dependency/Collaboration | O-RAN SC Dependency/Collaboration | Contact Persons |
---|---|---|---|---|
REQ-457 | Extend ORAN A1 support - Honolulu | None, will use O-RAN A1-AP v2.0 specification | Alignment/collaboration needed with O-RAN SC Non-RT RIC project | |
REQ-429 | Use Case for ONAP-based SON for 5G networks | Availability of O1 yang models | None, could explore collaboration with O-RAN SC components for e2e demo | |
REQ-440 | E2E Network Slicing use case requirements for Honolulu release |
| Alignment/collaboration needed with O-RAN SC Near-RT RIC project | |
REQ-427 | Configuration Persistence Service in R8 | None, O-RAN dependency for H-release to be covered by REQ-429 and REQ-440 | None | |
REQ-433 | ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu) | @Marge Hillis, Damian Nowak |