“Software-Defined Data Plane Enhancing SDN and NFV”

Pursuing “Deeper Programmability”

Aki Nakao TTC

(The University of Tokyo)

GSC 18 2014/7/23 1

2

Control-Plane Elements

Network Applications

Data-Plane Elements

Applications

Control Plane

Data Plane

SDN Architecture

North Bound Interface (NBI)

South Bound Interface (SBI)

3

Control-Plane Elements

Network Applications

Data-Plane Elements

Applications

Control Plane

Data Plane

Application Driven Thinking

Current SDN (bottom up)

Future SDN should be (top down)

4

Application-Driven Thinking Premise: Programmable networking has been enabled by SDN and NFV App-Driven Thinking: •  Think of “(killer) applications” first and then design network functions and interfaces APIs for SDN and NFV

•  Not just OPEX/CAPEX reduction, but create new values via SDN and NFV

Lets start with an example application!

“Next-Gen MVNO”

5

An  ISP  needs  app  specific  traffic  control

Standard Mode (flat rate)

High Speed Mode (pay as you go)

bandwidth

150kbps

Bandwidth Control According to Apps !

6

MVNO Customers Need More Flexible Subscription

App-specific traffic control enables more fine-grained subscription plans that can get an MVNO out of the “ever-lower-cost” competition

Smartphones

Packet  Marking  

The  Internet  FLARE  Network  (SDN/NFV  Enabled)  

Header   Payload  

Add app/device information to packet trailers

Trailer  

App/Device  Informa@on  

Smartphones (wearables)

Header   Payload  

Parse and remove “trailers” and map between flows and apps

FLARE（Deeply Programmable Node)

Header   Payload  

Traffic Engineering based on headers

SDN Controller

NTT Docomo

Our Proposal

SDN  Controller  

7  

Gateway  

MVNO Backhaul

Packet  

Parse  and  Remove  Trailers  

Smartphones  aGach  app/device  informa@on  to  packets  FLARE  detects  app/device  informa@on  and  creates  mapping  between  flows  and  apps/devices  

8

App-Specific Traffic Control

Smartphone connected to our MVNO

Remote console of programmable network node (FLARE)

9

Benefits •  Application Specific Traffic Engineering for MVNO •  Application Name Based •  Application Process Based（Fore/Background) •  Device Type Based •  Device State Based (Context / Location Aware) •  Parental Control •  Not by apps on devices, but by networking •  Additional Value-Add services for specific applications •  Differentiation for competing apps (e.g., Chrome vs. Firefox)

Application Driven SDN

•  Flow abstraction in Southbound Interface is for operators <Flow Pattern> <Action> <Stat>

•  App/Device abstraction is useful and intuitive <App/Device> <Action><Stat>

10

Some ISPs need more direct SDN Southbound Interface

Application Driven SDN QoS

Smartphone   FLARE  Deeply  programmable  network  node  With  soNware  defined  data  plane  

Chrome  :    Pass  Thru  Firefox:          Block  YouTube:  Rate  Limit  

 App    Packet  

11  

Bandwidth Control According to Apps !  

12

We won the best demo award! GEC20@UC Davis

Software Defined Data Plane

13

Control-Plane Elements

Network Applications

Programmable Data-Plane Elements

Applications

Control Plane

Data Plane

North-Bound Interface (NBI)

E.g. OpenFlow Switches

Packet Process

Packet Process

Publish API

Innovation Cycle

14

Network Applications Data-Plane

Elements

Southbound Interface

Application Driven Thinking

Operation and Evaluation Feedback

ITU-T Y.3300 (Y.SDN-FR) “Framework of software-defined networking,”

15

Sliceable Software Defined Data Planes

16

Control-Plane Elements

Network Applications

Programmable Data-Plane Elements

Applications

Control Plane

Data Plane

North-Bound Interface (NBI)

E.g. OpenFlow Switches

Packet Process

Packet Process

Publish API

Programmable Data-Plane Elements Programmable Data-Plane Elements Programmable Data-Plane Elements

17

Control-Plane Elements

Network Applications

Programmable Data-Plane Elements

Applications

Control Plane

Data Plane

North-Bound Interface (NBI)

E.g. OpenFlow Switches

Packet Process

Packet Process

Programmable Data-Plane Elements Programmable Data-Plane Elements Programmable Data-Plane Elements

SDN for Network Control NFV for Data Processing

Programmable Data-Plane Elements Programmable Data-Plane Elements Programmable Data-Plane Elements Programmable Data-Plane Elements

SDN data plane and NFV could be unified

Control-Plane Elements

Orchestrator

FLARE Node Implementation

36-72 cores (upto 100-200 cores in future)

(board designed by NakaoLab)

x86 Processor

Many Core Processor

The University of Tokyo Confidential

Hierarchical Resource Management • General Purpose Processor(s) • Network Processor(s) • ...and more types of processors

18 18

19

Programming Model Toy-Block Networking

19

Toy-Block Networking GUI

20

Summary

21

•  Application Driven Thinking •  Top-down, dynamic update of software •  User, app, device, service oriented modeling

•  Deep (Data Plane) Programmability •  SDN data plane as a network function in NFV •  Data plane slicing (virtualization) •  Evolve-able APIs •  New protocol handling

•  Programming Model •  Toy-Block Networking •  Accommodate a wide range of programmers •  Marketing of reusable network function blocks

Missing from the current landscape of SDN and NFV