IP Library Granted Patent US 12,372,971
Granted Patent B2
US 12,372,971 · App. 18/766,734 · Granted Jul 29, 2025

Exception handling for autonomous vehicles

Inventors: Dong Li (Los Gatos, CA); Matthew McNaughton (Mountain View, CA); Shir Yehoshua (San Francisco, CA); Aida Khosroshahi (San Jose, CA); Ioan-Alexandru Sucan (East Palo Alto, CA)
Assignee: Waymo LLC
G05D1/0289G05D1/0088G05D1/0223G05D1/65G05D1/693G05D1/81
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 12,372,971
App. No.
18/766,734
Granted
Jul 29, 2025
Kind
B2
Abstract

Aspects of the technology relate to exception handling for a vehicle. For instance, a current trajectory for the vehicle and sensor data corresponding to one or more objects may be received. Based on the received sensor data, projected trajectories of the one or more objects may be determined. Potential collisions with the one or more objects may be determined based on the projected trajectories and the current trajectory. One of the potential collisions that is earliest in time may be identified. Based on the one of the potential collisions, a safety-time-horizon (STH) may be identified. When a runtime exception occurs, before performing a precautionary maneuver to avoid a collision, waiting no longer than the STH for the runtime exception to resolve.

Claims (28)

1. A method comprising:

receiving, by one or more processors, sensor data corresponding to an object in an environment of a vehicle;

determining, by the one or more processors, a point in time for avoiding a potential collision with the object;

determining, by the one or more processors, an exception handling speed profile; and

when the point in time has passed and a runtime exception is unresolved, controlling, by the one or more processors, the vehicle according to the exception handling speed profile to avoid the potential collision with the object.

2. The method of claim 1 , wherein the runtime exception relates to a processing delay.

3. The method of claim 1 , wherein the runtime exception relates to a communication delay.

4. The method of claim 1 , wherein the runtime exception relates to missing sensor data generated by a perception system of the vehicle.

5. The method of claim 1 , wherein the runtime exception relates to a lost connection with a remote computing device.

6. The method of claim 1 , wherein the exception handling speed profile is determined based on a characteristic of the runtime exception.

7. The method of claim 6 , wherein the characteristic includes a priority of the runtime exception such that the higher the priority, the greater a rate of deceleration of the exception handling speed profile, and the lower the priority, the lower a rate of deceleration of the exception handling speed profile.

8. The method of claim 1 , wherein the exception handling speed profile includes a constant deceleration over time.

9. The method of claim 1 , wherein the exception handling speed profile includes one or more changes in deceleration over time.

10. The method of claim 1 , wherein the point in time is determined based on an earliest in time potential collision with the object.

11. A system comprising one or more processors configured to:

receive sensor data corresponding to an object in an environment of a vehicle;

determine a point in time based on a potential collision with the object;

in response to a runtime exception, determine an exception handling speed profile; and

when the point in time has passed and a runtime exception is unresolved, control the vehicle according to the exception handling speed profile to avoid the potential collision with the object.

12. The system of claim 11 , further comprising the vehicle.

13. The system of claim 11 , wherein the runtime exception relates to a processing delay.

14. The system of claim 11 , wherein the runtime exception relates to a communication delay.

15. The system of claim 11 , wherein runtime exception relates to missing sensor data generated by a perception system of the vehicle.

16. The system of claim 11 , wherein the runtime exception relates to a lost connection with a remote computing device.

17. The system of claim 11 , wherein the exception handling speed profile is determined based on a characteristic of the runtime exception, wherein the characteristic includes a priority of the runtime exception such that the higher the priority, the greater a rate of deceleration of the exception handling speed profile, and the lower the priority, the lower a rate of deceleration of the exception handling speed profile.

18. The system of claim 11 , wherein the exception handling speed profile includes a constant deceleration over time.

19. The system of claim 11 , wherein the exception handling speed profile includes one or more changes in deceleration over time.

20. The system of claim 11 , wherein the point in time is determined based on an earliest in time potential collision with the object.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 9, 2024
From: LI, DONG; MCNAUGHTON, MATTHEW; YEHOSHUA, SHIR; KHOSROSHAHI, AIDA; SUCAN, IOAN-ALEXANDRU
To: WAYMO LLC
Reel/Frame 067934/0097 →
Continuity (4)
Continuation 18204135 · May 31, 2023
Continuation 17712760 · Apr 4, 2022
Continuation 16383096 · Apr 12, 2019
Related Publication 20240361770A1 · Oct 31, 2024
References Cited (58)
US 6116862A · Rau et al. · 2000 [cited by applicant]
US 7631552B2 · Keski-Hynnila et al. · 2009 [cited by applicant]
US 7797107B2 · Shiller · 2010 [cited by applicant]
US 8260538B2 · Noda et al. · 2012 [cited by applicant]
US 9216745B2 · Beardsley et al. · 2015 [cited by applicant]
US 9221396B1 · Zhu et al. · 2015 [cited by applicant]
US 9873427B2 · Danzl et al. · 2018 [cited by applicant]
US 10042363B1 · Hayward · 2018 [cited by applicant]
US 10061313B2 · Letwin et al. · 2018 [cited by applicant]
US 10139828B2 · Ho et al. · 2018 [cited by applicant]
US 10331127B2 · Oba · 2019 [cited by applicant]
US 10611371B2 · Kusano et al. · 2020 [cited by applicant]
US 10829128B2 · Hoshikawa et al. · 2020 [cited by applicant]
US 11079764B2 · Nister et al. · 2021 [cited by applicant]
US 11327507B2 · Li et al. · 2022 [cited by applicant]
US 11709503B2 · Li et al. · 2023 [cited by applicant]
US 20090088977A1 · Yasuhara et al. · 2009 [cited by applicant]
US 20100256852A1 · Mudalige · 2010 [cited by applicant]
US 20120203418A1 · Braennstroem et al. · 2012 [cited by applicant]
US 20120303216A1 · Yoshimura et al. · 2012 [cited by applicant]
US 20130331934A1 · Kabir et al. · 2013 [cited by applicant]
US 20150360687A1 · Meyer · 2015 [cited by examiner]
US 20170060368A1 · Kochura · 2017 [cited by applicant]
US 20170090480A1 · Ho et al. · 2017 [cited by applicant]
US 20170349169A1 · Deshpande · 2017 [cited by applicant]
US 20170351261A1 · Levinson et al. · 2017 [cited by applicant]
US 20180093676A1 · Emura et al. · 2018 [cited by applicant]
US 20180286242A1 · Talamonti et al. · 2018 [cited by applicant]
US 20180339712A1 · Kislovskiy et al. · 2018 [cited by applicant]
US 20190291726A1 · Shalev-Shwartz et al. · 2019 [cited by applicant]
US 20190347492A1 · Morimura et al. · 2019 [cited by applicant]
US 20190362632A1 · Fokin · 2019 [cited by examiner]
US 20200122694A1 · Eigel et al. · 2020 [cited by applicant]
US 20200148201A1 · King et al. · 2020 [cited by applicant]
US 20220111871A1 · Schmitt et al. · 2022 [cited by applicant]
US 20220315052A1 · Oboril et al. · 2022 [cited by applicant]
US 20230305577A1 · Li et al. · 2023 [cited by applicant]
CN 101859494A · 2010 [cited by applicant]
CN 108597251A · 2018 [cited by applicant]
CN 109311474A · 2019 [cited by applicant]
DE 102004051758A1 · 2006 [cited by applicant]
DE 102008001301A1 · 2009 [cited by applicant]
EP 3576069A1 · 2019 [cited by applicant]
JP 2009085761A · 2009 [cited by applicant]
JP 2009196464A · 2009 [cited by applicant]
JP 2012216017A · 2012 [cited by applicant]
JP 2019527397A · 2019 [cited by applicant]
WO 2013185073A1 · 2013 [cited by applicant]
Non-Final Rejection of U.S. Appl. No. 18/204,135 dated Jan. 31, 2024 (Year: 2024). [cited by examiner]
Allowability Notice of U.S. Appl. No. 18/204,135 dated May 3, 2024 (Year: 2024). [cited by examiner]
Decision to Grant a Patent for Japanese Patent Application No. 2021-557966, May 24, 2023, 5 Pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2020/027662 dated Jul. 21, 2020. [cited by applicant]
Notice of Allowance for Chinese Patent Application No. 202080028282.X, Jun. 21, 2022. [cited by applicant]
The Extended European Search Report for European Patent Application No. 20787044.5, Nov. 7, 2022, 6 Pages. [cited by applicant]
““Determining the maximum time horizon for vehicles to safely follow a trajectory””, Magdici et al. (S. Magdici, Z. Ye and M. Althoff, 2017 IEEE 20th International Conference on Intelligent Transportation Systems (ITSC)… [cited by applicant]
“A Framework for Automated Driving System Testable Cases and Scenarios”, NHTSA, 2018, 180 pages, downloaded on May 23, 2023 at url: https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/13882-automateddrivingsystems_092… [cited by applicant]
Rudametkin , “Robusta: An Approach to Building Dynamic Applications”, Software Engineering, 2013, 212 Pages. [cited by applicant]
Xue , et al., “A Fallback Approach for an Automated Vehicle Encountering Sensor Failure in Monitoring Environment”, IEEE Intelligent Vehicles Symposium (IV), 2018, pp. 1807-1812. [cited by applicant]