Use Case Authors:

China Mobile, Vodafone, Huawei, ZTE, VMWare, Intel, WindRiver.

NOTE: More participants are welcome.

Overview

Recap for Casablanca 

In Casablanca release, we propose CCVPN(Cross Domain and Cross Layer VPN) use case, in which scenario if a customer wants to set up a VPN from Beijing to London, we can use ONAP to stretch such a VPN service that is cross operator, cross domain and cross layer.
cross operator: the VPN service could be stretched between two ONAPs.
cross domain: a VPN service is cross diffrent OTN domains which is controlled by different 3rd parties
cross layer: the VPN service can be l1,l2,l3 or any composition of these layers, eg: a VPN service that is cross l2 and l3

From an Operator's perspective, it is important to introduce the capability to manage the performance of the CCVPN End-to-End service (especially when it spans across different Operators).  The ultimate goal of this use case is, by taking advantage of the strong orchestration ability of ONAP, to automatically create and deploy a cross operator, cross domain (SOTN + SD-WAN), cross layer (L1, L2, L3) end to end VPN and update the service dynamically.
Main functions in this use case include automatically design of end to end service, creation of end to end service, cross-domain resource cooperation, global rerouting.
We testified this possibility in C release and realized functions like topology discovery, simple service creation, as well as back-up link switch in closed loop.

Planning for Dublin

In Casablanca, the basic CCVPN usecase demonstrated ONAP's capability in designing and creating an end-to-end VPN service across operator domains.

In realistic CCVPN service deployment, the customer may want to add two sites in Shanghai and Wuhan onto the original service due to their business needs. Customers also have the need to do some modifications on the existing service, eg: to change the bandwidth or to build up a vFW in the VPN.

Therefore, in Dublin release, we would like to extend the scenario of CCVPN use case to include enhancements in the following aspects:

1. Service Change Management, to allow the customer to dynamically add more branch sites or value-added services (e.g. vFW) on demand to individual site onto their running CCVPN service instances.
2. Intelligent Bandwidth on Demand, to allow third party analytics applications to trigger ONAP close loop for adjusting the running CCVPN service instances (e.g. the bandwidth between specified sites).

User Stories

Service Provisioning Categories

In Dublin, CCVPN assumes the SP provides two types of service componts to its enterprise customer for selection, including: 

• Basic VPN service between sites, where the number of sites and the bandwidth among them could be adjusted dynamically.
• Value-Added services which could be part of the intial service procurement before its creation or added on demand to a running service instance.

To best represent the common requirements for potentially huge number of value-added services that might be interesting to the cutomer, two are selected for CCVPN demonstration, including 

• vFW, which demonstrate the requirements for chaining another traffic handling function into the user plane, and
• intelligent surveillance application, which demonstrate the requirement for distributed deployment architecture in the user plane and also the close loop automation integration in the control plane.

Network Topology Assumptions

A network hierachy of at least two layering of DCs  are assumed in this usecase, including:

• the core DC, where the ONAP central is running, and
• the edge DCs, where the virtual functions/applications that are deployed near the customer's sites are running.

For the intelligent surveillance application, which is a specific value-added service, once intialized,

• its centralized monitoring portal is deployed at the edge DC near the enterprise HQ, and
• the AI applications for collecting both the vioce/video monitoring and anormaly recognition, are deployed in a distributed fashion to the edge DCs that are near the specific site(s) under surveillance.

User Stories

1. Service Procurement (SP)

2. Service Instantiation (SI)

3. Service Change (SC)

   1. SC1: Adding a new site

   2. SC2: Adding a new value-added service 

4.  Close Loop Intelligent Suveillance (IS)

Gap Anaysis and Functional Requirements

Implementation Proposals  

Design Time Workflows

• VNF onboarding

• Service Template Design

• Service Change Workflow Design

• Bandwidth on Demand Policy Design 

Run Time Sequence Diagram

• Service Procurement (SP)

• Service Initialization (SI)

• Service Change (SC)

  1. SC1: Adding a new site

  2. SC2: Adding a new value-added service 

• Close loop Intelligent Suveillance (IS)

Current Situation

In Casablanca release, the CCVPN service is created by mean of separate multiple Service Orders via TMF 641, with one service orderItem for each of the services that make up the CCVPN connectivity Service. (Note -the UUI in Casablanca makes separate calls to SO, i.e. does decomposition but without Service Orders)

The complete removal of the CCVPN Service would involve the Portal/UUI making multiple separate Service Orders with one orderItem, each with a ‘delete’ action. This because there is no E2E Service Instance that corresponds to the full CCVPN Service. 

High Priority Extensions (enhancements) in Dublin release:

Multi-site to multi-site Service Creation (Priority: Layer 3  > Layer2 > Layer1)

In an ideal implementation, the Portal shall create a single Service Order via TMF 641, with multiple service orderItem(s) for each of the services that make up the CCVPN Service.

• SDC should support create an E2E service with one service template by supporting inputs of multiple resources at the same time (instead of using multiple service templates one by one when creating an E2E service) and SO should have the capability to decompose and (eventually) delegate the nested Services.
• A&AI should maintain composite End-to-End Service Instance for CCVPN.
• Parameters for all services can be passed as one composite orderItem to External API. 

Service Change : Add or Delete a site (Priority: Layer 3  > Layer2 > Layer1):

A CCVPN End-to-End Service Change (e.g., bandwidth change), should be either triggered by the portal (as TMF 641 single service orderItem with ACTION ‘change’) or by a policy implemented to guarantee that SLS is met.

Similarly to the Service Creation, this change (or modification) should be handled by SO, which decomposes the Service Change and sends it, via External API, to the other Operator(s) in the form of PATCH service.

SO should offer Service Modification API and associated workflows to interact with SDN-C, A&AI and External API to make the required service adjustments.

Finally, SDC must be able to model the LCM Operation/Interfaces for modifications allowed on the CCVPN Service (e.g., AdjustBandwidth) so that the modification capability can be exposed through the Service Catalog.

Besides the change of service components like adding or deleting the sites, we also have the needs to add a VNF like vFW in the service or change the inputs parameters of an existing service.

Specific sub-use cases / functional requirements

• Distributes Analytics as a Service 

Additional Extensions

• E-LAN Service (EP-LAN, EVP-LAN)
• Smart Disaster Recovery(DR) for NFV
• CCVPN Service Function Chain(SFC)
• Extension for L0/L1 (Dublin) - Proposal

Priorities for Dublin

(Initial assessment)

High Priority

Medium Priority

Low Priority

*feature already proposed for Dublin release