81  Multi-Hop Ad Hoc Apps

In 60 Seconds

Multi-hop ad hoc networks excel in disaster rescue, agriculture, and remote monitoring where infrastructure is unavailable. Strategic relay placement matters more than relay count – 15 well-placed solar relays cover a 500-acre farm for under $7,500 versus $50K+ for per-device cellular, but the funnel effect means gateway-adjacent relays need larger batteries.

Minimum Viable Understanding

• Multi-hop ad hoc networks excel in disaster rescue, agriculture, and remote monitoring where fixed infrastructure is unavailable, impractical, or too expensive.
• Strategic relay placement matters more than total relay count – 15 well-placed solar-powered relays can cover a 500-acre farm for under $7,500 total cost versus $50K+ for per-device cellular.
• Multi-hop saves up to 80% total network energy compared to single long-range transmission, but creates a “funnel effect” where relay nodes near the gateway drain fastest and need larger batteries or solar power.

81.1 Learning Objectives

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

• Analyze Real-World Deployments: Examine multi-hop IoT systems in disaster rescue, agriculture, and archaeology
• Design Relay Placement: Calculate optimal relay node positions for coverage and hop count constraints
• Compare Network Architectures: Evaluate ad hoc vs infrastructure networks for specific use cases
• Plan Deployment Strategies: Create cost-effective multi-hop IoT network designs
• Calculate Energy Requirements: Determine node battery capacity and relay burden distribution

81.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 patterns

Sensor Squad: The Farm Network Adventure

The Sensor Squad was visiting Farmer Green’s 500-acre farm, and there was a BIG problem.

“My soil moisture sensors are spread across ALL these fields,” said Farmer Green, “but there’s no cell phone signal out here, and Wi-Fi only reaches 100 meters from my farmhouse!”

Sammy the Sensor looked across the vast fields. “That’s way too far for any of us to shout to the farmhouse directly!”

Max the Microcontroller had a plan. “We don’t need to shout that far! What if we place a few helper sensors – called relays – along the farm roads? Each sensor passes its message to the nearest relay, and the relays pass it along until the message reaches the farmhouse!”

“Like a bucket brigade putting out a fire!” said Lila the LED.

“Exactly! And the best part,” Max added, “each relay only needs to send a SHORT distance, so it uses very little battery. Farmer Green only needs 15 relays with solar panels to cover the entire 500-acre farm!”

Bella the Battery did the math. “200 sensors at $25 each, plus 15 relays at $150 each… that’s only $7,450! A cell phone module for each sensor would cost $50,000!”

Farmer Green was thrilled. “Multi-hop networking saves my crops AND my wallet!”

For Beginners: Why Use Multi-Hop in Real Applications?

Many IoT deployments are in places where traditional internet infrastructure simply does not exist – farms without cellular coverage, forests too vast for Wi-Fi, disaster zones where towers have been destroyed.

Multi-hop networking solves this by letting devices pass messages through each other, like a chain of people handing a letter from one to the next. The key benefits are:

• No infrastructure needed: Devices create their own network
• Cost-effective: A few relay nodes can cover huge areas
• Resilient: If one relay fails, messages find another path
• Scalable: Just add more nodes to extend coverage

Real-world examples include agricultural monitoring, disaster rescue communications, and environmental monitoring in remote locations.

81.3 Real-World Ad Hoc IoT Deployments

81.3.1 Disaster Rescue Operations

Figure 81.1: Disaster Rescue Operations: Emergency Multi-Hop Communication Network with drone relays

Scenario:

• Earthquake destroys cellular infrastructure
• Rescue teams carry portable IoT nodes
• Victims’ smartphones/wearables transmit distress signals
• Drones provide aerial relay nodes
• Network self-organizes as teams move through rubble
• Real-time victim location and vital signs relayed to command center

Requirements:

• Rapid deployment (no time for infrastructure setup)
• Resilience to node failures
• Support for mobile nodes
• Low power consumption (battery-operated)

81.3.2 Agricultural Monitoring Network

Figure 81.2: Agricultural Mesh Network: Field sensors in multiple zones relay through solar-powered nodes along farm roads to reach the gateway. This topology adapts to seasonal crop rotation and equipment movement.

Scenario:

• Large farm with hundreds of hectares
• Sensors deployed across multiple field sections
• No cellular coverage in remote areas
• Sensors form mesh to relay data to farmhouse gateway
• Dynamic routing adapts to:
  • Seasonal node deployments
  • Battery failures
  • Weather-induced link quality changes
  • Moving agricultural equipment (temporary obstacles)

Benefits:

• Cost-effective (no infrastructure deployment)
• Scalable (add nodes anywhere)
• Resilient (multiple paths to gateway)
• Flexible topology (adapt to crop rotation)

81.3.3 Archaeological Site Monitoring

Figure 81.3: Archaeological Site Network: Sensors monitor ruins with solar-powered relays forming an expandable ring around the excavation perimeter. Network topology evolves as new areas are uncovered, with satellite uplink for remote sites without cellular coverage.

Scenario:

• Remote archaeological site without power/connectivity
• Structural health monitoring of exposed ruins
• Environmental sensors tracking preservation conditions
• Security monitoring for artifact protection
• Nodes battery-powered with solar charging
• Network topology changes as excavation progresses

Challenges:

• Ultra-low power requirements (solar-charged batteries)
• Harsh environmental conditions
• Variable node density as sites expand
• Need for multi-year deployment without maintenance

81.4 Ad Hoc vs Infrastructure Networks

Table 81.1: Ad Hoc vs Infrastructure Network Comparison

Feature	Ad Hoc Networks	Infrastructure Networks
Topology	Dynamic mesh	Fixed star/tree
Setup	Self-organizing	Requires planning/installation
Cost	Low (no infrastructure)	High (APs, cabling, power)
Scalability	Organic growth	Requires infrastructure expansion
Reliability	Resilient (multi-path)	Single point of failure (AP)
Range	Extended via multi-hop	Limited by AP coverage
Routing	Distributed protocols	Centralized (AP-based)
Power	Battery-constrained	Infrastructure-powered APs
Mobility	High node mobility	Fixed infrastructure
Best For	Temporary, remote, mobile	Permanent, high-density, high-bandwidth

81.5 Smart Agriculture Case Study

Scenario: 500-acre farm in rural Iowa needs soil moisture monitoring across 200 sensor nodes.

Challenge: No cellular coverage, Wi-Fi range limited to 100m, budget constraints prohibit infrastructure.

Solution Architecture:

Figure 81.4: Smart Agriculture Deployment: 500-Acre Farm with Strategic Relay Nodes

Implementation Details:

Component	Specification	Cost	Rationale
Field Sensors	ESP32 + soil moisture probe, 915 MHz LoRa	$25 x 200 = $5,000	Battery-powered, 2-year life, 2km range per hop
Relay Nodes	Solar-powered repeaters, always-on	$150 x 15 = $2,250	Strategic placement every 200m along field perimeter
Gateway	Raspberry Pi + LTE modem + LoRa concentrator	$200	Aggregates data, cellular backhaul to cloud
Monthly Cost	LTE data plan	$30/month	1 GB sufficient for daily sensor updates
Total Investment		$7,450	vs. $50K+ for cellular module per sensor

Performance Metrics (6 months operation):

• Average hop count: 2.3 hops per message
• Packet delivery rate: 97.8% (baseline: 95% target)
• Energy efficiency: Sensors last 18 months on 2x AA batteries (90% duty cycle sleep mode)
• Latency: 3.2 seconds average from sensor reading to cloud (acceptable for daily irrigation decisions)
• Network resilience: 2 relay node failures caused zero data loss (automatic rerouting)

Key Lessons:

1. Strategic relay placement more important than total relay count - 15 well-placed nodes cover 500 acres
2. Heterogeneous network: Different node types (sensor, relay, gateway) optimize cost vs. capability
3. Duty cycling critical: Sensors transmit 1 reading per hour, sleep otherwise - battery life extended from 3 months to 18 months
4. Packet loss acceptable: Missing 2-3% of readings has no impact on irrigation decisions (daily aggregates used)

81.6 Worked Example: Relay Node Placement for Coverage

Worked Example: Relay Node Placement for Coverage

Scenario: A warehouse needs temperature monitoring across a 300m x 200m floor. Design relay placement to ensure 2-hop maximum path length to gateway.

Given:

• Warehouse dimensions: 300m x 200m
• Gateway location: Corner (0, 0)
• Sensor radio range: 100m (circular coverage)
• Target: All sensors reach gateway in 2 hops or less
• Grid sensor deployment: 50m spacing

Steps:

1. Calculate coverage requirements:
   • 2-hop coverage from gateway: 100m (hop 1) + 100m (hop 2) = 200m radius
   • Farthest point: diagonal corner at sqrt(300^2 + 200^2) = 361m
   • 361m > 200m -> Single gateway insufficient for 2-hop coverage
2. Determine relay positions:
   • Relay needed at ~150m from gateway to extend coverage
   • Optimal position: Along diagonal toward far corner
   • Relay at (150, 100): Covers nodes from 50m to 250m along diagonal
3. Verify coverage with relay:
   • Gateway covers: (0,0) to (100,100) direct
   • Relay covers: (100,50) to (250,200) via gateway
   • Far corner (300, 200): Distance to relay = sqrt(150^2 + 100^2) = 180m (within range for 2 hops via relay)
4. Calculate total deployment:
   • Grid sensors: (300/50 + 1) x (200/50 + 1) = 7 x 5 = 35 sensors
   • Relay nodes: 1 (strategic placement)
   • Maximum hops: 2 (gateway <- relay <- far sensor)

Result: One relay at (150, 100) extends gateway coverage to entire warehouse with 2-hop maximum.

Key Insight: Strategic relay placement multiplies coverage area. Placing relays along the diagonal maximizes reach. For a rectangular area, relays at 60-70% of the maximum dimension along the diagonal typically optimize 2-hop coverage. Each additional relay extends coverage by one radio range in the placement direction.

81.7 Worked Example: Hop Count vs Energy Trade-off Analysis

Worked Example: Hop Count vs Energy Trade-off Analysis

Scenario: A vineyard deploys soil moisture sensors that must reach a gateway 800m away. Compare direct single-hop transmission versus multi-hop relay.

Given:

• Distance to gateway: 800m
• Single-hop radio: 1W transmit power, 1km range
• Multi-hop radio: 50mW transmit power, 200m range
• Message size: 100 bytes
• Transmission energy: P x t (power x time)
• Transmission time: 10ms per message at either power level
• Path loss model: Energy proportional to d^2 (power required grows with distance squared)

Steps:

1. Calculate single-hop energy:
   • Distance: 800m
   • Power needed: 1W (to reach 1km, covering 800m with margin)
   • Energy per transmission: 1W x 10ms = 10 mJ
   • Total network energy: 10 mJ (only source transmits)
2. Calculate multi-hop energy:
   • Hops needed: 800m / 200m = 4 hops
   • Power per hop: 50mW (200m range)
   • Energy per hop: 50mW x 10ms = 0.5 mJ
   • Total network energy: 4 hops x 0.5 mJ = 2 mJ
3. Compare approaches:
   • Single-hop: 10 mJ (source only)
   • Multi-hop: 2 mJ (distributed across 4 nodes)
   • Energy savings: 80% with multi-hop
4. Consider relay energy burden:
   • Source: 0.5 mJ (transmit own data)
   • Relay 1: 0.5 mJ receive + 0.5 mJ transmit = 1 mJ
   • Relay 2-3: 1 mJ each
   • Source energy: 0.5 mJ vs 10 mJ = 95% savings for source

Result: Multi-hop uses 80% less total network energy and 95% less source energy, at cost of involving 3 additional relay nodes.

Key Insight: Multi-hop dramatically reduces source energy consumption but creates the “funnel effect” - relay nodes near the gateway handle all traffic. Plan for this by placing mains-powered or larger-battery nodes near gateways.

81.8 Interactive: Multi-Hop Energy Calculator

Explore how hop count and transmit power affect total network energy consumption.

viewof totalDistance = Inputs.range([100, 2000], {value: 800, step: 50, label: "Total distance to gateway (m)"})

viewof hopRange = Inputs.range([50, 500], {value: 200, step: 25, label: "Range per hop (m)"})

viewof singleHopPowerW = Inputs.range([0.1, 2.0], {value: 1.0, step: 0.1, label: "Single-hop transmit power (W)"})

viewof multiHopPowerMW = Inputs.range([10, 200], {value: 50, step: 5, label: "Multi-hop transmit power per hop (mW)"})

{
  const txTimeMs = 10;
  const numHops = Math.ceil(totalDistance / hopRange);
  const singleHopEnergyMJ = singleHopPowerW * txTimeMs;
  const perHopEnergyMJ = (multiHopPowerMW / 1000) * txTimeMs;
  const multiHopTotalMJ = numHops * perHopEnergyMJ;
  const savings = singleHopEnergyMJ > 0 ? ((singleHopEnergyMJ - multiHopTotalMJ) / singleHopEnergyMJ * 100) : 0;

  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid #3498DB; margin-top: 0.5rem;">
  <p><strong>Number of hops:</strong> ${numHops}</p>
  <p><strong>Single-hop energy:</strong> ${singleHopEnergyMJ.toFixed(2)} mJ (source only)</p>
  <p><strong>Multi-hop energy per hop:</strong> ${perHopEnergyMJ.toFixed(3)} mJ</p>
  <p><strong>Multi-hop total energy:</strong> ${multiHopTotalMJ.toFixed(3)} mJ (distributed across ${numHops} nodes)</p>
  <p><strong>Energy savings:</strong> <span style="color: ${savings > 0 ? '#16A085' : '#E74C3C'}">${savings.toFixed(1)}%</span> ${savings > 0 ? 'savings' : 'overhead'} with multi-hop</p>
  </div>`;
}

Putting Numbers to It

Let’s calculate battery life implications of the funnel effect for a 20-node vineyard sensor network with 4-hop paths to the gateway.

Topology: Source nodes → Relay1 → Relay2 → Relay3 → Gateway. Each sensor transmits once per hour.

Traffic load per node (assuming balanced tree with 5 sources per path):

\[L_{\text{source}} = 1\text{ transmission/hour (own data)}\]

\[L_{\text{relay3}} = 5 \times 2\text{ (RX + TX)} = 10\text{ operations/hour}\]

\[L_{\text{relay2}} = 10 \times 2 = 20\text{ operations/hour}\]

\[L_{\text{relay1}} = 20 \times 2 = 40\text{ operations/hour (funnel bottleneck!)}\]

Energy budget per operation: RX = 30 mA × 20 ms = 0.6 mAh, TX = 50 mA × 10 ms = 0.5 mAh. Total per relay operation = 1.1 mAh.

Daily energy consumption:

\[E_{\text{source}} = 24 \times 0.5 = 12\text{ mAh/day}\]

\[E_{\text{relay3}} = 10 \times 1.1 = 11\text{ mAh/day}\]

\[E_{\text{relay2}} = 20 \times 1.1 = 22\text{ mAh/day}\]

\[E_{\text{relay1}} = 40 \times 1.1 = 44\text{ mAh/day (4× source!)}\]

Battery life with 2,000 mAh battery:

\[T_{\text{source}} = \frac{2000}{12} = 167\text{ days} \approx 5.5\text{ months}\]

\[T_{\text{relay1}} = \frac{2000}{44} = 45\text{ days} \approx 1.5\text{ months}\]

Solution: Use heterogeneous battery sizing or solar power. Relay1 (near gateway) needs 4× battery capacity (8,000 mAh = 4× 18650 cells) to match source lifetime, OR solar panel (5V @ 500 mA = 2.5W, generates ~12 Wh/day ≫ 44 mAh × 3.7V = 0.16 Wh needed).

81.9 Knowledge Check

Test Your Understanding

81.10 Visual Reference Gallery

Visual: Multi-Hop Communication Path

Multi-hop relay network extending coverage

Visual: Relay Node Architecture

Relay node design in wireless sensor networks

Visual: Ad Hoc Routing Protocols

Classification of ad hoc routing protocols

Common Mistake: Random Relay Placement in Multi-Hop Networks

The Mistake: A farm deploys 200 soil sensors across 500 acres and adds 20 relay nodes “wherever convenient” (near roads, power sources, existing structures). After 6 months, 40% of sensors report intermittent connectivity, and gateway-adjacent relays drain batteries in 3 months instead of the expected 18 months.

Why It Fails:

1. Ignoring hop count distribution: Random placement creates uneven hop paths. Some sensors are 6 hops from gateway (high latency, 40% packet loss), while others are 1 hop. Optimal placement targets uniform 2-3 hop distribution.

2. Funnel effect concentration: 15 of the 20 relays were placed at field edges. Gateway-adjacent relays forward traffic from ALL upstream sensors. A relay 1 hop from gateway handles 80+ sensor streams (40,000 packets/day) vs edge sensors (200 packets/day self-generated only). Battery drains 200x faster.

3. Connectivity blind spots: Relays placed for human convenience (near roads) create coverage gaps in field centers where sensors are densest. 45 sensors in northeast quadrant all route through 1 overloaded relay – single point of failure.

The Fix: Strategic Grid Placement

Before (random): 20 relays, $3,000 hardware, 60% reliable connectivity, 3-month relay battery life After (strategic grid): 15 relays, $2,250 hardware, 97% reliable connectivity, 18-month relay battery life

Strategic placement algorithm:

1. Map sensor density: Create 50m x 50m grid. Count sensors per cell. High-density cells need nearby relays.
2. Calculate relay positions: Place relays at 60-70% of max field dimension along diagonals (maximizes 2-hop coverage circle overlap).
3. Prioritize gateway-adjacent relays: Relays within 1 hop of gateway get 3x larger batteries (3000 mAh vs 1000 mAh for edge relays). Cost: $15 extra per relay = $60 total for 4 gateway-adjacent relays.
4. Validate with graph analysis: Run Dijkstra’s algorithm from each sensor to gateway. If any path >3 hops, add relay at midpoint.

Real-world numbers (500-acre farm case study): - Random placement: Average 3.7 hops, 82% delivery rate, 15 relay failures in year 1 (75% failure rate) - Strategic placement: Average 2.3 hops, 97.8% delivery rate, 1 relay failure in year 1 (7% failure rate) - Energy distribution: Strategic placement balances load – gateway relays forward 15K packets/day vs 30K+ in random placement (50% reduction via multi-path routing)

Key lesson: Multi-hop network performance depends more on relay placement strategy than relay count. 15 well-placed relays outperform 20 randomly placed relays while costing 25% less.

Match Multi-Hop Application Scenarios to Network Characteristics

Order: Designing a Multi-Hop Agricultural Sensor Network

Place these deployment steps in the correct order.

Key Concepts

• Vehicular Ad Hoc Network (VANET): A specialized MANET for vehicles communicating via DSRC (dedicated short-range communications) or C-V2X to share safety alerts, traffic conditions, and cooperative driving data
• Disaster Recovery Network: A rapidly deployed ad hoc mesh providing emergency communications when infrastructure (cellular towers, fiber) is destroyed, using first responders’ devices as network nodes
• Search and Rescue Mesh: An ad hoc network deployed in disaster zones where GPS-tagged sensor nodes and rescuer devices relay survivor signals (distress beacons, phone pings) to emergency coordinators
• Military Tactical Network: A battlefield mesh network where troops, vehicles, and drones form an infrastructure-free network with frequency hopping, ECCM, and self-healing topology for communications under adversarial conditions
• Smart Grid Mesh: A neighborhood area network (NAN) using multi-hop mesh protocols (ZigBee SEP, Wi-SUN) to collect smart meter readings across hundreds of meters without cellular connectivity
• Industrial Wireless Mesh: A WirelessHART or ISA100.11a deployment in a refinery or chemical plant providing sensor data from process instrumentation across buildings and equipment that block radio line-of-sight

Common Pitfalls

1. Designing for Ideal RF Conditions

Assuming multi-hop paths established in lab testing will persist in field deployment. Physical obstacles, interference, and device movement cause link failures that require routing protocol adaptation. Design for 30–50% link failure rate and test routing protocol convergence under these conditions.

2. Not Planning for Gateway Capacity

Treating the multi-hop gateway as an infinite throughput device. All network traffic funnels through the gateway — at 1,000 devices × 1 packet/minute, the gateway must process 16 packets/second continuously. Size gateway processing, storage, and uplink bandwidth for the full network load.

3. Ignoring Time Synchronization in Multi-Hop Applications

Deploying multi-hop IoT for time-sensitive applications (event sequencing, synchronized actuation) without addressing time synchronization. Multi-hop propagation delay (1–10 ms per hop × 5 hops = 5–50 ms) and clock drift across nodes require explicit time synchronization (IEEE 802.15.4 TSCH, PTP, NTP).

4. Not Testing Routing Protocol Convergence Time

Deploying multi-hop IoT without measuring how long the routing protocol takes to find new paths after a node failure. Convergence times of 5–30 seconds are common in RPL deployments — applications requiring sub-second failover need alternative routing protocols or topology designs.

Label the Diagram

💻 Code Challenge

81.11 Summary

This chapter covered real-world multi-hop IoT applications:

• Disaster Rescue: Self-organizing networks with drone relays for emergency communication when infrastructure is destroyed
• Agricultural Monitoring: Cost-effective sensor meshes covering hundreds of hectares with organic scalability and seasonal adaptability
• Archaeological Sites: Ultra-low power deployments for multi-year monitoring in remote locations without maintenance access
• Network Comparison: Ad hoc networks excel in temporary, remote, and mobile scenarios; infrastructure networks suit permanent high-bandwidth deployments
• Case Study: Smart agriculture deployment showing 200 sensors, 15 relays, $7,450 total cost vs. $50K+ for per-device cellular
• Relay Placement: Strategic positioning along diagonals maximizes 2-hop coverage; 60-70% of maximum dimension is optimal
• Energy Analysis: Multi-hop can save 80% network energy but creates funnel effect requiring heterogeneous battery sizing

81.12 What’s Next

If you want to…	Read this
Test your multi-hop knowledge	Multi-Hop Assessment
Review multi-hop core concepts	Multi-Hop Core Concepts
Start with multi-hop fundamentals	Multi-Hop Fundamentals
Explore wireless sensor network architectures	Wireless Sensor Networks
Study routing protocols for IoT meshes	Routing and RPL