IP Library › Granted Patent US 12,462,319
Granted Patent B2
US 12,462,319 · App. 18/627,194 · Granted Nov 4, 2025

Computing system configuring destination accelerators based on usage patterns of users of a transport service

Inventors: Yuhki Yamashita (San Francisco, CA); Didier Patrick Hilhorst (San Francisco, CA); Bryant Jow (San Francisco, CA); Peter Ng (San Francisco, CA)
Assignee: Uber Technologies, Inc.
G06Q50/40G06F3/04842G06F3/0485G06F9/451G06Q10/00G06Q10/1095H04L67/1095H04L67/306H04L67/52H04L67/60
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,462,319
App. No.
18/627,194
Granted
Nov 4, 2025
Kind
B2
Abstract

A computing system can detect the launch of a rider application on computing devices of users of a transport service. The computing system can receive location data indicating the current location of each user, and determine a usage pattern for each user based on historical data corresponding to historical utilization of the transport service by the user. Based on the current location and the usage pattern of the user, the computing system can determine one or more suggested destination locations for the user, and transmit, over the one or more networks, display data to cause the rider application to display a destination accelerator for each of the one or more suggested destination locations. The destination accelerator can be selectable by the user to automatically input a destination location into a transport request for the transport service.

Claims (54)

1 . A computing system comprising:

a network communication interface communicating, over one or more networks, with computing devices of users of a network service;

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the computing system to perform operations that comprise:

storing, in a database accessible by the computing system, historical data that corresponds to utilization of the network service by a plurality of users, including a first user;

receiving, over the one or more networks and via a GPS resource of a computing device of the first user, a current location of the first user;

based on the historical data, determining multiple destination locations for the first user, each of the multiple destination locations being associated with a corresponding time period that correlates to when a likelihood of the first user requesting a transport service for that destination location exceeds a threshold level;

based at least in part on a current time, the current location of the computing device of the first user, and the corresponding time period associated with each of the multiple destination locations, selecting a destination location of the multiple destination locations to represent as a corresponding destination feature by a service application operating on the computing device of the first user;

transmitting, over the one or more networks, display data to the computing device of the first user, the data causing the service application operating on the computing device of the first user to provide, on a display of the computing device, the corresponding destination feature for the selected destination location;

based on the first user selecting the corresponding destination feature, receiving, over the one or more networks from the computing device of the first user, the service request for transporting the first user to the selected destination location; and

processing the service request by selecting, from a plurality of candidate service providers, a service provider to fulfill the service request based, at least in part, on a current location of the service provider, received via a GPS resource of a computing device of the service provider.

2 . The computing system of claim 1 , wherein the multiple destination locations are based on historical data that is not specific to the first user.

3 . The computing system of claim 2 , wherein the multiple destination locations include a point of interest within a proximity of the current location of the first user.

4 . The computing system of claim 3 , wherein determining the point of interest is further based at least in part on the historical data of the first user.

5 . The computing system of claim 1 , wherein the destination feature is based on historical data that is specific to the first user.

6 . The computing system of claim 5 , wherein the operations further comprise:

storing a first user profile for the first user, the first user profile indicating a preference of the first user for a type of vehicle or a type of transport service;

associating at least the destination feature of the user selection with the preference; and

wherein selecting the service provider is based at least in part on at least one of a type of vehicle operated by the service provider or the type of service provided with the service provider.

7 . The computing system of claim 1 , wherein determining the multiple destination locations includes determining, based on the historical data, that the first user is in a region where the first user has not previously utilized the network service, and wherein the multiple destination locations include a point of interest of the region.

8 . The computing system of claim 1 , wherein the operations further comprise:

receiving, over the one or more networks and via GPS resources of a plurality of service provider devices, a plurality of current locations of a plurality of candidate service providers; and

wherein selecting the service provider from the plurality of candidate service providers includes determining a proximity of each service of the plurality of candidate service providers to the current location of the first user.

9 . A non-transitory computer-readable medium that stores instructions, which when executed by one or more processors of a computing system, cause the computing system to perform operations that comprise:

storing, in a database accessible by the computing system, historical data that corresponds to utilization of a network service by a plurality of users, including a first user;

receiving, over the one or more networks and via a GPS resource of a computing device of the first user, a current location of the first user;

based on the historical data, determining multiple destination locations for the first user, each of the multiple destination locations being associated with a corresponding time period that correlates to when a likelihood of the first user requesting a transport service for that destination location exceeds a threshold level;

