Moving along the NFV Way - IEICE The Institute of Electronics...

Moving along the NFV Way_

Diego R. Lopez Telefónica I+D May 2014

DISCOVER, DISRUPT, DELIVER

Network functions are fully defined by SW, minimising dependence on HW constraints

DPI BRAS

GGSN/ SGSN

Firewall

CG-NAT

PE Router

VIRTUAL NETWORK FUNCTIONS

COMMON HW (Servers & Switches)

FUNCTION

CAPACITY

The NFV Concept


NFV-based Target Service Provider Network

•  The target is a simplified, less expensive service provider network •  Service level functionality should be implemented largely in software •  The network infrastructure consists of low unit cost COTS network

elements: servers, packet optical transport, data center switches and storage

•  Leverage low cost per unit to provide bandwidth expansion and increasing range of services

•  Use distributed storage instead of expensive routing and transport to deliver popular, high volume content

•  Use software-based service delivery to be more responsive to new requirements from customers and market opportunities

•  Automate management and provisioning to the greatest extent possible •  From hardware-based networks to software defined, virtualized ones •  Leverage SDN for application-aware routing, and separation of packet

forwarding from control to rapidly introduce new services and adapt to changing traffic patterns

•  Network functions, caching, applications, enablers all run in virtualized distributed data centers

•  IP & transport infrastructure still used as necessary in optical backbone and Internet


Architectural Use Cases

• Network Functions Virtualisation Infrastructure as a Service §  Network functions go cloud-

like • Virtual Network Function as a Service §  Ubiquitous, delocalized

network functions • Virtual Network Platform as a Service §  Applying multi-tenancy at

the VNF level • VNF Forwarding Graphs §  Building E2E services by

composition

!


Service-Oriented Use Cases

•  Mobile core network and IMS §  Elastic, scalable, more resilient EPC §  Specially suitable for a phased approach

•  Mobile base stations §  Evolved Cloud-RAN §  Enabler for SON

•  Home environment §  L2 visibility to the home network §  Smooth introduction of residential

services

•  CDNs §  Better adaptability to traffic surges §  New collaborative service models

•  Fixed access network §  Offload computational intensive

optimization §  Enable on-demand access services

!

!


The NFV Framework

NFV Infrastructure

End Point

End Point

E2E Network Service

Compute Storage Network HW Resources

Virtualization Layer Virtualization SW

Virtual Compute

Virtual Storage

Virtual Network

Virtual Resources

Logical Abstractions Network Service

VNF VNF VNF

VNF VNF

Logical Links

VNF Instances

VNF VNF VNF SW Instances

VNF : Virtualized Network Function

VNF


XaaS for Network Services

NFVI Provider

IaaS NaaS NaaS SaaS

NFVIaaS

Hosting Service Provider VNF

VNF VNF

VNF VNF

VNF

VNF VNF

VNF

VNF Tenants

NSP

VNF VNF

VNF

VNF

VNF

VNF Forwarding Graph Admin User

Admin User

VNFaaS

User

PaaS PaaS

VNPaaS


The NFV Reference Architecture

Computing Hardware

Storage Hardware

Network Hardware

Hardware resources

Virtualisation Layer

Virtualised

Infrastructure Manager(s)

VNF Manager(s)

VNF 2

OSS/BSS

NFVI

VNF 3

VNF 1

Execution reference points Main NFV reference points Other reference points

Virtual Computing

Virtual Storage

Virtual Network

EMS 2

EMS 3

EMS 1

Service, VNF and Infrastructure Description

Or-Vi

Or-Vnfm

Vi-Vnfm

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vi

Vn-Nf

Vl-Ha

Orchestrator


Proofs of Concept

•  Look for practical results •  Demonstrate and disseminate

NFV capabilities •  Explore technology options •  Facilitate gap analysis •  Contribute to guide the

future ISG activity •  Lightweight process

•  Few (objective) requirements to file a PoC proposal

•  Run PoC project •  Openly report results to the

community

•  The call is open along the ISG lifetime


It Ain’t Cloud Applied to Carriers

The network differs from the computing environment in 2 key factors…

Data plane workloads (which are huge!)

Network requires shape (+ E2E interconnection)

HIGH PRESSURE ON PERFORMANCE

GLOBAL NETWORK VIEW IS REQUIRED FOR MANAGEMENT

1

2

…which are big challenges for vanilla cloud computing.

AN ADAPTED VIRTUALISATION ENVIRONMENT IS NEEDED TO OBTAIN CARRIER-CLASS BEHAVIOUR


CLOUD COMPUTING NFV

1. PERFORMANCE BOUND TO CPU 1. PERFORMANCE BOUND TO I/O & MEMORY ACCESS

2. AGGREGATED VIEW OF RESOURCES (CPU, memory, etc.)

2. NUMA VIEW Internal architecture is relevant for guests

3. ENDPOINTS Applications need the OS

3. MIDDLEPOINTS Data-plane network functions bypass the OS

4. NODE-CENTRIC Shapeless interconnection

4. NETWORK-CENTRIC The network has a shape

5. MANY AND SMALL VMs 5. FEW AND LARGE VMs

Cloud Computing vs NFV


v v

COTS HW

LOCAL PoPs REGIONAL DATA CENTRES

Centralized Control Plane Distributed Data Plane

OS + HyperVisor

MPLS/SDN/Optical

Infrastructure

Service Domain

Network Domain

CDN Video

P-CSCF

EPC BRAS

CG-NAT DPI

SDP CSFB

IMS

DHCP PCRF

