US2013132140A1PendingUtilityA1

Determining a location related to on-demand services through use of portable computing devices

Assignee: UBER TECHNOLOGIES INCPriority: Dec 4, 2009Filed: Nov 8, 2012Published: May 23, 2013
Est. expiryDec 4, 2029(~3.3 yrs left)· nominal 20-yr term from priority
G06Q 10/06G06Q 10/06311G06Q 40/12G06Q 10/02G06Q 30/0201G06Q 30/0202G06Q 30/0284G06Q 10/063G06Q 30/0601G06Q 10/025G06Q 50/30G06Q 50/40
66
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method for determining a location relating to an on-demand service on a computing device is provided. One or more processors receiving a transport request from a user. The transport request specifies at least one of a pick-up region or a drop-off region. One or more locations of interests within the at least one of the pick-up region or the drop-off region are determined. Based on the at least one of the pick-up region or the drop-off region, one or more historical locations related to the user is determined. A likely location is determined based on the determined one or more locations of interest and the one or more historical locations.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for determining a location relating to a transport service on a computing device, the method being performed by one or more processors and comprising:
 receiving a transport request from a user, the transport request specifying at least one of a pick-up region or a drop-off region;   determining one or more locations of interests within the at least one of the pick-up region or the drop-off region;   comparing the at least one of the pick-up region or the drop-off region with one or more historical locations related to the user; and   determining a likely location based on the determined one or more locations of interest and the one or more historical locations.   
     
     
         2 . The method of  claim 1 , wherein determining one or more locations of interests includes referencing a business directory. 
     
     
         3 . The method of  claim 1 , wherein the one or more historical locations related to the user includes one or more locations recently visited by the user. 
     
     
         4 . The method of  claim 3 , wherein the one or more historical locations related to the user includes one or more locations commonly visited by the user. 
     
     
         5 . The method of  claim 4 , wherein the one or more historical locations related to the user includes one or more locations previously visited by the user that is closest to the at least one of the pick-up region or the drop-off region. 
     
     
         6 . The method of  claim 1 , further comprising:
 in response to determining the likely location, providing a prompt on a user interface feature that asks the user whether the likely location is a location the user would like to be picked up at or dropped off at.   
     
     
         7 . The method of  claim 6 , further comprising:
 receiving a user confirmation that the likely location is the location the user would like to be picked up at or dropped off at; and   arranging the transport service for the user based on the likely location.   
     
     
         8 . The method of  claim 6 , further comprising:
 receiving a user input that specifies that the likely location is not the location the user would like to be picked up at or dropped off at; and   determining a second likely location based on the determined one or more locations of interest and the one or more historical locations.   
     
     
         9 . A non-transitory computer readable medium storing instructions that, when executed by one or more processors, causes the one or more processors to perform steps comprising:
 receiving a transport request for a transport service from a user, the transport request specifying at least one of a pick-up region or a drop-off region;   determining one or more locations of interests within the at least one of the pick-up region or the drop-off region;   comparing the at least one of the pick-up region or the drop-off region with one or more historical locations related to the user; and   determining a likely location based on the determined one or more locations of interest and the one or more historical locations.   
     
     
         10 . The non-transitory computer readable medium of  claim 9 , wherein the instructions cause the one or more processors to determine one or more locations of interests by referencing a business directory. 
     
     
         11 . The non-transitory computer readable medium of  claim 9 , wherein the one or more historical locations related to the user includes one or more locations recently visited by the user. 
     
     
         12 . The non-transitory computer readable medium of  claim 11 , wherein the one or more historical locations related to the user includes one or more locations commonly visited by the user. 
     
     
         13 . The non-transitory computer readable medium of  claim 12 , wherein the one or more locations previously visited by the user that is closest to the at least one of the pick-up region or the drop-off region. 
     
     
         14 . The non-transitory computer readable medium of  claim 9 , wherein the instructions cause the one or more processors to:
 in response to determining the likely location, provide a prompt on a user interface feature that asks the user whether the likely location is a location the user would like to be picked up at or dropped off at.   
     
     
         15 . The non-transitory computer readable medium of  claim 14 , wherein the instructions cause the one or more processors to:
 receive a user confirmation that the likely location is the location the user would like to be picked up at or dropped off at; and   arrange the transport service for the user based on the likely location.   
     
     
         16 . The non-transitory computer readable medium of  claim 14 , wherein the instructions cause the one or more processors to:
 receive a user input that specifies that the likely location is not the location the user would like to be picked up at or dropped off at; and   determine a second likely location based on the determined one or more locations of interest and the one or more historical locations.   
     
     
         17 . A mobile computing device comprising:
 a display;   one or more memory resources; and   one or more processors coupled to the display and the one or more memory resources, the one or more processors to:
 receive a transport request for a transport service from a user, the transport request specifying at least one of a pick-up region or a drop-off region; 
 determine one or more locations of interests within the at least one of the pick-up region or the drop-off region; 
 compare the at least one of the pick-up region or the drop-off region with one or more historical locations related to the user; and 
 determine a likely location based on the determined one or more locations of interest and the one or more historical locations. 
   
     
     
         18 . The mobile computing device of  claim 17 , wherein the one or more processors determine one or more locations of interests by referencing a business directory. 
     
     
         19 . The mobile computing device of  claim 17 , wherein the one or more historical locations related to the user includes at least one of one or more locations recently visited by the user, one or more locations commonly visited by the user, or one or more locations previously visited by the user that is closest to the at least one of the pick-up region or the drop-off region. 
     
     
         20 . The mobile computing device of  claim 17 , wherein the one or more processors further:
 in response to determining the likely location, provide a prompt on a user interface feature that asks the user whether the likely location is a location the user would like to be picked up at or dropped off at.

Join the waitlist — get patent alerts

Track US2013132140A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.