IP Library Granted Patent US 9,368,026
Granted Patent B1
US 9,368,026 · App. 14/721,604 · Granted Jun 14, 2016

Fallback requests for autonomous vehicles

Inventors: Joshua Seth Herbach (San Francisco, CA); Philip Nemec (San Jose, CA); Nathaniel Fairfield (Mountain View, CA)
Assignee: Google Inc.
G08G1/00G06F9/4881G06F9/546
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 9,368,026
App. No.
14/721,604
Granted
Jun 14, 2016
Kind
B1
Abstract

Aspects of the present disclosure relate to a system having a memory, a plurality of self-driving systems for controlling a vehicle, and one or more processors. The processors are configured to receive at least one fallback task in association with a request for a primary task and at least one trigger of each fallback task. Each trigger is a set of conditions that, when satisfied, indicate when a vehicle requires attention for proper operation. The processors are also configured to send instructions to the self-driving systems to execute the primary task and receive status updates from the self-driving systems. The processors are configured to determine that a set of conditions of a trigger is satisfied based on the status updates and send further instructions based on the associated fallback task to the self-driving systems.

Claims (54)

1. A system comprising:

a memory;

one or more self-driving systems for controlling a vehicle; and

one or more processors configured to:

receive at least one fallback task in association with a request for a primary task and at least one trigger of each fallback task, each trigger being a set of conditions that, when satisfied, indicate when a vehicle requires attention for proper operation;

send a first set of instructions to the one or more self-driving systems to execute the primary task;

receive status updates from the self-driving systems;

determine that a set of conditions of a trigger is satisfied based at least in part on the status updates; and

send a second set of instructions to one or more self-driving systems based on the fallback task associated with the trigger.

2. The system of claim 1 , wherein each set of conditions is different for each trigger; and

wherein the one or more processors are further configured to determine that a set of conditions of a trigger has been satisfied.

3. The system of claim 1 , wherein

a base location is hardcoded on the memory;

the one or more processors are further configured to determine that the fallback task associated with the trigger is non-executable; and

update the fallback task to be driving to the base location.

4. The system of claim 1 , wherein the one or more processors are further configured to:

send a status update report based on the status update from the self-driving systems;

receive at least one updated fallback task; and

store the at least one updated fallback task in the memory.

5. The system of claim 4 , wherein the one or more processors are further configured to update at least one fallback task based on the at least one updated fallback task.

6. The system of claim 1 , wherein the one or more processors are further configured to:

determine that the set of conditions of the trigger are no longer satisfied; and

when one or more conditions of the trigger are determined to no longer be satisfied, send a third set of instructions to one or more self-driving systems to autonomously resume the primary task.

7. The system of claim 1 , wherein the one or more processors are further configured to:

determine a level of urgency of the trigger, the level of urgency being related to how quickly the fallback task associated with the trigger is executed after the set of conditions of the trigger is satisfied; and

send the second set of instructions before the primary task is completed when the level of urgency of the trigger is a certain level.

8. The system of claim 1 , wherein the second set of instructions includes instructions that cause the self-driving systems to stop executing the primary task.

9. The system of claim 1 , wherein the one or more processors are further configured to determine which fallback task is associated with the trigger by accessing a mapping of each trigger to corresponding fallback tasks.

10. The system of claim 1 , further comprising the vehicle.

11. The system of claim 10 , wherein the vehicle will not start if a base location is not stored on the memory.

12. A fleet management system comprising a server configured to:

receive updates regarding the status of a plurality of vehicles capable of autonomously driving; and

send a dispatch command to one of the vehicles, the dispatch command including a request for a primary task, at least one fallback task, and at least one trigger of each fallback task, each trigger being a set of conditions that, when satisfied, indicate when a vehicle requires attention for proper operation;

wherein the dispatch command further includes a level of urgency for each trigger, the level of urgency being related to how quickly the fallback task associated with the trigger is executed after the set of conditions of the trigger is satisfied.

13. The system of claim 12 , wherein the server is further configured to send at least one updated fallback task in response to the received updates.

14. The system of claim 12 , wherein the server is further configured to determine one or more fallback locations that one of the vehicles may drive to when executing at least one fallback task; and

wherein the dispatch command further includes the one or more fallback locations.

15. The system of claim 12 , further comprising the plurality of vehicles capable of autonomously driving.

16. A system comprising:

a plurality of self-driving systems for controlling a vehicle;

one or more processors; and

a memory comprising:

a trip manager module comprising instructions that, when executed, cause the one or more processors to:

send a first set of instructions to one or more self-driving systems to execute a primary task, and

send a second set of instructions to one or more self-driving systems to execute a fallback task associated with a trigger, the trigger being a set of conditions that, when satisfied, indicate when a vehicle requires attention for proper operation; and

a task overseer module comprising instructions that, when executed, cause the one or more processors to:

receive vehicle status updates from the trip manager module,

determine that the set of conditions of a trigger is satisfied based on a current vehicle status received from the trip manager module, and

send information to the trip manager module based on the fallback task associated with the set of conditions of the trigger that is satisfied.

17. The system of claim 16 , wherein

the task overseer module further comprises instructions that, when executed, cause the one or more processors to determine a level of urgency of the trigger, the level of urgency being related to how quickly the fallback task associated with the trigger is executed after the set of conditions of the trigger is satisfied, wherein the indication includes the level of urgency; and

the trip manager module further comprises instructions that, when executed, cause the one or more processors to send the second set of instructions with instructions to stop executing the primary task.

18. The system of claim 16 , wherein the task overseer module further comprises instructions that, when executed, cause the one or more processors to determine which fallback task is associated with the trigger by accessing a mapping of each trigger to corresponding fallback tasks.

19. The system of claim 16 , further comprising the vehicle.

Assignments (6)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE REMOVAL OF THE INCORRECTLY RECORDED APPLICATION NUMBERS 14/149802 AND 15/419313 PREVIOUSLY RECORDED AT REEL: 44144 FRAME: 1. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME. Recorded Mar 4, 2024
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 068092/0502 →
SUBMISSION TO CORRECT AN ERROR MADE IN A PREVIOUSLY RECORDED DOCUMENT THAT ERRONEOUSLY AFFECTS THE IDENTIFIED APPLICATIONS Recorded Nov 11, 2019
From: WAYMO LLC
To: WAYMO LLC
Reel/Frame 050978/0359 →
CHANGE OF NAME Recorded Oct 6, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044144/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 28, 2017
From: WAYMO HOLDING INC.
To: WAYMO LLC
Reel/Frame 042108/0021 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 27, 2017
From: GOOGLE INC.
To: WAYMO HOLDING INC.
Reel/Frame 042099/0935 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2015
From: HERBACH, JOSHUA SETH; NEMEC, PHILIP; FAIRFIELD, NATHANIEL
To: GOOGLE INC.
Reel/Frame 035851/0730 →