Apparatus and method for activating a localization process for a tire pressure monitor

Information

  • Patent Grant
  • 9024743
  • Patent Number
    9,024,743
  • Date Filed
    Tuesday, August 9, 2011
    13 years ago
  • Date Issued
    Tuesday, May 5, 2015
    9 years ago
Abstract
A receiver device is tuned to monitor for first transmissions at a first time according to a first criterion and to monitor for second transmissions at a second time according to a second criterion. When the receiver device initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, the recognized transmission is verified as being valid. When the transmission is recognized as valid, a transmission apparatus is activated to transmit an indication to a receiver so that a localization process can be executed.
Description
CROSS REFERENCES TO RELATED APPLICATIONS

“Tire Pressure Monitoring Apparatus and Method” having application Ser. No. 13/206,225;


“Protocol Arrangement in a Tire Pressure Monitoring System” having application Ser. No. 13/206,314; and


“Protocol Misinterpretation Avoidance Apparatus and Method for a Tire Pressure Monitoring System” having application Ser. No. 13/206,358;


all of which being filed on the same date as the present application and all of which having their contents incorporated herein by reference in their entireties.


FIELD OF THE INVENTION

The field of the invention relates to tire pressure monitoring devices that utilize potentially different transmission protocols.


BACKGROUND

The pressure and other operating parameters of tires are important concerns when operating a vehicle. Not only can incorrect tire pressure (or the incorrect setting of some other tire parameter) lead to inefficient vehicle operation (e.g., the waste of fuel and other problems leading to higher operating costs), but too low a tire pressure (or an inadequate value for some other tire parameter) can lead to safety problems such as accidents. It is difficult and sometimes time-consuming for users to manually measure tire pressure (or other parameters) with a pressure gauge (or other instruments). Consequently, automatic tire pressure monitoring systems have been devised and these systems free the user from manually making tire measurements.


An automatic tire pressure monitoring device typically mounts to a wheel within the tire and wirelessly transmits information indicative of conditions within the tire. The transmissions and the order of information are typically defined by a protocol corresponding to a receiver within the vehicle. Once the receiver receives the information, the information can be processed and presented to a user. For instance, a user can be warned when the pressure in their tires is too high or too low and thus avoid safety problems. Each automobile manufacturer typically has a unique, preferred, and pre-defined protocol to meet application specific needs and applications. Consequently, receivers using one manufacturers' protocol are not responsive to transmitters operating according to other manufacturers' protocols.


Tire pressure monitors also typically need to be activated and/or initialized. Various portable tools can be used for this purpose. Unfortunately, a particular type of tire pressure monitoring device needs to operate with a tool that is compatible with that device. A user has to ensure that the two devices are compatible, or the tire pressure monitor cannot be initialized and/or activated. Consequently, a user needs to worry about compatibility issues and under some circumstances (e.g., when a mismatch is made by the user) the tire pressure monitor cannot be initialized. This results in user dissatisfaction with these previous approaches.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 comprises a block diagram of a tire pressure monitoring system according to various embodiments of the present invention;



FIG. 2 comprises a flowchart showing one example of an approach for initializing and/or activating a tire pressure monitor according to various embodiments of the present invention;



FIG. 3 comprises a flowchart showing one example of an approach for initializing and/or activating a tire pressure monitor according to various embodiments of the present invention;



FIG. 4 comprises a block diagram of a tire monitor according to various embodiments of the present invention;



FIG. 5 comprises a block diagram of timeline showing sensing patterns for a receiver device according to various embodiments of the present invention.





Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. 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 tire pressure monitoring device can receive and recognize activation signals from a plurality of activation sources, each of these sources potentially transmitting according to different formats, different data contents, and/or different protocols. Consequently, according to the present approaches a user does not have to ensure that a particular activation device is compatible with a particular tire pressure monitor. In fact, the user can simply install the tire pressure monitor described herein and activate the device without worrying about compatibility. In one aspect, the approaches described herein can achieve compatibility in the sense that all activation devices can be accommodated. In another aspect, a subset of all possible activation devices can be accommodated, such as the most popular devices to mention one example. By “activation” and as used herein it is meant that a process is executed upon the tire pressure monitor being “activated.” For example, a localization process can be executed. In another example, a control program that transmits RF frames can be executed. Other examples are possible.


In many of these embodiments, a receiver device is tuned to monitor first transmissions at a first time according to a first criterion and to monitor transmissions at a second time according to a second criterion. When the receiver device initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, the recognized transmission is verified as being valid or authentic. When the transmission is recognized as valid or authentic, an indication is sent to a receiver (e.g., a control unit in a vehicle) and this is effective to activate a localization process that in turn ensures that tire pressure monitoring information can be correlated to a particular tire (with a known identifier) at a known location.


In one aspect, the first criterion describes a low frequency (LF) sinusoidal waveform and the second criterion describes a low frequency (LF) transmission of a predetermined data pattern. Other examples are possible. In another aspect, the verifying includes verifying that the recognized transmission is received for a predetermined time period.


In other aspects, the sensitivity of the receiver device in the monitor can be dynamically adjusted. For example, it can be lowered when the vehicle is not moving and increased when the vehicle is moving.


The transmission of the tire pressure information may be accomplished in a variety of different ways. For instance, a control program may be executed to transmit the tire pressure information according to each of a plurality of communications formats incorporated into the control program and not according to a manufacturers' code. Transmissions may be made according to each and every possible manufacturers' protocol or a subset of these protocols. Other examples of transmission approaches are possible.


In others of these embodiments, an apparatus (e.g., a tire pressure monitor) includes a receiver device, a transmitter apparatus, and a controller. The receiver device is configured to receive first transmission and second transmissions from an activation source or sources.


The controller is coupled to the transmitter apparatus and the receiver device. The controller is configured to tune the receiver device to monitor first transmissions at a first time according to a first criterion and to monitor transmissions at a second time according to a second criteria. The controller is further configured to when the receiver device initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, to verify that the recognized transmission is valid. The controller is still further configured to when the transmission is recognized as valid, send an indication to a receiver so that a localization process can be accomplished. Once the localization process is accomplished, tire pressure information that is sent can be associated with a monitor at a known location.


Thus, approaches are provided where a tire pressure monitoring device can receive and recognize activation signals from a plurality of sources, each of these sources potentially transmitting according to different formats, different data contents, and/or different protocols. Consequently, according to the present approaches a user does not have to ensure that a particular activation device is compatible with a particular tire pressure monitor and the user can simply install the monitor and automatically activate the localization process associated with the device without concerns about compatibility.


Referring to FIG. 1, a tire pressure monitoring system 100 is shown assembled within a vehicle 102. The system 100 includes a receiver 106 that receives communications from tire pressure monitoring devices 104 (“monitors”) assembled within each of the vehicle's tires 108. The receiver 106 may be any communication device configured to receive any type of transmitted communication but tuned to only recognize some of these communications. In one example, these communications are radio frequency (RF) communications, but other types of communications are also possible.


Although the device 104 is described as a tire pressure monitoring device herein, it will be appreciated that this device can gather and transmit other types of information related to the tire in addition to or in place of tire pressure information. For example, the information can include temperature information, acceleration information, or information related to the wear of the treads of the tire. Appropriate sensors or sensing devices may be used to obtain this information. Other examples of information may also be gathered by the tire pressure monitoring device 104.


Each of the tire pressure monitoring devices 104 are assembled within the tires 108 of the vehicle 102 and, as mentioned, communicate information indicative of conditions within the tires 108 to the receiver 106. These conditions include temperature, pressure, and/or any other desired information that aids in the evaluation of tire conditions. Other examples of conditions may also be sensed.


The system 100 includes the tire pressure monitoring devices 104 that in this example includes a memory device 126. The memory device 126 is utilized for the storage of a control program 128. The control program 128, once compiled and executed, transmits sensed information (e.g., tire pressure information) according to one or more protocols (or formats) that govern operation and communication between the tire pressure monitoring device 104 and the receiver 106. Examples of communication protocols that may be used include protocols that specify the frequency and timing of transmissions from the tire pressure monitoring device 104 to the receiver 106 or the format of transmission (such as what constitutes a “1” or a “0,” modulation type, error detection and/or correction content, synchronization pattern, and so forth to name but a few examples in these regards). Tire pressure monitoring information may be transmitted according to the protocols sequentially (e.g., using the same antenna) or at the same time (e.g., using different antennas). No separate manufacturers' codes are used in making the transmissions. Once the control program is compiled, the protocols that have been selected cannot be changed without changing (e.g., editing, compiling, and installing anew) the control program 128. In one aspect, the control program 128 is compiled and stored in the memory 126 during manufacturing.


