Internet of Things Architecture

VE Service

VE & IoT

Service Monitoring

VE Resolution

IoT ServiceResolution IoT Service

OrchestrationService

CompositionService

CommunicationEnd To End CommunicationNetwork CommunicationHop to Hop

Management Security

Application

Virtual Entity IoT Service

Communication

Fault

Authorisation

Key Exchange &Management

Trust & Reputation

Identity Management

Authentication

Device

Reporting

Member

State

Process Management IoT

ModelingProcess

ExecutionProcess

ChoreographyService

OrganisationService

On-board

Logistics

Temperature Sensor

Configuration

Figure 40 : ―Red Thread‖ example

In that figure, Functional Components which are used only once, such as during
the instantiation of the process model or configuration of devices are indicated
in light yellow.

Functional Components which are used at runtime of the use case are indicated
in orange.

The example of this section can be described only at a high level, since a
concrete architecture and implementation are needed to go into further detail.
Also the design choices of the concrete architecture need to be considered.

In this example, the embedded sensors (Temperature Sensor) continuously
measure the environmental conditions within the truck. The measurement data
is available to ―Ted‖ ‘s IoT-Phone (On-board Logistics Application) since the
IoT-Phone is subscribed to the service exposing the measurement data (IoT
Service). In order to subscribe to the data, the association between the service
exposing the data and the Load carrier needs to be resolved (VE Resolution
and IoT Service Resolution). The communication from sensor to IoT-Phone
makes use of the network protocol stack of the IoT Communication Model (End
To End Communication, Network Communication, Hop to Hop Communication,
Key Exchange & Management). All transactions take place in a secure way,
meaning that no operations are allowed unless authentication (Authentication)
took place and explicit authorisation is obtained for the particular operation
(Authorisation).

It is beyond the scope of this section but an illustration of the adaption of the
ARM to a specific case and implementation can be found in [Meyer 2013].