Versions Compared

Old Version 27

changes.mady.by.user jianguo zeng

Saved on

compared with

New Version Current

changes.mady.by.user LIN MENG

Saved on

Key

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

...

China Mobile, Huawei, VDF, ZTE, VMWare

NOTE: More participants are welcome.

...

It is the general demand for big operators 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 privide  a provide  a high-speed, flexible and intelligent service for high-value customers, and an instant and flexible VPN service for SMB companies. 

Furthermore, Operators want to be able to offer International end-to-end services to their Enterprise Customers. The ability to collaborate and interwork across Carriers is of paramount importance in such scenarios.

The current SOTN has some obvious disadvantages, such as:

...

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 perspective. Scenarios includes 'SOTN only', SD-VAN and international WAN and end-to-end cross Carrier international private line . But at present, 'SOTN only' is at our 1 priority, which is going to be executed in Phase1 in the following.

...

creation. Priorities are described in the following sections.

Function specifications include:

  1. Physical network onboarding in ONAP 
  2. Cross-domain orchestration (multiple physical networks) : include route calculation based on abstract topology
  3. Cross operator end-to-end service provisioning
  4. Closed-loop reroute for Cross-domain service

 Priorities in the whole plan:

  • Priority1Priority 1: Combine SOTN with ONAP, to manage and orchestrate services automatically.
  • Priority2:  SD-WAN controller is added in this phase to realize cross Layer VPN services.
  • Priority3:  Priority 2: Cross-domain E2E Orchestration.
  • Priority4Priority 3:  Build up Create the international private line , to realize the connection between ONAPs(ONAP instances interconnection and interwork).
  • Priority 4:  SD-WAN controller is added to realize cross Layer VPN services.

Action Phases:

  • Phase1: SOTN Orchestration
    • Single Domain
    • Multiple Domains
  • Phase2: Cross Carrier Service Creation (ONAP interworking)
  • Phase 3: + SD-WAN Phase2: ONAPs Connectionservice Creation

Specific sub-use cases are:

  • Service onboardingand resource on-boarding
  • Service configuration
  • Service termination 
  • Self service addaption adaptation (Bandwidth on demand  to be added)
  • Auto-scaling based on  fault and performance (stretch goal)
  • fault detection and auto-healing (stretch goal)
  • data correlation and analytics (stretch goal)

Overall Topology Diagram

Work Flows 

Phase1:


Brief

Short description

...

After the ONAP brought in, users can forward client service via a unified Following a successful ONAP deployment, Customers can order CCVPN services via a customer self-service portal. ONAP orchestrator will send out channel built request to SOTN Controller after checking the forward requests to 3rd party SOTN Controller upon successful check of service request and OTN resource state. Then 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.



  1. Topology Notification flow
    Image Removed    Image Added

    1.0 3rd SDN controller notify the single domain topology to SDNC.
    1.1 . Register the 3rd party SOTN Controller to ESR.
    2. ESR trigger a 3rd Controller registered event to Dmaap.
    3. SDNC subscribe the event and this event notified .
    4. SDNC synchronize the topology from 3rd SOTN controller.
    5. SDNC analyse the data from 3rd SDN controller.  Get the nodes, links, terminal points of the topology.
    16. 2 SDNC call A&AI to create the nodes, links terminal points to save the topology.
          Note: For multi 3rd SDN controllers, there will be several topologies notified.  The links across the domain topology should be discovered or created by ONAP. 

  2. SOTN VPN Infra Service Deploy Flow
    Image Removed
  • 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 decompose the CCVPN service template distributed by SDC.
  • 2.2 SO calls A&AI to create the new service instance in inventory
  • 2.3 SO calls SDNC to create CPE configure resource
  • 2.4 SDNC calls 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.

3. Service Design Flow

Image Removed

  1. Image Added
  • 1. UUI create SOTN VPN Infra Service 
  • 2. SO create service instance to A&AI
  • 3. SO decompose the service template.
  • 4. SO allocate the resources needed by cross ONAP deploy. 
  • 5. SO call the East/West APIs of ONAP of service provider partner, to create the service in the partner side.
  • 6. SO create SPPartner resource information in A&AI. this will maintain the service instance uuid from the partner side.
  • 7. SO call SDN-C to create SOTN connectivity resource.
  • 8. SDN-C create SOTN connectivity resource instance in A&AI.
  • 9. SO call SDN-C to activate SOTN connectivity resource.
  • 10. SDN-C call 3rd party SOTN controller to create SOTN VPN instance if it is needed. For EPLine/EVPLine ,this operation is not needed here. For EPLAN/EVPLAN, it is needed to create a VPN with no UNIs in the 3rd SOTN controller.
  • 11. SDN-C call A&AI to create SOTN VPN Instance, the instance will be related to VPN resource instance.

3. SD-WAN VPN Infra Service Deploy Flow

