IP Library Granted Patent US 12,123,731
Granted Patent B2
US 12,123,731 · App. 17/590,261 · Granted Oct 22, 2024

System and method for storing and providing routes

Inventor: Vinay Goel (Bangalore, IN)
Assignee: Google LLC
G01C21/3484G01C21/34G01C21/3476G01C21/3492H04W4/02H04W4/024
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,123,731
App. No.
17/590,261
Granted
Oct 22, 2024
Kind
B2
Abstract

In one aspect, a system and method is provided whereby map-related requests from mobile devices are used to store and aggregate routes. The routes are then used to determine optimum directions in response to subsequent requests.

Claims (44)

1. A method comprising:

receiving, from a user, a request for directions from a starting location to an ending location;

filtering candidate routes between the starting location and the ending location based on popularity;

determining, with one or more processors at least a first route and a second route, each of the first route and the second route having one or more associated characteristics, wherein the first route and the second route each passed through the filtering based on having at least a threshold level of popularity;

providing to the user an option for selecting a route from at least the first route and the second route based on the associated characteristics;

receiving, through an interface, user input selecting one of the first route or the second route;

providing for display turn-by-turn directions along the selected route; and

providing live traffic information along the selected route.

2. The method of claim 1 , wherein the characteristics comprise an expected time to traverse the route.

3. The method of claim 2 , wherein the expected time to traverse the route is updated based on a time of day.

4. The method of claim 1 , wherein the characteristics comprise a popularity of the route.

5. The method of claim 1 , wherein each of the first route and the second route are optimized based on different types of associated characteristics.

6. The method of claim 5 , wherein the first route is optimized based on time and the second route is optimized based on popularity.

7. The method of claim 1 , wherein the request for directions identifies the ending location based on a point of interest.

8. A system comprising:

memory; and

one or more processors in communication with the memory, the one or more processors configured to:

receive, from a user, a request for directions from a starting location to an ending location;

filter candidate routes between the starting location and the ending location based on popularity;

determine at least a first route and a second route, each of the first route and the second route having one or more associated characteristics, wherein the first route and the second route each passed through the filter based on having at least a threshold level of popularity;

provide to the user an option for selecting a route from at least the first route and the second route based on the associated characteristics;

receive user input selecting one of the first route or the second route;

provide for display turn-by-turn directions along the selected route; and

providing live traffic information along the selected route.

9. The system of claim 8 , wherein the characteristics comprise an expected time to traverse the route.

10. The system of claim 9 , wherein the expected time to traverse the route is updated based on a time of day.

11. The system of claim 8 , wherein the characteristics comprise a popularity of the route.

12. The system of claim 8 , wherein each of the first route and the second route are optimized based on different types of associated characteristics.

13. The system of claim 12 , wherein the first route is optimized based on time and the second route is optimized based on popularity.

14. The system of claim 8 , wherein the request for directions identifies the ending location based on a point of interest.

15. A non-transitory computer-readable medium storing instructions executable by one or more processors for performing a method comprising:

receiving, from a user, a request for directions from a starting location to an ending location;

filtering candidate routes between the starting location and the ending location based on popularity;

determining at least a first route and a second route, each of the first route and the second route having one or more associated characteristics, wherein the first route and the second route each passed through the filtering based on having at least a threshold level of popularity;

providing to the user an option for selecting a route from at least the first route and the second route based on the associated characteristics;

receiving user input selecting one of the first route or the second route;

providing for display turn-by-turn directions along the selected route; and

providing live traffic information along the selected route.

16. The non-transitory computer-readable medium of claim 15 , wherein the characteristics comprise an expected time to traverse the route.

17. The non-transitory computer-readable medium of claim 16 , wherein the expected time to traverse the route is updated based on a time of day.

18. The non-transitory computer-readable medium of claim 15 , wherein the characteristics comprise a popularity of the route.

19. The method of claim 1 , further comprising:

providing, through an interface, an option for selecting a transportation system other than cars; and

generating a suggested route for the transportation system.

Assignments (2)
CHANGE OF NAME Recorded Feb 4, 2022
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 058959/0319 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2022
From: GOEL, VINAY
To: GOOGLE INC.
Reel/Frame 058874/0719 →
Continuity (7)
Continuation 16274667 · Feb 13, 2019
Continuation 15438829 · Feb 22, 2017
Continuation 14271831 · May 7, 2014
Continuation 13861558 · Apr 12, 2013
Continuation 13479443 · May 24, 2012
Continuation 12291852 · Nov 14, 2008
Related Publication 20220155084A1 · May 19, 2022