WO2017131763A1

WO2017131763A1 - Motor-vehicle-hosted can-bus data and network communications system

Info

Publication number: WO2017131763A1
Application number: PCT/US2016/015744
Authority: WO
Inventors: Robert P. Hodson; Brett J. Mcnalley; Matthew Adam STARR
Original assignee: Hydro Electronic Devices, Inc.
Priority date: 2016-01-29
Filing date: 2016-01-29
Publication date: 2017-08-03

Abstract

A vehicle information processing system, an electronic control device for processing information relating to a vehicle, and a method of processing information relating to a vehicle are provided. The system and device are configured to decode vehicle information concerning diagnostic data for the various systems of an automotive machine or vehicle using decoding information stored within the electronic control device. The electronic control device by itself and as part of the system is configured to generate webpage data from the decoded information and broadcast the webpage to a user device where the decoded data is rendered such that the diagnostic data is presented as a human-readable representative of the data. The method is a stepwise procedure for achieving the results of the system and device.

Description

MOTOR- VEHICLE-HOSTED CAN-BUS DATA AND NETWORK

COMMUNICATIONS SYSTEM

BACKGROUND OF THE INVENTION

[0001] The present invention relates generally to the field of vehicle networking

communication. The present invention relates specifically to a vehicle information processing system and an electronic control device for processing information relating to a vehicle.

SUMMARY OF THE INVENTION

[0002] One embodiment of the invention relates to a vehicle which generates webpage data which represents information relating to the vehicle. The vehicle includes a vehicle data bus which communicates vehicle data in accordance with a vehicle network communication protocol. The vehicle additionally includes at least one control unit coupled to the vehicle data bus and a vehicle system. The vehicle further includes a vehicle computer coupled to the data bus. The vehicle computer receives encoded data representative of operational parameters of the vehicle system, where the encoded data is encoded for use with the vehicle network communication protocol. Additionally, the vehicle computer has stored decoding data corresponding to the vehicle network communication protocol associated with the encoded data. The vehicle computer further has stored programming which generates webpage data from the encoded data and the decoding data. The webpage data is useable by a user device external to the vehicle to generate a human-readable representative of the encoded data referenced to the operational parameters of the vehicle system.

[0003] Another embodiment of the invention relates to an electronic control device for processing information relating to a vehicle. The electronic control device includes a database containing a plurality of vehicle network decoding information corresponding to a plurality of vehicle network communication protocols. The electronic device also includes a vehicle network connector. The vehicle network connector is configured to pass-through coded data representative of the operation of an automotive machine received from a vehicle network. The coded data is encoded for use with one of the plurality of vehicle network communication protocols. The electronic control device further includes a vehicle parameter control module coupled to the database and the vehicle network connector. The vehicle parameter control device is configured to receive the coded data from the vehicle network connector. The vehicle parameter control device is further configured to retrieve the vehicle network decoding information from the database corresponding to the specific vehicle network communication protocol associated with the coded data. The vehicle parameter control device is also configured to decode the coded data using the vehicle network decoding information, and output the decoded data. The electronic control device further includes a web server coupled to the vehicle parameter control module. The web server is configured to receive the decoded data output from the vehicle parameter control module. The web server is also configured to generate webpage data containing the decoded data, and output the webpage data. The electronic control device also includes a first communication interface coupled to the web server. The first communication interface is configured to receive the webpage data output from the web server and broadcast the webpage data out from the electronic control device.

[0004] Another embodiment of the invention relates to a method of processing information relating to a vehicle. The method includes the step of receiving at an electronic control device coded data from a vehicle network encoded for use with a specific vehicle network

communications protocol. The coded data is representative of the operation of an automotive machine. The method also includes the step of comparing the coded data to decoding

information stored in a database of the electronic control device. The decoding information corresponds to a plurality of vehicle network communication protocols. The method further includes the step of identifying the specific vehicle communication protocol used to encode the data based on the comparison. The method also includes the step of retrieving the decoding information corresponding to the specific communications protocol used to encode the coded data from the database. The method further includes the step of decoding the coded data, using the retrieved decoding information. The method also includes the step of broadcasting the decoded data out from the electronic control device as webpage data. The web page data is broadcast such that when rendered the webpage data displays a human-readable version of the data representative of the operation of an automotive machine.

[0005] Alternative example embodiments relate to other features and combinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] This application will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements in which:

[0007] FIG. 1 shows a block diagram of a system for processing information related to a vehicle according to an example embodiment.

[0008] FIG. 2 is a structural diagram of a vehicle network database according to an example embodiment.

[0009] FIG. 3 is a diagram of a connection mode of the system according to an example embodiment.

[0010] FIG. 4 is a diagram of another connection mode of the system according to another example embodiment.

DETAILED DESCRIPTION

[0011] Referring generally to the figures, various embodiments of a vehicle information processing system and an electronic control device for processing information relating to a vehicle are shown. In modern automotive vehicles the internal systems (e.g. motor, brakes, climate, etc.) are monitored by electronic control units. These electronic control units communicate with each other over an internal vehicle network using a proprietary

communication protocol. The communication protocol varies depending on the manufacturer of the vehicle or electronic control units. The internal network can be accessed by electronic devices connected to the vehicle network to provide diagnostic information and/or control capability over the vehicle to a user. However, access to the full breadth of data and control capabilities is limited.

