2020-12-02 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting

2020-12-02 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting

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 !

https://zoom.us/j/436210993

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

Summer Daylight Savings time eventually stabilizes to: 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)

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

Dec 2, 2020

Attendees

  • @John Keeney (Ericsson EST)

  • @Swaminathan S

  • Alessandro D'Alessandro

  • @abhghgh1

  • @Andy Mayer

  • @Andrea Buldorini [TIM]

  • @Former user (Deleted)

  • @Dibas Das

  • @Emmanuel Sarris

  • @Grzegorz Wielgosinski

  • @Hariom Gupta (Deactivated)

  • @Joachim Blixt (Deactivated)

  • @Hariom Gupta (Deactivated)

  • @Kamel Idir

  • @Konrad Bańka

  • @Lasse Kaihlavirta

  • @Lathishbabu Ganesan

  • Paulo Costa

  • @Scott Blandford

  • @subhash

  • @Timo Perala

  • @Vidhu (Deactivated)

  • @Zu Qiang

  • Some others may have joined later ... please add yourself

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

Contents:

Recording

Notes:

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

  • Pushing with Integration & Deployment tasks with Felix in OOSC Integration team.

  • Please come along to OSC NONRTRIC Cherry Demo:

  • ONAP Honolulu reqmnt for A1 Policy functions approved through ONAP ArchCom & PTL approved. M1 expected 7thJan

  • @Former user (Deleted) Question about reuse of ONAP code in OSC at OSC TOC call: @John Keeney (Ericsson EST) No issue found. If there is a later divergence we will work it out then

  • @Former user (Deleted) Same for ONF? @John Keeney (Ericsson EST) Don't know. Have had no communications. Would welcome working together if its useful. Hopefully divergence can be avoided.

SMO

  • No update

SIM

  • No update

OAM

  • No update

ONAP - OSC

  • ONAP Usecases:

    • Please see:  Potential ONAP <-> O-RAN collaboration use cases 

    • @Swaminathan S Use cases & requirements working through requirements & architecture committee. 

    • @John Keeney (Ericsson EST) Come see ONAP A1 Policy functions at Demo on Friday(See above)

    • @John Keeney (Ericsson EST) A1 Policy Functions in ONAP H passed Archcom & has PTL Approval

  • ONAP E2E Network Slicing Usecase:

    • @Swaminathan S Hope to use the A1 interface to nearRTRIC. Come along to ONAP Slicing use case call for more info.

    • @John Keeney (Ericsson EST) Which nearRTRIC will you use in that use case: @Swaminathan S Not decided yet, maybe Simulator or OSC nearRTRIC.

    • @John Keeney (Ericsson EST) How would a nearRTRIC/RAN-CNF be deployed / stood-up? SDC, Orchestrator. @Swaminathan S in Guilin all NFs are already up & running. May move to dynamic instantiation in Honolulu. Lots to do for modelling too in H for RU/DU/CU. Also Mid-haul & Fronthaul & would need to interact with transport slicing functions .... TBC

    • @Swaminathan S Will demo slicing in late Jan or early Feb. Would be great to engage O-RAN folks there.

    • @Swaminathan S Looking for update on Yang Model ... (Please confirm with @Martin Skorupski & O-RAN WG1 team).

    • @Swaminathan S Any plans in OSC for Slicing? @John Keeney (Ericsson EST) Don't think there is a plan in OSC Dawn to look at slicing. Will of course touch base if there is

  • ONAP SON use case

    • @Swaminathan S Currently SON has PCI & ANR SON functions. A simulator exists if useful for OSC. The earlier version of the simulator's "Controller" code is available at https://git.onap.org/integration/simulators/ran-simulator. The architecture for Dublin release is available at RAN-Simulator impacts. Further enhancements are being made to it for the E2E Network Slicing case. Will share references once the wiki is updated.

    • @John Keeney (Ericsson EST) Any plan to make the SON use case more general for other use cases? If so any way it would align with Control-Loop/Apps in ONAP or rApps in OSC?

      • @Swaminathan S Should be possible for other use cases to add their own use cases following SON/Control-loop approach. Will add more use cases if they drive platform capabilities forward.

      • @Swaminathan S Also hope to look at control loop interactions (Paused since Frankfurt). Also hope to look more at ML-based SON.

      • @John Keeney (Ericsson EST) Sounds like good options for alignment. Let's keep doors open

End-to-End use case in OSC

  • @John Keeney (Ericsson EST) No substantial update this week

Other

  • @Lasse Kaihlavirta CSIT in ONAP ... Disaggregating CSIT many CSIT functions out to individual projects & more granular. @John Keeney (Ericsson EST) Great. A1 Policy functions need to & will align more towards this in ONAP H.



(From last week: @Michela Bevilacqua [Ericsson] @Liam Fallon will revert about a quick demo for TOSCA Defined Control Loop PoC in ONAP & TOSCA Defined Control Loop: Architecture and Design in coming weeks )