57
Software Defined Network dla Operatora czy to ma sens Adam P. Grodecki [email protected] Kraków 30.09.2013

Kraków 30.09.2013 Software Defined Network dla · PDF fileSoftware Defined Network dla Operatora ... SingleRAN SingleFAN Single Metro Single Backbone SingleCloud GSM/UMTS/HSP A/LTE

Embed Size (px)

Citation preview

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Software Defined Network dla Operatora –

czy to ma sens

Adam P. Grodecki

[email protected]

Kraków

30.09.2013

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 2

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 3

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 4

SDN – review – is there any order?

XML

YANG schema

Python

ASIC VMware

OpenFlow

OpenStack

NetConf

eSDK Cloud

Stack

BYOD

PM

TCL

SLAX

XSLT

XMPP

Perl

IRS

SDN

Overlay

OF

Config

OVS

Orchiestration

LLDP

OTV

VSM/VEM

Open

API

CDN

service

IaaS

NaaS

CaaS

Security

aaS

REST

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 5

SDN – review – is there any order?

XML

YANG schema

Python

ASIC

VMware

OpenFlow

OpenStack

NetConf

eSDK Cloud

Stack

BYOD

PM

TCL SLAX XSLT XMPP

Perl

IRS

SDN

Overlay

OF

Config

OVS

Orchiestration

PCEP

OTV

VSM/VEM

Open

API

CDN

service

IaaS NaaS

CaaS

Security

aaS

Application Layer

SDN Controller

Device Layer

REST

Southbound BGP

Northbound NetConf

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 6

SDN – review – why?

XML

YANG schema

Python

ASIC

VMware

OpenFlow

OpenStack

NetConf

eSDK Cloud

Stack

BYOD

PM

TCL SLAX XSLT XMPP

Perl

IRS

SDN

Overlay

OF

Config

OVS

Orchiestration

PCEP

OTV

VSM/VEM

Open

API

CDN

service

IaaS NaaS

CaaS

Security

aaS

Application Layer

SDN Controller

Device Layer

REST

Decoupled

Flexible

Interactive

Open

BGP

NetConf

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 7

SDN – review – why?

Application Layer

SDN Controller

Device Layer

Decoupled

Flexible

Interactive

Open

DC App Carrier App End User App

L2 forwarding,

Addressing

Bandwith Utilization

L3 forwarding,

Addresing,

TTM

Service Orchestration

Elephant Traffic,

Quality on Demand

Business Transparency

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 8

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 9

SoftCOM Network Paradigms

Network Function Virtualization

Network Function Virtualization

Software Defined

Networking

Application Driven Innovation

Open API Network Program-mability

Cloud Based

Network Functions

Common IT

Platform

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 10

SoftCOM Innovation / Standardisation Matrix

CP / DP

separation

Software-

defined

control

Network

Function

Virtuali-

zation

Network

Program-

mability

Big Data /

Network

Analytics

Carrier

Overlay

Radio

Access

Mobile

Core

Fixed

Access

Layers

1 – 3

IP,

MPLS,

Ethernet,

OTN, etc

NFV

ITU-T

3GPP

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 11

SoftCOM Standardization Initiatives

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 12

Network Architecture has been Evolving for the Past Decade ALL IP

2000+ 2008 2005 2011

All-IP Technologies

RAN

Platform

FAN

Platform

IP+

Optical

Platform

Cloud

Platform

AD

SL / V

DSL

PO

N/ N

G-P

ON

GSM

/ UM

TS

LTE/ L

TE-A

40G

/ 100G

400G

/ 1T

Ap

p1

Ap

pn

… … … …

ALL-IP enabled platforms

Emerging technologies are plug and

play

SoftCOM

Cloud technology is the

foundation

Beyond network:

Internetized operation,

structurally lowers the

cost

Saving TCO and growing

revenue in new ways

Single

SingleRAN SingleFAN

Single

Metro

Single

Backbone

SingleCloud

Sin

gle

OSS

Sin

gle

BSS

GSM/UMTS/HSP

A/LTE …

ADSL/VDSL/PON/

Ng-PON

Supporting bandwidth requirements

