← Back to the chapter · Next detail →
Technical detail · IoT Edge Models: Cold-Chain Processing
Latency and bandwidth placement
18.7 Latency vs Bandwidth Matrix
Latency sensitivity and data volume are separate reasons to process locally. An urgent control loop needs a bounded elapsed path even if its messages are small. A high-volume stream can need local reduction even when its analysis tolerates delay. The processing table therefore pairs sub-second control with edge placement and minutes-to-hours reporting with cloud placement, while separately considering high-frequency raw streams and pre-aggregated summaries.
For the cold chain, the modeled cloud delay is about 3.7 seconds and the local condition is about 3 seconds. Both fit the nominal 30-second scenario deadline while connectivity is available. The decisive difference during a dead zone is that the local condition remains evaluable. Remote delivery of the resulting alert is a separate part of the path.