84  Ad-Hoc Network Concepts

In 60 Seconds

Ad-hoc networks are infrastructure-less, self-organizing wireless networks with five defining characteristics: no infrastructure, self-organizing topology, multi-hop communication, dynamic topology, and distributed control. Use ad-hoc when you cannot deploy infrastructure (disaster zones, remote areas) or when mobility exceeds infrastructure handoff capability.

Minimum Viable Understanding

• Ad-hoc networks are infrastructure-less, self-organizing wireless networks where devices communicate peer-to-peer and every device can act as a router for others
• Five defining characteristics: no infrastructure, self-organizing, multi-hop communication, dynamic topology, and distributed control
• Use ad-hoc when you cannot deploy infrastructure (disaster zones, remote areas, temporary events) or when device mobility is too high for infrastructure handoffs (vehicles, drones)

Sensor Squad: The No-Tower Network

“What if there were NO Wi-Fi routers and NO cell towers?” asked Sammy the Sensor nervously. “How would we talk to each other?”

“Easy!” said Max the Microcontroller. “We talk DIRECTLY to each other! I whisper to Sammy, Sammy whispers to Lila, and Lila whispers to Bella. The message hops from friend to friend!”

“That’s called an ad-hoc network!” Bella the Battery explained. “The word ‘ad-hoc’ means ‘for this purpose’ in Latin. We create a network just when we need it, and it goes away when we’re done!”

Lila the LED demonstrated by blinking a pattern. “Think of it like a bucket brigade at a fire! No fire station needed – people just line up and pass buckets of water hand-to-hand. Each person is both a receiver AND a passer!”

The Squad’s five rules of ad-hoc networks:

1. No towers – devices talk directly to each other
2. Self-organizing – the network forms automatically when devices turn on
3. Multi-hop – messages jump from device to device to reach far away
4. Always changing – devices move around, so the network path changes constantly
5. No boss – every device makes its own routing decisions

84.1 Learning Objectives

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

• Define Ad-Hoc Networks: Explain the concept of infrastructure-less, self-organizing wireless networks and their core principles
• Describe Key Characteristics: Identify and explain the five defining features of ad-hoc networks
• Compare Network Types: Distinguish between ad-hoc and infrastructure-based networks with specific criteria
• Evaluate Trade-offs: Analyze deployment scenarios and justify when ad-hoc networking is the appropriate solution
• Apply to IoT Scenarios: Determine which IoT deployment scenarios require ad-hoc networks and design accordingly

84.2 Prerequisites

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

• Networking Basics for IoT: Understanding IP addressing, packet forwarding, and basic routing concepts
• Wireless Communication Concepts: Familiarity with wireless transmission, signal propagation, and link-layer protocols

For Beginners: What Makes Ad-Hoc Networks Special

Traditional Networks: In Wi-Fi or cellular, every device connects to a central access point or tower. The infrastructure is fixed and pre-deployed.

Ad-Hoc Networks: Devices connect directly to each other, forming a network without any central infrastructure. Every device can be a router, forwarding data for others.

Real-World Analogy: Imagine a town with no roads or postal service. To send a letter across town, you hand it to your neighbor, who hands it to their neighbor, and so on until it reaches the destination. Each person decides who to pass it to next. That’s ad-hoc networking!

Why “Ad-Hoc”? The term means “for this purpose” in Latin—these networks form spontaneously for a specific need and can dissolve when no longer required.

Key Characteristics:

Feature	Ad-Hoc Network	Traditional Network
Infrastructure	None needed	Requires APs/towers
Setup	Instant, self-organizing	Pre-planned deployment
Failure tolerance	High (multiple paths)	Low (single point of failure)
Scalability	Limited (10-100 nodes)	High (thousands)
Latency	Variable (hop count)	Low (direct to AP)

When to Use Ad-Hoc Networks:

• Disaster response (no existing infrastructure)
• Military/tactical (rapid deployment)
• Sensor networks (forests, oceans, farms)
• Vehicle-to-vehicle communication
• Temporary events (concerts, construction sites)

Bottom Line: Use ad-hoc networks when you can’t or don’t want to deploy fixed infrastructure, and devices need to communicate peer-to-peer.

84.3 How It Works: Ad-Hoc Network Formation and Communication

Understanding how ad-hoc networks actually form and route traffic is essential. Here’s a step-by-step walkthrough of the complete lifecycle of communication in an ad-hoc network:

Putting Numbers to It

As hop count increases, end-to-end delivery probability drops multiplicatively.

\[ P_{success} = (1-p_{link})^{h} \]

Where \(p_{link}\) is per-hop loss probability and \(h\) is hop count.

Worked example: If each link loses 8% of packets (\(p_{link}=0.08\)):

\[ \begin{aligned} P_{2hop} &= (0.92)^2 = 84.6\%\\ P_{5hop} &= (0.92)^5 = 65.9\% \end{aligned} \]

Adding one end-to-end retry raises 5-hop success to:

\[ P_{retry} = 1-(1-0.659)^2 = 88.4\% \]

This shows why long multi-hop routes often need reliability mechanisms (retries, alternate paths, or stronger links).

Step 1: Network Discovery (Node Joins Network)

When a new node powers on: 1. Beacon Broadcasting: Node broadcasts periodic “HELLO” messages every 1-2 seconds announcing its presence, including its node ID, supported protocols, and available resources 2. Neighbor Discovery: Existing nodes receive these beacons and add the new node to their neighbor tables with signal strength (RSSI) and link quality metrics 3. Topology Integration: The routing protocol (DSDV, DSR, or ZRP) incorporates the new node into the network topology - proactive protocols immediately share routing updates, reactive protocols wait until a route through this node is needed

Step 2: Route Discovery (Finding a Path)

When Node A wants to send data to Node D:

For Reactive Protocols (DSR/AODV):

1. Route Request Flood: Node A broadcasts a ROUTE_REQUEST packet containing its ID, destination D, and a unique sequence number
2. Intermediate Forwarding: Nodes B and C receive the request and rebroadcast it (after checking they haven’t seen this sequence number before to prevent loops)
3. Destination Reply: When Node D receives the request, it sends a ROUTE_REPLY packet back along the reverse path (D → C → A or D → B → A)
4. Route Caching: Node A stores the discovered route (A → B → D or A → C → D) in its route cache

