Real-Time Monitoring of Vehicle

• US 20140288766A1
• Filed: 02/18/2014
• Published: 09/25/2014
• Est. Priority Date: 03/20/2013
• Status: Active Grant

• Current Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Original Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Inventors: Purushothaman, Balamuralidhar, Chakravarty, Tapas, Ghose, Avik, Pal, Arpan, Chowdhary, Arijit
• Granted Patent: US 9,324,192 B2
• Time in Patent Office: Days
• US Class Current: 701/32.4
• CPC Class Codes: G05B 23/0235 based on a comparison with predetermined threshold or range, e.g. "classical methods", carried out during normal operation; threshold adaptation or choice; when or how to compare with the threshold
• CPC Class Codes: G07C 5/00 Registering or indicating the working of vehicles

Abstract

A monitoring unit for vehicle monitoring comprising a receiving module configured to receive data from an OBD, wherein the data is associated with a plurality of jerks detected by a 3-axis accelerometer. The monitoring unit comprises an analytics module configured to compare an intensity of each jerk of the plurality of jerks to a predefined jerk threshold and capture high intensity jerks from the plurality of jerks. The high intensity jerks have intensity equal to or more than the predefined jerk threshold. The method further comprises determining an elapsed time for each of the high intensity jerks. The elapsed time for each of the high intensity jerks is compared to a predefined time threshold. Further it is determined whether an analysis on the high intensity jerks is to be performed at the vehicle or at a server located remotely.

Claims

1. A monitoring unit for real-time monitoring of a vehicle, the monitoring unit comprising:

a processor; and

a memory coupled to the processor, wherein the memory comprises a plurality of modules capable of being executed by the processor, and wherein the plurality of modules comprises;

a receiving module configured to receive data from an On-Board Diagnostic (OBD), wherein the data is associated with a plurality of jerks detected by a three-axis accelerometer coupled to the OBD; and

an analytics module configured to;

compare an intensity of each jerk of the plurality of jerks to a predefined jerk threshold;

capture at least one high intensity jerk of the plurality of jerks, wherein the at least one high intensity jerk has an intensity level of at least the predefined jerk threshold;

determine an elapsed time for each of the at least one high intensity jerk, wherein the elapsed time is indicative of a time between an observation of the at least one high intensity jerk and a feedback sent to a user;

compare the elapsed time for each of the at least one high intensity jerk to a predefined time threshold; and

determine whether an analysis on the at least one high intensity jerk should be performed at the vehicle or at a server located remotely from the vehicle, wherein the analysis is based on the comparison of the elapsed time to the predefined time threshold.

2. The monitoring unit of claim 1, wherein the three-axis accelerometer is configured to capture chassis dynamics of the vehicle on at least one of:

an X-axis, a Y-axis, and a Z-axis of a Cartesian coordinate system.

3. The monitoring unit of claim 1, wherein the data comprise at least one of:

the intensity of each jerk of the plurality of jerks, a ratio of jerk to acceleration of the vehicle, a ratio of acceleration of the vehicle to velocity of the vehicle, a power spectral density, a wavelet transform, a ratio of an x-axis acceleration to a y-axis acceleration, a ratio of the x-axis acceleration to a z-axis acceleration followed by a jerk computation, a ratio of the z-axis acceleration to the y-axis acceleration followed by the jerk computation, a dominant frequency estimation on the ratio of the x-axis acceleration to the y-axis acceleration, and an identified change in a loaded natural frequency of the vehicle.

4. The monitoring unit of claim 1, wherein the analytics module is further configured to receive a position stamp of the vehicle for the at least one high intensity jerk from a Global Positioning System (GPS) unit.

5. The monitoring unit of claim 1, wherein the analysis is performed on at least one of:

the OBD, and a second module installed in the vehicle.

6. The monitoring unit of claim 1, further comprising a test harness module stored within a memory of the server, wherein at least a portion of the data received in the receiving module and the at least one high intensity jerk is analyzed within the test harness module.

