Internet-based system for monitoring vehicles

The invention provides a method for monitoring a vehicle that features the steps of: 1) generating a data packet including vehicle data retrieved from the vehicle using a wireless appliance; 2) transmitting the data packet over an airlink with the wireless appliance so that the data packet passes through a network and to a host computer system; 3) processing the data packet with the host computer system to generate a set of data; and 4) displaying the set of data on a web page hosted on the internet.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS REFERENCE TO RELATED APPLICATION

This application 1) is a continuation of, and claims priority under 35 U.S.C. §120 to, U.S. patent application Ser. No. 10/614,665, now U.S. Pat. No. 7,747,365, entitled ‘Internet-based system for monitoring vehicles’, which has a filing date of Jul. 7, 2003, and which is a continuation of U.S. patent application Ser. No. 09/804,888, which was filed on Mar. 13, 2001, now abandoned, both of which are incorporated by reference in its entirety their entireties herein. This application also and; 2) is a continuation-in-part of, and claims priority under 35 U.S.C. §120 to U.S. patent application Ser. No. 11/796,372, now U.S. Pat. No. 7,904,219, entitled ‘Peripheral Access Devices and Sensors for Use with Vehicle Telematics Devices and Systems’, which has a filing date of Apr. 27, 2007., which is a continuation-in-part of prior U.S. patent application Ser. No. 10/810,373, filed Mar. 26, 2004, now U.S. Pat. No. 7,228,211, which is (1) a continuation-in-part of prior U.S. patent application Ser. No. 10/431,947, filed May 8, 2003, now issued as U.S. Pat. No. 6,957,133; and (2) a continuation-in-part of prior U.S. patent application Ser. No. 10/447,713, filed May 29, 2003, now issued as U.S. Pat. No. 6,732,031, which is a continuation of prior U.S. patent application Ser. No. 09/776,106, filed Feb. 1, 2001, now issued as U.S. Pat. No. 6,636,790, which claims the benefit of U.S. Provisional Application No. 60/220,986, filed Jul. 25, 2000, U.S. Provisional Application No. 60/222,213, filed Aug. 1, 2000 and U.S. Provisional Application No. 60/222,152, filed Aug. 1, 2000. The contents of all of the above-listed applications are incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates to use of an Internet-based system for monitoring a vehicle's performance.

BACKGROUND OF THE INVENTION

The Environmental Protection Agency (EPA) requires vehicle manufacturers to install on-board diagnostics (OBD-II) for monitoring light-duty automobiles and trucks beginning with model year 1996. OBD-II systems (e.g., microcontrollers and sensors) monitor the vehicle's electrical and mechanical systems and generate data that are processed by a vehicle's engine control unit (ECU) to detect any malfunction or deterioration in the vehicle's performance. Most ECUs transmit status and diagnostic information over a shared, standardized electronic buss in the vehicle. The buss effectively functions as an on-board computer network with many processors, each of which transmits and receives data. The primary computers in this network are the vehicle's electronic-control module (ECM) and power-control module (PCM). The ECM typically monitors engine functions (e.g., the cruise-control module, spark controller, exhaust/gas recirculator), while the PCM monitors the vehicle's power train (e.g., its engine, transmission, and braking systems). Data available from the ECM and PCM include vehicle speed, fuel level, engine temperature, and intake manifold pressure. In addition, in response to input data, the ECU also generates 5-digit ‘diagnostic trouble codes’ (DTCs) that indicate a specific problem with the vehicle. The presence of a DTC in the memory of a vehicle's ECU typically results in illumination of the ‘Service Engine Soon’ light present the dashboard of most vehicles.

Data from the above-mentioned systems are made available through a standardized, serial 16-cavity connector referred to herein as an ‘OBD-II connector’. The OBD-II connector typically lies underneath the vehicle's dashboard. When a vehicle is serviced, data from the standardized buss is typically queried using an external engine-diagnostic tool (commonly called a ‘scan tool’) that connects to the OBD-II connector. The data are then displayed an analyzed with the scan tool, and can then be used to service the vehicle.

Some vehicle manufacturers also include complex electronic systems in their vehicles to access and analyze some of the above-described data. For example, General Motors includes a system called ‘On-Star’ in some of their high-end vehicles. On-Star collects and transmits data relating to these DTCs through a wireless network. On-Star systems are not connected through the OBD-II connector, but instead are wired directly to the vehicle's electronic system. This wiring process typically takes place when the vehicle is manufactured.

BRIEF SUMMARY OF THE INVENTION

It is an object of the present invention to provide a wireless, internet-based system for monitoring a vehicle. Specifically, it is an object of the invention to access data from a vehicle, analyze it, and make it available to organizations (e.g. an automotive dealership or service center) over the internet so that the vehicle's performance can be analyzed accurately and in real-time. The data include, for example, DTCs that trigger ‘alert messages’ that are emailed to a vehicle owner or displayed on a web page on the internet.

In one aspect, the invention provides a method for monitoring a vehicle that features the steps of: 1) generating a data packet that includes data retrieved from the vehicle using a wireless appliance; 2) transmitting the data packet over an airlink with the wireless appliance so that it passes through a network and to a host computer system; 3) processing the data packet with the host computer system to generate a set of data; and 4) displaying the set of data on a web page hosted on the internet.

The ‘wireless appliance’ used in the above-described method includes electronics that extract data from the vehicle's ECU, and a transmitting component (e.g. a radio or cellular modem) that sends out the data packet over an existing network (e.g., Cingular's Mobitex network). Such a wireless appliance is described in the U.S. patent application Ser. No. 09/776,106, now U.S. Pat. No. 6,636,790, entitled WIRELESS DIAGNOSTIC SYSTEM FOR VEHICLES, and filed Feb. 1, 2001, the contents of which are incorporated herein by reference.

In embodiments, the processing step includes extracting at least one of the following vehicle parameters from the data packet: numerical data, an alphanumeric text message, an active or pending diagnostic trouble code (e.g., a 5-digit code), or a vehicle identification number. These parameters are then processed with database software (e.g., an Oracle database) to generate a set of data that comprises an alphanumeric text message. The text message, e.g. an alert message, can be displayed on the web page or emailed to a user. The text message can also include a description of the data parameter, such as a written description of the DTC.

