← Back to the chapter · Next detail →

Technical detail · IoT Glossary: G-H

Messages, roles, and acknowledgement limits

Under the hood, several G-P terms sound interchangeable because they all move data. A packet is a network-layer or link-layer unit with headers and size limits. A payload is the application data carried inside an envelope. Metadata describes context around the payload, such as timestamp, gateway id, quality flag, spreading factor, RSSI, schema version, or tenant. A message may include payload plus headers, topic, properties, and broker state. Mixing those terms makes debugging harder because the missing field may not be in the place the report claims it is.

Gateway, router, middleware, and platform also overlap in everyday speech. A router forwards packets between networks. A gateway may translate protocols, buffer offline telemetry, map local identities to cloud identities, normalize timestamps, run rules, and manage credentials. Middleware may transform messages or coordinate services without owning the whole device lifecycle. A platform may own registry, policy, storage, analytics, command routing, and operational workflows. One physical box or cloud product can contain several roles, so the report should name the role being tested rather than only the product name.

Messaging terms hide guarantee boundaries. An MQTT publisher can send at QoS 0, QoS 1, or QoS 2, but the broker’s acknowledgement is not the same as a database write or operator action. A retained message may be useful for last-known state and dangerous when old state looks current. Wildcard topic filters make subscribers powerful and risky. HTTP status codes can confirm that an API accepted a request, but they do not prove that downstream analytics, alerting, or dashboard refresh completed unless those states are separately inspected.

← Back to the chapter · Next detail →