36 UAV: FANETs and Integration
36.1 Learning Objectives
By the end of this chapter, you will be able to:
- Explain FANET Architecture: Describe Flying Ad Hoc Network structures and UAV-to-UAV communication in 3D airspace
- Compare Network Types: Differentiate FANETs from MANETs and VANETs based on mobility, topology, and energy
- Design Gateway Selection: Implement stability-score-based algorithms for optimal ground connectivity
- Integrate Ground Networks: Connect FANETs with terrestrial IoT and vehicular infrastructure
- Evaluate Routing Protocols: Select position-based and predictive routing for high-mobility environments
- Optimize Multi-Layer Architecture: Plan altitude stratification for sensing, relay, and communication separation
Minimum Viable Understanding
If you take away only three things from this chapter:
- FANETs are 3D mobile ad hoc networks with uniquely rapid topology changes – UAVs move at 10-30 m/s with full three-dimensional freedom, making traditional 2D routing protocols (designed for ground-based MANETs/VANETs) insufficient. Position-based routing using GPS coordinates replaces route-discovery protocols that cannot keep pace with link changes.
- Gateway selection is the critical bottleneck for FANET-to-ground communication – a stability score combining link quality (40%), residual energy (30%), and network centrality (30%) identifies the best UAV to relay data to the ground control station. Poor gateway selection causes 60%+ packet loss in high-mobility scenarios.
- FANET-VANET integration creates heterogeneous multi-layer networks – combining flying UAVs (high altitude, wide coverage) with ground vehicles (street-level, localized) enables applications impossible with either alone, such as disaster response where UAVs provide connectivity while ground vehicles deliver supplies.
Sensor Squad: The Flying Messenger Network
Hey Sensor Squad! Imagine Sammy, Lila, Max, and Bella are playing a giant game of tag in a huge park – but they cannot shout across the whole park. So they come up with a clever plan!
Sammy’s Idea – “Flying Messenger Drones!”
Sammy brings toy drones that can carry messages between players. But here is the tricky part – the drones are flying around too, so everyone is moving!
Here is how the Sensor Squad’s flying network works:
- Lila is the Relay Drone: She flies her drone between Sammy and Max, passing messages. But when Max runs to the other side of the park, Lila’s drone must quickly find a new path – maybe through Bella’s drone instead!
- Max is the Gateway: His drone is the only one close enough to the park entrance (the “ground station”). So ALL messages to the outside world go through Max’s drone. But what if Max’s drone battery is low? They need a backup plan!
- Bella is the Scout: Her drone flies high above to see where everyone is. She reports positions so other drones know which way to send messages. She is like a “GPS helper” for the network!
- Sammy’s 3D Challenge: Unlike walkie-talkies on the ground, these drones fly UP, DOWN, and SIDEWAYS. A drone 50 meters away horizontally but 100 meters above is actually farther than you think! (Use the triangle rule: about 112 meters away)
Why this matters: Real drone swarms work exactly like this! Search-and-rescue drones form flying networks to find people after earthquakes. Each drone talks to its neighbors, picks the best “gateway” to send data home, and constantly adjusts as drones move around in 3D space.
Fun fact: A flock of birds is nature’s FANET! Birds communicate through position and movement patterns, adjust formation dynamically, and the bird closest to the destination leads the way – just like a gateway UAV!
For Beginners: Flying Networks Made Simple
What is a FANET? A Flying Ad Hoc Network is a temporary wireless network formed by drones (UAVs) communicating with each other while airborne. Think of it as a Wi-Fi hotspot that flies and keeps changing shape.
Why not just use regular networks? Drones are different from phones or cars:
| Feature | Phone Network (MANET) | Car Network (VANET) | Drone Network (FANET) |
|---|---|---|---|
| Movement | Walking (1-2 m/s) | Roads (10-30 m/s) | 3D airspace (10-30 m/s) |
| Dimensions | 2D (ground) | 2D (roads) | 3D (any direction) |
| Topology Change | Slow | Medium | Very Fast |
| Energy | Plugged in / big battery | Engine-powered | Small battery, critical |
Three key ideas to remember:
- Gateway UAV: One special drone is chosen to talk to the ground station. It is picked based on a “stability score” – how good its radio signal is, how much battery it has, and how well-connected it is to other drones.
- Position-Based Routing: Instead of building routing tables (too slow when everything moves fast), drones use GPS coordinates to forward messages toward the destination. “I know where you are, so I send the message in your direction.”
- Multi-Layer Architecture: Drones at different altitudes have different jobs. High drones (200m+) relay long-distance messages. Low drones (50-100m) collect sensor data. This separation prevents interference and improves efficiency.
Real-world example: After a hurricane knocks out cell towers, a swarm of 20 drones is launched. They form a FANET to provide temporary communication coverage. High-altitude drones act as relays, mid-altitude drones scan for survivors with cameras, and low-altitude drones collect data from ground sensors. The gateway drone connects the entire swarm to the emergency command center.
36.2 Overview
This section covers Flying Ad Hoc Networks (FANETs) and their integration with ground networks. FANETs are mobile ad hoc networks formed by UAVs, characterized by high mobility, 3D topology, and dynamic membership. These chapters explore FANET architecture, gateway selection algorithms, and integration with vehicular and sensor networks.
How It Works: FANET Gateway Selection in 3D Space
The Core Problem: In a FANET, one UAV must be designated as the gateway to relay data between the flying swarm and the ground control station (GCS). But which UAV should be chosen when they are all moving at 10-30 m/s in three-dimensional space?
Step-by-Step Gateway Selection Process:
Identify Candidates: Filter UAVs that are within communication range of the GCS (typically within 500-800m Euclidean distance using 3D coordinates). If UAV is at position (x, y, z) and GCS is at (0, 0, 0), calculate distance = sqrt(x² + y² + z²)
Compute Link Quality (LQ): For each candidate, measure RSSI (Received Signal Strength Indicator, typically -40 to -90 dBm) and PDR (Packet Delivery Ratio, 0-100%). Normalize both to 0-1 scale and combine: LQ = 0.5 × RSSI_norm + 0.5 × PDR_norm
Compute Residual Energy (RE): Combine battery percentage and estimated remaining flight time: RE = 0.6 × battery_pct + 0.4 × (flight_time_remaining / max_flight_time). This ensures we do NOT select a UAV with good signal but nearly dead battery
Compute Network Centrality (NC): Measure how well-connected the UAV is to the rest of the FANET. NC = 0.5 × (neighbor_count / max_neighbors) + 0.5 × betweenness_centrality. A UAV with 6 neighbors routes more traffic than one with only 2 neighbors
Calculate Stability Score: Weighted combination: S = 0.4 × LQ + 0.3 × RE + 0.3 × NC. The weights prioritize link quality (40%) since the gateway’s primary job is reliable GCS communication, followed by energy sustainability (30%) and network connectivity (30%)
Select Maximum Score: The UAV with the highest stability score becomes the gateway. If scores are tied, prefer the UAV with higher residual energy to maximize time before next re-selection
Set Re-Evaluation Triggers: Monitor the gateway continuously. Re-run selection if: timer expires (every 20-30 seconds), gateway battery drops below 20%, RSSI to GCS drops below -80 dBm, or gateway’s neighbor count drops below 3
Real-World Example: In a search-and-rescue FANET with 8 UAVs, three are within GCS range. UAV-A has excellent signal (-55 dBm) but 18% battery remaining. UAV-C has moderate signal (-72 dBm) but 85% battery and 6 neighbors. The stability score favors UAV-C (score 0.696 vs UAV-A’s 0.591) because UAV-A would need replacement within minutes, disrupting communications during a critical mission.
Why This Works: The multi-criteria scoring prevents “greedy” selection that picks only the best signal and then fails minutes later. Weighted scoring balances immediate performance (link quality) with long-term sustainability (energy) and network resilience (centrality).
36.3 Chapters in This Section
36.3.1 FANET: Flying Ad Hoc Network Fundamentals
Understand the core concepts of Flying Ad Hoc Networks:
- FANET Architecture: UAV-to-UAV communication in 3D space
- Comparison with MANETs/VANETs: Mobility, topology dimension, and energy constraints
- Communication Types: Intra-plane, inter-plane, ground station, and WSN links
- Routing Protocols: Position-based and predictive routing for high-mobility environments
36.3.2 FANET: Gateway Selection and Optimization
Design algorithms for optimal ground station connectivity:
- Stability Score Formula: Weighted combination of link quality, energy, and centrality
- Sub-Area Partitioning: K-means clustering for balanced gateway distribution
- Dynamic Reselection: Triggers and handover procedures for changing conditions
- Load Balancing: Distributing traffic among multiple gateways
36.3.3 FANET-VANET Integration and Ground Networks
Integrate UAV networks with vehicular and ground infrastructure:
- Integration Use Cases: Coverage extension, traffic monitoring, emergency response
- Dual Mobility Challenges: Handling both UAV and vehicle movement
- Position-Based Routing: Energy-aware geographic forwarding in 3D
- Multi-Layer Architecture: Altitude stratification for sensing and relay separation
36.4 FANET vs MANET vs VANET Comparison
Understanding how FANETs differ from other ad hoc network types is essential for selecting the right routing protocols and architecture.
36.5 Gateway Selection Process
The gateway UAV is the critical link between the aerial FANET and the ground control station. Selection uses a weighted stability score.
36.6 FANET-VANET Integration Architecture
When UAVs operate alongside ground vehicles, a heterogeneous multi-layer network emerges with unique routing and handover challenges.
36.7 Learning Path
## FANET Gateway Stability Score Calculator
Compute and compare UAV gateway stability scores interactively:
36.8 Prerequisites
Before starting these chapters, ensure familiarity with:
- UAV Networks: Fundamentals and Topologies: Basic UAV network concepts, star and mesh topologies, 3D mobility challenges
- Multi-Hop Fundamentals: Relay strategies and multi-hop routing protocols
- Wireless Sensor Networks: WSN architectures for understanding FANET-WSN integration
- Networking Basics: Core ad hoc networking and routing concepts
36.9 Key Concepts
| Concept | Description |
|---|---|
| FANET | Flying Ad Hoc Network – UAVs forming temporary wireless networks in 3D space |
| 3D Topology | Network connections in three-dimensional space with altitude layers |
| High Mobility | UAVs move at 10-30 m/s, causing very fast topology changes |
| Intra-Layer | Horizontal communication between UAVs at same altitude |
| Inter-Layer | Vertical communication between UAVs at different altitudes |
| Gateway UAV | Selected UAV that relays data between FANET and ground control station |
| Stability Score | Weighted metric combining link quality, energy, and centrality for gateway selection |
| Position-Based Routing | Geographic forwarding using GPS coordinates without explicit route discovery |
| FANET-VANET Integration | Heterogeneous network combining aerial and ground vehicle networks |
| V2U Link | Vehicle-to-UAV communication link bridging ground and aerial networks |
36.10 Common Pitfalls
Common Pitfalls in FANET Design
1. Applying 2D routing protocols to 3D space. Many designers use MANET routing protocols (AODV, DSR) without modification for FANETs. These protocols assume 2D topology and cannot account for altitude differences. A drone 100m away horizontally but 150m higher is actually 180m away (3D Euclidean distance), which may exceed communication range. Always use 3D distance calculations and position-based routing.
2. Ignoring gateway re-selection frequency. Setting gateway re-evaluation timers too long (e.g., 5 minutes) means the network continues using a gateway UAV that may have moved out of ground station range or depleted its battery. Conversely, re-evaluating too frequently (every 2 seconds) wastes bandwidth on control messages. A 20-30 second interval with event-driven triggers (energy < 20%, RSSI drop) balances stability and responsiveness.
3. Underestimating FANET-VANET handover complexity. When a message transitions from a ground vehicle (VANET) to a UAV (FANET), the routing protocol, addressing scheme, and QoS parameters may all change. Designers often assume seamless handover, but without a proper cross-network gateway protocol, packets are dropped at the V2U boundary. Design explicit protocol translation at the integration layer.
4. Neglecting wind and weather effects on link quality. Indoor simulations show excellent FANET performance, but real deployments face wind turbulence, rain attenuation, and temperature-induced signal fading. A link budget calculated for clear weather may fail in moderate wind (UAV wobble changes antenna orientation by 10-15 degrees, reducing gain by 3-6 dB).
5. Single gateway as a single point of failure. Selecting only one gateway UAV creates a critical dependency. If that UAV fails (battery depletion, hardware fault, collision avoidance maneuver), the entire FANET loses ground connectivity. Always design with at least two candidate gateways and implement fast failover (< 5 seconds).
36.11 Worked Example: Gateway Selection for a Search-and-Rescue FANET
Worked Example: Computing Gateway Stability Scores
Scenario: A search-and-rescue mission deploys 8 UAVs to search a 2 km x 2 km disaster area. The ground control station (GCS) is located at position (0, 0, 0). Three UAVs are within communication range of the GCS and are candidates for gateway selection. We need to compute stability scores and select the best gateway.
Given Data:
| UAV | Position (x,y,z) m | RSSI (dBm) | PDR (%) | Battery (%) | Flight Time Left (min) | Neighbor Count | Betweenness |
|---|---|---|---|---|---|---|---|
| UAV-A | (200, 150, 100) | -65 | 95 | 72 | 35 | 5 | 0.42 |
| UAV-B | (100, 80, 80) | -55 | 98 | 45 | 18 | 4 | 0.35 |
| UAV-C | (300, 200, 120) | -72 | 88 | 85 | 45 | 6 | 0.51 |
Step 1: Normalize Link Quality (LQ)
Link quality combines RSSI and PDR on a 0-1 scale:
- LQ = 0.5 * RSSI_norm + 0.5 * PDR_norm
- RSSI_norm: Map [-90 dBm (worst), -40 dBm (best)] to [0, 1]
- PDR_norm: Direct percentage / 100
UAV-A: RSSI_norm = (-65 - (-90)) / (-40 - (-90)) = 25/50 = 0.50; PDR_norm = 0.95; LQ = 0.5(0.50) + 0.5(0.95) = 0.725
UAV-B: RSSI_norm = (-55 - (-90)) / (-40 - (-90)) = 35/50 = 0.70; PDR_norm = 0.98; LQ = 0.5(0.70) + 0.5(0.98) = 0.840
UAV-C: RSSI_norm = (-72 - (-90)) / (-40 - (-90)) = 18/50 = 0.36; PDR_norm = 0.88; LQ = 0.5(0.36) + 0.5(0.88) = 0.620
Step 2: Normalize Residual Energy (RE)
RE combines battery percentage and remaining flight time:
- RE = 0.6 * battery_pct + 0.4 * (flight_time / max_flight_time)
- Assume max_flight_time = 60 minutes
UAV-A: RE = 0.6(0.72) + 0.4(35/60) = 0.432 + 0.233 = 0.665
UAV-B: RE = 0.6(0.45) + 0.4(18/60) = 0.270 + 0.120 = 0.390
UAV-C: RE = 0.6(0.85) + 0.4(45/60) = 0.510 + 0.300 = 0.810
Step 3: Normalize Network Centrality (NC)
NC combines neighbor count and betweenness centrality:
- NC = 0.5 * (neighbors / max_neighbors) + 0.5 * betweenness
- Assume max_neighbors = 7 (total UAVs minus self)
UAV-A: NC = 0.5(5/7) + 0.5(0.42) = 0.357 + 0.210 = 0.567
UAV-B: NC = 0.5(4/7) + 0.5(0.35) = 0.286 + 0.175 = 0.461
UAV-C: NC = 0.5(6/7) + 0.5(0.51) = 0.429 + 0.255 = 0.684
Step 4: Compute Stability Score
S = 0.4 * LQ + 0.3 * RE + 0.3 * NC
| UAV | LQ (x0.4) | RE (x0.3) | NC (x0.3) | Total Score |
|---|---|---|---|---|
| UAV-A | 0.290 | 0.200 | 0.170 | 0.660 |
| UAV-B | 0.336 | 0.117 | 0.138 | 0.591 |
| UAV-C | 0.248 | 0.243 | 0.205 | 0.696 |
Result: UAV-C is selected as the gateway with the highest stability score of 0.696, despite having the weakest signal. Its high battery (85%), longest remaining flight time (45 min), and best network centrality (6 neighbors, betweenness 0.51) outweigh the moderate link quality.
Key Insight: UAV-B has the best signal quality but the lowest battery – it would become a poor gateway within 18 minutes. The stability score correctly penalizes this short-term advantage and favors the more durable UAV-C.
Putting Numbers to It
The FANET gateway stability score balances multiple criteria through weighted combination. For link quality \(LQ\), residual energy \(RE\), and network centrality \(NC\) (each normalized to [0,1]):
\[ S = w_{LQ} \cdot LQ + w_{RE} \cdot RE + w_{NC} \cdot NC \]
where \(w_{LQ} = 0.4\), \(w_{RE} = 0.3\), \(w_{NC} = 0.3\) (weights sum to 1). For UAV-C: \(\text{RSSI}_{norm} = \frac{-72 - (-90)}{-40 - (-90)} = \frac{18}{50} = 0.36\), \(\text{PDR}_{norm} = 0.88\), so \(LQ = 0.5(0.36) + 0.5(0.88) = 0.620\). \(RE = 0.6 \times 0.85 + 0.4 \times \frac{45}{60} = 0.510 + 0.300 = 0.810\), \(NC = 0.5 \times \frac{6}{7} + 0.5 \times 0.51 = 0.429 + 0.255 = 0.684\). Thus \(S_C = 0.4(0.620) + 0.3(0.810) + 0.3(0.684) = 0.248 + 0.243 + 0.205 = 0.696\). This matches the worked example – LQ uses both RSSI and PDR, not RSSI alone.
Re-evaluation triggers for this deployment:
- Timer-based: Re-evaluate every 30 seconds
- UAV-C battery drops below 20% (about 36 minutes from now)
- RSSI to GCS drops below -80 dBm (UAV-C drifts out of range)
- UAV-C neighbor count drops below 3 (becoming isolated)
36.12 What You’ll Learn
By completing these chapters, you will be able to:
- Explain FANET Architecture: Describe Flying Ad Hoc Networks and UAV-to-UAV communication
- Compare Network Types: Differentiate FANETs from MANETs and VANETs based on mobility and topology
- Design 3D Topologies: Plan aerial network formations accounting for three-dimensional space
- Apply High-Mobility Routing: Select routing protocols suitable for very fast topology changes
- Implement Gateway Selection: Design stability-score-based algorithms for optimal ground connectivity
- Integrate Ground Networks: Connect FANETs with terrestrial IoT and vehicular infrastructure
- Optimize for Constraints: Balance communication range, energy, and mission requirements
36.13 Knowledge Check
Test your understanding of FANET architecture, gateway selection, and integration concepts.
36.14
36.15 Enhanced Summary
36.15.1 Key Takeaways
FANETs represent the most challenging class of ad hoc networks due to their combination of high mobility (10-30 m/s), three-dimensional topology, and severe energy constraints. This section covered three interconnected topics:
| Topic | Core Concept | Key Metric |
|---|---|---|
| FANET Fundamentals | 3D mobile ad hoc networks formed by UAVs | Topology change rate: every 10-30 seconds |
| Gateway Selection | Stability-score algorithm for ground connectivity | S = 0.4LQ + 0.3RE + 0.3*NC |
| FANET-VANET Integration | Heterogeneous multi-layer networks | V2U link range: 300-500m |
36.15.2 Architecture Decision Framework
36.15.3 Critical Design Principles
- Always use 3D Euclidean distance for link budget and communication range calculations. 2D distance underestimates the true path length and leads to connectivity assumptions that fail in deployment.
- Design for gateway redundancy with at least two candidate gateways and soft handover procedures. A single gateway is a single point of failure for the entire FANET.
- Match routing protocol to mobility – position-based routing (GPSR) for high-speed FANETs, predictive routing for mission-planned trajectories, and hybrid approaches for FANET-VANET integration.
- Altitude stratification scales better than flat topologies for missions requiring both sensing and long-range relay, reducing interference between data collection and backbone forwarding.
- Factor in environmental conditions – wind, rain, and temperature affect both UAV stability (antenna orientation) and signal propagation (attenuation), requiring 6-10 dB link margin beyond clear-weather calculations.
Try It Yourself: Design a Multi-Layer FANET for Disaster Response
Scenario: You are designing a FANET deployment for post-earthquake search-and-rescue. The area is 3 km × 3 km with collapsed buildings up to 30m high. You have 15 UAVs available with the following specifications:
- Communication range: 500m line-of-sight
- Battery life: 45 minutes at cruise speed
- Sensors: thermal camera (range 100m), ground sensor interface (range 50m)
- GCS location: Edge of the disaster area at ground level
Your Task: Design a three-layer FANET architecture and answer these questions.
Question 1: What altitudes should you assign to each layer? - Sensing layer: 50-80m (above 30m buildings, close enough for thermal camera 100m range) - Relay layer: 150-180m (midpoint for inter-layer connectivity) - Backbone layer: 280-320m (maximum altitude for wide area coverage)
Question 2: How many UAVs should you allocate to each layer to achieve coverage? - Sensing layer: Coverage area = π × 100² = 31,416 m² per UAV. Total area = 3,000m × 3,000m = 9,000,000 m². Need 9,000,000 / 31,416 ≈ 7 sensing UAVs (with 20% overlap) - Relay layer: Need enough to connect sensing UAVs to backbone. With 500m range, 4 relay UAVs positioned at 750m intervals cover the area - Backbone layer: 3 backbone UAVs positioned at 1km intervals provide long-distance forwarding - Gateway: 1 backbone UAV positioned closest to GCS serves as primary gateway
Total: 7 + 4 + 3 + 1 = 15 UAVs (perfectly utilizing available resources)
Question 3: With 45-minute battery life, how often must UAVs return to base for battery swaps? - Flight time budget: 45 minutes total - 5 min outbound - 5 min return - 5 min safety margin = 30 minutes on-station - Rotation schedule: Deploy in two waves of 15 UAVs each. Wave 1 operates for 30 min, then returns while Wave 2 deploys, creating continuous coverage
Question 4: The gateway UAV (backbone layer) is 300m altitude, positioned at (500m, 500m, 300m) from GCS at (0, 0, 0). What is the 3D distance to GCS? - Distance = sqrt(500² + 500² + 300²) = sqrt(250,000 + 250,000 + 90,000) = sqrt(590,000) ≈ 768m - Link budget check: 768m > 500m communication range! This gateway position WILL NOT WORK. - Fix: Move gateway to (300m, 300m, 300m): sqrt(300² + 300² + 300²) = sqrt(270,000) ≈ 520m – still marginal! - Better fix: Move gateway to (200m, 200m, 300m): sqrt(200² + 200² + 300²) = sqrt(170,000) ≈ 412m – within range with margin
Question 5: What triggers should initiate gateway re-selection? - Timer: Every 25 seconds (topology changes quickly) - Energy: Gateway battery < 25% (15% remaining = 6.75 min, enough time for handover + return flight) - Signal: RSSI to GCS < -80 dBm - Centrality: Neighbor count < 2 (becoming isolated from FANET)
Bonus Challenge: A 6.0 magnitude aftershock occurs 20 minutes into the mission, causing all UAVs to trigger emergency collision avoidance and scatter. How do you re-establish the network? 1. Backbone layer immediately broadcasts beacon to re-locate scattered UAVs 2. All UAVs report positions to backbone via direct link (no multi-hop) 3. Gateway re-selection runs immediately (old gateway may have moved out of GCS range) 4. UAVs re-converge to planned formation positions over 60-90 seconds 5. Sensing layer resumes thermal scanning once relay connectivity is restored
What to Observe:
- 3D distance calculations are CRITICAL – a seemingly good gateway position fails when altitude is factored in
- Layered architecture enables functional specialization (sensing vs relay vs backbone)
- Battery life constrains mission duration – rotation schedules and energy-aware planning are essential
- Emergency re-convergence protocols are as important as normal operation procedures
36.16 Concept Relationships
| Concept | Relates To | Relationship Type | Significance |
|---|---|---|---|
| FANET 3D mobility | MANET/VANET 2D mobility | Architectural extension | FANETs extend ground-based ad hoc networks into 3D airspace, requiring Euclidean distance calculations (not Manhattan distance) and altitude-aware routing – a UAV 200m horizontal but 150m above is actually 250m away via sqrt(200² + 150²) |
| Gateway stability score | Quality of Service (QoS) | Multi-criteria optimization | The weighted formula (40% link quality + 30% energy + 30% centrality) balances immediate performance with long-term sustainability – prevents “greedy” selection of best-signal UAV that depletes battery in minutes |
| Position-based routing | GPS/GNSS navigation | Protocol dependency | GPSR (Greedy Perimeter Stateless Routing) relies on accurate GPS coordinates for each UAV – GPS outages or spoofing attacks cause routing failures, requiring inertial navigation system (INS) backup |
| FANET-VANET integration | Heterogeneous networking | Cross-layer design | Vehicle-to-UAV (V2U) links bridge 2D ground networks with 3D aerial networks, requiring protocol translation at the integration layer – VANET uses road-based addressing while FANET uses geographic coordinates |
| Multi-layer altitude stratification | Interference mitigation | Spatial frequency reuse | Separating sensing (50m), relay (150m), and backbone (300m) UAVs by altitude allows the same frequency to be reused vertically without inter-layer interference – increases network capacity by 3× versus flat single-layer |
| Soft handover for gateway re-selection | Seamless mobility in cellular networks | Reliability mechanism | Maintaining both old and new gateways active during 2-5 second overlap period (transferring routing tables and buffered packets) prevents data loss – mirrors “make-before-break” handover in LTE networks |
36.17 See Also
- UAV Network Fundamentals and Topologies - Star vs mesh topology trade-offs, 3D communication challenges, and basic UAV network architectures
- Position-Based Routing Protocols - GPSR (Greedy Perimeter Stateless Routing) and geographic forwarding for mobile ad hoc networks
- Multi-Hop Relay Strategies - Relay node selection, opportunistic forwarding, and cooperative communication in multi-hop networks
- Vehicular Ad Hoc Networks (VANETs) - Ground vehicle networks for understanding FANET-VANET integration challenges
- Wireless Sensor Network Integration - FANET-WSN connectivity for UAV data collection from ground sensors
36.18 What’s Next
| If you want to… | Read this |
|---|---|
| Get hands-on UAV trajectory implementation | UAV Trajectory Labs and Implementation |
| Study FANET fundamentals in depth | FANET Fundamentals |
| Explore FANET-VANET integration | FANET-VANET Integration |
| Learn gateway selection for FANETs | FANET Gateway Optimization |
| Review all UAV network concepts | UAV Networks: Production and Review |