Name: SHAILLY

Roll no.-IMH/10024/15
I MSc Mathematics and Computing
CS 6107 COMPUTER NETWORKS

ASSIGNMENT
TOPIC: NETWORK FUNCTION VRTUALISATION

Network Function Virtualization

Network functions virtualization (NFV) provides a new way to create, distribute, and operate
networking services. It is the process of decoupling the network functions from proprietary
hardware appliances so they can run in software on standardized hardware. These functions
(such as firewall, deep packet inspection, and intrusion prevention) become virtual network
functions (VNF).

NFV is designed to build up and deliver the networking components needed to support an
infrastructure totally independent from hardware. These components include virtual
compute, storage and network functions. NFV utilizes standard IT virtualization technologies
that run on off-the-shelf hardware like commodity x86 servers. It is applicable to any data plane
processing or control plane function in both wired and wireless network infrastructures.

History of Network Function Virtualization

[The concept and collaborative work on NFV was born in October 2012 when a number of the
world's leading TSPs jointly authored a white paper calling for industrial and research action. In
November 2012 seven of these operators (AT&T, BT, Deutsche Telekom, Orange, Telecom Italia,
Telefonica and Verizon) selected the European Telecommunications Standards Institute (ETSI) to be
the home of the Industry Specification Group for NFV (ETSI ISG NFV)]
The concept of NFV originated from service providers who wanted to make adding new network
functions or applications easier and faster. The constraints of hardware-based appliances led
them to apply standard IT virtualization technologies to their networks. To accelerate progress
towards this common goal, the companies who had formed the European Telecommunications
Standards Institute (ETSI) devoted resources to a new group, the Industry Specification Group
for Network Functions Virtualization (ISG NFV) in January 2013.

The ETSI ISG NFV is a group charged with developing requirements and architecture for
virtualization of various functions within telecoms networks, such as standards like NFV
management and network orchestration (MANO). ETSI is also instrumental in
collaborative projects like the newly announced OPNFV.
The Benefits of NFV:
NFV virtualizes network services via software to enable operators to:

 Reduced equipment costs and reduced power consumption through consolidating

equipment. Cost efficiency is main driver of NFV.
 Services can be rapidly scaled up/down as required. In addition, speed of service
deployment is improved is improved by provisioning remotely in software without any
site visits required to install new hardware.
 Accelerate time-to-market by reducing the time required to deploy new networking
services to support changing business requirements, new market opportunities, and
return on investment of new services. NFV lowers the risks associated with rolling out
new services, allowing providers to easily trial and evolve services to determine what
best meets the needs of customer
 Deliver agility and flexibility to quickly scale services up or down to address changing
demands; services can be delivered via software on any industry-standard server
hardware.
 Improved operational efficiency by taking advantage of the higher uniformity of the
physical network platform and its homogeneity to other support platforms.

NFV Architectural Framework

The NFV framework consists of three main components:

1. Virtualized network functions (VNFs) are software implementations of network

functions that can be deployed on a network functions virtualization infrastructure (NFVI).
2. Network functions virtualization infrastructure (NFVI) is the totality of all
hardware and software components that build the environment where VNFs are deployed.
The NFV infrastructure can span several locations. The network providing connectivity
between these locations is considered as part of the NFV infrastructure.
3. Network functions virtualization management and orchestration architectural
framework (NFV-MANO Architectural Framework) is the collection of all functional
blocks, data repositories used by these blocks, and reference points and interfaces through
which these functional blocks exchange information for the purpose of managing and
orchestrating NFVI and VNFs.
The building block for both the NFVI and the NFV-MANO is the NFV platform. In the NFVI role, it
consists of both virtual and physical processing and storage resources, and virtualization software.
In its NFV-MANO role it consists of VNF and NFVI managers and virtualization software operating
on a hardware controller. The NFV platform implements carrier-grade features used to manage and
monitor the platform components, recover from failures and provide effective security – all required
for the public carrier network.
 FIG-1: HIGH LEVEL NFV

NFV introduces the following three major differences:

1) Separation of software from hardware: This separation enables the software to evolve
independently from the hardware, and vice versa.

2) Flexible deployment of network functions: NFV can automatically deploy network-function software
on a pool of hardware resources which may run different functions at different times in different data
centers.

3) Dynamic service provisioning: Network operators can scale the NFV performance dynamically
and on a grow-as- you-need basis with fine granularity control based on the current network
conditions.

VIRTUALISATION NETWORK FUNCTIONS (VNF) - the virtual

network function is the software that runs on an NFV, Network Functions
Virtualization network to provide the various functions required
Virtualized network functions or VNFs are the software realizations of the various network functions
that can be deployed on a Network Functions Virtualization Infrastructure and needed to enable the
network to operate.
In this way, a virtual network function or VNF handles a specific network function that run on one or
more virtual machines on top of the hardware networking infrastructure.

The individual virtual network functions, VNFs, can be considered to be building blocks and they can
be connected or combined together, providing all the capabilities required to provide a complete
networking communication service.

Examples of various virtual network functions can be found within all areas of a telecommunications
network and they can include:

 Switching: BNG, CG-NAT, routers.

 Tunneling gateway elements: IPsec/SSL VPN gateways.
 Security functions: firewalls, intrusion detection systems, virus scanners, spam protection.
In this way, it can be seen that a huge number of VNFs can be run on a network using Network
Functions Virtualization.

Network Functions Virtualization Infrastructure (NFVI)

Physical and software resources, and virtualization layer, on top of which VNFs are executed. The
NFVI-PoPs include processing, storage and networking resources. The NFVI is implemented as a
distributed set of NFVI nodes deployed in various NFVI PoPs as required, to support the locality and
latency objectives of the different use cases and fields of application. The virtualization is an
important element in the NFVI domain, because it abstracts the hardware resources and decouples
the VNF software from the underlying hardware, thus ensuring a hardware independent lifecycle
for the VNFs.

NFV Management and Network Orchestration (MANO)

By nature, Network functions virtualization (NFV) changes the way networks are managed. From
initial set up to day-to-day operations, NFV management and network orchestration (MANO) fills
the management role. NFV MANO is a framework developed by a working group of the same
name within the European Telecommunications Standards Institute (ETSI) Industry Specification
Group for NFV (ETSI ISG NFV). Over time, the framework became more commonly referred to
as just NFV management and orchestration. It is the ETSI-defined framework for the management
and orchestration of all resources in a virtualized data center including compute,
networking, storage, and virtual machine (VM) resources. The main focus of NFV MANO is to
allow flexible on-boarding, sidestepping the chaos that can be associated with rapid spin-up of
network components.

It is broken up into three components:

 NFV Orchestrator: Responsible for on-boarding of new network services (NS) and virtual
network function (VNF) packages; NS lifecycle management; global resource
management; validation and authorization of network functions virtualization infrastructure
(NFVI) resource requests.
 VNF Manager: Oversees lifecycle management of VNF instances; fills the coordination
and adaptation role for configuration and event reporting between NFV Infrastructure
(NFVI) and Element/Network Management Systems.
  Virtualized Infrastructure Manager (VIM): Controls and manages the NFVI compute,
storage, and network resources

Relationship between NFV and SDN

NFV and SDN are two closely related, independent, yet complementary and mutually beneficial
technologies.
Virtualization is highly complementary to Software Defined Networking (SDN), but not
dependent on it (or vice-versa). Network functions can be virtualized and deployed without
SDN technologies, and non-virtualized functions can be controlled by SDN. The primary
distinction between the two has to do with the domain to which they apply: While NFV replaces
proprietary hardware network elements (NEs) with software running on standard servers, SDN
deals with the replacement of standardized networking protocols with centralized control.
While SDN function involves separation of control and data; centralization of control and
programmability of network whereas NFV deals with transfers of network functions from
dedicated appliances to generic servers. Network Functions Virtualization is able to support
SDN by providing the infrastructure upon which the SDN software can be run. Furthermore,
Network Functions Virtualization aligns closely with the SDN objectives to use commodity
servers and switches.