[White Paper]

T-Engine Forum
Ubiquitous ID Center
Document
DRAFT
910-S002-0.00.24 / UID-CO00002-0.00.24
11/16/2006

Ubiquitous ID Architecture

T-Engine Forum
Ubiquitous ID Center Document

Number:Title:
Status:Date:

910-S002-0.00.24 / UID-CO00002-0.00.24

910-S002-0.00.24 / UID-CO00002-0.00.24
Ubiquitous ID Architecture[X] Working Draft, [ ] Final Draft for Voting, [ ] Standard
11/16/2006

Copyright (C) 2010, Ubiquitous ID Center, T-Engine Forum. All rights reserved.

2

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Table of Contents

Introduction......................................................................................................................................................................... 4
Scope................................................................................................................................................................................ 4
Concept of this Document....................................................................................................................................... 4
Reference Documents ............................................................................................................................................... 4
Definition of Terms .......................................................................................................................................................... 4
1. Ubiquitous ID Architecture.................................................................................................................................... 6
1.1. Purpose of Ubiquitous ID Architecture Establishment......................................................................... 6
1.2. Basic Principles of Ubiquitous ID Architecture....................................................................................... 8
1.3. Fundamental Technology and Mechanism of Ubiquitous ID Architecture .................................... 8
2. ucode ............................................................................................................................................................................112.1. ucode Model ........................................................................................................................................................112.2. ucode Classification .........................................................................................................................................122.3. Code System of ucode....................................................................................................................................122.4. ucode Tag.............................................................................................................................................................132.4.1. ucode Tag System....................................................................................................................................132.4.2. Security Class ............................................................................................................................................13
2.4.3. Interface Category....................................................................................................................................14
3. Information Representation by ucode ..........................................................................................................16
3.1. ucode Relation Model (ucR model).............................................................................................................16
3.1.1. ucR Unit........................................................................................................................................................16
3.1.2. ucR Graph ....................................................................................................................................................18
3.2. ucR Format ..........................................................................................................................................................19
3.3. ucR Vocabulary ..................................................................................................................................................20
3.4. Simplified ucode Relation Model..................................................................................................................20
4. ucode Resolution ....................................................................................................................................................21
4.1. ucode Resolution ...............................................................................................................................................21
4.1.1. ucR Database .............................................................................................................................................21
4.1.2. ucode Resolution and ucode Information Service .......................................................................21
4.2. Simplified ucode Resolution ..........................................................................................................................23

3

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Ubiquitous ID Architecture

Introduction
ScopeThis document describes the basic concept of Ubiquitous ID architecture.
It also specifies an outline of the fundamental technologies for Ubiquitous ID
architecture.

Position of this Document
This document describes the basic concept and system outline of
Ubiquitous ID architecture. It lays the groundwork for other specifications forthis ubiquitous ID architecture.

Other respective documents for Ubiquitous ID

architecture are derived from this specification.

References[1] T-Engine Forum, Ubiquitous ID Center, "ucode: Ubiquitous Code."
910-S101/UID-00010, 2006.
[2] T-Engine

Forum,

UbiquitousID

Center,"ucodeTag

System."

930-S201/UID-00017, 2006.
[3] T-Engine Forum, Ubiquitous ID Center, "ucode Resolution Protocol(Simplified Edition)." 910-S202/UID-0005, 2006.
[4] T-Engine Forum, Ubiquitous ID Center, "ucode Resolution Protocol(Standard Edition)." 930-S221/UID-00008, 2006.
[5] T-Engine Forum, Ubiquitous ID Center, "ucode Contents Transfer
Protocol: uCTP." 930-S301/UID-00009, 2006.
[6] T-Engine Forum, Ubiquitous ID Center, "ucR format: ucode Relation
Description Format." 940-S101/UID-00026, 2006.
[7] T-Engine Forum, Ubiquitous ID Center, "ucR vocabulary: Vocabulary
Definition in the ucR Model." 940-S301/UID-00029, 2006.

Definition of Terms

