Time & Location:

Meeting Detail: Times & Joining Info

Tuesdays at 14:00 UTC in Summer (DST), 15:00 UTC in Winter

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

  • Ensure you are signed into your Zoom account to join.
  • Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • 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 (Q2, Q3) eventually stabilizes to:
      7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST
    • Winter (non-DST) time (Q4, Q1) eventually stabilizes to:
      7am PST | 10am EST | 15:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 20:30 IST | 23:00 CST (Thurs) | 00: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 Project roundup:

News from OSC TOC call last week

  • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
    • Last week's TOC (Thursday):
      • Update from several projects, including OAM, SIM,
    • This week's TOC (in 2 days):
      • New meeting format with updates from relevant PTL etc
        • week 0: RSAC, Integration I (cross-project testing related), Infrastructure

        • Week 1 : RIC, RICAPP, AIMLFW

        • Week 2: NONRTRIC, SMO, OAM, SIM

        • Week 3: Integration II (lab related), O-DU-HIGH, O-DU-LOW

        • This week: 
          •    RICAPP, O-DU-HIGH, O-DU-LOW, INT
      • Planned update from O-RAN MVPC co-chair

NONRTRIC (John Keeney)

  • Demo Last week: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode" Aravindhan Ayyanathan
  • Demo last week: "CAPIF for Service Registration & Service Discovery" Yennifer Chacon
  • TOC Update last week
  • Focus on documentation, final testing & release tasks for ONAP London & OSC H
  • Some team member updates in coming weeks.
  • Making progress with stating a new 'rApp manager' function. Still very early, but will one of the main activities in new OSC release.
  • Previous weeks:
    • Consolidating PM data exposure in new repo for RAN PM functions
    • (R1) Service Exposure & Management
      • CAPIF Aligned Service Registry
      • Secured/Sandbox execution environment
      • Controlled access & exposure of service to/from rApps

    • (R1) Data Management & Exposure

      • File-based PM data → InfluxDB
      • Previous focus on PM data - but will extend to other use cases too
      • Aim to work with AIML project for Training (and Inference ?) data access

    • rApp Management

      • Built on ONAP “Automation Composition” model & platform to implement rApp use cases
        • Inference Services in rApps
          • Added a 'KServe Participant'
        • rApp-specific extensions needed
      • Packaging, Onboarding & Orchestration of rApps
        • rApp-specific packaging & Onboarding
          • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
        • (rApps with & without µService)
      • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

    • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

      • A1 Spec evolution
      • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
      • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
    • Sample use cases (rApps)
      • Requirements Drivers for rApp/R1 development
      • High degree of cross-project integration activity

    • Testing, Maintenance & Housekeeping

      • Function Test & Integration Test environment,
      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

SIM (Alex Stancu)

OAM (Martin Skorupski)

  • Release preparations
  • Discussions ongoing about PM streaming using websockets & protobuf - will align with 3GPP O1 spec.
  • Debating with WG10 about fixing some openapi/yaml inconsistencies in 3GPP specs.

O-DU Vidhu Shekhar Pandey)

  • No update this week

OSC Integration / INT (James Li )

  • No update this week

SMO (Seshu Kumar Mudiganti )

RSAC (David Kinsey Rittwik Jana )

AI/ML platform project (Joseph Thaliath)

ONAP/OSC Usecases (N.K. Shankaranarayanan)

  • See below

ONAP/OSC Alignment Usecase proposal for ONAP Montreal (N.K. Shankaranarayanan)

  • As discussed in previous weeks
  • Aiming for presentation to ONAP ArchCom: 13 June
  • Unclear yet what the outputs will be ...
    • Even just articulating how functions should work together, and reflecting existing/resourced work as in-scope for this activity.
    • Little new/usecase-specific development expected
  • ONAP M1: 22 June

Questions / Comments / AOB:


Meeting ends 25min