ISO/DTR 24168

• Status: Not Published
• ICS: 35.040.50 - Automatic identification and data capture techniques
• ICS: 55.180.40 - Complete, filled transport packages
• Technical Committee: ISO/TC 122 - Packaging
• Drafting Committee: ISO/TC 122 - Packaging
• Current Stage: 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
• Start Date: 21-Sep-2026
• Completion Date: 21-Sep-2026

Overview

ISO/DTR 24168:2026 is a draft technical report developed by ISO Technical Committee 122, focused on packaging. This document explores the effective use of radio frequency (RF) tags-commonly implemented via RFID technology-on returnable transport items (RTIs) to enable dynamic information exchange throughout the logistics and supply chain sectors. The report provides guidance on leveraging RF tag memory to capture, store, and access information concerning goods packed on or within RTIs.

By converting traditional paper-based logistics processes into digital, automated workflows, organizations can unlock higher efficiency, reduce operational costs, and improve traceability across various stages of the supply chain.

Key Topics

• RTI Identification and Data Storage:
  ISO/DTR 24168 underlines approaches for using RF tag memory to uniquely identify RTIs and manage associated logistics data. It references best practices from standards such as ISO/IEC 17360 and ISO/IEC 18000-63.

• Separation of RTI Data:
  The standard distinguishes between “important data” (requiring high reliability and low latency, stored in the UII memory area) and “general data” (requiring more storage capacity, stored in the USER memory area). This division ensures that critical operational information is quickly accessible, while larger datasets remain available as needed.

• Supply Chain Process Integration:
  The document details how information on goods-such as order number, part numbers, shipment details, and delivery receipts-can be electronically encoded in RF tags. This enables real-time data retrieval at multiple touchpoints, enhancing visibility for suppliers, logistics providers, and recipients.

• Automation and Operational Benefits:
  Automatic RF tag reading streamlines logistics tasks, reducing manual data entry and paperwork, and supporting system interoperability. The standard highlights the anticipated efficiency gains and reduced error rates in shipping, warehousing, and inventory management operations.

• Environmental and Compliance Advantages:
  Transitioning from paper to digital information frameworks not only minimizes environmental impact but also facilitates faster compliance checks, such as customs clearance, by embedding critical data within transport items.

Applications

The guidance from ISO/DTR 24168 benefits industries relying on reusable packaging and returnable containers-such as automotive, retail, electronics, and food supply chains. Practical applications include:

• Automated Inventory Tracking:
  Enable real-time tracking of RTIs and contained goods for warehouse management systems, reducing inventory discrepancies.

• Enhanced Shipment Verification:
  Instantly verify content, destination, and shipment details during goods handover points, improving logistics accuracy and efficiency.

• Paperless Logistics Operations:
  Support sustainability and reduce administrative overhead by replacing paper-based records with RFID-enabled digital processes.

• Customs and Regulatory Compliance:
  Embed import/export and shipment-related data within RF tags to facilitate customs clearance and ensure regulatory conformity.

• Interoperability in Multi-party Supply Chains:
  Uniform RF tag data structures enable seamless data sharing among suppliers, logistics providers, and customers.

Related Standards

To ensure compatibility and optimal use of radio frequency tags, this document aligns with several established international standards, including:

• ISO/IEC 17360:
  Covers permanent identification of RTIs and the use of RFID for supply chain management.
• ISO/IEC 18000-63:
  Specifies technical requirements for RFID in ultra-high frequency (UHF) band.
• ISO 21067-1 & ISO 21067-2:
  Provide vocabulary and environmental terms for packaging.
• ISO/IEC 19762:
  Harmonizes vocabulary for automatic identification and data capture (AIDC) technologies.
• ISO/IEC 15962 & ISO/IEC 15963-1:
  Define data structure and tag identifier standards used for encoding information in RFID tags.

Conclusion

Implementing ISO/DTR 24168 empowers organizations to streamline logistics, enhance supply chain transparency, and adapt to digital transformation trends using standardized RFID best practices for returnable transport items. For businesses and logistics operators handling reusable packaging, applying these principles supports greater operational efficiency, sustainability, and regulatory compliance.

FINAL DRAFT
Technical
Report
ISO/TC 122
Packaging — Effective use of radio
Secretariat: JISC
frequency tags on returnable
Voting begins on:
transport items (RTIs) to obtain
2026-09-21
information concerning goods on or
Voting terminates on:
in RTIs
2026-11-16
Emballage — Utilisation d'étiquettes à radiofréquence sur les
emballages de transport réutilisables (RTI) pour l'obtention
d'informations relatives aux marchandises sur et dans les RTI
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
FINAL DRAFT
Technical
Report
ISO/TC 122
Packaging — Effective use of radio
Secretariat: JISC
frequency tags on returnable
Voting begins on:
transport items (RTIs) to obtain
information concerning goods on or
Voting terminates on:
in RTIs
Emballage — Utilisation d'étiquettes à radiofréquence sur les
emballages de transport réutilisables (RTI) pour l'obtention
d'informations relatives aux marchandises sur et dans les RTI
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .2
3.2 Abbreviated terms .2
4 Business-to-business ordering and logistics . 2
4.1 Definitions of notations .2
4.1.1 Numeric notation .2
4.1.2 Character notation .3
4.2 Flow of order receipt and delivery between organisations .3
4.3 Importance of information in business-to-business logistics .3
4.4 Information expected to be stored in the RF tag attached to the RTI .4
4.4.1 General .4
4.4.2 At the location of the supplier .4
4.4.3 At the logistics provider (between the supplier and the client) .4
4.4.4 At the location of the client (delivery destination upon receipt of the products) .4
5 Obtaining and using information from RF tags attached to RTIs. 6
5.1 Expectations for automation of information acquisition and on-site work efficiency.6
5.2 Features and utilization of RF tag memory area.7
5.2.1 General .7
5.2.2 Characteristics of UII and USER.7
5.2.3 Allocation and operation of information to be stored in the memory area.7
5.3 Expected effects of using RF tags attached to RTIs as an information medium .8
6 How to utilize RF tag memory . 8
6.1 Data storage in the UII .8
6.2 Storing data in the USER .9
7 Data structure . 9
7.1 General .9
7.2 Memory structure .9
7.2.1 General .9
7.2.2 RESERVED memory bank (MB00) .9
7.2.3 UII memory bank (MB01) .9
7.2.4 TID memory bank (MB10) .9
7.2.5 USER memory bank (MB11) .10
7.3 Identification of RTIs .10
7.4 Additional information encoding .11
7.4.1 General .11
7.4.2 Additional information encoding to UII memory .11
7.4.3 Additional information encoding to USER memory . 13
8 RF tag utilization model for RTI and demonstration experiment .16
8.1 Scope of operation and demonstration model .16
8.1.1 General .16
8.1.2 Evaluation items between the ordering party and the supplier .16
8.1.3 Experimental model onsite after acceptance of the products .16
8.1.4 Experimental models onsite after arrival of the order at the ordering party.16
8.2 Results and issues for each demonstration model .17
8.2.1 Identification of bottlenecks in the parts export process .17
8.2.2 Improving efficiency of verification work at customs clearance .17
8.2.3 Preventing parts from being incorrectly loaded .17
8.2.4 Automated RTI sorting .18

iii
8.2.5 Quality improvement of shipping operations .18
8.3 Summary and future work .18
Annex A (informative) Demonstrations and results .20
Annex B (informative) 6-bit encoding.33
Annex C (informative) Data byte count-indicator for ISO/IEC 15434 messages .34
Annex D (informative) RTI's operational model .35
Annex E (informative) Appending and rewriting transient data .37
Annex F (informative) Case studies with large amounts of information .39
Annex G (informative) Role of the host system in utilizing RF tags for RTI .42
Annex H (informative) Relationship between RTI owner and RTI management tag .43
Annex I (informative) Identification of RTI using "ISO/IEC 15418 and ANSI MH10.8.2 DIs: UTF-8
8-bit UII encoding" in ISO/IEC 17360 .44
Bibliography .46

iv
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 122, Packaging.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
Introduction
ISO/IEC 17360 provides permanent identification of returnable transport items (RTIs) and returnable
packaging items (RPI), which are both referred to as RTI in this document, using Radio Frequency
Identification (RFID). Associated information for purchasing, accounting or customs purposes is frequently
available via associated electronic data interchange (EDI). In practice, and for a number of reasons, many
logistics operations rely on a paper document for items slip, packing slip, bill of lading information. They
also rely on paper labels for physical distribution information. This is inefficient and labour intensive.
In the logistics field, it is important that packing details and work instructions are based on the latest
information. In such cases, it is more efficient if the relevant data are written in the radio frequency (RF) tag
on the RTI.
This document demonstrates how existing RFID technology can be used to electronically deliver the relevant
information written in the RF tag on the RTI that is accessible throughout the logistics supply chain.
This document describes a methodology to effectively use RF tags for identification in RTIs according to
existing standards (e.g. ISO/IEC 17360, ISO/IEC 18000-63).
Specifically, it shows how to write and rewrite goods data stored or loaded on RTIs. It also gives examples
of information that is distributed to RF tags already attached to RTIs according to existing standards. It also
summarizes how to confirm effectiveness through several demonstration experiments.

vi
FINAL DRAFT Technical Report ISO/DTR 24168:2026(en)
Packaging — Effective use of radio frequency tags on
returnable transport items (RTIs) to obtain information
concerning goods on or in RTIs
1 Scope
This document describes methods of using the RF tag memory for identification of returnable transport
items (RTIs) or returnable packaging items (RPIs) to store and access supply chain logistics information.
This document covers the following:
— information used in supply chain logistics scenarios;
— memory area usage and encoding;
— application models;
— feasibility study and results;
— some issues and future directions.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 445, Pallets for materials handling — Vocabulary
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Vocabulary
ISO 21067-1, Packaging — Vocabulary — Part 1: General terms
ISO 21067-2, Packaging — Vocabulary — Part 2: Packaging and the environment terms
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO 445, ISO/IEC 19762 and ISO 21067-1
and ISO 21067-2 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/

3.1 Terms and definitions
3.1.1
memory bank
MB
designated name of a segmented memory structure
Note 1 to entry: ISO/IEC 18000-63 compliant tags have 4 (four) individually usable memory banks, numbered Memory
Bank 00 (MB00), Memory Bank 01 (MB01), Memory Bank 10 (MB10), and Memory Bank 11 (MB11).
[SOURCE: ISO 20910:2019, 3.1]
3.1.2
serial number
SN
codes such as sequential numbers for uniqueness
Note 1 to entry: The structure of the serial number can be decided by the organization that is under the control of the
issuing agency. This is normally composed of an item number and its production number (serial number).
3.2 Abbreviated terms
CRC-16 16-bit cyclic redundancy check (CRC)
DSFID data storage format identifier indicator
MB memory bank
PC protocol control
RESERVED reserved memory bank
UII unique item identifier memory bank
USER user memory bank
4 Business-to-business ordering and logistics
4.1 Definitions of notations
4.1.1 Numeric notation
In this document, numerical values are represented as follows.
Binary numbers are written in Arabic numerals with the initial letter "b" for "binary" added as a subscript
at the end of the numerical notation. The upper digits are written from the left end, and the lower digits are
written from the right end. Each four digits are separated by a space and zero suppression (omitting the
high-order 0) is not used. For example, nnnn nnnn nnnn (n represents a variable).
b
Decimal numbers are represented numerically using Arabic numerals only, with no subscripts or symbols
indicating decimal numbers. In addition, every three digits from the least significant to the most significant
are separated by a space. For example, nn nnn nnn (n represents a variable).
Hexadecimal numbers are written using Arabic numerals from 0 to 9 and capital letters from A to F, with
the initial letter "h" for "hexadecimal" added as a subscript at the end. The higher value is written from the
left end, and the lower value is written on the right side. Each two digits are separated by a space and zero
suppression (omitting the high-order 0) is not performed. For example, nn nn nn (n represents a variable).
h
The same value can be expressed in binary, decimal, or hexadecimal as follows:

Binary: 0000 0001 1000 0001 1100 1101
b
Decimal: 98 765
Hexadecimal: 01 81 CD
h
4.1.2 Character notation
In this document, character strings that are treated as information for ID or article identification are
enclosed in double-quotation marks. For example, "25B". Then, for control characters used in character
strings treated as information, such as characters indicating group separation and characters indicating the
end of transmission, enclose the abbreviation of the control character in square brackets for each control
character. For example, "[GS]", "[EOT]". Blank spaces are indicated by "[]".
“25BTAJ70107010260960000000202211000001[GS]8D20221101100011[EOT] [EOT] [EOT]”
4.2 Flow of order receipt and delivery between organisations
Logistics between companies occurs because of the act of placing and receiving orders between two parties.
Specifically, the supplier such as a parts manufacturer, produces parts based on order information provided
by the ordering organisation, for example an assembly manufacturer acting as the client. The supplier stores
the parts in shipping cases, such as RTIs, and uses EDI for information exchange during this process. The
parts are then handled through inventory and cargo arrangement process before being shipped by the
supplier to the ordering organisation.
This procedure is the basic process unit of the flow of goods. These processes have connected each other
from the material procurement stage to the delivery stage to the end user, forming a supply chain. See
Figure 1 and Figure 2.
Key
1 supplier: shipper, shipping source organisation that receives orders, prepares and ships the goods
2 client: consignee, shipping destination organisation that places the order and receives the goods
3 transportation
4 information or data transmission (e.g. EDI)
Figure 1 — Image of business-to-business logistics
4.3 Importance of information in business-to-business logistics
Within an organization, parts and products are usually stored in containers and loaded on pallets after
completion and then moved and stored in factories and warehouses. Typical forms and models of loading
are described in Annex D. Logistics between organizations is also generally conducted in the same manner.
The containers and pallets used in this process are called RTI and are basically collected when parts or
products have been emptied and returned to the organization that owns the RTI. The following three cases
are expected for the owner (see Annex H):
— case 1: supplier (e.g. parts manufacturer);

