The document outlines a high-level framework for Network Functions Virtualization (NFV), detailing its infrastructure, virtualized network functions, management, orchestration, and various use cases. It discusses the separation of architecture domains within NFV, such as compute, hypervisor, and network support, and the roles of management and orchestration components. Additionally, it presents specific use cases including NFVI as a service and virtualization of mobile networks among others.

1. Mustufa Sir

2. Mustufa Sir

3. High-Level NFV Framework
Mustufa Sir

4. Index
1. NFV INFRASTRUCTURE
2. VIRTUALIZED NETWORK FUNCTIONS
3. NFV MANAGEMENT AND ORCHESTRATION
4. NFV USE CASES
Mustufa Sir

5. 1. NFV INFRASTRUCTURE
Compute domain: Provides
commercial off-the-shelf (COTS) high-
volume servers and storage.
Hypervisor domain: Mediates the
resources of the compute domain to
the VMs of the software appliances,
providing an abstraction of the
hardware.
Infrastructure network domain
(IND): Comprises all the generic high
volume switches interconnected into
a network that can be configured to
supply infrastructure network
services.
Mustufa Sir

6. Container Interface
• An execution environment on a host system
within which a functional block executes.
• The functional block is on the same physical
host as the container that provides the
container interface.
Mustufa Sir

7. Mustufa Sir

8. • The architecture of the VNFs is separated from the
architecture hosting the VNFs (that is, the NFVI).
• The architecture of the VNFs may be divided into a number
of domains with consequences for the NFVI and vice versa.
• Given the current technology and industrial structure,
compute (including storage), hypervisors, and
infrastructure networking are already largely separate
domains and are maintained as separate domains within
the NFVI.
• Management and orchestration tends to be sufficiently
distinct from the NFVI as to warrant being defined as its
own domain.
• The interface between the VNF domains and the NFVI is a
container interface and not a functional block interface.
• The management and orchestration functions are also likely
to be hosted in the NFVI (as VMs) and therefore also likely
to sit on a container interface.
Mustufa Sir

9. Mustufa Sir

10. Deployment of NFVI Containers
Mustufa Sir

11. Mustufa Sir

12. Compute Domain
• The principal elements in a typical compute
domain may include the following:
1. CPU/memory
2. Internal storage
3. Accelerator
4. External storage with storage controller
5. Network interface card (NIC)
6. Control and admin agent
7. Eswitch
8. Compute/storage execution environment
Mustufa Sir

13. NFVI Implementation Using Compute Domain
Nodes
1. Compute node
2. Gateway node
3. Storage node
4. Network node
Mustufa Sir

14. Hypervisor Domain
1. Compute/storage resource sharing/management
2. Network resource sharing/management
3. Virtual machine management and API
4. Control and admin agent
5. Vswitch
Mustufa Sir

15. Infrastructure Network Domain
• The infrastructure network domain (IND) performs a
number of roles. It provides
– The communication channel between the VNFCs of a
distributed VNF
– The communications channel between different VNFs
– The communication channel between VNFs and their
orchestration and management
– The communication channel between components of the
NFVI and their orchestration and management
– The means of remote deployment of VNFCs
– The means of interconnection with the existing carrier
network
Mustufa Sir

16. 2. VIRTUALIZED NETWORK FUNCTIONS
Mustufa Sir

17. VNF Interfaces
Mustufa Sir

18. VNFC to VNFC Communication
Mustufa Sir

19. VNF Scaling
• scale up
– Expand capability by adding additional physical or
virtual machines.
• scale out
– Expand the capability of a single physical machine
or VM.
Mustufa Sir

20. 3. NFV MANAGEMENT AND ORCHESTRATION
• The NFV management and orchestration (MANO)
component of NFV has as its primary function the
management and orchestration of an NF
environment.
• Further complicating MANO functionality is its
need to interoperate with and cooperate with
existing operations support systems (OSS) and
business support systems (BSS) in providing
management functionality for customers whose
networking environment consists of a mixture of
physical and virtual elements.
Mustufa Sir

21. Mustufa Sir

22. Virtualized Infrastructure Manager
• Virtualized infrastructure management (VIM)
comprises the functions that are used to
control and manage the interaction of a VNF
with computing, storage, and network
resources under its authority, as well as their
virtualization.
Mustufa Sir

23. Mustufa Sir

