Apparatus, system and method for configuring a tire information sensor with a transmission protocol based on vehicle trigger characteristics

Information

  • Patent Grant
  • 10220660
  • Patent Number
    10,220,660
  • Date Filed
    Monday, August 1, 2016
    7 years ago
  • Date Issued
    Tuesday, March 5, 2019
    5 years ago
Abstract
In a vehicle tire pressure sensor, a wireless, low frequency (LF) receiver identifies a particular type of signal protocol that was used to form a first message that is sent to the sensor by the vehicle. Using the identification of the protocol used to form the first message, the sensor determines a type of signal protocol to be used to transmit information to the vehicle, such as an identifier for the tire pressure sensor in a second message.
Description
CROSS REFERENCE TO RELATED APPLICATIONS

The following documents are considered to be related to the subject matter of this disclosure and are incorporated by reference herein in their entireties: U.S. patent application Ser. No. 13/206,336 entitled “Apparatus and Method for Activating a Localization Process for a Tire pressure Monitor;” now U.S. Pat. No. 9,024,743, U.S. application Ser. No. 13/206,314 entitled “Protocol Arrangement in a Tire Pressure Monitoring System;” now U.S. Pat. No. 8,576,060, U.S. application Ser. No. 13/206,358 entitled “Protocol Misinterpretation Avoidance Apparatus and Method for a Tire Pressure Monitoring System;” now U.S. Pat. No. 8,502,655, U.S. application Ser. No. 13/206,225 entitled “Tire Pressure Monitoring Apparatus and Method;” now U.S. Pat. No. 8,742,914, U.S. Pat. No. 8,692,661 entitled “Universal Tire Pressure Monitor Sensor;” U.S. Pat. No. 8,576,060 entitled “Protocol Arrangement in a Tier Pressure Monitoring System;” U.S. Pat. No. 7,243,535 entitled “Tire Monitoring System and Its Monitor Receiver, Monitor and Sensor,” and U.S. Pat. No. 7,518,495 entitled, “Universal Tier Pressure Monitor.”


TECHNICAL FIELD

The technical field relates to tire pressure monitoring devices that can operate using different message protocols.


BACKGROUND

Tire inflation pressure, tire temperature, tire age and tire rotational speed are known to be important to the safe operation of a motor vehicle. By way of example, a low tire pressure will reduce a vehicle's fuel efficiency, shorten tire life but more importantly a low tire pressure can cause a tire to fail.


Monitoring tire pressure is an inconvenience. Consequently, automatic tire pressure monitoring systems have been devised and most of these systems free the user from having to manually test a tire's inflation pressure.


Known automatic tire pressure sensing (TPS) devices are typically mounted within a tire that is mounted onto a wheel. The TPS device includes a pressure sensor, which provides signals that indicate or which correspond to a pressure inside the tire. The TPS wirelessly transmits such sensor information, using a protocol corresponding to, or required by a receiver within or coupled to the vehicle. Once the receiver receives the tire operating condition information, the information is presented on an instrument panel (IP) and thus provides a real-time or near real-time indication of actual tire conditions.


Inasmuch as tire pressure information is provided to an instrument panel and thus “incorporated” into or with other vehicle information, tire operating condition information is sent by a TPS device to a vehicle using radio frequency (RF) band signals, the format and transmission repetition rate of which is defined or specified by a vehicle's manufacturer. Each manufacturer typically uses its own unique, preferred, and pre-defined communications protocol in order to meet its own needs. Stated another way, the transmitters and receivers attached to a vehicle which send information to and receive information from a TPS device in a tire require the TPS device to use the manufacturer's TPS communication protocol. A tire pressure monitor device capable of operating with different communication protocols of different manufacturers, as well as different communication protocols used by the same manufacturer would reduce the number of different TPS devices that TPS manufacturers and servicers would have to provide and would thus be an improvement over the prior art.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a tire pressure monitoring system;



