46  UAV Networks: Production and Review

In 60 Seconds

UAV swarm coordination uses Reynolds flocking rules (cohesion, separation, alignment) across 4 formation types, with typical link lifetimes of only 30-67 seconds at 10-50 m/s speeds. A UAV at 300m altitude covers 78.5 km2 compared to 3.14 km2 for a ground station, but path loss increases 6 dB per altitude doubling – making altitude-coverage tradeoff the central design tension for production FANET deployments.

46.1 Learning Objectives

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

• Implement Path Planning: Design 3D trajectories with collision avoidance for UAV swarms
• Coordinate Swarms: Build formation control and distributed coordination algorithms
• Optimize Coverage: Apply algorithms for efficient area monitoring with multiple UAVs
• Design Energy-Aware Systems: Create mission planning that maximizes flight time
• Model Communication Links: Simulate air-to-air and air-to-ground link characteristics
• Implement FANET Protocols: Apply Flying Ad Hoc Network protocols for dynamic topologies

Minimum Viable Understanding

• UAV network topologies: FANET mesh networks support 10-50 m/s 3D mobility with position-based greedy forwarding routing and typical link lifetimes of 30-67 seconds
• Altitude-coverage tradeoff: A UAV at 300m altitude covers approximately 78.5 km2 (5 km radius LOS) compared to 3.14 km2 for a 10m ground station, but path loss increases by 6 dB per altitude doubling
• Swarm coordination patterns: Reynolds flocking (cohesion, separation, alignment) with 4 formation types (line, V-shape, grid, circle) enables distributed multi-UAV missions with collision avoidance using Closest Point of Approach prediction

Sensor Squad: Flying Robot Teams

Sammy the Sound Sensor is amazed: “Imagine a team of flying robots – like drones you see in parks – working together to help people! After an earthquake, these drones fly up high and become flying phone towers so rescue workers can make calls.”

Lila the Light Sensor adds: “I love how they see things from above! A drone flying at 300 meters high can see an area 25 times bigger than a tower on the ground. It is like standing on a really tall ladder versus standing on the floor – you can see so much more!”

Max the Motion Sensor explains the teamwork: “The drones fly in formations – like a V-shape, just like geese! They talk to each other to avoid crashing, and if one drone runs low on battery, another one takes its place. It is like a relay race in the sky!”

Bella the Bio Sensor shares a nature example: “On farms, drones fly over fields checking if plants are healthy or need water. Instead of a farmer walking across a huge field for hours, a drone can check the whole farm in 30 minutes! The plants have tiny sensors in the soil, and the drone collects their data as it flies overhead – like a mail carrier picking up letters.”

For Beginners: UAV Networks in Simple Terms

A UAV network is a group of drones that communicate with each other and with the ground while flying. Think of it like a team of delivery drones that need to coordinate who goes where, avoid bumping into each other, and report back to a control center.

Three main types of UAV networks:

• FANET (Flying Ad Hoc Network): Drones talk directly to each other in the air, forming a mesh network. Used when drones need to coordinate without a central controller, like in search-and-rescue.
• UAV-WSN: A drone flies over ground sensors and collects their data, acting like a mobile mailbox. Great for farms or forests where sensors are spread out.
• UAV-BS (Flying Base Station): A drone hovers high up and acts like a cell tower, providing phone or internet service to people below. Used in emergencies when real towers are destroyed.

Why UAVs are special for IoT: They can be deployed in minutes (no infrastructure needed), reach dangerous or remote areas, cover huge areas from altitude, and be repositioned on the fly. The main limitations are battery life (20-90 minutes of flight) and regulations on where they can fly.

46.2 Prerequisites

Required Chapters:

• UAV Fundamentals - UAV concepts
• UAV FANET - Flying ad-hoc networks
• Ad-hoc Fundamentals - MANET basics

Technical Background:

• UAV flight dynamics basics
• 3D networking concepts
• Mobility models

UAV Network Types:

Type	Nodes	Communication	Use Case
FANET	UAVs only	Air-to-air	Swarms
UAV-WSN	UAVs + sensors	Air-to-ground	Data collection
UAV-BS	UAVs + base	Air-to-infrastructure	Relay

Estimated Time: 1 hour

Key Concepts

• Production UAV Network: A deployed multi-UAV system with battery rotation schedules, redundant communication paths, automated failover, and operational procedures for continuous mission coverage
• Coverage Continuity: The operational requirement that ground IoT devices maintain connectivity throughout a UAV battery swap cycle — requires overlapping coverage from adjacent UAVs during handoff
• UAV Deployment Time: The advantage of aerial base stations in emergency response — UAVs deploy in 15 minutes vs. 6+ hours for ground infrastructure — enabling first responder connectivity during disaster scenarios
• 25× Coverage Advantage: Line-of-sight from 300m altitude provides 78.5 km² coverage vs. 3.14 km² for ground nodes at 10m — the primary operational justification for UAV relay networks
• FANET Routing Production Requirement: Production FANET routing must handle routes with 40–67 second lifetime (vs. 50–250 seconds in ground MANET) — only position-based or predictive routing meets this requirement
• Battery Rotation Strategy: Maintaining a rotation pool (one flying, one charging, one spare) to provide continuous coverage beyond single-battery flight time — fundamental to any mission >45 minutes
• Trade-off: Coverage vs. Capacity: UAV aerial base stations provide larger coverage areas but lower processing capacity than ground stations — UAVs are coverage extenders, not capacity enhancers

46.3 Cross-Hub Connections

This chapter connects to multiple learning resources:

Quiz Practice:

• Quizzes Hub - Test UAV network knowledge with scenario-based questions

Visual Learning:

• Simulations Hub - Explore interactive FANET routing and mission planning tools

Hands-On:

• Knowledge Map - See how UAV networks fit within IoT architecture landscape

Video Resources:

• Videos Hub - Watch real-world UAV deployment case studies and FANET demonstrations

Concept Review:

• Knowledge Gaps - Common UAV misconceptions about altitude, coverage, and battery life

For Beginners: How to Use This Review

What is this chapter? This advanced chapter covers production-level UAV network deployments. It’s designed for review after studying fundamentals.

When to use:

• After completing UAV fundamentals and topologies
• When designing real UAV network solutions
• For exam preparation on UAV topics

Key Review Topics:

Topic	Focus Area
Deployment	Real-world UAV network setup
Regulations	Airspace, safety, communications
Performance	Latency, handoff, coverage
Applications	Disaster response, agriculture, inspection

Prerequisites:

• UAV Fundamentals
• Basic networking knowledge
• Understanding of ad-hoc networks

Recommended Path:

1. Complete prerequisites first
2. Study this chapter for production insights
3. Review related quiz content

46.4 UAV Network Architecture for IoT

⏱️ ~15 min | ⭐⭐ Intermediate | 📋 P05.C23.U01

UAV networks integrate multiple layers to enable aerial IoT capabilities, from flight control to application services.

Common Misconception: “Higher Altitude = Better Coverage Always”

The Myth: Flying UAVs at maximum altitude (400m regulatory limit in US) always provides optimal coverage for IoT networks.

The Reality: Altitude optimization requires balancing multiple competing factors with quantified tradeoffs.

Real-World Data:

Altitude	Coverage Radius	Path Loss (2.4 GHz)	Power Consumption	Optimal Use Case
100m	3.5 km	92 dB	200W hover	Dense urban (buildings block LOS)
200m	5.0 km	98 dB	220W hover	Agricultural monitoring (optimal balance)
300m	6.1 km	102 dB	250W hover	Disaster response (maximum coverage)
400m	7.1 km	105 dB	280W hover	Regulatory max (rarely optimal)

Why It’s Wrong:

1. Free-Space Path Loss Increases: Doubling altitude from 100m to 200m adds 6 dB path loss (4× signal attenuation). IoT sensors need higher transmit power or lower data rates.

2. Wind Speed Increases: Wind speed typically increases 20-40% from 100m to 300m altitude. UAV must fight stronger winds → 15-25% higher battery consumption → shorter mission time.

3. Interference Changes: Lower altitudes may have ground clutter but less co-channel interference from distant base stations. 300m+ altitude can receive interference from 10+ km away.

4. Regulatory Constraints: US Part 107 limits recreational drones to 400 feet (122m). Commercial operations above 400m require special authorization.

Real Deployment Example: Agricultural IoT monitoring system (2021 California study): - 400m altitude: 158 km² theoretical coverage, but soil moisture sensors at 10 mW transmit power couldn’t reach UAV (108 dB path loss exceeds link budget by 12 dB). - 200m altitude: 79 km² coverage, 98 dB path loss within link budget, 100% sensor connectivity. 32-minute flight time vs 22 minutes at 400m (+45% endurance). - Result: 200m altitude provided better effective coverage despite smaller geometric footprint.

Best Practice: Calculate optimal altitude using link budget analysis (sensor TX power + antenna gain - path loss - fading margin ≥ receiver sensitivity). Typical IoT optimal range: 150-250m for sub-GHz, 100-200m for 2.4 GHz.

UAV network architecture for IoT

Figure 46.1

UAV Network Architecture for IoT (Five-Layer System)

Layer	Components	Function	Connections
Application	Disaster Response, Precision Agriculture, Infrastructure Inspection, Search & Rescue	Mission-specific applications	Sends requirements to Network layer
Network Management	FANET Routing (Position-Based), Swarm Coordination, Gateway Selection, QoS Management	Network topology and coordination	Routes traffic via Communication layer
Mission Planning	Path Planning (3D A*), Task Allocation, Energy Management, Collision Avoidance	Autonomous mission execution	Controls Physical layer systems
Communication	Air-to-Air (UAV-UAV), Air-to-Ground (UAV-Sensor), Air-to-Infrastructure (UAV-Base)	Multi-mode wireless links	Bridges Physical and Ground layers
Physical	UAV Hardware (Sensors/Radio), Flight Control (Autopilot), Battery System, Positioning (GPS/IMU)	Aerial platform operation	Interfaces with Ground infrastructure
Ground Infrastructure	Ground Control Station, IoT Sensor Network, Base Stations, Cloud Backend	Terrestrial support systems	Receives data, sends control commands