and emerging technologies for 10

years

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 13

TC/ EP

SoftCOM standardization landscape

IETF

ONRC ONF ETSI

ISG

BBF

SIMR

ITU-T

WP/13 or FG

Network Functions Virtualization

SDN @ Telco

Network Virtualization

Framework Network Virtualization

Framework SDN

Transport aspects of SDN

Residential Gateway virtualization

Broadband network virtualization

SDN @ Data Center

NBI API

Use Cases

NetConf

Use Cases

Architecture

Hybrid

OpenFlow

Conf & Mgmt

Testing & Interop

Transport

NBI

Requirements

HL Architecture

Research

Detailed Architecture

Protocols

Test & Interop

CCSA ATIS

IRTF

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 14

Targets in SoftCOM Standardization

ONRC ONF

Leading edge

technology

research

Main battlefield, use

cases, longitudinal

architecture,

extended control

protocol

OpenFlow+

BBF

IETF

ITU-T

Northbound

Interface

API (IRS)

SDN based Bearer &

Resource Control

SoftCOM

One center, multi-cardinal points, cross-SDO coordinate network

Requirement, Use Case, coordinate with telecom

to push ONF, Solution TR, Marketing whitepaper

ETSI ISG

NFV

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 15

Quick Summary of SoftCOM Standardization

„ Huawei cooperating on SDN/NFV standardization topics

› Orchestration

› Performance

„ Carrier SDN Standardization Landscape

› ETSI/BBF/ITU-T driving market and business requirements from a carrier

perspective and High Level Architecture.

› ITU-T driving SDN based Bearer and Resource Management

» One use case is network sharing and virtual network support

› ONF/IETF driving requirement harmonization, detailed architecture, OpenFlow,

Test specifications and IOT

„ Huawei is actively participating to complience verifiacion with

EANTC and ONF Plug Fest testing campaigns

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Huawei Standards Compliance Summary

Standard Work Item Relation to Huawei SDN controller / forwarding nodes

IETF ForcES Not supported

I2RS Support depends on customer interest

PCE PCE for southbound i/f in commercial Forwarding Node, commercial controller, foreseen that

OpenFlow will replace PCE in the long run

NETCONF Supported by controller (pre-commercial) and forwarding node (commercial)

NetMOD Part of NETCONF

ALTO Supported in Controller prototype

NVO3 NVGRE, VXLAN supported by Forwarding Node (commercial)

IDR Supported by Forwarding Node (commercial), RR+ controller is being developed, supports

controlling forwarding node traffic via BGP (non-commercial)

ONF OpenFlow POF supported by S12700 Agile Switch, OpenFlow 1.3 supported by pre-commercial

Controller and Forwarding node, northbound APIs supported by pre-commercial Controller

GSMA OneAPI So far, ONF nortbound APIs only

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Standard progress related to Gi LAN Traffic Steering / Service Chaining

Use Case Huawei contributions on standards Prototype/Product Progress

Traffic Steering

(Gi LAN)

ONF: Arch&NBI WG, proposed use case, SDN-based Service

Chaining

IETF

draft-niu-service-chaining-header

draft-li-service-chaining-requirements

draft-jiang-service-chaining-arch

draft-liu-service-chaining-use-cases

draft-xjz-nfv-model-problem-statement

draft-dunbar-l4-l7-sc-problem-statement

draft-yong-gre-in-udp-encap-4-service-chaining

draft-boucadair-chaining-requirements

BBF: Flexible Service Chaining (SD-326)

NFV

SWA(13)000019r1_Basic_Use_Cases_of_Service_Routing

SWA(13)000037_VNF_Forwarding_Graph_and_Service_Graph

_use_case-vAR

• Prototype PoC with VF

• Demonstrated during Innovation

Summit beginning of July 2013

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Standard progress related to SDN in IP domains

Use Case Huawei contributions on

standards

Prototype/Product Progress

SDN in IP domains

(Data Centre,

IP/MPLS Core, IP

RAN)

ONF

Arch&NBI WG, proposed use cases,

Instant VPN/TE (VPN over Traffic

Engineered Tunnels) leads POF, SDN