In related embodiments, the method includes the step of processing at least one numerical parameter from the numerical data with a mathematical algorithm. This generates an alert message from data other than DTCs. For example, the numerical parameter can be compared or displayed with at least one numerical parameter generated at an earlier point in time (e.g., a previously determined fuel level), or with a predetermined numerical value (e.g., a mileage level corresponding to a recommended service appointment). These values, or a simple analysis of the data, can be included in the alphanumeric text message displayed on the web page or sent out in an email.

In another aspect, the invention features a similar set of steps for processing data from multiple vehicles (e.g., a group of customers) associated with a corporate organization (e.g., a vehicle dealership). Specifically, the invention features the steps of 1) generating a first data packet comprising vehicle data retrieved from a first vehicle in a set of vehicles using a first wireless appliance disposed in the first vehicle; 2) transmitting the first data packet over an airlink with the first wireless appliance so that it passes through a network and to a host computer system; 3) repeating steps 1 and 2 for a second vehicle; 4) processing the first and second data packets with the host computer system to generate first and second sets of data; 5) displaying the first set of data on a first web page hosted on the internet; and 6) displaying the first and second sets of data on a second web page hosted on the internet.

In this embodiment, a single web site includes the first and second web pages. The web site also includes a ‘login’ web page for entering a user name and a password so that one group of users (e.g. vehicle owners) can log in with and view data from a single vehicle, while another group (e.g. corporate organizations such as vehicle dealerships, vehicle-rental organizations, insurance organizations, or fleet organizations) can log in and view data of all the users associated with the group.

In the above-described method, the term “airlink” refers to a standard wireless connection (e.g., a connection used for wireless telephones or pagers) between a transmitter and a receiver. Also in the above-described method, the ‘generating’ and ‘transmitting’ steps can be performed at any time and with any frequency, depending on the diagnoses being performed. For a ‘real-time’ diagnoses of a vehicle's engine performance, for example, the steps may be performed at rapid time or mileage intervals (e.g., several times each minute, or every few miles). Alternatively, other diagnoses (e.g. an emissions or ‘smog’ check) may require the steps to be performed only once each year or after a large number of miles are driven. Alternatively, the vehicle may be configured to automatically perform these steps at predetermined or random time intervals.

The term ‘web page’ refers to a single page that is hosted on the internet or world-wide web. A ‘web site’ typically includes multiple web pages.

The invention has many advantages. In particular, wireless transmission of data from a vehicle, followed by analysis and display of these data using a web site hosted on the internet, makes it possible to diagnose the performance of a vehicle in real-time from virtually any location that has internet access. This ultimately means the problems with the vehicle can be efficiently diagnosed, and in some cases predicted before they actually occur. Moreover, data from the vehicle can be queried and analyzed while the vehicle is actually in use to provide a relatively comprehensive diagnosis that is not possible using a conventional scan tool. An internet-based system for vehicle diagnoses can also be easily updated and made available to a large group of users simply by updating software on the web site. In contrast, a comparable updating process for a series of scan tools can only be accomplished by updating the software on each individual scan tool.

The wireless appliance used to access and transmit the vehicle's data is small, low-cost, and can be easily installed in nearly every vehicle with an OBD-II connector in a matter of minutes. It can also be easily transferred from one vehicle to another, or easily replaced if it malfunctions.

An in-vehicle wireless appliance can also collect data that is not accessible using a scan tool. For example, data that indicates a vehicles performance can be collected while the vehicle is actually driven. Scan tools, in contrast, can only collect data in a vehicle service bay. Service technicians, for example, can analyze DTCs during repair of the vehicle. The system described herein makes also makes data available in real-time, thereby allowing the technicians to order parts and schedule resources for service appointments before the vehicle is actually brought into the dealership.

The resulting data, of course, have many uses for automotive dealerships, vehicle-service organizations, vehicle-renting firms, insurance companies, vehicle owners, organizations that monitor emission performance (e.g., the EPA), manufacturers of vehicles and related parts, survey organizations (e.g., J.D. Power) and vehicle service centers. In general, these data yield information that benefits the consumer, vehicle and parts manufacturers, vehicle service centers, and the environment.

These and other advantages of the invention are described in the following detailed disclosure and in the claims.

BRIEF DESCRIPTION OF DRAWINGS

The features and advantages of the present invention can be understood by reference to the following detailed description taken with the drawings, in which:

FIG. 1 is a schematic drawing of a website with a login process that renders a series of web pages associated with either a dealer interface or a customer interface;

FIG. 2 is a screen capture of a web page from the web site of FIG. 1 wherein a user enters a login and password;

FIG. 3 is a screen capture of a web page from the web site of FIG. 1 that shows a list of customers corresponding to a single dealership;

FIG. 4 is a screen capture of a web page from the web site of FIG. 1 that shows an alert message, generated by an odometer reading, for a customer's vehicle;

FIG. 5A is a screen capture of a web page from the web site of FIG. 1 that shows two alerts, each generated by a separate DTC, for a customer's vehicle;

FIG. 5B is a screen capture of a web page associated with the web page of FIG. 5A that shows two 5-digit DTCs corresponding to the two alert messages shown in FIG. 5A;

FIG. 6 is a screen capture of a web page from the web site of FIG. 1 that shows recent diagnostic data for a customer's vehicle; and

FIG. 7 is a screen capture of a web page from the website of FIG. 1 that shows several time-dependent sets of diagnostic data for a customer's vehicle.

 DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 shows a schematic drawing of a login process 10 for a website 20 that displays diagnostic data for a series of ‘customer’ vehicles associated with a vehicle ‘dealership’. Within each vehicle is a wireless appliance that retrieves data from the vehicle's engine computer, and then sends these data, formatted in a data packet, wirelessly through a network. The data eventually are transferred from the network to the website 20 where they are formatted and displayed and processed as described below.

A user ‘logs’ into the website 20 by entering a username and password that, once entered, are compared to a database associated with the website. The comparison determines if the user is a dealer or a customer. If the user is determined to be a dealer, the website renders a dealer interface 27 that contains, e.g., diagnostic information for each vehicle purchased from the particular dealership. Users viewing the dealer interface 27 do not have access to data corresponding to vehicles sold by other dealerships. If the user is determined to be a customer, the website 20 renders a customer interface 29 that contains diagnostic information for one or more vehicles corresponding to the customer. The customer interface contains diagnostic information for each vehicle corresponding to the customer.

