IP Library Granted Patent US 11,087,286
Granted Patent B2
US 11,087,286 · App. 15/411,840 · Granted Aug 10, 2021

Method and system for scheduling a ride service for one or more third parties

Inventors: Ritu Narayan (San Carlos, CA); Vivek Garg (San Mateo, CA); Abhishek Garg (Cambridge, MA)
Assignee: Zum Services, Inc.
G06Q10/1093H04L51/32H04L67/10H04L67/16H04L67/18G06Q50/01H04W4/02H04W4/40
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 11,087,286
App. No.
15/411,840
Granted
Aug 10, 2021
Kind
B2
Abstract

This disclosure generally relates to a method and system for requesting a ride for a third party rider. In one embodiment, a user device may be used to transmit a ride request to a server for a third party rider. The user device may receive an indication of a driver from a set of trusted drivers among a pool of drivers. Further, the user device and a device associated with the third party user may receive a ride confirmation.

Claims (61)

1. A method of requesting a ride for a third party rider by a ride requestor, comprising:

transmitting, by a user device, a wireless ride request to a server for a third party rider;

identifying, by the server, a previous ride requester who previously requested a ride from a driver from a set of trusted drivers among a pool of drivers, wherein the previous ride requestor is within a social network sphere of the user;

receiving, by the user device, from the server, the identification of the previous ride requester who previously requested a ride from the driver from the set of trusted drivers among the pool of drivers, wherein the previous ride requestor is within the social network sphere of the user;

displaying, by the user device, the identification of the previous ride requestor who is within the social network sphere of the user on a display screen of the user device;

receiving, by the user device, an identification of the driver from the set of trusted drivers among the pool of drivers who previously gave a ride to the previous ride requestor who is within the social network sphere of the user;

displaying, by the user device, the identification of the driver on the display screen of the user device;

transmitting, by a user device, a password set by the user to a device associated with the driver;

transmitting, by a user device, the password set by the user to a device associated with the third party rider;

determining, by the third party rider, that the password associated with the driver and the password associated with the third party rider match;

receiving, by the user device, a ride confirmation message, the ride confirmation message including a ride itinerary;

displaying, by the user device, the ride confirmation message including the ride itinerary on the display screen of the user device;

receiving, by the user device, a calculated distance and estimated time of arrival;

displaying, by the user device, the calculated distance and estimated time of arrival on the display screen of the user device;

receiving, by the user device, a real time status update of the requested ride that includes an updated current location of the driver and an updated drop off time; and

displaying, by the user device, the real time status update of the requested ride that includes the updated currently location of the driver and the drop off time on the display screen of the user device.

2. The method of claim 1 , wherein the ride request includes an identification of a third party rider.

3. The method of claim 2 , wherein the identification of the third party rider includes a pictorial representation of the third party rider.

4. The method of claim 1 , wherein the ride request further includes a pickup location and a dropoff location.

5. The method of claim 1 , wherein the ride request further includes a pickup time.

6. The method of claim 1 , wherein the ride request further includes a dropoff time.

7. The method of claim 1 , wherein the set of trusted drivers include drivers who have previously provided driving services to family members of the ride requestor.

8. The method of claim 1 , wherein the set of trusted drivers includes drivers who have previously provided driving services to members of at least one social network who are connected with the ride requestor on that at least one social network.

9. The method of claim 1 , wherein the ride confirmation includes identification information for a vehicle associated with the driver.

10. The method of claim 1 , wherein upon receiving, by the user device, the real-time status update of the requested ride transmitting, by the user device, an alternate dropoff address for an additional third party rider.

11. A system for requesting a ride for a third party rider by a ride requestor, comprising:

a user device, including a processor to:

transmit a wireless ride request to a server for a third party rider;

transmit a dropoff contact information;

identify, by the server, a previous ride requester who previously requested a ride from a driver from a set of trusted drivers among a pool of drivers, wherein the previous ride requestor is within a social network sphere of the user;

receive, from the server, an identification of the previous ride requester who previously requested the ride from the driver from the set of trusted drivers among the pool of drivers, wherein the previous ride requestor is within the social network sphere of the user;

