1) The document discusses the emerging field of connecting embedded devices to the internet and modeling their services using RESTful APIs to make them part of the World Wide Web.
2) Several prototypes are described that implement a "Web of Things" approach, including projects for energy monitoring and physical mashups.
3) Challenges are discussed around client-server interactions for embedded devices, discovery of connected devices, and the need for standards or best practices as the Web of Things continues to grow.
Dev Dives: Streamline document processing with UiPath Studio Web
When Things will Speak "Web" (Lecture)
1. When Things will Speak « Web » Architecture, Challenges and Business Opportunities for a Dominique Guinard, ETH Zurich & SAP Research Lecture for Lancaster University, UK. 18.02.2010
2.
3.
4.
5.
6. Enable Real-World Mashups REST REST URL PHP REST API [http://www.pachube.com] [http://www.webothings.com/energievisible] REST [http://www.clickscript.ch] JavaScript Dominique Guinard, ETH / SAP Research
7.
8.
9. 1) Connecting Embedded Devices to the Internet 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 Dominique Guinard, ETH / SAP Research
10.
11.
12.
13.
14.
15.
16.
17. Talk to devices: The WEB Way Dominique Guinard, ETH / SAP Research
Talk at least about CHUMBY, TOASTER, POKEN, NABAZTAG, etc.
The problem is that to build applications on top of these devices we still need to learn a 100 different systems and APIs. Our thesis: how do you enable business to create applications on top of eco-systems of sensor networks and embedded devices.
Thus, we suggest creating a Web of Things as an alternative. We basically consider sensor nodes as nodes of the Internet and make them universally accessible over HTTP like the Web is. We do this by: Having IP connectivity (IPv6 Lowpan) Having the nodes (or a gateway) embedding a Web-Server Modeling services as resources.
Easy to program, create new stuff Browse and use the IoT 1 or 2.0
Where we started, a quick overview of our first trials to integrate sensor networks to business applications. A few guidelines on how to make sensor nodes first class citizens of the Web. Our implementation of these guidelines on the Sun SPOT plateform, including the video of a business use case we implemented using the RESTful Sun SPOTs.
The first step is to get the Sensors connected to the Internet (!= Web, the Internet is the underlying network! Not the application layer). This can be achieved in two ways: Direct connectivity by using for instance IPv6 Lowpan, i.e. the Ipv6 protocol for resource constrained devices. More and more sensor networks (e.g. Arch Rock nodes, etc.) For non-IPv6 nodes we propose the concept of smart gateways. Smart gateways are small pieces of software that can be installed on emedded devices such as Wireless routers or NAS (Network Access Storage). Their goal is to understand the proprietary protocols and APIs of embedded devices (e.g. BT) and to « translate » offer access to these devices through uniform REST APIs.
Now that we have means to connect the nodes to the Internet we need to « Web enable » them. This is done by exposing their services as « resources », i.e. by applying the REST architectural style to represent their functionality and thus making them service nodes of the Web. REST is basically about four concepts: every thing, that can and that's worth, getting a URI and links is a resource Resources have a unique name in the form of a URI (often a URL). Resources have several representations (JSON, XHTML). Resources can be interacted with using a unform interface: HTTP:
Let’s turn a Sun SPOT sensor node into a resource. The first step is to think of what should be a resource in a Sun SPOT. Obviously the spot itself should be, so it’s sensors and actuator.
Then we think about the representation of these resources. We suggest offering at least HTML since it allows for natural browsing and user oriented-discovery of the sub resources. For application to application communication we suggest JSON, a lightweight alternative to XML which is easily parseable into objects (javascript or java). To specify the format we would like to obtain we use either a .format or the standard http accept header (recommended).
The last part is already given. HTTP provides us with pretty much everything we need to provide services on the Web.
Where we started, a quick overview of our first trials to integrate sensor networks to business applications. A few guidelines on how to make sensor nodes first class citizens of the Web. Our implementation of these guidelines on the Sun SPOT plateform, including the video of a business use case we implemented using the RESTful Sun SPOTs.
Discovery, embedded WebServer Access the Ploggs functionality directly from the browser.
Demo
Discover a Sun Spot, see the Web UI, browse it.
Where we started, a quick overview of our first trials to integrate sensor networks to business applications. A few guidelines on how to make sensor nodes first class citizens of the Web. Our implementation of these guidelines on the Sun SPOT plateform, including the video of a business use case we implemented using the RESTful Sun SPOTs.
Where we started, a quick overview of our first trials to integrate sensor networks to business applications. A few guidelines on how to make sensor nodes first class citizens of the Web. Our implementation of these guidelines on the Sun SPOT plateform, including the video of a business use case we implemented using the RESTful Sun SPOTs.