network migration, OF security;

BBF

initiated and leads Carrier SDN E2E

solution (SD-313)

IETF

Started to participate in I2RS

• DC SDN Network Architecture Design with

TEF/KDDI/Telefonica

• “IP RAN SDN PoC” and “VIP on-demand Custom

routing” with China Telecom

• Huawei VRP Controller Quantum Plugin

• Application-aware service programming

• SDN-based Mobile Backhaul Network

• Implementing ALTO with SDN

• IPv6 Transition with SDN

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Standard progress related to SDN in Tx domains

Use Case Huawei contributions on standards Prototype/Product Progress

SDN in Tx domains

(Transport SDN)

In transport and access domains, leads transport/access

network virtualization and open capability. In ONF, leads

transport SDN evolution solution architecture, in ITU-T,

leads transport SDN information model standards.

T-SDN2.0 Demo Shown in OFC 2013

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Standard progress related to SDN in vFamiliy (umbrella for vHome and vOffice)

Use Case Huawei contributions on standards Prototype/Product Progress

vFamiliy

(vHome, vOffice)

BBF

Leading valuable NFV feature

• vHome (WT-317): Use cases, requirements

and functional architecture of Network

Enhanced Residential Gateway (NERG)

• vAR (WT-302):Use cases of cloud services

including Virtualized Access Router

• vEnterprise (WT-xxx): the new project

application was accepted, and the number for

the WT is unallocated yet

vAR prototype progress:

• 2013.04 POC1 installation in Orange Lab(JIP

project)

• 2013.05 POC1 installation in China telecom

Lab(JIP project)

• 2013.06 POC1 demonstration in BBF Q2

meeting

• 2013.10 POC2 will be ready

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 21

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 22

Model Concept #1 - Open Flow

Controller

NE

NE

NE

NE

NE

Controller is the only to : - collect topology information - compute paths - distribute forwarding rules

Out of Band Management is advised

Location/Distance Matter

Internetworking is the key issue

Difficult to scale

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 23

Model Concept #2 – Overlay Controllers are like NE in LargeScale: - collect topology information - compute paths - distribute forwarding rules - react between each other - react with outside world - some NE understand more(VXLAN,NVGRE)

Out of Band Management locally only

Controller and NE always collocated

Internetworking solved by standard Protocols (BGP, IS-IS, GRE tunneling) Scale is bigger, need to reinvent network and own develop controllers

Controller

NE

NE

NE

NE

NE

Controller

NE

NE

NE

NE

NE

Controller is more distributed, Orchestration is seperate from local MNT Root/Master selection may be automated

Root Controller

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 24

Model Concept #3 – Hybrid

Controller

NE

NE

NE

NE

NE

Controller is not the only to : - collect topology information - compute paths - distribute forwarding rules

In-Band Management is possible

Network Will Work Without Controller

Internetworking is solved as today

Scale as much as today Local sygnaling, routing

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 25

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 26

Basic Concept – Open Flow follows

Controller

Flow Switch

Host A Host B

Flow Switch

Flow Switch

Flow Switch

Host C

*ETHANE (2007)

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 27

Open Flow basics Flow Table Entries

+ mask what fields to match 5.6.7.8

Action

* * * * * * * * * * port6 *

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 28

Open Flow basics More examples

5.6.7.8

Action

* * * * * * * * * * port6 *

Routing

*

Action

* * * * * * * * * 22 drop *

Firewall

*

Action

101 * * 00:1f:.. * * * * * * Port1 Port6 *

Vlan Switching

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 29

Open Flow basics There is more to get to SDN

Configuration

Feature Request

Flow/Port/Table modification

StatisticsBarriers (~transaction)

Packet In/Out

Messages

Any Combination of supported headers

IP & MAC additional wildcards

Other Fields (OF 1.2)

IPv6 (OF 1.3)

Flow Clasifiers

Header rewrites (like ex.NAT)

Push/Pop VLAN/MPLS tags (OF 1.2)

Output to a port

Send to normal Processing

Send to controler

Flow Actions

No Capabilities negotiations

All Controller to NE should be ssl

NE Controll Plane Need SD Abstraction