For Proactive Protocols (DSDV):

1. Pre-Existing Routes: Node A already has a routing table entry for D from periodic updates (destination: D, next-hop: B, hop-count: 2, sequence#: 47)
2. Immediate Forwarding: No route discovery needed - packets sent immediately to next-hop node B

Step 3: Data Transmission (Multi-Hop Forwarding)

1. Packet Preparation: Node A encapsulates data with headers (source: A, destination: D, next-hop: B, TTL: 10)
2. First Hop: Node A wirelessly transmits the packet to neighbor Node B (uses MAC layer addressing and collision avoidance)
3. Intermediate Relay: Node B receives the packet, decrements TTL, looks up next hop for destination D in its routing table, and forwards to next neighbor (Node C or directly to D)
4. Final Delivery: Last hop node delivers packet to destination D’s application layer

Step 4: Link Failure Handling (Topology Change)

If the link between B and D fails (nodes move out of range or B’s battery dies): 1. Failure Detection: Node B detects failure through missing ACKs (3 consecutive transmission failures) or missing periodic beacons from D 2. Route Invalidation: - Reactive protocols: B sends ROUTE_ERROR back to source A, triggering new route discovery - Proactive protocols: B broadcasts routing update with D marked as unreachable (hop-count = infinity, sequence# incremented) 3. Alternative Path: Network reconverges using surviving paths (e.g., A → C → E → D if that path exists)

Step 5: Node Departure (Graceful or Abrupt)

Graceful Shutdown:

• Node broadcasts “GOODBYE” message before powering off
• Neighbors immediately remove it from routing tables

Abrupt Failure (battery dies):

• Neighbors detect absence through missing beacons (timeout after 3 × beacon_interval)
• Routing protocol propagates topology change through update messages

Key Mechanisms Summary:

Mechanism	Purpose	Frequency
Beacon Messages	Announce presence, maintain neighbor list	Every 1-2 sec
Routing Updates	Share topology changes (proactive protocols)	Every 15-30 sec
Route Discovery	Find paths on-demand (reactive protocols)	Only when needed
Route Errors	Notify about broken links	On link failure
ACKs	Confirm successful packet delivery	Per packet

Example Timeline (Reactive Protocol):

t=0s:   Node A wants to send data to D
t=0s:   A floods ROUTE_REQUEST
t=0.1s: B and C rebroadcast request
t=0.2s: D receives request, sends ROUTE_REPLY
t=0.3s: A receives reply, route cached (A→B→D, 2 hops)
t=0.4s: A sends data packet to B
t=0.5s: B forwards to D
t=0.6s: D receives data, sends ACK back
t=5s:   Link B-D breaks (B moves)
t=5.3s: B detects failure (3 missed ACKs)
t=5.4s: B sends ROUTE_ERROR to A
t=5.5s: A initiates new route discovery
t=5.8s: New route found (A→C→E→D, 3 hops)
t=6s:   Data transmission resumes

This walkthrough shows how ad-hoc networks dynamically adapt to topology changes without centralized control - each node independently discovers neighbors, maintains routes, and handles failures using distributed protocols.

84.4 What Is an Ad-Hoc Network?

⏱️ ~8 min | ⭐ Foundational | 📋 P04.C02.U01

An ad-hoc network (also called MANET - Mobile Ad-hoc Network) is a decentralized, self-configuring wireless network where devices communicate directly without relying on pre-existing infrastructure.

Common Misconceptions About Ad-Hoc Networks

Misconception 1: “Ad-hoc networks are always mesh networks”

Reality: Not all ad-hoc networks use mesh topology. Ad-hoc refers to infrastructure-less operation; topology can be star (single-hop), tree, or mesh (multi-hop). Example: Bluetooth piconets are ad-hoc but use star topology (1 master, 7 slaves).

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

Reality: While self-organizing, ad-hoc networks still require initial configuration: radio parameters (frequency, power), security keys (encryption), routing protocol selection. “Self-organizing” means topology forms automatically, not that setup is zero.

Misconception 3: “More hops always mean worse performance”

Reality: Multi-hop can improve performance if single-hop requires high transmit power. Example: 5-hop path using 10 mW/hop (50 mW total) beats 1-hop path using 1000 mW (Friis equation). Energy efficiency improves, though latency increases.

Misconception 4: “Reactive routing is always better for energy”

Reality: Reactive routing saves energy only for sparse traffic. For continuous traffic, route discovery overhead (flooding) exceeds proactive update cost. Example: Smart city sensors reporting every 30 seconds waste energy rediscovering routes; proactive routing is better.

Misconception 5: “Ad-hoc networks can scale infinitely”

Reality: Routing overhead and collision probability limit scalability. Flat ad-hoc networks struggle beyond 100-200 nodes. Solutions: Hierarchical routing (cluster heads), geographic routing (location-based), or hybrid approaches.

Misconception 6: “All nodes must be identical (homogeneous)”

Reality: Heterogeneous ad-hoc networks are common: some nodes have more battery (USB-powered vs coin cell), more memory (gateway vs sensor), or better radios (long-range vs short-range). Routing protocols can exploit heterogeneity (e.g., prefer high-battery nodes as relays).

84.5 Key Characteristics

⭐ Foundational

The five defining characteristics of ad-hoc networks are:

1. No Infrastructure: Devices (nodes) communicate peer-to-peer without access points, base stations, or routers
2. Self-Organizing: Network topology forms automatically as nodes join and leave
3. Multi-Hop Communication: Packets may traverse multiple intermediate nodes to reach destinations
4. Dynamic Topology: Node mobility and failures cause frequent topology changes
5. Distributed Control: No centralized authority; routing decisions made locally

These characteristics differentiate ad-hoc networks from traditional infrastructure-based networks and create unique challenges for routing, security, and resource management.

84.6 Ad-Hoc vs Infrastructure Networks

Schematic of an ad-hoc network showing self-organizing mesh topology with nodes communicating peer-to-peer without central infrastructure

Figure 84.1: Schematic of an ad-hoc network: Nodes self-organize into a mesh topology, with each device capable of acting as both endpoint and relay for multi-hop communication.

Ad-hoc routing protocol visualization

Figure 84.2: Ad-hoc routing protocols enable decentralized path discovery in infrastructure-less networks. Unlike traditional networks with routers, each mobile device participates in routing decisions, dynamically forwarding packets through neighbors toward destinations. This self-organizing capability makes ad-hoc networks resilient to failures and adaptable to changing topologies.

Ad-hoc route discovery process

Figure 84.3: Route discovery in reactive ad-hoc protocols begins with a broadcast flood. The source sends a Route Request (RREQ) that propagates through neighbors until reaching the destination. Each intermediate node records the reverse path, enabling the destination to send a Route Reply (RREP) back to the source. This on-demand approach conserves energy in sparse traffic scenarios.

84.7 Why Ad-Hoc Networks Matter for IoT

Ad-hoc networks are critical for IoT scenarios where:

• Rapid Deployment: Emergency response, military operations, temporary events
• No Infrastructure: Remote areas (forests, oceans, deserts), developing regions
• Cost Constraints: Infrastructure deployment too expensive for sparse node density
• Mobility: Vehicle-to-vehicle (V2V), drone swarms, wearable health monitors
• Resilience: Self-healing networks for critical infrastructure monitoring

Tradeoff Decision Guide: Ad-Hoc vs Infrastructure Networks

Factor	Ad-Hoc Network	Infrastructure Network	When to Choose
Deployment Time	Minutes (self-organizing)	Weeks-months (AP installation)	Ad-hoc for emergency/temporary deployments
Infrastructure Cost	None (peer-to-peer)	High ($500-5K per access point)	Ad-hoc when infrastructure ROI unclear
Scalability	Limited (10-200 nodes typical)	High (thousands per AP)	Infrastructure when >200 nodes needed
Latency	Variable (hop-dependent, 50-500ms)	Low and predictable (<20ms)	Infrastructure for real-time applications
Bandwidth	Limited (shared among hops)	High (dedicated backhaul)	Infrastructure for video/high-throughput
Reliability	Self-healing (multiple paths)	Single point of failure risk	Ad-hoc for mission-critical resilience
Mobility Support	Excellent (dynamic topology)	Limited (handoff overhead)	Ad-hoc for vehicular/drone networks
Management	Complex (distributed)	Simple (centralized)	Infrastructure when IT team available

Quick Decision Rule: Choose ad-hoc networking when you cannot deploy infrastructure (disaster zones, remote areas, temporary events) or when device mobility is too high for infrastructure handoffs (VANETs, drone swarms).

Quick Check: Ad-Hoc Network Fundamentals

Cross-Hub Connections: Ad-Hoc Networks Across the Book

Explore Related Topics:

Protocols Using Ad-Hoc Principles:

• Zigbee Mesh Networking - How Zigbee implements self-healing mesh using AODV-like routing
• Thread Mesh Architecture - Thread’s mesh networking with border routers
• Bluetooth Mesh - Managed flooding and friend nodes for low-power mesh
• RPL for IoT - Proactive routing optimized for low-power lossy networks

Architecture Patterns:

• Wireless Sensor Networks - WSNs as stationary ad-hoc networks with energy constraints
• UAV Networks - Flying ad-hoc networks (FANETs) with 3D topology and high mobility
• Edge Computing Patterns - How edge nodes collaborate in ad-hoc fashion for distributed inference

Design and Simulation:

• Network Design and Simulation - Simulating ad-hoc networks in NS-3, OPNET
• Network Topology Design - Mesh vs star vs tree topology trade-offs
• Simulations Hub - Interactive ad-hoc routing simulators

Security Challenges:

• Threats and Attacks - Sybil attacks, wormholes, and blackholes in ad-hoc networks
• Encryption Architecture - Securing ad-hoc communications without infrastructure

Real-World Applications:

• Smart City Applications - VANET for traffic management
• Industrial IoT - Ad-hoc sensor networks in factories

84.8 Understanding Check: Infrastructure vs Ad-Hoc Trade-offs

Scenario Analysis: Construction Site Monitoring

Scenario: You’re designing a temporary construction site monitoring system for a 6-month project. The site has 30 sensors (dust, noise, vibration) spread across 500m x 500m area. No existing Wi-Fi or cellular coverage. Budget: $10,000 total.

Think about:

1. Should you deploy infrastructure (cellular base station or Wi-Fi APs) or use ad-hoc networking?
2. What are the cost, reliability, and deployment time trade-offs?
3. How does the 6-month temporary nature affect your decision?

Key Insight: Ad-hoc networking is ideal for this scenario.

Cost analysis:

• Infrastructure option: Install 5x Wi-Fi APs ($200 each) = $1,000. Trenching/mounting = $3,000. Monthly internet = $100 x 6 = $600. Total: $4,600 infrastructure + $5,400 for sensors.
• Ad-hoc option: Sensors with mesh radios ($180 each) = $5,400. Gateway with cellular backhaul ($500 + $50/month x 6) = $800. Total: $6,200 (saves $4,400).

Deployment time:

• Infrastructure: 2-3 weeks (permits, installation, wiring).
• Ad-hoc: 2-3 days (place sensors, power on, auto-mesh).

Reliability:

• Infrastructure: Single point of failure (AP down -> all sensors in that zone offline).
• Ad-hoc: Self-healing mesh (sensor fails -> neighbors route around it).

Temporary nature:

• Infrastructure investment wasted after 6 months (Wi-Fi APs remain, but no reuse).
• Ad-hoc sensors relocatable to next site.

Trade-offs: Infrastructure provides higher bandwidth and lower latency, but ad-hoc’s cost and deployment advantages dominate for temporary deployments.

General rule: Use ad-hoc for temporary (<1 year), mobile, or infrastructure-less scenarios. Use infrastructure for permanent deployments with high bandwidth needs.

Test Your Understanding

Question 1: Which of the following is NOT one of the five defining characteristics of ad-hoc networks?

1. No infrastructure required
2. Centralized control authority
3. Self-organizing topology
4. Multi-hop communication

Answer

b) Centralized control authority. Ad-hoc networks use DISTRIBUTED control, not centralized. The five defining characteristics are: no infrastructure, self-organizing, multi-hop communication, dynamic topology, and distributed control. The absence of central authority is fundamental – every node makes its own routing decisions independently.

Question 2: A construction company needs temporary monitoring for a 6-month project site with 30 sensors and no existing network coverage. Budget is $10,000. Should they use ad-hoc networking or deploy infrastructure?

1. Infrastructure – always more reliable
2. Ad-hoc – faster deployment, lower cost, and sensors can be reused at the next site
3. Neither – cellular is always available
4. Infrastructure – sensors need centralized management

Answer

b) Ad-hoc networking. For temporary deployments (<1 year), ad-hoc provides: faster deployment (2-3 days vs 2-3 weeks), lower infrastructure cost (no access point installation), self-healing mesh resilience, and sensor reusability at the next project site. Infrastructure’s advantages (higher bandwidth, lower latency) are unnecessary for periodic sensor readings.

Question 3: What does the term “ad-hoc” literally mean, and why is it appropriate for these networks?

1. “Without wires” – because they use wireless communication
2. “For this purpose” – because networks form spontaneously for a specific need
3. “Always on” – because they operate continuously
4. “Many paths” – because they use multi-hop routing

Answer

b) “For this purpose” in Latin. Ad-hoc networks form spontaneously when needed and can dissolve when the purpose is fulfilled. This perfectly describes networks for disaster response (form when earthquake hits, dissolve when infrastructure restores), temporary events (concert, construction site), or mobile scenarios (vehicle convoys that meet and separate).

84.9 Real-World Deployment: Disaster Response Ad-Hoc Networks

Case Study: Mesh Networking After Hurricane Maria (Puerto Rico, 2017)

Background: When Hurricane Maria destroyed 95% of Puerto Rico’s cellular towers in September 2017, leaving 3.4 million residents without communication for weeks, multiple organizations deployed ad-hoc mesh networks to restore connectivity. The most documented effort was by the open-source goTenna project and the American Red Cross.

Deployment Details:

Parameter	Value
Area covered	42 km squared (San Juan metro)
Nodes deployed	175 goTenna Mesh units + 30 relay nodes
Network type	Multi-hop ad-hoc mesh (up to 6 hops)
Per-node cost	$179 (consumer device)
Frequency	900 MHz ISM band
Per-hop range	1-4 km (line of sight), 0.5-1 km (urban)
Power	1 W transmit, internal battery (24-hour life)
Deployment time	3 days (first node online within 4 hours of arrival)

Performance vs Infrastructure Alternatives:

Metric	Ad-Hoc Mesh (goTenna)	Portable Cell Tower (AT&T COW)	Satellite Phone (Iridium)
Setup time	4 hours	48-72 hours	Immediate (per phone)
Cost for 200 users	$35,800 (200 units)	$250,000+ (one COW)	$260,000 (200 phones at $1,300)
Coverage area	42 km squared (multi-hop)	2-5 km squared (single cell)	Global (but point-to-point only)
Throughput	Text/GPS only (no voice/video)	Full cellular (voice + data)	2.4 kbps (voice only)
Power requirement	USB battery pack per node	Diesel generator (500 L/week)	Per-phone battery
Self-healing	Yes (automatic re-routing)	No (single point of failure)	N/A (no mesh)
Maintenance	None (consumer hardware)	Trained technician required	None

Operational Lessons:

1. Ad-hoc was fastest to deploy but lowest bandwidth: The mesh network provided text messaging and GPS location sharing within 4 hours. This was sufficient for coordinating relief logistics (where to deliver water, which roads were passable) but could not support voice calls or data-heavy applications.

2. 6-hop limit was the practical ceiling: Beyond 6 hops, end-to-end latency exceeded 30 seconds for a single text message, and delivery probability dropped below 60%. The team placed solar-powered relay nodes on hilltops to reduce average hop count from 4.2 to 2.8 hops.

3. Heterogeneous nodes improved resilience: The 30 dedicated relay nodes (mounted on rooftops with solar panels and external antennas) provided backbone connectivity. The 175 consumer units connected to this backbone within 1-2 hops. This hybrid approach (infrastructure-like relays + ad-hoc consumer nodes) outperformed a purely homogeneous deployment by 40% in delivery rate.

4. The $35,800 ad-hoc network complemented, not replaced, infrastructure: Once AT&T deployed portable cell towers (3 weeks after the hurricane), the mesh network became a fallback for areas still without cellular coverage. The two systems coexisted, with the mesh handling coordination in remote barrios while cellular served dense urban centers.

Decision Framework from This Experience:

Use Ad-Hoc When	Use Portable Infrastructure When
First 0-72 hours (immediate response)	After 72 hours (sustained operations)
Text/location sufficient	Voice/video required
Many small coverage areas	Few large coverage areas
No trained telecom staff available	Trained technicians on site
Budget < $50,000	Budget > $100,000
Terrain prevents vehicle access	Vehicle access available for generators

Worked Example: Disaster Response Network Deployment Cost-Benefit Analysis

Scenario: Earthquake destroys cellular infrastructure across 20 km² area. Emergency responders need communication within 2 hours. Compare ad-hoc vs. infrastructure restoration.

Option 1 - Infrastructure Restoration:

• Deploy portable cell tower (COW - Cell on Wheels): $250,000/unit
• Coverage area per tower: 2-5 km² → Need 4-10 towers
• Setup time: 24-72 hours (transport, power, backhaul connection)
• Diesel fuel: $500/day per tower
• Cost for 7-day operation: 5 towers × ($250K + $3,500 fuel) = $1.27M
• Availability: 24-72 hours after disaster

Option 2 - Ad-Hoc Mesh Network (goTenna Mesh):

• Deploy 200 mesh nodes carried by responders: $179/unit = $35,800
• Coverage: Each responder becomes a node, automatic multi-hop mesh forms
• Setup time: 4 hours (distribute devices, power on, auto-mesh)
• Power: USB battery packs ($20/node) = $4,000
• Cost for 7-day operation: $35,800 hardware + $4,000 batteries = $39,800
• Availability: 4 hours after disaster

Comparison:

Metric	Infrastructure	Ad-Hoc Mesh	Winner
Deployment cost	$1.27M	$39.8K	Ad-hoc (97% cheaper)
Time to operational	24-72 hours	4 hours	Ad-hoc (6-18× faster)
Coverage flexibility	Fixed tower locations	Follows responders	Ad-hoc
Throughput	100+ Mbps (full cellular)	Text/GPS only (~10 kbps)	Infrastructure
Resilience	Single point of failure	Self-healing mesh	Ad-hoc
Maintenance	Requires technicians	Zero maintenance	Ad-hoc

Decision: Ad-hoc mesh for initial 24-48 hours (critical for life-saving), then add infrastructure for bandwidth-intensive operations (video, large data transfers).

Result: First responders use ad-hoc text/GPS coordination to save lives in first 48 hours, while infrastructure teams deploy portable towers for sustained operations.

Concept Check: Ad-Hoc Network Characteristics

Test your understanding of the key concepts covered so far.

Decision Framework: Ad-Hoc vs. Infrastructure Network Selection

Decision Criteria	Infrastructure Network	Ad-Hoc Network	Scoring
Deployment duration	>1 year permanent	<1 year temporary	+5 for ad-hoc if <1yr
Setup time available	Weeks-months acceptable	Hours-days required	+5 for ad-hoc if <7 days
Device count	>200 devices	<200 devices	+3 for ad-hoc if <200
Bandwidth needs	>10 Mbps per device	<1 Mbps per device	+5 for ad-hoc if <1 Mbps
Mobility	Fixed/slow (<5 km/h)	High mobility (>20 km/h)	+5 for ad-hoc if >20 km/h
Budget	>$100K available	<$100K budget	+5 for ad-hoc if <$100K
Expertise available	Network engineers on staff	No IT staff	+3 for ad-hoc if no staff

Scoring:

• Total >15: Ad-hoc recommended
• Total 5-15: Hybrid (ad-hoc for bootstrap, infrastructure for scale)
• Total <5: Infrastructure preferred

Example 1 - Construction Site Monitoring (6-month project, 30 sensors, <1 Mbps, $50K budget): - Duration: +5, Setup: +0, Devices: +3, Bandwidth: +5, Mobility: +0, Budget: +5, Expertise: +3 = 21 → Ad-hoc

Example 2 - Smart Campus (permanent, 5,000 devices, 10 Mbps per device, $2M budget): - Duration: +0, Setup: +0, Devices: +0, Bandwidth: +0, Mobility: +0, Budget: +0, Expertise: +0 = 0 → Infrastructure

Example 3 - Vehicular Network (VANET, 100 vehicles, <1 Mbps, 100 km/h): - Duration: +0, Setup: +0, Devices: +3, Bandwidth: +5, Mobility: +5, Budget: +0, Expertise: +0 = 13 → Hybrid (ad-hoc V2V, infrastructure V2I)

Common Mistake: Deploying Ad-Hoc Networks Beyond Scalability Limits

The Mistake: Using flat ad-hoc routing protocols (DSR, AODV) for networks with >100 nodes, assuming they scale linearly.

Reality Check: Routing overhead in flat ad-hoc networks grows O(n²) with node count due to route discovery flooding.

Measured Impact (from ns-2 simulation validated against testbeds):

Network Size	AODV Routing Overhead (% of bandwidth)	Packet Delivery Ratio	Avg. End-to-End Latency
25 nodes	8%	96%	120ms
50 nodes	18%	91%	280ms
100 nodes	42%	78%	850ms
200 nodes	73%	51%	2,400ms
500 nodes	91%	22%	>10,000ms

At 200 nodes, 73% of available bandwidth is consumed by routing protocol overhead (route discoveries, updates, error messages), leaving only 27% for actual data. Packet delivery drops below 50% because collisions and congestion from routing traffic cause data loss.

Why It Happens:

• Each route discovery floods entire network (N nodes receive broadcast)
• With C concurrent communications, C × N route discovery packets in flight
• Collision probability scales with network density
• Mobile nodes cause frequent route breaks → rediscoveries

Correct Approaches for Large Networks:

Option 1 - Hierarchical Routing (ZRP, CBRP): - Divide network into clusters (20-30 nodes each) - Intra-cluster: Use proactive routing (low overhead within small cluster) - Inter-cluster: Use reactive routing (only for cross-cluster traffic) - Overhead reduction: 200 nodes → 10 clusters = 95% vs. 73% overhead

Option 2 - Geographic Routing (GPSR): - Use GPS location instead of flooding - Forward packets toward destination coordinates - No route discovery needed - Overhead: <5% regardless of network size

Option 3 - Hybrid Fog Architecture:

• Ad-hoc for local clusters (20-50 nodes each)
• Infrastructure gateways connect clusters
• Best of both worlds: ad-hoc flexibility, infrastructure scalability

Decision Rule:

• <50 nodes: Flat ad-hoc (DSR, AODV) acceptable
• 50-200 nodes: Consider hierarchical (ZRP) or geographic (GPSR)

• 200 nodes: Infrastructure or hybrid mandatory

Real Example: Military tactical network tried deploying 300-node flat ad-hoc AODV network. Result: <30% packet delivery, >5s latency, unusable. Migrated to hierarchical ZRP with 15-node clusters → 85% delivery, <800ms latency.

84.10 Try It Yourself: Design a Disaster Response Ad-Hoc Network

Apply the concepts from this chapter to design an ad-hoc network for a realistic scenario. Work through the exercise step-by-step, then compare your decisions with the provided analysis.

Scenario:

An earthquake has destroyed cellular infrastructure across a 15 km² urban area. Emergency responders need to coordinate rescue operations across 8 teams (40 people total). The command center is located centrally, and teams will be distributed across damaged buildings.

Your Design Task:

You have two technology options:

Option A: Consumer Mesh Radios

