33  UAV Network Topologies

In 60 Seconds

UAV networks (FANETs) are flying ad hoc networks where drones serve as mobile sensors, relay stations, or base stations that deploy in minutes. Star topology suits single-hub missions (simple, single point of failure); mesh topology enables resilient multi-UAV swarms with automatic failover; hierarchical combines both. UAVs at 300m altitude cover 25× more area than equivalent ground nodes by leveraging line-of-sight propagation above buildings and terrain.

33.1 Overview

Unmanned Aerial Vehicles (UAVs), commonly known as drones, are transforming IoT architectures by providing aerial sensing, mobile base stations, and rapid deployment capabilities. UAV networks, particularly Flying Ad Hoc Networks (FANETs), enable dynamic, three-dimensional communication infrastructures for applications ranging from disaster response to smart agriculture.

This chapter series covers the complete foundation of UAV networks for IoT applications. The content has been organized into focused modules for easier learning.

MVU: Minimum Viable Understanding

Core concept: UAV networks (FANETs) are flying ad-hoc networks where drones serve as mobile sensor platforms, flying base stations, or data relays that can be deployed in minutes. Why it matters: Drones provide instant coverage where ground infrastructure is destroyed, inaccessible, or too expensive to build permanently. Key takeaway: Choose star topology for simple missions with one control point, mesh for resilient multi-drone swarms, and hierarchical for large-scale operations with ground integration.

33.2 Chapter Series

This comprehensive UAV networks topic is organized into the following focused chapters:

33.2.1 1. UAV Introduction and Fundamentals

Estimated time: 15-20 minutes

Start here to learn the basics of UAV networks and their role in IoT systems:

• What are UAV networks and FANETs
• Three roles of UAVs: mobile sensors, aerial base stations, data relays
• Real-world applications in disaster response, agriculture, and search & rescue
• Why UAVs offer capabilities ground networks cannot match

33.2.2 2. UAV Network Features and Challenges

Estimated time: 20-25 minutes

Understand the core capabilities and constraints of UAV networks:

• Core features: flexible topology, wide coverage, rapid deployment
• 3D mobility challenges and topology changes
• Energy constraints and battery trade-offs
• Environmental effects (wind, temperature, weather)
• Communication range planning with worked examples

33.2.3 3. UAV Network Topologies

Estimated time: 15-20 minutes

Compare and select network topologies for different missions:

• Star topology: centralized control, simple coordination
• Mesh topology: distributed resilience, multi-hop routing
• Topology comparison and selection criteria
• Multi-hop relay network design

33.2.4 4. UAV Swarm Coordination

Estimated time: 20-25 minutes

Learn how multiple UAVs work together cooperatively:

• Coordination algorithms: centralized, distributed consensus, leader-follower
• Payload capacity trade-offs and sensor selection
• Operational fleet sizing for 24/7 coverage
• Regulatory compliance strategies (VLOS, BVLOS)
• Environmental planning for extreme conditions

33.2.5 5. UAV Interactive Lab

Estimated time: 45-60 minutes

Hands-on FANET simulation with ESP32:

• Complete working code for 4-drone swarm simulation
• Mesh network formation and neighbor discovery
• Multi-hop message relay implementation
• Leader election algorithms
• Formation control patterns
• Five guided exercises with solutions

33.3 Learning Path

33.4 Interactive: UAV Coverage Area Calculator

Calculate how many UAVs you need to cover a given area based on altitude and camera field of view:

viewof altitude_uav = Inputs.range([50, 500], {value: 100, step: 10, label: "UAV Altitude (m)"})

viewof fov_uav = Inputs.range([60, 150], {value: 120, step: 5, label: "Camera Field of View (degrees)"})

viewof area_uav = Inputs.range([10, 1000], {value: 500, step: 10, label: "Total Area to Cover (hectares)"})

{
  const r = altitude_uav * Math.tan((fov_uav / 2) * Math.PI / 180);
  const coveragePerUAV = Math.PI * r * r / 10000; // hectares
  const effectiveCoverage = coveragePerUAV * 0.8; // 20% overlap
  const uavsNeeded = Math.ceil(area_uav / effectiveCoverage);
  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid #16A085; margin-top: 0.5rem;">
  <p><strong>Ground Radius per UAV:</strong> ${r.toFixed(0)} m</p>
  <p><strong>Coverage Area per UAV:</strong> ${coveragePerUAV.toFixed(1)} ha (${(coveragePerUAV * 0.8).toFixed(1)} ha effective with 20% overlap)</p>
  <p><strong>UAVs Needed:</strong> ${uavsNeeded} UAVs for ${area_uav} ha</p>
  <p style="font-size: 0.85em; color: #666;">Formula: radius = altitude × tan(FOV/2); coverage = π×r²; 20% overlap assumed for image stitching.</p>
  </div>`;
}

33.5 Learning Objectives

By completing this chapter series, you will be able to:

• Classify UAV Network Types: Distinguish between single-UAV, multi-UAV, and FANET architectures
• Design UAV Topologies: Select appropriate network topologies (star, mesh, hierarchical) for aerial IoT applications
• Analyze 3D Mobility Challenges: Explain routing and coordination challenges unique to three-dimensional UAV networks
• Implement Aerial Base Stations: Deploy UAVs as temporary wireless access points for emergency or remote coverage
• Coordinate UAV Swarms: Apply swarm algorithms for distributed sensing and cooperative mission execution
• Integrate Ground and Air Networks: Design hybrid systems connecting UAV networks with ground IoT infrastructure

33.6 Prerequisites

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

• Networking Basics: Fundamental networking concepts including topology types, routing, and wireless communication
• Wireless Sensor Networks: WSN architectures, energy constraints, and data collection strategies
• Multi-Hop Fundamentals: Multi-hop routing and relay strategies

Key Concepts

• UAV Network Topology: The structural pattern of communication links between UAVs — star (hub-and-spoke, simple control), mesh (peer-to-peer, resilient routing), and hybrid configurations
• Single-UAV Architecture: One UAV acting as aerial access point or relay — simplest deployment (15 min setup) but single point of failure affecting entire coverage area
• Multi-UAV Mesh: Multiple UAVs forming a self-organizing network with automatic failover when one UAV fails or loses power — required for critical infrastructure applications
• Coverage Geometry: The mathematical relationship between UAV altitude and ground coverage area — doubling altitude quadruples coverage (πr² where r ≈ altitude × tan(coverage angle))
• Topology-Failure Tradeoff: Star topologies fail completely when the hub UAV loses power; mesh topologies degrade gracefully but require 3× more UAVs for equivalent coverage with the same resilience
• Altitude Optimization: The tradeoff between coverage (increases with altitude) and link quality (degrades with distance, atmospheric absorption) — an optimal altitude exists for each application
• 3D Spatial Management: UAVs operating at different altitudes to avoid collision while maintaining communication links — altitude bands assigned per UAV role (relay, sensor, coordinator)

33.7 Related Chapters

After completing this series, continue with:

• FANET and Integration - Advanced routing protocols and ground IoT integration
• UAV Production Review - Comprehensive summary and review questions
• Ad-hoc Networks - Mobile ad hoc networking foundations
• Energy Management - Battery and power optimization strategies

For Kids: Meet the Sensor Squad!

UAV networks are like a team of superhero drones that fly through the sky and talk to each other – kind of like a flock of really smart birds!

33.7.1 The Sensor Squad Adventure: The Drone Dream Team

One day, Sammy the Temperature Sensor looked up at the sky and saw something amazing – a group of drones flying in perfect formation, like a team of superheroes!

“What are they doing up there?” asked Lila the Light Sensor.

Max the Motion Detector, who was riding on one of the drones, called down: “We are a FANET – a Flying Ad-hoc Network! Think of us like a flying Wi-Fi network. Each drone can see and sense things from way up high, and we pass messages to each other like a flying bucket brigade!”

Bella the Button Sensor was curious: “But how do you decide who flies where?”

Max explained: “It depends on the mission! Sometimes we fly in a STAR pattern – one boss drone in the middle tells everyone where to go. Other times we fly in a MESH – everyone talks to everyone, so if one drone has to land for a recharge, the others keep going. And for really BIG missions, we use a HIERARCHY – ground control talks to leader drones, who talk to worker drones!”

33.7.2 Key Words for Kids

Word	What It Means
UAV	Unmanned Aerial Vehicle – a flying robot (drone!)
FANET	Flying Ad-hoc Network – a team of drones that talk to each other while flying
Star Topology	One boss drone in the center, all others report to it
Mesh Topology	Every drone talks to every nearby drone – no single boss
Swarm	A group of drones working together, like bees in a hive

For Beginners: UAV Networks Overview

What are UAV networks? UAV (Unmanned Aerial Vehicle) networks are groups of drones that communicate with each other and with ground systems to accomplish tasks like search and rescue, crop monitoring, or disaster response.

Why drones instead of fixed sensors?

Factor	Ground Sensors	Drone Networks
Deployment speed	Days to months	Minutes
Coverage flexibility	Fixed location	Adjustable in real-time
Disaster response	May be destroyed	Deployed immediately
Cost for large areas	Expensive infrastructure	Fewer units needed

Putting Numbers to It

Consider a precision agriculture deployment where 5 UAVs survey a 500-hectare farm. Each UAV operates at 100m altitude with a camera covering a 120° field of view. The coverage radius \(r\) at altitude \(h\) is:

\[r = h \cdot \tan\left(\frac{\theta}{2}\right) = 100 \cdot \tan(60°) = 173 \text{ m}\]

Coverage area per UAV: \(A = \pi r^2 = \pi \cdot 173^2 \approx 94,000 \text{ m}^2 = 9.4 \text{ hectares}\)

For 500 hectares with 20% overlap for stitching: \(\text{Required passes} = \frac{500}{9.4 \times 0.8} \approx 67 \text{ passes}\)

At 12 m/s flight speed with 2 km pass length: \(\text{Time per pass} = \frac{2000}{12} = 167 \text{ seconds}\)

Total mission time with 5 UAVs: \(\frac{67 \times 167}{5 \times 60} \approx 37 \text{ minutes}\)

This fits within a typical 40-minute battery window, demonstrating how altitude and coverage geometry drive mission feasibility.

This chapter series covers:

1. UAV basics and roles (sensor, base station, relay)
2. Network features and challenges (3D mobility, battery life)
3. Topology choices (star vs mesh)
4. Swarm coordination algorithms
5. Hands-on simulation lab

Start with the first chapter and work through in order for the best learning experience.

33.8 Knowledge Check

Test Your Understanding

Question 1: A disaster response team needs to deploy a communication network within 30 minutes after an earthquake. Ground cell towers are destroyed. Which approach is most appropriate?

1. Rebuild ground cell towers using emergency crews
2. Deploy a FANET (Flying Ad-hoc Network) of drones as temporary aerial base stations
3. Use satellite phones exclusively for all communication
4. Wait for infrastructure repair before establishing communication

Answer

b) Deploy a FANET of drones as temporary aerial base stations. FANETs can be deployed in minutes, providing immediate network coverage. Ground tower rebuilding takes weeks, satellite phones have limited capacity, and waiting is unacceptable in emergencies where lives are at stake.

Question 2: Which UAV network topology is best for a simple agricultural monitoring mission with one ground control station and 3 drones flying predetermined paths?

1. Mesh topology with distributed control
2. Star topology with centralized control from the ground station
3. Hierarchical topology with multiple control layers
4. Ring topology with sequential data passing

Answer

b) Star topology with centralized control. For simple missions with few drones and a single control point, star topology is optimal because it minimizes coordination complexity. Each drone communicates directly with the ground station. Mesh adds unnecessary overhead for 3 drones, and hierarchical is designed for large-scale operations.

Question 3: What is the primary challenge that distinguishes FANET (Flying Ad-hoc Network) routing from MANET (Mobile Ad-hoc Network) routing?

1. FANETs use different radio frequencies
2. FANETs have 3D mobility with much faster topology changes
3. FANETs cannot use encryption
4. FANETs require wired connections between drones

Answer

b) FANETs have 3D mobility with much faster topology changes. Unlike ground-based MANETs where nodes move in 2D at walking or vehicle speeds, FANET nodes move in three dimensions at speeds of 30-100+ km/h. This causes topology links to form and break much more rapidly, requiring specialized routing protocols that can adapt in seconds rather than minutes.

Worked Example: FANET Topology Selection for Search and Rescue

Scenario: Mountain search and rescue needs 10 drones to cover 50 km² area. Ground control station 5 km from search area.

Option 1 - Star Topology (all drones → ground station): - Advantage: Simple coordination, single command point - Problem: Max range 300m (802.11n) → Drones must stay within 300m of ground station → Cannot cover 50 km² - Verdict: Infeasible for range requirement

Option 2 - Mesh Topology (drones relay for each other): - Coverage calculation: Each drone covers circle with 300m radius ≈ 0.28 km² - To cover 50 km²: Need 50 / 0.28 = 179 drones (too expensive) - Multi-hop solution: Drones form relay chain from search area back to ground station - 5 km distance ÷ 300m hop = 17 hops minimum - Advantage: Full area coverage, self-healing if drone fails - Latency: 17 hops × 50ms/hop = 850ms end-to-end - Verdict: Feasible with acceptable latency

Option 3 - Hierarchical (3 leader drones + 7 worker drones): - Leaders fly high (500m altitude, extended range to 1 km due to line-of-sight) - Workers fly low (50m) in clusters under leaders - Leaders relay to ground station: 5 km ÷ 1 km = 5 hops - Workers report to nearest leader: 1 hop - Advantage: Lower latency (6 hops max vs. 17), battery savings (leaders have extended batteries) - Latency: 6 hops × 50ms = 300ms - Cost: 3 leader drones × $5K = $15K, 7 worker drones × $2K = $14K, Total $29K - Verdict: Optimal for this mission

Decision: Hierarchical topology chosen for range coverage + acceptable latency + cost efficiency.

Decision Framework: UAV Network Topology Selection

Mission Characteristic	Star Topology	Mesh Topology	Hierarchical Topology
Coverage area	<1 km² (single hop)	Any (multi-hop)	>5 km² (leader relay)
Drone count	<10 drones	10-50 drones	>30 drones
Latency requirement	<50ms (single hop)	<1s (tolerate multi-hop)	<500ms (balanced)
Resilience priority	Low (single point failure OK)	High (critical mission)	Medium (leader redundancy)
Coordination complexity	Low (centralized)	High (distributed)	Medium (leader-based)
Budget	Low ($2K/drone)	Medium ($3K/drone for mesh radio)	High ($5K leaders, $2K workers)

Selection Rule:

• Star: Simple missions near base, <1 km coverage, <10 drones
• Mesh: Resilience critical, distributed search, 10-50 drones
• Hierarchical: Large area (>5 km²), >30 drones, mixed altitude operations

Example - Agricultural Monitoring (200 hectare farm, 12 drones, base station at center): Mesh (covers area, 12 drones within mesh range, resilience preferred)

Example - Package Delivery (single drone, returns to depot): Star (direct communication to depot sufficient)

Example - Disaster Response (50 drones, 100 km² area, temporary base): Hierarchical (scale required, leader drones with satellite backhaul)

Common Mistake: Underestimating FANET Topology Change Rate

The Mistake: Designing FANET routing protocols with same assumptions as ground MANET (vehicle speed, 2D topology), without accounting for 3D mobility and wind effects.

Reality Check:

• Ground vehicles: 30-60 km/h, 2D movement, roads constrain paths
• UAVs: 50-100 km/h cruise speed, 3D movement, wind gusts change position ±10m

Topology Change Calculation:

• Two drones flying toward each other at 60 km/h = 120 km/h relative speed = 33 m/s
• Communication range: 300m (802.11n)
• Link duration: 300m ÷ 33 m/s = 9 seconds
• Routing protocol must discover, use, and update routes in <9s or links break mid-transmission

Putting Numbers to It

Consider a FANET link budget for air-to-ground communication. A UAV at 300m altitude transmits at 20 dBm (100 mW) using 2.4 GHz with 3 dBi antennas on both ends. The free-space path loss is:

\[L_{fs} = 20\log_{10}(d) + 20\log_{10}(f) + 20\log_{10}\left(\frac{4\pi}{c}\right)\]

where \(d = 300\) m, \(f = 2.4 \times 10^9\) Hz, \(c = 3 \times 10^8\) m/s:

\[L_{fs} = 20\log_{10}(300) + 20\log_{10}(2.4 \times 10^9) - 147.6 \approx 49.5 + 187.6 - 147.6 = 89.5 \text{ dB}\]

Link budget: \(P_{rx} = P_{tx} + G_{tx} + G_{rx} - L_{fs} = 20 + 3 + 3 - 89.5 = -63.5 \text{ dBm}\)

For 802.11n at 6 Mbps, sensitivity is -82 dBm, providing: \(\text{Margin} = -63.5 - (-82) = 18.5 \text{ dB}\)

This 18.5 dB margin accommodates fading, multipath, and interference. At 600m altitude, path loss increases to 95.5 dB, reducing margin to 12.5 dB—still viable but with reduced reliability.

Measured Impact (from Princeton FANET testbed):

Routing Protocol	Design For	FANET Link Duration	Route Discovery Time	Packet Delivery
AODV (MANET)	Ground vehicles, 30s links	9s avg	1.2s	62%
OLSR (MANET)	Stable topology	9s avg	N/A (proactive)	71%
GPSR (Geographic)	Position-based	N/A	0s (greedy forward)	89%
Custom FANET	High mobility	9s avg	0.3s	93%

Why MANET protocols fail in FANET:

• AODV route discovery (1.2s) + data transmission (2s) = 3.2s, but link exists only 9s → Succeeds 65% of time
• Wind gusts cause ±10m position changes → Cached routes stale after 3-5s
• 3D topology breaks assumptions (e.g., AODV assumes link symmetry, but altitude differences create asymmetric links)

Correct FANET-Specific Approach:

1. Use GPS-based routing (GPSR): Forward packets toward destination coordinates, no route discovery
2. Mobility prediction: Estimate future drone positions using velocity vectors, pre-emptively reroute
3. Link quality weighting: Prefer drones flying parallel (longer link duration) over converging drones
4. Aggressive link monitoring: Detect broken links in <500ms (not 3s MANET default)

Result with FANET-Aware Protocol:

• Packet delivery: 62% (AODV) → 93% (GPSR + mobility prediction)
• End-to-end latency: 850ms → 340ms (fewer retransmissions)
• Routing overhead: 18% → 4% (no flooding for route discovery)

Lesson: Never assume ground-based MANET protocols will work in 3D high-mobility FANETs. Topology changes 5-10× faster, requiring specialized routing.

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

Common Pitfalls

1. Using Star Topology for Mission-Critical Applications

Star topology means all communication routes through the central hub UAV. If that UAV’s battery dies at 20 minutes into a 30-minute mission, the entire network fails. Use mesh topology for any application where connectivity loss causes mission failure — disaster response, search and rescue, critical monitoring.

2. Calculating Coverage as 2D Ground Area Only

Students calculate UAV coverage as a flat circle on the ground. Real UAV networks must also consider: building heights blocking LOS, terrain elevation variations, and the minimum elevation angle for link quality. Always use 3D terrain models for urban deployments — a UAV at 150m altitude cannot see behind a 200m skyscraper.

3. Ignoring Handoff in Mobile UAV Deployments

When a UAV moves (following a target, dynamic coverage adjustment), ground devices lose their current connection before establishing a new one — handoff. Without pre-emptive handoff protocols, devices experience 2–10 second connectivity gaps. Design handoff sequences before deploying moving UAV networks.

4. Deploying Without Collision Avoidance Planning

Multi-UAV deployments without altitude band assignments (e.g., UAV1: 100m, UAV2: 150m, UAV3: 200m) risk near-miss incidents when UAVs converge on the same coordinate. Assign fixed altitude bands by UAV role and enforce them with GPS geofencing — never assume pilots can maintain separation manually during incidents.

Label the Diagram

💻 Code Challenge

33.9 Summary

This chapter series provides a comprehensive introduction to UAV networks for IoT applications:

• UAV Roles: Drones serve as mobile sensor platforms, aerial base stations, and data relays – providing capabilities that ground networks cannot match
• FANET Concept: Flying Ad Hoc Networks enable self-organizing drone communication without fixed infrastructure, critical for disaster response and remote operations
• Topology Selection: Star topology suits simple centralized missions; mesh topology provides resilience for multi-drone swarms; hierarchical topology scales for large operations
• Key Challenges: 3D mobility creates rapidly changing topologies, battery life limits flight time to 20-40 minutes, and coordination complexity grows with swarm size
• Applications: Disaster response, precision agriculture, search and rescue, infrastructure inspection, and temporary event coverage

33.10 Start Learning

Begin with UAV Introduction and Fundamentals

33.11 Knowledge Check

Quiz: UAV Network Topologies

33.12 What’s Next

If you want to…	Read this
Explore FANETs and UAV integration	UAV: FANETs and Integration
Study FANET fundamentals	FANET Fundamentals
Understand UAV network features and challenges	UAV Network Features and Challenges
Review all UAV network concepts	UAV Networks: Production and Review
Get hands-on with the interactive UAV lab	UAV/FANET Interactive Lab