82 Multi-Hop Ad Hoc Assessment

In 60 Seconds

Optimal hop count is 3-5 hops – at 95% per-hop reliability, 10 hops yields only 60% end-to-end delivery. The energy hole problem is the most common deployment failure: nodes near the gateway relay all upstream traffic and die first while edge nodes retain 80% battery. Always test bidirectional links – wireless links are often asymmetric, meaning node A hearing node B does not guarantee B can hear A.

Minimum Viable Understanding

Optimal hop count is 3-5 hops – beyond that, reliability degrades exponentially (95% per-hop reliability over 10 hops yields only 60% end-to-end delivery).
The energy hole problem is the most common deployment failure: nodes near the gateway relay all upstream traffic and die first while edge nodes still have 80% battery.
Bidirectional link testing is essential because wireless links are often asymmetric – just because node A hears node B does not mean B can hear A.

82.1 Learning Objectives

By the end of this chapter, you will be able to:

Evaluate multi-hop network designs by testing understanding of hop count, reliability, and energy trade-offs
Diagnose common pitfalls including the energy hole problem, hop limit violations, and asymmetric link assumptions
Apply best practices from real-world implementations across planning, deployment, and operation phases
Calculate end-to-end reliability and battery life for multi-hop network configurations

For Beginners: Multi-Hop Assessment

This assessment tests your understanding of multi-hop networking, where data passes through several devices to reach its destination. Think of it like a relay race practice test – it checks whether you understand how the baton (data) moves from runner to runner (device to device) and what happens when someone drops it (a node fails).

82.2 Prerequisites

Before diving into this chapter, you should be familiar with:

Multi-Hop Core Concepts: Understanding of ad hoc networks, hop count trade-offs, and energy distribution
Multi-Hop Applications: Real-world deployment examples and relay placement strategies

Sensor Squad: The Quiz Show

The Sensor Squad was competing on “Who Wants to Be a Network Engineer?” – a quiz show hosted by Max the Microcontroller!

“First question!” announced Max. “Sammy, if you add MORE hops to a network path, what happens to reliability?”

Sammy the Sensor thought hard. “Each hop has a chance of failing. If each hop works 95% of the time, then 10 hops means… 0.95 times itself 10 times… only 60% of messages get through! So more hops means LESS reliability!”

“Correct! Next question for Lila: What’s the energy hole problem?”

Lila the LED answered confidently. “Nodes near the gateway have to relay EVERYONE’s messages, so their batteries die first while edge nodes still have plenty of power. The fix is to give gateway-neighbor nodes bigger batteries or solar power!”

“Perfect! Final question for Bella: Should you assume wireless links work equally well in both directions?”

“NEVER!” said Bella the Battery. “Just because I can hear you doesn’t mean you can hear me. Radio signals can be asymmetric due to obstacles, antenna direction, or interference. Always test links in BOTH directions!”

“All correct! The Sensor Squad is ready to design real multi-hop networks!” cheered Max.

82.3 Knowledge Check

Question 1: Multi-hop Benefits

Question 2: Hop Count Impact

Question 3: Energy Considerations

Question 4: Routing Protocol Classes

Question 5: Optimal Hop Count

Question 6: Single-Hop vs Multi-Hop

82.4 Common Misconceptions

Common Misconceptions

Misconception 1: “More hops always means better coverage”

Reality: While multi-hop extends range, each hop adds latency and potential failure points. The optimal hop count balances coverage extension with reliability and latency requirements.

Misconception 2: “Ad hoc networks don’t need any planning”

Reality: Though self-organizing, ad hoc networks still require careful design of node density, transmission power, routing protocols, and energy management strategies.

Misconception 3: “All nodes in ad hoc networks consume equal energy”

Reality: Nodes near the sink create a “funnel effect” - they relay traffic from many sources and deplete batteries much faster than edge nodes.

Misconception 4: “Multi-hop is always more energy-efficient than long-range transmission”

Reality: This depends on the scenario. While individual hops use less power, the total network energy (summed across all relay nodes) may exceed direct long-range transmission for certain distances.

82.5 Common Pitfalls

Pitfall: Ignoring the Energy Hole Problem

The mistake: Deploying multi-hop sensor networks with uniform battery capacity across all nodes, then discovering that nodes closest to the gateway die within weeks while edge nodes still have 80% battery.

Why it happens: Network designers calculate average energy consumption without modeling the “funnel effect” - nodes near the sink relay traffic from all upstream nodes. A node 1 hop from the gateway may forward 50x more packets than edge sensors.

The fix: Use heterogeneous deployment - nodes near the sink should have larger batteries (2-4x capacity), solar/mains power, or be designated as upgradable relay stations. Alternatively, deploy multiple sinks to distribute the traffic load, or implement load-balancing routing that spreads relay duties across multiple paths.

Pitfall: Exceeding the Practical Hop Limit

The mistake: Designing networks with 8-10+ hops to maximize coverage, then experiencing 40%+ packet loss and multi-second latencies that render the system unusable.

Why it happens: Each hop has independent failure probability. With 95% per-hop reliability (good for wireless), a 10-hop path delivers only 60% of packets (0.95^10 = 0.60). Latency accumulates linearly, but reliability degrades exponentially.

The fix: Limit designs to 3-5 hops maximum for reliable operation. For larger coverage areas, deploy additional gateways/sinks rather than extending hop count. If more hops are unavoidable, implement acknowledgments and retransmissions at every hop (not just end-to-end), and use link quality metrics to avoid marginal links.

Putting Numbers to It

End-to-end reliability in multi-hop networks degrades exponentially with hop count. If each hop has independent reliability $p$, then the probability of successful delivery over $n$ hops is the product of individual hop reliabilities.

\[R_{\text{end-to-end}} = p^n\]

Worked example: A 10-hop path where each link has 95% reliability yields only $0.95^{10} = 0.599$ or 60% end-to-end success rate. Reducing to 5 hops improves reliability to $0.95^5 = 0.774$ or 77%. This exponential decay explains why 3-5 hops is optimal – beyond that, even high per-link reliability produces unacceptable packet loss.

82.6 Interactive: Hop Count Reliability Calculator

Explore how per-hop link reliability and hop count combine to determine end-to-end packet delivery rate.

Show code