4

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Relevant terms are defined in the text when they appear for the first time.

5

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

1. Ubiquitous ID ArchitectureThis chapter describes the overall outline specifications of Ubiquitous ID
architecture and the structure of this document.

1.1. Purpose of Ubiquitous ID Architecture Establishment
Ubiquitous computing is a technology that supports a better way of living by
providing computing cpacity to various entities in the living space—for
example, walls, furniture, floors as well as home electronic appliances—andequipping them with autonomous control so that they can exchange
information and operate in collaboration (Figure 1).

Intelligent Lighting
SystemIntelligent
Air-Conditioning System
Intelligent
Ceiling
Intelligent
SensorIntelligent
Wall

Communication
MachineIntelligent DeskIntelligent
ChairIntelligent
Floor
OPEN-ENDED

Figure 1: Image of Indoor Ubiquitous Computing
Moreover, this technology supports a better way of living by providing
computing power to not only indoor but also outdoor objects including utility
poles and signboards in towns and equipping them with autonomous control
so that they can exchange information and operate in collaboration.

6

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Figure 2: Image of Outdoor Ubiquitous Computing Environment
In order to realize such ubiquitous computing environment, it is important torecognize the real-world context. This is called context-awareness. To
realize context-awareness, it is essential to recognize various objects, places,
and concepts in the real world. It is impossible to enumerate all the contexts in
the real world in advance.
Accordingly, in our approach, unique identifiers consisting of fixed-length
integers are provided to respective objects, spaces, and concepts desired tobe identified in the real world. We also provide frameworks that can map thereal world and its context to the format acceptable as digital information byrepresenting them as the relationships among objects, places, and concepts towhich their unique identifiers are assigned. The target to be identified is calledan "entity" in our terminology, and the unique identifier to identify the entity iscalled a ucode (ubiquitous code). To summarize, the ucode model is one ofdescriptive models representing the real-world context as digital information.
This model assigns ucodes to individual entities and maps the real world andits context to the format acceptable as digital information by using therelationships between ucodes. Ubiquitous ID architecture is a systemarchitecture for substantiating the ucode model.
7

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Ubiquitous ID architecture is a common platform which obtains an device
status and controls the device and provides information and services by using
ucodes that identify entities in the real world as triggers.

It is theinfrastructure architecture to connect the real world which entities represent
and the virtual world which device networks and information services
represent. This document and its derived specifications are designed torealize Ubiquitous ID architecture.

1.2. Basic Principles of Ubiquitous ID Architecture
The basic principles of Ubiquitous ID architecture are as follows:(1) Identifying an Entity
The ucode is defined as an identifier system for identifying individual entities
uniquely.
(2) Assuming Network Environment
Only ucodes are assigned to individual entities themselves. Information ofentities to which the ucodes are assigned is usually stored into the server on
the network. By detaching entity identifications from information management,
we can realize such services as obtaining the latest information on a certain
object or its related entities.
(3) Providing a Security Mechanism
A secure wide-area distributed system that can assure privacy protection
into account is established by using the eTRON architecture as security
infrastructure.
(4) Providing an Open Platform
The Ubiquitous ID architecture specification shall be basically released.

1.3. Fundamental Technology and Mechanism of Ubiquitous ID
Architecture
The fundamental technologies for realizing Ubiquitous ID architecture are as
follows:(1) ucode Tag
A ucode tag is a medium that stores a ucode.
(2) Ubiquitous Communicator: UC
A UC is a user terminal that reads ucodes and provides services based on
the ucode to a user.
8

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24(3) ucode Relation Database
A ucode relation database manages entity information in a distributedmanner.
(4) ucode Information Server
A ucode information server manages information displayed by and services
provided to UCs.
With these fundamental technologies, a UC receives services based on theucode in the following steps.
(1) A UC reads the ucode assigned to an entity and obtains the context in thesurrounding real world.
(2) A UC accesses the ucode relation database and derives the informationaccording to the ucode and context from the ucode relation database
based on the obtained ucode. This process is called ucode resolution. A
UC can register the information associated with ucode to the ucode
relation database. This process is called ucode registration.
(3) As a result of the ucode resolution, a UC accesses a ucode information
server after it obtains the address of the ucode information server fromthe ucode relation database. This allows the terminal to provide theservices related to the ucode retrieved from the ucode information server
such as displaying the information on the obtained ucode, and controllingthe device corresponding to the ucode. Registration to the ucode relation
database is among the services related to ucodes.
Figure 3 illustrates one of the important Ubiquitous ID architecture
applications, which is a mechanism of deriving and displaying the information
related to the obtained ucode.

