also be seen as a convenience function as the Service Description also
contains the currently valid service locator.
Associations can be registered with the VE Resolution by services that know for
what Virtual Entities they can provide information. The registration can be done
by users, by special management components, or by the VE & IoT Service
Monitoring component. The VE & IoT Service Monitoring component
automatically derives the Associations based on information existing in the
system, including Service Descriptions and other associations.
4.2.3.3 Information handling by Functional Components
The following section describes how information is handled and exposed by the
functional components in an IoT-system and shows the information flows
between the functional components.
Before going into detail Figure 43 shows the information flow through the
Functional Components based on the recurring example from Section 2.3. From
the actuator on device level the temperature information is transferred to the IoT
Service and afterwards to the VE Service. The VE Service itself is described in
Section 3.4.2. From the VE Service the temperature value is transferred to the
AndoidApp via the Subscribe/Notify-pattern.
Figure 43 : Information flow based on the ―Read Thread‖.General information flow concepts
There are four message exchanges patterns considered for information
exchange between IoT Functional Components. The first message exchange