DNS UDB

COTS HW

OS + HyperVisor

MPLS/SDN/Optical

SRVCC

HW and SW decoupling

HW and SW decoupling

GGSN

PE

Security

NGIN

M/SMSC

Networks PoPs and datacentres intra- and inter-communications will be critical to guarantee network service elasticity and network plasticity

Redesigning Network Segments


With the Proper Balance between NFV & SDN

BNG CONTROL CG-NAT SW-defined network functions §  Separation of HW and SW §  No vertical integration

-  HW vendor ≠ SW vendor ≠ Mgmt vendor §  Once network elements are SW-based, HW

can be managed as a pool of resources

NFV

Interconnecting Virtual Network Functions (a.k.a. backplane) §  Separation of control and data plane §  Easy orchestration with SW domain

SDN

DHCP

UPnP

TR-069

IPv4 / IPv6

Session mgmt

NAT

NAT ctrl.

Pool admin

POOL MGMT


@Cloud VM

Bare Metal

Acceptable performance

Bare Metal VM

@Cloud

GAP

x10

Bare Metal VM @vPoP

EXEC

UTI

ON

MA

NA

GEM

ENT EX

ECU

TIO

N

MA

NA

GEM

ENT

What defensive Industry says

What can be achieved doing things well(*)

80 Gbps per COTS blade

(*) ETSI NFV Work Item “NFV Performance & Portability Best Practises”: DGS/NFV-PER001 Current version: v0.0.7 (stable draft – 15/10/2013)

High and Predictable Performance is Achievable


An Evolutionary Approach

• NFV implies a significant change for current network infrastructures §  No zero-day approach is feasible §  Avoiding disruptions

•  Identify relevant use cases §  Emerging services §  Reuse of equipment still in amortization §  Leverage on new planned elements in

architecture • Plan for phased deployments §  Interworking with existing infrastructure §  Not breaking current operational practice

• Take advantage of NFV advantages §  Flexibility §  Extensibility §  Reusability

Soft-Node

DS vCPE


•  Simple, stable along the time and cheaper customer premises equipment

•  Quick and transparent migration to IPv6

•  Service evolution and operation is supported inside telco network

•  Monetize cloud and video services (virtual set top box)

•  Monetize security and digital identity features

EXPLORE PoC TRIAL DEPLOY

MATURITY LEVEL

Switch Access Point Módem

Virtual CPE

FW

TR-069 NAT

UPnP

DHCP

IPv4/IPv6

STB Home environment

Telco Network environment

Shifting network functions deployed in home environment to the network…

Live trial today

Commercial before end 2014

NFV Current Targets: Virtual Residential CPE


•  >80 Gbps line rate per server

•  Stable signatures

•  Flexible data analysis and signature upgrade

•  Forensic analysis feasible.


MATURITY LEVEL

RAW USER TRAFFIC

OF Controller OF Switch

Deeper

REAL-TIME ANALYSIS

Network Big Data

RELEVANT INFO Metadata interface

RAW USER TRAFFIC MITIGATION

Copy

POLICY DECISIONS

Security Alarms

OpenFlow

Other data

xDRs

CENTRALISED INTELLIGENCE

NFV domain

SDN domain

NFV Current Targets: Elastic DPI


•  QinQ termination

•  LPM Routing

•  GRE tunnelling (reference for wholesale services)

•  MPLS tunnelling

•  80 Gbps line rate switching per server

BNG


MATURITY LEVEL

NFV Current Targets: SW BNG


•  Common routing protocols supported and extended by open source project.

•  Well-known router command line.


MATURITY LEVEL

Leverage on open source routing project (Quagga) as rich and widely tested protocol suite while assuring data plane performance

OPEN-SOURCE CONTROL PLANE

(Quagga + Linux)

OPTIMIZED DATA PLANE

(DPDK-based)

•  High-performance line-rate data plane.

•  Running as separate process, does not lead to licensing issues.

NFV Current Targets: Enhanced Virtual Router


PoC Develop

Time

AVAILABLE

Industry

SDOs & de facto technologies

Exploration Trial & Industrialised product

Deployment

Months

Open source & basic technologies

Standardise Drive

ROADMAP ACCELLERATION

Accelerating Transformation


Commodity HW

OS + Hypervisor

Commodity Switching infrastructure

Virtualised Infrastructure

Manager

VNF Manager Virtual Network

Functions

Orchestrator

Legacy OSS/BSS

Current State of the Art is good enough (if properly arranged)

ADD VALUE HERE: Industry should focus on

providing differential VNFs

and Network Orchestration

ADD VALUE HERE: Industry should

focus on providing differential VNFs.

Credible ROADMAP needed!!

Network Virtualisation Infrastructure and its Management should become COMMODITY

Network Virtualisation Infrastructure and its Management should become completely homogenous (commoditized if you like)

Work is needed in Open Source

to AVOID proliferation of VERTICAL SOLUTIONS

Closing the Gaps


Taking a First Step: The NFV Reference Lab @ Telefónica

22

NFVO

Proper HW & Hypervisor

config

ADD VALUE HERE: Network Orchestration

on top of Carrier-grade

OpenStack

VNFs

ADD VALUE HERE: Simplest integration

NFVI VIM = OpenStack++ OFC++

BASELINE TECHNOLOGIES

ECOSYSTEM

ECOSYSTEM

Carrier-grade OpenStack going to upstream

development

Moving along the NFV Way - IEICE The Institute of Electronics...

Documents

Transcript of Moving along the NFV Way - IEICE The Institute of Electronics...