Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DESCRIPTION

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.

Image Added

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

Image Addedxx

ROADMAP - Use Case Evolution per Release

...