[White Paper]

T-Engine Forum
Ubiquitous ID Center
Document
DRAFT
910-S204-1.A0.04/UID-CO00007-01.A0.04
2008-10-17

ucode Resolution Gateway

T-Engine Forum
Ubiquitous ID Center Specification

Number:Title:
Status:Date:

910-S204-1.A0.04/UID-CO00007-01.A0.04

910-S204-1.A0.04/UID-CO00007-01.A0.04
ucode Resolution Gateway[X] Working Draft, [ ] Final Draft for Voting, [ ] Standard
2008/10/17

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

2

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table of Contents
Introduction ........................................................................................................................... 5
Scope................................................................................................................................................................................ 5
Position of this Document ....................................................................................................................................... 5
Reference Documents ............................................................................................................................................... 5
Definition of Terms ................................................................................................................ 5
1. Purpose ............................................................................................................................ 6
1.1. Definition................................................................................................................................................................. 6
1.2. Purpose ................................................................................................................................................................... 6
2. Gateway Functions ...........................................................................................................7
2.1. ucode Resolution/Contents Acquisition Function ................................................................................. 7
2.2. Cache Function .................................................................................................................................................... 7
2.3. Contents Conversion Function ...................................................................................................................... 7
2.4. Signature Verification Function ..................................................................................................................... 7
2.5. Operation Mode.................................................................................................................................................... 8
3. Gateway Behavior ............................................................................................................93.1. Without a Cache Hit ........................................................................................................................................... 93.2. With a Cache Hit on the Gateway ................................................................................................................ 93.3. With a Cache Hit on the Terminal ..............................................................................................................10
4. ucode Resolution Gateway Protocol............................................................................... 124.1. Outline ...................................................................................................................................................................124.2. Parameter Definition ........................................................................................................................................124.2.1. Request Parameters ................................................................................................................................124.2.2. Response Parameter ...............................................................................................................................15
4.3. Gateway Operation Mode...............................................................................................................................194.3.1. Recursive Mode .........................................................................................................................................19
4.3.2. Resolveall Mode.........................................................................................................................................19
4.3.3. Resolve Mode .............................................................................................................................................20
4.3.4. Redirect Mode ............................................................................................................................................20
4.3.5. Portal Mode .................................................................................................................................................20
4.4. Method of Sending/Receiving Parameters .............................................................................................21
4.4.1. Method of Sending Request Parameters.........................................................................................21
4.4.2. Method of Receiving Response Parameters ..................................................................................22
4.4.3. HTTP Parameter .......................................................................................................................................23
4.5. Cache .....................................................................................................................................................................24
3

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

4.5.1. Cache Method ............................................................................................................................................24
4.5.2. TTL .................................................................................................................................................................25
4.6. Contents Conversion .......................................................................................................................................26
4.7. Operation Example............................................................................................................................................26

4

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

ucode Resolution Gateway

Introduction
ScopeThis document specifies the functions of a ucode resolution gateway and aninterface protocol between the client and gateway.

Position of this Document
The protocol used for ucode resolution in this document is a simplified
ucode resolution protocol [2]. This document can be extended in the future tocorrespond to the "ucode Resolution Protocol (Standard Edition)" [3] based on"Ubiquitous ID Architecture" [1].

Reference Documents[1] T-Engine Forum, Ubiquitous ID Center, "Ubiquitous ID Architecture,"
910-S002/UID-00002, 2006.
[2] T-Engine Forum, Ubiquitous ID Center, "Simplified ucode Resolution
Protocol," 910-S202/UID-00005, 2006.
[3] T-Engine Forum, Ubiquitous ID Center, "ucode Resolution Protocol(Standard Edition)," 910-S221/UID-00008, 2006.
[4] T-Engine Forum, Ubiquitous ID Center, "ucode Encode Specification withQR Code Tag Signature," 930-S304/UID-00025, 2006.
[5] RFC 2068, "Hypertext Transfer Protocol -- HTTP/1.1," 1997.
[6] RFC3513, 「Internet Protocol Version 6 (IPv6) Addressing Architecture」,
2003.
[7] RFC3986, 「Uniform Resource Identifier (URI): Generic Syntax」, 2005.
[8] RFC952, 「DOD INTERNET HOST TABLE SPECIFICATION」, 1985.

Definition of Termszucode
An identifier (ID) for the purpose of identifying "objects" and "places" in thereal world5

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

1. Purpose
1.1. Definition
The ubiquitous ID architecture permits information on "objects" and "places"in the real world to be retrieved by various kinds of terminals such as cellular
phones.

The ucode resolution gateway is a proxy server for accessing ucode

resolution servers and information servers in place of terminals, and the ucode
resolution gateway protocol is an access protocol for this ucode resolution
gateway.

1.2. Purpose
To retrieve information on "objects" and "places" in the real world, it isnecessary to retrieve ucode resolution information from a ucode resolution
server and access an information server.

However, since ucode resolution

databases are hierarchically structured, resolution may not be done efficiently
obtained in the terminals where a CPU power or network bandwidth isrestricted. Therefore, instead of terminals, the ucode resolution gateway isdefined which executes ucode resolution and contents acquisition.

By using

the ucode resolution gateway, terminals can retrieve contents from ucodes
efficiently.

6

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

2. Gateway Functions
This chapter defines the functions of the ucode resolution gateway(hereinafter referred to as Gateway).

The Gateway is required to provide theucode resolution/contents acquisition function among the following functions.
The remaining functions are as optional.

2.1. ucode Resolution/Contents Acquisition Function
The Gateway has a function to access ucode resolution servers and retrieve
information server addresses associated with ucodes.

If ucode resolution

servers have a hierarchical multilayer structure, resolution is recursively
executed for each hierarchy.

In addition, the Gateway has a function toaccess information servers based on ucode resolution information and retrieve
contents.

This function permits terminals to retrieve contents from ucodeswith only a single request to the ucode resolution gateway.

2.2. Cache Function
The Gateway can use a cache to recycle ucode resolution results.
However, it must provide a mechanism in which the enabling/disabling of thecache for resolution and resolution results must be settable by the terminal
side. In addition, an expired cache must not be used.

This document does

not specify the cache function for contents.

2.3. Contents Conversion Function
The Gateway can have a function to convert contents into the most optimal
format, based on the terminal type which is notified by the terminal.

2.4. Signature Verification Function
The Gateway can have a function to receive and verify ucodes andsignature data.

However, it must provide a mechanism in which the signature

verification function can be enabled/disabled by a Gateway user.
This signature verification function permits users to know the validity ofucode tags.

How to store ucodes with signatures into QR Code tags is

specified in [4].

7T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

2.5. Operation Mode
The Gateway can change its behavior by switching operation modes.
Each operation mode is described in Section 4.3.

8

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

3. Gateway Behavior
This chapter describes Gateway behaviors.

The Gateway accesses ucode

resolution servers and information servers in place of terminals. Patterns ofucode resolution and contents acquisition by use of the Gateway can beclassified in the following three types according to the cache retention status ofucode resolution information.

In addition, all of the patterns are described on

the assumption that a recursive mode is set as the operation mode (Section
4.3).

3.1. Without a Cache Hit
If there is no cache on both the terminal and the Gateway, the Gateway
acquires contents by accessing the ucode resolution server and information
server and returns to the terminal.

Figure 1 shows the processing

procedures.
Terminal

Gatewayucode<1>──────→←──────<6>Contents

ucode resolution server
ucode<2>──────→←──────<3>ucode resolution
information↑<4>││Acquisition request││││
Contents ││<5>↓

Information server<1> The terminal sends the ucode to the Gateway.
<2> The Gateway sends a ucode resolution request to the ucode resolution server.
<3> The information server address is returned.
<4> The Gateway sends a contents acquisition request to the information server.
<5> The contents are returned.
<6> The Gateway returns the contents to the terminal.
Figure 1: Gateway Operation (Without a Cache)3.2. With a Cache Hit on the Gateway
If the Gateway retains the cache entry that matches the requested ucode
resolution information, it retrieves contents by accessing the information

9

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

server based on the resolution information and returns them to the terminal.
Figure 2 shows the processing procedures.
Terminal

Gateway(Retaining the cache)ucode
ucode resolution<1>──────→<2>─┐←──────<5>←─┘Contents↑<3>││Acquisition request││││
Contents ││<4>↓

Information server<1> The terminal sends the ucode to the Gateway.
<2> The Gateway executes ucode resolution with the cache search function.
<3> The Gateway sends a contents acquisition request to the corresponding
information server.
<4> The contents are returned.
<5> The Gateway returns the contents to the terminal.

Figure 2: Gateway Operation (With a Cache Hit on the Gateway)

3.3. With a Cache Hit on the Terminal
If the terminal retains the cache entry that matches ucode resolution
information, it sends address information to the Gateway, and the Gateway
retrieves contents by accessing the information server based on the specified
address information and returns them to the terminal.
processing procedures.

10

Figure 3 shows the

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Terminal

Gateway(Retaining the cache)ucode<2>──────→←──────<5>Contents↑<1>││└┘
ucode resolution
Contents↑<3>││Acquisition request
││
││
││
<4>↓

Information server<1> The terminal executes ucode resolution with the cache search function.
<2> The terminal sends the corresponding address information on the information
server to the Gateway.
<3> The Gateway sends a contents acquisition request to the specified information
server.
<4> The contents are returned.
<5> The Gateway returns the contents to the terminal.

Figure 3: Gateway Operation (With a Cache Hit on the Terminal)

11

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

4. ucode Resolution Gateway Protocol
4.1. Outline
This chapter defines the ucode resolution gateway protocol which is aninterface for sending requests/receiving responses between terminals and the
Gateway.
The ucode resolution gateway protocol is an application protocol which
operates on HTTP (Hypertext Transfer Protocol) [5]. The HTTP header field,
body field, and request URL are used for sending/receiving parameters, sothat existing network resources for cellular phones and intranets, etc. andterminal software are usable.

4.2. Parameter Definition
4.2.1. Request Parameters
Terminals send the following three parameters to the Gateway as HTTP
requests.
z

Gateway parameter
The Gateway parameter is defined as a parameter which directs Gateway

operations.

It is not forwarded to the ucode resolution server and information

server.
z

ucode resolution parameter
The ucode resolution parameter is defined as a parameter for the ucode

resolution protocol. It is forwarded to the ucode resolution server but not to
the information server.
z

