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 |


ZOOM: https://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

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
    • ONAP Usecases
    • ONAP Req & ONAP TSC committees
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

John Keeney 

Next meetings:

Please follow the calendar


00:05O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
  • Non-RT-RIC: John Keeney 
    • Service Exposure Manager - progress!
    • O-RAN Spec API compliance for R1-SME, R1-DME (spec vs code), R1-A1(spec vs code?), A1 (looks good)
    • Mostly same as last week:
      • Making good progress on rApp manager.
        • Adding support for DME integration now.
        • will be in I-Release
        • Demo (smile) today - thanks 

      • 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.
        • close to finished → demo (smile) soon
        • CODE MERGED !!!(smile)
        • new - outgoing API → callbacks or ...
          • northbound outgoing API
      • 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.
        • pairwise test should "move" to INT project
          • robot test under it-deb??!? better under ??? integration into test-suite?!?!?
          • trigger xApp as "consumer" of A1 commands 
      • Release mode very soon (in ONAP and O-RAN-SC)
        • ask Naman (smile)
  • SIM: Alex Stancu
    • ONF deployed NearRtRic - to be considered? 
  • OAM: Martin Skorupski
    • ongoing work on a "planned" O-RAN
      • py format, lint, test 
      • handover areas between cells
      • 5G-Core per SMO instance 
  • O-DU: @Vidhu
    • No update this week
  • AI/ML: @Joseph Thaliath

    • Minutes & Meeting: Meeting notes 

    • No update this week
    • Shankar introduced the "flows"
  • INT: James Li(CMTI)
      • pairwise testing
      • sync with Taiwan lab - work with Bimo
      • joint effort between INT and OSC Taiwan Lab - THANKS!!!!

00:20OAI / O-RAN-SC Workshop 

John Keeney James Li @Bimo 

Chat (smile)
  • excellent workshop
  • good potential for collaboration between OAI and O-RAN-SC
  • impact on OSFG Blueprint based on the workshop
  • synergies 
  • option for end-to-end testing and demos

00:30Energy Saving

@Bimo

Energy Saving

  • definition of rApp
  • call flows → please keep N.K. Shankaranarayanan in the loop as he has all the flows "under control" (smile)
  • as inspiration see demo below... (What is an rApp?)

00:38DemoAravindhan Ayyanathan 

rApp Manager

  • life cycle control of rApp
  • integration with ONAP components. 
  • Slides:
  • Video:
    20231121 - NONRTRIC - rApp manager.HiRes.mp4

  • Makes a lot of use of ONAP ACM to support rApps that contain a composition of K8s microservices, ML Models, Policies, Workflows, Configuration, A1 Policy, etc
    • Multiple rApp instances for rApp types
    • rApp is Lifecycle Managed as a single composition of App elements
      • Different Element types are handled by pluggable 'Participants'/Handlers
        • Current Participants: K8s/Helm, A1 policy, ONAP Policy, KServe (ML), HTTP configurator, DME, others
  • Adds Service Management & Exposure - SME    (Not already supported in ACM)
    • All produced & Consumed services are described in App package, so Service Registration & Service Discovery needs to be handled.
    • Uses NONRTRIC CAPIF Core function
    • R1-SME aligned
  • Add Data Management & Exposure - DME    (Not already supported in ACM) 
    • All produced & consumed Data Types are described in App package, so Data Producer Registration & Data Type Discovery & Data Job creation needs to be handled. 
    • Uses NONRTRIC Information Coordinator Service
    • Similar to R1-DME
  • Prototype rApp Package presented - Not yet Stable!
  • rApps, rApp instances have well-defined state models
  • Call sequences for various rApp & rApp Instance workflows presented.
  • Demo:
    • Show a sample rApp package
    • Deploy & prime the rApp
    • Create one instance - showing all its constituent parts configured, started & running. Service & Data types registed & discovered, Data Jobs created.
    • Delete the created instance - showing all its constituent parts stopped & removed
    • Delete the rApp & its definition - showing rApp environment cleaned up

00:76Meeting ends





LNF DTF

John Keeney 

Feedback
  • postponed to 2023-11-28

00:00"flows"N.K. Shankaranarayanan 
 of "Project report"
  • SMO architecture evolving 
  • attraction by WG2

00:22

PM Event Streaming

Martin Skorupski 

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:

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


00:ONAP SON/slicing Use case

N.K. Shankaranarayanan 

  • No Update this week
  • 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 (Taiwan lab)

N.K. Shankaranarayanan 

  • 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 last week 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 directory 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 .. A lot of the charts/deployment is use case specific.

00:00Disaggregated SMO Flows 

N.K. Shankaranarayanan 



Q/A


None this week

00:50Meeting ends



00:003GPP copyright issue

N.K. Shankaranarayanan 

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