Outline Introduction The Internet of Things Mashups eHealth Use-Case

Introduction to the Web of ThingsPrinciples and Architectures supporting the Web of Things

Andreas Ruppen1

1University of FribourgDepartment of Informatics

Software Engineering Group

{firstname.lastname}@unifr.ch

Informatique de GestionDecember, 2013

Outline Introduction The Internet of Things Mashups eHealth Use-Case

1 Introduction

2 The Internet of Things

3 Mashups

4 eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline

1 Introduction

2 The Internet of Things

3 Mashups

4 eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

From Past to Presentand Future

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Moore’s Lawand some related problems

Definition (Moore)Transistors count doubles each 18 month.

Direct ConsequencesDevices get cheaper.More and more connected devices.

Indirect ConsequencesLack of enough IPv4 Addresses.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Moore’s Lawand some related problems

Definition (Moore)Transistors count doubles each 18 month.

Direct ConsequencesDevices get cheaper.More and more connected devices.

Indirect ConsequencesLack of enough IPv4 Addresses.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Moore’s Lawand some related problems

Definition (Moore)Transistors count doubles each 18 month.

Direct ConsequencesDevices get cheaper.More and more connected devices.

Indirect ConsequencesLack of enough IPv4 Addresses.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline

1 Introduction

2 The Internet of Things

3 Mashups

4 eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart Environments

Loading...The Social Web of Things

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart Environments

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background I

IoT is the Internet related to Things.A Thing is roughly a device (physical) to which somesensors or actuators are attached together with someservices (virtual) over which the Thing can communicate.The term goes back to 1999 and become popular throughthe Auto-ID Center.It was born from the need of tracking RFID tags.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background I

IoT is the Internet related to Things.A Thing is roughly a device (physical) to which somesensors or actuators are attached together with someservices (virtual) over which the Thing can communicate.The term goes back to 1999 and become popular throughthe Auto-ID Center.It was born from the need of tracking RFID tags.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background I

IoT is the Internet related to Things.A Thing is roughly a device (physical) to which somesensors or actuators are attached together with someservices (virtual) over which the Thing can communicate.The term goes back to 1999 and become popular throughthe Auto-ID Center.It was born from the need of tracking RFID tags.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background I

IoT is the Internet related to Things.A Thing is roughly a device (physical) to which somesensors or actuators are attached together with someservices (virtual) over which the Thing can communicate.The term goes back to 1999 and become popular throughthe Auto-ID Center.It was born from the need of tracking RFID tags.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background II

(a) Bar Code (b) QR Code (c) RFID Tag

Figure: Different means of identification

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background III

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Historical Background IV

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ThingsA not so formal definition

Definition (A Thing)A Thing is an entity of interest composed of a physical and avirtual side. We can interact with either of the two sides, butinteraction on one side should be reflected on the other side.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Underlying Model

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart Thermometer

Example (Digital Thermometer)To know the temperature of a given room we need somesort of a sensor.This usually comes in the form of a thermometer.Suppose that this thermometer also has a USBconnection, then one can read the temperature

either by looking at the small display orby using some sort of software on the computer.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerPhysical Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerPhysical Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerVirtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerVirtual Side

Loading...Interacting with the Virtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerVirtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart Door

Example (Smart Door)Imagine a door, then suppose that this door:

can be locked or unlocked andcan be open or close.

Furthermore it is possible to see whether a door isopen or closedlocked or unlocked

We would like to model this door and render it smart byadding some sensors and actuators.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart DoorPhysical Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart DoorVirtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerVirtual Side

Loading...Interacting with the Virtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Smart ThermometerVirtual Side

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline

1 Introduction

2 The Internet of Things

3 Mashups

4 eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

MashupsDefinition

Definition (Mashup)Mashups are a new way of programming. It is the art ofcreating new and innovative application by putting togetheralready existing applications and crossing their data. It can besee much like the job of a DJ.

UsageMashups allow quick implementation of new applications orquick modifications of already existing applications to adapt tonew situations.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

MashupsDefinition

Definition (Mashup)Mashups are a new way of programming. It is the art ofcreating new and innovative application by putting togetheralready existing applications and crossing their data. It can besee much like the job of a DJ.

UsageMashups allow quick implementation of new applications orquick modifications of already existing applications to adapt tonew situations.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

MashupsExamples

Yahoo Pipes: http://pipes.yahoo.com/pipes/How far can I travel:http://www.freemaptools.com/how-far-can-i-travel.htmFlight tracking:http://casperflights.com/unified/?location=lfbdJapan Failedrobot: http://japan.failedrobot.com/EPC Dashboard: http://epcmashup.appspot.com/

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Outline

1 Introduction

2 The Internet of Things

3 Mashups

4 eHealth Use-Case

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Domain ModelBig Picture

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Observations

At a first glance there are almost no Things on the diagram.Yet, Patients, Medical Records etc can also be seen asThings.However, they don’t have an associated physical entity.Though, the information they provide comes directly from adatabase.The interaction with such virtual only resources is exactlythe same as for real things.Furthermore, it is still possible to interact with most of themphysically, they are just loosely coupled.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Theory ISome Definitions

Definition (Web-service)Web-services are a special kind of services which are deliveredand consumed over a network. It is not important how theseservices are delivered/consumed.However, they have incommon that they offer a stable and known API to the client.

Definition (RESTful)RESTful services have a restricted interface to a set ofwell-known operations: GET, PUT, POST, DELETE. Besides,REST defines the concept of Resources. It uses HTTPapplication protocol. Therefore nothing else than a browser isneeded to interact with RESTful services and is stateless.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Theory ISome Definitions

Definition (Web-service)Web-services are a special kind of services which are deliveredand consumed over a network. It is not important how theseservices are delivered/consumed.However, they have incommon that they offer a stable and known API to the client.

Definition (RESTful)RESTful services have a restricted interface to a set ofwell-known operations: GET, PUT, POST, DELETE. Besides,REST defines the concept of Resources. It uses HTTPapplication protocol. Therefore nothing else than a browser isneeded to interact with RESTful services and is stateless.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Theory IISome Definitions

Definition (Resource)A Resource is everything that can be uniquely identified andaccessed by a client using one of the well-known operations.

Definition (Representation)A Representation of a resource is what is sent to the client.Nobody can get the resource, it is an abstract concept, realizedthrough one or many Representations. Through theseRepresentations a client can interact with a resource.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Theory IISome Definitions

Definition (Resource)A Resource is everything that can be uniquely identified andaccessed by a client using one of the well-known operations.

Definition (Representation)A Representation of a resource is what is sent to the client.Nobody can get the resource, it is an abstract concept, realizedthrough one or many Representations. Through theseRepresentations a client can interact with a resource.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingThe Alerts

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

ModelingDesing considerations

In a database all fields are equal.In representations some fields are more equal.Representations don’t have 3NF.Besides structural integrity, performance is a factorinfluence the representations.Battery life is an other factor influencing the design of therepresentations.For example, a Patient and a Caregiver will have somecommon field in their respective representation, althoughin a Database this would be modeled as a hierarchy with acommon ancestor Person.

Outline Introduction The Internet of Things Mashups eHealth Use-Case

UsageWeb-browser

Outline Introduction The Internet of Things Mashups eHealth Use-Case

Android

Démo