Image Added

  • 1. UUI create SD-WAN VPN Infra Service 
  • 2. SO create service instance to AAI
  • 3. SO decompose the service template.
  • 4. SO allocate the resources needed by cross ONAP deploy. 
  • 5. SO call the East/West APIs of ONAP of service provider partner, to create the service in the partner side.
  • 6. SO create SPPartner resource information in A&AI. this will maintain the service instance uuid from the partner side.
  • 7. SO call SDN-C to create SD-WAN connectivity resource
  • 8. SDN-C call AAI to create SD=WAN connectivity resource instance
  • 9. SO call SDN-C to activate the SD-WAN connectivity resource
  • 10. SDN-C call 3rd party SD-WAN controller to create the SD-WAN VPN instance.
  • 11. SDN-C save the SD-WAN VPN instance information from 3rd party SD-WAN controller to A&AI.
  • 12. SO call SDN-C to create internet cloud access resource.
  • 13. SDN-C call A&AI to create internet cloud access resource instance.
  • 14. SO call SDN-C to activate the internet cloud access resource.
  • 15. SDN-C call 3rd SD-WAN controller to create internet cloud access.

3. Site Enterprise Service Deploy Flow

     Image Added

  • 1. UUI create Site Enterprise Service 
  • 2. SO create service instance to A&AI
  • 3. SO decompose the service template.
  • 4. SO allocate the resources needed by cross ONAP deploy. 
  • 5. SO call the East/West APIs of ONAP of service provider partner, to create the service in the partner side.
  • 6. SO create SPPartner resource information in A&AI. this will maintain the service instance uuid from the partner side.
  • 7. SO Check the site location to check if it is locate in local ONAP.
  • 8. SO call SDN-C to create device PNF resource
  • 9. SDN-C call A&AI to create device PNF resource instance
  • 10. SO call SDN-C to activate the device PNF resource
  • 11. SDN-C call 3rd party SD-WAN controller to create device of the site.
  • 12. SDN-C create device instance in A&AI.
  • 13. SO call SDN-C to create site resource.
  • 14. SDN-C call A&AI to create site resource instnace.
  • 15. SO call SDN-C to activate the site resource.
  • 16. SDN-C call 3rd SD-WAN controller to create site.
  • 17. SO call SDN-C to create SOTN VPN attachment resource.
  • 18. SDNC call AAI to create SOTN VPN attachment resource.
  • 19. SO query the network access point information from inventory OSS of SP.
  • 20. SO call SDN-C to activate the VPN attachment resource. SDN-C will get the existing VPN Infra Service information and the VPN attachment resource , to get the L1/L2 connectivity needed.
  • 21. SDN-C call OOF to do L1/L2 connectivity route calculate between multi 3rd SOTN controller topologys.
  • 22. OOF will query AAI for the whole topology  notified by multi SOTN controllers.
  • 23. OOF do route calculate,OOF return the route informations for L1/L2 connectivity VPNs on each SOTN controller.
  • 24. SDN-C will loop the VPNs , and create the SOTN VPN instance to A&AI. This will also upate the VPN Infra service instance.
  • 25. SDN-C call 3rd SOTN controller to create VPN over topology.
  • 26. SDN-C add relationship between the VPN instance and the topology.
  • 27. SO call SDN-C to create SD-WAN VPN attachment resource
  • 28. SDN-C call A&AI to create SD-WAN VPN attachment resource instance.
  • 29. SO call SDN-C to activate the SDN-WAN VPN attachment resource.
  • 30. SDN-C call SD-WAN controller to attach the site to the SD-WAN VPN instance.
  • 31. SO call SDN-C to create WAN port resource.
  • 32. SDN-C call A&AI to create WAN port resource instance.
  • 33. SO call SDN-C to activate WAN port resource.
  • 34. SDN-C call SD-WAN controller to create WAN port for the Site.
  • 35. SO call SDN-C to create LAN port resource.
  • 36. SDN-C call A&AI to create LAN port resource instance.
  • 37. SO call SDN-C to activate LAN port resource.
  • 38. SDN-C call SD-WAN controller to create LAN port for the Site.

4. Site DC Service Deploy Flow

