uID Concept IoT Reference Model
ConceptCommentsLocation Physical Entity Location is not modelled explicitly in the
IoT Domain Model. However, a specific
(possibly tagged) place can be regarded
as a Physical Entity.
uCR model Relates to Information
ModeluCR can be used for representing IoT-A
Information Model instances
ucode No direct relation The ucode can be used as an globally
unique identifier for any instance of the
IoT-A RM concept
ucode resolution
gatewayNetwork-based
ResourceProvides a ucode resolution over HTTPucode signature
serverNetwork-based
ResourcePrevents ucode counterfeiting by verifying
and generating signatures
ucode management
serverNetwork-based
ResourceManages the allocated ucode spaceucode issue
gatewayNetwork-based
ResourceProvides a HTTP interface for obtaining
ucode issued by ucode management
server
ucode entry update
gatewayNetwork-based
ResourceProvides a HTTP interface for updating
ucode resolution entry
Top Level Domain
ServerNetwork-based
ResourceHierarchical component of the ucode
resolution server
Second Level
Domain ServerNetwork-based
ResourceHierarchical component of the ucode
resolution server
ucode Resolution
ServerNetwork-based
Resource / ServiceThe Resource would be exposed through
a resolution service.
Application
Information ServiceService Provides infrastructure and application
services
ucode Tag Tag
User Terminal (Device) Is a device that reads ucodes and provides
services based on the ucode to a user. A
user terminal that is just used to run an
application or display some information is
not in the scope of the IoT Domain Model.
However, a user terminal containing a
reader is in the terms of the IoT Domain
Model a Device with an embedded Sensor
Device.
Reader Device / Sensor
Table 36 : Mapping of uID concepts to the IoT Reference ModelIn turn, the reverse mapping produced the following UML (see Figure 108 )
below: