Torsten Braun, Universität Bern [email protected] , cds.unibe.ch

ICT LEIT in H2020 Info Day & International Brokerage Event

Information-Centric and Software-Defined Networking

Torsten Braun, Universität Bern

[email protected], cds.unibe.ch

mailto:[email protected]

http://www.iam.unibe.ch/

Torsten Braun: Information-Centric and Software-Defined Networking

2

Future Internet

> The current Internet is based on principles of the 1960s with the main purpose to interconnect large computers.

> Today, Internet users are mainly interested in retrieving content and accessing services.

> Increasing bandwidth demand due to— (personalized) multimedia data streams— Cloud computing and storage,

visualization on (mobile / high-resolution) end systems— Large data sets from measurements and scientific experiments— Internet of Things, Internet of Services, …

> New approaches, e.g., Information-Centric Networking (ICN), Software-Defined Networking (SDN), need more research, development, testing etc.

Koc University, December 6, 2013


3

Traditional Web Retrieval / Web Services


web server / web service

DNS server

search engine /service registry

user’s end system


4

Information-Centric Networking (ICN)

> Naming of content rather than hosts/interfaces— Content independent of devices that store it— Naming is location independent (receiver mobility support !)

> Receivers (subscribers) request content.> Senders (publishers) advertise and deliver content.> Receivers and senders

— do not have to be aware of each other— are decoupled in time

> Example: Content-Centric Networking (CCN)



5

Content-Centric Networking (CCN)

> Combination of content lookup and message routing> Idea: describe the user’s interests in the message header,

but not where to get it. > Messages (using XML encoding)

— Interest: content name, selector— Data: content name, signature (info), data

> Hierarchical content names— Example: /unibe.ch/braun/lecture/os/20130219

> Related Projects— NDN = Named Data Networking, www.named-data.net — CCNx = open source software reference implementation for CCN,

www.ccnx.orgVan Jacobson, Diana K. Smetters, James D. Thornton, Michael F. Plass, Nicholas H. Briggs, and Rebecca L. Braynard: Networking named content, 5th international conference on Emerging networking experiments and technologies (CoNEXT '09). ACM, New York, NY, USA, 1-12.


http://www.named-data.net/

http://www.ccnx.org/


6

Content Distribution with ICN/CCN


/unibe.ch/braun/lecture/os/20130219

1

32

4 5 76

Interest / Data


7

Service-Centric Networking (SCN)

> Extension of content-centric networking to support services, possibly operating on content.

> Description of a service using content naming scheme, e.g., /google.com/file-service

> Services are provided by service elements. > Service request (response) in Interest (Data) message> Goals

— Reducing delay for providing services— Minimizing network bandwidth for service access— Load balancing

Braun, T.; Hilt, V.; Hofmann, M.; Rimac, I.; Steiner, M.; Varvello, M.: Service-Centric Networking, 2011 IEEE International Conference on Communications Workshops (ICC), pp.1-6, Kyoto, 5-9 June 2011



8

Target Services Supported by SCN

> Infrastructure services, e.g., deploy / find / use cloud computing and storage services

> Client-oriented services, e.g., web services> Continuous content retrieval and streaming services,

e.g., A/V conferencing, streaming> Event services, e.g., sensor or stocks data> In-network services, e.g., (sensor) data aggregation and filtering> Location-based services



9

Service-Centric Network


SCN router

Service request / response


10

SCN Objects

contentdata

read

1: Content Object 2: Service Object

contentdata

read

3: Content/Service Object

function3function1

function2

function1

function2



11

Example: Real-time Audio Conferencing


Echo cancellation

Trans-coding

Sent audio data

Received audio data

Mixing

Software Defined Networking (SDN)

API to data plane, e.g., OpenFlow

(centralized) control

switches

smart, slow

dumb, fast



13

SDN Architecture



14

Application Layer

Control Layer

Infrastructure Layer

Business Applications

SDNControl Software

Network Services

Network Device

API API API


15

Service-Defined Service-centric Networking (SDSN)

> Services might be composed out of multiple atomic services. > Single service request can be considered as service program

involving atomic services from different servers. > Service mapper

— identifies servers to provide atomic services— calls atomic services by service requests— may combine results into a single service response to the requester

> Analogy between Software-Defined Networks and SCN: separation of control and forwarding

→ Software-Defined Service-Centric Networking (SDSN)— SDSN could provide API to service developers to define services,

SDSN then programs the network to provide requested services.

Torsten Braun, Andreas Mauthe, Vasilios Siris: Service-Centric Networking Extensions,28th ACM Symposium on Applied Computing, Coimbra, Portugal, March 18 - 22, 2013



16

SDSN Operation


SM

T

E

M

Service ElementsService MapperNetwork Device

SDSN can use SDN• to establish flows between clients and

discovered service entities (service discovery by Interest / Data)

• to set up a SDSN overlay network


17

Service Element

Routing & Switching

ICN/CCN

Service Processing

Network Device

Routing & Switching

SDSNInterface

SDN Interface

API

Service Mapper

SDSN and SDN Devices


ICN/CCN


18

Energy Router

ICN/SDN in Smart Grid


Energy sources /

consumers

Controllers of energy sources /

consumers

Energy switch

Control


19

Conclusions

> SDN is being used as network management technology so far and its potential has not been exploited.

> ICN/CCN as promising Future Internet paradigm> SDSN as generalization of SDN and ICN towards services:

Configuration of both network devices and service elements> SDSN as enabler for an Internet of Services, Internet of Things,

etc. > Open ıssues

— Securıty— Energy effıcıency


Documents

Torsten Braun, Universität Bern [email protected] , cds.unibe.ch