← Back to the chapter · Next detail →

Technical detail · CoAP Observe: Efficiency and Lifecycle

Components of an 18-byte Observe notification

A CoAP Observe traffic model estimates the bytes sent when a server notifies registered clients of resource updates.

A Token is the request identifier echoed in responses. The notification model counts a 4-byte CoAP header, a 2-byte Token, a 3-byte Observe option, 2 bytes for Content-Format, which identifies the payload’s data format, a 1-byte payload marker, which marks the start of message content, and the assumed 6-byte payload. An option carries protocol metadata. Those components produce the assumed 18-byte notification.

Count acknowledgements according to the selected message type. A NON notification is nonconfirmable and expects no acknowledgement. A CON notification is confirmable and requires an acknowledgement, or ACK, which confirms receipt. Neither message type proves that a commanded lamp performed an action. A temperature-traffic comparison cannot establish a lamp command’s outcome.

← Back to the chapter · Next detail →