ISO/IEC TR 29162:2012

TECHNICAL ISO/IEC
REPORT TR
First edition
2012-07-15
Information technology — Guidelines for
using data structures in AIDC media
Technologies de l'information — Directives pour l'usage des structures
de données dans des medias d'AIDC

Reference number
©
ISO/IEC 2012
©  ISO/IEC 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved

Contents Page
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 1
5 Standards applied to data encoding for AIDC media . 2
6 ISO/IEC 15434 application for high capacity AIDC media . 3
6.1 Assigned formats in ISO/IEC 15434 . 4
6.2 System data elements for compatibility across all AIDC media . 5
6.3 Data Carrier Identifiers for RFID and other AIDC media . 5
7 RFID encoding of UII . 6
7.1 Extant numbering systems for RFID . 6
7.2 Tag type and UII data storage area . 7
7.3 ISO/IEC 18000-63, Type C and 18000-3m3 ASK and EPCglobal memory architecture . 8
7.4 Unique Identifier of a physical object (UII) . 9
7.5 Data construct . 11
7.6 Encoding of Memory Bank “01” Unique Item Identifier . 11
8 RFID encoding of user data . 14
8.1 No directory . 14
8.2 Directory. 14
8.3 Packed Object . 14
8.4 Tag Data Profile . 15
9 RFID ISO/IEC 15434 direct encoding of user data . 15
10 Storing data in various types of RF tags . 15
11 Methods to store UII data in RFID memory and other AIDC media . 16
Bibliography . 31

© ISO/IEC 2012 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
In exceptional circumstances, when the joint technical committee has collected data of a different kind from
that which is normally published as an International Standard (“state of the art”, for example), it may decide to
publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review
every five years in the same manner as an International Standard.
Attention is drawn to the possibility that some of the elements of this Technical Report may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC TR 29162 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.

iv © ISO/IEC 2012 – All rights reserved

Introduction
Radio frequency identification (RFID) is one of the AIDC media widely used in the market place. Linear bar
codes and two-dimensional symbols have long utilized AIDC media. The international standard for AIDC
syntax is ISO/IEC 15434. ISO/IEC 15961 and ISO/IEC 15962 were developed as encoding rules for RFID.
Users have long utilized linear bar codes and two-dimensional symbols for item identification and numerous
RFID technologies have recently been developed. Users who want to utilize RFID transponders should
consider compatibility with linear bar codes and two-dimensional symbols already in the system. Because of
the growing diversity and complexity of AIDC media in the market place, especially in RFID, it is not easy for
users to understand how to read and write their data to each application of AIDC media.
This Technical Report explains common data structures used in both optically readable media (linear bar
codes and two-dimensional symbols) and radio-frequency identification. It primarily addresses the use of ASC
MH10 Data Identifiers to provide the semantics, ISO/IEC 15434 to provide the syntax, and ISO techniques of
unique item identification with ISO/IEC 15961 Application Family Identifiers (AFIs) and encoding rules for
RFID using ISO/IEC 15962.
Those interested in applications using Air Transport Association (ATA) SPEC 2000, Text Element Identifiers,
are encouraged to contact the ATA for specific guidance.
Those interested in applications using GS1 Application Identifiers and EPC, specifically for material found in
the EPC Tag Data Standard (TDS), are encouraged to contact GS1 for specific guidance.

© ISO/IEC 2012 – All rights reserved v

TECHNICAL REPORT ISO/IEC TR 29162:2012(E)

Information technology — Guidelines for using data structures
in AIDC media
1 Scope
This Technical Report provides guidance on the use of AIDC media (e.g. linear bar codes, two-dimensional
symbols, RFID transponders) in the supply chain.
2 Normative references
The following referenced documents are indispensable for the application of this Technical Report. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 19762 (all parts), Information technology — Automatic identification and data capture (AIDC)
techniques — Harmonized vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 (all parts) apply.
4 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO/IEC 19762 (all parts) and the following
apply.
AFI Application Family Identifier
AI Application Identification
AIDC Automatic Identification and Data Capture
CIN Company Identification Number
DI Data Identifier
DSFID Data Storage Format Identifier
ECI Extended Channel Interpretations
EPC Electronic Product Code
IAC Issuing Agency Code
IATA International Air Transport Association
© ISO/IEC 2012 – All rights reserved 1

