Internet of Things Architecture

IoT-A (257521)

Internet of Things – Architecture © - 86 -

class Domain Model

Device

Physical Entity

Human User

Service

On-Device

Resource

Actuator Sensor

Network Resource

Resource

User

Passive

Artefact

Active

Artefact

Virtual Entity

Digital

Augmented Entity

Tag

Animate objects (humans, animals

Hardware

Softwar

Not clearly classifiable (e.g., combination)

Colour Scheme

XOR

0..*

contain

0..1

0..*

interacts

1 0..*^

1

1..*

relates to 1

0..*

is associated with

0..*

0..*

contain

0..*

0.. (^) identifies
0.. (^) 0..1
is associated with
0..
0..
host 1
0..
contain
0..1
1
1..
0..
contain
0..1
0..
invokes
0..
0..
invokes / subscribes
1..
0..
has Information about / acts
0..
0..
reads
0..
0..
monitors
0..
0..
acts
0..
0..
is attached 0..
0..
exposes
0..*
Figure 18 : IoT DM entities involved in a Service / Resource / Device interaction (This is
a zoom of the complete IoT DM in Figure 10 ).
The complexity of this interaction is due to variety of different properties that a
Device can have; in particular, a Device can be as simple and limited as a Tag
and as complex and powerful as a server (Tag Terminal Type (TT3) and
unconstrained Terminal Type (TT1), respectively, in D3.3 [Rossi 2012]). In
fact, while powerful Devices can easily support the needed software to host and
access Services and to expose the needed Resources for other Services to
interact with, simpler Devices may only be able to provide access to their own
Resources and the simplest may even not be powerful enough even to support
this. In the latter two cases, Resources and Services must be provided
somewhere else in the network, by some other more powerful Device(s).
Thus the IoT Communication Model helps to model and to analyse how
constrained Devices can actively participate in an IoT-A compliant
communication and to study possible solutions, such as the usage of
application layer gateways, to integrate legacy technologies.