IP Library Granted Patent US 12,430,701
Granted Patent B1
US 12,430,701 · App. 16/944,428 · Granted Sep 30, 2025

Dynamically generating geospatial-based-proportion metrics based on transportation events relative to geocoded areas

Inventors: Praveen Athmanathan Panneer Selvam (Sunnyvale, CA); Davide Crapis (San Francisco, CA); Daniel Freund (New York, NY); Jiayu Gong (Fremont, CA); Jae Ik Jin (San Francisco, CA); Hao Yi Ong (San Francisco, CA); Shengke Zhou (San Bruno, CA)
Assignee: Lyft, Inc.
G06Q50/40G06Q10/06393
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,430,701
App. No.
16/944,428
Granted
Sep 30, 2025
Kind
B1
Abstract

This disclosure describes methods, non-transitory computer readable media, and systems that can determine locations and geospatial scores for pick-up events and other transportation events relative to geocoded areas at a given time period and generate geospatial-based proportion metrics for provider devices corresponding to such transportation events as proportional premiums for performing the events. For example, the systems determine locations of provider devices across geocoded areas for a particular time period. The systems can generate geospatial scores for transportation events of the provider devices occurring within the time period based on the specific locations and times of the events relative to the geocoded areas. Based on the geospatial scores and cumulative metrics accounting for such transportation events relative to the geocoded areas, the systems can generate geospatial-based-proportion metrics corresponding to such events for a graphical display on provider devices.

Claims (77)

1. A method comprising:

determining, by one or more servers of a transportation matching system, locations of provider devices across geocoded areas for a time period based on GPS locators of the provider devices providing GPS data associated with the provider devices at regular intervals during the time period to the one or more servers;

generating, by the one or more servers of the transportation matching system and based on the GPS data provided by the provider devices at the regular intervals, geospatial scores for transportation events of the provider devices during the time period relative to the geocoded areas comprising measurement representations of particular locations and particular times of the transportation events relative to the geocoded areas, the transportation events occurring as part of transportation requests assigned to the provider devices and the geospatial scores indicating measurements of distances and times from the transportation events to the geocoded areas, the transportation events comprising pick-up events, drop-off events, or movement of the provider devices occurring as part of the transportation requests relative to the geocoded areas;

determining, by the one or more servers of the transportation matching system utilizing the GPS data provided by the provider devices at the regular intervals and for the geocoded areas, cumulative-events metrics indicating cumulative values of the transportation events occurring within or through the geocoded areas and during the time period by incrementing the cumulative values stored in geocode-specific repositories for the geocoded areas each time a pick-up event, a drop-off event, or a tracked movement of a provider occurs as part of a transportation request within or through the geocoded areas;

generating geospatial-based-proportion metrics for the transportation events based on combinations of the geospatial scores of the transportation events and portions of the cumulative-events metrics from the geocode-specific repositories of corresponding geocoded areas;

generating, in response to a provider device of the provider devices approaching one or more target geocoded areas, a heatmap indicating an inner zone surrounding one or more target geocoded areas, an outer zone surrounding the inner zone, a location of the provider device relative to the inner zone and the outer zone, and the geospatial-based-proportion metrics of the transportation events occurring within or through the one or more target geocoded areas; and

providing the heatmap for display within a map in a mapping interface of a provider application of the provider device.

2. The method of claim 1 , wherein determining a cumulative-events metric for a particular geocoded area comprises:

incrementing, for each transportation event within the particular geocoded area for the time period, a value for the cumulative-events metric corresponding to the particular geocoded area; and

storing the cumulative-events metric in a geocode-specific repository for the particular geocoded area.

3. The method of claim 2 , further comprising:

determining a difference between the cumulative-events metric stored in the geocode-specific repository for the particular geocoded area and a cumulation of the geospatial-based-proportion metrics for the particular geocoded area and the time period; and

generating premiums for the provider devices according to the geospatial-based-proportion metrics based on the cumulative-events metric stored in the geocode-specific repository and a cumulative-reserve metric from a regional repository for the geocoded areas.