9T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Ubiquitous
Communicatorucode Relation
Database

Place
Network

Physical Object(product)

ucode Information
serverFigure 3: Information Retrieval Mechanism Based on Ubiquitous ID Architecture10T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

2. ucodeThis chapter specifies the ucode which is the base of Ubiquitous ID
architecture. Among the ucode specifications are the ucode model whichmaps the real-world context to the format acceptable as digital information
using ucodes, the ucode classification and code system, and the ucode tag
which is a medium that stores a ucode. This document outlines the ucodeclassification and code system and the ucode tag which is a medium that
stores a ucode.

2.1. ucode Model
To identify individual objects, spaces, and concepts in the real world, unique
identifiers are assigned to respective objects, spaces and concepts that wewish to identify. This model is called a ucode model. The target in the realworld to be identified in the ucode model is called an "entity,” and the unique
identifier assigned for identifying the entity is called a ucode.
The entity consists of objects, places, and concepts. "Objects" in the ucode
model include tangible objects such as industrial products and agricultural
crops, and intangible objects such as content and programs. "Places" include
features in the real world such as roads and buildings and more detailed
smaller components in the real world such as rooms and corridors. "Concepts"
include the relationships between "objects" and "places" and the information
which can be the real-world context. In a nutshell, the entity is a target to be
identified among objects, places, or concepts in the real world, and theidentifier to identify the entity is a ucode.
ucodes are not assigned to every entity in the real world in advance. Whenrealizing various services, ucodes are assigned as needed to the targets
needed to be identified. Conversely, objects, places, and concepts in the realworld cannot be distinguished based in the ucode model unless ucodes are
assigned to them. The information to which ucodes are not assigned andconstant is called an atom. Figure 4 illustrates the above relationships.2

2

It is our policy not to attach ucode tags to people due to security and private concerns.
11T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

entityucode

entity

ucode

atom
atom
ucode

entityreal world

ucode model

Figure 4: Relationships among ucodes, Entities and Atoms

2.2. ucode Classification
A ucode model classifies a ucode into the following two types (Figure 5).
z

Physical ucode:

A physical ucode is a ucode stored in thedevice physically associated with an individual item (this device iscalled a ucode tag [2] ).
z

Logical ucode:

A logical ucode is not a physical ucode, inother words, does not have to be stored in a ucode tag.

ucode
ucode
A ucode in a ucode tag
associated with an individual item

Physical ucode

A ucode not physicallyassociated with an individual item

Logical ucode

Figure 5: ucode Classification
Generally, the ucodes which identify tangible objects are physical ucodes,
and the ucodes which identify intangible objects, contexts, and relationships
between ucodes are logical ucodes.

2.3. Code System of ucode
The basic width of a ucode is 128 bits, and it can be extended in 128 bit
units. This ucode space is managed by being divided into subspaces called adomain. In other words, a domain is a subspace as a ucode management unit .
A domain can be a metacode domain that embeds other code systems. The
detailed code system of a ucode is specified in [1].

12T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

2.4. ucode Tag
The medium which stores a physical ucode is called a ucode tag.

In otherwords, the medium stores a ucode and is physically associated with anindividual item.

A detailed ucode tag system is specified in [2].

This

document describes its outline.

