Time & Location:

Date

Nov 10, 2021

Attendees

• @John Keeney (Ericsson EST)

• @Alex Stancu

• Arnold Alvarado (NIWC)

• @Dibas Das

• Doug Evans

• @David Allabaugh

• @Hariom Gupta

• @James Li

• @Kevin Tang

• @Kevin Timoney

• @marcin krasowski

• @Gervais-Martial Ngueko

• @michal.cmarada@gmail.com

• @N.K. Shankaranarayanan

• Neil Hoff

• @Pawel Slowikowski

• Ryan McAllister 

• Sebastien Determe (AT&T)

• @Sonia Sangari

• @Timo Perala (Nokia)

• @Former user (Deleted)

• 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 2021-11-10 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

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

NOTE: DST Changeover in coming weeks!

• See above & Keep a close eye on the calendars! All done now

OSC Project roundup:

News from OSC TOC call this week

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

• OSC Integration labs making progress but still not ready. (ref also INT topics below)

• E-Release "hurry-up"

  • Code Freeze early Dec.

• Licensing - SCCL

  • No much update - discussions on CLA continue

NONRTRIC (@John Keeney (Ericsson EST))

• Continuing with data exposure from DMaaP (& from Kafka via SMO adapter https://gerrit.o-ran-sc.org/r/c/smo/ves/+/6974) 

• Still working on Helm Chart updates & aligning with IT/DEP charts (ref also SMO/Integration package/charts topic below)

• Getting started on O-DU-Slicing–Usecase "Link Monitor" rApp

SIM (@Alex Stancu)

• On track for "O-DU Hello-World" Yang model & implementation

OAM (@Martin Skorupski)

•  @Martin Skorupski On vacation this week (Enjoy )

• No Update - Yang models still under review - All comments ready to merge ?

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

• Successfully installed 3GPP Yang models  ... & created an edit point

• Implementation for PM VES almost complete

• Working on Slice/Cell configuration

• Hoping for completion/review next week

RSAC/SMO (@Former user (Deleted))

OSC Integration / INT (@James Li )

• Working with @Martin Skorupski Sébastien Determe etc on it/dep SMO / environment charts - hoping for a finalised PR soon.

• integration test for nearRTRIC/nonrtric integration - O1 & A1.

• A1 / Traffic steering app - re-enable A1? Also aim for an A1-EI integration test

• Met with Prof. Ray re progress on Taiwan lab & James' lab. Offering some help building up lab & work division.

• Working with Keysight (who helped already with 2 OTIC labs) re OSC lab in Silicon Valley.

ONAP SMO deployment options

• Sébastien Determe 

  • Updated code for simulator configuration & topology (at runtime)

  • SIM 137(?) : Fixed (No more need for IP at SIM set up https://lf-o-ran-sc.atlassian.net/browse/SIM-77)

  • New PR adding tests (https://gerrit.o-ran-sc.org/r/c/it/dep/+/7015 )

  • Fixed verify Jenkins job ... had to remove Kong (temporary) - difficulty downloading. Discussing with LF. Ready to review now ...

    • Follow up.

  • First draft of Python test SDK (in PR#2 https://gerrit.o-ran-sc.org/r/c/it/dep/+/7015) - uses ONAP Python library for ONAP component verification, with O-RAN updates.

ONAP Use cases etc (@N.K. Shankaranarayanan)

• Slicing Use case:

  • WIPRO lead & team stepping back somewhat  ... (mail from Ahila: https://lists.onap.org/g/onap-tsc/topic/86928483#8256)

  • Will be further discussed at Slicing Use Case team.

  • Use case remains important for O-RAN Slicing discussions.

• SON Use case:

  • @N.K. Shankaranarayanan presented SON Use case at Requirements committee ONAP Jakarta

    • Jakarta release - functional requirements proposed list#5GOOFSONUseCase 

    • A1 action needs enforcement - touches on many aspects

    • "rApp'ifying"/"R1-ifying" the use case?

    • Continue to use as a requirements driver - platform, O1, SIM, A1, etc..

• "Sleeping Cell - A1 Enforcement Simulator"

  • Possible to have as Use case for Jakarta ??? Running out of time for Jakarta.

  • Offline call & further discussions needed probably.

  • @Pawel Slowikowski Already a PoC - Missing O1 parts - (RANSIM netconf)

    • Maybe RANSIM capabilities here? Please Join SON use case call ... or talk offline.

O1 models over R1 (@N.K. Shankaranarayanan)

(@00:40 in recording) (@N.K. Shankaranarayanan)

Open

(Note, you may need to download and view offline if the content appears garbled)

• For O1-CM enabling functions in R1, then R1 models should be based on O1 models - but probably need something more, extending main O1 model - "Primary Model & Secondary Models"

• How is secondary model synced with primary model? E.g. In ONAP CPS the TBDMT function does this.

  • Expressiveness of mappings make make it possible/difficult to maintain such mappings ... or would richer logic be needed/possible? FFS.

• Needs discussion in WG2 (R1 aspects) & WG10 (OAM/SMO aspects) - likely too late for November train at this stage

Q/A

• Ran out of time again