← Back to the chapter · Next detail →

Technical detail · Network Simulation: Claims and Scenarios

Preserve the mechanism behind the tail

In OMNeT++, a NED topology describes the network modules and their connections. In Cooja, a mote is a modeled sensor node running firmware. Preserve these definitions and builds so another reviewer can reconstruct the run.

The scenario pack should preserve enough state to explain those tails. Network state includes topology, queue policy, retry timer, route repair, airtime, channel occupancy, packet size, and gateway backhaul. Device state includes sleep schedule, firmware version, buffer size, sample interval, watchdog reset, and power mode. Measurement state includes clock sync, capture point, pilot size, RF condition, and log-retention window. In ns-3, that may mean preserving helper configuration, mobility or propagation assumptions, packet traces, and random seeds. In OMNeT++/INET, it may mean NED topology, ini parameters, result filters, and module versions. In Cooja, it may mean mote firmware commits, radio medium, serial logs, and packet captures.

In an RPL mesh, a connected non-root node chooses a preferred parent for upward traffic toward the root. Downward routes use separate mechanisms. When a route fails, repair can find a usable path again; parent choice and repair can change delay and loss. The under-the-hood review asks whether the mechanism that controls the decision is visible. If a LoRaWAN result depends on path loss, spreading factor, duty cycle, or downlink scarcity, the pack should expose those inputs and plan an RF or gateway-log check. If a mesh result depends on RPL repair, parent choice, or 802.15.4 interference, the pack should preserve route-change evidence and not only final delivery ratio. If an application result depends on MQTT session behavior, CoAP retransmission, TCP reconnect, or TLS handshake cost, packet timing and broker logs should be part of the validation path. Variation is useful because it points to the assumption that must be measured next.

← Back to the chapter · Next detail →