Vehicle diagnostic communications system and application

• US 8,897,952 B1
• Filed: 08/29/2013
• Issued: 11/25/2014
• Est. Priority Date: 05/20/2011
• Status: Active Grant

• Current Assignee: Dashlogic Incorporated
• Original Assignee: Dashlogic Incorporated
• Inventors: Palmer, Brian
• Primary Examiner(s): Cheung, Mary
• Assistant Examiner(s): BUTLER, RODNEY ALLEN
• Application Number:
  US14/013,940
• Time in Patent Office: 453 Days
• Field of Search: 701/29.1, 701/33, 701/35, 714/25, 714/699
• US Class Current: 701/31.5
• CPC Class Codes: G07C 2205/02 using a vehicle scan tool
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A system for web-enabled vehicle diagnostic communications that includes a transceiver having a web server supporting WebSockets and is connected to a vehicle data port. The transceiver accepts web connections from various computing devices. The transceiver receives URIs from computing devices over the web connection and checks to determine if they are diagnostic URIs, in which case the web connection is converted into a diagnostic WebSocket capable of bidirectional vehicle communications. A web application may be used to operate the system.

Claims

1. A web-enabled vehicle diagnostic system configured to be in electrical communication with a vehicle data port and configured to communicate with a computing device, the diagnostic system comprising:

a transceiver that communicates with the vehicle data port, the transceiver including a built-in web server supporting WebSockets;

the transceiver configured to accept at least one web connection from the computing device, the computing device communicating at least one Uniform Resource Identifier or URI to the transceiver over the accepted web connection;

the transceiver further configured to check the at least one URI and to recognize one or more predetermined URIs as being diagnostic URIs;

the transceiver further configured to convert any web connection using a recognized diagnostic URI from a web connection into a diagnostic WebSocket;

the transceiver further configured to listen for predetermined commands on the diagnostic WebSocket that are not vehicle diagnostic communication requests, upon receipt of which the transceiver acts on those commands in a predetermined way and provides a response over the diagnostic WebSocket;

the transceiver further configured to listen for vehicle diagnostic communication requests on the diagnostic WebSocket, upon receipt of which the transceiver processes, prioritizes and sequences the requests in compliance with predetermined vehicle protocol requirements;

the transceiver configured to send processed requests to the vehicle data port so that the vehicle may operate on the processed requests and pass back to the transceiver any vehicle communications that incorporate data from the vehicle and are responsive to the processed requests; and

selectively transmitting the responsive vehicle communications from the transceiver to the computing devices over the diagnostic WebSocket.

2. The system of claim 1 in which the transceiver contains a built-in data storage medium containing a web app and the transceiver is further configured:

to check the at least one URI and to recognize predetermined URIs as being web app URIs; and

to download a web app to the computing devices over the web connection upon recognizing a web app URI;

and wherein the web app is configured to make one or more additional web connections to the transceiver and to communicate diagnostic URIs over the web connections.

3. The system of claim 1 in which the computing device accesses a web app from a server external to the transceiver or accesses a web app downloaded from an app delivery system, the accessed web app being configured to make one or more web connections to the transceiver and to communicate diagnostic URIs over the web connection.

4. The system of claim 1 in which the transceiver is further configured:

to analyze communications requests received on the diagnostic WebSocket and to classify predetermined communications requests as being Text Frames or Binary Frames;

to further process each Text Frame communications request in a predetermined way to identify certain predetermined Text Frame communications requests as being either a human readable command, a Hayes command, or a text encoded binary command;

to further process any human readable commands in a predetermined way to identify certain human readable commands as being vehicle communications requests and other human readable commands as not being vehicle communications requests;

to further process any Hayes commands in a predetermined way to identify certain Hayes commands as being vehicle communications requests and other Hayes commands as not being vehicle communications requests;

to further process any text encoded binary commands and to convert the text encoded binary commands into binary data requests and to process the binary data requests in a predetermined way to identify certain binary data requests as being vehicle communications requests and other requests as not being vehicle communications requests;

to process each Binary Frame communications request as a binary data request in a predetermined way to identify certain Binary Frame communications requests as being vehicle communications requests and other Binary Frame communications requests as not being vehicle communications requests;

