sdns and nfv: why operators are investing...

SDNs and NFV:

Why Operators Are Investing Now

An Infonetics Research webinar co-produced with

Ciena, Fujitsu and Radisys

2

Today’s Speakers

Michael Howard

Co-Founder and Principal

Analyst, Carrier Networks

Infonetics Research

Ralph Santitoro

Director of Strategic Market

Development

Fujitsu Network

Communications

Mitch Auster

Senior Director - Product

Marketing

Ciena

Eric Gregory

Director, Product

Management

Radisys

JoAnne Emery

(Moderator)

Event Director

Infonetics Research

Agenda

3

SDN Trends

3

4

Problems and Challenges

New Options and Solutions

Service Provider Deployment Applications

Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

4 4

Infonetics Definition: SDNs Are Subset of Programmable Networks

‣ SDNs enable networking applications to request and

manipulate services provided by the network…

‣ …and allow the network to expose

network state back to the applications

‣ 2 common types of SDNs

• API

• Control plane abstracted

from data plane

Programmable Networks

Network

APIs

SDN “API”

protocols

* IETF SDNP

* ALTO

* OpenFlow

* PCE

* BGP-TE

SDNs

SDN

“Control Plane”

Protocols

© Infonetics Research 2013

5 5

Infonetics View of Carrier Network Architecture ~2020

MBH N.A.

Home

services

Business

VPNs

CDN

Mobile Core

EPC

Cloud

Services

Optical

Transport

MBH Asia

Consumer

Broadband

RAN

Access/

Aggregation

App

Network Control & Map

Centralized Control & Orchestration: Controller of Controllers

Holistic, Global End-to-End View of Network

Distributed

Domain

Controllers

(e.g., OpenFlow)

SDN-optimized

Network Hardware

Servers for

NFV, cloud, etc.

App App

Services Control & Map

Policy input

Control is

distributed

Gather network

and subscriber

behavior

Real-time

analytics

Feedback to

Apps, control,

policy


6

Why Service Providers Want SDNs & NFV

Top Drivers

‣ New revenue and operational efficiency drive SDN/NFV

• #1 Service velocity (100%) — quicker time to new revenue

• #2 Simpler provisioning over multi-vendor networks

• #3 Lower OPEX with master view over multi-vendor, multi-layer

• Corollary: Global view and network intelligence means networks

can run hotter — saves CAPEX

• Corollary: Global view and subscriber intelligence means quicker

new services and new revenues

‣ Translation: Need more automation, new paradigm


Strategy to Deploy SDNs

7

82% Plan to deploy SDNs in their

existing networks, not just in

greenfield networks

“Hybrid SDN” is critical


8

Likely Domains for Deployments

‣ Prioritized list of SDN target domains

• DC-related: intra-DC, inter-DC, cloud services

• Consumer/business services via “virtual CPE”

• Optical transport

• EPC/mobile core, BNG/BRAS, mobile backhaul,

metro aggregation


Contained Domains—Data Centers Are Easy

9

‣ Service providers are inspired by DC SDNs as proof of concept

• 3 years of Google resources/investments + Nicira smarts solves

operational problems of data center environment

• SDNs work!

‣ DC is simple contained domain…while service provider

networks are much more complex

• Much bigger challenge / much bigger payoff

‣ SDNs will take time

9 © Infonetics Research 2013

Agenda

10

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

Current Network Issues

Manage a bunch of boxes,

from different NE vendors

heterogeneous EMSs,

control planes ...

Embedded service

intelligence in multiple NE

types, of different vintage,

from different vendors

Application service-layer and

networks (mobile, WiFi, fixed

broadband) are all silos

Slow and costly service

innovation, deployment

Constrained service

differentiation

Static, one-size-fits all

network service pricing

Tedious Operations &

Inconsistent, Inefficient

Service Delivery

11

PMO

Service Delivery Is Inflexible & Inefficient

Residential

Business

Mobile

12

Challenges for WAN Service Providers

Cloud Services

IT

World

WAN Services

Telecoms

World

On Demand Automated

Elastic Programmable

Services

Cloud applications changing how WAN services are used Carrier networks must evolve to support this new reality

13

Cloud Services