Key Data Flows:

Source	Destination	Data Type
Ground Control Station	Flight Control	Control commands, telemetry
UAV Physical Layer	Cloud Backend	Data upload (sensor readings, video)
Air-to-Ground Links	IoT Sensor Network	Sensor data collection
Air-to-Infrastructure	Base Stations	Network relay, backhaul

46.5 Production Framework: UAV Network Management

⏱️ ~12 min | ⭐⭐⭐ Advanced | 📋 P05.C23.U02

This section provides a comprehensive, production-ready Python framework for UAV network management, implementing path planning, swarm coordination, energy-aware routing, and coverage optimization.

For Beginners: Reading the UAV Production Framework

This chapter sits at the end of the UAV/FANET sequence and shows what a full multi‑UAV management system looks like in code.

It should come after:

• uav-fundamentals-and-topologies.qmd – basic UAV roles, topologies, and constraints.
• uav-trajectory-labs-and-implementation.qmd – trajectory planning and lab‑style experiments.
• uav-fanet-and-integration.qmd – FANET characteristics and integration with ground networks.

If you are still getting comfortable with UAV networking:

• Skim the example outputs (mission planning tables, collision warnings, swarm formations) and relate them back to the earlier conceptual chapters.
• Treat the detailed Python as an example of how to glue all those ideas together, not something you must fully understand on first read.

46.6 UAV Communication Systems Comparison

⏱️ ~8 min | ⭐⭐ Intermediate | 📋 P05.C23.U03

Different UAV network architectures serve distinct IoT use cases based on communication patterns and network topology.

UAV communication systems comparison

Figure 46.2

UAV Communication Systems Comparison

Architecture	Topology	Communication	Speed	Primary Use Case
FANET (Flying Ad Hoc Network)	Mesh (UAV-to-UAV)	Air-to-Air only	10-50 m/s	Search & rescue, swarm coordination
UAV-WSN (Data Collection)	Star (Mobile sink)	Air-to-Ground	Variable	Environmental monitoring, data mule
UAV-BS (Flying Base Station)	Star + Backhaul	Air-to-Infrastructure	Hovering	Disaster response, coverage extension

FANET Characteristics:

• Nodes: Multiple UAVs in mesh topology
• Links: Bidirectional air-to-air
• Routing: Position-based (greedy forwarding)
• Mobility: 3D, high speed, dynamic topology
• Challenge: Frequent link changes

UAV-WSN Characteristics:

• Nodes: Mobile UAV + stationary ground sensors
• Links: Single-hop air-to-ground
• Pattern: Mobile sink visits sensors sequentially
• Benefit: Energy balancing (no multi-hop)
• Tolerance: Delay-tolerant (minutes to hours)

UAV-BS Characteristics:

• Nodes: UAV base station + IoT devices + ground gateway
• Links: Air-to-ground (devices), air-to-infrastructure (backhaul)
• Coverage: 3-10 km radius from altitude
• Advantage: Line-of-sight, rapid deployment
• Use: Emergency communications when infrastructure fails

Performance Comparison:

Metric	FANET	UAV-WSN	UAV-BS
Coverage	Wide (swarm area)	Area scan pattern	3-10 km radius
Latency	Variable	Minutes-Hours	Low (milliseconds)
Energy	High (mobility)	Low (sensors)	Medium
Complexity	High (coordination)	Medium	Low

This production framework provides comprehensive UAV network management capabilities including:

• Path Planning: 3D A* algorithm with collision avoidance and obstacle detection
• Swarm Coordination: Formation control with 4 types (Line, V-Shape, Grid, Circle)
• Energy-Aware Routing: Greedy and energy-aware routing strategies for FANETs
• Coverage Optimization: Grid-based positioning for maximum area coverage
• Communication Modeling: Free-space path loss model with link quality metrics

The framework demonstrates production-ready patterns for UAV networks with realistic physics, energy constraints, and communication characteristics.

---

46.7 Advanced Production Framework: Complete UAV Network System

This comprehensive advanced framework extends the base UAV framework with multi-UAV mission planning, swarm intelligence, collision avoidance, task allocation, and complete system integration for real-world autonomous aerial operations.

46.7.1 Framework Overview

The advanced framework implements: - Multi-UAV mission planning (task allocation, cooperative path planning) - Swarm intelligence algorithms (flocking, consensus, distributed coordination) - Advanced collision avoidance (velocity obstacles, predictive algorithms) - Dynamic network topology (FANET routing, gateway selection, handoff) - Ground station integration (command/control, telemetry, mission updates) - Battery management (charging station planning, emergency landing)