4. The method of claim 1 , further comprising:

providing, for display by the provider device of the provider devices, customized instructions guiding a transportation vehicle corresponding to the provider device toward a target geocoded area of the one or more target geocoded areas based on the location of the provider device relative to the target geocoded area for the time period;

providing, in response to detecting the provider device of the provider device traveling to a target geocoded area, an indication of a premium for the provider device according to a geospatial-based-proportion metric for the target geocoded area; and

scaling the heatmap to include the location of the provider device, the inner zone surrounding the one or more target geocoded areas, and the outer zone surrounding the inner zone within the mapping interface.

5. The method of claim 1 , wherein determining a cumulative-events metric for a particular geocoded area of the geocoded areas and the time period comprises:

determining an allocation of provider devices across the geocoded areas based on the locations of the provider devices and a projected number of transportation requests across the geocoded areas for the time period;

determining a transportation-value metric for the particular geocoded area for the time period based on the allocation of provider devices and a target number of provider devices within the particular geocoded area to receive premiums according to the geospatial-based-proportion metrics; and

determining the cumulative-events metric for the particular geocoded area and the time period based on a number of transportation requests within the particular geocoded area for the time period and the transportation-value metric.

6. The method of claim 1 , wherein generating the geospatial-based-proportion metrics further comprises:

determining a target premium metric for a particular geocoded area based on an allocation of provider devices across the geocoded areas;

iteratively adjusting a value for a premium metric for the particular geocoded area to reduce a difference between the premium metric and the target premium metric; and

generating the geospatial-based-proportion metrics based further on the adjusted value of the premium metric.

7. The method of claim 6 , further comprising iteratively adjusting the value for the premium metric to reduce the difference between the premium metric and the target premium metric based in part on a balanced-treatment constraint by comparing the premium metric according to an allocation-flow matrix for the geocoded areas to cumulative-event metrics and cumulative-reserve metrics according to a contribution matrix for the geocoded areas.

8. A system comprising:

at least one processor; and

a non-transitory computer readable storage medium comprising instructions that, when executed by the at least one processor, cause the system to:

determine, by one or more servers of a transportation matching system, locations of provider devices across geocoded areas for a time period based on GPS locators of the provider devices providing GPS data associated with the provider devices at regular intervals during the time period to the one or more servers;

generate, by the one or more servers of the transportation matching system and based on the GPS data provided by the provider devices at the regular intervals, geospatial scores for transportation events of the provider devices during the time period relative to the geocoded areas comprising measurement representations of particular locations and particular times of the transportation events relative to the geocoded areas, the transportation events occurring as part of transportation requests assigned to the provider devices and the geospatial scores indicating measurements of distances and times from the transportation events to the geocoded areas, the transportation events comprising pick-up events, drop-off events, or movement of the provider devices occurring as part of the transportation requests relative to the geocoded areas;

determine, by the one or more servers of the transportation matching system utilizing the GPS data provided by the provider devices at the regular intervals and for the geocoded areas, cumulative-events metrics indicating cumulative values of the transportation events occurring within or through the geocoded areas and during the time period by incrementing the cumulative values stored in geocode-specific repositories for the geocoded areas each time a pick-up event, a drop-off event, or a tracked movement of a provider occurs as part of a transportation request within or through the geocoded areas;

generate geospatial-based-proportion metrics for the transportation events based on combinations of the geospatial scores of the transportation events and portions of the cumulative-events metrics from the geocode-specific repositories of corresponding geocoded areas;

generate, in response to a provider device of the provider devices approaching one or more target geocoded areas, a heatmap indicating an inner zone surrounding one or more target geocoded areas, an outer zone surrounding the inner zone, a location of the provider device relative to the inner zone and the outer zone, and the geospatial-based-proportion metrics of the transportation events occurring within or through the one or more target geocoded areas; and