display, by the user device, the identification of the previous ride requestor who is within the social network sphere of the user on a display screen of the user device,

receive, from the server, an identification of a driver from a set of trusted drivers among a pool of drivers who previously gave a ride to the previous ride requestor who is within the social network sphere of the user;

display, by the user device, the identification of the driver on the display screen of the user device;

transmit a password set by the user to a device associated with the driver;

transmit the password to a device associated with the third party rider;

receive, from the server, a ride confirmation message in response to a determination by the third party rider that the password associated with the driver and the password associated with the third party rider match, wherein the ride confirmation message includes a ride itinerary;

display, by the user device, the ride confirmation message including the ride itinerary on the display screen of the user device;

receive a real-time status updates of the requested ride that includes a current location of the driver and an updated drop off time; and

receive a display, on the display screen of the user device, the real-time status updates of the requested ride that includes the current location of the driver the updated drop off time displayed on the device.

12. The system of claim 11 , wherein the user device further transmits the ride confirmation message to a device associated with the third party rider.

13. The system of claim 11 , wherein the set of trusted drivers include drivers who have previously provided driving services to family members of the ride requestor.

14. The system of claim 11 , wherein the set of trusted drivers includes drivers who have previously provided driving services to members of at least one social network who are connected with the ride requestor on the at least one social network.

15. The system of claim 11 , wherein upon receiving the real-time status update of the requested ride, an alternate dropoff address for an additional third party rider is transmitted from the user device.

16. A non-transitory computer-readable medium containing instructions which, when executed by a processor, cause the processor to:

transmit a ride request to a server for a third party rider;

transmit a dropoff contact information;

identify, by the server, a previous ride requester who previously requested a ride from a driver from a set of trusted drivers among a pool of drivers, wherein the previous ride requestor is within a social network sphere of the user;

receive, from the server, an identification of the previous ride requester who previously requested the ride from the driver from the set of trusted drivers among the pool of drivers, wherein the previous ride requestor is within the social network sphere of the user;

display, by the user device, the identification of the previous ride requestor who is within the social network sphere of the user on a display screen of the user device,

receive, from the server, an identification of the driver from the set of trusted drivers among the pool of drivers who previously gave a ride to the previous ride requestor who is within the social network sphere of the user;

transmit a password set by the user to a device associated with the driver;

transmit a password set by the user to a device associated with the third party rider;

receive, from the server, a ride confirmation message in response to a determination by the third party rider that the password associated with the driver and the password associated with the third party rider match, wherein the ride confirmation message includes a ride itinerary;

display, by the user device, the ride confirmation message including the ride itinerary on the display screen of the user device;

receive a real-time status updates of the requested ride that includes a current location of the driver and an updated drop off time; and

receive a display, on the display screen of the user device, the real-time status updates of the requested ride that includes the current location of the driver the updated drop off time displayed on the device.

17. The non-transitory computer-readable medium of claim 16 , wherein the processor further transmits the ride confirmation message to a device associated with the third party rider.

18. The non-transitory computer-readable medium of claim 16 , wherein upon receiving the real-time status update of the requested ride for an additional third party rider, the processor transmits an alternate dropoff address.

19. The non-transitory computer-readable medium of claim 18 , wherein the status of the requested ride includes an indicator displayed on a map representing the current location of a vehicle associated with the driver.

20. The non-transitory computer-readable medium of claim 16 , wherein the set of trusted drivers include drivers who have previously provided driving services to family members of the ride requestor.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 41030 FRAME: 324. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 3, 2025
From: NARAYAN, RITU; GARG, VIVEK; GARG, ABHISHEK
To: ZUM SERVICES, INC.
Reel/Frame 073517/0915 →
SECURITY INTEREST Recorded Oct 31, 2025
From: ZUM SERVICES, INC.
To: HASI FLEET LENDER 2 LLC
Reel/Frame 072749/0949 →
SECURITY INTEREST Recorded Jul 19, 2023
From: ZUM SERVICES, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 064318/0684 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 20, 2017
From: NARAYAN, RITU; GARG, ABHISHEK; GARG, VIVEK
To: ZUM SERVICES, LLC
Reel/Frame 041030/0324 →