IP Library Granted Patent US 8,762,058
Granted Patent B2
US 8,762,058 · App. 13/861,558 · Granted Jun 24, 2014

System and method for storing and providing routes

Inventor: Vinay Goel (Bangalore, IN)
Assignee: Google Inc.
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 8,762,058
App. No.
13/861,558
Granted
Jun 24, 2014
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 (42)

1. A method comprising:

receiving a plurality of routes previously traveled by one or more client devices, each route of the plurality of routes identifying respective starting location for a particular client device and a respective ending location for that particular client device;

receiving a request for directions including a starting location and an ending location; and

selecting, by a processor, a given previously traveled route of the plurality of routes previously traveled by comparing the respective starting locations of the plurality of routes previously traveled to the starting location of the request and by comparing the respective ending locations of the plurality of routes previously traveled to the ending location of the request.

2. The method of claim 1 , wherein the given previously traveled route is further selected based on a number of client devices that have provided the given route.

3. The method of claim 1 , wherein the given previously traveled route is further selected based on a time that the request for directions is received.

4. The method of claim 1 , wherein the given previously traveled route is further selected based on user preferences associated with a particular client device that requested the directions.

5. The method of claim 1 , wherein the given previously traveled route is further selected by determining that the given route is available by comparing the given previously traveled route to the plurality of routes previously traveled.

6. A method comprising:

receiving a plurality of routes previously traveled by one or more client devices, each route of the plurality of routes identifying a respective starting location for a particular client device and a respective ending location for that particular client device;

receiving a request for directions including a starting location and an ending location;

determining that a route between the starting location and the ending location is unavailable;

selecting, by a processor, a first previously traveled route of the plurality of routes previously traveled by comparing the respective starting locations of the plurality of routes previously traveled to the starting location of the request;

selecting, by a processor, a second previously traveled route of the plurality of routes previously traveled by comparing the respective ending locations of the plurality of routes previously traveled to the ending location of the request; and

concatenating the first previously traveled route and the second previously traveled route to generate a third route between the starting location and the ending location of the request.

7. The method of claim 6 , wherein the first previously traveled route is further selected based on a number of client devices that have provided the given route.

8. The method of claim 6 , wherein the first previously traveled route is further selected based on a time that the request for directions is received.

9. The method of claim 6 , wherein the first previously traveled route is further selected based on user preferences associated with a particular client device that requested the directions.

10. The method of claim 6 , wherein the first previously traveled route is further selected by determining that the given route is available by comparing the given previously traveled route to the plurality of routes previously traveled.

11. A system comprising:

memory storing a plurality of routes previously traveled by one or more client devices, each route of the plurality of routes identifying a respective starting location for a particular client device and a respective ending location for that particular client device; and

a processor configured to:

access the memory;

receive a request for directions including a starting location and a ending location; and

select a given previously traveled route of the plurality of routes previously traveled by comparing the respective starting locations of the plurality of routes previously traveled to the starting location of the request and by comparing the respective ending locations of the plurality of routes previously traveled to the ending location of the request.

12. The system of claim 11 , wherein the processor is further configured to select the given previously traveled route on a number of client devices that have provided the given route.

13. The system of claim 11 , wherein the processor is further configured to select the given previously traveled route based on a time that the request for directions is received.

14. The system of claim 11 , wherein the processor is further configured to select the given previously traveled route based on user preferences associated with a particular client device that requested the directions.

15. The system of claim 11 , wherein the processor is further configured to select the given previously traveled route by determining that the given route is available by comparing the given previously traveled route to the plurality of routes previously traveled.

16. A system comprising:

memory storing a plurality of routes previously traveled by one or more client devices, each route of the plurality of routes identifying respective starting location for a particular client device and a respective ending location for that particular client device; and

a processor configured to:

access the memory;

receive a request for directions including a starting location and an ending location;

determine that a route between the starting location and the ending location is unavailable;

select a first previously traveled route of the plurality of routes previously traveled by comparing the respective starting locations of the plurality of routes previously traveled to the starting location of the request;

select a second previously traveled route of the plurality of routes previously traveled by comparing the respective ending locations of the plurality of routes previously traveled to the ending location of the request; and

concatenate the first previously traveled route and the second previously traveled route to generate a third route between the starting location and the ending location of the request.

17. The system of claim 16 , wherein the processor is further configured to select first previously traveled route based on a number of client devices that have provided the given route.

18. The system of claim 16 , wherein the processor is further configured to select first previously traveled route based on a time that the request for directions is received.

19. The system of claim 16 , wherein the processor is further configured to select first previously traveled route based on user preferences associated with a particular client device that requested the directions.

20. The system of claim 16 , wherein the processor is further configured to select the first previously traveled route by determining that the given route is available by comparing the given previously traveled route to the plurality of routes previously traveled.

Assignments (2)
CHANGE OF NAME Recorded Oct 2, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044277/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 19, 2013
From: GOEL, VINAY
To: GOOGLE INC.
Reel/Frame 030253/0795 →
Continuity (3)
Continuation 13479443 · May 24, 2012
Continuation 12291852 · Nov 14, 2008
Related Publication 20130226457A1 · Aug 29, 2013