providing the heatmap for display within a map in a mapping interface of a provider application of the provider device.

9. The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine a cumulative-events metric for a particular geocoded area by:

incrementing, for each transportation event within the particular geocoded area for the time period, a value for the cumulative-events metric corresponding to the particular geocoded area; and

storing the cumulative-events metric in a geocode-specific repository for the particular geocoded area.

10. The system of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the system to:

determine a difference between the cumulative-events metric stored in the geocode-specific repository for the particular geocoded area and a cumulation of the geospatial-based-proportion metrics for the particular geocoded area and the time period; and

generate premiums for the provider devices according to the geospatial-based-proportion metrics based on the cumulative-events metric stored in the geocode-specific repository and a cumulative-reserve metric from a regional repository for the geocoded areas.

11. The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to:

provide, for display by the provider device of the provider devices, customized instructions guiding a transportation vehicle toward a target geocoded area from a first geocoded area of the geocoded areas based on the location of the provider device across the geocoded areas for the time period, the customized instructions comprising indications of premiums for the provider device according to the geospatial-based-proportion metrics;

cause the provider device to display the heatmap including the target geocoded area and the location of the provider device while modifying the location of the provider device to reflect movement of the transportation vehicle toward the target geocoded area.

12. The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine a cumulative-events metric for a particular geocoded area of the geocoded areas and the time period by:

determining an allocation of provider devices across the geocoded areas based on the locations of the provider devices and a projected number of transportation requests across the geocoded areas for the time period;

determining a transportation-value metric for the particular geocoded area for the time period based on the allocation of provider devices and a target number of provider devices within the particular geocoded area to receive premiums according to the geospatial-based-proportion metrics; and

determining the cumulative-events metric for the particular geocoded area and the time period based on a number of transportation requests within the particular geocoded area for the time period and the transportation-value metric.

13. The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to generate the geospatial-based-proportion metrics by:

determining a target premium metric for a particular geocoded area based on an allocation of provider devices across the geocoded areas;

iteratively adjusting a value for a premium metric for the particular geocoded area to reduce a difference between the premium metric and the target premium metric; and

generating the geospatial-based-proportion metrics based further on the adjusted value of the premium metric.

14. The system of claim 13 , further comprising instructions that, when executed by the at least one processor, cause the system to iteratively adjust the value for the premium metric to reduce the difference between the premium metric and the target premium metric based in part on a balanced-treatment constraint by comparing the premium metric according to an allocation-flow matrix for the geocoded areas to cumulative-event metrics and cumulative-reserve metrics according to a contribution matrix for the geocoded areas.

15. A non-transitory computer readable storage medium comprising instructions that, when executed by at least one processor, cause a computing device to:

determine, by one or more servers of a transportation matching system, locations of provider devices across geocoded areas for a time period based on GPS locators of the provider devices providing GPS data associated with the provider devices at regular intervals during the time period to the one or more servers;

generate, by the one or more servers of the transportation matching system and based on the GPS data provided by the provider devices at the regular intervals, geospatial scores for transportation events of the provider devices during the time period relative to the geocoded areas comprising measurement representations of particular locations and particular times of the transportation events relative to the geocoded areas, the transportation events occurring as part of transportation requests assigned to the provider devices and the geospatial scores indicating measurements of distances and times from the transportation events to the geocoded areas, the transportation events comprising pick-up events, drop-off events, or movement of the provider devices occurring as part of the transportation requests relative to the geocoded areas;

determine, by the one or more servers of the transportation matching system utilizing the GPS data provided by the provider devices at the regular intervals and for the geocoded areas, cumulative-events metrics indicating cumulative values of the transportation events occurring within or through the geocoded areas and during the time period by incrementing the cumulative values stored in geocode-specific repositories for the geocoded areas each time a pick-up event, a drop-off event, or a tracked movement of a provider occurs as part of a transportation request within or through the geocoded areas;

