PLATFORM TOPICS:

Controller to NF Association

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

PLATFORM TOPICS:

Data Persistency, RunTime DB

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

PLATFORM TOPICS:

Controller LCM API Evolution

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

• 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 CASE/5G:

RAN (ORAN-3GPP) Standards harmonization with ONAP

• 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 CASE/5G:

Licensing Management

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

Use case Wiki: LICENSING MANAGEMENT

USE CASE/5G:

OOF / SON

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:

BBS U/C Evolution

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://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/6088750416362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

USE CASES/5G:

PM Dictionary/FM MD GUI

USE CASES/5G:

PNF S/W Upgrade

USE CASES/5G:

Preonboarding/Onboarding

IoT Service Creation

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

USE CASES:

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, RAN)

ORAN (WGs, RAN)

Open ROADM (reconfig optical add/drop multiplexer, Optical)

ONF (Optical)

ISOMII (Optical)

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.

Presented at the 2019 June LFN DDF, titled as '5G Provisioning management service to NRM' 

Presentation scheduled for Aug 8, 2019

Architecture S/C

PNF POB/OB Flow

Arch S/C Information Flows:

Draft ONAP Information Flows

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

ARCHCOM: InfoFlow - Onboard Resource into SDC Flow

A&AI updates

TSC:

PoC Definition

TSC/USE CASES:

Test Automation Progress

Use Case Test Automation

Action Items: Use case subcommittee to reach the Dublin use case owner to provide the following information. what's the current percentage of testing automation regarding your use case and functional requirements; what will be the plan to be 100% and constraints (resources availability etc.)

Use Case Tracking Template

Need the U/C teams to fill out the Dev. Impacts.

More Generalized Use Case Template (discussed w/ Model team):

Use Case Tracking Template and Use Case Template

Wiki Page: PNF PLUG and PLAY in R6 Frankfurt

SUMMARY: R6

Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

(Spreadsheet/Use Case Team): 

SUMMARY: Needs investigation

5G / RAN ORAN 3GPP Standards Harmonization

Wiki Page: CCVPN Use Case in Frankfurt Release

SUMMARY: Needs investigation

No Impact. Modeling impact.

SUMMARY: No Impact

Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

Epic#1 - OOF/SON Enhancements

Functionality enhancement to SON Handler MS

Will also USE the CM Notify (being introduced in VES update)

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: Needs Clarification

5G / RAN ORAN 3GPP Standards Harmonization

Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP

Might have to delay. Enhancements expected from DCAE

(1) CM NOTIFICATION: Listen to CM notification (config change notification).

(2) 3GPP FAULT EVENT: how to support 3GPP fault. 3GPP fault as a separate domain; alignment with 3GPP.

(3) FILE READY - VES event, add a field for the type of file. Sub: data field collector. Can use existing fields to support this. Applicable to other types of file beyond the PM file (e.g. trace, log files) want it to be generic.

(Spreadsheet/Use Case Team): Indicates impact

Timeline - meeting held Oct 2 to align 3GPP fault event, converging on an approach; another meeting next week Oct 7+. Maybe difficult to achieve by M2/M3 (Nov 7 2019)

SUMMARY: (see CM Notify VES event)

CM notications are new impacting VES event registration & listener.

VES publications happen before components use it. VES updates need to happen before development. VES event reg & listener, FM dictionary. Modeling updates by M2. A finalized VES document might be difficult by Nov 7

IMPACTS: ORAN/ONAP Harmonization U/C, OOF/SON/PCI Use Case, and RunTime DB Use Case.

SUMMARY: DCAE commits, but wants to follow-through on the definition of the VES definitions. WARNING: M2/M3 deadline for M2/M3 Nov 7 2019. Collector change to accommodate VES

Wiki Page: Scaling Use Case (Frankfurt)

Goal: Manual and Automatic Scale In

Scale In Trigger (Priority: 2)

Support creating a Threshold Alert (TA) when capacity needs to be reduced

Send the TA to Policy 

No new functionality for scaling expected.

SUMMARY: Needs Investigation.

Wiki Page: MOBILE SERVICE CHAINING

We want close loop mechanism for service chaining operation
Policy Framework, DCAE, and Service Orchestration Project may be upgraded

SUMMARY: Need Investigation.

Wiki / PPT slide indicates no impact

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: No impact

Wiki Page: CCVPN Use Case in Frankfurt Release

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: Needs Investigation

Self Serve Control Loops - continuation from Dublin

PNF support in Control Loops - non-service Control Loops

Adding Policy Update and PEP (Policy Enforcement Point) registration with Policy for updates on Decision Policies

CLAMP would provide arbitrary blueprints to DCAE instead of SDC.

CL Event format standardization to VES

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: DCAE some things are committed. Separate requirements created.

Wiki Page: Change Management Frankfurt Extensions

(Spreadsheet/Use Case Team): No impact listed

SUMMARY:  No impact.

SUMMARY: Needs investigation

Wiki Page: K8S based Cloud region support (Continue from R4)

(Spreadsheet/Use Case Team):

SUMMARY: Needs investigation

Wiki Page: Third-party Operational Domain Manager

SUMMARY: Needs investigation