IEP Inter-sector Electronic Purse
ISBT International Association of Blood Transfusion services
OID Object Identifier
PC Protocol Control (bits)
RFID Radio Frequency Identification
SN Serial Number
TEI Text Element Identifier
TID Tag identification
UII Unique Item Identifier
UML Unified Modeling Language
UPU Universal Postal Union
VIN Vehicle Identification Number
XPC Extended PC (bits)
5 Standards applied to data encoding for AIDC media
AIDC media in various forms are transported and/or stored, together with goods or items.
ISO/IEC 15434 was developed as a syntax for high capacity AIDC media and applied to many kinds of two-
dimensional symbols.
ISO/IEC 15961 and ISO/IEC 15962 were developed for RFID air interface standards, as an encoding method
only for RFID.
For the sake of simplicity, users want to use a single data standard for the various forms of AIDC media. (See
Figure 1). However, because of the inherent characteristics of RFID and optical technologies, differences in
data encoding arise, some of which will be described within this Technical Report.

Figure 1 — Application user requirement
For example, bar codes are always scanned one at a time, but a large population of RFID tags can be
inventoried nearly simultaneously. To support the RFID inventory operation, the Unique Item Identificaiton
(UII) of the RFID tag is prefaced by “filtering” information (a numbering system identifier or an AFI) that has no
correlation in bar code systems.
2 © ISO/IEC 2012 – All rights reserved

As a second example, for faster inventory operations, many RFID tag architectures transmit only the UII
portion of their data during inventory, sending item attendant data only upon request. In contrast, a 2D symbol
reader always obtains and transmits the full contents simultaneously (both UII and item attendant data).
Since the 1970s, linear bar code symbols have typically encoded application-specific “license plate” item
information. The bar code symbol encodes an identifying primary key to a database entry that contains current
information about the item. If the bar code identifier is not serialized (UPC symbols are an example), it
identifies a class of item, such as a certain product of a certain size. If serialized, the “license plate” identifies a
specific instance of an item; in open system applications, it is important that the identification system can
guarantee that each “license plate” is uniquely distinct from all others.
Unique Item Identifiers (UIIs) can be contained in “unique identification-only” media such as a license-plate
bar code symbol or an RFID tag containing only a UII. In the case of “unique identification-only,” a database or
look-up to trading partner communications is required to establish additional information about the entity to
which the UII is attached. Technologies such as two-dimensional symbols and data rich RF tags can contain
this additional “item attendant data” within that medium.
A number of ISO/IEC specifications have been developed for encoding and decoding of linear bar code
symbologies, such as ISO/IEC 15420 for EAN/UPC and ISO/IEC 15417 for Code 128, and for two-
dimensional symbologies, such as ISO/IEC 15438 for PDF417 (see Bibliography for a complete list).
The remainder of this technical report describes currently available methods for encoding both UII and item
attendant data in optical and RFID media. For all two-dimensional symbols, the data syntax specified in
ISO/IEC 15434 (and summarized in Section 6 of this Technical Report) can be used. For most RFID data
carriers, the UII is encoded separately (for efficient inventory operations), and the item attendant data should
be encoded using ISO/IEC 15434 syntax. The RFID encoding options are summarized in Sections 7, 8, and 9
of this Technical Report, and additional RFID-specific guidance is provided in Sections 10, 11, and the
Annexes A through D
6 ISO/IEC 15434 application for high capacity AIDC media
ISO/IEC 15434 is a transfer structure, syntax and coding of messages and data formats when using high
capacity AIDC media between trading partners, specifically between suppliers and recipients and, where
applicable, in support of carrier applications such as bills of lading and carrier sorting and tracking;
ISO/IEC 15434 includes encoded data:
 used in the shipping, receiving and inventory of transport units;
 contained within supporting documentation, in paper or electronic form, related to unit loads or
transport packages;
 used in the sorting and tracking of transport units;
 used for the sorting and tracking of returnable transport items;
 used for the sorting and tracking of products and product packages.

To allow multiple data formats to be contained within a data stream, a two level structure of enveloping is
employed. The outermost layer of the message is a Message Envelope that defines the beginning and end of
the message. Within the Message Envelope are one or more Format Envelopes that contain the data (See
Figure 2). Multiple formats in a single message should be employed only through trading partner agreements.
© ISO/IEC 2012 – All rights reserved 3

