Unique identification for all objects

The most fundamental element for ubiquitous ID technology is the unique ubiquitous identification code (ucode) assigned to real-world objects in a format easily read by computers. This enables computers to automatically recognize real-world objects for processing guided by an awareness of the context.

There are currently many different code systems applied to objects at work in the distribution sector and other fields. For example, JAN codes, EAN codes, and UPC codes are used in barcodes, while ISBN codes are used for books and other publications. (The abbreviations stand for Japanese Article Number, European Article Number, Universal Product Code, and International Standard Bibliographic Number, respectively.) These codes are assigned to types of products, so the ISBN assigned to a book “Botchan” cannot be used to distinguish individual books within this category. In contrast, the ucode system is fundamentally a means of identification for individual objects. This system provides a way to identify each book “Botchan” stacked flat in a bookstore or each bottle of wine in a liquor store with individual ucodes. The unique codes assigned to each object can be especially significant for items such as food or medicine with distinctive characteristics and expiration dates. It can also be used as the basis for information services.

ucode: 128 bits long

As a code, the ucode is 128 bits long and can be extended as needed in 128-bit units to 256, 384, or 512 bits. With 128-bit numbers, 340,000,000,000,000,000,000,000,000,000,000,000,000 codes can be assigned.

Compatible with existing codes

The greatest advantage of ucode is its status as a meta-code system that can encompass various existing identification codes. And the very generous 128-bit capacity of ucode means it can accommodate many of these different numbers and identifications: from JAN, UPC, and EAN barcodes to ISBN and ISSN publication IDs, and from IP addresses assigned by hosts for Internet connections to the telephone number assigned to your phone. Let's see how the ucode system supports and accommodates the JAN code in this example.

The JAN code specifies a few different code lengths, but the standard code is a 13-digit decimal. Expressing each digit of the decimal with four bits, we can express the entire JAN code with 52 bits. In this case the 128 bits would be assigned as follows:

*Note that this is only an example given for purposes of explanation, not part of a finalized specification.

64-127: 64 bits, unique ID
The JAN code is a number assigned to types of products, and the unique ID segment stores a distinctive identification assigned to each identical product. In this example, 64 bits are available for the unique ID, so for each type of product 18,446,744,073,709,551,616 individual and unique product IDs can be assigned.

To uphold this kind of code compatibility, the Ubiquitous ID Center would assign the first 11-bit segment from 0-11 for the code identifier through the organization issuing the JAN code (in this case, the JAN code would be assigned by the Distribution Systems Research Institute). The authority for assigning the next 116-bit segment corresponding to the ucode would be entrusted to that organization. The Distribution Systems Research Institute would assign the 52-bit segment from 12-63 for the JAN code and the organization receiving the JAN code assignment from the Distribution Systems Research Institute would assign the 64-bit segment from 64-127 for unique and individual identification.

This model for entrusting assignment authority resembles the model for assigning IP addresses on the Internet because it is a process of gradual assignment. Thus, it is not a matter of the Ubiquitous ID Center being the central authority for assigning all individual product IDs worldwide.