Time & Location:

Meeting Detail: Times & Joining Info

Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !

Zoom Bridge :  https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

  • Ensure you are signed into your Zoom account to join.
  • Meeting ID: 890 6970 8424.
  • See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
  • NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. 
    • 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
  • Meeting ID: 890 6970 8424
  • You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Dial in: (Local numbers)
    • +1 646 558 8656 US (New York)
    • +49 30 5679 5800 Germany
    • +49 69 3807 9883 Germany
    • +353 1 240 8941 Ireland
    • +46 8 4468 2488 Sweden
    • +46 8 5016 3827 Sweden
    • +358 3 4109 2129 Finland
    • +358 9 7252 2471 Finland

Please checkout the calendars:

Anti-Trust Notice

Date

Attendees

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

Notes:

  • Low attendance this week ? Anyone know why? 
  • John Keeney can't attend next week - Vacation

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

OSC Project roundup:

News from OSC TOC call this week

NONRTRIC (John Keeney)

  • As per last week:
    • Working on e2e PM data - making it available over pre-R1 DME (OSC NONRTRIC) Information Coordination Service)
      • Making good progress - File-based almost working, and lots of parts of event-based working. Lots of integration.
    • Working on PoC Service Exposure - with a view towards R1 (3GPP CAPIF TS 23.222)
      • Will update more as this matures - still very early - hopefully a demo in coming weeks
    • Working on getting Repos set up - e.g. lots of Jenkins jobs.
      • Slow, but making good progress. 
      • Thanks to the LF team!

SIM (Alex Stancu)

  • No major update

OAM (Martin Skorupski)

  • No major update ... working away on dev tasks - Ref OAM JIRAs

O-DU (Hariom Gupta Vidhu Shekhar Pandey)

RSAC/SMO (David Kinsey)

  • No update this week

OSC Integration / INT (James Li )

SMO Integration Charts (Sébastien Determe, Christophe Closset)

  • No update this week.

ONAP Use Cases Update  (N.K. Shankaranarayanan)

ONAP/OSC 3GPP Copyright issues (N.K. Shankaranarayanan, Magnus Buhrgard )

  • ONAP TSC agreed to submit LS to 3GPP - awaiting formal response.
  • Informal feedback from 3GPP is that we should list how & where 3GPP specs are being used/needed in ONAP.
    • Yang models used in a few places, but not modified.
    • Obviously try to avoid re-distributing or re-publishing spec material verbatim in an extractable way
      • But what about re-generation of a spec document? e.g. query an interface for its model?
      • What about code generated from spec material (e.g. openapi, yang, asn1)
      • What about modified specs?

Update from ONAP Release status etc (David McBride)

  • ONAP Jakarta M4 approved last week
    • 1 week slip in Release date
    • Release candidate preparation ongoing
  • ONAP Kohn process have started: "M0 Kick off 7 Apr 2022 (smile))
  • Discussions ongoing with ONAP-ODL release cadence / alignment in K release.

Q/A

  • John Keeney What is the status of the VES-based PM Measurement reporting?
    • Any update on when the discussions might kick off in O-RAN Alliance ... we may be getting a bit far ahead in implementing support for this before it is agreed in O-RAN?
    • How much / any of this is proposed for 3GPP?
    • Need to be careful to differentiate Trace/Streaming from event-based PM reporting.
    • David Kinsey is main driver on CRs for this ... Will ask for a status update.