NE Forwarding Plane Must be in Hardware

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 30

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts – Architecture , NE

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 31

Hardware (4-5 vendors)

Software (many vendors)

Hypervisor (4-5 vendors)

Integrated solution

from one System Vendor

Network Function Virtualization

enhanced interface,

adapting to telco

requirements

enhanced interface,

adapting to telco

requirements

Software

Hardware

• Joint efforts needed to achieve

standardized environment

• Impact on etsbalished commercial

models (integration costs)

• Performance impact from migrating

SW from specialized to generic HW

with an intermediate HV layer

• Additional complexity

• Vendor/infrastructure SLA„s

• Trouble shooting

• Increased effort for IOT testing

• Orchestration and management

Issues & Challenges

Infrastructure

Virtualized network function

Network Function Virtualization – Basic Idea

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 32

Network Function Virtualization need to be E2E

Focus of this section

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 33

Huawei Networking SDN Strategy Overview

Converged SDN

DC Campus WAN

Goal

Capability

Hierarchical Openness Programmable forwarding and

control planes

20+ years experience

in networking

Easy to control Simplified High-level View

All Level Openness Services innovation

Convergence and Evolution Flexible and efficient network

Huawei Enterprise Networking SDN Strategy

Core

Concepts

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 34

The Evolution Towards Converged SDN Creating a more efficient and flexible network

Campus

DC WAN

Converged

SDN

20+ years experience in networking

OpenFlow, Openstack, PCE, … +

E2E device | Programmable device | Rich experience

in network deployment and maintenance

Consistency in service

and resource

deployment

Campus

DC WAN

SDN

Integrated

Decoupling

SDN Ready

SDN Ready

Converged SDN

Decoupling forwarding and controlling

function of single device, making

device programmable

Integrating various areas of the network

providing end-to-end situational

optimization

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 35

Huawei SDN Architecture

vSwitch

Physical Device

Device Manager

Virtualized Device

vRouter vFW/vADC

AP Switch Router Programmable

Switch OTN

TOPO Manager Routing

Stack

Path

Optimization

Network

Virtualization

Instant

Troubleshooting

Interface

Adapter

Quality

Monitor

Management &

Orchestration

layer

Control

layer

Network

device

layer

Huawei

SDN

Controller

UC & TP ERP OA

App

layer

Programmable environment Huawei eSDK

Service

Abstraction FusionSphere

Network Virtualization Management

Server

Northbound

Interface

Southbound

Interface

3rd Party App

Service

Policy Manager

Multi tenant

Manager vCenter

3rd Party

Controller

Application

Layer

SDN

Controller

Device

Layer

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Huawei SDN in The Data Center

Application layer

vDevice

DC controller

nCenter

NVGRE gateway

Programmable switch

Cloud

platform

VM

Policy

CE6800

CE5800

CE12800

Huawei

SDN controller

GALAX

REST API

OpenFlow/Netconf…

Plugin

Network device layer

Management & Orchestration layer

Control layer

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

The whole SDN architecture of Multiple Domain SDN

BNG

CSG

DSL

FTTH

PON

OLT

RSG

P Router

Metro Aggregation IP Core

Optical Metro

Backhaul

Router

Optical Transport

IDC

ICP Cloud CDN TE Tool Planning Tool Enterprise SI Partner 3rd Partner

Southbound

Access

Controller

Backhaul

Controller

Router

Controller

Transport

Controller IDC

Controller

Northbound API

Access

Optical Backbone

Fix

ed

Mo

bile

Service Controller

(BEP + CPN)

Service Controller

(IP + Optical) ……

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 38

SDN’s Key Requirements for Router

E2E & Operational SDN Network

Carrier Network

Gateway

(BNG/BRAS)

DC Network

Gateway

Access

Node

Access

Network

CE or OTN/WDM or

Fiber Backhaul

Network

IP/optical

Metro/Core

Network

Application

Layer

Service Orchestrator (Service Management based on User ID)

OTT/Cloud Application (ICP)

Orchestrator

Layer

Network

Control Plane

Data Plane

Access

Controller

Backhaul

Controller

User

GW

