Tire pressure monitor system apparatus and method

Information

  • Patent Grant
  • 9676238
  • Patent Number
    9,676,238
  • Date Filed
    Friday, November 6, 2015
    8 years ago
  • Date Issued
    Tuesday, June 13, 2017
    6 years ago
Abstract
A first signal transmission is received from a transmitter external to the monitor, the first signal having a transmission characteristic. Based upon the transmission characteristic of the first signal transmission and not any data in the first transmission, a corresponding at least one protocol is determined. A data resolution based upon the transmission characteristic is determined. A second data transmission is formed according to the corresponding at least one protocol, and the sensed data is inserted into the second data transmission according to the resolution. The second data transmission is transmitted.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This patent claims benefit under 35 U.S.C. 119(e) to U.S. Provisional Application No. 62/200,528 entitled “Apparatus, System and Method for Configuring Tire Information Sensor with a Transmission Protocol Based on Vehicle Trigger Characteristics” filed Aug. 3, 2015. This patent is also a continuation-in-part of application Ser. No. 14/190,905 (which issued as U.S. Pat. No. 9,193,222) filed Feb. 26, 2014 entitled “Apparatus and Method for Cloning Tire Pressure Monitor System Information.” This patent is also a continuation-in-part of application Ser. No. 14/524,836 (which issued as U.S. Pat. No. 9,259,980) entitled “Apparatus and Method for Data Transmissions in a Tire Pressure Monitor,” and filed Oct. 27, 2014, which is a continuation of U.S. Pat. No. 9,024,743 entitled “Apparatus and Method For Activating a Localization Process For A Tire Pressure Monitor” and filed Aug. 9, 2011, the contents of all of which are incorporated herein by reference in their entireties.


TECHNICAL FIELD

This application relates to tire pressure monitors system (TPMS) sensors, and transmissions made from these sensors.


BACKGROUND OF THE INVENTION

Tire pressuring monitoring (TPM) devices are used in today's vehicles. A tire pressure sensor senses the tire pressure reading (or other conditions, such as the temperature of the tire). These sensed readings may be communicated to a TPM receiver that is disposed in the vehicle. A display screen may also be coupled to the receiver. When the tire pressure reading falls below a particular threshold, the driver of the vehicle may be alerted, for example, by an alert message being displayed to the driver on the screen. The driver can then take any required action.


The transmissions made from the TPM sensor (transmitter) to the TPM receiver (e.g., in the vehicle) are made according to various types of formats. For instance, different automobile manufacturers use different formats. The formats relate to the positioning of data, the number of bits, the meaning of the bits, the transmission rate, the baud rate, and error-handling approaches, to mention a few examples.


In some approaches, each TPM sensor needs to be manually and individually programmed with the desired transmission format or protocol. Current approaches for programming the individual TPM sensors typically involve the use of a hand-held programming device. An operator manually programs the TPM sensor with the selected protocol or format according to the desired automobile manufacturer. Unfortunately, the manual programming approach is error prone, time-consuming, and inefficient.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosure, reference should be made to the following detailed description and accompanying drawings wherein:



FIG. 1 comprises a block diagram of a system for cloning TPMS information according to various embodiments of the present invention;



FIG. 2 comprises a flow chart of one approach for cloning TPMS information according to various embodiments of the present invention;



FIG. 3 comprises a block diagram of an apparatus for TPMS cloning according to various embodiments of the present invention;



FIG. 4 comprises a graph showing various resolution curves used in determining the resolution of cloned data according to various embodiments of the present invention;



FIG. 5 comprises a block diagram of an apparatus for TPMS cloning according to various embodiments of the present invention;



FIG. 6 comprises a block diagram of an apparatus configured to make TPMS transmissions according to various embodiments of the present invention;



FIG. 7 comprises a flow chart of an approach for making TPMS transmissions according to various embodiments of the present invention;



FIG. 8 comprises a flow chart of an approach for making TPMS transmissions according to various embodiments of the present invention;



FIG. 9 comprises a diagram of one example of a set of transmissions that can be made from the TPM sensors described herein according to various embodiments of the present invention.





Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein.


DETAILED DESCRIPTION

Approaches are provided where a first tire pressure monitoring system (TPMS) wheel unit (or programming tool) is configured to receive a “shell unit” transmission from a second wheel unit. The entire transmission (or selected parts of the transmission) are stored, for example, in a memory at the first wheel unit (or the tool). For instance, the decoded data or the entire physical layer transmission such as the entire burst) may be stored. The unit (or tool) identifies the data in the transmission that changes over time (such as the pressure and temperature information to mention a few examples). Alternatively, based upon the transmission characteristic of the first signal transmission, determining a corresponding at least one protocol. The wheel unit (or tool) overwrites the updated information (e.g., tire pressure data associated with the tire of the first wheel unit) into the identified location. Consequently, only the information that changes is modified while static, unchanging information remains unmodified. The modified transmission can then be made from the second wheel unit (or the tool).


In some aspects, the present approaches provide a “record and play” technique to clone a TPMS wheel unit so that no specific protocol or code needs to be utilized or programmed. Since the entire transmission is recorded and played back, all the portions of the data format that do not change are automatically produced while only data that changes is dropped and new data is inserted in the place of the changing data. This greatly simplifies development, especially software development of the TPMS monitor. For example, rather than develop software to build the data format in real time during normal operation, the entire format is simply stored in memory with only substituting the requisite data such as pressure, temperature, battery voltage or other suitable data. As a result, the complexity of software is greatly reduced, and memory such as ROM and any RAM is significantly reduced, thus reducing both labor and material/hardware costs.


In other aspects, TPMS cloning without a scan tool is also accomplished. As a result, users do not need to purchase or utilize scan tools. Another advantage is that the TPMS monitor does not need an HF receiver since the LF receiver is already in the sensor to receive LF signals during for example learn mode. Thus, no additional hardware such as an HF receiver is required. Further, since the TPMS monitor may determine a particular protocol, or a group of protocols out of several protocols, the wheel unit may configure the data transmissions to communicate with several different manufacturers protocols. For example, multi-application/multi-protocol sensors may be aftermarket sensors that are pre-programmed or configured with a variety of vehicle protocols/software. A single protocol sensor may transmit according to a single protocol that typically includes a burst sequence of one, two three or more frame types. A multiprotocol sensor may have a multiprotocol burst sequence of different bursts. Each of the different bursts may have frames from different manufacturers. The different multiprotocol bursts may be different from the bursts of the manufacturer. Since the receivers process only those frames according to the preprogrammed protocol, the receiver rejects the frames from other manufacturer protocols and thus receives the correct frames intended for the receiver according to the manufacturer protocol. Thus the multiprotocol sensor will have a new type of transmission that is a multiprotocol burst sequence. Among other advantages, the TPMS monitor simply may have the entire data format such as the multiprotocol burst sequence either stored in memory initially during manufacture, or during the learn mode of operation with the vehicle. For example, the sensor may contain several different multiprotocol burst sequences (MTBS) that correspond to groups of automotive vehicle platforms. Thus the sensor may receive an LF a first data transmission according to a manufacturer's protocol, determine which set of MTBS corresponds to that first data transmission and then transmit a second data transmission according to a second multiprotocol burst sequence. In another embodiment, a first data transmission and a second data transmission from a TPMS monitor are received. The first data transmission and the second data transmission are stored in a memory. The first data transmission and the second data transmission are compared and at least one changing portion of the data transmission is identified based upon the comparison. Sensed data is received from a tire pressure sensor. A data resolution is determined and a third data transmission is formed. The changing portion is replaced with the sensed data in the third data transmission according to the resolution. The third data transmission is transmitted including the sensed data with the proper resolution.


In some aspects, a resolution associated with a particular automobile manufacture is determined and the changing portion with the new data according to this resolution. In some examples, the sensed data is tire pressure information. In other examples, the sensed data is tire temperature information. Other types of data can also be written into the changing portion of the transmission.


In some other aspects, the resolution is determined utilizing a plurality of graphs stored in a memory. In other aspects, the plurality of graphs are linear graphs.


In others of these embodiments, an apparatus for cloning tire pressure information includes an interface, a memory and a controller. The interface has an input and an output and the input is configured to receive a first data transmission and a second data transmission from a TPMS monitor.


The controller is coupled to the memory and the interface. The controller is configured to store the first data transmission and the second data transmission in the memory. The controller is configured to compare the first data transmission and the second data transmission, and identify at least one changing portion of the data transmission based upon the comparison. The controller is also configured to receive sensed data from a tire pressure sensor at the input, and to determine a data resolution, and to form a third data transmission. The controller is configured to replace the at least one changing portion of the third data transmission with the sensed data according to the resolution. The controller is configured to transmit the third data transmission including the sensed data with the proper resolution at the output of the interface.


Referring now to FIG. 1, one example of a TPMS system 100 is described. The TPMS system resides in a vehicle 102. The system includes a first TPMS monitor (or sensor or unit or wheel unit) 104, a second TPMS monitor 106, a third TPMS monitor 108, and a fourth TPMS monitor 110. The monitors 104, 106, 108, and 110 communicate with a receiver 112. The communication between the TPMS monitors 104, 106, 108, and 110 and the receiver 112 is accomplished in one aspect via wireless, radio frequency (RF) links.


The TPMS monitors 104, 106, 108, and 110 may include processing devices and memories and execute computer instructions to sense and transmit tire pressure (or other) data. In these regards, the TPMS monitors 104, 106, 108, and 110 may themselves include structures, devices, or apparatus that actually sense the pressure (or other types of data) in the tire.


The receiver 112 includes hardware and/or software to receive (and in some examples transmit) information from the TPMS monitors 104, 106, 108, and 110. The receiver 112 is disposed at an appropriate location within the vehicle 102.


When the value of the sensed data communicated from one of the sensors 104, 106, 108 and 110 falls below a predetermined threshold (e.g., below a predetermined pressure value), this data is received at the receiver 112, and a determination is made at the receiver 112 to alert the driver/or other occupant of vehicle 102. The alert may be made via a screen coupled to the receiver 112. Other types of alerts (e.g., audio alerts) may also be issued. Although the approaches described herein are described as being implemented at a wheel unit, it will be appreciated that the approaches may also be implemented at a hand held scanning tool or other similar device.


In one aspect, the location of the pressure information in the data stream transmitted by one wheel unit may be identified at another wheel unit (e.g., by looking for changes in the data stream). Then, the required resolution of the data is determined because, for example, the resolution changes between automobile manufacturers, manufacturer protocols and/or wheel units. Consequently, a pressure resolution linear extrapolation may be determined and the data stream updated with measurements according to the appropriate resolution.


In another aspect, a data stream (e.g., a series of bursts) is transmitted from one wheel unit 104, 106, 108, or 110 (“the originating wheel unit”) and this data burst is to be copied or cloned, RX entire transmission, change pressure at another of the wheel units 104, 106, 108, and 110 (“the cloning wheel unit”). The pressure changes over time as the originating wheel unit 104, 106, 108, or 110 transmits (over a burst), and the originating wheel unit receives successive measurements. The cloning wheel unit receives the transmission and looks for changes in the data stream to identify pressure information/data. The changing portions of the data stream may correspond to pressure and different pressures in one example.


By “cloning” and as used herein, it is meant that a transmission from a first wheel unit is copied at another second wheel unit. The copied transmission is the same as the first transmission except that new data is inserted into the copied transmission in portions of the transmission that have been identified as changing (over time). According to one embodiment, the data format may be transmitted directly from memory rather than build the data format through routines such as loops as is known in software programming.


In still another aspect, the wheel unit 104, 106, 108, or 110 may be placed into pressure chamber and the pressure changed. Transmissions may be received at this wheel unit 104, 106, 108, or 110 and changes determined in the data stream. The changing portions of the data stream may correspond to pressure and different pressures.


In yet another aspect, transmissions are received from different wheel units 104, 106, 108, or 110, for example, the two to four units from a car coming in for wheel unit replacement.


In still another aspect, transmissions are received from wheel units 104, 106, 108, 110 while mounted on tire and wheel under pressure, and then when unmounted. This approach gives one to four measurements under pressure from four wheel units (slightly different) and another four at atmospheric pressure thereby eliminating the need for using a pressure chamber. According to another aspect, a user or technician may take out some pressure from 1 to 4 tires (e.g., from approximately 30 psi to 20-25 psi, and record transmissions at 1, 2, 3, 4 or more different pressure levels). Also, the user or technician may increase pressure from in one example 30 psi to 40-45 psi and also record the corresponding transmissions and pressure readings.


In yet another aspect (since the pressure and temperature resolution and range of data is different for a limited number of protocols), and based on one measurement such as pressure, the measurement can fit one of a limited number of curve fits or resolutions. With one or more pressure measurements the wheel unit can determine which curve or resolution is a best fit and the wheel unit can then select the correct resolution. Thus, all pressure measurements can be computed with the correct resolution and then drop/inserted into the transmission bit stream. For example, the different resolutions and data ranges can correspond to the different protocols or groups of protocols covered with the wheel unit. As such, then the wheel unit can support multiple protocols. For example a particular resolution may identify a group of related protocols that have the same or similar resolution types or settings. Thus, the transmission may be a single protocol or a group of protocols.


Referring now to FIG. 2, one example of how one wheel unit clones the transmission received from another wheel unit is described. At step 202, a first data transmission from a first wheel unit is received at a second wheel unit at (i.e., the cloning wheel unit that will be performing the cloning operation). At step 204, the first data transmission is stored at the second wheel unit. In one aspect, the data transmission is a burst of information that includes a plurality of frames, bytes, or bits to mention a few examples of the transmission units that may be included in the burst. Other examples are possible.


At step 206, a second data transmission from the first wheel unit is received at the second wheel unit. At step 208, the first data transmission is stored at the second wheel unit. As with the first transmission, the second data transmission is a burst of information that includes a plurality of frames. The burst itself may include several sub-sections with each sub-section relating to data in a format that is associated with a particular automobile manufacturer.


At step 210, the second wheel unit identifies one or more portions of the data transmission that change over time. This is accomplished by examining and comparing the received first and second transmissions (the burst) from the originating wheel unit and identifying which portion or portions (e.g., which bits, bytes, frames, or other type of data unit) changes.


At step 212, a resolution for new data is determined. The resolution may be determined by comparing the received data (for a known pressure) to various curves and determining which curve gives the best fit. At step 214, new data is inserted into the one or more portions of the transmission that change over time and this new data has the proper resolution. In one aspect, each automobile has a unique data resolution that is determined.


Referring now to FIG. 3, one example of an apparatus 300 for cloning TPMS transmissions in a TPMS system is described. The apparatus 300 includes a comparator 302, a resolution determination module 304, a memory 306, a transmitter 308, and a sensor 310. The various elements and modules described in FIG. 3 can be implemented in hardware, software, or combinations of hardware and software.


The comparator 302 receives a first data transmission 312 and a second data transmission 314. The transmissions 312 and 314 may be, in one aspects, bursts of information. In this respect, the transmissions 312 and 314 may include transmissions made according to multiple formats. Alternatively, the transmissions 312 and 314 may include transmissions made according to a single format.


The comparator 302 compares the two transmissions 312 and 314 and based upon the comparison determines which portions 316 of the transmission change. The changing portions 316 identify where pressure (or other type of sensed) data 318 will be inserted in a third transmission 320 that will eventually be transmitted from the transmitter 308. The third transmission 320 has the same format as the transmission 312 and 314. The difference between the original transmissions 312 and 314 is that the new pressure data 318 is inserted in the changing portion 316 of the transmission 320. The remaining portions (330 and 332) of the transmissions 320 are identical to the remaining portions (330 and 332) of transmissions 312 and 314.


Forming the third transmission may involve various types of operations and approaches and may be accomplished in different ways. In one approach, the forming merely takes any transmission originating from an originating wheel unit (including the first transmission 312 or second transmission 314 or any future transmission), stores the transmission in memory (briefly, for a longer period of time, or permanently), and overwrites the changing portion with sensed data. In other examples, nothing is stored for a significant amount of time except the location of the changing portion. As new transmissions are received, they are simply re-transmitted as received except the changing portion is overwritten with newly sensed data from the cloning wheel unit.


In one aspect, before the pressure data 318 is inserted into the transmission 320, it is done so according to a required or needed resolution. In this respect, the resolution determination module 304 obtains from memory 306 information 322 in order to determine the correct resolution. This process is described in greater detail below with respect to FIG. 4. In the example of FIG. 4, the pressure data is determined for a particular pressure (e.g., 30 psi) and then the graphs are examined to see (for the given pressure) which curve is the best fit. Once the best fit is determined, then the resolution has also been determined. The data 324 actually inserted into the transmission 320 has the correct resolution. As mentioned, the rest of the data in the transmission 320 is the same and is replicated from the transmissions 312 and/or 314.


Referring now to FIG. 4, one example of pressure resolution extrapolation is described. Generally speaking, a determination is first made of curves that represent the data resolution of different manufacturers. For example, 0 psi may map to hex AAAA for one manufacturer or hex 0000 for another manufacturer. In other examples, 100 psi may map to hex FFFF for the first manufacturer and AAAA for the second manufacturer. As will be appreciated, the resolution mapping between actual measurements and transmitted data is typically different for different manufacturers. This mapping must be determined or the receiver (which is expecting to receive data with a certain resolution) will not be able to recognize the transmission or will decode the data with the improper resolution (thus determining an improper value for the data).


As shown in FIG. 4, a first manufacturer has a first curve 402. A second manufacturer has a second curve 404. A third manufacturer has a third curve 406. In this example, the curves are linear and have associated with them an equation y−mx+b, where m is the slope (of a particular line) and b is the y intercept (of that line). However, it will be appreciated that the curves do not have to be linear and can be of any shape and be described by any type of equation or equations. In the graphs of FIG. 4, the x-axis represents pressure readings and the y-axis represents data values (e.g., in hex form).


In one aspect, each curve 402, 404, or 406 is determined by testing. For instance and in a test chamber, two or more data points are received. Based on pressure readings, readings for different pressure measurements and the corresponding pressure measurement, could be linear or non-linear. A slope (m) can be determined by two pressure readings as can the y-intercept. From this information, the equation y=mx+b is determined. This algorithm may be implemented in an application specific integrated circuit (ASIC) in one approach.


After the exact curve is determined (e.g., the equation describing the curve), the resolution of the pressure information that is being automatically determined. At any given pressure (e.g., 30 psi), a unique value (e.g., representing tire pressure) is transmitted by a sensing apparatus (e.g., a pressure sensing device) of a first manufacturer, another unique number by a second manufacturer, and still another unique number by a third manufacturer. So, for example, 29-31 psi may be transmitted as a hex 49 plus/minus tolerance hex for the first manufacturer, hex 29-31 for the second manufacturer, and hex 19-21 for the third manufacturer. If the actual sensed reading for 20 psi is hex 30, a comparison is made to see on which graph 402, 404, or 406 the data falls. In this case, it can be seen that this falls on point 408 on curve 404. Now, the wheel unit knows the proper resolution (the resolution associated with the curve 404) to use and the present data as well as all future data can be mapped according to the proper resolution.


Referring now to FIG. 5, an apparatus 500 for cloning tire pressure information includes an interface 502, a memory 504 and a controller 506. The interface 502 has an input 508 and an output 510 and the input 508 is configured to receive a first data transmission 512 and a second data transmission 514 from a TPMS monitor 516. The apparatus 500 may be implemented as any combination of hardware and software elements. The apparatus 500 may be disposed at a wheel unit or as a programming device used by a technician. Other placements are possible.


The controller 506 is coupled to the memory 504 and the interface 502. The controller 506 is configured to store the first data transmission 512 and the second data transmission 514 in the memory 504. The controller 506 is configured to compare the first data transmission 512 and the second data transmission 514, and identify at least one changing portion 518 of the data transmissions 512 and 514 based upon the comparison. The controller 506 is furthered configured to receive sensed data 522 from a tire pressure sensor 520 at the input 508, to determine a data resolution, and replace the at least one changing portion 518 with the sensed data 522 according to the resolution. The controller 506 is configured to transmit a third data transmission 524 including the sensed data 522 in the changing portion 518 at the output 510 of the interface 502.


Referring now to FIG. 6, an apparatus 600 (a TPMS sensor or monitor) includes a receiver 601, a determine template and resolution module 602, a memory 604 (including a first template 606, and a second template 608), a sensor 610, and a transmitter 612. The apparatus 600 may be a tire pressure monitoring (TPM) device that measures the pressure (or other attributes) of a tire 614. A portable electronic tool 616 (which in one example is a hand held device that is movable between different tires of a vehicle and between different vehicles) transmits a signal 618 to the apparatus 600. In one example, the signal 618 is an LF signal with no affirmative, embedded, or transmitted data or information that would inform or instruct the apparatus to perform any function.


It will be appreciated that any transmitter that produces the signal 618 may replace the tool 616. In these regards, a fixed transmitter (of any type) may be substituted for the portable tool 616.


The receiver 601 is any type of receiver that can receive a wide variety of signals. The determine template and resolution determination module 602 receives the signal 618. Based upon a transmission characteristic (e.g., frequency, modulation type) of the signal 618. For example, the resolution determination and protocol determination may be made by the type of modulation such as CW, PWM, FSK, ASK, PSK, raised cosine or any suitable type of modulation. According to one aspect, the resolution may be determined based on received data. For example, as shown in FIG. 4 the pressure data received 408 is within manufacturer B's resolution range. Since data 408, such as pressure does not overlap with manufacturer C or A's ranges, then the sensor may infer that the sensor is transmitting according to manufacturer B. According to another aspect, the resolution determination is not based upon any data (e.g., identification information) if any in the signal, a determination can be made by the determine template and resolution determination module 602 that the signal 618 relates to a protocol or set of protocols that in turn may be associated with one or more manufacturers, group of manufacturers, model of vehicle, vehicle platform(s), or some other vehicle category. For example, modulation such as ASK, FSK, pulse width modulation and other physical signal characteristics may be used to identify a manufacturer or a group of manufacturers. In other words, while transmission characteristics of the signal 618 identify a particular protocol (or set of different protocols) such identification is not made by information within or carried by the signal 618 or analyzing information within or carried by the signal 618.


As mentioned, the each template relates to, is defined by, and/or is constructed according to a protocol or a set of protocols. By “protocol” and as used herein it is meant rules that describe how to effectuate the transfer of data between devices. The protocol may include data formats, modulation schemes, or transmission frequencies to mention a few examples. Each manufacturer may have a unique protocol or common protocols may be used between different manufacturers. Thus, a protocol or set of protocols may be associated with one or more manufacturers.


As mentioned, one type of information that can be determined is modulation type and the modulation type relates to a particular manufacturer or vehicle type. Some examples of modulation or transmission types include continuous wave (CW) transmissions, continuous wave data (CWdata) pulse width modulation, continuous wave amplitude shift keying (CW_ASK) modulation, continuous wave frequency shift keying (CW_FSK) modulation. Other examples are possible. In one aspect, the determine template and resolution determination module 602, determines the modulation type. This can be performed by a combinations of software and hardware actions. For example, if a CW_FSK signal is transmitted and the receiver is looking for a CW_ASK signal, the output of the receiver would be a high level for the duration of the transmitted signal. Such a signature would indicate that a CW_ASK signal is being transmitted. Additionally, RF receivers may output both ASK and FSK data on two distinct pins. The modulation type would then be known based on the pin that the data was output on.


The determine template and resolution determination module 602 is configured to, once the transmission parameter is identified, map this to a predetermined transmission template 606 or 608. The modulation type is also mapped to a particular resolution by a similar mapping. In one example, mapping or look-up tables may be used for these operations. Other approaches may also be used. As mentioned, the templates may be associated with one or more protocols.


The sensor 612 is any measurement device that measures the pressure or other information (e.g., temperature) of the tire 614. The transmitter 610 is any transmission device that transmits information. The memory 604 is any type of memory device.


As mentioned and in one aspect, the templates 606 and 608 specify one or more data formats, modulation types, transmission frequencies, or any other formatting or transmission protocol specified by a manufacturer, group of manufactures, or relating to a specific vehicle model, or type. For example, template 608 may relate to a template for a first manufacturer and template 610 may relate to a second and different manufacturer. The templates 606 and 608 may be stored in memory 604 at the time of manufacturing or may be changed on the fly during operation of the vehicle.


To take one example, one template 606 or 608 may include a burst of information that is defined by two or more protocols. For example, the template 606 or 608 may include frames of information to be transmitted according to a first protocol associated with a first automobile manufacturer and other frames transmitted according to a second protocol associated with a second automobile manufacturer. The other template 606 or 608 may also include a burst of information that is defined by two or more protocols. For example, the other template 606 or 608 may include frames of information to be transmitted according to a third protocol associated with a third automobile manufacturer and other frames transmitted according to a fourth protocol associated with a fourth automobile manufacturer.


In one example of the operation of the apparatus of FIG. 6, a signal 618 (an LF signal is received from portable, hand-held tool 616. The signal 618 is received at receiver 601. The determine template and resolution determination module 602 determines a transmission characteristic of the signal 618. This may, in some examples, be the frequency of the signal 618 or the type of modulation of the signal 618. Once the transmission parameter or parameters is or are determined, this is mapped to a template 606 or 608 and a resolution that are associated with the transmission parameter. For example, a look-up table can be used to map the determined transmission characteristic to a predetermined template and a predetermined resolution.


The template may be either template 606 or template 608 and these may be selected by the select signal 621 that is generated by the determine template and resolution determination module 602 once the template has been determined. The determine template and resolution determination module 602 also generates a resolution signal 623 with the resolution for the data to be used with the selected template 606.


The sensor 614 measures pressure data 622 (and/or other types of data) from the tire 614. In this example, template 606 is selected by select signal 621. The resolution of the data as indicated by signal 623 is used in a transmission 625 that is made by the transmitter 610.


In one aspect, the data transmission 625 corresponds to a customizable burst that includes a plurality of frames, and at least some of the frames (and in some examples each of the frames) includes tire pressure monitoring information and portions of the burst can be utilized by multiple types of receivers. For instance, each template 606 or 608 corresponds to a customizable burst that includes a plurality of frames, and at least some of the frames include tire pressure monitoring information and portions of the burst can be utilized by multiple types of receivers. The burst may be customized as to the needs of the user or the system.


It will be appreciated that the elements described with respect to FIG. 6 may be implemented in any combination or hardware and/or software elements. For example, the determine template and resolution determination module 602 may be implemented at a microprocessor that executes programmed computer instructions that implement the functions that have been described above.


Referring now to FIG. 7, one example of an approach for transmitting data from a tire pressure monitoring (TPM) sensor or monitor is described.


At step 702, a signal is transmitted from a transmitter to the TPM sensor. The signal has certain transmission characteristics (e.g., modulation type, frequency). The signal may be transmitted from a portable tool or a fixed transmitter.


At step 704, the signal is received at the TPM sensor and the transmission characteristic determined. Although the signal may in some aspects include or carry data, this data may or may not be utilized by the TPM sensor. Instead, at 706 and after the transmission characteristic has been determined, a predetermined template and data resolution associated with the transmission characteristic are determined. The transmission characteristic may be a modulation type, frequency, or some other characteristic. The template may be associated with a protocols or set of protocols. According to one embodiment, the resolution is determined by receiving an LF signal via an LF receiver that is already included in the TPMS monitor to facilitate the learn operation of those relevant OEM protocols. Thus, no HF receiver, nor a scan tool for configuration is required because the TPMS monitor is self-configuring based on the resolution determination.


At step 708, pressure (or other information such as temperature) from a tire is sensed. At step 710, the TPM sensor transmits this information using the selected template with the data transmitted according to the selected resolution. The transmission may be made to a receiver in the vehicle. As mentioned above, the TPMS wheel unit may be capable of transmitting families of protocols where the family of a particular protocol is determined by the above resolution determination. Thus, the actual data format and actual protocols transmitted is just a family of protocols rather than all N families of protocols. Thus, the TPMS wheel unit does not need to transmit all protocols or more than one family of protocols.


Referring now to FIG. 8, another example of an approach for transmitting data from a tire pressure monitoring sensor is described. At step 802, a first signal transmission from a transmitter external to the monitor is received. In one example, first signal is a low frequency (LF) signal modulated by a CW, CWdata, CW_ASK, CW_FSK modulation approach. In the alternative or in addition, the first signal may be a high frequency signal (HF). For example, the HF signal may be 434 MHz, 315 MHz according to common OEM TPMS requirements, or any other suitable frequency. LF, thus would be lower in frequency than HF, such as 30 Hz, 60 Hz, 90 HZ, 125 KHz to 100's of KHz up to 315 MHz to 434 MHz or any suitable frequency. According to one embodiment, the LF signal is a LF low frequency trigger (wake) signal, typically a 125 KHz radio wave, with modulation (containing data) or without, transmitted by a TPMS scan tool or a vehicle transmitter to cause a TPMS sensor RF transmission. Other examples are possible.


At step 804 and in response to the first signal transmission, a determination is made as to whether the first signal corresponds to a corresponding set of protocols out of two or more sets of protocol.


At step 806, a data resolution is determined. At step 808, a second data transmission is formed according to the corresponding set of protocols and the sensed data is inserted into the transmission according to the resolution.


At step 810, the second data transmission is transmitted. In one example, the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes tire pressure monitoring information and wherein portions of the burst can be utilized by multiple types of receivers. In other aspects, a TPMS identifier is included in the second data transmission. In still other examples, a FCC identifier is included in the second transmission. In some examples, the second data is transmitted by a transmitter in the TPMS monitor. In other examples, the monitor configures itself without the use of a scan tool.


Referring now to FIG. 9, one example of a transmission made from the TPM sensor (e.g., sensors 300, 500, or 600). A set 900 of multiprotocol burst sequences includes a first multiprotocol burst sequence 902, a second multiprotocol burst sequence 904, and a third multiprotocol burst sequence 906. Each of the multiprotocol burst sequences includes frames that are transmitted according to a protocol. The protocol may be a manufacturer's protocol or may be compliant (e.g., not exactly match but be compatible with) a particular manufacturer's protocol, or may be a combination of manufacturer's protocols or manufacturer-compliant protocols.


The first multiprotocol burst sequence 902 includes frames 920 compliant or following a first manufacturer protocol (M1) and frames 922 compliant or following a second manufacturer protocol (M2). The second multiprotocol burst sequence 904 includes frames 930 compliant or following a third manufacturer protocol (M3) only. The third multiprotocol burst sequence 906 includes frames 940 compliant or following a fourth manufacturer protocol (M4), frames 942 compliant or following a fifth manufacturer protocol (M5), and frames compliant or following a sixth manufacturer protocol (M6). It will be appreciated that this is one example and that other examples are possible. It will also be appreciated that in the example of FIG. 6, the transmitted made from the transmitter is selected from the set 900. In other words, the selected template relates or is one of the multiprotocol burst sequences selected from the set 900 and this selection is based a characteristic of the transmission received at the apparatus 600 (e.g., a tire pressure monitoring sensor). Additionally, the frames complaint with different manufacturer's protocols may be interleaved. For example they may be interleaved as shown and in U.S. Pat. No. 8,576,060, which is incorporated by reference herein in its entirety.


It should be understood that any of the devices described herein (e.g., the programming or activation devices, the wheel units, the controllers, the receivers, the transmitters, the sensors, the presentation devices, or the external devices) may use a computing device to implement various functionality and operation of these devices. In terms of hardware architecture, such a computing device can include but is not limited to a processor, a memory, and one or more input and/or output (I/O) device interface(s) that are communicatively coupled via a local interface. The local interface can include, for example but not limited to, one or more buses and/or other wired or wireless connections. The processor may be a hardware device for executing software, particularly software stored in memory. The processor can be a custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computing device, a semiconductor based microprocessor (in the form of a microchip or chip set) or generally any device for executing software instructions.


The memory devices described herein can include any one or combination of volatile memory elements (e.g., random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), synchronous dynamic RAM (SDRAM), video RAM (VRAM), and so forth)) and/or nonvolatile memory elements (e.g., read only memory (ROM), hard drive, tape, CD-ROM, and so forth). Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. The memory can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor.


The software in any of the memory devices described herein may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing the functions described herein. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory.


It will be appreciated that any of the approaches described herein can be implemented at least in part as computer instructions stored on a computer media (e.g., a computer memory as described above) and these instructions can be executed on a processing device such as a microprocessor. However, these approaches can be implemented as any combination of electronic hardware and/or software.


In many of these embodiments, a method of transmitting data from a tire pressure monitoring system (TPMS) monitor includes: receiving a first signal transmission from a transmitter external to the monitor, the first signal having a transmission characteristic; based upon the transmission characteristic of the first signal transmission, determining a corresponding at least one protocol; determining a data resolution based upon the transmission characteristic; forming a second data transmission according to the corresponding at least one protocol, and inserting sensed data into the second data transmission according to the resolution; and transmitting the second data transmission.


In some aspects, the corresponding at least one protocol is a set of protocols selected from two or more sets of protocols. In other aspects, the transmission characteristic comprises a modulation type or frequency.


In some examples, the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst can be utilized by multiple types of receivers. In other examples, the first signal is a low frequency signal modulated by continuous wave (CW) modulation, continuous wave data (CW data) modulation, continuous wave amplitude shift keying (CW_ASK) modulation, or continuous wave frequency shift keying (CW_FSK) modulation.


In still other aspects, a TPMS identifier is included in the second data transmission. In some examples, the TPMS identifier comprises a FCC identifier. In other aspects, the monitor configures itself without the use of a scan tool.


In others of these embodiments, a computer usable non-transitory medium has a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method of transmitting data from a tire pressure monitoring system (TPMS) monitor, and the method includes: receiving a first signal transmission from a transmitter external to the monitor, the first signal having a transmission characteristic; based upon the transmission characteristic of the first signal transmission, determining a corresponding at least one protocol; determining a data resolution based upon the transmission characteristic; forming a second data transmission according to the corresponding at least one protocol, and inserting sensed data into the second data transmission according to the resolution; and transmitting the second data transmission.


In some aspects, the corresponding at least one protocol is a set of protocols selected from two or more sets of protocols. In other aspects, the transmission characteristic comprises a modulation type or frequency.


In some examples, the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst can be utilized by multiple types of receivers. In other examples, the first signal is a low frequency signal modulated by continuous wave (CW) modulation, continuous wave data (CW data) modulation, continuous wave amplitude shift keying (CW_ASK) modulation, or continuous wave frequency shift keying (CW_FSK) modulation.


In still other aspects, a TPMS identifier is included in the second data transmission. In some examples, the TPMS identifier comprises a FCC identifier. In other aspects, the monitor configures itself without the use of a scan tool.


In others of these embodiments, an apparatus includes: a receiver with an input, the receiver configured to receive a first signal transmission from a transmitter external to the apparatus at the input, the first signal having a transmission characteristic; a determine template and resolution determination module coupled to the receiver, the determine template and resolution determination module configured to based upon the transmission characteristic of the first signal transmission, determine a corresponding at least one protocol, the determine template and data resolution module further configured to determine a data resolution based upon the transmission characteristic, form a second data transmission according to the at least one corresponding protocol, and insert sensed data into the second data transmission according to the resolution; and a transmitter with an output and coupled to the determine template and resolution determination module, the transmitter configured to transmit the second data transmission at the output.


In some aspects, the corresponding at least one protocol is a set of protocols selected from two or more sets of protocols. In other aspects, the transmission characteristic comprises a modulation type or frequency.


In other examples, the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst can be utilized by multiple types of receivers. In other examples, a first signal is a low frequency signal modulated by continuous wave (CW) modulation, continuous wave data (CW data) modulation, continuous wave amplitude shift keying (CW_ASK) modulation, or continuous wave frequency shift keying (CW_FSK) modulation.


In some aspects, a TPMS identifier is included in the second data transmission. In some examples, the TPMS identifier comprises a FCC identifier. In other examples, the apparatus configures itself without the use of a scan tool.


Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. It should be understood that the illustrated embodiments are exemplary only, and should not be taken as limiting the scope of the invention.

Claims
  • 1. A method of transmitting data from a tire pressure monitoring system (TPMS) monitor, comprising: receiving a first signal transmission from a transmitter external to the monitor, the first signal having a transmission characteristic;based upon the transmission characteristic of the first signal transmission, determining a corresponding at least one protocol;determining a data resolution based upon the transmission characteristic;forming a second data transmission according to the corresponding at least one protocol, and inserting sensed data into the second data transmission according to the resolution; andtransmitting the second data transmission, wherein the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst are compatible with multiple types of receivers.
  • 2. A computer usable non-transitory medium having a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method of transmitting data from a tire pressure monitoring system (TPMS) monitor, the method comprising: receiving a first signal transmission from a transmitter external to the monitor, the first signal having a transmission characteristic;based upon the transmission characteristic of the first signal transmission, determining a corresponding at least one protocol;determining a date resolution based upon the transmission characteristic;forming a second data transmission according to the corresponding at least one protocol, and inserting sensed data into the second data transmission according to the resolution; andtransmitting the second data transmission, wherein the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst are compatible with multiple types of receivers.
  • 3. An apparatus, comprising: a receiver with an input, the receiver configured to receive a first signal transmission from a transmitter external to the apparatus at the input, the first signal having a transmission characteristic;a determine template and resolution determination module coupled to the receiver, the determine template and resolution determination module configured to based upon the transmission characteristic of the first signal transmission, determine a corresponding at least one protocol, the determine template and data resolution module further configured to determine a data resolution based upon the transmission characteristic, form a second data transmission according to the at least one corresponding protocol, and insert sensed date into the second data transmission according to the resolution; anda transmitter with an output and coupled to the determine template and resolution determination module, the transmitter configured to transmit the second data transmission at the output, wherein the second data transmission corresponds to a customizable burst that includes a plurality of frames, and each of the frames includes sensed tire pressure monitoring information and wherein portions of the burst are compatible with multiple types of receivers.
US Referenced Citations (370)
Number Name Date Kind
2428089 Mumma et al. Sep 1947 A
2451859 Mumma et al. Oct 1948 A
3777062 Ogawa Dec 1973 A
3814839 Lubarsky et al. Jun 1974 A
3814840 Lubarsky et al. Jun 1974 A
4589063 Shah et al. May 1986 A
4703359 Rumbolt Oct 1987 A
4734674 Thomas et al. Mar 1988 A
4737761 Dosjoub et al. Apr 1988 A
4742857 Gandhi May 1988 A
4774511 Rumbolt et al. Sep 1988 A
4924210 Matsui et al. May 1990 A
4959810 Darbee Sep 1990 A
4999622 Amano et al. Mar 1991 A
5061917 Higgs et al. Oct 1991 A
5196682 Englehardt Mar 1993 A
5201067 Grube Apr 1993 A
5223844 Mansel Jun 1993 A
5228077 Darbee Jul 1993 A
5231872 Bowler et al. Aug 1993 A
5243430 Emmons Sep 1993 A
5255313 Darbee Oct 1993 A
5303259 Loveall Apr 1994 A
5335540 Bowler et al. Aug 1994 A
5365225 Bachhuber Nov 1994 A
5414761 Darbee May 1995 A
5434572 Smith Jul 1995 A
5455570 Cook Oct 1995 A
5515052 Darbee May 1996 A
5537463 Escobosa Jul 1996 A
5540092 Handfield et al. Jul 1996 A
5552917 Darbee Sep 1996 A
5562787 Koch et al. Oct 1996 A
5564101 Eisfeld et al. Oct 1996 A
5581023 Handfield et al. Dec 1996 A
5585554 Handfield et al. Dec 1996 A
5600301 Robinson, III Feb 1997 A
5602524 Mock et al. Feb 1997 A
5614906 Hayes Mar 1997 A
5624265 Redford Apr 1997 A
5661651 Geschke et al. Aug 1997 A
5663496 Handfield et al. Sep 1997 A
5698353 Jeong Dec 1997 A
5706247 Merritt et al. Jan 1998 A
5731516 Handfield et al. Mar 1998 A
5731763 Herweck Mar 1998 A
5732283 Rose et al. Mar 1998 A
5741966 Handfield et al. Apr 1998 A
5768499 Treadway et al. Jun 1998 A
5808558 Meek et al. Sep 1998 A
5838229 Robinson, III Nov 1998 A
5841390 Tsui Nov 1998 A
5844131 Gabelmann et al. Dec 1998 A
5880363 Meyer et al. Mar 1999 A
5883305 Jo et al. Mar 1999 A
5900808 Lebo May 1999 A
5926087 Busch et al. Jul 1999 A
5959751 Darbee Sep 1999 A
5963128 McClelland Oct 1999 A
5965808 Normann et al. Oct 1999 A
6002450 Darbee Dec 1999 A
6005486 Fridley Dec 1999 A
6011463 Cormier, Sr. Jan 2000 A
6014092 Darbee Jan 2000 A
6018993 Normann et al. Feb 2000 A
6021319 Tigwell Feb 2000 A
6034597 Normann et al. Mar 2000 A
6078270 Shim Jun 2000 A
6087930 Kulka et al. Jul 2000 A
6112165 Uhl et al. Aug 2000 A
6124786 Normann et al. Sep 2000 A
6141792 Acker et al. Oct 2000 A
6154658 Casi Nov 2000 A
6155119 Normann et al. Dec 2000 A
6169480 Uhl et al. Jan 2001 B1
6169907 Chang et al. Jan 2001 B1
6181241 Normann et al. Jan 2001 B1
6192747 Fennel Feb 2001 B1
6194999 Uhl et al. Feb 2001 B1
6201819 Luders Mar 2001 B1
6204758 Wacker et al. Mar 2001 B1
6208341 van Ee et al. Mar 2001 B1
6218936 Imao Apr 2001 B1
6259361 Robillard et al. Jul 2001 B1
6271748 Derbyshire et al. Aug 2001 B1
6275148 Takamura et al. Aug 2001 B1
6297731 Flick Oct 2001 B1
6298095 Kronestedt et al. Oct 2001 B1
6333698 Roddy Dec 2001 B1
6362731 Lill Mar 2002 B1
6369703 Lill Apr 2002 B1
6396408 Drummond et al. May 2002 B2
6400263 Kokubo Jun 2002 B1
6408232 Cannon et al. Jun 2002 B1
6438467 Pacsai Aug 2002 B1
6441728 Dixit et al. Aug 2002 B1
6445286 Kessler et al. Sep 2002 B1
6446502 Normann et al. Sep 2002 B1
6453737 Young et al. Sep 2002 B2
6463798 Niekirk et al. Oct 2002 B2
6469621 Vredevogd et al. Oct 2002 B1
6477165 Kosco Nov 2002 B1
6486773 Bailie et al. Nov 2002 B1
6489888 Honeck et al. Dec 2002 B1
6490452 Boscovic et al. Dec 2002 B1
6507306 Griesau Jan 2003 B1
6518891 Tsutsui et al. Feb 2003 B2
6567032 Mullaly May 2003 B1
6571617 Van Niekerk et al. Jun 2003 B2
6612165 Juzswik et al. Sep 2003 B2
6622552 Delaporte Sep 2003 B1
6630885 Hardman et al. Oct 2003 B2
6633229 Normann et al. Oct 2003 B1
6662642 Breed et al. Dec 2003 B2
6667687 DeZori Dec 2003 B1
6681164 Berghoff et al. Jan 2004 B2
6693522 Tang et al. Feb 2004 B2
6704364 Lim et al. Mar 2004 B1
6705155 Katou Mar 2004 B2
6710708 McClelland et al. Mar 2004 B2
6731205 Schofield et al. May 2004 B2
6737965 Okubo May 2004 B2
6738697 Breed May 2004 B2
6747590 Weber Jun 2004 B1
6750761 Newman Jun 2004 B1
6774778 Lin Aug 2004 B2
6778380 Murray Aug 2004 B2
6788193 King et al. Sep 2004 B2
6794993 Kessler et al. Sep 2004 B1
6801872 Normann et al. Oct 2004 B2
6802213 Agrotis Oct 2004 B1
6804999 Okubo Oct 2004 B2
6822603 Crimmins et al. Nov 2004 B1
6828905 Normann et al. Dec 2004 B2
6832573 Evans et al. Dec 2004 B2
6871157 Lefaure Mar 2005 B2
6879252 DeZorzi et al. Apr 2005 B2
6885282 Desai Apr 2005 B2
6885292 Katou Apr 2005 B2
6885293 Okumura Apr 2005 B2
6885296 Hardman et al. Apr 2005 B2
6888471 Elsner et al. May 2005 B2
6897770 Lill May 2005 B2
6904796 Pacsai et al. Jun 2005 B2
6906624 McClelland et al. Jun 2005 B2
6910627 Simpson-Young et al. Jun 2005 B1
6914523 Munch et al. Jul 2005 B2
6915146 Nguyen et al. Jul 2005 B1
6915229 Taguchi et al. Jul 2005 B2
6919798 Ide Jul 2005 B2
6920785 Toyofuku Jul 2005 B2
6922140 Hernando et al. Jul 2005 B2
6927679 Taguchi et al. Aug 2005 B2
6941803 Hirohama et al. Sep 2005 B2
6972671 Normann et al. Dec 2005 B2
6983649 Katou Jan 2006 B2
6996418 Teo et al. Feb 2006 B2
7002455 Buck et al. Feb 2006 B2
7010968 Stewart et al. Mar 2006 B2
7015801 Juzswik Mar 2006 B1
7017403 Normann et al. Mar 2006 B2
7034661 Lonsdale et al. Apr 2006 B2
7039397 Chuey May 2006 B2
7042348 Schulze et al. May 2006 B2
7050794 Chuey et al. May 2006 B2
7084749 Honeck et al. Aug 2006 B1
7084751 Klamer Aug 2006 B2
7088226 McClelland et al. Aug 2006 B2
7095316 Kachouh et al. Aug 2006 B2
7096003 Joao et al. Aug 2006 B2
7103460 Breed Sep 2006 B1
7104438 Benedict Sep 2006 B2
7113083 Suitsu Sep 2006 B2
7116213 Thiesen et al. Oct 2006 B2
7116218 Ogawa et al. Oct 2006 B2
7120430 Christenson et al. Oct 2006 B2
7137296 Shida et al. Nov 2006 B2
7148793 Lin Dec 2006 B2
7161466 Chuey Jan 2007 B2
7161476 Hardman et al. Jan 2007 B2
7164117 Breed et al. Jan 2007 B2
7173520 Desai et al. Feb 2007 B2
7224269 Miller et al. May 2007 B2
7243535 Shimura Jul 2007 B2
7254994 Schulze et al. Aug 2007 B2
7307480 Shiu et al. Dec 2007 B2
7315240 Watabe Jan 2008 B2
7318162 Rineer et al. Jan 2008 B2
7369491 Beshai et al. May 2008 B1
7380450 Durif Jun 2008 B2
7382239 Song et al. Jun 2008 B2
7414523 Li et al. Aug 2008 B2
7453350 Kachouh et al. Nov 2008 B2
7478554 Roth et al. Jan 2009 B2
7508762 Ohtani Mar 2009 B2
7512109 Trott et al. Mar 2009 B2
7518495 Tang et al. Apr 2009 B2
7519011 Petrus et al. Apr 2009 B2
7535841 Beshai et al. May 2009 B1
7642904 Crano Jan 2010 B2
7663502 Breed Feb 2010 B2
7688192 Kenny et al. Mar 2010 B2
7697497 Grube et al. Apr 2010 B2
7817543 Beshai et al. Oct 2010 B2
7884707 Wittliff et al. Feb 2011 B2
7885603 Santavicca Feb 2011 B2
7895886 Tozawa et al. Mar 2011 B2
7900198 Kasman Mar 2011 B2
7948364 Lin et al. May 2011 B2
8013725 Murata et al. Sep 2011 B2
8015864 Petrucelli Sep 2011 B2
8019323 Jheng et al. Sep 2011 B2
8027359 Iwamura Sep 2011 B2
8031598 Beshai et al. Oct 2011 B2
8035257 Fornage Oct 2011 B2
8049533 Lin Nov 2011 B1
8082579 Shimizu et al. Dec 2011 B2
8155617 Magnusson et al. Apr 2012 B2
8185093 Jheng et al. May 2012 B2
8319378 Fornage Nov 2012 B2
8330594 Suzuki et al. Dec 2012 B2
8332104 Greer et al. Dec 2012 B2
8576060 Deniau et al. Nov 2013 B2
9259980 Deniau et al. Feb 2016 B2
20010050611 Achterholt Dec 2001 A1
20020030592 Laitsaari et al. Mar 2002 A1
20020059825 Lundqvist May 2002 A1
20020067285 Lill Jun 2002 A1
20020075145 Hardman et al. Jun 2002 A1
20020084895 Dixit et al. Jul 2002 A1
20020086708 Teo et al. Jul 2002 A1
20020087250 Pascai Jul 2002 A1
20020121132 Breed et al. Sep 2002 A1
20020126005 Hardman et al. Sep 2002 A1
20020130803 Conway et al. Sep 2002 A1
20020144134 Watanabe et al. Oct 2002 A1
20020168795 Schuumans Nov 2002 A1
20020186320 Carlsgaard Dec 2002 A1
20020190852 Lin Dec 2002 A1
20030005759 Breed et al. Jan 2003 A1
20030009270 Breed Jan 2003 A1
20030030553 Schofield et al. Feb 2003 A1
20030050070 Mashinsky et al. Mar 2003 A1
20030071723 Tang et al. Apr 2003 A1
20030079537 Luce May 2003 A1
20030080860 Stewart et al. May 2003 A1
20030080861 Okubo May 2003 A1
20030095553 Shiomoto et al. May 2003 A1
20030110851 Tsujita Jun 2003 A1
20030112138 Marguet et al. Jun 2003 A1
20030117276 Marguet et al. Jun 2003 A1
20030117277 Marguet et al. Jun 2003 A1
20030122660 Kachouh et al. Jul 2003 A1
20030131297 Fischel et al. Jul 2003 A1
20030179082 Ide Sep 2003 A1
20030197594 Olson et al. Oct 2003 A1
20030197595 Olson et al. Oct 2003 A1
20030197603 Stewart et al. Oct 2003 A1
20030197604 Ogawa et al. Oct 2003 A1
20030201783 Steber et al. Oct 2003 A1
20030228879 Witkowski Dec 2003 A1
20040027241 Forster Feb 2004 A1
20040039509 Breed Feb 2004 A1
20040041698 Lin Mar 2004 A1
20040061601 Freakes Apr 2004 A1
20040113765 Suitsu Jun 2004 A1
20040130442 Breed et al. Jul 2004 A1
20040149025 Toyofuku Aug 2004 A1
20040172179 Miwa Sep 2004 A1
20040174246 Mitchell Sep 2004 A1
20040203370 Luo et al. Oct 2004 A1
20040215382 Breed et al. Oct 2004 A1
20050024194 Ide Feb 2005 A1
20050039103 Azenko et al. Feb 2005 A1
20050046584 Breed Mar 2005 A1
20050075145 Dvorak et al. Apr 2005 A1
20050104722 Tang et al. May 2005 A1
20050132792 Lemense et al. Jun 2005 A1
20050134446 Stewart et al. Jun 2005 A1
20050156722 McCall et al. Jul 2005 A1
20050179530 Stewart et al. Aug 2005 A1
20050192727 Shostak et al. Sep 2005 A1
20050264405 Ueda Dec 2005 A1
20060001535 Hafele et al. Jan 2006 A1
20060006992 Daiss et al. Jan 2006 A1
20060012475 Froitzheim et al. Jan 2006 A1
20060017554 Stewart et al. Jan 2006 A1
20060022813 Schulze et al. Feb 2006 A1
20060025897 Shostak et al. Feb 2006 A1
20060044125 Pierbon Mar 2006 A1
20060114107 Kim et al. Jun 2006 A1
20060145829 Watabe Jul 2006 A1
20060148456 Chuey Jul 2006 A1
20060152342 Turner et al. Jul 2006 A1
20060161327 Emmerich et al. Jul 2006 A1
20060187014 Li et al. Aug 2006 A1
20060192661 Geradiere Aug 2006 A1
20060201241 Durif Sep 2006 A1
20060217850 Geerlings et al. Sep 2006 A1
20060235641 Fink et al. Oct 2006 A1
20060273889 Schulze et al. Dec 2006 A1
20060277989 Lee et al. Dec 2006 A1
20070063814 Olson et al. Mar 2007 A1
20070069947 Banet et al. Mar 2007 A1
20070090936 Nornes Apr 2007 A1
20070176736 Chuey et al. Aug 2007 A1
20070182531 Kuchler Aug 2007 A1
20070190993 Chuey et al. Aug 2007 A1
20070194898 Fukumori Aug 2007 A1
20070210920 Panotopoulos Sep 2007 A1
20070213951 Van Eeden Sep 2007 A1
20070223484 Crowle et al. Sep 2007 A1
20070247294 Baader et al. Oct 2007 A1
20070279201 Casey et al. Dec 2007 A1
20080001729 Kyllmann et al. Jan 2008 A1
20080024287 Boyle et al. Jan 2008 A1
20080037458 Myszne Feb 2008 A1
20080062880 Yew et al. Mar 2008 A1
20080080447 Grube et al. Apr 2008 A1
20080094198 Yu Apr 2008 A1
20080100430 Kochie et al. May 2008 A1
20080141766 Roth et al. Jun 2008 A1
20080143593 Graziano et al. Jun 2008 A1
20080157954 Tsuchida Jul 2008 A1
20080165688 Beshai et al. Jul 2008 A1
20080173082 Hettle et al. Jul 2008 A1
20080177441 Marlett et al. Jul 2008 A1
20080204217 Costello et al. Aug 2008 A1
20080205553 Costello et al. Aug 2008 A1
20080211672 Pei Sep 2008 A1
20080240283 Iwamura Oct 2008 A1
20080256260 Magnusson et al. Oct 2008 A1
20080282965 Crano Nov 2008 A1
20080285507 Mukherjee et al. Nov 2008 A1
20080320243 Mitsuzuka et al. Dec 2008 A1
20090021362 Kochie Jan 2009 A1
20090033478 Deniau et al. Feb 2009 A1
20090045930 Fu Feb 2009 A1
20090067854 Yokogawa et al. Mar 2009 A1
20090070863 Shimizu et al. Mar 2009 A1
20090108992 Shafer Apr 2009 A1
20090109012 Petrucelli Apr 2009 A1
20090179747 Lin et al. Jul 2009 A1
20090184815 Suzuki et al. Jul 2009 A1
20090207859 Beshai et al. Aug 2009 A1
20090224901 Yu Sep 2009 A1
20090231114 Yu Sep 2009 A1
20090245803 Garner et al. Oct 2009 A1
20090267751 Wittliff Oct 2009 A1
20090291710 Jheng et al. Nov 2009 A1
20090310477 Lee et al. Dec 2009 A1
20100071453 Isono Mar 2010 A1
20100308987 Haas et al. Dec 2010 A1
20110140876 Deniau Jun 2011 A1
20110181321 Matsudera Jul 2011 A1
20110211414 Musha Sep 2011 A1
20110250860 Lin Oct 2011 A1
20110267024 Halberstadt Nov 2011 A1
20110294548 Jheng et al. Dec 2011 A1
20120001745 Li Jan 2012 A1
20120117788 Deniau May 2012 A1
20120119895 Deniau May 2012 A1
20120139751 Lin Jun 2012 A1
20120147184 Siann et al. Jun 2012 A1
20120185110 Deniau et al. Jul 2012 A1
20120274461 Colombo et al. Nov 2012 A1
20130282231 Farr et al. Oct 2013 A1
20140139332 Mouchet May 2014 A1
20150015389 McIntyre et al. Jan 2015 A1
20150015390 McIntyre et al. Jan 2015 A1
Foreign Referenced Citations (82)
Number Date Country
4492128 Jun 1996 DE
19503756 Aug 1996 DE
19720123 Jul 1998 DE
19924830 Nov 2000 DE
10014076 Oct 2001 DE
10040238 Mar 2002 DE
10247761 Jun 2003 DE
10217239 Jul 2003 DE
10207014 Aug 2003 DE
10307265 Oct 2003 DE
69529456 Nov 2003 DE
10247149 Apr 2004 DE
60108973 Jul 2005 DE
60202342 Dec 2005 DE
60023387 Jul 2006 DE
102005004825 Aug 2006 DE
102005059009 Jun 2007 DE
102007039599 Mar 2008 DE
102008008237 Aug 2009 DE
102008033051 Feb 2010 DE
793579 Sep 1997 EP
1026016 Aug 2000 EP
1291230 Mar 2003 EP
1428694 Dec 2003 EP
1440824 Jul 2004 EP
1494877 Jan 2005 EP
1536392 Jun 2005 EP
1547827 Jun 2005 EP
1562162 Aug 2005 EP
1026015 May 2006 EP
1674299 Jun 2006 EP
1352763 Apr 2008 EP
1340629 Jun 2008 EP
2387032 Oct 2003 GB
2420415 May 2006 GB
2500697 Oct 2013 GB
62003537 Jan 1987 JP
63090407 Apr 1988 JP
05107134 Apr 1993 JP
8244423 Sep 1996 JP
2000142044 May 2000 JP
2000238515 Sep 2000 JP
2001080321 Mar 2001 JP
2001312860 Sep 2001 JP
2003025817 Jan 2003 JP
2003-312220 Nov 2003 JP
2004-145474 May 2004 JP
2005289116 Oct 2005 JP
2006015832 Jan 2006 JP
2007010427 Jan 2007 JP
2007200081 Aug 2007 JP
2007283816 Nov 2007 JP
2008137585 Jun 2008 JP
4265448 Feb 2009 JP
5502729 May 2014 JP
2003068216 Aug 2003 KR
1020070040883 Apr 2007 KR
10-2009-0091001 Aug 2009 KR
38461 Jun 2004 RU
2238190 Oct 2004 RU
2398680 Jun 2006 RU
2409480 Jul 2006 RU
2352473 Apr 2009 RU
9420317 Sep 1994 WO
9422693 Oct 1994 WO
9908887 Feb 1999 WO
0072463 Nov 2000 WO
0145967 Jun 2001 WO
02094588 Nov 2002 WO
03016079 Feb 2003 WO
2004038674 May 2004 WO
2005085651 Sep 2005 WO
2005116603 Dec 2005 WO
2007006871 Jan 2007 WO
2009006518 Jan 2008 WO
2008-103973 Aug 2008 WO
2008106387 Sep 2008 WO
2008107430 Sep 2008 WO
2012097154 Jul 2012 WO
2013063061 May 2013 WO
2013152294 Oct 2013 WO
2015015692 Feb 2015 WO
Non-Patent Literature Citations (35)
Entry
“Sony Remote Commander Operating Instructions RM-V701/V801”, 1998, Sony Corporation.
“Philips Magnavox 4 Function with Back Lighted Keypad Universal Remote” Operating Instructions, printed Oct. 2012, Philips Electronics North America Corporation.
“RadioShack 8-In-One Touch Screen Remote Control”, Owner's Manual, 2001, RadioShack Corporation.
Kais Mnif, “A Smart Tire Pressure Monitoring System”, Sensors Magazine, Nov. 1, 2001.
International Search Report and Written Opinion dated Sep. 28, 2012, from corresponding International Patent Application No. PCT/US2011/047112.
International Search Report dated Apr. 6, 2012, from corresponding International Patent Application No. PCT/US2011/047087.
International Search Report and Written Opinion mailed on Oct. 15, 2008, for Application No. PCT/US2008/069006.
International Preliminary Report on Patentability mailed on Jan. 14, 2010, for Application No. PCT/US2008/069006.
Chinese Office Action mailed on Apr. 19, 2011, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Chinese Office Action (second) mailed on Feb. 16, 2012, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Chinese Office Action (third) mailed on Oct. 10, 2012, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Japanese Office Action mailed on Jun. 7, 2012, for JP Application 2010-515252 (Corresponding to PCT/US2008/069006).
International Search Report and Written Opinion dated Sep. 28, 2012, from corresponding International Patent Application No. PCT/US2011/047104.
Germany Office Action dated Nov. 19, 2012.
Germany Office Action dated Sep. 17, 2007.
Preliminary Invalidity Contentions of Defendant Continental Automotive Systems US, Inc.; dated Jan. 17, 2012, , In the United States District Court for Western District of Virginia Lynchburg Division, Civil Action No. 6:11-CV-00014-NKM.
Amended Invalidity Contentions of Defendant Continental Automotive Systems US, Inc.; dated Jun. 18, 2012, , In the United States District Court for Eastern District of Michigan Southern Division, Civil Action No. 2:12-cv-10715-SJM-MJH.
Plaintiffs' Initial Infringement Contentions; dated Dec. 15, 2011, In the United States District Court for Western District of Virginia Lynchburg Division, Civil Action No. 6:11-CV-00014-NKM-RSB.
Joint Claim Construction and Prehearing Statement, dated Jun. 11, 2012, from co-pending litigation: Schrader-Bridgeport Int'l, Inc. v. Continental Automotive Sys, US, Inc., case docket No. 2:12-cv-10715-SJM-MJH, (filed Feb. 16, 2012, E.D. Mich.).
Plaintiffs' Opening Claim Construction Brief, dated Jun. 26, 2012, from co-pending litigation: Schrader-Bridgeport Int'l, Inc. v. Continental Automotive Sys. US, Inc., case docket No. 2:12-cv-10715-SJM-MJH, (filed Feb. 16, 2012, E.D. Mich.).
USPTO Translation of JP2003025817A, translated from Japanese by Schreiber Translations, Inc., Feb. 2013.
Jeff Burgess, “TPMS Demonstration Kit”, AN1943/D, Rev 1, Apr. 2002, Motorola, Inc., 2002 (16 pgs.).
Search Report dated Jun. 20, 2014 , from EP Patent Application No. 11870613.4.
Search Report dated Jun. 30, 2014 , from EP Patent Application No. 11870701.7.
Search Report dated Mar. 24, 2015, from EP Patent Application No. 11870650.6.
Search Report dated Apr. 19, 2012, from International Patent Application No. PCT/US2012/021082.
Search Report dated Aug. 20, 2015, from GB Patent Application No. GB1503824.3.
Machine Translation of RU2423246 C1.
Translation of Abstract of KR1020070040883A.
International Search Report mailed on Jun. 11, 2015 for application PCT/US2015/016182.
International Search Report and Written Opinion dated Sep. 28, 2012, from corresponding International Patent Application No. PCT/US2011/047108.
Jeff Burgess, “Tire Pressure Monitoring System Reference Design”, Tire Pressure Monitor System Demo, AN1951/D, Rev 1, May 2003, Motorola, Inc., 2003 (24 pgs.).
“Motorola's MPXY8000 Series Tire Pressure Monitoring Sensors”, Motorola Sensor Products Division Transportation & Standard Products Group, Motorola, Inc., May 2003 (22 pgs.).
Alfred Pohl et al. “Wirelessly Interrogable Surface Acoustic Wave Sensors for Vehicular Applications”, IEEE Transactions on Instrumentation and Measurement vol. 46, No. 4, IEEE, Aug. 1997 (8 pgs . . . ).
“Tire pressure Warning System Using Direct Measurement Method (SOARER)” G0880A ISSN: 0388-3841, vol. 51 No. 7, pp. 174-179, Toyota Motor Corporation, May 2, 2002 (6 pgs.).
Related Publications (1)
Number Date Country
20160059647 A1 Mar 2016 US