— case 2: ordering party (the client, e.g. assembly manufacturer);
— case 3: outsourced third party (who owns or provisions the RTI).
In addition, a great deal of information is generated while receiving and placing orders, i.e. the manufacture
of products within a company, inventory, in-process logistics and inter-company logistics, etc., and various
operations are carried out on site, referencing or using this information.
Especially in the field of logistics, smooth shipment and delivery operations between organizations cannot
be achieved without information on "stored items" and "number of items". Such information indicates what
items and how many items are loaded on RTIs (containers and pallets) used for transportation. In addition,
"logistics information" such as when and where to transport these items, is also important.
Currently, most of this information is printed on paper media, such as “item slips”, “delivery notes” or
“barcode labels”, and is attached to, affixed to, or inserted into each transportation unit.
It is expected that information is carried when moving goods in inter-company logistics, and it is useful to
integrate goods and information.
Currently, paper forms are usually affixed or converted into machine-readable labels as a means of
integration. It is assumed that if RF tags attached to RTIs can take on this role, this will improve the efficiency
of information acquisition and human work.
4.4 Information expected to be stored in the RF tag attached to the RTI
4.4.1 General
This subclause provides an overview of the typical information that is used in a business-to-business
logistics scene, based on the premise that the information is stored in RF tags attached to RTIs and read at
the location where the information is used.
In this subclause, the logistics between organizations are considered more concretely, as illustrated in
Figure 2. The flow is organized from the perspective of the ordering party (the client or receiving party
address nominated by the client) and clarifies the handling of RTIs and the relevant information for each
entity.
4.4.2 At the location of the supplier
The supplier, who is commonly the manufacturer, based on advance orders received or expected demand,
manufactures or otherwise obtains parts, etc. and stores them in RTIs in its warehousing. At this time, the
supplier affixes an in-house warehousing “actual product slip” that clearly indicates what kind of parts and
how many parts are stored.
When an order is received from an ordering party (the client), the ordered parts are provisioned by the
supplier and stored in units of RTIs among the stored products pending subsequent shipment area, and then
the order is picked and satiated. At that time, an “actual product slip” for the client is issued with order
details (e.g. parts part number, quantity) and the delivery address, and is affixed to the RTI for shipment
(and any internal warehousing “actual product slips” removed from the RTI).
4.4.3 At the logistics provider (between the supplier and the client)
Upon collection from the supplier, at the supplier’s shipping point, the logistics provider checks the actual
product slip and other documents affixed to the RTI. The provider then loads the RTIs onto a means of
transport (e.g. truck, train, ship or aeroplane) and transports the order, together with the delivery note, to
the delivery destination designated by the ordering party (e.g. client).
4.4.4 At the location of the client (delivery destination upon receipt of the products)
The delivery location checks the delivery slip and the actual product slip with the actual products loaded
in the RTIs and enters each unit of RTIs into its warehousing. The information on the delivery note is added

to the warehouse inventory system. It is then referred to when the unit of RTI is picked and put into the
production line based on the production plan, and each part in the RTI is used in the product assembly
process (or forwarded to the next link in the logistics chain).
a) Onsite after the order receiv- b) Between client and supplier c) Onsite after the acceptance of
er's arrival the products
Key
A supplier
B logistics provider
C client
1 line off and storage
2 warehousing
3 ordering and shipping
4 uniforms and shipping
5 warehousing, uniforms, shipping
6 acceptance
7 warehousing
8 leaving the depot
9 parts input
Figure 2 — Business-to-business logistics including logistics providers
Table 1 lists the specific information which is generally used at each site for the inter-company logistics
mentioned in 4.3, and is read from the forms affixed to RTIs for various confirmations at each site. Although
this information does not cover everything, it is assumed that the integration of objects and information will
be realized when such information is stored in RF tags attached to RTIs.

Table 1 — Specific examples of information relevant to the location
Location supplier logistics provider client
unloading
manufac- warehous- ship- receipt accept- assem-
(cargo, custody shipping
information type
ture ing ping of goods ance bly
etc.)
ordering party part
 
number
storage quantity    
ordering party part
  
number
quantity of contain-
ers to be transport-    
ed
recipient   
  
acceptance location
delivery date and
   
time
order number  
product no.   
commodity code 
Table 1 provides basic information used by workers at each location to quickly identify and verify the cargo
or RTI being handled. However, the types of information vary depending on the industry, business type and
work activity, and are intended for reference purposes only.
As indicated by the checkmarks in Table 1, the relevant information varies from one location to another.
Therefore, only a subset of the information listed in Table 1 can be stored in the RF tag attached to the RTI.
However, the memory of the RF tag is expected to be rewritten as appropriate so that the information can be
made available from the RF tag at the intended location and time.
In addition, various types of related information not listed in Table 1 can also be relevant, and the amount of
information varies. Therefore, it is important to consider how the information is divided and stored in the
memory area of the RF tag.
5 Obtaining and using information from RF tags attached to RTIs
5.1 Expectations for automation of information acquisition and on-site work efficiency
In many cases, information on cargo loaded on RTIs is obtained by workers visually reading paper forms
affixed to the cargo, or by machine-reading labels converted into machine-readable symbols with a handheld
terminal or similar device. On the other hand, if relevant information can be automatically obtained from a
medium such as an RF tag attached to a predetermined position of RTI without human intervention, it is
expected to greatly improve the efficiency of on-site work and promote automation.
In addition, logistics companies, warehouses, distribution centres, and other logistics specialists other
than the ordering organization are also involved in business-to-business transportation. There are many
work environments where it is not possible to obtain logistics-related information on the cargo transported
by the ordering organization in advance or directly on site, nor via EDI. If it becomes possible to obtain
logistics-related information from RF tags attached to RTIs at such workplaces, this information can be used
to improve efficiency and automation.
For example, when transporting a unit load of containers on a pallet at a logistics site, the on-site worker
confirms the destination of the unit load, the number of containers on the pallet, the designated date of
arrival, and other information obtained from the RF tag on the pallet. In addition, the ordering organization
uses the information obtained from the RF tags of the containers loaded on the pallet to check what kinds of

goods are contained in the containers, how many goods are included, and to which process the containers
will be transported next. Based on this information, the transport operation is automated.
By storing relevant information in RF tags attached to RTIs and automatically reading them, information
can be obtained and used effectively in various scenes of the work process, which is expected to contribute
greatly to efficiency.
5.2 Features and utilization of RF tag memory area
5.2.1 General
RF tags used for RTI permanent identification have UII and USER memory areas that contain information
and have the following characteristics as explained in 5.2.2.
5.2.2 Characteristics of UII and USER
According to ISO/IEC 18000-63, the UII has a cyclic-redundancy check (CRC) checking mechanism to ensure
reliability. On the other hand, the USER does not have such a mechanism.
In the UII, the inventory command is issued to obtain stored data. In the USER, after issuing the inventory
command, the “Read” command is issued by specifying the RF tag for which a response is requested based
on the return data from the RF tag and specifying the size of data to be read. Because of this complexity,
it generally takes more time to obtain stored data from the USER than from the UII. On the other hand,
USER tends to have a larger capacity than the UII and has the advantage of storing more data. Therefore, the
memory size of the UII is small, but its reliability is high, and the reading time is short. The USER has a large
memory capacity and can store a lot of information, but it takes longer to load. It is important to allocate
information that takes advantage of these features.
5.2.3 Allocation and operation of information to be stored in the memory area
Some information is expected to be obtained in a short time (low latency) at the read location, while other
information is not. Considering these characteristics and the intended use at the location, it is effective to
use the UII and the USER separately to store information.
In this document, the information to be stored is classified into two types, “important data” and “general
data”, as follows:
— important data are stored in the UII, and
— general data are stored in the USER.
This distinction arose from several demonstration experiments, which are described in Clause 8 and
Annex A. The characteristics of these different categories of data can be summarised as:
a) important data: data that are the basis for other data, data that are used repeatedly in many processes;
b) general data: data that are linked to important data and are not particularly sensitive to reading latency.
ISO/IEC 17360 specifies that the RTI identification information is written in the memory area following the
PC bits in the UII area (7.3). On the other hand, when important data are written in the UII, it is stored
as additional data following the RTI identification information (7.4). Important data are updated (revised)
from time to time.
The information items and data size to be handled will vary depending on the operations of the companies
that conduct the transactions.
While envisioning such an operational approach, this document examines the effectiveness of such an
approach by means of a demonstration experiment (see Annex A).