FIG. 2 is a block diagram of a tire pressure sensor;



FIG. 3 is a block diagram of a monitor, which receives tire pressure sensor information from tire pressure sensors;



FIG. 4 is a flow chart depicting a method of determining a particular type of protocol used to format an LF message from a vehicle;



FIG. 5 is a flow chart depicting steps of a method for communicating to a sensor from a vehicle;



FIG. 6A-6C depict different protocols used to form a low frequency or “LF” message;



FIG. 6D-6F depict different protocols used to form a radio frequency or “RF” message; and



FIG. 7 depicts how reception of different LF message protocols by a sensor are responded to by sending RF messages formed using different RF message protocols.





DETAILED DESCRIPTION


FIG. 1 depicts a motor vehicle 100 with a tire pressure monitoring system 102. The system 102 comprises at least one battery-powered tire pressure sensor 200, described hereinafter, located inside each tire 104. The system also comprises a tire pressure montor 300, which is attached to or located in the vehicle 100.


Signals are sent to the tire pressure sensor 200 using low power, low frequency “LF” signals, which are themselves known in the art. Signals are sent from the tire pressure sensor 200 to the monitor 300 using low power radio frequency or “RF” signals, which are themselves also known in the art.


As described below, each sensor 200 has an LF antenna 210 by which the sensor 200 can receive LF signals. Each wheel well 108 is provided with an LF antenna 302, which is thus “proximate” to the tire pressure sensor 200 for each tire 104 and the LF antenna for the sensor. The LF antennas on the sensor and in the wheel well enable information-bearing wireless signals to be sent to the sensors 200 from the monitor 300. As described hereinafter, the monitor 300 selectively communicates wirelessly with the tire pressure sensors 200 one-at-a-time or at the same time, i.e., concurrently, using at least one of two, different wireless communication protocols or methods described below.


Unlike prior art tire pressure monitoring systems, including those described in the prior art documents incorporated by reference, the battery powered tire pressure 200 described herein enables one single “type” of tire pressure sensor 200 to be usable with virtually any type of motor vehicle. Stated another way, the tire pressure sensor 200 is a “universal” sensor, usable with different vehicles made by different vehicle manufacturers, having a tire pressure monitor 300.


When tire pressure sensors are first installed onto a vehicle, they typically determine the type of vehicle they are installed on, and the communications protocols to use, by analyzing LF signals received from a service tool or an activation device, such as the activation device 120 disclosed in Applicant's U.S. Pat. No. 8,576,060. In order to provide a more general purpose tire pressure sensor, or if a service tool or an activation device are not available, when the tire pressure sensor 200 described herein is first installed or first configured for use with a vehicle, the sensor 200 “listens” for a low-frequency (LF) signal from a vehicle's tire pressure monitor 300. By analyzing LF signals received from the vehicle's monitor 300, the pressure sensor 200 determines a particular message protocol used by the vehicle and hence the type of vehicle it is installed into. After the particular protocol is identified by the sensor 200, the sensor thereafter sends information to the monitor 300 as required by the manufacturer, preferably, but not necessarily, using only the particular communication protocol for the particular vehicle, and preferably but not necessarily, only as often as is required by the manufacturer of the particular vehicle.


The ability of the sensor 200 to work cooperatively with multiple vehicles is provided to the sensor 200, by program instructions for a processor in the sensor 200. Those instructions cause the LF receiver in the sensor 200 to “listen” for an LF message and determine from a received LF message how the LF message was formatted, encoded or modulated, i.e., which protocol of several different possible protocols were used to form the LF message. And, since some LF message formats include or are determined by values or symbols in one or more fields of an LF message itself, determining a format, protocol or “modulation” can include analyses of message field contents. For the sake of clarity, the terms form, format, encode and modulate are used interchangeably and should be construed as possibly including values in one or more message fields.


