IP Library › Granted Patent US 11,900,821
Granted Patent B2
US 11,900,821 · App. 17/684,088 · Granted Feb 13, 2024

Fleet controller

Inventors: Grant Mark Bristow (Benbrook, TX); Matthew David Holvey (North Richland Hills, TX); Naveed Ahmed Siddiqui (Dallas, TX)
Assignee: TEXTRON INNOVATIONS INC.
G08G5/0069G05D1/101G07C5/02G08G5/0013H04W24/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,900,821
App. No.
17/684,088
Granted
Feb 13, 2024
Kind
B2
Abstract

An method for controlling an autonomous vehicle fleet, including obtaining, by a fleet controller, from a master schedule, a mission for a vehicle of a fleet of autonomous vehicles, where the mission is associated with a mission entry of the master schedule, generating vehicle commands according to mission parameters associated with the mission, maintaining a persistent connection with the vehicle, sending the vehicle commands to the vehicle using the connection, the vehicle commands causing the vehicle to execute the mission under control of the fleet controller, and monitoring operation of the vehicle during performance of the mission.

Claims (54)

1. An autonomous vehicle fleet control method, comprising:

obtaining, by a fleet controller a mission for a vehicle of a fleet of autonomous vehicles;

identifying a flight path associated with the mission;

verifying a usability of the flight path with an unmanned aircraft system (UAS) traffic management (UTM);

modifying the flight path according to data from the UTM in response to the UTM indicating that the usability of the flight path is not verified; and

controlling the vehicle according to the flight path by sending, through a control arbitrator, vehicle commands associated with the flight path to the vehicle, the controlling the vehicle causing the vehicle to execute the mission, wherein the control arbitrator forwards the vehicle commands to the vehicle in response to the control arbitrator determining that the vehicle is being controlled by a single source of commands.

2. The method according to claim 1 , wherein the UTM performs checking on the flight path for requirements for use of the flight path, wherein the requirements for use of the flight path comprise at least one of weight, size, minimum or maximum altitude, or airspeed.

3. The method according to claim 1 , further comprising monitoring operation of the vehicle during execution of the mission by at least monitoring a connection of the vehicle to a communications network associated with the fleet controller.

4. The method according to claim 3 , wherein the monitoring the connection comprises receiving, by the fleet controller, from an access point that is of the communications network and that monitors a connection between the vehicle and the access point, a last vehicle status in response to the access point determining that the connection has been lost.

5. The method according to claim 4 , further comprising assigning another vehicle to the mission in response to a loss of the connection.

6. The method according to claim 3 , wherein the monitoring operation of the vehicle comprises determining, during performance of the mission, whether mission parameters associated with the mission are supported by mission impact data received at the fleet controller; and

wherein the method further comprises:

generating, in response to the mission parameters not being supported by the mission impact data, adjusted vehicle commands according to the mission impact data and the mission parameters; and

sending the adjusted vehicle commands through the control arbitrator to the vehicle using the connection, the adjusted vehicle commands causing the vehicle to execute the mission under control of the fleet controller according to the adjusted vehicle commands.

7. The method according to claim 6 , wherein the sending the adjusted vehicle commands to the vehicle comprises:

determining, by the control arbitrator, whether the vehicle is subject to single source control by ensuring that vehicle commands sent to the vehicle result in the vehicle being subject to a single point of control at any one time; and

send the adjusted vehicle commands to the vehicle in response the vehicle being subject to the single source control, and further in response to the control arbitrator determining that the adjusted vehicle commands have proper authority, the adjusted vehicle commands causing the vehicle to execute the mission under control of the fleet controller according to the adjusted vehicle commands.

8. An autonomous vehicle fleet control method, comprising:

controlling, by a fleet controller, a vehicle of a fleet of autonomous vehicles according to a flight path associated with a mission for the vehicle, the controlling the vehicle causing the vehicle to execute the mission according to mission performance requirements;

monitoring, by the fleet controller, operation of the vehicle during performance of the mission;

monitoring, by the fleet controller, mission parameters associated with the mission, wherein the monitoring the mission parameters comprises monitoring at least operation of the vehicle during performance of the mission and mission performance requirements;

receiving mission impact data comprising at least one of an event message or updated unmanned aircraft system (UAS) traffic management (UTM) data received during performance of the mission;

determining, according to the mission parameter and the mission impact data, whether vehicle operation adjustment is needed;

generating, in response to determining that the vehicle operation adjustment is needed, adjusted vehicle commands; and

controlling the vehicle according to the adjusted vehicle commands by sending, through a control arbitrator, the adjusted vehicle commands associated with the flight path to the vehicle, the controlling the vehicle, wherein the control arbitrator forwards the adjusted vehicle commands to the vehicle in response to the control arbitrator determining that the vehicle is being controlled by a single source of commands.

9. The method claim 8 , wherein the generating the adjusted vehicle commands comprises generating the adjusted vehicle commands according to the mission impact data.

10. The method of claim 9 , wherein the generating the adjusted vehicle commands comprises generating the adjusted vehicle commands according to the mission impact data and according to the mission performance requirements.

11. The method of claim 10 , further comprising performing, before the controlling the vehicle according to the flight path:

identifying the flight path associated with the mission;

verifying a usability of the flight path with a UTM, wherein the UTM performs checking on the flight path for traffic in the flight path, availability of the flight path due to flight restrictions and requirements for use of the flight path; and

modifying the flight path according to data from the UTM in response to the UTM indicating that the usability of the flight path is not verified.

12. The method according to claim 8 , wherein the monitoring the at least operation of the vehicle during performance of the mission and mission performance requirements comprises monitoring a connection between the vehicle and an access point; and

wherein the method further comprises assigning another vehicle to the mission in response to a loss of the connection.

13. The method according to claim 8 , wherein the controlling the vehicle according to the adjusted vehicle commands comprises determining whether the vehicle is subject to single source control, wherein the determining whether the vehicle is subject to single source control comprises ensuring that the vehicle is subject to a single point of control at any one time; and

forwarding the adjusted vehicle commands to the vehicle in response the vehicle being subject to the single source control.

14. A fleet controller, comprising:

a processor; and

a non-transitory computer-readable storage medium storing a program for controlling a fleet of autonomous vehicles to be executed by the processor, the program including instructions for:

obtaining a mission for a vehicle of the fleet of autonomous vehicles;

identifying a flight path associated with the mission;

verifying a usability of the flight path with an unmanned aircraft system (UAS) traffic management (UTM), wherein the UTM performs checking on the flight path for at least one of traffic in the flight path, availability of the flight path due to flight restrictions, or requirements for use of the flight path;

modifying the flight path according to data from the UTM in response to the UTM indicating that the usability of the flight path is not verified; and

controlling the vehicle according to the flight path by sending, through a control arbitrator, vehicle commands associated with the flight path to the vehicle, the controlling the vehicle causing the vehicle to execute the mission, wherein the control arbitrator forwards the vehicle commands to the vehicle in response to the control arbitrator determining that the vehicle is being controlled by a single source of commands.

15. The fleet controller according to claim 14 , wherein the UTM performs checking on the flight path for requirements for use of the flight path, wherein the requirements for use of the flight path comprise at least one of weight, size, minimum or maximum altitude, or airspeed.

16. The fleet controller according to claim 14 , wherein the program further includes instructions for monitoring operation of the vehicle during execution of the mission by at least monitoring a connection of the vehicle to a communications network associated with the fleet controller.

17. The fleet controller according to claim 16 , wherein the monitoring the connection comprises receiving, from an access point that is of the communications network and that monitors a connection between the vehicle and the access point, a last vehicle status in response to the access point determining that the connection has been lost.

18. The fleet controller according to claim 17 , wherein the program further includes instructions for assigning another vehicle to the mission in response to a loss of the connection.

19. The fleet controller according to claim 16 , wherein instructions for monitoring the operation of the vehicle include instructions for determining, during performance of the mission, whether mission parameters associated with the mission are supported by mission impact data received at the fleet controller; and

wherein the program further includes instructions for:

generating, in response to the mission parameters not being supported by the mission impact data, adjusted vehicle commands according to the mission impact data and the mission parameters; and

sending the adjusted vehicle commands though the control arbitrator to the vehicle using the connection, the adjusted vehicle commands causing the vehicle to execute the mission under control of the fleet controller according to the adjusted vehicle command.

20. The fleet controller according to claim 19 , wherein the instructions for sending the adjusted vehicle commands to the vehicle include instructions for:

determining, by the control arbitrator, whether the vehicle is subject to single source control, wherein the determining whether the vehicle is subject to single source control comprises by ensuring that vehicle commands sent to the vehicle result in the vehicle being subject to a single point of control at any one time; and

sending the adjusted vehicle commands to the vehicle in response the vehicle being subject to the single source control, and further in response to the control arbitrator determining that the adjusted vehicle commands have proper authority.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2022
From: BELL TEXTRON INC.
To: BELL TEXTRON RHODE ISLAND INC.
Reel/Frame 060231/0336 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2022
From: BELL TEXTRON RHODE ISLAND INC.
To: TEXTRON INNOVATIONS INC.
Reel/Frame 060231/0373 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2022
From: BRISTOW, GRANT MARK; HOLVEY, MATTHEW DAVID; SIDDIQUI, NAVEED AHMED
To: BELL TEXTRON INC.
Reel/Frame 060517/0546 →
Continuity (2)
Continuation 16720543 · Dec 19, 2019
Related Publication 20220238030A1 · Jul 28, 2022
Cited By (1)
US 12,300,111