FIG. 2 shows a screen capture from a ‘home’ web page 40 of an actual website. The web page 40, corresponding to the web page 20 shown in FIG. 1 as www.networkcar.com, is accessed from a conventional web browser (e.g., Netscape Navigator). It renders a dealer/customer login portion 43 that prompts a user for a login and a password. The web page 40 includes a login region 42 where the user enters a login (in this case the user's email address), and a password region 44 where the user enters a corresponding password. The user then clicks the login button 46 to authenticate the login and log the user into the website as either a ‘customer’, ‘dealer’, or an invalid user. The authentication process is performed with conventional database software. Here and throughout the application, the term ‘clicks’ means a computer mouse is used to select or initiate a software-based feature on the web page.

The wireless appliance that provides a diagnostic data to the website is described in more detail in WIRELESS DIAGNOSTIC SYSTEM FOR VEHICLES, filed Feb. 1, 2001, the contents of which have been previously incorporated by reference. Each wireless appliance contains logic for retrieving data from the host vehicle and formatting the data in a data packet, and a wireless transmitter that transmits the data packet over an airlink to a wireless network (e.g., Cingular's ‘Mobitex’ network). Each appliance typically transmits a data packet at either a predetermined time interval (e.g., once each day), or shortly (e.g., within a few seconds) after a DTC is generated. The format of each data packet, along with the data contained therein, is described in the above-mentioned patent application. In general, each data packet contains information of its status, an address describing its destination, an address describing its origin, and a ‘payload’ that contains diagnostic data from the vehicle. The process for transmitting diagnostic data from a vehicle to a website is described in more detail in the above-referenced patent application.

FIG. 3 is a screen capture of a web page 50 included in the dealer interface indicated in FIG. 1. The host computer system renders this page once the user is determined to be a dealer following the login process. The screen capture features a customer list 52 corresponding to a single dealership that includes: customer names 56 for each customer; a vehicle description 58 that includes the vehicle's year, make and model; a unique 17-digit vehicle identification number (‘VIN’) 60 that functions as the vehicle's serial number; and an ‘alert’ listing 62 that provides a number of alerts, described in more detail below, for each vehicle.

An alert is generated when data, sent from the vehicle's wireless appliance to the host computer system, indicates either 1) a mechanical/electrical problem with the vehicle; or 2) that a scheduled maintenance is recommended for the vehicle. For example, the customer list 52 includes a data field 54 that lists the user ‘Five, Loaner’ with an associated 2001 Toyota Corolla. The data field 54 also includes the number ‘1 ’ in the alert listing 62, indicating the presence of one of a single alert.

FIG. 4 is a screen capture of a web page 60 entitled a ‘Vehicle Check Page’ that describes in more detail the alert and other data for ‘Five, Loaner’. The web page 60 for this user, or any other user in the customer list 52, is accessed by clicking on the highlighted name in the data field 54 shown in the web page 50 of FIG. 3. The web page 60 features a header 61 that lists general information corresponding to this particular user, e.g. name, vehicle description, and VIN. The header 61 also include diagnostic data such as a field 70 showing the vehicle's odometer reading (5229 miles), a time/date stamp 72 indicating the last time the host computer system received data from the vehicle, and an icon and data field 71 indicating the vehicle's emissions performance. In this last case, the green box with a ‘checkmark’ indicates that the vehicle's emissions are within the levels mandated by the EPA. It is present when the vehicle has no DTCs that are associated with its emissions system.

The web page 60 is separated into four categories describing, respectively, a status of the vehicle's ‘emission’ system 62, ‘transmission/brakes’ system 64, ‘engine/fuel’ system 66, and ‘other’ systems 68. For this vehicle, the emission 62, transmission/brakes 64, and engine/fuel 66 system categories have no associated alerts. This is indicated by, respectively, messages 62′, 64′, 66′ preceded an icon that features a green box with a checkmark similar to that shown in the data field 71 describing the overview vehicle's emissions status. These icons indicate that no DTCs corresponding to the respective categories were detected. Conversely the ‘other’ system category 68 includes an alert message 68′ that includes a text message field preceded by an icon that features a yellow box with a ‘question mark’. The presence of this single alert message 68′ is what generates the ‘1 ’ listed in the data field 54 in FIG. 3. The alert message 68′ is generated in response to an odometer reading (i.e., 5229 miles) transmitted in the most recent data packet sent by the vehicle.

The alert message 68′ is first generated when the vehicle's mileage is within 1000 miles of the mileage corresponding to a recommended scheduled maintenance, which in this case is 5000 miles. Thus, an alert in generated and first appears on the web page 60 when the vehicle's odometer reading is 4000 miles or greater. Mileage values corresponding to this and other recommended schedule maintenances are entered into the system in a ‘Scheduled Maintenance’ section 75 on the same page. The alert message 68′ appears on the web page 60 until: 1) the recommended service is performed on the vehicle; or 2) the vehicle's mileage is greater than 1000 miles from the mileage corresponding to a recommended scheduled maintenance (i.e., 6000 miles). In either case, the alert is ‘cleared’ from the web page 60 and is stored in a ‘History of Alert’ section 75 that, when clicked, historically lists all the cleared alerts corresponding to this particular vehicle.

FIGS. 5A and 5B show, respectively, screen captures of web pages 80 and 100 that indicate alert messages 62a′, 62b′ triggered by the presence of separate emissions-related DTCs within the vehicle. The DTC is sent from the vehicle in the data packet described above. The web pages 80, 100 feature the same general format as shown for FIG. 4, i.e. four categories describing the vehicle's ‘emission’ system 62, ‘transmission/brakes’ system 64, ‘engine/fuel’ system 66, and ‘other’ systems 68. In this case, the transmission/brakes 64, engine/fuel 66 and other 68 systems have no associated alerts, and thus include messages 64′, 66′, and 68′ preceded an icon that features a green box with a ‘checkmark’ as before. In contrast, the emissions system 62 includes two alert messages 62a′, 62b′. Each message includes a brief text message: ‘engine may not be processing exhaust gasses efficiently’. The text message is included in a database and associated with each of the 5-digit DTCs. Note that the presence of the alert messages 62a′, 62b′ means that there is a problem with this vehicle's emission system, and thus the icon in the data field 71 in the page's header 61 is red with an exclamation point.

