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. 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 RemovedImage Added

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

...