[0012] Access to the internal vehicle network may be provided in two ways. First, a subset of the diagnostic data is provided using standard communication protocols (e.g. on-board diagnostics (OBD)-II). Second, the entire breadth of diagnostic information and control capability is accessible by a device capable of deciphering and communicating using the specific proprietary communication protocol used by a specific vehicle. Devices for monitoring vehicle information communicate using a standard communication protocol or are designed to work with a specific proprietary vehicle communications protocol, thus limiting the amount of data a user can gather or the type of vehicle to which a device can be connected. Further, systems may utilize a complicated proprietary application or software interface to display data and execute commands. This feature increases user costs and decreases future flexibility. Accordingly, Applicant has identified the need for a single device capable of retrieving all available diagnostic information and control capabilities that is also capable of deciphering a multitude of the proprietary communication protocols used by different vehicles and/or electronic control units and presents the data and control capabilities in a standard uncomplicated interface of the type provided via a standard internet web browser.

[0013] Referring to FIG. 1, an embodiment of a novel vehicle information processing system

1 is shown. In one embodiment, the vehicle information processing system 1 includes a vehicle computer or electronic control device 2, a vehicle network 23, and a user device 4. User device 4 is configured to exchange data through a wired or wireless communication interface. Various embodiments of the user device 4 are contemplated such as a handheld computer, smartphone, laptop computer, or desktop computer. Electronic control device 2 is electrically coupled to vehicle network 23. Vehicle network 23 has at least one electronic or vehicle control unit 22.

Electronic control device 2 is coupled to the vehicle network 23 by a physical bus connector such as a controller area network ("CAN") bus. It should be understood that other methods of electronic coupling are contemplated, including wireless communication and wired connections such as Ethernet. In one embodiment, electronic control device 2 is a "stand-alone" unit, such as a printed circuit board. In another embodiment, the electronic control device 2 is integrated into a vehicle hosting vehicle network 23. In another embodiment, the electronic control device 2 includes an analog input for receiving analog signals from the vehicle having vehicle network 23.

[0014] Vehicle network 23 is a vehicle data bus which communicates vehicle data using a vehicle network communication protocol. Electronic control units 22 (e.g. ECUl, ECU2, ECU3. . . ECUn) gather or receive data representing the operational parameters of the vehicle systems coupled to the electronic control units 22.

[0015] One example of an ECU is an engine control module of the type which uses a microprocessor which can process the inputs from the engine sensors in real-time. An electronic control unit such as an engine control module typically contains the hardware and software (firmware). The hardware consists of electronic components on a printed circuit board (PCB), ceramic substrate or a thin laminate substrate. The main component on this circuit board is a microcontroller chip (CPU). The software is stored in the microcontroller or other chips on the PCB, typically in EPROMs or flash memory so the CPU can be re-programmed by uploading updated code or replacing chips. An engine control module (or any ECU of Electronic Control Units 22) may receive and use data from other ECUs coupled to network 23. For example, an engine control module may use data from transmission control units, a traction control unit, and the like.

[0016] Various embodiments having different vehicle systems connected to respective electronic control units 22 include engine control systems, braking/anti-lock systems, traction control systems, climate control systems, engine temperature and control systems, lubricant quality and temperature monitoring systems, navigation systems, locking/anti-theft systems, audio systems, display systems, camera systems, load handling systems, tire inflation systems, etc.

[0017] The data received and transmitted by the electronic control units 22 over network 23 is encoded or coded to be used with the specific vehicle network communications protocol used by the vehicle network 23. Each electronic control unit transmits and receives data for a different respective vehicle system. Examples of the type of such data include diagnostic data, sensor data, vehicle system control parameter data, etc.. [0018] In operation, the electronic control device 2 receives the encoded data from the vehicle network 23. Electronic control device 2 decodes the coded data using decoding data, algorithms or information stored within a vehicle network database 8 of electronic control device 2. Electronic control device 2 generates webpage data from the decoded data according to programming stored in electronic control device 2. The webpage data is generated as Hyper Text Markup Language ("HTML"). The generated webpage data is useable by user device 4 to generate a human-readable representative of the decoded version of the encoded data referenced to the operational parameters of the vehicle system. In addition to data from units 22, the webpage data may include data representative of the analog signals received at the analog input of the electronic control device 2 applied to the physical device interface/connector 12.

[0019] The webpage data is broadcast from the electronic control device 2, and received by the user device 4. User device 4 displays the webpage data such that it renders the decoded data as a human-readable version or representative of the operational parameters of the vehicle system corresponding to those parameters.

[0020] User device 4 displays or renders the webpage data in a web browser 17. The web browser displays or renders the webpage data using standard script languages (e.g.

JavaScript). User device 4 may alternately display the webpage data in a native application 18. User device 4 includes a communication interface 16 which receives the webpage data from the electronic control device 2 and passes the webpage data to the web browser 17 or native application 18.

[0021] Vehicle information processing system 1 also includes a remote server 3. Electronic control device 2 sends the decoded data to remote server 3 using an external communication network. Examples of external communication networks include the internet, local area network

