IP Library Granted Patent US 12,579,581
Granted Patent B2
US 12,579,581 · App. 18/236,740 · Granted Mar 17, 2026

System and method for preventing fraud in the capture of trip telemetry data

Inventors: Bennett Smith (Inver Grove Heights, MN); Kenneth J. Sanchez (San Francisco, CA)
Assignee: QUANATA, LLC
G06Q40/08G06Q30/0185G06Q30/0207H04W52/0235
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 12,579,581
App. No.
18/236,740
Granted
Mar 17, 2026
Kind
B2
Abstract

Technology for identifying potentially fraudulent user behavior related to the capture and transmission of vehicle trip telemetry data is provided. Automatic and periodic attempts may be made to wake up (e.g., launch, or change to an active mode) an application installed on a mobile device configured to transmit mobile device data, including captured sensor data, to a remote computer device. Based on the sensor data, the remote computer device may determine a number, frequency, and/or duration of vehicle trips associated with the user of the mobile device. When one or more types of expected mobile device data are not received by the remote computer device after a particular attempt to wake the application, data indicating a failure to receive expected mobile device data may be recorded in a log. Based on the log, an alert indicating potentially fraudulent behavior associated with the user of the mobile device may be generated.

Claims (53)

1 . A computer-implemented method, comprising:

receiving, by a heartbeat module of a mobile device via a network from a remote computing device, a heartbeat signal;

in response to receiving the heartbeat signal by the heartbeat module of the mobile device,

activating, by a processor of the mobile device, an application on the mobile device, wherein the application is activated from a dormant mode to an active or background mode;

collecting, by the application of the mobile device, mobile device data including vehicle trip telemetry data associated with one or more vehicle operations; and

transmitting, by the application via the network to the remote computing device, the mobile device data for analysis to identify one or more time periods in which a user of the mobile device may be operating a vehicle;

receiving, by the application via the network from the remote computing device, an indication that one or more types of expected mobile device data of the vehicle trip telemetry data were not received by the remote computing device, wherein the remote computing device stores, in a memory of the remote computing device, absence data indicating an absence of the one or more types of expected mobile device data with a timestamp associated with the heartbeat signal; and

receiving, by the application via the network from the remote computing device, an alert indicating potentially fraudulent behavior associated with the user of the mobile device, wherein the remote computing device generates the alert based on analyzing first data in the memory to identify a frequency of absences of the one or more types of expected mobile device data, wherein the frequency exceeds a predetermined threshold, and wherein the first data comprises the absence data.

2 . The method of claim 1 , wherein:

the remote computing device generates the alert further based on determining that the mobile device is configured to prevent transmission of the at least one of the one or more types of expected mobile device data.

3 . The method of claim 1 , wherein receiving the alert includes the remote computing device receiving data indicating that a first type of expected mobile device data was received by the remote computing device and a second type of expected mobile device data was not received by the remote computing device.

4 . The method of claim 1 , wherein receiving the heartbeat signal comprises:

receiving, by the heartbeat module via the network from the remote computing device, a first heartbeat signal at a first time;

receiving, by the heartbeat module via the network from the remote computing device, a second heartbeat signal at a second time, the second time occurring after the first time and separated from the first time by a predetermined time interval; and

receiving, by the heartbeat module via the network from the remote computing device, a third heartbeat signal at a third time, the third time occurring after the second time and separated from the second time by the predetermined time interval.

5 . The method of claim 1 , wherein the mobile device data includes data indicative of a lack of permission to access one or more sensors of the mobile device.

6 . The method of claim 1 , further comprising:

receiving, by the application via the network from the remote computing device, data identifying one or more time periods in which the user of the mobile device is operating a vehicle, wherein the remote computing device identifies the one or more time periods based on the mobile device data.

7 . The method of claim 1 , further comprising:

determining, by the processor of the mobile device, whether the application is running; and

based on the determining: (i) launching, by the processor of the mobile device, the application if the application is determined to not be running, or (ii) waking up, by the processor of the mobile device, the application if the application is running in the dormant mode.

8 . The method of claim 1 , wherein the heartbeat signal is received based on a location indication that the mobile device has changed to a second location, wherein a distance between the second location and a previous location of the mobile device is greater than a threshold distance, and wherein the previous location is a location of the mobile device when a previous heartbeat signal was received.

9 . The method of claim 8 , wherein the location indication is based on data detected by a Global Positioning System (GPS) sensor of the mobile device.

10 . The method of claim 8 , wherein the heartbeat module of the mobile device is part of the application of the mobile device.

11 . A computing system comprising a remote computing device, including:

one or more processors; and

one or more memories storing computer-executable instructions that, when executed by the one or more processors, cause the remote computing device to perform operations comprising:

sending, via a network, a heartbeat signal to a heartbeat module of a mobile device, wherein the mobile device is configured to activate, by a processor of the mobile device, an application on the mobile device from a dormant mode to an active or background mode upon receipt of the heartbeat signal by the heartbeat module of the mobile device;

receiving, via the network from the application of the mobile device, mobile device data, the mobile device data including vehicle trip telemetry data associated with one or more vehicle operations;

determining that one or more types of expected mobile device data, including the vehicle trip telemetry data, were not received in response to the heartbeat signal;

storing, in a memory of the remote computing device, absence data indicating an absence of the one or more types of expected mobile device data with a timestamp associated with the heartbeat signal;

generating an alert indicating potentially fraudulent behavior associated with a user of the mobile device based on analyzing first data in the memory to identify a frequency of absences of the one or more types of expected mobile device data, wherein the frequency exceeds a predetermined threshold, and wherein the first data comprises the absence data; and

transmitting, via the network to the application of the mobile device, the alert indicating potentially fraudulent behavior.

12 . The computing system of claim 11 , wherein generating the alert further comprises determining that the mobile device is configured to prevent transmission of the one or more types of expected mobile device data.

13 . The computing system of claim 11 , wherein determining that the one or more types of expected mobile device data were not received includes determining that a first type of expected mobile device data was received and a second type of expected mobile device data was not received.

14 . The computing system of claim 11 , wherein sending the heartbeat signal comprises:

sending a first heartbeat signal at a first time;

sending a second heartbeat signal at a second time, the second time occurring after the first time, the first time and the second time being separated from each other by a predetermined time interval; and

sending a third heartbeat signal at a third time, the third time occurring after the second time, the second time and the third time being separated from each other by the predetermined time interval.

15 . The computing system of claim 11 , wherein the mobile device data includes data indicating a lack of permission to access one or more sensors of the mobile device.

16 . The computing system of claim 11 , wherein the computer-executable instructions, when executed, further cause the remote computing device to identify one or more time periods in which the user of the mobile device is operating a vehicle based on the received mobile device data.

17 . The computing system of claim 11 , wherein the mobile device is further configured to, based on a determination by the processor of the mobile device of whether the application is running: (i) launch the application if the application is determined to not be running, or (ii) transition the application from the dormant mode to the active or background mode if the application is determined to be running in the dormant mode.

18 . The computing system of claim 11 , wherein the computer-executable instructions, when executed, further cause the remote computing device to send the heartbeat signal based on a location indication that the mobile device has changed to a second location, wherein a distance between the second location and a previous location of the mobile device is greater than a threshold distance, and wherein the previous location is a location of the mobile device when a previous heartbeat signal was sent.

19 . The computing system of claim 18 , wherein the location indication of the mobile device is based on data detected by a Global Positioning System (GPS) sensor of the mobile device.

20 . The computing system of claim 18 , wherein the heartbeat module of the mobile device is part of the application of the mobile device.

21 . A non-transitory computer-readable medium storing instructions, wherein the instructions, upon execution by a processor of a mobile device, cause the processor to perform operations comprising:

receiving, by a heartbeat module of the mobile device via a network from a remote computing device, a heartbeat signal;

in response to receiving the heartbeat signal by the heartbeat module of the mobile device,

activating, by the processor of the mobile device, an application on the mobile device, wherein the application is activated from a dormant mode to an active or background mode;

collecting, by the application of the mobile device, mobile device data including vehicle trip telemetry data associated with one or more vehicle operations; and

transmitting, by the application via the network to the remote computing device, the mobile device data for analysis to identify one or more time periods in which a user of the mobile device may be operating a vehicle;

receiving, by the application via the network from the remote computing device, an indication that one or more types of expected mobile device data of the vehicle trip telemetry data were not received by the remote computing device, wherein the remote computing device stores, in a memory of the remote computing device, absence data indicating an absence of the one or more types of expected mobile device data with a timestamp associated with the heartbeat signal; and

