Use Case Realization Call: September 11, 2019

Date

Sep 11, 2019

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?

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.

Pltfm

PLATFORM TOPICS:

Controller LCM API Evolution

@Oskar Malm

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 Cases

USE CASE/5G:

Licensing Management