Big telematics data network communication fault identification method

• US 20170150442A1
• Filed: 12/05/2016
• Published: 05/25/2017
• Est. Priority Date: 11/20/2015
• Status: Active Grant

• Current Assignee: GeoTab Incorporated
• Original Assignee: GeoTab Incorporated
• Inventors: Dodgson, Daniel Michael, Zhao, Yi, Cawse, Neil Charles
• Granted Patent: US 10,299,205 B2
• Time in Patent Office: Days
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 52/0216 using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

Apparatus, device, methods and system relating to a vehicular telemetry environment for the for identifying in real time unpredictable network communication faults based upon pre-processed raw telematics big data logs that may include GPS data and an indication of vehicle status data, and supplemental data that may further include location data and network data.

Claims

1. A big telematics data communication fault determination method comprising:

asynchronously establishing at least one expected communication period in a mobile device based upon an vehicle status, communicating from said mobile device to a remote device at least one of a signal, or data, or message at intervals of said at least one expected communication period,

asynchronously establishing at least one expected communication period in said remote device based upon said vehicle status,

wherein said remote device comparing in a selected time frame a number of actual communications received from said mobile device based upon said at least one expected communication with said at least one expected communication in the remote device and indicating a fault when said number of actual communication is not equal to said at least one expected communication in the remote device within said selected time frame.

2. A big telematics data communication fault determination method as in claim 1 wherein said vehicle status is an ignition status indication.

3. A big telematics data communication fault determination method as in claim 1 wherein said at least one expected communication period is based upon an active mode.

4. A big telematics data communication fault determination method as in claim 3 wherein said active mode includes a first timely communication period for communicating with said remote device.

5. A big telematics data communication fault determination method as in claim 4 wherein said first timely communication period establishes a first expected communication.

6. A big telematics data communication fault determination method as in claim 5 wherein said first expected communication is a period of 100 seconds.

7. A big telematics data communication fault determination method as in claim 71 wherein said at least one expected communication period is based upon an inactive mode.

8. A big telematics data communication fault determination method as in claim 7 wherein said inactive mode includes a second timely communication period for communicating with said remote device.

9. A big telematics data communication fault determination method as in claim 8 wherein said second timely communication period establishes a second expected communication.

10. A big telematics data communication fault determination method as in claim 9 wherein said second expected communication is a period of 1800 seconds.

11. A big telematics data communication fault determination method as in claim 7 wherein said inactive mode includes a third timely communication period for communicating with said remote device.

12. A big telematics data communication fault determination method as in claim 11 wherein said third timely communication period establishes a third expected communication.

13. A big telematics data communication fault determination method as in claim 12 wherein said third expected communication is 86,400 seconds.