Internet of Things Architecture

(Elliott) #1

Resources. The Application in the FV is the use-case as described the
beginning of this section. The Devices are the RFID readers and Tags used in
the operational theatre which communicate to the IoT Services by ̳End To End
Communication‘ and ̳Network Communication‘ FCs. The entire FV is depicted
in Figure 112


Figure 112 : Functional View of the MUNICH platfom

5.6.4.8 Specification of IoT Information Model


The IoT Information Model specified for this use-case also addresses
relationships between entities that are not depicted in the IoT Domain Model
before. Some more entities appear in the IoT Business Process Model shown
before in Figure 110. For instance it is depicted that an ̳Operation‘ is held for a
̳Patient‘ and thus the ̳PatientIdentifier‘ (valid in the clinic) is assigned to an
̳Operation‘. Operations are processes with a defined status at any point in time:
̳before‘, ̳in‘, and ̳after Operation‘. There is also an unknown status in case the
status cannot be obtained. The towels are represented as VEs with domain
attributes that are essential for the use-case. The towel‘s identifier stored into a
RFID tag is one of the attributes as well as the current state of a towel that can
be one of ̳unused‘, ̳in use‘, and ̳used‘. Again there is an ̳unknown‘ state
specified in case the state cannot be obtained by the system. The
aforementioned designated locations of the operating theatre are reflected in
the Information Model as attributes of the VE ̳Towel‘. For simplification the
allowed values for this attribute {InstrumentTable; OperationTable; WasteBin;

Free download pdf