IP Library Granted Patent US 12,420,831
Granted Patent B2
US 12,420,831 · App. 17/965,894 · Granted Sep 23, 2025

Systems and methods for operating an autonomous vehicle

Inventors: Scott Douglas Foster (San Diego, CA); Dishi Li (Menifee, CA); Hunter Scott Willoughby (San Diego, CA); Yufei Zhao (San Diego, CA)
Assignee: TUSIMPLE, INC.
B60W60/0011B60W30/18163B60W40/02B60W50/0097B60W50/14B60W60/0015B60W60/0027B60W60/00274G01S17/08G01S17/58G01S17/89G01S17/931G06F18/24137B60W2300/145B60W2420/403B60W2420/408B60W2520/06B60W2520/10B60W2520/22B60W2530/10B60W2552/10B60W2552/30B60W2554/20B60W2554/4026B60W2554/4041B60W2554/4042B60W2554/4045B60W2554/4046B60W2554/4049B60W2554/80B60W2556/40B60W2556/45B60W2556/65B60W2710/06B60W2754/20
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,420,831
App. No.
17/965,894
Granted
Sep 23, 2025
Kind
B2
Abstract

An example method includes detecting, via sensor data collected from sensors located on the AV, an upcoming object located on a roadway. The method further includes determining, from the sensor data, a relative distance and a relative direction of the upcoming object with respect to the autonomous vehicle. The method further includes mapping the upcoming object to an absolute location with respect to the roadway based on map data that describes upcoming topology of the roadway and a location of the autonomous vehicle. The method further includes associating the upcoming object with a lane of the roadway based on the absolute location mapped to the upcoming object and based on lane geometry data for the roadway. The method further includes operating the autonomous vehicle based on a relationship between the lane associated with the upcoming object and a current lane in which the autonomous vehicle is located.

Claims (51)

1. A method of operating an autonomous vehicle, comprising:

detecting, via sensor data collected from sensors located on the autonomous vehicle, an upcoming object located on a roadway on which the autonomous vehicle is located;

determining, from the sensor data, a relative distance and a relative direction of the upcoming object with respect to the autonomous vehicle;

mapping the upcoming object to an absolute location with respect to the roadway based on (i) map data that describes upcoming topology of the roadway and (ii) a location of the autonomous vehicle within the roadway;

associating the upcoming object with a lane of the roadway based on the absolute location mapped to the upcoming object and based on lane geometry data for the roadway;

operating the autonomous vehicle based on a relationship between the lane associated with the upcoming object and a current lane in which the autonomous vehicle is located;

determining a width and height of the upcoming object when the autonomous vehicle is a first distance away from the upcoming object; and

determining a length of the upcoming object along a direction of travel of the autonomous vehicle based on movement of the upcoming object and based on a two-dimensional bounding box associated with the determined width and height of the upcoming object when the autonomous vehicle is a second distance away from the upcoming object, wherein the second distance is less than the first distance, wherein the autonomous vehicle is operated further based on the width and the length of the upcoming object.

2. The method of claim 1 , further comprising:

tracking changes to the absolute location of the upcoming object for at least a length of time that the autonomous vehicle is approaching the upcoming object; and

updating the lane associated with the upcoming object based on the tracked changes.

3. The method of claim 1 , further comprising classifying the upcoming object as a static object or a moving object, wherein the autonomous vehicle is operated further based on whether the upcoming object is classified as a static object or a moving object.

4. The method of claim 3 , further comprising, in response to classifying the upcoming object as a moving object, updating the absolute location of the upcoming object at a pre-determined frequency.

5. The method of claim 3 , further comprising:

in response to classifying the upcoming object as a static object, monitoring the upcoming object for movement; and

based on a threshold degree of movement of the upcoming object being detected, re-classifying the upcoming object as a moving object.

6. The method of claim 1 , further comprising associating the upcoming object with a shoulder area of the roadway based on the lane geometry data defining shoulder areas of the roadway.

7. The method of claim 1 , further comprising:

determining a size of the upcoming object from the sensor data; and

based on the lane associated with the upcoming object and the current lane being a same lane, operating the autonomous vehicle with either a lane change operation or a lane bias operation based on the size of the upcoming object.

8. A system for operating an autonomous vehicle, comprising a computer that includes a processor configured to execute instructions to cause the system to:

detect, via sensor data collected from sensors located on the autonomous vehicle, an upcoming object located on a roadway on which the autonomous vehicle is located;

determine, from the sensor data, a relative distance and a relative direction of the upcoming object with respect to the autonomous vehicle;

map the upcoming object to an absolute location with respect to the roadway based on (i) map data that describes upcoming topology of the roadway and (ii) a location of the autonomous vehicle within the roadway;

associate the upcoming object with a lane of the roadway based on the absolute location mapped to the upcoming object and based on lane geometry data for the roadway;

operate the autonomous vehicle based on a relationship between the lane associated with the upcoming object and a current lane in which the autonomous vehicle is located;

determine a width and height of the upcoming object when the autonomous vehicle is a first distance away from the upcoming object; and

