86  Ad-Hoc Network Applications

In 60 Seconds

Ad-hoc networks serve five key domains: disaster recovery (no infrastructure), military tactical (mobile, hostile), vehicular (VANETs at 120+ km/h), WSNs (energy-constrained sensors), and drone swarms (FANETs with 3D mobility). Multi-hop routing reduces corner-sensor energy consumption by 98% compared to direct single-hop transmission.

Minimum Viable Understanding

• Ad-hoc networks serve five key domains: disaster recovery, military tactical, vehicular (VANETs), wireless sensor networks (WSNs), and drone swarms (FANETs) – all requiring infrastructure-less operation
• Routing protocol selection depends on traffic patterns: reactive (DSR) for sparse/infrequent traffic (<1 tx/node/hour), proactive (DSDV) for dense/continuous traffic, hybrid (ZRP) for large heterogeneous networks
• Multi-hop routing distributes energy across nodes rather than minimizing total energy, preventing premature battery death at edge sensors (98% energy reduction for corner sensors using 5-hop vs direct transmission)

Sensor Squad: Where Ad-Hoc Networks Save the Day

“When would you need a network with NO towers, NO routers, NO infrastructure at all?” asked Max the Microcontroller.

“Earthquakes!” said Sammy the Sensor. “When towers fall down, rescue teams use ad-hoc radios to talk to each other. Each radio passes messages to the next one until help arrives!”

“Or forests!” added Bella the Battery. “We sensor nodes sit in trees watching for fire. There’s no Wi-Fi out here, so we pass our temperature readings from sensor to sensor until they reach the ranger station.”

Lila the LED blinked excitedly. “Or DRONES! A swarm of search-and-rescue drones creates a flying network in the sky. No towers needed – they talk directly to each other while zooming around!”

“And don’t forget cars!” said Max. “Self-driving cars warn each other about accidents ahead. They form a network ON THE ROAD without needing any cell towers.”

The Squad’s rule of thumb: If you can’t build towers (disaster), won’t build towers (temporary events), or don’t need towers (vehicles already move around), use an ad-hoc network!

For Beginners: Ad-Hoc Network Applications

When to use ad-hoc networks: Any time you need a network but cannot or should not deploy fixed infrastructure.

Five main application areas:

Application	Why Ad-Hoc?	Example
Disaster recovery	Infrastructure destroyed	Rescue team radios forming mesh
Military	Rapid deployment, hostile area	Soldier wearable radio mesh
Vehicles (VANETs)	High mobility, brief contacts	Cars warning each other of hazards
Sensor networks	Remote/harsh environments	Forest fire detection sensors
Drone swarms	3D mobility, no ground infrastructure	Search-and-rescue UAV fleet

Key design decisions:

• Sparse traffic (sensors reporting hourly) -> Use reactive routing (DSR) to save energy
• Dense traffic (vehicles streaming data) -> Use proactive routing (DSDV) for low latency
• Large mixed networks (100+ nodes) -> Use hybrid routing (ZRP) for best balance

86.1 Learning Objectives

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

• Identify Use Cases: Determine when ad-hoc networks are the appropriate solution for IoT deployments
• Apply Routing Selection: Choose appropriate routing protocols for specific deployment scenarios and justify your choice
• Calculate Energy Trade-offs: Compute multi-hop vs direct transmission energy costs using the Friis equation
• Design for Scale: Assess scalability limitations and apply hierarchical solutions for large networks
• Evaluate Deployment Scenarios: Analyze real-world case studies and validate protocol selection through worked examples

86.2 Prerequisites

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

• Ad-Hoc Networks: Core Concepts: Understanding what ad-hoc networks are and their key characteristics
• Ad-Hoc Networks: Multi-Hop Routing: Understanding proactive, reactive, and hybrid routing approaches

Key Concepts

