NFV Use Cases

by Abdul Ravoof

NFV Definition

Network Functions Virtualization (NFV) aims to transform the way that network operators architect networks by evolving standard IT virtualization technology to consolidate many network equipment types onto industry standard high volume servers, switches and storage, which could be located in a variety of NFVI-PoPs including datacenters, network nodes and in end user premises

In short , Act of Being Something without being it

NFV Objectives

• Rapid service innovation through software-based deployment and operationalization of network functions and end-to-end services.

• Improved operational efficiencies resulting from common automation and operating procedures.

• Reduced power usage achieved by migrating workloads and powering down unused hardware.

• Standardized and open interfaces between network functions and their management entities so that such decoupled network elements can be provided by different players.

• Greater flexibility in assigning VNFs to hardware.

• Improved capital efficiencies compared with dedicated hardware implementations

Introduction on Use Cases

• Contains Service Models of Cloud Computing & applications of networks & Market Segments

• Virtual Network Function as Service ( VNFaaS)

• Virtualization of Mobile Core Network and IMS

• Virtualization of Mobile Base Station

• Virtualization of Home Environments

• Virtualization of CDNs

• Fixed Access Network Functions Virtualization

• Virtual Network Platform as a Service (VNPaaS)

• Virtual Network Infrastructure as a Service (VNIaaS)

• Virtualization Forwarding Graphs

Virtual Network Function as a Service( VNFaaS)

Motivation :-

• Virtualization of control plane functions improves scalability

• Virtualization of enterprise CPE ( access router ) to provider’s network

• Operate VNF instance for to implement enterprise CPE

• VNF instance for control plane of PE router to improve scalability

• VNF functionality available to enterprise as service = cloud computing software as service

• In SaaS , customer can manage application only from a configuration perspective & cannot control the complete infrastructure layer

• VNF = service provider application & Enterprise = consumer of the service

Advantages of VNFaaS

• Modest software tool footprint for the enterprise to access the service

• Efficient use of software licenses

• Centralized management and data

• Savings in up-front costs

VNFaaS Description

• Virtualization of CPE functions ( vE-CPE) in the Service provider Cloud • Virtualization of PE functions in the service provider cloud • vE-CPE and vPE may be controlled by a centralized controller following the SDN architecture principles & standards( e.g. OpenFlow) • Service provider is responsible for deploying, configuring, updating & managing VNF instance to provide expected SLA

Figure : Service Provider without Virtualization

Virtual Enterprise CPE(vE-CPE) Solution

• Eliminates the need of multiple CPE appliances benefitting lower CAPEX & OPEX

• Multiple CPE appliances includes advanced IPv4/IPv6 routing, firewall, intrusion detection, digital voice, WAN optimization Controller, DPI, Layer 3 VPNs, QoS support and MPLS

VNFaaS Virtual PE(vPE) Solution

Provider Provisioned Virtual Private Network Service (PPVPNS) functions in the vPE include layer 3 IP VPNs, layer 2 VPLS, EVPN, pseudo-wire services and more

Figure : Virtualisation of CPE, Virtual Network Services and PE core facing functions

VNFaaS Virtualization Target

• AR - Enterprise Access Router / Enterprise CPE

• PE - Provider Edge Router

• FW - Enterprise Firewall

• NG-FW - Enterprise NG-FW

• WOC - Enterprise WAN optimization Controller

• DPI - Deep Packet Inspection (Appliance or a function)

• IPS - Intrusion Prevention System and other Security appliances

• Network Performance Monitoring

VNFaaS Mixed Virtualization Scenarios

• Upper branch, the vE-CPE is implemented in the operator NFV network • Lower branch, represents a legacy solution provided by non- Virtualized branches

VNFaaS Problem description/Issues

• vE-CPE and vPE are required to support a large number of applications

• large number of Virtualised devices need to be integrated on limited number of CPUs

• Be integrated in a single virtual machine

• Be split across a core set of functions and virtual network services functions

• vPE and vE-CPE be controlled by a centralized controller following the SDN architecture principles and standards

• Extending the Enterprise LAN into the operator network requires a VPN between the enterprise and the operator virtual function