2.4.1. ucode Tag System
Since the ucode tag is attached to a tangible object, it is influenced by thephysical or RF property of the object or environment where the ucode tag is
attached and used. For example, certain RFID tags cannot perform
communication if they are attached to a moisture-containing material or tometallic surfaces. Moreover, depending on the application usage, it may benecessary to keep the ucode and additional information stored in the ucode
tag confidential.
Therefore, Ubiquitous ID architecture does not uniquely specify the ucode
tag to be used. More specifically we adopt a policy that an appropriate tag canbe selected from various types of tags according to the viewpoint of merits anddemerits and application requirements. In other words, the classification
criteria for the ucode tag are established. The tag manufacturers then apply forcertification of tags, and the tag which meets the criteria is certified as astandard ucode tag. There are two classification criteria.

One is a security

class, and the other is an interface category.

2.4.2. Security Class
The security function is classified according to the security and privacy
protection function which tags must be equipped with and consists of thefollowing seven classes.
zClass 0: Data defect detection function
Damage caused in a part of data due to disturbance or physical defects
in tags can be detected.

zClass 1: Physical duplication resistance and physical forgery
resistance function
Creating data which is physically identical or similar is difficult.
13

T-Engine Forum
Ubiquitous ID Center Documentz910-S002-0.00.24 / UID-CO00002-0.00.24

Class 2: Identification prevention function
Unauthorized third parties are prevented from identifying ucodes stored
in tags and communication content, status, and methods.

zClass 3: Tamper resistance, access control management function by
resources Information stored in tags cannot be illegally read physicallyor logically.

z

Class 4: Secure communications function with unknown nodes
A secure data communication path can be established even for an
unidentified node that does not share a private key in advance via an
open network.

zClass 5: Time-dependent resource management function
Time-limit management for carrier data, security information, and tag
operation can be conducted, such as setting up a data validity period
and stopping operations after a certain period of time.

z

Class 6: Internal programs and security information update function
Protection function permits maintaining an optimum security statusbased on their usage, such as updating firmware and applying security
patches.

2.4.3. Interface Category
The interface is classified according to a tag interface device equipped in a
UC and consists of the following four categories.
zCategory 0: Print tags (bar codes, two-dimensional bar codes, etc.)zCategory 1: Passive RF tags (RFID tags with contactless interfaces,
contactless IC cards, etc.)zCategory 2: Active RF tagszCategory 3: Active infrared tags

Ubiquitous ID architecture certifies and tags that satisfy the following
conditions as a standard ucode tag, and use them.
(1) Numbering and operations which assure the uniqueness of ucodes areprovided.
(2) Any of the security classes from Class 0 to 6 is satisfied.
(3) Technical information for communicating with UCs is disclosed.
14

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

15

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

3. Information Representation by ucodeThis chapter outlines information representation by using ucodes. The
specifications for information representation by using ucodes are as follows:- the ucode Relation model (ucR model) which represents information byusing the relationships between ucodes,- the ucR format which is a representation specification for the ucR model,
and- the ucR vocabulary which defines the allocation of the meaning to thebasic logical ucodes that should be understood by each application in acommon way.
This document outlines the specifications of ucR model, ucR format, and ucRvocabulary. Details of the ucR format are defined in [6] and ucR vocabulary in[7] respectively.

3.1. ucode Relation Model (ucR model)
Ubiquitous ID architecture represents the real-world context by modeling therelation on a real-world entity as a relational representation among ucodes
allocated to entities or between the ucode and atom. This representation
model is called a ucode Relation model (ucR model).

When a relationshipis represented by ucR model, it is called a RELATION.

3.1.1. ucR Unit
The basic unit of the ucR model consists of two ucodes or a ucode and atom,and their relationships. Moreover, the respective relationships between the twoare provided with a logical ucode called a relation ucode.

This basic unit

consisting of the above triplet is called a ucode relation unit (ucR unit).
When this triplet is set in a sentence where the relationships are represented
as the predicate, the ucode as the subject is called a subject ucode, and theucode as the predicate which is a relation part is called a relation ucode, andthe ucode as the object or complement is called an object ucode. The atom
can be substituted for the object ucode. For example, in a description, "R of S
is O" or "there is a relation R between S and O," S refers to the subject ucode,
R to the relation ucode, and O to the object ucode or atom. When it is notnecessary to uniquely identify any of the three elements comprising a ucR unit,
16

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

