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

Migration of existing PNF PnP sub-workflows to a new BB approach (probably we will be creating 4-5 new BBs).

VID Impact:

Within “old” VID macro orchestration pages, a special field to provide a pnf-id parameter (shall be actually called “correlationID” or “PNF correlationID”) has been displayed under the following conditions:

1. Service Model contains a PNF resource type.
2. Service type = vCPE

When we migrate to BB approach, we`d keep the possibility to provide this parameter to the SO API call as input.

How this will change with SO/BB approach, and with new VID GUI targeted at macro (GR) flows – we`d see exactly, after we execute some tests with VID.

We`d have to check, what capabilities and conditions could be applied to display and process this “PNF Correlation ID parameter”.

Can the same BBs could be re-used in “standard” vCPE use-case.

We`re looking at a generic solution, and we`d probably display this additional field, when we figure out, that there is a PNF resource used in a Service Model.

SUMMARY: Can Commit. Nokia will be helping to developing.

Will Generic Artifact Browser (existing SDC design studio, GAB) be available in VID? Run Time Usage.

SUMMARY: Let's have offline discussion with Damian to answer question. Former user (Deleted)

Will Generic Artifact Browser (SDC design studio, GAB) be available in VID?

SUMMARY: (discuss)

Display VID updates to support extensions

Not listed in Wiki, need to discuss w/ Ittay.

Onboarding SON functionality - Looking at feasibility of existing life cycle of U/C. SON mS triggered by RAN for Config. changes; onboarding to DCAE manually can this SON handler be designed by SDC and then SONaaS automated. No commitment for R6. If this is so, then there might be impact to VID. If designed by VID then modeling CLAMP.

NEW Cell Assignment - SON U/C cells are existing already configured; new CELL addition; ONAP may want to assigned PCI to new cell; PCI Assignment; if VID is involved.

QUESTION: is Swami committed, will this work be committed?

SUMMARY: Might be changes, still designing the U/C. U/C commitment. Probably in Oct. will have more clarity. 

how will slice be instantiated? SO (Seshu) you will require - using svc order API; reach SO through API/external API OSS-BSS client; if you want this external API would be VID change. otherwise need externalAPI w/ OSS-BSS client.

How would demonstrate/demo the test? Having VID is probably better choice. From VID perspective ; otherwise new Client

SUMMARY: To demo the Network Slice U/C in R6 would want to invoke via VID. POTENTIAL IMPACT. INVESTIGATE.

5G / RAN ORAN 3GPP Standards Harmonization

Display of RunTime DB information; Design Time view of Run Time DB info.

No Impact.

no direct impact; depends on the CFS part - SO handles CFS & RFS there may be VID impact.

VId will interact w/ Policy (in the future)

SUMMARY: Potential Impact. Still investigation.

Listed as Impact on R6 Release Page

But No impact stated on Wiki.

With scaling, Ittay & Scott has discussed. For R6 probably no impact. Multiple instances (nice to have in R6) but might be a very large change in VID. Does help many providers.

SUMMARY: Listed as a stretch goal for R6; if not put on road-map for a future release.

GUI/CLI based configuration of stack ?? (will this be VID change??)

SUMMARY: Investigate

IMPACT (but not described)

SUMMARY: Ittay will follow-up w/ Nishi.