Since most vehicle manufacturers use proprietary encoding or modulation, the determination of an encoding or modulation scheme from an LF message effectively identifies the particular type of vehicle that transmitted the LF message. Knowing the type of vehicle that sent an LF message enables the sensor 200 to respond with an RF message that is modulated or encoded according to only the vehicle manufacturer's specifications and no other. The sensor 200 can thus be used with any vehicle that it is programmed to recognize; it does not use or require programming or re-programming nor does it require switches or programming devices to change its operation.


In a preferred embodiment, the sensor 200 transmits tire condition information only as it is required by a vehicle's manufacture and thereby avoids transmitting the same tire information over and over using multiple different formats or protocols as do prior art tire pressure sensors. In an alternate embodiment, however, some information that might not be needed can nevertheless be transmitted. By way of example, if two types of LF messages are received, such as an LF type A and LF type B then the processor can end RF messages for both vehicle type A and vehicle type B. Such an arrangement allows the sensor 200 to meet F.C.C. transmission requirements while keeping the amount of software at a reasonable level.


The ability to recognize multiple different communication protocols used by multiple different manufactures and therefore send information using preferably only one protocol, and preferable only as often as needed or required by a vehicle's manufacturer significantly reduces the length of a transmission from the sensor 200. Reducing the length or duration of a message sent by the sensor 200 significantly increases battery life.


For clarity as well as claim construction, as used herein a “tire” is considered to be the generally annular-shaped, relatively soft or flexible cushion that fits around a wheel and which normally contains compressed air. A “wheel” is a circular frame of hard material, e.g., aluminum or steel, that may be solid, partly solid, or spoked, but which is capable of being attached to and turning on an axle and on which a tire is mounted.


A “tire pressure sensor” is considered to be a device capable of being attached to a tire or located inside a tire or attached to or located inside wheel. It obtains tire operating characteristics and information from one or more sensors or transducers. Such information includes but not limited to inflation pressure, internal or external temperature, rotational speed and acceleration.


A tire pressure sensor is of course also capable of obtaining and wirelessly transmitting such tire-related information in real time or nearly real time. A “tire pressure sensor” does not necessarily include or require either a wheel, a tire or a wheel-tire assembly nor does it require a vehicle or tire pressure monitor 300.


As used herein, “tire-located” should be construed to be mean, located on or inside a tire or, attached to or inside a vehicle wheel to which a tire is mounted such that characteristics of the tire on the wheel can be sensed.


“Real time” means the actual time during which something takes place.


In a preferred embodiment of the system 102 shown in FIG. 1, at least one tire pressure sensor device 200 is located within each tire 104 of the vehicle 102. As is known in the art, tire pressure sensors communicate with a vehicle's tire pressure monitoring system or “receiver” using both LF and RF signals. Information is sent by the vehicle to a sensor using LF signals; information is received by the vehicle from a sensor using “RF” signals.


Referring now to FIG. 2, a preferred embodiment of a tire pressure sensor 200 comprises an LF receiver 202 and an RF transmitter 204. For simplicity and brevity, the LF receiver 202 and RF transmitter 204 are depicted as having their own corresponding antennas 210 and 216.


The LF receiver 202 is configured to be able to receive relatively low-frequency, low-power and thus short-range signals through the conventional LF antenna 210. Such LF signals and antennas are well known: they have short propagation distances but which are nevertheless great enough to traverse the distance between the LF antenna 210 and an LF antenna 302 in a vehicle's wheel well.


The nominal frequency of the LF signals is typically about one-hundred-twenty-five kilohertz (125 kHz). Information on the LF signal is preferably provided by amplitude modulating (AM) the 125 kHz. signal. Such LF signals are thus considered to be in a first frequency band, i.e., a first portion of the electromagnetic spectrum.


The RF transmitter 204 portion of the sensor 200 transmits low power-level signals from the RF signal antenna 216 for the sensor 200 at a much higher frequency, i.e., about 315 Mhz., which is a distinctly different portion of the electromagnetic spectrum and hence in a different band, i.e., the radio frequency band. The RF transmitter 204 is thus considered herein as operating in a second, different frequency band. Information can be carried on the RF signals using any one of a variety of different modulation techniques, e.g., FM, AM, FSK, PSK, all of which are well known to those of ordinary skill in the communications art.


