Versions Compared

Version Old Version 39 New Version 40
Changes made by

Chuanyu Chen

Chuanyu Chen

Saved on

Key

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

Use Case Authors:

...

  • Service onboarding
  • Service configuration
  • Service termination 
  • Self service addaption (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)

...

  1. Topology Notification flow


    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.
    6. 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 RemovedImage 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 FlowImage Removed

     

  • 3.0 UUI/Portal create Site Enterprise Service 
  • 3.1 SO create service instance to AAI
  • 3.2 SO decompose the service template.
  • 3.3 SO call SDNC create PNF resource
  • 3.4 SDNC call AAI to create PNF resource instance
  • 3.5 SO call SDNC to activate the PNF resource
  • 3.6 SDNC call 3rd SD-WAN controller to create device of the site.
  • 3.7 SO call SDNC to create site resource.
  • 3.8 SDNC call AAI to create site resource instnace.
  • 3.9 SO call SDNC to activate the site resource.
  • 3.10 SDNC call 3rd SD-WAN controller to create site.
  • 3.11 SO call SDNC to create VPN attachment resource.
  • 3.12 SDNC call AAI to create VPN attachment resource.
  • 3.13 SO query the network access point information from inventory OSS of SP.
  • 3.14 SO call SDNC to activate the VPN attachment resource. SDNC will get the existing VPN Infra Service information and the VPN attachment resource , to get the L1/L2 connectivity needed.
  • 3.15 SDNC call OOF to do L1/L2 connectivity route calculate between multi 3rd SOTN controller topologys.
  • 3.16 OOF will query AAI for the whole topology  notified by multi SOTN controllers.
  • 3.17 OOF do route calculate.
  • 3.18 OOF return the route informations for L1/L2 connectivity VPNs on each SOTN controller.
  • 3.19 SDNC will loop the VPNs , and create the SOTN VPN instance to AAI. This will also upate the VPN Infra service instance.
  • 3.20 SDNC call 3rd SOTN controller to create VPN over topology.
  • 3.21 SDC add relationship between the VPN instance and the topology.
  • 3.22 SDNC call SD-WAN controller to attach the site to the SD-WAN VPN instance.
  • 3.23 SDNC call SD-WAN controller to create LAN for the Site.
  • 3.24 SDNC call SD-WAN controller to create WAN for the Site.

...