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
    • Release process for ONAP and O-RAN-SC all below
    • Pushing on with work on rApp manager - especially rApp onboarding, preparing for SME, DME etc
      • Lots of bits there already ... this will tie them together in a coordinated way when deploying rApps
      • Much of the rAPP LCM will be handled by ONAP ACM functions
      • Main issue is we still have no clear definition of rApp package.
      • We will likely be out of alignment with O_RAN specs when they arrive / mature. We will evolve our work then.
    • Continuing as per last week :
      • Alot of work in JDK 17 & Springboot 3 updates
      • Consolidating PM data exposure in new repo for RAN PM functions
      • (R1) Service Exposure & Management
        • CAPIF Aligned Service Registry
        • Secured/Sandbox execution environment
        • Controlled access & exposure of service to/from rApps
        • 2023-04-19: good progress - maybe a demo in a couple of weeks.

      • (R1) Data Management & Exposure

        • File-based PM data → InfluxDB
        • Previous focus on PM data - but will extend to other use cases too
        • Aim to work with AIML project for Training (and Inference ?) data access

      • rApp Management

        • Built on ONAP “Automation Composition” model & platform to implement rApp use cases
          • Inference Services in rApps
            • Added a 'KServe Participant'
          • rApp-specific extensions needed
        • Packaging, Onboarding & Orchestration of rApps
          • rApp-specific packaging & Onboarding
            • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
          • (rApps with & without µService)
        • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

      • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

        • A1 Spec evolution
        • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
        • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
        • 2023-04-19: fine grain access control
      • Sample use cases (rApps)
        • Requirements Drivers for rApp/R1 development
        • High degree of cross-project integration activity

      • Testing, Maintenance & Housekeeping

        • Function Test & Integration Test environment,
        • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
        • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
        • test deployments
  • SIM: Alex Stancu
    • WG4 OFHM - supervision in NTS (O-RU function)
      • available for  NTS-O1 1.6.3
    • PM File generation
      • update for the stndDefined fileReady → 3GPP REL-18
      • John Keeney Alex Stancu : req: file ready event - template for 3gpp-xml file → timestamps - generated provided by John
        • same certs for FTPes 
        • each sim instance will create its own file (file per node)
        • check read-the-docs of Non-RT-RIC
        • deployment done on AWS by Alex with support by Non-RT-RIC
  • OAM: Martin Skorupski
    • release notes - issue with docx (sad)
    • documentation
    • Team discussion about O1 PM-Streaming (3GPP → websocket/GPB/yang)
    • CR preparation with WG10 for 3GPP OpenAPI yamls (some minor issues: upper-case, lower-case, typo)
  • O-DU: @Vidhu
    • no report

00:15ONAP SON/slicing Use case

N.K. Shankaranarayanan 

    • Presented plan for proposal
      • Slides : Draft / WIP

Issue when deployment with OOM:

  • oom - strimzi > 
    • one option to reinstall strimzi 

Preparation for the next release

  • enhancements of RAN SIM

To be on the agenda for June 13!



00:18ONAP/O-RAN-SC Cooperation/Alignment

N.K. Shankaranarayanan Seshu Kumar Mudiganti John Keeney Martin Skorupski 

Was topic at ONAP TSC

  • more interest
  • use case should drive the discussions
  • end-to-end use case requires rApp - thoughts?
    • ACM control loop


Meeting 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