DCT
2:21-cv-00240
Orange Electronic Co Ltd v. Autel Intelligent Technology Corp Ltd
Key Events
Complaint
Table of Contents
complaint
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Orange Electronic Co. Ltd. (Taiwan)
- Defendant: Autel Intelligent Technology Corp., Ltd. (China)
- Plaintiff’s Counsel: The Heartfield Law Firm; Sughrue Mion PLLC
- Case Identification: 2:21-cv-00240, E.D. Tex., 06/30/2021
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because a substantial part of the events giving rise to the claim occurred in the district and because Defendant is subject to personal jurisdiction there.
- Core Dispute: Plaintiff alleges that Defendant’s Tire Pressure Monitoring System (TPMS) products, including its programmable sensors and handheld programming tools, infringe a patent related to the method and system for copying a unique identification code from an old or failing sensor to a new, rewriteable replacement sensor.
- Technical Context: TPMS technology is a federally mandated safety feature in modern vehicles, creating a significant aftermarket for replacing sensors that have failed or reached the end of their battery life.
- Key Procedural History: The asserted patent has undergone three separate ex parte reexaminations, resulting in the cancellation of original claims 1-7 and 9, the subsequent cancellation of claims 8 and 10-15, and the amendment or addition of the currently asserted claims. This extensive prosecution history may suggest a narrowed scope for the surviving claims and will likely be a central feature of any claim construction dispute.
Case Timeline
| Date | Event |
|---|---|
| 2008-09-17 | ’064 Patent Priority Date |
| 2011-10-04 | U.S. Patent No. 8,031,064 Issues |
| 2013-11-07 | ’064 C1 Reexamination Certificate Issued |
| 2014-12-12 | ’064 C2 Reexamination Certificate Issued |
| 2020-05-15 | ’064 C3 Reexamination Certificate Issued |
| 2020-07-09 | Plaintiff alleges sending notice letter to Defendant |
| 2021-06-30 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,031,064 C3 - "Tire Pressure Detecting Apparatus and Tire Pressure Detector Identification Copying Method for the Same"
- Reexamination Certificate Issued: May 15, 2020
The Invention Explained
- Problem Addressed: The patent's background describes the difficulty of replacing a vehicle's TPMS sensor. Each sensor has a unique identification (ID) that the vehicle’s main computer is programmed to recognize. When a sensor fails, simply installing a new one is insufficient, as the vehicle will not recognize the new sensor's different ID. The conventional solution required using a specialized setting apparatus, often manufacturer-specific, to reprogram the vehicle's central monitoring system to accept the new sensor's ID, a process described as "necessary but troublesome" ('064 Patent, col. 6:23-24, 6:52-60).
- The Patented Solution: The invention proposes a two-part system to simplify this process: (1) a replacement tire pressure detector containing a rewriteable memory unit, and (2) a separate setting apparatus. This apparatus can read the ID from the old, failed sensor (or accept manual entry of the ID) and then wirelessly transmit and write that same ID into the new replacement sensor's rewriteable memory. This "clones" the original sensor, allowing the vehicle to recognize the new sensor without requiring any reprogramming of the vehicle's onboard computer ('064 Patent, Abstract; col. 6:5-13). Figure 1 of the patent illustrates the two main components: the "identification rewriteable tire pressure detector" (10) and the "setting apparatus" (20) ('064 Patent, Fig. 1).
- Technical Importance: This approach creates a universal replacement method that is independent of the vehicle's manufacturer, streamlining the process for aftermarket automotive service centers and technicians (Compl. ¶1).
Key Claims at a Glance
- The complaint asserts independent claims 23 (method) and 26 (system), among others (Compl. ¶19).
- Independent Claim 23 (Method) includes the essential elements of:
- Providing a setting apparatus with an input and receiving module.
- Obtaining an "update identification" by either (1) reading an old ID from an old sensor via an RF signal or (2) receiving a manually input ID.
- Wirelessly writing the identification into a new rewriteable tire pressure detector.
- Verifying the newly recorded identification.
- Independent Claim 26 (System) includes the essential elements of:
- An identification rewritable tire pressure detector with a micro-processing module, a rewriteable memory, a sensing module, a transmitting module, and an interface for receiving an external signal.
- A "portable setting apparatus" that is "not equipped in the vehicle" and is configured to obtain an update ID (from an old sensor or manual input), store it, and generate the external signal to program the new sensor.
- The complaint reserves the right to assert additional claims, including dependent claims (Compl. ¶19).
III. The Accused Instrumentality
Product Identification
- The complaint names a range of Autel's TPMS products, focusing on the combination of the handheld MaxiTPMS TS501 programming tool and the programmable MX-Sensor (Compl. ¶¶18, 20).
Functionality and Market Context
- The complaint alleges the MaxiTPMS TS501 is a portable, handheld device that communicates wirelessly with Autel's programmable sensors, such as the MX-Sensor (Compl. ¶28).
- It is alleged that the TS501 tool allows a user to "clone" a sensor ID through several methods. These include "Copy by Activation," where the tool reads the ID from an existing sensor, and "Manual Create," where the user manually types in an ID to be written to the new sensor (Compl. ¶¶35, 38). An image from Autel's user manual shows a menu screen on the TS501 with options for "Copy by Activation," "Auto Create," and "Manual Create" (Compl. p. 12, Fig. 5.31).
- The complaint asserts that the MX-Sensor is an "ID clone-able" universal TPMS sensor with a rewriteable memory that can be programmed by an Autel tool (Compl. ¶¶21, 22).
IV. Analysis of Infringement Allegations
Infringement Allegations: U.S. Patent No. 8,031,064 C3, Claim 26 (System)
| Claim Element (from Independent Claim 26) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| an identification rewritable tire pressure detector...comprising: a micro-processing module having a rewritable memory unit to record an identification | The Autel MX-Sensor includes a micro-processing module which contains rewriteable RAM memory. | ¶22 | col. 15:30-32 |
| an interface arranged to receive an external signal...wherein the external signal comprises an external identification to be written into the rewriteable memory unit | The MX-Sensor includes a Low Frequency Receiver (LF RECVR) interface that receives an external signal, including an external ID, to be written into its memory. | ¶26 | col. 15:44-49 |
| a portable setting apparatus arranged to communicate with the identification rewriteable tire pressure detector...wherein the portable setting apparatus is not equipped in the vehicle and is portable relative to the vehicle | The accused MaxiTPMS TS501 is a portable, handheld device external to the vehicle that communicates with the MX-Sensor. The complaint includes a photograph of the handheld TS501 tool alongside an MX-sensor (Compl. p. 7). | ¶28 | col. 17:48-51 |
| [the setting apparatus is configured to:] obtain an update identification...either by (1) receiving the RF signal from an old tire pressure detector...or by (2) receiving a manual input of the identification | The TS501 is configured to obtain an ID by either reading an RF signal from an old sensor ("Copy by Activation") or by receiving manual input from its keyboard ("Manual Create"). | ¶35 | col. 17:53-62 |
| generate the external signal comprising the update identification...and send the external signal to the new identification rewriteable tire pressure detector | The TS501's control module generates an external signal containing the obtained ID and sends it to the MX-Sensor for programming. A block diagram from an Autel manual shows the MX-Sensor's LF Receiver (LFR) for this purpose (Compl. p. 9). | ¶¶32-33 | col. 17:65-col. 18:6 |
Infringement Allegations: U.S. Patent No. 8,031,064 C3, Claim 23 (Method)
| Claim Element (from Independent Claim 23) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| obtaining, by the setting apparatus, an update identification...by either (1) reading an old identification...by receiving radio frequency (RF) signal...or (2) receiving an input of a manually input identification | A user operating the TS501 tool obtains an ID by either using the "Copy by Activation" function to read an old sensor's RF signal or the "Manual Create" function to enter an ID via the keyboard. The complaint includes an image of the TS501 keyboard connected to its internal circuit board (Compl. p. 14). | ¶35 | col. 16:11-23 |
| wirelessly writing the old identification into a new identification rewriteable tire pressure detector...such that the new...detector records the update identification | The TS501 tool sends signals that cause the new MX-Sensor to record the update ID in its rewriteable memory, overwriting any preset ID. | ¶38 | col. 16:24-33 |
| verifying, by the setting apparatus, the update identification newly recorded in the rewritable memory unit of the new...detector | After writing the new ID, the TS501 allegedly "judges the consistency" of the newly recorded ID with the ID stored in the tool. The complaint shows a photo sequence allegedly depicting this confirmation process (Compl. p. 23). | ¶40 | col. 16:47-56 |
Identified Points of Contention
- Scope Questions: Claim 26 requires the setting apparatus to be "not equipped in the vehicle." The analysis may question whether tools that also perform functions requiring a connection to a vehicle’s OBD-II port (a feature of some advanced TPMS tools) would fall outside this limitation's scope, even if programming can be done portably.
- Technical Questions: The "verifying" step of method claim 23, which was added during reexamination, may become a key point of dispute. The analysis will raise the question of what technical actions constitute "verifying" and "judging...consistency." Does a simple "write successful" confirmation from the tool meet this limitation, or does it require a more specific process of reading back the newly written ID and comparing it to the source ID stored in the tool, as the patent specification suggests? ('064 Patent, col. 7:38-44).
V. Key Claim Terms for Construction
The Term: "verifying...the update identification" (Claim 23)
- Context and Importance: This term defines a critical active step in the asserted method claim that was added during the third reexamination. Its construction will be central to determining infringement, as the specific actions performed by the accused TS501 tool after programming a sensor must be mapped to this limitation. Practitioners may focus on this term because its meaning was likely narrowed by arguments made to the USPTO to overcome prior art.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: A party could argue that in its plain and ordinary meaning, "verifying" simply requires confirming that the programming operation was completed successfully, a common feature in such devices.
- Evidence for a Narrower Interpretation: The C3 reexamination certificate, which added this limitation, also contains language about "judging...consistency of the update identification newly recorded...and the old identification" ('064 Patent, C3, col. 2:25-30). This suggests a specific requirement to receive data back from the newly programmed sensor and perform a comparison, not just confirm the write command was sent. The specification describes this as the setting apparatus receiving wireless signals back from the new detector to "judge[] the consistence of the identifications" ('064 Patent, col. 7:38-44).
The Term: "portable setting apparatus" (Claim 26)
- Context and Importance: This term, along with the qualifiers "not equipped in the vehicle" and "portable relative to the vehicle," defines the accused programming tool. The boundaries of what it means to be "not equipped" will be critical.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification broadly distinguishes the setting apparatus (20) from the in-car "monitoring apparatus" (72) of the prior art, suggesting the primary distinction is being separate from the permanent, in-vehicle TPMS receiver ('064 Patent, col. 6:25-30, Fig. 1).
- Evidence for a Narrower Interpretation: The specific limitations "not equipped in the vehicle" and "portable" were added in claim 26 during reexamination ('064 Patent, C3, col. 5:50-51). This addition may support an interpretation that the apparatus must be capable of its claimed function (obtaining and writing an ID) without any physical or data connection to the vehicle itself, potentially excluding devices that rely on an OBD-II connection for certain cloning operations.
VI. Other Allegations
- Indirect Infringement: The complaint alleges inducement of infringement, stating that Autel provides user manuals, data sheets, and other instructions that guide end-users (e.g., technicians) to operate the accused products in a manner that performs the patented method (Compl. ¶46).
- Willful Infringement: The complaint alleges willful infringement based on pre-suit knowledge. It specifically pleads that on July 9, 2020, nearly one year prior to the filing of the lawsuit, Plaintiff sent a letter to Defendant identifying the ’064 Patent and the accused infringing TPMS products (Compl. ¶¶41, 48).
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of claim scope shaped by prosecution history: Given the patent's three intensive reexaminations, a central question is how narrowly the doctrine of prosecution history estoppel will require the court to construe key amended or added terms like "verifying" and "portable setting apparatus." The patentee's ability to prove infringement may depend on surviving a narrow construction of these critical limitations.
- A key evidentiary question will be one of technical operation: The case will likely require a detailed technical examination of how the accused MaxiTPMS TS501 tool operates. Specifically, does the tool's post-programming confirmation process perform the specific "judging...consistency" function arguably required by the "verifying" step of claim 23, or does it perform a more generic "write successful" check that may fall outside the claim's scope?
Analysis metadata