("LAN"), satellite, and cellular networks. A router 5 is connected to electronic control device 2 and facilitates connection to remote server 3, through the external communication network.

Remote server 3 stores the decoded data in a data storage module 21. Data storage module 21 is a long term non-volatile storage medium with retrieval capabilities, and includes a user interface

25 for inspecting the data stored in data storage module 21. Remote server 3 also includes a server interface 19, which provides the logical and physical interface or connection point between remote server 3 and the external communication network. Remote server 3 has a data processing module 20 for controlling access to remote server 3 and maintaining the other modules, such as data storage module 21, contained within remote server 3.

[0022] Still referring to FIG. 1, an internal schematic of an embodiment of electronic control device 2 is shown. Electronic control device 2 includes a memory module 6 a vehicle parameter control module 7, a vehicle network database 8, a non-volatile data storage module 9, a web server 10, a physical device interface or connector 11, a vehicle network interface or connector 12, an authentication module 13, communication interfaces 14, a data upload logic module 15, and a communication logic module 24.

[0023] Vehicle network database 8 is coupled to vehicle parameter control module 7 and contains a plurality of vehicle network decoding information corresponding to a plurality of vehicle network communication protocols. An example structure for vehicle network database 8 is show in FIG. 2.

[0024] Vehicle network connector 12 is coupled to vehicle parameter control module 7 and is configured to connect with a vehicle network such as vehicle network 23. Connector 12 is configured to receive coded data, which is encoded for use with one of the plurality of vehicle network communication protocols and representative of the operation of an automotive machine, from a vehicle network such as vehicle network 23. Vehicle network connector 12 is configured to pass-through coded data to vehicle parameter control module 7. A variety of connection methods are contemplated including wireless connection methods (e.g. Bluetooth, Wi-Fi, or cellular, etc.) and wired connection methods (e.g. CAN, Ethernet, serial, fiber optics, FlexRay, etc.). In one embodiment, vehicle network connector 12 is a male CAN bus connector.

[0025] Vehicle parameter control module 7 is configured to receive coded data from the vehicle network connector 12. Vehicle parameter control module 7 is configured to search or parse the coded data for unique identifiers corresponding to the decoding information stored in vehicle network database 8. The coded data may be network traffic made up of data packets.

Where the coded data is network traffic, it is filtered by looking for the unique identifiers at various locations in each network data packet. If the packet matches the decoding information stored for any of the database entries in database 8, it will be decoded, and otherwise it will be ignored. In this way, vehicle parameter control module 7 is configured to identify the specific communication protocol associated with the coded data and retrieve the corresponding decoding information from the vehicle network database 8.

[0026] Once vehicle parameter control module 7 has retrieved the corresponding decoding information from database 8, vehicle parameter control module 7 is configured to decode the data by converting the data into an electronic representation of a textual or human-readable representative of the operational parameters of the vehicle having the vehicle network to which the electronic control device 2 is connected. For example, a numerical value of 100 identified as the coded value for the temperature of an engine will be decoded to data representing a text string containing the numerical value 100 and the corresponding degree unit (e.g. Celsius, Fahrenheit, etc.). The electronic representation of the human-readable representative for the decoded data can also be a visual indicator, such as a mark on a graph or scale.

[0027] In other instances the coded data value represents a binary condition (e.g. on or off). In that instance, vehicle parameter control module 7 is configured to identify coded data as representing a binary condition such as the status of the parking break and decode the data into data representing a text string. For example, a coded value of 0 would be decoded into electronic data for the text "off, and a coded value of 1 would be decoded into electronic data for the text "on". Vehicle parameter control module 7 may also be configured to decode the binary condition into an electronic representation of a non-textual indicator of the condition such as a colored indicator light that can be rendered on a web page in proximity to text describing the system associated with the binary condition.

[0028] Vehicle parameter control module 7 is further configured to output the decoded data to web server 10. The decoded data may be sent to web server 10 at a periodic rate, when the data changes value, or in response to a direct request. The coded data received at network connector 12 contains multiple parameters, with each parameter corresponding to different operations of the vehicle that can be monitored (e.g. engine temp, rpm, parking brake status, climate, etc.). The parameters have group associations stored in database 8. Database 8 also contains values for requesting an individual parameter, group names, and parameter-to-group membership. [0029] Web server 10 is coupled to vehicle parameter control module 7 and is configured to receive the decode data from vehicle parameter control module 7. Web server 10 is configured to format the decoded data into webpage data and output that data to the communication interfaces 14. In another embodiment, the webpage data is formatted in vehicle parameter control module 7 and web server 10 is configured to host the complete webpage data and output the webpage data to communication interfaces 14. The webpage data consists of HTML data representing the formatting, style, and features of a webpage rendered from the webpage data, and a stream of the decoded data, using web sockets for example. The decoded data is placed into preconfigured code blocks corresponding to the specific operational parameter the decoded data represents. For example, the decoded element from the stream of data corresponding to the status of the parking break would be placed in a preconfigured location within the web page, as defined by the HTML block for indicating the parking break status, and when the parking brake state changes on the vehicle, the stream of data would contain updated information for the parking brake's new state, which in turn would be used to update the web page.

[0030] In one embodiment, the HTML block is preconfigured to render a textual

representation of the decoded data from the stream of data. For example, where the coded and decoded data relate to the temperature of the engine a web page rendered from the HTML code containing the temperature information will display readable text indicating the numerical value and unit (e.g. 100 degrees Celsius) where the exact formatting is determined by the underlying HTML block, but the value of the temperature will be updated from the stream of data. In another embodiment, the HTML block is preconfigured to render a non-textual representation of the decoded data. For example, where the coded and decoded data relate to the temperature of the engine, a web page rendered from the HTML code containing the temperature information will display the temperature information in a visual or graphical manner such as a digital thermometer or graph, and the visual state of the readout will be updated by specific data contained within the connected stream of data. Various combinations of textual and non-textual preconfigured HTML block assignments for the various operational parameters are

contemplated. In one embodiment, each operational parameter has multiple textual and nontextual preconfigured HTML blocks. Web server 10 is configured to use a default HTML block for each parameter and is further configured with an application programming interface by which a user can select a different HTML block from the default. The different HTML code blocks for the different operational parameters can represent different pages, different sections of pages, or a combination of the two for a webpage rendered from the combination of all the HTML code blocks.

[0031] Communication interfaces 14 can be a single communication interface or multiple communication interfaces as depicted in FIG. 1. Communication interfaces 14 are coupled to web server 10 and are configured to receive webpage data from web server 10. Communication interfaces 14 are configured to broadcast the webpage data out from electronic control device 2 where it can be received by a user device, such as user device 4, and rendered as a webpage displaying the human-readable representatives of the decoded data. Communication interfaces 14 can use a single communication medium to broadcast the webpage data or alternatively can be configured to use multiple communication mediums. Example communication mediums include serial, WI-FI, Bluetooth, and Ethernet.

[0032] Authentication module 13 is coupled to web server 10 and vehicle parameter control module 7. Authentication control module 13 is configured to verify user credentials received from web server 10 and sent from a user device such as user device 4. Authentication module 13 is configured to compare the received user credentials against locally stored credentials, and allow access to functions in vehicle parameter control module 7 if the received user credentials match any of the locally stored credentials. The locally stored credentials may be stored in database 8, memory module 6 or non-volatile data storage module 9. In one embodiment of electronic control device 2 (not shown), authentication module 13 is omitted. In this instance, either vehicle parameter control module 7 is configured to perform the functions of

authentication module 13, or electronic control device 2 is configured to operate without verifying user credentials.

[0033] Electronic control device 2 includes a memory module 6 coupled to vehicle parameter control module 7. Memory module 6 may be a standard computer memory such as volatile random access memory ("RAM"). Vehicle parameter control module 7 is configured to store the decoded data in memory module 6 such that the decoded data has the same corresponding parameters as the coded data. The decoded data stored in memory module 6 can be a copy of the data decoded in vehicle parameter control module 7. Storing the decoded data in memory module 6 overwrites any previously stored data.

[0034] Vehicle parameter control module 7 is configured to store the decoded data in memory module 6 such that each parameter of the decoded data is separately accessible. The parameters can be retrieved by multiple mechanisms: directly asking for an individual parameter, through a textual label, a database index associated to parameter; or by requesting a group of parameters, to which one or several parameters are subscribed too. The membership to one or many groups will be stored in the vehicle network database 8 and a request for a particular group will result in the complete list of member parameters to be sent back to the web server 10.

[0035] Communication interfaces 14 are configured to receive a predefined signal from a user device, such as user device 4 and pass the predefined signal to vehicle parameter control module 7. Configuring electronic control device 2 to receive a predefined signal, improves security and reliability by strictly limiting the control available to a user. The predefined signal may be a request to automatically broadcast a parameter or group of parameters. The list of parameters requested, is dependent on the content displayed on a user device sending the request, and is customizable for each individual application. Alternatively, the predefined signal is a request for a specific parameter. Vehicle parameter control module 7 is configured to analyze the predefined signal and identify the parameter corresponding to the request, retrieve the decoded version of that parameter from memory module 6, and send the decoded data parameter to web server 10. Web server 10 is configured to format the decoded data parameter into webpage data and output that data to communication interfaces 14 which are configured to broadcast it out of electronic control device 2.

[0036] The predefined signal may also be a request for a specific automotive machine operation (e.g. lights on, apply brakes, etc.), and vehicle network database 8 contains a plurality of automotive machine operation command data corresponding to a plurality of vehicle network communication protocols. Vehicle parameter control module 7 is configured to analyze the predefined signal and determine the specific automotive machine operation requested. Vehicle parameter control module 7 is further configured to retrieve from vehicle network database 8 the command data corresponding to the operation requested that is used with the network communication protocol used by a vehicle network, such as vehicle network 23 connected to network connector 12.

[0037] Vehicle parameter control module 7 is configured to identify the specific network communication protocol by parsing the concurrently incoming network traffic. Vehicle parameter control module 7 may alternatively be configured to identify the specific network communication protocol by parsing the prior incoming network traffic, (e.g. the most recently received transmission) and store that identification in memory module 6, database 8 or nonvolatile data storage module 9, and use the stored identification to retrieve the corresponding command data. Where the command data stored in database 8 is a complete message, vehicle parameter control module 7 is configured to pass the command data retrieved from vehicle network database 8 to network connector 12, which is configured to send the command data out to an automotive machine over a vehicle network such as vehicle network 23. Where the command data is not a complete message, vehicle parameter control module 7 is configured to generate a command message from the command data retrieved from vehicle network database 8 and send the command message to network connector 12. Network connector 12 is configured to send the command message out to an automotive machine over a vehicle network such as vehicle network 23.

[0038] In an example operation, electronic control device 2 receives over communication interfaces 14, a predefined signal containing a request to turn on a vehicle's lights. Vehicle parameter control module 7 receives the predefined signal and identifies the lights on request.

Vehicle parameter control module 7 then retrieves from database 8 the command data used to turn on the lights for the communication protocol that is associated with concurrently parsed incoming network traffic or a stored identification. For example, the retrieved command data can be to insert a 1 into a specific byte (e.g. 4th, 5th, or 8th byte) of a transmission sent to the vehicle network attached to vehicle network connector 12, and also to send the transmission with a particular identifier across the network. Vehicle parameter control module 7 would generate a command message having the particular identifier and inserting a 1 into the specific bit indicated in the command data. The module or electronic control unit responsible for turning on the lights is configured to recognize a transmission having that specific identifier, and apply the command data written into the identified bit of the command message to the connected vehicle system, which in this case would turn on the vehicle's lights.

[0039] Where communication interfaces 14 includes a first and second communication interface coupled to web server 10 and configured to receive the webpage data output form the web server 10. The second communication interface can be configured to use a communication medium different than the first communication interface. For example, the second

communication interface can be configured to use the Bluetooth communication medium and the first communication interface can be configured to use the WI-FI communication medium.

Various other combinations of wired and wireless communication mediums are contemplated.

Vehicle parameter control application 7 is configured to maintain a list of parameters to transmit automatically for each active communication interface in use. Thus allowing display of different content simultaneously on multiple user devices, such as user device 4.

[0040] Communication logic module 24 is coupled to communication interfaces 14, and vehicle network connector 12. Communication logic module 24 is configured to receive the coded data from network connector 12 and parse the coded data to determine an operating state

(environment, configuration, etc.) for the vehicle attached to electronic control device 2.

Communication logic module 24 is configured to selectively broadcast the webpage data from at least the first and second communication interfaces based on the operating state of the vehicle.

Alternatively, communication logic module is configured to selectively broadcast the webpage data from at least the first and second communication interfaces based on scheduled and/or discrete command actions. Communication logic module 24 may selectively output the webpage data by starting and stopping at least the first and second communication interfaces. The functions of communication logic module 24 can alternatively be performed by vehicle parameter control module 7, which would be coupled to communication interfaces 14.

[0041] Data upload logic module 15 is coupled to first communication interface 14 and vehicle parameter control module 7. Data upload logic module 15 is configured to receive the decoded data from vehicle parameter control module 7 and send out the decoded data from electronic control device 2 to a remote server, such as remote server 3. Data upload logic module 15 uses communication interfaces 14 to send out the decoded data. Data upload logic module 15 is also configured to encrypt the decoded data, prior to sending it out. Data upload logic module 15 may also be configured to verify the transfer was successful, and perform corrective action if the transfer was not successful. The functions of data upload logic module 15 can alternatively be performed by vehicle parameter control module 7. Where data upload logic module 15 is coupled to memory module 6, data upload logic module 15 is configured to retrieve the decoded data stored in memory module 6 and send out the retrieved data to a remote server.

[0042] Non-volatile data storage module 9 is coupled to vehicle parameter control module 7 and data upload logic module 15. Non-volatile storage module 9 is a semi -permanent memory (e.g. FLASH, SD card, Hard drive, etc.), which is configured to be erased, read from, written to, and maintain data on power loss. Non-volatile storage module 9 is configured to store a history of decoded data processed by vehicle parameter control module 7. Data upload logic module 15 is configured to retrieve the decoded data from non-volatile data storage module 9 and send out the retrieved data to a remote server. Non-volatile data storage module 9 may be configured to preserve the history of decoded data until it is retrieved by data upload logic module 15, or purposefully deleted.

[0043] Vehicle parameter control module 7 is configured with a plurality of preconfigured behaviors to store or record decoded data in non-volatile data storage module 9. The predefined behaviors include don't record, record every message, record a message when the data changes, record the value at on a time interval, and send the decision to record to a custom on-equipment- manufacturer ("OEM") provided system. It should be understood that various combinations of the listed behaviors are contemplated.

[0044] The specific behavior of vehicle parameter control module 7 can be selected by configuration settings stored in vehicle network database 8. Database 8 is configured such that the settings for each parameter are set individually. Example formats for storing the decoded data in non-volatile storage module 9 include structured query language ("SQL"), and comma separated variables ("CSV"). The format of the records can be modified to improve support for various operational needs. For example, if the end application wants to search through the records for a specific event, a database would provide an optimized structure for complex search operations. However, if the data is going to be reviewed via a simple spreadsheet, then CSV would provide a robust solution, as it can be opened by all major spreadsheet software.

The format of the file stored in non-volatile storage module 9, can be controlled through a set of application programming interfaces (APIs). Use of the APIs allows a developer to modify the file format to suit individual needs. The APIs can also be used to vary the decoding operation from the standard procedures to customized operation for specialized use cases.

