Overview
ISO/IEC 29161:2016 - Information technology - Data structure - Unique identification for the Internet of Things - defines a universal unique identification (UI) scheme for the Internet of Things (IoT). The standard establishes common rules to ensure full interoperability across different identity systems so that any physical object, virtual object, or person can be unambiguously identified in IoT information systems. It is media-agnostic and intended for use with any IoT communication interface (RFID, QR codes, sensors, IP-based protocols, etc.).
Key technical topics and requirements
- Universal construct for entities: Treats “thing”, “item”, “object” and “entity” synonymously and covers people, locations, devices, software and virtual objects.
- Unambiguous wrapper: Requires the use of a Uniform Resource Identifier (URI) as an “unambiguous wrapper” for identifiers (URI per IETF RFC 3986). URNs are the preferred mechanism for wrapping existing identifier schemes where needed.
- Support for existing identifier schemes: Enables interoperable use of pre-existing identification formats (AIDC, EPC, OID structures) by combining them inside a common wrapper so different identity domains can be mixed in a single message.
- URN namespaces and examples: Recognizes widely used URN namespaces (for example urn:epc and urn:oid:1.0.sssss) and recommends using registered URN schemes from the IANA registry when available.
- Encoding and use: Addresses UI concept and encoding rules for IoT messages, and includes informative annexes on URI usage with ISO/IEC JTC 1/SC 31 standards, OID wrappers, sensor networks and identification ontologies.
- Interoperability focus: Emphasizes portability, ASCII-based syntax, and compatibility across network and supply-chain perspectives.
Practical applications and target users
ISO/IEC 29161 is practical for:
- IoT architects and system integrators designing cross-domain identity solutions.
- Device and tag manufacturers (RFID, NFC, QR code producers) who must embed interoperable identifiers.
- Software developers and API designers implementing IoT messaging, registries or lookup services.
- Supply chain, asset management and logistics teams that need reliable item, sensor and gateway identification.
- Standards bodies and implementers who map legacy identifier schemes (EPC, OIDs, AIDC) into modern IoT applications.
Common use cases:
- Sensor networks and telemetry where sensor, node, gateway and item IDs must be correlated.
- Mixed-media scenarios (RFID + QR + IP) where identifiers from multiple domains are combined in a single transaction.
- Asset tracking, smart retail/minibar scenarios, location-based services, and identity resolution for IoT resources.
Related standards (as referenced)
- ISO/IEC 15459 series (AIDC unique identification)
- ISO/IEC 15961, 15962 (RFID data objects)
- RFC 3986 (URI), RFC 5134 (urn:epc), RFC 3061 (urn:oid)
- ITU-T X.660 / X.668 (OID/URN foundations)
- ISO/IEC 19762 (terms and definitions)
Keywords: ISO/IEC 29161, IoT unique identification, URI, URN, IoT identifiers, AIDC, EPC, OID, interoperability, device identification.