WoT @ Oracle-Labs

Researching the Web of Things

Dominique GuinardMIT Auto-ID Labs / ETH Zurich / SAP Research

2Dominique Guinard MIT / ETH

I, in a Nutshell

2005: Bachelor in Fribourg: RFID Indoor Assets Tracking

Framework (RFIDLocator) @ Sun Microsystems

2006 – 2007: Master in Lancaster: Service architecture for sensor

supported interactions from mobile phones

2007 – 2008: Auto-ID Labs Zurich: « Mobile Internet of Things » project

with Nokia Research.

2007 – 2011: SAP: Socrades & Sensei IoT projects

2008 – now: Ph.D. @ ETH Zurich: Pervasive Computing, Web of Things

2010 – now: Visiting Researcher @ MIT: Web-enablement of the RFID network

Oracle-Labs, Jan. 26, 2011


INTRODUCTION AND MOTIVATION

What’s the Web of Things? What is it good for?

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



The Embedded Systems Era

Ubiquitous: Home appliances Industries Smart Cities

Connected: Zigbee, Bluetooth, Wifi

Application Integration?



Finding an Application Integration Platform

Question: How do we enable tech savvys and

companies to create applications on top of this eco-system?

Hundreds of different platforms Web?

Scalable (7000 Facebook p/sec.)

Ubiquitous (from mobile to desktop)

Well-understood (1.73 Bio. users)

Thesis: Re-use and develop Web-standards to

build a Things Universal API.



The Web of Things


Today’s Menu

1. Motivation

2. Web of Things Architecture

3. Applications

4. Evaluations

5. Case Study in RFID

6. Challenges beyond REST

7. WoT and the business

7

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

Dominique Guinard, ETH / SAP Research


WEB OF THINGS ARCHITECTURE

Building a Web of Things, piece by piece…

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



REST: The Core of the Web

REST: architecture with 5 constraints

1. Identify resources and links: A resource: something, that can and that’s worth, getting a URI and

links

2. Design respresentations

3. Use the uniform interface

4. Bring things to the Internet&Web

[2] Architectural styles…

[1] RESTful Web Services.



Case Study with Sun Spots1) Resources and Links

Thanks to their atomicity services on embedded devices are quite adapted to Resource-Oriented Architectures. 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

Resource Identification Hypermedia



2) Representation Design

HTML as default, ideal for browsing: http://webofthings.com/spots

JSON & JSONp, ideal for mashups

XML, ideal for integration with business systems

Self-Describing Messages Hypermedia


http://webofthings.net/spots


3) Interface Design

Leverage content negotiation: Accept: application/json

Use the HTTP Verbs extensively: GET, PUT, POST, DELETE GET http://webofthings.com/spots/2/sensors/temperature PUT http://webofthings.com/spots/2/actuators/led/1

Map status codes: 200 OK, 201 Created, 400 Bad Request

Uniform Interface Self-Describing Messages


http://webofthings.com/spots/2/sensors/temperature



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




4) Bringing Things to the Internet&Web: Smart Gateways

6lowpan coming quickly: Cisco, IPSO, OpenPicus

HTTP Reverse Proxy Hiding IoT proprietary protocols

(Zigbee, Bluetooth, etc.): Dongle based

OSGi modularity

Installed on residential gateways: Wireless routers (OpenWrt)

NAT

RESTful Design Process can be (partially) automated

[3] Facilitating Integration of

Services for WoT


Demo!


APPLICATIONS

What can we build on top of the Web of Things?

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



Typical WoT Architecture: « Energie Visible »

Project for a private foundation for sustainability (cudrefin02.ch)

Goal: an easily deployable system for better understanding consumption: Cross-platform

Web access

Uses the Plogg sensor nodes Smart Gateway provides

RESTful API



« Energie Visible »: Mashup and UIs

Web UI / Mashup using Javascript (GWT): www.webofthings.com/energievisible

E-Meter iPhone App

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

[4] Increasing Energy Awareness Through Web-enabled Power Outlets.



Physical Mashup Editors

• Clickscript:– Javascript (JQuery / DOJO) based

visual language.

• Added wrappers for WoT devices:

– SunSPOT, Ploggs, RFID reader

[http://www.clickscript.ch]

[5] Mashing up Your Web-Enabled Home


Demo!


Protecting Access to Things: Friends and Things (FAT)


[9] “Sharing Using Social Networks in a

Composable Web of Things.”


Friends and Things: User Interface


Demo!


EVALUATION

Ok, it’s easier to build apps upon, but is the WoT really feasible?

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



Quantitative Evaluation

10’000 requests on the Sun SPOTs

1) Embedded Webserver: 205 ms (97 – 8500)

Could be improved with a proxy!

2) Smart Gateway: Sync-based (caching)

4 ms (2 – 49)

Age max: 300 ms

Good enough for most sub-second use cases.



Next Steps: Qualitative Evaluations

Plogg RESTful API & Sun SPOT API used by ~10 independent research labs.

Early feedback: Easy to understand and use Straightforward testing & Web-integration

Evaluation with 80 students: REST easier to understand, more straightforward REST more adapted to embedded devices



WEB-ENABLING THE GLOBAL RFID NETWORK

