DESCRIPTION
The CCVPN (Cross-layer Cross-domain VPN) use case enables ONAP to offer various connectivity services provisioned on physical networks. While CCVPN itself being an independent use case, it can also be used to support/enable other use cases. For example, CCVPN can be used in the the E2E Network Slicing use case, providing the Transport Slicing serivce (i.e., acting as the TN NSSMF). The page describes the basic applications and comon functionality of CCVPN. Extended CCVPN applications, such as Transport Slicing and Intent-based Cloud Leased Line, are captured in .
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.
Service Provisioning Categories
CCVPN assumes the SP provides two types of service functions 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 customer, 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.
The following shows another architecture view
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 | Use Case did not exist yet |
| R4 Dublin | CCVPN Use Case (Dublin) |
| R5 El Alto | MAINTENANCE RELEASE (No Use Case work) |
| R6 Frankfurt | CCVPN Use Case in Frankfurt Release |
| R7 Guilin | https://docs.onap.org/projects/onap-integration/en/latest/docs_CCVPN.html |
| R8 Honolulu | https://docs.onap.org/projects/onap-integration/en/latest/docs_CCVPN.html |
| R9 Istanbul | No New Development for this Use Case |
| R10 Jakarta | No New Development for this Use Case |
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:
| Topic | Description |
|---|---|
| Overview Slides | |
| Overview Presentation | |
| Demo |