determine a length of the upcoming object along a direction of travel of the autonomous vehicle based on movement of the upcoming object and based on a two-dimensional bounding box associated with the determined width and height of the upcoming object when the autonomous vehicle is a second distance away from the upcoming object, wherein the second distance is less than the first distance, wherein the autonomous vehicle is operated further based on the width and the length of the upcoming object.

9. The system of claim 8 , wherein the processor further causes the system to:

track the upcoming object across successive sensor data collected from the sensors at subsequent points in time; and

update the lane associated with the upcoming object based on the tracking.

10. The system of claim 8 , wherein the processor further causes the system to classify the upcoming object as a vehicular object or a non-vehicular object, wherein the autonomous vehicle is operated further based on whether the upcoming object is classified as a vehicular object or a non-vehicular object.

11. The system of claim 10 , wherein the processor further causes the system to, in response to classifying the upcoming object as a vehicular object, update the absolute location of the upcoming object at a pre-determined frequency.

12. The system of claim 10 , wherein the processor further causes the system to:

in response to classifying the upcoming object as a non-vehicular object, monitor the upcoming object for movement; and

operate the autonomous vehicle to maintain at least a minimum distance away from the upcoming object, wherein the minimum distance corresponds to movement of the upcoming object.

13. The system of claim 8 , wherein the lane associated with the upcoming object includes a shoulder area of the roadway.

14. A non-transitory computer readable program storage medium having code stored thereon, the code, when executed by a processor, causing the processor to:

detect, via sensor data collected from sensors located on an autonomous vehicle, an upcoming object located on a roadway on which the autonomous vehicle is located;

determine, from the sensor data, a relative distance and a relative direction of the upcoming object with respect to the autonomous vehicle;

map the upcoming object to an absolute location with respect to the roadway based on (i) map data that describes upcoming topology of the roadway and (ii) a location of the autonomous vehicle within the roadway;

associate the upcoming object with a lane of the roadway based on the absolute location mapped to the upcoming object and based on lane geometry data for the roadway;

operate the autonomous vehicle based on a relationship between the lane associated with the upcoming object and a current lane in which the autonomous vehicle is located;

determine a width and height of the upcoming object when the autonomous vehicle is a first distance away from the upcoming object; and

determine a length of the upcoming object along a direction of travel of the autonomous vehicle based on movement of the upcoming object and based on a two-dimensional bounding box associated with the determined width and height of the upcoming object when the autonomous vehicle is a second distance away from the upcoming object, wherein the second distance is less than the first distance, wherein the autonomous vehicle is operated further based on the width and the length of the upcoming object.

15. The non-transitory computer readable program storage medium of claim 14 , wherein the code further causes the processor to:

track the upcoming object across other sensor data collected from a different set of sensors located on the autonomous vehicle, wherein the different set of sensors are configured for a different sensing modality than the sensors, wherein the relative distance and the relative direction of the upcoming object is determined further from the other sensor data.

16. The non-transitory computer readable program storage medium of claim 14 , wherein the code further causes the processor to predict a degree of movement of the upcoming object, wherein the autonomous vehicle is operated further based on the predicted degree of movement.

17. The non-transitory computer readable program storage medium of claim 16 , wherein the code further causes the processor to update the absolute location of the upcoming object at a pre-determined frequency that is based on the predicted degree of movement.

18. The non-transitory computer readable program storage medium of claim 14 , wherein at least a portion of the map data is provided by one or more vehicles located at an upcoming portion of the roadway.

19. The non-transitory computer readable program storage medium of claim 14 , wherein the relative distance and the relative direction of the upcoming object is determined using a centroid of a LiDAR point cloud of the sensor data via which the upcoming object is detected.

