...

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

Image Added

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

...