IP Library Granted Patent US 11,881,064
Granted Patent B2
US 11,881,064 · App. 17/690,483 · Granted Jan 23, 2024

Technologies for determining driver efficiency

Inventor: Stephen E. Peterson (Dana Point, CA)
Assignee: CalAmp Corp
G07C5/0816G07C5/008
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 11,881,064
App. No.
17/690,483
Granted
Jan 23, 2024
Kind
B2
Abstract

Technologies for determining driver efficiency include receiving, by a telematics server, accelerometer data from a telematics device located in a vehicle driven by a driver. The accelerometer data defines a pattern of acceleration of the vehicle over a time period. The telematics server determines a driver efficiency score of the driver based on the accelerometer data. The driver efficiency score is indicative of an average absolute acceleration of the vehicle over the time period. The determined driver efficiency score may be compared to a reference efficiency score and/or efficiency scores of other drivers to rank the drivers.

Claims (39)

1. A telematics server for determining driver efficiency, the telematics server comprising:

a device interface configured to receive accelerometer data from a telematics device located in a vehicle driven by a driver, wherein the accelerometer data defines a pattern of acceleration of the vehicle over a time period; and

a driver efficiency analyzer configured to (i) determine a driver efficiency score of the driver based on the accelerometer data, wherein the driver efficiency score is indicative of an average absolute acceleration of the vehicle over the time period, (ii) compare the driver efficiency score to a reference efficiency score, and (iii) generate a notification in response to a determination that the driver efficiency score satisfies a relationship to the reference efficiency score,

wherein the device interface is further configured to transmit the notification.

2. The telematics server of claim 1 , wherein to determine the driver efficiency score comprises to determine absolute accelerometer data based on the accelerometer data, determine a total acceleration value for the time period based on the absolute accelerometer data, and determine an average absolute acceleration by dividing the total acceleration value by a temporal length of the time period.

3. The telematics server of claim 2 , wherein to determine the average absolute acceleration of the vehicle over the time period comprises to ignore periods of the accelerometer data having no acceleration.

4. The telematics server of claim 1 , wherein to transmit the notification comprises to transmit the notification to the telematics device, wherein the notification instructs the telematics device to generate an alert.

5. The telematics server of claim 1 , wherein the driver efficiency analyzer is further configured to determine a driver rank for the driver based on the driver efficiency score determined for the driver and driver efficiency scores determined for other drivers.

6. The telematics server of claim 1 , wherein the device interface is further configured to receive route information defining a route taken by the vehicle during the generation of the accelerometer data, and

wherein to determine the driver efficiency score comprises to determine a driver efficiency score of the driver for the route.

7. The telematics server of claim 1 , wherein the driver efficiency analyzer is further configured to determine a reward for the driver based on the driver efficiency score determined for the driver.

8. The telematics server of claim 1 , wherein the driver efficiency analyzer is further configured to assign the driver to another vehicle based on the driver efficiency score determined for the driver.

9. The telematics server of claim 1 , wherein the device interface is further configured to receive route information defining a route taken by the vehicle during the generation of the accelerometer data, and

wherein the driver efficiency analyzer is further configured to determine an average driver efficiency score for the route based on the driver efficiency score determined for the driver and driver efficiency scores determined for other drivers for the route.

10. The telematics server of claim 9 , wherein the driver efficiency analyzer is further configured to assign the driver to a first route based on the driver efficiency score determined for the driver and the average driver efficiency score of the first route.

11. A method for determining driver efficiency, the method comprising

receiving, by a telematics server, accelerometer data from a telematics device located in a vehicle driven by a driver, wherein the accelerometer data defines a pattern of acceleration of the vehicle over a time period;

determining, by the telematics server, a driver efficiency score of the driver based on the accelerometer data, wherein the driver efficiency score is indicative of an average absolute acceleration of the vehicle over the time period;

comparing the driver efficiency score to a reference efficiency score;

