Table of Contents

Use Cases

Use Case

Owner

Projects or functional requirements Impacted

for Casablanca

Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any)

Dependency (from/to) another project(s)

T-Shirt Size (XS, S, M, L, XL)*

Project's Impact: Test Only (TO), Code (C)

Committed (C)/Partially Committed (P) or not (N) per Impacted projects

If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)

Company Engagement

Notes

M4 Status

vFW

AT&T

HPA

All: Test Only

N/A - part of regression tests

vDNS

AT&T

HPA

All: Test Only

N/A - part of regression tests

VoLTE

China Mobile

HPA

All: Test Only

N/A - part of regression tests

vCPE

Kang Xi

HPA

All: Test Only

N/A - part of regression tests

CCVPN

LIN MENG

Chaker Al-Hakim

SO,OOF, SDNC,UUI, integration

Stretch goal:

SDC, DCAE, external API.

NOTE: No project should be code impacted by this use case.

Materials Lin Meng . Material Jianguo Zeng

All; Test

Code:

SO,OOF, SDNC,UUI

Stretch goal:

SDC, DCAE, external API, CCSDK

SO:committed,

OOF:committed (Huawei resources as required).

UUI:committed

Integration: committed

SDNC: (Huawei resources as required).

Stretch goal:

DCAE : Not committed(Huawei &CMCC plan to contribute)

SDC: Not committed

External API:(VDF & huawei plan to contribute)

CCSDK: (Huawei resources as required).

if projects not committed is just in strech goal, then we will dev based on exist features, may impact some usibiligy, but won't impact the final result.

DCAE : From discussion with Xin Miao (Huawei), this usecase requires new RESTCONF collector to be added into DCAE.This cannot be committed for R3 due to pending requirement clarification and architectural alignment besides resourcing constraint.

China Mobile, Vodafone

Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement

Status

colour	Green
title	On Track

POC Demo planned for ONS at Amsterdam

OSAM/PNF

Sumithra Bhojan

Bora Eliacik

Ryan Hallahan

SO, Portal, External API, APPC, DCAE

HPA

**NOTE: OSAM uses the PNF capability similar to 5G use case. No new development efforts were identified to support OSAM using PNF

VNFRQTS (include PNFs)

OSAM Material

All: Test Only

ATT, Turk Telecom, Swisscom

Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement

Status

colour	Yellow
title	Delayed

Not M4 Gating

No Component development required for this usecase in Casablanca

Integration testing delayed due to resource contraint.

May need to defer to Dublin

T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

...

Functional Requirements

Owner

Projects Impacted

for Casablanca

Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any)

Priority

(from SP perspective)

Dependency (from/to) another project(s)

T-Shirt Size (XS, S, M, L, XL)*

Project's Impact: Test Only (TO), Code (C)

Committed (C)/Partially Committed (P) or not (N) per Impacted projects

If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)

Company Engagement

Notes

M4 Status

HPA

Alexander Vul

VNFSDK (minor)
SDC (minor)
Policy
OOF (minor)
SO (minor)
AAI,
Multi-Cloud
VNFRQTS

HPA Enhancements (For Casablanca Release)

Orange: 2

ATT: 2

China Telecom: 2

China Mobile: 1

Verizon: 2

Vodafone: 2

VNFSDK: none

SDC: VNFSDK, VNFD model

Policy: SDC

OOF: SO, Policy, AAI

AAI: Multi-CLoud

VNFSDK: M
SDC:XS
Policy: M
OOF: S
SO: S
AAi: S/M
Multi-Cloud: M

VNFSDK (C)
SDC (TO/C)
Policy (C)
OOF (C)
SO (C/TO)
AAI (C)
Multi-Cloud (C)

Policy: Committed based on Intel providing resources

OOF: Committed

VNFSDK: Committed

SDC: committed based on Intel contribution.

SO: committed

AAI: committed based on Intel resources.

Multi-Cloud: committed

Intel
ARM
AT&T
Huawei