to listen for any commands or requests that are not vehicle diagnostic communication requests, upon receipt of which the transceiver acts on those commands or requests in a predetermined way and provides a response over the diagnostic WebSocket;

to listen for any commands or requests that are vehicle diagnostic communication requests, upon receipt of which the transceiver processes, prioritizes and sequences the requests in compliance with predetermined vehicle protocol requirements;

to send processed requests to the vehicle data port so that the vehicle may operate on the processed requests and pass back to the transceiver any vehicle communications that incorporate data from the vehicle and are responsive to the processed requests; and

selectively to transmit the responsive vehicle communications from the transceiver to the computing devices over the diagnostic WebSocket.

5. The system of claim 1 in which the transceiver contains a user configurable setting specifying a limit to the number of concurrent diagnostic WebSocket connections allowed and is further configured such that when a new diagnostic WebSocket connection is made that exceeds the user configured limit, the transceiver automatically drops or doses an existing diagnostic WebSocket connection.

6. The system of claim 1 in which the transceiver is further configured to allow connection and disconnection from the vehicle data port.

7. The system of claim 1 in which the transceiver is provided as original equipment in the vehicle.

8. The system of claim 1 in which the transceiver is provided as an after-market item for the vehicle.

9. The system of claim 1 in which the electrical communication between the transceiver and the vehicle data port is a direct connection.

10. The system of claim 1 in which the electrical communication between the transceiver and the vehicle data port includes a pass-thru hardware interface.

11. The system of claim 1 in which the electrical communication between the transceiver and the vehicle data port is a wireless connection.

12. The system of claim 2 in which the transceiver contains built-in wireless communication functionality and is configured to create a standalone wireless network that the computing device may join, the transceiver is further configured to listen for wireless communications sent from any computing device that has joined the wireless network and to detect wireless communications meant for devices other than the transceiver and wherein the transceiver responds to the detected communications in a predetermined manner.

13. The system of claim 2 in which the web app is configured to make web connections to more than one separate transceiver simultaneously and to communicate diagnostic URIs over the web connections.

14. The system of claim 12 in wherein the transceiver response to the detected communications comprises redirection to a predetermined web page.

15. The system of claim 3 in which the web app is configured to make web connections to more than one separate transceiver simultaneously and to communicate diagnostic URIs over the web connections.

16. A method of enabling communications between at least one computing device containing a web-enabled diagnostic app and a transceiver that includes a built-in web server that supports WebSockets, the method comprising:

creating one or more web connections using the web-enabled diagnostic app and the transceiver while the transceiver is in electrical communication with a vehicle data port;

communicating, via the web-enabled diagnostic app, predetermined Uniform Resource Identifiers or URIs over the web connections to the transceiver wherein some predetermined URIs are diagnostic URIs that cause any web connection containing a diagnostic URI to be converted into a diagnostic WebSocket capable of bidirectional vehicle diagnostic communication with each computing device;

sending at least one of predetermined commands and predetermined vehicle diagnostic communications to the transceiver over the diagnostic WebSocket; and

receiving responses to the at least one of predetermined commands and predetermined vehicle diagnostic communications from the transceiver over the diagnostic WebSocket.

17. The method of claim 16 further comprising:

sending a communications request over the diagnostic WebSocket using the web-enabled diagnostic app before or after a timer initiates a predetermined timeout period, the expiration of the timeout period causing a call to a predetermined timeout callback function inside the web-enabled diagnostic app, the timeout callback function configured to take a predetermined timeout action in the event that communications responses have not been received within the predetermined timeout period;

employing a receive callback function to receive vehicle and other communications data from the transceiver on the diagnostic WebSocket, the receive callback function configured;

to be called when communications responses are received from the transceiver on the diagnostic WebSocket;

to process the communications responses in a predetermined way; and

to cancel the timer when communications responses are received by the receive callback function or to notify the timeout callback function that communications responses have been received.

18. The method of claim 16 in which the web-enabled diagnostic app is further configured to automatically reconnect the web connection or diagnostic WebSocket in the event that the web connection or diagnostic WebSocket has been dropped, lost, closed, or stalled.

19. The method of claim 17 in which the predetermined timeout action is the action of resending the communications request over the diagnostic WebSocket until a predetermined retransmission limit is reached.

20. The method of claim 17 in which the predetermined timeout action is the action of dropping or closing the diagnostic WebSocket connection.