Use Case Realization Call: September 4, 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?

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

Pltfm

PLATFORM TOPICS:

Data Persistency, CM

@N.K. Shankaranarayanan

STATUS: Work for ConfigDB completed, not merged in R4

Dan Timoney moved to R5, one Jira for ConfigDB. 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

Dongho KimpeakmenPltfm

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