Martin Skorupski

Next meetings: 

2021-04-21: John Keeney

2021-04-28: Martin Skorupski

2021-05-05: John Keeney

2021-05-12: Martin Skorupski 

Status reports:

• Non-RT-RIC: John Keeney 
• SIM: Alex Stancu  
• OAM: Martin Skorupsk
  • looking int VES stndDefined based on DMaaP 
  • late changes of API - but all good
  • Request for a NF-OAM-ADAPTER 

https://wiki.lfnetworking.org/display/LN/5G+Super+Blueprint+Timeline?preview=/53608675/53608679/5G%20+%20Slicing%20+%20O-RAN%20SC%20+%20MEC%20.png

Martin Skorupskimy personal understanding 2021-04-04:

• O-RAN-SC → RAN
• Magma → Core
• ONAP (including O-RAN-SC Non-RT-RIC) → SMO

Specs from 3GPP (core, N1, N2, N3, E1, F1, X?) and O-RAN (A1, O1(based on 3GPP), O2, OpenFrontaul, E2)

@all: Please correct, in case of my misinterpretations. 

Swaminathan Seetharaman

SMO functionality and alignment between ONAP and O-RAN SC

• Swami, John and Martin: slide set was presented 
• There was a meeting between ONAP TSC and O-RAN-SC ToC - including LFN
• 

Some thoughts: https://www.lfnetworking.org/5g-super-blueprint/ 

Q/A

for agenda next week

Claudio David Gasparinisome insides from CPS - thanks!

@all

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

• REF/Background:
  • (OAM) Closed loop use case
  • (RSAC) Meeting 14 Jan:
    • Slides: https://wiki.o-ran-sc.org/download/attachments/1179971/RU_failure_recovery_use_case.pptx?version=1&modificationDate=1610637325824&api=v2
    • Recording: https://zoom.us/rec/share/mKYOGkB3mgpvIo2Hx1eY5Oifyw9qV9NQd7NiEj-FxQKP0kUpWOc7yvMO_LLPhA_M.lmx2LCh7-QwDHAFi
• Martin Skorupski provided intro
  • Alarm when fronthaul connection dies (O-DU - O-RU) (VES to SMO)
• John Keeney If there is a failure both O-DU & O-RU will try reconnect anyway - without this loop? Martin Skorupski Yes.
• @? How does SMO connect to O-RU?
  • Martin Skorupski This is a mix of different deployment options (hierarchical vs hybrid, O1 vs M-Plane). Main issue is agreeing models & terminology.
• John Keeney Seems this use case is not real-world useful, especially since recovery will happen automatically anyway, & mix of standards ...
• Martin Skorupski John Keeney Using this use case as longer term motivator for SMO/NONRTRIC/rApp development - independent of usecase
• Topology ??:
  • May need a topology service for this use case - John Keeney Will use a simple file/hardcoded for initial versions of this use case.
  • Paweł Pawlak Andy Mayer Topology in A&AI, CPS ? John Keeney No - not initially. Plan to  keep it simple for this release.

<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