Network Functions

Virtualization (NFV)

1
Course Objectives
• What is Network Functions Virtualization (NFV)
1

• Relationship with Cloud Computing and Software Defined Networks (SDN)

2

• SDN, OpenFlow, OpenStack and Cloud Computing (IaaS) principles

3

• Principles of virtualization of servers

4

• Benefits of Network Functions Virtualization (NFV)

5

• The Changing Telecoms Industry Landscape and Transformation

6

• Enablers for Network Functions Virtualization (NFV)

7

2 | Training Title
 Course Objectives continued..
• Principles of Cloud Computing
8

• Industry Standard High Volume Servers

9

• Challenges for Network Functions Virtualization (NFV)

10

• NFV architecture
11

• Why NFV and The IP Multimedia Subsytem (IMS)

12

• VoLTE, LTE and IMS NFV requirements and benefits

13

3 | Training Title
CLASSROOM RULES
During the Training Please follow Two Simple Steps:

SMILE and FUN

Switch Phone to Vibrate
Minimise taking calls
Initiate New Ideas
Listen and Learn
Enjoy the training and you will learn more

Feel free to ask any question no matter how silly

Understand if you do not understand ASK
NO WORKING PLEASE
Copyright 2008 AIRCOM International
 What is NFV

Network functions virtualization (NFV) (also known as 

virtual network function (VNF)) offers a new way to design, deploy and
manage networking services. NFV decouples the network functions, such as 
network address translation (NAT), firewalling, intrusion detection, 
domain name service (DNS), and caching, to name a few, from proprietary
hardware appliances so they can run in software.

It’s designed to consolidate and deliver the networking components needed

to support a fully virtualized infrastructure – including virtual servers,
storage, and even other networks. It utilizes standard IT virtualization 
technologies that run on high-volume service, switch and storage hardware
to virtualize network functions. It is applicable to any data plane processing
or control plane function in both wired and wireless network infrastructures.

5
Problems Network Functions Virtualization
Addresses
The desire to automate the orchestration and management of network, storage,
and compute resources is a key driver of development for NFV and SDN. Imagine a
scenario that includes one physical server with 10 VMs or hundreds of containers.
This concept would never scale if manual operations were required. With
automation, you can rapidly spin up or destroy virtualized network functions (VNFs)
 such as VMs, containers, routers, firewalls, and intrusion prevention systems (IPS),
to elastically scale your network functions to match dynamic demand.

6
The Benefits of Network Functions Virtualization

NFV virtualizes network services via software to enable operators to:

• Reduce CapEx: reducing the need to purchase purpose-built hardware and

supporting pay-as-you-grow models to eliminate wasteful over-provisioning.
• Reduce OpEX: reducing space, power and cooling requirements of
equipment and simplifying the roll out and management of network services.
• Accelerate Time-to-Market: reducing the time to deploy new networking
services to support changing business requirements, seize new market
opportunities and improve return on investment of new services. Also 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
customers.
• Deliver Agility and Flexibility: quickly scale up or down services to
address changing demands; support innovation by enabling services to be
delivered via software on any industry-standard server hardware.

7
Relationship with Cloud Computing
and Software Defined Networks
SDN main objectives and features

8
SDN Basic Architecture

9
Network Function Virtualization

10
Network Function Virtualization (cont’d)

11
Network Function Virtualization (cont’d)

12
NFV Architecture

13
NFV- SDN cooperation

14
NFV SDN-Cooperation

15
SDN and Network Function
Virtualization

16
 Cloud Computing
This is an internet based computing that enables computers and
devices to share resources and data on demand. It is built with
the intention to make data ubiquitous and whenever requirement
by sharing the data between various types of computer resources
like networks, servers, applications, services, storage, etc. This,
in turn, leads to economies of scale and valuable cost savings.

Since everything is stored in the

virtual world, cloud computing
saves infrastructure costs like
purchasing servers, maintaining
server rooms, etc. Thus,
businesses can use the saved
funds in critical operational
requirements.