their relevant parts can be left blank.
A ucR unit can be drawn as diagram in the following manner (Figure 6).
zucodes are represented as the shape of ellipses, and ucode values oralias names are entered in the ellipses.

z

Atoms are represented as rectangles, and their details are entered in
the rectangles.

zBlank elements are represented as the shape of ellipses, and theinsides of the ellipses are left blank.

z

Arrows connect subject ucodes and an object ucode or an atom in the
direction from the subject ucode to the object ucode or the atom, andrelation ucodes are placed on the arrows.

ucode1

ucodeAucode2

subject ucode

relation ucode

object ucode

ucode

ucodeB…

Figure 6: ucR Unit

atom

The real-world context which is used in ubiquitous computing can be
represented by using these ucR units. The real-world context is represented in
Ubiquitous ID architecture by using this ucR units.
A simple representation example of the real world context by using ucR units
is shown below. Figure 7 illustrates a diagram of each ucR unit drawn using
the procedures above.
(1) Suppose ucode: u1 is assigned to place P1, ucode: u2 to place P2,, anducode: uA to the relation that they are "adjacent." In this case, the ucR unit
diagram representing that "place P1 is adjacent to place P2." shows that u1
and u2 are connected with uA.
(2) Suppose that ucode: u3 is assigned to a PET bottle of green tea which
exists in the real world and ucode: uB to the relation "name." The ucR unit
17

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

diagram indicating "the name of this PET bottle of green tea is ‘tasty
green tea’." shows that u3 and the atom that represents "Tasty Green
Tea" are connected with uB.
(3) Suppose ucode: uC is assigned to the relation "instruction URL." The ucRunit diagram, which indicates "the instruction for the PET bottle of green
tea

described

inthe

http://www.example.org/"

previous

associates

section
u3

and

is
an

availableatom

atindicating

http://www.example.org/ is associated with uC. Note that the URL
indicating http://www.example.org/ is an atom, to which the ucode is not
assigned.
Place P1

u1

Adjacent

Place P2

ucodeA

u2

Name

u3

ucodeB

Good
Tea
Tasty
Green
Tea

Instruction URL

u3ucodeC

http://www.uidcenter.org/

Figure 7: Example of ucR unit

3.1.2. ucR Graph
The information and context about an entity are represented by combining
relations among multiple entities. For example, for information on an entity
indicating a “stuffed cabbage,” pieces of information such as its recipe, acabbage as ingredients, and a production area of the cabbage are combined.
To represent such information, ucR units are combined, and a digraph wheremultiple ucodes and atoms are connecting by relation ucodes is built. The
digraph generated based on the above method is called a ucode Relationgraph (ucR graph). More specifically, the ucR graph is a massive graphstructure, in which ucodes are connected by relations and pieces of
information described as atoms are associated with each ucode.
visualizes the ucR graph.

Figure 8

Atoms always appear as leaves of the ucR graph.

18

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Figure 8: ucR Graph
For example, starting from a dish called a stuffed cabbage, as information
on its ingredient, recipe, a production area of the ingredient, etc. is added, theucR graph as shown in the following Figure 9 can be constructed.
Name

uC

u2

Cabbage

Production
area

uB

uD

Kanagawa Pref.

Rank

L

uE
Material

Manufacturer’s
messageuA

StuffedCabbageCabbage
roll

Name

uB

u1

u3

uF

uG

Type

RecipeFigure 9: Example of a ucR Graph3.2. ucR Format
A ucR format is a generic term of description specifications based on the
ucR model.
There are three main ucR format specifications. The first stipulation is forstipulating the ucode representation method in a string text format (serialized
ucode). The second is for serializing a ucR graph into a text or a binary format(ucR format for Serialization), and the third is for embedding the ucR format
19

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

