IP Library › Granted Patent US 12,205,419
Granted Patent B2
US 12,205,419 · App. 17/685,178 · Granted Jan 21, 2025

Mobile compute system with interface verification mechanism and method of operation thereof

Inventor: James Anthony Curtis (Temecula, CA)
Assignee: MOJ.IO, Inc.
G07C5/0808G01R31/55G07C5/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 12,205,419
App. No.
17/685,178
Granted
Jan 21, 2025
Kind
B2
Abstract

A method of operation of a mobile compute system comprising: identifying a vehicle prepared to travel by monitoring an on-board diagnostics; detecting an unplug event based on a message from the on-board diagnostics; detecting a trip in progress during the unplug event; and transferring the message identifying a loose connector pin in an on-board diagnostic port during the trip in progress for displaying on a device.

Claims (57)

1. A method of operation for a mobile compute system comprising:

identifying a vehicle prepared to travel by monitoring an on-board diagnostics;

detecting an unplug event based on an error message from a communication protocol of the on-board diagnostics;

detecting a trip in progress during the unplug event; and

transferring a message group identifying a loose connector pin in an on-board diagnostic port during the trip in progress for displaying on a device.

2. The method as claimed in claim 1 wherein identifying the vehicle prepared to travel includes:

receiving the message group from an engine control unit node;

receiving the message group from a braking system node;

receiving the message group from a transmission system node and

determining an engine is on, a brake is engaged, and a transmission is engaged.

3. The method as claimed in claim 1 wherein detecting the unplug event includes receiving the message group out of sequence, performing a reauthentication with a gateway module, detecting a new car event with a speed greater than a threshold, issuing a diagnostic trouble code (DTC), or a combination thereof.

4. The method as claimed in claim 1 further comprising detecting the loose connector pin during authenticating with a gateway module.

5. The method as claimed in claim 1 wherein displaying the message group identifying a loose connector pin includes detecting the unplug event three times in a time window.

6. The method as claimed in claim 1 further comprising:

monitoring functions of the vehicle after a first occurrence of the unplug event includes receiving the message group from subsystems of the vehicle; and

monitoring vehicle location/route after the first occurrence of the unplug event includes receiving the message group from a control unit with location information from a location circuit.

7. The method as claimed in claim 1 further comprising transferring trip statistics for display includes:

reporting a disconnect based on the unplug event detection; and

logging the occurrence of the unplug event in a trip statistics displayed in the vehicle.

8. A mobile compute system comprising:

a communication circuit configured to:

transmit a message, identifying a vehicle prepared to travel, through an on-board diagnostic, and

receive the message from the on-board diagnostic identifying a loose connector pin in an on-board diagnostic port;

a control circuit, coupled to the communication circuit, configured to:

determine an unplug event has occurred based on an error message from a communication protocol of the on-board diagnostic,

detect a trip in progress during the unplug event, and

transfer a message group, to identify the loose connector pin in the on-board diagnostic port, for displaying on a device.

9. The system as claimed in claim 8 wherein the control circuit is further configured to:

receive the message group from an engine control unit node;

receive the message group from a braking system node; and

receive the message group from a transmission system node; and

determine an engine is on, a brake is engaged, and a transmission is engaged.

10. The system as claimed in claim 8 wherein the control circuit is further configured to detect the unplug event includes receive the message group out of sequence, perform a reauthentication with a gateway module, detect a new car event with a speed greater than a threshold, issue a diagnostic trouble code (DTC), or a combination thereof.

11. The system as claimed in claim 8 wherein the control circuit is further configured to detecting the loose connector pin during authentication with a gateway module.

12. The system as claimed in claim 8 wherein the control circuit is further configured to display the message group to identify a loose connector pin includes detecting the unplug event three times in a time window.

13. The system as claimed in claim 8 wherein the control circuit is further configured to:

monitor functions of the vehicle after a first occurrence of the unplug event includes receiving the message group from subsystems of the vehicle; and

monitor vehicle location/route after the first occurrence of the unplug event includes receiving the message group from a control unit with location information from a location circuit.

14. The system as claimed in claim 8 wherein the control circuit is further configured to transfer trip statistics for display includes:

reporting a disconnect based on the unplug event detection; and

logging the occurrence of the unplug event in a trip statistics displayed in the vehicle.

15. A non-transitory computer readable medium including instructions executable by a control circuit for a mobile compute system comprising:

identifying a vehicle prepared to travel by monitoring an on-board diagnostics;

detecting an unplug event based on an error message from a communication protocol of the on-board diagnostics;

detecting a trip in progress during the unplug event; and

transferring a message group identifying a loose connector pin in an on-board diagnostic port during the trip in progress for displaying on a device.

16. The non-transitory computer readable medium as claimed in claim 15 wherein identifying the vehicle prepared to travel includes:

receiving the message group from an engine control unit node;

receiving the message group from a braking system node;

receiving the message group from a transmission system node and

determining an engine is on, a brake is engaged, and a transmission is engaged.

17. The non-transitory computer readable medium as claimed in claim 15 wherein detecting the unplug event includes receiving the message group out of sequence, performing a reauthentication with a gateway module, detecting a new car event with a speed greater than a threshold, issuing a diagnostic trouble code (DTC), or a combination thereof.

18. The non-transitory computer readable medium as claimed in claim 15 further comprising detecting the loose connector pin during authenticating with a gateway module.

19. The non-transitory computer readable medium as claimed in claim 15 wherein displaying the message group identifying a loose connector pin includes detecting the unplug event three times in a time window.

20. The non-transitory computer readable medium as claimed in claim 15 further comprising:

monitoring functions of the vehicle after a first occurrence of the unplug event includes receiving the message group from subsystems of the vehicle; and

monitoring vehicle location/route after the first occurrence of the unplug event includes receiving the message group from a control unit with location information from a location circuit.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 2, 2022
From: CURTIS, JAMES ANTHONY
To: MOJ.IO, INC.
Reel/Frame 059151/0827 →
Continuity (1)
Related Publication 20230282038A1 · Sep 7, 2023
References Cited (16)
US 6529808B1 · Diem · 2003 [cited by examiner]
US 10417839B2 · Allen, Jr. et al. · 2019 [cited by applicant]
US 20090150118A1 · Naima · 2009 [cited by applicant]
US 20170093866A1 · Ben-Noon · 2017 [cited by examiner]
US 20170345227A1 · Allen, Jr. et al. · 2017 [cited by applicant]
US 20180182182A1 · Meyer · 2018 [cited by examiner]
US 20180227306A1 · Borkowicz · 2018 [cited by examiner]
US 20190007511A1 · Rodriguez · 2019 [cited by examiner]
US 20190013621A1 · Buhlman · 2019 [cited by examiner]
US 20190228654A1 · Olsen · 2019 [cited by examiner]
US 20190301845A1 · Nickel · 2019 [cited by applicant]
US 20210375076A1 · Scotland et al. · 2021 [cited by applicant]
CN 111426984A · 2020 [cited by examiner]
TW 201313527A · 2013 [cited by examiner]
WO WO2019043471A1 · 2019 [cited by examiner]
WO WO2020089643A1 · 2020 [cited by examiner]