Still referring to FIG. 2, the LF receiver 202 and RF transmitter 204 are both coupled to a conventional processor 220, preferably a microcontroller with its own on-board memory, through a conventional bus 222, which is a set of electrically-parallel conductors in an electronic system that form a main transmission path between various components of the system. Using the bus 222, the processor 220 is able to send data and control signals to one or both the LF receiver 202 and RF transmitter 204. The processor 220 also receives data and information from the LF receiver 202 and RF transmitter 204. The processor 220, LF receiver 202 and RF transmitter 204 are thus considered to be coupled to each other through the bus 222.


As used herein, a “sensor” is a device that responds to a physical stimulus such as pressure, heat and acceleration, and which generates an electrical signal representing the stimulus. In FIG. 2, the processor 220 is coupled to one or more sensors 224, 226, 228 through the bus 222. In a preferred embodiment, at least one sensor coupled to the processor 220 is a pressure sensor. It outputs an electrical signal to the processor via the bus 222 or another conductor, not shown, which is proportional to, or representative of, a tire's inflation pressure. In other embodiments, the sensors 224, 226 and 228 can include a pressure sensor, a temperature sensor, an accelerometer and a timer, all of which can sense an operating condition of a tire and are thus considered to be tire operating condition sensing devices.


As can be seen in FIG. 2, the sensors provide signals that represent corresponding tire conditions to the processor 220 via the bus 222. The signal representing tire operating conditions are provided by the processor 220 to the RF transmitter 204, which generates a radio frequency signal that is transmitted from the RF antenna 216. The sensor 200 thus transmits signals representing tire operating conditions by forming a message that is modulated onto a radio frequency carrier signal using a tire sensor information communications protocol.


Most vehicle manufacturers use their own protocols to send tire operating condition information from a tire sensor to a vehicle. The ability to modulate the various tire operating condition information onto an RF signal using different protocols is provided by program instructions 250 stored in the memory 230 for the sensor's processor.


The processor 220 for the sensor 200 provides “intelligence” to the sensor by controlling devices coupled to the bus 222. The control of those devices ir provided by executable program instructions that are stored in a memory device 230.


As shown in FIG. 2, the memory device 230 is coupled to the processor 220 by a second and different bus 226 because the memory device 230 and processor 220 are part of a microcontroller and thus typically co-located on the same semiconductor die 227. The memory device 230 is in any case a non-transitory storage device for a control program 232 that is located inside the memory device 230. The memory device 230 can, however, also store data sent to the processor 220 by the various peripheral devices that include the receiver 202, transmitter 204 and sensors.


Referring now to FIG. 3, which is a block diagram of the tire pressure monitor 300, a conventional low frequency (LF) antenna is installed into each wheel well of a vehicle. Vehicle wheel wells are not shown in FIG. 3. Four LF antennae are shown in FIG. 3, one for each wheel well, and identified by reference numerals 302A-302D.


An antenna switch 304 is able to selectively couple one or more of the antennae 302 to an LF transmitter 306. The LF antenna switch 304 and the LF transmitter are both coupled to a processor 308 through a bus 310 and thus receive data and control instructions from the processor 308 via the bus 310.


The LF antennas 302A-302D are sized, shaped and arranged in the vehicle's wheel wells to inductively couple them to LF antennae for tire pressure sensors 200 also in a wheel well. A low frequency signal output from the LF transmitter 306 can thus be selectively provided to one antenna or multiple antenna by way of control signals provided to the antenna switch 304 by the processor 308. Information-bearing signals from the LF transmitter 306 can thus be wirelessly transferred from the monitor 300 to the tire pressure sensor 200 via LF antennae via the LF antennae 302A-302D and the antennae 210 for each tire pressure sensor 200. Selectively connecting or energizing the different wheel well antennae 302 enables the monitor 300 to selectively communicate with tire pressure sensors 200 one-at-a-time or in parallel.


