Use Case Realization Call: April 17, 2019

R5 El Alto Cadence Release Proposal

(EUAG / End-User Advisory Group)

@Catherine Lefèvre

https://wiki.lfnetworking.org/display/LN/EUAG+2019-04-09+meeting+minutes

Summary: The R5 El Alto release could be shortened

and focus on internal (tech) debt and defect backlogs.

A proposed release cycle is presented.

R4/Dublin (M4 Milestone/RC0)

April 25

 @Benjamin Cheung

Release Candidate 0 - RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

1. supporting integration testing (complete Health Check and Pair Wise Testing)

2. closing high priority defects

3. supporting Documentation team

R4 Dublin Release Planning Wiki: Release Planning

Score Card: M4 Dublin Release Requirements

PLATFORM TOPICS:

Controller to NF Association

@Benjamin Cheung

PLATFORM TOPICS:

Data Persistency

@N.K. Shankaranarayanan

Work for ConfigDB, 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.

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:

BBS U/C Evolution

@David Perez Caparros

@Tim Carey

San Jose presented proposals for next release for R5/R6.

Slide set linked in R5 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/5G:

PM Dictionary/FM MD GUI

@marge.hillis

FM META DATA & PM DICTIONARY in R5

USE CASES/5G:

Preonboarding/Onboarding

@Benjamin Cheung

@Michela Bevilacqua

@Zu Qiang

PNF PREONBOARDING / ONBOARDING in R5

USE CASES:

Splitting up PNF & 5G U/Cs

@Benjamin Cheung

@Alla.Goldner

R5 El Alto Use Case Page:

Release 6 (Frankfurt) proposed use cases and functional requirements

A new General PNF Use Case Page was created

https://wiki.onap.org/pages/resumedraft.action?draftId=60892496&draftShareId=8c48e706-ad4f-464d-84a9-273af806571f

Alla will discuss creating new pages for

Mobile Service Chaining (KDDI): MOBILE SERVICE CHAINING

IoT Service Creation

USE CASES:

Modeling gNB/5G RAN

@Thinh Nguyenphu (Unlicensed)

@Tracy Van Brakle

Align, harmonize, reconcile various information models to ONAP model:

Expand & verify model and harmonize with the ONAP internal information & data model:

ETSI SOL001 ... 007 with ONAP internal Model

PNFD modeling (Model S/C)

5G Model (3GPP)

ORAN (WGs)

Open ROADM (reconfig optical add/drop multiplexer)

ONF

ISOMII

OTCC (Optical transport config & control)

 - Use Cases that need transport models need some model consistency.

 - Try a Use Case with extended ONAP model & real equipment.

Arch S/C

PNF POB/OB Flow

Use Case Realization Call: April 17, 2019

Use Case Realization Call: April 17, 2019

Use Case Realization Call: April 17, 2019

Arch S/C Information Flows:

Dublin ONAP Information Flows

New Information flow for Preonboarding/Onboarding xNF packages/resources.

ARCHCOM: InfoFlow - RunTime Config DB Information Flow

A&AI - Model Browser

@James Forsyth

Modeling S/C decompose the A&AI data model

A&AI developer Model Browser

NEXT / UPCOMING Presentation

Edge Deployment

@Ramki Krishnan

Ramki will be presenting on Edge Deployments in upcoming meetings (contacted)

O-RAN Modeling & alignment with ONAP

@Tracy Van Brakle

work with Open RAN alliance availability of 3GPP baseline (that vendor & operators agreed upon) add to ONAPs information model and expand existing management I/F for CM management.

want to plug them into ONAP and facilitate the 5G and other use cases working these open I/F specifications. For El Alto WG-1,3,6. Configuration management NetConf YANG specification derived from info model aligned w/ 3GPP RM & existing 3GPP info-model. Papyrus. Which 5G U/C good candidates verification w/ evolving model. PNF PnP/OOF?

Near Real Time RIC. WG-4 open Front Haul.

In PCI/SON U/C - the SDN-R Interaction w/ RAN simulator is Netconf/YANG based. In R5 we could see what parts of the model would come from ORAN.

Attributes similar with LTE. 5G Architecture evolution.

Audio Only (M4A)

Zoom_0 (MP4)

Playback (M3U)