Scribd
Upload
102 views48 pages

Introduction To NFV

The document provides an overview of network function virtualization (NFV) including the concept, motivation, functional blocks, terminology, and scope. It discusses NFV components like VNFs, VIM, VNFM, NFVO and repositories. It also covers VNF and network service lifecycles, containers versus VMs, and how to explore the ETSI NFV website.

Uploaded by

Mohamed Abdel Monem
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
102 views48 pages

Introduction To NFV

The document provides an overview of network function virtualization (NFV) including the concept, motivation, functional blocks, terminology, and scope. It discusses NFV components like VNFs, VIM, VNFM, NFVO and repositories. It also covers VNF and network service lifecycles, containers versus VMs, and how to explore the ETSI NFV website.

Uploaded by

Mohamed Abdel Monem
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 48

NFV Foundation

Ahmed Salah
Tech-Strategy Consultant
TE Internal Use
Table of Content
 The Concept Behind NFV
 The Motive
 NFV Functional blocks
 MANO Functional Blocks
 NFV Terminology
 STC Scope
 Containers vs Virtual Machines
 How to explore ETSI website
The Concept Behind NFV- Legacy Network
 Network Function (NF)
 A typical network consist of network elements with external interfaces to deliver specific
functions
 Network functions are mapped to network elements and physical appliances such as : MSC –
MGW –SGSN-GGSN which is composed of proprietary HW and SW
The Drive & Motive
• VoLTE Service Example
Problem Statement (VoLTE Example)

1. Lack of agility to introduce innovative services efficiently.


2. Increasing Cost of Energy and Capital investment challenges.
3. HW Lifecycle gets shorter with an accelerated services innovation inhibits the roll-out of new
revenue earning network service and constraining the innovation.
4. Lack of skills needed design, integrate and operate increasingly complex hardware-based
appliances.

 Extracted from NFV introductory white paper – oct 2012


The Concept Behind NFV- Physical to Virtual
 The Virtualization layer abstract the HW resources and decouples the NF SW from the
underlying HW ,and enabling them to run on a SW environment Hence allowing use of COTS
HW (general purpose servers and storage)
 the transition from a hardware-based to a software based implementation has been an active area
of study within ETSI NFV ISG
The Kickoff
 The first white paper was published in Oct ,2012 at the “SDN and Open Flow World
Congress” in Germany

 The publishing group had members from Tier-1 operators such as AT&T , Verizon , Telefonica
and others

 The main objective was to provide an introduction about the concept , highlight the
benefits/challenges and call for action

 ETSI (NFV ISG) was chosen and founded on November 2012 to be the home of NFV
NFV ETSI Reference Architecture
 NFV Building Blocks
 VNF - Virtual Network Function
 NFVI - NFV Infrastructure
 VIM - Virtualized infrastructure
Manager
 VNFM - VNF Manager
 NFVO - NFV Orchestrator
 EMS – Element manager system
 Data Repositories
 OSS/BSS
NFV Functional blocks-VNF
 VNF Concepts
 It’s the implementation of a NF that can
be deployed on NFVI
 A VNFC is characterised as an internal component
of a VNF that can be mapped to a single container
interface to provide a sub-set of the VNF’s functionality
as shown in Figure
 VNFC maps to a partition of the compute node (VC)
which refers to OS container or VM
NFV Functional blocks- VNF/NFVI
Relation
NFV Functional blocks-VIM
VIM – Virtualized infrastructure manager

 VIM is responsible for managing NFVI compute ,


Storage , and network resources within one
operator’s infrastructure domain (NFVI-PoP)
which can be seen as DC or PoD
 It has northbound interface with VNFM,NFVO to
allocate resources on NFVI

 OpenStack is an example of market solution of


NFV VIM
 Most of the commercial deployment is based on
openstack and VMWare
NFV Functional blocks-VNFM
 Responsible for VNF LCM which are
classified into:

 VNF Instantiation
 VNF Termination
 VNF Scaling
 VNF Upgrade
 VNF Healing
 Each VNF may have a specific VNFM or a generic
VNFM may be deployed

 The VNFM has access to repository of available VNF


packages and different version of them , all
represented via their associated VNFDs
NFV Functional blocks-NFVO
 NFVO has two main functions

• The orchestration of NFVI resources across multiple


DCs
• Service orchestration

• Two common ways are used within resources


orchestration:
 Direct mode
 Indirect mode

A network service is constructed by chaining VNFs and/or Physical Network


Functions (PNFs).
NFV Functional blocks-Other

 Element Manager is responsible for the FCAPS


of the VNF

 OSS/BSS may provide management and


orchestration for legacy systems and may have
e2e visibility of services provided by legacy
network
NFV Functional Blocks- ETSI NFV Scope
MANO - Functional Blocks
 MANO Architecture framework includes 3 blocks
(NFVO ,VNFM &VIM)
 MANO includes four data repositories (NS Catalog ,
VNF Catalog , NFV Instance , NFVI Resources)

NFV management and orchestration functions can be grouped in three


broad categories: virtualised resources, virtualised network functions, and
network services.
A network service is constructed by chaining VNFs and/or Physical
Network Functions (PNFs).
MANO Functional Blocks – Repositories
VNF Lifecycle Management- VNF
Package
 VNF Package in a nutshell

 VNF Package is an archive that is provided by VNF vendors and includes a VNFD ,
the SW image associated with the VNF , as well as additional artefacts to check the
integrity and prove the validity of the archive
 The vendor provides the required VNF software components and auxiliary files to
run and manage the VNF in VNF package
VNF Lifecycle Management
VNF Lifecycle Management-VNF Package

• VNFD is basically a configuration template that describers a VNF in terms of deployment and operational behaviour ,
it also defines meta data for package on boarding
• VNF Package includes VNF SW image and a manifest file that provides package integrity and authenticity

• Other artefacts may includes scripts , license , change history , certificates ..etc
VNF Lifecycle Management-VNFD
VNF Lifecycle Management-VNFD
VNF Lifecycle Management
VNF Lifecycle Management-VNF Package

 Why a standard VNF


package is needed ?
VNF Lifecycle Management-Instantiation (1-2)
VNF Lifecycle Management (2-2)
VNF Lifecycle Management-Scaling
NS Lifecycle Management – NS Catalogue
NFV Terminology
 Hypervisor
NFV Terminology
 Virtual Machine
NFV Terminology
 vNIC/vSwitch
NFV Terminology
NFV Terminology
NFV Terminology
NFV Terminology
STC Scope
STC Telco Cloud Scope
In STC:
 2 sites each one 30Gbps M2M
 NFVO , VNFM,VNFs Huawei 2 GGSN, 2 MME
 HW: Dell
 VIM: RedHat
 SDN Controller : Juniper Contrail
 VNF and VNFM from the same vendor
 Each VIM has a certain capacity of 250 nodes , so we have 2 PODs each is considered as separate DC
 NFVO manages all the PODs
Thank you
Containers or Virtual Machines !
Comparison
Advantages of Containers
Use Cases -Zero Downtime Deployment
Use Cases –Micro services
 Microservice is a SW architecture that
divide the one bulky application to a
seperate small portion of SW (called
microservices) that allow flexibility and
scalability

 containers fits perfectly in this new


architecture , as you can make each
container handles one microservice , such
as DB , processing ..etc

 Orchestration allows for easily scalability


by auto scaling the container for specific
workload
Use Cases – Containers and cloud transformation

 Cloud transformation is the process of migrating your existing IT infrastructure to the cloud ,
many companies today are making the transition away from locally-hosted services towards
services hosted in the cloud

 its easy to wrap the existing applications such as web services ,mail service into containers
and then run those containers on the cloud
 Cloud service providers usually accounts for compute/processing units used , so in case of
containers which needs fewer resources than VM or other technology we will save a lot of
OPEX
E2E SO
 OSS/BSS will handle the service between virtual and physical domains , E2E SO
can fit within OSS block in ETSI reference model
How to explore ETSI website

g/technologies/nfv
References

 NFV Technical Training (delivered by Karim Rabea in STC)


 ETSI NFV White Paper
 ETSI GS NFV-MAN 001
 ETSI GS NFV-SWA 001
 ETSI NFV- IFA-007
 Linux Academy (Containers Part)
Openstack Components/Projects

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy