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)


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
    • both (maybe) for O-RAN f2f 20thOct 
  • SIM: Alex Stancu
    • reviewing o1NotifyPnfRegistration
    • starting implementing it on O1-Sim
    • meeting with O-RAN-SC SMO (aarna) → contribution to O1-SIM in O-RAN-SC
  • OAM: Martin Skorupski
    • defining the data model for o1NotifyPnfRegistration 
      • response from WG4 → add dependency to ietf-hardware
        • idea: addressing ietf and 3gpp hardware models by augmentation and separate yangs
    • Analysing kafka-bridge api and its usage based on
      • first out come → sending via kafka-bridge works fine but not understood issues when reading topics via kafka-bridge → SDN-R topic listener may better use kafka-api?!?!
  • O-DU:HariomGupta(HCL) / @Vidhu
    • nothing to report
  • AI/ML: @Sandeep J
    • Tue 12 UTC → 2 pm CEST - first meeting yesterday: link
    • areas to start with seed code
    • project setup ongoing wiki/jira/...
    • candidate for SMO Components → WG1?
  • RSAC/SMO: David Kinsey 
    • AI/ML project report from yesterdays first meeting
    • f2f preparation
    • sprint-demo-preparation
  • INT: James Li(CMTI)
    • Sep21 for demo the X-Testing on RSAC meeting
      • ricplt health use case

00:20SMO packageGervais-Martial Ngueko 

ONE acceptance for SMO package

  • O-RAN-SC ToC should be now aware of the "SMO package" at ONE

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


00:30SCCL agreement

SCCL agreement - review process

  • contribution to SCP - should have that licence 
  • is there a conflict between SCCL and O-RAN-SC license 


--

different topic - O-RAN Alliance and ETSI (including 3GPP) license is more complex.


00:30Q/A
None this week.
Have a good week (big grin)

END



00:00SON/slicing Use caseN.K. Shankaranarayanan 

No update this week.


Last week:

  • work is progressing on using A1-Sim as the A1-Termination in RAN-Sim.
  • Discussions are ongoing on the Kafka message format from the A1-Termination to the RAN App in RAN-Sim.










Action items