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	Use Case realization records
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	John Keeney
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	N.K. Shankaranarayanan ,Swaminathan Seetharaman	https://wiki.onap.org/download/attachments/84653613/zoom_0.mp4?version=1&modificationDate=1592407459000&api=v2
REQ-440	E2E Network Slicing use case requirements for Honolulu release	Availability of O1 yang models Availability of O2 specification (stretch goal, needed beyond H-release) Collaboration on overall RAN Slicing concept, handling of FH and MH, Closed Loop scenarios, etc.	Alignment/collaboration needed with O-RAN SC Near-RT RIC project	Swaminathan Seetharaman, LIN MENG, Sandeep Shah	https://wiki.onap.org/download/attachments/93000405/202011Nv12UCR_zoom_0.mp4?version=1&modificationDate=1605196303000&api=v2
REQ-427	Configuration Persistence Service in R8	None, O-RAN dependency for H-release to be covered by REQ-429 and REQ-440	None	Toine Siebelink Benjamin Cheung	https://wiki.onap.org/download/attachments/84649072/zoom_0.mp4?version=1&modificationDate=1590611895000&api=v2
REQ-433	ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu)			@Marge Hillis, Damian Nowak

Space shortcuts