Time & Location:

New Meeting Slot

New Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !

NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)

Winter (non-DST) time eventually stabilizes to: 9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

Date

Nov 25, 2020

Attendees

@John Keeney (Ericsson EST)
@Martin Skorupski
@Mahesh Jethanandani
Alessandro D'Alessandro
@abhghgh1
@Andy Mayer
@Andrea Buldorini [TIM]
@Former user (Deleted)
@Dibas Das
@Emmanuel Sarris
Fernamdo (Fred) Oliveira (Verizon)
@Joachim Blixt (Deactivated)
@Hariom Gupta (Deactivated)
@Kamel Idir
@Lasse Kaihlavirta
@marcin krasowski
@Michela Bevilacqua [Ericsson]
Paulo Costa
@Pawel Slowikowski
Ruslan Kashapov
@Sonia Sangari
@Scott Blandford
@subhash
@Timo Perala
@Vidhu (Deactivated)
@Zu Qiang
Some others may have joined later ... please add yourself

Recording

Recording (mp4)

Notes:

Meeting 2 December - @John Keeney (Ericsson EST)will open the bridge. @Martin Skorupski is unavailable
Meeting 9 December - @Martin Skorupski will start
Meeting 16 December unconfirmed. Will decide closer
Meeting 23 December & 30 December cancelled due to holidays

OSC Project roundup

OSC Cherry Rapidly approaching! (Release early Dec)

NONRTRIC (@John Keeney (Ericsson EST))

Continuing with Cherry Release Prep.
Plan to demo A1-Enrichment Function next week (will send invite to all here, discuss@o-ran.sc.org & add to ONAP & OSC calendar)
Continuing pre-release with Integration & Deployment mainly.
ONAP Guilin Release of A1 Policy Functions on track.

SMO (@Mahesh Jethanandani)

Yang validation tool function available in SMO gerrit, and Cherry Integration tasks continue pre-release.
Demo first version CSAR Package Validation tool
- @Pawel Slowikowski Similar tools already exist in ONAP. @Mahesh Jethanandani Tools is based on ONAP VNFSDK version with unnecessary parts removed
- @John Keeney (Ericsson EST) Tosca parsing tools available in ONAP. Ref Tosca Parser in Policy Framework (and SO).

SIM (@Alex Stancu )

@Mahesh Jethanandani still working with @Alex Stancu on wiki page etc Yang Validator (Netconf) client in OSC Lab.

OAM (@Martin Skorupski )

See video of OSC Cherry OAM (FCaPS functions) https://lf-o-ran-sc.atlassian.net/wiki/display/OAM/Use+cases+demonstration

ONAP - OSC

@Swaminathan S Added additional content to ONAP use cases page: https://wiki.onap.org/display/DW/Potential+ONAP+%3C-%3E+O-RAN+collaboration+use+cases - including the key JIRAs & people.
- @Former user (Deleted) For more info on these use cases refer to Use Case Realization Meeting Register MoM & attend meeting if desired.
@John Keeney (Ericsson EST) & All: Suggest we need a similar page in OSC (RSAC?) to discuss/assist collaboration from ONAP community into OSC use cases too?
- @Martin Skorupski Alot of what is used in OSC is downstream ... and most exists independent of OSC.

End-to-End use case in OSC

@John Keeney (Ericsson EST) Continued discussion from last week 2020-11-18 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting
Discussed some possible options (All need proper discussion later to check feasibility):
- Front-haul-based
  - What creates the VES fault event when O-RU is brought down? (@Mahesh Jethanandani & @Martin Skorupski had some discussions with O-DU team ... still ongoing)
    - Can be created from O-RU or O-DU.
  - FM VES notification received via DMaaP to rApp. @John Keeney (Ericsson EST) NONRTRIC team can create a simple rAPP to then trigger a O1 CM change via OAM controller (Sample Postman scripts are available).
  - Different options for O1 message: O1-CM to O-DU, O1-CM to O-RU https://oranalliance.atlassian.net/wiki/spaces/FHWG/pages/1092485360/WG4-2020.003+-+O1+support+on+the+O-RU+-+prelim
    - Multiple options might be best.
- Near-RT-RIC (only)
  - Only pre-spec FM available in near-RT-RIC (To confirm with OSC nearRTRIC teams)
  - NONRTRIC rApp sends A1 message to near-RT-RIC. (Probably need an xApp to receive it)
  - @John Keeney (Ericsson EST) & @Martin Skorupski Need to talk to the rea-RT-RIC team in OSC
- nearRT-RIC & E2 (More ambitious)
  - Could include O-DU (O1 source & O1 target & E2 target) ?

- Use cases in ONAP may be useful, e.g. Slicing? OOM? (But need to be reported in OSC)
- Possibility or re-using Samsung ONAP demo and making it publicly available?
  - @Pawel Slowikowski - Can share, but an "official" usecase introduces alot of overhead in ONAP, need a repo, project. long term support. Would need to be properly landed in ONAP etc ....
    - @John Keeney (Ericsson EST) Possibly an PoC - less requirements? @Pawel Slowikowski Still needs to be landed somewhere.

Apps/Control-Loop/Automation-Loop in ONAP

@Pawel Slowikowski Where would the apps be? @John Keeney (Ericsson EST) In OSC we'd call these rApps, @Pawel Slowikowski no concept of rApp in ONAP ... or ONAP-App either!
- @John Keeney (Ericsson EST) PoC in ONAP Guilin & Honolulu TOSCA Defined Control Loop PoC in ONAP & TOSCA Defined Control Loop: Architecture and Design
- @Michela Bevilacqua [Ericsson] @Liam Fallon Possibly demo in coming weeks? (TBC)

2020-11-25 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting