Automatic Generation of Communication Requirements for Enforcing Multi-Agent Safety
Eric S. Kim (University of California, Berkeley), Murat Arcak, (University of California, Berkeley), Sanjit A. Seshia (University of, California, Berkeley), BaekGyu Kim (Toyota InfoTechnology Center, U.S.A.),, Shinichi Shiraishi (Toyota InfoTechnology Center, U.S.A.)

TL;DR
This paper introduces a method to automatically generate communication requirements in multi-agent systems to ensure safety, reducing unnecessary communication by identifying when agents need to coordinate.
Contribution
It proposes a coordination-free controllable predecessor operator to determine when agents must communicate to maintain safety, enabling more efficient multi-agent control protocols.
Findings
Identifies when agents need to communicate for safety
Provides an upper bound on connection delays
Supports self-triggered coordination schemes
Abstract
Distributed controllers are often necessary for a multi-agent system to satisfy safety properties such as collision avoidance. Communication and coordination are key requirements in the implementation of a distributed control protocol, but maintaining an all-to-all communication topology is unreasonable and not always necessary. Given a safety objective and a controller implementation, we consider the problem of identifying when agents need to communicate with one another and coordinate their actions to satisfy the safety constraint. We define a coordination-free controllable predecessor operator that is used to derive a subset of the state space that allows agents to act independently, without consulting other agents to double check that the action is safe. Applications are shown for identifying an upper bound on connection delays and a self-triggered coordination scheme. Examples are…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
