Versions Compared

Key

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

Date

 | 9am PST |  noon EST | 17:00 UTC | 18:00 CET | 21:30 IST 

Zoomhttps://zoom.us/j/436210993?pwd=SjI2V3hIVW42SmpCV3l0aEFGV2RVQT09

Attendees


Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-01-27: John Keeney (O-RAN vf2f)

2021-02-03: Martin Skorupski

2021-02-20: John Keeney

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

Status reports:


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





Other

From last week

Other



END






Action items

  •