Information server parameter
The information server parameter is defined as an application parameter

which is forwarded to the information server but not to the ucode resolution
server.
This document specifies Gateway parameters and ucode resolution
parameters only.

Table 1 shows the request parameter List, and Table 2

shows the request parameter value List.

12

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table 1: Request Parameter List
Type
Gateway
parameter

ucode
resolution
parameterSignatureverification

Parameter name
X-UIDC-GWMODEX-UIDC-TERMTYPE
X-UIDC-GWREQIF
X-UIDC-GWRESIF

Meaning
Gateway operation mode
Terminal typeSpecification for the request-sending method
Specification for the response-receiving
methodX-UIDC-GWCACHE
Storage/no storage of the cache for resolution
results
X-UIDC-UCODE
ucode to be searched
X-UIDC-QUERYMASKQuery bitmask of the ucode to be searched
X-UIDC-UCODETYPE
Bit length type of the ucode
X-UIDC-QUERYMODE
Search mode for the ucode resolution
X-UIDC-QUERYATTRIBUTE Data attribute to be retrieved by the ucode
resolution
X-UIDC-SIGNATURE
Signature data
X-UIDC-ALGORITHM

13

Algorithm type used for signature verification

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table 2: Request Parameter Value List
Parameter name
X-UIDC-GWMODEX-UIDC-TERMTYPE
X-UIDC-GWREQIF

X-UIDC-GWRESIF
X-UIDC-GWCACHE

X-UIDC-UCODEX-UIDC-QUERYMASKX-UIDC-UCODETYPEX-UIDC-QUERYMODE(List values by
separating with ","(comma))X-UIDC-QUERYATTRIBUTE

X-UIDC-SIGNATURE
X-UIDC-ALGORITHM

Value"recursive"

Meaning
ucode resolution andcontents acquisition"resolveall"ucode resolution only (allhierarchies)"resolve"
ucode resolution only (onehierarchy only)"redirect"
ucode resolution and an
HTTP redirect"portal"ucode resolution and aportal display"proxy"Contents acquisition only
"default"
Do not convert.
"http-header"
Send by a header.
"http-get"Send by a GET parameter.
"http-post"
Send by a POST
parameter.
"http-header"
Receive by a header.
"http-body"Receive by a body.
"cache"Store the query result in
the cache.
"no-cache"
Do not store the query inthe cache.
<ucode string>ucode to be resolved<ucode string>ucode query maskbit"UIDC_DATATYPE_UCODE_128" 128bit ucode type
"UIDC_DATATYPE_UCODE_256" 256bit ucode type
"UIDC_DATATYPE_ UCODE_384" 384bit ucode type
"UIDC_DATATYPE_ UCODE_512" 512bit ucode type
"UIDC_RSMODE_RESOLUTION" A normal ucode resolution
search"UIDC_RSMODE_CACHE"
Use cache resolution"UIDC_RSMODE_CASCADE"
Use cascade resolution.
"UIDC_ATTR_ANONYMOUS"
Do not specify a node
type.
"UIDC_ATTR_RS"
Specify the ucode
resolution server.
"UIDC_ATTR_IS"
Specify the information
server.
"UIDC_ATTR_USER"
Specify user-defined
information.
<sign string>
Signature string<algo type>
Algorithm used forsignature verification

14

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04<ucode string> ::= 32HEXDIG※1 ; ex. 0efffec0000000000000000000050123<sign string> ::= 40HEXDIG ; ex. 6455FDB217CFE086953A844DABAC0491B05D91D2<host string> ::= host [":" port]; ex. 192.168.0.1:8081
DIGIT = "0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"HEXDIG = DIGIT|"A"|"B"|"C"|"D"|"E"|"F"|"a"|"b"|"c"|"d"|"e"|"f"<algo type> = <mac type> | " PBEWith" <mac type><mac type> = "HmacMD5"|"HmacSHA1"|"HmacSHA256"|"HmacSHA384"|"HmacSHA512"※1 : n<element> represents that a same element is repeated for a given integral numberof times (n).

Default values are set for each parameter.

If the specification of eachparameter is omitted, each default value is automatically set.

Table 3 shows

the request parameter default value list.
Table 3: Request Parameter Default Value List
Parameter name
X-UIDC-GWMODEX-UIDC-TERMTYPE
X-UIDC-GWREQIF

Default value (Interpretation if the setting is omitted)"redirect""default"
For the GET method: "http-get"
For the POST method: "http-post"
For the methods other than the two above: "http-header"
X-UIDC-GWRESIF
If X-UIDC-GWREQIF is http-header: "http-header"
If X-UIDC-GWREQIF is http-get/http-post: "http-body"
X-UIDC-GWCACHE"cache"X-UIDC-UCODE(Cannot be omitted)
X-UIDC-QUERYMASK ffffffffffffffffffffffffffffffff
X-UIDC-UCODETYPE UIDC_DATATYPE_UCODE_128
X-UIDC-QUERYMODE UIDC_RSMODE_RESOLUTION
X-UIDC-QUERYATTRIB UIDC_ATTR_ANONYMOUSUTE
X-UIDC-SIGNATURE
If omitted, the signature verification function is disabled. To
enable signature verification, it cannot be omitted.