• Cost: $180/unit
• Range: 0.5-1 km (urban environment with obstacles)
• Power: USB battery pack, 24-hour battery life
• Throughput: Text messaging and GPS only (~10 kbps)
• Setup complexity: Power on and automatic mesh formation (zero configuration)

Option B: Professional Portable Repeaters

• Cost: $2,500/unit for repeater + $400/handheld radio
• Range: 2-5 km per repeater (high power)
• Power: Requires generator or vehicle power
• Throughput: Voice communication (full-duplex)
• Setup complexity: Repeaters need manual positioning and configuration (2-4 hours)

Questions to Answer:

1. Node count: How many devices do you deploy for each option?
2. Topology: Draw the expected network topology (star, mesh, hybrid?)
3. Coverage strategy: Where do you place fixed nodes (if any) to maximize coverage?
4. Timeline: When will the network be operational?
5. Cost: Total deployment cost for each option?
6. Bandwidth requirements: Will text/GPS be sufficient, or do you need voice?
7. Power sustainability: How do you ensure 7-day operation?

Work Through Your Solution:

Before checking the analysis below, write down: - Your chosen technology option (A or B, or hybrid?) - Number of devices and placement strategy - Estimated cost and deployment timeline - Key trade-offs you considered

Analysis and Discussion

Recommended Solution: Hybrid Approach (Option A for responders + Option B backbone)

Deployment Plan:

1. Immediate Phase (0-4 hours): Option A Consumer Mesh
   • Deploy 40 units (one per responder): 40 × $180 = $7,200
   • Additional 10 units for fixed relay positions (building rooftops): 10 × $180 = $1,800
   • Topology: Mobile ad-hoc mesh (responders) connected to fixed relays forming a backbone
   • Coverage: 15 km² requires ~15 relay nodes at 1 km spacing, but only 10 deployed initially (60% coverage, expanded as needed)
   • Operational: Within 1 hour of distribution (automatic mesh formation)
   • Use case: Text coordination (“Building 5 cleared,” “Medical needed at Grid D-4,” GPS location sharing)
2. Sustained Phase (24-72 hours): Add Option B Professional Repeaters
   • Deploy 3 repeaters at strategic high points: 3 × $2,500 = $7,500
   • Deploy 8 handheld radios (one per team leader): 8 × $400 = $3,200
   • Topology: Star topology (repeaters serve as hubs), with ad-hoc mesh as backup
   • Coverage: 3 repeaters at 4 km spacing cover full 15 km² with voice communication
   • Operational: 24-48 hours (requires generator transport and setup)
   • Use case: Voice coordination for complex operations, command center communication

Total Cost: $19,700 ($7,200 + $1,800 + $7,500 + $3,200)

Justification for Hybrid Approach:

Requirement	Option A Only	Option B Only	Hybrid (A+B)
Speed	✓ Operational in 1 hour	✗ 24-48 hour setup	✓ Mesh ready in 1 hour, voice in 48 hours
Coverage	⚠ 50 nodes needed for full 15 km² (1 km range)	✓ 3 repeaters sufficient (4 km range)	✓ Best of both
Cost	50 × $180 = $9,000	3 × $2,500 + 40 × $400 = $23,500	$19,700 (16% cheaper than B-only)
Bandwidth	✗ Text only (no voice)	✓ Voice (essential for complex coordination)	✓ Text first 24h, voice after
Power	✓ USB batteries (easy)	✗ Generators (logistically complex)	⚠ Generators needed after 24h
Resilience	✓ Self-healing mesh	✗ Single point of failure per repeater	✓ Mesh as fallback

Key Insights:

1. First 24 hours are life-critical: Ad-hoc mesh provides immediate text/GPS coordination when voice is unavailable. This saves lives (responders locate survivors, call for medical transport, avoid collapsed structures).

2. Voice becomes essential for sustained operations: After initial rescue, coordinating complex tasks (equipment sharing, resource allocation, multi-team operations) requires voice. Text is too slow.

3. Mesh provides resilience: If a repeater fails (power loss, damage), the ad-hoc mesh automatically reroutes around the failure. Without mesh, repeater failure creates a coverage blackout.

4. Cost is dominated by scale: 40 responders × $400 handhelds = $16,000 in Option B. Hybrid uses cheaper mesh radios ($180) for most users, reserving expensive professional gear for team leaders and command center.

Alternative Approaches:

• Option A only (pure mesh): Cheaper ($9,000) and faster (1 hour), but no voice communication. Acceptable if text/GPS is truly sufficient (small-scale operations, trained responders with standardized procedures).

• Option B only (professional gear): Best performance (voice + longer range) but slowest deployment (48 hours) and most expensive ($23,500). Acceptable if you have 48 hours before operations start (e.g., pre-positioning before a hurricane).

• Delay professional gear until needed: Start with mesh ($9,000), add repeaters only if voice proves necessary. Risk: If you need voice on Day 2, you lose 48 hours waiting for repeater deployment.

What to Observe:

After deployment, monitor these metrics to validate your design:

• Connectivity: What % of responder-to-command messages are delivered successfully? (Target: >90% for mesh, >98% for repeaters)
• Latency: How long does a text message take to reach the command center? (Mesh: expect 5-20 seconds for multi-hop, Repeater: <1 second for voice)
• Hop count: In the mesh network, what’s the average number of hops per message? (Target: <4 hops; if >6 hops, coverage is too sparse, add more fixed relays)
• Power consumption: How long do batteries last in practice? (Mesh: 24 hours if users transmit every 5 minutes, 48+ hours if transmit every 30 minutes)
• Failure recovery: If a repeater goes down, how quickly does the mesh reroute? (Should be automatic within 30-60 seconds)

Connection to Chapter Concepts:

This exercise applied all five ad-hoc characteristics:

1. No Infrastructure: Cellular destroyed, mesh forms peer-to-peer
2. Self-Organizing: Mesh topology forms automatically, no manual routing
3. Multi-Hop: Responders relay for each other (0.5-1 km range → 5-10 hops across 15 km²)
4. Dynamic Topology: Responders move between buildings, mesh adapts
5. Distributed Control: Each node independently decides next hop based on local neighbor table