Four RF antennae are identified by reference numerals 312A-312D, one being located inside each wheel well. A second antenna switch 316 selectively couples one or more of the antennae 312 to an RF receiver 314. The RF antenna switch 316 and the RF receiver 314 are both coupled to the processor 308 through the bus 310 and thus receive data and control instructions from the processor 308.


One or more memory devices 320 coupled to the processor 308 store executable instructions for the processor 308. The memory device(s) 320 can also store data, of course, such an identifier for the vehicle.


When the program instructions stored in the memory device(s) 320 are executed, the cause the processor 308 send control signals to the LF transmitter and RF receiver. Control signals sent to the LF transmitter cause it to generate various types of signals, which are formatted using a protocol specified by the vehicle's manufacturer.


The stored instructions also cause the processor 308 to receive information from the RF receiver, which can include tire pressure identifiers and tire operating condition data, such as an inflation pressure for each of the vehicle's tires.


Data that represents tire operating conditions, such as tire pressure, is provided by the processor 308 an instrument panel display 318, which is coupled to the processor.


The term “protocol” refers to rules that describe how to effecuate the transfer of data between devices. A protocol thus specifies the format of the data. A protocol also specifies the data signals that start, control and end the transfer set of data.


Examples of communication protocols that may be used with a tire pressure monitoring system include the frequency and timing of transmissions from a tire pressure sensor 200 to the monitor 300; the format of a transmission, such as what constitutes a “1” or a “0;” a modulation type, such as amplitude or frequency modulation, error detection and/or correction, a synchronization pattern, and so forth.



FIGS. 6A-6C depict the same LF message 600 formatted using three (3) different LF protocols. The LF messages are denominated as LF Command 1, LF Command 2 and LF Command 3.



FIGS. 6D-6F depict the same RF message 650 formatted using three different RF protocols. The RF messages formatted with different protocols are denominated as RF protocol message A, RF Protocol message B and RF protocol message C.


In FIG. 6A, the first protocol requires message content 600A to be preceded by a synchronization segment 604 and an identifier or “ID” 606 of a particular sensor to which the message 600 is addressed. The data of the message is modulated using amplitude shift keying (ASK) and encoded using an inverted Manchester encoding. In FIG. 6B, the message 600B is ASK modulated but encoded using a biphase encoding. In FIG. 6C, the LF message 600C is modulated using ASK but preceded by a message preamble 614 and.


Referring now to FIG. 6D, an RF message 650A to be sent by the sensor 200 to a pressure monitor 300, is preceded by a start bit 652, a message preamble 654, a sensor identifier 656, a status field 658 and followed by a check sum 660. The message 650 is modulated using frequency shift keying (FSK), and biphase encoded.


In FIG. 6E, the same RF message is modulated using FSK but encoded using inverted Manchester encoding, The message 650B is preceded by a preamble 670 but followed by a sensor identifier 672, a status field 674 and a checksum 676.


In FIG. 6F, the RF message 650C is ASK modulated and biphase encoded. The message is preceded by a preamble 672 but followed by a sensor identifier 674, a status field 676 and a checksum 678.



FIG. 7 depicts how the sensor 200 shown in FIG. 2 receives LF messages formatted using various protocols and outputs an RF message that is formatted with a protocol selected using the LF message protocol. More particularly, in FIG. 7, the reception of the LF message 600A shown in FIG. 6A, causes the sensor 200 to subsequently transmit two RF messages, i.e, a first message 650A using both RF protocol A and a second message 650B.


