37 FANET Fundamentals
37.1 Learning Objectives
By the end of this chapter, you will be able to:
- Analyze FANET Architecture: Examine Flying Ad Hoc Network structures and evaluate UAV-to-UAV, UAV-to-ground, and UAV-to-satellite communication links
- Compare Network Types: Differentiate FANETs from MANETs and VANETs across six key dimensions including mobility speed, topology dimension, node density, and energy constraints
- Design 3D Topologies: Plan aerial network formations using intra-layer and inter-layer communication across altitude bands (50-500m)
- Evaluate Routing Protocols: Assess proactive, reactive, position-based, and hybrid routing approaches for FANET-specific challenges including sub-minute route lifetimes
- Calculate Link Budgets: Determine maximum UAV separation distances using free-space path loss at 5.8 GHz with Doppler shift verification for high-speed scenarios
- Implement Store-Carry-Forward: Apply delay-tolerant networking techniques for sparse FANET deployments where continuous connectivity cannot be guaranteed
Minimum Viable Understanding
- FANET = 3D mobile ad hoc network: UAVs form temporary wireless networks in three-dimensional airspace at speeds of 10-30 m/s, causing topology changes every 30-67 seconds compared to 100+ seconds in ground MANETs
- Position-based routing is essential: Traditional MANET protocols (AODV, DSDV) generate 70% control overhead in FANETs; GPS-based greedy forwarding reduces this to under 10% by eliminating route discovery entirely
- Five communication types: Intra-plane (same altitude), inter-plane (cross-altitude), UAV-to-ground station, UAV-to-WSN (mobile data mule), and UAV-to-VANET (vehicle coordination)
Sensor Squad: Drones That Talk in the Sky
Sammy the sound sensor was riding on a drone high above the city. “I can hear traffic sounds from way up here!” he shouted to his friends on other drones nearby.
“Look at all those lights below!” called Lila the light sensor from a drone flying at the same height. “But how do we send our readings back to the scientists on the ground?”
Max the motion sensor had an idea. “Our drones can talk to each other! My drone passes the message to Lila’s drone, then Lila’s drone passes it to Bella’s drone, and Bella’s drone is close enough to send it all the way down to the ground station!”
“It is like a game of telephone in the sky!” said Bella the button sensor, pressing her relay button. “But what happens when my drone flies away too fast?”
“That is the tricky part,” explained Sammy. “Our drones move really fast - imagine running as fast as a car on the highway! So the chain of message-passing keeps changing. One second I am talking to Lila, and the next second she has flown too far away, so I need to find Max instead.”
“And we fly in THREE directions,” added Lila. “Not just left-right and forward-back like cars on a road, but also UP and DOWN! That makes it much harder to keep track of who can talk to who.”
Max zoomed his drone higher. “Think of it like a school of fish in the ocean - they all swim together, changing direction constantly, but somehow they stay coordinated. Our drone network works the same way - everyone shares their GPS location so we always know where to send messages next!”
What the Sensor Squad learned: A FANET is like a flying team of friends passing notes to each other while zooming through the air. They use GPS (like a map on a phone) to always know where their friends are, so even when everyone is moving fast, the messages still get through!
37.2 Prerequisites
Before diving into this chapter, you should be familiar with:
- UAV Networks: Fundamentals and Topologies: Understanding UAV network types, basic topologies (star, mesh), and three-dimensional mobility challenges provides the foundation for advanced FANET architectures and coordination
- Multi-Hop Fundamentals: Knowledge of multi-hop routing protocols and relay strategies is essential for designing FANETs where UAVs communicate through intermediary nodes across dynamic 3D topologies
- Wireless Sensor Networks: Familiarity with WSN architectures and data collection strategies helps understand FANET-WSN integration where UAVs serve as mobile data collectors for ground sensor networks
- Networking Basics: Core networking concepts including ad hoc networks, routing protocols, and topology management provide context for FANET-specific challenges and solutions
Key Concepts
- FANET (Flying Ad Hoc Network): A specialized MANET where all nodes are UAVs flying in 3D space at 15–25 m/s, creating topology changes 3–5× faster than ground MANETs — requires position-based or predictive routing
- MANET vs. FANET: Ground MANETs have routes lasting 50–250 seconds (practical for route discovery); FANET routes last 40–67 seconds at typical UAV speeds — making AODV route discovery futile in FANETs
- 3D Topology: UAV networks operate in full 3D space, requiring altitude-aware link quality assessment (two UAVs 100m apart horizontally at different altitudes have a 3D separation > 100m)
- Doppler Effect in FANETs: At 20 m/s, UAVs experience Doppler frequency shifts that degrade link quality on Doppler-sensitive modulations — position-based routing must account for relative velocity
- Position-Based Routing (GPSR): Greedy Perimeter Stateless Routing uses GPS coordinates instead of routing tables — forward to the geographic neighbor closest to the destination, no route discovery needed
- Predictive Routing: UAVs share flight plans and pre-establish routes to where neighboring nodes will be in 30–60 seconds — reduces route establishment failures caused by rapid topology change
- Store-Carry-Forward in FANETs: When no forwarding path exists, buffer packets onboard a UAV and deliver when connectivity is restored — effective for intermittent FANET connectivity
37.3 Flying Ad Hoc Networks (FANETs)
For Beginners: Flying Networks (FANETs)
Drones don’t just fly alone—they can form flying networks, communicating with each other mid-air to coordinate missions. This is called a FANET (Flying Ad Hoc Network).
What’s an ad hoc network? No fixed infrastructure (like cell towers)—devices dynamically connect to whoever’s nearby. Like a group of hikers with walkie-talkies forming a temporary network as they move through mountains.
FANET vs other networks:
- MANET (Mobile Ad Hoc Network): People with smartphones walking around campus
- VANET (Vehicular Ad Hoc Network): Cars communicating on highways
- FANET (Flying Ad Hoc Network): Drones communicating in 3D airspace
Key difference: FANETs move in 3D space at high speeds with rapidly changing topology. A drone swarm searching for wildfire survivors needs to constantly reconfigure who talks to who as drones move.
Three communication types:
- UAV-to-UAV: Drones talking to each other (coordinate search patterns)
- UAV-to-Ground: Drones talking to ground control or ground sensors (download collected data)
- UAV-to-Satellite: Long-range communication for remote operations
| Term | Simple Explanation |
|---|---|
| FANET | Flying Ad Hoc Network—drones forming temporary wireless networks |
| 3D Topology | Network connections in three-dimensional space (not just ground-level like cars/phones) |
| High Mobility | Drones move fast (10-30 m/s), connections break/reform constantly |
| Intra-Layer | Communication between drones at same altitude (horizontal links) |
| Inter-Layer | Communication between drones at different altitudes (vertical links) |
| Data Mule | Drone that collects data by flying close to ground sensors, then uploads to base |
Real example: Amazon testing drone delivery. 50 drones operate in same airspace. They form FANET to: - Coordinate flight paths (avoid collisions) - Share weather sensor data (wind, rain) - Relay messages to distribution center - Reroute around obstacles discovered by other drones
Challenge: Traditional network protocols assume slow-moving nodes. FANETs need protocols that handle very fast topology changes—if Drone A is talking to Drone B, but B flies away, A must quickly find new relay (C or D) within seconds.
Integration with ground networks: Drone swarm collects data from isolated ground sensors (like farms, forests), then uploads bulk data when returning to base. Acts as mobile gateway for sensors that can’t reach fixed infrastructure.
Why 3D matters: Altitude adds complexity. Two drones 100m apart horizontally but at different altitudes (one at 50m, one at 200m) might have 223m separation (use Pythagorean theorem: √(100² + 150²)). This affects communication range and routing decisions.
37.4 FANET Architecture and Communication
FANETs are mobile ad hoc networks formed by UAVs, characterized by high mobility, 3D topology, and dynamic membership.
37.4.1 FANET Communication Architecture
37.4.2 FANET Characteristics vs MANETs/VANETs
| Characteristic | MANET | VANET | FANET |
|---|---|---|---|
| Mobility | Low-Medium | Medium | Very High |
| Speed | 0-5 m/s | 10-30 m/s | 10-30 m/s |
| Topology Dimension | 2D | 2D | 3D |
| Node Density | High | Variable | Low |
| Topology Change | Slow | Fast | Very Fast |
| Path Predictability | Low | High (roads) | Medium (missions) |
| Energy Constraint | Moderate | Low (vehicles) | Very High (battery) |
| Communication Range | 100-300m | 300-500m | 1-5 km |
37.4.3 FANET Communication Types
1. Intra-Plane (Intra-Layer) Communication
- UAVs at same altitude communicate peer-to-peer
- Short distance, high reliability
- Cluster coordination
2. Inter-Plane (Inter-Layer) Communication
- Communication between UAVs at different altitudes
- Relay for extended range
- Hierarchical coordination
3. FANET-Ground Station Communication
- Command and control from GCS
- Mission updates, telemetry upload
- Critical for safety
4. FANET-WSN Communication
- Data collection from ground sensors
- UAV acts as mobile sink
- Extends WSN coverage
5. FANET-VANET Communication
- V2X (Vehicle-to-Everything) support
- Traffic monitoring and guidance
- Emergency message relay
Worked Example: Air-to-Air Link Budget for High-Speed FANET
Scenario: Two UAVs in a FANET swarm need to maintain a reliable 10 Mbps data link while flying at 25 m/s in opposite directions (closing velocity = 50 m/s). You need to determine the maximum separation distance that supports this data rate.
Given:
- Frequency: 5.8 GHz (802.11a/n)
- Transmit power: 20 dBm (100 mW)
- Antenna gain: 5 dBi (omnidirectional)
- Receiver sensitivity for 10 Mbps: -78 dBm
- Required fade margin: 10 dB (for multipath, interference)
- UAV altitude: Both at 150 m
- Closing velocity: 50 m/s
Steps:
- Calculate link budget:
- Available path loss = Tx power + Tx antenna gain + Rx antenna gain - Rx sensitivity - Fade margin
- Available path loss = 20 + 5 + 5 - (-78) - 10 = 98 dB
- Apply free-space path loss formula: FSPL (dB) = 20×log₁₀(d) + 20×log₁₀(f) + 20×log₁₀(4π/c)
- At 5.8 GHz: FSPL = 20×log₁₀(d) + 55.75 dB
- Solve for maximum distance: 98 = 20×log₁₀(d) + 55.75
- 20×log₁₀(d) = 42.25
- d = 10^(42.25/20) = 10^2.1125 = 129.5 m → use 120 m with safety margin
- Calculate Doppler shift: f_doppler = f × v/c = 5.8 GHz × 50 m/s / 3×10⁸ = 967 Hz
- 802.11 subcarrier spacing: 312.5 kHz >> 967 Hz. Doppler within tolerance
- Calculate link duration at maximum range: Starting from 120 m apart, approaching at 50 m/s: Time to pass = minimal (they’re flying toward each other). But if maintaining formation at 120 m: Link stable as long as formation holds
- Verify for diverging case: If flying apart at 50 m/s from 50 m initial separation: Time to 120 m limit = (120 - 50) / 50 = 1.4 seconds before link degrades below 10 Mbps
Result: The air-to-air link supports 10 Mbps at up to 120 m separation. At 5.8 GHz with omnidirectional antennas, Doppler shift from 50 m/s relative motion is negligible. However, the short 1.4-second link duration when UAVs diverge requires proactive handoff to maintain connectivity in dynamic FANET topologies.
Key Insight: FANET air-to-air links benefit from line-of-sight propagation but suffer from limited range due to omnidirectional antennas and regulatory power limits. The critical challenge is not Doppler (which is manageable at UAV speeds) but the short link duration when high-speed UAVs pass each other. Design for 2-3x margin on separation distance to allow time for routing protocol adaptation before links break.
37.5 Interactive: FANET Link Budget Calculator
Use this calculator to explore how UAV separation distance changes with transmit power and frequency:
37.6 FANET Routing Protocols
FANET routing must handle 3D mobility, rapid topology changes, and energy constraints.
Common Misconception: “FANETs Can Use Standard MANET Protocols”
Misconception: Since FANETs are just flying ad hoc networks, existing MANET protocols like AODV or DSDV should work fine with minor tweaks.
Reality: FANET mobility characteristics fundamentally break traditional MANET protocol assumptions, requiring completely different approaches.
Quantified Example - Route Lifetime Comparison:
MANET (Ground-based ad hoc network):
- Node speed: 1-5 m/s (walking/slow vehicles)
- Communication range: 250m
- Route lifetime: 50-250 seconds (250m ÷ 5 m/s)
- AODV route discovery: 2-5 seconds
- Usable route time: 45-245 seconds (plenty of time to use discovered route)
FANET (UAV ad hoc network):
- UAV speed: 15 m/s (typical)
- Communication range: 1000m (better air propagation)
- Route lifetime: 67 seconds (1000m ÷ 15 m/s)
- AODV route discovery: 5-10 seconds (longer due to lower node density)
- Usable route time: 57-62 seconds (route obsolete quickly)
At 25 m/s (aggressive flight):
- Route lifetime: 40 seconds
- Route discovery: 8-12 seconds
- Usable route time: 28-32 seconds (barely usable!)
Why Traditional Protocols Fail:
Control Overhead Explosion: In MANET with 10 nodes moving slowly, topology changes every ~100s. Protocol sends ~5 control packets/node/minute. In FANET with same 10 nodes at 20 m/s, topology changes every ~30s. Control overhead increases 3-5×, often exceeding data traffic (measured: 70% control overhead in FANET vs 15% in MANET).
Route Discovery Futility: By the time AODV discovers multi-hop route (5-10 seconds), intermediate UAVs have moved significantly. Example: 3-hop route discovered in 8 seconds. At 15 m/s, each UAV moved 120m. Original route geometry no longer exists—packets reach dead zones.
Energy Waste: Proactive protocols (DSDV, OLSR) maintain routing tables for all destinations. In FANET, tables must update every 2-5 seconds to stay valid. This continuous control message flooding drains battery 3-4× faster than position-based routing.
FANET-Specific Solutions Required:
Position-Based Routing (GPSR, Greedy Forwarding): Use GPS coordinates, forward to geographic neighbor closest to destination. No route discovery. Adapts instantly to topology changes. Control overhead: <10%.
Predictive Routing: UAVs share flight plans. Protocol predicts future positions, establishes routes proactively to where UAVs will be, not where they are. Reduces link breaks by 40-60%.
Store-Carry-Forward: When no forwarding neighbor exists, buffer packets, carry while flying, forward when connectivity improves. Essential for sparse FANETs.
Bottom Line: MANET protocols assume topology changes slowly enough for route establishment to be worthwhile. FANETs change so fast that discovering routes is often futile—you need geographic/predictive approaches that work without explicit route discovery.
Putting Numbers to It
Scenario: Design a FANET for border surveillance with 5 UAVs covering a 10 km patrol line.
Given: UAV-to-UAV communication range = 2 km, UAV speed = 15 m/s, patrol altitude = 150 m.
Calculations:
Spacing between UAVs: 10 km line ÷ 4 gaps = 2.5 km apart. But 2.5 km > 2 km radio range → connectivity breaks. Solution: space at 1.8 km (90% of range for margin) → need 10 km ÷ 1.8 km ≈ 6 UAVs minimum for continuous chain.
3D distance adjustment: Two UAVs at same horizontal position but 100 m altitude difference: \(d = \sqrt{0^2 + 100^2} = 100\) m. Two UAVs 1.8 km apart horizontally, one at 150 m and one at 200 m altitude: \(d = \sqrt{1800^2 + 50^2} = 1800.7\) m (negligible altitude penalty at this scale).
Route lifetime: At 15 m/s closing velocity (UAVs moving toward each other), 2 km link lasts \(t = 2000 / 15 = 133\) seconds. With AODV route discovery taking 5-10 seconds, usable route time = 123-128 seconds → adequate for position-based routing, but marginal for traditional reactive protocols.
Worked example: With 6 UAVs at 1.8 km spacing, maximum hop count from end-to-end = 5 hops. At ~50 ms latency per hop, total end-to-end latency = 250 ms (acceptable for surveillance video relay). Each hop adds 50 ms processing + transmission delay, so a packet from UAV-1 to ground station takes \(5 \times 50 = 250\) ms.
Key insight: The 90% spacing rule (1.8 km for 2 km radios) provides a 200 m link margin that accommodates GPS positioning error (±5 m) and Fresnel zone clearance at altitude, preventing intermittent connectivity as UAVs drift within their patrol zones.
37.7 Knowledge Check
Test your understanding of FANET fundamentals.
Common Pitfalls
1. Using AODV Directly in FANET
AODV requires 5–10 seconds for route discovery. At 20 m/s, UAVs move 100–200m during discovery — the discovered route is already stale. AODV generates 3× more control overhead in FANET than in ground MANET. Use position-based routing (GPSR) or predictive routing instead of adapting AODV for aerial networks.
2. Ignoring 3D Geometry in Link Quality Estimation
Students calculate UAV separation using 2D distance (horizontal only). Two UAVs 100m apart horizontally at altitudes 50m and 200m are actually 180m apart in 3D (Pythagorean). This 80% underestimate of separation causes incorrect link quality predictions and unexpected disconnections. Always use 3D Euclidean distance.
3. Applying Ground MANET Performance Benchmarks to FANET
MANET routing performance metrics (route lifetime, control overhead) are measured for pedestrian (1–1.5 m/s) or vehicular (10–14 m/s) mobility. FANET at 20 m/s has fundamentally different trade-offs. Don’t compare FANET protocols against MANET benchmarks — use FANET-specific simulation scenarios.
4. Neglecting Battery as a Routing Constraint
FANET routing affects battery consumption — control message floods drain battery 2–3× faster than data forwarding. Protocols that minimize control overhead (GPSR: near-zero control messages) are preferred over flooding-based protocols in battery-limited UAVs. Always include energy consumption in FANET protocol evaluation.
37.8 Summary and Key Takeaways
This chapter covered the fundamentals of Flying Ad Hoc Networks (FANETs):
- FANET Definition: Flying ad hoc networks are mobile ad hoc networks formed by UAVs, characterized by 3D topology, very high mobility (10-30 m/s), and dynamic membership
- Comparison with MANETs/VANETs: FANETs differ from ground-based networks in topology dimension (3D vs 2D), node density (low), energy constraints (very high), and topology change rate (very fast)
- Communication Types: FANETs support five communication types: intra-plane (same altitude), inter-plane (different altitudes), ground station, WSN, and VANET integration
- Routing Challenges: Traditional MANET protocols fail in FANETs due to high control overhead, route discovery delays, and energy waste from frequent updates
- Position-Based Routing: GPSR and greedy forwarding use GPS coordinates for next-hop decisions without explicit route discovery, adapting instantly to topology changes
- Store-Carry-Forward: Essential technique for sparse FANETs where UAVs buffer packets during connectivity gaps and forward when links become available
37.9 What’s Next
| If you want to… | Read this |
|---|---|
| Study FANET gateway selection algorithms | FANET Gateway Optimization |
| Explore FANET-VANET integration | FANET-VANET Integration |
| Understand UAV network features and challenges | UAV Network Features and Challenges |
| Explore UAV swarm coordination | UAV Swarm Coordination |
| Review all UAV network concepts | UAV Networks: Production and Review |