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

Date

Attendees

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

Contents


Recording

Notes:

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

OSC Project roundup:

News from OSC TOC call this week

  • https://wiki.o-ran-sc.org/display/TOC
  • M3 deadline extended .. 3 weeks? Perhaps combine M3 & M4?
  • Processes to support SCCL license is still ongoing & under discussion
  • For E Release Slicing Assurance use case ... Can we use 3GPP yang models for O-DU OAM?
    • Unclear
    • Still have backup "Plan B" to reuse/extend "Hello World" model from D release

NONRTRIC (John Keeney)

  • No update this week

SIM (Alex Stancu)

  • TLS call home now working in SIM (ODL Silicon+ )
    • (Bug? SSH Netconf callback connections drop after 10 minutes if no messages)

OAM (Martin Skorupski)

  • Creating "Plan B" yang model for slicing use case (see above)
  • Working on WG10 CR for PM streaming (+ N.K. Shankaranarayanan David Kinsey )
    • Timelines too tight for November train ... Will continue in next train

O-DU (HariomGupta(HCL))

Using 3GPP models 

  • Discussion: Martin Skorupski Timo Perala N.K. Shankaranarayanan John Keeney
    • Still a lack of clarity about how to use 3GPP licensed models
    • Approach until now has been to stay model-driven (so don't reproduce any existing specs/models)
      • But this cannot continue esp. in OSC when O1 builds so much on 3GPP specs and functions that are model-specific are now in development.
    • Is problem for ONAP & OSC the same?
      • Yes!
      • Perhaps we could escalate to LF?

ONAP SMO deployment options

  • Christophe: Working with David Johnson to reuse ONAP/OSC SMO deployment/package in POWDER lab as a profile
    • Working setup now. Tweaking configurations to reduce footprint size a little for smaller deployments
  • Next step - aiming for meaningful automated end-to-end tests

Q&A

  • Pawan Kumar, Janak Kulkarni: New to OSC/ONAP integration & interested in getting up to speed   (Welcome!!! (big grin))
    • How's progress with rApps & R1?
      • John Keeney Neither are very well defined yet ... but in OSC & ONAP we are trying to guess at some of the parts that will eventually be useful for supporting R1 & rApps ...
        • App LCM
        • uService LCM & management (for rApps with microservices)
        • ONAP Tosc-defined Control Loop evolution (for rApps with multiple constituent parts including non-microservice parts, e.g. policies, workflows, configurations, templates, blueprints, etc)
        • ONAP SMO services - which may become/inform R1 services (e.g. CPS, Data collection, File collection, VES termination, Topology & inventory, Orchestration etc)
        • Service exposure & discovery & authorization & access control (which will likely be useful for R1 - service independent)
        • App sandboxing & controlling App <-> SMO interactions (which will likely be useful for R1 enforcement)
        • etc ...
    • Attempting to get ONAP & NonRTRIC & nearRTRIC functions running