IoT Day 2013 - Madrid

Post on 08-May-2015

738 views 0 download

description

This presentation was given at the celebration of the international Internet of Things day in Madrid. It presents the use of IP and Web standard communication technologies for the IoT. In particular the 6LowPAN and CoAP protocols are briefly presented.

Transcript of IoT Day 2013 - Madrid

WALTER COLITTI (@waltercolitti) VRIJE UNIVERSITEIT BRUSSEL

Open IP and Web Technologies for the Internet of Things

2

“Big” devices

Things on the Internet

3

“Small” devices

Intranet of Things

Different protocols = no interoperability

Gateways = architectural complexity

Gateways = no integration with the Web

4

Internet background

Interoperability

End-to-End principle

Why not repeating the IP success in IoT?

Embedded IP Technologies

6

Promotes IP as network technology for embedded devices

Embedded IP – Standards

6LoWPAN

RPL

Enables IPv6 over constrained networks

Routing protocol for Low-power Lossy Networks

7

6LowPAN – Advantage

Application

Transport

Internet (IPv4/IPv6)

Link

INTERNET

LAN

Wireless

Sensor

Network

Internet (IPv4/IPv6)

Link

Application

Transport

Internet (IPv6)

Link

(802.15.4) Link

(802.15.4)

6LoWPAN

TCP/IP enabled

Sensor mote

LAN/Internet

border router

6LoWPAN

Internet

(IPv6)

Internet/WSN

border router

Internet (IPv4/IPv6)

Link

Application

Embedded Web Technologies

(Web of Things)

9

Embedded Web - Advantage

The Web is everywhere

REST

XML

JSON

URI

HTTP

10

Embedded Web - Problem

REST/HTTP complex for tiny devices Relies on TCP

Complex observation mechanisms

No multicast support

REST/HTTP not designed for IoT/M2M apps

Long-lived transactions

Constrained Application Protocol (CoAP)

12

CoAP standard

Constrained Application Protocol

CoRE Working Group

HTTP functionalities for constrained devices

Extra functionalities added

13

Transaction layer for message exchange

CoAP principle

Dual Layer

Request/Response layer for resource manipulation

Features Small message overhead (4 bytes binary header)

Client can observe resource status changes

CoAP

UDP

IP

HTTP

TCP

IP

Request/

Response

Transaction

14

CoAP Performance

Response Time

15

CoAP Performance

(server mote)

Energy consumption

16

HTTP – CoAP Proxy

Client Proxy Server

http:// sensor1.contikigh.com/readings

http://193.226.5.150/readingsGET /readings HTTP/1.1Host: sensor1.contikigh.com coap:// sensor1.contikigh.com/readings

coap:// [aaaa::c30c:0:0:365]/readingsCON GETURI -Path: readings

CON 2.00{“sensor”:”212:7400:2:202”,”readings”:{“hum”:50,”temp”:26.8}}

HTTP/1.1 200 OKHumidity: 50, Temperature: 26.8

THANK YOU for your attention

WALTER COLITTI (@waltercolitti)

Email: wcolitti@gmail.com