7. The monitoring unit of claim 6, wherein analysis within the test harness module further comprises use of a simulation module having a quantity of historical data.

8. The monitoring unit of claim 6, wherein the test harness module determines a probability of a reoccurrence of the at least one high intensity jerk.

9. The monitoring unit of claim 1, wherein determining whether the analysis on the at least one high intensity should be performed at the vehicle or at the server further comprises determining an optimization of a size of the data.

10. The monitoring unit of claim 1, wherein determining whether the analysis on the at least one high intensity should be performed at the vehicle or at the server further comprises determining a tolerance of latency of detection of the plurality of jerks.

11. A method for real-time monitoring of a vehicle, the method comprising:

receiving data associated with a plurality of jerks detected by a three-axis accelerometer, wherein the three-axis accelerometer is embedded in the vehicle and configured to capture at least one signal from vehicle chassis;

comparing an intensity of each jerk of the plurality of jerks to a predefined jerk threshold;

capturing at least one high intensity jerk of the plurality of jerks, wherein the at least one high intensity jerk has intensity level of at least the predefined jerk threshold;

determining an elapsed time for each of the at least one high intensity jerk of the plurality of jerks, wherein the elapsed time is indicative of a time between an observation of the at least one high intensity jerk and a feedback sent to a user;

comparing the elapsed time for each of the at least one high intensity jerk to a predefined time threshold; and

determining whether an analysis on the at least one high intensity jerk should be performed at the vehicle or at a server located remotely from the vehicle, wherein the analysis is based on the comparison of the elapsed time to the predefined time threshold, and wherein at least one of the steps of;

receiving the data, comparing the intensity, capturing the at least one high intensity jerk, determining the elapsed time, comparing the elapsed time, and determining the analysis is performed by a processor.

12. The method of claim 11, further comprising receiving a position stamp of the vehicle for the at least one high intensity jerk from a Global Positioning System (GPS).

13. The method of claim 11, wherein the data is received from an On-Board Diagnostic (OBD).

14. The method of claim 11, further comprising the step of analyzing the at least one high intensity jerk within a test harness module stored within a memory of the server.

15. The method of claim 14, wherein the step of analyzing the at least one high intensity jerk within the test harness module stored within the memory of the server further comprises using a simulation module having a quantity of historical data.

16. The method of claim 14, wherein the step of analyzing the at least one high intensity jerk within the test harness module stored within the memory of the server further comprises determining a probability of a reoccurrence of the at least one high intensity jerk.

17. The method of claim 11, wherein the step of determining whether the analysis on the at least one high intensity should be performed at the vehicle or at the server further comprises determining an optimization of a size of the data.

18. The method of claim 11, the step of determining whether the analysis on the at least one high intensity should be performed at the vehicle or at the server further comprises determining a tolerance of latency of detection of the plurality of jerks.

19. A computer program product having embodied thereon a computer program for real-time monitoring of a vehicle, the computer program product comprising:

a program code for receiving data associated with a plurality of jerks detected by a three-axis accelerometer, wherein the three-axis accelerometer is embedded in the vehicle and configured to capture at least one signal from vehicle chassis;

a program code for comparing an intensity of each jerk of the plurality of jerks to a predefined jerk threshold;

a program code for capturing at least one high intensity jerk of the plurality of jerks, wherein the at least one high intensity jerk has an intensity level of at least the predefined jerk threshold;

a program code for determining an elapsed time for each of the at least one high intensity jerk, wherein the elapsed time is indicative of a time between an observation of the at least one high intensity jerk and a feedback sent to a user;

a program code for comparing the elapsed time for each of the at least one high intensity jerk to a predefined time threshold; and

a program code for determining whether an analysis on the at least one high intensity jerk should be performed at the vehicle or at a server located remotely from the vehicle, wherein the analysis is based on the comparison of the elapsed time to the predefined time threshold.

20. The computer program product of claim 19, further comprising a program code for receiving a position stamp of the vehicle for the at least one high intensity jerk from a Global Positioning System (GPS).