{
  const endToEnd = Math.pow(perHopReliability, numHopsCalc);
  const pct = (endToEnd * 100).toFixed(1);
  const color = endToEnd >= 0.9 ? '#16A085' : endToEnd >= 0.75 ? '#E67E22' : '#E74C3C';
  const rating = endToEnd >= 0.9 ? 'Good' : endToEnd >= 0.75 ? 'Marginal' : 'Poor';

  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid ${color}; margin-top: 0.5rem;">
  <p><strong>End-to-end delivery rate:</strong> <span style="color: ${color}; font-size: 1.2em;">${pct}%</span> (${rating})</p>
  <p><em>Formula: ${(perHopReliability).toFixed(2)}<sup>${numHopsCalc}</sup> = ${endToEnd.toFixed(4)}</em></p>
  <p style="margin-bottom: 0;">Optimal range (90%+): keep hop count ≤ ${Math.floor(Math.log(0.90) / Math.log(perHopReliability))} hops at this per-hop reliability.</p>
  </div>`;
}

Pitfall: Assuming Symmetric Links

The mistake: Building routing tables based on received signal strength (RSSI) from neighbors, assuming that if node A can hear node B clearly, then B can also hear A equally well.

Why it happens: Radio propagation is often asymmetric due to antenna orientation, local interference sources, transmit power differences, and environmental obstacles. Node A’s transmission may take a different physical path than node B’s response.

The fix: Validate links bidirectionally before adding to routing tables. Use bidirectional link probing: node A sends probe, node B responds, and A confirms receipt. Measure link quality in both directions separately. Avoid routes using unidirectional links - they cause ACK failures and route discovery loops. Consider using ETX (Expected Transmission Count) which inherently measures both directions.

Pitfall: Ignoring Duty Cycle Impact

The mistake: Designing multi-hop routing assuming all nodes are always awake and ready to forward packets.

Why it happens: Energy-constrained IoT nodes use duty cycling (sleeping 90-99% of the time). A packet arriving at a sleeping relay node either waits (adding latency) or is dropped (reducing reliability).

The fix: Use synchronous duty cycling protocols where neighbors coordinate wake schedules, or asynchronous protocols with low-power listening. Factor wake-up latency into end-to-end timing calculations. Consider wake-on-radio capabilities for time-critical applications.

82.7 Worked Example: Energy Hole Mitigation in a Vineyard WSN

Scenario: A vineyard deploys 120 soil moisture sensors across 30 hectares in a grid pattern. All data routes to a single gateway at the vineyard office. The network uses multi-hop routing with a maximum of 4 hops. Each sensor node has a 3.6V, 2600 mAh lithium battery.

Energy consumption model:

Activity	Current Draw	Duration per Event
Sense + process	15 mA	50 ms
Transmit own data	45 mA	30 ms
Receive + forward relay packet	30 mA	40 ms
Sleep	8 uA	(remainder)

Traffic analysis by hop distance:

Each sensor generates 1 packet every 15 minutes = 96 packets/day of its own data.

Hop Distance	Own Packets/Day	Relay Packets/Day	Total TX/Day	Daily Energy (mAh)
Hop 4 (edge)	96	0	96	0.14
Hop 3	96	~96 (1 child)	192	0.24
Hop 2	96	~480 (5 upstream nodes)	576	0.56
Hop 1 (gateway neighbor)	96	~2,880 (30 upstream nodes)	2,976	2.72

Battery life by position:

Position	Daily Consumption	Battery Life
Hop 4 (edge)	0.14 mAh	18,571 days (50.9 years)
Hop 3	0.24 mAh	10,833 days (29.7 years)
Hop 2	0.56 mAh	4,643 days (12.7 years)
Hop 1 (gateway neighbor)	2.72 mAh	956 days (2.6 years)

The energy hole: Gateway-adjacent nodes die in 2.6 years while edge nodes would last 50+ years. When hop-1 nodes die, the entire network partitions – edge nodes with full batteries become unreachable.

Mitigation strategies applied:

Larger batteries at hop 1: Replace 2600 mAh with 19,000 mAh D-cell batteries for the 8 gateway-neighbor nodes. Cost: $12 extra per node = $96. New lifetime: 19.1 years.
Add a second gateway: Placing a second gateway at the far end of the vineyard halves the maximum relay load. Hop-1 relay packets drop from 2,880 to ~1,440/day. Battery life at hop 1 improves from 2.6 to 4.8 years. Gateway cost: $300.
Solar panel on hop-1 nodes: A 1W solar panel ($8) with 4 hours of sunlight generates 1,111 mAh/day – far exceeding the 2.72 mAh consumption. Effectively infinite lifetime. Total cost: 8 panels x $8 = $64.

Recommended solution: Solar panels on the 8 gateway-neighbor nodes ($64 total) provides the best cost-effectiveness – cheaper than larger batteries and avoids the $300 second gateway.

82.8 Best Practices Summary

Multi-Hop Network Design Best Practices

Planning Phase:

Survey the deployment area - Measure actual radio range with representative hardware, not theoretical maximum
Calculate hop count - Target 3-5 hops maximum; add gateways if more coverage needed
Identify funnel points - Mark locations where traffic concentrates; plan for larger batteries or power sources

Deployment Phase:

Test links bidirectionally - Verify both directions of every link before including in routing tables
Use heterogeneous nodes - Relay-heavy positions get larger batteries, solar panels, or mains power
Deploy incrementally - Validate each section works before expanding coverage

Operation Phase:

Monitor energy distribution - Track which nodes drain fastest; reposition or replace proactively
Log packet loss by path - Identify weak links before complete failure
Plan for graceful degradation - Design so losing one relay affects minimal sensors

Key Concepts

Assessment Criteria: The dimensions evaluated in a multi-hop network design review: routing protocol selection, topology management strategy, energy-balancing approach, security mechanisms, and performance under node failure
Proactive vs Reactive Routing Trade-off: Proactive protocols (OLSR, DSDV) maintain full routing tables at all times — low latency for established paths but high overhead; reactive protocols (AODV, DSR) discover routes on demand — low idle overhead but higher first-packet latency
Load Balancing: The distribution of routing burden across multiple mesh nodes to prevent central nodes from depleting their batteries faster than leaf nodes, achieved through metrics incorporating remaining energy in routing decisions
Network Lifetime: The operational duration until the first (or k-th) node battery exhaustion causes a network partition, used as the primary performance metric for energy-constrained multi-hop IoT meshes
Coverage and Connectivity Trade-off: The tension between maximizing the geographic area covered by a sensor mesh (requiring sparse node placement) and maintaining multi-hop connectivity (requiring sufficient neighbor density for path diversity)
Throughput-Latency Trade-off: In multi-hop networks, adding relay hops increases per-message latency (each hop adds processing and queuing delay) while potentially increasing overall network capacity through spatial frequency reuse

Label the Diagram

💻 Code Challenge

82.10 Summary

This chapter covered assessment and best practices for multi-hop networks:

Knowledge Checks: Six questions testing understanding of multi-hop benefits, hop count impacts, energy distribution, routing protocols, and design decisions
Common Misconceptions: Clarified four false assumptions about coverage, planning, energy, and efficiency
Critical Pitfalls: Identified four major deployment mistakes - energy hole problem, hop limit violations, asymmetric link assumptions, and duty cycle oversight
Best Practices: Nine guidelines organized across planning, deployment, and operation phases
Cross-References: Links to related topics in ad hoc routing, WSN, and interactive learning resources

82.11 What’s Next

If you want to…	Read this
Explore real-world multi-hop applications	Multi-Hop Applications
Review core multi-hop concepts	Multi-Hop Core Concepts
Start with fundamentals	Multi-Hop Fundamentals
Study wireless sensor network design	Wireless Sensor Networks
Learn about software-defined networking	Software-Defined Networking