Emerging Paradigms · Study deck

UAV Network Topologies

A group of aircraft maps the edge of a wildfire.

Blueprint Bina is your guide for this deck.

topologies
Blueprint Bina, the module guide, in a scene from this chapter.
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Compare star, mesh, hierarchical, relay-chain, and store-carry-forward UAV topology patterns.
  • Separate physical topology from logical routing behavior.
  • Choose a topology using mission role, traffic class, link freshness, gateway reachability, energy reserve, and payload behavior.
  • Identify when a topology has hidden single points of failure.
iotclass.org

Major section

Start Simple

The lead operator needs urgent status now, while large images can wait.

  • One aircraft can speak directly to the ground station, another needs a relay, and a third may carry data until it returns.
  • Calling the group a mesh does not prove that each mission need has a safe path.
  • No single shape is best for every flight or traffic type.
  • The proof is limited to the tested mission, motion, and equipment.

Key terms

No single shape
No single shape is best for every flight or traffic type.
iotclass.org

Major section

In 60 Seconds

UAV topology is the communication shape that connects aircraft, field devices, operators, relays, and gateway exits during a mission.

  • Star topology is simple but depends on a hub.
  • Mesh topology gives alternate paths but needs current neighbor and route records.
iotclass.org

Major section

Checkpoint: Minimum Viable Understanding

A topology decision is a mission decision, not just a diagram shape.

  • Star topology is easiest to supervise, but the hub and ground link must be checked as dependencies.
  • Mesh topology can reroute around some failures, but only when alternate physical links really exist.
iotclass.org

Major section

How This Chapter Fits

The introduction and features chapters explain why UAV networks are useful.

  • This chapter focuses on the communication shape that lets those roles work together.
  • Later FANET, gateway, coordination, and production chapters use this topology vocabulary when they evaluate routes, gateway exits, and fallback behavior.
  • The overview depth layer shows the topology decision map that anchors mission service, traffic classes, link records, gateway exit, role records, payload behavior, rejected pattern, and fallback rule.
UAV topology decision map showing mission service, traffic classes, link records, gateway exit, role records, payload behavior, rejected pattern, and fallback rule feeding topology choice.
UAV topology decision map showing mission service, traffic classes, link records, gateway exit, role records, payload behavior, rejected pattern, and fallback rule feeding topology choice.
iotclass.org

Major section

Topology Patterns

Aircraft exchange state with peers and can route through more than one path.

  • Best fit: missions where individual UAVs may lose contact but nearby peers can still help.
  • Best fit: missions where sensing, relaying, gateway exit, and supervision should not all sit on the same aircraft.
  • Best fit: long or narrow mission areas where direct ground contact is unreliable.
UAV topology pattern comparison showing star, mesh, hierarchical relay, and store-carry-forward patterns with their main dependency and fallback question.
UAV topology pattern comparison showing star, mesh, hierarchical relay, and store-carry-forward patterns with their main dependency and fallback question.
iotclass.org

Major section

Topology Decision Record

The decision record should be short enough to keep current during a mission.

  • It should still be detailed enough that another teammate can see why one topology was accepted and another was rejected.
UAV topology decision record showing mission service, selected topology, rejected topology, traffic classes, physical links, gateway exit, energy reserve, payload behavior, fallback action, and recheck trigger.
UAV topology decision record showing mission service, selected topology, rejected topology, traffic classes, physical links, gateway exit, energy reserve, payload behavior, fallback action, and recheck trigger.

The decision record should be short enough to keep current during a mission. It should still be detailed enough that another teammate can see why one topology was accepted and another was rejected.

iotclass.org

Major section

Worked Example: Utility Corridor Inspection

Scenario: A field crew wants UAV support for a utility corridor after a storm.

  • The mission needs current status notes for crews and can tolerate delayed upload for high-resolution imagery.
  • Every UAV reports directly to the ground station.
  • The result is not "mesh is better than star." The result is a documented topology split: current status gets a relay path; bulk imagery gets store-carry-forward; supervision stays centralized.
iotclass.org

Major section

1. Assuming Mesh Always Wins

Mesh can improve resilience only when alternate physical links exist and the routing state is fresh.

  • In a narrow corridor, a mesh protocol may still behave like a relay chain.

Mesh can improve resilience only when alternate physical links exist and the routing state is fresh. In a narrow corridor, a mesh protocol may still behave like a relay chain.

iotclass.org

Major section

UAV Networks for IoT

Its camera sees one blocked drain, and the ground team must decide whether to send a person there.

  • The first question is not how modern the aircraft looks.
  • A gateway means a device or service that joins two message paths.
  • A payload means the useful reading, image, or command carried inside a message.
Three UAV roles in IoT: mobile sensor for data collection, aerial relay for network extension, and flying actuator for physical actions, each with use cases and payloads.
Three UAV roles in IoT: mobile sensor for data collection, aerial relay for network extension, and flying actuator for physical actions, each with use cases and payloads.
iotclass.org

Major section

UAV Networks for IoT (continued)

Fly beyond one link, delay a reading, repeat it, restart the ground receiver, and reject an old position as current.

  • This runway does not prove airworthiness, radio coverage, or mission safety.
  • The deeper sections explain aircraft roles, moving links, energy limits, network patterns, and the evidence needed for a real flight decision.
  • A UAV can collect observations, provide temporary access, relay traffic, or bridge a mission area to a ground gateway.