Image Added

  • 1. UUI create Site Enterprise Service 
  • 2. SO create service instance to A&AI
  • 3. SO decompose the service template.
  • 4. SO allocate the resources needed by cross ONAP deploy. 
  • 5. SO call the East/West APIs of ONAP of service provider partner, to create the service in the partner side.
  • 6. SO create SPPartner resource information in A&AI. this will maintain the service instance uuid from the partner side.
  • 7. SO Check the site location to check if it is locate in local ONAP.
  • 8. SO call VF-C/APP-C to create device VNF resource
  • 9. VF-C/APP-C call A&AI to create device VNF resource instance
  • 10. SO call VF-C/APP-C to activate the device VNF resource.
  • 11. VF-C/APP-C call the 3rd party VNFM to deploy VNF.
  • 12. VF-C/APP-C call A&AI to create VNF instance.
  • 13. SO call SDN-C to activate the device VNF resource
  • 14. SDN-C call 3rd party SD-WAN controller to create device of the site.
  • 15. SDN-C create device instance in A&AI.
  • 16. SO call SDN-C to create site resource.
  • 17. SDN-C call A&AI to create site resource instnace.
  • 18. SO call SDN-C to activate the site resource.
  • 19. SDN-C call 3rd SD-WAN controller to create site.
  • 20. SO call SDN-C to create SOTN VPN attachment resource.
  • 21. SDNC call AAI to create SOTN VPN attachment resource.
  • 22. SO query the network access point information from inventory OSS of SP.
  • 23. SO call SDN-C to activate the VPN attachment resource. SDN-C will get the existing VPN Infra Service information and the VPN attachment resource , to get the L1/L2 connectivity needed.
  • 24. SDN-C call OOF to do L1/L2 connectivity route calculate between multi 3rd SOTN controller topologys.
  • 25. OOF will query AAI for the whole topology  notified by multi SOTN controllers.
  • 26. OOF do route calculate,OOF return the route informations for L1/L2 connectivity VPNs on each SOTN controller.
  • 27. SDN-C will loop the VPNs , and create the SOTN VPN instance to A&AI. This will also upate the VPN Infra service instance.
  • 28. SDN-C call 3rd SOTN controller to create VPN over topology.
  • 29. SDN-C add relationship between the VPN instance and the topology.
  • 30. SO call SDN-C to create SD-WAN VPN attachment resource
  • 31. SDN-C call A&AI to create SD-WAN VPN attachment resource instance.
  • 32. SO call SDN-C to activate the SDN-WAN VPN attachment resource.
  • 33. SDN-C call SD-WAN controller to attach the site to the SD-WAN VPN instance.
  • 34. SO call SDN-C to create WAN port resource.
  • 35. SDN-C call A&AI to create WAN port resource instance.
  • 36. SO call SDN-C to activate WAN port resource.
  • 37. SDN-C call SD-WAN controller to create WAN port for the Site.
  • 38. SO call SDN-C to create LAN port resource.
  • 39. SDN-C call A&AI to create LAN port resource instance.
  • 40. SO call SDN-C to activate LAN port resource.
  • 41. SDN-C call SD-WAN controller to create LAN port for the Site.


5. Closed Loop Flow 

Image Added

  • 1. SDC/CLAMP Portal design and activate policy.
  • 2. SDC/CLAMP config and activate the policy.
  • 3. SDC/CLAMP distribute the DCAE config.
  • 4. SDC/CLMAP distribute the alarm correlation rules to Holmes.
  • 5. 3rd party SOTN controller report link down alarm to DCAE
  • 6. DCAE will do data cleaning and filtering for the alarms
  • 7. DCAEk keep track the datas.
  • 8. Holmes do analysis for the alarms.
  • 9. Holmes notify the reroute event.
  • 10. Policy matching the reroute rules.
  • 11. Policy call SO to delete the old services and create the new services. For the creation flow, a variable route will be recalculated.

5.1 DCAE Flow in Close Loop (with better diagram later on)

      Image Added

  1. RestConf Collector (RC)subscribes for remote failure alarm to SOTN Controller (SC) 
  2. RC requests to set up a long term tunnel with the 3rd party SC
  3. SC responses with OK upon successful tunnel setting
  4. SC pushes service route status data to the collector
  5. RC receives alarm data, converts it into JSON format and publishes on DMAAP with topic of ROUTE_ALARM_OUTPUT
  6. UVA consumes the alarm message
  7. UVA requests the RestConf2VES mapping
  8. UVA converts json alarm into VES  event
  9. UVA publishes the VES event on DMAAP for further correlation   

6. Service Design Flow

Image Added

  • 1. Design the service in SDC portal
  • 2.
  • 3.0 Design the service in SDC portal
  • 3.1 SDC distribute the service information to SO
  • 3. 2 SDC distribute the service network information to SDNC
  • 34. 3 SDC distribute the service model information to AAI
  • 35. 4 SDC distribute the service VNF information to VFC/APPC.

...

Tenant management

Project Impact

Image RemovedImage Added

PHASE1:

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

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

    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

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

    A&AI    - DM for PNF, abstract topology of physical network, use travel query tor all resource related to special service

    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)

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

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

  • External APIs   - 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)

  • Modeling       - the modeling for PNF and abstract topology for physical network

...

Location

PNFs

Intended Provider

PNF CSAR

Site

CPE

Huawei, ZTE


Physical network

OTN network element

Huawei, ZTE






VNF:

VNF: vCPE or similar VNF/APP that need to deploy in site (the enterprise or the Datacenter).

NFVI+VIM: provide infrastructure to run VNF/app.

Location

VNFs

Intended VNF Provider

VNF CSAR

enterprise

vCPE

Huawei?ZTE





Datacenter









NFVI+VIM:

Utilize vendors NFVI+VIMs in the ONAP platform.

Location

NFVI+VIMs

Intended VNF Provider

Note

Datacenter


Huaiwei, VMWare






Work Commitment

< identify who is committing to work on this use case and on which part>

Work Item

ONAP Member Committed to work on CCVPN

Modeling

CMCC, VDF, Huawei, Verizon

SDC

Huawei

SO

Huawei

OOF

Huawei

SDN-C

CMCC, Huawei

UUI

CMCC, Huawei

DCAE

Huawei

VF-C

Huawei

A&AI

Huawei

External API

Huawei

...