receiving, by the application via the network from the remote computing device, an alert indicating potentially fraudulent behavior associated with the user of the mobile device, wherein the remote computing device generates the alert based on analyzing first data in the memory to identify a frequency of absences of the one or more types of expected mobile device data, wherein the frequency exceeds a predetermined threshold, and wherein the first data comprises the absence data.

Assignments (2)
CHANGE OF NAME Recorded May 29, 2024
From: BLUEOWL, LLC
To: QUANATA, LLC
Reel/Frame 067558/0600 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2024
From: SMITH, BENNETT; SANCHEZ, KENNETH J.
To: BLUEOWL, LLC
Reel/Frame 066186/0093 →
Continuity (3)
Continuation 15880787 · Jan 26, 2018
Provisional Application 62569208 · Oct 6, 2017
Related Publication 20230394590A1 · Dec 7, 2023
References Cited (47)
US 6532543B1 · Smith et al. · 2003 [cited by applicant]
US 8590785B1 · Mesaros · 2013 [cited by examiner]
US 8646060B1 · Ben Ayed · 2014 [cited by applicant]
US 9135415B2 · Schaefer · 2015 [cited by applicant]
US 9185117B2 · Grigg et al. · 2015 [cited by applicant]
US 9215225B2 · Desai · 2015 [cited by applicant]
US 9460447B2 · Pointer · 2016 [cited by examiner]
US 9659160B2 · Ligatti et al. · 2017 [cited by applicant]
US 9697508B1 · Ramalingam · 2017 [cited by examiner]
US 9786176B2 · Northrup et al. · 2017 [cited by applicant]
US 9788211B2 · Zhang · 2017 [cited by applicant]
US 9858595B2 · Barnes, Jr. · 2018 [cited by applicant]
US 9961624B1 · Zait · 2018 [cited by applicant]
US 10257668B2 · Shaw · 2019 [cited by applicant]
US 10375082B2 · Brown et al. · 2019 [cited by applicant]
US 10706704B1 · Shannon et al. · 2020 [cited by applicant]
US 11122433B2 · Mahaffey et al. · 2021 [cited by applicant]
US 20030227745A1 · Khoo · 2003 [cited by applicant]
US 20090253410A1 · Fitzgerald et al. · 2009 [cited by applicant]
US 20110010234A1 · Lindelsee · 2011 [cited by examiner]
US 20130238413A1 · Carlson · 2013 [cited by examiner]
US 20140129305A1 · Frame · 2014 [cited by examiner]
US 20140143086A1 · Birsin · 2014 [cited by examiner]
US 20140278970A1 · Calman · 2014 [cited by examiner]
US 20140289833A1 · Briceno et al. · 2014 [cited by applicant]
US 20150019443A1 · Sheets et al. · 2015 [cited by applicant]
US 20150052064A1 · Karpenko et al. · 2015 [cited by applicant]
US 20150095152A1 · Walters · 2015 [cited by examiner]
US 20150161643A1 · Randell · 2015 [cited by examiner]
US 20150269600A1 · Randle · 2015 [cited by examiner]
US 20160098076A1 · Chng et al. · 2016 [cited by applicant]
US 20160173447A1 · Achim et al. · 2016 [cited by applicant]
US 20160234209A1 · Kahol et al. · 2016 [cited by applicant]
US 20160350786A1 · Loomis · 2016 [cited by examiner]
US 20170076265A1 · Royyuru et al. · 2017 [cited by applicant]
US 20170076274A1 · Royyuru et al. · 2017 [cited by applicant]
US 20170195339A1 · Brown · 2017 [cited by examiner]
US 20170255988A1 · Calio · 2017 [cited by examiner]
US 20180047273A1 · Dejong et al. · 2018 [cited by applicant]
US 20180247262A1 · Arena · 2018 [cited by applicant]
US 20190124044A1 · Kurian · 2019 [cited by applicant]
US 20190258818A1 · Yu et al. · 2019 [cited by applicant]
US 20200329136A1 · Gerhardt et al. · 2020 [cited by applicant]
US 20210144557A1 · Gulick, Jr. et al. · 2021 [cited by applicant]
EP 2887296A2 · 2015 [cited by examiner]
EP 2993637A1 · 2016 [cited by examiner]
WO 2013190380A2 · 2013 [cited by applicant]