17
 What is the difference
between these technologies?
With the ever-increasing competition in
the telecom industry pushing down the
ARPU for every telecom operator in the
recent year, the operators were looking
forward to technologies that will help them
to keep their networks scalable, provide
uninterrupted service and enable new
subscribers quickly. NFV, SDN and Cloud
computing are the technologies that fulfil
their requirements.

18
The availability of NFV, SDN and Cloud computing will enable the operators to
move their infrastructure to enterprise class cloud computing servers. This will
make their networks more agile, flexible and responsive. It is also expected to
significantly bring down the costs of network commissioning and also the
operating costs.

Cloud computing has already been a roaring success in most industries, and
internationally the telecommunication operators are quickly realizing the worth of
NFV and SDN as well. Together, they allow the operators to harness the true
power of virtual computing by porting their network hardware and software
applications to the cloud, and operating them remotely.

These technologies are being developed rapidly and are expected to become
more robust, sophisticated and affordable in the future. Several major hardware
and software companies are dedicating their time and energy to grow the scope
of these technologies further. Needless to say, all players in the 
telecommunication industry need to look at these seriously, understand, and
leverage the advantages and efficiencies that they can get from these.

19
SDN, OpenFlow, OpenStack and
Cloud Computing (IaaS) principles

THE 4 PRINCIPLES OF SOFTWARE-DEFINED NETWORKING(SDN)

 Centralized Management :-Large, distributed networking environments require
numerous manual touches, consequently decreasing efficiency and risking security.
In a non-centralized network, it’s harder to push updates or see everything
happening, not to mention compare traffic or performance. This provides a more
effective way to interact with the networks in order to drive changes.

• Network Abstraction :- Network abstraction builds on network automation.

While network automation allows us to drive infrastructure changes in a much
more effective, less error-prone manner, network abstraction builds on that same
concept. As a result, instead of purpose-filled network functions, IT departments
can uniformly deliver services in a more abstracted manner anywhere on the
infrastructure.
• Network Automation :- For network automation, traditionally when you stand
up a server (like a virtual machine) you allocate the CPU, memory and storage
resources, but then you also have to involve the security team and put the firewall
rules into place. You have to engage the network team and define the virtual local
area network (VLAN) required for the virtual machine. When the server is built,
whether it’s in production or development, all the relevant network and security
parameters are also automated. It eases the burden to configure all required
parameters for this virtual machine to be operationally accessible.

• Programmability :- Another feature of the intelligent software that drives the

SDN infrastructure is programmability. We’re interacting with the network in a
much more programmatic fashion. This lets us make infrastructure changes that
properly reflect the state, the requirements of the networks, and what they need
from the network.

21
 OpenStack
Guiding Principles:- OpenStack has a set of guiding principles that are used to
inform and shape decisions. These principles are not aspirational. Rather, they form
the bedrock upon which the OpenStack community and software are built.
First and foremost, OpenStack follows The Four Opens. All four of them are essential,
and most of the principles described in this derive from them. In their personal
interactions, our community members are also bound by the rules described in the 
OpenStack Community Code of Conduct.

4 principals ::
• Open Source :- We do not produce “open core” software.
We are committed to creating truly open source software that is usable and
scalable. Truly open source software is not feature or performance limited and is
not crippled. There will be no “Enterprise Edition”.
We use the Apache License, 2.0.
OSI approved
GPLv3 compatible
DFSG compatible

22
• Open Design :-
We are committed to an open design process. Every development cycle the
OpenStack community holds face-to-face events to gather requirements and write
specifications for the upcoming release. Those events, which are open to anyone,
include users, developers, and upstream projects. We gather requirements, define
priorities and flesh out technical design to guide development for the next development
cycle.
The community controls the design process. You can help make this software meet your
needs.

