when things will speak "web" (lecture)

When Things will Speak « Web »Architecture, Challenges and Business Opportunities for a

Dominique Guinard, ETH Zurich & SAP ResearchLecture for Lancaster University, UK.18.02.2010

MOTIVATIONDo we really need a Web of Things?

[http://www.flickr.com/photos/moragcasey/]

Embedded Devices Invade us!

• Emergence of the physical Web:– Embedded devices get

more ubiquitous.– They are also getting

connected to the Internet.

3Dominique Guinard, ETH / SAP Research

Problem: How to Achieve a (Re-)Composable Web of Things?

• Huge eco-system of embedded devices.

– About 1000 smart objects / person:

– and… about 1000 systems to use them and build applications on top of them.

• How do we enable tech savvys and companies to create applications on top of this eco-system?

Dominique Guinard, ETH / SAP Research 4

“re-think the way we design computing systems in order to take into account the >1000 smart objects

per people we will soon have to deal with.” David Orban, Open Spime

Contribution: Web of Things (WoT) in a Nutshell

• Creating a Web of Things by:– Connecting embedded devices to the Internet (IP) [Hui08].– Having them embedding a Web-Server.– Modelling their services in a Resource Oriented manner (RESTful API)

so that they become first-class citizens of the World Wide Web!

• Benefits:– Ease the building of applications on top of embedded devices.– Get a lot of the features/services of the Web almost for free:

• bookmarking, caching, linking, searching, securing etc.• Twitter, Atom, blogs, social networks, visualization APIs, maps, etc.

– And enable physical mashups:• dynamic, ad-hoc composite applications involving real-world devices


[Hui08] Hui, Jonathan W., and David E. Culler. “IP is dead, long live IP for wireless sensor networks.” In Proceedings of the 6th ACM conference on Embedded network sensor systems, 15-28. Raleigh, NC, USA: ACM, 2008.

Enable Real-World Mashups

6

REST

REST

URL

PHP

RE

ST

AP

I

[http://www.pachube.com] [http://www.webothings.com/energievisible]

REST

[http://www.clickscript.ch]

JavaScript

Dominique Guinard, ETH / SAP Research

Today’s Menu

1. Motivation2. A Web Oriented

Architecture for the Real World

3. Protoypes and Applications

4. WoT and the Business5. Challenges for a

seamless WoT

7

[http://www.flickr.com/photos/lessio/1346732230/]


A WEB ORIENTED ARCHITECTURE FOR THE REAL WORLD

Push the Web down to devices!

[http://www.flickr.com/photos/julianbleecker]

1) Connecting Embedded Devices to the Internet

9

IPv6

lowpan

[3] Vlad Trifa, Samuel Wieland, Dominique Guinard, Thomas Michael Bohnert: Design and Implementation of a Gateway for Web-based Interaction and Management of Embedded Devices.Proceedings of the 2nd International Workshop on Sensor Network Engineering (IWSNE 09). Marina del Rey, CA, USA, June 2009

Non

IP devices


2) Resource Oriented Embedded Devices REST in a Nutshell

• Resources• Their names (URIs).• Their representations (JSON, XHTML).• Links between them.• A uniform interface (HTTP).

10

REPRESENTATIONHTTP URI

Links


2.1.) Resource Design

• Thanks to their atomicity services on embedded devices are quite adapted to Resource-Oriented Architectures.• Root: http://webofthings.com/• Resources:

– Spots: http://webofthings.com/spots– Spot 2: http://webofthings.com/spots/2– Light Sensor: http://webofthings.com/spots/2/sensors/light– Led Actuator:

http://webofthings.com/spots/2/actuators/led/

11 Dominique Guinard, ETH / SAP Research

2.2) Representation Design

•XHTML as default, ideal for browsing:– http://webofthings.com/spots

•JSON, ideal for parsing:– http://webofthings.com/spots.json

•XML, ideal for integration with business systems:– http://webofthings.com/spots.xml


2.3. Uniform Interface• HTTP Verbs: What do you want to do?

– GET: retrieve the representation of a resource:– Current consumption of an electricity sensor.

– PUT: update a resource:– Turn a device on/off.

– DELETE: remove a resource:– Delete a threshold on a senors, shut a device down.

– POST: create a subordinate:– Create a new feed to trace the location of a tagged object.

• HTTP Headers: What type of data are you sending me/requesting?– Metadata:

• Content type: application/json, text/html, etc.– Status:

• 200 OK, 201 Create, 400 Bad Request, 401 Unauthorized


Today’s Menu





seamless WoT

14



APPLICATIONS AND PROTOTYPESLet’s get concrete!

[http://www.flickr.com/photos/lpettinati/]

The « Energie Visible » Project• Help people better

understanding the energy consumption of devices.

• Monitor and control your energy consumption at home.

• Fully integrate the monitoring and control to the web.

• webofthings.com/energievisible

16

Gateway Level:Web server and RESTful API

Sensor Level:Ploggs

Device Level:Appliances

Client Level:Web/Mobile App


Talk to devices: The WEB Way


Energy « Mashups »

18

• Energie Visible Control and Visualization Interface [Gui09]:– JavaScript (GWT) page.

• E-meter iPhone [Wei09]

Interface:– Objective C program.

[http://www.vs.inf.ethz.ch/res/show.html?what=emeter_demo

[Wei09] Markus Weiss, Dominique Guinard, Thorsten Staake, and Wolf Roediger, eMeter: An interactive energy monitor. Proceedings of Ubicomp 2009.

[Gui09] Dominique Guinard, Vlad TrifaTowards the Web of Things: Web Mashups for Embedded Devices. In proceedings of WWW 2009.

Demo


RESTful SunSPOTs

• Web-enabling the Sun SPOT platform:– All sensors and actuators

become resources.

• Two implementation:– Web-server on the

nodes.– Web-server on the

gateway.

20

[http://www.sunspotworld.com]

[GuiSpot09] Dominique Guinard, Vlad Trifa, Thomas Pham, Olivier Liechti. Towards Physical Mashups in the Web of Things. Proceedings of IEEE INSS 2009


Physical-Physical Mashup:Ambient Energy Meter

• Create an ambient device that can assess the energy consumption of the current place it is in.

• Mashup of:– The RESTful Ploggs– The RESTful Sun Spots– The Smart Gateways.


FAT: Friends and Things• Sharing platform for the WoT:

– Discovery, share and advertise things with friends (e.g. Facebook), relatives and colleagues (e.g. LinkedIn).

– Aggregate feeds from several sensors using ATOM.

– Based on social networks APIs.

– http://tiny.cc/sac315

[GuiFAT10] Dominique Guinard, Mathias Fischer, Vlad Trifa . Sharing Using Social Networks in a Composable Web of Things. Proc. of the first IEEE Conference on the Web of Things (WoT 2010).


Mobile Energy Mashup Editor

• RESTful Framework allowing the creation of physical mashups:– « Turn the heating off

when I’m more than two KMs away from home ».

– Workflow engine based on Ruote (Ruby).

– Interface between devices and the Web.

– Mashup editor on Android.


Today’s Menu





seamless WoT

25



WOT AND THE BUSINESSBusiness Opportunities

[http://www.flickr.com/photos/daviddmuir/]

Forcasts• Specialists talk about a

market of $4.6 billion for Wireless Sensor Networks in 2011 [OnWorld07]

• This does not take into account Web-enabled consumer electronics.

• Clear trend for the Ubiquitous Web.

[OnWorld07] M. Hatler, D. Gurganious, C. Chi, and M. Ritter, “WSN for Smart Industries,” OnWorld Study, 2007. [Online]. Available on: www.onworld.com

[Trends for Web of Things and Internet of Things on www.google.com]


Actors of the (future) WoT Market

• « Smart Gateway » providers:– There corporation (ex-

Nokia), Oberon.ch, Netgear, Arimaz, ioBridge, etc.

– The OSGi folks.– Energy dedicated

gateways:• Apple, Energy Optimizers

[http://therecorporation.com/] [http://www.netgear.com]

[http://www.iobridge.com]

[http://www.arimaz.com]



• « Smart Things » manufacturers:– Consumer « gadgets »:

• Violet, Chumby, Poken, Arimaz

– Sensors/actuators nets:• Phidget, SunSPOTs,

Sentilla, etc.

– Energy Monitoring and Management:

• Energy Optimizers, DiyKyoto, Current Cost, etc.

[http://violet.net/] [http://www.chumby.com]

[http://www.plogginternational.com/] [http://www.diykyoto.com/]



• « Software » companies:– Pachube– Google:

• Power Meter• Visualization API

– SAP:• SAP MII, AII

– Oberon.ch• Yaler.net

[http://www.google.org/powermeter]

[http://www.pachube.com]

[http://www.sap.com]

[http://code.google.com/apis/charttools]


Today’s Menu





seamless WoT

31



CHALLENGES FOR A SEAMLESS WOTWhere do we go from there?

[http://www.flickr.com/photos/parmiter/]


Beware, WoT is coming!

• The vision [Kindberg02] of our everyday physical world merging with the World Wide Web is becoming a reality.

• There is a need for standards or at least good practices.

• The REST architectural style is a good candidate!

• Yes! But… [Kindberg02] Kindberg, Tim, John Barton, Jeff Morgan, Gene Becker, Debbie Caswell, Philippe Debaty, Gita Gopal, et al. “People, places, things: web presence for the real world.” Mob. Netw. Appl. 7, no. 5 (2002): 365-376.


A Word About Client-Servers

• REST over HTTP (i.e. client pull) on/for embedded devices is good for control scenarios (e.g. actuation).

• Monitoring scenarios (e.g. sensing) speak for device/gateway push.

• Atom can help, but clients still pull data.• « Web-flavored » alternatives exist and have to

be further explored:– Pubsubhubbub, Comet, Webhooks, XMPP, etc.


And a Word about Discovery

• Another important challenge is discovery and search of Web-enabled things:– How to understand what a thing provides beyond

what is described by its REST API?– How to search for things in an ecoystem of billion

of devices?

• Here also, Web-flavored solutions are being developed:– Microformats, Semantic Web, RDFa, etc.


Thanks a lot for your attention

• Contact:– Dominique Guinard– dguinard a t ethz.ch– www.guinard.org

• Special thanks to:– Thomas Pham, Mathias

Fischer, Azulena Aguilar, Vlad Trifa, …


www.webofthings.com

when things will speak "web" (lecture)

Technology