DESCRIPTION

This page describes the evolution of CCVPN Use Case and its extended functionalities/applications. For the CCVPN base use case, please refer to CCVPN Base Use Case Page.

It is the general demand for big Operators such as CMCC and Vodafone to build high-bandwidth, flat and super high-speed OTN (Optical Transport Network) facing with the transition to digital economy and information-based society. They also want to provide  a high-speed, flexible and intelligent service for high-value customers, and an instant and flexible VPN service for SMB companies. 

Furthermore, Operators want to be able to offer International end-to-end services to their Enterprise Customers. The ability to collaborate and interwork across Carriers is of paramount importance in such scenarios.

The current SOTN has some obvious disadvantages, such as:

• Manual labor is highly needed in service scheduling and resource maintenance which is time-consuming and costly.

• With the high demand for large bandwidth in private line, the expansion to OTN is required. The network needs to be reconstructed under this condition.

• There is no bridge or platform to connect different service providers.

Also, there are urgent demands for:

• Real-time resource update.

• OTN equipment operation and scheduling for different vendors.

• Multi-constrained end-to-end route computation.

• Multi-domain end-to-end service providing.

• Multi-domain network end-to-end survivability.

• Supply SMB companies with VPN service on demand, instantly, flexibly

• Deploy VPN service by overlay mode , untouch carrier network

• “One-click open”and “One-stop”, automatically deploy enterprise VPN service

• Self-service order for client-side CPE, self-delivery client-side CPE

• Provide various value-added service on client-side SD-CPE and cloud side
  
  
  

Considering the above aspects, we plan to make a combination of SOTN and ONAP in virtue of the strong orchestration ability of ONAP, which is called CCVPN(Cross Domain and Cross Layer VPN), to realize a unified management and scheduling of resource and services, and also to deploy services automatically. OTN super controller can be realized as a module of ONAP(SDN-C). In this way, multi-domain cooperation is achieved as well as resource and service automatically providing.
In this use case, our focus is not only restricted to resource, but also services from end to end perspective. Scenarios includes 'SOTN only', SD-WAN and end-to-end cross Carrier international private line creation.

Cross Layer Support to integrate L1, L2, L3 layers. Allowing SPs to offer services across layers, and connect different domains together. L3 (IP) realized at the edge (Site). The CPE has routing capabilities, CCVPN can provision the IP VPN (L3) at the edge and also provision the E-Line services (Core network).

TOPOLOGY DIAGRAM

Open

CCVPN ENHANCEMENTS

In Release 9, one application is CCVPN updates for Intent Based Networking

The goal here is to enhance the CCVPN use-case to support Intent-based networking. Intent separates “what”(description of the desired outcome) from “how”(actual network configurations), and can be used to enable the full network automation. This requirement wants to make CCVPN offer an Intent NBI that can be used to enable the closed-loop automation of the transport network. Also, Cloud Leased Line (CLL) is another use-case which comes as an enhancement to CCVPN. In CLL, one VPN service connects an enterprise network to multiple clouds; i.e. multiple VPNs can co-exist (service-isolation, performance monitoring).

CCVPN WORKFLOWS

Open

Following a successful ONAP deployment, Customers can order CCVPN services via a customer self-service portal. ONAP orchestrator will forward requests to 3^rd party SOTN Controller upon successful check of service request and OTN resource state. Afterwards, a private channel is built. Domain controller will finish resource configuration on the basis of ONAP request.

For The CCVPN use case, 4 services are designed: SOTN VPN Infra Service, SD-WAN VPN Infra Service, Site DC Service , Site Enterprise Service.

One CCVPN scenario, may contain one SOTN VPN Infra Service, more than one SD-WAN VPN Infra Services, more than one Site DC Services, more than one Site Enterprise Services. Likewise, each  SD-WAN VPN Infra Service can attach more than one site.

ROADMAP - Use Case Evolution per Release

The following table links to the development for this use case in a particular release:

PRIOR BASE PAGE

If a Prior "Base page" exists for this Use Case you can use it instead of this page or link to it.

KEY LINKS & KEY INFORMATION

The following table shows some Key Links and Key Information for this Use Case:

OVERVIEW SLIDES & PRESENTATIONS/DEMOS:

This table has overview slides of the Use Case and presentations or demos