30  Flying Ad-Hoc Networks (FANETs)

Core Concepts for 3D Aerial Ad Hoc Links, Routing Records, and Sparse Connectivity

emerging-paradigms
uav
fanet

30.1 Start Simple

Start with a mission that moves, loses energy, and changes its radio path while it works. In Flying Ad-Hoc Networks (FANETs), the practical question is what the aircraft must sense, relay, decide, and prove before the flight or network role is safe enough to trust.

In 60 Seconds

Flying Ad Hoc Networks (FANETs) are temporary wireless networks formed by UAVs in 3D space. The design problem is not only “which radio can reach?” but also “which neighbor will still be useful when the packet arrives?” A good FANET design records fresh position, altitude, heading, neighbor, link, route, buffer, and gateway state before choosing direct forwarding, geographic forwarding, predictive routing, or store-carry-forward.

30.2 Learning Objectives

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

  • Explain what makes a FANET different from ground mobile ad hoc networks and road-constrained vehicular networks.
  • Identify the main aerial and ground-facing link types used in UAV team missions.
  • Describe the topology records a UAV needs before it can make a routing decision.
  • Choose among table-driven, on-demand, position-based, predictive, and store-carry-forward routing patterns based on mission conditions.
  • Build a readiness checklist that keeps FANET designs focused on connectivity, safety, energy, and proof instead of unsupported performance promises.

30.3 Routes Move With Aircraft

If you only need the intuition, this layer is enough: a FANET route is useful only while the aircraft positions, link quality, mission priority, and gateway path still make sense. A static path can become stale in seconds.

Four UAV network challenges: frequently changing topology from 3D mobility, intermittent links, energy constraints, and security threats such as GPS spoofing and link hijacking.
UAV networks are shaped by rapidly changing topology, intermittent links, tight energy budgets, and open-RF security threats.

Mobile summary: A FANET forwarding choice should be based on current 3D position, heading, neighbor freshness, link quality, route and buffer state, and gateway reachability.

3D position

Forwarding depends on latitude, longitude, altitude, heading, speed, and expected movement.

Fresh neighbors

A neighbor record needs age, signal history, packet success, and whether the UAV is moving toward usefulness.

Exit path

Mission traffic often needs a ground, vehicle, satellite, or backhaul gateway before it is complete.

30.4 Practitioner: Build the Routing Record

Before choosing a routing pattern, write a short record for the packet class. A high-priority safety alert should not use the same forwarding rule as a low-priority image summary that can wait for a gateway pass.

Packet class

Name the traffic: telemetry, alert, map update, inspection image, command, or delayed sensor collection.

Allowed delay

State whether the packet must move now, may be buffered, or should be discarded when the route is stale.

Routing mode

Choose table-driven, on-demand, position-based, predictive, or store-carry-forward from the current evidence.

Safety limit

Record when routing traffic must yield to flight energy, collision avoidance, return-to-base, or command priority.

30.5 Why FANET Decisions Age Quickly

FANET routing fails when the control record is older than the airspace reality. A route table, predicted path, or gateway choice can be correct when computed and wrong by the time a packet reaches the next hop.

  • Geometry changes: altitude and heading can change usable distance even when a map view looks close.
  • Link changes: line of sight, antenna orientation, interference, and packet loss can change faster than mission plans.
  • Priority changes: safety alerts, commands, telemetry, and bulk imagery deserve different delay and retry rules.
  • Partition changes: sparse UAV teams may need buffering until a relay or gateway becomes useful again.
Quick Check: FANET Routing Boundaries
Minimum Viable Understanding
  • A FANET is an ad hoc network whose nodes are UAVs moving in 3D space.
  • Links change because UAVs move horizontally, change altitude, turn, return to base, lose line of sight, or hand off to ground systems.
  • Routing decisions need fresh local records: position, neighbor state, link quality, intended path, and whether buffering is acceptable.
  • Position-based and predictive routing are common FANET tools, but sparse missions also need store-carry-forward behavior.

30.6 Prerequisites

Before continuing, revisit these chapters if any of the terms are unfamiliar:

30.7 What Is a FANET?

A Flying Ad Hoc Network (FANET) is a self-organizing network formed by UAVs without relying on one fixed communication path. A FANET may include a ground station, gateways, or sensor systems, but the defining feature is that UAVs can forward traffic for each other while the aerial topology changes.

The same mission can contain several link roles at once:

30.8 FANETs vs Ground Ad Hoc

Ground mobile ad hoc networks and vehicular networks already deal with movement, but FANETs add several extra pressures:

  • 3D topology: altitude is part of the route, not just a drawing detail.
  • Sparse neighbors: UAV missions often spread nodes apart to cover an area, so every relay choice matters.
  • Fast path aging: a route can become less useful as UAVs turn, climb, descend, or pass behind obstacles.
  • Planned mobility: flight plans can make some movement predictable, but wind, safety limits, task changes, and return-to-base events still change the topology.
  • Energy and payload constraints: routing traffic competes with sensing, compute, flight time, and safety reserve.
  • Gateway dependence: many FANETs are only useful if the aerial path eventually reaches a ground, vehicle, satellite, or backhaul connection.

The design question is therefore record-based: what does the node know now, how fresh is that knowledge, and which forwarding choice remains useful long enough to deliver the traffic?

30.9 Topology Records

A FANET node should not forward based only on a static route table. It needs a compact routing record that describes the local topology and the mission state.

30.9.1 Position and altitude

The node records its own position, altitude, and the advertised positions of nearby UAVs. Altitude changes can shorten or lengthen the true path.

30.9.2 Heading and velocity

Direction matters because a neighbor moving toward the destination is more useful than a neighbor that is about to leave the useful region.

