ISO/IEC 24730

An international standard for real-time locating systems defining air interface protocols, system architecture, and performance testing methods. Provides standardized framework for RTLS implementations ensuring interoperability and performance consistency. Parts include requirements for 2.4 GHz, UWB, and other frequency bands. Important reference for industrial RTLS deployments.

International standard for real-time locating systems defining interfaces, protocols, and test methods. ISO/IEC 24730 consists of multiple parts: Part 1 (Application Programming Interface), Part 2 (2.4 GHz Air Interface), Part 5 (Chirp Spread Spectrum Air Interface), Part 61 (Low Rate Pulse Repetition Frequency UWB Air Interface), and Part 62 (High Rate Pulse Repetition Frequency UWB Air Interface). Standard addresses: air interface specifications (defining radio communications between tags and infrastructure), API definitions (standardizing software interfaces to RTLS data), test methods (procedures for verifying performance), and conformance requirements (minimum specifications for standards compliance). ISO/IEC 24730 benefits include: vendor interoperability (theoretically enabling tags from one vendor to work with infrastructure from another), procurement clarity (specifying standards compliance in requirements), and performance comparison (standard test methods enabling objective vendor comparisons). However, standard adoption limited in industrial RTLS: many vendors use proprietary protocols for performance advantages, standard focuses primarily on 2.4 GHz technologies (less relevant for UWB), and achieving true interoperability requires more than air interface standardization (positioning algorithms, data formats, system integration). More influential standards in modern industrial RTLS: IEEE 802.15.4z (UWB PHY/MAC), FiRa specifications (UWB interoperability), and Bluetooth 5.1+ (direction finding). ISO/IEC 24730 more relevant in: government/military procurement (mandating open standards), healthcare (multi-vendor RTLS deployments), and situations requiring future-proofing (avoiding vendor lock-in). For most industrial applications, proprietary vendor solutions offer better performance than standards-compliant approaches, though this may change as standards mature and adoption increases.