| 9am PDT |  noon EDT | 16:00 UTC | 18:00 CEST | 21:30 IST 


ZOOMhttps://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424


Attendees

Informed

See also

Goals

  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC SMO
    • ONAP CCSDK/SDNC/SDN-R
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-06-16: John Keeney

2021-06-23: Martin Skorupski

2021-06-30: John Keeney 

2021-07-07: Martin Skorupski

00:05O-RAN-SCO-RAN-SC PTLs

Status reports:

00:20SMO deployment options

SMO deployment options

  • Please see presentation within 
00:30

Q/A



END






00:??Use Case

@all

OSC Proposed e2e integration use case: O-RU FH connection recovery

<bridge dropped recording stopped at this point. Most participants reconnected once bridge started again>

  • Topology ??: (contd)
    • John Keeney Lots of options for how this should be done properly in ONAP.
    • Swaminathan Seetharaman ONAP usecases already have some plans for this e.g. slicing, oof,  etc
    • Andy Mayer A model should be agreed in ONAP. Lots of previous discussions in ONAP - e.g. what goes in A&AI and CPS ... but that was a while ago.
    • Martin Skorupski SDNR has some topology model too - not standards based.
    • @Sven John Keeney Martin Skorupski Lots of issues with different topology models ... and most existing hierarchical models break down in a 5G/CloudRan environment
    • Lots of work ... Andy Mayer Martin Skorupski Can create a JIRA in ONAP MODCOM ...
    • ... but will keep it simple here for this use case.
  • @? Will other O1 usecases be effected? Martin Skorupski i No. O1 functions continue as before.
  • Martin Skorupski Please add feedback if any



Action items