Carrier

Network

Gateway

DC Network

Controller

DC Gateway

Controller

OSS/BSS Network Planning &

Optimization Tools (Offline)

NMS/EMS

Network Control Functions ( DHCP, DNS, NAT, Firewall, AAA , ALTO …)

Openflow

Access Service Orchestrator

Transit Service Orchestrator

R-Controller

T-Controller

Cloud Service Orchestrator

Home

/Enterprise

Network (Computing

/Store /Display)

DC Network

(Switching /

Computing

/Store )

Service Processing

Forwarding

Service Processing

Forwarding

SDN Router

■ Software-defined forwarding

behavior to support decoupling of

control and data planes

■ Network resource virtualization to

realize centralized control

■ Open interface, so equipments

could be programmed/controlled

by Controller and Orchestrator

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 39

Benchmarks for SDN-Enabled Router

SDN-Enabled Router: Three “Must-Have” Features

Hardware Platform

Software Platform

Controller

N

P

N

P

N

P

N

P

N

P

N

P

N

P

N

P

Programmable

Virtualization

SDN

Network Control

Plane

Data Plane

RV:

Resource Virtualization

SDN-Enabled Router

OI:

Open Interface

SDFB: SW-Defined

Forwarding Behavior

Application

Layer

Orchestrator

Layer

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 40

Generate RIB

RIB

Current Router

Forwarding

Instruction

FIB

Forwarding behaviors are defined by Data

Plane,embedded in data-plane hardware

Control Plane

Generate Forwarding Instruction

RIB

SDN-Enabled Router

Forwarding behaviors are defined by Control Plane.

Data plane operates automatically

Forwarding Instruction

1: Hardware Platform Based on SDFB

FIB

Generate RIB

Control Plane

Data Plane Data Plane

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 41

Solar 3.0 Enables High-Performance SDFB

Solar 3.0

■ Support SDFB

■ Support programmable Open Flow interface

■ High-Performance: 1st 480G NP

Next

Key

Next

Table ID

Action

List

Table1

Process

Ingress Port ID

Next

Key

Next

Table ID

Action

List

TableN

Process ...

■ Data plane doesn’t need to understand the meaning of Keys. It operates

automatically according to Key and Table ID (defined by software)

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 42

2: Software Platform to Enable RV

RDF Resilient Distributed

Framework

FVRM Flexible Virtualization

Resource Management

SDMF Smart Deployment

& Migration

Framework

4 Key Features

OPS Open Programmable

System

For virtualization, a router is the composite of interfaces, forward engine and software

Optimized Software Platform to implement Resource Virtualization (RV)

■ Support concurrent &

distributed operation

■ Multi-dimensional & real-

time control

■ Flexible component

deployment

■ Multi-level open

■ Unified API

■ Easy simulation

■ Decide resource allocation

strategy by reliability &

service requirements

■ Allocate resources based

on the selected strategy

■ Computing resource

pool

■ Monitor and manage

computing resources

■ Dynamic migration

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 43

VRP Software Platform Realizes Virtualization

■ Distributed Computing

■ 4-Level Virtualization

■ Dynamic Migration

BGP OSPF ISIS

CU pool (Computing Unit pool)

CU4 CU5 CUn CU1 CU2 CU3

■ Centralized Control: PCE

NMS

PCE

Domain A Domain B

Centralized path computation

SW

VRP

Full-Service

Distributed

Framework

Centralized

Control

Non-Stop Process Migration

CU

CU

CU

CU

CU

CU

CU

CU

CU

CU

CU

CU

PS

VS1

VRF0

VRFn

VSn

VRF1

LSn LS1 LS0

VS0

Non-Stop Load Migration

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 45

3: Open & Programmable Control Plane

SDN Router

Controller

OpenFlow OpenFlow

Box-Independent Applications

■ Service can be created by defining service atoms

& service paths

■ Service atom and composite service can provide

service API for open service environment

Service Atom

Service

Network Apps

Open Interface

Orchestrator

Service Atom

Service Path

Programmable Programmable Programmable

SDN Router SDN Router

“Instant BoD” “Dynamic VPN”

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 46