Figure 2 — Envelope structure of ISO/IEC 15434
6.1 Assigned formats in ISO/IEC 15434
Header data and format trailer for each format are defined in Table 1.
Table 1 — ISO/IEC 15434 header data and trailers
Format Format
Variable Header Data Format Description
Indicator Trailer
00  Reserved for future use
G R
vv
01 Transportation
S S
02  Complete EDI message / transaction
F G U R
vvvrrr
03 Structured data using ANSI ASC X12 Segments
S S S S
F G U R
vvvrrr
04 Structured data using UN/EDIFACT Segments
S S S S
G R
05 Data using GS1 Application Identifiers
S S
G R
06 Data using ASC MH 10 Data Identifiers
S S
R
07 Free form text
S
08 vvvvrrnn Structured data using CII Syntax Rules
Binary data (file type) (compression technique) (number
G G G G R
ttt.t ccc.c nnn.n
S S S S S
of bytes)
10-11  Reserved for future use
G R
12 Structured data following Text Element Identifier rules
S S
13-99  Reserved for future use

4 © ISO/IEC 2012 – All rights reserved

Users should refer to ISO/IEC 15434 for the use of information objects as defined in the EDI standard
directories, GS1 AI directory (GS1 General Specification) or ANSI DI directory (ANS MH10.8.2).
6.2 System data elements for compatibility across all AIDC media
As bar code technology began to proliferate in the 1980s, it became apparent that the need existed to encode
more than simple product identity. Lot/batch and serial numbers, purchase order numbers, destination postal
codes, country of origin and a unique license plate for the entity might all need to be encoded on a single
label. Schemes in various industries evolved until the cross-industry exchange of product forced
standardization of tags, or prefixes, to identify the information encoded in the bar code. This gave rise to the
standardization of Data Identifiers (DIs) and Application Identifiers (AIs), referred to as the semantics of an
AIDC data structure, managed by ASC MH10 (DIs) and GS1 (AIs) as defined in ISO/IEC 15418.
Over time, applications were developed for encoding the information on a shipping label into a single symbol,
permitting the information to be read with a single scan. The ability to encode multiple data fields into a symbol
created the requirement to know whether DIs or AIs were being read, where the various structures ended and
others began, and when one would know that no more data followed. This gave rise to the standardization of
data structures into messages, referred to as the syntax of an AIDC message, and was codified in ANS
MH10.8.3 and later in ISO/IEC 15434.
ISO/IEC 24729-1, Information technology — Radio frequency identification for item management — Part 1:
RFID-enabled labels provides a method for enoding the information resident in the RF tag into an optical
symbol, thereby ensuring a backup source of data if the RFID tag should fail.
6.3 Data Carrier Identifiers for RFID and other AIDC media
Various applications need to identify the type of data carrier, and readers and interrogators are able to identify
the means by which the data was entered: RFID, bar code, or key entry. They are able to preface the data
with a data carrier identifier, following the rules of ISO/IEC 15424, Information technology -- Automatic
identification and data capture techniques -- Data Carrier Identifiers (including Symbology Identifiers).
As an example, if an RF tag is unreadable, it may be possible to access a “back-up” technology, e.g. a linear
bar code or two-dimensional symbol. If there is no “back-up” symbol or if it is unreadable, it may be necessary
to key enter the data. Studies for key-entry of data have shown an error rate of approximately 1 in every 300
characters entered, compared to automated techniques with an error rate of 1 in every 1 000 000 characters
entered, or better. If an RF tag or optically readable media fails, it is important to notify the supplier.
© ISO/IEC 2012 – All rights reserved 5

Figure 3 — Operation of data carrier identifiers
7 RFID encoding of UII
Figure 5 shows the memory layout of ISO/IEC 18000-63, Type C and ISO/IEC 18000-3, Mode 3 ASK RF tags.
UIIs are encoded in Memory Bank ‘01’ (MB01 ), as shown in Figure 6. The ISO/IEC 15459 series deals
specifically with Unique Item Identifiers (UIIs), including the means to identify physical objects according to
ISO TC 122’s 1736x relevant documents, and EPC.
The AFI (Application Family Identifier) is encoded in MB01 in the event trading partners do not use EPC
structures. The following subsections detail the steps involved.
7.1 Extant numbering systems for RFID
There are several existing systems to uniquely identify physical objects in an RFID context. These include:
 ISO/IEC 15459-1:2006, Information technology — Unique identifiers — Part 1: Unique identifiers for
transport units
 ISO/IEC 15459-2:2006, Information technology — Unique identifiers — Part 2: Registration
procedures
 ISO/IEC 15459-3:2006, Information technology — Unique identifiers — Part 3: Common rules for
unique identifiers
 ISO/IEC 15459-4:2006, Information technology — Unique identifiers — Part 4: Unique identifiers for
individual items
 ISO/IEC 15459-5:2007, Information technology — Unique identifiers — Part 5: Unique identifier for
