Top Banner
OpenFlow Wireless Stanford Clean Slate Program http://cleanslate.stanford.edu Funded by Cisco, Deutsche Telekom, DoCoMo, Ericsson, Google, LightSpeed, MDV, NEC, NSF, Xilinx Guru Parulkar [email protected] KK Yap, Nick McKeown, Sachin Katti
29

OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Apr 21, 2018

Download

Documents

dominh
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Wireless

Stanford Clean Slate Programhttp://cleanslate.stanford.edu

Funded by Cisco, Deutsche Telekom, DoCoMo, Ericsson, Google, LightSpeed, MDV, NEC, NSF, Xilinx

Guru [email protected]

KK Yap, Nick McKeown, Sachin Katti

Page 2: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

2

Cellular Networks and Internet

• Two phenomenally successful infrastructures • Smart phones and data starting to dominate• Lots of action and growth

Cellular Network InternetGWGWGW

So what is wrong?

Page 3: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

• Many cellular networks visible (5-7 common), many wifi networks visible (10-15

common).

• But not practically available to me – closed infrastructures.

• Seamless mobility impossible

Why can’t I use of all the infrastructure around me?

Mobile Network Infrastructure Today

cellular

WiFi

Page 4: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Ideally, in Future Wireless Network Substrate we want

• Simultaneous access to all infrastructure

• Continued connectivity and seamless mobility as I move

• Maximal user choice

• Allow innovation, instead of closing the infrastructure

Page 5: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Ideally we want

DumbRadio-dependent

AP/BS

Open SharedPacket Infrastructure

Can Internet be the shared packet infrastructure?

Page 6: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Internet has many problems

Plenty of evidence and documentation

Internet’s “root cause problem”

It is Closed for Innovations

6

Page 7: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Million of linesof source code

5400 RFCs Barrier to entry

500M gates10Gbytes RAM

Bloated Power Hungry

Many complex functions baked into the infrastructureOSPF, BGP, multicast, differentiated services,Traffic Engineering, NAT, firewalls, MPLS, redundant layers, …

An industry with a “mainframe‐mentality”

We have lost our way

Specialized Packet Forwarding Hardware

OperatingSystem

App App App

Routing, management, mobility management, access control, VPNs, …

7

Page 8: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

8

Controller

OpenFlow Switch

FlowTableFlowFlowTableTable

SecureChannelSecureSecure

ChannelChannel

PC

OpenFlow

Protocol

SSL

hw

sw

OpenFlow: Enable Innovations “within” the Infrastructure

• Add/delete flow entries• Encapsulated packets• Controller discovery

API

Net Services

Page 9: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

9

OpenFlow Protocol

C

D

D

D D

D

D

DD

D

C C

FLOWVISOR

OpenFlow Protocol

D

D

DD

D

D

DD

D

D

D

DD

D

D

DD

Research Team A Controller

Research Team B Controller

Production Net Controller

IsolatedNetwork Slices

Physical Infrastructure

Packet & Circuit

Switches: wired, wireless,optical media

Sliced and Virtualized OpenFlow Infrastructure

Control Plane API

9

Page 10: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

10

Example Network Services• New routing protocol: unicast, multicast,

multipath, load-balancing• Inter-domain routing• Network access control• VLAN management • Mobile VM management • Mobility and handoff management • Energy management • Network measurement and visualization• IPvX• …

Page 11: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Enabled Equipments

More to follow...

NEC IP8800

HP Procurve 5400

WiFi

Juniper  MX‐series(prototype)Cisco Catalyst 6k

(prototype)Core Router

EnterpriseCampusData Center

CircuitSwitch

Wireless

Quanta LB4G

Prototype Product

Ciena CoreDirector

WiMAX (NEC)

Cisco Catalyst 3750 (prototype)

Arista 7100 series (Q4 2010)

Page 12: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Deployment

• Europe 

‐ 5 EU Universities inter‐connected by GEANT2

• Japan‐ 3‐4 Universities interconnected by JGN2plus

• Interest in Korea, China, Canada, Brazil, …

12

• US‐ Deployed as GENI substrate

‐ 8 Univ. interconnected by 

2 National Backbones (in 2010)

‐ Potential 25 universities in the next step

Page 13: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

13

OpenFlow: A Hack to Experiment? Is there a bigger architecture story with