You also applied the decision framework: Ad-hoc wins for rapid deployment (<4 hours), low bandwidth (text/GPS), and resilience. Infrastructure (repeaters) wins for high bandwidth (voice) and large coverage per node. Hybrid combines strengths.

Label the Diagram

💻 Code Challenge

84.11 Summary

Ad-hoc networks represent a fundamental paradigm shift from infrastructure-based networking to decentralized, self-organizing wireless communication. This chapter introduced the core concepts and characteristics that define ad-hoc networks.

84.11.1 Key Takeaways

1. Infrastructure-Less Operation: Ad-hoc networks eliminate the need for pre-deployed access points, base stations, or routers, enabling rapid deployment in remote, temporary, or disaster-affected areas.

2. Five Defining Characteristics: No infrastructure, self-organizing, multi-hop communication, dynamic topology, and distributed control.

3. Trade-Offs vs Infrastructure:

   • Ad-hoc offers rapid deployment, self-healing, and no infrastructure cost
   • Infrastructure offers higher bandwidth, lower latency, and better scalability

4. IoT Relevance: Ad-hoc networks are essential for disaster recovery, military operations, vehicular networks, sensor deployments, and drone swarms.

5. Decision Framework: Choose ad-hoc when infrastructure deployment is impractical, temporary, or when device mobility is high.

84.11.2 Common Pitfalls to Avoid

1. Assuming self-organizing means zero configuration: Radio parameters, security keys, and routing protocols still require careful setup
2. Expecting infinite scalability: Flat ad-hoc networks struggle beyond 100-200 nodes
3. Confusing ad-hoc with mesh: Ad-hoc is infrastructure-less; topology can vary

84.12 Multi-Hop Delivery Probability Calculator

Explore how per-hop packet loss affects end-to-end delivery probability in multi-hop ad-hoc networks:

viewof link_loss_pct = Inputs.range([0, 30], {value: 8, step: 1, label: "Per-hop packet loss (%)"})
viewof hop_count = Inputs.range([1, 15], {value: 5, step: 1, label: "Number of hops"})
viewof retries = Inputs.range([0, 3], {value: 1, step: 1, label: "End-to-end retries"})

{
  const p_success_per_hop = 1 - link_loss_pct / 100;
  const p_e2e = Math.pow(p_success_per_hop, hop_count);
  const p_with_retry = 1 - Math.pow(1 - p_e2e, retries + 1);
  return html`
    <div style="display:grid;grid-template-columns:repeat(3,1fr);gap:1rem;margin:1rem 0">
      <div style="background:#eaf4fb;border-left:4px solid #3498DB;padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">Per-hop success</div>
        <div style="font-size:1.8rem;font-weight:bold;color:#2C3E50">${(p_success_per_hop * 100).toFixed(0)}%</div>
      </div>
      <div style="background:${p_e2e > 0.8 ? '#eafaf1' : p_e2e > 0.6 ? '#fef9e7' : '#fdf2f8'};border-left:4px solid ${p_e2e > 0.8 ? '#16A085' : p_e2e > 0.6 ? '#E67E22' : '#E74C3C'};padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">E2E delivery (no retry)</div>
        <div style="font-size:1.8rem;font-weight:bold;color:#2C3E50">${(p_e2e * 100).toFixed(1)}%</div>
        <div style="font-size:0.8rem;color:#777">${(p_success_per_hop * 100).toFixed(0)}%^${hop_count}</div>
      </div>
      <div style="background:#eafaf1;border-left:4px solid #16A085;padding:1rem;border-radius:4px">
        <div style="font-size:0.85rem;color:#555">With ${retries} retr${retries===1?'y':'ies'}</div>
        <div style="font-size:1.8rem;font-weight:bold;color:#2C3E50">${(p_with_retry * 100).toFixed(1)}%</div>
      </div>
    </div>
    <p style="font-size:0.9rem;color:#555">${hop_count}-hop path with ${link_loss_pct}% per-hop loss: P(success) = (${(p_success_per_hop).toFixed(2)})^${hop_count} = ${(p_e2e * 100).toFixed(1)}%. ${retries > 0 ? `Adding ${retries} retry improves to ${(p_with_retry * 100).toFixed(1)}%.` : 'Add retries to see the improvement.'}</p>
  `;
}

84.13 Knowledge Check

Quiz: Ad-Hoc Network Concepts

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

84.14 Concept Relationships

Understanding how ad-hoc network concepts relate to each other and to broader networking principles helps build a cohesive mental model. The table below maps key relationships between concepts covered in this chapter.