• Open Development :-
We maintain a publicly available source code repository through the entire development
process. We do public code reviews. We have public roadmaps. This makes participation
simpler, allows users to follow the development process and participate in QA at an early
stage.
• Open Community :-
One of our core goals is to maintain a healthy, vibrant developer and user community.
Most decisions are made using a lazy consensus model. All processes are documented,
open and transparent.
The technical governance of the project is provided by the community itself, with
contributors electing team leads and members of the Technical Committee.
All project meetings are held in public IRC channels and recorded. Additional technical
communication is through public mailing lists and is archived.

23
 OpenFlow principle

When A, B, D are required to send packets to G, in the original structure, no

uniform control, the transmission path from the distribution router, three
hardware router would choose the same route, i.e., R3, R3 path causing heavy
traffic, and other resources (R1, R2, R4) dummy waste. If R3 path transmission
fails, ABD will refer both to the new path R2, R2 during limited load, only
completed A packet is sent, B and D are both alternates to R4, R4 same packet is
sent only to complete the B, D is Finally, use R1 to complete, F point will return a
message to the controller, and the controller is assigned A packet through R1, B
by R2, C completed by R4 transmission, to avoid wasting resources which under
the original framework packet B and D required to repeated twice more to
complete the transfer.

24
25
26
Cloud Computing (IaaS) principles

In defining Infrastructure as a Service we need to drill into specific characteristics

that a cloud platform provider must provide to be considered Infrastructure as a
Service. This has been no easy task as nearly every cloud platform provider has
recently promoted features and services designed to address the infrastructure as a
service and cloud computing market. Fortunately, as the technology has evolved
over time, a definition of cloud computing has emerged from the National Institute
of Standards and Technology (NIST) that is composed of five essential
characteristics, three service models, and four deployment models.

Principals ::

• On-demand self-service. A consumer can independently and unilaterally

provision computing capabilities, such as compute time, network
connectivity and storage, as needed automatically without requiring
human interaction with each service’s provider.

27
• Broad network access. Capabilities are available over the network
and accessed through standard mechanisms that promote use by
heterogeneous thin or thick client platforms.

• Resource pooling. The provider’s computing resources are pooled

to serve multiple consumers using a multi-tenant model, with
different physical and virtual resources dynamically assigned and
reassigned according to consumer demand. There is a sense of
location independence in that the customer generally has no control
or knowledge over the exact location of the provided resources, but
may be able to specify location at a higher level of abstraction (e.g.,
country, state, region or datacenter). Examples of computing
resources include storage, processing (compute), memory, network
bandwidth, and virtual machines.

28
• Rapid elasticity. Capabilities can be rapidly and elastically
provisioned, in some cases automatically, to quickly scale out, and
rapidly released to quickly scale in. To the consumer, the capabilities
available for provisioning often appear to be unlimited and can be
purchased in any quantity at any time.

• Measured Service. Cloud systems automatically control and

optimize resource use by leveraging a metering capability at some
level of abstraction appropriate to the type of service (e.g., storage,
compute, bandwidth, active user accounts, etc.). Resource usage can
be monitored, controlled, and reported, providing transparency for
both the provider and consumer of the utilized service.

29
Principles of virtualization of
servers

What is virtualization?

In computing, virtualization is a broad term that refers to the abstraction of

computer resources. Virtualization hides the physical characteristics of
computing resources from their users, be they applications, or end users. This
includes making a single physical resource (such as a server, an operating
system, an application, or storage device) appear to function as multiple virtual
resources; it can also include making multiple physical resources (such as
storage devices or servers) appear as a single virtual resource...”

there are four basic principles to consider when choosing the right
hardware for your virtual environment:

30
1. Choose servers designed for virtualization.

Virtualization software can create substantial performance overhead that increases

application latencies and reduces available capacity for consolidation. Intel® Xeon®
processor-based servers address this challenge with technologies that have been
developed with key virtualization software vendors. With hardware-assisted
virtualization, the hypervisor doesn’t emulate the CPU which allows applications
running on the virtual machine’s guest operating system to take advantage of low-
level CPU features. This helps to:

 Achieve better application performance and higher consolidation ratios by reducing

