Skip to end of metadata
Go to start of metadata

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)

Meeting ID: 890 6970 8424


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



Please tag yourself using LF ID User Name.
Don't have an LF ID yet? Go here:

LF Antitrust

See also / Co-Located


  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC O-DU
    • LFN (wink)


Discussion items


Next meetings: 

Please follow the calendar


  • 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 
  • RSAC/SMO: David Kinsey 
    • from yesterday - f2f - lab status - connection from Taiwan to Bedminster (smile)
    • draft agenda by Jinri - o-ran-sc-discuss
  • INT: James Li(CMTI)
    • work will continue
    • Ric-Platform and Ric-App - check wiki including workflow
    • test-case implementation - x testing
    • Q: can existing test cases be "integrated" by just pointing to existing cases?
      • A: bash, robot, python and heml, can be adopted by the "3 step process" → so yes (smile)

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


  • A1 artifacts from O-RAN-SC are used
  • Schema for the use case needs to be integrated into A1-Termination-Sim 
    • in real world - Near-RT-RIC policy-types are known by the Near-RT-RIC instance 


Please summit your topics (smile)

None this week.
Have a good week (big grin)


00:303GPP 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)

Action items