[0045] Physical device interface or connector 11 is electrically coupled to vehicle parameter control module 7. Physical device connector 11 is configured to accept inputs from physical devices attached externally to electronic control device 2. Physical device connector 11 may be a signal conditioning unit configured to drive and/or read various analog signals (e.g. voltage levels), digital signals, and/or external devices (e.g. relays, lights, etc.). Physical device connector 11 is also configured to inform various subsystems of electronic control device 2 of changes in value and/or the level of one of the inputs received. For example, where physical device interface 11 is configured to report a switched battery signal (which changes state upon ignition or shutdown of the vehicle) to vehicle parameter control module 7, vehicle parameter control module 7 is configured to suspend recording of data to non-volatile storage module 9, and prepare electronic control device 2 for system power off or shutdown when it receives the signal.

[0046] Physical device connector 11 is also coupled to communication logic module 24.

Physical device connector 11 is configured to pass the accepted inputs to communication logic module 24, and communication logic module 24 is configured to parse the accepted input along with the coded data to determine the operating state of the vehicle attached to electronic control device 2. Physical device connector 11 may also be omitted from electronic control device 2.

[0047] In one embodiment, the various components of electronic control device 2 described above are separate software modules operating on a single computing device (e.g.

microcontroller, field programmable gate array, microprocessor, personal computing device, etc.). The software modules are virtually coupled together in that they communicate using software defined interfaces. The software interfaces contain the parameters necessary to effect the communication of the data between the various modules as described above. In an alternative embodiment, the components of electronic control device 2 are separate hardware units electrically coupled together (e.g. fiber optics, coper wiring, etc.). The hardware units can be combined on a single substrate or multiple substrates electrically bridged together. In another embodiment, some components of electronic control device 2 are different hardware units and some components are combined together as different software modules. The software components are virtually coupled together and the entire unit containing the software is electrically coupled to the other hardware modules according to the schematic in FIG. 1. For example, database 8 and vehicle parameter control module 7 can be a single software unit and the rest of the components can be distinct hardware units electrically coupled to the computing device running the software modules. Each component can be configured as a separate hardware unit of software module, and all such potential combinations and connections are contemplated.

