Internet of Things Architecture

the IoT DM relationships, and try mapping the EPCglobal concepts to the IoT-A
concepts). Nevertheless, we still executed to reverse mapping by building an
EPCglobal domain model taking a basis the generic IoT DM (meaning we linked
the EPCglobal concepts using the IoT DM relationships, and mapped the
EPCglobal concepts to the IoT-A concepts)

First we identified a list of concepts that can be extracted from the EPCglobal
system architecture and mapped them to the corresponding IoT DM concepts.
This mapping is illustrated in the Table 34.

EPCglobal

Concept

IoT Ref. Model

Concept

Comments

Entity Physical Entity Is the Physical object been tracked by the

EPCglobal system

End-user User The user managing and using the EPCIS,

and reading the EPC

Partner user User The user willing to access EPC information

for their own business

Physical Entity Physical Entity (special

case of)

Corresponds to physical objects like

parcels, objects etc...

Location Physical Entity (special

case of)

Places, room, lift,...

RFID tag Tag The physical tag embedding the EPC.

Tag Reader Device/Sensor

Reader Interface Service

EPC manager Service Is granted a portion of the naming space

and assigns EPC to products

EPCIS Accessing

Application

User Located at end-user side that is willing to

access EPC related information

EPCIS Service Service Service that encompasses interfaces for

data exchange (through the EPCIS Query

Interface e.g.) and specification of Data

(EPCIS data standard)

EPCIS Query

Interface

Service Interface exposed by the EPCIS and

accessed by the EPCIS Accessing

Application

EPCIS Capture

Interface

Service