Among the those in the list, the X-UIDC-UCODE setting cannot be omitted.
If it is omitted, a parameter error will be returned.
All parameters other than those shown in Table 1 are interpreted as
information server parameters.

4.2.2. Response Parameter
HTTP responses which are returned by the Gateway to terminals include
the following three types of data.
(1)

Gateway status
The Gateway status is defined as a parameter for Gateway operation

15

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

results.
(2)

ucode resolution status
The ucode resolution status is defined as a parameter for ucode
resolution protocol operation results.

The status from the ucode

resolution server is forwarded without any changes.
(3)

Information server status
The information server status is defined as a parameter for
information server operation results. The status from the information
server is forwarded without any changes.

(4)

Contents
The contents in this document are defined as contents associated withthe ucode specified by requests. The contents retrieved from theinformation server are forwarded without any changes.

This document specifies (1) and (2) only.

Table 4 shows the response

parameter list, and Table 5 shows the response parameter value list.
Table 4: Response Parameter List
Remarks
Gateway
statusucode
resolution
statusParameter name
X-UIDC-GWSTATUS

Meaning
Gateway status

X-UIDC-UCODERP-STATUS

ucode resolution protocol status at thetime of ucode resolution

X-UIDC-DATA
X-UIDC-DATAVERSION

Data retrieved from ucode resolution
Data version retrieved from ucode
resolution
Data attribute retrieved from ucode
resolution
Data type retrieved from ucode
resolution
Bitmask retrieved from ucode
resolution
Expiration date of data retrieved fromucode resolution
Mode executed at the time of ucode
resolution

X-UIDC-DATAATTRIBUTE
X-UIDC-DATATYPE
X-UIDC-RETURNMASKX-UIDC-TTL
X-UIDC-RESOLVEMODE

16

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table 5: Response Parameter Value List
Parameter name
X-UIDC-GWSTATUS

Value<2byte string>
0x00000x00010xffef0xffdf0xfdffMeaning

0xfdfeX-UIDC-UCODERP-STATUS

0xfdfd
0xfdfc0xfffb
<2byte string>

X-UIDC-DATA<data string>

X-UIDC-DATAVERSION<2byte string>

X-UIDC-DATAATTRIBUTE"UIDC_ATTR_RS""UIDC_ATTR_IS""UIDC_ATTR_USER"
X-UIDC-DATATYPE

X-UIDC-RETURNMASK"UIDC_DATATYPE_UCODE_128""UIDC_DATATYPE_UCODE_256""UIDC_DATATYPE_UCODE_384""UIDC_DATATYPE_UCODE_512""UIDC_DATATYPE_IPV4""UIDC_DATATYPE_IPV6""UIDC_DATATYPE_URL""UIDC_DATATYPE_HOST""UIDC_DATATYPE_EMAIL""UIDC_DATATYPE_PHONE""UIDC_DATATYPE_TXT""UIDC_DATATYPE_USER"<ucode string>

X-UIDC-TTL<4byte string>

X-UIDC-RESOLVEMODE"UIDC_RSMODE_RESOLUTION""UIDC_RSMODE_CACHE""UIDC_RSMODE_CASCADE"

17

Normal termination
Conditional normal termination
Request for unsupported function
Parameter error
Connection to the ucode resolution
server failed
Connection to an information server
failedUnsupported protocol
Signature verification error
System error
ucode resolution protocol status
code (see [2].)Data attribute of the ucode
resolution protocol response
dataVersion attribute of the ucode
resolution protocol response
dataAttribute attribute of the ucode
resolution protocol response
ucode resolution server
Information server
User-defined attribute
dataType attribute of the ucode
resolution protocol response
128bit ucode
256bit ucode384bit ucode
512bit ucode
IPv4 address
IPv6 address
URL
Host namee-mail address
Phone number
Text information
User-defined
returnMask attribute of the ucode
resolution protocol response
ttl attribute of the ucode resolution
protocol response
resolveMode attribute of the ucode
resolution protocol response
Executed a normal ucode resolution
searchExecuted cache resolution
Executed cascade resolution

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04<2byte string> ::= ("0" ("x"|"X") 1*4HEXDIG※1) | 1*5DIGIT ; ex. 0x1234<4byte string> ::= ("0" ("x"|"X") 1*8HEXDIG) | 1*10DIGIT ; ex. 0x12345678<data string> ::= <ucode string> | ; for UIDC_DATATYPE_UCODE_*<IPv4 address in dot decimal notation※2> | ; for UIDC_DATATYPE_IPV4<IPv6 address in string notation※3> | ; for UIDC_DATATYPE_IPV6<URI in string notation※4> | ; for UIDC_DATATYPE_URL<host in string notation※5> | ; for UIDC_DATATYPE_HOST*CHAR; for other types
CHAR = <US-ASCII characters>※1 : n*m<element> represents that a same element is repeated for n times or more andm times.or more
※2 : 4 decimal notation separated with dots (for example, aaa.bbb.ccc.ddd)※3 : Refer to [6].
※4 : Refer to [7].
※5 : Refer to [8]Among the above response parameters, the Gateway must return at least
the "X-UIDC-GWSTATUS" (Gateway status code) parameter.

Table 6 lists

