Time & Location:

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

Aug 3, 2022

Attendees

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

• @Martin Skorupski (Highstreet & OSC OAM)

• @Alex Stancu (Highstreet & OSC SIM)

• @James Li (CMCC & OSC INT)

• @N.K. Shankaranarayanan (STL)

• @Halil Cakal (Ericsson EST)

• @Kevin Tang (STL)

• @michal.cmarada@gmail.com (Pantheon)

• @Timo Perala (Nokia)(Nokia & ONAP)

• 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 2022-08-03 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

Notes:

Housekeeping:

• @Martin Skorupski away next week  

OSC SMO Meeting Series: Reminder from previous weeks:

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

  • 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

OSC Project roundup:

News from OSC TOC call last week

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

  • Note Time change for TOC calls from May 5th onward

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

  • News from TOC call last weeks:

    • Proposal from Samsung to create new AI-ML Platform project in OSC

    • Discussion continue this week

  • This week's TOC (Tomorrow):

NONRTRIC (@John Keeney (Ericsson EST))

• No update from last week. Most of team on vacation

SIM (@Alex Stancu)

• No update from last week

OAM (@Martin Skorupski)

• Discussing with SMO Tacker team - figuring out role for interface VNFM↔EMS (SOL-002 ve-vnfm-em)  ...

  • OAM functions likely act as the EMS here

  • Mostly needed to get identifiers/inventory information initially ... more later

• O-RAN WG10 & WG6 has a new std-defined VES body (OAM-Spec v7)

  • No machine-readable data model (yet)

  • Currently working on a non-spec/pre-spec version for OSC

• @Martin Skorupski away next week.

O-DU (@Hariom Gupta @Vidhu (Deactivated))

• No Update

OSC Integration / INT (@James Li )

• @James Li Still working with @Sridhar Rao re XTesting framework

  • Testing deploying near-rt-ric (but xtesting is uses Ansible for deployment, so some translation needed to support the deployment)

  • Likely other functions for deployment will also need Ansible playbooks.

• CMCC setting up industry test lab in CMCC Silicon Valley lab. Does existing OSC functions support common usecases?

  • Some aspects are partly supported - so yes & no. More details on request/test-cases needed.

RSAC/SMO (@David Kinsey [AT&T])

• Minutes & Meeting: 2024 RSAC Meetings

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

• This Week:

  • No meeting this week

DMaaP vs Kafka in ONAP/OSC

• DMaaP MR being phased out (deprecated) - to be replaced by Kafka & Strimzi Bridge

  • Ref Fiachra Corcoran - ONAP DMaaP PTL Email: https://lists.onap.org/g/onap-discuss/topic/92666891

  • Should be a relatively easy change, but code changes environment changes needed during G Release

Q/A

• @N.K. Shankaranarayanan How does O1 to O-DU handle OpenFH messages to O-RU?

  • What if there are features in O-RU's OpenFH model that are not in O-DU O1 model? @Martin Skorupski It needs to be added to O-DU O1 model ... so need to raise with O-RAN Alliance team WG5.

    • Not every detail should be exposed? mapping openFH to O1 is non-trivial - some abstractions are hard to map!