virtualization overhead and more efficiently sharing processor, memory and I/O
resources between virtual machines.
• Reduce the footprint of your data center by enabling higher consolidation ratios
and delivering leading performance per watt. Intel Xeon processor-based servers
help to reduce space, power and cooling requirements, as well as share network
and SAN ports more efficiently to avoid costly and unnecessary capital
improvements.
• Deploy virtualization with greater confidence. By providing a better hardware
foundation for virtualization, Xeon-based servers help to improve interoperability
among diverse operating systems, versions and applications.

31
2. Standardize to leverage server resource pools.

Organizations are increasingly consolidating applications onto server

resource pools, where virtual machines running live applications can be
moved easily from one physical server to another with no
application downtime. The bottom line benefit is dramatic improvement in
IT service levels at a surprisingly low cost.
However, you do need to be aware that the presence of different
hardware-assisted virtualization technologies in the same resource pool can
cause issues such as the failure to live migrate a virtual machine from
one physical host to another. The good news is that given the enormous
community of vendors delivering Xeon-based servers, organizations are
finding it a snap to deploy best-fit servers while maintaining live
migration support across all their systems.

32
3. Size your virtual servers the same way you would size your physical
servers.

Whether you’ll leverage a scale up strategy and put just one virtual machine on a
physical server (as you may do for a Tier 1 application where you’ll maximize the
utilization of the server, but still want the availability and flexibility of deploying in
a virtual environment), or a scale out strategy with multiple virtual machines
spread across multiple physical servers – sizing resource requirements for a
specific application doesn’t change when you virtualize. Start with the application
requirements, desired consolidation ratio, resource pools and select the server
that best matches these requirements. With Intel Xeon processor-based servers
you’ll have all the option you need. From small two-socket servers to scalable
systems with up to 16 processors (96 cores), you can choose the best server for
specific requirements and still maintain optimal performance and live migration
support.

33
4. Time your server refreshes to optimize total value.

The latest Xeon-based servers increase virtualization by a factor of two compared

with previous-generation servers and by a factor of nine compared with older,
single-core processor-based systems. That means that even organizations that
have already implemented virtualization are likely to see dramatic cost savings
and a quick ROI as they transition to these powerhouses. If you’re interested in
estimating the potential value of a server refresh in your current environment, try
out the Intel ROI Estimator.
By tracking server advances in speed, increased energy efficiency, memory
capacity and bandwidth, you can time your server refreshes to optimize your
returns with each refresh – and build an increasingly powerful, agile and cost-
effective infrastructure for your business.

34
 Benefits of Network Functions
Virtualization (NFV)
NFV also is flexible, cost-effective, scalable, and secure. With these benefits, NFV
addresses several trends shaping service provider networks.

These are the 5 benefits :-

Flexibility: Operators looking to quickly deploy new services require a much

more flexible and adaptable network -- one that can be easily and quickly
installed and provisioned.

Cost: Cost is a top consideration for any operator or service provider these days,
even more so now that they see Google and others deploying massive
datacenters using off-the-shelf merchant silicon (commoditized hardware) as a
way to drive down cost. Cost is also reflected in opex -- how easy it is to deploy
and maintain services in the network.

Scalability: To adapt quickly to users' changing needs and provide new services,
operators must be able to scale their network architecture across multiple
servers, rather than being limited by what a single box can do.

35
• Security: Security has been, and continues to be, a major challenge in
networking. Operators want to be able to provision and manage the
network while allowing their customers to run their own virtual space
and firewall securely within the network.

• Virtualization in another service provider network: To meet

customers' needs better, service providers want the ability
to substantiate their service anywhere in the world using virtualization.

36
 The Changing Telecoms Industry
Landscape and Transformation
Digital Transformation of the Telecom Industry :-

The digital transformation journey is so fundamental that it requires changing the

