er Virtualized infrastructure Compute Storage Network manager Physical resources Figure 3.2 ETSI NFV reference architecture. of different aspects of NFV. Figure 3.2 shows the ETSI NFV reference architecture [50]. It includes the following components: NFVI: The NFVI provides the technology platform with a common execution platform for a variety of VNFs. It consists of a distributed set of NFVI nodes in various locations to support the locality and latency requirements of the different use cases. NFVI can be categorized into three domains: the compute and storage domain, the hypervisor domain, and the infrastructure network domain. The compute domain refers to the computing hardware in Figure 3.2. The hypervisor domain includes both virtual computing and virtualization layer. The infrastructure network domain refers to the virtual networks as well as the network hardware. 3.1 NFV Architecture NFV orchestrator: The objective of NFV is to separate the VNFs from the infrastructure, and this includes their management. This management and orchestration block is often complex and composed of great many distributed component parts. On the one hand, it handles the network-wide orchestration and management of NFV resources. It is an integral and essential part of the NFV framework and is specified within the GS NFV management and network orchestration (MANO) documentation. On the other hand, it is used to realize the NFV service topology on NFVI. VNF manager(s): It is responsible for VNF life cycle management, including VNF creation, resource allocation, migration, and termi- nation. Virtualized infrastructure manager(s): It is responsible for control- ling and managing the computing, storage, and network resources, as well as their virtualization. OSS: Similar to OSS in traditional cellular network infrastructure, the main role of OSS in NFV is supporting the comprehensive management and operations functions. EMS: It performs the typical FCAPS functionality for a VNF. The current element manager functionality needs to be a