Assignments (2)
CHANGE OF NAME Recorded Dec 3, 2025
From: TUSIMPLE, INC.
To: CREATEAI, INC.
Reel/Frame 073832/0553 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 23, 2023
From: FOSTER, SCOTT DOUGLAS; LI, DISHI; WILLOUGHBY, HUNTER SCOTT; ZHAO, YUFEI
To: TUSIMPLE, INC.
Reel/Frame 063732/0239 →
Continuity (2)
Provisional Application 63255839 · Oct 14, 2021
Related Publication 20230123912A1 · Apr 20, 2023
References Cited (67)
US 9598076B1 · Jain et al. · 2017 [cited by applicant]
US 10403140B2 · Banvait et al. · 2019 [cited by applicant]
US 10698404B2 · Nelson · 2020 [cited by applicant]
US 10752242B2 · Mamchuk et al. · 2020 [cited by applicant]
US 11814070B1 · Prioletti · 2023 [cited by examiner]
US 20080077464A1 · Gottlieb et al. · 2008 [cited by applicant]
US 20130261872A1 · Ferguson et al. · 2013 [cited by applicant]
US 20150210312A1 · Stein · 2015 [cited by examiner]
US 20160098926A1 · Probert et al. · 2016 [cited by applicant]
US 20160167650A1 · Clarke et al. · 2016 [cited by applicant]
US 20160214608A1 · Packwood-Ace · 2016 [cited by applicant]
US 20160318523A1 · Kim · 2016 [cited by applicant]
US 20170330455A1 · Kikuchi · 2017 [cited by applicant]
US 20180037219A1 · Johri · 2018 [cited by applicant]
US 20180186208A1 · Coombs · 2018 [cited by applicant]
US 20190061765A1 · Marden · 2019 [cited by examiner]
US 20190071099A1 · Nishiguchi · 2019 [cited by applicant]
US 20190088135A1 · Do · 2019 [cited by applicant]
US 20190283802A1 · Matsunaga et al. · 2019 [cited by applicant]
US 20190354105A1 · Cunningham · 2019 [cited by applicant]
US 20190384994A1 · Frossard · 2019 [cited by applicant]
US 20200226924A1 · Yeung · 2020 [cited by applicant]
US 20200257299A1 · Wang et al. · 2020 [cited by applicant]
US 20200276972A1 · Ito · 2020 [cited by applicant]
US 20200324777A1 · Kato et al. · 2020 [cited by applicant]
US 20200336375A1 · Ucar · 2020 [cited by applicant]
US 20200353894A1 · Obaidi · 2020 [cited by applicant]
US 20200363800A1 · Jojo-Verge · 2020 [cited by applicant]
US 20210183246A1 · Zack · 2021 [cited by applicant]
US 20210239492A1 · Yano · 2021 [cited by examiner]
US 20210245740A1 · George · 2021 [cited by applicant]
US 20210261133A1 · Sakayori et al. · 2021 [cited by applicant]
US 20210302982A1 · Yasui · 2021 [cited by examiner]
US 20210387622A1 · Kudo · 2021 [cited by applicant]
US 20210405642A1 · Danford · 2021 [cited by applicant]
US 20220107197A1 · Yeung · 2022 [cited by applicant]
US 20220258800A1 · Zimmerman · 2022 [cited by applicant]
US 20220333933A1 · Ma · 2022 [cited by applicant]
US 20220348227A1 · Foster et al. · 2022 [cited by applicant]
US 20220371583A1 · Kario · 2022 [cited by applicant]
US 20230119659A1 · Foster · 2023 [cited by applicant]
US 20230123611A1 · Foster · 2023 [cited by applicant]
US 20230123912A1 · Foster · 2023 [cited by applicant]
US 20230124314A1 · Foster · 2023 [cited by applicant]
US 20230222908A1 · Yueng · 2023 [cited by applicant]
DE 102013003215A1 · 2013 [cited by applicant]
DE 102016008514A1 · 2017 [cited by applicant]
DE 102020200876A1 · 2021 [cited by examiner]
EP 2902290A1 · 2015 [cited by applicant]
EP 3418150A1 · 2018 [cited by applicant]
EP 3659883A1 · 2020 [cited by applicant]
WO 2014130178A1 · 2014 [cited by applicant]
WO 2019009382A1 · 2019 [cited by applicant]
WO 2022251880A1 · 2022 [cited by applicant]
“CMV Driving Tips—Following too Closely,” Oct. 21, 2019, FMCSA.gov (Year: 2019). [cited by examiner]
U.S. Patent & Trademark Office, Non-Final Office Action for U.S. Appl. No. 17/965,889, mailed on Oct. 17, 2024, 13 pages. [cited by applicant]
U.S. Patent & Trademark Office, Notice of Allowance for U.S. Appl. No. 17/965,893, mailed on Oct. 28, 2024, 10 pages. [cited by applicant]
U.S. Patent & Trademark Office, Final Office Action for U.S. Appl. No. 17/809,543, mailed on Dec. 4, 2024, 23 pages. [cited by applicant]
International Search Report from corresponding International Application No. PCT/US2022/071992, dated Sep. 13, 2022. [cited by applicant]
International Search Report from corresponding International Application No. PCT/US2022/073241, dated Jan. 2, 2023. [cited by applicant]
International Search Report & Written Opinion for Application No. PCT/US2022/046646, dated Mar. 30, 2023, 20 pages. [cited by applicant]
U.S. Patent & Trademark Office, Non-Final Office Action for U.S. Appl. No. 17/809,543, mailed on Jun. 18, 2024, 21 pages. [cited by applicant]
U.S. Patent & Trademark Office, Non-Final Office Action for U.S. Appl. No. 17/965,893, mailed on Jun. 27, 2024, 14 pages. [cited by applicant]
U.S. Patent & Trademark Office, Non-Final Office Action for U.S. Appl. No. 17/965,896, mailed on Jul. 17, 2024, 23 pages. [cited by applicant]
U.S. Patent & Trademark Office, Final Office Action for U.S. Appl. No. 17/661,273, mailed on Aug. 21, 2024, 24 pages. [cited by applicant]
U.S. Patent & Trademark Office, Non-Final Office Action for U.S. Appl. No. 17/661,273, mailed on Mar. 14, 2024, 22 pages. [cited by applicant]
International Search Report & Written Opinion for Application No. PCT/US2022/048289, dated Apr. 28, 2023, 22 pages. [cited by applicant]