The present invention relates to use of an internet-based system for monitoring a vehicle's performance.
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.
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, 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.
The features and advantages of the present invention can be understood by reference to the following detailed description taken with the drawings, in which:
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.
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.
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.
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
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.
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:
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
Referring to
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.
This application is a continuation application of U.S. patent application Ser. No. 09/804,888, filed Mar. 13, 2001 now abandoned, the contents of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3748894 | White et al. | Jul 1973 | A |
4258421 | Juhasz et al. | Mar 1981 | A |
4602127 | Neely et al. | Jul 1986 | A |
4690475 | McElroy | Sep 1987 | A |
4694408 | Zaleski | Sep 1987 | A |
4926330 | Abe et al. | May 1990 | A |
4956777 | Cearley et al. | Sep 1990 | A |
5003317 | Gray et al. | Mar 1991 | A |
5026293 | Wilson | Jun 1991 | A |
5050080 | Abe | Sep 1991 | A |
5157610 | Asano et al. | Oct 1992 | A |
5223844 | Mansell et al. | Jun 1993 | A |
5289378 | Miller et al. | Feb 1994 | A |
5343906 | Tibbals, III | Sep 1994 | A |
5442553 | Parrillo | Aug 1995 | A |
5450321 | Crane | Sep 1995 | A |
5463567 | Boen et al. | Oct 1995 | A |
5473540 | Schmitz | Dec 1995 | A |
5479479 | Braitberg et al. | Dec 1995 | A |
5491486 | Welles et al. | Feb 1996 | A |
5519621 | Wortham | May 1996 | A |
5532927 | Pink et al. | Jul 1996 | A |
5537336 | Joyce | Jul 1996 | A |
5550551 | Alesio | Aug 1996 | A |
5555498 | Berra et al. | Sep 1996 | A |
5574427 | Cavallaro | Nov 1996 | A |
5586130 | Doyle | Dec 1996 | A |
5619412 | Hapka | Apr 1997 | A |
5633645 | Day | May 1997 | A |
5636122 | Shah et al. | Jun 1997 | A |
5671141 | Smith et al. | Sep 1997 | A |
5673305 | Ross | Sep 1997 | A |
5680328 | Skorupski et al. | Oct 1997 | A |
5732074 | Spaur et al. | Mar 1998 | A |
5737215 | Schricker et al. | Apr 1998 | A |
5739761 | Kobayashi | Apr 1998 | A |
5750886 | Lambert et al. | May 1998 | A |
5754965 | Hagenbuch | May 1998 | A |
5758300 | Abe | May 1998 | A |
5774828 | Brunts et al. | Jun 1998 | A |
5781101 | Stephen et al. | Jul 1998 | A |
5781871 | Mezger et al. | Jul 1998 | A |
5797134 | McMillan et al. | Aug 1998 | A |
5798647 | Martin et al. | Aug 1998 | A |
5808907 | Shetty et al. | Sep 1998 | A |
5815071 | Doyle | Sep 1998 | A |
5828585 | Welk et al. | Oct 1998 | A |
5844473 | Kaman | Dec 1998 | A |
5850209 | Lemke et al. | Dec 1998 | A |
5884202 | Arjornand | Mar 1999 | A |
5928292 | Miller et al. | Jul 1999 | A |
5941918 | Blosser | Aug 1999 | A |
5964821 | Brunts et al. | Oct 1999 | A |
5987377 | Westerlage et al. | Nov 1999 | A |
6020654 | Chutorash | Feb 2000 | A |
6064970 | McMillan et al. | May 2000 | A |
6088648 | Shah et al. | Jul 2000 | A |
6104988 | Klarer | Aug 2000 | A |
6140969 | Lindenmeier et al. | Oct 2000 | A |
6141611 | Mackey et al. | Oct 2000 | A |
6141710 | Miesterfeld | Oct 2000 | A |
6144916 | Wood, Jr. et al. | Nov 2000 | A |
6154658 | Caci | Nov 2000 | A |
6167426 | Payne et al. | Dec 2000 | A |
6202008 | Beckert et al. | Mar 2001 | B1 |
6208948 | Klingler et al. | Mar 2001 | B1 |
6225898 | Kamiya et al. | May 2001 | B1 |
6236933 | Lang | May 2001 | B1 |
6240295 | Kennedy et al. | May 2001 | B1 |
6240365 | Bunn | May 2001 | B1 |
6246935 | Buckley | Jun 2001 | B1 |
6263268 | Nathanson | Jul 2001 | B1 |
6278921 | Harrison et al. | Aug 2001 | B1 |
6285953 | Harrison et al. | Sep 2001 | B1 |
6295492 | Lang et al. | Sep 2001 | B1 |
6330499 | Chou et al. | Dec 2001 | B1 |
6338152 | Fera et al. | Jan 2002 | B1 |
6339736 | Moskowitz et al. | Jan 2002 | B1 |
6339745 | Novik | Jan 2002 | B1 |
6346876 | Flick | Feb 2002 | B1 |
6354868 | Korczynski et al. | Mar 2002 | B1 |
6356205 | Salvo et al. | Mar 2002 | B1 |
6356823 | Iannotti et al. | Mar 2002 | B1 |
6400701 | Lin et al. | Jun 2002 | B2 |
6405106 | Sheth et al. | Jun 2002 | B1 |
6408232 | Cannon et al. | Jun 2002 | B1 |
6429773 | Schuyler | Aug 2002 | B1 |
6442460 | Larson et al. | Aug 2002 | B1 |
6459988 | Fan et al. | Oct 2002 | B1 |
6480170 | Langley et al. | Nov 2002 | B1 |
6487479 | Nelson | Nov 2002 | B1 |
6487494 | Odinak et al. | Nov 2002 | B2 |
6487717 | Brunemann et al. | Nov 2002 | B1 |
6496777 | Tennison et al. | Dec 2002 | B2 |
6502030 | Hilleary | Dec 2002 | B2 |
6505106 | Lawrence et al. | Jan 2003 | B1 |
6507786 | Flick | Jan 2003 | B2 |
6522267 | Flick | Feb 2003 | B2 |
6526335 | Treyz et al. | Feb 2003 | B1 |
6526460 | Dauner et al. | Feb 2003 | B1 |
6529159 | Fan et al. | Mar 2003 | B1 |
6552682 | Fan et al. | Apr 2003 | B1 |
6556889 | Rudick et al. | Apr 2003 | B2 |
6556905 | Mittelsteadt et al. | Apr 2003 | B1 |
6564127 | Bauerle et al. | May 2003 | B1 |
6580916 | Weisshaar et al. | Jun 2003 | B1 |
6594579 | Lowrey et al. | Jul 2003 | B1 |
6604032 | Moller | Aug 2003 | B1 |
6604033 | Banet et al. | Aug 2003 | B1 |
6604038 | Lesesky et al. | Aug 2003 | B1 |
6609051 | Fiechter et al. | Aug 2003 | B2 |
6611686 | Smith et al. | Aug 2003 | B1 |
6611739 | Harvey et al. | Aug 2003 | B1 |
6611740 | Lowrey et al. | Aug 2003 | B2 |
6611755 | Coffee et al. | Aug 2003 | B1 |
6636790 | Lightner et al. | Oct 2003 | B1 |
6675081 | Shuman et al. | Jan 2004 | B2 |
6678614 | McCarthy et al. | Jan 2004 | B2 |
6687587 | Kacel | Feb 2004 | B2 |
6694234 | Lockwood et al. | Feb 2004 | B2 |
6718425 | Pajakowski et al. | Apr 2004 | B1 |
6732031 | Lightner et al. | May 2004 | B1 |
6732032 | Banet et al. | May 2004 | B1 |
6751452 | Kupczyk et al. | Jun 2004 | B1 |
6751479 | Knight | Jun 2004 | B1 |
6754485 | Obradovich et al. | Jun 2004 | B1 |
6757262 | Weisshaar et al. | Jun 2004 | B1 |
6845362 | Furuta et al. | Jan 2005 | B2 |
6895444 | Weisshaar et al. | May 2005 | B1 |
6944121 | Weste et al. | Sep 2005 | B1 |
6947760 | Weisshaar et al. | Sep 2005 | B2 |
6947816 | Chen | Sep 2005 | B2 |
6973324 | Weisshaar et al. | Dec 2005 | B2 |
7092803 | Kapolka et al. | Aug 2006 | B2 |
7155321 | Bromley et al. | Dec 2006 | B2 |
20010016789 | Staiger | Aug 2001 | A1 |
20010018628 | Jenkins et al. | Aug 2001 | A1 |
20010033225 | Razavi et al. | Oct 2001 | A1 |
20010034609 | Dovolis | Oct 2001 | A1 |
20020008644 | Flick | Jan 2002 | A1 |
20020008645 | Flick et al. | Jan 2002 | A1 |
20020016655 | Joao | Feb 2002 | A1 |
20020029101 | Larson et al. | Mar 2002 | A1 |
20020032505 | Good | Mar 2002 | A1 |
20020065698 | Schick et al. | May 2002 | A1 |
20020073170 | Hoffman et al. | Jun 2002 | A1 |
20020078458 | Furon et al. | Jun 2002 | A1 |
20020099520 | Falada et al. | Jul 2002 | A1 |
20020118222 | Fogarty | Aug 2002 | A1 |
20020133273 | Lowrey et al. | Sep 2002 | A1 |
20020140545 | Nietupski et al. | Oct 2002 | A1 |
20020143446 | Rogers et al. | Oct 2002 | A1 |
20020147610 | Tabe | Oct 2002 | A1 |
20020150050 | Nathanson | Oct 2002 | A1 |
20020171650 | Prabhakaran | Nov 2002 | A1 |
20020173889 | Odinak et al. | Nov 2002 | A1 |
20020177476 | Chou | Nov 2002 | A1 |
20030004623 | Namaky et al. | Jan 2003 | A1 |
20030004624 | Wilson et al. | Jan 2003 | A1 |
20030009270 | Breed | Jan 2003 | A1 |
20030078722 | Odinak et al. | Apr 2003 | A1 |
20030083809 | Hatano | May 2003 | A1 |
20030093199 | Mavreas | May 2003 | A1 |
20030093204 | Adachi et al. | May 2003 | A1 |
20030130005 | Weisshaar et al. | Jul 2003 | A1 |
20030139179 | Fuchs et al. | Jul 2003 | A1 |
20030147534 | Ablay et al. | Aug 2003 | A1 |
20030182055 | Curatolo et al. | Sep 2003 | A1 |
20030231118 | Kitson | Dec 2003 | A1 |
20030236596 | Eisenmann et al. | Dec 2003 | A1 |
20040023645 | Olsen et al. | Feb 2004 | A1 |
20040039502 | Wilson et al. | Feb 2004 | A1 |
20040039504 | Coffee et al. | Feb 2004 | A1 |
20040044454 | Ross et al. | Mar 2004 | A1 |
20040075539 | Savoie et al. | Apr 2004 | A1 |
20040093134 | Barber et al. | May 2004 | A1 |
20040104842 | Drury et al. | Jun 2004 | A1 |
20040196182 | Unnold | Oct 2004 | A1 |
20050131729 | Melby et al. | Jun 2005 | A1 |
20070069947 | Banet et al. | Mar 2007 | A1 |
Number | Date | Country |
---|---|---|
2133673 | Oct 1994 | CA |
2372900 | May 2003 | CA |
0816820 | Jan 1998 | EP |
WO 0040038 | Jul 2000 | WO |
WO 0079727 | Dec 2000 | WO |
Number | Date | Country | |
---|---|---|---|
Parent | 09804888 | Mar 2001 | US |
Child | 10614665 | US |