Concept A	Relationship	Concept B	Explanation
No Infrastructure	enables	Rapid Deployment	Eliminating the need to deploy access points or base stations reduces setup time from weeks to hours (e.g., disaster response networks operational in 4 hours vs. 48+ hours for portable cell towers)
Self-Organizing	depends on	Routing Protocols	Topology forms automatically, but nodes must run distributed routing protocols (DSDV, DSR, ZRP) to discover neighbors and maintain paths without central coordination
Multi-Hop Communication	trades off	Latency vs. Range	Multi-hop extends network coverage beyond single-hop radio range, but each hop adds 10-50ms latency and reduces delivery probability (90% delivery per hop → 59% after 5 hops)
Dynamic Topology	challenges	Route Stability	Node mobility and failures cause frequent topology changes, forcing routing protocols to balance fast convergence (quick route updates) vs. overhead (control message bandwidth)
Distributed Control	increases	Resilience	No single point of failure - if one node fails, neighbors automatically reroute around it (self-healing), unlike infrastructure networks where AP failure creates coverage blackout
Distributed Control	increases	Routing Overhead	Each node independently maintains routing tables or caches, duplicating effort across the network (O(n²) state for n nodes in proactive protocols)
Heterogeneous Nodes	improves	Energy Efficiency	Mixing high-capability nodes (solar-powered relays) with low-power nodes (battery sensors) allows relays to handle routing overhead while sensors conserve energy
Heterogeneous Nodes	requires	Protocol Awareness	Routing protocols must account for node differences - preferring high-battery nodes as relays, avoiding resource-constrained nodes for forwarding
Sequence Numbers (DSDV)	prevents	Routing Loops	Monotonically increasing sequence numbers ensure fresher route information always wins, preventing stale routes that could create forwarding loops
Route Discovery (DSR)	trades	Zero Overhead for Unused Routes vs. Discovery Latency	Reactive protocols save bandwidth by not maintaining routes to all destinations, but incur latency when discovering routes on-demand (flooding ROUTE_REQUEST packets)
Hop Count	is a	Routing Metric	Shortest-path routing uses hop count as metric (fewest intermediate nodes), but alternative metrics (ETX, link quality, residual energy) may provide better performance
Ad-Hoc Networks	suitable for	Sparse Traffic	Reactive routing excels when nodes communicate infrequently (route discovery cost < periodic update cost), e.g., sensor networks transmitting once per hour
Ad-Hoc Networks	unsuitable for	Dense Traffic	Constant communication requires proactive routing (routes always ready), otherwise reactive discovery overhead exceeds useful data traffic
Proactive Routing	example	DSDV Protocol	Proactive (table-driven) routing maintains complete routing tables at all times via periodic updates - DSDV is the canonical example using distance-vector + sequence numbers
Reactive Routing	example	DSR Protocol	Reactive (on-demand) routing discovers routes only when needed - DSR floods ROUTE_REQUEST and caches discovered paths in packet headers (source routing)
Beacon Messages	enable	Neighbor Discovery	Periodic HELLO broadcasts (every 1-2 sec) announce node presence, allowing neighbors to build and maintain neighbor tables for routing decisions
Link Failure	triggers	Route Invalidation	Broken links detected via missing ACKs cause nodes to mark routes as invalid (hop count = ∞) and propagate ROUTE_ERROR messages to sources
Scalability Limit	caused by	O(n²) Overhead	Flat ad-hoc networks struggle beyond 100-200 nodes because routing state and control traffic grow quadratically with node count (n nodes × n destinations × periodic updates)

Key Insight from Relationships:

The five defining characteristics (no infrastructure, self-organizing, multi-hop, dynamic topology, distributed control) are not independent - they form a dependency chain:

1. No infrastructure mandates distributed control (no central authority exists)
2. Distributed control requires self-organizing protocols (nodes must coordinate peer-to-peer)
3. Self-organizing enables dynamic topology (network adapts to changes automatically)
4. Dynamic topology necessitates multi-hop communication (nodes move, direct links break, packets must route around failures)
5. Multi-hop routing creates scalability challenges (every node is a router, overhead grows with network size)

Understanding these relationships helps you predict trade-offs: improving one characteristic (e.g., faster convergence for dynamic topology) often degrades another (e.g., increased routing overhead). Effective ad-hoc network design requires balancing these interconnected concepts based on application requirements.

84.15 See Also

Expand your understanding of ad-hoc networks by exploring related concepts and protocols:

Foundation Concepts:

• Networking Basics for IoT - Packet forwarding, routing tables, and IP addressing fundamentals that underpin ad-hoc routing protocols
• Routing Fundamentals - Distance-vector vs. link-state routing algorithms, metrics (hop count, ETX), and loop prevention mechanisms adapted by ad-hoc protocols
• Wireless Sensor Networks - Infrastructure-less sensor deployments where ad-hoc routing is essential for multi-hop data collection

Ad-Hoc Routing Protocols (Deep Dives):

• Ad-Hoc Routing: Proactive (DSDV) - Table-driven routing with periodic updates, sequence numbers for loop prevention, and complete routing tables at all nodes
• Ad-Hoc Routing: Reactive (DSR) - On-demand source routing with route caching, flooding-based discovery, and minimal overhead for sparse traffic
• Ad-Hoc Routing: Hybrid (ZRP) - Zone-based approach combining proactive intra-zone routing with reactive inter-zone discovery for scalability
• Multi-Hop Routing Fundamentals - Detailed coverage of routing paradigms, metrics, and protocol comparison frameworks

Related Network Architectures:

• Mesh Networks - Relationship between ad-hoc (infrastructure-less) and mesh (multi-hop topology) - not all ad-hoc networks use mesh, not all meshes are ad-hoc
• WSN Network Topologies - Star vs. tree vs. mesh topologies in wireless sensor networks, trade-offs for battery-constrained ad-hoc deployments
• Edge Computing Architectures - Hybrid architectures combining ad-hoc edge nodes with cloud infrastructure for resilience

Wireless Technologies Enabling Ad-Hoc:

• 802.15.4 Fundamentals - Low-power physical layer used by Zigbee and Thread ad-hoc networks
• Bluetooth Mesh - Managed flooding-based ad-hoc mesh for BLE devices
• LoRa and LoRaWAN - Long-range wireless suitable for sparse ad-hoc sensor networks (though LoRaWAN itself uses star topology)

Challenges and Advanced Topics:

• Security in Ad-Hoc Networks - Distributed authentication, sybil attacks, black hole attacks, and wormhole attacks unique to infrastructure-less networks
• Energy-Efficient Routing - Power-aware routing metrics, duty cycling, and topology control for battery-powered ad-hoc nodes
• Geographic Routing - Location-based routing (GPSR, GEAR) that scales better than topology-based approaches for large ad-hoc networks

Real-World Applications:

• Vehicular Ad-Hoc Networks (VANETs) - V2V communication, high-mobility challenges, DSRC/802.11p protocols
• Disaster Response IoT Systems - Case studies of ad-hoc deployments in earthquakes, hurricanes, and search-and-rescue operations
• Military Tactical Networks - Rapidly deployable, resilient ad-hoc networks for battlefield communications (inspiration for early MANET research)

84.16 What’s Next

If you want to…	Read this
Learn multi-hop routing protocols	Multi-Hop Routing and Protocols
Explore real-world ad hoc applications	Applications and Practice
Study DSDV proactive routing in depth	Ad-hoc Routing: Proactive (DSDV)
Study DSR reactive routing in depth	Ad-hoc Routing: Reactive (DSR)
Explore hybrid zone-based routing	Ad-hoc Routing: Hybrid (ZRP)