DESCRIPTION
This page describes the evolution of CCVPN Use Case and associated Use Casesits 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.
...
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
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
Following a successful ONAP deployment, Customers can order CCVPN services via a customer self-service portal. ONAP orchestrator will forward requests to 3rd 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.
...
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:
| RELEASE | Link to Use Case |
|---|---|
| R1 Amsterdam | Use Case did not exist yet |
R2 Beijing | Use Case did not exist yet |
| R3 Casablanca | CCVPN(Cross Domain and Cross Layer VPN) USE CASE |
| R4 Dublin | Use Case did not exist yet |
| R5 El Alto | MAINTENANCE RELEASE (No Use Case work) |
| R6 Frankfurt | Use Case did not exist yet |
| R7 Guilin | Use Case did not exist yet |
| R8 Honolulu | Use Case did not exist yet |
| R9 Istanbul | R9 CCVPN Support for Intent-Based Networking |
| R10 Jakarta |
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:
| Topic | Description |
|---|---|
| Key Use Case Leads | |
| Key Use Case Contacts | |
| Meetings Register & Recordings |
OVERVIEW SLIDES & PRESENTATIONS/DEMOS:
This table has overview slides of the Use Case and presentations or demos
...