SDN-Enabled Router Scenario 1: BNG

Routing Processing

Unified engine for package/flow forwarding

Data Plane

BNG Controller

Service Processing

Resource Pool

SDN-Enabled BNG

Programmable service, simplified new service developing/provisioning

FW Video … WoC

RR

■ Website:1week

■ APP: 3 days

■ Introduce IT platform for complex services

processing + Open & Programmable API

■ Shorten the period of new service

developing,facilitate service innovation

Open & Programmable API

Challenge

Service Innovation

Flexible Deployment Modes

Operator

■ New Service:

8 to12 months

L

P

U

L

P

U

S

P U

Service Processing Server

Router R R R

R R R R

Slow

Service Processing Server Pool

Increasing

new services

Few

new services

Blooming

new services

8 to 12 months 2 to 4 weeks

Single Equip. Equip.+Server

Separate Control plane and Data plane entities

Equip.+Server Pool

Flow Creation / 1st package processing

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 47

Virtual RGW (Residential)

Residential GW

Virtual CGW (Cell Site)

vRGW

Move

Routing/ NAT/

DHCP /Firewall

Into SDN Router

Virtual EGW (Enterprise)

Enterprise AR

vEGW

Move

Routing/Mgmt

Into SDN Router

Move

Routing/NAT/

IPSec/Firewall

Into SDN Router

Lite GW Lite CPE

SDN-Enabled Router Scenario 2: Access

■ Simplify network management: Centralized control and management plane, PnP access box

■ Simplify service provisioning: Only operate on SDN-Enabled router

■ Allow operators to go up the value chain leading to increased revenue

Move up the CPE functions, simplify service provisioning & maintenance

vCGW

Lite CSG

Cell Site GW

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 48

SDN-Enabled Router Scenario 3.1:

Business Drive More Flexible Service Chain in Gi-LAN

Rapid Service integration : Fast

integration of new service enablers

Simple & flexible Architecture: The

architecture is defined through

software configuration

Efficient Service delivery: tight

coupling of customer policies and

service provisioning through SDN

Lower latency: reducing the traffic

path by selecting dynamically only

applicable services

Traditionally traffic goes through all the Gi Service LAN

GGSN

Content

filtering

Internet

Service

Awareness Cache Firewall

Gi Service LAN

Gi LAN SDN– Steer traffic to go through “all” , “a subset”, or “None”

GGSN

Internet

Gi Service LAN Controller HTTP + Url filtering

FTP traffic

Encrypted Traffic

Content

filtering Service

Awareness Cache Firewall

Video Traffic

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 49

Controller

Gi LAN

Enabler_3 Enabler_4

Enabler_5

Service

Switch 1 Flow Router

Enabler_1

IP Network

Enabler_2

GGSN

PCRF

2G

UMTS

LTE

User aware

Bearer aware

Application aware

User Profile

Service

Switch 2

User Profile

Simple & flexible Architecture

Rapid Service delivery

Low TCO

SDN-Enabled Router Scenario 3.2:

Business Drive More Flexible Service Chain in Gi-LAN

pt

0

:

LT Medium

: Arial

pt

0

黑体

pt

pt

黑色

:

LT Regular

: Arial

pt

pt

黑色

细黑体

Page 50

vCGW: Optimize Mobile Backhaul Network

■ FE: Forward Engine

■ CP: Control Plane

■ CA: Control Agent

Control Planes

are centralized

on masters Convert each network area into

a virtual network

Reduce number of network

elements

Fast diagnosis

Simplified operation: network container

FE

CP

FE

CP … CSG

FE

CA

FE

CA … CSG

Master FE CP

CSG Plug & Play

New CSG is recognized automatically upon installation

Investment protection: easy upgrade

Support new features/services by software upgrades on master

nodes. No need to change CSGs hardware

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 51

Huawei SDN-Enabled Router Roadmap

OpenFlow 1.0 Demo

OpenFlow 1.3 Demo

open API for 3rd party

vRGW

vCSG (embedded controller)

vCSG (standalone controller)

SDFB demo on Solar 3.0

SDFB demo on Solar 4.0

2012

2013

2014

SDFB (Software-Defined Forwarding Behavior) RV (Resource Virtualization) OI (Open Interface)

BRAS/SR Virtual cluster

Commercial product with hybrid-mode OpenFlow

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 52

Agenda

SDN – review

Standardization Overview

Model Concept Open flow, Overlay and Hybrid

How it is made

Implementation Concepts

Reference Cases – Successful Tests

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 53

Huawei SDN Controller and OpenFlow Prototype

■ Huawei SDN-Enabled Router passed the

OpenFlow interoperability test organized

by ONF in May 2012

RIB

/FIB TE Data

Base ILM

NorthBound

API

Extended Application

(incl. 3rd party, could be deployed on

others servers)

Core Application (Routing / Path

Computation)

Basic Module

(Node/Link/Topology

discovery)

Communication Protocol Layer

(South interfaces: OpenFlow, XML, Netconf, etc.)

Setup

Signaling

Path

Computing

routing (inter-/

intra-AS

Topology

Information

Topology Discovery Addressing ND and Link

Management

Controller

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 54

SUMMARY Huawei SDN solution

Reliability As exist network with dual-homing AGGs without any reduction.

Update No service interrupt with two control planes.

Topology Hub-Spoke, Ring

All of existing network topologies

Compatibility No need new hardware.

Control Plane

Generate Forwarding Instruction

RIB

Huawei SDN-Enabled Router

Forwarding behaviors are defined by Control Plane. Data plane operates automatically

Forwarding Instruction

FIB

Generate RIB

Data Plane

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Page 55

Thank You!

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Migration(1/3)

Metro A

controller

Metro D

RR

Metro C

Metro B Route

EBGP MPLS

PCEP

Route

EBGP

Stage1 Centre calculate path(PCE) for

the internal flow optimization.

The edge router are just upgraded to

support PCEP. the provision is easy .

And it don’t affect the other services.

Centre calculate the internal

data path

running rsvp in routers and setup the data path

according to the result of calculation of the

controller

the edge routing protocol and

routing retain

MPLS

Control-interface: PCEP

Migration strategy:

services is controlled

by SDN controller step

by step

Metro A

controller

Metro D

Metro C

Metro B

Edge

Route

EBGP

EBGP

IBGP

MPLS

IBGP Stage1 Centre control the edge routings

for in/out flow optimization (e.g. DC

exit routing).

the traditional router is compatible with

it. the provision is easy. And it don’t

affect the other services.

RR

Centre control the

external routings

the edge routing protocol retain,but controller centre control the

routing seleting

control-interface: IBGP

the traditional protocol

retain in internal routers

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Migration(2/3)

Metro A

controller

Metro D

Metro C

Metro B

Route

EBGP MPLS

PCEP

EBGP

IBGP

MPLS

IBGP

Stage2:

Both of the external routing and internal

path are centre controlled. the flow can be

optimized end to end .

But it just require the edge routers to

support SDN. the internal routers can run

the traditional protocol.

But the stage is optional, stage1 can

migrate to stage3 directly.

RR control-interface :IBGP+PCEP(IBGP

control routing,PCEP control lsp)

the edge routing protocol retain,but controller centre control the

routing seleting

Centre calculate the internal

data path

Centre control the external

routings

running rsvp in routers and setup the data path

according to the result of calculation of the

controller

Optional step

35pt

: R153 G0 B0

:

LT Medium

: Arial

32pt

: R153 G0 B0

黑体

22pt

) :18pt

黑色

:

LT Regular

: Arial

20pt

):18pt

黑色

细黑体

Migration(3/3)

Metro A

controller

Metro D

Metro C

Metro B

Route

EBGP

openflow

EBGP

Stage3

All of services are centre controlled.

Stage1 can migrate to staged directly

(e.g. the data path is setup by openflow

instead of PCEP. ). In this scenario, it

is hybrid model, some services use

openflow and some services use the

traditional protocol.

full centre control

the protocol and routing are

centre controlled

MPLS control-interface:

openflow

the traditional protocol is no longer

retained(except the IGP for that SDN

controller can communicate with forwarding

nodes.)

Mcast …