Check: Ad-Hoc Readiness Checkpoints

Knowledge check · self-test
Check: Ad-Hoc Readiness Checkpoints
Checkpoint: Minimum Viable Understanding. Routing protocol choice depends on traffic patterns: proactive (DSDV/OLSR) for frequent traffic, reactive (AODV/DSR) for sparse traffic, hybrid (ZRP) for mixed patterns. Multi-path redundancy can reduce outage duration when backup paths are prevalidated and the failover trigger is measured. Energy-aware routing can extend network lifetime when relay load and battery state are measured instead of assuming the shortest path is always best. Putting Numbers to It. Without multi-path: link failure detection (100 ms ACK timeout) + route discovery (8s for 4-hop RREQ/RREP) = 8.1 seconds outage. With pre-cached backup: failure detection (100 ms) + cache lookup (5 ms) + first packet on backup (62 ms for 4-hop path) = 167 ms recovery. The modeled recovery window falls from about 8 seconds to 167 ms; actual packet loss depends on retry, queueing, and failure timing. Checkpoint: Protocol Fit and Link Evidence. You now know: Proactive, reactive, and hybrid routing differ mainly in control overhead, route latency, and how much route state they keep ready. A GOOD link is not a guess: the example classifies 82% PDR, -74 dBm RSSI, and 35 ms latency against the 70-90% PDR, -70 to -80 dBm, and 20-50 ms bands. A route choice is ready for production discussion only after traffic pattern, mobility, link quality, energy state, and recovery requirement are connected. Checkpoint: Worked Failover Claims. You now know: In the vineyard example, the modeled recovery window falls from about 8 seconds to 167 ms; actual packet loss depends on retry, queueing, and failure timing. A backup route must pass both timing and energy checks: the 35% battery path is rejected against the 40% threshold even though it is short. For critical alerts, the 3-hop path changes worst-case latency from 620 ms to 380 ms and stays inside the 500 ms budget. Checkpoint: Scenario Transfer. You now know: Range, delivery, cache freshness, battery distribution, and mobility prediction all change the routing answer. Multi-hop range planning trades a 2km single link for four 500m hops; social routing cuts epidemic-style 50+ copies down to 5-10 targeted copies when contact patterns help. Energy-aware selection can leave the weakest route at 25% battery instead of 0%, while mobility prediction reroutes around the -85 dBm failure point. Correction: In the Scenario Transfer recap, the weakest route retains 28% battery, as calculated in Energy-Aware Multi-Path Selection; 25% is a typo.
Checkpoint: Minimum Viable Understanding. Routing protocol choice depends on traffic patterns: proactive (DSDV/OLSR) for frequent traffic, reactive (AODV/DSR) for sparse traffic, hybrid (ZRP) for mixed patterns. Multi-path redundancy can reduce outage duration when backup paths are prevalidated and the failover trigger is measured. Energy-aware routing can extend network lifetime when relay load and battery state are measured instead of assuming the shortest path is always best. Putting Numbers to It. Without multi-path: link failure detection (100 ms ACK timeout) + route discovery (8s for 4-hop RREQ/RREP) = 8.1 seconds outage. With pre-cached backup: failure detection (100 ms) + cache lookup (5 ms) + first packet on backup (62 ms for 4-hop path) = 167 ms recovery. The modeled recovery window falls from about 8 seconds to 167 ms; actual packet loss depends on retry, queueing, and failure timing. Checkpoint: Protocol Fit and Link Evidence. You now know: Proactive, reactive, and hybrid routing differ mainly in control overhead, route latency, and how much route state they keep ready. A GOOD link is not a guess: the example classifies 82% PDR, -74 dBm RSSI, and 35 ms latency against the 70-90% PDR, -70 to -80 dBm, and 20-50 ms bands. A route choice is ready for production discussion only after traffic pattern, mobility, link quality, energy state, and recovery requirement are connected. Checkpoint: Worked Failover Claims. You now know: In the vineyard example, the modeled recovery window falls from about 8 seconds to 167 ms; actual packet loss depends on retry, queueing, and failure timing. A backup route must pass both timing and energy checks: the 35% battery path is rejected against the 40% threshold even though it is short. For critical alerts, the 3-hop path changes worst-case latency from 620 ms to 380 ms and stays inside the 500 ms budget. Checkpoint: Scenario Transfer. You now know: Range, delivery, cache freshness, battery distribution, and mobility prediction all change the routing answer. Multi-hop range planning trades a 2km single link for four 500m hops; social routing cuts epidemic-style 50+ copies down to 5-10 targeted copies when contact patterns help. Energy-aware selection can leave the weakest route at 25% battery instead of 0%, while mobility prediction reroutes around the -85 dBm failure point. Correction: In the Scenario Transfer recap, the weakest route retains 28% battery, as calculated in Energy-Aware Multi-Path Selection; 25% is a typo.
Back to Ad-Hoc Production: Readiness Checks: Knowledge Check