You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Use Case Authors:

China Mobile, Huawei, VDF

NOTE: More participants are welcome.


Description:

Business Driver:

It is CMCC's strategy to realize big connection and provide a high-speed, flexible and intelligent service for high-value customers. Furthermore, CMCC also plans to provide instant, flexible VPN service for SMB companies.
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. Scenarios includes 'SOTN only', SD-VAN and international private line. But at present, 'SOTN only' is at our 1 priority, which is called Phase1 in the following.

Three phases in the whole plan:

  • PHASE1: Combine SOTN with ONAP, to manage and orchestrate services automatically.
  • PHASE2: Take both SOTN and SD-VAN into account, and combine them with ONAP.
  • PHASE3:  Build up the international private line, to realize the connection between ONAPs.

Specific sub-use cases are:

  • Service onboarding
  • Service configuration
  • Service termination 
  • Auto-scaling based on  fault and performance (stretch goal)
  • fault detection and auto-healing (stretch goal)
  • data correlation and analytics (stretch goal)



Topology Diagram


Work Flows

Workflow in Phase1:


Brief description:

After the ONAP brought in, users can forward client service via a unified customer self-service portal. ONAP orchestrator will send out channel built request to SOTN Controller after checking the service request and OTN resource state. Then a private channel is built. Domain controller will finish resource configuration on the basis of ONAP request.

  1. Topology Notification flow(TBD)

  2. Service Deploy Flow

  • 2.0 The user clicks the button on UUI/Portal to deploy the CCVPN service, UUI/Portal will sent the deploy request to SO.
  • 2.1 SO talk with A&AI to create the new service instance in A&AI inventory
  • 2.2 SO decompose the CCVPN service template distributed by SDC.
  • 2.3 SO call SDNC to create CPE configure resource
  • 2.4 SDNC call A&AI to create CPE configure resource instance and attach this resource instance to the service instance.
  • 2.5 SO call SDNC to configure CPE
  • 2.6 SDNC call 3rd SDN controller to configure CPE.
  • 2.7 SO call VFC to create vCPE VNF
  • 2.8 VFC create the vCPE VNF instance in A&AI.
  • 2.9 SO call VFC to instantiate vCPE VNF
  • 2.10 VFC call 3rd VNFM to deploy the vCPE.
  • 2.11 SO call SDNC to create vCPE configure resource
  • 2.12 SDNC call A&AI to create vCPE configure resource instance and attach this resource instance to the service instance.
  • 2.13 SO call SDNC to configure the vCPE
  • 2.14 SDNC call the 3rd SDN controller to configure the vCPE.
  • 2.15 SO create the VPN network resource instance in A&AI and attach this resource instance to the service instance.
  • 2.16 SO query the network access points which CPE and vCPE connects to from the inventory OSS.  This access point are the terminal point of the topology in A&AI that notified by 3rd SDN controller(Refer to the flow 1).
  • 2.17 SO call OOF to calculate the route between the topology terminal points of CPE and vCPE.
  • 2.18 OOF query the whole topology information from A&AI.
  • 2.19 OOF calculate the route for the terminal points. And return a VPN list across multi topology.
  • 2.20 SO loop the VPNs to call SDNC to instantiate the VPN instance. 
  • 2.21 SDNC call 3rd SDN controller create vpn over the domain topology.
  • 2.22 SDNC add relationship between domain topology and  the VPN instance and return the VPN instance to SO.
  • 2.23 SO call A&AI to attach the VPN instance to VPN network resource instnace.


Platform Requirements

PNF Onboard (abstract topology)

Deploy Artifacts for physical network

Cross-Operators interwork (MEF etc.)

Tenant management

Project Impact

PHASE1:

  • n  SDC    – PNF resource onboarding (include: CPE and physical network which can provide MEF EPL service and can be designed as abstract resource)

    n  SO/OOF – service orchestration & homing based on abstract topology(for the physical network)

    n  SDNC - integrated with 3rd controller, New DG for provision to CPE & physical network, sync abstractor topology for the physical network and store it into A&AI

    n  UUI      - E2E service provision(need support for tenant & site)

    n  A&AI    - DM for PNF, DM for abstract topology of physical network

    n  ESR     - external controller?OTN controller in phase 1?, external inventory OSS to provide reference between physical location information and CPE or UNI/NNI of physical network, or external link between different physical network domain(stretch goal)

    n  DCAE   - collect the event data for MEF EPL service or from PNF.

    n  VF-C/APP-C –VNF deployment & management when need

PHASE2+:

  • ESR - SD WAN controller & external OSS: inventory/order etc.
  • External API - cross operator’s service interwork
  • Policy           - E2E close-Loop for cross domain service

Priorities (TBD)

Work Commitment

  • No labels