Professional Documents
Culture Documents
SDN has been one of the pillars of innovation in network infrastructures, allowing the decoupling
of the control and data planes through an open and standard interface that enables the
programmability of the network. OpenFlow, ForCES, and I2RS are some examples of SDN
technology. SDN has also contributed to the virtualization of the network infrastructure, providing
the foundation to isolate, abstract, and share the network resources. Service provisioning is often
based on proprietary hardware appliances, which imposes some restrictions when trying to deploy
new network services, such as capacity and availability. In this scenario, the network infrastructure
is not flexible enough to accommodate new services or migrate them to other locations due to its
dependence on the physical appliances.
NFV Framework
The basic components of virtualized platforms where NFV is deployed are:
Physical server: The physical server is the bare-metal machine that has all the physical
resources such as CPU, storage, and RAM.
Hypervisor: The hypervisor, or virtual machine monitor, is the software that runs and
manages physical resources. It provides the virtual environment on which the guest virtual
machines are executed.
The guest virtual machine: A piece of software that emulates the architecture and
functionalities of a physical platform on which the desired application is executed.
NFV Challenges and Solutions
In a nutshell, differences between SDN and NFV can be illustrated as:
REFERENCES
[1] Sakir Sezer et al., Are We Ready for SDN? Implementation Challenges for Software-Defined
Networks.
[2] Hassan Hawilo et al., NFV: State of the Art, Challenges, and Implementation in Next
Generation Mobile Networks (vEPC)
[3] Jon Matias et al., Toward an SDN-Enabled NFV Architecture