Short research presentation for Ph.D and Professors of the university of Fribourg.

1. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Introduction to the Web of Things
Principles and Architectures supporting the Web of Things
Andreas Ruppen1
1University of Fribourg
Department of Informatics
Software Engineering Group
{firstname.lastname}@unifr.ch
Informatique de Gestion
December, 2013

2. Outline Introduction The Internet of Things Mashups eHealth Use-Case
1 Introduction
2 The Internet of Things
3 Mashups
4 eHealth Use-Case

3. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Outline
1 Introduction
2 The Internet of Things
3 Mashups
4 eHealth Use-Case

4. Outline Introduction The Internet of Things Mashups eHealth Use-Case
From Past to Present
and Future

5. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Moore’s Law
and some related problems
Definition (Moore)
Transistors count doubles each 18 month.

6. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Moore’s Law
and some related problems
Definition (Moore)
Transistors count doubles each 18 month.
Direct Consequences
Devices get cheaper.
More and more connected devices.

7. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Moore’s Law
and some related problems
Definition (Moore)
Transistors count doubles each 18 month.
Direct Consequences
Devices get cheaper.
More and more connected devices.
Indirect Consequences
Lack of enough IPv4 Addresses.

8. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Outline
1 Introduction
2 The Internet of Things
3 Mashups
4 eHealth Use-Case

9. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Environments
Loading...The Social Web of Things

10. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Environments

11. 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 some
sensors or actuators are attached together with some
services (virtual) over which the Thing can communicate.
The term goes back to 1999 and become popular through
the Auto-ID Center.
It was born from the need of tracking RFID tags.

12. 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 some
sensors or actuators are attached together with some
services (virtual) over which the Thing can communicate.
The term goes back to 1999 and become popular through
the Auto-ID Center.
It was born from the need of tracking RFID tags.

13. 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 some
sensors or actuators are attached together with some
services (virtual) over which the Thing can communicate.
The term goes back to 1999 and become popular through
the Auto-ID Center.
It was born from the need of tracking RFID tags.

14. 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 some
sensors or actuators are attached together with some
services (virtual) over which the Thing can communicate.
The term goes back to 1999 and become popular through
the Auto-ID Center.
It was born from the need of tracking RFID tags.

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

16. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Historical Background III

17. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Historical Background IV

18. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Things
A not so formal definition
Definition (A Thing)
A Thing is an entity of interest composed of a physical and a
virtual side. We can interact with either of the two sides, but
interaction on one side should be reflected on the other side.

19. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Underlying Model

20. 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 some
sort of a sensor.
This usually comes in the form of a thermometer.
Suppose that this thermometer also has a USB
connection, then one can read the temperature
either by looking at the small display or
by using some sort of software on the computer.

21. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Physical Side

22. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Physical Side

23. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Virtual Side

24. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Virtual Side
Loading...Interacting with the Virtual Side

25. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Virtual Side

26. 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 and
can be open or close.
Furthermore it is possible to see whether a door is
open or closed
locked or unlocked
We would like to model this door and render it smart by
adding some sensors and actuators.

27. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Door
Physical Side

28. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Door
Virtual Side

29. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Virtual Side
Loading...Interacting with the Virtual Side

30. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Smart Thermometer
Virtual Side

31. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Outline
1 Introduction
2 The Internet of Things
3 Mashups
4 eHealth Use-Case

32. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Mashups
Definition
Definition (Mashup)
Mashups are a new way of programming. It is the art of
creating new and innovative application by putting together
already existing applications and crossing their data. It can be
see much like the job of a DJ.
Usage
Mashups allow quick implementation of new applications or
quick modifications of already existing applications to adapt to
new situations.

33. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Mashups
Definition
Definition (Mashup)
Mashups are a new way of programming. It is the art of
creating new and innovative application by putting together
already existing applications and crossing their data. It can be
see much like the job of a DJ.
Usage
Mashups allow quick implementation of new applications or
quick modifications of already existing applications to adapt to
new situations.

34. Outline Introduction The Internet of Things Mashups eHealth Use-Case

35. Outline Introduction The Internet of Things Mashups eHealth Use-Case

36. Outline Introduction The Internet of Things Mashups eHealth Use-Case

37. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Mashups
Examples
Yahoo Pipes: http://pipes.yahoo.com/pipes/
How far can I travel:
http://www.freemaptools.com/how-far-can-i-travel.htm
Flight tracking:
http://casperflights.com/unified/?location=lfbd
Japan Failedrobot: http://japan.failedrobot.com/
EPC Dashboard: http://epcmashup.appspot.com/

38. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Outline
1 Introduction
2 The Internet of Things
3 Mashups
4 eHealth Use-Case

39. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Domain Model
Big Picture

40. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

41. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

42. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

43. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

44. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

45. 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 as
Things.
However, they don’t have an associated physical entity.
Though, the information they provide comes directly from a
database.
The interaction with such virtual only resources is exactly
the same as for real things.
Furthermore, it is still possible to interact with most of them
physically, they are just loosely coupled.

46. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Theory I
Some Definitions
Definition (Web-service)
Web-services are a special kind of services which are delivered
and consumed over a network. It is not important how these
services are delivered/consumed.However, they have in
common that they offer a stable and known API to the client.
Definition (RESTful)
RESTful services have a restricted interface to a set of
well-known operations: GET, PUT, POST, DELETE. Besides,
REST defines the concept of Resources. It uses HTTP
application protocol. Therefore nothing else than a browser is
needed to interact with RESTful services and is stateless.

47. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Theory I
Some Definitions
Definition (Web-service)
Web-services are a special kind of services which are delivered
and consumed over a network. It is not important how these
services are delivered/consumed.However, they have in
common that they offer a stable and known API to the client.
Definition (RESTful)
RESTful services have a restricted interface to a set of
well-known operations: GET, PUT, POST, DELETE. Besides,
REST defines the concept of Resources. It uses HTTP
application protocol. Therefore nothing else than a browser is
needed to interact with RESTful services and is stateless.

48. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Theory II
Some Definitions
Definition (Resource)
A Resource is everything that can be uniquely identified and
accessed 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, realized
through one or many Representations. Through these
Representations a client can interact with a resource.

49. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Theory II
Some Definitions
Definition (Resource)
A Resource is everything that can be uniquely identified and
accessed 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, realized
through one or many Representations. Through these
Representations a client can interact with a resource.

50. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
The Alerts

51. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

52. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

53. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

54. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

55. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

56. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Modeling
Desing 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 factor
influence the representations.
Battery life is an other factor influencing the design of the
representations.
For example, a Patient and a Caregiver will have some
common field in their respective representation, although
in a Database this would be modeled as a hierarchy with a
common ancestor Person.

57. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Usage
Web-browser

58. Outline Introduction The Internet of Things Mashups eHealth Use-Case
Android
Démo