In one aspect, the control program 128 may be executed continuously whenever the vehicle is moving. The control program 128 may also be executed when the vehicle is not moving, but only when the sensor is activated externally (i.e., via LF or grounding of a pin on the ASIC during manufacturing). At other times, it may not be executed. However, learning the identities of the devices 104 and/or determining where each device is located (“localization”, e.g., front left, front right, and so forth) may be accomplished by using an activation device 120. The activation device 120 emits a wireless signal 122 (e.g., an LF signal) that is received by a corresponding one of the tire pressure monitoring devices 104. Receipt of the wireless signal 122 causes the device 104 to transmit identity information and also indicate to the receiver 106 that the device 104 has received an LF signal and that the localization process can occur. When the vehicle is moving, LF transmitters (e.g., antennas) may transmit LF signals (in place of the device 120). When moving, the RF signals are periodically being transmitted and when the device 104 finds an LF signal, it so indicates to the receiver 106 (e.g., by flipping a bit in the RF transmission). Once this indication is received, localization can be completed (e.g., this process may occur for a predetermined amount of time to ensure that the device 104 is correctly localized). Once localization is complete, tire pressure information can be associated with a known tire. It will be appreciated that in other examples, the control program may itself be activated by the LF signals.


The activation device 120 includes a series of selectable buttons 124 (or other types of actuators) that are actuated by a user to indicate that they wish to activate the tire pressure monitoring device. Although the example device 120 is shown with buttons, other display and selection configurations, such as touch screens, switches or some other selection interface may be used as will be appreciated by those skilled in the art. Accordingly, installation of the multi applications tire pressure monitoring devices 104 optionally includes the initial step of physically activating the tire pressure monitoring devices 104 within each of the corresponding tires 108 or activate a localization process that allows tire pressure data to be associated with particular tires.


If an activation device is used, the activation device 120 is placed proximate to each of the tire pressure monitoring devices 104 to send a signal 122. In one example, the signal 122 is a low frequency transmission received by the proximate tire pressure monitoring device 104.


The devices 104 operate with the receiver 106 in the vehicle and the receiver 106 typically has a display (or some sort of user interface) that is configured to alert the driver when the tire pressure falls below a predetermined threshold value. As mentioned, once physically installed in the tire, the devices 104 are first “learned” by the control unit. During this process, the receiver 106 determines the particular identifiers and during or after learning, a localization process may be executed in which each of the devices 104 is associated with a particular tire.


During normal operation (after the sensors are learned and localized and the vehicle is moving), the device 104 senses the tire pressure and sends a radio frequency (RF) signal to the receiver 106 indicating the tire pressure. The receiver 106 can then determine if a pressure problem exists. If a problem exists, the user can be alerted so that appropriate action can be taken. As mentioned, this is all accomplished by use of a control program that is compiled, translated, and/or assembled before it is executed. In one aspect, once compiled the structure of the control program (e.g., the protocols selected) can not be changed. Also, nothing external to the device can be input into this control program to change the structure of the control program once the control program (and the protocols specified in the control program) is compiled. It will be appreciated that although many of the examples described herein refer to a control program being executed to transmit RF frames with tire pressure information, that other approaches can also be used. For instance, systems that utilize manufacturers' codes can also have their monitors localized according to the approaches described herein.


The devices 104 can also receive indications as to whether the vehicle is moving. For example, a signal can be sent from the control unit of the vehicle with this information.


Referring now to FIG. 2, one example of an approach for operating a tire pressure monitoring system is described. At step 201, it is determined if the user is attempting to initialize the sensor. If the answer is affirmative, step 202 is performed and if the answer is negative, step 210 is performed. At step 202, LF signals are received from an external activation source. The external source may be a portable or fixed device. The received signals may be sinusoidal signals of a predetermined frequency (CW) or be modulated to include information (e.g., bytes of information). Signals other that LF signals may also be used. The device verifies that the signals are what was expected. When verified, an indicator is transmitted to a receiver (e.g., a control module) that informs the receiver that the monitor has received and verified LF reception.


In another aspect, the type of signals received may affect the operation of the monitor. For instance if LF CW signals are received, bursts have certain formats may be sent. Other examples are possible.


At step 204 and upon verification, the learning process and localization process are performed. Learning refers to obtaining the identifier of a monitor and localization refers to determining where the monitor is located (e.g., front right wheel, front left wheel and so forth). The indicator transmitted by the monitor may be an RF signal of a burst of frames whereby selected ones of the frames include tire pressure information and where a specified predetermined bit is flipped (from a “0” to a “1”, or vice versa) to indicate LF was verified at the monitor. It will be appreciated that the monitor may attempt to verify reception of LF signals a predetermined number of times to ensure that the signal is valid.


At step 208 it is determined if a timeout has occurs (e.g., has a certain period of time passed so that RF transmissions can be halted). If the answer is affirmative, at step 212 transmissions are halted. If the answer is negative, execution continues at step 210 where it is determined whether the vehicle is moving.


If the answer at step 210 is negative, execution continues at step 208 as has been described above. If the answer is affirmative, then at step 214 LF signals are received from LF antennas at the vehicle and are verified as being valid activation signals.


At step 216, an indicator is sent to the receiver to indicate that the monitor has received valid LF signals and the localization process is activated at the receiver (e.g., the vehicle controller). At step 218, the RF transmissions are made and tire pressure information can be associated with a particular monitor at a known location. At step 220, it is determined if the vehicle is stopped, in one example if it has been stopped for a predetermined period of time (e.g., 15 minutes). If the answer is negative, execution continues at step 218 and if the answer is affirmative execution continues at step 212.


Referring now to FIG. 3, one approach for activating a tire pressure monitor is described. At step 302, a receiver device is tuned to monitor first transmissions at a first time according to a first criterion and to monitor transmissions at a second time according to a second criterion. In one aspect, the first criterion describes a low frequency (LF) sinusoidal waveform and the second criterion describes a low frequency (LF) transmission of a predetermined data pattern. In another aspect, the verifying includes verifying that the recognized transmission is received for a predetermined time period.


At step 304, when the receiver device initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion. At step 306, the transmission is recognized as valid and at step 308 an indication is sent to the receiver that the monitor has received a valid LF activation signal and that the localization process can be executed.


After step 308 is accomplished, the tire pressure information can be associated with a known monitor that is at a known location. Consequently, reports can be generated to the user that alert the user when a tire becomes deflated, for example. It will be appreciated that in one aspect tire pressure information can be transmitted periodically when the vehicle is moving. However, it is only after localization is completed that this information can be linked with a monitor that resides at a known location. As used herein, “monitor” refers to the tire pressure monitor such as one of the devices 104 in FIG. 1 or the device 400 of FIG. 4.


Referring now to FIG. 4, an apparatus 400 (e.g., a tire pressure monitor) for initializing a tire pressure monitor includes a receiver device 402, a transmitter apparatus 404, and a controller 406. The receiver device 402 is configured to monitor for first transmission and second transmissions having predetermined formats (that may be present in activation signals 405) received from an activation source or sources 408 via the antenna 403.


The controller 406 is coupled to the transmitter apparatus 404 and the receiver device 402. The controller 406 is configured to tune the receiver device 402 using control signals 407 to monitor for first transmissions at a first time according to a first criterion and to monitor for second transmissions at a second time according to a second criterion. The controller 406 is further configured to when the receiver device 402 initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, to verify that the recognized transmission is valid (e.g., it matches predetermined requirements such as being of a particular frequency, having a particular value, having a predetermined power level, and so forth). The controller 406 is still further configured to when the transmission is recognized as valid, activate the transmission apparatus 404 to transmit an indicator (e.g., a flipped bit in an RF signal 411) via the antenna 415. This information 411 is transmitted to a vehicle receiver or controller 420 where it may be further processed as described above to initiate the localization process. Although the device 400 may be periodically broadcasting tire pressure information when the vehicle is moving (e.g., in bursts of frames transmitted every approximately 17 seconds) it is only after the localization process is complete that the tire pressure information can be associated with a known tire.


In another aspect, the sensitivity of the LF reception by the receiver device can be adjusted, i.e., it has a dynamic sensitivity. For example, the sensitivity can be lowered when the vehicle is at rest. This may be done, for example, so that when the vehicle is stopped spurious LF signals (e.g., caused by other electronic devices) are not confused as being valid signals. The sensitivity can be increased when the vehicle is moving since there is less of a chance of detecting spurious signals when the vehicle is moving down a roadway.


Referring now to FIG. 5, one example of how a receiver device (e.g., device 402 in FIG. 4) in a monitor is tuned is described. FIG. 5 shows an x-axis that represents time and the time units are expressed in arbitrary units (0, 1 . . . 23). Each time period includes the criteria that a controller (e.g., controller 406 of FIG. 4) has tuned a receiver device (e.g., device 402 of FIG. 4) to listen. For example, between time 0 and 1, the receiver device in the monitor is tuned to listen for LF signals that have a data content of byte 1 and byte 2. Between time 1 and 2, the receiver device in the monitor is tuned to listen for a low frequency (LF) sinusoidal signal (CW). It will be appreciated that these are examples only and that other types of signals can be listened for and in different orders.


Between times 8 and 9, the controller identifies the received transmission as an LF CW transmission. Between time 9 and 12 the receiver device in the monitor is configured to verify this is a valid transmission by listening for the LF CW pattern. For example, the receiver device in the monitor ensures that this is not a noise signal by verifying a constant frequency and/or amplitude to take one example, At time 12, the transmission of RF signals (e.g., using a control program) is enabled. The receiver device in the monitor then alternates between checking/listening for the byte pattern and LF CW patterns described above.


At times 16 and 17, the controller identifies the received transmission as one of the byte patterns byte 1 or byte 2. Between time 17 and 20 the receiver is configured to verify this is a valid transmission by listening for byte 1 or byte 2. For example, the receiver device ensures that this is not a noise signal by verifying that the values of byte 1 or byte 2 do not change. At time 20, the transmission of RF signals (e.g., using a control program) is enabled. The receiver device then alternates between checking for the byte pattern and LF CW patterns described above.


It will be appreciated that in this example the LF CW may be transmitted by one type of activation device (e.g., from a first manufacturer) while the LF byte transmissions are transmitted by another type of activation device (e.g., from a second manufacturer). However, these approaches are applicable to any number of possible received formats and are not limited to two as shown here. The byte patterns may be any byte pattern as is known to those skilled in the art.


