System and Method for Mobile Payments in a Vehicle
US-2016063459-A1 · Mar 3, 2016 · US
US11067409B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11067409-B2 |
| Application number | US-201816028927-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 6, 2018 |
| Priority date | Jul 14, 2017 |
| Publication date | Jul 20, 2021 |
| Grant date | Jul 20, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Aspects of the disclosure relate to processing remotely captured sensor data. A computing platform having at least one processor, a communication interface, and memory may receive, via the communication interface, from a user computing device, sensor data captured by the user computing device using one or more sensors built into the user computing device. Subsequently, the computing platform may analyze the sensor data received from the user computing device by executing one or more data processing modules. Then, the computing platform may generate trip record data based on analyzing the sensor data received from the user computing device and may store the trip record data in a trip record database. In addition, the computing platform may generate user record data based on analyzing the sensor data received from the user computing device and may store the user record data in a user record database.
Opening claim text (preview).
What is claimed is: 1. A computing system, comprising: at least one user computing device including one or more sensors and storing instructions that, when executed, cause the at least one user computing device to: capture, by a first user computing device of the at least one user computing device, first sensor data using one or more sensors built into the first user computing device, wherein the first sensor data is captured by the first user computing device during a first vehicle trip; and capture, by the first user computing device of the at least one user computing device, second sensor data using the one or more sensors built into the first user computing device, wherein the second sensor data is captured by the first user computing device during a second vehicle trip; and a computing platform, comprising: at least one processor; a communication interface; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the at least one processor to: receive, via the communication interface, from the first user computing device, the first sensor data captured by the first user computing device; analyze the first sensor data received from the first user computing device to identify an end location of the first vehicle trip; based on analyzing the first sensor data received from the first user computing device to identify the end location of the first vehicle trip, update a user-specific listing of trip-end locations; after updating the user-specific listing of trip-end locations, receive, via the communication interface, from the first user computing device, the second sensor data captured by the first user computing device; determine a distance between the end location of the first vehicle trip and a start location of the second vehicle trip; based on the distance between the end location of the first vehicle trip and the start location of the second vehicle trip, generate driver-detection data indicative of whether a user of the first user computing device is a driver of a vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip; store, in at least one database maintained by the at least one processor and accessible to one or more data analysis modules associated with the at least one processor, the driver-detection data indicative of whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip, wherein generating the driver-detection data indicative of whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip comprises: generating data indicating that the user of the first user computing device is a driver of the vehicle during the second vehicle trip when the distance between the end location of the first vehicle trip and the start location of the second vehicle trip does not exceed a user-specific distance threshold; and generating data indicating that the user of the first user computing device is a passenger of the vehicle during the second vehicle trip when the distance between the end location of the first vehicle trip and the start location of the second vehicle trip exceeds the user-specific distance threshold, and wherein the user-specific distance threshold is learned by the at least one processor based on information indicating end points of multiple previous trips taken by the user of the first user computing device and information indicating how closely to each end point of each previous trip of the multiple previous trips a subsequent vehicle trip started, based on storing the driver-detection data indicative of whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip, generate a notification indicating whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip; send, via the communication interface, to the first user computing device, the notification indicating whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip, wherein sending the notification indicating whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip causes the first user computing device to prompt the first user associated with the first user computing device to confirm whether the user of the first user computing device is a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip; and update the user-specific distance threshold based on a response from the first user computing device confirming whether the user of the first user computing device was a driver of the vehicle during the second vehicle trip or a passenger of the vehicle during the second vehicle trip. 2. The computing system of claim 1 , wherein receiving the first sensor data captured by the first user computing device comprises receiving data captured by one or more of an accelerometer, a gyroscope, a magnetometer, a barometer, a gravitometer, a proximity sensor, an ambient light sensor, an ambient temperature sensor, an orientation sensor, a pedometer, an altimeter, a satellite positioning sensor, or an activity recognition sensor built into the first user computing device. 3. The computing system of claim 1 , wherein receiving the first sensor data from the first user computing device comprises receiving location data identifying geographic coordinates of the end location of the first vehicle trip. 4. The computing system of claim 1 , wherein analyzing the first sensor data received from the first user computing device to identify the end location of the first vehicle trip comprises determining the end location of the first vehicle trip by determining an exit point associated with a time window in which the user of the first user computing device exited a vehicle during the first vehicle trip. 5. The computing system of claim 4 , wherein determining the exit point associated with the time window in which the user of the first user computing device exited the vehicle during the first vehicle trip comprises using a sliding window approach to determine a point in time at which the user of the first user computing device exited the vehicle during the first vehicle trip, and wherein using the sliding window approach to determine the point in time at which the user of the first user computing device exited the vehicle during the first vehicle trip comprises creating 3-second or 5-second window frames that form a partially-overlapping sequence. 6. The computing system of claim 4 , wherein determining the exit point associated with the time window in which the user of the first user computing device exited the vehicle during the first vehicle trip comprises assigning probability values to a plurality of time windows associated with possible times at which the user of the first user computing device exited the vehicle during the first vehicle trip. 7. The computing system of claim 1 , wherein the user-specific listing of trip-end locations comprises information identifying one or more locations at which one or more previous vehicle trips taken by the user of the first user computing device ended. 8. The computing system of claim 1 , wherein receiving the second sensor data from the first us
specially adapted for the location of the user terminal · CPC title
Preferred or disfavoured areas, e.g. dangerous zones, toll or emission zones, intersections, manoeuvre types or segments such as motorways, toll roads or ferries · CPC title
using display panels · CPC title
Event management; Broadcasting; Multicasting; Notifications · CPC title
Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.