Referring again to FIG. 2, the tire pressure sensor 200 is configured to work with virtually any type of vehicle tire pressure monitor 300 by programming the processor 220 for the sensor 200 to be able to receive an LF message, compare the received message to exemplars or samples of LF messages that were formatted using various manufacturers' protocols and from such a comparison identify a particular protocol that used to format or “modulate” the LF signal that was received from a vehicle tire pressure monitor 300. Stated another way, the sensor 200 is provided with the ability to “learn” an RF message protocol to use to send out messages to a vehicle by listening to an LF message that was sent from a vehicle 100. The sensor 200 is thus provided with the ability to identify from the LF message protocol, the type of RF message protocol that should be used to send tire information to the vehicle. Stated another way, the sensor 200 learns the RF message protocol required by the vehicle's manufacturer by analysis of the LF message protocol that it receives.


By executing various pre-determined instructions for the processor 220 that are stored in the memory device 230, an essentially unintelligible LF message received by the sensor 200, such as a message that “polls” a tire pressure sensor, is resolved by the processor 220 into component parts or “parsed.” The components of the received LF message that can be matched with or correlated to corresponding or the same parts of the same type of message created using different types of protocols, and which are stored in the memory device 230 for the processor as reference LF messages 234A, 234B, enable a protocol that was used to modulate the received LF polling message to be unambiguously identified by the processor 220.


By way of example, an LF polling message received by the sensor 200 is compared to samples of polling messages 234 that were formatted or created using various different protocols used by a various different vehicle manufacturers, and which are stored in the memory device 230. A known good polling message formatted with a particular protocol and that matches a received LF polling message, effectively identifies the LF protocol that was used to format the received LF message. Known LF message protocols that are used by various manufacturers and which are stored in the memory device 230 as exemplars 234 are indexed in the memory device 230 to corresponding RF message protocols used by the same manufacturer. Identifying the LF message protocol thus identifies an RF message protocol to be used by the sensor 200 in order for it to conduct subsequent RF communications with the vehicle.


After a protocol used to create an LF is determined, subsequent RF communications sent to the vehicle by the sensor 200 are formatted by the processor 220 preferably, but not necessarily, using only the vehicle-appropriate protocol and preferably only as often as is required by vehicle's manufacturer, significantly reducing the number of unnecessary and battery-wasting transmissions. Unlike “generic” prior art tire pressure sensors, no tire pressure message needs to be repeated using other protocols; no switches or other devices are used to identify or input a communications protocol or enter types of protocols.



FIG. 4 depicts steps of a method 400 by which the non-specific or generic tire pressure sensor 200 depicted in FIG. 2 is autonomously configured, i.e. configured automatically by itself, for use with a particular type of vehicle, and which requires tire pressure information signals to be exchanged between the tire sensors and the vehicle, according to a particular manufacturer's communications protocol.


The first step 402 of the method 400 is of course the reception of an LF signal by the pressure sensor 200 at an LF receiver 202. As shown in FIG. 2, the LF receiver 202 is coupled to a processor 220 via a bus 222, which enables the processor to receive the LF signal from the receiver 202. In one alternate embodiment of the method 400, the received LF message is stored by the processor 220 at step 404 in one or more memory locations of the memory device 230.


At steps 406 and 408, a received LF message is parsed and its components analyzed to determine a particular protocol or “modulation scheme” by which the received LF message was created. Known good exemplars of LF messages that were created using various different protocols are stored in the sensor's memory device 230 as a database or list. Using any appropriate comparison technique, database entries are compared to the received LF message until a database entry is determined to match the received LF message. Stated another way, each database entry is compared to a received LF message until a database entry is determined to match the structure or protocol of the received LF message.


In the preferred embodiment, each database entry, i.e., each exemplar 234 stored in memory 230 is correlated to a particular type of protocol to be used to communicate with a particular type of vehicle. Once the protocol of a received LF message is determined from the database entries, the protocol to be used with subsequent communications for the same vehicle is obtained from the database. More particularly, an RF message protocol is obtained from or determined from the exemplars 234.