returnable transport items (RTIs)
 ISO/IEC 15459-6:2007, Information technology — Unique identifiers — Part 6: Unique identifier for
product groupings
 ISO/IEC 15963:2004, Information technology — Radio frequency identification for item management
— Unique identification for RF tags
6 © ISO/IEC 2012 – All rights reserved

 ISO/IEC 7816-5:2004, Identification cards — Integrated circuit cards — Part 5: Registration of
application providers,
 ISO/IEC 7816-6:2004, Identification cards — Integrated circuit cards — Part 6: Inter-industry data
elements for interchange
 EPCglobal Tag Data Standards, Version 1.5
 ITU X.668 | ISO/IEC 9834-9, Information technology – Open Systems Interconnection – Procedures
for the operation of OSI Registration Authorities: Registration of object identifier arcs for applications
and services using tag-based identification
 ITU X.660, Information technology – Open Systems Interconnection – Procedures for the operation of
OSI Registration Authorities: General procedures and top arcs of the International Object Identifier
tree
7.2 Tag type and UII data storage area
In the early RF tags, RFID memory consisted of a conventional memory structure, incorporating a system
area and a user memory area, as shown in Figure 4. However, in ISO/IEC 18000-63 type C RFID, the
structure changed, and the memory structure and the kinds of data that could be written in each memory area
are defined in the ISO/IEC 18000-63 standard.
From the standpoint of storing UII data, the early RFID had only one user memory area and that is where UII
data was stored. It is recommended that UII data should be the first element in these user area data elements.
In 18000-63 RFID, UII data is written in the UII are. If users intend to deal with two or more UIIs for one item,
the second UII is considered as user data. Because the UII data writing area is dependent on both the
memory type and the intention of the user, the system user should pay careful attention to this point.
User data
ISO Unique ID
Tag control data

System area
User memory area
+
Memory type A
Conventional Memory Structure
ISO Unique ID
EPC or

18000-6C
User data
System area UII area
+
Memory type B
Memory type C System area + UII area + User memory area
EPC User data
ISO Unique ID

UII area User memory area
System area + +
18000-6C
(EPC) (ISO Unique ID) + (User Data)
Memory type C
Figure 4 — RFID memory type and stored data to each memory area
© ISO/IEC 2012 – All rights reserved 7

7.3 ISO/IEC 18000-63, Type C and 18000-3m3 ASK and EPCglobal memory architecture
The first data element on a compliant tag for product and product packaging shall be the unique identification
described in ISO/IEC 15459-4. The length and nature of this unique identification is defined in this data
element. For an ISO/IEC 18000-63 Type C and ISO/IEC 18000-3 Mode 3 ASK compliant tag, the "unique
identification" data element is segregated from any additional (User Data) by the memory architecture. The
unique identification data element shall be stored in UII memory (Bank 01) with any additional data being
stored in User memory (Bank 11). For the purposes of this standard a unique identity of products can be up to
35 alphanumeric characters in length, including the Data Identifier (an3+an.32). With trading partner
agreement the combined length of the Data Identifier and data can be up to 50 alphanumeric characters in
length. This architecture is shown in Figures 5 and 6 below.

Figure 5 — 18000-63, Type C & 3m3 ASK, Memory structure
8 © ISO/IEC 2012 – All rights reserved

Note 1: User Memory (MB11) in Use Indicator (UMI)
Note 2: XPC Indicator
Note 3: “0=Binary / 1=AFI+ISO/IEC 15459”
Note 4: AFI for ISO / TDS-defined for EPC / 29161 defined for ISO binary
Note 5: Last bit of AFI for ISO / Haz Mat for EPC
Figure 6 — 18000-63, Type C & 3m3 ASK, Memory Bank (MB) “01 ”
7.4 Unique Identifier of a physical object (UII)
The UII can follow one of two formats designated by the state of Bit 0x17 of Memory Bank “01 ”
(EPC=0/ISO=1). If Bit 0x17 is a “1” what follows at Bit 0x18 is an AFI (Application Family Identifier). The
AFI formats are shared between JTC 1/SC 31(Automatic identification and data capture techniques) and
JTC 1/SC 17 (Integrated Circuit Cards). The values assigned by JTC 1/SC 17 at the time of publication of this
document are as shown in Table 2. The values under the control of JTC 1/SC 31 are shown in Table 3.
Table 2 — AFI values
AFI most AFI least
Meaning
significant significant Examples / note