Short service lifecycle

Automated service activation

Frequent changes (Elastic)

Open and programmable

WAN Services

Long service lifecycle

Manual service activation

Infrequent changes

Proprietary & hard to program

Challenges with Network Programmability

Computing Devices and Cloud Environments vs. Wide Area Networks

Easy to program: Computing Devices and Cloud Environments

• Singular, technology-abstracted programming environments

• Open, standardized, and “de facto” APIs, OSs and development tools

Difficult to program: Wide Area Networks

• Multi-vendor, multi-technology with limited technology-abstraction

• Diversity of protocols, interfaces and APIs for EMSs and network elements

14

Telecom Cloud Components

TEMs will need an approach that enables a non-disruptive migration

15

Where is the middle

ground?

Where to

start?

‣ Determined to leverage existing hw architectures

‣ Must deliver cost savings to stay in the game

SDN NFV

‣ Determined to follow Enterprise Virtualization Path

‣ High Availability requirements must still be met

Operators desiring improved

financials

Vendors trying to maximize

utilization through automation

IT Infrastructure is not a “drop in” for telecom

Enterprise Cloud ≠ Telecom Cloud

Enterprise Cloud

Less Strict “3 9s”

Reliability Requirements

Some Latency

Homogeneous Transport

(Ethernet)

Single Control Protocol

(OpenFlow)

Controlled Data Center

Operating Environment

Smaller Number of

Warehouse-sized Data Centers

Telecom Cloud

Strict “5 9s”

Reliability Requirement

Low Latency

Heterogeneous Transport

(Optical, Ethernet, Wireless)

Multiple Control Protocols

(OpenFlow, SNMP)

Regulatory Requirements

(NEBS)

Larger Number of Smaller,

Distributed Data Centers

16

Agenda

17

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

SDN Paradigm & the Power of “Global Views”

‣ Abstraction and

Layering

‣ Openness

‣ Global “Views” &

Explicit Control

‣ Virtualization

‣ Automation &

Orchestration

‣ Better Leverage of

Policy & Analytics

Control Layer

Global Network State/Control

Infrastructure Layer

Application Layer

AP

I

AP

I

AP

I

AP

I

AP

I

Network Virtualization

Global Demand Synthesis

Real-Time

Analytics

+

18

PMO

Network Functions Virtualization + SDN Enable Efficient Network Service Delivery

Software-defined

packet-optical metro

Expensive network functions are more

centralized and virtualized on shared high-

performance COTS servers

Data

Center

Residential

Wireless

Enterprise

Aggregate & Express

19

Programmable Networks from an SDN Perspective .. like programming devices and cloud applications

In the Southbound direction

Abstracts networking technology/protocol details from NetOS/Controller

Provides vendor-independent programmability of network elements

In the Northbound direction

Provides network programmability (APIs) by software applications

Abstracts networking technology details from the applications

Enables automated, on-demand capabilities just like cloud apps enjoy today

Northbound APIs (network abstraction)

Network OS/Controller

Southbound APIs (technology abstraction)

Network Element

Network Element

EMS

Apps Apps Apps

Web 2.0 APIs for Apps to program

network, e.g., RESTful, JSON, XML

Software adapters for

NetOS/Controller to NE/EMS

protocols, e.g., OpenFlow, SNMP,

NETCONF, TL1, MTOSI (XML)

20

Network Element

Apps

Technology Abstraction Multiple layers of abstraction required to make the network programmable

Different Transport Network Technologies

• EoF EoWDM / OTN EoS

• Need “gateways” to convert between different transport technologies

Different Network Layers

• Layer 0/1: Ethernet (EoF), DWDM, OTN, SONET/SDH

• Layer 2/2.5: Ethernet or MPLS-TP

• Layer 3: IP or IP/MPLS

Different NE traffic management implementations

• EAD: 3 CoS, PCP CoS IDs, WFQ scheduler, G.8031/2 or UPSR protection

• Aggregation: 8 CoS, DSCP CoS IDs, 8 DWRR schedulers, G/MPLS protection

• Core: 4 CoS, DSCP CoS IDs, 1 Priority/3 WRR schedulers, G/MPLS protection

21