for Serialization into content data in other formats (ucR format for Content).

3.3. ucR Vocabulary
The ucR graph indicates relationships among ucodes. The ucode itself isonly a fixed-length value and does not essentially have any other meaning. On
the other hand, if various types of applications are built on Ubiquitous ID
architecture, the meaning of the ucR graph in each application should beunderstood by third parties. Therefore, it is necessary to know what logicalucodes mean in advance. For example, the food traceability systems
recognizes ucodes indicating a grade and production area of crops, and theubiquitous location information systems understand ucodes indicating that twoplaces are adjacent, etc. The definition of the meaning of basic logical ucodes
for which a common understanding is required for various applications iscalled Vocabulary..
The ucR vocabulary is a generic term that refers to vocabulary definition
specifications.
In Ubiquitous ID architecture specifications, unless otherwise specified,"vocabulary" refers to the ucR vocabulary.

3.4. Simplified ucode Relation Model
In some applications, there may be only one type of relation between asubject ucode and an object ucode or between a subject ucode and an atom,or it may not be required to identify such relations. For those applications,Ubiquitous ID architecture permits omitting the relation ucode, recognizing
there is an "implied relation" in the ucR unit. That is, the real-world context isrepresented by modeling information on entities in the real world as theimplied relations between ucodes assigned to entities or between a ucode
assigned to an entity and an atom. This representation model is called thesimplified ucode Relation model.

20

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

4. ucode Resolution
This chapter outlines the mechanism for realizing the ucode model and ucRmodel consisting of three parts as follows.
- the ucode relation database,- the ucode resolution which manipulates information using the ucode
relation database, and- the ucode information service which is obtained as a result of the ucode
resolution.
This document describes an outline of these three mechanisms.

Theirdetails are defined in [3], [4], and [5].

4.1. ucode Resolution
4.1.1. ucR Database
The wide-area distributed database which manages ucR graphs is called aucode Relation database.

The ucR database comprehensively manages

information on the relations among multiple ucodes in addition to the content
such as information services associated with individual entities to whichucodes are assigned.

The ucR database is basically an open databasewhich anyone can use to reference or register information, but it can also
implement an access control.
Ubiquitous ID architecture does not specify the internal configuration of theucR database.

However, the ucR database must provide an interface forucode resolution explained in the following section.

4.1.2. ucode Resolution and ucode Information Service
When a user physically accesses an entity in the real world, Ubiquitous ID
architecture identifies the information appropriate to the situation from the ucR
database, based on the ucode assigned to the entity. This process is calleducode resolution. Moreover, the information associated with ucodes, namely,
the ucR graph is registered in the ucR database.

This process is called aucode registration.
The protocol for accessing the ucR database in this manner is called ucode
Resolution Protocol (ucodeRP).
The server, which provides ucode information services and content reachedby performing the ucode resolution, is called a ucode information server.
21

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

The ucode resolution consists of four main function modules (Figure 10).
(1) ucR Database Node (UDN)
The ucR database node (UDN) is an individual node of the ucR
database which executes distributed management of ucR units.
(2) ucR Database Front-End (UDF)
To search information on a certain ucode, it is necessary to build a ucRgraph containing the searched ucode(s). However, since the UDN which
manages ucR units is generally different depending on the ucode, it isnecessary to collect necessary ucR units from distributed UDNs and builda ucR graph consisting of these units. The ucR database front-end(UDF) handles this process.
(3) ucR Vocabulary Engine (UVE)
Basically, the UDF builds

a ucR graph, but it does not know the meaningof the ucR graph. A functional module that provides semantic inference
and interpretation for the ucR graph obtained from the UDF to narrow
down range of the intended information is called a ucR Vocabulary
Engine (UVE). The UVE may be implemented if the application-specificsearch logic is required for an application. For example, extracting
location information from the ucR graph and searching for places within a
specified range from a specified distance is one such application-specificUVE.
(4) ucode Information Service (ucodeIS)The ucode information service (ucodeIS) is a service derived from ucRgraph search results and used by users finally.