DNA of every communications service provider. The telco industry is going through
massive structural changes. The rapid development of disruptive technologies (such
as 4G LTE), messaging services (such as WhatsApp, WeChat), and products (such
as over-the-top Netflix streaming) has eliminated many of the traditional
distinctions between wireless, cable, internet and local and long distance
communication services, and has brought new competitors to telephone companies,
cable companies, wireless service providers, satellite providers, application and
device providers, and providers of Voice over Internet Protocol (VoIP) services.

The key market trends include

■ Convergence of previously discrete markets (for example, content, TV,
broadband, wireless and cable).
■ Exponential growth of data volumes (for example, streaming apps in the cloud).
■ Digitization: More and more services are moving to the cloud.
■ New customer behavior patterns (for example, cord-cutting and binge watching).

37
Three-tier Digital Strategy of Every Telco

38
Digital Trends Transforming the Telecom Industry:-

Technology developments, interconnected markets, shifting consumer needs and

converging industry ecosystems are creating innovative opportunities for
communications service. Providers have the chance to transform around the
capabilities of high-performing networks (4G and 5G networks) with a goal of
future growth based on delivering what customers want and need in the new
digital world.

The Network of the Future: 5G Networks

Over the next decade, the development of the next generation of wireless services
will be enabled by 5G and wireless broadband. As networks evolve from dumb
pipes to smart pipes, we expect that the next wave of use cases will be truly
transformational.

39
Customers want faster access and
richer services. 5G infrastructure
promises the following:

■ Up to 100 times faster data rates

than 4G: instant access to services and
applications.
■ Network latency lowered by a factor
of five: use cases in areas such as
intelligent transport and remote
machinery.
■ Expand data volumes by a factor of
1,000.

This new innovation in bandwidth and

speed enables a new set of digital use
cases, sparking another wave of
innovation
40
The specific trends in digital media
and interactive entertainment
include:

■ Access to live streaming video

content with virtually no buffering,
regardless of the number of devices
using the service.
■ Scalable platforms for delivering
content (including live broadcasts,
video on demand, games, software
and websites) to customers on their
devices at any time.
■ Video scale expanding advertising
opportunities and enhanced
targeting.

41
Evolution of Video

42
 Over-the-Top Streaming

Over-the-top (OTT) can be seen in other services. For instance, over-the-top

messaging is an instant messaging service provided by a third party as an
alternative to text messaging services provided by a mobile network operator.
Examples include WhatsApp, Messenger, and Skype services.

43
Transformation Agenda: Five Key
Strategic Initiatives for Every Service
Provider

Key Strategic Initiatives at a Leading Telecom Provider

Above figure illustrates how a leading communications service provider has

translated their digital strategy into a series of key initiatives.

44
Data-Driven Digital Transformation Model From Hitachi Data
Systems

45
Enablers for Network Functions
Virtualization (NFV)
Several recent technology developments make the goals of Network Functions
Virtualisation achievable. This section describes these enablers and briefly
discusses relevance.

Cloud Computing

Network Functions Virtualisation will leverage modern technologies such as those

developed for cloud computing. At the core of these cloud technologies are
virtualisation mechanisms: hardware virtualisation by means of hypervisors, as well
as the usage of virtual Ethernet switches (e.g. vswitch) for connecting traffic
between virtual machines and physical interfaces. For communication-oriented
functions, high-performance packet processing is available through high-speed
multi-core CPUs with high I/O bandwidth, the use of smart Ethernet NICs for load
sharing and TCP Offloading, and routing packets directly to Virtual Machine
memory, and poll-mode Ethernet drivers (rather than interrupt driven, for example
Linux NAPI and Intel’s DPDK).

46
Cloud infrastructures provide methods to enhance resource availability and
usage by means of orchestration and management mechanisms, applicable to
the automatic instantiation of virtual appliances in the network, to the
management of resources by assigning virtual appliances to the correct CPU
core, memory and interfaces, to the re-initialisation of failed VMs, to snapshot
VM states and the migration of VMs. Finally, the availability of open APIs for
management and data plane control, like OpenFlow, OpenStack, OpenNaaS or
OGF’s NSI, provide an additional degree of integration of Network Functions
Virtualisation and cloud infrastructure.

