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 Project roundup:

News from OSC TOC call last week

NONRTRIC (John Keeney)

  • Release G completed before Christmas/New Year break.

  • Release H Planning continues:

    • (R1) Service Exposure & Management

      • CAPIF Aligned Service Registry
      • Secured/Sandbox execution environment
      • Controlled access & exposure of service to/from rApps

    • (R1) Data Management & Exposure

      • 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
        • 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)

  • Still working on OSC H Release Planning

OAM (Martin Skorupski)

  • Looking at OAM Specs from O-RAN Alliance & 3GPP REL 18
    • e.g. Updating VES stddefined support etc, new versions of SDNR etc. 

O-DU (Hariom Gupta Vidhu Shekhar Pandey)

  • No Update

OSC Integration / INT (James Li )

  • Plan to use XTesting integration tests with INF project (esp for O2)

RSAC/SMO (David Kinsey)

  • Ref: RSAC Meetings

  • Update from AIML project re Release H plans

    • Included discussion on overlap/alignment/integration opportunities with NONRTRIC, SMO, Near-RT-RIC, RICAPPs, OAM projects.

  • Update from O-DU HIgh project re Release H plans

  • Update from SMO Tacker project re Release H plans

  • OSC/ONAP 

    • Mentioned this meeting - Unfortunately David Kinsey cannot attend today - meeting clash.

  • Upcoming Open RAN workshop

AI/ML platform project ()

ONAP Use cases (N.K. Shankaranarayanan)

  • No time for an update this week

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

Discussion: ONAP TSC Would like to better formalize relations between ONAP & O-RAN SC, and ONAP & O-RAN Alliance

  • @00:13:00 in Recording
  • Pawel, Magnus Buhrgard, Bob, N.K. Shankaranarayanan 
  • Also trying to establish a snapshot of interactions currently
  • How to improve cooperation
  • Goal: Avoid fragmentation, improve synergy, avoid duplication, raise awareness
  • (Unfortunately .. (or fortunately) ONAP TSC & OSC TOC calls are at the same time)
  • Areas being considered in ONAP: Is there a need to streamline requirements gathering process & cadence, release processes & cadence, integrated platforms vs services, using licensed specs
    • Same considerations could be looked at in OSC too - to have a 2-way flow of awareness, requirements, software,
    • For example, there can be a very significant lag between a requirement becoming obvious in one project, and released software being available in the other ... often Many months.
      • Rule of thumb: A project should only use 'released' software from other communities
      • It would be better to have a much more flexible, continuous, faster cadence of requirements planning & interim or continuous software releases. (while also keeping the periodic Major Release time scales)
  • Would be good to have better cooperation between specification work & implementation (pre-spec & post-spec)
    • Note: Any project - not just OSC - including ONAP - can consume/feedback to O-RAN Alliance on a equal basis
      • Would be good to better understand if/what 'special relationship' between OSC & O-RAN Alliance. No blocker exists to other projects.
    • O-RAN Licensing remains an issue for all opensource projects - including ONAP & OSC
  • Some topics where there is a clear interaction ONAP/OSC - and alignment would be beneficial:
    • release cadence
    • non-rt-ric / smo
    • rapps
    • oam
    • orchestration and cloud
    • simulator (O-CU, O-DU, O-RU)
    • use cases alignment 
    • integration
    • license issues

  • Potential actions

Questions / Comments / AOB:

  • Follow up Note on opensource/specification alignment: :
    • Magnus Buhrgard, Martin Skorupski, John Keeney  
      • Would be good to have a separate discussion about how opensource and specification activities could benefit each other better if there was better interactions.
      • O-RAN Alliance seems like a particularly good candidate to examine this
      • Lets discuss this further in another call.
  • No more time this week


Meeting ends