30.9.3 Neighbor table freshness

Each neighbor entry needs a timestamp or freshness state. Stale neighbor data is worse than no neighbor data because it can create false confidence.

30.9.5 Route and buffer state

The node tracks whether a route is currently usable, whether a predictive path is planned, and whether packets may be buffered until contact returns.

30.9.6 Gateway state

For traffic that must leave the aerial network, the node tracks which gateway is reachable, overloaded, moving away, or reserved for higher priority traffic.

The overview depth layer introduces the compact topology record that keeps FANET routing tied to current mission state.

30.10 Routing Choices

FANET routing is not one protocol choice for every mission. It is a decision about how much topology state is worth maintaining and how quickly that state becomes stale.

30.10.1 Table-driven routing

Maintains routes proactively. This can work for small or stable aerial formations, but it becomes expensive when neighbor state changes faster than tables can remain useful.

30.10.2 On-demand routing

Discovers routes only when traffic needs them. This can be acceptable when route discovery is short compared with route usefulness.

30.10.3 Position-based routing

Uses location and neighbor information to choose the next hop. It reduces dependence on a complete route table and fits many mobile aerial paths.

30.10.4 Predictive routing

Uses mission plans, headings, or expected contact windows to route toward where nodes will be, not only where they are now.

30.10.5 Store-carry-forward

Buffers traffic when no useful forwarder exists, then forwards after a later contact. This is essential for sparse or disrupted missions.

FANET routing protocol taxonomy with four categories: proactive or table-driven (DSDV, OLSR), reactive or on-demand (AODV, DSR), geographic or position-based (GPSR, GLSR), and hybrid (ZRP), each with trade-offs.
Figure 30.2: FANET routing protocols fall into four families - proactive, reactive, geographic, and hybrid - each trading control overhead against adaptability.

30.12 Temporary Inspection Corridor

Scenario: A small UAV team inspects a linear asset after a storm. The team must exchange telemetry, deliver high-priority alerts quickly, and upload inspection summaries when a ground gateway becomes reachable.

Design record:

  • Mission service: telemetry, safety alerts, low-rate image summaries, and delayed bulk upload.
  • Topology model: UAVs form a loose corridor with some same-layer links and one higher relay when available.
  • Routing mode: position-based forwarding for live telemetry, predictive forwarding for planned inspection passes, and store-carry-forward for segments with no reliable forwarder.
  • Gateway rule: prefer the gateway with fresh link records and enough remaining capacity for the current priority class.
  • Buffer rule: safety alerts are forwarded immediately when any suitable path exists; routine summaries can wait for a better gateway contact.
  • Decision record: neighbor freshness, chosen next hop, reason for buffering, gateway handoff record, and any delivery failure reason.

Result: The design does not promise one fixed route across the whole corridor. It uses the best current records for urgent traffic and accepts delayed delivery for lower priority data when the aerial path is temporarily partitioned.

30.13 Readiness Checklist

Use this checklist before accepting a FANET design:

30.13.1 Topology

  • Are position, altitude, and heading part of the route decision?
  • Is stale neighbor information detected?
  • Does the design account for sparse areas?

30.13.2 Routing

  • Is the selected routing mode matched to topology stability?
  • Is route discovery justified when used?
  • Is there a fallback when no forwarder is available?

30.13.3 Gateway

  • Is gateway selection tied to live records?
  • Does the design avoid a single fragile exit path?
  • Are handoffs recorded?

30.13.4 Operations

  • Are priority classes clear?
  • Does buffering respect mission urgency?
  • Are failure reasons visible after the mission?

30.14 Knowledge Check

Quiz: FANET Fundamentals

Label the Diagram

Code Challenge

30.15 Common Pitfalls

Flight plans are useful context, but they are not proof that a link will exist. A design still needs live neighbor and link checks.

Horizontal separation alone can hide the true 3D distance between UAVs. Include altitude when estimating whether a neighbor remains useful.

Old neighbor state can make a route look valid after the neighbor has moved away or become a poor forwarder. Record freshness and expire stale entries.

Aerial forwarding is only part of the system when data must leave the FANET. Track gateway reachability, handoff conditions, and delivery records.

Sparse FANETs may have temporary gaps. Low-priority but useful data can often be buffered and delivered later instead of being discarded immediately.

30.16 Concept Relationships

  • FANET extends ad hoc networking into UAV-based 3D movement.
  • 3D topology records keep neighbor and link decisions tied to current mission state.
  • Position-based routing uses current location and neighbor records for local next-hop choices.
  • Predictive routing adds movement expectations or planned contact windows.
  • Store-carry-forward protects useful data when no current forwarder exists.
  • Gateway selection connects the aerial path to ground or vehicle systems.

30.17 Further Reading

  • IETF MANET materials for ad hoc routing terminology and route-maintenance concepts.
  • Delay-tolerant networking literature for store-carry-forward behavior in intermittent networks.
  • Geographic routing literature, including GPSR-style greedy forwarding and perimeter recovery concepts.
  • UAV networking survey literature for aerial mobility, energy, and topology-management tradeoffs.
  • Aviation and mission operations guidance from the relevant operating authority for airspace, safety, and command responsibilities.

30.18 Summary

FANET fundamentals start with a simple idea: UAVs can form an ad hoc network in the air. The difficult part is keeping forwarding decisions tied to current 3D records. Useful designs describe the aerial link types, collect fresh topology and link state, choose routing behavior that matches the mission, buffer lower priority data during temporary partitions, and record gateway handoffs so the mission can be checked afterward.

30.19 What’s Next

30.20 Key Takeaway

FANETs are ad hoc networks in motion. Routing must account for changing 3D positions, link freshness, energy reserves, gateway reachability, and mission priority.