generate geospatial-based-proportion metrics for the transportation events based on combinations of the geospatial scores of the transportation events and portions of the cumulative-events metrics from the geocode-specific repositories of corresponding geocoded areas;

generate, in response to a provider device of the provider devices approaching one or more target geocoded areas, a heatmap indicating an inner zone surrounding one or more target geocoded areas, an outer zone surrounding the inner zone, a location of the provider device relative to the inner zone and the outer zone, and the geospatial-based-proportion metrics of the transportation events occurring within or through the one or more target geocoded areas; and

providing the heatmap for display within a map in a mapping interface of a provider application of the provider device.

16. The non-transitory computer readable storage medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine a cumulative-events metric for a particular geocoded area by:

incrementing, for each transportation event within the particular geocoded area for the time period, a value for the cumulative-events metric corresponding to the particular geocoded area; and

storing the cumulative-events metric in a geocode-specific repository for the particular geocoded area.

17. The non-transitory computer readable storage medium of claim 16 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:

determine a difference between the cumulative-events metric stored in the geocode-specific repository for the particular geocoded area and a cumulation of the geospatial-based-proportion metrics for the particular geocoded area and the time period; and

generate premiums for the provider devices according to the geospatial-based-proportion metrics based on the cumulative-events metric stored in the geocode-specific repository and a cumulative-reserve metric from a regional repository for the geocoded areas.

18. The non-transitory computer readable storage medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:

provide, for display by the provider device of the provider devices, customized instructions guiding a transportation vehicle associated with the provider device toward the one or more target geocoded areas based on the location of the provider device; and

provide the heatmap for display by the provider device by centering the mapping interface around the location of the provider device while scaling the heatmap to include the one or more target geocoded areas.

19. The non-transitory computer readable storage medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine a cumulative-events metric for a particular geocoded area of the geocoded areas and the time period by:

determining an allocation of provider devices across the geocoded areas based on the locations of the provider devices and a projected number of transportation requests across the geocoded areas for the time period;

determining a transportation-value metric for the particular geocoded area for the time period based on the allocation of provider devices and a target number of provider devices within the particular geocoded area to receive premiums according to the geospatial-based-proportion metrics; and

determining the cumulative-events metric for the particular geocoded area and the time period based on a number of transportation requests within the particular geocoded area for the time period and the transportation-value metric.

20. The non-transitory computer readable storage medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to generate the geospatial-based-proportion metrics by:

determining a target premium metric for a particular geocoded area based on an allocation of provider devices across the geocoded areas;

iteratively adjusting a value for a premium metric for the particular geocoded area to reduce a difference between the premium metric and the target premium metric; and

generating the geospatial-based-proportion metrics based further on the adjusted value of the premium metric.

