impact of nfv and sdn on connectivity networks · october 2014 anthony magee –business...

October 2014

Anthony Magee – Business Development Director

Impact of NFV and SDN on Connectivity Networks

© 2014 ADVA Optical Networking. All rights reserved. Confidential.22

• Present network architecture and technology layering

• Introduction to NFV

• Impact of NFV and SDN• Connectivity Provisioning• What Functions to Virtualize

• Network Demarcation in NFV and SDN Networking

• Collaboration activities

Agenda


Access/

Aggregation

Metro Transport

Typical Legacy Network Scenario

Base Station

Enterprise

Residential

DSLAM

BRAS

LER

OTN

RNC, MSC

WDM or PON

Carrier Ethernet

Core Transport

Point of Presence(PoP)

DWDM

OTN

Technology trend: MPLS to the edge, increasing Bandwidth Requirements

Technology trend: switched OTN layer, high scalability, CP interworking

xDSL

MPLS







Agenda


Virtualization Is Not A New Concept

Switch BoardDedicated hardware for single application

Soft SwitchApplication running on shared servers

Virtualization impacts architecture and technology of operator networks


Traditional Network Appliances Virtualized Network Functions

What is Network Functions Virtualisation?

Common hardware, software-based provisioning, accelerate innovation

BRAS

FirewallDPI

CDN

Tester/QoE

Monitor

WAN

Acceleration

Message

Router

RAN Controller

Carrier

Grade NAT

Session Border

Controller

PE RouterSGSN/GGSN

Standard, High-Volume

Servers


Storage


Switches

htt

p:/

/ww

w.e

tsi.org

/technolo

gie

s-c

luste

rs/t

echnolo

gie

s/n

fv


• Virtual Customer Premises Equipment (vCPE)• Virtual Customer Premises Equipment (vCPE)

• Virtual Home Gateway (vHG)• Virtual Home Gateway (vHG)

• Virtual EPC (vEPC), Centralized RAN (C-RAN)• Virtual EPC (vEPC), Centralized RAN (C-RAN)

Initial NFV Implementations

Targeting mobile, residential and business applications

Residential Services

Business Services

Mobile Networks







Agenda


1. Start: Firewall runs as virtualized network function (VNF) in DC 1;

Impact of NFV on Network Control and Connectivity Network

Enterprise

Transport Network

Network Resource Controller

Resource Orchestration

Computing Resource Controller

COTS Server

virtualizedfirewall

Data Center 1


1. Start: Firewall runs as virtualized network function (VNF) in DC 1; as Enterprises scale, and new VNFs are deployed DC1 resource alarms start ringing !!!


Enterprise

Transport Network




COTS Server

virtualizedfirewall

Data Center 1


1. Start: Firewall runs as virtualized network function (VNF) in DC 1; as Enterprises scale, and new VNFs are deployed DC1 resource alarms start ringing !!!

2. Orchestrator decides to move some VNFs to DC 2

a) Computing Resource Controller moves some VNFs from DC 1 to DC 2

b) Network Resource Controller allocates capacity for moving data between DC1 and DC2

c) Network Resource Controller sets-up new flows from enterprise to DC2


Enterprise

Transport Network



COTS Server

virtualizedfirewall

Data Center 2


COTS Server

virtualizedfirewall

Data Center 1

2.a

2.c

2.b



Enterprise

Transport Network



COTS Server

virtualizedfirewall

Data Center 2


COTS Server

virtualizedfirewall

Data Center 1

• Software Defined Networking: network, computing and storage resources can be allocated by software

• Virtualization: hypervisor shares resources among multiple users/ applications

• Orchestration: coordinated allocation of network resources and computing/ storage resources

• Transport SDN: flow-based PtPconnectivity network, centrally “programmed” (= real-time, software provisioning)


NFV/SDN Impact on Control of Connectivity Network

Transport Network

Network Resource Controller aka Network Hypervisor

DC 2

DC 1

Distributed routing- and signaling e.g. IP/MPLS

Packed flows programmedthrough open interfaces

and open software controllers

CPE







Agenda


To Virtualize or Not to Virtualize

Not all network functions are perfect candidates for virtualization

• Limited life-time of function or service

• Flexible adaptation of parameters and algorithms