At step 410 and after an LF protocol has been identified, the method proceeds to step 412 where the sensor 200 generates and sends an identification message to the vehicle. In most pressure sensors, the first message sent by the sensor 200 is an “ID” or identification message includes a unique, numeric identifier for the sensor 200, i.e., a number that uniquely and unambiguously identifies the sensor 200 to the monitor 300. The sensor id 414 is preferably stored in the memory device 230 coupled to the processor 220 and for instrument panel display purposes, the ID enables the monitor 300 to track the pressure inside each tire regardless of the wheel well in which the tire is located.


After the sensor ID is sent, the sensor 200 is able to monitor tire conditions and report them to the monitor 300. Step 420 thus depicts tire conditions being monitored and reported to the monitor 300.



FIG. 5 depicts steps of a method by which the monitor 300 can initialize a sensor 200 or selectively communicate with each sensor on a vehicle using the vehicle's particular communications protocol. FIG. 5 also depicts a method of locating a particular sensor 200 at a particular vehicle wheel.


Referring first to FIG. 3, the tire pressure monitor 300 comprises an antenna switch 304, which can selectively connect the LF transmitter 306 to different LF antennae 302 under the control of the processor 308 in the monitor 300. In FIG. 5, at step 502 a particular LF antenna located inside a particular wheel well 302 is “energized” or connected to the LF transmitter by the processor for the monitor 300.


At step 504, a polling message is generated by an LF transmitter in the monitor 300 responsive to control signals sent to the LF transmitter by the processor and broadcast from the particular LF antenna to which the transmitter was connected by step 502. At step 506, and after the sensor 200 in the wheel well 302 having the energized antenna identifies the polling message protocol, an identifier (ID) for the sensor, which is transmitted by the sensor 200, is received at the sensor 300 as an RF message.


At steps 508 and 510, the located and identified sensor 200 is “in service” and reports tire pressure to the monitor 300 as required by the vehicle's manufacturer. Having learned the vehicle's RF message protocol, no extraneous messages are sent by the sensor 200 nor are such messages received by the monitor 300.


Finally, one embodiment of the sensor 200 is configured and arranged to be usable with vehicles having tire pressure monitoring systems but which do not transmit LF initialization signals. Some such vehicles “learn” a tire pressure sensor's RF transmission protocol from RF signals transmitted by the sensor. In such an embodiment of the sensor 200, program instructions for the processor 220 cause the processor to assume that the sensor 200 is installed on an auto-learn vehicle when an LF signal is not received within a predetermined amount of time. After the passage of a some pre-determined period of time, the sensor 200 autonomously transmits RF messages, using one or more protocols selected from the memory device 230. The protocol(s) of the transmitted RF message are thereafter adopted by the vehicle for subsequent use.


The foregoing description is for purposes of illustration only. The true scope of the invention is set forth in the following claims.