nibble nibble
0 0 All families and subfamilies No applicative pre-selection
X 0 All families and subfamilies Wide applicative pre-selection
X Y Only the Yth subfamily of family X
0 Y Proprietary sub-family Y only
1 0, Y Transport Mass transit, Bus, Airline, …
2 0, Y Financial IEP, Banking, Retail, …
3 0, Y Identification Access control, …
4 0, Y Telecommunication Public telephony, …
5 0, Y Medical
6 0, Y Multimedia Internet services, …
7 0, Y Gaming
8 0, Y Data storage Portable files, …
9 0, Y Managed by JTC 1/SC 31 Managed by JTC 1/SC 31
A 0, Y Managed by JTC 1/SC 31 Managed by JTC 1/SC 31
B 0, Y UPU Managed by JTC 1/SC 31
C 0, Y IATA Managed by JTC 1/SC 31
D 0, Y RFU Managed by JTC 1/SC 17
E '0', Y = 1, Machine Readable Travel Y=1 ePassport
Y = 2, Other Y Documents (MRTDs) Y=2 eVisa
values are RFU
F 0, Y RFU Managed by JTC 1/SC 17
© ISO/IEC 2012 – All rights reserved 9

Table 3 — AFI values assigned by JTC 1/SC 31
Data Format
Data
AFI for Root-OID for
Organization: function Format OID for UII
byte additional other data
binary
memory
Reserved for Future Use 90 – 9F
ISO 17367: Supply chain applications A1 6-bit ASCII 1 0 15459 4 6-bit ASCII 1 0 15418 1
of RFID – Product tagging (“1” suffix is to
identify DIs,
“0” for AIs)
ISO 17365: Supply chain applications A2 6-bit ASCII 1 0 15459 1 6-bit ASCII 1 0 15418 1
of RFID – Transport unit
ISO 17364: Supply chain applications A3 6-bit ASCII 1 0 15459 5 6-bit ASCII 1 0 15418 1
of RFID – Returnable transport item
ISO 17367: Supply chain applications A4 6-bit ASCII 1 0 15459 4 6-bit ASCII 1 0 15418 1
of RFID – Product tagging,
containing hazardous materials
ISO 17366: Supply chain applications A5 6-bit ASCII 1 0 15459 4 6-bit ASCII 1 0 15418 1
of RFID – Product packaging
ISO 17366: Supply chain applications A6 6-bit ASCII 1 0 15459 4 6-bit ASCII 1 0 15418 1
of RFID – Product packaging,
containing hazardous materials
ISO 17365: Supply chain applications A7 6-bit ASCII 1 0 15459 1 6-bit ASCII 1 0 15418 1
of RFID – Transport unit, containing
hazardous materials
ISO 17364: Supply chain applications A8 6-bit ASCII 1 0 15459 5 6-bit ASCII 1 0 15418 1
of RFID – Returnable transport item,
containing hazardous materials
ISO 17363: Supply chain applications A9 6-bit ASCII 1 0 10891 0 6-bit ASCII 1 0 15418 1
of RFID – Freight containers
ISO 17363: Supply chain applications AA 6-bit ASCII 1 0 10891 0 6-bit ASCII 1 0 15418 1
of RFID – Freight containers,
containing hazardous materials
ISO/IEC 29174 for Mobile Item AB 7 2 27 1 3 1 0 15434
Identifier (MII) and additional data
Reserved for Future Use AC - BF

ISBT item level blood products BB 30 encoded Not applicable 30 encoded Not applicable
in DSFID = in DSFID =
0x3E 0x3E
IATA RP1740C baggage handling C1 xxx01100 1 0 15961 12 1 xxx01100 1 0 15961 12
[separate UII memory]
EDItEUR: library items C2 xxx00110 1 0 15961 6 1 1 0 15961 6
Reserved for Future Use C3 - CF
Request by German Government TBD

agency for VIN to ISO 3779
Request for Oil and Gas exploration TBD
sector, initiated by Norwegian
Standards
Note: At the time of publication this is the most current listing of AFI values. For an current version of the Data Constructs
Register of which AFIs are a component please download the most current version
from http://isotc.iso.org/livelink/livelink?func=ll&objId=8913563&objAction=browse&viewType=1
10 © ISO/IEC 2012 – All rights reserved