5.3 Expected effects of using RF tags attached to RTIs as an information medium
By using RF tags attached to RTIs as an information medium for business-to-business logistics, the following
various effects are expected.
a) Reduced labour or workforce: Reduction in the amount of work for on-site workers, i.e. less information
on paper to visually read and understand, or to input into the system.
b) Information linkage with corporate systems: Information automatically obtained from RF tags can be
immediately linked to the related systems in the organization, enabling rapid response to the processing
of accepted RTIs and loads (e.g. inspection work, inventory control work) (see Annex G).
c) Reduction of work related to paper media and environmental considerations: This reduces the
preparation and printing of paper media such as actual product slips and delivery slips, as well as the
collection and disposal of paper media.
d) Reduction of operational costs in the logistics chain: In an operation where physical and document
checks are performed each time, RF tags are used to store information items to be checked, enabling
automatic cross-checking, thereby minimizing the information to be checked by workers.
e) Customs clearance: In customs clearance of international logistics, it is important to distinguish
whether an RTI is an import and export product or simply a transport container, etc. By appropriately
storing information to be checked at customs clearance on the RF tag, it complies with the re-import
duty exemption procedures.
6 How to utilize RF tag memory
6.1 Data storage in the UII
When appending or rewriting a part of the UII in RF tags for RTI management, ISO/IEC 17360 specifies a
header area whose data identifier (DI) starts with “25B”. This area contains the data of the RTI and the
owner of the RTI, so “important data” can be written in the area following it, as shown in Figure 3.
Since the RF tag for RTI management is affixed to the RTI by the owner of the RTI, the RF tag also belongs to
the owner of the RTI. Therefore, for security reasons, the owner of the RF tag is also responsible for managing
the password when writing data. Since, in ownership case 1 (described in 4.3), the RTI administrator knows
the access password for RTI management tags, suppliers can store data in RTI management tags.
NOTE See Annex H for the relationship between ownership cases 1, 2 and 3 (described in 4.3) and RTI management
tags. In ownership case 2 and 3, suppliers can store data in RTI management tags where the owner of the RTI tag is
prepared to share its password with the supplier.
In business-to-business logistics, important or general data are written when products are loaded into an
RTI (see Annex E). Therefore, writing or rewriting these data at other places or timing is only possible where
the password is shared.
Key
1 additions and rewritten portions of UII area
Figure 3 — Important data writing locations in the UII

6.2 Storing data in the USER
General data can be stored in the USER, using the methods specified in ISO/IEC 18000-63, and ISO/IEC 17360.
7 Data structure
7.1 General
The memory and data structures of the RFIDs used for validation in this document are defined in
ISO/IEC 18000-63. The provisions of ISO/IEC 17360 are used for the data structures.
7.2 Memory structure
7.2.1 General
The memory structure of RFID specified in ISO/IEC 18000-63 has four memory banks (MBs):
— MB00: RESERVED
— MB01: UII
— MB10: TID
— MB11: USER
7.3 describes the placing and use of identification information for RTIs, while 7.4 explains additional
information that can be stored in UII memory and USER memory according to the provisions of that memory
structure. See ISO/IEC 18000-63 for more information on the functions of the RESERVED and TID memory.
7.2.2 RESERVED memory bank (MB00)
The RESERVED memory is an area that stores the kill password and the access password. The kill password
functions to prevent the RF tag from being killed and the access password functions to prevent the data
from being rewritten.
7.2.3 UII memory bank (MB01)
The UII memory is an area for storing unique identifiers. The first word (16 bits) stores the CRC-16, which
has the function of determining if there is an error in communication, and the next word is a dedicated area
where “StoredPC” is stored (this area is hereinafter referred to as "PC bits"). The UII data are stored in the
area following the “PC bit” area. The extended PC bits are then stored in MB 01 at addresses 210 to 22F
h h
(“StoredPC” is defined in ISO/IEC 18000-63).
When the code system conforms to ISO/IEC 18000-63, the Application Family Identifier (AFI) registration
contents define the data structure, bit compression method, and format of the UII memory, and these
registration contents are specified in AIM global document: ISO/IEC 15961-2 Applications Family Identifier
[15]
(AFI) Assignments Register.
The PC bits define only UII memory, not USER memory.
7.2.4 TID memory bank (MB10)
The TID memory stores the class identifier defined in ISO/IEC 15963-1: the custom commands and optional
functions specified by the registrar defined by the value of the class identifier and uniquely identifiable
information. The TID memory is permanently locked at the time of RF tag IC manufacturing.

7.2.5 USER memory bank (MB11)
When storing data in ISO/IEC 15962 format, the first 16 bits are dedicated to the “Data storage format
identifier” (DSFID) and pre-cursor, and store the USER data access method, format, data compression method
and format information. Depending on the RF tag type, some RTI ID tags cannot support USER memory.
7.3 Identification of RTIs
Identification information for RTIs can be stored in UII memory using 6-bit UII encoding with Data Identifiers
(DIs) specified in ISO/IEC 15418 AND ANSI MH10.8.2, in accordance with ISO/IEC 17360.
Since this scheme uses ANSI MH10.8.2 for the DI, the basic DI for identifying RTIs is "25B" of ANSI MH10.8.2.
The data following DI "25B" contain the Issuing Agency Code (IAC), Company Identification Number (CIN),
and Serial Number (SN) as determined in ANSI MH10.8.2. The RTIs are unique with the RTIs owner's
company code and serial number. The issuing agencies for the company codes that can be used here are
[16]
listed in the AIM global document: Register of Issuing Agency Codes for ISO/IEC 15459.
As an example, DI "25BUN0433257110000001" can be stored for RTIs.
"25BUN0433257110000001"
— "25B" DI
— "UN" IAC
— "043325711" CIN
— "0000001" SN
Table 2 shows an example of PC bits settings. Since the code system conforms to ISO/IEC 18000-63, the PC
bit address is set to 17 , and the numbering system identifier toggle (T) is set to 1 , to distinguish it from
h b
encoding conforming to the GS1 EPC Tag Data Standard (TDS). The AFI is A3 (1010 0011) selected from
h b
the ANSI MH10 DI standard, 6-bit compression of RFID for supply chain. The total data length of the 22-digit
6-bit code is 132 bits. 9 words (144 bits) are used as the data length is set in words. CRC-16 and PC bits data
are not included in the data length calculation.
Table 2 shows an example of PC bits using 6-bit UII encoding with DIs specified in ISO/IEC 15418 and ANSI
MH10.8.2, in accordance with ISO/IEC 17360 (see Annex B).
Table 2 — Example of PC bits for ISO/IEC 15418 and ANSI MH10.8.2 DIs: 6-bit UII encoding
Protocol control (PC) bits
...

ISO TR/DTR 24168:2026(E)
ISO/TC 122/WG 12
Secretariat: JISC
Date: 2026-06-0509-07
Packaging — Effective use of radio frequency tags on returnable
transport items (RTIs) to obtain information concerning goods on
or in RTIs
Draft Technical Report
Warning for WDs, CDs and DTRs
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to
change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.

i
ISO #####-#:####(X)
Emballage — Utilisation d'étiquettes à radiofréquence sur les emballages de transport réutilisables (RTI) pour
l'obtention d'informations relatives aux marchandises sur et dans les RTI
2 © ISO 2024 - All rights reserved

