Time & Location:

Meeting Detail: Times & Joining Info

Wednesdays at 16:00 UTC in Summer, 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:

Important Note about Daylight Savings Time

Important: Daylight Savings Time

  • We are now back to a stable timeslot for approx 6 months.
    • 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)  

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

NONRTRIC (John Keeney)

  • Trying to assemble options for demos.
  • Continuing as per last week : No specific update
    • Alot of work in JDK 17 & Springboot 3 updates
    • 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)

  • Working on Std-Defined VES Message examples for CM, FM, PM (17 different samples)
    • VES collector code updated to pull & inject YAML models automatically
      • Previously netconf only - now also supports http/ves notifications
    • Dockerfile with scripts
  • Investigating WG4 OFHM v11 now has VES std defined models → Netoconf notification
    • 27 notifications defined.
    • Working to see how to integrate them

O-DU Vidhu Shekhar Pandey)

  • Not many recent contribution for O-DU O1
    • Some updates needed?
    • Need to check std-defined PM VES messages are still OK (Based on OSC schema, no 3GPP model for VES-based PM available?)
      • PM over VES still not supported by 3GPP - only use websocket streaming instead

OSC Integration / INT (James Li )

RSAC/SMO (David Kinsey)

AI/ML platform project (Joseph Thaliath)

Discussion on how to set up Bulk-PM subscriptions on the RAN functions → rApps/DME

  • Overlap with AI/ML data access & NONRTRIC DME & OAM observability
  • Many RAN functions have restrictions on the number (1?) of PM Jobs/subscriptions (created over CM) on the node.
    • Need to combine subscriptions in overlapping 'jobs' on the nodes.
  • Ref old work in in ONAP about PM job management
  • Currently no relation between DME subscription set up & PM job management in NF. Assume PM delivery already initiated.
    • In O-RAN Alliance it is currently unclear if Non-RT-RIC DME, or OAM PM functions, or rApp via OAM CM functions, or some other functions will be responsible for mapping DME requests to PM jobs. 
    • Lots off potential for implementation-specific optimizations.

ONAP Use cases (N.K. Shankaranarayanan)

ONAP / OSC / O-RAN Alliance: Cooperation & Alignment

Questions / Comments / AOB:

  • None


Meeting ends 53min