7.5 Data construct
AFIs A1 through AA note that the construction of the data shall be defined in the applicable standard, namely
ISO 17367 through ISO 17363. Therein the AFI defines the data construct. The construct for GS1 data
structures are not encoded using AFIs; they are encoded according to the rules of GS1 EPCglobal when Bit
0x17 of MB01 is set to a “0”. When Bit 0x17 (EPC=0/ISO=1) of MB01 is set to a “1” the semantics, and
2 2
encoding complies with the rules of this clause.
7.5.1 Data semantics
When Bit 0x17 of MB01 (as shown in Figure 6) is set to a “0” the semantics will be as defined in the rules for
GS1 EPCglobal. When Bit 17 of MB01 is set to a “1”, each data field should be prefaced by an
ISO/IEC 15434 message format indicator.
7.5.2 Data syntax
Tags that encode identity only are considered to have no syntax. When Bit 0x17 of MB01 (as shown in
Figure 6) is set to a “0” the syntax will be as defined in the rules for GS1 EPCglobal. When Bit 0x17 of MB01
is set to a “1” the syntax will the same as those for optically readable media.
7.5.2.1 Syntax for the Unique Item Identifier
The Unique Item Identifier (UII), contained in MB01 , is interpreted as a single data element, similar to a single
linear bar code. Therefore there is no message structure except for the Data Identifier and the data. The last
E E
character in this field is the O character defined in Tables C.1 and D.1. The encoding of O removes the
T T
necessity to either identify the length of the field or to zero- or blank-fill unused positions in a single variable
length field.
The Unique Item Identifier (UII) shall be unique among all other items and shall be comprised of:
1. Unique item identifier compliant to ISO/IEC 15459 “25x”
a. Data Identifier (DI)    an…3
b. Issuing Agency Code (IAC)   an…3
c. Company Identifying Number (CIN), and  (length determined by Issuing Agency)
d. Serial Number (SN)
2. Vehicle Identification Number (an17) utilizing the DI “I”
When Bit 0x17 of MB01 (EPC=0/ISO=1) is set to a “1” and Bit 0x15 User Memory (No=0/Yes=1) is set to a
“0”, the contents of MB01 will be read as a linear symbol.
7.6 Encoding of Memory Bank “01” Unique Item Identifier
Bit 0x17 is the switch between ISO formats and EPC formats. When Bit 0x17 is set to a “0”, the UII encoding
is per the EPC Tag Data Standard, Version 1.5 or higher. When Bit 0x17 is set to a “1”, the UII encoding is per
ISO/IEC 15459 preceded by an ISO/IEC 15961 Application Family Identifier (AFI). The specific AFIs defined
for the ISO 1736x series of International Standards are shown in Table 4.

The combined length of IAC, CIN, and SN shall be 50 characters or less. ISO/IEC 15459 states that “The
composition of the serial number may include the product code, but in no case shall the UII exceed 50 characters plus the
Data Identifier. For efficient use within various AIDC data carrier systems, it is recommended that the number of
characters to be coded not exceed 20 characters, and number of characters should be kept as short as possible
regardless of the permissible maximum of 50 characters.” The ISO 1736x series of standards state, “A unique identifier
can be up to 35 alphanumeric characters in length, excluding the Data Identifier (an3+an.35). With the mutual agreement
of the trading partners this length can be extended to 50 characters (an3+an.50).”
© ISO/IEC 2012 – All rights reserved 11

Table 4 — 1736x Application Family Identifiers (AFIs)
AFI Assigned Organisation or Function
0xA1 ISO 17367 product tagging
0xA2 ISO 17365 transport unit
0xA3 ISO 17364 returnable transport unit
0xA4 ISO 17367 product tagging, but for hazardous materials
0xA5 ISO 17366 product packaging
0xA6 ISO 17366 product packaging, but for hazardous materials
0xA7 ISO 17365 transport unit, but containing hazardous materials
0xA8 ISO 17364 returnable transport unit, but containing hazardous materials
0xA9 ISO 17363 freight containers
0xAA ISO 17363 freight containers, but containing hazardous materials

A linear bar code symbol encoding the data providing unique item identification is comprised of the Data
Identifier (DI), Issuing Agency Code (IAC), Company Identification (CIN), and Serial Number (SN). Such a
unique item identification linear bar code would be represented in Code 128 as shown in Figure 7.
 DI = 25S
 IAC = UN (DUNS)
 CIN = 043325711
 SN = MH8031200000000001
Figure 7 — Code 128 encoding “25SUN043325711MH8031200000000001”
Adding the AFI to the structure for RFID purposes we have
 AFI = 0xA1
 DI = 25S
 IAC = UN (DUNS)
 CIN = 043325711
 SN = MH8031200000000001
