when topology is any-to-any; leaf resource-route-target-hub { type uint32; //when topology is hub-and-spoke; leaf resource-route-target-spoke { type uint32; //when topology is hub-and-spoke; list vrf { key "resource-vrf-id"; - leaf resource-vrf-id type uint32; leaf resource-route-distinguisher { type uint32; leaf resource-import-route-target { type uint32; Software-Defined Networking leaf resource-export-route-target type uint32; list site { key "site-id" ; leaf site-id { type uint32; leaf site-interface { type string; leaf site-13-routing type string ; } //list-site } //list-vrf } // list-pe } // vpn-pe container } // module vpn-network 6.7 NETWORK CONTROLLER AND ORCHESTRATION USE-CASE EXAMPLE: CUSTOMER REQUESTING VPN SERVICE Figure 6.4 (and the associated description) shows an end-to-end use case of what happens when a customer requests a five-node VPN service. 1. Business support system (BSS) submits request to master orchestration and management function (OMF) service orchestration for 5 VPN sites for customer X. 2. OMF requests 5 VPN sites for customer X to service controller (SC), which supports VPN. Customer Business/Operations Request Interface Service Orchestrator Function Cloud Service/Resource Orchestrator Function Network Service Network Resource Controller Function Controller Function Cloud Ntwrk Customer Specific Ctlr Fnct Vendor Nodal Controller Computer Computer WAN PNF Network LAN Network Compute Storage FIGURE 6.4 Customer request for VPN service. Building the Network of the Future 3. VPN service controller (VPN-SC) requests from network controller (NC) if network resources are ready. 4. NC configures the set of PNFs/VNFs to support service a. For PNF-goes directly to the WAN PNF to configure b. For VNF-goes to infrastructure orchestration and control (IO&C) to create the con- tainer (compute, storage) for the VNF application C. NC requests a VNF from the IO&C with the specific location, policy IO&C spins up compute, storage based on VNF container policies, and loads/starts up the VNF e. IO&C te