← Back to the chapter · Next detail →

Technical detail · IoT Glossary: Q-R

Guarantees stop at layer boundaries

Under the hood, Q-Z terms often fail when a guarantee is stretched beyond its layer. MQTT QoS 1 confirms a broker delivery handshake, but a subscriber may still process the same payload twice. MQTT QoS 2 narrows a duplicate path inside MQTT, but it does not prove that storage, alerts, or physical actuators are exactly once. A retained message can be useful for last-known state and dangerous when old state appears current after a reboot. Wildcard subscriptions can simplify monitoring and accidentally cross tenant, device, or command namespaces.

TLS and token terms stop at their own boundaries too. TLS can authenticate the endpoint and protect bytes in transit, but it cannot decide whether a device is allowed to publish to a topic unless an authorization layer checks that policy. A token may authorize an API call, but it does not prove sensor calibration, payload truth, or device possession unless it is combined with device identity. Bad clocks can break certificate validity and token expiry checks, so time synchronization becomes part of security evidence.

Data terms hide another boundary. A timestamp may be generated by the sensor, gateway, broker, ingestion service, database, or dashboard. Each choice changes ordering and incident reconstruction. Schema validation can reject malformed data, but it cannot prove units, calibration, or semantic truth. Downsampling can make long-term dashboards efficient while deleting spikes that matter for safety, warranty, or maintenance. TSDB compression and retention policies therefore belong in the engineering argument, not in a footnote.

Wireless and adaptation terms hide state that is easy to miss. Thread and Zigbee meshes depend on router roles, neighbor tables, link quality, and channel planning. Z-Wave behavior depends on regional frequencies, inclusion security, and network healing. 6LoWPAN compresses IPv6 headers and fragments packets across small IEEE 802.15.4 frames; losing one fragment can lose the whole IPv6 packet. Wi-Fi has familiar IP behavior but higher idle listening costs and shared-channel contention. Sigfox and other narrowband options constrain payload size, downlink, and regional service availability.

A rigorous Q-Z explanation names both the useful guarantee and the stop sign. QoS helps broker delivery but stops before application idempotency. TLS protects transport but stops before authorization and operations. TSDB stores time-indexed rows but stops before proof that the signal was sampled correctly. Thread or Zigbee helps low-power mesh behavior but stops before evidence that the actual deployment has healthy routes.

← Back to the chapter · Next detail →