• Moderate processing and storage load

• Limited life-time of function or service

• Flexible adaptation of parameters and algorithms

• Moderate processing and storage load

Where Virtualization Works

• Limited gains from resource sharing

• Performance and delay-critical functions

• Static functions, deployed in high volume

• Synchronization

• Limited gains from resource sharing

• Performance and delay-critical functions

• Static functions, deployed in high volume

• Synchronization

Dedicated Hardware Preferred


• Connectivity network becomes “programmable”: connectivity is established by central control through open interfaces with pre-defined service parameters

• Some functions will require hardware support e.g. network synchronization, encryption at lower network layers

• Each network element in a connectivity network will also provide processing and storage capacity

Intermediate Summary

Data Centre becomes Network / Network becomes Data Centre


Evolution of Network Demarcation towards NFV/SDN-Centric Networking

Ethernet OAMEthernet OAM

Auto. ActivationAuto. Activation



L3/4 OAML3/4 OAM

ProgrammabilityProgrammability

SecuritySecurity



L3/4 OAML3/4 OAM

ProgrammabilityProgrammability

SecuritySecurity

StorageStorage

VF ServerVF Server

functionality

network evolution

proNID

proNID (VM)

NID







Agenda


SDN

FMCNG-POP

EU Project - Fixed Mobile Convergence

19

FMC ToolboxFMC Architectural Blueprint

NFV

Grant Agreement N°: 317762


NFV and Structural vs Functional Convergence

20

• Structural convergence is defined as sharing/mutualization of network equipment and infrastructure resources for several network types. The moving of existing functions of different network types to a unified network entity for a better distribution of functions belongs to structural convergence.

• Functional convergence means the implementation of a generic function to realize similar goals in different network types (fixed, mobile, Wi-Fi). This includes the moving of functions in order to merge specific fixed, mobile and Wi-Fi functions into some generic functions.

Mobile

- Network Functions

FixedStructural converged Network

Mobile

FixedFunctional converged Network


COMBO UAG Deployment Models

BBU hotel

eNB

Wi-Fi AP

Mobile:

Backhaul & Fronthaul

Access / Aggregation

Network

eNB

CPRI Test

Fixed Line:

Residential/Business & Wi-Fi/Small Cells

Content

Cache

Mobile

EPCuAAA PMM

IntfcSelect

UAG

eNB

Fixed Line

NID/RGW

Advanced Interface

Selection and 3D Handover

Simultaneous Transport of Fixed Line and Mobile over Converged

Access/Aggregation Network


Service Provider SDN Connectivity Demo

• Common optical connectivity network• Self-provisioning / virtualized optical and

Ethernet network resources• Multiple concurrent clients such as DCs,

customers, customer applications• Network programmability by OpenFlow• Open software DayLight controller

programs the network

DC Site 1DC Site 1

MAN / WANConnectivity

DC Site NDC Site N

Customer Site 1Customer Site 1 Customer Site 2Customer Site 2

Customer NMS / BSSCustomer NMS / BSS

Customer Domain

Operator Domain

OF Progr.Interface

Optical NetworkHypervisor


• Programmability is paradigm of SDN/NFV-centric networking

• Open interfaces and open software controllers for painless network integration

• Not all network functions can be virtualized

• Demarcation devices will become programmable and provide processing/storage resources

• New business models are enabled by adoption of NFV & SDN

Key Takeaways

[email protected]

Thank You

IMPORTANT NOTICE

The content of this presentation is strictly confidential. ADVA Optical Networking is the exclusive owner or licensee of the content, material, and information in this presentation. Any reproduction, publication or reprint, in whole or in part, is strictly prohibited.

The information in this presentation may not be accurate, complete or up to date, and is provided without warranties or representations of any kind, either express or implied. ADVA Optical Networking shall not be responsible for and disclaims any liability for any loss or damages, including without limitation, direct, indirect, incidental, consequential and special damages, alleged to have been caused by or in connection with using and/or relying on the information contained in this presentation.

Copyright © for the entire content of this presentation: ADVA Optical Networking.

Grant Agreement N°: 317762

Acknowledgements:

impact of nfv and sdn on connectivity networks · october 2014 anthony magee –business...

Documents