← All Modules|Mobile Robotics

4 Multi-Robot Systems: Taxonomy, Estimation, and Coordination

robotics
coordination
physical-world

4.1 Overview: A Team Adds Information Paths, Not Just Robots

Robot teams, swarms, and robot networks address problems whose work or geography is distributed. A team can cover more space, divide roles, continue after one unit fails, and sometimes produce performance greater than isolated individual efforts. The source lecture grounds that motivation in search and rescue, surveillance or monitoring, and product pickup or delivery.

More robots also add coupling. An estimate made on one robot can influence another robot’s estimate, a delayed message can arrive after the state it describes, and a coordinator can become a single point of failure. Multi-robot design therefore begins with taxonomy, not with a fleet-size target.

4.1.1 Three Independent Taxonomy Axes

Architecture

Centralized systems route estimation or control through one unit. Decentralized systems distribute those decisions across robots.

Communication

Explicit communication sends state that teammates cannot directly observe. Implicit communication occurs when robots infer information from observable motion or environment changes.

Heterogeneity

Homogeneous teams share capabilities. Heterogeneous teams deliberately combine complementary sensors, mobility, payload, or compute.

These axes are independent. A heterogeneous team can still be centrally controlled. A decentralized team can use explicit radio messages. A homogeneous swarm can coordinate partly through observable motion.

4.1.2 Topology Shapes Coordination Risk

Fully Connected

Every robot exchanges information with every other robot. Information paths are short, but message count and dependency management grow quickly.

Star

All robots communicate through a central node. Coordination is simple to inspect, but the center and its links become critical dependencies.

Random Mesh

Each robot communicates with a changing neighborhood. The topology tolerates some failures but makes connectivity and convergence time-dependent.

The goal of decentralization is to approach the performance of an ideal centralized system without inheriting its single point of failure. The costs are communication delay and overhead, asynchronous inputs, and solutions that may be temporarily sub-optimal. Some algorithms degrade gracefully under whatever communication is available, but that property must be demonstrated for the chosen algorithm and topology; it is not automatic.

4.2 Practitioner: Share Relative Observations Without Counting Them Twice

Distributed estimation asks each robot to estimate a local or global variable from incomplete evidence. Kalman filters and particle filters can be distributed by fusing relative observations of teammates with communicated position beliefs.

Collaborative localization provides the concrete workflow:

1. Observe

Robot 1 measures relative range and bearing to Robot 2.

2. Exchange

Robot 2 communicates its position estimate and uncertainty.

3. Transform

Robot 1 maps the relative observation into its local frame.

4. Fuse

The filter updates weights or state while preserving dependency history.

In a particle-filter version, the detected robot reweights its particles using the detecting robot’s belief and the relative measurement, then resamples from the new weights. A Kalman-filter version can perform the same conceptual fusion when its model assumptions fit.

Rumor-propagation warning: a relative observation is not independent merely because it arrived in a new message. If Robot 1's estimate influenced Robot 2, and Robot 2 later sends that estimate back as if it were fresh independent evidence, the same information is counted again. Confidence grows without new evidence. Correct distributed fusion tracks dependency or information history instead of treating every received estimate as independent.

Log at least the observation timestamp, source robot, frame transform, source-estimate version, covariance or particle-belief summary, and dependency identifier. Without lineage, a filter cannot distinguish a new measurement from recycled information.

4.2.1 Choose the Coordination Problem Before the Algorithm

Multi-robot coordination is several problem families, not one:

Problem familyGoalMechanisms named in the source
Coordinated motionmove as a formation or flocklocal potential fields, graph/network control, leader-follower
Allocationdistribute roles or resourcesmarket-based and threshold-based algorithms
Coveragespread robots over a spatial areaLloyd’s algorithm and gradient-based coverage control
Agreementmake local states convergeconsensus over neighbor interactions

Do not choose consensus for a problem that is actually allocation, or use flocking rules where a coverage guarantee is required. First name the variable to coordinate: pose, velocity, role, resource, territory, estimate, or clock.

4.3 Under the Hood: Neighbor Rules Become Team-Level Behavior

Graph control abstracts the communication network as nodes and edges. Robot ii has a neighbor set Ni\mathcal{N}_i determined by the current topology or a proximity rule. The controller then uses local states from that set rather than assuming global access.

4.3.1 Flocking: Three Local Steering Rules

Reynolds’ boids model (1987) produces flock-level motion from three local rules:

Separation

Steer away from nearby neighbors to prevent crowding or collision.

Alignment

Steer toward the average heading or velocity of neighbors.

Cohesion

Steer toward the local center of neighboring positions so the group remains together.

Each robot reacts only to neighbors within a region of influence defined by distance and angle. Team behavior changes when that neighborhood graph disconnects, when sensing is asymmetric, or when delay makes neighbor velocity stale. The rule names do not guarantee collision freedom; gains, limits, update timing, and geometry still matter.

4.3.2 Consensus: State the Local Update Contract

The lecture closes with the general consensus update associated with Olfati-Saber, Fax, and Murray (2007):

$$x_i[t+1]=f\left(x_i[t],\{x_j[t]\mid j\in\mathcal{N}_i\}\right).$$

The function ff is often an averaging rule. Robot ii updates from its current value and the values available from its neighbors. The intended outcome is decentralized agreement: all robots converge to the same value through local interactions. Motion coordination, cooperative estimation, and synchronization all fit this form once xix_i is chosen appropriately.

For a simple weighted average:

xi[t+1]=wiixi[t]+jNiwijxj[t],x_i[t+1]=w_{ii}x_i[t]+\sum_{j\in\mathcal{N}_i}w_{ij}x_j[t],

with non-negative weights summing to one. The update stays within the local convex hull of received values. Convergence claims still depend on the graph and update assumptions: the network must retain enough connectivity, weights must be well formed, and delays, packet loss, or adversarial values cannot be ignored.

4.3.3 Worked Agreement Trace

Three robots start with scalar values 00, 66, and 1212. On a fully connected graph, let every robot replace its value with the average of all three values:

xˉ=0+6+123=6.\bar{x}=\frac{0+6+12}{3}=6.

All three reach 66 in one update because every node sees the whole graph and uses identical weights. On a line graph, end robots see only the center and agreement takes multiple updates. On a disconnected graph, separate components can converge internally to different values; local agreement is not global agreement.

The source lecture states exponential-rate convergence as the consensus outcome. Treat that as a property of a qualifying algorithm under its stated graph and timing assumptions, not as a promise attached to any function named consensus.

4.4 Summary

  • Multi-robot architecture, communication mode, and heterogeneity are independent taxonomy axes.
  • Decentralization removes one central failure point but introduces asynchronous information, delay, overhead, and temporary sub-optimality.
  • Collaborative localization fuses relative range or bearing with communicated beliefs, while preserving measurement dependency history.
  • Coordinated motion, task allocation, coverage, flocking, and consensus solve different coordination variables.
  • Consensus turns local-neighbor updates into agreement only when topology, weighting, timing, and integrity assumptions support convergence.

4.5 Key Takeaway

A robot team is an information system with actuators. State who can observe whom, which evidence has already been fused, how the neighbor graph changes, and which assumption makes the team-level behavior emerge from local updates.

4.6 See Also