• Ad Hoc Network Applications: Real-world domains using infrastructure-less networks: disaster response, military, vehicular, sensor, and community networking
• Disaster Response Networks: Emergency communication networks formed after infrastructure destruction; first responders need instant mesh connectivity
• Vehicular Ad Hoc Networks (VANET): V2V and V2I networks for safety, traffic management, and infotainment; nodes are vehicles with high mobility
• Battlefield Networks (MANET): Military mobile ad hoc networks requiring secure, resilient, and anti-jamming communication
• Community Mesh Networks: Volunteer-built community wireless networks providing internet access in underserved areas
• IoT Sensor Mesh: Ad hoc networks of IoT sensors for environmental monitoring, agriculture, and infrastructure inspection
• Application-Driven Protocol Selection: Choosing routing protocol (DSDV, DSR, AODV, ZRP) based on application’s mobility, density, and traffic pattern
• Quality of Service (QoS) in Ad Hoc: Providing delay, bandwidth, and reliability guarantees in resource-constrained multi-hop networks

86.3 Ad-Hoc Network Applications

⏱️ ~10 min | ⭐⭐ Intermediate | 📋 P04.C02.U04

⭐⭐ Intermediate

Figure 86.1: Real-world ad-hoc network applications showing five deployment scenarios: disaster recovery, military tactical, vehicular networks, sensor networks, and drone swarms.

86.3.1 Disaster Recovery and Emergency Response

⭐⭐ Intermediate

• Scenario: Earthquake destroys cellular towers; rescue teams need communication
• Solution: Handheld radios form ad-hoc mesh; relay messages multi-hop
• Requirements: Rapid deployment, high reliability, no infrastructure dependency
• Real Deployment: 2011 Fukushima disaster - rescue teams deployed 150 ad-hoc radios covering 25km² with 4-6 hop paths, enabling coordination when all cellular networks failed for 72 hours

Case Study – 2023 Turkey-Syria Earthquake Response: When the magnitude 7.8 earthquake struck southeastern Turkey, cellular infrastructure across a 350 km radius was destroyed or overloaded. International rescue teams from 12 countries deployed Rajant Kinetic Mesh radios within 6 hours of arrival. Key numbers:

Metric	Value
Mesh nodes deployed	420 radios across 180 km²
Average hop count	3.7 hops (range: 1-8)
Network setup time	4 hours for initial 50-node backbone
Throughput per link	20-40 Mbps (802.11n)
Operational temperature	-5 to 35 degrees C during February rescue
Cost per node	$3,800 (Rajant Peregrine)
Total equipment cost	$1.6 million
Lives assisted	6,400+ people rescued using mesh-coordinated search

The critical design decision was reactive routing (AODV variant) because rescue teams moved constantly between collapse sites, making proactive route maintenance impractical. The 4-hour setup time highlights why ad-hoc networks exist: no time to install towers when people are trapped.

86.3.2 Military and Tactical Operations

• Scenario: Soldiers in battlefield need real-time coordination
• Solution: Wearable radios create mobile mesh network; encrypted communications
• Requirements: High security, low latency, resilience to node capture

Why ad-hoc over satellite: Military satellite links provide 256 kbps-2 Mbps shared across an entire platoon but cost $5,000-15,000/month in airtime and introduce 500-700 ms latency (geostationary orbit round-trip). An ad-hoc mesh of 30 soldier-worn radios provides 10-50 Mbps aggregate bandwidth with 5-20 ms latency at zero recurring cost. The trade-off: satellite works everywhere with line-of-sight to sky, while the mesh requires node density (typically one radio per 50-200 m).

86.3.3 Vehicular Ad-Hoc Networks (VANETs)

• Scenario: Cars exchange traffic, safety, and infotainment data
• Solution: 802.11p/DSRC radios create vehicle-to-vehicle (V2V) mesh
• Requirements: High mobility support, low latency (collision warnings), privacy

Scale of the challenge: At 120 km/h, two cars approaching each other have a closing speed of 240 km/h (67 m/s). A collision warning must be generated, transmitted, received, and processed within 500 ms to provide meaningful braking distance (approximately 33 m at highway speed). With 802.11p’s typical range of 300-1,000 m, messages traverse 1-3 hops before the cars physically pass each other. This leaves only 100-200 ms for routing decisions, which is why VANETs use position-based greedy forwarding (GPSR) instead of route discovery protocols – there is no time for RREQ/RREP exchanges.

86.3.4 Wireless Sensor Networks (WSNs)

• Scenario: Forest fire detection using temperature/smoke sensors
• Solution: Battery-powered sensors relay data multi-hop to gateway
• Requirements: Energy efficiency, scalability (1000s of nodes), long lifetime

Real deployment – Great Smoky Mountains fire detection (2016-present): The National Park Service deployed 1,200 battery-powered sensors across 3,000 hectares of fire-prone forest. Sensors transmit temperature and humidity readings every 15 minutes via Zigbee mesh (802.15.4), with 8-12 hop paths to 6 solar-powered gateways. Network lifetime target: 3 years on 2x AA batteries (6,000 mAh at 3 V = 18 Wh). Actual lifetime: 2.4 years average, with hotspot relay nodes near gateways failing at 18 months (the energy hole problem). Adding a second ring of gateway nodes at Year 2 extended remaining sensor lifetime by 40%.

Putting Numbers to It

Battery energy: \(E = V \times Q = 3 \text{ V} \times 6{,}000 \text{ mAh} = 18 \text{ Wh} = 64{,}800 \text{ J}\). Target 3-year (26,280 hr) lifetime requires \(64{,}800 / 26{,}280 = 2.47 \text{ J/hr}\) budget. Worked example: Edge sensor (4 tx/hr × 50 mJ) = 200 mJ/hr. Gateway relay (10 neighbors + own) = 2,200 mJ/hr (11× more). Real overhead pushes relay to 3.6 J/hr: \(64{,}800 / 3.6 = 18{,}000\) hrs = 2.05 years, matching observed 18-month failures.

86.3.5 Flying Ad-Hoc Networks (FANETs)

• Scenario: Drone swarm for search-and-rescue or surveillance
• Solution: Drones relay video and coordinates via ad-hoc mesh
• Requirements: 3D topology support, high mobility, GPS integration

Design constraint unique to FANETs: Unlike ground-based ad-hoc networks, FANET nodes move in three dimensions at 10-30 m/s, causing link lifetimes of 30-120 seconds (compared to 5-60 minutes for pedestrian MANETs). A 10-drone search pattern covering 2 km² requires each drone to maintain 2-4 simultaneous air-to-air links and at least one air-to-ground link. With typical drone battery capacity of 74 Wh and flight power of 150-300 W, communication energy (2-5 W) is negligible – the design bottleneck is link stability during high-speed maneuvers, not energy.

86.3.6 Application Selection Matrix

Application Domain	Typical Scale	Routing	Latency Req.	Node Lifetime	Cost/Node
Disaster recovery	50-500 nodes	Reactive (AODV)	1-5 seconds	Hours-days	$500-4,000
Military tactical	20-100 nodes	Proactive (OLSR)	10-50 ms	Days-weeks	$5,000-20,000
Vehicular (VANET)	100-10,000	Position-based (GPSR)	<200 ms	Vehicle lifetime	$200-500
Forest WSN	200-5,000	Reactive (AODV/RPL)	1-60 seconds	2-5 years	$20-100
Drone swarm	5-50 nodes	Hybrid	50-500 ms	20-40 minutes	$1,000-5,000

86.4 Worked Examples

Worked Example: Selecting Routing Protocol for Wildlife Tracking Network

Scenario: A conservation team is deploying GPS collars on 50 elephants across a 200 km² wildlife reserve in Kenya. Collars transmit location data twice daily to solar-powered relay nodes scattered throughout the reserve. The relay nodes form an ad-hoc mesh to route data to a central base station.

Given:

• 50 elephant collars (mobile, unpredictable movement)
• 30 relay nodes (stationary, solar-powered)
• Communication frequency: 2 transmissions per collar per day = 100 total transmissions/day
• Network diameter: 8-10 hops from furthest relay to base station
• Latency tolerance: 5 minutes (non-real-time)