Looking at a completed data structure using the encoding defined above and using DUNS as the Issuing
Agency Code (IAC), we find that MB01, when encoding a Product, this data structure is
25SUN043325711MH8031200000000001 and is represented in MB01 as shown in Table 5.
Table 5 — MB01 structure of AFI and UII (DUNS) using six-bit encoding
AFI = 0xA1 2 5 S U N 0 4 3 3 2 5 7 1
1010 0001 110010 110101 010011 010101 001110 110000 110100 110011 110011 110010 110101 110111 110001
1 M H 8 0 3 1 2 0 0 0 0 0 0 0 0
110001 001101 001000 111000 110000 110011 110001 110010 110000 110000 110000 110000 110000 110000 110000 110000

0 0 1
110000 110000 110001
12 © ISO/IEC 2012 – All rights reserved

Alternately, looking at a completed data structure using the encoding defined above, using ODETTE as the
Issuing Agency Code (IAC), we find that MB01 when encoding a Product having an:
 AFI = 0xA1
 DI = 25S
 IAC = OD (ODETTE)
 CIN = CIN1
 SN = 0000000RTIA1B2C3DOSN12345 (This example shows the SN composed of Object Type and
Object Serial Number)
. . . we have an MB01 structure as shown in Table 6.
Table 6 — MB01 structure of AFI and UII (ODETTE) using six-bit encoding
AFI = 0xA1 2 5 S O D C I N 1 0 0 0 0
1010 0001 110010 110101 010011 001111 000100 000011 001001 001110 110001 110000 110000 110000 110000
0 0 0 R T I A 1 B 2 C 3 D O S N
110000 110000 110000 010010 010100 001001 000001 110001 000010 110010 000011 110011 000100 001111 010011 001110

1 2 3 4 5
110001 110010 110011 110100 110101

In both cases, once the AFI is stripped from the message, the output of the RFID reader is identical to that of
the linear bar code.
7.6.1 Conclusion
Using the ISO/IEC 15434 Direct Encoding, MB01 of an ISO/IEC 18000-63, Type C or an ISO/IEC 18000-3,
Mode 3 ASK RF tag will provide the same output as optically readable media. Using the Harmonized Six-Bit
approach, the encoding of MB11 of an ISO/IEC 18000-63, Type C or an ISO/IEC 18000-3, Mode 3 ASK RF
tag will provide the same output as Figures 8 and 9, below. This method also has the benefit of simplifying
the data encoding process. When encoded in a 2D symbol, the output would be identical:
[)>0625SUN043325711MH80312000000000011T110780Q214LUS

Figure 8 — QR Code encoding the contents of MB01 and MB11
[)>0625SUN043325711MH80312000000000011T110780Q214LUS

Figure 9 — Data Matrix encoding the contents of MB01 and MB11
© ISO/IEC 2012 – All rights reserved 13

[)>0625SUN043325711MH80312000000000011T110780Q214LUS
For 18000-63, Type C and 18000-3, Mode 3 ASK air interfaces an interrogator will simply read the number of
words specified in 0x10 to 0x14 of MB01 , read those bytes, and then pass the payload for post-read
processing, which might be done in a host processor or a module of the interrogator. From that read the
Unique Item Identifier (UII) will be extracted.
8 RFID encoding of user data
The Access-Method, (shown in Table 7) as defined by the application, is the most significant determinant of
how data is encoded on the RFID tag. The value of the Access-Method should be stored on the RFID tag, or
may be defined by the air interface services, if this can be done unambiguously. The Access-Method is
defined as an integer value in the application command and encoded as a compound bit value in the DSFID
and the SFF (Special Features Flag) byte on the RFID tag
Table 7 — ISO/IEC 15962 Table 7
15961 15962 15962 Name Description
integer DSFID SFF bit
code bit code code
0 00 00 No-Directory This structure supports the contiguous abutting of all the Data-
Sets
1 01 00 Directory The data is encoded exactly as for No-Directory but the RFID
tag supports an additional directory, which is first read to point to
the address of the relevant object identifier.
2 10 00 Packed-Objects This is an integrated compaction and encoding scheme that
formats data in an indexed structure as defined by the
Application administrator (see ISO/IEC 15961-2)
3 11 00 Tag-Data-Profile This is an integrated compaction and encoding scheme for a
fixed set of data elements, each of a defined length

8.1 No directory
The Access-Method = No-Directory is designed to achieve a combination of flexibility and efficiency for the
bytes that are encoded on the RFID tag. In particular:
 Data Objects are compacted efficiently using a defined set of compaction techniques that reduce
the encoding of data objects on the RFID tag across the air interface;
 Data formatting minimises the encoding of the Object-Identifiers on the RFID tag and on the air
