Network Bandwidth

The data transmission capacity available for RTLS communication, measured in bits per second or packets per second. Requirements depend on tag count, update rates, and data payload size. Insufficient bandwidth causes delays, data loss, and system instability.

Data transmission capacity of network infrastructure connecting RTLS components, measured in bits per second. RTLS bandwidth requirements vary by architecture: (1) Raw measurement transmission - anchors sending raw signal measurements to central processor require substantial bandwidth (100-1000 bytes per tag update, multiplied by anchor count and tag count, typical facility: 4-8 anchors each detecting 200-500 tags at 1 Hz = 1-10 Mbps). (2) Computed position transmission - systems performing edge processing transmit only computed positions (50-200 bytes per tag, typical facility 500 tags at 1 Hz = 0.1-1 Mbps). (3) Historical data queries - retrieving large datasets for analytics (90 days of data for 1000 tags = 100-500 GB requiring gigabit connectivity for reasonable transfer times). Bandwidth calculation example: 1000 tags updating 1 Hz, 150 bytes per position update, transmitted from edge processor to central server = 1000 tags × 1 Hz × 150 bytes = 150 KB/s = 1.2 Mbps, plus overhead (protocols, retries, status) suggesting 2-3 Mbps allocation. Industrial facilities typically use: Gigabit Ethernet backbone (1000 Mbps) connecting edge servers and central systems, providing ample headroom. 100 Mbps Ethernet typically sufficient for individual edge processors. Bandwidth planning considerations: (1) Peak vs. average - design for peak concurrent tag counts (all tags active simultaneously), not averages. (2) Growth headroom - provision 2-3x current requirements for expansion. (3) Non-RTLS traffic - account for other facility network usage. (4) Redundancy - backup network paths for critical functions.

Monitoring network utilization ensures adequate capacity: sustained utilization above 70-80% suggests approaching capacity limits.