← Back to the chapter · Next detail →
Technical detail · Network Simulation: Tool Landscape
Timing, loss, and protocol settings behind the result
For MQTT, session expiry controls how long a broker retains a disconnected client’s session; QoS sets message delivery and acknowledgement behavior. Record both when reconnect recovery or delivery guarantees affect the decision. Retained messages are the broker’s saved latest value for a topic, and keepalive is the interval used to detect a dead connection.
TLS resumption reuses information from an earlier secure connection to make a later handshake faster; include it when reconnect time or device energy matters. Broker throttling limits how quickly or how many messages a broker accepts or forwards, so include its configured limits when testing burst load or recovery after an outage. CoAP confirmable retransmission, TCP reconnect timing, and the other protocol settings should likewise be recorded when they can change the result.
The hidden mechanism is usually timing and loss. Simulators generate events from configured distributions; packet captures depend on timestamp accuracy and capture placement; RF surveys depend on antenna orientation and environmental state; gateway dashboards depend on aggregation windows; and pilots depend on who installed, provisioned, powered, and maintained the devices. A result that looks authoritative can still be wrong for the decision if one of those mechanisms is outside the tool. That is why the validation step should attack the riskiest assumption first. Compare a modelled delivery ratio with gateway counters, compare a simulated retry burst with packet traces, compare an RF prediction with measured RSSI/SNR, and compare firmware sleep-state assumptions with current traces or device logs.
- Input boundary: Topology, traffic distribution, radio model, firmware path, queue policy, sampling interval, and outage scenario.
- Observation boundary: Capture point, clock sync, antenna, channel, test duration, pilot size, and log-retention window.
- Decision boundary: The exact design choice the tool can support and the residual risk that still needs field validation.