Versions Compared

Old Version 3

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version Current

changes.mady.by.user gasparini24

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note: Contact persons denote only ONAP contacts as of now. It has to be extended to include O-RAN/O-RAN SC contacts also.

JiraDescriptionO-RAN Dependency/CollaborationO-RAN SC Dependency/CollaborationContact PersonsUse Case realization records
REQ-457Extend ORAN A1 support - HonoluluNone, will use O-RAN A1-AP v2.0 specificationAlignment/collaboration needed with O-RAN SC Non-RT RIC project

John Keeney (Ericsson EST) 


REQ-429Use Case for ONAP-based SON for 5G networksAvailability of O1 yang modelsNone, could explore collaboration with O-RAN SC components for e2e demo

N.K. Shankaranarayanan ,Swaminathan Seetharaman

https://lf-onap.atlassian.net/wiki/download/attachments/16429831/zoom_0.mp4?version=1&modificationDate=1592407459000&api=v2
REQ-440E2E 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://lf-onap.atlassian.net/wiki/download/attachments/16450259/202011Nv12UCR_zoom_0.mp4?version=1&modificationDate=1605196303000&api=v2
REQ-427Configuration Persistence Service in R8None, O-RAN dependency for H-release to be covered by REQ-429 and REQ-440None

Toine Siebelink Benjamin Cheung

https://lf-onap.atlassian.net/wiki/download/attachments/16427063/zoom_0.mp4?version=1&modificationDate=1590611895000&api=v2
REQ-433ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu)

@Marge Hillis, damian.nowak