Internet of Things Architecture

EPCglobal

Concept

IoT Ref. Model

Concept

Comments

EPC Record Virtual Entity Consists of all info related to Physical

Object identified by EPC (stored in EPCIS

Data Base), i.e. IPCIS Data

EPCIS Static Data Value Contains class level Data and Instance

level Data

EPCIS

Transactional Data

Value Relates to observations (instances,

quantity within a class)

Table 35 : Mapping of the EPCglobal information model to the IoT Information Model

Security Model

As explained in the EPCglobal Architecture Framework document [EPC
1.0.13], the EPCglobal Architecture Framework allows for many different
authentication technologies across the different interfaces. It is however
recommended in the EPCglobal architecture document, that the X.509
certificate-based method should be used by end-users when accessing the
EPCIS interface for example. Typical case occurs when the EPCIS Accessing
Application of an accessing end-user (referred as Partner user in the
architecture framework) is willing to access the EPCIS service of the primary
end-user (the one owning the EPCIS data for instance). If used the X.509
certificates are expected to comply with the X.509 Certificate Profile which
provide minimum level of security.

At the network level some network standards within EPCglobal rely on
Transport Layer Security (TSL), some others EPCglobal standards rely on
HTTPS (HTTP over TLS) for the purpose of Data protection.

At higher level both EPCIS Capturing I/f and EPCIS Query i/f standards are
allowing authentication of client‘s identity so that companies (owners of the
data) can decide very precisely whether access to that data can be granted or
denied. For the query interface, Applicability Statement 2 (AS2) is used for
communication with external partners. This RFC (4130) specifies how to
securely transport data over Internet and allows in particular for mutual
authentication, data confidentiality and integrity and non-repudiation. Those
security qualities are required in the ARM. AS2 uses x.509 certificate as defined
above.

The high level interface (AuthX) used for Authentication in the ARM Security
Model does authorise for the use of X.509 certificates.

5.6.3 uCode

The Ubiquitous ID (uID) architecture is an architecture proposed by Prof.
Sakamura (from the University of Tokyo) [Koshizuka 2010] to implement
the concept of Ubiquitous Computing (ubicomp). Ubiquitous computing is a
paradigm coined initially by Mark Weiser in the late 80‘s [Weiser 1991]. It
touches many aspects of computing, like OS‘s, displays, intelligent user