← Back to the chapter · Next detail →

Technical detail · IoT Glossary: A

What a protocol or data term actually guarantees

5.3.1 Words Hide Protocol Scope

Under the hood, many A-F terms look similar because they are often described with short textbook phrases. The implementation scope is what separates them. An ACK can mean a TCP segment arrived, a CoAP confirmable message was received, an AMQP broker accepted a delivery, or an application command was processed. Those events sit at different layers and give different guarantees. A report that only says “the ACK was received” has not yet named the contract.

Exactly-once is another scope-sensitive term. It may describe stream-processing state inside a broker, idempotent application writes, deduplicated storage commits, or a transaction boundary. It rarely means that every physical sensor event is acted on exactly once across device resets, retries, network partitions, and dashboard refreshes. At-least-once and at-most-once also need a boundary: packet delivery, broker acceptance, database row, command execution, or user-visible state.

Security terms hide similar scope. DTLS protects UDP traffic, but endpoint validation, key rotation, certificate expiry, authorization, logging, and recovery remain separate design decisions. Encryption can protect bytes while metadata, topic names, timestamps, or access policies still leak operational meaning. A certificate can establish a trust chain while a misconfigured ACL still grants the wrong device action.

Architecture terms hide ownership. Edge computing may reduce latency and bandwidth, but it also moves update, observability, and failure-recovery responsibilities closer to the device. Fog computing may coordinate several local nodes, but it still needs a contract for cloud sync and local fallback. Cloud may simplify storage and dashboards, but it introduces dependency on identity, quota, retention, network reachability, and service-owner response.

Data representation terms hide one more layer of scope. CBOR can reduce payload size, but it does not define units, calibration, retention, or semantic validity. Compression can shrink a signal while making local inspection harder. Aggregation can stabilize dashboards while erasing spikes that matter for safety or maintenance. The technical term is therefore only complete when the report names what evidence survived the transformation.

← Back to the chapter · Next detail →