Mesh Network
A network topology where devices connect to multiple neighbors, each device able to relay data for others. Creates resilient, self-healing networks that continue operating if individual devices fail. Used in some RTLS implementations for extended coverage and redundancy. Particularly valuable in ad-hoc mode deployments.
Network topology where devices communicate peer-to-peer, each node forwarding data for others, creating self-healing network without centralized infrastructure dependency. Mesh networking technologies: Zigbee (802.15.4-based, common in industrial sensors and control), Thread (IPv6-based mesh for IoT), Bluetooth Mesh (designed for lighting and building automation), and proprietary protocols (vendor-specific implementations). In RTLS context, mesh networking used primarily for: (1) Infrastructure communications - anchors/gateways forming mesh network for data backhaul where wired Ethernet impractical (though wired preferred when available). (2) Extended coverage - mesh tags relaying signals from other tags in coverage gaps, though this rarely used for positioning due to complexity. (3) Sensor networks - environmental sensors in mesh communicating through RTLS infrastructure. Mesh challenges for RTLS: (1) Positioning complexity - mesh topology with variable paths complicates time-based positioning (TDoA requires known paths and delays). (2) Latency variability - multi-hop routing introduces variable delays (problematic for time-critical applications like collision avoidance). (3) Capacity limitations - each hop consumes bandwidth and processing (limiting scalability compared to star topology with central coordination). (4) Power consumption - relaying others' messages drains battery (mesh nodes typically requiring mains power). (5) Network management - mesh topology discovery, route optimization, and troubleshooting more complex than star topology. Industrial RTLS implementations typically favor infrastructure mode (star topology with fixed anchors) over mesh for: predictable performance (deterministic latency and capacity), simplified management (centralized configuration and monitoring), better positioning accuracy (known fixed infrastructure positions), and higher reliability (redundancy through multiple fixed anchors vs. dependency on peer nodes).