Steps:

1. Analyze traffic pattern: 100 transmissions/day = ~4 transmissions/hour = 1 every 15 minutes. This is sparse traffic - nodes are mostly idle.

2. Evaluate mobility: Relay nodes are stationary (good for route stability). Elephant collars move but only communicate twice daily, so routes can be discovered fresh each time.

3. Calculate proactive overhead: DSDV with 30 relays, 15-second updates = 30 nodes x 4 updates/minute = 120 control packets/minute = 7,200/hour. With only 4 data packets/hour, overhead ratio is 1800:1 (unacceptable).

4. Calculate reactive overhead: DSR with 100 discoveries/day, ~50 packets per discovery = 5,000 control packets/day vs. 100 data packets/day. Overhead ratio is 50:1 (acceptable for solar-powered nodes).

5. Consider latency: 5-minute tolerance easily accommodates DSR’s 500ms-2s discovery delay.

Result: Reactive routing (DSR) is optimal. The sparse communication pattern (100 transmissions/day) makes proactive overhead prohibitive. DSR’s discovery delay (1-2 seconds) is negligible compared to the 5-minute latency tolerance.

Key Insight: For IoT deployments with infrequent communication (<1 transmission per node per hour), reactive routing typically provides 10-100x lower overhead than proactive approaches. The key decision factor is the ratio of communication frequency to routing update frequency.

Worked Example: Calculating Multi-Hop Energy Savings

Scenario: A smart agriculture deployment monitors soil moisture across a 500m x 500m field. A sensor at the corner (500m from the gateway) can either transmit directly using high-power mode or use multi-hop through intermediate sensors spaced 100m apart.

Given:

• Direct transmission distance: 500m (diagonal)
• Multi-hop path: 5 hops of 100m each
• Direct transmission power: 100 mW (to achieve 500m range)
• Multi-hop transmission power: 2 mW per hop (for 100m range)
• Packet transmission time: 10 ms
• Relay overhead: 5 ms processing per hop for receive + forward
• Sensor battery: 2400 mAh (2x AA batteries)
• Transmission voltage: 3.3V

Steps:

1. Calculate direct transmission energy:
   • Power: 100 mW at 3.3V = 30.3 mA
   • Duration: 10 ms
   • Energy: 30.3 mA x 10 ms = 0.303 mAs; at 3.3V: 0.303 mAs × 3.3V = 1.0 mJ per packet
2. Calculate multi-hop source energy (just the originating sensor):
   • Power: 2 mW at 3.3V = 0.61 mA
   • Duration: 10 ms
   • Energy: 0.61 mA x 10 ms = 6.1 µAs; at 3.3V: 6.1 µAs × 3.3V = 0.02 mJ per packet
3. Calculate total network energy (all 5 hops):
   • Each hop: transmit (10 ms x 2 mW) + receive (10 ms x 15 mW typical) + process (5 ms x 30 mW)
   • Per hop: 0.02 + 0.15 + 0.15 = 0.32 mJ
   • Total 5 hops: 5 x 0.32 mJ = 1.6 mJ vs. direct: 1.0 mJ
4. Evaluate trade-off:
   • Source sensor savings: 1.0 mJ → 0.02 mJ = 98% reduction
   • Total network energy: Multi-hop uses 1.6x more total energy
   • But energy is distributed across 5 nodes instead of concentrated at one

Result: Multi-hop routing reduces the corner sensor’s energy consumption by 98% (from 84.2 nWh to 1.69 nWh per packet). While total network energy increases 60%, the energy is distributed across multiple nodes, preventing premature battery death at the corner sensor.

Putting Numbers to It

Radio power scales with distance squared: \(P_{tx} \propto d^2\) per Friis equation. For 500m direct at 100 mW, five 100m hops require \(100 \times (100/500)^2 = 4\) mW per hop. Worked example: Direct energy = 100 mW × 10 ms = 1 mJ. Multi-hop source = 4 mW × 10 ms = 0.04 mJ (98% reduction). Network total = 5 hops × 0.32 mJ/hop = 1.6 mJ (60% more), but distributed prevents corner sensor depletion.

Key Insight: Multi-hop routing doesn’t minimize total energy—it distributes energy across multiple nodes. This prevents “energy holes” where sensors near the gateway or at network edges deplete first. For battery-powered networks, energy distribution is often more important than total efficiency.

86.5 Multi-Hop Energy Trade-off Calculator

Compare source sensor energy consumption for direct vs multi-hop transmission:

viewof total_distance = Inputs.range([50, 1000], {value: 500, step: 50, label: "Total distance to gateway (m)"})
viewof hops = Inputs.range([1, 10], {value: 5, step: 1, label: "Number of hops"})
viewof direct_power_mw = Inputs.range([10, 500], {value: 100, step: 10, label: "Direct TX power (mW)"})

{
  const hop_dist = total_distance / hops;
  // Power scales with d^2 (Friis path loss model, simplified)
  const hop_power = direct_power_mw * Math.pow(hop_dist / total_distance, 2);
  const tx_time_ms = 10;
  const direct_energy_mj = direct_power_mw * tx_time_ms / 1000;
  const source_energy_mj = hop_power * tx_time_ms / 1000;
  const savings_pct = ((direct_energy_mj - source_energy_mj) / direct_energy_mj * 100);
  return html`
    <div style="display:grid;grid-template-columns:repeat(3,1fr);gap:1rem;margin:1rem 0">
      <div style="background:#fef9e7;border-left:4px solid #E67E22;padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">Direct TX energy</div>
        <div style="font-size:1.6rem;font-weight:bold;color:#2C3E50">${direct_energy_mj.toFixed(3)} mJ</div>
        <div style="font-size:0.8rem;color:#777">${direct_power_mw} mW × ${tx_time_ms} ms</div>
      </div>
      <div style="background:#eafaf1;border-left:4px solid #16A085;padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">Source hop energy</div>
        <div style="font-size:1.6rem;font-weight:bold;color:#2C3E50">${source_energy_mj.toFixed(4)} mJ</div>
        <div style="font-size:0.8rem;color:#777">${hop_power.toFixed(1)} mW × ${tx_time_ms} ms</div>
      </div>
      <div style="background:#eaf4fb;border-left:4px solid #3498DB;padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">Source energy saved</div>
        <div style="font-size:1.6rem;font-weight:bold;color:#2C3E50">${savings_pct.toFixed(1)}%</div>
        <div style="font-size:0.8rem;color:#777">${hops} hops of ${hop_dist.toFixed(0)}m each</div>
      </div>
    </div>
    <p style="font-size:0.9rem;color:#555">Using simplified Friis model (P ∝ d²): each ${hop_dist.toFixed(0)}m hop needs ${hop_power.toFixed(1)} mW vs ${direct_power_mw} mW for the full ${total_distance}m. Energy saving applies to the <em>source sensor</em> — relay nodes also consume energy.</p>
  `;
}

86.6 Knowledge Check

Test your understanding of these architectural concepts.

Quiz 1: Routing Protocol Selection

Quiz 2: DSDV Sequence Numbers

Quiz 3: Multi-Hop Energy Trade-offs

Quiz 4: ZRP Zone Radius Selection

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

86.7 Visual Reference Gallery

Ad-hoc Network Visualizations

These AI-generated figures provide alternative visual representations of ad-hoc networking concepts covered in this chapter.

86.7.1 Ad-hoc Network Schematic

Ad-hoc Network Schematic

86.7.2 Ad-hoc Routing Protocols

Ad-hoc Routing Protocols

86.7.3 Context-Aware Routing

Context-Aware Routing Example

86.8 Concept Relationships

