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)

  • Work ongoing - as per last week:
    • RAN PM functions - tidying up & re-releasing in maintenance release.
    • Making good progress on rApp manager. More in coming weeks
    • 3PP dependency updates & addressing vulnerability
    • 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 expressivity of docs etc.
    • Issue with test framwwork
      • underscore in URI hostnames - introduced by docker-compose (v1)
    • Some changes in A1-Mediator in near-RT-RIC plt in H-Release.
      • Further investigation needed re effects on A1-PMS/ICS & A1-SIM

SIM (Alex Stancu)

OAM (Martin Skorupski)

  • Looking at Netconf "Yang Schema Mount" for O-DU/O-RU relationship (WG5 yang models)
    • making some progress ... more to come
  • Request (from RSAC) to make proposal for RAN PM streaming
  • Working with team in T-Systems to update ONAP VES collector to work  with native kafka.

O-DU Vidhu Shekhar Pandey)

  • No update this week

OSC Integration / INT (James Li )

  • Near-RT-RIC team today showed a demo of osc near-rtr-ric with an updated version of OAI DU/CU
    • To work with KPIMon xApp.
    • Hope to be able to reuse this work in ongoing OAI collaboration

SMO (Seshu Kumar Mudiganti )

RSAC (David Kinsey Rittwik Jana )

  • No update this week
  • Minutes: RSAC Meetings 
  • Good discussion about I-Release plans, & how to report progress according to new streams/usecases. 
    • More to follow in coming RSAC & TOC calls.
    • Some concern about scope ambition vs resourcing ...
      • Maybe discuss at SMO call tomorrow?

AI/ML platform project (Joseph Thaliath)

SMO end-to-end & SMO in Opensource (N.K. Shankaranarayanan )

  • No update this week

ONAP Update (N.K. Shankaranarayanan Seshu Kumar Mudiganti )

  • No update this week

ONAP/OSC Usecases (N.K. Shankaranarayanan)

  • No update this week

PM Data Streaming (Martin Skorupski  & All)

  • (Recording timestamp @ 10:30)

  • PM Streaming 

  • O-RAN OAM spec refers to 3GPP specs to use websocket for transport

  • Data serialisation format options presented by 3GPP:  Ref sect 11.5 TS 28.532

  • Suggestion to do 3gpp-XML→yang→GPB  ...
  • Refer to "establishStreamingConnection" operation, table 11.5.1.1.2 "streamInfoList" input parameter where PM stream job is defined
  • But how will the SMO terminate streams, parse, and distribute the data?
    • Proposal
      • SMO needs a Websocket stream terminator (e.g. to: S3 bucket, or Kafka?)
      • SMO needs a GPB data parser (to: XML, or JSON?)
      • <a big gap - for further study>
        • Alot depends on the data characteristics & scalability concerns
      • Then re-use NONRTRIC RAN PM functions so rApps can subscribe to filtered PM data in JSON format in Kafka and/or InfluxDB
    • Need to read-up some more and come back to this in future weeks.
    • Need to clearly demonstrate if there is a benefit beyond file-based PM and/or streamed trace data.
      • e.g. shorter reporting period (ROP) file-based?
    • Very significant scalability challenges as reporting period decreases, network function increases, job count per function increases.

Questions / Comments / AOB:

  • None this week.


Meeting ends 51min