← Back to the chapter · Next detail →
Technical detail · CoAP Observe: Subscriptions and Updates
Modelled polling and Observe traffic over 24 hours
For a temperature resource, polling repeats read requests while CoAP Observe registers a continuing read request so the server can send later updates called notifications.
A lossless temperature-monitoring model assumes 16-byte requests and 28-byte responses. Over 24 hours, polling every 60 seconds creates 1,440 requests and 1,440 responses. Observe with 10 changes per hour creates a registration request, an initial response, and 240 later notifications: 242 messages.
The resulting counts are 63,360 bytes for polling and 6,764 bytes for Observe, about 89.3% fewer modelled bytes. These example sizes exclude UDP/IP, security, acknowledgements (receipt replies), retries, cancellation, and recovery. Radio wake costs and other device work also matter. This comparison cannot establish battery life.