ISO/TRDTR 24168: 2026(E:(en)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilisedutilized otherwise in any form or by any means, electronic or mechanical, including
photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested
from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 -• Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Fax: [phone]
EmailE-mail: [e-mail]
Website: www.iso.orgwww.iso.org
Published in Switzerland
iii
ISO/TRDTR 24168: 2025(E:(en)
Contents
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 2
4 Business-to-business ordering and logistics . 3
4.1 Definitions of notations . 3
4.2 Flow of order receipt and delivery between organisations . 3
4.3 Importance of information in business-to-business logistics . 4
4.4 Information expected to be stored in the RF tag attached to the RTI . 5
5 Obtaining and using information from RF tags attached to RTIs . 8
5.1 Expectations for automation of information acquisition and on-site work efficiency . 8
5.2 Features and utilization of RF tag memory area . 8
5.3 Expected effects of using RF tags attached to RTIs as an information medium . 9
6 How to utilize RF tag memory . 10
6.1 Data storage in the UII . 10
6.2 Storing data in the USER . 11
7 Data structure . 11
7.1 General. 11
7.2 Memory structure . 11
7.3 Identification of RTIs . 12
7.4 Additional information encoding . 15
8 RF tag utilization model for RTI and demonstration experiment . 22
8.1 Scope of operation and demonstration model . 22
8.2 Results and issues for each demonstration model . 23
8.3 Summary and future work . 25
Annex A (informative) Demonstrations and results . 26
Annex B (informative) 6-bit encoding . 43
Annex C (informative) Data byte count-indicator for ISO/IEC 15434 messages. 44
Annex D (informative) RTI's operational model . 46
Annex E (informative) Appending and rewriting transient data . 50
Annex F (informative) Case studies with large amounts of information . 53
Annex G (informative) Role of the host system in utilizing RF tags for RTI . 57
Annex H (informative) Relationship between RTI owner and RTI management tag . 58
Annex I (informative) Identification of RTI using "ISO/IEC 15418 and ANSI MH10.8.2 DIs: UTF-8
8-bit UII encoding" in ISO/IEC 17360 . 59
Bibliography . 62

iv
ISO/TRDTR 24168: 2026(E:(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights
in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s)
which may be required to implement this document. However, implementers are cautioned that this may not
represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 122, Packaging.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
ISO/TRDTR 24168: 2025(E:(en)
Introduction
ISO/IEC 17360 provides permanent identification of returnable transport items (RTIs) and returnable
packaging items (RPI), which are both referred to as "RTI" in this document, using Radio Frequency
Identification (RFID). Associated information for purchasing, accounting or customs purposes is frequently
available via associated electronic data interchange (EDI). In practice, and for a number of reasons, many
logistics operations rely on a paper document for items slip, packing slip, bill of lading information. They also
rely on paper labels for physical distribution information. This is inefficient and labour intensive.
In the logistics field, it is important that packing details and work instructions are based on the latest
information. In such cases, it is more efficient if the relevant data are written in the radio frequency (RF) tag
on the RTI.
This document demonstrates how existing RFID technology can be used to electronically deliver the relevant
information written in the RF tag on the RTI that is accessible throughout the logistics supply chain.
This document providesdescribes a methodology to effectively use RF tags for identification in RTIs according
to existing standards (e.g. ISO/IEC 17360, ISO/IEC 18000-63).
Specifically, it shows how to write and rewrite goods data stored or loaded on RTIs. It also describesgives
examples of information to bethat is distributed to RF tags already attached to RTIs according to existing
standards. It also summarizes how to confirm effectiveness through several demonstration experiments.
vi
Packaging — — Effective use of radio frequency tags on returnable
transport items (RTIs) to obtain information concerning goods on or
in RTIs
1 Scope
This document specifiesdescribes methods of using the RF tag memory for identification of returnable
transport items (RTIs) or returnable packaging items (RPIs) to store and access supply chain logistics
information.
This document describescovers the following:
— information used in supply chain logistics scenarios;
— memory area usage and encoding;
— application modelmodels;
— feasibility study and results;
— some issues and future directions.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 445, Pallets for materials handling — Vocabulary
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabulary — Vocabulary
ISO 21067-1, Packaging — Vocabulary — Part 1: General terms
ISO 21067-2, Packaging — Vocabulary — Part 2: Packaging and the environment terms
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO 445, ISO/IEC 19762 and ISO 21067-
1 and ISO 21067-2 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— — ISO Online browsing platform: available at https://www.iso.org/obp
— — IEC Electropedia: available at https://www.electropedia.org/
3.1 Definition of terms
3.1
Terms and definitions
3.1.1
memory bank
MB
designated name of a segmented memory structure
Note 1 to entry: Four memory banks are defined for ISO/IEC 18000-63 compliant tags: have 4 (four) individually usable
memory banks, numbered Memory Bank 00 (MB00), Memory Bank 01 (MB01), Memory Bank 10 (MB10), and Memory
Bank 11 (MB11).
[SOURCE: ISO 20910:2019, 3.1]
3.1.13.1.2
serial number
SN
codes such as sequential numbers for uniqueness
Note 1 to entry: The structure of the serial number can be decided by the organisationorganization that is under the
control of the issuing agency. This is normally composed of an item number and its production number (serial number).
3.2 Abbreviated terms
CRC-16  16-bit cyclic redundancy check (CRC)
DSFID  data storage format identifier indicator
MB   memory bank
PC   protocol control
RESERVED reserved memory bank
UII   unique item
identifier memory bank
USER  user memory bank
CRC-16 16-bit cyclic redundancy check (CRC)
DSFID data storage format identifier indicator
MB memory bank
PC protocol control
RESERVED reserved memory bank
UII unique item identifier memory bank
USER user memory bank
4 Business-to-business ordering and logistics
4.1 Definitions of notations
4.1.1 Numeric notation
In this document, numerical values are represented as follows.
Binary numbers are written in Arabic numerals with the initial letter "b" for "binary" added as a subscript at
the end of the numerical notation. The upper digits are written from the left end, and the lower digits are
written from the right end. Each four digits are separated by a space and zero suppression (omitting the high-
order 0) is not used. For example, nnnn nnnn nnnn (n represents a variable).
b
Decimal numbers are represented numerically using Arabic numerals only, with no subscripts or symbols
indicating decimal numbers. In addition, every three digits from the least significant to the most significant
are separated by a space. For example, nn nnn nnn (n represents a variable).
Hexadecimal numbers are written using Arabic numerals from 0 to 9 and capital letters from A to F, with the
initial letter "h" for "hexadecimal" added as a subscript at the end. The higher value is written from the left
end, and the lower value is written on the right side. Each two digits are separated by a space and zero
suppression (omitting the high-order 0) is not performed. For example, nn nn nn (n represents a variable).
h
The same value can be expressed in binary, decimal, or hexadecimal as follows:
Binary:   0000 0001 1000 0001 1100 1101
b
Decimal:   98 765
Hexadecimal:  01 81 CD
h
Binary: 0000 0001 1000 0001 1100 1101
b
Decimal: 98 765
Hexadecimal: 01 81 CDh
4.1.2 Character notation
In this document, character strings that are treated as information for ID or article identification are enclosed
in double-quotation marks. For example, "25B". Then, for control characters used in character strings treated
as information, such as characters indicating group separation and characters indicating the end of
transmission, enclose the abbreviation of the control character in square brackets for each control character.
For example, "[GS]", "[EOT]". Blank spaces are indicated by "[]".
“25BTAJ70107010260960000000202211000001[GS]8D20221101100011[EOT] [EOT] [EOT]”
4.2 Flow of order receipt and delivery between organisations
Logistics between companies occurs because of the act of placing and receiving orders between two parties.
Specifically, the supplier such as a parts manufacturer, produces parts based on order information provided
by the ordering organisation, for example an assembly manufacturer acting as the client. The supplier stores
the parts in shipping cases, such as RTIs, and uses EDI for information exchange during this process. The parts
are then handled through inventory and cargo arrangement process before being shipped by the supplier to
the ordering organisation.
This procedure is the basic process unit of the flow of goods. These processes have connected each other from
the material procurement stage to the delivery stage to the end user, forming a supply chain. See Figure 1 and
Figure 2.
1 2
モモ モモモ モモ モ モモ モモ モ
Key
1 supplier: shipper, shipping source organisation that receives orders, prepares and ships the goods
2 client: consignee, shipping destination organisation that places the order and receives the goods
transportation
information or data transmission (e.g. EDI)
1 supplier: shipper, shipping source organisation that receives orders, prepares and ships the goods
2 client: consignee, shipping destination organisation that places the order and receives the goods
3 transportation
4 information or data transmission (e.g. EDI)
Figure 1 — Image of business-to-business logistics
4.3 Importance of information in business-to-business logistics
Within an organisationorganization, parts and products are usually stored in containers and loaded on pallets
after completion and then moved and stored in factories and warehouses. Typical forms and models of loading
are described in Annex D. Logistics between organisationsorganizations is also generally conducted in the
same manner. The containers and pallets used in this process are called RTI and are basically collected when
parts or products have been emptied and returned to the organisationorganization that owns the RTI. The
following three cases are expected for the owner (see Annex H):
— — Casecase 1: Suppliersupplier (e.g. parts manufacturer)
— Case);
— case 2: Orderingordering party (the client, e.g. assembly manufacturer)
— Case);
— case 3: Outsourcedoutsourced third party (who owns or provisions the RTI)).
In addition, a great deal of information is generated while receiving and placing orders, i.e. the manufacture
of products within a company, inventory, in-process logistics and inter-company logistics, etc., and various
operations are carried out on site, referencing or using this information.
Especially in the field of logistics, smooth shipment and delivery operations between
organisationsorganizations cannot be achieved without information on "stored items" and "number of items".
Such information indicates what items and how many items are loaded on RTIs (containers and pallets) used
for transportation. In addition, "logistics information" such as when and where to transport these items, is
also important.
Currently, most of this information is printed on paper media, such as “item slips”, “delivery notes” or “barcode
labels”, and is attached to, affixed to, or inserted into each transportation unit.
It is expected to carrythat information is carried when moving goods in inter-company logistics, and it is useful
to integrate goods and information.
Currently, paper forms are usually affixed or converted into machine-readable labels as a means of integration.
It is assumed that if RF tags attached to RTIs can take on this role, this will improve the efficiency of
information acquisition and human work.
4.4 Information expected to be stored in the RF tag attached to the RTI
4.4.1 General
4.4.11.1.1 General
This subclause provides an overview of the typical information that is used in a business-to-business logistics
scene, based on the premise that the information is stored in RF tags attached to RTIs and read at the location
where the information is to be used.
In this subclause, the logistics between organisationsorganizations are considered more concretely by
illustrating it, as shownillustrated in Figure 2. The flow is organized from the perspective of the ordering party
(the client or receiving party address nominated by the client) and clarifies the handling of RTIs and the
relevant information for each entity.
4.4.2 At the location of the supplier
The supplier, who is commonly the manufacturer, based on advance orders received or expected demand,
manufactures or otherwise obtains parts, etc. and stores them in RTIs in its warehousing. At this time, the
supplier affixes an in-house warehousing “actual product slip” that clearly indicates what kind of parts and
how many parts are stored.
When an order is received from an ordering party (the client), the ordered parts are provisioned by the
supplier and stored in units of RTIs among the stored products pending subsequent shipment area, and then
the order is picked and satiated. At that time, an “actual product slip” for the client is issued with order details
(e.g. parts part number, quantity) and the delivery address, etc., and is affixed to the RTI for shipment (and
any internal warehousing “actual product slips” removed from the RTI).
4.4.3 At the logistics provider (between the supplier and the client)
OnUpon collection from the supplier, at the supplier’s shipping point, the logistics provider checks the actual
product slip and other documents affixed to the RTI. The provider then loads the RTIs onto a means of
transport (e.g. truck, train, ship or aeroplane) and transports the order, together with the delivery note, to the
delivery destination designated by the ordering party (e.g. client).
4.4.4 At the location of the client (delivery destination upon receipt of the products)
The delivery location checks the delivery slip and the actual product slip with the actual products loaded in
the RTIs and enters each unit of RTIs into its warehousing. The information on the delivery note is added to
the warehouse inventory system. It is then referred to when the unit of RTI is picked and put into the
production line based on the production plan, and each part in the RTI is used in the product assembly process
(or forwarded to the next link in the logistics chain).

a) Onsite after the order receiver's b) Between client and supplier
c) Onsite after the acceptance of the products
arrival
Key
supplier 4 uniforms and shipping
Deleted Cells
A
Deleted Cells
Deleted Cells
B logistics provider 5 warehousing, uniforms,
shipping
b) Between client and supplier c) Onsite after the
Ca) Onsite after the order receiver's arrival 6
Deleted Cells
acceptance of the
products
1 Line off and storage 7 warehousing
2 warehousing 8 leaving the depot
3 ordering and shipping 9 parts input
Key
A supplier
B logistics provider
C client
1 line off and storage
2 warehousing
3 ordering and shipping
4 uniforms and shipping
5 warehousing, uniforms, shipping
6 acceptance
7 warehousing
8 leaving the depot
9 parts input
Figure 2 — Business-to-business logistics including logistics providers
Table 1shows lists the specific information which is generally used at each site for the inter-company logistics
mentioned in 4.3 which, and is read from the forms affixed to RTIs for various confirmations at each site.
Although this information does not cover everything, it is assumed that the integration of objects and
information will be realized when such information is stored in RF tags attached to RTIs.
Table 1 — Specific examples of information relevant to the location
loLcocatioant ion ssuupplpplieri er lologgististicsic ps provriodevrid er clcielient nt