Concept	Relationship	Connected Concept
Disaster Recovery Networks	Require ad-hoc deployment when	Infrastructure is Destroyed
VANET Mobility	Demands position-based routing handling	67 m/s Closing Speeds
WSN Energy Constraints	Favor reactive routing for	Sparse Communication Patterns
Multi-Hop Energy Distribution	Prevents energy holes by spreading load across	Multiple Relay Nodes
Protocol Selection	Depends on traffic frequency relative to	Routing Update Intervals

86.9 See Also

• Ad-Hoc Networks: Core Concepts - Foundation and characteristics
• Ad-Hoc Networks: Multi-Hop Routing - Protocol mechanics
• Ad Hoc Routing: Proactive (DSDV) - Table-driven approach
• Ad Hoc Routing: Reactive (DSR) - On-demand discovery
• Multi-Hop Fundamentals - Relay and forwarding concepts

Common Pitfalls

1. Designing a Single Protocol for All Ad Hoc Applications

Military MANETs need security and resilience; sensor networks need energy efficiency; VANETs need predictive routing for high mobility. No single routing protocol excels across all these domains. Match protocol characteristics (proactive vs reactive, overhead vs latency) to application-specific requirements.

2. Ignoring Application-Layer Requirements in Network Design

Ad hoc network routing must support application-layer QoS. A video surveillance application needs guaranteed bandwidth; a sensor report application tolerates delay. Designing only at the network layer without considering application requirements produces networks that are technically functional but practically unusable.

3. Underestimating the Importance of Physical Layer in Ad Hoc

Ad hoc network performance depends heavily on radio characteristics: directional antennas reduce interference but require beam management; power control extends battery life but reduces redundancy. Application design must account for physical layer constraints that are often fixed in infrastructure networks.

4. Not Planning for Network Partition in Disaster Scenarios

Disaster response ad hoc networks must function even when the network partitions into disconnected islands. Applications must handle partial connectivity — some responders can communicate, others cannot. DTN-style store-carry-forward and data mule strategies must be in the design from the start for disaster scenarios.

Label the Diagram

💻 Code Challenge

86.10 Summary

This chapter explored the practical applications of ad-hoc networks and provided worked examples to solidify understanding of routing protocol selection and energy trade-offs.

86.10.1 Key Takeaways

1. Diverse Applications: Ad-hoc networks are essential for disaster recovery, military operations, vehicular networks (VANETs), wireless sensor networks (WSNs), and drone swarms (FANETs).

2. Protocol Selection Depends on Traffic:

   • Sparse, infrequent communication -> Reactive routing (DSR, AODV)
   • Dense, continuous communication -> Proactive routing (DSDV, OLSR)
   • Large, heterogeneous networks -> Hybrid routing (ZRP)

3. Energy Distribution Matters: Multi-hop routing doesn’t minimize total energy—it distributes energy across nodes, preventing premature battery death at edge nodes.

4. Overhead Calculations: For sparse traffic (<1 transmission/node/hour), reactive routing provides 10-100x lower overhead than proactive approaches.

5. Scalability Planning: Design for 3-5x initial node count; flat routing struggles beyond 100-200 nodes.

86.10.2 Design Guidelines Summary

• Use proactive routing when: Network is small (<50 nodes), relatively static, and has continuous traffic patterns
• Use reactive routing when: Network is large, mobile, energy-constrained, and has bursty or sparse traffic
• Use hybrid routing when: Network exceeds 100 nodes with heterogeneous mobility and traffic patterns
• Prefer multi-hop when: Coverage area exceeds single-hop radio range (typically >100m for low-power IoT radios)
• Consider infrastructure when: Deployment is permanent, bandwidth requirements are high (>1 Mbps), or ultra-low latency (<50ms) is critical

86.11 What’s Next

If you want to…	Read this
Learn ad hoc routing fundamentals	Ad-Hoc Multi-Hop Routing
Study proactive DSDV routing	DSDV Proactive Routing
Learn reactive DSR routing	DSR Fundamentals and Route Discovery
Explore DTN for disrupted networks	DTN Store-Carry-Forward
Review all ad hoc network concepts	Ad Hoc Networks Review