iotclass.org

Deck summary

Key takeaways

The lead operator needs urgent status now, while large images can wait.

  • UAV topology is the communication shape that connects aircraft, field devices, operators, relays, and gateway exits during a mission.
  • A topology decision is a mission decision, not just a diagram shape.
  • The introduction and features chapters explain why UAV networks are useful.
  • Aircraft exchange state with peers and can route through more than one path.
iotclass.org

Retrieval practice

Recall check 1 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q1A corridor mission uses a relay UAV for urgent status and buffers high-resolution imagery. The relay's battery reserve falls below the return threshold while gateway freshness is also stale. Which topology action is most defensible?

AKeep sending all traffic through the same relay because the preflight diagram selected that topology.
BTrigger the recorded role replacement for urgent status and buffer delay-tolerant imagery.
CSwitch every aircraft to bulk imagery upload first, because imagery files are the largest payload.
DDeclare the fleet fully meshed because each UAV still runs mesh-capable routing software.
Show answer

Answer: B The topology record separates fresh traffic from delay-tolerant payloads and names the fallback when relay and gateway records degrade; affected imagery segments are marked as pending until a fresh gateway path exists.

iotclass.org

Retrieval practice

Recall check 2 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q2A corridor inspection mission needs urgent status messages during flight and high-resolution imagery after contact improves. Which first topology record keeps the choice traceable?

AUse mesh for every flow because the routing software supports mesh and mesh is more resilient than star topology.
BApprove the preflight topology diagram because one relay delivered a status packet during a short hover test.
CChoose star topology for commands, telemetry, imagery, and fallback paths alike, because a single ground station hub is easiest to supervise.
DName the mission service, traffic classes, selected topology for each class, rejected topology, and physical link evidence.
Show answer

Answer: D A traceable UAV topology decision separates traffic classes, selected and rejected topology patterns, physical link evidence, gateway exit, energy and payload constraints, fallback behavior, ownership, and recheck triggers before the mission depends on the path.

iotclass.org

Retrieval practice

Recall check 3 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q3A UAV route covers a long corridor. The routing software supports mesh, but each aircraft can currently hear only the aircraft immediately before and after it. What should the topology check conclude?

ATreat the mission as fully meshed, because mesh-capable routing software will discover alternate paths whenever they are needed
BTreat the chain as robust because interior aircraft each have two neighbors, allowing forwarding in either direction along the corridor
CChoose a star around the ground station to simplify supervision and remove the relay-chain maintenance burden
DTreat the physical topology as a relay chain and identify the chain positions that would break the path if lost
Show answer

Answer: D Topology checks should distinguish logical routing support from physical reachability.

iotclass.org

Retrieval practice

Recall check 4 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q4Why might a UAV mission use star supervision for commands but store-carry-forward for imagery?

ABecause a later high-rate contact can upload imagery with less transmission time
BBecause star topology physically cannot carry sensor payloads such as imagery over its hub links
CBecause sending images would interfere with command packets on the star's shared links
DCommands need current oversight, while high-volume imagery may tolerate delayed upload
Show answer

Answer: D A good topology design separates traffic classes.

iotclass.org

Retrieval practice

Recall check 5 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q5A UAV can collect road-inspection images but loses the live gateway link near the far end of the route. Which readiness record is most useful?

AA single-path rule that sends every message the same way to keep mission handling uniform.
BA note that the operations dashboard already renders images, proving the gateway link is sufficient.
CA fallback record that separates urgent status from delay-tolerant image batches.
DA fleet-size estimate showing that two extra aircraft would restore continuous gateway coverage.
Show answer

Answer: C A mission readiness record distinguishes traffic urgency and fallback paths before topology or fleet sizing.

iotclass.org

Retrieval practice

Recall check 6 of 6

Blueprint Bina says: answer from memory, then check your reasoning.

Q6Why is a stale FANET route dangerous for urgent UAV mission traffic?

ABecause longer air links consume more power as the radio works harder to bridge distance.
BBecause buffered imagery can use airtime even when route entries are fresh.
CBecause moving UAVs can invalidate a once-valid path before urgent delivery.
DBecause a ground exit is never needed when UAVs have peer connectivity.
Show answer

Answer: C FANET design depends on link freshness, traffic class, and gateway evidence, not just a topology diagram.

iotclass.org

Print reference

Answers 1 of 2

Answer key.

  1. B · The topology record separates fresh traffic from delay-tolerant payloads and names the fallback when relay and gateway records degrade; affected imagery segments are marked as pending until a fresh gateway path exists.
  2. D · A traceable UAV topology decision separates traffic classes, selected and rejected topology patterns, physical link evidence, gateway exit, energy and payload constraints, fallback behavior, ownership, and recheck triggers before the mission depends on the path.
  3. D · Topology checks should distinguish logical routing support from physical reachability.
iotclass.org

Print reference

Answers 2 of 2

Answer key.

  1. D · A good topology design separates traffic classes.
  2. C · A mission readiness record distinguishes traffic urgency and fallback paths before topology or fleet sizing.
  3. C · FANET design depends on link freshness, traffic class, and gateway evidence, not just a topology diagram.
iotclass.org