based at least in part on a current time, the current location of the computing device of the first user, and the corresponding time period associated with each of the multiple destination locations, selecting a destination location of the multiple destination locations to represent as a corresponding destination feature by a service application operating on the computing device of the first user;

transmitting, over the one or more networks, data to the computing device of the first user, the data causing the service application operating on the computing device of the first user to provide, on a display of the computing device, the corresponding destination feature for the selected destination location;

based on the first user selecting the corresponding destination feature, receiving, over the one or more networks from the computing device of the first user, the service request for transporting the first user to the selected destination location; and

processing the service request by selecting, from a plurality of candidate service providers, a service provider to fulfill the service request based, at least in part, on a current location of the service provider, received via a GPS resource of a computing device of the service provider.

10 . The non-transitory computer-readable medium of claim 9 , wherein the multiple destination locations are based on historical data that is not specific to the first user.

11 . The non-transitory computer-readable medium of claim 10 , wherein the multiple destination locations include a point of interest within a proximity of the current location of the first user.

12 . The non-transitory computer-readable medium of claim 11 , wherein determining the point of interest is further based at least in part on the historical data of the first user.

13 . The non-transitory computer-readable medium of claim 9 , wherein the destination feature is based on historical data that is specific to the first user.

14 . The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:

storing a first user profile for the first user, the first user profile indicating a preference of the first user for a type of vehicle or a type of transport service;

associating at least the destination feature of the user selection with the preference; and

wherein selecting the service provider is based at least in part on at least one of a type of vehicle operated by the service provider or the type of service provided with the service provider.

15 . The non-transitory computer-readable medium of claim 9 , wherein determining the multiple destination locations includes determining, based on the historical data, that the first user is in a region where the first user has not previously utilized the network service, and wherein the multiple destination locations include a point of interest of the region.

16 . The non-transitory computer-readable medium of claim 9 , wherein the operations further comprise:

receiving, over the one or more networks and via GPS resources of a plurality of service provider devices, a plurality of current locations of a plurality of candidate service providers; and

wherein selecting the service provider from the plurality of candidate service providers includes determining a proximity of each service of the plurality of candidate service providers to the current location of the first user.

17 . A method for providing a network service, the method being implemented by one or more processors of a computing system and comprising:

storing, in a database accessible by computing system, historical data that corresponds to utilization of a network service by a plurality of users, including a first user;

receiving, over the one or more networks and via a GPS resource of a computing device of the first user, a current location of the first user;

based on the historical data, determining multiple destination locations for the first user, each of the multiple destination locations being associated with a corresponding time period that correlates to when a likelihood of the first user requesting a transport service for that destination location exceeds a threshold level;

based at least in part on a current time, the current location of the computing device of the first user, and the corresponding time period associated with each of the multiple destination locations, selecting a destination location of the multiple destination locations to represent as a corresponding destination feature by a service application operating on the computing device of the first user;

transmitting, over the one or more networks, data to the computing device of the first user, the data causing the service application operating on the computing device of the first user to provide, on a display of the computing device, the corresponding destination feature for the selected destination location;

based on the first user selecting the corresponding destination feature, receiving, over the one or more networks from the computing device of the first user, the service request for transporting the first user to the selected destination location; and

processing the service request by selecting, from a plurality of candidate service providers, a service provider to fulfill the service request based, at least in part, on a current location of the service provider, received via a GPS resource of a computing device of the service provider.

18 . The method of claim 17 , wherein the multiple destination locations are based on historical data that is not specific to the first user.

19 . The method of claim 18 , wherein the multiple destination locations include a point of interest within a proximity of the current location of the first user.

20 . The method of claim 19 , wherein determining the point of interest is further based at least in part on the historical data of the first user.

