Bosch Automotive Service Solutions LLC v. Shenzhen Xtooltech Intelligence Co Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Bosch Automotive Service Solutions LLC (Delaware)
  • Defendant: Shenzhen XTOOLTech Intelligent Co., Ltd. (People's Republic of China)
  • Plaintiff’s Counsel: Baker Botts LLP.
• Case Identification: 2:26-cv-00828, E.D. Tex., 09/17/2026
• Venue Allegations: Venue is alleged to be proper because the Defendant is a foreign company that may be sued in any judicial district, and because Defendant allegedly imports, ships, distributes, offers for sale, and sells the Accused Products into the Eastern District of Texas through various channels, including its websites and online storefronts.
• Core Dispute: Plaintiff alleges that Defendant’s portfolio of vehicle diagnostic tools infringes five U.S. patents related to tire pressure monitoring systems, customizable data recording, diagnostic trouble code management, and fault urgency indication.
• Technical Context: The technology at issue involves handheld electronic tools used by automotive technicians and consumers to interface with, diagnose, and service the increasingly complex computer systems in modern vehicles.
• Key Procedural History: The complaint alleges that Plaintiff notified Defendant of its patents and the alleged infringement prior to filing the lawsuit, which may form a basis for a subsequent claim of willful infringement.

Case Timeline

Date	Event
2006-10-30	Earliest Priority Date ('903 Patent, '320 Patent)
2007-07-26	Earliest Priority Date ('145 Patent)
2008-04-23	Earliest Priority Date ('622 Patent)
2009-09-22	'903 Patent Issued
2010-01-01	Defendant Company Formed (approx.)
2011-07-26	'028 Patent Issued
2011-12-06	'320 Patent Issued
2013-03-12	'622 Patent Issued
2013-06-25	'145 Patent Issued
2016-01-01	Defendant Entered U.S. Market (approx.)
2025-11-01	Defendant Attended SEMA Trade Show (approx.)
2026-09-17	Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,592,903 - "Tire pressure monitor system tool with re-learn and diagnostic procedures," issued September 22, 2009 (’903 Patent)

The Invention Explained

• Problem Addressed: The patent addresses the complexity and unreliability of prior art methods for "re-learning" or resetting a vehicle’s tire pressure monitoring system (TPMS) after tire service Compl. ¶39 These methods often involved vehicle-specific, complex button sequences and separate physical magnets to activate sensors, which were prone to being lost and could suffer from magnetic interference '903 Patent, col. 2:5-3:11
• The Patented Solution: The invention is a handheld tool that consolidates the re-learn process. The tool stores a database of procedures for various vehicles, guides the user to select the correct vehicle, determines the appropriate procedure, communicates with the vehicle’s electronic control unit (ECU), and wirelessly initiates the individual tire sensors to complete the re-learn process '903 Patent, abstract '903 Patent, col. 4:45-5:14
• Technical Importance: The technology aimed to replace a fragmented, error-prone, and tool-intensive process with a single, guided, electronic device, thereby increasing efficiency and reliability for automotive technicians Compl. ¶42

Key Claims at a Glance

• The complaint asserts independent claim 13 Compl. ¶84
• The essential elements of Claim 13 include:
  • requesting vehicle data of a vehicle;
  • accessing stored tire pressure monitor system information;
  • determining if a portion of the stored information is associated with the vehicle data;
  • determining if the information comprises a reset or diagnostic procedure;
  • communicating with an electronic control unit of the vehicle;
  • initiating at least one tire pressure sensor on a wheel to enable communication with the ECU;
  • providing feedback to a user that the sensor has been initiated; and
  • simulating the at least one tire pressure sensor to validate that the TPMS is functional Compl. ¶41
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 8,072,320 - "Tire pressure monitor system tool with vehicle entry system," issued December 6, 2011 (’320 Patent)

The Invention Explained

• Problem Addressed: The patent identifies the significant complexity technicians faced in servicing TPMS, as they first had to determine which specific system, procedures, and communication protocols were used by a particular vehicle before a diagnostic tool could effectively communicate with it Compl. ¶48 '320 Patent, col. 3:1-11
• The Patented Solution: The patent describes a method where a diagnostic tool prompts a user for vehicle data (e.g., make, model, year), receives that data, and then uses it to access an onboard memory that stores information for a plurality of TPMS. Based on the vehicle data, the tool automatically determines the correct TPMS and the corresponding communication protocol to use for interfacing with the vehicle's ECU '320 Patent, abstract '320 Patent, col. 6:25-44
• Technical Importance: This invention provided a key improvement in the interoperability of diagnostic tools, enabling a single device to automatically configure itself to work with a wide variety of different TPMS implementations, eliminating manual identification steps Compl. ¶52

Key Claims at a Glance

• The complaint asserts independent claim 15 and dependent claim 16 Compl. ¶96
• The essential elements of Claim 15 include:
  • requesting a vehicle data using a display on the monitoring tool;
  • receiving the requested vehicle data;
  • accessing a tire pressure monitoring system from a memory of the tool, where the memory stores a plurality of such systems; and
  • determining the tire pressure monitoring system used by a vehicle based on the vehicle data Compl. ¶50
• Claim 16 adds the steps of accessing the memory for a communication protocol from a plurality of protocols and communicating with the vehicle's ECU using the determined protocol Compl. ¶51

U.S. Patent No. 8,396,622 - "Customizable initiation of data recordings," issued March 12, 2013 (’622 Patent)

• Technology Synopsis: The patent addresses the inefficiency of vehicle data recorders, which often captured large amounts of irrelevant data Compl. ¶58 The invention provides a method for customizing the start of a data recording session based on user-defined triggers and Boolean logic, allowing for more focused and relevant data capture Compl. ¶¶60-61
• Asserted Claims: Claim 9 Compl. ¶108
• Accused Features: The functionality of the Accused Diagnostic D, A, IP, Gasoline, EV, and Key Programmer product series is alleged to infringe Compl. ¶109

U.S. Patent No. 7,987,028 - "Method and apparatus for reading and erasing diagnostic trouble codes from a vehicle," issued July 26, 2011 (’028 Patent)

• Technology Synopsis: The patent addresses the problem of a single vehicle fault generating multiple, duplicate Diagnostic Trouble Codes (DTCs) across different electronic modules, which complicates diagnosis Compl. ¶67 The invention is a method for a diagnostic tool to retrieve DTCs from multiple systems, identify any duplicates, and provide the option to clear all related codes efficiently Compl. ¶¶69-70
• Asserted Claims: Claim 9 Compl. ¶120
• Accused Features: The functionality of the Accused Diagnostic D, IP, Gasoline, EV, and Key Programmer product series, as well as certain A-series products, is alleged to infringe Compl. ¶121

U.S. Patent No. 8,473,145 - "Code evaluator tool with urgency indicator," issued June 25, 2013 (’145 Patent)

• Technology Synopsis: The patent addresses the issue that a generic malfunction indicator lamp does not inform a driver about the seriousness of a vehicle fault Compl. ¶76 The invention provides a method for a tool to retrieve a DTC, cross-reference it with a database to determine a "level of urgency," and display a distinct indicator corresponding to that level, along with a suggested course of action Compl. ¶78
• Asserted Claims: Claim 8 Compl. ¶132
• Accused Features: The functionality of various products, including the AD20, D7S, and IP900S, is alleged to infringe Compl. ¶133

III. The Accused Instrumentality

Product Identification

The complaint names Defendant's "entire portfolio of vehicle diagnostic tools" as the Accused Products Compl. ¶7 This includes specific product lines such as the Accused Tire Pressure Scanners (e.g., TP500), Accused Diagnostic D Series (e.g., D8S), Accused Diagnostic A Series, Accused Diagnostic IP Series, and others Compl. ¶¶7a-g

Functionality and Market Context

The Accused Products are described as handheld electronic devices that interface with vehicle computer systems to perform diagnostics and maintenance Compl. ¶2 The complaint alleges these products are manufactured in China and imported into the U.S. for sale to consumers, repair shops, and mechanics through various distribution channels, including official stores on Amazon, Walmart, and eBay Compl. ¶5 Compl. ¶¶29-32 Visual evidence in the complaint includes a photograph of the product label for the accused "D8S" model, identifying it as a "Smart Diagnostic System" Compl. p. 6 Another photograph shows the label for the "TP500," a "TPMS Diagnostic Tool" Compl. p. 7 A screenshot of Defendant's eBay storefront describes its products as "car diagnostic scan tools" shipped from the United States Compl. p. 10

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits (Exhibits F, G, H, I, J) purporting to show how specific accused products meet the limitations of the asserted claims Compl. ¶86 Compl. ¶98 Compl. ¶110 Compl. ¶122 Compl. ¶134 As these exhibits were not provided, the following is a summary of the narrative infringement theories presented in the complaint.

'903 Patent Narrative Summary

The complaint alleges that the Accused '903 Products, such as the TP150, practice the method of claim 13 Compl. ¶84 Compl. ¶86 The narrative theory suggests these tools perform a method that involves requesting and using vehicle data to determine the correct TPMS reset procedure, communicating with the vehicle's ECU, initiating the tire sensors to establish a new association, and providing feedback to the user, thereby mapping to the steps of claim 13 (Compl. ¶¶41-42; Compl. ¶84). The alleged infringement occurs when customers use the products as instructed by Defendant's manuals and videos Compl. ¶91

'320 Patent Narrative Summary

The complaint alleges that Accused '320 Products, such as the IP919 PRO, practice the method of claims 15 and 16 Compl. ¶96 Compl. ¶98 The infringement theory is that these tools request and receive vehicle-specific data through their user interface, access an internal memory containing information for a plurality of TPMS, and use that data to determine the specific system and communication protocol required to interface with the vehicle's ECU, thereby practicing the claimed method (Compl. ¶¶50-52; Compl. ¶96).

Identified Points of Contention

• Scope and Technical Questions ('903 Patent): A potential point of contention is the "simulating the at least one tire pressure sensor" limitation of claim 13. The analysis may raise the question of whether the accused products perform a function that constitutes "simulating" to "validate" the system's functionality, or if they perform a simpler confirmation step that falls outside the claim's scope. Further, the court may need to determine what evidence supports the allegation that the accused tools "initiate" the sensor in the specific manner required to enable communication with the ECU, as distinct from merely reading a pre-existing broadcast from the sensor.
• Scope and Technical Questions ('320 Patent): The infringement analysis for the '320 Patent will likely focus on the "determining the tire pressure monitoring system... based on the vehicle data" limitation. A central question is whether the accused products' method for selecting the correct system technically aligns with the process described in the patent. For example, does the accused tool use a direct lookup in a stored database as taught by the patent, or does it employ an alternative technique such as iterative protocol testing that may not meet the claim limitation?

V. Key Claim Terms for Construction

For the '903 Patent

• The Term: "simulating the at least one tire pressure sensor" (from Claim 13)
• Context and Importance: This term describes a functional step for validating that the TPMS is operational after a reset procedure. Practitioners may focus on this term because its definition is critical to determining whether the accused products perform the final validation step as claimed, or a different, non-infringing function.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification describes this step functionally: "The tool 10 may also include a simulating module 84. The simulating module 84 may be used to simulate a tire pressure sensor to validate the functionality of a tire pressure monitor system on a vehicle" '903 Patent, col. 8:55-59 Plaintiff may argue this broad functional language covers any action that tests and confirms the system is working.
  • Evidence for a Narrower Interpretation: The word "simulate" in an engineering context often implies actively mimicking a component's signal or behavior. Defendant may argue that this requires the tool to generate a test signal that emulates a real sensor transmission, and that merely receiving a confirmation signal from the vehicle's ECU does not constitute "simulating."

For the '320 Patent

• The Term: "determining the tire pressure monitoring system used by a vehicle based on the vehicle data" (from Claim 15)
• Context and Importance: This term is the core of the claimed invention, describing the automated selection process that eliminates manual-user effort. The case may turn on how the accused device accomplishes this "determination" versus what the patent requires.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language is functional and does not specify a particular mechanism. Plaintiff may argue that any process where vehicle data is an input and the correct TPMS is the output falls within the scope of "determining." The specification states the tool "determines a tire pressure monitor system installed on the vehicle using information stored by the tool" '320 Patent, abstract, which is broad.
  • Evidence for a Narrower Interpretation: The specification provides a specific example: "The tool determines a tire pressure monitor system installed on the vehicle by, for example, associating the vehicle data input by the user with vehicle data stored in a lookup table by the tool" '320 Patent, col. 3:28-31 While "for example" suggests other possibilities, a defendant may argue that this language limits the claim to methods analogous to a database lookup, potentially excluding methods like brute-force protocol testing.

VI. Other Allegations

Indirect Infringement

The complaint alleges both induced and contributory infringement for all five asserted patents. The inducement allegations are based on Defendant allegedly providing product manuals, quick start guides, online instructional videos, and other technical documentation that instruct customers on how to use the Accused Products in an infringing manner Compl. ¶91 Compl. ¶103 Compl. ¶115 Compl. ¶127 Compl. ¶139 The contributory infringement allegations are based on the assertion that the Accused Products contain specialized components adapted to perform the patented methods and are not staple articles of commerce with substantial non-infringing uses Compl. ¶92 Compl. ¶104 Compl. ¶116 Compl. ¶128 Compl. ¶140

Willful Infringement

The complaint alleges willful infringement for all five asserted patents. The allegations are based on both pre-suit and post-suit knowledge. Plaintiff claims it "notified Defendant of Bosch Automotive patents relating to vehicle diagnostic tools and Defendant's infringement of those patents prior to the filing of the Complaint" Compl. ¶89 Compl. ¶101 Compl. ¶113 Compl. ¶125 Compl. ¶137 The complaint also asserts a theory of willful blindness, alleging Defendant entered a "patent-intensive" market and deliberately avoided investigating third-party patent rights Compl. ¶89

VII. Analyst’s Conclusion: Key Questions for the Case

1. Evidentiary Congruence: A primary issue will be whether the evidence produced during discovery demonstrates a technical congruence between the Accused Products' actual operation and the specific steps recited in the asserted claims. As the complaint's infringement contentions rely on unavailable exhibits, the case will depend heavily on an examination of the accused source code and internal design documents to see if they perform, for example, the claimed "simulating" ('903 Patent) or "determining" ('320 Patent) steps.

2. Claim Construction and Scope: The dispute will likely involve significant debate over the scope of key claim terms. A core question will be one of definitional scope: can the term "simulating," used to describe system validation in the ’903 Patent, be construed to cover the accused products' confirmation process, or does it require a more active signal-generation function? Similarly, the scope of terms like "determining" ('320 Patent) and "customizable initialization operations" ('622 Patent) will be central to the infringement analysis.

3. Knowledge and Willfulness: Given the explicit allegation of pre-suit notice, a crucial question for willfulness and potential enhanced damages will be the content and sufficiency of that notice. The court will need to determine if the pre-suit communications were specific enough to provide actual knowledge of infringement for the patents-in-suit, or if the allegations rely more heavily on the broader, more difficult to prove, theory of willful blindness.