Overview
ISO/IEC 30181:2024 specifies a functional architecture and requirements to enable resource identifier interoperability across heterogeneous Internet of Things (IoT) platforms. The standard defines an IoT Resource Name System (RNS) that converts and maps resource identifiers and resource paths (for example URIs) so devices, services and applications built on different IoT platforms can discover and request the same resources without duplicating ontologies or platform-specific integrations.
Key capabilities described include resource registration and deletion, discovery services, path conversion, and mapping/management of resource IDs to support cross‑platform access. The document is intended for use at middleware or edge layers to facilitate interoperability between platforms such as oneM2M, GS1, IBM Watson IoT, OCF/IoTivity and FIWARE (examples appear in informative annexes).
Key topics and technical requirements
- IoT RNS architecture: functional components, metamodel and sequences/algorithms for ID/path conversion and lookup.
- Interoperability requirements: uniqueness, equality, persistency, scalability, and security of resource identifiers across platforms.
- Resource lifecycle functions: registration, deletion, discovery, mapping table management and path conversion.
- Format analysis: comparative formats and examples of resource identifier schemes across multiple IoT platforms (informative annexes).
- Edge/middleware deployment: guidance for modularizing RNS in edge computing or gateway layers to support local conversions and reduce latency.
- Sequence and algorithm descriptions: procedure-level guidance for converting resource requests and reconfiguring resource paths between platforms.
Applications and who uses it
ISO/IEC 30181 is practical for:
- IoT platform vendors who need to expose or consume resources across other ecosystems.
- System architects and integrators building cross‑platform solutions (smart cities, healthcare, logistics, smart buildings, industrial IoT).
- Middleware and edge developers implementing gateway-level RNS services for device-to-cloud translation.
- City planners and solution providers deploying multi-vendor smart city services that require resource discovery and reuse.
- Standards bodies and interoperability labs validating cross-platform ID mapping approaches.
Typical use cases: converting URIs between platforms during discovery, sharing mapping tables for device/resource lookup, reconfiguring resource requests when forwarding between heterogeneous systems.
Related standards
- ISO/IEC 30141 - IoT reference architecture (referenced for interoperability context)
- IEC 61406-2 - requirements for globally unique identification
- ISO/IEC TR 30164 - edge computing concepts and deployment considerations
Keywords: ISO/IEC 30181, IoT resource identifier, resource ID interoperability, IoT RNS, resource path conversion, heterogeneous IoT platforms, URI conversion, smart city interoperability.