Trip anomaly detection system

Patent metadata

Field	Value
Publication number	US-9883371-B2
Application number	US-201715634234-A
Country	US
Kind code	B2
Filing date	Jun 27, 2017
Priority date	Jun 17, 2015
Publication date	Jan 30, 2018
Grant date	Jan 30, 2018

Abstract

An anomaly detection system is provided in connection with a transport service. The anomaly detection system can construct routine route profiles for individual users of the transport service using historical route data. The anomaly detection system can monitor a current route traveled by a user. The anomaly detection system can further identify a matching routine route profile of the respective user. The anomaly detection system can utilize the matching routine route profile to identify a probable anomaly in the current route. In response to detecting the probable anomaly, the anomaly detection system can enable a safety protocol to perform a number of actions.

First claim

What is claimed is:

1. An anomaly detection system for a service comprising:
one or more processors; and
one or more memory resources storing instructions that, when executed by the one or more processors, cause the anomaly detection system to:
monitor, by receiving location data from location-aware resources of a mobile device of a user or a driver, a current route traveled by the driver servicing a pick-up request for the user, the current route including an estimated time of arrival;
determine a probable anomaly in the current route based on the estimated time of arrival exceeding, by an anomaly threshold, a historical travel time for the current route, wherein determining the probable anomaly in the current route includes determining, using the location-aware resources of the mobile device of the user or the driver, that a geographic position of a vehicle of the driver has remained static for a period of time exceeding a threshold period of time; and
in response to determining the probable anomaly, perform one or more actions in accordance with a safety protocol, including transmitting a status query to the mobile device of the user or contacting an emergency authority to report the probable anomaly.

2. The anomaly detection system of claim 1 , wherein the executed instructions further cause the anomaly detection system to:
raise or lower the anomaly threshold and/or the threshold period of time based on a reputation factor of the driver, wherein the reputation factor includes (i) a complaint history of the driver, and (ii) reputation indicators of the driver received or retrieved from third-party resources.

3. The anomaly detection system of claim 1 , wherein the executed instructions further cause the anomaly detection system to:
raise or lower the anomaly threshold and/or the threshold period of time based on a comparison between a user profile of the user and a driver profile of the driver, the user profile comprising one or more of age, gender, and user preferences, and the driver profile comprising one or more of age, gender, and reputation data.

4. The anomaly detection system of claim 1 , wherein the executed instructions further cause the anomaly detection system to:
utilize environmental data for a region including the current route to raise or lower the anomaly threshold and/or the threshold period of time.

5. The anomaly detection system of claim 4 , wherein the environmental data includes traffic data, police report data, local news, and crime data.

6. The anomaly detection system of claim 1 , wherein an initial action of the safety protocol comprises transmitting a status query to the mobile device of the user, and wherein a subsequent action in the safety protocol comprises contacting an emergency authority to report the probable anomaly.

7. The anomaly detection system of claim 6 , wherein the executed instructions further cause the anomaly detection system to:
in response to the status query, receive an indication of a negative condition from the mobile device of the user; and
in response to receiving the indication, transmit a driver directive to a mobile device of the driver indicating the negative condition.

8. The anomaly detection system of claim 1 , wherein the one or more actions performed in accordance with the safety protocol include:
providing a selectable emergency feature on a graphical user interface of the mobile device of the user during the current route; and
receiving a user selection of the selectable emergency feature.

9. A non-transitory computer readable medium storing instructions that, when executed by one or more processors of an anomaly detection system, cause the anomaly detection system to:
monitor, by receiving location data from location-aware resources of a mobile device of a user or a driver, a current route traveled by the driver servicing a pick-up request for the user, the current route including an estimated time of arrival;
determine a probable anomaly in the current route based on the estimated time of arrival exceeding, by an anomaly threshold, a historical travel time for the current route, wherein determining the probable anomaly in the current route includes determining, using the location-aware resources of the mobile device of the user or the driver, that a geographic position of a vehicle of the driver has remained static for a period of time exceeding a threshold period of time; and
in response to determining the probable anomaly, perform one or more actions in accordance with a safety protocol, including transmitting a status query to the mobile device of the user or contacting an emergency authority to report the probable anomaly.

10. The non-transitory computer readable medium of claim 9 , storing further instructions to cause the anomaly detection system to:
raise or lower the anomaly threshold and/or the threshold period of time based on a reputation factor of the driver, wherein the reputation factor includes (i) a complaint history of the driver, and (ii) reputation indicators of the driver received or retrieved from third-party resources.

11. The non-transitory computer readable medium of claim 9 , storing further instructions to cause the anomaly detection system to:
raise or lower the anomaly threshold and/or the threshold period of time based on a comparison between a user profile of the user and a driver profile of the driver, the user profile comprising one or more of age, gender, and user preferences, and the driver profile comprising one or more of age, gender, and reputation data.

12. The non-transitory computer readable medium of claim 9 , storing further instructions to cause the anomaly detection system to:
utilize environmental data for a region including the current route to raise or lower the anomaly threshold and/or the threshold period of time.

13. The non-transitory computer readable medium of claim 12 , wherein the environmental data includes traffic data, police report data, local news, and crime data.

14. The non-transitory computer readable medium of claim 9 , wherein an initial action of the safety protocol comprises transmitting a status query to the mobile device of the user, and wherein a subsequent action in the safety protocol comprises contacting an emergency authority to report the probable anomaly.

15. The non-transitory computer readable medium of claim 14 , storing further instructions to cause the anomaly detection system to:
in response to the status query, receive an indication of a negative condition from the mobile device of the user; and
in response to receiving the indication, transmit a driver directive to a mobile device of the driver indicating the negative condition.

16. A computer-implemented method for detecting route anomalies, the method performed by one or more processors of an anomaly detection system and comprising:
monitoring, by receiving location data from location-aware resources of a mobile device of a user or a driver, a current route traveled by the driver servicing a pick-up request for the user, the current route including an estimated time of arrival;
determining a probable anomaly in the current route based on the estimated time of arrival exceeding, by an anomaly threshold, a historical travel time for the current route, wherein determining the probable anomaly in the current route includes determining, using the location-aware resources of the mobile device of the user or the driver, that a geographic position of a vehicle of the driver has remained static for a period of time exceeding a threshold period of time; and
in response to dete

Assignees

• Uber Technologies Inc

Inventors

• Truong Michael
• Purdy David
• Mawas Rami

Classifications

• H04W76/50

  for emergency connections · CPC title

• B60R11/04

  Mounting of cameras operative during drive; Arrangement of controls thereof relative to the vehicle · CPC title

• H04W4/40

  for vehicles, e.g. vehicle-to-pedestrians [V2P] · CPC title

• E05Y2900/548

  Trunk lids · CPC title

• H04W4/023

  using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds · CPC title