Change Management -
Flexible designer/orchestrator

Ajay Mahimkar

SDC, SO, VID

Link to Slide

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2

VID: on SO

SDC: on SO

SDC:XL

VID: M

Code: SO,VID,SDC

VID: Not committed (Note: VID part is "nice to have" - no dependency on VID from other projects)

SDC: committed based on Amdocs contribution

SO : Committed (with support from ATT resources)

VID: requires additional resources

AT&T, Amdocs

Change Management - traffic migration

Ajay Mahimkar

SDNC, APPC, VNFSDK

Link to Slide

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2

Code: SDNC, APPC

SDN-C: committed

APPC: Not committed

Orange: Committed

APPC: Not enough details on requirements, plus limited resources

AT&T, Orange, Intel

Change Management - 5G PNF software upgrade

Ajay Mahimkar

SO, A&AI, Ansible/EM - test only support; SDNC (SDNR)- dev to incorporate 5G PNFs

Link to Slide

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2

SDN-C: Committed

SDN-C: Will use the SDN-R sub-project capabilities

AT&T, China Mobile, Huawei

Change Management - CM scheduler

Ajay Mahimkar

OOF, VID

VID - Nice to have - the functionality can still be delivered with OOF only (scheduler would need to be invoked through CLI)

Link to Slide

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2

VID on OOF

VID: S

Code: OOF, VID

OOF: Committed

VID: Not committed

(this can still be delivered with OOF)

VID: requires additional resources

AT&T

Scaling

Closed Loop Scaling

(High Priority)

Scott Blandford

Policy, CLAMP, SO, DCAE

Link to Slides

Orange: 1

ATT: 1

China Telecom: 1

China Mobile: 1

Verizon: 3

Vodafone: 1

CLAMP: on Policy

Policy: on SO

CLAMP: M

Code: SO, CLAMP, Policy

Test: DCAE

CLAMP: Committed with risks (dependency on Policy)

Policy: Committed with risks (TBD)

SO: Committed

DCAE: Committed

AT&T

Status

colour	Green
title	On Track

All code has been or will be submitted

Scaling

Beijing Improvements

(High Priority)

Scott Blandford

APPC, SDNC, SO, AAI, VID

VID: on SO

APPC: on SO

VID: XS

AAI: XS

Code: APPC, SDNC, SO, AAI

AAI: Committed

APPC: Committed

SDNC: Committed

SO: Committed

VID: Committed

AT&T

Status

colour	Green
title	On Track

All code has been or will be submitted

(VID is having issues with test environment)

Scaling

Controller_Topic_ID

(Medium Priority)

Scott Blandford

SO

Code: SO

SO: Committed

AT&T

Status

colour	Green
title	On Track

All code has been or will be submitted

Scaling

Homing and Capacity Check

(Low Priority)

Scott Blandford

Multi-VIM, OOF, SDNC, SO

OOF: on Multicloud and Policy

OOF: S

Code: OOF, SO, SDNC, Multi-VIM

OOF: Partially Committed

OOF: Resource issue if R2 solution needs to be extended for new policy constraints.

AT&T

Pushed to Dublin

5G/PNF

Plug and Play

Benjamin Cheung

Vimal Begwani

Shekar Sundaramurthy

SDC, SO, SDN-C, A&AI, CDT, Modeling, VID, DCAE, DMaaP

Link to Slide

Orange: 2

ATT: 1

China Telecom: 3

China Mobile: 1

Verizon: 1

Vodafone: 2

VID: on SO

VID: S

AAI: XS? need clarification on what's expected

OOF: No impact

Code: VID

Test Only: SDC

Code : DCAE

VID: Committed based on Nokia's contribution

SDNC: committed

SO: Committed (with resources from Nokia)

SDC: support based on current sdc capabilities from Beijing.

APPC: No impact

AAI: No code change, only modeling changes

OOF: No impact

DCAE: committed

DMaaP: committed