22

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

ucode Information Service(ucodeIS)

Service provision function

UCR Search Engine (UVE)

Vocabulary
analysisfunction

UCR Database
Front-end (UDF)

Vocabulary enginewith
vocabulary analysis function of
UCR graph according to theapplications

Function for building/providing
UCR graph (DB front-end)

UCR Database
UCR Database
Node (UDN)

Information service used byusers in the end

Basic search enginewith
UCR graph building and basic
query function

Distributed management function Distributed database nodeof UCR unitgroup which controls UCR
units

Application
systemInfrastructure
systemFigure 10: Basic Function Model of ucode Resolution"(1) ucR Database Node" and "(2) ucR Database Front-End" of these fourfunctional modules are part ofVocabulary

Engine"andUbiquitous ID architecture, and "(3) ucR
"(4)

ucode

Information

Service"areapplication-dependent.
In the actual systemconfiguration, each function module may be placed at
any nodes in the system such as a server, a terminal, etc. Its placement
pattern is not specified as part of ubiquitous ID architecture.

4.2. Simplified ucode Resolution
The ucode resolution performed based on the simplified ucR model is called
simplified ucode resolution. The simplified ucode resolution is a directory
service which identifies the address of content or services associated withucodes.
The UDN in the simplified ucode resolution is a distributed database which
manages the association between ucodes and the address of content orservices, and this is specially called a ucode resolution database. In addition,
the UDF in the simplified ucode resolution is a function module which identifies
location of information on content or services associated with ucodes byquerying one or more UDN.

The server with a UDF function in the simplified

ucode resolution scheme is specially called a ucode resolution server.
23

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

There is no UVE function in simplified ucode resolution. The server with aucodeIS function in the simplified ucode resolution is sometimes called simply
an Information serveR.

24

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Index
Ａ

Ｓ

atom ...........................................................................................11

security class ........................................................................13
serialized ucode..................................................................19
Simplified ucode relation model.................................20

Ｃ

simplified ucode resolution ...........................................23
context .................................................................................7, 17

subject ucode .......................................................................16

ＥＵ
ubiquitous code ...................................................→ ucode

entity ............................................................................................ 7

ubiquitous ID architecture ............................................... 7
ucode.....................................................................................7, 11

Ｉ

logical ucode ...............................................12
information server ..............................................................23

object ucode................................................16interface category...............................................................13

physical ucode ............................................12
relation ucode..............................................16
subject ucode ..............................................16

Ｌ

ucode registration........................................21
logical ucode .........................................................................12

ucode resolution ..........................................21
ucode Information Server ..............................................21
ucode Information Service ............................................22

Ｏ

ucode model.....................................................................7, 11
object ucode..........................................................................16

ucode registration .........................................................9, 21
ucode relation database.................. →ucR databaseucode relation graph..................................→ucR graphＰucode Relation Model........................... → ucR modelucode Relation Unit...................................... → ucR unit

physical ucode .....................................................................12

ucode resolution ............................................................9, 21
ucode resolution database............................................23

Ｒ

ucode Resolution Protocol..................... → ucodeRP
relation......................................................................................16

ucode resolution server ..................................................23

relation ucode.......................................................................16

ucode tag ................................................................................1225

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

ucode Tag ...............................................................................13

ucR model ..............................................................................16

ucodeRP..................................................................................21

ucR unit....................................................................................16

ucR database .......................................................................21

ucR vocabulary....................................................................20

ucR Database Front-end................................................22

ucR Vocabulary Engine ..................................................22

ucR Database Node .........................................................22
ucR format..............................................................................19Ｖ

ucR format for Contents .................................................20
ucR format for Serialization..........................................19

Vocabulary .............................................................................20

ucR graph ...............................................................................18

26

T-Engine Forum
Ubiquitous ID Center Document

910-S002-0.00.24 / UID-CO00002-0.00.24

Copyright (C) 2006, Ubiquitous ID Center, T-Engine Forum, all rights reserved.
27