Claims
  • 1. A tire pressure sensor for a motor vehicle having a tire pressure monitor, the tire pressure sensor comprising: a non-Bluetooth wireless receiver located inside a vehicle tire, the non-Bluetooth wireless receiver being configured to: receive from the vehicle tire pressure monitor, a first, non-Bluetooth low-frequency (LF) wireless message when the non-Bluetooth wireless receiver is inside the vehicle tire, the received first non-Bluetooth message being formed using one of a plurality of different types of first wireless message protocols;while the non-Bluetooth wireless receiver is inside the tire, identify a particular type of wireless message protocol that was used to form the received first non-Bluetooth wireless message; andgenerate a non-Bluetooth output message to a non-Bluetooth wireless transmitter co-located with the non-Bluetooth wireless receiver while the non-Bluetooth wireless receiver is inside the vehicle tire, the non-Bluetooth output message from the non-Bluetooth wireless receiver comprising an identifier, which identifies the non-Bluetooth wireless message protocol by which the received non-Bluetooth first wireless message was formed by the vehicle tire pressure monitor; anda non-Bluetooth wireless transmitter co-located with the non-Bluetooth wireless receiver inside the vehicle tire, the non-Bluetooth wireless transmitter being coupled to the non-Bluetooth wireless receiver, and configured to transmit to the tire pressure monitor from inside the tire, a second, non-Bluetooth, high-frequency message containing tire information using a second non-Bluetooth wireless message protocol, which is selected in response the identifier for the tire pressure sensor;wherein the reception of the first non-Bluetooth message by the non-Bluetooth wireless receiver, the identification of the first non-Bluetooth wireless message protocol by the non-Bluetooth wireless receiver and selection of the second non-Bluetooth wireless message protocol by the non-Bluetooth wireless receiver takes place inside the tire.
  • 2. The tire pressure sensor of claim 1, wherein the non-Bluetooth wireless transmitter is configured to transmit the identifier to the vehicle tire pressure monitor autonomously.
  • 3. The tire pressure sensor of claim 1, further comprising a tire operating condition sensing device operatively coupled to the non-Bluetooth wireless transmitter, the tire operating condition sensing device providing signals that represent an operating condition of a tire, wherein the non-Bluetooth wireless transmitter is configured to receive information from the operating condition sensing device and to transmit the information on a radio frequency (RF) signal, which is formed using a non-Bluetooth message protocol identified by said first non-Bluetooth wireless message from the non-Bluetooth wireless receiver.
  • 4. The tire pressure sensor of claim 3, wherein the non-Bluetooth wireless transmitter transmits the operating condition information on a second radio frequency band, using the protocol identified by the non-Bluetooth wireless receiver and only as often as is required by a manufacturer of the vehicle.
  • 5. The tire pressure sensor of claim 1, wherein the non-Bluetooth wireless receiver is additionally configured to receive a second non-Bluetooth wireless signal, which is formed using one of a plurality of different types of protocols and upon receipt of said second wireless signal, initialize said non-Bluetooth wireless transmitter.
  • 6. The tire pressure sensor of claim 1, wherein the non-Bluetooth wireless receiver is a non-Bluetooth low-frequency, short-range wireless signal receiver, the first wireless signal is a short-range, low-frequency signal and wherein the non-Bluetooth wireless transmitter is a high-frequency radio frequency transmitter.
US Referenced Citations (374)
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 Niekerk et al. Oct 2002 B2
6469621 Vredevoogd 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
9381777 Yu et al. Jul 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 Pacsai 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 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 Kaleal 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
20130038443 Deniau Feb 2013 A1
20130282231 Farr et al. Oct 2013 A1
20140002258 Chen Jan 2014 A1
20140139332 Mouchet May 2014 A1
20150015389 McIntyre et al. Jan 2015 A1
20150015390 McIntyre et al. Jan 2015 A1
20160303925 Liu Oct 2016 A1
Foreign Referenced Citations (86)
Number Date Country
1521027 Aug 2004 CN
103503353 Jan 2014 CN
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
1013483 Jun 2000 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
2002064404 Feb 2002 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
2003016079 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 (34)
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 dated Oct. 15, 2008, for Application No. PCT/US2008/069006.
International Preliminary Report on Patentability dated Jan. 14, 2010, for Application No. PCT/US2008/069006.
Chinese Office Action dated Apr. 19, 2011, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Chinese Office Action (second) dated Feb. 16, 2012, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Chinese Office Action (third) dated Oct. 10, 2012, for Chinese Application 200880023390.7 (Corresponding to PCT/US2008/069006).
Japanese Office Action dated 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.).
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.).
Search Report dated Aug. 20, 2015, from GB Patent Application No. GB1503824.3.
International Search Report and Written Opinion dated Sep. 28, 2012, from corresponding International Patent Application No. PCT/US2011/047108.
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.
Translation of Abstract of KR1020070040883A.
Machine Translation of RU2423246 C1.
Related Publications (1)
Number Date Country
20170036499 A1 Feb 2017 US
Provisional Applications (1)
Number Date Country
62200528 Aug 2015 US