2023-04-26 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

Apr 26, 2023

Attendees

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

• @Martin Skorupski (Highstreet & OSC OAM)

• @Alex Stancu (Highstreet & OSC SIM)

• @James Li (CMTI & OSC INT)

• @Vidhu (Deactivated) (HCL & OSC O-DU-High)

• @Aravindhan Ayyanathan (Ericsson EST)

• @Kevin Timoney (Ericsson EST)

• @Sonia Sangari (Ericsson EST)

• 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-04-26 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

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

• 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

Should we change the time for this call?

• Time is very late for attendees from Asia ... maybe a bit earlier ... but not earlier than 5AM West-US

• Suggestions in coming weeks.

  • Feedback from @James Li - West coast US (last week): not much earlier please

  • Feedback from  @Vidhu (Deactivated) - India - A little earlier would be nice - esp in Winter - but not a major issue.

• Will keep this topic open for another while - requesting feedback from the community.

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):

    • No major update. See minutes.

  • This week's TOC (Tomorrow):

NONRTRIC (@John Keeney (Ericsson EST))

• No major update:

  • Struggling with some issues building readthedocs documentation site for nonrtric-plt-ranpm repo ....

• Otherwise continuing as per last week :
  
  

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

• Still working on WG4 OFHM O-RAN watchdog/supervision activity & reset
  
  

  • (Reverse) Heartbeat from O-RU

• PM File generation
  
  

  • @John Keeney (Ericsson EST) @Alex Stancu No update

OAM (@Martin Skorupski)

• Still working on:

  • stndDefined examples for 

    • 3GPP based FM, CM

    • OFHM based FM, CM

  • OFHM supervision mechanism. 

• See below - Spotted an error with VES message from O-DU ...

• Added a traffic gateway function to help with security cert issues.

  • HTTPs terminates at the gateway then http from there.

O-DU @Vidhu (Deactivated))

• O-DU PM VES events need an update - adding Slice array
  
  

  • Currently using ONAP Domain: Measurement VES event.
    Suggest moving to a custom std-defined event - can then define own schema - ref: Network Slicing Use Case#ExampleVESPMstndDefined 

OSC Integration / INT (@James Li )

• @James Li  Just back from vacation
  
  

  • No other update

SMO (@Seshu Kumar Mudiganti )

• No update

• Meeting notes for this week: 2023-04-26 Meeting notes 

  • Possibility of changing the meeting time?

RSAC (@David Kinsey [AT&T])

• Minutes: 2024 RSAC Meetings (25/4)

AI/ML platform project (@Joseph Thaliath)

• Minutes & Meeting: Meeting notes

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

• No update this week

ONAP Use cases (@N.K. Shankaranarayanan)

• No Update

ONAP / OSC / O-RAN Alliance: Cooperation & Alignment

• No Update

Questions / Comments / AOB:

• None

Meeting ends 25min