receipt of unloading
manufacture warehousing shipping receipt unloadin acceptance assembly custody shipping
goods (cargo, etc.)
manufac warehous shippi acceptan assem custod shippi
information type
of g (cargo,
information type
ture ing ng ce bly y ng
ordering party part
goods etc.)
✓ ✓
number
ordering party
storage quantity ✓ ✓  ✓ ✓
✓ ✓
part number
ordering party part
✓  ✓ ✓
number
storage quantity
✓ ✓ ✓ ✓
quantity of containers to
✓ ✓ ✓ ✓
ordering party
be transported
✓ ✓ ✓
part number
recipient  ✓ ✓ ✓
acceptance Location  ✓ ✓ ✓
quantity of
delivery date and time  ✓ ✓ ✓ ✓
containers to be  ✓ ✓ ✓ ✓
order number  ✓  ✓
transported
product No.    ✓ ✓ ✓
recipient
✓ ✓ ✓
commodity code     ✓
acceptance
✓ ✓ ✓
location
delivery date and
✓ ✓ ✓ ✓
time
order number
✓  ✓
product no.
✓ ✓ ✓
Location supplier logistics provider client
receipt unloadin
manufac warehous shippi acceptan assem custod shippi
of g (cargo,
information type
ture ing ng ce bly y ng
goods etc.)
commodity code
✓
Table 1 provides basic information used by workers at each location to quickly identify and verify the cargo
or RTI being handled. However, the types of information vary depending on the industry, business type and
work activity, and are intended for reference purposes only.
As indicated by the checkmarks in Table 1, the relevant information varies from one location to another.
Therefore, only a subset of the information listed in Table 1 can be stored in the RF tag attached to the RTI.
However, the memory of the RF tag is expected to be rewritten as appropriate so that the information cacan
be made available from the RF tag at the intended location and time.
In addition, various types of related information not listed in Table 1 can also be relevant, and the amount of
information varies. Therefore, it is important to consider how the information is divided and stored in the
memory area of the RF tag.
5 Obtaining and using information from RF tags attached to RTIs
5.1 Expectations for automation of information acquisition and on-site work efficiency
In many cases, information on cargo loaded on RTIs is obtained by workers visually reading paper forms
affixed to the cargo, or by machine-reading labels converted into machine-readable symbols with a handheld
terminal or similar device. On the other hand, if relevant information can be automatically obtained from a
medium such as an RF tag attached to a predetermined position of RTI without human intervention, it is
expected to greatly improve the efficiency of on-site work and promote automation.
In addition, logistics companies, warehouses, distribution centres, and other logistics specialists other than
the ordering organisationorganization are also involved in business-to-business transportation. There are
many work environments where it is not possible to obtain logistics-related information on the cargo
transported by the ordering organisationorganization in advance or directly on site, nor via EDI. If it becomes
possible to obtain logistics-related information from RF tags attached to RTIs at such workplaces, this
information can be used to improve efficiency and automation.
For example, when transporting a unit load of containers on a pallet at a logistics site, the on-site worker
confirms the destination of the unit load, the number of containers on the pallet, the designated date of arrival,
and other information obtained from the RF tag on the pallet. In addition, the ordering
organisationorganization uses the information obtained from the RF tags of the containers loaded on the pallet
to check what kinds of goods are contained in the containers, how many goods are included, and to which
process the containers are towill be transported next. Based on this information, the transport operation is
automated.
By storing relevant information in RF tags attached to RTIs and automatically reading them, information can
be obtained and used effectively in various scenes of the work process, which is expected to contribute greatly
to efficiency.
5.2 Features and utilization of RF tag memory area
5.2.1 General
RF tags used for RTI permanent identification have UII and USER memory areas that contain information and
have the following characteristics as explained in 5.2.2:.
5.2.2 Characteristics of UII and USER
According to ISO/IEC 18000-63, the UII has a cyclic-redundancy check (CRC) checking mechanism to ensure
reliability. On the other hand, the USER does not have such a mechanism.
In the UII, the inventory command is issued to obtain stored data. In the USER, after issuing the inventory
command, the “Read” command is issued by specifying the RF tag for which a response is requested based on
the return data from the RF tag and specifying the size of data to be read. Because of this complexity, it
generally takes more time to obtain stored data from the USER than from the UII. On the other hand, USER
tends to have a larger capacity than the UII and has the advantage of storing more data. Therefore, the memory
size of the UII is small, but its reliability is high, and the reading time is short. The USER has a large memory
capacity and can store a lot of information, but it takes longer to load. It is important to allocate information
that takes advantage of these features.
5.2.3 Allocation and operation of information to be stored in the memory area
Some information is expected to be obtained in a short time (low latency) at the read location, while others
areother information is not. Considering these characteristics and the intended use at the location, it is
effective to use the UII and the USER separately to store information.
In this document, the information to be stored is classified into two types, “important data” and “general data”,
as follows:
— important data are stored in the UII, and
— general data are stored in the USER.
This concept was derived because ofdistinction arose from several demonstration experiments undertaken,
and , which are described in Clause 8 and Annex A. The characteristics of these different categories of data can
be summarised as:
a) Importantimportant data: Datadata that are the basis for other data, data that are used repeatedly in many
processes.;
b) Generalgeneral data: Datadata that are linked to important data and are not particularly sensitive to
reading latency.
ISO/IEC 17360 specifies that the RTI identification information is written in the memory area following the
PC bits in the UII area ((7.3). On the other hand, when important data are written in the UII, it is stored as
additional data following the RTI identification information (7.4(). “). Important data” are updated (revised)
from time to time.
The information items and data size to be handled will vary depending on the operations of the companies
that conduct the transactions.
While envisioning such an operational approach, this document examines the effectiveness of such an
approach by means of a demonstration experiment (see Annex A).
5.3 Expected effects of using RF tags attached to RTIs as an information medium
By using RF tags attached to RTIs as an information medium for business-to-business logistics, the following
various effects are expected.
a) a) LaborReduced labour or manpower savingworkforce: Reduction in the amount of work for on-site
workers, i.e. less information on paper to visually read and understand information on paper , or to input
relevant information into the system.
b) b) Information linkage with corporate systems: Information automatically obtained from RF tags can be
immediately linked to the related systems in the organisationorganization, enabling rapid response to the
processing of accepted RTIs and loads (e.g. inspection work, inventory control work) (see Annex G).
c) c) Reduction of work related to paper media and environmental considerations: This will reducereduces
the preparation and printing of paper media such as actual product slips and delivery slips, as well as the
collection and disposal of paper media.
d) d) Reduction of operational costs in the logistics chain: In an operation where physical and document
checks are performed each time, RF tags are used to store information items to be checked, enabling
automatic cross-checking, thereby minimizing the information to be checked by workers.
e) e) Customs clearance: In customs clearance of international logistics, it is important to distinguish
whether an RTI is an import and export product or simply a transport container, etc. By appropriately
storing information to be checked at customs clearance on the RF tag, it will complycomplies with the re-
import duty exemption procedures.
6 How to utilize RF tag memory
6.1 Data storage in the UII
When appending or rewriting a part of the UII in RF tags for RTI management, ISO/IEC 17360 specifies a
header area whose data identifier (DI) starts with “25B”. This area contains the data of the RTI and the owner
of the RTI, so “important data” can be written in the area following it, as shown in Figure 3.
Since the RF tag for RTI management is affixed to the RTI by the owner of the RTI, the RF tag also belongs to
the owner of the RTI. Therefore, for security reasons, the owner of the RF tag is also responsible for managing
the password when writing data. Since, in ownership Casecase 1 (described in 4.3), the RTI administrator
knows the access password for RTI management tags, suppliers can store data in RTI management tags. (
NOTE See Annex H for the relationship between ownership Casescases 1, 2 and 3 (described in 4.3) and RTI
management tags.). In ownership Casecase 2 and 3, suppliers can store data in RTI management tags where the owner
of the RTI tag is prepared to share its password with the supplier.
In business-to-business logistics, the time of storing products, etc. is the timing for writing important or
general data are written when products are loaded into an RTI (see Annex E). Therefore, writing or rewriting
these data at other places or timing is only possible where the password is shared.
UII area USER area
“25B” header area data area1 data area2 . data area1 data area2 .
DI IAC CIN SN . . . . . . .
25B UN 1‥ A1. . . . . . . .

