14:00 UTC | 7am PDT | 10am EDT | 15:00 WEST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST |  23:00 JST |


ZOOMhttps://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424

Calendars:

(During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)

Table of Contents

Attendees

Administration

LF Antitrust

See also / Co-Located

Goals

  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC O-DU
    • O-RAN-SC SIM
    • O-RAN-SC INT
    • O-RAN-SC AI/ML
    • ONAP CCSDK/SDNC/SDN-R
    • ONAP Usecases
    • ONAP Req & ONAP TSC committees
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

Please follow the calendar

  • 2023-10-10 John Keeney Martin OoO, AlexS OoO
  • 2023-10-17 O-RAN F2F & Martin OoO - Cancel meeting - O-RAN F2F

00:05O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
    • As per 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.

        • Almost all working now - no functional change visible, but lots of work!
        • back to function (smile)
      • 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.
      • Support of PM Streaming flows (thanks!!!)
  • SIM: Alex Stancu
    • continuing on ... no major update
    • Hoping to get back to PM work ASAP
    • Looking at TIM dataset
      • Parsing & now a bit easier to use.
      • Very large. Looking for somewhere to share it (Nexus?)
  • OAM: Martin Skorupski
  • O-DU: @Vidhu
    • No update this week
  • AI/ML: @Joseph Thaliath

00:30

PM Event Streaming

No update this week


PM Event streaming

Discussion: https://wiki.o-ran-sc.org/display/OAM/PM+Streaming

proto: https://wiki.o-ran-sc.org/download/attachments/82706888/o-ran-sc-oam-meas-data.proto?api=v2

template: https://wiki.o-ran-sc.org/download/attachments/82706888/o-ran-sc-oam-meas-data.template.json?api=v2

  • John Keeney  is updating sequence diagram for file-based & streaming proposal - Work in progress
  • Alex Stancu  Trying to get back to this topic for SIM as soon as possible.

Link to the plantUml code under version control: https://gerrit.o-ran-sc.org/r/q/topic:OAM-349

Jira: https://jira.o-ran-sc.org/browse/OAM-349


00:35ONAP SON/slicing Use case
  • 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)


    • Presented plan for proposal
      • Slides : Draft / WIP

00: SMO Deployment (Tainwan lab)
  • 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.

00:Disaggregated SMO Flows 

00:OSC / OAI / OSFG


Q/A


None this week

00:40Meeting ends



00:003GPP copyright issue

Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN

Problem Statement might be not fully understood. 

Next step: Call with Magnus Buhrgard 

After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP

The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08

> Magnus wont give up (smile)




Action items