US 12,283,194 B2
Drone to drone communication and task assignment
Ali Reza Manouchehri, McLean, VA (US); Udaya Chundury, Aldie, VA (US); and Vy Truong, Vienna, VA (US)
Assigned to MetroStar Systems LLC, Reston, VA (US)
Filed by MetroStar Systems LLC, Reston, VA (US)
Filed on Feb. 5, 2024, as Appl. No. 18/433,322.
Application 18/433,322 is a continuation of application No. 18/206,755, filed on Jun. 7, 2023, granted, now 12,014,640.
Prior Publication US 2024/0412648 A1, Dec. 12, 2024
Int. Cl. G08G 5/00 (2006.01); B64U 10/00 (2023.01); G08G 5/25 (2025.01); G08G 5/30 (2025.01); G08G 5/56 (2025.01); H04L 9/40 (2022.01); B64U 101/20 (2023.01); B64U 101/30 (2023.01)
CPC G08G 5/56 (2025.01) [B64U 10/00 (2023.01); G08G 5/25 (2025.01); G08G 5/30 (2025.01); H04L 63/083 (2013.01); H04L 63/105 (2013.01); B64U 2101/20 (2023.01); B64U 2101/30 (2023.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, at a server, one or more communications transmitted from a drone to the server, wherein the one or more communications comprise one or more heartbeat signals associated with another drone;
determining, via the server, the one or more communications identify a drone identifier of the drone and a drone identifier of the another drone;
determining, via the server, whether the one or more communications were received within a time window;
assigning, via the server, a token to the identified drone indicating the drone is active and has a leader role;
assigning, via the server, a mission with one or more requirements to the drone responsive to the token being assigned, and wherein the drone initiates one or more flying actions based on the one or more requirements; and
storing, via the server, the token and the mission as a transaction in memory.