46.7.2 Complete Implementation

46.7.3 Key Features

1. Multi-UAV Mission Planning (Example 1):
   • Auction-based task allocation
   • Priority-based scheduling (1-10 scale)
   • Deadline-aware planning
   • 5 UAVs, 4 tasks with 100% allocation rate
2. Swarm Coordination (Example 2):
   • Reynolds’ flocking algorithm (cohesion, separation, alignment)
   • 4 formation types (line, V-shape, grid, circle)
   • Formation maintenance with real-time adjustment
   • 10-UAV swarm with 25m spacing
3. Collision Avoidance (Example 3):
   • Closest Point of Approach (CPA) prediction
   • 10-second prediction horizon
   • Velocity obstacle avoidance
   • Severity-based maneuver computation (0.0-1.0)
4. FANET Routing (Example 4):
   • Dynamic topology management
   • Dijkstra’s routing algorithm
   • Gateway selection
   • 8-node network with 300m comm range
5. Ground Station Integration (Example 5):
   • Telemetry buffering (100 entries)
   • Command queuing
   • Connectivity monitoring
   • Emergency recall capability
6. Integrated System (Example 6):
   • All components working together
   • 6-UAV fleet with complete lifecycle
   • Mission planning + swarm + collision + routing + battery + ground station
   • Real-time statistics and monitoring

46.7.4 Example Output

=== Example 1: Multi-UAV Mission Planning ===

1. Created 5 UAVs and 4 tasks

2. Allocating Tasks Using Auction Mechanism...

3. Task Allocations:
   task_4: UAV_0 (priority=10, type=search_rescue)
   task_3: UAV_1 (priority=9, type=surveillance)
   task_1: UAV_2 (priority=8, type=point_inspection)
   task_2: UAV_3 (priority=6, type=area_coverage)

4. Mission Statistics:
   Total tasks: 4
   Assigned: 4
   Pending: 0
   Active UAVs: 4

=== Example 3: Collision Avoidance ===

1. Initial Setup:
   UAV_A: pos=(0, 0), vel=(5.0, 5.0)
   UAV_B: pos=(100, 100), vel=(-5.0, -5.0)

2. Predicting Collisions...
   ⚠ Detected 1 potential collision(s)
   - UAV_A vs UAV_B
     Time to collision: 7.07s
     Collision point: (35.4, 35.4)
     Severity: 0.85

3. Computing Avoidance Maneuvers...
   UAV_A avoidance: (-4.24, -4.24, 4.25)

---

Alternative View: UAV Mission Phase State Machine

This variant shows UAV operations as a state machine, emphasizing the transitions between mission phases and the communication requirements at each stage.

Figure 46.3: Alternative view: UAV operations progress through distinct phases with different communication requirements. Pre-flight needs reliable ground station links. Launch requires high-rate telemetry. Cruise uses efficient FANET mesh. Task execution demands maximum bandwidth. Understanding these phases helps design adaptive communication protocols.

Alternative View: FANET vs Traditional MANET Comparison

This variant contrasts FANET characteristics with ground-based MANETs, highlighting the unique challenges of aerial networking.

Figure 46.4: Alternative view: FANETs differ fundamentally from ground MANETs. High speed (10-50x faster) and 3D mobility invalidate traditional reactive routing protocols. However, line-of-sight propagation and predictable trajectories enable position-based and predictive routing approaches not feasible for ground networks.

46.8 Visual Reference Gallery

Explore these AI-generated visualizations that complement the UAV network concepts covered in this chapter. Each figure uses the IEEE color palette (Navy #2C3E50, Teal #16A085, Orange #E67E22) for consistency with technical diagrams.

Visual: FANET Architecture

Flying Ad Hoc Network architecture

This visualization illustrates the FANET architecture covered in this chapter, showing how UAVs form dynamic mesh networks with air-to-air and air-to-ground communication links.

Visual: FANET Topology Dynamics

Dynamic FANET topology changes

This figure depicts the rapid topology changes discussed in the FANET characteristics section, illustrating how 3D mobility and high speed create unique networking challenges.

Visual: Drone Swarm Coordination

Multi-UAV swarm coordination

This visualization shows the swarm coordination concepts covered in the production framework, illustrating how multiple UAVs collaborate for coverage optimization and mission planning.

Visual: UAV Network Considerations

Considerations in UAV network design

This figure illustrates the key considerations for UAV network deployment discussed in the production and review sections, covering energy, range, and regulatory factors.

Visual: FANET vs VANET Integration

FANET-VANET network integration

This visualization depicts the FANET-VANET integration concepts covered in the production framework, showing how UAVs extend vehicular network coverage and enable emergency response.

Common Pitfalls and Misconceptions

1. Assuming mesh topology is always best for UAV networks: Mesh adds significant routing overhead (15+ control packets/node/minute in FANETs). For small swarms of fewer than 10 UAVs with reliable cellular backhaul, a simple star topology with ground control station coordination is simpler, lower latency, and sufficient. Choose topology based on swarm size, resilience requirements, and available infrastructure – not default to mesh.

2. Ignoring wind and weather impact on mission planning: Wind speed increases 20-40% between 100m and 300m altitude, adding 15-25% battery consumption. A mission planned for 30 minutes at ground level may only achieve 22 minutes at 300m altitude. Always include a wind margin of at least 20% in energy budgets, and plan return-to-base triggers at 30% remaining battery, not 10%.

3. Using ground MANET routing protocols (AODV, OLSR) for FANETs without adaptation: At 20 m/s UAV speed, AODV route discovery takes 8 seconds, during which each UAV moves 160m – making the discovered route immediately obsolete. FANET route lifetimes are 30-67 seconds versus 50-250 seconds for ground MANETs. Use position-based routing (GPSR) or predictive routing that leverages GPS coordinates and flight plans instead.

4. Treating UAV coverage as purely geometric (ignoring link budget): A UAV at 400m altitude has a theoretical 7.1 km coverage radius, but 10 mW IoT soil sensors cannot close the link at 105 dB path loss. The same sensors achieve 100% connectivity at 200m altitude where path loss is 98 dB. Always calculate coverage from the weakest device upward: sensor TX power plus antenna gain minus path loss minus fading margin must exceed receiver sensitivity.

5. Overlooking regulatory altitude and flight restrictions: US Part 107 limits recreational drones to 400 feet (122m), not 400 meters. Commercial operations above this limit require FAA waivers that take weeks to obtain. International regulations vary significantly – the EU caps at 120m, and many countries require visual line-of-sight operation, which limits range to approximately 500m regardless of radio capability. Design systems within regulatory constraints from the start.

Worked Example: FANET Emergency Response Deployment

Scenario: A wildfire threatens a mountain community. Normal cellular infrastructure has been destroyed. You must deploy a 5-UAV FANET to provide emergency communications while firefighters establish safe evacuation routes.

Given Data:

• Coverage area needed: 4 km radius (50 km² circular zone)
• UAV altitude: 300m for line-of-sight
• Individual UAV coverage at 300m: π × (5 km)² = 78.5 km² theoretical
• Required mesh connectivity: minimum 3 neighbors per UAV
• Battery life per UAV: 45 minutes continuous hover
• Formation options: grid, circle, or adaptive

Step-by-Step Solution:

1. Calculate required UAVs for coverage: Total area 50 km² ÷ 78.5 km² per UAV = 0.64 UAVs (1 UAV sufficient for coverage, but…)

2. Apply mesh connectivity constraint: For 3-neighbor minimum in mesh, need minimum 4-5 UAVs (graph theory: degree-3 requires 4+ nodes)

3. Position UAVs in circular formation: Place 5 UAVs equally spaced around 3 km radius circle (120m altitude separation for 3D mesh)

   • Spacing: 2π × 3000m ÷ 5 = 3.77 km between UAVs
   • At 2 km air-to-air range, each UAV reaches 2 neighbors (total 10 bidirectional links)

4. Calculate mission endurance: 45 min battery ÷ 2 = 22.5 min usable (50% reserve for return-to-base)

   • Deploy rotation: 3 UAVs active, 2 charging → continuous 24-hour coverage

5. Verify altitude-coverage tradeoff: At 300m altitude, free-space path loss = 20 log₁₀(300) + 20 log₁₀(915 MHz) ≈ 89 dB

   • Link budget: TX 20 dBm - 89 dB path loss + 2 dBi antenna = -67 dBm received
   • Above -100 dBm sensitivity → link margin 33 dB (excellent)

Result: 5-UAV circular formation at 300m altitude with 22.5 min rotation provides 50 km² emergency coverage with 3-neighbor mesh redundancy and 33 dB link margin.

Key Insight: The altitude-coverage tradeoff is NOT about maximizing altitude. At 400m (regulatory max), path loss increases 6 dB, requiring higher TX power that reduces battery life 15%, cutting rotation time to 19 minutes. The 300m altitude balances coverage, path loss, and endurance.

Decision Framework: Choosing UAV Network Topology

Factor	Star (Central GCS)	Hierarchical (Cluster Heads)	Full Mesh (Peer-to-Peer)
Swarm Size	1-10 UAVs	10-50 UAVs	5-20 UAVs
Control Latency	Low (1 hop to GCS)	Medium (2 hops)	Variable (multi-hop)
Resilience	Low (GCS failure = total loss)	Medium (cluster head failure)	High (no single point)
Comm Overhead	2N messages/sec (N UAVs × 2)	N + 2K (K cluster heads)	N(N-1)/2 links
Deployment Speed	Fast (GCS first)	Medium (elect heads)	Slow (establish mesh)
Coverage Range	Limited by GCS range	Extended (relay via heads)	Extended (multi-hop)
Best Use Case	Agricultural survey (small area, reliable GCS)	Large-area search (50+ UAVs, organized teams)	Disaster response (no infrastructure, resilience critical)
Energy Efficiency	High (direct to GCS)	Medium (2 hops average)	Low (multi-hop relay)

Decision Rules:

1. If swarm < 10 UAVs AND GCS reliable → Star
2. If swarm > 20 UAVs AND organized mission → Hierarchical
3. If infrastructure destroyed OR high mobility → Full Mesh
4. If energy critical AND GCS available → Star
5. Default for unknown conditions → Hierarchical (balanced tradeoffs)

Common Mistake: Ignoring Formation Impact on Battery Life

The Mistake: A team plans a 20-UAV agricultural survey using grid formation with 100m spacing. They calculate 30-minute battery life based on hover power consumption, expecting to complete a 10 km² survey in one flight.

Why It Fails: Grid formation requires constant position correction: - GPS drift: ±2.5m horizontal position error accumulates to 5-10m over 10 minutes - Each correction: 0.5-1 second flight maneuver at 150W (vs 80W hover) - Frequency: Every 30 seconds to maintain ±5m grid tolerance - Added consumption: 20 corrections/min × 1s × 70W excess = 1,400W-sec/min = 23W average overhead - Actual endurance: 30 min × (80W / 103W) = 23.3 minutes (not 30)

The Fix: Use formation patterns matched to mission dynamics:

Formation	Position Tolerance	Correction Frequency	Battery Overhead	Best For
Tight Grid	±5m	Every 30s	25-30%	Precision mapping
Loose Grid	±20m	Every 2 min	8-12%	Area coverage
Following	±10m behind leader	Leader-reactive	15-18%	Linear inspection
Free Swarm	Zone-based (50m radius)	Every 5 min	5-8%	Search & rescue

Correct Approach: For 10 km² agricultural survey, use loose grid (±20m tolerance). This reduces correction overhead from 25% to 10%, extending endurance from 23.3 to 27.2 minutes — sufficient to complete the survey with 2-minute reserve.

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

Label the Diagram

💻 Code Challenge

46.9 Summary

This chapter explored UAV networks and Flying Ad Hoc Networks (FANETs):

Key Takeaways:

1. UAV Network Topologies: Star (simple, centralized) vs Mesh (resilient, distributed)

2. FANET Characteristics: 3D mobility, very high speed, rapid topology changes distinguish from MANETs/VANETs

3. Position-Based Routing: Greedy forwarding with position prediction handles mobility effectively

4. Gateway Selection: Reduces GCS connections, balances load, considers stability, energy, and centrality

5. FANET-VANET Integration: UAVs extend vehicular network coverage, provide traffic monitoring, enable emergency response

6. Trajectory Control: Dynamic path adjustment optimizes network throughput and coverage

7. Swarm Coordination: Distributed algorithms for search missions with collision avoidance

UAV networks unlock aerial IoT capabilities—rapid deployment, wide coverage, and mobility—transforming applications from disaster response to smart agriculture.

Related Chapters

Deep Dives:

• UAV Fundamentals - Basic UAV network concepts
• UAV Trajectory Labs - Path planning implementation
• UAV FANET Integration - Flying ad-hoc networks

Comparisons:

• MANET vs FANET - Ground vs aerial networks
• WSN Overview - Stationary vs mobile sensing

Applications:

• Disaster Response - Emergency UAV deployment
• Smart Agriculture - Precision farming

Learning:

• Quizzes Hub - UAV network exercises
• Simulations Hub - Mission planning tools

---

46.10 Further Reading

1. Bekmezci, İ., et al. (2013). “Flying ad-hoc networks (FANETs): A survey.” Ad Hoc Networks, 11(3), 1254-1270.

2. Gupta, L., et al. (2016). “Survey of important issues in UAV communication networks.” IEEE Communications Surveys & Tutorials, 18(2), 1123-1152.

3. Mozaffari, M., et al. (2019). “A tutorial on UAVs for wireless networks: Applications, challenges, and open problems.” IEEE Communications Surveys & Tutorials, 21(3), 2334-2360.

---

Chapter Summary

This chapter explored UAV networks as a novel IoT architecture pattern, leveraging aerial mobility for flexible sensing and communication.

UAV Network Capabilities: UAVs offer unique advantages for IoT applications: rapid deployment without infrastructure requirements, aerial perspective enabling wide-area surveillance, three-dimensional mobility reaching locations inaccessible to ground devices, and temporary deployment for events or emergencies. They function as mobile sensors collecting imagery, environmental data, or performing inspections, and as flying base stations providing wireless connectivity to ground IoT devices.

FANET Characteristics: Flying Ad Hoc Networks formed by multiple UAVs differ significantly from ground MANETs. UAVs move much faster with three-dimensional freedom, creating highly dynamic topologies with frequent link changes. Line-of-sight propagation in air reduces interference but rapid mobility challenges routing protocols. Energy constraints are severe - flight time is limited by battery capacity, requiring careful mission planning and energy-aware protocols. Wind and weather affect stability and navigation.

Applications and Challenges: UAVs enable critical applications: disaster response providing emergency communications when infrastructure fails, precision agriculture monitoring crop health over large farms, infrastructure inspection examining bridges and pipelines, search and rescue operations covering large areas quickly, and environmental monitoring tracking wildlife or forest fires. However, challenges include regulatory restrictions on autonomous flight, limited battery life restricting mission duration, vulnerability to weather and malicious attacks, and the complexity of coordinating multiple UAVs safely.

UAV networks represent an emerging IoT architecture pattern particularly valuable for temporary deployments, emergency response, and monitoring vast or dangerous areas.

46.11 Knowledge Check

Test your understanding of UAV network architectures and FANET characteristics.

Quiz 1: UAV Network Topologies

Quiz 2: FANET Characteristics

Real deployment (Hurricane Maria 2017):

• 3 UAVs at 300m altitude provided 150 km² coverage
• Equivalent ground stations would require 15-20 units
• UAVs deployed in 15 minutes; ground stations would take 6+ hours

Trade-offs:

• Battery: UAVs limited to 20-45 min flight time (rotation strategy needed)
• Capacity: UAV has less processing power than ground base station
• Backhaul: UAV needs satellite or LTE backhaul to core network

Key insight: The “25× larger coverage” comes from geometry (LOS from altitude) not from superior radio hardware. Same radio at 300m covers dramatically more area than at 10m.

46.12 Understanding Checks

Apply these concepts to real-world UAV deployment scenarios.

Understanding Check: Disaster Response UAV Coverage

Scenario: Hurricane destroys all cellular infrastructure across 10 km² coastal area. Rescue teams need emergency communications. Options: deploy ground base stations (requires power, backhaul, roads) or launch 3 UAVs at 300m altitude providing temporary LTE coverage.

Think about:

1. Calculate coverage: ground station at 10m height vs UAV at 300m height
2. Why can UAVs launch within 15 minutes while ground stations take 6+ hours?
3. What are battery/endurance tradeoffs (UAV 20-90 min flight vs ground station continuous)?

Key Insight: Ground station (10m height) covers ~1 km radius (3 km² area). UAV (300m altitude) provides line-of-sight to 5+ km radius (79 km² area) - 25× more coverage per node. Three UAVs at 300m cover 150 km² serving 100,000+ emergency calls (real Hurricane Maria 2017 deployment). Rapid deployment: UAVs launch from truck, no infrastructure needed. Ground stations require generator, satellite backhaul, transport through debris. Endurance: UAV 20-90 min → rotating fleet (3 flying, 3 charging). Tethered UAVs provide 24+ hour continuous coverage with power cable. Trade rapid deployment for maintenance complexity.

Understanding Check: FANET Position-Based Routing

Scenario: Search and rescue FANET with UAV-A at origin (0,0,100m) needs to forward data to UAV-B at destination (500,500,200m). Three intermediate options: UAV-C (250,100,150m), UAV-D (100,400,180m), UAV-E (400,300,190m). Traditional routing (AODV) takes 200ms to discover routes in fast-moving topology.

Think about:

1. Calculate 3D Euclidean distance from each neighbor to destination UAV-B
2. Why does position-based routing avoid route discovery overhead?
3. What happens at “greedy failure” local minimums?

Key Insight: Distance to B(500,500,200m): UAV-C = 474m, UAV-D = 413m, UAV-E = 224m. UAV-E is closest → forward to E (geographic progress). Position-based routing: stateless (no route tables), scalable (only neighbor positions needed from beacons), adaptive (automatic topology adaptation). Traditional AODV: flood RREQ, store routes, update on breaks → routes stale instantly in high-mobility FANETs. Greedy failure: No neighbor closer to destination than current node → use perimeter routing or 3D face routing around obstacles. Position-based perfect for FANETs with GPS-equipped UAVs moving 10-50 m/s.

Understanding Check: UAV Aerial Base Station Coverage Advantage

Scenario: Rural agricultural IoT deployment: 1,000 soil sensors across 25 km². Ground base station (30m tower) has 10-20 dB obstruction loss from trees/terrain, covers 1-2 km radius. UAV base station (300m altitude) provides line-of-sight with free-space propagation.

Think about:

1. Calculate path loss difference: ground NLOS vs UAV LOS propagation
2. How does altitude affect coverage radius (coverage area scales with radius²)?
3. What’s optimal UAV altitude balancing coverage vs free-space loss?

Key Insight: Ground station (30m): Non-line-of-sight through trees/hills → 90-100 dB path loss at 1km, 1-2 km radius coverage. UAV (300m): Line-of-sight → 70-80 dB path loss → 15-20 dB advantage = 30-100× better signal strength. Coverage: 5 km radius = 79 km² area. Result: Single UAV replaces 5-7 ground base stations. IoT sensors use lower transmit power (extended battery life) or achieve higher data rates. Optimal altitude: 100-300m balances coverage (higher = larger radius) vs path loss (higher = more attenuation) vs battery (hovering power increases with altitude) vs regulations (airspace restrictions above 400m). Rural monitoring: 200m altitude optimal.

Understanding Check: SD-FANET Centralized Control

Scenario: Search and rescue mission with 15 UAVs. Surveillance UAV captures victim video (high priority, needs 5 Mbps, <100ms latency). Routine telemetry (low priority, 10 Kbps, tolerates 1-second delays). Traditional distributed routing (OLSR) treats all traffic equally, converges slowly after topology changes.

Think about:

1. How does centralized SDN controller optimize routes globally vs local OLSR decisions?
2. Calculate convergence time: distributed OLSR (10-30s) vs SDN (sub-second flow installation)
3. Why does application-aware QoS matter for mission-critical traffic?

Key Insight: SD-FANET architecture: Control plane (ground station) has global view of all UAV positions, link qualities, battery levels, mission objectives. Data plane (UAVs) performs simple forwarding per controller rules. Advantages: (1) Global optimization: finds optimal multi-hop paths considering energy + latency + reliability. OLSR makes suboptimal local decisions. (2) Application-aware QoS: victim video gets dedicated high-bandwidth low-latency path, telemetry uses leftover capacity. (3) Rapid adaptation: link fails → controller recalculates routes in <1 second, pushes new rules to all UAVs. OLSR takes 10-30s to converge. Result: Mission-critical video reaches command center with guaranteed QoS while maximizing network efficiency.

Understanding Check: UAV Mobile Sink for WSN Energy Balance

Scenario: Forest environmental monitoring: 200 sensors spread across 2 km² collecting hourly readings. Stationary gateway at edge: sensors 300m+ away use 3-5 hop multi-hop paths. Nodes within 50m of gateway forward 80% of network traffic → energy hotspot, depleted in 3 months. Mobile UAV flies daily 30-minute collection route, each sensor transmits single-hop when UAV nearby.

Think about:

1. Calculate energy savings: single-hop transmission vs 5-hop multi-hop forwarding
2. Why do intermediate nodes near gateway deplete faster than remote sensors?
3. What’s the tradeoff between data freshness and UAV energy consumption?

Key Insight: Energy hotspot problem: Stationary gateway → sensors near gateway relay packets for entire network → 80% of traffic → depleted in weeks while remote sensors last years → network partition. Mobile UAV solution: Each sensor transmits once (single-hop to UAV when nearby) → eliminates forwarding → balanced energy consumption. All sensors use similar energy → network lifetime = individual sensor lifetime (3+ years vs 3 months). Tradeoffs: Data latency (24-hour collection cycle vs real-time), UAV deployment cost, trajectory optimization (visit frequency vs flight energy). Perfect for delay-tolerant environmental monitoring where sensor longevity matters more than low latency.

---

46.13 Interactive: Altitude-Coverage-Path Loss Tradeoff

Explore how UAV altitude affects both coverage area and signal path loss:

viewof altitude_m = Inputs.range([50, 1000], {value: 300, step: 10, label: "UAV Altitude (m)"})

viewof freq_ghz = Inputs.select([0.9, 2.4, 5.8], {value: 2.4, label: "Frequency (GHz)"})

{
  const losRadius = Math.sqrt(2 * altitude_m * 6371000) / 1000; // km, radio horizon
  const coverageKm2 = Math.PI * losRadius * losRadius;
  const fspl_dB = 20 * Math.log10(altitude_m) + 20 * Math.log10(freq_ghz * 1e9) + 20 * Math.log10(4 * Math.PI / 3e8);
  const ref300 = 20 * Math.log10(300) + 20 * Math.log10(freq_ghz * 1e9) + 20 * Math.log10(4 * Math.PI / 3e8);
  const pathLossIncrease = fspl_dB - ref300;
  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid #2C3E50; margin-top: 0.5rem;">
  <p><strong>LOS Horizon Radius:</strong> ${losRadius.toFixed(1)} km</p>
  <p><strong>Coverage Area:</strong> ${coverageKm2.toFixed(1)} km²</p>
  <p><strong>Path Loss (nadir):</strong> ${fspl_dB.toFixed(1)} dB (${pathLossIncrease >= 0 ? "+" : ""}${pathLossIncrease.toFixed(1)} dB vs 300 m baseline)</p>
  <p style="font-size: 0.85em; color: #666;">Coverage area scales with altitude²; path loss increases 6 dB per altitude doubling. Balance coverage needs against link budget.</p>
  </div>`;
}

46.14 What’s Next

If you want to…	Read this
Explore ad hoc networking concepts	Ad Hoc Networks Fundamentals
Study M2M communication patterns	M2M Overview and Fundamentals
Understand Sensing-as-a-Service	S2aaS Fundamentals
Explore trajectory planning	UAV Trajectory Labs and Implementation
Study FANET fundamentals	FANET Fundamentals