possible values retrieved as "X-UIDC-GWSTATUS" and their meanings.
Other parameters can be omitted according to the provided Gateway
functions.
Table 6: Gateway Status Code List
Status0x00000x0001

Meaning
Normal termination
Conditional normal
termination

0xffefRequest for
unsupported
function
Parameter error

0xffdf0xfdff0xfdfe0xfdfd
0xfdfc0xfffbConnection toucode Resolution
Server failed
Connection to
information server
failedUnsupported
protocolSignatureverification error
System error

Condition
Completed a request
Normally terminated as a Gateway function but did notcomplete a request. It means that an abnormal
termination occurs in the ucode resolution status orinformation server status; therefore, each status should
be interpreted.
Requested a Gateway function which has been definedin the specification but not implemented.
Specified a Gateway parameter value which has notbeen defined in specification, or a parameter to be
specified has not been specified.
Connection to the ucode resolution server failed.

Connection to the information server failed.

URL scheme retrieved from ucode resolution was not a
supported protocol.
Specified signature was verified, and an error was
detected.
Any error other than the above occurred within the
Gateway.

18

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

4.3. Gateway Operation Mode
4.3.1. Recursive ModeIf “recursive” is specified in the "X-UIDC-GWMODE," the Gateway executes
ucode resolution and a contents acquisition for the ucode specified by arequest.

The ucode resolution may be performed in multiple phases.

Regarding the access protocol for the information server, the Gateway makes
a judgment based on the ucode resolution information.

For example, theaccess protocol is determined based on the URL scheme (for example, "http,""ftp," etc.).
Shown below is the Gateway processing procedures in case of the recursivemode.
(1) If UIDC_RSMODE_CACHE is specified in "X-UIDC-QUERYMODE," itchecks if there is a cache.

If a cache exists, it skips (2) and (3).

(2) It makes a query to the ucode resolution server and performs ucode
resolution.
(3) If a cache is specified in "X-UIDC-GWCACHE," the ucode resolution
information is cached.
(4) Steps (2) and (3) are repeated until the information server address isretrieved.
(5) The information server is accessed, and contents are retrieved.
(6) The ucode resolution information and contents are returned to the request
source.

4.3.2. Resolveall ModeIf “resolveall” is specified in "X-UIDC-GWMODE," the Gateway performs
ucode resolution and retrieves location information on the information server
for the ucode specified by a request.

The ucode resolution may be

performed in multiple phases.
Shown below is the Gateway processing procedures in case of theresolveall mode.
(1) If

UIDC_RSMODE_CACHE

isspecifiedin"X-UIDC-QUERYMODE," it checks if there is a cache. If acache exists, it skips (2) and (3).
(2) It makes a query to the ucode resolution server and executes
ucode resolution.
19

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04(3) If a cache is specified in "X-UIDC-GWCACHE," the ucode
resolution information is cached.
(4) Steps (2) and (3) are repeated until the information server
address is retrieved.
(5) The ucode resolution information is returned to the request
source.

4.3.3. Resolve ModeIf “resolve” is specified in "X-UIDC-GWMODE," the Gateway performs
ucode resolution for the ucode specified by a request. If the ucode resolution
has a multiple phase structure, the Gateway performs ucode resolution for the
first phase only.
Shown below is the Gateway processing procedures in case of the resolvemode.
(1) If UIDC_RSMODE_CACHE is specified in "X-UIDC-QUERYMODE," itchecks if there is a cache. If a cache exists, it skips (2) and (3).
(2) It makes a query to the ucode resolution server and executes ucode
resolution.
(3) If a cache is specified in "X-UIDC-GWCACHE," the ucode resolution
information is cached.
(4) The ucode resolution information is returned to the request source.

4.3.4. Redirect ModeIf “redirect” is specified in "X-UIDC-GWMODE", the Gateway performs
ucode resolution and retrieves location information on the information server
for the ucode specified by a request.
redirect for the retrieved URL.
multiple phases.

In addition, the Gateway performs httpThe ucode resolution may be performed in

In the http redirect, the client must read the URL by

rewriting the http header location.

4.3.5. Portal ModeIf “redirect” is specified in "X-UIDC-GWMODE," the Gateway executes
ucode resolution and retrieves location information on the information server
for the ucode specified by a request.

Additionally, html pages including

anchors to the retrieved URL are structured and returned to the client.

20

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

4.4. Method of Sending/Receiving Parameters4.4.1. Method of Sending Request Parameters
This document specifies the following three methods of sending request
parameters to the Gateway.
(1) Request header method
Request parameters are described in the HTTP request header.

All

header fields other than the Gateway/ucode resolution parameters areforwarded to the information server without any changes.
(2) GET parameter method
Request parameters are described in the HTTP request URL.

All GETparameters other than the Gateway/ucode resolution parameters areforwarded to the information server without any changes.
(3) POST parameter method
Request parameters are described in the HTTP request body.

All POSTparameters other than the Gateway/ucode resolution parameters areforwarded to the information server without any changes.
Terminals can specify the method of sending parameters by using the"X-UIDC-GWREQIF" parameter.

The "X-UIDC-GWREQIF" parameter itself

must be sent using the request header method. The Gateway interprets the"X-UIDC-GWREQIF" parameter value in the request header and receives theremaining parameters according to the specified method.
However, request headers cannot be freely set in some existing cellular
phones; therefore, "X-UIDC-GWREQIF" may not be sent using the request
header method.

In case of these terminals, the method of sending

parameters is automatically judged based on the HTTP request method.

For

example, if the GET method is requested, it will be judged that parameters aresent using the GET parameter method.
Table 7 shows the criteria for the method of sending request parameters at
the Gateway.

21

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table 7: Criteria of the Method of Sending Request Parameters

http-header
http-get

HTTP
requestmethodAnyAny

http-post

Any

None

GET

None

POST

None

OthersX-UIDC-GWREQIF
value
X-UIDC-GWREQIF
is specified in therequest header
X-UIDC-GWREQIF
is not specified in
the request header

Method of Sending
Parameters
Request header method
GET parameter method
POST parameter
methodGET parameter method
POST parameter
methodRequest header method

Next, Table 8 shows an example of HTTP payload descriptions whenparameters are sent using each method.
Table 8: Example of HTTP Payload Descriptions (Request)
MethodRequestheadermethodGETparameter
methodPOSTparameter
methodHTTP Payload
GET /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF: http-header
X-UIDC-UCODE: 0efffec0000000000000000000050123
GET/resolve.cgi?X-UIDC-UCODE=0efffec0000000000000000000050123(Æcontinued) HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF: http-get// can be omitted
POST /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF: http-post// can be omitted(Blank line)
X-UIDC-UCODE=0efffec0000000000000000000050123(described minimum headers only.)

4.4.2. Method of Receiving Response Parameters
This document specifies the following two methods of receiving response
parameters from the Gateway.
(1) Response header method
Response parameters are described in the HTTP response header.

(2) Response body method
Response parameters are described in the HTTP response body.
Terminals can specify the method of receiving parameters by using the"X-UIDC-GWRESIF" parameter.

The "X-UIDC-GWRESIF" parameter as wellas other parameters is sent to the Gateway using the method specified by the22

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04"X-UIDC-GWREQIF" parameter.
However, in the response body method, both response parameters andcontents can not be received simultaneously.

When "http-body" is specified

as the "X-UIDC-GWRESIF" parameter in a request, and when contents are
returned, the response parameter is omitted, and only the contents are
returned.

When it is requested to receive both contents and response

parameters, it is required to specify "http-header" as the "X-UIDC-GWRESIF"
request parameter and to receive the response parameter using the response
header method.
Table 9 shows an example of HTTP payload descriptions when parameters
are received by each method.
Table 9: Example of HTTP Payload Descriptions (Response)
MethodResponse header method

Response body method

HTTP Payload
200 OK
Host: gw.uidcenter.org
X-UIDC-GWSTATUS: 0x0000
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: http://www.uidcenter.org/getinfo.cgi...
(Blank line)--Contents
200 OK
Host: gw.uidcenter.org...
(Blank line)
X-UIDC-GWSTATUS: 0x0000
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: http://www.uidcenter.org/getinfo.cgi

4.4.3. HTTP Parameter(1) HTTP response status code
Returned HTTP payloads include HTTP status codes.

Table 10 shows

possible HTTP status codes returned from the Gateway and the Gateway
conditions at that time.

23

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Table 10: HTTP Status Code List
Status code
200

Meaning
Normal termination
Gateway error
ucode resolution error

Other than thoseabove

GatewayHTTP error(When
X-UIDC-GWSTATUS does
not exist)
Information server error(When
X-UIDC-GWSTATUS
exists)Condition
Completed request
X-UIDC-GWSTATUS value is otherthan 0x0000/0x0001.
X-UIDC-UCODERP-STATUS value
is other than 0x0000.
Indicates an HTTP layer error which
occurred while accessing the
Gateway
Indicates an HTTP layer error which
occurred while accessing theinformation server(2) HTTP header field
All HTTP header fields in a request are forwarded to the information server
except for the Gateway/ucode resolution parameter.

In addition, all header

fields in a response from the information server are forwarded to the terminal.
However, if the header shown in Table 11 is included, the Gateway should
rewrite the headers as an exception to the appropriate value.
Table 11: Header Fields required to be rewritten
Header nameContent-Length

Setting method
Since the Gateway/ucode resolution parameter
is not forwarded to the information server, if theparameter is included in the body field, theGateway rewrites the size of the entity-body
excluding the Gateway/ucode resolution
parameter.

Request4.5. Cache
When the same request is received more than once, the Gateway can
execute a high-speed processing without making a re-query to the ucode
resolution server by locally caching ucode resolution information.

However,the cache resolution can be performed only for the requests where cache
resolution is permitted.

4.5.1. Cache Method
When the Gateway receives a request where cache resolution is permitted
from the terminal, it searches cache records held inside based on the request
parameter.

The cache records are collections of records with the attributes
24

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

shown in Table 12.
Table 12: The List of Attributes included in Cache Records
Attribute
ucode
ucodemask
data
ttl
resolvemodedataversion
dataattributedatatype

Description
ucode indicated by the record
Bit mask indicating effective bits in ucodes
Location information corresponding to ucodes
Expiration date of the cache (seconds)
Search mode used when the cache data is searched
Cache information version
Location information feature indicated by the data
Data representation type

The cache record is a record keyed by the ucode & ucodemask (bitwise
logical AND) group.

