IP Library Granted Patent US 10,547,972
Granted Patent B2
US 10,547,972 · App. 15/985,436 · Granted Jan 28, 2020

Method for requesting transportation services

Inventors: Olaf Martin Lubeck (Santa Fe, NM); John H. Hall (Alexandria, VA)
Assignee: Lyft, Inc.
H04W4/023G01C21/3667G06Q50/30G08G1/123G08G1/202G08G1/205H04L61/605H04L67/26H04M1/0202H04W4/02H04W4/029H04W4/12H04W8/24H05K999/99G01S13/46G01S19/13G01S2013/468G06Q2240/00H04M2250/10H04W8/22H04W84/042
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 10,547,972
App. No.
15/985,436
Granted
Jan 28, 2020
Kind
B2
Abstract

A method for safely and efficiently requesting transportation services through the use of mobile communications devices capable of geographic location is described. Individual and package transportation may be provided. New customers may be efficiently serviced, and the requester and transportation provider locations may be viewed in real time on the mobile devices.

Claims (45)

1. A method for managing transportation services, the method comprising:

receiving, from a first requester device, a first transportation request that indicates a first location of the first requester device and, from a second requester device, a second transportation request that indicates a second location of the second requester device;

providing, for presentation within a map displayed on a transporter device, the first location of the first requester device and the second location of the second requester device;

receiving, from the first requester device, an indication of an updated location of the first requester device;

providing the updated location of the first requester device for presentation within the map displayed on the transporter device;

determining, based on communications with the transporter device, that a transporter associated with the transporter device will service the first transportation request and providing, to the first requester device, an acknowledgement message comprising identification of the transporter associated with the transporter device that will service the first transportation request.

2. The method of claim 1 , further comprising receiving a confirmation from the transportation device indicating that the transporter will service the first transportation request.

3. The method of claim 2 , wherein the confirmation comprises a selection of the first location within the map displayed on the transporter device.

4. The method of claim 2 , wherein the confirmation from the transportation device comprises a unique identifier associated with the first transportation request.

5. The method of claim 1 , wherein the first transportation request further indicates one or more of a number of individuals to be transported, a number of packages to deliver, a package size, a package weight, or a type of material to be transported.

6. The method of claim 1 , further comprising:

determining that no transporter is available to service the second transportation request; and

in response to determining that no transporter is available to service the second transportation request, providing a notification to the second requester device.

7. The method of claim 1 , further comprising tracking movement of the first requester device by periodically receiving location information from the first requester device.

8. The method of claim 1 , further comprising receiving the updated location of the first requester device and providing the updated location for presentation within the map on the transporter device in real time.

9. The method of claim 1 , further comprising dispatching the transporter device to service the first transportation request.

10. A system for managing transportation services, the system comprising:

at least one processor; and

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

receive, from a first requester device, a first transportation request that indicates a first location of the first requester device and, from a second requester device, a second transportation request that indicates a second location of the second requester device;

provide, for presentation within a map displayed on a transporter device, the first location of the first requester device and the second location of the second requester device;

receive, from the first requester device, an indication of an updated location of the first requester device;

provide the updated location of the first requester device for presentation within the map displayed on the transporter device;

determine, based on communications with the transporter device, that a transporter associated with the transporter device will service the first transportation request; and

provide, to the first requester device, an acknowledgement message comprising identification of the transporter associated with the transporter device that will service the first transportation request.

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

determine that no transporter is available to service the second transportation request; and

in response to determining that no transporter is available to service the second transportation request, provide a notification to the second requester device.

12. The system of claim 11 , wherein the instructions cause the system to determine that there is no transporter available to service the second transportation request by determining that no transporter device has provided a confirmation for the second transportation request within a time limit.

13. The system of claim 10 , further comprising instructions that, when executed by the at least one processor, cause the system to track movement of the first requester device by periodically receiving location information from the first requester device.

14. The system of claim 10 , further comprising instructions that, when executed by the at least one processor, cause the system to store, in a digital storage, transportation request information indicating the first transportation request and the first location of the first requester device.

15. The system of claim 14 , further comprising instructions that, when executed by the at least one processor, cause the system to store, in the digital storage, transportation request information indicating the second transportation request and the second location of the second requester device.

16. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to, based on receiving the indication of the updated location of the first requester device, store, in the digital storage, location information indicating the updated location of the first requester device.

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

receive, from a first requester device, a first transportation request that indicates a first location of the first requester device and, from a second requester device, a second transportation request that indicates a second location of the second requester device;

provide, for presentation within a map displayed on a transporter device, the first location of the first requester device and the second location of the second requester device;

receive, from the first requester device, an indication of an updated location of the first requester device;

provide the updated location of the first requester device for presentation within the map displayed on transporter device;

determine, based on communications with the transporter device, that a transporter associated with the transporter device will service the first transportation request; and

provide, to the first requester device, an acknowledgement message comprising identification of the transporter associated with the transporter device that will service the first transportation request.

18. The non-transitory computer readable medium of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the computer device to track movement of the first requester device by periodically receiving location information from the first requester device.

19. The non-transitory computer readable medium of claim 18 , further comprising instructions that, when executed by the at least one processor, cause the computer device to store, in a digital storage, transportation request information indicating the first location of the first requester device.

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

determine that no transporter is available to service the second transportation request; and

in response to determining that no transporter is available to service the second transportation request, provide a notification to the second requester device.

Assignments (4)
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 Jan 18, 2019
From: PROSPER TECHNOLOGY, LLC
To: LYFT, INC.
Reel/Frame 048060/0649 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 21, 2018
From: LUBECK, OLAF M.; HALL, JOHN H.
To: AIRSMOBILE INC.
Reel/Frame 045865/0414 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 21, 2018
From: AIRSMOBILE, INC.
To: PROSPER TECHNOLOGY, LLC
Reel/Frame 045865/0417 →
Continuity (10)
Continuation 15470553 · Mar 27, 2017
Continuation 15446991 · Mar 1, 2017
Continuation 15429779 · Feb 10, 2017
Continuation 15177762 · Jun 9, 2016
Continuation 14745346 · Jun 19, 2015
Continuation 13413492 · Mar 6, 2012
Continuation 12348850 · Jan 5, 2009
Provisional Application 61027508 · Feb 11, 2008
Provisional Application 61009839 · Jan 3, 2008
Related Publication 20180268706A1 · Sep 20, 2018