IP Library Granted Patent US 10,672,198
Granted Patent B2
US 10,672,198 · App. 15/182,217 · Granted Jun 2, 2020

Trip termination determination for on-demand transport

Inventors: Kevin Brinig (San Francisco, CA); Maksim Ioffe (San Francisco, CA); Brandon Layton (San Francisco, CA); Theodore Sumers (San Francisco, CA); Mohammed Waleed Kadous (San Francisco, CA)
Assignee: Uber Technologies, Inc.
G07B15/02H04W4/027H04W4/029H04W4/42H04W4/021H04W4/48
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,672,198
App. No.
15/182,217
Granted
Jun 2, 2020
Kind
B2
Abstract

In context of a transportation service provided through a transport arrangement service, examples determine a point of trip termination for a trip. The point of trip termination can be determined from passive information that is collected from a computing device of a driver. The point of trip termination can be determined based on driver input and the collected information from the driver's computing device.

Claims (36)

1. A method of implementing a transport service, the method being performed by one or more processors and comprising:

communicating, over one or more networks, with (i) computing devices of riders of a transport service via an executing rider application, and (ii) computing devices of drivers of the transport service via an executing driver application;

receiving, over the one or more networks, first sensor data from a computing device of a driver of the transport service, the first sensor data including location data from a positioning system of the computing device of the driver;

receiving, over the one or more networks, second sensor data from a computing device of a rider being transported in a vehicle by the driver, the second sensor data includes location data from a positioning system of the computing device of the rider;

remotely monitoring a velocity of the vehicle over the course of a trip in which the driver transports the rider, based on at least one of the location data from the computing device of the driver or the location data from the computing device of the rider;

receiving, over the one or more networks, input data indicating a trip termination input from the computing device of the driver via the executing driver application, the trip termination input signaling termination of the trip by the driver at a termination location;

based at least in part on monitoring the velocity of the vehicle and in response to the trip termination input signaling termination of the trip, determining whether the termination location corresponding to the trip termination input is valid, wherein the termination location is valid when the trip termination input correlates to the vehicle being stopped; and

in response to determining that the termination location is not valid, validate an actual point of trip termination based on the first sensor data and the second sensor data to determine a fare for the trip.

2. The method of claim 1 , wherein validating the actual point of trip termination comprises correcting the termination location.

3. The method of claim 2 , wherein correcting the termination location includes extending the trip to the actual point of trip termination.

4. The method of claim 2 , wherein correcting the termination location includes shortening the trip to the actual point of trip termination.

5. The method of claim 1 , wherein the first sensor data further comprises acceleration data from one or more motion sensing components of the computing device of the driver.

6. The method of claim 1 , wherein determining that the termination location is not valid comprises determining, based on at least one of the first sensor data or the second sensor data, the velocity of the vehicle of the driver when the driver provides the trip termination input.

7. A non-transitory computer readable medium storing instructions for determining a point of trip termination for a trip provided by a transport service, the instructions being executable by one or more processors of a computing system for a transport arrangement service to:

communicate, over one or more networks, with fi) computing devices of riders of a transport service via an executing rider application, and (ii) computing devices of drivers of the transport service via an executing driver application;

receive, over the one or more networks, first sensor data from a computing device of a driver of the transport service, the first sensor data including location data from a positioning system of the computing device of the driver;

receive, over the one or more networks, second sensor data from a computing device of a rider being transported in a vehicle by the driver, the second sensor data includes location data from a positioning system of the computing device of the rider;

remotely monitoring a velocity of the vehicle over the course of a trip in which the driver transports the rider, based on at least one of the location data from the computing device of the driver or the location data from the computing device of the rider;

receive, over the one or more networks, input data indicating a trip termination input from the computing device of the driver via the executing driver application, the trip termination input signaling termination of the trip by the driver at a termination location;

based at least in part on monitoring the velocity of the vehicle and in response to the trip termination input signaling termination of the trip, determine whether the termination location corresponding to the trip termination input is valid, wherein the termination location is valid when the trip termination input correlates to the vehicle being stopped; and

in response to determining that the termination location is not valid, validate an actual point of trip termination based on the first sensor data and the second sensor data to determine a fare for the trip.

8. A computer system comprising:

a network communication interface to communicate, over one or more networks, with (i) computing devices of riders of a transport service via an executing rider application, and (ii) computing devices of drivers of the transport service via an executing driver application;

a memory storing a set of instructions;

a processor executing the set of instructions, causing the processor to:

receive, over the one or more networks, first sensor data from a computing device of a driver, the first sensor data including location data from a positioning system of the computing device of the driver;

receive, over the one or more networks, second sensor data from a computing device of a rider being transported in a vehicle by the driver, the second sensor data includes location data from a positioning system of the computing device of the rider;

remotely monitor a velocity of the vehicle over the course of a trip in which the driver transports the rider, based on at least one of the location data from the computing device of the driver or the location data from the computing device of the rider;

receive, over the one or more networks, input data indicating a trip termination input from the computing device of the driver, the trip termination input signaling termination of the trip by the driver at a termination location;

based at least in part on monitoring the velocity of the vehicle and in response to the trip termination input signaling termination of the trip, determine whether the termination location corresponding to the trip termination input is valid, wherein the termination location is valid when the trip termination input correlates to the vehicle being stopped; and

in response to determining that the termination location is not valid, validate an actual point of trip termination based on the first sensor data and the second sensor data to determine a fare for the trip.

9. The computer system of claim 8 , wherein the executed instructions cause the processor to validate the actual point of trip termination by correcting the termination location.

10. The computer system of claim 9 , wherein the executed instructions cause the processor to correct the termination location by extending the trip to the actual point of trip termination.

11. The computer system of claim 9 , wherein the executed instructions cause the processor to correct the termination location by shortening the trip to the actual point of trip termination.

12. The computer system of claim 8 , wherein the first sensor data further comprises acceleration data from one or more motion sensing components of the computing device of the driver.

13. The computer system of claim 8 , wherein the executed instructions cause the processor to determine that the termination location is not valid by determining, based on at least one of the first sensor data or the second sensor data, the velocity of the vehicle of the driver when the driver provides the trip termination input.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069110/0508 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT (TERM LOAN) AT REEL 050767, FRAME 0076 Recorded Sep 11, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC. AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069133/0167 →
RELEASE OF SECURITY INTEREST Recorded Mar 10, 2021
From: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 055547/0404 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0109 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0076 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBER PREVIOUSLY RECORDED AT REEL: 45853 FRAME: 418. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 26, 2018
From: UBER TECHNOLOGIES, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 049259/0064 →
SECURITY INTEREST Recorded Apr 6, 2018
From: UBER TECHNOLOGIES, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 045853/0418 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2017
From: BRINIG, KEVIN; IOFFE, MAKSIM; LAYTON, BRANDON; SUMERS, THEODORE; KADOUS, MOHAMMED WALEED
To: UBER TECHNOLOGIES, INC.
Reel/Frame 041555/0119 →
Continuity (1)
Related Publication 20170358147A1 · Dec 14, 2017
Cited By (3)
US 12,216,473 US 12,222,731 US 12,399,016