IP Library Granted Patent US 9,410,814
Granted Patent B2
US 9,410,814 · App. 14/851,341 · Granted Aug 9, 2016

Passive crowd-sourced map updates and alternate route recommendations

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 9,410,814
App. No.
14/851,341
Granted
Aug 9, 2016
Kind
B2
Abstract

The claimed subject matter is directed to systems and methods for providing passive crowd-sourced alternate route recommendations. In one embodiment, locations of users of a number of mobile location-aware devices are tracked over time. Upon receiving a request, users of mobile location-aware devices that have traveled from a desired start location to a desired stop location are identified. At least one of the different routes taken by one or more users from the desired start location to the desired stop location is provided to the requestor as at least one recommended alternate route. The different routes taken by the one or more users from the desired start location to the desired stop location include routes taken that begin before the desired start location and go through the start location and routes taken that stop beyond the desired stop location and go through the desired stop location.

Claims (53)

1. A method comprising:

tracking locations of a plurality of users of a plurality of mobile location-aware devices over time;

receiving an alternate route request from a requestor, the alternate route request identifying a desired start location and a desired stop location;

determining, by a processor, at least one of one or more different routes taken by one or more users of the plurality of users from the desired start location to the desired stop location to provide to the requestor as at least one recommended alternate route, wherein the one or more users includes users other than the requestor and the different routes taken by the one or more users from the desired start location to the desired stop location include routes taken that begin before the desired start location and go through the start location and routes taken that stop beyond the desired stop location and go through the desired stop location; and

enabling the at least one recommended alternate route to be provided to the requestor.

2. The method of claim 1 comprising:

identifying the one or more users of the plurality of users that have traveled from the desired start location to the desired stop location based on the tracked locations of the plurality of users of the plurality of mobile location-aware devices; and

determining, by the processor, the one or more different routes taken by the one or more users from the desired start location to the desired stop location based on the locations of the one or more users.

3. The method of claim 2 wherein identifying the one or more users of the plurality of users that have traveled from the desired start location to the desired stop location comprises identifying one or more users of the plurality of users that have traveled from the desired start location to the desired stop location during a desired time window.

4. The method of claim 3 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

5. The method of claim 1 further comprising:

determining, for each different route of the at least one of the one or more different routes, a characteristic of the different route; and

providing the characteristic of each different route to the requestor.

6. The method of claim 5 wherein the characteristic of the different route is at least one of: a number of users of the plurality of users that have traveled the different route, an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route, and an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route during a desired time window.

7. The method of claim 6 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

8. The method of claim 1 wherein the determining of the at least one of one or more different routes request for alternate routes is provided automatically in response to a subsequent request from the requestor for navigation from a desired start location to a desired stop location.

9. The method of claim 1 wherein the request for alternate routes is provided automatically based on a request of a third party map service.

10. At least one server comprising:

a communication interface communicatively coupling the server to a plurality of mobile location-aware devices via a network; and

a controller associated with the communication interface and adapted to:

track locations of a plurality of users of the plurality of mobile location-aware devices over time;

receive an alternate route request from a requestor, the alternate route request identifying a desired start location and a desired stop location;

determine at least one of one or more different routes taken by one or more users of the plurality of users from the desired start location to the desired stop location to provide to the requestor as at least one recommended alternate route, wherein the one or more users includes users other than the requestor and the different routes taken by the one or more users from the desired start location to the desired stop location include routes taken that begin before the desired start location and go through the start location and routes taken that stop beyond the desired stop location and go through the desired stop location; and

enable the at least one recommended alternate route to be provided to the requestor.

11. The at least one server of claim 10 , wherein the controller is further adapted to:

identify one or more users of the plurality of users that have traveled from the desired start location to the desired stop location based on the locations of the plurality of users of the plurality of mobile location-aware devices; and

determine the one or more different routes taken by the one or more users from the desired start location to the desired stop location based on the locations of the one or more users.

12. The at least one server of claim 11 wherein in order to identify one or more users of the plurality of users that have traveled from the desired start location to the desired stop location, the controller is further adapted to identify one or more users of the plurality of users that have traveled from the desired start location to the desired stop location during a desired time window.

13. The at least one server of claim 12 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

14. The at least one server of claim 10 wherein the controller is further adapted to:

determine, for each different route of the at least one of the one or more different routes, a characteristic of the different route; and

provide the characteristic of each different route to the requestor.

15. The at least one server of claim 14 wherein the characteristic of the different route is at least one of: a number of users of the plurality of users that have traveled the different route, an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route, and an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route during a desired time window.

16. The at least one server of claim 15 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

17. The at least one server of claim 10 wherein the determining of the at least one of one or more different routes request for alternate routes is provided automatically in response to a subsequent request from the requestor for navigation from a desired start location to a desired stop location.

18. The at least one server of claim 10 wherein the request for alternate routes is provided automatically based on a request of a third party map service.

19. A non-transitory computer-readable medium storing software for instructing at least one controller of at least one server to:

track locations of a plurality of users of a plurality of mobile location-aware devices over time;

receive an alternate route request from a requestor, the alternate route request identifying a desired start location and a desired stop location;

determine at least one of one or more different routes taken by one or more users of the plurality of users from the desired start location to the desired stop location to provide to the requestor as at least one recommended alternate route, wherein the one or more users includes users other than the requestor and the different routes taken by the one or more users from the desired start location to the desired stop location include routes taken that begin before the desired start location and go through the start location and routes taken that stop beyond the desired stop location and go through the desired stop location; and

enable the at least one recommended alternate route to be provided to the requestor.

20. The non-transitory computer-readable medium of claim 19 wherein the software further instructs the at least one controller of at least one server to:

identify the one or more users of the plurality of users that have traveled from the desired start location to the desired stop location based on the locations of the plurality of users of the plurality of mobile location-aware devices; and

determine the one or more different routes taken by the one or more users from the desired start location to the desired stop location based on the locations of the one or more users.

21. The non-transitory computer-readable medium of claim 20 wherein in order to identify one or more users of the plurality of users that have traveled from the desired start location to the desired stop location, the software further instructs the controller to identify one or more users of the plurality of users that have traveled from the desired start location to the desired stop location during a desired time window.

22. The non-transitory computer-readable medium of claim 21 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

23. The non-transitory computer-readable medium of claim 19 wherein the software further instructs the controller to:

determine, for each different route of the at least one of the one or more different routes, a characteristic of the different route; and

provide the characteristic of each different route to the requestor.

24. The non-transitory computer-readable medium of claim 23 wherein the characteristic of the different route is at least one of a number of users of the plurality of users that have traveled the different route, an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route, and an average travel time for the different route determined based on actual travel times of users of the plurality of users that have traveled the different route during a desired time window.

25. The non-transitory computer-readable medium of claim 24 wherein the desired time window is a reoccurring time window corresponding to at least one of a group consisting of: a current time of day and a current day of the week.

26. The non-transitory computer-readable medium of claim 19 wherein the determining of the at least one of one or more different routes request for alternate routes is provided automatically in response to a subsequent request from the requestor for navigation from a desired start location to a desired stop location.

27. The non-transitory computer-readable medium of claim 19 wherein the request for alternate routes is provided automatically based on a request of a third party map service.

Assignments (17)
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069110/0508 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT (TERM LOAN) AT REEL 050767, FRAME 0076 Recorded Sep 11, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC. AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069133/0167 →
RELEASE OF SECURITY INTEREST Recorded Mar 10, 2021
From: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 055547/0404 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0109 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0076 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBER PREVIOUSLY RECORDED AT REEL: 45853 FRAME: 418. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 26, 2018
From: UBER TECHNOLOGIES, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 049259/0064 →
SECURITY INTEREST Recorded Apr 6, 2018
From: UBER TECHNOLOGIES, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 045853/0418 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT NUMBER 8520609 PREVIOUSLY RECORDED ON REEL 043084 FRAME 0656. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Apr 2, 2018
From: IP3, SERIES 100 OF ALLIED SECURITY TRUST 1
To: UBER TECHNOLOGIES, INC.
Reel/Frame 045813/0044 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 4, 2017
From: IP3, SERIES 100 OF ALLIED SECURITY TRUST I
To: UBER TECHNOLOGIES, INC.
Reel/Frame 043084/0656 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 1, 2016
From: WALDECK TECHNOLOGY LLC
To: IP3, SERIES 100 OF ALLIED SECURITY TRUST I
Reel/Frame 039900/0862 →
SECURITY INTEREST Recorded Aug 24, 2016
From: CONCERT TECHNOLOGY CORPORATION
To: CONCERT DEBT, LLC
Reel/Frame 039800/0320 →
SECURITY INTEREST Recorded Aug 24, 2016
From: CONCERT TECHNOLOGY CORPORATION
To: CONCERT DEBT, LLC
Reel/Frame 039800/0306 →
RELEASE OF SECURITY INTEREST Recorded Aug 24, 2016
From: CONCERT DEBT, LLC
To: WALDECK TECHNOLOGY, LLC
Reel/Frame 039527/0303 →
RELEASE OF SECURITY INTEREST Recorded Aug 24, 2016
From: CONCERT DEBT, LLC
To: CONCERT TECHNOLOGY CORPORATION
Reel/Frame 039527/0182 →
SECURITY INTEREST Recorded Aug 24, 2016
From: WALDECK TECHNOLOGY, LLC
To: CONCERT DEBT, LLC
Reel/Frame 039800/0470 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2015
From: CURTIS, SCOTT; HALBER, ERIC B.; EVANS, GREGORY M.; PETERSEN, STEVEN L.
To: KOTA ENTERPRISES, LLC
Reel/Frame 036838/0065 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2015
From: KOTA ENTERPRISES, LLC
To: WALDECK TECHNOLOGY, LLC
Reel/Frame 036838/0114 →