It should be understood that any of the devices described herein (e.g., the programming or activation devices, the tire pressure monitoring devices, 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.


Those skilled in the art will recognize that a wide variety of modifications, alterations, and combinations can be made with respect to the above described embodiments without departing from the spirit and scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the scope of the invention.

Claims
  • 1. A method of initializing a tire pressure monitor, the method comprising: tuning a receiver device at a wheel unit to monitor for first transmissions from an initiation source during a first predetermined time period, the first transmissions being made according to a first criterion;tuning the receiver device at the wheel unit to monitor for second transmissions from the initiation source during a second predetermined time period according to a second criterion and not according to the first criterion, the second criterion being different than the first criterion;when the receiver device at the wheel unit initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, at the receiver device at the wheel unit verifying that the recognized transmission is valid by comparing the recognized transmission to an expected information pattern;in response to verifying at the receiver device the recognized transmission is valid, sending an indication from the receiver device to a central receiver unit in the vehicle so that a localization procedure can be executed.
  • 2. The method of claim 1 wherein the first criterion describes a low frequency (LF) sinusoidal waveform.
  • 3. The method of claim 2 wherein the second criterion describes a low frequency (LF) transmission of a predetermined data pattern.
  • 4. The method of claim 1 wherein the verifying comprises verifying that the recognized transmission is received for a predetermined time period.
  • 5. The method of claim 1 further comprising transmitting the tire pressure information.
  • 6. The method of claim 5 wherein the transmitting comprises executing a control program to transmit the tire pressure information according to each of a plurality of communications formats incorporated into the control program and not according to a manufacturers′ code.
  • 7. The method of claim 1 further comprising transmitting one of the first transmissions or the second transmissions from a portable tool.
  • 8. The method of claim 1 further comprising transmitting one of the first transmissions or the second transmissions from an antenna at a vehicle.
  • 9. The method of claim 1 further comprising dynamically adjusting the sensitivity of the receiver device.
  • 10. The method of claim 9 wherein the sensitivity is lowered when the vehicle is at rest and is increased when the vehicle is moving.
  • 11. An apparatus for initializing a tire pressure monitor, the apparatus being disposed at a wheel unit, the apparatus comprising: a receiver device, the receiver device configured to receive first transmission and second transmissions;a transmission apparatus;a controller coupled to the transmitter apparatus and the receiver device, the controller configured to tune the receiver device to monitor for first transmissions from an initiation source during a first predetermined time period according to a first criterion and configured to tune the receiver device to monitor for second transmissions from the initiation source during a second predetermined time period according to a second criterion and not according to the first criterion, the second criterion being different than the first criterion, the controller further configured to when the receiver device initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, to verify that the recognized transmission is valid by comparing the recognized transmission to an expected information pattern, the controller further configured to when the transmission is recognized as valid, transmit an indicator to a receiver in a vehicle so that a localization process can be executed to determine a location of the apparatus.
  • 12. The apparatus of claim 11 wherein the first criterion describes a low frequency (LF) sinusoidal waveform.
  • 13. The apparatus of claim 11 wherein the second criterion describes a low frequency(LF) transmission of a predetermined data pattern.
  • 14. The apparatus of claim 11 wherein the controller is configured to verify that the recognized transmission is received for a predetermined time period.
  • 15. The apparatus of claim 11 further comprising transmission apparatus is configured to transmit the tire pressure information.
  • 16. The apparatus of claim 15 wherein the controller is configured to execute a control program to transmit the tire pressure information according to each of a plurality of communications formats incorporated into the control program and not according to a manufacturers′ code.
  • 17. The apparatus of claim 11 wherein the first transmissions or the second transmissions are received from a portable tool.
  • 18. The apparatus of claim 11 wherein the first transmissions or the second transmissions are received from an antenna at a vehicle.
  • 19. 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 initializing a tire pressure monitor information, the method comprising: tuning a receiver device at a wheel unit to monitor for first transmissions from an initiation source during a first predetermined time period according to a first criterion;tuning the receiver device at the wheel unit to monitor for second transmissions from the initiation source during a second predetermined time period according to a second criterion and not according to the first criterion, the second criterion being different than the first criterion;when the receiver device at the wheel unit initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion, verifying that the recognized transmission is valid by comparing the recognized transmission to an expected information pattern;in response to verifying at the receiver device the recognized transmission is valid, sending an indication from the receiver device to a receiver in a vehicle so that a localization procedure can be executed.
  • 20. A computer usable non-transitory medium having a computer readable program code embodied therein, said computer readable program code adapted to form the following means when executed on a computer: means for tuning a receiver device at a wheel unit to monitor for first transmissions from an initiation source during a first predetermined time period according to a first criterion and to monitor for second transmissions from the initiation source during a second predetermined time period according to a second criterion and not according to the first criterion, the second criterion different than the first criterion;means for verifying that the recognized transmission is valid, when the receiver device at the wheel unit initially recognizes one of the first transmissions being transmitted according to the first criterion or the second transmissions being transmitted according to the second criterion;means for sending an indication to a receiver so that a localization procedure can be executed, when the transmission is recognized as valid by comparing the recognized transmission to an expected information pattern.
US Referenced Citations (343)
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
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 Bergerhoff et al. Jan 2004 B2
6693522 Tang et al. Feb 2004 B2
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
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
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
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
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
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
20030228879 Witkowski Dec 2003 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
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
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
20070063814 Olson et al. Mar 2007 A1
20070069947 Banet et al. Mar 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
20080165688 Beshai et al. Jul 2008 A1
20080173082 Hettle et al. Jul 2008 A1
20080177441 Marlett et al. Jul 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
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
20090179747 Lin et al. Jul 2009 A1
20090184815 Suzuki et al. Jul 2009 A1
20090207859 Beshai et al. Aug 2009 A1
20090231114 Yu Sep 2009 A1
20090267751 Kaleal Oct 2009 A1
20090291710 Jheng et al. Nov 2009 A1
20090310477 Lee et al. Dec 2009 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
20120147184 Siann et al. Jun 2012 A1
20120185110 Deniau et al. Jul 2012 A1
20120274461 Colombo et al. Nov 2012 A1
Foreign Referenced Citations (62)
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 Jun 2004 EP
1494877 Jan 2005 EP
1547827 Jun 2005 EP
1562162 Aug 2005 EP
1026015 May 2006 EP
1352763 Apr 2008 EP
1340629 Jun 2008 EP
2387032 Oct 2003 GB
2420415 May 2006 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
2003025817 Jan 2003 JP
2004-145474 May 2004 JP
2005289116 Oct 2005 JP
2006015832 Jan 2006 JP
2007200081 Aug 2007 JP
2007283816 Nov 2007 JP
2008137585 Jun 2008 JP
2003068216 Aug 2003 KR
2238190 Oct 2004 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
2009006518 Jan 2008 WO
2008-103973 Aug 2008 WO
2008106387 Sep 2008 WO
2008107430 Sep 2008 WO
Non-Patent Literature Citations (27)
Entry
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.).
International Search Report and Written Opinion dated Sep. 28, 2012, from corresponding International Patent Application No. PCT/US2011/047108.
“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.).
Translation copy 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.).
Related Publications (1)
Number Date Country
20130038442 A1 Feb 2013 US