Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
iconfalse

 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)


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

Calendars:

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)


Table of Contents

Table of Contents

Attendees

Administration

Please tag yourself using LF ID User Name.
Don't have an LF ID yet? Go here:
https://myprofile.lfx.linuxfoundation.org/
Please remove yourself from this list if you don't want to be tagged for future meetings

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
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 


00:05O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
  • Non-RT-RIC: John Keeney
    • G-Release Maintenance - image version updates
    • H-Release planning
      • data management exposure
        • data type filtering
      • service management exposure
        • auth
        • rApp management
        • registration aligned to 3GPP CAPIF
      • rsac inputs
      • interfacing with ai/ml project artifacts
      • rApp package and its definition in O-RAN Alliance
    • checkout Jira (smile)
  • SIM: Alex Stancu
    • H-Release planning
    • Trigger SIM for sending VES messages via ODLUX.
    • collaboration with OAI - integration of componentse.g. O-RAN-SC-DU interworking with OAI-CUno report
  • OAM: Martin Skorupski
    • updates according O-RAN OAM-Interface Spec
    • Working on updating stndDefined VES messages with latest artifacts from 3GPP REL-18
      • using Node-Red to visualize the flows
    • investigation of traefik for docker-compose 
      • Gateway to SMO components and single Cert-Management
      • please check istio, kong (check it-dep)
  • O-DU:HariomGupta(HCL) / @Vidhu
    • No update this week
  • AI/ML: @Sandeep J
    • No update this week
  • RSAC/SMO:David Kinsey  
    • smo: very short meeting - checkout the recording
    • rasc: 
      • release planning
      • code changes for O-DU
    • interworking with OAI
    • SMO disaggregation and 3 touch-points with AI/ML project
    • Timo and Shankar joint 
  • INT: James Li(CMTI)
    • x-testing with other projects
    • O-RAN-SC SMO project as "package" for O-RAN-SC artifacts (O-RAN-SC blueprints for deployments)
      • DMS needed by Tacker/O-RAN-SC-SMO 
      • Cloud orchestration and its relation to nephio . O2 aspects

00:3018VES → YANG identification@all

3GPP TS 28532 

  • ves:body → href (3GPP NotificationHeader) + path (body) does the trick
  • sample message - will be updated accordantly

00:4525ONAP Req ↔ O-RAN-SC RSACN.K. Shankaranarayanan 

first ideas are formulated for ONAP Req ↔ O-RAN-SC RSAC communications

  • background
    • plan - more synergy between the projects
    • start on requirements work
  • on the agenda for RSAC next week - thanks Timo for joining the O-RAN-SC RSAC meeting next week
  • Topics
    • O1 related → WG10 (WG4 for OFHM)
    • Non-RT-RIC, rApp:  (A1) related → WG2 (WG10, app management)
    • Orchestration, cloud, O2 related → WG6
    • AI/ML related (Training, ...) → WG2
    • Security!!!! (smile) → WG11
    • Sim work

00:4000:50SON/slicing Use caseN.K. Shankaranarayanan 

Planning for ONAP London

2023-02-01:

  • see discussion on CM VES messages
  • VES goes directly to CPS - please see: 

00:0045Q/A

Status of PM KPI (PM counters)

  • Non-RT-RIC has some experience with reading VES-Events from Kafka (based on topics).
  • Non-RT-RIC file based PM available 
  • O-RAN-SC SMO project add VES-events to from Kafka to InfluxDB
  • ONAP

WG10 - how data can be shared between SMO components








END


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

  •