EoF EAD Agg. EoWDM Core EoS EAD Agg.

GW GW GW Layer 0/1 Layer 2/2.5

Layer 3

EoWDM EoWDM Core

Extremely complex to program networks without technology abstraction Impossible

Transitioning to SDN + NFV

OpenFlow

Overlay: Existing network element exposes an SDN

interface to enable centralized control

Hybrid: The network element starts off with a separated in-skin distributed control and

data plane. Control plane moved physically

at a future date.

Traditional: Tight coupling of Control

and Data Plane

A hybrid architecture offers a simple phased approach to network transformation

Data Plane

Control Plane

Data Plane

Control Plane

Control Plane

Control Plane

Data Plane

22

Agenda

23

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

SDN-based Network-as-a-Service

Enterprise A

Resource Broker & Scheduler app.

BWoD Portal app.

Enterprise A

Enterprise B

Cloud Data

Center

SDN Controller

Dynamic

Pricing

e.g. IT-WAN ASM

Maximized profitability through self-serve mass

customization and analytics-based dynamic pricing

24

Traffic Steering for Mobile QoE Management

‣ Content delivery protocols (e.g. ABR) work fine when network impairments build slowly

• Use buffer fill on client device to signal server to adjust coding rate

‣ Impairments on mobile networks change too quickly for ABR to handle

‣ Use real-time knowledge of RAN to trigger coding rate change well before client can

• Steer through real-time transcoder

SDN Controller

QoE Manager RAN Traffic

Monitor

ABR feedback loop

Transcoder

25

Vision for Network Functions Virtualization (NFV)

Traditional Approach

• Purpose-built network appliances

• Physical install per appliance per site

NFV Approach

COTS servers and storage

Virtualized Network Functions (vNFs)

Set Top Box

Message Router

Firewall DPI

CDN

Tester/QoE monitor

Residential Gateway

Carrier Grade NAT

Session Border Controller

BRAS PE Router S/GGSN

26

Packet / Optical Network Equipment

With NFV, network functions no longer fixed in time and space

Service Provider Programmable Networks Using Network Functions Virtualization (NFV)

Virtualized Network Functions (vNFs)

Some network functions (NFs) moved out of NE and run elsewhere in the network

• On COTS blade servers in a data center (or central office)

Optical Transport Network vNFs: Path Computation, Network Defragmentation, etc.

Network Services vNFs: Firewall, IDS/IPS, LTE EPC, Residential Gateway, etc.

Some NFs split between Network Element (NE) and blade server

Part of vNF runs on NE to be “near” forwarding plane to meet performance needs

Part of vNF run on a blade server for scalability and simplified operations

Optical Transport Network

Network Services

NFs

NFs NFs

NFs

NFs

NFs

NFs

NFs

NFs

NFs NFs

NFs

NFs

NFs

NFs

vNF vNF vNF

vNF vNF vNF

vNF

vNF

vNF vNF vNF

vNF vNF vNF vNF

Blade Servers

vNF

vNF vNF vNF vNF

27

Application Transformation Site Router

Site Router

Data Plane • Implemented on NPU ATCA Blade

• Application Virtualization

Routing & Load Balancing

Step 1: Absorb Edge Router into Wireless Gateway

Step 2: Split Control and Data

Planes

Step 3: Break out control plane to SDN

application layer

Applications require a telecom-grade platform to deliver these capabilities

Control Plane • Implemented on an Intel ATCA Blade

• Application Virtualization

OpenFlow

28

Agenda

29

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

‣ Multi-layer and

carrier-grade

‣ Open, modular

control layer

‣ Adding OpenFlow

support to

infrastructure layer

Ciena’s SDN Approach

30

Fujitsu’s Approach to SDN Initial focus on multi-layer technology abstraction to accelerate service delivery

Deliver services over multiple transport technologies

Abstract the Service from the Transport Technology

Just provision service end point attributes

Bandwidth, Protection, CoS, etc.

Normalize technology differences between device types

Using “templates” and middleware to profile a device’s capabilities

e.g., # of CoS, CoS ID type, scheduler types, etc.

Unified platform for mgmt. of services and network resources

31

EoF EAD Agg. EoWDM Core EoS EAD Agg. EoWDM EoWDM Core

