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:

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

OSC Project roundup:

News from OSC TOC call last week

NONRTRIC (John Keeney)

  • G release planning
    • Presented as OSC RSAC meeting today
      • Slides:
      • Recording will appear at RSAC Meetings
      • Proposal - as discussed here previously:
        • Continue Service Exposure work (R1-SEF)
        • Continue Data Management & Exposure work (R1-DME)
        • Progress rApp manager especially
          • rApp registration & discover & authorization
          • rApp LCM
          • Overlapping with service & data exposure/consumption
          • Will further identify overlap & extensions to ONAP "Automation Composition Manager (ACM)"
        • Continue A1 work
        • Use cases, Integration & other project housekeeping
    • Work on overlapping topics related to proposed AI/ML work (see TOC/RSAC discussions)
  • Delivering call-out capability in A1-Simualtor to support policy-specific or app-spec behavior
    • Will be use in ONAP - A1-Sim embedded in ONAP RANSim - used 5G SON Use case NONRTRIC-754 - Getting issue details... STATUS
      • REF ONAP SON Use case below

SIM (Alex Stancu)

  • G release planning (presented in RSAC)

OAM (Martin Skorupski)

  • G release planning (presented in RSAC)
  • Updating to latest version of Opendaylight.
    • Martin Skorupski working through some issues with Opendaylight team: e.g. NETCONF-845
    • ODL Sulphur requires an update to MountPointRegister

O-DU (Hariom Gupta Vidhu Shekhar Pandey)

  • No Update

OSC Integration / INT (James Li )

  • James Li No update - just back from vacation 

RSAC/SMO (David Kinsey)

  • Minutes & Meeting: RSAC Meetings
  • Calendar: https://lists.o-ran-sc.org/g/main/calendar
  • This Week:
    • G-Release planning & scope
      • This week:
        • Near-RT-RIC platform
        • SIM (see above)
        • OAM (see above)
        • NONRTRIC (see above)
    • Discussion on proposal for new project & work in current projects around ML/AI functions in OSC.
      • Some detail on G release plan/proposal
      • Likely vote in OSC TOC tomorrow to create project.

ONAP / OSC Copyright issues:

ONE Summit / LFN DTF: Proposal for OSC/ONAP/Others Cross-project/-community topics

Q/A

  • user-941adIs OSC taking ONAP as its SMO
    • John Keeney Martin Skorupski N.K. Shankaranarayananuser-941ad
      • OSC SMO Project Building some SMO functions, along with OAM functions in OAM, Non-RT-RIC functions in NONRTRIC project

      • An SMO can then be assembled for given use cases etc.
      • OSC it/dep repo contains several such integration environments/usecase/deployments - including one with lots of ONAP functions (along with functions from the OSC projects: OAM, SMO, SIM, O-DU, NONRTRIC)
      • Where a function already exists in ONAP - or other projects - it makes sense to reuse them to avoid community fragmentation & duplication