2023-05-30 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

May 30, 2023

Attendees

• @John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)

• @Martin Skorupski (Highstreet & OSC OAM)

• @Alex Stancu  (Highstreet & OSC OAM)

• @N.K. Shankaranarayanan(ONAP) 

• @Aravindhan Ayyanathan(Ericsson EST) 

• @Kevin Timoney (Ericsson EST)

• @Vamshi Namilikonda (Cap Gemini)

• May not have captured a full attendee list for this meeting  ... please add/remove yourself

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

• Co-located with ONAP 2023-05-30 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

• Recording (MP4 - lo res)

Notes:

Housekeeping:

• Calendar:

  • https://lists.o-ran-sc.org/g/main/calendar

  • https://lists.onap.org/g/onap-meetings/calendar

  • 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

• OSC SMO project calls now move to its own time slot - alternate Thursdays - TBC
  
  

  • See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars

  • See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar

  • (Note this meeting to open to anyone, including non-ORAN members)

  • We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.

  • See OSC SMO Project meeting notes

• See also OSC AIML Project meeting notes

• @John Keeney (Ericsson EST) will be away on 20-June & 27-June
  
  

  • Propose to cancel 20-June meeting - overlaps with O-RAN F2F meeting in Osaka. Will confirm in coming weeks.

OSC Project roundup:

News from OSC TOC call last week

• https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)

  • Last week's TOC (Thursday):

    • Update from several projects, including OAM, SIM,

  • This week's TOC (in 2 days):

    • New meeting format with updates from relevant PTL etc

      • week 0: RSAC, Integration I (cross-project testing related), Infrastructure

      • Week 1 : RIC, RICAPP, AIMLFW

      • Week 2: NONRTRIC, SMO, OAM, SIM

      • Week 3: Integration II (lab related), O-DU-HIGH, O-DU-LOW

      • This week: 

        •    RICAPP, O-DU-HIGH, O-DU-LOW, INT

    • Planned update from O-RAN MVPC co-chair

NONRTRIC (@John Keeney (Ericsson EST))

• Demo Last week: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode" @Aravindhan Ayyanathan

• Demo last week: "CAPIF for Service Registration & Service Discovery" @Yennifer Chacon

• TOC Update last week

• Focus on documentation, final testing & release tasks for ONAP London & OSC H

• Some team member updates in coming weeks.

• Making progress with stating a new 'rApp manager' function. Still very early, but will one of the main activities in new OSC release.

• Previous weeks:
  
  

  • Consolidating PM data exposure in new repo for RAN PM functions

    • https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Fplt%2Franpm.git;a=summary

  • (R1) Service Exposure & Management

    • CAPIF Aligned Service Registry

    • Secured/Sandbox execution environment

    • Controlled access & exposure of service to/from rApps

  • (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

  • 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.

SIM (@Alex Stancu)

• Succeeded to deploy NONRTRIC ranpm/DME solution in AWS
  
  

  • 2 Issues: Space in Base64 encoded tokens, cert generation would work better with a small fix

  • @Björn Magnusson has the details

  • Next wtep PM file genreation with simulator.

• Still looking at PM file passing:

  • Some additional useful info: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm/en/latest/

OAM (@Martin Skorupski)

• Release preparations

• Discussions ongoing about PM streaming using websockets & protobuf - will align with 3GPP O1 spec.

• Debating with WG10 about fixing some openapi/yaml inconsistencies in 3GPP specs.

O-DU @Vidhu (Deactivated))

• No update this week

OSC Integration / INT (@James Li )

• No update this week

SMO (@Seshu Kumar Mudiganti )

• No update this week

• Meeting notes Meeting notes

RSAC (@David Kinsey [AT&T] @Rittwik Jana )

• Minutes: 2024 RSAC Meetings 

AI/ML platform project (@Joseph Thaliath)

• No update this week

• Minutes & Meeting: Meeting notes

• Calendar: https://lists.o-ran-sc.org/g/main/calendar

ONAP/OSC Usecases (@N.K. Shankaranarayanan)

• See below

ONAP/OSC Alignment Usecase proposal for ONAP Montreal (@N.K. Shankaranarayanan)

• As discussed in previous weeks

• Aiming for presentation to ONAP ArchCom: 13 June

• Unclear yet what the outputs will be ...

  • Even just articulating how functions should work together, and reflecting existing/resourced work as in-scope for this activity.

  • Little new/usecase-specific development expected

• ONAP M1: 22 June

Questions / Comments / AOB:

• @N.K. Shankaranarayanan: Wondering if "Cloud Events" is relevant for event formats? Maybe of interest for R1?

  • CPS team in ONAP considering this.

  • https://cloudevents.io/

Meeting ends 25min