Continuity (4)
Continuation 16440567 · Jun 13, 2019
Continuation 15395341 · Dec 30, 2016
Provisional Application 62399642 · Sep 26, 2016
Related Publication 20240257287A1 · Aug 1, 2024
References Cited (176)
US 5495389A · Dewitt · 1996 [cited by applicant]
US 5598318A · Dewitt · 1997 [cited by applicant]
US 5986891A · Sugimoto · 1999 [cited by applicant]
US 6668177B2 · Salmimaa · 2003 [cited by applicant]
US 7024205B1 · Hose · 2006 [cited by applicant]
US 7519916B1 · Hartwell · 2009 [cited by applicant]
US 7925540B1 · Orttung · 2011 [cited by applicant]
US 8340691B1 · Starenky · 2012 [cited by applicant]
US 8630987B2 · Prada Gomez · 2014 [cited by applicant]
US 8843307B1 · Kolodziej · 2014 [cited by applicant]
US 8976536B2 · French, Jr. · 2015 [cited by applicant]
US 9197696B1 · Jakatdar · 2015 [cited by applicant]
US 9244147B1 · Soundararajan · 2016 [cited by applicant]
US 9922469B1 · Ashton · 2018 [cited by applicant]
US 9990655B2 · MacTiernan · 2018 [cited by applicant]
US 9997863B2 · Matsuura et al. · 2018 [cited by applicant]
US 10356927B2 · Ehlen · 2019 [cited by applicant]
US 10622026B1 · Tsorng · 2020 [cited by applicant]
US 10721327B2 · Cheng · 2020 [cited by applicant]
US 11196838B2 · Cheng · 2021 [cited by applicant]
US 11441921B2 · Vereshshagin · 2022 [cited by applicant]
US 11924308B2 · Cheng · 2024 [cited by applicant]
US 20020034292A1 · Tuoriniemi · 2002 [cited by applicant]
US 20030151332A1 · Chen · 2003 [cited by applicant]
US 20040198366A1 · Crocker · 2004 [cited by applicant]
US 20040202132A1 · Heinonen · 2004 [cited by applicant]
US 20050177799A1 · Knight · 2005 [cited by applicant]
US 20060059023A1 · Mashinsky · 2006 [cited by applicant]
US 20070011233A1 · Manion · 2007 [cited by applicant]
US 20070150375A1 · Yang · 2007 [cited by applicant]
US 20090113296A1 · Lacy · 2009 [cited by applicant]
US 20090296990A1 · Holland · 2009 [cited by applicant]
US 20100030612A1 · Kim · 2010 [cited by applicant]
US 20100076795A1 · Steir · 2010 [cited by applicant]
US 20100097912A1 · Lin · 2010 [cited by applicant]
US 20100179750A1 · Gum · 2010 [cited by examiner]
US 20110016862A1 · Song · 2011 [cited by applicant]
US 20110035142A1 · Tang · 2011 [cited by applicant]
US 20110053552A1 · Kim · 2011 [cited by applicant]
US 20110099040A1 · Felt · 2011 [cited by applicant]
US 20110153629A1 · Lehmann · 2011 [cited by applicant]
US 20110238289A1 · Lehmann · 2011 [cited by applicant]
US 20110307282A1 · Camp · 2011 [cited by applicant]
US 20110310552A1 · Huang · 2011 [cited by applicant]
US 20120150436A1 · Rossano · 2012 [cited by applicant]
US 20120253548A1 · Davidson · 2012 [cited by applicant]
US 20120311584A1 · Gruber · 2012 [cited by applicant]
US 20130036117A1 · Fisher · 2013 [cited by applicant]
US 20130073327A1 · Edelberg · 2013 [cited by applicant]
US 20130090950A1 · Rao · 2013 [cited by applicant]
US 20130132140A1 · Amin · 2013 [cited by examiner]
US 20130138723A1 · Ku · 2013 [cited by applicant]
US 20130185152A1 · Aaron · 2013 [cited by applicant]
US 20130246301A1 · Radhakrishnan · 2013 [cited by applicant]
US 20130268406A1 · Radhakrishnan · 2013 [cited by applicant]
US 20130282283A1 · Bondesen · 2013 [cited by applicant]
US 20130285855A1 · Dupray · 2013 [cited by applicant]
US 20130311997A1 · Gruber · 2013 [cited by applicant]
US 20140040079A1 · Smirin · 2014 [cited by applicant]
US 20140082069A1 · Varoglu · 2014 [cited by applicant]
US 20140129951A1 · Amin · 2014 [cited by applicant]
US 20140164525A1 · Malik · 2014 [cited by applicant]
US 20140195972A1 · Lee · 2014 [cited by applicant]
US 20140221006A1 · Jhanji · 2014 [cited by applicant]
US 20140307386A1 · French, Jr. · 2014 [cited by applicant]
US 20140309789A1 · Ricci · 2014 [cited by examiner]
US 20140364150A1 · Marti · 2014 [cited by examiner]
US 20150012341A1 · Amin · 2015 [cited by applicant]
US 20150039368A1 · Polyakov · 2015 [cited by applicant]
US 20150099461A1 · Holden · 2015 [cited by applicant]
US 20150112919A1 · Weir et al. · 2015 [cited by applicant]
US 20150161564A1 · Sweeney · 2015 [cited by examiner]
US 20150161752A1 · Barreto · 2015 [cited by applicant]
US 20150241239A1 · van Dok · 2015 [cited by applicant]
US 20150248689A1 · Paul · 2015 [cited by applicant]
US 20150339928A1 · Ramanujam · 2015 [cited by applicant]
US 20160006702A1 · Chestnut · 2016 [cited by applicant]
US 20160026936A1 · Richardson · 2016 [cited by applicant]
US 20160027306A1 · Lambert · 2016 [cited by applicant]
US 20160048804A1 · Paul · 2016 [cited by applicant]
US 20160054767A1 · Chen · 2016 [cited by applicant]
US 20160069694A1 · Tao · 2016 [cited by applicant]
US 20160078374A1 · Lippow · 2016 [cited by applicant]
US 20160104112A1 · Gorlin · 2016 [cited by applicant]
US 20160105787A1 · Hammer · 2016 [cited by applicant]
US 20160140789A1 · Wickersham, III · 2016 [cited by applicant]
US 20160165510A1 · Jun · 2016 [cited by applicant]
US 20160171584A1 · Cao · 2016 [cited by applicant]
US 20160203522A1 · Shiffert · 2016 [cited by applicant]
US 20160203576A1 · Novak · 2016 [cited by applicant]
US 20160300318A1 · Godil · 2016 [cited by applicant]
US 20160301698A1 · Katara · 2016 [cited by applicant]
US 20160370194A1 · Colijn · 2016 [cited by applicant]
US 20170013408A1 · Grzywaczewski · 2017 [cited by applicant]
US 20170052034A1 · Magazinik · 2017 [cited by applicant]
US 20170059347A1 · Flier · 2017 [cited by applicant]
US 20170115125A1 · Outwater · 2017 [cited by applicant]
US 20170126837A1 · Wang · 2017 [cited by applicant]
US 20170132540A1 · Haparnas · 2017 [cited by applicant]
US 20170147951A1 · Meyer · 2017 [cited by applicant]
US 20170147959A1 · Sweeney · 2017 [cited by applicant]
US 20170169366A1 · Klein · 2017 [cited by applicant]
US 20170186126A1 · Marco · 2017 [cited by applicant]
US 20170191842A1 · Magazinik · 2017 [cited by applicant]
US 20170193458A1 · Marco · 2017 [cited by applicant]
US 20170220966A1 · Wang · 2017 [cited by applicant]
US 20170240098A1 · Sweeney · 2017 [cited by applicant]
US 20170255881A1 · Ritch · 2017 [cited by applicant]
US 20170255966A1 · Khoury · 2017 [cited by applicant]
US 20170270794A1 · Sweeney · 2017 [cited by applicant]
US 20170272901A1 · Chen · 2017 [cited by applicant]
US 20170357408A1 · Anglin · 2017 [cited by applicant]
US 20180089784A1 · Yamashita · 2018 [cited by applicant]
US 20180091604A1 · Yamashita · 2018 [cited by applicant]
US 20180092057A1 · Yamashita · 2018 [cited by applicant]
US 20180131767A1 · Kozman · 2018 [cited by applicant]
US 20180137594A1 · Marco · 2018 [cited by applicant]
US 20180158166A1 · Tulabandhula · 2018 [cited by applicant]
US 20180189918A1 · Lu · 2018 [cited by applicant]
US 20180285846A1 · Oesterling · 2018 [cited by applicant]
US 20180315021A1 · Bijor · 2018 [cited by applicant]
US 20190045651A1 · Ehlen · 2019 [cited by applicant]
US 20190050775A1 · Bijor · 2019 [cited by applicant]
US 20190109926A1 · Hotchkies · 2019 [cited by applicant]
US 20190130764A1 · Karani · 2019 [cited by applicant]
US 20190230180A1 · Wang · 2019 [cited by applicant]
US 20190295206A1 · Yamashita · 2019 [cited by applicant]
US 20190306258A1 · Yamashita · 2019 [cited by applicant]
US 20200022101A1 · Yamashita · 2020 [cited by applicant]
US 20200081933A1 · Jiang · 2020 [cited by applicant]
US 20200105140A1 · Wang · 2020 [cited by applicant]
US 20200221257A1 · Zhang · 2020 [cited by applicant]
US 20200258386A1 · Lu · 2020 [cited by applicant]
US 20200273337A1 · Sweeney · 2020 [cited by applicant]
US 20200322451A1 · Cheng · 2020 [cited by applicant]
US 20210112674A1 · Ehlen · 2021 [cited by applicant]
US 20210213933A1 · Borrelli · 2021 [cited by applicant]
US 20210337047A1 · Cheng · 2021 [cited by applicant]
US 20220027805A1 · Bijor · 2022 [cited by applicant]
US 20220156338A1 · Jiang · 2022 [cited by applicant]
US 20220172259A1 · Pandit · 2022 [cited by examiner]
US 20220223043A1 · Sweeney · 2022 [cited by applicant]
US 20230147033A1 · Cheng · 2023 [cited by applicant]
US 20230164228A1 · Yamashita · 2023 [cited by applicant]
US 20230334988A1 · Sweeney · 2023 [cited by applicant]
US 20240163349A1 · Cheng · 2024 [cited by applicant]
US 20240257287A1 · Yamashita · 2024 [cited by applicant]
CA 2975002 · 2016 [cited by applicant]
WO WO2010142862 · 2010 [cited by applicant]
WO WO2011067741 · 2011 [cited by applicant]
WO WO2011132181 · 2011 [cited by applicant]
WO WO2014074407 · 2014 [cited by applicant]
Jain et al., “Context based adaptation of application icons in mobile computing devices”, 2013 Third World Congress on Information and Communication Technologies (WICT), pp. 31-36 (Year: 2013). [cited by examiner]
Borison, Rebecca, “Uber Brings its SUV Fleet to NYC”, Jul. 30, 2014, Business Insider, p. 1. [cited by applicant]
Cody Toombs: Maps v.9.19 Introduces New ‘Driving Mode’ with Traffic Update and ETAs, Audio Toggle for Navigation, and Timeline Seetings [APK Download and Teardown], Jan. 12, 2016 URL: http://www.androidpolice. Com/2016/… [cited by applicant]
Darrell Etherington: “Google Maps on Mobile Gets Uber Integration and More” May 6, 2014 URL: https://techcrunch.com /2014/05/06/google-maps-on-mobile- gets-uber-integration-and-more. [cited by applicant]
Edelman, Computing the Mind, Oxford University Press, 2008, pp. xi-36. [cited by applicant]
EESR issued in EP 16735494.3 dated May 18, 2018. [cited by applicant]
Exam Report No. 1 is AU 2016205059 dated Oct. 29, 2020. [cited by applicant]
Goffman, Frame Analysis, Northeastern University Press, 1974, pp. 1-39, 301-344. [cited by applicant]
Gupta, Inside Bluetooth Low Energy, Artech House, 2013, pp. 119-130. [cited by applicant]
Harmon, W., Icy Dock EZConvert MB705M2P-B Review M.2 to U.2 NVMe SSD Adapter, Jul. 5, 2019. [cited by applicant]
Hilen, Brittany, Uber and Google bring WIFI to cars in Philadelphia, Slashgear, dated Jul. 24, 2014, p. 1, https://web.archive.org/web/20140724201314/http://ww.slashgear.com/uber-and-google-bring-wifi-to-cars-in-philade… [cited by applicant]
ISR and Written Opinion in PCT/US2017/053469 dated Dec. 8, 2017. [cited by applicant]
ISR and Written Opinion in PCT/US2018/046496 dated Nov. 28, 2019. [cited by applicant]
ISR and Written Opinion issued Jan. 11, 2018 in PCT/US2017/053514. [cited by applicant]
Jain, “Context based adaptation of application icons in mobile computing devices”, 2013 Third World Congress on Information and Communication Technologies (WICT 2013) pp. 31-36, 2013. [cited by applicant]
Jain, “Contextual Adaptive User Interface for Android Devices”, Annual IEEE India Conference (INDICON), IEEE, pp. 1-4 (2013). [cited by applicant]
Lakoff, Metaphors We Live by, University of Chicago Press, 1980, pp. ix-55. [cited by applicant]
Lin et al. A Model of Multimodel Ridesharing and it's Analysis, 2016 17th IEEE International Conference on Mobile Data Management, pp. 164-173, Jun. 13-16, 2016 (2016). [cited by applicant]
McLaren, Sharing Cities, MIT Press, 2015, pp. 21-69. [cited by applicant]
Office Action in EP 17783640.0 dated Jan. 12, 2021. [cited by applicant]
Trasee, UberEVENTS: A Ride for Every Occasion, Uber Newsroom, Nov. 16, 2015, https://www.uber.com/newsroom/uberevents- a-ride-for-every-occasion/. [cited by applicant]
Wirth, Algorithms + Data Structures = Programs, 1976, pp. xii-55. [cited by applicant]
Written Opinion in PCT/US2018/046496 dated Aug. 5, 2019. [cited by applicant]
Office Action dated Mar. 20, 2024 in CA 3,972,339. [cited by applicant]