24. Virtual Network Function Manager
• VNFM performs the following:
– VNF instantiation, including VNF configuration if
required by the VNF deployment template
– VNF initial configuration with IP addresses
– VNF instantiation feasibility checking, if required
– VNF instance software update/upgrade
– VNF instance modification
– VNF instance scaling out/in and up/down
Mustufa Sir

25. Mustufa Sir

26. NFV Orchestrator
• The NFV orchestrator (NFVO) is responsible for
resource orchestration and network service
orchestration.
• Resource orchestration manages and coordinates
the resources under the management of different
VIMs.
• Network services orchestration manages/
coordinates the creation of an end-to-end service
that involves VNFs from different VNFMs
domains.
Mustufa Sir

27. Repositories
• Associated with NFVO are four repositories of
information needed for the management and
orchestration functions:
1. Network services catalog
2. VNF catalog
3. NFV instances
4. NFVI resources
Mustufa Sir

28. Mustufa Sir

29. Element Management
• The element management is responsible for
fault, configuration, accounting, performance,
and security (FCAPS) management
functionality for a VNF.
Mustufa Sir

30. Mustufa Sir

31. OSS/BSS
• The OSS/BSS are the combination of the
operator’s other operations and business
support functions that are not otherwise
explicitly captured in the present architectural
framework, but are expected to have
information exchanges with functional blocks
in the NFV-MANO architectural framework.
Mustufa Sir

32. 4. NFV USE CASES
• There are currently nine use cases, which can
be divided into the categories of architectural
use cases and service-oriented use cases
Architectural Use Cases
1. NFVI as a Service
2. VNF as a Service
3. Virtual Network Platform as a Service
4. VNF Forwarding Graphs
Service-Oriented Use Cases
5. Virtualization of Mobile Core Network and
IP Multimedia Subsystem
6. Virtualization of Mobile Base Station
7. Virtualization of the Home Environment
8. Virtualization of CDNs
9. Fixed Access Network Functions
Virtualization
Mustufa Sir

33. 1. NFVI as a Service
• NFVIaaS is a scenario in which a service
provider implements and deploys an NFVI that
may be used to support VNFs both by the
NFVIaaS provider and by other network
service providers.
• For the NFVIaaS provider, this service provides
for economies of scale.
Mustufa Sir

34. 2. VNF as a Service
• Whereas NFVIaaS is similar to the cloud model
of Infrastructure as a Service (IaaS), VNFaaS
corresponds to the cloud model of Software
as a Service (SaaS).
• With VNFaaS, a provider develops VNFs that
are then available off the shelf to customers.
Mustufa Sir

35. 3. Virtual Network Platform as a Service
• The programmability and development tools
of the VNPaaS that allow the subscriber to
create and configure custom ETSI NFV-
compliant VNFs to augment the catalog of
VNFs offered by the service provider.
Mustufa Sir

36. 4. VNF Forwarding Graphs
• VNF FG allows virtual appliances to be chained
together in a flexible manner. This technique is
called service chaining. For example, a flow
may pass through a network monitoring VNF,
a load-balancing VNF, and finally a firewall
VNF in passing from one endpoint to another.
Mustufa Sir

37. 5. Virtualization of Mobile Core Network and IP
Multimedia Subsystem
• NFV aims at reducing the network complexity
and related operational issues by leveraging
standard IT virtualization technologies to
consolidate different types of network
equipment onto industry standard high-
volume servers, switches, and storage
Mustufa Sir

38. 6. Virtualization of Mobile Base Station
• RAN is the part of a telecommunications
system that implements a wireless technology
to access the core network of the mobile
network service provider.
• There is the possibility that a number of RAN
functions can be virtualized as VNFs running
on industry standard infrastructure.
Mustufa Sir

39. 7. Virtualization of the Home Environment
• This use case deals with network provider
equipment located as customer premises
equipment (CPE) in a residential location.
Mustufa Sir

40. 8. Virtualization of CDNs
• Some Internet service providers (ISPs) are
deploying proprietary Content Delivery
Network (CDN) cache nodes in their networks
to improve delivery of video and other high-
bandwidth services to their customers.
• Both CDN cache nodes and CDN control nodes
can potentially be virtualized.
Mustufa Sir

41. 9. Fixed Access Network Functions Virtualization
• NFV offers the potential to virtualize remote functions in
the hybrid fiber/copper access network and passive
optical network (PON) fiber to the home and hybrid
fiber/wireless access networks.
Mustufa Sir

42. Reference
Foundations of Modern Networking: SDN,
NFV, QoE, IoT, and Cloud
by William Stallings
Mustufa Sir

43. Thank you
Mustufa Sir