Use Case Realization Call: September 18, 2019

Date

Sep 18, 2019

Attendees

  • @Benjamin Cheung

  • @Fari Behi

  • @ittay

  • @Vimal Begwani

  • Seshu

  • huang Cheng

  • @Gerard Hynes

  • @Joanne Liu Rudel

  • @Scott Blandford

  • @Zu Qiang

  • @Prabhu

  • @Oskar Malm

  • @James Forsyth

  • @Swaminathan Seetharaman

  • Melanie Sater

DISCUSSION ITEMS LOG

 

Ctgry

Item

Who

Notes

Pltfm

 

PLATFORM TOPICS:

Controller to NF Association

@Benjamin Cheung

R5/R6 Topic

See Slides Nov 6, 2018. Development of Controller to NF assignment association S/W.

CDS, VF-C, APP-C, SDN-R, SDN-C; will the CCSDK "merging" of controllers happen in R6?

USE CASE REALIZATION MEETING (Notes 2018-11-6) Ctrl-NF

Pltfm

PLATFORM TOPICS:

Data Persistency, RunTime DB

@N.K. Shankaranarayanan

@Joanne Liu Rudel

@Benjamin Cheung

STATUS: Work for RunTime DB completed, not merged in R4

Dan Timoney moved to R5, one Jira for RunTime DB. One issue about merging.

ONAP code added can take a test ONAP deployment to have the ConfigDB work.

USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency

Pltfm

PLATFORM TOPICS:

Controller LCM API Evolution

@Oskar Malm

https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

Goals (Architecture Evolution)

  • Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations

  • Support PNFs for applicable LCM operations in a consistent way

  • Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category

    • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.

  • Evolution steps that preserve backwards compatibility for clients

Present at the Arch S/C Apr 9 (Tue) second presentation.

Use Cases

USE CASE/5G:

RAN (ORAN-3GPP) Standards harmonization with ONAP

@marge.hillis

@Vimal Begwani

@fred feisullin

  • Orchestration at the Edge.

  • A1/O1/E2 communications. Edge to ENBs, Telemetry.

  • E2 will not have this info. O1 is I/F for PM counts. Not a management I/F.

  • WG3 (ORAN) is defining this.

  • ONAP w/ O1. Changes w/ O1 interface.

  • How to satisfy A1/O1 and in what time-frame.

  • U/C ORAN - ONAP harmonization. 3GPP ORAN ONAP.

  • Starting a new U/C in 5G. Marge, Vimal, Fred Feisullin

  • Edge inventory & topology. Transport BH consideration w/ real-time near-RT aspects

  • Akraino. MEC. Edge automation (Ramki).

Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP

Use Cases

USE CASE/5G:

Licensing Management

@Timo Perala

@Samuli Kuusela

New U/C added to the 5G Use Cases for Licensing Management

Use case Wiki: LICENSING MANAGEMENT

Use Cases

USE CASE/5G:

OOF / SON

@N.K. Shankaranarayanan

PoC U/C will happen in WinLab. To meet time lines do those parts in Windriver focusing on DCAE, Policy and OOF.

Jira SDN-C (Dan Timoney) pushed El Alto (the Maintenance Release).

Use Cases

USE CASES:

BBS U/C Evolution

@David Perez Caparros

@Tim Carey

@Chaker Al-Hakim

BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.

  1. Change Service - want to use ONAP platform.

  2. Full Closed Loop for Fault Management - CLAMP.

  3. Service Update API (SO) - will be developed

https://lf-onap.atlassian.net/wiki/download/attachments/16362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

Use Cases

USE CASES/5G:

PM Dictionary/FM MD GUI

@marge.hillis

FM META DATA & PM DICTIONARY in R5

Use Cases

USE CASES/5G:

PNF S/W Upgrade

@Zu Qiang

@wangyaoguang

PNF software upgrade in R6 Frankfurt

Use Cases

USE CASES/5G:

Preonboarding/Onboarding

@Benjamin Cheung

@Zu Qiang

@Michela Bevilacqua

PNF PREONBOARDING / ONBOARDING in R5

Use Cases

USE CASES:

IoT Service Creation

@Atul Purohit

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

Use Cases