IP Library Granted Patent US 12,372,367
Granted Patent B2
US 12,372,367 · App. 18/437,504 · Granted Jul 29, 2025

Collective vehicle traffic routing

Inventor: David M. Barth (Seattle, WA)
Assignee: GOOGLE LLC
G01C21/3492G01C21/3415G01C21/3655G01C21/3658G01C21/3667G01C21/3691G01C21/3694G08G1/0133G01S19/42
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,367
App. No.
18/437,504
Granted
Jul 29, 2025
Kind
B2
Abstract

Systems and methods provide a route and turn-by-turn directions based on estimates of current and future traffic along the route. A client device may request turn-by-turn directions between an initial and a final location. A server may identify a plurality of routes between the locations. Each route of the plurality of routes may be divided into route segments. For each route segment of a particular route, the server may estimate a travel time. The travel time may be based on estimated vehicle volume data generated from information received from other vehicles. The server may estimate a total travel time for the particular route. The server may repeat this estimate for each of the plurality of routes between the locations and select the route with the lowest estimated travel time. Based on the selected route, the server may generate turn-by-turn directions and transmit the directions to the client device for display.

Claims (37)

1. A computer-implemented method, the method comprising:

receiving, by one or more computing devices, vehicle volume data associated with at least one route segment of a route;

estimating, by the one or more computing devices, a travel time for the at least one route segment based on the vehicle volume data;

receiving, by the one or more computing devices, data indicative of requests for directions from a plurality of different client devices for the at least one route segment;

updating, by the one or more computing devices, the travel time based on the received data indicative of requests for directions from the plurality of different client devices; and

generating, by the one or more computing devices, turn-by-turn directions for the route based at least in part on the updated travel time.

2. The computer-implemented method of claim 1 , wherein the vehicle volume data comprises location information associated with a plurality of client devices.

3. The computer-implemented method of claim 2 , wherein at least one of the plurality of client devices is a portable device, and wherein the location information is indicative of a current location for the portable device.

4. The computer-implemented method of claim 3 , wherein the current location comprises one or more global positioning system coordinates for the portable device.

5. The computer-implemented method of claim 2 , wherein the location information is indicative of a future location for at least one of the plurality of client devices.

6. The computer-implemented method of claim 1 , wherein the vehicle volume data comprises a capacity index indicative of a capacity of the at least one route segment relative to other route segments.

7. The computer-implemented method of claim 6 , wherein the capacity index correlates a traffic speed associated with the at least one route segment with a number of vehicles on the at least one route segment.

8. A computing device comprising:

memory for storing route segments, wherein each respective route segment is associated with respective vehicle volume data; and

one or more processors configured to:

receive vehicle volume data associated with at least one route segment of a route;

estimate a travel time for the at least one route segment based on the vehicle volume data;

receive data indicative of requests for directions from a plurality of different client devices for the at least one route segment;

update the travel time based on the received data indicative of requests for directions from the plurality of different client devices; and

generate turn-by-turn directions for the route based at least in part on the updated travel time.

9. The computing device of claim 8 , wherein the vehicle volume data comprises estimates of a present volume of traffic and a future volume of traffic along at least one lane of the at least one route segment.

10. The computing device of claim 8 , wherein the vehicle volume data is based on a plurality of requests for directions received from a plurality of second client devices.

11. The computing device of claim 8 , wherein the vehicle volume data comprises a capacity index indicative of a capacity of the at least one route segment relative to other route segments.

12. The computing device of claim 11 , wherein the capacity index correlates a traffic speed associated with the at least one route segment with a number of vehicles on the at least one route segment.

13. The computing device of claim 11 , wherein the client device is a mobile phone.

14. A non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by one or more computing devices, cause the one or more computing devices to perform a method comprising:

receive vehicle volume data associated with at least one route segment of a route;

estimate a travel time for the at least one route segment based on the vehicle volume data;

receive data indicative of requests for directions from a plurality of different client devices for the at least one route segment;

update the travel time based on the received data indicative of requests for directions from the plurality of different client devices; and

generate turn-by-turn directions for the route based at least in part on the updated travel time.

15. The non-transitory computer-readable medium of claim 14 , wherein the vehicle data comprises a capacity index indicative of a capacity of the at least one route segment relative to other route segments.

16. The non-transitory computer-readable medium of claim 15 , wherein the capacity index correlates a traffic speed associated with the at least one route segment with a number of vehicles on the at least one route segment.

17. The non-transitory computer-readable medium of claim 14 , wherein the vehicle data comprises location information associated with a plurality of client devices.

18. The non-transitory computer-readable medium of claim 17 , wherein at least one of the plurality of client devices is a portable device, and wherein the location information is indicative of a current location for the portable device.

19. The non-transitory computer-readable medium of claim 18 , wherein the current location comprises one or more global positioning system coordinates for the portable device.

20. The non-transitory computer-readable medium of claim 14 , wherein the vehicle volume data comprises estimates of a present volume of traffic and a future volume of traffic along at least one lane of the at least one route segment.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 12, 2024
From: BARTH, DAVID M.
To: GOOGLE INC.
Reel/Frame 066733/0397 →
CHANGE OF NAME Recorded Mar 12, 2024
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 066797/0290 →
Continuity (8)
Continuation 17590493 · Feb 1, 2022
Continuation 16577340 · Sep 20, 2019
Continuation 15664070 · Jul 31, 2017
Continuation 15392164 · Dec 28, 2016
Continuation 15392133 · Dec 28, 2016
Continuation 14635685 · Mar 2, 2015
Continuation 12757178 · Apr 9, 2010
Related Publication 20240263954A1 · Aug 8, 2024
References Cited (15)
US 6209026B1 · Ran et al. · 2001 [cited by applicant]
US 6317686B1 · Ran · 2001 [cited by examiner]
US 20010029425A1 · Myr · 2001 [cited by applicant]
US 20020082806A1 · Kaub · 2002 [cited by applicant]
US 20050021225A1 · Kantarjiev · 2005 [cited by examiner]
US 20050131643A1 · Shaffer et al. · 2005 [cited by applicant]
US 20050222750A1 · Tsuge et al. · 2005 [cited by applicant]
US 20060178811A1 · Liu et al. · 2006 [cited by applicant]
US 20070135990A1 · Seymour et al. · 2007 [cited by applicant]
US 20080046134A1 · Bruce et al. · 2008 [cited by applicant]
US 20080071465A1 · Chapman et al. · 2008 [cited by applicant]
US 20080208451A1 · Minami · 2008 [cited by applicant]
US 20100010732A1 · Hartman · 2010 [cited by applicant]
US 20100185382A1 · Barker et al. · 2010 [cited by applicant]
US 20100228467A1 · Wolfe · 2010 [cited by applicant]