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

Administration

Please tag yourself using LF ID User Name.
Don't have an LF ID yet? Go here:
https://myprofile.lfx.linuxfoundation.org/.

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
  • Non-RT-RIC: John Keeney
    • demo preparation for PM File Collection to rApp...
    • demo service management exposer
    • SMO deployment on Minikube
    • SMO installation from it/deb
    • logging and metrics improvement 
  • SIM: Alex Stancu
    • implementing o1NotifyPnfRegistration on O1-Sim
  • OAM: Martin Skorupski
    • working on ietf-hardware integration into o1NotifyPnfRegistration 
    • updates on docker-compose deployment for latest ONAP and keycloak images including its config/overwirtes 
    • SDN-R support of VES-StndDefinded-NewAlarm and ClearedAlarm
  • O-DU:HariomGupta(HCL) / @Vidhu
    • nothing to report
  • AI/ML: @Sandeep J

00:12ONAP TSC Election@onap

https://lists.onap.org/g/onap-tsc/topic/93238808#8845

until 23:59 UTC, September 21, 2022


00:15SON/slicing Use caseN.K. Shankaranarayanan 
  • A1 policy artifacts are used for the use case.
  • Abstraction for RAN
  • ongoing implementation on RAN-SIM 
  • all in Kohn

00:203GPP copyright issue

Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN

Problem Statement might be not fully understood. 

Next step: Call with Magnus Buhrgard 

After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP

The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08

> Magnus wont give up (smile)


00:20O-RAN-F2F and OpenRAN summitJames Li also on the OpenRAN summit is an open-source (Oct26) session - call for participation 
00:25Q/A
None this week.
Have a good week (big grin)

END










Action items