Assignments (2)
SECURITY INTEREST Recorded Nov 3, 2022
From: LYFT, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 061880/0237 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2020
From: ATHMANATHAN PANNEER SELVAM, PRAVEEN; CRAPIS, DAVIDE; FREUND, DANIEL; GONG, JIAYU; JIN, JAE IK; ONG, HAO YI; ZHOU, SHENGKE
To: LYFT, INC.
Reel/Frame 053535/0972 →
References Cited (158)
US 7663528B1 · Malakian et al. · 2010 [cited by applicant]
US 9358986B2 · Hunt · 2016 [cited by applicant]
US 9864778B1 · Strand et al. · 2018 [cited by applicant]
US 10032181B1 · Madhow et al. · 2018 [cited by applicant]
US 10157436B2 · Samocha et al. · 2018 [cited by applicant]
US 10552773B1 · Shah et al. · 2020 [cited by applicant]
US 10706487B1 · Chachra et al. · 2020 [cited by applicant]
US 10794713B2 · Magazinik et al. · 2020 [cited by applicant]
US 11035683B2 · Marco · 2021 [cited by applicant]
US 11514546B2 · Chachra et al. · 2022 [cited by applicant]
US 11551139B1 · Finamore · 2023 [cited by examiner]
US 11763411B1 · Chachra et al. · 2023 [cited by applicant]
US 11887483B2 · Bajaj et al. · 2024 [cited by applicant]
US 20050015316A1 · Salluzzo · 2005 [cited by applicant]
US 20050021225A1 · Kantarjiev et al. · 2005 [cited by applicant]
US 20060069601A1 · Simon et al. · 2006 [cited by applicant]
US 20080195428A1 · O'Sullivan · 2008 [cited by applicant]
US 20090119006A1 · Silver et al. · 2009 [cited by applicant]
US 20090210262A1 · Clark et al. · 2009 [cited by applicant]
US 20090325556A1 · Lee et al. · 2009 [cited by applicant]
US 20100268450A1 · Stephen · 2010 [cited by applicant]
US 20110161116A1 · Peak et al. · 2011 [cited by applicant]
US 20110184640A1 · Coleman et al. · 2011 [cited by applicant]
US 20110246404A1 · Lehmann et al. · 2011 [cited by applicant]
US 20120246039A1 · Fain et al. · 2012 [cited by applicant]
US 20120316763A1 · Haynes, III et al. · 2012 [cited by applicant]
US 20130041708A1 · Jackson, Jr. et al. · 2013 [cited by applicant]
US 20130132140A1 · Amin et al. · 2013 [cited by applicant]
US 20130246207A1 · Novak et al. · 2013 [cited by applicant]
US 20130253969A1 · Das et al. · 2013 [cited by applicant]
US 20140129951A1 · Amin et al. · 2014 [cited by applicant]
US 20140156410A1 · Wuersch et al. · 2014 [cited by applicant]
US 20140172439A1 · Conway et al. · 2014 [cited by applicant]
US 20140207375A1 · Lerenc · 2014 [cited by applicant]
US 20140279654A1 · Lievens et al. · 2014 [cited by applicant]
US 20140337123A1 · Nuernberg et al. · 2014 [cited by applicant]
US 20140358435A1 · Bell et al. · 2014 [cited by applicant]
US 20150039214A1 · Mcclellan et al. · 2015 [cited by applicant]
US 20150046080A1 · Wesselius et al. · 2015 [cited by applicant]
US 20150081399A1 · Mitchell et al. · 2015 [cited by applicant]
US 20150154810A1 · Tew et al. · 2015 [cited by applicant]
US 20150161554A1 · Sweeney et al. · 2015 [cited by applicant]
US 20150161564A1 · Sweeney et al. · 2015 [cited by applicant]
US 20150206267A1 · Khanna et al. · 2015 [cited by applicant]
US 20150242772A1 · Backof, II et al. · 2015 [cited by applicant]
US 20150262430A1 · Farrelly et al. · 2015 [cited by applicant]
US 20150339928A1 · Ramanujam · 2015 [cited by applicant]
US 20150371157A1 · Jaffe · 2015 [cited by applicant]
US 20150379437A1 · Reich · 2015 [cited by applicant]
US 20160026936A1 · Richardson et al. · 2016 [cited by applicant]
US 20160027307A1 · Abhyanker et al. · 2016 [cited by applicant]
US 20160034845A1 · Hiyama et al. · 2016 [cited by applicant]
US 20160098649A1 · Ifrach et al. · 2016 [cited by applicant]
US 20160117610A1 · Ikeda et al. · 2016 [cited by applicant]
US 20160148164A1 · Luk et al. · 2016 [cited by applicant]
US 20160171574A1 · Paulucci et al. · 2016 [cited by applicant]
US 20160171882A1 · Handley · 2016 [cited by applicant]
US 20160209220A1 · Laetz · 2016 [cited by applicant]
US 20160320198A1 · Liu et al. · 2016 [cited by applicant]
US 20160321566A1 · Liu et al. · 2016 [cited by applicant]
US 20170034110A1 · Bijor et al. · 2017 [cited by applicant]
US 20170061801A1 · Huang et al. · 2017 [cited by applicant]
US 20170098377A1 · Marco et al. · 2017 [cited by applicant]
US 20170102243A1 · Samocha et al. · 2017 [cited by applicant]
US 20170124506A1 · Khan · 2017 [cited by applicant]
US 20170147951A1 · Meyer et al. · 2017 [cited by applicant]
US 20170154348A1 · Biswas et al. · 2017 [cited by applicant]
US 20170169366A1 · Klein et al. · 2017 [cited by applicant]
US 20170169377A1 · Liu et al. · 2017 [cited by applicant]
US 20170169535A1 · Tolkin et al. · 2017 [cited by applicant]
US 20170191842A1 · Igor et al. · 2017 [cited by applicant]
US 20170227370A1 · O'Mahony · 2017 [cited by examiner]
US 20170262790A1 · Khasis · 2017 [cited by applicant]
US 20170353536A1 · Shraer et al. · 2017 [cited by applicant]
US 20170372235A1 · Dayama et al. · 2017 [cited by applicant]
US 20180025407A1 · Zhang et al. · 2018 [cited by applicant]
US 20180032928A1 · Li et al. · 2018 [cited by applicant]
US 20180075380A1 · Perl et al. · 2018 [cited by applicant]
US 20180101878A1 · Marueli et al. · 2018 [cited by applicant]
US 20180121847A1 · Zhao · 2018 [cited by examiner]
US 20180121958A1 · Aist et al. · 2018 [cited by applicant]
US 20180158322A1 · McDonnell et al. · 2018 [cited by applicant]
US 20180174446A1 · Wang · 2018 [cited by applicant]
US 20180190040A1 · Batten et al. · 2018 [cited by applicant]
US 20180211541A1 · Rakah et al. · 2018 [cited by applicant]
US 20180225796A1 · Liu · 2018 [cited by examiner]
US 20180232840A1 · Liu · 2018 [cited by applicant]
US 20190066251A1 · Samocha et al. · 2019 [cited by applicant]
US 20190080340A1 · Berger · 2019 [cited by examiner]
US 20190295259A1 · Deskevich · 2019 [cited by applicant]
US 20190340928A1 · Goldman et al. · 2019 [cited by applicant]
US 20200082313A1 · Crapis et al. · 2020 [cited by applicant]
US 20200082315A1 · Crapis et al. · 2020 [cited by applicant]
US 20200250600A1 · Gupta et al. · 2020 [cited by applicant]
US 20210072035A1 · Magazinik et al. · 2021 [cited by applicant]
US 20210192292A1 · Zhai · 2021 [cited by applicant]
US 20210192555A1 · Tang · 2021 [cited by examiner]
US 20220187084A1 · Qin et al. · 2022 [cited by applicant]
US 20240070571A1 · Mayer et al. · 2024 [cited by applicant]
WO WO2020159431A1 · 2020 [cited by examiner]
Ma, et al. “Spatio-temporal pricing for ridesharing platforms.” Operations Research 70.2 (2022): 1025-1041. [online], [retrieved on Dec. 17, 2022]. Retrieved from the Internet <https://arxiv.org/abs/1801.04015> (Year: 2… [cited by examiner]
Lyft Help; “Personal Power Zones”; Date downloaded Jan. 12, 2022; https://help.lyft.com/hc/e/articles/115012926807-Personal-Power-Zones. [cited by applicant]
European Search Report for European Patent Application No. EP 17195935.6, mailed Dec. 11, 2017, 9 pages. [cited by applicant]
Office Action as received in European Application 17195935.6 dated Oct. 18, 2019. [cited by applicant]
Summons to attend oral proceedings as received in European Application 17195935.6 dated Jun. 16, 2020. [cited by applicant]
Office Action as received in Israeli Application 254949 dated Sep. 24, 2019. [cited by applicant]
Office Action as received in Israeli Application 254949 dated Jul. 26, 2020. [cited by applicant]
U.S. Appl. No. 16/539,965, Jun. 8, 2021, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Aug. 29, 2017, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Feb. 21, 2018, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, May 29, 2018, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Dec. 17, 2018, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Apr. 4, 2019, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Sep. 16, 2019, Office Action. [cited by applicant]
U.S. Appl. No. 14/985,565, Jun. 4, 2020, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 15/290,366, Jun. 25, 2019, Office Action. [cited by applicant]
U.S. Appl. No. 15/290,366, Jan. 10, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 15/290,366, May 13, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 15/290,366, Oct. 27, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 15/290,366, Mar. 22, 2021, Office Action. [cited by applicant]
U.S. Appl. No. 14/880,021, Jan. 13, 2017, Office Action. [cited by applicant]
U.S. Appl. No. 14/880,021, Jul. 11, 2017, Office Action. [cited by applicant]
U.S. Appl. No. 14/880,021, Dec. 5, 2017, Office Action. [cited by applicant]
U.S. Appl. No. 14/880,021, Apr. 17, 2018, Office Action. [cited by applicant]
U.S. Appl. No. 14/880,021, Aug. 23, 2018, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 16/177,085, Nov. 5, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 16/177,085, Mar. 25, 2021, Office Action. [cited by applicant]
U.S. Appl. No. 16/177,085, Jul. 18, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 16/780,712, Jun. 24, 2022, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 16/921,698, Jul. 26, 2022, Notice of Allowance. [cited by applicant]
Chawdhry, Amit, Uber: Users are more likely to pay surge pricing if their phone battery is low, May 25, 2016. Forbes.com https://www.forbes.conn/sites/annitchowdhry/2016/05/25/uber-low-battery/#732fbb8074b3 (Year: 2016). [cited by applicant]
U.S. Appl. No. 16/125,563, Nov. 30, 2018, Office Action. [cited by applicant]
U.S. Appl. No. 16/125,563, May 1, 2019, Office Action. [cited by applicant]
U.S. Appl. No. 16/125,563, Oct. 8, 2019, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 16/125,551, Aug. 14, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 16/125,527, Aug. 18, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 16/125,540, Aug. 19, 2020, Office Action. [cited by applicant]
U.S. Appl. No. 15/810,028, Dec. 2, 2019, Office Action. [cited by applicant]
U.S. Appl. No. 15/810,028, Apr. 30, 2019, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 15/290,366, Jun. 29, 2021, Office Action. [cited by applicant]
U.S. Appl. No. 16/177,085, Feb. 18, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 16/780,712, Mar. 25, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 16/921,698, Mar. 31, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 17/063,403, Dec. 28, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 17/063,403, Mar. 22, 2023, Notice of Allowance. [cited by applicant]
Alexander et al., Origin-destination trips by purpose and time of day inferred from mobile phone data, 2015, Elsevier, Transportation Research Part C 58, pp. 240-250 (Year: 2015). [cited by applicant]
U.S. Appl. No. 16/539,965, Apr. 21, 2023, Office Action. [cited by applicant]
U.S. Appl. No. 18/059,071, Mar. 30, 2023, Office Action. [cited by applicant]
U.S. Appl. No. 18/059,071, May 2, 2023, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 16/539,965, Sep. 26, 2022, Office Action. [cited by applicant]
U.S. Appl. No. 16/177,085, Oct. 27, 2022, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 16/539,965, Oct. 26, 2023, Office Action. [cited by applicant]
U.S. Appl. No. 18/469,127, Apr. 11, 2024, Office Action. [cited by applicant]
U.S. Appl. No. 18/469,127, May 15, 2024, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 18/048,545, Jul. 2, 2024, Office Action. [cited by applicant]
U.S. Appl. No. 18/048,545, Nov. 26, 2024, Notice of Allowance. [cited by applicant]
U.S. Appl. No. 17/554,530, Mar. 6, 2025, Office Action. [cited by applicant]
U.S. Appl. No. 18/356,101, Jul. 3, 2025, Office Action. [cited by applicant]
Cited By (1)
US 12,679,408