These steps are required to create a framework

for a more programmable network to accelerate service delivery

Management & Control

What Is the Best Platform?

Cloud services and virtualization: What is the best platform?

Source: Seeing through the Cloud: A survey of mobile operators' views on the

evolution of the mobile core, Monica Paolini, Senza Fili Consulting, Feb. 2013

ATCA is the clear choice for telecom

environments

Full Survey Results: http://go.radisys.com/paper-lte-2nd-annual-operator-survey.html

http://go.radisys.com/paper-lte-2nd-annual-operator-survey.html











Agenda

33

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

Conclusions: SDN-NFV Here to Stay

‣ A network is a collection of elements/nodes and EMSs using many

technologies, protocols, and architectures, using multivendor equipment

‣ SDN and NFV create a new paradigm for network operations and services

• New levels of innovation not possible with current technologies

‣ New revenue and operational efficiency drive SDN/NFV

• Global network view and intelligence means networks can run hotter—saves CAPEX

• Global network view and subscriber behavior data means new services and quicker

revenues

‣ Many operators are testing, doing proof of concepts (PoCs), learning, and

some are pushing toward initial commercialized services or network

operations based on SDN and NFV

‣ SDNs and NFV are a fundamental change that will take many years for

transformation — but operators are starting now, first in targeted contained

domains

34

What Carriers Expect from SDN & NFV

Networks

Operations

Service

Delivery

Monetization

Global view of services and network, higher utilization, more deterministic control

Automation with higher quality with fewer human resources and network elements

Global view of multi-vendor, multi-layer, multi-technology service-delivery fabric

Automation helps optimize “network as a system” – for QoS, revenue, power,

utilization, etc.

Accelerated time-to-market and revenues; new services at “IT speed”

Scale network, services, and revenue with sub-linear cost

Reduced cost, higher velocity, open platform for service innovation

Better matching of network supply with application demand and user willingness to

pay

35

Agenda

36

Market trends

3

4




Sponsor Approaches

Conclusions

Q&A

1

2

3

4

5

6

7

37

Q&A

Michael Howard

Co-Founder and Principal

Analyst, Carrier Networks

Infonetics Research

Ralph Santitoro

Director of Strategic Market

Development

Fujitsu Network Communications

Mitch Auster

Senior Director - Product

Marketing

Ciena

Eric Gregory

Director – Product

Management

Radisys

JoAnne Emery

(Moderator)

Event Director

Infonetics Research

Thank You This webcast will be available on-demand for 90 days

For additional Infonetics events, visit https://www.infonetics.com/infonetics-events/

https://www.infonetics.com/infonetics-events/



Appendix

40

Vendor 3

Value of abstracting full data center domain

The DC Is a Contained Domain for Abstraction…

SDN Controller

Nicera

App App App App App App

App App App

VMs

VMs

VMs

Vendor 2

L2 Ethernet

40

Hypervisor

VMWare


41

…But Carrier Networks Are Unconstrained Planes

• Multi-equipment types

• Dare we tackle multi-operator?

SDN Controller

App App App

Wholesale

connections

Mobile backhaul

Vendor 3

Vendor 2

L0 WDM

Vendor 3

Vendor 2

L1 OTN SDH SONET

Vendor 3

Vendor 2

L2 Ethernet

Vendor 3

Vendor 2

L3 Routing

Vendor 3

Vendor 2

L4–L7

PON

FTTH

DSL

• Multi-layer

• Multi-vendor

Business

connections

41

L3 VPNs

L2 VPNs

VLANs

L3 VPNs

L2 VPNs

Ethernet

services

L3 VPNs

L2 VPNs

VLANs

L3 VPNs

L2 VPNs


42

Carriers Start with Contained Domains, e.g., EPC

SDN Controller

App App App

Mobile Packet Core, EPC

Vendor 3

Vendor 2

L0 WDM

Vendor 3

Vendor 2

L1 OTN SDH SONET

Vendor 3

Vendor 2

L2 Ethernet

Vendor 3

Vendor 2

L3 Routing

Vendor 3

Vendor 2

L4–L7

42 © Infonetics Research 2013

sdns and nfv: why operators are investing...

Documents