[0048] Referring now to FIG. 2, a structural diagram of an embodiment of vehicle network database 8 contained within electronic control device 2 of vehicle information processing system 1 is shown. Database 8 contains a custom set of parameter groups, which are defined according to the vehicle's purpose and the needs of a user. The parameter groups provide a convenient mechanism to read the current value of a set of parameters without needing to hard-code them individually into website data. The number of members to a group, and which parameters are subscribed to, is dependent on how the data is laid out on the web page rendered from the webpage data, and is flexible so as to cover a wide range of designs. Each parameter may have a set of Parameter Values and corresponding Text Strings assigned to it. These values can add further definition to the parameter's value, by attaching words to a specific value of a parameter (e.g. value 0 = "Off and value 1 ="On"). Each piece of vehicle information has a Parameter Label for identification. The Parameter Label can be a member of one parameter group or multiple parameter groups.

[0049] Each parameter has a Receive CAN Message field, which is represented by a condensed label in Fig 2. The Receive CAN Message field has attributes to identify the specific communication protocol used by a parameter value contained in a payload or message received at electronic control device 2 from vehicle network 23. The Receive CAN Message field includes values for CAN ID, CAN ID Mask, CAN Bus number, Length, Payload Mask, the start bit, and length to extract the parameter value out of the payload or message received from vehicle network 23. The pieces of information, amounts, and values contained in the Receive CAN Message field are different for different parameters and are dependent on the specific communication protocol corresponding to each parameter.

[0050] Database 8 includes a Write Value CAN Message field which contains information to change the value of a data point or control the operation of a system of the vehicle connected to electronic control device 2 based on a predefined signal sent from user device 4. This field contains multiple pieces of information (e.g. CAN ID, CAN Length, CAN Bus Number, Start Bit, and Length to define where to insert new values in an outgoing CAN message) so that electronic control units 22 will properly receive and decode the data. Predefining the outgoing message improves security and reliability, because it strictly limits the control available to the user.

[0051] Database 8 also includes a Retrieve Value CAN Message field, which contains information for user device 4 to request data from the vehicle connected to electronic control device 2. A message with a fixed identifier and payload is sent to a specific ECU of electronic control units 22, and then the specific ECU of electronic control units 22 sends a response containing the desired information. This field contains multiple pieces of information (e.g. CAN

ID, CAN Length, Payload and CAN Bus Number) so that the specific ECU of electronic control units 22 can properly send the desired data to electronic control device 2.

[0052] A Log Control field is used to define how electronic control device 2 treats new values for each parameter when the Receive CAN message is detected. Examples of behaviors include ignore, log all messages, log when the value changes, or log once per second. Gain and

Offset fields are used together to mathematically modify the raw data in the CAN payload, and convert it into electronic data representing its actual units. A Unit Name field is used to associate a string with the units that the data has been converted to. The associated string is an example of meta-data. The meta-data is provided to user device 4 to generate a dynamic user interface.

[0053] Database 8 supports a structure which stores several alternatives for every string contained within it. This feature allows support for several different languages and locales for global distribution of the system. A command from user device 4 can be used to switch database 8 to an alternative list of strings during normal operation without modifying the permanent configuration or computer code.

[0054] Vehicle information processing system 1 has two operating modes, a client mode and access point mode. Electronic control device 2 has communication interfaces 14 (e.g.

communication interface 1, 2, 3, ... (n), etc.) that output the decoded data to either user device 4 or remote server 3 depending on the operating mode. Communication interfaces 14 can be a variety of interface types including Wi-Fi, Ethernet, satellite, cellular, fiber optic, etc. The operating mode of the vehicle information processing system 1 is selected by parsing the coded data received from vehicle network 23 to determine an operating state for the vehicle. Switching between modes allows a single communication interface to provide a variety of functions.

Switching also reduces the cost of the electronic control device by limiting the amount of communication interfaces needed to connect to both local devices and remote servers.

Additionally by controlling the mode automatically the work load on the user is reduced.

Electronic control device 2 may include a switch for selecting between client and access point modes, which allows for greater flexibility in operation.

[0055] Referring to FIG. 3 a depiction of vehicle information processing system 1 in client mode is shown. In client mode, communication interfaces 14 output the decoded data to remote server 3. Communication interfaces 14 send the decoded data over a fixed network to server interface 19. Where the fixed network is a wireless network, communication interfaces 14 are pre-configured with the access credentials to connect to the network.

[0056] Client mode is activated when parsing the coded data corresponds to a condition that the vehicle manufacturer has specified correlates with the vehicle being parked or in a non- operational state. Various conditions are contemplated including ignition off, shore-power attached, maintenance mode active, parking brake engaged, etc. Client mode is used for archiving vehicle electronic data to a remote server, remote troubleshooting of the vehicle by an off-site technician, retrieving updates for a vehicle's electronic systems from a factory server, sending electronic messages about the state of the vehicle, or maintenance requirements of the vehicle to an interested party. While in client mode, electronic control device 2 interacts with remote server 3 through the fixed network. The connection to the fixed network can be automated except for local user interaction placing electronic control device 2 into client mode.

[0057] Referring now to FIG. 4, a depiction of vehicle information processing system 1 in access point mode is shown. In access point mode the communication interfaces 14 output the decoded data to user device 4. Access point mode is activated when parsing the coded data corresponds to a condition that the vehicle manufacturer has specified correlates with the vehicle being moving or in an operational state. Various conditions are contemplated including the engine running, the parking break off, the vehicle shifted into drive, etc. When in access point mode, electronic control device 2 creates a fully mobile local network that travels with the vehicle.

[0058] It should be understood that the various embodiments of the vehicle information processing system 1 and electronic control device 2 as described above can be directed to a method of processing information relating to a vehicle.

[0059] It should be understood that the figures illustrate the exemplary embodiments in detail, and it should be understood that the present application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.

[0060] Further modifications and alternative embodiments of various aspects of the invention will be apparent to those skilled in the art in view of this description. Accordingly, this description is to be construed as illustrative only. The construction and arrangements, shown in the various exemplary embodiments, are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.) without materially departing from the novel teachings and advantages of the subject matter described herein. Some elements shown as integrally formed may be constructed of multiple parts or elements, the position of elements may be reversed or otherwise varied, and the nature or number of discrete elements or positions may be altered or varied. The order or sequence of any process, logical algorithm, or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes and omissions may also be made in the design, operating conditions and arrangement of the various exemplary embodiments without departing from the scope of the present invention.

Claims

WHAT IS CLAIMED IS:

1. A vehicle which generates webpage data which represents information relating to the vehicle, the vehicle comprising:

a vehicle data bus which communicates vehicle data in accordance with a vehicle network communication protocol;

at least one control unit coupled to the vehicle data bus and a vehicle system; and a vehicle computer coupled to the data bus to receive encoded data representative of operational parameters of the vehicle system, the encoded data being encoded for use with the vehicle network communication protocol, the vehicle computer storing decoding data corresponding to the vehicle network communication protocol associated with the encoded data, and the vehicle computer storing programming which generates webpage data from the encoded data and the decoding data, the webpage data being useable by a user device external to the vehicle to generate a human-readable representative of the encoded data referenced to the operational parameters of the vehicle system.

2. The vehicle according to claim 1, wherein the vehicle computer includes an analog input, and the webpage data includes data representative of a signal applied to the analog input.

3. The vehicle according to claim 1 further comprising a communication interface compatible with a remote server and a user device to transmit decoded data to the remote server and user device.

4. The vehicle according to claim 3, wherein the vehicle computer is programmed to parse the encoded data to determine an operating state of the vehicle system and to selectively output the decoded data between the remote server and the user device in the form of the webpage data representative of the operating state.

5. The vehicle according to claim 4, wherein the vehicle computer outputs decoded data to the remote server in response to encoded data being representative of the operating state representing that a parking brake is set to on.

6. The vehicle according to claim 4, wherein the vehicle computer outputs the decoded data to the user device in the form of the broadcasted webpage data in response to the encoded data being representative of the operating state representing that a parking brake is set to off.

7. An electronic control device for processing information relating to a vehicle comprising:

a database containing a plurality of vehicle network decoding information corresponding to a plurality of vehicle network communication protocols;

a vehicle network connector configured to pass-through coded data representative of the operation of an automotive machine received from a vehicle network, wherein the coded data is encoded for use with one of the plurality of vehicle network communication protocols;

a vehicle parameter control module coupled to the database and the vehicle network connector configured to receive the coded data from the vehicle network connector, retrieve the vehicle network decoding information from the database corresponding to the specific vehicle network communication protocol associated with the coded data, decode the coded data using the vehicle network decoding information, and output the decoded data;

a web server coupled to the vehicle parameter control module and configured to receive the decoded data output from the vehicle parameter control module, generate webpage data containing the decoded data, and output the webpage data; and

a first communication interface coupled to the web server and configured to receive the webpage data output from the web server and broadcast the webpage data out from the electronic control device.

8. The electronic control device for processing information relating to a vehicle according to claim 7 further comprising a memory module coupled to the vehicle parameter control module, and wherein the vehicle parameter control module is further configured to store the decoded data in the memory module.

9. The electronic control device for processing information relating to a vehicle according to claim 8:

wherein the coded data received from the vehicle network has multiple parameters and the decoded data stored in the memory module has corresponding parameters;

wherein the first communication interface is further configured to receive a predefined signal from a user device requesting a specific parameter, and pass the predefined signal to the vehicle parameter control module; and

wherein the vehicle parameter control module is further configured to receive the predefined signal from the first communication interface, analyze the predefined signal, retrieve the decoded data from the memory module where the corresponding parameter matches the specific parameter contained in the predefined signal, and send that data to the web server to be broadcast out over the first communication device.

10. The electronic control device for processing information relating to a vehicle according to claim 8:

wherein the database contains a plurality of automotive machine operation command data corresponding to a plurality of vehicle network communication protocols;

wherein the first communication interface is further configured to receive a predefined signal from a user device requesting a specific automotive machine operation , and pass the predefined signal to the vehicle parameter control module; and

wherein the vehicle parameter control module is further configured to receive the predefined signal from the first communication interface, analyze the predefined signal to determine the specific automotive machine operation requested, retrieve from the database the automotive machine operation command data that corresponds to the specific automotive machine operation determined by analyzing the predefined signal, generate a command message based on the retrieved automotive machine operation command data, and send the command message to the vehicle network connector; and

wherein the vehicle network connector is further configured to receive the command message from the vehicle parameter control module, and send the command message out to an automotive machine over the vehicle network.

11. The electronic control device for processing information relating to a vehicle according to claim 7 further comprising a second communication interface coupled to the web server configured to receive the webpage data output from the web server and broadcast the webpage data out from the electronic control device using a communication medium different from the first communication interface.

12. The electronic control device for processing information relating to a vehicle according to claim 11 further comprising a communication logic module coupled to the first communication interface, second communication interface, and the vehicle network connector, the

communication logic module configured to selectively broadcast the webpage data from the first and second communication interfaces based on an operating state of the automotive machine as determined by parsing the coded data in the communication logic module.

13. The electronic control device for processing information relating to a vehicle according to claim 7 further comprising a data upload logic module coupled to the first communication interface and the vehicle parameter control module and configured to receive the decoded data from the vehicle parameter control module, and send the decoded data out to a remote server from the electronic control device using the first communication interface.

14. The electronic control device for processing information relating to a vehicle according to claim 13 further comprising a communication logic module coupled to the first communication interface, the vehicle network connector, and the data upload logic module, the communication logic module configured to output the decoded data selectively between the remote server in the form of the decoded data and the user device in the form of the broadcasted webpage data based on an operating state of the automotive machine as determined by parsing the coded data in the vehicle parameter control unit.

15. A method of processing information relating to a vehicle comprising the steps of:

receiving at an electronic control device coded data from a vehicle network encoded for use with a specific vehicle network communications protocol, the coded data representative of the operation of an automotive machine;

comparing the coded data to decoding information stored in a database of the electronic control device, the decoding information corresponding to a plurality of vehicle network communication protocols;

identifying the specific vehicle communication protocol used to encode the data based on the comparison;

retrieving the decoding information corresponding to the specific communications protocol used to encode the coded data from the database;

decoding the coded data, using the retrieved decoding information; and broadcasting the decoded data out from the electronic control device as webpage data, such that when rendered the webpage data displays a human-readable version of the data representative of the operation of an automotive machine.

16. The method of processing information relating to a vehicle according to claim 15 further comprising the step of rendering the webpage data on a user device.

17. The method of processing information relating to a vehicle according to claim 16 wherein the webpage data is rendered in a native application on the user device.

18. The method of processing information relating to a vehicle according to claim 16 wherein the webpage data is rendered in a web browser on the user device.

19. The method of processing information relating to a vehicle according to claim 15 further comprising the steps of:

determining an operational state of the automotive machine by parsing the coded data in the electronic control device; and

determining a specific communication medium to use for broadcasting the webpage data based on the operational state.

20. The method of processing information relating to a vehicle according to claim 15 further comprising the steps of:

selectively outputting the decoded data to a remote server or broadcasting the decoded data as the webpage data based on the operational state of the automotive machine.