Internet of Things Architecture

(ALE i/f) and capturing i/f are implemented according to the EPCglobal
standards.

To finish up with the lower level, the Data Capture Device box (Tag Reader) is
the one observing events relating to RFID Tags. The corresponding Reader i/f
provides those events to the Filtering & Collection box.

Data Capture

Device

(i.e. RF Reader)

Data Capture

Device Management

(i.e. RF Reader Mngt)

Filtering &

Collections

EPCIS

Capturing Application

EPCIS Repository

EPCIS Accessing

Application ONS^ i/f Local^ ONS

Reader Mngt i/f

Air protocol

Reader i/f

Application Level Event i/f

EPCIS Capturing i/f

EPCIS Query i/f

End User A

Discovery Services ONS Root

EPC Network Services

EPCIS Accessing

Application

End User B

EPCIS Query i/f

Discovery i/f Discovery i/f

RFID Tag

Figure 105 : EPCglobal system architecture (simplified).

The purpose of the reverse mapping is to check if the EPCglobal architecture is
compatible with the IoT Reference Model.

The EPCglobal architecture illustrated above in the Figure 105 is not exactly an
EPCglobal domain model (as we understand IoT Domain Model in IoT-A), but
rather a high-level diagram of a concrete architecture. Because the two models
are not exactly similar in nature (i.e. IoT Domain Model is clearly at the
―concept‖ level while the EPCglobal is a high level system architecture
description) the reverse mapping of the EPCglobal architecture towards the IoT
Domain Model is not a straightforward or simple process.

So in the following we use the EPCglobal system architecture in order to extract
the EPCglobal concepts and then build an EPCglobal domain model taking a
basis the generic IoT DM (meaning we try linking the EPCglobal concepts using