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

NONRTRIC (John Keeney)

  • Mostly same as last week:
    • Updating sonar scans and related updates to improve results: making good progress
    • Making good progress on rApp manager.

    • OpenAPI-first in A1-PMS & ICS

      • Change from code→openapi→docs to openapi → code-stubs & docs

      • To better align with R1 specs as they mature

      • To improve expressiveness of docs etc.

      • Working now - tested functional equivalence achieved - merging this week. Then more work to follow.
    • Some changes in A1-Mediator in near-RT-RIC plt in H-Release.
      • Meeting planned with Near-RT-RIC team tomorrow.
      • Further investigation needed re effects on A1-PMS/ICS & A1-SIM
      • Looks like OSC_v2.1.0. A1-AP (P) profile will b deprecated
        • Will phase out support A1-SIM and A1-PMS in coming releases, when A1-Mediator moves to spec version of A1-AP
      • Need to verify current implementation are fully spec compliant
      • Working on Pairwise test - will be ready as A1-Mediator implementation continues (few weeks)
        • Received info on how to start A1-Mediator in standalone mode - easier to test.

SIM (Alex Stancu)

  • Looking at TIM dataset
    • Parsing & now a bit easier to use.
    • Very large. Looking for somewhere to share it (Nexus?)

OAM (Martin Skorupski)

OSC Integration / INT (James Li)

  • No other update

O-DU Vidhu Shekhar Pandey)

  • No update this week

SMO (Seshu Kumar Mudiganti)

RSAC (David Kinsey Rittwik Jana)

AI/ML platform project (Joseph Thaliath)

PM Streaming (Martin Skorupski)

ONAP Update (N.K. Shankaranarayanan)

  • No update this week

ONAP/OSC Usecases (N.K. Shankaranarayanan)

  • Details of using CPS is still ongoing
    • Quite complex ...
      • How to interact/integrate SDNR & CPS, e.g. mounted netconf device models, CM notifications
      • VES vs Netconf id mapping is very tricky & must be maintained.
        • Decision: CM handle in CPS is same as Netconf server ID in RANSIM & same of NF ID & same as sourceID in VES message.
    • Also relevant for O-RAN SMO sequence flow work (N.K. Shankaranarayanan)

SMO Deployment

  • Ref: RSAC meeting 20/Sep - Slides & video @ RSAC Meetings 
  • Still very unclear how it/dep deployment works & if it is maintained.
  • Work from Taiwan Lab should / could be reusable hopefully.
  • Meeting with ONAP OOM team tomorrow to iron out technicalities of deploying ONAP functions
  • There have been updates since OAM function version in it/dep / ONAP worked
    • e.g. VES collector needs to be built (3gpp)
    • e.g. OAM gateway (sdnc, keycloak, dmaap, ves collector are now behind gateway for ease of addressing)
  • SIM / topology ... still pretty similar - but very use case specific
  • NONRTRIC ... Charts in it-dep/nontric diretory are up to date. charts/configurations in it-dep/smo-intall are a little dated, but not too bad.
  • Main question is where does platform stop & use case start .. Alot of the charts/deployment is use case specific.

Disaggregated SMO Flows (N.K. Shankaranarayanan)

 OAI / OSC / OSFG (Irfan Ghauri)

Questions / Comments / AOB:

  • None this week.


Meeting ends 40min