Internet of Things – Architecture © - 84 -
multicast and anycast are needed for fulfilling many other IoT application
requirements, such as data collection and information dissemination, etc.
With reference to our ―Red Thread‖ and the IoT Domain Model section, the
main communicating elements are: the Mote Runner Node (Device), the Alarm
Service (Service), the AndroidApp (Active Digital Artefact) and ―Ted‖ (Human
User).
This section provides insight and guidance on the interactions between
elements of the IoT Domain Model. In particular, per possible communicating
entity pair, a discussion about the relevant layer of the IoT Communication
Model will be provided.
User-Service / Service-Service interactions
As shown in Figure 17 , the IoT Domain Model entities involved in this
interaction are mainly two: User and Service (circled in solid red lines). For
instance, in our recurring example this interaction models the truck driver, Ted,
who needs to interact with the AndroidApp in order to receive alarms. However,
a Service may also assume the user role when invoking another Service, thus
Users can either be Human User or Active Digital Artefacts.
(^)
class Domain Model
Device
Physical Entity
Human User
Service
OnResource-Device
Actuator Sensor
Network Resource
Resource
User
Active Digital Artefact Passive Digital Artefact
Virtual Entity
Digital Artefact
Augmented Entity
Tag
Animate objects (humans, animals etc.)
Hardware
Software
Not clearly classifiable (e.g., combination)
Colour Scheme
XOR
contains0.. (^)
0..1
0..
interacts with
1 0..^
1
1..
relates to 1
0..
is associated with
0..
0..
contains
0..
0.. (^) identifies
0.. (^) 0..1
is associated with
0..
0..
hosts (^1)
contains (^) 0..
0..1
1
1..
0..
contains
0..1
0..
invokes
0..
0..
invokes / subscribes
1..
0..
has Information about / acts on
0..
0..
reads
0..
0..
monitors
0..
0..
acts on
0..
0..
is attached to (^) 0..
0..
exposes
0..*
Figure 17 : DM entities involved in a User-Service / Service-Service interaction (zoom of
the whole IoT DM in Figure 10 ).