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 target next week ...
    • demo service management exposure (SME) → demo later

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


  • integration with RAN-SIM complete and testing in progress


  • preparation for DTF


Demo service management exposure (SME)

  • "Architecture & prototyping SMO Service Exposure & Discovery: Using Keycloak & JWTs to expose & secure services used by rApps"
  • Abstract:
    • "We moving towards an open disaggregated service-oriented SMO, where multi-vendor rApps can easily use its services, and where some parts of the SMO may also be provided by 3rd parties. It is therefore vital that we can control how services are exposed and accessed - whether those services are provided by the SMO platform or by   rApps. This is a key requirement for the new R1 interface between SMO services and rApps. 

      In this talk/demo we explain & show service exposure for rApps to support service discovery and exposure. We demonstrate a secured service- and rApp-execution environment,  we show how platform services and rApp services are secured, registered, discovered and used in a secure manner manner - protected by enforcing access control enabled by access tokens."

  • Slides:
  • Recording (Ref Meeting Recording15:25-1:10:00)
  • (pre) R1 interfacing
  • multi-vendor environment → security
  • selected and controlled service exposure

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