V1.0 | 1©6WIND 2015 NON Network Video transcoding Pattern matching Network L2-L4 related Filtering IPSec NAT L4 load balancing Network L7 related HTTP load balancing SSL proxy Accelerations VNF Accelerator or NFVI Accelerator VNF Accelerator vRouter + NSD/VNFD/VNFFGD

V1.0 | 2©6WIND 2015 NFVI Accelerator: vRouter instead of vSwitch INF005 / 7.1.3

V1.0 | 3©6WIND 2015 NS1 descriptors NSD = { ID=NS1, VNFD={SigGW}, VNFFGD=fg1, VLD={}, vnf_dependency= {}, service_deployment_flavor={ { flavor_key=40Gbps, { constituent_vnf= { vnf_reference=SigGW, capability=100%, number_of_instances=1 } connection_point={CP1=IP} } PNFD = { ID=SmallCell, connection_point={ {ID=CP1, type=IPSec} } VNFD = { ID=SigGW connection_point={ {ID=CP1, type=IPSec}, {ID=CP2, type==IP} } VNFFGD = { ID=fg1, constituent_vnfs={SigGW}, number_of_end_points=1, number_of_virtual_links=2, connection_point={ SmallCell.CP[1-40], SigGW.CP1, SigGW.CP2, NS1.CP1 }, network_forwarding_path={nfp1} } Sig GW Core RTR LBNAT NS1 CP1 NS2 CP1 CP2 Small Cell VLD = { ID=SmallCell-SigGW connectivity_type=e-tree, number_of_endpoints=41, connection={ SmallCell.CP[1-40], SigGW.CP1 }, root_requirement=40Gbps, leaf_requirement=1Gbps } VLD = { ID=SmallCell-SigGW connectivity_type=e-line, number_of_endpoints=2, connection={ SigGW.CP2, NS1.CP1 }, root_requirement=40Gbps, leaf_requirement=40Gbps } NFPD = { ID=nfp1, connection={ {SmallCell.CP1, 1}, {SigGW.CP1, 2}, {SigGW.CP2, 3}, {NS1.CP1, 4} }, }

V1.0 | 4©6WIND 2015 NS2 descriptors NSD = { ID=NS2, vendor=etsi, version=1 VNFD={LB, NAT} VNFFGD=fg2 VLD={} vnf_dependency = {target= NAT, source=LB} service_deployment_flavor={ { flavor_key=10Gbps, { constituent_vnf= { vnf_reference=LB, capability=100%, number_of_instances=1 } constituent_vnf= { vnf_reference=SigGW, capability=100%, number_of_instances=1 } { flavor_key=40Gbps, { constituent_vnf= { vnf_reference=LB, capability=100%, number_of_instances=1 } constituent_vnf= { vnf_reference=SigGW, capability=25%, number_of_instances=4 } connection_point={CP1=IP, CP2=Internet} } Core RTR LBNAT NS2 CP1 CP2 VLD = { ID=LB-NAT-40Gbps connectivity_type=e-tree, number_of_endpoints=2, connection={ LB.CP1, NAT.CP1 }, root_requirement=40Gbps, leaf_requirement=10Gbps } VLD = { ID=LB-NAT-10Gbps connectivity_type=e-tree, number_of_endpoints=2, connection={ LB.CP1, NAT.CP1 }, root_requirement=10Gbps, leaf_requirement=10Gbps }

V1.0 | 5©6WIND NFVO receives a request to instantiate a new Network Service using the operation Instantiate Network Service of the Network Service Lifecycle Management interface. 2.NFVO validates the request, both validity of request (including validating that the sender is authorized to issue this request) and validation of the parameters passed for technical correctness and policy conformance. In case the Network Service contains multiple VNF Forwarding Graphs, policy rules might result in only a subset being valid for a given Network Service instance. 3.For each VNF instance needed in the Network Service, the NFVO checks with the VNF Manager if an instance matching the requirements exists already using the operation Query VNF of the VNF Lifecycle Management interface. If such a VNF instance exists, it will be used as part of the Network Service. 4.Optionally, NFVO runs a feasibility check of the VNF interconnection setup. Steps 3 to 5 constitute the feasibility check of the request. Step 3 consists of the following sub-steps: a.NFVO requests to VIM availability of network resources needed for the VNF Interconnection and reservation of those resources using the operation Create Resource Reservation of the Virtualised Resources Management interface. Note that some of the network connectivity between the VNFs might already exist. b.VIM checks the availability of network resources needed for the VNF Interconnection and reserves them. c.VIM returns result of reservation back to NFVO. Instantiation 1/3 Source: MANO Annex C.3

V1.0 | 6©6WIND Optionally, once the list of VNF instances to be provisioned is known and assuming it is not empty, the NFVO validates if resources are available to honour the VNF instantiation requests and if so, reserves them using the operation Create Resource Reservation of the Virtualised Resources Management interface. (procedure describe separately) 6.NFVO requests from VIM instantiation of the network connectivity using the operations Allocate Resource or Update Resource from the Virtualised Resources Management interface. Note that some of the network connectivity between the VNFs might already exist and might only need to be extended. 7.VIM instantiates the connectivity network needed for the Network Service. 8.VIM acknowledges completion. 9.Assuming the list of VNF instances to be provisioned is not empty, the NFVO instantiate the new VNF instances needed. This is done by calling the “Instantiate VNF” request using the operation Instantiate VNF of the VNF Lifecycle Management interface as illustrated in section 7.2, VNF Instantiation. 10.Once all VNF instances are available and for the VNFs not already connected, NFVO requests VIM to connect them together using the operations Allocate Resource or Update Resource from the Virtualised Resources Management interface. It includes a.Requesting VIM to connect external interfaces of each VNFs b.Requesting VIM to attach needed VDUs (VMs) to the Network Service’s connectivity network. Instantiation 2/3

V1.0 | 7©6WIND VIM connects needed VDUs (VMs) to the connectivity network. 12.VIM acknowledges completion. 13.If needed, NFVO requests Network Manager to connect VNF external interfaces to physical network function interfaces. 14.NFVO acknowledges the completion of the Network Service instantiation. Instantiation 3/3

V1.0 | 8©6WIND 2015 Network Service Record for 40Gbps flavor Sig GW Core RTR LBNAT.1 Small Cell NS1 CP1 NS2 CP1 CP2 NAT.1 CP3 CP4 CP5 MANO Clause 6.5: “Further study is needed to determine how the VNFFG will track changes to the deployed instances, such as additional VNF instances being brought into service to handle scalability required for a traffic peak, and migration of VNF workloads to an alternative infrastructure to enable operational maintenance or provide business continuity in the event of major link or site failure.”

V1.0 | 9©6WIND 2015 VIM instantiates the connectivity network Openstack Distributed Virtual Router (DVR) Virtual Networking = vSwitching + vRouting

V1.0 | 10©6WIND 2015 NFVI Acceleration: Look-aside crypto accelerator SigGW VNF Virtual Router NIC VNFs NFVI IPSec

V1.0 | 11©6WIND 2015 NFVI Acceleration: inline IPSec accelerator SigGW VNF Virtual Router IPSec Packet Processor VNFs NFVI