← Latest papers
⚡ electrical engineering

Resource Allocation with Multi-Team Collaboration Based on Hamilton's Rule

This paper proposes a multi-team collaboration framework for resource allocation based on Hamilton's rule, where teams bid for shared agents by weighing transfer costs, benefits, and mission importance, and validates the approach through simulations in a coverage control mission.

Original authors: Riwa Karam, Ruoyu Lin, Brooks A. Butler, Magnus Egerstedt

Published 2026-03-25
📖 5 min read🧠 Deep dive

Original authors: Riwa Karam, Ruoyu Lin, Brooks A. Butler, Magnus Egerstedt

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are the manager of a large construction company. You have four different construction crews (Teams 1, 2, 3, and 4) working on four different buildings across the city. You also have a limited pool of 16 specialized workers (robots) that can be moved between these crews.

Your goal is to get all four buildings finished as well as possible. But here's the tricky part:

  • Team 1 is building a skyscraper in a very dense, complex area. They need more workers to do a good job.
  • Team 2 is building a small shed in an open field. They don't need as many workers; adding more would just get in their way.
  • Team 3 has a high-priority contract (maybe it's a hospital), so their work matters more than the others.
  • Team 4 has a low-priority contract.

The Problem: If you just leave the workers where they started, you might end up with Team 1 struggling with too few people while Team 2 has workers standing around doing nothing. You need a smart way to move workers from "less important" or "overstaffed" teams to "more important" or "understaffed" teams.

The "Altruistic" Solution: Hamilton's Rule

This paper introduces a clever way to decide who gives up a worker and who gets a new one. They borrow an idea from nature called Hamilton's Rule.

In nature, this rule explains why a squirrel might risk its life to warn its family of a predator. It works like this:

If the benefit to the family (weighted by how related they are) is greater than the cost to the squirrel, the squirrel should take the risk.

The authors apply this to robots:

  • The "Relatedness": Instead of family ties, they use Mission Importance. If Team 3 is building a hospital, they are "more related" to the company's success than Team 4 building a shed.
  • The "Benefit" (B): How much better Team 3 will do if they get one extra robot.
  • The "Cost" (C): How much worse Team 4 will do if they lose one robot.

The Rule: A robot should only move from Team A to Team B if:

(Importance of Team B) × (How much Team B improves) > (Importance of Team A) × (How much Team A suffers)

The "Bidding War" Analogy

Since there are multiple teams, they can't just look at one pair at a time. The paper describes a Bidding Process:

  1. The Pitch: Every team looks at its neighbors. "Hey Team 3, if I give you a robot, how much better will you do?" and "Team 3, if I take a robot from you, how much will I suffer?"
  2. The Calculation: They calculate a "Net Gain Score."
    • Example: If Team 3 (High Priority) gets a robot, their score jumps up a lot. If Team 4 (Low Priority) loses one, their score drops only a little. The "Net Gain" is huge.
    • Counter-Example: If Team 4 (Low Priority) gets a robot, the gain is small. If Team 1 (High Priority) loses one, the drop is huge. The "Net Gain" is negative.
  3. The Decision: Teams only accept a trade if the Net Gain is positive. They pick the neighbor that offers the biggest positive gain.

The "Diminishing Returns" Concept

The paper also relies on a simple economic truth: Diminishing Returns.

Imagine Team 1 has 1 robot. Adding a 2nd robot helps a lot (maybe they can cover twice the area). Adding a 3rd helps, but not quite as much. Adding a 10th robot might not help at all because they are just stepping on each other's toes.

The algorithm uses this to balance things out. It stops moving robots when adding one more to a team doesn't help enough to justify taking one away from another team.

The Real-World Test: Covering a Map

To prove this works, the authors simulated a "Coverage" mission. Imagine four teams of robots trying to cover different parts of a map with sensors.

  • Some areas are "dense" (lots of important stuff to watch).
  • Some areas are "sparse."
  • Some teams have higher priority.

The Result:
The robots automatically shuffled themselves.

  • Teams with high-priority, dense areas ended up with more robots.
  • Teams with low-priority, sparse areas ended up with fewer robots.
  • The system kept shuffling until it reached the "perfect" balance where the total performance of the whole company was maximized.

Why This Matters

In the past, if you had multiple robot teams, you might have had to manually tell them to swap workers, or they might have acted selfishly (keeping all their robots even if they didn't need them).

This paper gives the robots a "moral compass" based on math. It allows them to be altruistic: "I will give up my robot because it helps the bigger picture more than it hurts me." This ensures that in emergencies (like search and rescue or disaster response), resources flow exactly where they are needed most, automatically and efficiently.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →