16:00 UTC, 09:00 PST, 12:00 EST,  17:00 BST, 18:00 CEST, 19:00 EEST, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)


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

Calendars:

Summer Daylight Savings time eventually stabilizes to:
9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)

Winter (non-DST) time eventually stabilizes to:
9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

(During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)


Table of Contents

Attendees

Informed

LF Antitrust

See also / Co-Located

Goals

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

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

Please follow the calendar

00:02O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
00:25SON/slicing Use caseN.K. Shankaranarayanan 

A1 introduction to ONAP use cases

Update 2022-06-01:

  • both use cases using control loops
  • SON PTL, Policy PTL were included in the discussion
  • adding A1 actions to the use case
  • use case oriented RAN-SIM
    • adding A1 termination to RAN-SIM
  • parallel flows in ONAP for A1 and O1 messages
  • A1/O1 separation within SDN-R (SDNC)
  • Question:
    • Does A1/E2 trigger a "change" in the E2 nodes?
    • How is the sync mechanisms to SMO for configuration changes?

Update 2022-06-08:

  • go for SON use case
  • technical discussion on slicing 
  • policy/a1/non-rt-ric team are working together
00:00Q/A
None this week.
Have a good week (big grin)
END



3GPP copyright issue
  • Struggling with 3GPP copyright / reuse.
  • status
    • LS (draft) from ONAP to 3GPP - ask for approval by ONAP TSC
    • init positive response for some part (use terminology)
    • open: usage of entire data models

2022-04-06:

  • How to you yang/OAS3 in open-source?
    • no modification (use case specific enhancements are done by "augmentation" in separate schemas 
    • integrating them into code repos and docker images
    • during runtime - exposing the schemas to the clients. 
    • auto-generation of code from schemas
  • What is meant by "redistribution"?
  • How to use other 3GPP documents next to 3GPP schemas?

Martin Skorupski : check latest email from Magnus Buhrgard and response 



Action items