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)


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

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

John Keeney

Next meetings: 

Please follow the calendar


00:05O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
  • Non-RT-RIC: John Keeney
    • H-Release planning
      • data management exposure
        • data type filtering
      • service management exposure
        • auth
        • rApp management
      • rsac inputs
      • interfacing with ai/ml project artifacts
      • rApp package and its definition in O-RAN Alliance
  • OAM: Martin Skorupski
    • updates according O-RAN OAM-Interface Spec
    • Working on updating stndDefined VES messages with latest artifacts from 3GPP REL-18
  • O-DU:HariomGupta(HCL) / @Vidhu
    • No update this week
  • AI/ML: @Sandeep J
    • No update this week
  • RSAC/SMO: David Kinsey 
    • AI/ML project - and its plan for H and interfacing with other O-RAN-SC projects (Non-RT-Ric)
  • INT: James Li(CMTI)
    • INF project - O2 work and usage of INT artifacts
    • xTesting

00:13ONAP TSC / O-RAN-SC ToC ....Paweł Pawlak 

ONAP TSC discussed in 2022-12 that we shall synch with you and John in terms of your recent activities around ONAP/O-RAN-SC/SMO.

Do you think we could have a short chat at the next Wednesday’s meeting (6 PM CET) you run?


Problem statement and objectives

  • formalize interaction between ONAP and O-RAN-SC
  • prio activities in ONAP
  • O-RAN Alliance interactions
  • avoid fragmentation 
    • needs awareness of tasks and use cases
    • and finally alignment of tasks, use cases and time lines


1 - Releases and requirements: 

  • cadence between ONAP and OSC
  • they have a peer relationship
  • both upstream and downstream.
  • streamline release process
    • sequence of implementation (may) led to "delays" in ONAP and O-RAN-SC
  • improvement of req process


2. Relationships: LFN/LF, OSC/O-RAN, OSC/ONAP/O-RAN

- OSC does not have special relationship with O-RAN Alliance

- ONAP and OSC have same relationship with O-RAN Alliance (license issues to use specs from O-RAN Alliance)

  • LFN projects - O-RAN-SC is not part
    • O-RAN Alliance and O-RAN-SC relationship - no specific 
      • issue of licence
  • input from dev to specs


3.  List specific examples of areas of interaction and issues involved:

  • release cadence
  • non-rt-ric
  • rapps
  • oam
  • orchestration and cloud
  • simulator (cu,du,ru)
  • use cases alignment 
  • integration
  • license issues


potential actions

  • bring together ONAP REQ and O-RAN-SC RSAC - just a "hello"
  • bring together ONAP TSC and O-RAN-SC ToC
  • explanation of the diff between O-RAN Alliance and O-RAN-SC

00:45SON/slicing Use caseN.K. Shankaranarayanan 
Planning for ONAP London

00:00Q/A




END


00:003GPP copyright issue

N.K. Shankaranarayanan 

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