FIG. 5B shows a screen capture of a web page 100 that includes more details for the alert messages 62a′, 62b′ from FIG. 5A. The web page 100 renders when a user clicks on the ‘View Emissions System Details’ link 85 in the emissions category 62 and includes alert messages 62a″, 62b″. These messages are essentially more detailed versions of the alert messages 62a′, 62b′ shown in FIG. 5A. They include the same text description as alert messages 62a′, 62b′ in addition to a more detailed text description (“Exhaust Gas Recirculation Flow Insufficient Detected” for alert message 62a″″; “Exhaust Gas Recirculation Flow Excessive Detected” for alert message 62b″″) and the 5-digit DTC (P0401 for alert message 62a″; P0402 for alert message 62b″). Detailed diagnostic data corresponding to the DTCs is accessed by clicking on the ‘To System Diagnostic Measurements’ field 90 in FIG. 5B. As shown in FIG. 6, this field 90 renders a web page 120 that lists a detailed data set 122 transmitted from the vehicle-based wireless appliance to the host computer system. The host computer system receives the data set 122 at a time described by a time/date stamp 72 listed in the header 61. The data set 122 includes a data parameter name 125, a corresponding numerical value 127, and a description of the units 129 of the numerical value 127. Some of the numerical values (e.g., the status of the ‘MIL light’ 131) are dimensionless, i.e. they do not have units. As described above, to generate the numerical values 127 the wireless appliance queries the vehicle's ECU at a set time interval (e.g. every 20 seconds), and transmits a data set 122 at a longer time interval (e.g. every 10 minutes). Thus, the numerical values in the data set can represent ‘instantaneous’ values that result from a single query to the ECU, or they can represent ‘average’ values that result from an average from multiple sequential queries.

The data parameters within the set 122 describe a variety of electrical, mechanical, and emissions-related functions in the vehicle. Several of the more significant parameters from the set are listed in Table 1, below:

TABLE 1 Parameters Monitored from Vehicle Pending DTCs Ignition Timing Advance Calculated Load Value Air Flow Rate MAF Sensor Engine RPM Engine Coolant Temperature Intake Air Temperature Absolute Throttle Position Sensor Vehicle Speed Short-Term Fuel Trim Long-Term Fuel Trim MIL Light Status Oxygen Sensor Voltage Oxygen Sensor Location Delta Pressure Feedback EGR Pressure Sensor Evaporative Purge Solenoid Dutycycle Fuel Level Input Sensor Fuel Tank Pressure Voltage Engine Load at the Time of Misfire Engine RPM at the Time of Misfire Throttle Position at the Time of Misfire Vehicle Speed at the Time of Misfire Number of Misfires Transmission Fluid Temperature PRNDL position (1, 2, 3, 4, 5 = neutral, 6 = reverse) Number of Completed OBDII Trips Battery Voltage

The parameters listed in Table 1 were measured from a Ford Crown Victoria. Similar sets of data are available for nearly all vehicles manufactured after 1996. In addition to these, hundreds of other vehicle-specific parameters are also available from the vehicle's ECU.

The data set 122 shown in FIG. 6 represents a current data sent from the vehicle's wireless appliance to the host computer system. Data sets sent at earlier times can also be analyzed individually or in a group to determine the vehicle's performance. These ‘historical data’, for example, can by used to determine trends in the vehicle's performance. In some cases data analyzed in this manner can be used to predict potential problems with the vehicle before they actually occur.

Referring to FIG. 7, a web page 130 includes a historical data set 132 containing data parameter names 125′, units 129′ and a series of data sets 127a-127c transmitted at earlier times from the in-vehicle wireless appliance. Each of these data sets is similar to the data set 122 shown in FIG. 6, but is received by the host computer system at an earlier time indicated by a timestamps 140a-140c. For example, the first two data sets 127c, 127b where transmitted with time stamps 140b, 140c of 11:42 and 11:52 on Feb. 12, 2001; the last data set 127a was transmitted the next morning with a time stamp 140a of 6:05. Time-dependent data shown in this manner can be analyzed to determine trends in a vehicle's performance. The trends can then be used to diagnose or predict a problem with the vehicle.

Other embodiments are also within the scope of the invention. In particular, the web pages used to display the data can take many different forms, as can the manner in which the data are displayed. Web pages are typically written in a computer language such as ‘HTML’ (hypertext mark-up language), and may also contain computer code written in languages such as Java for performing certain functions (e.g., sorting of names). The web pages are also associated with database software (provided by companies such as Oracle) that is used to store and access data. Equivalent versions of these computer languages and software can also be used.

Different web pages may be designed and accessed depending on the end-user. As described above, individual users have access to web pages that only show data for their particular vehicle, while organizations that support a large number of vehicles (e.g. dealerships or distributors) have access to web pages that contain data from a collection of vehicles. These data, for example, can be sorted and analyzed depending on vehicle make, model, odometer reading, and geographic location. The graphical content and functionality of the web pages may vary substantially from what shown in the above-described figures. In addition, web pages may also be formatted using standard wireless access protocols (WAP) so that they can be accessed using wireless devices such as cellular telephones, personal digital assistants (PDAs), and related devices.

The web pages also support a wide range of algorithms that can be used to analyze data once it is extracted from the data packets. For example, the above-mentioned method alert messages are sent out in response to a DTC or when a vehicle approaches a pre-specified odometer reading. Alternatively, the message could be sent out when a data parameter (e.g. engine coolant temperature) exceeded a predetermined value. In some case, multiple parameters (e.g., engine speed and load) can be analyzed to generate an alert message. In general, an alert message can be sent out after analyzing one or more data parameters using any type of algorithm. These algorithms range from the relatively simple (e.g., determining mileage values for each vehicle in a fleet) to the complex (e.g., predictive engine diagnoses using ‘data mining’ techniques). Data analysis may be used to characterize an individual vehicle as described above, or a collection of vehicles, and can be used with a single data set or a collection of historical data. Algorithms used to characterize a collection of vehicles can be used, for example, for remote vehicle or parts surveys, to characterize emission performance in specific geographic locations, or to characterize traffic.

Other embodiments of the invention include algorithms for analyzing data to characterize vehicle accidents and driving patterns for insurance purposes; algorithms for determining driving patterns for use-based leasing; and algorithms for recording vehicle use and driving patterns for tax purposes. In general, any algorithm that processes data collected with the above-described method is within the scope of the invention.

Similarly, the temporal or mileage frequency at which data is collected can be adjusted to diagnose specific types of problems. For example, characterization of certain types of vehicle performance indicators, such as emissions, may need to be monitored relatively frequently (e.g., once every few minutes). Other properties, such as mileage and fluid levels, may only need to be monitored every few days, or in some cases just a few times each year.

In other embodiments, additional hardware can be added to the in-vehicle wireless appliance to increase the number of parameters in the transmitted data. For example, hardware for global-positioning systems (GPS) may be added so that the location of the vehicle can be monitored along with its data. Or the radio modem used to transmit the data may employ a terrestrial GPS system, such as that available on modems designed by Qualcomm, Inc. In still other embodiments, the location of the base station that transmits the message can be analyzed to determine the vehicle's approximate location. In addition, the wireless appliance may be interfaced to other sensors deployed in the vehicle to monitor additional data. For example, sensors for measuring tire pressure and temperature may be deployed in the vehicle and interfaced to the appliance so that data relating the tires' performance can be transmitted to the host computer system.

In other embodiments, data processed using the above-described systems can be used for: remote billing/payment of tolls; remote smog and emissions checks; remote payment of parking/valet services; remote control of the vehicle (e.g., in response to theft or traffic/registration violations); and general survey information.

Still other embodiments are within the scope of the following claims.

Claims

1. A method for monitoring a vehicle with a vehicle computer device located in the vehicle, comprising:

(a) acquiring, by a vehicle computer device connected to an engine control unit (ECU) of a vehicle via an OBD or OBD-II connector, vehicle data comprising numerical diagnostic data or location-based data associated with the vehicle;
(b) processing, by the vehicle computer device connected to the ECU of the vehicle via the OBD or OBD-II connector, the vehicle data according to a mathematical algorithm to generate derived diagnostic or location information that is at least in part derived from the acquired vehicle data, and wherein the derived diagnostic information has a meaning distinct from the acquired vehicle data;
(c) formatting, by the vehicle computer device connected to the ECU of the vehicle via the OBD or OBD-II connector, the derived diagnostic or location information for display on an application running on a host computer device, wherein the application can provide an interface for presenting information associated with the vehicle, wherein the interface includes at least one of an icon and or a data field associated with derived diagnostic information indicative of the vehicle's emissions performance, of the vehicle; and
(d) wirelessly transmitting, by a cellular modem included in the vehicle computer device connected to the ECU of the vehicle via the OBD or OBD-II connector and via an internet, the derived diagnostic information in a communication to the host computer device,
the derived diagnostic information for a first diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a first temporal interval or mileage interval set based on the first diagnostic problem to be diagnosed, and
the derived diagnostic information for a second diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a second temporal interval or mileage interval set based on the second diagnostic problem to be diagnosed, the first temporal interval or mileage interval being simultaneous with and different than the second temporal interval or mileage interval.

2. The method of claim 1, wherein the application includes a browser.

3. The method of claim 1, wherein the processing further includes extracting information representative of at least one of the following vehicle parameters from the received vehicle data: numerical data, an alphanumeric text message, and or a vehicle identification number.

4. The method of claim 1, wherein the numerical diagnostic data includes at least one of the following numerical parameters: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel injector performance, spark-plug timing, and or a status of an anti-lock braking system.

5. The method of claim 1, wherein the host computer device is one of a cellular telephone, a personal digital assistant (PDA), a wireless smartphone, or a personal computer.

6. A vehicle computer device, located in a vehicle, configured to perform a method, the method comprising:

a cellular modem;
a connector that connects to an OBD or OBD-II connector of a vehicle; and
a processor to: (a) acquiring acquire vehicle data comprising numerical diagnostic data or location-based data associated with the vehicle via the OBD or OBD-II connector of the vehicle; (b) processing process the vehicle data according to a mathematical algorithm to generate derived diagnostic or location information that is at least in part derived from the acquired vehicle data, and wherein the derived diagnostic information has a meaning distinct from the acquired vehicle data; (c) formatting format the derived diagnostic or location information for display on an application running on a host computer device, wherein the application can provide an interface for presenting information associated with the vehicle, wherein the interface includes at least one of an icon and or a data field associated with derived diagnostic information indicative of the vehicle's emissions performance, of the vehicle; and (d) wirelessly transmitting transmit, using the cellular modem, the derived diagnostic information in a communication via an internet to the host computer device, the derived diagnostic information for a first diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a first temporal interval or mileage interval set based on the first diagnostic problem to be diagnosed, and the derived diagnostic information for a second diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a second temporal interval or mileage interval set based on the second diagnostic problem to be diagnosed, the first temporal interval or mileage interval being simultaneous with and different than the second temporal interval or mileage interval.

7. The method vehicle computer device of claim 6, wherein the application includes a browser.

8. The method vehicle computer device of claim 6, wherein the processor, when processing the vehicle data, is to:

wherein the processing further includes extracting extract information representative of at least one of the following vehicle parameters from the received vehicle data: numerical data, an alphanumeric text message, and or a vehicle identification number.

9. The method vehicle computer device of claim 6, wherein the numerical diagnostic data includes at least one of the following numerical parameters: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel injector performance, spark-plug timing, and or a status of an anti-lock braking system.

10. The method vehicle computer device of claim 6, wherein the host computer device is one of a cellular telephone, a personal digital, assistant (PDA), a wireless smartphone, or a personal computer.

11. A graphical user interface running on a host computer device for displaying derived diagnostic or location information corresponding to a vehicle wherein the derived diagnostic or location information displayed by the graphical user interface includes diagnostic or location information wirelessly transmitted by, a vehicle computer device coupled to the vehicle to acquire diagnostic and location vehicle data generated thereby, and wherein the vehicle computer device processes the diagnostic or location vehicle data according to a mathematical algorithm, and wherein the information comprises at least one of vehicle status reports and vehicle service recommendations to generate the derived information so that it has a meaning distinct from the acquired diagnostic and location vehicle data,

