Time & Location:

Date

Feb 9, 2022

Attendees

• Incomplete. Sorry. I didn't get an attendee snapshot before the call ended

  • Please add yourself.

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

• @Martin Skorupski (Highstreet & OSC OAM & ONAP)

• @Alex Stancu(Highstreet & OSC SIM)

• @James Li (CMCC & OSC INT)

• @Hariom Gupta (HCL)

• @ChrisC

• @David Johnson

• @N.K. Shankaranarayanan (STL)

• @Kevin Timoney (Ericsson EST)

• @marcin krasowski (Samsung)

• @Gervais-Martial Ngueko (AT&T)

• @Sonia Sangari (Ericsson EST)

• Sebastien Determe (AT&T)

• @Timo Perala (Nokia) (Nokia)

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

• Co-located with ONAP 2022-02-09 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

Notes:

Housekeeping:

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 this week

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

  • F Release planning

    • Just OSC SMO & NONRTRIC covered this week

  • Discussion if OSC could act as / help a compliance test environment

• O-RAN vF2F this week & next week - See the O-RAN Wiki https://oranalliance.atlassian.net

NONRTRIC (@John Keeney (Ericsson EST))

• E-Maintenance Release

  • Done

  • Still need to update some docs/wiki - ongoing

• O-RU use case versions (and it/dep charts) now working in local test env

  • Want to work together with it/dep integration team re tests of different versions / deployments / scenarios

• Splitting gerrit/repo contents across multiple repos 

  • In progress

• F-Release prep

  • R1 for rApps

  • R1 for Service Exposure

  • Data Management & Exposure - including end-to-end demo

SIM (@Alex Stancu)

• Working on F-Release prep

• Working on Pre-Spec-ing PM streamimg

• O2 related issues

OAM (@Martin Skorupski)

• Working on F-Release prep

• PM Streaming pre-spec-ing

• Experimenting with topology visualization

  • May have more to report at O-RAN F2F

  • Would be good to reuse this topology service in future use cases.

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

• @Hariom Gupta

  • F Release prep

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

• No update.

OSC Integration / INT (@James Li )

• 3 labs currently in progress (Taiwan, Bedminster (AT&T), California (CMCC)) and Powder Lab

• Taiwan lab team working on testing procedures/process improvement

• POWDER lab - working with @David Johnson to get more OSC components into the lab, to make it easier to run tests / deploy with SMO etc.

ONAP Use Cases Update  (@N.K. Shankaranarayanan)

• We have a JIRA for the SON Use Case "VNFRQTS-1003 - Develop new FM/PM/CM VES message formats aligned with O-RAN O1"

  • The task to converge on the best VES format for FM/PM/CM messages for the SON use case (and other use cases?) going forward

  • "DCAEGEN2-2986 - DCAE impacts for 5G OOF SON use case in Jakarta release"

  • In the case of PM VES format, there are two templates/files in OSC which look a little different in the body/payload part of the msg.

    • Would like to discuss which one we should build upon.

    •  1. OSC sim/O-DU Slicing PM VES msg and template: There is a sample PM VES msg in the Slicing Use Case wiki: https://lf-o-ran-sc.atlassian.net/wiki/display/SIM/Network+Slicing+Use+Case#NetworkSlicingUseCase-ExampleVESPMstndDefined 

      • https://gerrit.o-ran-sc.org/r/gitweb?p=sim/o1-interface.git;a=blob;f=ntsimulator/deploy/o-ran-du/ves_template.json

    • 2. OSC oam VES template: There is a PM msg template and other template files in the oam repo

      • https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/dev/client-scripts-ves-v7/json/templates/measurement.json

    • @Martin Skorupski #1 is VES std-defined - proper way. #2 is VES performance domain for OSC O-DU/OSC SMO for E release

      • Best to use the std-defined version (#1) . (#2 being phased out in F Release?)

      • (Note OAM functions support both options above)

  • Std-Defined ...

    • Still discussing how to have multiple groups of data ... lists?

    • But tricky to get an agreed schema

      • Currently we can just use a custom schema (which is a massive advantage of the std-defined ves format!) .

        • e.g. see https://wiki.onap.org/display/DW/CM+handling+guide#CMhandlingguide-CreatecustomVES-collector for guide for how to configure VES collector with custom schemas.

      • Can/Should we use standardized counters? - Yes - but Licensing/Copyright issues.

      • Until we have agreement it is not clear.

  • Would be nice to get end-to-end dynamic job creation working

    • Have most of the parts ... will working on plumbing together in coming sprints.

    • All pre-spec for now!

SMO Integration Charts (Sebastien Determe & @ChrisC)

• Issue with O1 tests (https://gerrit.o-ran-sc.org/r/c/it/dep/+/7635)

• Still working on ONAP PF Apex Policy for O-RU use case ...

  • Ref: change in CM endpoint (model) via SDNC (See below)

  • @John Keeney (Ericsson EST) will check if this is already updated in NONRTRIC project

• Thinking about an O2 simulator ... ??

Q/A

•  No topics today.