interface, but still provides complete flexibility for identifying specific data.
8.2 Directory
The Access-Method = Directory has a two part structure in the Logical Memory:
 The lower addressed blocks are identical to the No-Directory structure;
 The higher blocks contain the directory.
8.3 Packed Object
The Packed-Objects encoding scheme was developed after the first edition of ISO/IEC 15962 was published.
It uses a rules-based table, defined by the application administrator and registered under the rules of
ISO/IEC 15961-2. This encoding scheme specifies common compaction schemes which are significantly more
efficient than those defined for the No-Directory structure, and a compaction scheme can be specified for
each Relative-OID value in the table. In addition, the Packed-Objects encoding scheme may specify the use
14 © ISO/IEC 2012 – All rights reserved

of the same compaction schemes as of the No-Directory Access-Method. This enables a simpler
implementation, but still with encoding efficiencies over the basic No-Directory Access-Method.
8.4 Tag Data Profile
The Access-Method = Tag-Data-Profile is designed to support applications that are able to define all the
encoded data as mandatory and of a fixed or maximum length. It is possible to apply encoding rules that
achieve an efficient encoding of the bytes on the RFID tag. In particular:
 The Tag-Data-Profile table, if accessed by the interrogator, provides a rapid access to any data
on the RFID tag.
 Data Objects are compacted efficiently using a defined set of compaction techniques that reduce
the encoding of data objects on the RFID tag across the air interface.
 The Precursor and other syntax on the No-Directory Access-Method are retained to enable
interrogators with no access to the Tag-Data-Profile to decode the data.
The encoding consists of some meta-data that uniquely identifies the Tag-Data-Profile plus encoded data
sets that are the same as if encoded using the No-Directory Access-Method, except that all the data has a
predetermined length and compaction.
9 RFID ISO/IEC 15434 direct encoding of user data
There is one combination of the ISO/IEC 15962 Access Method and Data Format used for the direct encoding
of an ISO/IEC 15434 message into user memory (as in the case of 18000-63, Type C). Annex C and Annex D
detail the methods of encodation and formatting. Annex C gives examples of all supported ISO/IEC 15434
data formats whereas Annex D explains specific implementations of Data Identifiers for use with ISO TC 122
documents (ISO 17364, ISO 17365, ISO 17366, and ISO 17367).
10 Storing data in various types of RF tags
For RFID transponders that do not have memory bank separation, there are four ways to store user data in
the memory of the transponder.
 Employ ISO/IEC 15434. The first information object should be the UII. UII is interpreted as a linear bar
code symbol following the rules of ISO/IEC 15459. Utilize ISO 1736x to specify encoding. Differences
in encoding are an attribute of the Application Family Identifier (AFI). The revision of 1736x specifies
6-bit ASCII encoding as shown in Annex D.
 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. With root OID the reference should be
ISO/IEC 15434. The user data can be constructed based on the rules of ISO/IEC 15434. And it is
recommended that the first information object should be the UII.
 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. With root OID the reference should be
ISO/IEC 15418. The user data can be constructed using ANSI DIs or GS1 AIs. And it is
recommended that the first information object should be the UII.
 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. The user data can be constructed using
proprietary defined information objects (with Object IDs & Values). And it is recommended that the
first information object should be the UII.
For RFID transponders that have memory bank separation (e.g., ISO/IEC 18000 part 6 type C and
ISO/IEC 18000 part 3 mode 3: see Figure 5), there are also four ways to store user data in the memory of the
RFID transponder.
 Employ ISO/IEC 15434. The UII should be stored in “MB01”. Utilize ISO 1736x to specify encoding.
Differences in encoding are an attribute of the Application Family Identifier (AFI). The revision of
1736x specifies 6-bit ASCII encoding as shown in Annex D. User memory “MB11” is interpreted as a
two-dimensional symbol using the ISO/IEC 1534 syntax
© ISO/IEC 2012 – All rights reserved 15

 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. With root OID the reference should be
ISO/IEC 15434. The user data can be constructed based on the rules of ISO/IEC 15434. And the UII
should be stored in the UII memory bank.
 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. With root OID the reference should be
ISO/IEC 15418. The user data can be constructed using ANSI DIs or GS1 AIs. And the UII should be
stored in the UII memory bank.
 Employ ISO/IEC 15961 and ISO/IEC 15962 structure. The user data can be constructed using
proprietary defined information objects (with Object IDs & Values). And UII should be stored in UII
memory bank.
11 Methods to store UII data in RFID memory and other AIDC media
As defined in the ISO/IEC 5459 series, the UII is cons
...