wherein the graphical user interface includes at least one of an icon and data field associated with derived information indicative of the vehicle's emissions.

12. The graphical user interface of claim 11 wherein the displayed graphical user interface includes a web browser.

13. The graphical user interface of claim 11, wherein the graphical user interface is configured for displaying information formatted according to at least one wireless access protocol (WAP).

14. The graphical user interface of claim 11, wherein the host computer device is one of a cellular telephone, a personal digital assistant (PDA), a wireless smartphone, or a personal computer.

15. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a vehicle computer device connected to an engine control unit (ECU) of a vehicle via an OBD or OBD-II connector, cause the one or more processors to: acquire vehicle data comprising numerical diagnostic data associated with the vehicle via the OBD or OBD-II connector of the vehicle; process the vehicle data according to a mathematical algorithm to generate derived diagnostic information that is at least in part derived from the vehicle data, and wherein the derived diagnostic information has a meaning distinct from the vehicle data; format the derived diagnostic information for display on an application running on a host computer device, wherein the application can provide an interface for presenting information associated with the vehicle, wherein the interface includes at least one of an icon or a data field associated with derived diagnostic information indicative of emissions performance of the vehicle; and
wirelessly transmit, using a cellular modem included in the vehicle computer device, the derived diagnostic information in a communication via an internet to the host computer device, the derived diagnostic information for a first diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a first temporal interval or mileage interval set based on the first diagnostic problem to be diagnosed, and the derived diagnostic information for a second diagnostic problem to be diagnosed being monitored and wirelessly transmitted at a second temporal interval or mileage interval set based on the second diagnostic problem to be diagnosed, the first temporal interval or mileage interval being simultaneous with and different than the second temporal interval or mileage interval.

16. The non-transitory computer-readable medium of claim 15, wherein the application includes a browser.

17. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the one or more processors to process the vehicle data, cause the one or more processors to:

extract information representative of at least one of the following vehicle parameters from the vehicle data: numerical data, an alphanumeric text message, or a vehicle identification number.

18. The non-transitory computer-readable medium of claim 15, wherein the numerical diagnostic data includes at least one of the following numerical parameters: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel injector performance, spark-plug tinting, or a status of an anti-lock braking system.

19. The non-transitory computer-readable medium of claim 15, wherein the host computer device is one of a cellular telephone, a personal digital, assistant (PDA), a wireless smartphone, or a personal computer.

20. The non-transitory computer-readable medium of claim 15, wherein the first temporal interval or mileage interval is a temporal interval, and

the derived diagnostic information for the first diagnostic problem to be diagnosed is wirelessly transmitted by the cellular modem a plurality of times each minute based on the temporal interval to provide the derived diagnostic information to the host computer device in real-time.

21. The non-transitory computer-readable medium of claim 15, wherein the first temporal interval or mileage interval is a mileage interval.

Referenced Cited
U.S. Patent Documents
3748894 July 1973 White et al.
4258421 March 24, 1981 Juhasz et al.
4602127 July 22, 1986 Neely et al.
4690475 September 1, 1987 McElroy
4694408 September 15, 1987 Zaleski
4926330 May 15, 1990 Abe et al.
4956777 September 11, 1990 Cearley et al.
5003317 March 26, 1991 Gray et al.
5026293 June 25, 1991 Wilson
5050080 September 17, 1991 Abe
5157610 October 20, 1992 Asano et al.
5223844 June 29, 1993 Mansell et al.
5289378 February 22, 1994 Miller et al.
5343906 September 6, 1994 Tibbals
5431042 July 11, 1995 Lambert
5442553 August 15, 1995 Parrillo
5450321 September 12, 1995 Crane
5463567 October 31, 1995 Boen et al.
5473540 December 5, 1995 Schmitz
5479479 December 26, 1995 Braitberg et al.
5491486 February 13, 1996 Welles et al.
5519621 May 21, 1996 Wortham
5532927 July 2, 1996 Pink et al.
5537336 July 16, 1996 Joyce
5550551 August 27, 1996 Alesio
5555498 September 10, 1996 Berra et al.
5574427 November 12, 1996 Cavallaro
5586130 December 17, 1996 Doyle
5619412 April 8, 1997 Hapka
5633645 May 27, 1997 Day
5636122 June 3, 1997 Shah et al.
5671141 September 23, 1997 Smith et al.
5673305 September 30, 1997 Ross
5680328 October 21, 1997 Skorupski et al.
5729452 March 17, 1998 Smith et al.
5732074 March 24, 1998 Spaur et al.
5737215 April 7, 1998 Schricker et al.
5739761 April 14, 1998 Kobayashi
5750886 May 12, 1998 Lambert et al.
5754965 May 19, 1998 Hagenbuch
5758300 May 26, 1998 Abe
5774828 June 30, 1998 Brunts et al.
5781101 July 14, 1998 Stephen et al.
5781871 July 14, 1998 Mezger et al.
5797134 August 18, 1998 McMillan
5798647 August 25, 1998 Martin et al.
5808907 September 15, 1998 Shetty et al.
5815071 September 29, 1998 Doyle
5828585 October 27, 1998 Welk et al.
5844473 December 1, 1998 Kaman
5850209 December 15, 1998 Lemke et al.
5884202 March 16, 1999 Arjomand
5928292 July 27, 1999 Miller et al.
5941918 August 24, 1999 Blosser
5957985 September 28, 1999 Wong
5964821 October 12, 1999 Brunts et al.
5987377 November 16, 1999 Westerlage et al.
6020654 February 1, 2000 Chutorash
6064970 May 16, 2000 McMillan et al.
6088648 July 11, 2000 Shah et al.
6104988 August 15, 2000 Klarer
6140969 October 31, 2000 Lindenmeier et al.
6141611 October 31, 2000 Mackey et al.
6141710 October 31, 2000 Miesterfeld
6144916 November 7, 2000 Wood et al.
6154658 November 28, 2000 Caci
6167426 December 26, 2000 Payne et al.
6202008 March 13, 2001 Beckert et al.
6208948 March 27, 2001 Klingler et al.
6225898 May 1, 2001 Kamiya et al.
6236933 May 22, 2001 Lang
6240295 May 29, 2001 Kennedy et al.
6240365 May 29, 2001 Bunn
6246935 June 12, 2001 Buckley
6263268 July 17, 2001 Nathanson
6278921 August 21, 2001 Harrison et al.
6285953 September 4, 2001 Harrison et al.
6292718 September 18, 2001 Staiger
6295492 September 25, 2001 Lang et al.
6330499 December 11, 2001 Chou et al.
6338152 January 8, 2002 Fera et al.
6339736 January 15, 2002 Moskowitz et al.
6339745 January 15, 2002 Novik
6346876 February 12, 2002 Flick
6354868 March 12, 2002 Korczynski et al.
6356205 March 12, 2002 Salvo et al.
6356823 March 12, 2002 Iannotti et al.
6362730 March 26, 2002 Razavi et al.
6370454 April 9, 2002 Moore
6400701 June 4, 2002 Lin et al.
6401528 June 11, 2002 Lambert
6405106 June 11, 2002 Sheth et al.
6408232 June 18, 2002 Cannon et al.
6429773 August 6, 2002 Schuyler
6442460 August 27, 2002 Larson et al.
6459988 October 1, 2002 Fan et al.
6477452 November 5, 2002 Good
6480170 November 12, 2002 Langley et al.
6487479 November 26, 2002 Nelson
6487494 November 26, 2002 Odinak et al.
6487717 November 26, 2002 Brunemann et al.
6496777 December 17, 2002 Tennison et al.
6502030 December 31, 2002 Hilleary
6505106 January 7, 2003 Lawrence et al.
6507786 January 14, 2003 Flick
6512466 January 28, 2003 Flick
6522267 February 18, 2003 Flick
6526335 February 25, 2003 Treyz et al.
6526460 February 25, 2003 Dauner et al.
6529159 March 4, 2003 Fan et al.
6552682 April 22, 2003 Fan
6556889 April 29, 2003 Rudick et al.
6556905 April 29, 2003 Mittelsteadt et al.
6564127 May 13, 2003 Bauerle et al.
6564128 May 13, 2003 Baird et al.
6580916 June 17, 2003 Weisshaar et al.
6594576 July 15, 2003 Fan et al.
6594579 July 15, 2003 Lowrey et al.
6604032 August 5, 2003 Moller
6604033 August 5, 2003 Banet et al.
6604038 August 5, 2003 Lesesky et al.
6609051 August 19, 2003 Fiechter et al.
6611686 August 26, 2003 Smith et al.
6611739 August 26, 2003 Harvey et al.
6611740 August 26, 2003 Lowrey et al.
6611755 August 26, 2003 Coffee et al.
6636790 October 21, 2003 Lightner et al.
6662091 December 9, 2003 Wilson et al.
6664922 December 16, 2003 Fan
6671617 December 30, 2003 Odinak et al.
6675081 January 6, 2004 Shuman et al.
6678614 January 13, 2004 McCarthy et al.
6687587 February 3, 2004 Kacel
6694234 February 17, 2004 Lockwood et al.
6701233 March 2, 2004 Namaky et al.
6718425 April 6, 2004 Pajakowski et al.
6732031 May 4, 2004 Lightner et al.
6732032 May 4, 2004 Banet et al.
6738697 May 18, 2004 Breed
6751452 June 15, 2004 Kupczyk et al.
6751479 June 15, 2004 Knight
6754485 June 22, 2004 Obradovich et al.
6757262 June 29, 2004 Weisshaar et al.
6766233 July 20, 2004 Odinak et al.
6795017 September 21, 2004 Puranik et al.
6801841 October 5, 2004 Tabe
6809659 October 26, 2004 Flick et al.
6812888 November 2, 2004 Drury et al.
6832140 December 14, 2004 Fan et al.
6832175 December 14, 2004 Adachi et al.
6836708 December 28, 2004 Tripathi
6845307 January 18, 2005 Rother
6845362 January 18, 2005 Furuta et al.
6862524 March 1, 2005 Nagda et al.
6867733 March 15, 2005 Sandhu et al.
6868386 March 15, 2005 Henderson
6879894 April 12, 2005 Lightner et al.
6882313 April 19, 2005 Fan et al.
6889064 May 3, 2005 Baratono et al.
6889135 May 3, 2005 Curatolo et al.
6892131 May 10, 2005 Coffee et al.
6895444 May 17, 2005 Weisshaar et al.
6907330 June 14, 2005 Eisenmann et al.
6922566 July 26, 2005 Puranik et al.
6928348 August 9, 2005 Lightner et al.
6941202 September 6, 2005 Wilson et al.
6944121 September 13, 2005 Weste et al.
6947760 September 20, 2005 Weisshaar et al.
6947816 September 20, 2005 Chen
6956501 October 18, 2005 Kitson
6957133 October 18, 2005 Hunt et al.
6970703 November 29, 2005 Fuchs et al.
6973324 December 6, 2005 Weisshaar et al.
6988033 January 17, 2006 Lowrey et al.
6993675 January 31, 2006 Roddy et al.
7016774 March 21, 2006 Barber et al.
7034710 April 25, 2006 Falada et al.
7062375 June 13, 2006 Hatano
7072668 July 4, 2006 Chou
7085710 August 1, 2006 Beckert
7092803 August 15, 2006 Kapolka et al.
7113127 September 26, 2006 Banet et al.
7155321 December 26, 2006 Bromley et al.
7174243 February 6, 2007 Lightner et al.
7225065 May 29, 2007 Hunt et al.
7228211 June 5, 2007 Lowrey et al.
7400954 July 15, 2008 Sumcad et al.
7447574 November 4, 2008 Washicko et al.
7477968 January 13, 2009 Lowrey et al.
7480551 January 20, 2009 Lowrey et al.
7523159 April 21, 2009 Williams et al.
7532962 May 12, 2009 Lowrey et al.
7532963 May 12, 2009 Lowrey et al.
7747365 June 29, 2010 Lowrey et al.
7891004 February 15, 2011 Gelvin
7904219 March 8, 2011 Lowrey et al.
8214100 July 3, 2012 Lowrey et al.
8447459 May 21, 2013 Lowrey et al.
20010016789 August 23, 2001 Staiger
20010018628 August 30, 2001 Jenkins et al.
20010033225 October 25, 2001 Razavi et al.
20010034609 October 25, 2001 Dovolis
20020008644 January 24, 2002 Flick
20020008645 January 24, 2002 Flick
20020016655 February 7, 2002 Joao
20020029101 March 7, 2002 Larson et al.
20020032505 March 14, 2002 Good
20020065698 May 30, 2002 Schick et al.
20020073170 June 13, 2002 Hoffman et al.
20020078458 June 20, 2002 Furon et al.
20020099520 July 25, 2002 Falada et al.
20020118222 August 29, 2002 Fogarty
20020133273 September 19, 2002 Lowrey et al.
20020140545 October 3, 2002 Nietupski et al.
20020143446 October 3, 2002 Rogers et al.
20020147610 October 10, 2002 Tabe
20020150050 October 17, 2002 Nathanson
20020171650 November 21, 2002 Prabhakaran
20020173885 November 21, 2002 Lowrey et al.
20020173889 November 21, 2002 Odinak et al.
20020177476 November 28, 2002 Chou
20030004623 January 2, 2003 Namaky et al.
20030004624 January 2, 2003 Wilson et al.
20030009270 January 9, 2003 Breed
20030040854 February 27, 2003 Rendahl
20030078722 April 24, 2003 Odinak et al.
20030083809 May 1, 2003 Hatano
20030093199 May 15, 2003 Mavreas
20030093204 May 15, 2003 Adachi et al.
20030130005 July 10, 2003 Weisshaar et al.
20030130774 July 10, 2003 Tripathi et al.
20030139179 July 24, 2003 Fuchs et al.
20030147534 August 7, 2003 Ablay et al.
20030182055 September 25, 2003 Curatolo et al.
20030231118 December 18, 2003 Kitson
20030236596 December 25, 2003 Eisenmann et al.
20040023645 February 5, 2004 Olsen et al.
20040039502 February 26, 2004 Wilson et al.
20040039504 February 26, 2004 Coffee et al.
20040044454 March 4, 2004 Ross et al.
20040075539 April 22, 2004 Savoie et al.
20040093134 May 13, 2004 Barber et al.
20040104842 June 3, 2004 Drury et al.
20040196182 October 7, 2004 Unnold
20050131729 June 16, 2005 Melby et al.
20050144318 June 30, 2005 Chang
20060116800 June 1, 2006 Obradovich
20070069947 March 29, 2007 Banet et al.
20080027606 January 31, 2008 Helm
20080319665 December 25, 2008 Berkobin et al.
20100228429 September 9, 2010 Lowrey et al.
20110153367 June 23, 2011 Amigo
20120053759 March 1, 2012 Lowrey et al.
20120259504 October 11, 2012 Lowrey et al.
Foreign Patent Documents
2133673 April 1996 CA
2372900 May 2003 CA
0816820 January 1998 EP
2000/040038 July 2000 WO
2000/079727 December 2000 WO
Other references
  • RD-422061 A; Anonymous; Jun. 10, 1999; Abstract, Using Internet for vehicle diagnostics-enabling using to operate vehicle personal computer to direct web browser to vehicle diagnostics website . . . .
  • “#1 Appendix Chart of Asserted Claims U.S. Pat. No. 6,636,790”, 6:07-CV-00466-LED, entered, Feb. 11, 2008.
  • “#2 Appendix Chart of Asserted Claims U.S. Pat. No. 6,372,031”, 6:07-CV-00466-LED, entered, Feb. 11, 2008.
  • “#3 Appendix Chart of Asserted Claims U.S. Pat. No. 6,611,740”, 6:07-CV-00466-LED, entered, Feb. 11, 2008.
  • “40 CFR 51”, 40 CFR 51, Ch. I (Jul. 1, 2001 Edition), pp. 130-481.
  • “40 CFR 85”, 40 CFR 85. Ch. I (Jul. 1, 2001 Edition), 143 pages.
  • “Automotive ISO 9141 Serial Link Driver”, Motorola, Inc. Document MC333199/D, 1996, 12 Pages.
  • “Chipset”, Definition of “Chipset,” printed from Webopedia, Internet site, Oct. 31, 2002, 3 pages.
  • “Definition of “Chipset” from Wikipedia, Feb. 23, 2006.”, Definition of “Chipset” from Wikipedia, Feb. 23, 2006.
  • “12C”, printed from http://www.nxp.com, Internet site, (associated with www.philipslogic.com), website accessed on Jun. 8, 2006, 3 pages.
  • “Notice of Disclosure by HTI IP, LLC”, of Asserted Claims and Infringement Contentions and Document Production Accompanying Disclosure, Feb. 11, 2008.
  • “Qualcomm Chipset Solutions”, printed from http://www.qualcomm.com, Internet site, website accessed on Jun. 8, 2006, 48 pages.
  • Di Genova, et al., “Incorporation of Wireless Communications into Vehicle On-Board Diagnostic (OBD) Systems”, Report No. SR00-01-03 prepared for California Air Resources Board (Sierra Research, Inc.) Jan. 18, 2000.
  • Oliver, “Implementing the J1850 Protocol”, Intel Corporation, 15 p.p.
  • Wilson, et al., “Modular system for multiparameter in-line machine fluid analysis”, (Technology showcase Apr. 3-6, 2000).
Patent History
Patent number: RE47422
Type: Grant
Filed: Jul 17, 2013
Date of Patent: Jun 4, 2019
Assignee: Verizon Patent and Licensing Inc. (Basking Ridge, NJ)
Inventors: Larkin Hill Lowrey (Seabrook, TX), Matthew Banet (San Diego, CA), Bruce Lightner (La Jolla, CA), Diego Borrego (San Diego, CA), Chuck Myers (La Jolla, CA)
Primary Examiner: Dennis G Bonshock
Application Number: 13/944,782
Classifications
Current U.S. Class: Exhaust Gas Component Analysis (73/114.71)
International Classification: G06F 19/00 (20180101); G07C 5/00 (20060101); F02M 25/08 (20060101);