Key
１ additions and rewritten portions of UII area

1 additions and rewritten portions of UII area
Figure 3 — Important data writing locations in the UII
6.2 Storing data in the USER
“General” data can be stored in the USER, using the methods specified in ISO/IEC 18000-63, and ISO/IEC
17360.
7 Data structure
7.1 General
The memory and data structures of the RFIDs used for validation in this document are defined in ISO/IEC
18000-63. The provisions of ISO/IEC 17360 are used for the data structures.
7.2 Memory structure
7.2.1 General
The memory structure of RFID specified in ISO/IEC 18000-63 has four memory banks (MBs). ):
— MB00: RESERVED
— MB01: UII
— MB10: TID
— MB11: USER
7.3This document describes the placing and use of identification information offor RTIs, while 7.4 and explains
additional information that can be stored in UII memory and USER memory in accordance withaccording to
the provisions of that memory structure. See ISO/IEC 18000-63 for more information on the functions of the
RESERVED and TID memory.
7.2.2 RESERVED memory bank (MB00)
The RESERVED memory is an area that stores the kill password and the access password. The kill password
functions to prevent the RF tag from being killed and the access password functions to prevent the data from
being rewritten.
7.2.3 UII memory bank (MB01)
The UII memory is an area for storing unique identifiers. The first word (16 bits) stores the CRC-16, which has
the function of determining if there is an error in communication, and the next word is a dedicated area where
“StoredPC” is stored (this area is hereinafter referred to as "PC bits"). The UII data are stored in the area
following the “PC bit” area. The extended PC bits are then stored in MB 01 at addresses 210h to 22Fh
(“StoredPC” is defined in ISO/IEC 18000-63).
When the code system conforms to ISO/IEC 18000-63, the Application Family Identifier (AFI) registration
contents define the data structure, bit compression method, and format of the UII memory, and these
registration contents are specified in AIM global document: ISO/IEC 15961-2 Data ConstructsApplications
[15]
Family Identifier (AFI) Assignments Register.
The PC bits define only UII memory, not USER memory.
7.2.4 TID memory bank (MB10)
The TID memory stores the class identifier defined in ISO/IEC 15963-1: the custom commands and optional
functions specified by the registrar defined by the value of the class identifier and uniquely identifiable
information. The TID memory is permanently locked at the time of RF tag IC manufacturing.
7.2.5 USER memory bank (MB11)
When storing data in ISO/IEC 15962 format, the first 16 bits are dedicated to the “Data storage format
identifier” (DSFID) and pre-cursor, and store the USER data access method, format, data compression method,
and format information. Depending on the RF tag type, some RTI ID tags cannot support USER memory.
7.3 Identification of RTIs
Identification information for RTIs can be stored in UII memory using ISO/IEC 17360 and ISO/IEC 15418
(ANSI MH10.8.2)6-bit UII encoding with Data Identifiers (DIs): Monomorphic 6-bit UII encoding. An example
of encoding UII using Monomorphic UTF-8 is shown) specified in .ISO/IEC 15418 AND ANSI MH10.8.2, in
accordance with ISO/IEC 17360.
Since this scheme uses ANSI MH10.8.2 for the DI, the basic DI for identifying RTIs is "25B" of ANSI MH10.8.2.
The data following DI "25B" will contain the Issuing Agency Code (IAC), Company Identification Number (CIN),
and Serial Number (SN) as determined in ANSI MH10.8.2. The RTIs will beare unique with the RTIs owner's
company code and serial number. The owner of the RTIs can use their own company code issued by theThe
issuing authority. The issuing agencyagencies for the company codes that can be used here can be foundare
listed in the list at AIM global document: Register of issuing agency codesIssuing Agency Codes for ISO/IEC
[16]
15459. .
As an example, store DI "25BUN0433257110000001" can be stored for RTIs.
"25BUN0433257110000001"
— "25B"   DI
— "UN"   IAC
— "043325711"  CIN
— "0000001"  SN
— "25B" DI
— "UN" IAC
— "043325711" CIN
— "0000001" SN
Table 2 shows an example of PC bits settings. Since the code system conforms to ISO/IEC 18000-63, the PC bit
address is set to 17 , and the numbering system identifier toggle (T) is set to 1 , to distinguish it from encoding
h b
conforming to the GS1 EPC Tag Data Standard (TDS). The AFI is A3 (1010 0011) selected from the ANSI
h b
MH10 DI standard, 6-bit compression of RFID for supply chain. The total data length of the 22-digit 6-bit code
is 132 bits. 9 words (144 bits) are used as the data length is set in words. CRC-16 and PC bits data are not
included in the data length calculation.
Table 22 shows an example of PC bits using 6-bit UII encoding with DIs specified in ISO/IEC 15418 (and ANSI
MH10.8.2) DIs: Monomorphic 6-bit UII encoding , in accordance with ISO/IEC 17360 (see Annex B).

Table 2 — Example of PC bits for ISO/IEC 15418 Dis: Monomorphicand ANSI MH10.8.2 DIs: 6-bit UII
encoding
Protocol control (PC) bits
a
RFU (T = 0 , EPC format)
b
UII data length
Function UMI XI T
words
AFI (T = 1 , ISO format)
b
MB01
b
10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
h h h h h h h h h h h h h h h h
Address
Value 0 1 0 0 1 0 0 1 1 0 1 0 0 0 1 1
b b b b b b b b b b b b b b b b
Key
UMI User memory indicator
XI XPC indicator
T Numbering system identifier toggle
RFU Reserved for future use
AFI Application family identifier
a
UII data length stores the data length of UII data except CRC-16 and PC bits in UII memory in
word units. 1 word is 16 bits.
— Address 10 - 14 UII data length: 0 1001 (0 1001 , 9 words, 144 bits)
h h b b
— Address 15h  User memory indicator: 0b (no user memory)
— Address 16  XPC indicator: 0 (no XPC)
h b
— Address 17  Numbering system identifier toggle: 1 (ISO
h b
coding scheme)
— Address 18 - 1F Application family identifier: 1010 0011 (A3)
h h b h
Protocol control (PC) bits
RFU (T = 0b, EPC format)
a
Function UII data length words UMI XI T
AFI (T = 1b, ISO format)
MB01
b
10h 11h 12h 13h 14h 15h 16h 17h 18h 19h 1Ah 1Bh 1Ch 1Dh 1Eh 1Fh
Address
Value 0 1 0 0 1 0 0 1 1 0 1 0 0 0 1 1
b b b b b b b b b b b b b b b b
Key
UMI User memory indicator
XI XPC indicator
T Numbering system identifier toggle
RFU Reserved for future use
AFI Application family identifier
UII data length stores the data length of UII data except CRC-16 and PC bits in UII memory in word units. 1
a
word is 16 bits.
— Address 10 - 14 UII data length: 0 1001 (0 1001 , 9 words, 144 bits)
h h b b
— Address 15h User memory indicator: 0b (no user memory)
— Address 16 XPC indicator: 0 (no XPC)
h b
— Address 17 Numbering system identifier toggle: 1 (ISO coding scheme)
h b
— Address 18 - 1F Application family identifier: 1010 0011 (A3)
h h b h
The PC bits in Table 2 are followed by "25BUN0433257110000001[EOT]", which is encoded according to
Table B.1. The remainder of the specified length be filled by encoding [EOT].
An example of 6-bit encoding is shown in Table 33.
Table 3 — Example of 6-bit UII encoding
Character "2" "5" "B". "U" "N" "0".
Encoding value 11 0010b 11 0101b 00 0010b 01 0101b 00 1110b 11 0000b
Character "4" "3" "3" "2" "5" "7"
Encoding value 11 0100 11 0011 11 0011 11 0010 11 0101 11 0111
b b b b b b
Character "1" "1" "0". "0". "0". "0".
Encoding value 11 0001 11 0001 11 0000 11 0000 11 0000 11 0000
b b b b b b
a a
Character "0". "0". "1" "[EOT]" "[EOT]" "[EOT]"
Encoding value 11 0000 11 0000 10 0001 10 0001 10 0001 10 0001
b b b b b b
a Last two [EOT] characters of the data are padding data.
7.4 Additional information encoding
7.4.1 General
A.1.1.1 General
This subclause describes how to store valid information other than RTIs identification information
(“Important” and “General” information) in the memory of RF tags for RTIs in
...