Various embodiments include methods and systems for determining a tire pressure status. Further embodiments include methods and systems for determining a rate of inflation or deflation of one or more vehicle tires.
Various examples exist in the field for determining a tire pressure status. For instance, U.S. Pat. No. 6,441,732 issued to Laitsaari et al. discloses a system for displaying tire characteristics. A vehicle depot such as for example a gas station, a bus stop or a truck terminal, is equipped with a communications system to receive data from a vehicle that represents the operational characteristics of the tires of the vehicle. The information may be automatically transmitted to an appropriate transceiver located at the gas station when the vehicle enters a preset perimeter of, or is a given distance from, the gas station. Thus, when the operator of the vehicle begins to pump gas or input air to the tires of his vehicle, he could readily view the operational characteristics, or the status, of the tires of his vehicle at a display that is mounted either at the gas pump, the handle of the gas hose, the housing of the air supply or some other convenient location at the gas station. In addition, the attendant at the gas station can view the operational characteristics of the tires of any of the vehicles parked at the gas station so that, if tire abnormalities are observed, the attendant could inform the operator of the vehicle that has the abnormal tire(s) that there is a potential problem. A permanent record of the operational characteristics of the tires of any of the vehicles may be printed out. Displays may also be incorporated to roadside signs/billboards so that passing motorists may readily ascertain from the displays the operational characteristics of the tires of their vehicles. Simple alert messages that apprize the motorists, either at the vehicle depot or passing the roadside sign/billboard displays, of whether attention needs to be directed to the tires of their vehicles may be displayed in place of the actual tire operational characteristics.
U.S. Pat. No. 6,612,165 issued to Juzswik et al. discloses a tire pressure monitoring system with pressure gauge operating mode for indicating when air pressure within a tire is within a predetermined pressure range. A tire inflation pressure monitoring system and a method for monitoring air pressure within a tire are provided. The system includes a tire based unit for sensing air pressure within the tire and for transmitting a pressure signal indicative thereof. The system also includes a vehicle based unit for receiving the pressure signal and for comparing the pressure signal to a predefined pressure range. The vehicle based unit is operable in one of (i) a normal operating mode that outputs an alert signal in response to the air pressure within the tire being outside of the predefined pressure range and (ii) a pressure gauge operating mode that outputs an in-range signal in response to the air pressure within the tire being within the predetermined pressure range.
One aspect may include a tire pressure status notification system for a vehicle. The tire pressure status notification system may include at least one computer which may be configured to receive input defining an inflation status of one or more vehicle tires and receive tire inflation data of the one or more tires. The at least one computer may be also configured to calculate a specific value associated with an inflation event of the one or more vehicle tires based on the inflation data.
The specific value may be a numeric pressure value of the one or more vehicle tires measured in a unit of pressure. The specific value may also be an inflation rate.
The specific numeric pressure value may be a pressure value of the one or more tires measured at one or more instances during the inflation event. The numeric pressure values may additionally or alternatively be a difference between a stored placard pressure value (which may be input by a user) and a pressure value of the one or more tires measured at one or more instances during the inflation event.
The specific inflation rate value may be measured in a unit of time.
The at least one computer may be further configured to generate one or more messages for outputting the specific value from one or more vehicle components (e.g., and without limitation, one or more vehicle lights, a vehicle horn, a vehicle audio system, or a voice-based vehicle computing system) and to transmit the one or more messages to the one or more vehicle components. The specific value may be output as one or more messages from the vehicle. The messages may be audible and may include, but are not limited to, one or more beeps, tones, horn honks, or one or more voice-based messages.
Another aspect may include a method for tire pressure status notification from a vehicle. The method may include receiving input defining an inflation status of one or more vehicle tires and receiving tire inflation data of the one or more tires. The status input and the inflation data may be received via one or more data packets transmitted from one or more tire pressure monitoring sensors. In one embodiment, the status input and the inflation data may be received in response to a triggering event (e.g., and without limitation, an air mass change of one or more tires). In a further embodiment, the status input and the inflation data may be received periodically after the triggering event (e.g., and without limitation, every 15 to 30 seconds).
The method may further include calculating a specific value associated with an inflation event of the one or more vehicle tires based on the inflation data. One or more messages for outputting the specific value from one or more vehicle components may be generated and transmitted to the one or more vehicle components. In one embodiment, the one or more vehicle components may be selected based on a user preference. The specific value may be output as one or more messages from the vehicle.
In one embodiment, the method may include periodically sampling a pressure value of the one or more tires. This sampled pressure value may be included in the tire inflation data. Further, the pressure value may be sampled according to a sampling mode.
In another embodiment, the tire inflation data may include at least one of a placard pressure value and a duration of inflation of the one or more tires.
Another aspect may include a method which includes receiving input defining an inflation status of one or more vehicle tires and receiving inflation data for the vehicle tires. The method may also include calculating a specific value for an inflation event based on the inflation data. The specific value may be output as one or more messages to one or more vehicle components.
These and other aspects of the present invention will be better understood in view of the attached drawings and following detailed description of the invention.
The figures identified below are illustrative of some embodiments of the present invention. The figures are not intended to be limiting of the invention recited in the appended claims. Embodiments of the present invention, both as to their organization and manner of operation, together with further objects and advantages thereof, may best be understood with reference to the following description, taken in connection with the accompanying drawings, in which:
a illustrates a data packet message format for transmitting one or more messages from one or more tire pressure monitoring system sensors according to one of the various embodiments;
b illustrates a data packet message format for transmitting a tire pressure status message from one or more tire pressure monitoring system sensors according to one of the various embodiments;
c illustrates a non-limiting example of a function code transmitted in the data packet of
Detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.
Tire sensors 104a-d may be installed onto one or more wheels as part of the TPMS in order to detect the pressure status of one or more vehicle tires. Furthermore, tire sensors 104a-d may periodically monitor or sample tire pressure for making a pressure determination. For example, tire sensors 104a-d may monitor tire pressure every 15 minutes. The periods at which the sensors 104a-d may monitor the tire pressure may vary depending on the preferences of the vehicle manufacturer.
Tire sensor(s) 104a-d may have different modes for monitoring tire pressure. Non-limiting examples of tire sensor modes include a rotating mode (i.e., wheels are moving), a stationary mode (i.e., wheels have been stationary for an extended period of time, e.g., greater than 15 minutes), and an interim mode (i.e., a predetermined time (e.g., 15 minutes) between a tire pressure event (including, but not limited to, wheel motion) and the stationary mode). The monitoring periods may also vary depending on the mode in which the tire sensors 104a-d are operating. For example, in a rotating mode, tire sensors 104a-d may monitor tire pressure every 5 seconds. In stationary mode, tire sensors 104a-d may monitor tire pressure less frequently (e.g., every minute). In the interim mode, the sensors 104a-d may monitor tire pressure every 2 seconds. The mode in which the tires are operating may be based on signal(s) transmitted from a motion sensor(s) communicating with tire pressure sensor(s) 104a-d indicating a movement status of the tires. Furthermore, one or more timers may be installed in sensor(s) 104a-d for measuring the span of the interim period.
During a tire pressure event (i.e., an event effecting tire pressure including, but limited to, an inflation event or deflation event), tire sensors 104a-d may enter a rapid pressure change mode (RPC). In RPC mode, sensors 104a-d may transmit the monitored tire pressure data obtained from the one or more tires. Transmission rates may vary depending on vehicle manufacturer preferences. In one non-limiting embodiment, the tire pressure data may be transmitted in the range of every 15 to 30 seconds.
The tire pressure data may be transmitted to a TPMS receiver 108 for transmission to the vehicle body control module (BCM) 102. The TPMS receiver 108 may be a radio frequency receiver module installed in the vehicle. Accordingly, in one non-limiting embodiment, the tire pressure data from the sensor 104a-d may be transmitted as radio frequency signals 110 to the TPMS receiver 108.
TPMS receiver 108 may be in communication with the BCM 102 over a vehicle communication network 112 which may include, without limitation, CAN, J-1850, GMLAN. The vehicle communication network 112 may facilitate unilateral and/or bilateral data exchange (e.g., data from and/or to sensor(s) 104a-d) between the TPMS receiver 108 and BCM 102. It should be understood that the architecture is non-limiting and may be modified and/or re-arranged without departing from the scope of the various embodiments. By way of example and not limitation, TPMS receiver 108 may be a component of BCM 102 rather than as a separate component as illustrated in
The body control module (BCM) 102 may be disposed in the vehicle and may receive tire inflation status data from tire pressure sensor(s) 104a-d. BCM 102 may include programmable instructions (or an algorithm) 106 for determining tire inflation/deflation status. For example, as will be described below, TPMS algorithm 106 may determine a tire pressure level measured in pound-force per square inch (psi), kiloPascal (kPa), bars, or other pressure units. As another non-limiting example, TPMS algorithm 106 may measure the rate of inflation/deflation which may be measured in, as a non-limiting example, units of time (e.g., seconds). It should be understood that the units of measurement used in these examples are non-limiting and other units may be utilized without departing from the scope of the various embodiments.
BCM 102 may transmit the tire inflation/deflation status to one or more components of the vehicle for transmitting a status message to a user. A non-limiting example of a user is any individual inflating/deflating the vehicle's tires such as a vehicle owner, user, or service technician. Non-limiting examples of vehicle components to which one or more inflation/deflation status messages may be transmitted include a vehicle horn 114, vehicle lights (exterior or interior) 116, a vehicle computing system 118, a vehicle audio system 118, the vehicle instrument cluster 120, or combinations thereof.
In one embodiment, the status message(s) may be transmitted to and displayed on a user's nomadic device (not shown) via a wireless connection with the vehicle computing system 118. A nomadic device may include, but is not limited to, a mobile phone, PDA, smartphone, or any other wireless device. The wireless connection may be, without limitation, BLUETOOTH, WiFi, or WiMax.
The messages to the one or more vehicle components may be transmitted over a vehicle communication network 122 which may include, without limitation, CAN, J-1850, GMLAN. It should be understood that the arrangement of
Status messages received by the BCM 102 from the sensor(s) 104a-d may be transmitted as one or more data packets according to one or more message protocols. In one embodiment, data may be defined by at least four data packets (or frames).
a illustrates a general structure of the data packet and the message protocol transmitted from the sensor(s) 104a-d. The preamble field 200 may include bits of data (e.g., 8 bits) for initializing the data transmission. The ID field 202 may include identification information of the data packet. The identification information may include a destination address and a source address. The pressure field 204 may include updated tire pressure value(s). For example, the information may include the tire pressure value from the last inflation event. In one embodiment, this information may be updated at predetermined intervals (e.g., and without limitation every 15-30 seconds). Temperature field 206 may include tire air temperature information. Status field 208 may include sensor status data including, but not limited to, one or more functions transmitted from the sensor 104a-d. Checksum field 210 may be a verification field to verify the bits of data transmitted in the packet frame.
b illustrates the composition of the status field in further detail. The status field may comprise 8 bits of information transmitted in the data packet. In one embodiment, the first three bits may be reserved to provide specific information. For example, and without limitation, the first three bits may comprise a battery status 208a, a mode status 208b, and pressure sensor range 208c.
Battery status 208a may indicate the life of the sensor's battery. In one embodiment, battery status 208a may be a low battery status message. Mode status 208b may indicate the mode in which the sensor(s) 104a-d is operating (as described above). The pressure sensor range 208c comprises the range at which the sensor obtains pressure information relative to the atmosphere. In one embodiment, the pressure range may be a numeric value (e.g., measured in “psig”). In another embodiment, the range may be a general range (e.g., a “low/high” range).
The remaining five bits of the 8 bit status field may be comprised of one or more function codes. A non-limiting example of a function code is an RPC transmission function code. When the sensor(s) 104a-d are transmitting tire inflation/deflation data in RPC mode, the status field of the data packet(s) will include the “RPC transmission” function code for identifying a rapid pressure change. A non-limiting example of a RPC function code is provided in
For example, if the tires are being inflated, the function code will include data representing tire inflation. Tire inflation may be determined by a change in measured pressure data by a predetermined amount (e.g., and without limitation, 2 psi). In one embodiment, the sensor(s) 104a-d may measure the change in pressure and transmit a pressure increase confirmation (PIC) signal based on the pressure change. Conversely, if the tires are being deflated, the function code may include data representing tire deflation. In one embodiment, the sensor(s) 104a-d may measure the change in pressure and transmit a pressure decrease confirmation (PDC) signal based on the pressure change.
The TPMS system 100, as disclosed in the various embodiments, may offer useful information to a user by transmitting pressure status information through one or more vehicle components. Non-limiting examples of information to a user may include pressure values and/or a rate of inflation/deflation during an inflation/deflation event. The messages transmitted from the TPMS system 100 may be received by a user as individual status messages or as a combination of messages.
As illustrated in block 302, sensor(s) 104a-d may determine the air mass status of one or more tires by, for example, monitoring (or sampling) the air mass. In one embodiment, monitoring the air mass may be performed at predetermined time intervals. Thus, as illustrated in block 304, a determination may be made whether the time for measuring the air mass has lapsed. For example, and without limitation, in the interim mode, air mass monitoring may occur every 2 seconds. As another non-limiting example, in the stationary mode, the air mass monitoring may occur every minute. Depending on the mode in which the sensor(s) 104a-d is operating, if the time for air mass monitoring has not lapsed, then sensor(s) 104a-d may stall an air mass measurement.
If the predetermined time has lapsed, a further determination may be made as to whether a change in the tire's air mass has occurred as illustrated in block 306. If a change has not occurred, sensor(s) 104a-d may return to monitoring the air mass status at predetermined intervals. If a mass change has occurred, the sensor(s) 104a-d may enter the RPC mode as illustrated in block 308. As described above, the air mass change may be a trigger for the RPC mode.
Sensor 104a-d may identify the change in air mass as an inflation or deflation event based on the increase or decrease in air mass, respectively. Upon entering the RPC mode, sensor 104a-d may transmit the pressure reading(s) (e.g., the PIC or PDC) to the BCM 102 as illustrated in block 310. As described above, the PIC or PDC may include the pressure value(s) of the tire(s) based on the increase or decrease in air mass, respectively. This information may be transmitted to the BCM 102 at predetermined time intervals (e.g., and without limitation, every 15-30 seconds for an increase or every 2 seconds for a decrease).
As illustrated in block 312, upon receipt of the tire inflation status signals, the BCM 102 may determine the pressure value of the inflated tire(s) based on the algorithm 106 programmed to and performed at the BCM 102. In one embodiment, the algorithm 106 may include instructions for transmitting the pressure value to the user via one or more vehicle components. Thus, one or more commands may be transmitted to the one or more vehicle components for outputting the pressure value. The message output operation is represented by circle block A in
In one embodiment, the user may receive multiple pressure status values. In this embodiment, the user may, for example, initiate an inflation event and temporarily stall the inflation event to obtain an initial pressure value status message. Thus, after adding one or more blasts of air, the user may discontinue inflation and wait for a message to be output from one or more vehicle components to determine an initial pressure value. The user may continue the inflation event (with or without inflation event pauses) to obtain one or more additional pressure values until the desired pressure value is reached as determined by the output message.
Alternatively or additionally, the user may continuously inflate the one or more tires while receiving one or more pressure value messages output from the vehicle. The user may discontinue further inflation when the desired pressure value has been reached as determined by the output message.
The frequency of the air mass sampling may depend on the monitoring mode. The sensor(s) 104a-d may determine whether to sample the air mass of one or more tires based on the lapse of a predetermined time interval, as illustrated in block 404, associated with each monitoring mode. As described above, depending on the mode in which the sensor(s) 104a-d is operating, if the time for air mass monitoring has not lapsed, then sensor(s) 104a-d may stall an air mass determination.
If the predetermined time has lapsed, a further determination may be made as to whether a change in the tire's air mass has occurred as illustrated in block 406. If a change has not occurred, sensor(s) 104a-d may return to monitoring the air mass status at predetermined time intervals. If a mass change has occurred, the sensor(s) 104a-d may enter the RPC mode as illustrated in block 408. As described above, the air mass change may be a trigger for the RPC mode. Upon entering the RPC mode, sensor 104a-d may transmit the pressure reading(s) (e.g., the PIC or PDC) to the BCM 102 as illustrated in block 410.
As illustrated in block 412, a placard pressure stored in a vehicle computing system (not shown) may also be received at the BCM 102. The placard pressure is generally a recommended tire pressure level for operating a vehicle. Accordingly, the placard pressure may be utilized by the system 100 to notify the user of the rate of inflation/deflation until the placard pressure is reached.
The placard pressure may or may not be stored in the vehicle computing system by an OEM at factory installation. In one embodiment, a user (e.g., a vehicle owner or vehicle user) may input one or more desired placard pressures depending on the condition(s) in which the vehicle is driven. As one non-limiting example, the placard pressure may be changed based on vehicle speed (e.g., and without limitation, the driver wishes to drive at high speeds). As another non-limiting example, the placard pressure may be changed based on the vehicle load (e.g., and without limitation, due to the number of passengers or the weight of equipment in the vehicle). The updated placard pressure may then be used when notifying a user of a tire pressure status during an inflation/deflation event. Further details of the notification process are described below.
As illustrated in block 414, the inflation/deflation time of the tire(s) may be measured. During an RPC event, one or more timestamps may be associated with each change in pressure that is sampled (e.g., and without limitation, every two seconds in interim mode). Sensor(s) 104a-d may calculate the rate of inflation/deflation based on a change in pressure values between sampling instances. For example, if the sensor(s) 104a-d are in a stationary mode that samples pressure every 30 seconds, and 30 seconds have lapsed since a user began the inflation event, the sensor(s) 104a-d may measure the pressure value change with respect to the placard pressure and the pressure of the tire at or around 30 seconds.
In one embodiment, the result may be output once the sampling has been made (i.e., at 30 seconds). When the user recommences inflation, the pressure value change may be measured again based on the pressure value of the last inflation event. It will be appreciated that the time values are exemplary and other values may or may not be utilized without departing from the scope of the various embodiments.
In another embodiment, transmission of the rate of inflation/deflation may be delayed. For example, if pressure status transmission occurs every 60 seconds (in an RPC mode), the sensor 104a-d may gather air mass information 2 times and calculate the rate of inflation based on the air mass changes that have occurred prior to the transmission. It will be appreciated that the time values are exemplary and other values may or may not be utilized without departing from the scope of the various embodiments.
It should be understood that the same analysis may be performed during a deflation event. Furthermore, it should be understood that inflation/deflation may occur continuously (i.e., without a pause or interruption by the user) until the desired pressure level has been reached.
The inflation/deflation data may be received by the BCM 102 as illustrated in block 416.
The information received from the sensor(s) 104a-d and transmitted to the BCM 102 may be input to the TPMS algorithm 106. The rate of inflation may be determined as illustrated in block 418. The rate of inflation may be measured in units of time (e.g., and without limitation, seconds). As illustrated in block 420, from the rate of inflation, the time until the placard pressure is reached (for example) is determined.
In one embodiment, the algorithm 106 may include instructions for transmitting the rate of inflation and/or time status to the user via one or more vehicle components. Thus, one or more commands may be transmitted to the one or more vehicle components for outputting the rate of inflation. The message output operation is represented by circle block A in
The decision to output a status message from the vehicle computing system or another component may be based on a user preference stored at the vehicle computing system. The user may input this preference from the vehicle computing system and/or from a website. If the preferences are input from a website, the information may be transmitted to the vehicle over any wireless network (e.g., and without limitation, WiFi, WiMax or cellular). A non-limiting example of such a website is www.syncmyride.com.
If the status message(s) are transmitted through the vehicle computing system, the BCM 102 may transmit a command signal to the vehicle computing network 122, as illustrated in block 502, for transmission to the vehicle computing system. The vehicle computing system may receive the command as illustrated in block 504. The vehicle computing system may then output the status message(s) from one or more vehicle speakers as illustrated in block 506.
The status message(s) may be output as audible messages. Non-limiting example of audible messages include tones, beeps, speech, or combinations thereof. For example, if a tire pressure value is at 32 psi, a message output as a tone or beep may be heard as “beep-beep-beep (pause) beep-beep.” Alternatively or additionally, the vehicle computing system may output “32 psi” in a spoken language. It should be understood that the vehicle computing system may output the status message in any language.
As another non-limiting example, if the inflation time status is determined to be 5 seconds, one output may be “beep-beep-beep-beep-beep.” Another non-limiting output may be “5 seconds” output in a spoken language from the voice computing system.
If the status message(s) are not transmitted through the vehicle computing system and/or audio system, the status message(s) may be transmitted through other vehicle components (e.g., and without limitation, the vehicle horn or the vehicle lights). In this instance, the BCM 102 may transmit one or more commands to the vehicle horn and/or vehicle light(s) as illustrated in block 508. The status message(s) may be output from the vehicle horn and/or light(s) as illustrated in block 510.
Using the examples above to illustrate this embodiment, if the placard pressure is 32 psi, the vehicle horn may output “beep-beep-beep (pause) beep-beep.” If there are 5 seconds left until the placard pressure is reached, the horn may beep 5 times. Alternatively or additionally, the interior or exterior lights may flash as follows to represent 32 psi: flash 3 times, pause, flash 2 times. To represent that 5 seconds are left until the placard pressure is reached, the lights may flash 5 times.
As illustrated in block 600, sensor 104a-d may determine a pressure status. The pressure status that is used may be determined based on the commencement of the inflation/deflation event as illustrated in block 602.
If the sensor(s) 104a-d are determining the tire pressure status for the first time in the tire inflation/deflation session, the sensor(s) 104a-d may used the placard pressure for determining a pressure value change as illustrated in block 604. A determination may be made whether the placard pressure has been input by a user as illustrated in block 606.
If not, a default may be used (e.g., as input by the OEM) as illustrated in block 608. If a placard pressure has been received from a user, the user input placard pressure may be utilized as illustrated in block 610.
If the tire pressure status is not being determined for the first time, the sensor(s) 104a-d may use the pressure value from the last pressure reading to determine the pressure value change as illustrated in block 612. If a change in pressure value has occurred, the sensor(s) 104a-d may update the pressure reading as illustrated in block 614.
As illustrated in block 616, the updated pressure reading or the placard pressure may be transmitted in pressure field 204 (
While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.
This application is a continuation of U.S. application Ser. No. 12/712,669, filed Feb. 25, 2010, the disclosure of which is incorporated in its entirety by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
4797671 | Toal, Jr. | Jan 1989 | A |
4804937 | Barbiaux et al. | Feb 1989 | A |
5355511 | Hatano et al. | Oct 1994 | A |
5432841 | Rimer | Jul 1995 | A |
5633484 | Zancho et al. | May 1997 | A |
5654686 | Geschke et al. | Aug 1997 | A |
5732074 | Spaur et al. | Mar 1998 | A |
5758300 | Abe | May 1998 | A |
5889468 | Banga | Mar 1999 | A |
5942979 | Luppino | Aug 1999 | A |
5943206 | Crayford | Aug 1999 | A |
5963129 | Warner | Oct 1999 | A |
5986543 | Johnson | Nov 1999 | A |
5993397 | Branson | Nov 1999 | A |
6025777 | Fuller et al. | Feb 2000 | A |
6037676 | Foree | Mar 2000 | A |
6067009 | Hozuka et al. | May 2000 | A |
6104931 | Havinis et al. | Aug 2000 | A |
6292095 | Fuller et al. | Sep 2001 | B1 |
6295449 | Westerlage et al. | Sep 2001 | B1 |
6339736 | Moskowitz et al. | Jan 2002 | B1 |
6343220 | Van Der Salm | Jan 2002 | B1 |
6370472 | Fosseen | Apr 2002 | B1 |
6377890 | Doi | Apr 2002 | B1 |
6415210 | Hozuka et al. | Jul 2002 | B2 |
6429773 | Schuyler | Aug 2002 | B1 |
6435018 | Murakami et al. | Aug 2002 | B1 |
6441732 | Laitsaari et al. | Aug 2002 | B1 |
6470732 | Breton | Oct 2002 | B1 |
6487478 | Azzaro et al. | Nov 2002 | B1 |
6525643 | Okada et al. | Feb 2003 | B1 |
6571617 | Van Niekerk et al. | Jun 2003 | B2 |
6587040 | Seto | Jul 2003 | B2 |
6611740 | Lowrey et al. | Aug 2003 | B2 |
6612165 | Juzswik et al. | Sep 2003 | B2 |
6629031 | Gustavsson et al. | Sep 2003 | B2 |
6671609 | Nantz et al. | Dec 2003 | B2 |
6691025 | Reimer | Feb 2004 | B2 |
6732031 | Lightner et al. | May 2004 | B1 |
6738697 | Breed | May 2004 | B2 |
6825758 | Laitsaari | Nov 2004 | B1 |
6832708 | Sinai | Dec 2004 | B2 |
6839614 | Timko et al. | Jan 2005 | B1 |
6845314 | Fosseen | Jan 2005 | B2 |
6847872 | Bodin et al. | Jan 2005 | B2 |
6853853 | Van Wiemeersch et al. | Feb 2005 | B1 |
6868358 | Brown, Jr. | Mar 2005 | B2 |
6892052 | Kotola et al. | May 2005 | B2 |
6930614 | Rackham et al. | Aug 2005 | B2 |
6937141 | Muramatsu | Aug 2005 | B2 |
6943669 | Otterbach et al. | Sep 2005 | B2 |
6983200 | Bodin et al. | Jan 2006 | B2 |
6993421 | Pillar et al. | Jan 2006 | B2 |
7039508 | Lin et al. | May 2006 | B2 |
7040154 | Shaw et al. | May 2006 | B2 |
7053761 | Schofield et al. | May 2006 | B2 |
7068158 | Komatsu et al. | Jun 2006 | B2 |
7092804 | McQuade et al. | Aug 2006 | B2 |
7096101 | Sonnenrein et al. | Aug 2006 | B2 |
7114379 | Emord | Oct 2006 | B2 |
7170400 | Cowelchuk et al. | Jan 2007 | B2 |
7171188 | Watanabe et al. | Jan 2007 | B1 |
7216532 | Rimkus et al. | May 2007 | B2 |
7218208 | Kikuchi | May 2007 | B2 |
7218209 | Utter et al. | May 2007 | B2 |
7219063 | Schalk et al. | May 2007 | B2 |
7224262 | Simon et al. | May 2007 | B2 |
7228122 | Oyagi et al. | Jun 2007 | B2 |
7319378 | Thompson et al. | Jan 2008 | B1 |
7379541 | Iggulden et al. | May 2008 | B2 |
7394352 | Bell et al. | Jul 2008 | B2 |
7509849 | Rutherford et al. | Mar 2009 | B2 |
7778186 | Oman et al. | Aug 2010 | B2 |
7783246 | Twitchell, Jr. et al. | Aug 2010 | B2 |
7849149 | Habaguchi et al. | Dec 2010 | B2 |
7859392 | McClellan et al. | Dec 2010 | B2 |
8061879 | Simmons et al. | Nov 2011 | B2 |
8089348 | Kameyama | Jan 2012 | B2 |
8120475 | Iwamoto et al. | Feb 2012 | B2 |
8325028 | Schofield et al. | Dec 2012 | B2 |
20010033225 | Razavi et al. | Oct 2001 | A1 |
20020130771 | Osborne et al. | Sep 2002 | A1 |
20030004741 | Johnson et al. | Jan 2003 | A1 |
20030016130 | Joao | Jan 2003 | A1 |
20030093218 | Jones | May 2003 | A1 |
20030145650 | Juzswik et al. | Aug 2003 | A1 |
20030158640 | Pillar et al. | Aug 2003 | A1 |
20030205081 | Proschka | Nov 2003 | A1 |
20030208309 | Triphathi | Nov 2003 | A1 |
20040050188 | Richards et al. | Mar 2004 | A1 |
20040075539 | Savoie et al. | Apr 2004 | A1 |
20040112124 | Sonnenrein et al. | Jun 2004 | A1 |
20040193368 | Sanqunetti | Sep 2004 | A1 |
20040203634 | Wang et al. | Oct 2004 | A1 |
20050024189 | Weber | Feb 2005 | A1 |
20050137763 | Watkins et al. | Jun 2005 | A1 |
20050179518 | Kawamura et al. | Aug 2005 | A1 |
20050190900 | White et al. | Sep 2005 | A1 |
20050195106 | Davis et al. | Sep 2005 | A1 |
20050242936 | Watabe | Nov 2005 | A1 |
20050273218 | Breed et al. | Dec 2005 | A1 |
20060095174 | Sonnenrein et al. | May 2006 | A1 |
20060208865 | Quach et al. | Sep 2006 | A1 |
20060220806 | Nguyen | Oct 2006 | A1 |
20060220809 | Stigall et al. | Oct 2006 | A1 |
20060220813 | Utter et al. | Oct 2006 | A1 |
20060220814 | Kawashima | Oct 2006 | A1 |
20060232391 | Nakatani et al. | Oct 2006 | A1 |
20060235652 | Rimkus et al. | Oct 2006 | A1 |
20060250227 | Naito | Nov 2006 | A1 |
20060273885 | Thompson | Dec 2006 | A1 |
20060288101 | Mastrodonato et al. | Dec 2006 | A1 |
20070015548 | Flick | Jan 2007 | A1 |
20070027595 | Nou | Feb 2007 | A1 |
20070060056 | Whitaker et al. | Mar 2007 | A1 |
20070069951 | Sweet | Mar 2007 | A1 |
20070155300 | Hsieh | Jul 2007 | A1 |
20070156317 | Breed | Jul 2007 | A1 |
20070193348 | Rutherford et al. | Aug 2007 | A1 |
20070200671 | Kelley et al. | Aug 2007 | A1 |
20070229350 | Scalisi et al. | Oct 2007 | A1 |
20070290881 | Nikitin et al. | Dec 2007 | A1 |
20080024285 | Vandenbrink et al. | Jan 2008 | A1 |
20080046149 | Breed | Feb 2008 | A1 |
20080077292 | Gisler | Mar 2008 | A1 |
20080082221 | Nagy | Apr 2008 | A1 |
20080106859 | Eguchi et al. | May 2008 | A1 |
20080125665 | Nigam | May 2008 | A1 |
20080136611 | Benco et al. | Jun 2008 | A1 |
20080140265 | Hong et al. | Jun 2008 | A1 |
20080147265 | Breed | Jun 2008 | A1 |
20080147271 | Breed | Jun 2008 | A1 |
20080172147 | Taki et al. | Jul 2008 | A1 |
20080197970 | Fouts | Aug 2008 | A1 |
20080204556 | de Miranda et al. | Aug 2008 | A1 |
20080215665 | Appleby et al. | Sep 2008 | A1 |
20080228355 | de Jonk et al. | Sep 2008 | A1 |
20080266051 | Taki et al. | Oct 2008 | A1 |
20080299961 | Muller et al. | Dec 2008 | A1 |
20080309451 | Zellweger et al. | Dec 2008 | A1 |
20090075624 | Cox et al. | Mar 2009 | A1 |
20090091437 | Corniot | Apr 2009 | A1 |
20090096575 | Tieman | Apr 2009 | A1 |
20090096576 | Oman et al. | Apr 2009 | A1 |
20090096596 | Sultan et al. | Apr 2009 | A1 |
20090098907 | Huntzicker et al. | Apr 2009 | A1 |
20090102633 | Ebinuma et al. | Apr 2009 | A1 |
20090167524 | Chesnutt et al. | Jul 2009 | A1 |
20090273438 | Sultan et al. | Nov 2009 | A1 |
20100145759 | Hembury | Jun 2010 | A1 |
20100168967 | Dlugoss et al. | Jul 2010 | A1 |
20100233957 | Dobosz | Sep 2010 | A1 |
20110015971 | Hembury | Jan 2011 | A1 |
20110029875 | Milch | Feb 2011 | A1 |
20110071720 | Schondorf et al. | Mar 2011 | A1 |
20110071725 | Kleve et al. | Mar 2011 | A1 |
20110071734 | Van Wiemeersch et al. | Mar 2011 | A1 |
20110080282 | Kleve et al. | Apr 2011 | A1 |
20110130945 | Deedy et al. | Jun 2011 | A1 |
20110205040 | Van Wiemeersch et al. | Aug 2011 | A1 |
20110205047 | Patel et al. | Aug 2011 | A1 |
20110215901 | Van Wiemeersch et al. | Sep 2011 | A1 |
20110230165 | Kleve et al. | Sep 2011 | A1 |
Number | Date | Country |
---|---|---|
1646337 | Jul 2005 | CN |
1942749 | Apr 2007 | CN |
1609629 | Dec 2005 | EP |
2006075533 | Jul 2006 | WO |
Entry |
---|
Chinese Patent Office, First Office Action for the corresponding Chinese Patent Application No. 201110039418.X mailed May 27, 2014. |
Office Action mailed Nov. 6, 2014 from the Chinese Patent Office for Application No. 201110039418.X. |
Chinese Patent Office, Office Action for the corresponding Chinese patent application No. 201110039418.X mailed Feb. 13, 2015. |
Number | Date | Country | |
---|---|---|---|
20130311033 A1 | Nov 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12712669 | Feb 2010 | US |
Child | 13947533 | US |