A cache information search is executed by the same

method as an entry search method in the ucode resolution server which is
specified in the ucode resolution protocol.
However, this document does not specify the behavior executed by the
Gateway when multiple cache records are matched during a search.
There are following two types of Gateway cache retention.
(1) Dynamic cache
The Gateway can dynamically cache ucode resolution request results to theucode resolution server.

At this time, each field value included in the ucode

resolution protocol response is stored as cache information as shown in Table
12.
(2) Static cache
The Gateway can have static cache information set offline.

The staticcache information is often set up in advance by an administrator.

4.5.2. TTLThe Gateway must not use a cache that is beyond the expiration date in a
TTL attribute included in a cache record.

As an implementing method forchecking the effective period, it is considered possible to check if thedifference between the cache storage time and the current time exceeds the
TTL when using a cache or subtract a TTL value within a record in real time.
However, ucode resolution information cannot be cached if its TTL value is 0.
In addition, ucode resolution information does not have the cache retention
25

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

period if its TTL is 0xFFFFFFFF(-1).

4.6. Contents Conversion
Terminals can direct the Gateway to convert contents using the"X-UIDC-TERMTYPE" parameter.

However, in the current version, only "Noconversion (X-UIDC-TERMTYPE is set to default)" is defined (for future
extension).

4.7. Operation Example(1-a) Request header method/recursive mode (normal system)
In case of the request header method and recursive mode, an example ofthe normal system flow is shown below.

The terminal receives ucode

resolution information in the response header and contents in the response
body.

26

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Terminal

Gatewayucode<1>──────→←──────<6>Contents

ucode resolution server
ucode<2>──────→←──────<3>ucode resolution
information↑<4>││Acquisition request││││
Contents││<5>↓

Information server
Number
<1>

<2>

<3>

<4>

<5>

<6>

Parameter
GET /resolve.cgi?ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE : 0efffec0000000000000000000050123
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = http://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
GET /getinfo.cgi?ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: www.uidcenter.org
HTTP/1.1 200 OK...
(Blank line)<<Contents>>
HTTP/1.1 200 OK
X-UIDC-GWSTATUS: 0x0000
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: http://www.uidcenter.org/getinfo.cgi...
(Blank line)<<Contents>>
Figure 4: Parameter Example When a Header Field is Used(1-b) POST parameter method/recursive mode (normal system)
In case of the POST parameter method and recursive mode, an example ofthe normal system flow is shown below.
27

Since the terminal receives contents

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

in the response body, it cannot receive ucode resolution information.
Terminal

Gatewayucode<1>──────→←──────<6>Contents

ucode resolution server
ucode<2>──────→←──────<3>ucode resolution
information↑<4>││Acquisition request││││
Contents ││<5>↓

Information server
Number
<1>

<2>

<3>

<4>

<5>

<6>

Parameter
POST /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org...
(Blank line)
X-UIDC-UCODE=0efffec0000000000000000000050123&(ÆContinued) ucode=0efffec0000000000000000000050123&param=1
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = http://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
POST /getinfo.cgi HTTP/1.1
Host: www.uidcenter.org(Blank line)
ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1 200 OK...
(Blank line)<<Contents>>
HTTP/1.1 200 OK...
(Blank line)<<Contents>>
Figure 5: Parameter Example when a POST Method is Used(1-c) GET parameter method/recursive mode (normal system)
28

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

In case of the GET parameter method and recursive mode, an example ofthe normal system flow is shown below.

Since the terminal receives contents

in the response body, it cannot receive ucode resolution information.
Terminal

Gatewayucode<1>──────→←──────<6>Contents

ucode resolution server
ucode<2>──────→←──────<3>ucode resolution
information↑<4>││Acquisition request││││
Contents ││<5>↓

Information server
Number
<1>

<2>

<3>

<4>

<5>

<6>

Parameter
GET /resolve.cgi?X-UIDC-UCODE=0efffec0000000000000000000050123&(ÆContinued) ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: gw.uidcenter.org...
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = http://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
GET /getinfo.cgi?ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: www.uidcenter.org
HTTP/1.1 200 OK...
(Blank line)<<Contents>>
HTTP/1.1 200 OK...
(Blank line)<<Contents>>
Figure 6: Parameter Example when a GET Method is Used29

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04(1-d) Request header method/resolveall mode (normal system)
In case of the request header method and resolveall mode, an example ofthe normal system flow is shown below.

The terminal receives ucode

resolution information in the response header and does not receive contents.
Terminal

Gatewayucode<1>──────→←──────<4>ucode resolution
information

Number
<1>

<2>

<3>

<4>

ucode resolution server
ucode<2>──────→←──────<3>ucode resolution
information

Parameter
GET /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWMODE : resolveall
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE=0efffec0000000000000000000050123...
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = http://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
HTTP/1.1 200 OK
X-UIDC-GWSTATUS: 0x0000
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: http://www.uidcenter.org/getinfo.cgi...
Figure 7: Parameter Example in the resolveall mode(1-e) Request header method/resolve mode (normal system)
In case of the request header method and resolve mode, an example of thenormal system flow is shown below.

The terminal receives ucode resolution

information in a response header, and its ucode resolution information is only
based on a resolution result of the first phase.

The terminal does not receive

contents.
Terminal