Industry Standard High Volume Servers

The use of industry standard high volume servers is a key element in the
economic case for Network Functions Virtualisation. Network Functions
Virtualisation leverages the economies of scale of the IT industry. An industry
standard high volume server is a server built using standardised IT components
(for example x86 architecture) and sold in the millions. A common feature of
industry standard high volume servers is that there is competitive supply of the
subcomponents which are interchangeable inside the server.

47
We believe that Network Appliances which depend on the development of
bespoke Application Specific Integrated Circuits (ASICs) will become
increasingly uncompetitive against general purpose processors as the
cost of developing ASICs increases exponentially with decreasing feature
size.[5] Merchant silicon will still be applicable for commodity functions
implemented at scale, and ASICs will still be applicable for some types of
very high throughput applications.

48
Principles of Cloud Computing
Six principles for cloud computing

1. The Enablement Principle: Plan for cloud computing as a strategic enabler,

rather than as an outsourcing arrangement or technical platform.
2. The Cost/Benefit Principle: Evaluate the benefits of cloud acquisition based
on a full understanding of the costs of cloud compared with the costs of other
technology platform business solutions.
3. The Enterprise Risk Principle: Take an enterprise risk management (ERM)
perspective to manage the adoption and use of cloud.
4. The Capability Principle: Integrate the full extent of capabilities that cloud
providers offer with internal resources to provide a comprehensive technical
support and delivery solution.
5. The Accountability Principle: Manage accountabilities by clearly defining
internal and provider responsibilities.
6. The Trust Principle: Make trust an essential part of cloud solutions, building
trust into all business processes that depend on cloud computing.
The cloud's availability means the technology infrastructure is
not the market differentiator it has been in the past. 

49
 Industry Standard High
Volume Servers

An NFV server needs to support a complete range of operating systems

(OSs), hypervisors, cloud computing platforms including OpenStack®, and
an extensive array of telecom software applications. These telecom
software components and applications then must be optimized to handle
the high volume of packet processing that is demanded by telecom control
and data plane tasks in areas such as encryption/decryption, quality of
service (QoS), and transcoding.
A server that’s at home in any environment :-
To efficiently host data plane applications such as firewalls, load balancers,
and content delivery networks (CDNs), an NFV server must be equally at
home in the central office (CO), network data center, or IT data center. In a
CO environment, NFV servers must support –48VDC, may need to be network
equipment building system (NEBS) certified for safety and reliability, and
must support application availability of 99.999 percent or greater.

50
Tuned for intense packet processing

To optimize NFV data plane application deployments, an NFV server must be

precisely configured and tuned to handle high volume packet-processing
applications. The server should also support the industry’s leading packet-
processing software, such as Data Plane Development Kit (DPDK). These
technologies enable a wide range of new server-based network application
capabilities. For example, in security where it is essential to remain agile,
current, and in complete control, these applications can now be deployed on
industry-standard servers.

Don’t overlook ease of management

Regardless of the environment, having a pool of trained system
operators is essential. Although industry-standard hardware doesn’t
demand very much in the way of vendor-specific training or
certification, it is critical that operators have access to state-of-the-art
tools that enable them to effectively manage the mix of telecom and IT
infrastructure in their network.

51
Challenges for Network
Functions Virtualization (NFV)

52
There are a number of challenges to implement Network Functions
Virtualization which need to be addressed by the community interested in
accelerating progress. Challenges we have identified
• NFV involves a variety of still-evolving technologies:-
NFV operations differ fundamentally from classical network operations.
Operators must borrow heavily from IT in designing their operations, but
make telecom-specific adaptations. The pioneers of NFV operations are
following their own paths. They are developing proprietary functionality
and pivoting regularly to address their individual concerns. This is
causing market fragmentation and uncertainty for both vendors and
other operators that want “standard” blueprints to follow.