business implications?

Page 14: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

14

Controller

OpenFlow Switch

FlowTableFlowFlowTableTable

SecureChannelSecureSecure

ChannelChannel

PC

OpenFlow

Protocol

SSL

hw

sw

OpenFlow: Enable Innovations “within” the Infrastructure

• Add/delete flow entries• Encapsulated packets• Controller discovery

API

Net Services

Page 15: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

15

App

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

App App

Simple Packet Forwarding Hardware Simple Packet

Forwarding Hardware

Network Operating System

1. Open interface to hardware

3. Well-defined open API2. At least one good operating system

Extensible, possibly open-source

Architecturally what It Means

Page 16: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

16

Why Providers Care: New Data Center

Cost200,000 serversFanout of 20 10,000 switches$5k commercial switch $50M$1k custom-built switch $10M

Savings in 10 data centers = $400M

Control

•Optimize for features needed•Customize for services & apps•Quickly improve and innovate

The value prop applies to enterprise and service provider networks

Page 17: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Ecosystem Coming Together

Data CenterGoogle, Amazon, Microsoft, ..

NW ProvidorDT, DoCoMo(Level3, BT, Verizon,..)  

Data CenterGoogle, Amazon, Microsoft, ..

NW ProvidorDT, DoCoMo(Level3, BT, Verizon,..)  

Providers

Researchers

Research & Education Network

Researchers

Research & Education Network

Universities

Switch/Router Vendors‐ Enterprise & Backbone‐ Packet & Circuit‐WirelessChip Vendors‐ Broadcom, Marvell, Dune,New Class‐ Nicira

Switch/Router Vendors‐ Enterprise & Backbone‐ Packet & Circuit‐WirelessChip Vendors‐ Broadcom, Marvell, Dune,New Class‐ Nicira

Vendors(Hardware/Software)

Page 18: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Ideally we want

DumbRadio-dependent

AP/BS

Shared Packet Infrastructure:OpenFlow/SDN Infrastructure

Page 19: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Mobile Networks Today...

CellularProvider A

Cellular Provider B CellularProvider C

Page 20: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Our Vision of Tomorrow

Infra A Infra B Infra C

Service provider 1Service provider 1 Service provider IIService provider II

Separating the infrastructure from the service providers.

Page 21: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Wireless Platform:WiFi, WiMAX, Wired Networks

Page 22: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Stanford Deployment• Deployed

o 80+ WiFi APs across School of Engineering

o 2 WiMAX basestations

o Multiple switches in wiring closets

• Planned WiMAX deployment

o To deploy outdoor WiMAX basestation to serve School of Engineering

o To use stack from Open Programmable WiMAX

Page 23: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Current Demo at StanfordHow innovation in mobility management can use the platform

demonstrate "macrodiversity" performed over WiFi and WiMAX

Page 24: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

WiFi-WiMAX Handover• Technology agnostic

o Shown handover between WiFi-WiMAX• Device/technology/application customizable

http://www.openflowswitch.org/wp/n-casting-mobility-using-openflow/

Unicasting Tricasting

Page 25: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Wireless Extension for GENI Networking Substrate

WiFi WiFi

WiFiWiMax

WiFi WiFi

WiFiWiMax

WiFi WiFi

WiFiWiMax WiFi WiFi

WiFiWiMax

Page 26: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Software-defined Networks

and OpenFlowApril 2010

With Martin Casado and Scott ShenkerAnd contributions from many others

Page 27: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

Thank you!

Page 28: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow Wireless Components

• OpenFlow as common API to forwarding elements (switches, APs, base-stations)

• Remote configuration of devices

• Virtualization using FlowVisor in forwarding

• Uses NOX as controller with simple API

o e.g. rerouting (done in 12 lines)

Page 29: OpenFlow Wireless - Stanford University 03, 2010 · OpenFlow Wireless Components • OpenFlow as common API to forwarding elements (switches, APs, base-stations) • Remote configuration

OpenFlow: Architecture Concepts• Separate data from control

– A standard protocol between data and control• Define a “generalized flow” based data path

– Very flexible and generalized flow abstraction– Delayer or open up layers1-7

• Logically centralized “open” controller with API– For control and management applications

• Virtualization of data and control planes • Backward compatible

– Though allows completely new header