Gateway30

ucode resolution server

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

ucode<1>──────→←──────<4>ucode resolution
information
Number
<1>

<2>

<3>

<4>

ucode
<2>──────→←──────<3>ucode resolution
information

Parameter
GET /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWMODE : resolve
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE=0efffec0000000000000000000050123...
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = 0xC0A80001// Binary format of 192.168.0.1
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_RS
dataType = UIDC_DATATYPE_IPV4
HTTP/1.1 200 OK
X-UIDC-GWSTATUS: 0x0000
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: 192.168.0.1...

Figure 8: Parameter Example in the resolve Mode(2-a) Request header method/recursive mode (abnormal system)
In case of the request header method and recursive mode, shown below is
an example of the abnormal system flow used when the ucode resolution
server fails in ucode resolution

Terminal

Gateway31

ucode resolution server

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

ucode<1>──────→←──────<4>Error status
Number
<1>

<2>

<3>
<4>

ucode
<2>──────→←──────<3>
Error status

Parameter
GET /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE=0efffec0000000000000000000050123...
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
ErrorCode = 0xffcc// ucode Resolution Protocol status code
HTTP/1.1 200 OK
X-UIDC-GWSTATUS: 0x0001
X-UIDC-UCODERP-STATUS: 0xffcc...
Figure 9: Parameter Example in case the ucode Resolution Fails(2-b) Request header method/recursive mode (abnormal system)
In case of the request header method and recursive mode, shown below is
an example of the abnormal system flow used when the information server
returns an error.

32

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Terminal

Gatewayucode<1>──────→←──────<6>Error status

Error statusucode Resolution Server
ucode<2>──────→←──────<3>ucode resolution
information↑<4>││Acquisition request
││
││
││
<5>↓

Information server
Number
<1>

<2>

<3>

<4>

<5>
<6>

Parameter
GET /resolve.cgi?ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE : 0efffec0000000000000000000050123
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = http://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
GET /getinfo.cgi?ucode=0efffec0000000000000000000050123&param=1
HTTP/1.1
Host: www.uidcenter.org
HTTP/1.1 404 Not Found...
HTTP/1.1 404 Not FoundX-UIDC-GWSTATUS: 0x0001
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: http://www.uidcenter.org/getinfo.cgi...

Figure 10: Parameter Example when the Information Server Returns an Error(2-c) Request header method/recursive mode (abnormal system)
In case of the request header method and recursive mode, shown below is
an example of the abnormal system flow used when the information server is
not accessed by the http protocol method which is not supported by the
Gateway.
33

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Terminal

Gatewayucode<1>──────→←──────<4>ucode resolution
information

Number
<1>

<2>

<3>

<4>

ucode Resolution Server
ucode<2>──────→←──────<3>ucode resolution
information

Parameter
GET /resolve.cgi HTTP/1.1
Host: gw.uidcenter.org
X-UIDC-GWREQIF : http-header
X-UIDC-UCODE=0efffec0000000000000000000050123...
ucode = 0efffec0000000000000000000050123
queryMask = ffffffffffffffffffffffffffffffff // Default value applied
ucodeType = UIDC_DATATYPE_UCODE_128// Default value applied
queryMode = UIDC_RSMODE_RESOLUTION// Default value applied
queryAttribute = UIDC_ATTR_ANONYMOUS// Default value applied
data = https://www.uidcenter.org/getinfo.cgi
returnMask = ffffffffffffffffffffffffffff0000
TTL = 86400
dataVersion = 0x0001
resolveMode = UIDC_RSMODE_RESOLUTION
dataAttribute = UIDC_ATTR_IS
dataType = UIDC_DATATYPE_URL
HTTP/1.1 200 OK
X-UIDC-GWSTATUS: 0xfdfd
X-UIDC-UCODERP-STATUS: 0x0000
X-UIDC-DATA: https://www.uidcenter.org/getinfo.cgi...
Figure 11: Parameter Example when used an Unsupported Protocol

34

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

Index
Ｃ

Ｐ

Cache ........................................................................................... 7

POST parameter method ..............................................21contents ...................................................................................16

Portal mode.............................................................................20

Contents conversion............................................................. 7Ｑ
Ｄ
QR Code ................................................................................... 7
Dynamic cache ....................................................................25

Ｒ
Ｇ
Request header method.................................................21
ucode resolution gateway protocol ............................ 6

Recursive mode.....................................................................19

Gateway parameter ..........................................................12

Redirect mode........................................................................20

Gateway status....................................................................15

Resolve mode .........................................................................20

GET parameter method..................................................21

Resolveall mode.....................................................................19Ｈ

Ｓ

HTTP (Hypertext Transfer Protocol)........................12Signature verification............................................................ 7
Static cache ...........................................................................25

Ｉ
Ｕ
Information server parameter......................................12
Information server status ...............................................16

ucode resolution parameter .........................................12

information server ................................................................ 6

ucode resolution status...................................................16
ucode resolution gateway ............................................... 6
ucode resolution server .................................................... 6Ｏucode resolution information ......................................... 6
ucode resolution database.............................................. 6

Operation mode ....................................................................... 835

T-Engine Forum
Ubiquitous ID Center Specification

910-S204-1.A0.04/UID-CO00007-01.A0.04

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