generating a notification in response to a determination that the driver efficiency score satisfies a relationship to the reference efficiency score; and

transmitting the notification.

12. The method of claim 11 , wherein determining the driver efficiency score comprises determining absolute accelerometer data based on the accelerometer data, determining a total acceleration value for the time period based on the absolute accelerometer data, and determining an average absolute acceleration by dividing the total acceleration value by a temporal length of the time period.

13. The method of claim 11 , further comprising determining, by the telematics server, a driver rank for the driver based on the driver efficiency score determined for the driver and driver efficiency scores determined for other drivers.

14. The method of claim 1 , further comprising receiving, by the telematics server, route information defining a route taken by the vehicle during the generation of the accelerometer data, and

wherein determining the driver efficiency score comprises determining a driver efficiency score of the driver for the route.

15. The method of claim 11 , further comprising assigning, by the telematics server, the driver to another vehicle based on the driver efficiency score determined for the driver.

16. The method of claim 11 , further comprising:

receiving, by the telematics server, route information defining a route taken by the vehicle during the generation of the accelerometer data, and

determining, by the telematics server, an average driver efficiency score for the route based on the driver efficiency score determined for the driver and driver efficiency scores determined for other drivers for the route.

17. The method of claim 16 , further comprising assigning, by the telematics server, the driver to a first route based on the driver efficiency score determined for the driver and the average driver efficiency score of the first route.

18. One or more non-transitory, computer-readable storage media comprising a plurality of instructions that, in response to execution, cause a telematics server to:

receive accelerometer data from a telematics device located in a vehicle driven by a driver, wherein the accelerometer data defines a pattern of acceleration of the vehicle over a time period;

determine a driver efficiency score of the driver based on the accelerometer data, wherein the driver efficiency score is indicative of an average absolute acceleration of the vehicle over the time period;

compare the driver efficiency score to a reference efficiency score;

generate a notification in response to a determination that the driver efficiency score satisfies the relationship to a reference efficiency score; and

transmit the notification.

19. The one or more non-transitory, computer-readable storage media of claim 18 , wherein the plurality of instructions, in response to execution, further cause the telematics server to determine a driver rank for the driver based on the driver efficiency score determined for the driver and driver efficiency scores determined for other drivers.

20. The one or more non-transitory, computer-readable storage media of claim 18 , wherein the plurality of instructions, in response to execution, further cause the telematics server to receive route information defining a route taken by the vehicle during the generation of the accelerometer data, and

wherein to determine the driver efficiency score comprises to determine a driver efficiency score of the driver for the route.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Aug 15, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: CALAMP CORP.; CALAMP WIRELESS NETWORKS CORPORATION; SYNOVIA SOLUTIONS LLC
Reel/Frame 068655/0542 →
RELEASE OF SECURITY INTEREST Recorded Dec 18, 2023
From: PNC BANK, NATIONAL ASSOCIATION
To: CALAMP CORP
Reel/Frame 066059/0252 →
PATENT SECURITY AGREEMENT Recorded Dec 18, 2023
From: CALAMP CORP.; CALAMP WIRELESS NETWORKS CORPORATION; SYNOVIA SOLUTIONS LLC
To: LYNROCK LAKE MASTER FUND LP [LYNROCK LAKE PARTNERS LLC, ITS GENERAL PARTNER]
Reel/Frame 066061/0946 →
PATENT SECURITY AGREEMENT Recorded Dec 18, 2023
From: CALAMP CORP.; CALAMP WIRELESS NETWORKS CORPORATION; SYNOVIA SOLUTIONS LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 066062/0303 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2023
From: PETERSON, STEPHEN E.
To: CALAMP CORP.
Reel/Frame 064484/0978 →
SECURITY INTEREST Recorded Jul 14, 2022
From: CALAMP CORP.; CALAMP WIRELESS NETWORKS CORPORATION; SYNOVIA SOLUTIONS LLC
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 060651/0651 →