• Ignoring NFV is a high-risk strategy :-

Virtualization is a pervasive industrial trend. NFV democratizes
networking technologies and lowers barriers to telecoms-market entry
for web-scale companies, large enterprises, and new start-ups. Leading
proponents of NFV among operators anticipate an unrecognizable
networking landscape in 2020,  due to developments in the technology
that will by then have become mainstream. 

53
• Stamina and determination throughout an
organization are essential for success in NFV:-
Software mastery is key to virtualization and NFV leaders have stressed the
necessity of advanced software skills in-house. Examples of this trend are
AT&T’s creation of ECOMP, Telefonica’s founder membership of Open Source
MANO, and investment by other operators in innovative software start-ups and
Cloud companies to gain access to DevOps/agile software development skills.

• Automation :-

Network Functions Virtualisation will only scale if all of the functions can be
automated. Automation of process is paramount to success.

• Integration :-
Seamless integration of multiple virtual appliances onto existing industry
standard high volume servers and hypervisors is a key challenge for Network
Functions Virtualisation. Network operators need to be able to “mix & match”
servers from different vendors, hypervisors from different vendors and virtual
appliances from different vendors without incurring significant integration costs
and avoiding lock-in. The ecosystem must offer integration services and
maintenance and third-party support; it must be possible to resolve integration
issues between several parties.
54
 NFV architecture
NFV Concepts

 Network Function (NF): Functional building block with a

well defined interfaces and well defined functional behavior
 Virtualized Network Function (VNF): Software
implementation of NF that can be deployed in a virtualized
infrastructure
 VNF Set: Connectivity between VNFs is not specified, e.g.,
residential gateways
 VNF Forwarding Graph: Service chain when network
connectivity order is important, e.g., firewall, NAT, load
balancer
 NFV Infrastructure (NFVI): Hardware and software required
to deploy, mange and execute VNFs including computation,
networking, and storage.

55
 NFV Concepts conti..
 NFVI Point of Presence (PoP): Location of NFVI
 NFVI-PoP Network: Internal network
 Transport Network: Network connecting a PoP to other PoPs or external networks
 VNF Manager: VNF lifecycle management e.g., instantiation, update, scaling, query,
monitoring, fault diagnosis, healing, termination
 Virtualized Infrastructure Manager: Management of computing, storage, network,
software
resources
 Network Service: A composition of network functions and defined by its functional and
behavioral specification
 NFV Service: A network services using NFs with at least one VNF.
 User Service: Services offered to end users/customers/subscribers.
 Deployment Behavior: NFVI resources that a VNF requires, e.g., Number of VMs, memory,

disk, images, bandwidth, latency

 Operational Behavior: VNF instance topology and lifecycle operations, e.g., start, stop,
pause, migration, …
 VNF Descriptor: Deployment behavior + Operational behavior
 NFV Orchestrator: Automates the deployment, operation, management, coordination of
VNFs and NFVI.
 VNF Forwarding Graph: Connection topology of various NFs of which at least one is a VNF

56
NFV Architecture

57
Some of the VNFs and elements possible include the following:

 Application Acceleration
 Application Delivery Controllers/Load Balancers
 DDos Protection
 Deep-packet Inspection
 Evolved Packet Core (EPC) functions
 Intrusion Prevention
 Network Brokering, Tapping, or Monitoring
 Policy Management
 Virtual Firewalls
 Virtual Routing & Switching
 WAN Optimization Controller

58
 Why NFV and The IP
Multimedia Subsytem (IMS)
Why We need NFV?

1. Virtualization: Use network resource without

worrying about where it is physically located,
how much it is, how it is organized, etc.
2. Orchestration: Manage thousands of devices
3. Programmable: Should be able to change behavior on the fly.
4. Dynamic Scaling: Should be able to change size, quantity
5. Automation
6. Visibility: Monitor resources, connectivity
7. Performance: Optimize network device utilization
8. Multi-tenancy
9. Service Integration
10. Openness: Full choice of Modular plug-ins

Note: These are exactly the same reasons why we need SDN

59
 What is IMS ?
 IP Multimedia Subsystem
 Architectural Framework
 Overlay Network (PS and CS Networks)
• Support for IP-Based Interactive Multimedia (QoS)
• Mandatory Support for IPV6
• Signaling based on IETF Protocol SIP , DIAMETER and COPS
• Core and Access
• Integration with PSTN
• Access Independent
• Wireless ( UMTS , WLAN, WiMAX)
• Wired ( DSL)
Key Functions of IMS network
• Session Control/Management
• Subscription/Registrations Management
• Service Control
• Charging and Billing
• Operations, Administration, Maintenance and
Provisioning (OAM&P/OSS)
• Interworking with PSTN

60
IMS Protocols Interfaces

61
Protocols Used in IMS Networks

• Session Initiation Protocol (SIP)

• Registration , Authentication
• Call Control/Session Establishment
• Interworking Functions
• DIAMETER
• Next Generation AAA Model
• Pull/Push Registrations Data
• User Profiles
• Service Provisioning/Service Control
• IMS Charging
• Common Open Policy Service ( COPS)
• QoS Parameters Negotiations

62
 VoLTE, LTE and IMS NFV
requirements and benefits

VoLTE and IMS Features & Benefits

• Provides interworking, normalization, transcoding and relay functions for
signaling and media protocols to ensure disparate networks can communicate
and deliver best call quality
• Delivers seamless, uninterrupted roaming, with optimal media routing and call
handoff, to ensure fast call connection times and reduced call latency for end
users
• Provides SIP signaling control and media anchoring to ensure voice call
continuity for calls that traverse LTE and 3G networks
• Enables the use of HD voice and EVS voice codecs, including transcoding,
delivering a better quality of experience (QoE) for end users compared to over-
the-top (OTT) services
• Secures the network edge for user access and/or peer network interconnection
with topology hiding, Internet Protocol Security encryption (IPSec), Transport
Layer Security (TLS), Secure Real-Time Transport Protocol (SRTP) and intrusion
protection such as from Distributed Denial of Service (DDoS) attack.

63
 LTE Features & Benefits

4G LTE has some inherent advantages over previous generation (3G) of mobile
communications which makes it suitable for connectivity for enterprises.  
    
• Higher bandwidth (data speeds), 4G LTE provides true broadband speeds in
comparison to 3G.
• Low latency, lower idle-to-active times (improved network responsiveness)
• High spectrum efficiency means higher network capacity, improved cost efficiency
• Backwards compatibility and future-proofing
• All IP network means easier integration, improved cost efficiency
• Enhancements to security and Quality of Service differentiation

64
NFV Features & Benefits

NFV also is flexible, cost-effective, scalable, and secure. With these benefits, NFV addresses
several trends shaping service provider networks.

• Flexibility: Operators looking to quickly deploy new services require a much more flexible
and adaptable network -- one that can be easily and quickly installed and provisioned.
• Cost: Cost is a top consideration for any operator or service provider these days, even more
so now that they see Google and others deploying massive datacenters using off-the-shelf
merchant silicon (commoditized hardware) as a way to drive down cost. Cost is also reflected
in opex -- how easy it is to deploy and maintain services in the network.
• Scalability: To adapt quickly to users' changing needs and provide new services, operators
must be able to scale their network architecture across multiple servers, rather than being
limited by what a single box can do.
• Security: Security has been, and continues to be, a major challenge in networking. Operators
want to be able to provision and manage the network while allowing their customers to run
their own virtual space and firewall securely within the network.
• Virtualization in another service provider network: To meet customers' needs better,
service providers want the ability to substantiate their service anywhere in the world using
virtualization.

65
Thank You

66