A (business-relevant) case-study in RFID



The Web Era

Rise of the WoT: Ubiquitous & Scalable The new universal integration

bus Machines, appliances,

sensors, mobile phones consumer electronics are in

Full of apps, widgets and mashups

Where is RFID?

Web



EPC Network in a Nutshell

Integration

Interface



Towards a mashable EPC Network

Classical SOAP Web Services adequate for business integration (e.g., ERP): Not so much for more light-weight, ad-hoc integration

Requirements for new API: Low entry barrier for developements (easier/cheaper) Direct data access to users Lightweight (embedded/mobile devices) Easy to scale (cloud)

[6] “Restful web services vs. "big" web services:

making the right architectural decision.”

[7] “Why is the Web Loosely Coupled? A Multi-

Faceted Metric for Service Design.”



API Design: Addressability & Connectedness

Resources: Locations, Readers, Tagged objects

(EPC), etc.

Links: Every resource is linked to its children.

And to relevant resources.

http://.../location/migros:basel/reader/warehouse:incoming/time/2009-12-21T13:22:04.000Z/event/EPC



Wait, the EPCIS is not Hierachical!

The EPCIS data isn‘t really hierachical: Complex queries become cumbersome:

all events occurring in 2010 for urn:epc:id:sgtin: 0057000.123430.2025 Query-based interface

http://.../eventquery/result?param1=value1&..&paramN=valueN

http://.../eventquery/result?reader=sap:regensdorf:frc:storage&epc=urn:epc:id:sgtin:200057000.*



Design: Representations

Several representations: XML: EPCIS standard

JSON: Web integration

HTML: browsability CSS for browser

CSS for mobile (IUI)

Selected through “HTTP content negotiation”

Atom feeds for subscription to queries.



Implementation: EPCIS Web-adapter



Performance Evaluation



EPC Mashup Dashboard

Javascript mashup (GWT). Uses the REST API. Extensible widget base.


Demo!


Next Steps: EPC Cloud @ MIT Auto-ID Labs


Demo!


CHALLENGES BEYOND REST

Where is/should the Web of Things go?

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



Enabling the Real-Time Web: Beyond Client-Server

Client-server paradigm not really natural for sensing application.

Need for sensor push. First step:

Atom (cleaner RSS) / AtomPub

Real push HTML5 Websockets

Pubsubhubbub

Server-sent events

XMPP



Search and Performances

Finding Services: HTML5 Microdata RDFa WoT Search:

Google Custom Engine Yahoo Search Monkey Dyser

Performances! Push vs Pull Highly scalable Web-servers

Node.js Grizzly

Cloud solutions: GWE



WOT & THE BUSINESS

A Compelling Business Use Case for the WoT

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



Actors of the (future) WoT Market

« Smart Things » manufacturers: Consumer « gadgets »:

Violet, Chumby, Poken, Arimaz

Sensors/actuators nets: Phidget, SunSPOTs, Sentilla,

OpenPicus, 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/]




« 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]




Software / Cloud solution providers Pachube Sensor.Network Google:

Power Meter Visualization API GAE

SAP, Oracle, IBM SAP MII, AII IBM Smarter Planet Sensor Edge Server

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

[http://www.pachube.com]

[http://www.sap.com]

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


Wrap Up: Beware, WoT is coming!

The vision 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 and the Web are a good

candidates: Ubiquitous Rather easy to understand Scalable Core to the Web Lightweight, etc.

A lot of WoT consumer-products / business opportunities are emerging.

41Dominique Guinard MIT / ETHOracle-Labs, Jan. 26, 2011


Thanks a lot for your attention

Dominique Guinard Contact details:

www.guinard.org

Blog: www.webofthings.com

Software: www.webofthings.com/projects

Papers and articles: www.guinard.org/publications


http://www.guinard.org/

http://www.webofthings.com/

http://www.webofthings.com/projects

http://www.guinard.org/publications


References

1. L. Richardson and S. Ruby. “RESTful Web Services”. O'Reilly Media, Inc., 2007

2. R. Fielding: “Architectural styles and the design of network-based software architectures”, 2000

3. S. Mayer, D. Guinard, V. Trifa: “Facilitating Integration and Interaction of Real-World Services for WoT” Urban IoT 2010

4. M. Weiss, D. Guinard: “Increasing Energy Awareness Through Web-enabled Power Outlets” MUM 2010

5. D. Guinard: “Mashing up Your Web-Enabled Home”, Touch the Web 2010


All our papers are on: www.guinard.org/publications


References

6. Pautasso, Cesare, Olaf Zimmermann, and Frank Leymann. “Restful web services vs. "big" web services: making the right architectural decision.” WWW '08

7. Pautasso, Cesare, and Erik Wilde. “Why is the Web Loosely Coupled? A Multi-Faceted Metric for Service Design.” WWW’09

8. 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.

9. Dominique Guinard, Mathias Fischer, Vlad Trifa10. “Sharing Using Social Networks in a Composable Web of

Things.” Proc. of the First IEEE International Workshop on the Web of Things (WOT2010). Mannheim, Germany, March 2010



Backup



Age of Cache


WoT @ Oracle-Labs

Technology

Transcript of WoT @ Oracle-Labs