Granted Patent B2

US 12,283,194 · App. 18/433,322 · Granted Apr 22, 2025

Inventors: Ali Reza Manouchehri (McLean, VA); Udaya Chundury (Aldie, VA); Vy Truong (Vienna, VA)

Assignee: MetroStar Systems LLC

G08G5/56B64U10/00G08G5/25G08G5/30H04L63/083H04L63/105B64U2101/20B64U2101/30

Abstract

Claims (87)

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.

2. The method of claim 1 , comprising

authorizing the drone; and

storing the transaction in a blockchain.

3. The method of claim 1 , comprising

initiating the time window since a last communication received from the drone;

determining the one or more communications were received within the time window; and

resetting the time window responsive to the one or more communications being received.

4. The method of claim 1 , comprising

initiating the time window since a last communication received from the drone;

determining the one or more communications were not received within the time window;

create a new transaction identifying the drone is offline; and

releasing the token assigned to the drone.

5. The method of claim 1 , comprising

identifying new content via the one or more communications;

creating a new transaction comprising the drone identifier, the role assigned to the drone, an updated mission status and the new content; and

storing the new transaction in a blockchain.

6. The method of claim 1 , comprising

identifying from the one or more communications the drone is active in a geographical area;

assigning one or more assignments to the drone based on the geographical area and the role assigned to the drone.

7. The method of claim 1 , comprising

identifying one or more additional drones;

assigning the drone to monitor an area for a period of time; and

assigning the one or more additional drones to monitor the area for another period of time when the period of time has expired.

8. An apparatus comprising:

a receiver configured to receive one or more communications transmitted from a drone, wherein the one or more communications comprise one or more heartbeat signals associated with another drone;

a processor configured to

determine the one or more communications identify a drone identifier of the drone and a drone identifier of the another drone;

determine whether the one or more communications were received within a time window;

assign a token to the identified drone indicating the drone is active and has a leader role;

assign 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 the token and the mission as a transaction in memory.

9. The apparatus of claim 8 , wherein the processor is further configured to

authorize the drone; and

store the transaction in a blockchain.

10. The apparatus of claim 8 , wherein the processor is further configured to

initiate the time window since a last communication received from the drone;

determine the one or more communications were received within the time window; and

reset the time window responsive to the one or more communications being received.

11. The apparatus of claim 8 , wherein the processor is further configured to

initiate the time window since a last communication received from the drone;

determine the one or more communications were not received within the time window;

create a new transaction identifying the drone is offline; and

release the token assigned to the drone.

12. The apparatus of claim 8 , wherein the processor is further configured to

identify new content via the one or more communications;

create a new transaction comprising the drone identifier, the role assigned to the drone, an updated mission status and the new content; and

store the new transaction in a blockchain.

13. The apparatus of claim 8 , wherein the processor is further configured to

identify from the one or more communications the drone is active in a geographical area; and

assign one or more assignments to the drone based on the geographical area and the role assigned to the drone.

14. The apparatus of claim 8 , wherein the processor is further configured to

identify one or more additional drones;

assign the drone to monitor an area for a period of time; and

assign the one or more additional drones to monitor the area for another period of time when the period of time has expired.

15. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:

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.

16. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

authorizing the drone; and

storing the transaction in a blockchain.

17. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

initiating the time window since a last communication received from the drone;

determining the one or more communications were received within the time window; and

resetting the time window responsive to the one or more communications being received.

18. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

initiating the time window since a last communication received from the drone;

determining the one or more communications were not received within the time window; and

create a new transaction identifying the drone is offline; and

releasing the token assigned to the drone.

19. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

identifying new content via the one or more communications;

creating a new transaction comprising the drone identifier, the role assigned to the drone, an updated mission status and the new content; and

storing the new transaction in a blockchain.

20. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

identifying from the one or more communications the drone is active in a geographical area;

assigning one or more assignments to the drone based on the geographical area and the role assigned to the drone.

Assignments (2)

Continuity (2)

References Cited (41)