Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29173-1 — Information Technology — Mobile Item Identification — Part 1: Framework
Enabling Ubiquitous Identification of Mobile Objects in IoT Environments
Overview of ISO/IEC 29173-1
ISO/IEC 29173-1 establishes a framework for identifying mobile items — physical or digital objects whose location or affiliation changes over time. This includes items in logistics supply chains, returned assets in rental ecosystems, portable medical equipment in hospitals, and tools on construction sites. The standard defines an identifier structure, a resolution infrastructure, and a set of protocols for discovering and communicating with mobile items as they move across organizational boundaries.
The standard adopts a hierarchical identifier scheme based on ISO/IEC 15459 (unique identifiers for transport units) and extends it with mobile-specific attributes such as location history, ownership chain, and service context.
Mobile item identification poses unique challenges compared to stationary item identification: identifiers must remain valid as items cross administrative domains, the resolution system must handle frequent location updates, and the identification scheme must support both human-readable and machine-readable representations (barcodes, RFID, NFC, QR codes). ISO/IEC 29173-1 addresses these challenges by specifying a three-part identifier: a fixed global company prefix, a mobile item class identifier, and a serial number with embedded security features to prevent counterfeiting.
Implementing ISO/IEC 29173-1 enables end-to-end visibility across the mobile item lifecycle — from manufacturing through distribution, rental, maintenance, and eventual retirement — without requiring a single centralized database.
Architecture and Identifier Structure
The mobile item identification architecture defined by ISO/IEC 29173-1 comprises three tiers: the identifier namespace tier, the resolution tier, and the discovery tier. The identifier namespace assigns globally unique identifiers to mobile items. The resolution tier maps identifiers to current item data through a distributed resolution system analogous to DNS. The discovery tier enables applications to locate items based on attributes rather than pre-known identifiers, supporting ad-hoc interaction in IoT scenarios.
| Tier | Component | Protocol | Example |
|---|---|---|---|
| Identifier Namespace | ID format, prefix allocation | ISO/IEC 15459-2 | Company prefix: 0-123-4567 |
| Resolution | ID-to-data mapping service | ONS (Object Naming Service) / HTTP | Lookup by 16-digit UII |
| Discovery | Attribute-based item search | EPCIS / DS (Discovery Services) | Find all items by manufacturer |
The resolution service is a critical infrastructure component. ISO/IEC 29173-1 recommends operating redundant resolution servers across at least two geographic regions and using DNSSEC-style signing to authenticate resolution responses against spoofing and cache poisoning attacks.
The identifier itself is a variable-length string with a maximum of 64 characters, encoded in UTF-8 for maximum interoperability. It begins with a 3-digit issuing agency code (e.g., 012 for GS1), followed by a company prefix, an item class code, and a unique serial number. The serial number includes a check digit computed using the Luhn algorithm to detect common transcription errors. For RFID implementations, the identifier maps directly to the EPC (Electronic Product Code) Tag URI scheme defined by GS1.
Engineering Implementation and Use Cases
Deploying an ISO/IEC 29173-1-compliant identification system requires integration with existing enterprise resource planning (ERP) and warehouse management systems (WMS). At minimum, organizations must implement an identifier allocation service that issues compliant IDs from their allocated prefix range, a resolution endpoint that returns current item state, and a discovery interface for attribute-based queries. The standard provides XML and JSON schemas for resolution responses as well as REST API bindings for modern cloud-native architectures.
One of the most common implementation failures is neglecting identifier lifecycle management. When a mobile item is retired or recycled, its identifier must be decommissioned in the resolution system to prevent confusion with newly manufactured items. A minimum retention period of five years after decommissioning is recommended for audit trail integrity.
In the healthcare sector, mobile item identification is used to track infusion pumps, ventilators, and defibrillators as they move between departments and external service providers. The standard’s support for attaching contextual metadata enables clinicians to verify calibration status, maintenance history, and sterilization cycles before equipment use. In logistics, the identification framework underpins automated sortation, cross-docking coordination, and last-mile delivery tracking, significantly reducing manual scan operations and associated error rates.
Frequently Asked Questions
Q: How does ISO/IEC 29173-1 relate to GS1 standards?
A: ISO/IEC 29173-1 is compatible with GS1 identification standards. It uses GS1 company prefixes as the basis for its identifier allocation and aligns with the EPC Tag URI scheme for RFID implementations.
Q: Is the resolution system required to be globally centralized?
A: No. The resolution system is designed as a federated architecture. Each organization operates its own resolution server for items under its management, and global resolution chains servers through referral pointers, analogous to DNS delegation.
Q: What security measures are specified for mobile item identification?
A: The standard recommends digital signatures on identifier metadata, TLS encryption for resolution queries, access control on discovery services, and optional anti-counterfeiting fields in the serial number using cryptographic check values.
