14:00 UTC | 7am PDT | 10am EDT | 15:00 WEST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST |  23:00 JST |

Meeting ID: 890 6970 8424


(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:
Please remove yourself from this list if you don't want to be tagged for future meetings

LF Antitrust

See also / Co-Located


  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC O-DU
    • O-RAN-SC SIM
    • O-RAN-SC INT
    • O-RAN-SC AI/ML
    • ONAP Usecases
    • ONAP Req & ONAP TSC committees
    • LFN (wink)


Discussion items

  • Meeting 04 July 2023 (Today) - Small attendance expected - Public Holiday in US.
  • Meeting 27 June 2023 cancelled (Key attendees unavailable)
  • Meeting 20 June 2023 cancelled (O-RAN F2F OSAKA)

Next meetings: 

  • O-RAN-SC ToC

Q/AVarada Varad
Varadarajan Srinivasan (Samsung)

What is the motivation of CAPIF in NONRTRIC?

Meeting ends

00:ONAP SON/slicing Use case
    • Presented plan for proposal
      • Slides : Draft / WIP

Issue when deployment with OOM:

  • oom - strimzi > 
    • one option to reinstall strimzi 

Preparation for the next release

  • enhancements of RAN SIM

To be on the agenda for June 13!

on the Agenda at O-RAN f2f on WED.

00:00ONAP/O-RAN-SC Cooperation/Alignment

Was topic at ONAP TSC

  • more interest
  • use case should drive the discussions
  • end-to-end use case requires rApp - thoughts?
    • ACM control loop

00:003GPP 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