1. IEEE SN4MS 2012, Besançon, France – November 20, 2012
A novel approach to Web of Things:
M2M and enhanced Javascript
technologies
Vincenzo Catania, Giuseppe La Torre, Salvatore Monteleone and
Davide Patti
University of Catania
Stefano Vercelli and Fabio Ricciato
Telecom Italia S.p.A.

2. From IoT to WoT
 Internet of Things (IoT)
 Network of daily life objects (things)
 Identifiable things: RFID, QR-Code
 Lack of a standard communication protocol
 Fields: Tracking, domotic, health
 Web of Things (WoT)
 Identifiable and controllable “smart things”
 Things are identified by URI
 Communication through RESTfull API

3. Future trends
Source: Cisco IBSG, 2011

4. Future trends
Source: Analysis Mason

5. WoT Platforms
Social Networks of Things
 REST Web technologies for API
 JSON (JavaScript Object Notation)

6. Cosm (Pachube)

7. WoT/M2M Requirements
 Things discovery
 Identification, position
 Multi-user access
 E.g. Network of temperature sensors
 Privacy and access control
 Health applications
 Low-level abstraction
 Several languages, Several hardware

8. The Webinos Project
The webinos project will define and deliver an Open Source Platform
and software components for the Future Internet in the form of web
runtime extensions, to enable web applications and services to be
used and shared consistently and securely over a broad spectrum of
converged and connected devices, including mobile, PC, home media
(TV) and in-car units.

9. Webinos features
 Cross-platform
 Windows, Linux, OSX, Android
 Cross-domain
 PC, Handsets, Entertainment, Automotive,
Embedded systems (Pandaboard)
 As soon: Raspberry PI
 Service Discovery
 User Management
 Security

10. Webinos Personal Zones
 A Personal Zone Virtually
contains a set of devices
owned by a user
 PZ can include non-IP
devices (BT, ZigBee)
 Devices authenticate
themselves to the PZH
 PZHs can be bridged for
inter-user communication

11. Webinos Personal Zones

12. Webinos Device/PZP Architecture
12

13. Webinos APIs
 Each Device’s API can be seen as a service.
 Discovery API
 To access services exposed
 By device
 by entities directly connected to the device (e.g sensors)
 by trusted entities registered in a personal zone
 File API (data storage)
 Messaging API (notifications)
 Sensors/Actuator API

14. Webinos Sensors/Actuators APIs
 The sensors/actuators services can be located in the
user's personal zone or be shared on the current network.
 Sensors API (http://webinos.org/api/sensors)
 Each sensor has a GeoPosition information
 Sensor’s configuration (timeout, rate, …)
 Sensor’s value can be get periodically or when it changes
 Actuators API (http://webinos.org/api/actuators)
 Support for: switches, motors, thermostats, …
 setValue(double[], succ, fail) function

15. Sample code: Webinos Sensors API
webinos.discovery.findServices(new ServiceType(
'http://webinos.org/api/sensors.temperature'),
{onFound: function (service) {
temp_sensor = service;}
});
temp_sensor.sensor.configureSensor(
{rate: 2000, eventFireMode: "fixedinterval"},
successCallback, errorCallback);
temp_sensor. addEventListener(”temperature",
function (event) {
alert(“Current Temperature is “ +
event.sensorValues[0]);
},
false);

16. Webinos Users/Devices Management
 Authentication API
 User authentication
 Google ID, Yahoo ID
 Device authentication
 Each devices has public/private key
pair
 PZH acts as certificate authority
 Secure communication among
devices and PZs
 TLS (Transport Layer Security)

17. Webinos Security and Privacy
 XACML-like Security policy architecture
 Each API is identified by unique URI
 Which entity (user/devices) can access a resource (API/data)
provided by one of user’s devices (one of each inside my PZ)
 Each device can be shared across several PZs but is owned by
only one user
 Policy editor
 Automatic Policy synchronization (and conflicts notification)
among devices
 Supports both Access Control and Data Handling policies

18. Webinos Sensors Demo

19. Example: Webinos M2M Application
My house
My parents’ house
My PZH alerts my smartphone when something happens (e.g. burglar alarm
has been activated) in my or my parents’ house

20. Conclusions
 WoT/M2M requirements
 Webinos as platform for WoT and M2M, Webinos meets:
 Hardware abstraction
 Discovery
 Security
 User/device management
 Our contribute
 Specification and implementation of Sensors/Actuators API
 Demo Web application