Trip termination determination for on-demand transport

Patent metadata

Field	Value
Publication number	US-10672198-B2
Application number	US-201615182217-A
Country	US
Kind code	B2
Filing date	Jun 14, 2016
Priority date	Jun 14, 2016
Publication date	Jun 2, 2020
Grant date	Jun 2, 2020

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.

First claim

What is being claimed is:

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 processo

Assignees

• Uber Technologies Inc

Inventors

• Brinig Kevin
• Ioffe Maksim
• Layton Brandon
• Sumers Theodore
• Kadous Mohammed Waleed

Classifications

• H04W4/029

  Location-based management or tracking services · CPC title

• H04W4/027

  using movement velocity, acceleration information · CPC title

• H04W4/48

  for in-vehicle communication · CPC title

• H04W4/42

  for mass transport vehicles, e.g. buses, trains or aircraft · CPC title

• H04W4/021

  Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences · CPC title