APPC: Per review of slides, does not appear to be anything specific for APPC in Casablanca. Items mentioned are more longer term, roadmap items

AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs

OOF: Additional information required on policies required for PNF placement

DCAE: Committed based on Nokia's contribution on PRH

AT&T, Nokia,

5G/PNF

Software Version Reporting

Vimal Begwani

Shekar Sundaramurthy

CCSDK, SDN-C

Link to Slide

CCSDK: committed

SDN-C: committed

AT&T

A&AI and SDC support has been developed. Usage in the 5G Software Upgarde Use Case is pushed to Dublin

5G/PNF

Lifecycle Management Support

Vimal Begwani

Shekar Sundaramurthy

SO, A&AI, Ansible/EM - test only support. SDNC (SDNR) dev to incorporate 5G PNFs

Link to Slide

OOF: Committed

SDN-C: Committed

Will address this via Change Management

AT&T, China Mobile, Huawei

5G/performance Analysis and Optimization

High Volume and RT Data Collection of PM

Benjamin Cheung

Vimal Begwani

Shekar Sundaramurthy

DCAE, DMaaP, ~~SDN-R,~~

Link to Slide

Orange: 2

ATT: 2

China Telecom: 1

China Mobile: 3

Verizon: 3

Vodafone: 3

DCAE: on DMAAP (native Kafka support)

OOF: M

DCAE: L

code change: OOF

Code : DCAE

CCSDK: committed

SDN-C: committed

OOF: No Impact

DCAE: Committed (based on Nokia contribution) with dependency risk

OOF: Limited resources

AT&T, Nokia,

DCAE: Edge deployment support for R3, DDS-VES and new analytic platform (flink) not committed due to resource constraint

5G/performance Analysis and Optimization

Bulk PM

DCAE, DMaaP

DCAE: on DMAAP-DR

DCAE:L

code change: DMaaP

Code change: DCAE

DCAE: DataFileCollector- Committed (based on Ericsson Contribution) with dependency risk

PMMapper - Partial Commit (Based on Ericsson contribution) + dependency risk – Not a hard requirement

DCAE: Dependency on DMAAP-DR + PMMapper (Stretch goal)

AT&T, Ericsson

5G/performance Analysis and Optimization

Optimization Framework Enhancements (Placement, Formulation, Solving)

OOF

OOF: M

code change: OOF

OOF: Committed to SON

AT&T, Nokia, Reliance Jio

Status

colour	Green
title	On Track

All code has been or will be submitted

~~5G/Network slicing~~

~~Vimal Begwani~~

~~Shekar Sundaramurthy~~

~~Benjamin Cheung~~

Withdrawn from Casablanca release by the requirement owner

Orange: 3

ATT: 3

China Telecom: 1

China Mobile: 2

Verizon: 2

Vodafone: 3

Centralized Representation and Consistent ID of Cloud Regions,

Plan B, Phase 1: Centralized Representation of Cloud Regions

Bin Yang

SO, Integration

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

Orange: 1

ATT: 2

China Telecom: 2

China Mobile: 3

Verizon: 1

Vodafone: 1

code :

SO, Integration

SO: committed based on Intel's contribution

Integration: committed

To align MVP, propose alternative action plan B: break this requirement into 3 phases.

Phase 1 is to centralize the representation of cloud regions;

Phase 2 is to apply consistent ID across all related ONAP projects.

Phase 3 is to correlate and align dcaeLocation to AAI's cloud region. This phase requires further discussion, hence not listed here.

Note on "Intel's contribution": This is the synergy effort with HPA, no further special changes needed here. hence this can be deemed as a dependency on HPA's impact on SO.

SO: will be ready to test soon.

Integration: Not started yet.

Centralized Representation and Consistent ID of Cloud Regions,

Plan B, Phase 2: Consistent ID of Cloud Regions

Bin Yang

SO,VID,SDNC,OOF,VFC, UUI,MultiCloud.

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

Orange: 1

ATT: 2

China Telecom: 2

China Mobile: 3

Verizon: 1