1007-00003 · Whitfield & Gaines PLLC · Analysis

invalidity-non-infringement-assessment.docx DOCUMENT Litigation

1 / 12 → ✕

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION / ATTORNEY WORK PRODUCT

CALDERWOOD & HARKNESS LLP One Fountain Square, 11th Floor Detroit, Michigan 48226

MEMORANDUM

March 15, 2025

TO: Marcus Delgado, Responsible Partner, intellectual Property, Calderwood & Harkness LLP Rachel Nguyen, Vice President & Associate General Counsel, Vantage Mobility Systems Corp.

FROM: Omar Siddiqui, Lead Associate, intellectual Property, Calderwood & Harkness LLP Christy Bauer, Working Associate, intellectual Property, Calderwood & Harkness LLP

RE: Invalidity and Non-Infringement Assessment — U.S. Patent No. 9,847,312 B2; Pinnacle Innovations LLC v. Vantage Mobility Systems Corp., No. 2:24-cv-00187-JRG (E.D. Tex.)

Engagement No.: 1007-00003

CONFIDENTIALITY NOTE: This memorandum is protected by the attorney-client privilege and the work-product doctrine. It is prepared in anticipation of litigation and for the purpose of providing legal advice to Vantage Mobility Systems Corp. ("VMS") in connection with the above-referenced proceeding. The contents of this memorandum reflect the mental impressions, conclusions, opinions, and legal theories of counsel. This memorandum, and any attachments or appendices referenced herein, should not be disclosed, distributed, or otherwise disseminated to any person or entity without the prior written authorization of Calderwood & Harkness LLP. Inadvertent disclosure of this memorandum does not constitute a waiver of any applicable privilege or protection.

Right-click to update Table of Contents

I. Executive Summary

The purpose of this memorandum is to assess the invalidity and non-infringement defenses available to Vantage Mobility Systems Corp. ("VMS") with respect to Claims 1, 7, and 14 of U.S. Patent No. 9,847,312 B2 (the "'312 Patent"), which are asserted against VMS by Pinnacle Innovations LLC ("Pinnacle") in the above-captioned action currently pending in the United States District Court for the Eastern District of Texas before the Honorable J. Rodney Gilstrap. This assessment is intended to inform VMS's strategic decision-making regarding continued defense of this action, the pursuit of dispositive motions, and the evaluation of potential settlement alternatives.

This analysis incorporates and relies upon the technical findings and opinions of Dr. Franklin Yeoh, Ph.D. (Electrical Engineering), Principal of Greystone Technical Consulting LLC, Ann Arbor, Michigan, who has been retained by Calderwood & Harkness LLP as a defense technical expert in this matter. Dr. Yeoh has prepared detailed claim charts mapping the prior art to the asserted claims and has analyzed the accused VMS products at the source-code and hardware-schematic level. His analysis forms the technical foundation for the legal conclusions set forth herein.

The '312 Patent, titled "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks," was issued on March 6, 2018, to DataStream Automotive, Inc., a now-dissolved Illinois corporation, and names Dr. Alan Prescott as the sole inventor. The patent was assigned to Pinnacle via a recorded assignment dated August 14, 2023. Pinnacle is a non-practicing entity that acquired a portfolio of approximately 35 patents from DataStream and has commenced an enforcement campaign against multiple defendants in the connected-vehicle and fleet-management industries.

The accused products in this action are the VMS DriveLink™ 4.0 telematics control unit (a hardware device installed in fleet vehicles) and the VMS FleetPulse™ cloud platform (a software-as-a-service application that receives, processes, and displays vehicle telemetry data for fleet operators). These products are core components of VMS's connected-vehicle offering and account for a significant portion of the company's annual revenue.

Based on our analysis, our assessment of VMS's defensive posture is as follows:

• Invalidity: We estimate a 65–70% probability of invalidating at least one of the asserted independent claims at trial. This assessment is based principally on two prior art references: Tanaka et al. (U.S. Patent No. 8,214,097), which anticipates Claims 1 and 14 under 35 U.S.C. § 102, and Morales (PCT Application WO 2014/036281), which, in combination with Tanaka, renders Claim 7 obvious under 35 U.S.C. § 103. Dr. Yeoh has prepared element-by-element claim charts supporting these invalidity positions, and his analysis demonstrates strong mapping of the prior art disclosures to the asserted claim limitations.

• Non-Infringement: We estimate a 55–60% probability of prevailing on non-infringement following the Court's December 19, 2024 Claim Construction Order (Dkt. 87). The Court's constructions of "adaptive interval" and "aggregated data packet" were generally favorable to VMS and provide meaningful grounds for non-infringement arguments. However, the Court's construction of "network congestion metric" was ambiguous, leaving unresolved whether implicit measures of network conditions — such as transmission latency and packet loss rates — fall within the scope of the term. This ambiguity creates residual infringement exposure with respect to Claim 7, which is the claim most central to Pinnacle's infringement theory.

These probability assessments must be weighed against several additional factors: the estimated cost to take this matter through trial ($2.8M–$3.4M in additional fees and expenses beyond amounts already incurred), the inherent unpredictability of jury trials in the Eastern District of Texas, and the management distraction and opportunity costs to VMS of continued litigation. If VMS is found to infringe one or more valid claims, potential damages exposure is estimated at $1.5M–$4.0M based on a reasonable royalty theory. The risk of enhanced damages or injunctive relief is assessed as low.

A separate settlement recommendation memorandum will follow this assessment.

II. Background

A. The '312 Patent

The patent at issue in this litigation is U.S. Patent No. 9,847,312 B2, titled "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks." The key bibliographic and ownership details of the '312 Patent are summarized below:

• Patent Number: U.S. 9,847,312 B2

• Title: "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks"

• Issue Date: March 6, 2018

• Priority Date: September 12, 2015 (based on U.S. Provisional Application No. 62/217,854, filed September 12, 2015)

• Expiration Date: September 12, 2035 (calculated as 20 years from the filing date of the provisional application; no terminal disclaimers have been recorded, and no patent term adjustment or extension has been granted)

• Named Inventor: Dr. Alan Prescott, who served as the Chief Technology Officer of DataStream Automotive, Inc. during the relevant period

• Original Assignee: DataStream Automotive, Inc., an Illinois corporation that was dissolved in 2021 following cessation of business operations

• Current Assignee: Pinnacle Innovations LLC, a Texas limited liability company, which acquired the '312 Patent and related portfolio assets from DataStream's dissolution estate by assignment recorded at the United States Patent and Trademark Office on August 14, 2023

The '312 Patent is one component of a larger portfolio of approximately 35 patents that Pinnacle acquired from DataStream. Based on publicly available information and representations made by Pinnacle's counsel during the litigation, the '312 Patent is considered one of the core assets in Pinnacle's portfolio and serves as the centerpiece of its current enforcement campaign. Pinnacle is a non-practicing entity — it does not manufacture or sell any products or services that practice the '312 Patent or any other patents in its portfolio. Pinnacle is managed by Grayson Holt, who has been identified in public filings and corporate records as the sole managing member of the entity.

Our investigation has also revealed that Pinnacle's enforcement campaign is financed by Arcadia Litigation Finance, LP, a Delaware limited partnership that specializes in litigation funding for patent monetization campaigns. While the specific terms of the funding arrangement between Pinnacle and Arcadia are not publicly known, the involvement of a litigation funder is relevant to VMS's defense strategy insofar as it may affect Pinnacle's settlement calculus, willingness to proceed to trial, and potential exposure to discovery regarding its financial arrangements and litigation decision-making.

The technology described in the '312 Patent relates broadly to the field of vehicular telematics — specifically, to a method and system for collecting on-board diagnostic (OBD-II) data and Global Positioning System (GPS) telemetry data from multiple sensors within a vehicle, aggregating the collected data into a composite data packet, compressing and encrypting the aggregated data packet, and transmitting the processed data packet over a cellular data connection to a remote server or cloud platform. The '312 Patent further describes a mechanism for adjusting the timing of data transmissions based on network congestion conditions, with the goal of optimizing bandwidth utilization and reducing data loss during periods of high cellular network traffic. This adaptive transmission feature is the focus of Claim 7 and represents the most technically distinctive aspect of the patented invention.

B. Asserted Claims

Pinnacle asserts three independent claims of the '312 Patent against VMS: Claims 1, 7, and 14. At this stage of the litigation, Pinnacle has not independently asserted any dependent claims, although it has reserved the right to do so. The full text of each asserted independent claim is set forth below, with annotations identifying the key limitations relevant to VMS's invalidity and non-infringement defenses.

Claim 1 is directed to a method and recites:

1. A method for transmitting vehicle telemetry data over a cellular data connection, the method comprising:

(a) collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors;

(b) aggregating the collected OBD-II diagnostic data and GPS telemetry data into an aggregated data packet;

(d) transmitting the compressed and encrypted aggregated data packet over a cellular data connection to a remote server.

Claim 1 is the broadest of the three asserted independent claims and does not include the "adaptive interval" or "network congestion metric" limitations found in Claim 7. It covers the fundamental method of collecting, aggregating, compressing, encrypting, and transmitting vehicle telematics data over a cellular connection.

Claim 7 builds upon the general telematics data transmission method and adds the adaptive transmission interval limitation:

7. A method for transmitting vehicle telemetry data over a cellular data connection, the method comprising:

(a) collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors;

(b) aggregating the collected OBD-II diagnostic data and GPS telemetry data into an aggregated data packet;

(d) receiving a network congestion metric from a cellular network; and

(e) transmitting the compressed and encrypted aggregated data packet over the cellular data connection at an adaptive interval determined based on the received network congestion metric.

Claim 7 is the most technically specific of the asserted claims and incorporates two limitations — "adaptive interval" and "network congestion metric" — that are central to both the invalidity and non-infringement analyses. The Court's Claim Construction Order addressed both of these terms, as discussed in Section II.E below.

Claim 14 is a system claim that recites:

14. A telematics control unit for a vehicle, comprising:

(a) an OBD-II interface configured to collect OBD-II diagnostic data from the vehicle;

(b) a GPS receiver configured to collect GPS telemetry data;

(c) a processor configured to aggregate the OBD-II diagnostic data and the GPS telemetry data into an aggregated data packet and to compress and encrypt the aggregated data packet; and

(d) a cellular modem configured to transmit the compressed and encrypted aggregated data packet over a cellular data connection to a remote server.

Claim 14 is a system claim that recites a hardware architecture for the telematics control unit and covers the same functional steps as Claim 1 (aggregation, compression, encryption, and cellular transmission) but in the context of a specific hardware configuration. Claim 14 does not include the adaptive interval or network congestion metric limitations of Claim 7.

C. Accused Products

Pinnacle accuses two VMS products of infringing the '312 Patent:

VMS DriveLink™ 4.0. The DriveLink™ 4.0 is a telematics control unit designed for installation in commercial fleet vehicles. The unit is a compact, ruggedized hardware device that connects to a vehicle's OBD-II diagnostic port and reads diagnostic trouble codes, engine performance parameters, fuel consumption data, and other sensor outputs via the vehicle's Controller Area Network (CAN) bus. The DriveLink™ 4.0 also incorporates an integrated GPS receiver that captures vehicle location, speed, heading, and altitude data. The unit aggregates data from these sensor inputs, compresses it, applies transport-layer encryption (TLS 1.3), and transmits the processed data to VMS's cloud infrastructure via an integrated LTE cellular modem. The DriveLink™ 4.0 was introduced to the market in Q2 2022 and is currently deployed in approximately 34,000 fleet vehicles across the United States and Canada.

VMS FleetPulse™. The FleetPulse™ platform is a cloud-based software-as-a-service (SaaS) application that serves as the data ingestion, processing, and visualization layer for VMS's connected-vehicle ecosystem. FleetPulse™ receives data transmissions from deployed DriveLink™ units, stores and processes the telemetry data, and presents it to fleet operators through a web-based dashboard and mobile application. FleetPulse™ also provides the administrative console through which fleet managers can configure DriveLink™ operating parameters, including transmission intervals, operating modes, and alert thresholds. While FleetPulse™ is primarily a cloud software product, Pinnacle includes it in its infringement allegations on the theory that the FleetPulse™ platform, in combination with the DriveLink™ hardware, constitutes the complete infringing system.

VMS's fleet-management products, including DriveLink™ and FleetPulse™, are a significant component of the company's business. VMS reported total annual revenue of approximately $218 million for fiscal year 2024, with connected-vehicle products (including DriveLink™ hardware sales, FleetPulse™ subscription revenue, and related installation and support services) representing a material portion of that figure.

D. Procedural History

The procedural history of this action is relevant to understanding the current posture of VMS's defenses and the upcoming deadlines that will govern strategic decision-making:

• February 28, 2024: Pinnacle filed its Complaint for Patent Infringement (Dkt. 1) in the United States District Court for the Eastern District of Texas, marshall Division, asserting infringement of Claims 1, 7, and 14 of the '312 Patent against VMS. The Complaint alleges that VMS's DriveLink™ 4.0 and FleetPulse™ products directly and indirectly infringe the asserted claims.

• April 15, 2024: VMS, then represented by Hargrove Dunn LLP, filed its Answer and Counterclaims (Dkt. 18), denying infringement and asserting counterclaims for declaratory judgment of invalidity under 35 U.S.C. §§ 102 and 103, declaratory judgment of non-infringement, and inequitable conduct. VMS also asserted various affirmative defenses, including prosecution history estoppel, laches, and equitable estoppel.

• May through October 2024: The parties engaged in fact discovery, including the exchange of initial disclosures, interrogatory responses, and document productions. VMS served its invalidity contentions on July 12, 2024, and Pinnacle served its infringement contentions on June 28, 2024. Substantial e-discovery was conducted, with documents hosted and processed by Meridian Document Solutions LLC.

• November 14, 2024: The Court conducted a Markman hearing on the parties' disputed claim construction positions. The hearing addressed the construction of nine disputed terms, including "adaptive interval," "aggregated data packet," and "network congestion metric."

• December 19, 2024: The Court entered its Claim Construction Order (Dkt. 87), resolving the disputed claim terms. The constructions adopted by the Court are discussed in detail in Section II.E below.

• January 2025: Prior defense counsel, Hargrove Dunn LLP, withdrew from the representation due to a conflict of interest arising from the firm's engagement by an entity affiliated with Pinnacle's litigation funder, Arcadia Litigation Finance, LP. Hargrove Dunn's total fees for the representation from inception through withdrawal were approximately $624,000. Calderwood & Harkness LLP assumed VMS's defense effective January 15, 2025, under Engagement No. 1007-00003. Caldwell Barrow LLP (Sandra Caldwell), located in Tyler, Texas, was engaged as local counsel.

• March 28, 2025: Fact discovery closes. The parties are currently completing the production of remaining responsive documents and finalizing deposition schedules. Two depositions remain to be taken: the deposition of Dr. Alan Prescott (inventor) and the Rule 30(b)(6) deposition of Pinnacle.

• May 30, 2025: Expert report deadline. This is the deadline for VMS to serve its opening expert reports on invalidity and non-infringement, including Dr. Yeoh's expert report and claim charts. Pinnacle's responsive expert reports will be due 30 days thereafter.

• October 6, 2025: Trial date. The case is set for a five-day jury trial before Judge Gilstrap.

The transition of counsel, while disruptive, has provided an opportunity for fresh assessment of VMS's defensive posture in light of the Claim Construction Order. This memorandum represents the product of that reassessment.

E. Claim Construction Order — Key Constructions

The Court's Claim Construction Order of December 19, 2024 addressed nine disputed terms. Three of those terms are directly relevant to VMS's non-infringement defenses and are discussed below. The remaining six terms are not material to the analysis at this stage.

"Adaptive interval." The Court construed this term as: "a time period between successive data transmissions that is dynamically adjusted based on one or more measured parameters." This construction is favorable to VMS because it requires that the transmission interval be "dynamically adjusted" — that is, changed in real time by the device based on parameters the device measures — rather than merely being configurable by an external operator. DriveLink™ 4.0 uses a fixed, server-configurable transmission schedule in which the interval between data transmissions (default: 30 seconds) is set by a human fleet operator through the FleetPulse™ administrative console. The device does not autonomously alter its transmission cadence based on measured parameters during normal operation. Pinnacle had urged the Court to adopt a broader construction that would encompass any interval that is "capable of being changed," but the Court rejected that position and adopted the narrower, dynamic-adjustment construction that VMS advocated.

"Aggregated data packet." The Court construed this term as: "a single data structure containing data collected from at least two different sensor types combined prior to transmission." This construction is favorable to VMS in certain respects because it requires that data from multiple sensor types be "combined prior to transmission" into a "single data structure." In certain operating modes of the DriveLink™ 4.0 — specifically "Mode B" or "split-payload mode" — the unit transmits OBD-II diagnostic data and GPS telemetry data as separate, independent payloads rather than combining them into a single data structure. In Mode B, no aggregation occurs prior to transmission within the meaning of the Court's construction. However, in "Mode A" or "unified mode," the DriveLink™ 4.0 does combine OBD-II and GPS data into a single JSON payload prior to transmission, which would satisfy this claim limitation. Approximately 60% of currently deployed DriveLink™ 4.0 units operate in Mode A.

"Network congestion metric." The Court construed this term as: "a parameter indicative of the level of traffic or availability on a cellular data network." This construction is ambiguous and represents the most significant adverse outcome from the Markman hearing. The Court's construction does not resolve whether the "parameter" must be an explicit metric received from the cellular network infrastructure (such as a congestion notification or load indicator transmitted by a base station) or whether implicit, indirect measures of network conditions — such as observed transmission latency, packet loss rates, or retry success rates — qualify as "parameters indicative of the level of traffic or availability on a cellular data network." This ambiguity is critical because DriveLink™ 4.0 does monitor transmission latency and retry success rates as part of its firmware-level retry backoff algorithm. If these implicit measures are deemed to constitute "network congestion metrics" within the Court's construction, Pinnacle's infringement argument with respect to Claim 7 is substantially strengthened. Conversely, if the term is limited to explicit, network-provided congestion signals, VMS has a strong non-infringement position because DriveLink™ 4.0 does not query or receive any such explicit signal from the cellular infrastructure.

The full text of the Claim Construction Order is attached hereto as Appendix C.

III. Invalidity Analysis

A. Legal Standards

Under 35 U.S.C. § 282, an issued patent is presumed valid, and the party challenging validity bears the burden of proving invalidity by clear and convincing evidence. Kestrel Partners LLC v. i4i Ltd. P'ship, 564 U.S. 91, 95 (2011). This heightened standard applies whether invalidity is raised as a defense at trial or in a motion for summary judgment.

Anticipation under 35 U.S.C. § 102. A patent claim is invalid as anticipated if a single prior art reference discloses every element of the claimed invention, either expressly or inherently. Schering Corp. v. Geneva Pharms., Inc., 339 F.3d 1373, 1377 (Fed. Cir. 2003). To establish anticipation, the challenger must show that each and every limitation of the claim is found in the prior art reference, arranged as in the claim, and that the reference enables the claimed invention. Verdegaal Bros., Inc. v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Anticipation is a question of fact. In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009).

Obviousness under 35 U.S.C. § 103. A patent claim is invalid as obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which the subject matter pertains. The analysis is guided by the four factors set forth in Graham v. John Deere Co., 383 U.S. 1 (1966): (1) the scope and content of the prior art; (2) the differences between the prior art and the claims at issue; (3) the level of ordinary skill in the pertinent art; and (4) any objective indicia of nonobviousness (secondary considerations). The Supreme Court's decision in KSR International Co. v. Teleflex Inc., 550 U.S. 398 (2007), established that the analysis is flexible, that a motivation to combine prior art references need not be found in the references themselves but may be drawn from the general knowledge of a person of ordinary skill, and that combining known elements according to known methods to yield predictable results may support a finding of obviousness.

The clear and convincing evidence standard makes invalidity a challenging defense to establish at trial, particularly before a jury. However, the strength of the prior art identified by Dr. Yeoh provides a solid foundation for VMS's invalidity case, as detailed below.

B. Prior Art Reference 1: Tanaka et al. — U.S. Patent No. 8,214,097

The strongest prior art reference identified in our invalidity analysis is Tanaka et al., U.S. Patent No. 8,214,097 ("Tanaka"), which was issued on July 3, 2012.

Prior Art Status. Tanaka qualifies as prior art under pre-AIA 35 U.S.C. § 102(b) because it was patented more than one year before the '312 Patent's earliest claimed priority date of September 12, 2015. The '312 Patent claims priority to a provisional application filed on September 12, 2015, and because the provisional application was filed before March 16, 2013 — the effective date of the America Invents Act's first-inventor-to-file provisions — the pre-AIA patent statute governs the prior art analysis. Tanaka's July 3, 2012 issue date places it comfortably within the § 102(b) statutory bar period. There is no dispute regarding Tanaka's prior art status.

Subject Matter. Tanaka is directed to a vehicle telematics system for collecting, processing, and transmitting diagnostic and positional data from a motor vehicle to a remote monitoring station. The system described in Tanaka includes a telematics control unit installed in a vehicle that interfaces with the vehicle's OBD-II diagnostic port and a GPS receiver, collects data from these sources, aggregates the data into a unified data structure (referred to in Tanaka as a "composite telemetry frame"), applies compression and encryption to the aggregated data, and transmits the processed data to a remote server over a 3G WCDMA cellular data connection.

Anticipation of Claim 1. Dr. Yeoh's element-by-element claim chart, attached as Appendix A, maps each limitation of Claim 1 to corresponding disclosures in Tanaka. The mapping is summarized as follows:

Limitation (a) — Collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors. Tanaka discloses collecting OBD-II diagnostic data (including diagnostic trouble codes, engine RPM, coolant temperature, vehicle speed, and fuel consumption data) from the vehicle's OBD-II diagnostic port and GPS telemetry data (including latitude, longitude, altitude, speed, and heading) from an integrated GPS receiver. Tanaka, col. 4, ll. 22–45. Tanaka describes the vehicle as having "a plurality of vehicle sensors" connected to the OBD-II interface. Id. at col. 3, ll. 55–67.

Limitation (b) — Aggregating the collected data into an aggregated data packet. Tanaka discloses combining the OBD-II diagnostic data and GPS telemetry data into a single data structure that it terms a "composite telemetry frame." Tanaka, col. 6, ll. 10–32. The composite telemetry frame is described as a structured data packet containing fields for each type of sensor data, with a header indicating the data types included and a timestamp. Id. at col. 6, ll. 33–50.

Limitation (c) — Compressing and encrypting the aggregated data packet. Tanaka discloses applying GZIP compression to the composite telemetry frame to reduce its size for transmission. Tanaka, col. 7, ll. 5–15. Tanaka further discloses encrypting the compressed composite telemetry frame using AES-128 encryption prior to transmission. Id. at col. 7, ll. 18–30. The specification describes the compression and encryption steps as sequential, with compression applied first and encryption applied to the compressed output. Id.

Limitation (d) — Transmitting the compressed and encrypted data packet over a cellular data connection. Tanaka discloses transmitting the compressed and encrypted composite telemetry frame over a 3G WCDMA cellular data connection to a remote monitoring server. Tanaka, col. 8, ll. 1–20. The transmission is performed by a cellular modem integrated into the telematics control unit. Id. at col. 5, ll. 38–52.

Assessment — Claim 1 Anticipation. Based on Dr. Yeoh's analysis, Tanaka discloses each and every element of Claim 1. The mapping is clean, with each limitation finding a direct, express counterpart in the Tanaka disclosure. There are no significant gaps or areas where inherent disclosure must be argued. Dr. Yeoh has assessed the probability of establishing anticipation of Claim 1 by Tanaka at 65–70%, with the principal uncertainty being the clear and convincing evidence standard and the inherent variability of jury decision-making rather than any weakness in the substantive mapping.

Anticipation of Claim 14. Claim 14 is a system claim that recites the same functional steps as Claim 1 but in the context of a specific hardware architecture — a telematics control unit comprising an OBD-II interface, a GPS receiver, a processor, and a cellular modem. Dr. Yeoh's claim chart (Appendix A) maps these system elements to Tanaka's hardware architecture, which is described in detail in Tanaka's specification and accompanying figures.

Tanaka discloses a telematics control unit (referred to in Tanaka as a "central processing module") that includes an OBD-II interface module for communicating with the vehicle's diagnostic port (Tanaka, col. 4, ll. 1–21), a GPS receiver module for receiving satellite positioning signals (col. 4, ll. 22–35), a processor (described as an ARM-based microcontroller) that executes software for data aggregation, compression, and encryption (col. 5, ll. 1–37), and a cellular modem module for 3G WCDMA data transmission (col. 5, ll. 38–52). Dr. Yeoh identifies Tanaka's "central processing module" as corresponding to the "telematics control unit" recited in Claim 14, and each sub-component of Tanaka's hardware architecture maps to a corresponding element of Claim 14.

Assessment — Claim 14 Anticipation. The anticipation analysis for Claim 14 tracks the analysis for Claim 1. Dr. Yeoh has assessed the probability of establishing anticipation of Claim 14 by Tanaka at 65–70%, consistent with the Claim 1 assessment.

Tanaka's Limitations with Respect to Claim 7. While Tanaka is a strong anticipation reference for Claims 1 and 14, it does not disclose the "adaptive interval" or "network congestion metric" limitations that are present in Claim 7. Specifically, Tanaka describes a fixed periodic transmission interval — the composite telemetry frame is transmitted every 60 seconds — with no mechanism for dynamically adjusting the interval based on network conditions. Tanaka, col. 8, ll. 21–35. Accordingly, Tanaka standing alone does not anticipate Claim 7 under § 102. However, Tanaka serves as the primary reference in an obviousness combination with Morales, as discussed in Section III.C below.

C. Prior Art Reference 2: Morales — PCT Application WO 2014/036281

The second principal prior art reference is Morales, PCT Application Publication No. WO 2014/036281 ("Morales"), published on March 13, 2014.

Prior Art Status. Morales qualifies as prior art under 35 U.S.C. § 102(a)(1) because it was published before the '312 Patent's effective filing date of September 12, 2015. The publication date of March 13, 2014 predates the priority date by approximately 18 months. There is no dispute regarding Morales's prior art status.

Subject Matter. Morales is directed to a method for adapting data transmission intervals in vehicular Internet of Things (IoT) devices based on cellular network load-balancing parameters. The Morales application describes a communication protocol for IoT devices installed in vehicles — including telematics sensors and diagnostic monitoring units — that adjusts the timing of data transmissions based on real-time information about the congestion status of the serving cellular base station. The protocol is designed to reduce data loss and improve transmission reliability by avoiding periods of peak network congestion.

Relevance to Claim 7 — Obviousness in Combination with Tanaka. While Morales does not independently disclose all of the elements of Claim 7 (it does not specifically describe the aggregation of OBD-II and GPS data into a combined data structure), Morales provides the critical disclosure of the "adaptive interval" and "network congestion metric" limitations that are absent from Tanaka. The combination of Tanaka and Morales renders Claim 7 obvious under § 103, as explained below.

"Adaptive interval" disclosure. Morales describes a transmission scheduling algorithm in which the time period between successive data transmissions from a vehicular IoT device is dynamically adjusted based on real-time network conditions. Morales, paras. [0042]–[0058]. Specifically, the Morales protocol monitors the congestion status of the cellular network and increases the transmission interval when congestion is high (to avoid contributing to network overload) and decreases the interval when congestion is low (to maximize data freshness). Id. at paras. [0049]–[0053]. The adjustment is performed autonomously by the device without human intervention. Id. at para. [0055].

"Network congestion metric" disclosure. Morales describes receiving congestion indicators from the serving cellular base station and using them to modulate the transmission frequency of the vehicular IoT device. Morales, paras. [0063]–[0071]. The congestion indicators described in Morales include: (i) a "load indicator" broadcast by the base station as part of the cellular control channel signaling; (ii) signal quality measurements (RSSI, RSRP, RSRQ) that reflect the level of traffic on the serving cell; and (iii) explicit congestion notification (ECN) signals embedded in data packets returned by the network. Id. at paras. [0065]–[0068]. Morales describes using these metrics as inputs to a scheduling algorithm that determines the adaptive transmission interval. Id. at paras. [0070]–[0071].

Motivation to Combine. A person of ordinary skill in the art at the time of the '312 Patent's invention would have been motivated to combine Tanaka's vehicle telemetry data aggregation and cellular transmission system with Morales's adaptive-interval and congestion-metric techniques for several reasons:

First, both Tanaka and Morales are in the same technical field — vehicular telematics and cellular data communication — and address closely related problems. A POSITA working on vehicle telematics systems in 2015 would have been aware of both types of references and would have considered their teachings in combination.

Second, Morales expressly discusses application of its adaptive transmission protocol to OBD-II telematics systems. Morales, para. [0035] ("The adaptive scheduling protocol described herein is particularly applicable to vehicle telematics systems that transmit OBD-II diagnostic data and sensor telemetry over cellular data connections, where network congestion can lead to data loss and delayed reporting."). This express statement provides a specific teaching and suggestion to apply Morales's adaptive interval technique to a system of the type disclosed in Tanaka.

Third, the combination involves applying a known technique (adaptive transmission scheduling based on network congestion) to a known device (vehicle telematics control unit with cellular data transmission) to yield a predictable result (improved bandwidth utilization and reduced data loss during high-congestion periods). Under KSR, this type of combination supports a finding of obviousness. 550 U.S. at 416–17.

Fourth, the problem of cellular network congestion affecting vehicle telematics data transmission was a well-known challenge in the industry as of the September 2015 priority date. Multiple industry publications and standards documents from this period discuss the need for adaptive transmission scheduling in vehicular IoT devices to address network congestion, confirming that a POSITA would have recognized the desirability of combining these approaches.

Dr. Yeoh's Assessment. Dr. Yeoh has assessed the probability of establishing that Tanaka in combination with Morales renders Claim 7 obvious at 65–70%. This probability assessment is somewhat tempered by the ambiguity in the Court's construction of "network congestion metric." If the Court or jury interprets the term narrowly — requiring an explicit, network-provided congestion signal — Morales maps extremely well to the claim limitation because Morales describes exactly such explicit signals (load indicators, ECN signals). If, however, the term is construed broadly to include implicit measures such as latency and packet loss, the Morales reference remains supportive but the argument is somewhat diluted because the distinction between Morales's explicit metrics and the implicit measures used by VMS's products becomes less clear-cut. Regardless, Dr. Yeoh considers the Tanaka/Morales combination to be a strong obviousness argument under either construction.

Dr. Yeoh's element-by-element claim chart for the Tanaka/Morales combination, including the motivation-to-combine analysis, is attached as Appendix B.

D. Additional Prior Art Considered

In preparing VMS's invalidity contentions, Dr. Yeoh conducted a comprehensive survey of prior art in the fields of vehicle telematics, OBD-II data processing, cellular data transmission protocols, and adaptive communication scheduling. This survey encompassed issued U.S. patents, published U.S. patent applications, PCT publications, academic publications, and industry standards documents. Several additional references were identified and evaluated, including:

• Hartmann et al. (U.S. Patent Application Publication No. 2013/0275623), which describes a vehicle diagnostic data collection system but does not disclose aggregation of GPS and OBD-II data into a single data structure or encryption of the aggregated data.

• Zhao (U.S. Patent No. 8,521,169), which describes a cellular network congestion management protocol but is directed to handset devices rather than vehicular telematics systems and does not disclose OBD-II data collection.

• IEEE 802.11p-related publications addressing vehicle-to-infrastructure communication, which operate in a different technical domain (DSRC/WAVE) than the cellular data transmission claimed in the '312 Patent.

While these additional references provide useful context regarding the state of the art, none were as strong as Tanaka and Morales for the specific claim elements at issue. Dr. Yeoh concluded that the Tanaka anticipation argument (for Claims 1 and 14) and the Tanaka/Morales obviousness combination (for Claim 7) represent VMS's strongest invalidity positions and should be the focus of the expert report and any dispositive motions.

It should also be noted that VMS's invalidity contentions were initially served during the period of Hargrove Dunn LLP's representation and have been supplemented by Calderwood & Harkness after assuming the engagement. The claim charts prepared by Dr. Yeoh have not yet been formally filed as expert reports, as the expert report deadline is May 30, 2025. To date, Dr. Yeoh's work product has been maintained as attorney work product and has not been produced or disclosed to Pinnacle.

E. Inequitable Conduct Defense

VMS's Answer and Counterclaims include a counterclaim for inequitable conduct, alleging that Dr. Prescott engaged in material misrepresentation or omission during the prosecution of the '312 Patent before the USPTO. Specifically, VMS alleged that Dr. Prescott failed to disclose material prior art references during prosecution and made affirmative misrepresentations regarding the novelty of the claimed invention.

Upon review of the complete prosecution history of the '312 Patent — including the original application as filed, all Office Actions, all applicant responses, all Information Disclosure Statements (IDS), and all examiner interviews — we have concluded that the evidence supporting the inequitable conduct counterclaim is weak. There are two principal reasons for this assessment:

First, Tanaka was cited in the prosecution history. Dr. Prescott filed an IDS on March 15, 2017, that included Tanaka (U.S. Patent No. 8,214,097) as a reference. The examiner considered the reference and initialed the IDS form. Although neither the examiner nor Dr. Prescott substantively discussed or distinguished Tanaka in the prosecution record, the fact that the reference was placed before the examiner significantly undermines any argument that it was intentionally withheld.

Second, the standard for inequitable conduct — as articulated by the Federal Circuit in Brightmoor & Co., Inc. v. Becton, Dickinson & Co., 649 F.3d 1276 (Fed. Cir. 2011) (en banc) — requires proof by clear and convincing evidence that the applicant (i) knew of material prior art, (ii) withheld it from the PTO or made a material misrepresentation, and (iii) did so with the specific intent to deceive the PTO. The "but-for" materiality standard set by Brightmoor & Co. is difficult to satisfy when the reference was disclosed and the intent-to-deceive requirement demands more than mere negligence or poor judgment. Given that Tanaka was cited in the IDS, demonstrating either "but-for" materiality (the examiner had the reference) or specific intent to deceive is a substantial challenge.

Assessment. The probability of prevailing on the inequitable conduct counterclaim is low. We recommend de-emphasizing this defense and focusing VMS's resources on the stronger invalidity and non-infringement arguments. However, we do not recommend voluntarily dismissing the counterclaim at this time, as its continued pendency may have strategic value in settlement negotiations and it imposes modest additional costs to maintain.

F. Overall Invalidity Probability Assessment

Based on the foregoing analysis and Dr. Yeoh's technical findings, our overall assessment of VMS's invalidity defenses is as follows:

• Claims 1 and 14 (Tanaka anticipation under § 102): 65–70% probability of invalidation at trial. The strength of this argument derives from the clean, element-by-element mapping of Tanaka's disclosures to the limitations of Claims 1 and 14, with no significant gaps requiring inherency arguments or expert interpretation.

• Claim 7 (Tanaka + Morales obviousness under § 103): 65–70% probability of invalidation at trial. This assessment is contingent on favorable resolution of the "network congestion metric" construction ambiguity. If the term is ultimately interpreted to require an explicit, network-provided congestion signal, the Morales reference maps directly and the obviousness argument is strong. If the term is construed broadly, the argument remains supportable but is somewhat less compelling.

• At least one independent claim: We assess a 65–70% composite probability of invalidating at least one of the three asserted independent claims at trial. Because the invalidity arguments for Claims 1 and 14 are based on the same prior art reference (Tanaka) and share similar strengths and weaknesses, the probability of invalidating at least one of these claims is correlated rather than independent. The addition of the Claim 7 obviousness argument provides a modest incremental benefit to the overall invalidity position.

• Caveats. These probability assessments are subject to inherent uncertainty. The clear and convincing evidence standard is a meaningful hurdle, and jury composition in the Eastern District of Texas adds significant variability to outcomes. Additionally, Pinnacle may present secondary considerations of nonobviousness (commercial success, long-felt need, failure of others) that could weaken the obviousness argument with respect to Claim 7, although we have not identified strong evidence of such secondary considerations in the record to date.

IV. Non-Infringement Analysis

A. Legal Standard

Patent infringement under 35 U.S.C. § 271(a) is established when the accused product or method practices each and every limitation of an asserted claim, either literally or under the doctrine of equivalents. Laitram Corp. v. Rexnord, Inc., 939 F.2d 1533, 1535 (Fed. Cir. 1991). It is the patentee's burden to prove infringement by a preponderance of the evidence. Harborview Corporation, Inc. v. Mirowski Family Ventures, LLC, 571 U.S. 191, 199 (2014). Claim construction, as established by the Court's Markman order, governs the scope and meaning of the claim terms for purposes of the infringement analysis. Markman v. Westview Instruments, Inc., 517 U.S. 370 (1996).

If the accused product or method does not satisfy even one limitation of a claim, there is no literal infringement of that claim. Bayer AG v. Elan Pharm. Research Corp., 212 F.3d 1241, 1247 (Fed. Cir. 2000). Under the doctrine of equivalents, a limitation is met if the accused element performs substantially the same function, in substantially the same way, to achieve substantially the same result as the claimed element. Warner-Jenkinson Co. v. Harborline Enterprises Davis Chem. Co., 520 U.S. 17, 40 (1997). However, the doctrine of equivalents is subject to several limiting principles, including prosecution history estoppel, which prevents a patentee from recapturing through equivalents claim scope that was surrendered during prosecution. Festo Corp. v. Fenmore & Co., 535 U.S. 722 (2002).

B. Non-Infringement Position — Claim 1

VMS's non-infringement argument with respect to Claim 1 centers on the "aggregated data packet" limitation. Under the Court's construction — "a single data structure containing data collected from at least two different sensor types combined prior to transmission" — VMS contends that DriveLink™ 4.0 does not practice this limitation in all operating modes.

Mode B (Split-Payload Mode). In Mode B, the DriveLink™ 4.0 transmits OBD-II diagnostic data and GPS telemetry data as separate, independent payloads. Each sensor type generates its own data structure, which is independently compressed, encrypted, and transmitted over the cellular data connection. In Mode B, OBD-II data is transmitted as a standalone JSON payload, and GPS telemetry data is transmitted as a separate JSON payload, with each payload sent in its own cellular data transmission. There is no step in Mode B where data from the two sensor types is "combined prior to transmission" into a "single data structure." Accordingly, DriveLink™ 4.0 operating in Mode B does not practice the "aggregated data packet" limitation and does not infringe Claim 1.

This argument is supported by Dr. Yeoh's review of the DriveLink™ 4.0 firmware source code (produced in discovery as VMS-DL-SC-000001 through VMS-DL-SC-004823), which confirms that Mode B implements separate data processing pipelines for OBD-II and GPS data, with no function call or data structure that combines the two data types into a single output. The technical architecture documentation for DriveLink™ 4.0 (produced as VMS-ARCH-000015 through VMS-ARCH-000042) further corroborates the separation of data flows in Mode B.

Mode A (Unified Mode). In Mode A, DriveLink™ 4.0 combines OBD-II diagnostic data and GPS telemetry data into a single JSON payload prior to transmission. The unified payload contains nested JSON objects for each data type, wrapped in a common data structure with a single header, timestamp, and device identifier. This unified payload is then compressed, encrypted, and transmitted as a single unit over the cellular data connection. Dr. Yeoh's analysis confirms that Mode A operation likely satisfies the "aggregated data packet" limitation under the Court's construction, as the data from two different sensor types (OBD-II and GPS) is combined into a single data structure prior to transmission.

Deployment Statistics. According to VMS's internal deployment records and configuration management data, approximately 60% of currently deployed DriveLink™ 4.0 units operate in Mode A (unified mode) and approximately 40% operate in Mode B (split-payload mode). The default configuration for new deployments is Mode A, although fleet operators can configure either mode through the FleetPulse™ administrative console. The distribution of operating modes across the installed base is relevant to the scope of potential infringement liability and damages exposure.

Net Assessment — Claim 1. The non-infringement argument with respect to Claim 1 is mixed. VMS has a strong position for units operating in Mode B (approximately 40% of the installed base), but the argument does not exculpate Mode A deployments (approximately 60% of the installed base). If the case proceeds to trial, Pinnacle will likely focus its infringement case on Mode A operation, where the "aggregated data packet" limitation appears to be satisfied. VMS may argue that Mode A operation was not the commercially significant mode at the time of the alleged infringement, but this is a damages argument rather than a liability argument. We assess the overall probability of prevailing on non-infringement for Claim 1 at 50–55%, reflecting the strength of the Mode B argument offset by the Mode A vulnerability.

C. Non-Infringement Position — Claim 7

Claim 7 is the most technically complex of the asserted claims and presents both VMS's strongest non-infringement argument and its most significant residual risk. The analysis turns on two claim limitations: "adaptive interval" and "network congestion metric."

"Adaptive Interval" Limitation. Under the Court's construction — "a time period between successive data transmissions that is dynamically adjusted based on one or more measured parameters" — VMS has a strong argument that DriveLink™ 4.0 does not practice this limitation during normal operation. The DriveLink™ 4.0 uses a server-configurable but fixed transmission schedule. The default transmission interval is 30 seconds, and fleet operators can adjust this interval to 15, 30, 60, or 120 seconds through the FleetPulse™ administrative console. Once configured, the interval remains fixed and is not changed by the device itself in real time based on any measured parameter. The transmission interval is determined by a human operator making a configuration choice, not by the device autonomously responding to measured conditions.

The strength of this argument derives directly from the Court's construction, which requires "dynamic" adjustment — a term that connotes real-time, autonomous, parameter-driven change by the device itself, as opposed to manual reconfiguration by a human operator. VMS's product design clearly falls outside this construction during normal operation.

However, there is a significant counterargument that Pinnacle will likely pursue. DriveLink™ 4.0 firmware includes a "retry backoff" algorithm that is invoked when a data transmission fails. Specifically, when a transmission attempt is unsuccessful (due to cellular connectivity loss, server timeout, or other transmission error), the firmware automatically increases the interval between successive retransmission attempts according to an exponential backoff schedule. The backoff interval starts at the configured transmission interval and doubles with each successive failed attempt, up to a maximum backoff interval of 600 seconds (10 minutes). The retry backoff algorithm operates autonomously without human intervention.

Pinnacle may argue that the retry backoff algorithm constitutes "dynamic adjustment" of the transmission interval "based on one or more measured parameters" (specifically, the measured parameter being the success or failure of the preceding transmission attempt). If the Court or jury accepts this characterization, the DriveLink™ 4.0 could be found to practice the "adaptive interval" limitation through its retry backoff behavior.

VMS's rebuttal to this argument is that retry backoff is an error-recovery mechanism, not a proactive, congestion-aware scheduling system. The '312 Patent specification describes the "adaptive interval" in the context of a system that affirmatively monitors network congestion conditions and adjusts its transmission schedule to optimize bandwidth utilization — not a system that simply retries failed transmissions with increasing delays. Retry backoff is a ubiquitous feature of virtually all networked communication systems and was well-known long before the '312 Patent. Characterizing retry backoff as "adaptive interval" scheduling would render the limitation so broad as to encompass nearly every networked device, which would undermine the construction the Court adopted.

"Network Congestion Metric" Limitation. This is the principal area of residual risk in VMS's non-infringement defense for Claim 7. The Court's construction — "a parameter indicative of the level of traffic or availability on a cellular data network" — is ambiguous with respect to whether the "parameter" must be an explicit metric received from the cellular network infrastructure or whether implicit, indirect measures of network conditions qualify.

As discussed in Section II.E, DriveLink™ 4.0 monitors transmission latency and retry success rates as part of its retry backoff logic. Specifically, the firmware tracks the round-trip time (RTT) for each transmission attempt and maintains a running average of RTT values. The firmware also records the number of consecutive failed transmission attempts and the success rate of recent transmissions. These metrics are used internally by the retry backoff algorithm to determine when to reattempt transmission and how aggressively to back off.

Pinnacle will likely argue that these metrics — transmission latency and retry success rates — are "parameters indicative of the level of traffic or availability on a cellular data network" within the Court's construction. Elevated transmission latency and low success rates, Pinnacle will contend, are symptoms of network congestion, and therefore monitoring them constitutes receiving a "network congestion metric." Under this theory, the retry backoff algorithm — which adjusts the transmission interval based on these metrics — would satisfy both the "adaptive interval" and "network congestion metric" limitations of Claim 7.

VMS's rebuttal is multi-faceted:

First, transmission latency and retry failures are not "network congestion metrics" in the sense contemplated by the '312 Patent specification. The specification describes the network congestion metric as an explicit signal received from the cellular network infrastructure — for example, a congestion notification from the base station or a network load indicator provided through control channel signaling. See '312 Patent, col. 9, ll. 14–38. DriveLink™ 4.0 does not query or receive any explicit congestion signal from the cellular infrastructure. The device has no awareness of the congestion status of the cellular network apart from the indirect inference that can be drawn from transmission failures and elevated latency.

Second, transmission latency and retry failures can result from numerous causes other than network congestion, including signal strength variations (the vehicle may be in a low-coverage area), server-side processing delays, hardware malfunctions, or transient radio interference. These metrics are not reliable or specific indicators of network congestion.

Third, the '312 Patent prosecution history supports a narrow interpretation of "network congestion metric." During prosecution, Dr. Prescott distinguished prior art by arguing that the prior art did not disclose receiving a "specific congestion indicator from the network" and instead relied on "general transmission quality metrics." This argument suggests that the inventors intended "network congestion metric" to refer to an explicit, dedicated congestion signal rather than a general-purpose quality metric like latency or packet loss.

Assessment — Claim 7. VMS's non-infringement position for Claim 7 is stronger than for Claims 1 and 14 due to the favorable "adaptive interval" construction, but the "network congestion metric" ambiguity creates meaningful residual risk. We assess the probability of prevailing on non-infringement for Claim 7 at 55–60%. The resolution of the "network congestion metric" construction ambiguity — whether through further briefing, a summary judgment ruling, or jury instruction — will be the single most important factor in determining the outcome of the Claim 7 infringement analysis.

D. Non-Infringement Position — Claim 14

Claim 14 is a system claim whose limitations parallel those of Claim 1, reciting a telematics control unit with an OBD-II interface, GPS receiver, processor, and cellular modem configured to perform the aggregation, compression, encryption, and cellular transmission steps. The non-infringement analysis for Claim 14 therefore largely tracks the Claim 1 analysis, with the Mode A/Mode B distinction serving as the primary basis for the defense.

In addition to the Mode A/Mode B argument, VMS has an incremental architectural distinction argument with respect to Claim 14. Claim 14 recites a specific hardware architecture in which the processor is "configured to aggregate" the OBD-II and GPS data. Dr. Yeoh identified minor differences between the DriveLink™ 4.0 hardware architecture and the architecture described in the '312 Patent and recited in Claim 14. Specifically, in DriveLink™ 4.0, the aggregation function (in Mode A) is performed by a dedicated microcontroller that operates as a co-processor alongside the main application processor, rather than being performed by a single processor as suggested by the claim language. However, Dr. Yeoh assessed these architectural distinctions as relatively minor and unlikely to carry the day independently. The claim language "a processor configured to aggregate" is sufficiently broad to encompass a system architecture in which the aggregation is performed by one of multiple processors or a co-processor, as the claim does not recite a single-processor architecture.

Assessment — Claim 14. We assess the probability of prevailing on non-infringement for Claim 14 at 50–55%. This assessment is somewhat weaker than the Claim 7 assessment because Claim 14 does not include the "adaptive interval" or "network congestion metric" limitations that provide VMS's strongest non-infringement arguments, and the Mode A exposure (60% of deployed units) is the dominant factor.

E. Doctrine of Equivalents Exposure

Even if VMS establishes literal non-infringement on one or more claim limitations, Pinnacle may pursue infringement under the doctrine of equivalents (DOE). Under DOE, a limitation is met if the accused element performs substantially the same function, in substantially the same way, to achieve substantially the same result as the corresponding claim limitation. This theory creates residual infringement risk, particularly with respect to the "aggregated data packet" limitation in the context of Mode B operation (where OBD-II and GPS data are transmitted in separate payloads that are arguably "substantially the same" as a single aggregated payload in function and result).

However, VMS has a strong prosecution history estoppel defense that should substantially limit Pinnacle's ability to pursue DOE. During the prosecution of the '312 Patent, Dr. Prescott amended the claims on November 8, 2017, in response to an Office Action rejecting the original, broader claims. The amendments added the "aggregated data packet" limitation (original claims recited only "data packet" without requiring aggregation of data from multiple sensor types) and the "adaptive interval" limitation (original claims recited only "transmitting at intervals" without requiring adaptive adjustment). These amendments narrowed the claim scope in response to prior art rejections, and under the doctr

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION / ATTORNEY WORK PRODUCT
CALDERWOOD & HARKNESS LLP One Fountain Square, 11th Floor Detroit, Michigan 48226
MEMORANDUM
March 15, 2025
TO: Marcus Delgado, Responsible Partner, intellectual Property, Calderwood & Harkness LLP Rachel Nguyen, Vice President & Associate General Counsel, Vantage Mobility Systems Corp.
FROM: Omar Siddiqui, Lead Associate, intellectual Property, Calderwood & Harkness LLP Christy Bauer, Working Associate, intellectual Property, Calderwood & Harkness LLP
RE: Invalidity and Non-Infringement Assessment — U.S. Patent No. 9,847,312 B2; Pinnacle Innovations LLC v. Vantage Mobility Systems Corp., No. 2:24-cv-00187-JRG (E.D. Tex.)
Engagement No.: 1007-00003
CONFIDENTIALITY NOTE: This memorandum is protected by the attorney-client privilege and the work-product doctrine. It is prepared in anticipation of litigation and for the purpose of providing legal advice to Vantage Mobility Systems Corp. ("VMS") in connection with the above-referenced proceeding. The contents of this memorandum reflect the mental impressions, conclusions, opinions, and legal theories of counsel. This memorandum, and any attachments or appendices referenced herein, should not be disclosed, distributed, or otherwise disseminated to any person or entity without the prior written authorization of Calderwood & Harkness LLP. Inadvertent disclosure of this memorandum does not constitute a waiver of any applicable privilege or protection.
Right-click to update Table of Contents
I. Executive Summary
The purpose of this memorandum is to assess the invalidity and non-infringement defenses available to Vantage Mobility Systems Corp. ("VMS") with respect to Claims 1, 7, and 14 of U.S. Patent No. 9,847,312 B2 (the "'312 Patent"), which are asserted against VMS by Pinnacle Innovations LLC ("Pinnacle") in the above-captioned action currently pending in the United States District Court for the Eastern District of Texas before the Honorable J. Rodney Gilstrap. This assessment is intended to inform VMS's strategic decision-making regarding continued defense of this action, the pursuit of dispositive motions, and the evaluation of potential settlement alternatives.
This analysis incorporates and relies upon the technical findings and opinions of Dr. Franklin Yeoh, Ph.D. (Electrical Engineering), Principal of Greystone Technical Consulting LLC, Ann Arbor, Michigan, who has been retained by Calderwood & Harkness LLP as a defense technical expert in this matter. Dr. Yeoh has prepared detailed claim charts mapping the prior art to the asserted claims and has analyzed the accused VMS products at the source-code and hardware-schematic level. His analysis forms the technical foundation for the legal conclusions set forth herein.
The '312 Patent, titled "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks," was issued on March 6, 2018, to DataStream Automotive, Inc., a now-dissolved Illinois corporation, and names Dr. Alan Prescott as the sole inventor. The patent was assigned to Pinnacle via a recorded assignment dated August 14, 2023. Pinnacle is a non-practicing entity that acquired a portfolio of approximately 35 patents from DataStream and has commenced an enforcement campaign against multiple defendants in the connected-vehicle and fleet-management industries.
The accused products in this action are the VMS DriveLink™ 4.0 telematics control unit (a hardware device installed in fleet vehicles) and the VMS FleetPulse™ cloud platform (a software-as-a-service application that receives, processes, and displays vehicle telemetry data for fleet operators). These products are core components of VMS's connected-vehicle offering and account for a significant portion of the company's annual revenue.
Based on our analysis, our assessment of VMS's defensive posture is as follows:
• Invalidity: We estimate a 65–70% probability of invalidating at least one of the asserted independent claims at trial. This assessment is based principally on two prior art references: Tanaka et al. (U.S. Patent No. 8,214,097), which anticipates Claims 1 and 14 under 35 U.S.C. § 102, and Morales (PCT Application WO 2014/036281), which, in combination with Tanaka, renders Claim 7 obvious under 35 U.S.C. § 103. Dr. Yeoh has prepared element-by-element claim charts supporting these invalidity positions, and his analysis demonstrates strong mapping of the prior art disclosures to the asserted claim limitations.
• Non-Infringement: We estimate a 55–60% probability of prevailing on non-infringement following the Court's December 19, 2024 Claim Construction Order (Dkt. 87). The Court's constructions of "adaptive interval" and "aggregated data packet" were generally favorable to VMS and provide meaningful grounds for non-infringement arguments. However, the Court's construction of "network congestion metric" was ambiguous, leaving unresolved whether implicit measures of network conditions — such as transmission latency and packet loss rates — fall within the scope of the term. This ambiguity creates residual infringement exposure with respect to Claim 7, which is the claim most central to Pinnacle's infringement theory.
These probability assessments must be weighed against several additional factors: the estimated cost to take this matter through trial ($2.8M–$3.4M in additional fees and expenses beyond amounts already incurred), the inherent unpredictability of jury trials in the Eastern District of Texas, and the management distraction and opportunity costs to VMS of continued litigation. If VMS is found to infringe one or more valid claims, potential damages exposure is estimated at $1.5M–$4.0M based on a reasonable royalty theory. The risk of enhanced damages or injunctive relief is assessed as low.
A separate settlement recommendation memorandum will follow this assessment.
II. Background
A. The '312 Patent
The patent at issue in this litigation is U.S. Patent No. 9,847,312 B2, titled "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks." The key bibliographic and ownership details of the '312 Patent are summarized below:
• Patent Number: U.S. 9,847,312 B2
• Title: "System and Method for Aggregated Vehicle Telemetry Data Transmission Over Cellular Networks"
• Issue Date: March 6, 2018
• Priority Date: September 12, 2015 (based on U.S. Provisional Application No. 62/217,854, filed September 12, 2015)
• Expiration Date: September 12, 2035 (calculated as 20 years from the filing date of the provisional application; no terminal disclaimers have been recorded, and no patent term adjustment or extension has been granted)
• Named Inventor: Dr. Alan Prescott, who served as the Chief Technology Officer of DataStream Automotive, Inc. during the relevant period
• Original Assignee: DataStream Automotive, Inc., an Illinois corporation that was dissolved in 2021 following cessation of business operations
• Current Assignee: Pinnacle Innovations LLC, a Texas limited liability company, which acquired the '312 Patent and related portfolio assets from DataStream's dissolution estate by assignment recorded at the United States Patent and Trademark Office on August 14, 2023
The '312 Patent is one component of a larger portfolio of approximately 35 patents that Pinnacle acquired from DataStream. Based on publicly available information and representations made by Pinnacle's counsel during the litigation, the '312 Patent is considered one of the core assets in Pinnacle's portfolio and serves as the centerpiece of its current enforcement campaign. Pinnacle is a non-practicing entity — it does not manufacture or sell any products or services that practice the '312 Patent or any other patents in its portfolio. Pinnacle is managed by Grayson Holt, who has been identified in public filings and corporate records as the sole managing member of the entity.
Our investigation has also revealed that Pinnacle's enforcement campaign is financed by Arcadia Litigation Finance, LP, a Delaware limited partnership that specializes in litigation funding for patent monetization campaigns. While the specific terms of the funding arrangement between Pinnacle and Arcadia are not publicly known, the involvement of a litigation funder is relevant to VMS's defense strategy insofar as it may affect Pinnacle's settlement calculus, willingness to proceed to trial, and potential exposure to discovery regarding its financial arrangements and litigation decision-making.
The technology described in the '312 Patent relates broadly to the field of vehicular telematics — specifically, to a method and system for collecting on-board diagnostic (OBD-II) data and Global Positioning System (GPS) telemetry data from multiple sensors within a vehicle, aggregating the collected data into a composite data packet, compressing and encrypting the aggregated data packet, and transmitting the processed data packet over a cellular data connection to a remote server or cloud platform. The '312 Patent further describes a mechanism for adjusting the timing of data transmissions based on network congestion conditions, with the goal of optimizing bandwidth utilization and reducing data loss during periods of high cellular network traffic. This adaptive transmission feature is the focus of Claim 7 and represents the most technically distinctive aspect of the patented invention.
B. Asserted Claims
Pinnacle asserts three independent claims of the '312 Patent against VMS: Claims 1, 7, and 14. At this stage of the litigation, Pinnacle has not independently asserted any dependent claims, although it has reserved the right to do so. The full text of each asserted independent claim is set forth below, with annotations identifying the key limitations relevant to VMS's invalidity and non-infringement defenses.
Claim 1 is directed to a method and recites:
1. A method for transmitting vehicle telemetry data over a cellular data connection, the method comprising:
(a) collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors;
(b) aggregating the collected OBD-II diagnostic data and GPS telemetry data into an aggregated data packet;
(c) compressing and encrypting the aggregated data packet; and
(d) transmitting the compressed and encrypted aggregated data packet over a cellular data connection to a remote server.
Claim 1 is the broadest of the three asserted independent claims and does not include the "adaptive interval" or "network congestion metric" limitations found in Claim 7. It covers the fundamental method of collecting, aggregating, compressing, encrypting, and transmitting vehicle telematics data over a cellular connection.
Claim 7 builds upon the general telematics data transmission method and adds the adaptive transmission interval limitation:
7. A method for transmitting vehicle telemetry data over a cellular data connection, the method comprising:
(a) collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors;
(b) aggregating the collected OBD-II diagnostic data and GPS telemetry data into an aggregated data packet;
(c) compressing and encrypting the aggregated data packet;
(d) receiving a network congestion metric from a cellular network; and
(e) transmitting the compressed and encrypted aggregated data packet over the cellular data connection at an adaptive interval determined based on the received network congestion metric.
Claim 7 is the most technically specific of the asserted claims and incorporates two limitations — "adaptive interval" and "network congestion metric" — that are central to both the invalidity and non-infringement analyses. The Court's Claim Construction Order addressed both of these terms, as discussed in Section II.E below.
Claim 14 is a system claim that recites:
14. A telematics control unit for a vehicle, comprising:
(a) an OBD-II interface configured to collect OBD-II diagnostic data from the vehicle;
(b) a GPS receiver configured to collect GPS telemetry data;
(c) a processor configured to aggregate the OBD-II diagnostic data and the GPS telemetry data into an aggregated data packet and to compress and encrypt the aggregated data packet; and
(d) a cellular modem configured to transmit the compressed and encrypted aggregated data packet over a cellular data connection to a remote server.
Claim 14 is a system claim that recites a hardware architecture for the telematics control unit and covers the same functional steps as Claim 1 (aggregation, compression, encryption, and cellular transmission) but in the context of a specific hardware configuration. Claim 14 does not include the adaptive interval or network congestion metric limitations of Claim 7.
C. Accused Products
Pinnacle accuses two VMS products of infringing the '312 Patent:
VMS DriveLink™ 4.0. The DriveLink™ 4.0 is a telematics control unit designed for installation in commercial fleet vehicles. The unit is a compact, ruggedized hardware device that connects to a vehicle's OBD-II diagnostic port and reads diagnostic trouble codes, engine performance parameters, fuel consumption data, and other sensor outputs via the vehicle's Controller Area Network (CAN) bus. The DriveLink™ 4.0 also incorporates an integrated GPS receiver that captures vehicle location, speed, heading, and altitude data. The unit aggregates data from these sensor inputs, compresses it, applies transport-layer encryption (TLS 1.3), and transmits the processed data to VMS's cloud infrastructure via an integrated LTE cellular modem. The DriveLink™ 4.0 was introduced to the market in Q2 2022 and is currently deployed in approximately 34,000 fleet vehicles across the United States and Canada.
VMS FleetPulse™. The FleetPulse™ platform is a cloud-based software-as-a-service (SaaS) application that serves as the data ingestion, processing, and visualization layer for VMS's connected-vehicle ecosystem. FleetPulse™ receives data transmissions from deployed DriveLink™ units, stores and processes the telemetry data, and presents it to fleet operators through a web-based dashboard and mobile application. FleetPulse™ also provides the administrative console through which fleet managers can configure DriveLink™ operating parameters, including transmission intervals, operating modes, and alert thresholds. While FleetPulse™ is primarily a cloud software product, Pinnacle includes it in its infringement allegations on the theory that the FleetPulse™ platform, in combination with the DriveLink™ hardware, constitutes the complete infringing system.
VMS's fleet-management products, including DriveLink™ and FleetPulse™, are a significant component of the company's business. VMS reported total annual revenue of approximately $218 million for fiscal year 2024, with connected-vehicle products (including DriveLink™ hardware sales, FleetPulse™ subscription revenue, and related installation and support services) representing a material portion of that figure.
D. Procedural History
The procedural history of this action is relevant to understanding the current posture of VMS's defenses and the upcoming deadlines that will govern strategic decision-making:
• February 28, 2024: Pinnacle filed its Complaint for Patent Infringement (Dkt. 1) in the United States District Court for the Eastern District of Texas, marshall Division, asserting infringement of Claims 1, 7, and 14 of the '312 Patent against VMS. The Complaint alleges that VMS's DriveLink™ 4.0 and FleetPulse™ products directly and indirectly infringe the asserted claims.
• April 15, 2024: VMS, then represented by Hargrove Dunn LLP, filed its Answer and Counterclaims (Dkt. 18), denying infringement and asserting counterclaims for declaratory judgment of invalidity under 35 U.S.C. §§ 102 and 103, declaratory judgment of non-infringement, and inequitable conduct. VMS also asserted various affirmative defenses, including prosecution history estoppel, laches, and equitable estoppel.
• May through October 2024: The parties engaged in fact discovery, including the exchange of initial disclosures, interrogatory responses, and document productions. VMS served its invalidity contentions on July 12, 2024, and Pinnacle served its infringement contentions on June 28, 2024. Substantial e-discovery was conducted, with documents hosted and processed by Meridian Document Solutions LLC.
• November 14, 2024: The Court conducted a Markman hearing on the parties' disputed claim construction positions. The hearing addressed the construction of nine disputed terms, including "adaptive interval," "aggregated data packet," and "network congestion metric."
• December 19, 2024: The Court entered its Claim Construction Order (Dkt. 87), resolving the disputed claim terms. The constructions adopted by the Court are discussed in detail in Section II.E below.
• January 2025: Prior defense counsel, Hargrove Dunn LLP, withdrew from the representation due to a conflict of interest arising from the firm's engagement by an entity affiliated with Pinnacle's litigation funder, Arcadia Litigation Finance, LP. Hargrove Dunn's total fees for the representation from inception through withdrawal were approximately $624,000. Calderwood & Harkness LLP assumed VMS's defense effective January 15, 2025, under Engagement No. 1007-00003. Caldwell Barrow LLP (Sandra Caldwell), located in Tyler, Texas, was engaged as local counsel.
• March 28, 2025: Fact discovery closes. The parties are currently completing the production of remaining responsive documents and finalizing deposition schedules. Two depositions remain to be taken: the deposition of Dr. Alan Prescott (inventor) and the Rule 30(b)(6) deposition of Pinnacle.
• May 30, 2025: Expert report deadline. This is the deadline for VMS to serve its opening expert reports on invalidity and non-infringement, including Dr. Yeoh's expert report and claim charts. Pinnacle's responsive expert reports will be due 30 days thereafter.
• October 6, 2025: Trial date. The case is set for a five-day jury trial before Judge Gilstrap.
The transition of counsel, while disruptive, has provided an opportunity for fresh assessment of VMS's defensive posture in light of the Claim Construction Order. This memorandum represents the product of that reassessment.
E. Claim Construction Order — Key Constructions
The Court's Claim Construction Order of December 19, 2024 addressed nine disputed terms. Three of those terms are directly relevant to VMS's non-infringement defenses and are discussed below. The remaining six terms are not material to the analysis at this stage.
"Adaptive interval." The Court construed this term as: "a time period between successive data transmissions that is dynamically adjusted based on one or more measured parameters." This construction is favorable to VMS because it requires that the transmission interval be "dynamically adjusted" — that is, changed in real time by the device based on parameters the device measures — rather than merely being configurable by an external operator. DriveLink™ 4.0 uses a fixed, server-configurable transmission schedule in which the interval between data transmissions (default: 30 seconds) is set by a human fleet operator through the FleetPulse™ administrative console. The device does not autonomously alter its transmission cadence based on measured parameters during normal operation. Pinnacle had urged the Court to adopt a broader construction that would encompass any interval that is "capable of being changed," but the Court rejected that position and adopted the narrower, dynamic-adjustment construction that VMS advocated.
"Aggregated data packet." The Court construed this term as: "a single data structure containing data collected from at least two different sensor types combined prior to transmission." This construction is favorable to VMS in certain respects because it requires that data from multiple sensor types be "combined prior to transmission" into a "single data structure." In certain operating modes of the DriveLink™ 4.0 — specifically "Mode B" or "split-payload mode" — the unit transmits OBD-II diagnostic data and GPS telemetry data as separate, independent payloads rather than combining them into a single data structure. In Mode B, no aggregation occurs prior to transmission within the meaning of the Court's construction. However, in "Mode A" or "unified mode," the DriveLink™ 4.0 does combine OBD-II and GPS data into a single JSON payload prior to transmission, which would satisfy this claim limitation. Approximately 60% of currently deployed DriveLink™ 4.0 units operate in Mode A.
"Network congestion metric." The Court construed this term as: "a parameter indicative of the level of traffic or availability on a cellular data network." This construction is ambiguous and represents the most significant adverse outcome from the Markman hearing. The Court's construction does not resolve whether the "parameter" must be an explicit metric received from the cellular network infrastructure (such as a congestion notification or load indicator transmitted by a base station) or whether implicit, indirect measures of network conditions — such as observed transmission latency, packet loss rates, or retry success rates — qualify as "parameters indicative of the level of traffic or availability on a cellular data network." This ambiguity is critical because DriveLink™ 4.0 does monitor transmission latency and retry success rates as part of its firmware-level retry backoff algorithm. If these implicit measures are deemed to constitute "network congestion metrics" within the Court's construction, Pinnacle's infringement argument with respect to Claim 7 is substantially strengthened. Conversely, if the term is limited to explicit, network-provided congestion signals, VMS has a strong non-infringement position because DriveLink™ 4.0 does not query or receive any such explicit signal from the cellular infrastructure.
The full text of the Claim Construction Order is attached hereto as Appendix C.
III. Invalidity Analysis
A. Legal Standards
Under 35 U.S.C. § 282, an issued patent is presumed valid, and the party challenging validity bears the burden of proving invalidity by clear and convincing evidence. Kestrel Partners LLC v. i4i Ltd. P'ship, 564 U.S. 91, 95 (2011). This heightened standard applies whether invalidity is raised as a defense at trial or in a motion for summary judgment.
Anticipation under 35 U.S.C. § 102. A patent claim is invalid as anticipated if a single prior art reference discloses every element of the claimed invention, either expressly or inherently. Schering Corp. v. Geneva Pharms., Inc., 339 F.3d 1373, 1377 (Fed. Cir. 2003). To establish anticipation, the challenger must show that each and every limitation of the claim is found in the prior art reference, arranged as in the claim, and that the reference enables the claimed invention. Verdegaal Bros., Inc. v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Anticipation is a question of fact. In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009).
Obviousness under 35 U.S.C. § 103. A patent claim is invalid as obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which the subject matter pertains. The analysis is guided by the four factors set forth in Graham v. John Deere Co., 383 U.S. 1 (1966): (1) the scope and content of the prior art; (2) the differences between the prior art and the claims at issue; (3) the level of ordinary skill in the pertinent art; and (4) any objective indicia of nonobviousness (secondary considerations). The Supreme Court's decision in KSR International Co. v. Teleflex Inc., 550 U.S. 398 (2007), established that the analysis is flexible, that a motivation to combine prior art references need not be found in the references themselves but may be drawn from the general knowledge of a person of ordinary skill, and that combining known elements according to known methods to yield predictable results may support a finding of obviousness.
The clear and convincing evidence standard makes invalidity a challenging defense to establish at trial, particularly before a jury. However, the strength of the prior art identified by Dr. Yeoh provides a solid foundation for VMS's invalidity case, as detailed below.
B. Prior Art Reference 1: Tanaka et al. — U.S. Patent No. 8,214,097
The strongest prior art reference identified in our invalidity analysis is Tanaka et al., U.S. Patent No. 8,214,097 ("Tanaka"), which was issued on July 3, 2012.
Prior Art Status. Tanaka qualifies as prior art under pre-AIA 35 U.S.C. § 102(b) because it was patented more than one year before the '312 Patent's earliest claimed priority date of September 12, 2015. The '312 Patent claims priority to a provisional application filed on September 12, 2015, and because the provisional application was filed before March 16, 2013 — the effective date of the America Invents Act's first-inventor-to-file provisions — the pre-AIA patent statute governs the prior art analysis. Tanaka's July 3, 2012 issue date places it comfortably within the § 102(b) statutory bar period. There is no dispute regarding Tanaka's prior art status.
Subject Matter. Tanaka is directed to a vehicle telematics system for collecting, processing, and transmitting diagnostic and positional data from a motor vehicle to a remote monitoring station. The system described in Tanaka includes a telematics control unit installed in a vehicle that interfaces with the vehicle's OBD-II diagnostic port and a GPS receiver, collects data from these sources, aggregates the data into a unified data structure (referred to in Tanaka as a "composite telemetry frame"), applies compression and encryption to the aggregated data, and transmits the processed data to a remote server over a 3G WCDMA cellular data connection.
Anticipation of Claim 1. Dr. Yeoh's element-by-element claim chart, attached as Appendix A, maps each limitation of Claim 1 to corresponding disclosures in Tanaka. The mapping is summarized as follows:
Limitation (a) — Collecting OBD-II diagnostic data and GPS telemetry data from a plurality of vehicle sensors. Tanaka discloses collecting OBD-II diagnostic data (including diagnostic trouble codes, engine RPM, coolant temperature, vehicle speed, and fuel consumption data) from the vehicle's OBD-II diagnostic port and GPS telemetry data (including latitude, longitude, altitude, speed, and heading) from an integrated GPS receiver. Tanaka, col. 4, ll. 22–45. Tanaka describes the vehicle as having "a plurality of vehicle sensors" connected to the OBD-II interface. Id. at col. 3, ll. 55–67.
Limitation (b) — Aggregating the collected data into an aggregated data packet. Tanaka discloses combining the OBD-II diagnostic data and GPS telemetry data into a single data structure that it terms a "composite telemetry frame." Tanaka, col. 6, ll. 10–32. The composite telemetry frame is described as a structured data packet containing fields for each type of sensor data, with a header indicating the data types included and a timestamp. Id. at col. 6, ll. 33–50.
Limitation (c) — Compressing and encrypting the aggregated data packet. Tanaka discloses applying GZIP compression to the composite telemetry frame to reduce its size for transmission. Tanaka, col. 7, ll. 5–15. Tanaka further discloses encrypting the compressed composite telemetry frame using AES-128 encryption prior to transmission. Id. at col. 7, ll. 18–30. The specification describes the compression and encryption steps as sequential, with compression applied first and encryption applied to the compressed output. Id.
Limitation (d) — Transmitting the compressed and encrypted data packet over a cellular data connection. Tanaka discloses transmitting the compressed and encrypted composite telemetry frame over a 3G WCDMA cellular data connection to a remote monitoring server. Tanaka, col. 8, ll. 1–20. The transmission is performed by a cellular modem integrated into the telematics control unit. Id. at col. 5, ll. 38–52.
Assessment — Claim 1 Anticipation. Based on Dr. Yeoh's analysis, Tanaka discloses each and every element of Claim 1. The mapping is clean, with each limitation finding a direct, express counterpart in the Tanaka disclosure. There are no significant gaps or areas where inherent disclosure must be argued. Dr. Yeoh has assessed the probability of establishing anticipation of Claim 1 by Tanaka at 65–70%, with the principal uncertainty being the clear and convincing evidence standard and the inherent variability of jury decision-making rather than any weakness in the substantive mapping.
Anticipation of Claim 14. Claim 14 is a system claim that recites the same functional steps as Claim 1 but in the context of a specific hardware architecture — a telematics control unit comprising an OBD-II interface, a GPS receiver, a processor, and a cellular modem. Dr. Yeoh's claim chart (Appendix A) maps these system elements to Tanaka's hardware architecture, which is described in detail in Tanaka's specification and accompanying figures.
Tanaka discloses a telematics control unit (referred to in Tanaka as a "central processing module") that includes an OBD-II interface module for communicating with the vehicle's diagnostic port (Tanaka, col. 4, ll. 1–21), a GPS receiver module for receiving satellite positioning signals (col. 4, ll. 22–35), a processor (described as an ARM-based microcontroller) that executes software for data aggregation, compression, and encryption (col. 5, ll. 1–37), and a cellular modem module for 3G WCDMA data transmission (col. 5, ll. 38–52). Dr. Yeoh identifies Tanaka's "central processing module" as corresponding to the "telematics control unit" recited in Claim 14, and each sub-component of Tanaka's hardware architecture maps to a corresponding element of Claim 14.
Assessment — Claim 14 Anticipation. The anticipation analysis for Claim 14 tracks the analysis for Claim 1. Dr. Yeoh has assessed the probability of establishing anticipation of Claim 14 by Tanaka at 65–70%, consistent with the Claim 1 assessment.
Tanaka's Limitations with Respect to Claim 7. While Tanaka is a strong anticipation reference for Claims 1 and 14, it does not disclose the "adaptive interval" or "network congestion metric" limitations that are present in Claim 7. Specifically, Tanaka describes a fixed periodic transmission interval — the composite telemetry frame is transmitted every 60 seconds — with no mechanism for dynamically adjusting the interval based on network conditions. Tanaka, col. 8, ll. 21–35. Accordingly, Tanaka standing alone does not anticipate Claim 7 under § 102. However, Tanaka serves as the primary reference in an obviousness combination with Morales, as discussed in Section III.C below.
C. Prior Art Reference 2: Morales — PCT Application WO 2014/036281
The second principal prior art reference is Morales, PCT Application Publication No. WO 2014/036281 ("Morales"), published on March 13, 2014.
Prior Art Status. Morales qualifies as prior art under 35 U.S.C. § 102(a)(1) because it was published before the '312 Patent's effective filing date of September 12, 2015. The publication date of March 13, 2014 predates the priority date by approximately 18 months. There is no dispute regarding Morales's prior art status.
Subject Matter. Morales is directed to a method for adapting data transmission intervals in vehicular Internet of Things (IoT) devices based on cellular network load-balancing parameters. The Morales application describes a communication protocol for IoT devices installed in vehicles — including telematics sensors and diagnostic monitoring units — that adjusts the timing of data transmissions based on real-time information about the congestion status of the serving cellular base station. The protocol is designed to reduce data loss and improve transmission reliability by avoiding periods of peak network congestion.
Relevance to Claim 7 — Obviousness in Combination with Tanaka. While Morales does not independently disclose all of the elements of Claim 7 (it does not specifically describe the aggregation of OBD-II and GPS data into a combined data structure), Morales provides the critical disclosure of the "adaptive interval" and "network congestion metric" limitations that are absent from Tanaka. The combination of Tanaka and Morales renders Claim 7 obvious under § 103, as explained below.
"Adaptive interval" disclosure. Morales describes a transmission scheduling algorithm in which the time period between successive data transmissions from a vehicular IoT device is dynamically adjusted based on real-time network conditions. Morales, paras. [0042]–[0058]. Specifically, the Morales protocol monitors the congestion status of the cellular network and increases the transmission interval when congestion is high (to avoid contributing to network overload) and decreases the interval when congestion is low (to maximize data freshness). Id. at paras. [0049]–[0053]. The adjustment is performed autonomously by the device without human intervention. Id. at para. [0055].
"Network congestion metric" disclosure. Morales describes receiving congestion indicators from the serving cellular base station and using them to modulate the transmission frequency of the vehicular IoT device. Morales, paras. [0063]–[0071]. The congestion indicators described in Morales include: (i) a "load indicator" broadcast by the base station as part of the cellular control channel signaling; (ii) signal quality measurements (RSSI, RSRP, RSRQ) that reflect the level of traffic on the serving cell; and (iii) explicit congestion notification (ECN) signals embedded in data packets returned by the network. Id. at paras. [0065]–[0068]. Morales describes using these metrics as inputs to a scheduling algorithm that determines the adaptive transmission interval. Id. at paras. [0070]–[0071].
Motivation to Combine. A person of ordinary skill in the art at the time of the '312 Patent's invention would have been motivated to combine Tanaka's vehicle telemetry data aggregation and cellular transmission system with Morales's adaptive-interval and congestion-metric techniques for several reasons:
First, both Tanaka and Morales are in the same technical field — vehicular telematics and cellular data communication — and address closely related problems. A POSITA working on vehicle telematics systems in 2015 would have been aware of both types of references and would have considered their teachings in combination.
Second, Morales expressly discusses application of its adaptive transmission protocol to OBD-II telematics systems. Morales, para. [0035] ("The adaptive scheduling protocol described herein is particularly applicable to vehicle telematics systems that transmit OBD-II diagnostic data and sensor telemetry over cellular data connections, where network congestion can lead to data loss and delayed reporting."). This express statement provides a specific teaching and suggestion to apply Morales's adaptive interval technique to a system of the type disclosed in Tanaka.
Third, the combination involves applying a known technique (adaptive transmission scheduling based on network congestion) to a known device (vehicle telematics control unit with cellular data transmission) to yield a predictable result (improved bandwidth utilization and reduced data loss during high-congestion periods). Under KSR, this type of combination supports a finding of obviousness. 550 U.S. at 416–17.
Fourth, the problem of cellular network congestion affecting vehicle telematics data transmission was a well-known challenge in the industry as of the September 2015 priority date. Multiple industry publications and standards documents from this period discuss the need for adaptive transmission scheduling in vehicular IoT devices to address network congestion, confirming that a POSITA would have recognized the desirability of combining these approaches.
Dr. Yeoh's Assessment. Dr. Yeoh has assessed the probability of establishing that Tanaka in combination with Morales renders Claim 7 obvious at 65–70%. This probability assessment is somewhat tempered by the ambiguity in the Court's construction of "network congestion metric." If the Court or jury interprets the term narrowly — requiring an explicit, network-provided congestion signal — Morales maps extremely well to the claim limitation because Morales describes exactly such explicit signals (load indicators, ECN signals). If, however, the term is construed broadly to include implicit measures such as latency and packet loss, the Morales reference remains supportive but the argument is somewhat diluted because the distinction between Morales's explicit metrics and the implicit measures used by VMS's products becomes less clear-cut. Regardless, Dr. Yeoh considers the Tanaka/Morales combination to be a strong obviousness argument under either construction.
Dr. Yeoh's element-by-element claim chart for the Tanaka/Morales combination, including the motivation-to-combine analysis, is attached as Appendix B.
D. Additional Prior Art Considered
In preparing VMS's invalidity contentions, Dr. Yeoh conducted a comprehensive survey of prior art in the fields of vehicle telematics, OBD-II data processing, cellular data transmission protocols, and adaptive communication scheduling. This survey encompassed issued U.S. patents, published U.S. patent applications, PCT publications, academic publications, and industry standards documents. Several additional references were identified and evaluated, including:
• Hartmann et al. (U.S. Patent Application Publication No. 2013/0275623), which describes a vehicle diagnostic data collection system but does not disclose aggregation of GPS and OBD-II data into a single data structure or encryption of the aggregated data.
• Zhao (U.S. Patent No. 8,521,169), which describes a cellular network congestion management protocol but is directed to handset devices rather than vehicular telematics systems and does not disclose OBD-II data collection.
• IEEE 802.11p-related publications addressing vehicle-to-infrastructure communication, which operate in a different technical domain (DSRC/WAVE) than the cellular data transmission claimed in the '312 Patent.
While these additional references provide useful context regarding the state of the art, none were as strong as Tanaka and Morales for the specific claim elements at issue. Dr. Yeoh concluded that the Tanaka anticipation argument (for Claims 1 and 14) and the Tanaka/Morales obviousness combination (for Claim 7) represent VMS's strongest invalidity positions and should be the focus of the expert report and any dispositive motions.
It should also be noted that VMS's invalidity contentions were initially served during the period of Hargrove Dunn LLP's representation and have been supplemented by Calderwood & Harkness after assuming the engagement. The claim charts prepared by Dr. Yeoh have not yet been formally filed as expert reports, as the expert report deadline is May 30, 2025. To date, Dr. Yeoh's work product has been maintained as attorney work product and has not been produced or disclosed to Pinnacle.
E. Inequitable Conduct Defense
VMS's Answer and Counterclaims include a counterclaim for inequitable conduct, alleging that Dr. Prescott engaged in material misrepresentation or omission during the prosecution of the '312 Patent before the USPTO. Specifically, VMS alleged that Dr. Prescott failed to disclose material prior art references during prosecution and made affirmative misrepresentations regarding the novelty of the claimed invention.
Upon review of the complete prosecution history of the '312 Patent — including the original application as filed, all Office Actions, all applicant responses, all Information Disclosure Statements (IDS), and all examiner interviews — we have concluded that the evidence supporting the inequitable conduct counterclaim is weak. There are two principal reasons for this assessment:
First, Tanaka was cited in the prosecution history. Dr. Prescott filed an IDS on March 15, 2017, that included Tanaka (U.S. Patent No. 8,214,097) as a reference. The examiner considered the reference and initialed the IDS form. Although neither the examiner nor Dr. Prescott substantively discussed or distinguished Tanaka in the prosecution record, the fact that the reference was placed before the examiner significantly undermines any argument that it was intentionally withheld.
Second, the standard for inequitable conduct — as articulated by the Federal Circuit in Brightmoor & Co., Inc. v. Becton, Dickinson & Co., 649 F.3d 1276 (Fed. Cir. 2011) (en banc) — requires proof by clear and convincing evidence that the applicant (i) knew of material prior art, (ii) withheld it from the PTO or made a material misrepresentation, and (iii) did so with the specific intent to deceive the PTO. The "but-for" materiality standard set by Brightmoor & Co. is difficult to satisfy when the reference was disclosed and the intent-to-deceive requirement demands more than mere negligence or poor judgment. Given that Tanaka was cited in the IDS, demonstrating either "but-for" materiality (the examiner had the reference) or specific intent to deceive is a substantial challenge.
Assessment. The probability of prevailing on the inequitable conduct counterclaim is low. We recommend de-emphasizing this defense and focusing VMS's resources on the stronger invalidity and non-infringement arguments. However, we do not recommend voluntarily dismissing the counterclaim at this time, as its continued pendency may have strategic value in settlement negotiations and it imposes modest additional costs to maintain.
F. Overall Invalidity Probability Assessment
Based on the foregoing analysis and Dr. Yeoh's technical findings, our overall assessment of VMS's invalidity defenses is as follows:
• Claims 1 and 14 (Tanaka anticipation under § 102): 65–70% probability of invalidation at trial. The strength of this argument derives from the clean, element-by-element mapping of Tanaka's disclosures to the limitations of Claims 1 and 14, with no significant gaps requiring inherency arguments or expert interpretation.
• Claim 7 (Tanaka + Morales obviousness under § 103): 65–70% probability of invalidation at trial. This assessment is contingent on favorable resolution of the "network congestion metric" construction ambiguity. If the term is ultimately interpreted to require an explicit, network-provided congestion signal, the Morales reference maps directly and the obviousness argument is strong. If the term is construed broadly, the argument remains supportable but is somewhat less compelling.
• At least one independent claim: We assess a 65–70% composite probability of invalidating at least one of the three asserted independent claims at trial. Because the invalidity arguments for Claims 1 and 14 are based on the same prior art reference (Tanaka) and share similar strengths and weaknesses, the probability of invalidating at least one of these claims is correlated rather than independent. The addition of the Claim 7 obviousness argument provides a modest incremental benefit to the overall invalidity position.
• Caveats. These probability assessments are subject to inherent uncertainty. The clear and convincing evidence standard is a meaningful hurdle, and jury composition in the Eastern District of Texas adds significant variability to outcomes. Additionally, Pinnacle may present secondary considerations of nonobviousness (commercial success, long-felt need, failure of others) that could weaken the obviousness argument with respect to Claim 7, although we have not identified strong evidence of such secondary considerations in the record to date.
IV. Non-Infringement Analysis
A. Legal Standard
Patent infringement under 35 U.S.C. § 271(a) is established when the accused product or method practices each and every limitation of an asserted claim, either literally or under the doctrine of equivalents. Laitram Corp. v. Rexnord, Inc., 939 F.2d 1533, 1535 (Fed. Cir. 1991). It is the patentee's burden to prove infringement by a preponderance of the evidence. Harborview Corporation, Inc. v. Mirowski Family Ventures, LLC, 571 U.S. 191, 199 (2014). Claim construction, as established by the Court's Markman order, governs the scope and meaning of the claim terms for purposes of the infringement analysis. Markman v. Westview Instruments, Inc., 517 U.S. 370 (1996).
If the accused product or method does not satisfy even one limitation of a claim, there is no literal infringement of that claim. Bayer AG v. Elan Pharm. Research Corp., 212 F.3d 1241, 1247 (Fed. Cir. 2000). Under the doctrine of equivalents, a limitation is met if the accused element performs substantially the same function, in substantially the same way, to achieve substantially the same result as the claimed element. Warner-Jenkinson Co. v. Harborline Enterprises Davis Chem. Co., 520 U.S. 17, 40 (1997). However, the doctrine of equivalents is subject to several limiting principles, including prosecution history estoppel, which prevents a patentee from recapturing through equivalents claim scope that was surrendered during prosecution. Festo Corp. v. Fenmore & Co., 535 U.S. 722 (2002).
B. Non-Infringement Position — Claim 1
VMS's non-infringement argument with respect to Claim 1 centers on the "aggregated data packet" limitation. Under the Court's construction — "a single data structure containing data collected from at least two different sensor types combined prior to transmission" — VMS contends that DriveLink™ 4.0 does not practice this limitation in all operating modes.
Mode B (Split-Payload Mode). In Mode B, the DriveLink™ 4.0 transmits OBD-II diagnostic data and GPS telemetry data as separate, independent payloads. Each sensor type generates its own data structure, which is independently compressed, encrypted, and transmitted over the cellular data connection. In Mode B, OBD-II data is transmitted as a standalone JSON payload, and GPS telemetry data is transmitted as a separate JSON payload, with each payload sent in its own cellular data transmission. There is no step in Mode B where data from the two sensor types is "combined prior to transmission" into a "single data structure." Accordingly, DriveLink™ 4.0 operating in Mode B does not practice the "aggregated data packet" limitation and does not infringe Claim 1.
This argument is supported by Dr. Yeoh's review of the DriveLink™ 4.0 firmware source code (produced in discovery as VMS-DL-SC-000001 through VMS-DL-SC-004823), which confirms that Mode B implements separate data processing pipelines for OBD-II and GPS data, with no function call or data structure that combines the two data types into a single output. The technical architecture documentation for DriveLink™ 4.0 (produced as VMS-ARCH-000015 through VMS-ARCH-000042) further corroborates the separation of data flows in Mode B.
Mode A (Unified Mode). In Mode A, DriveLink™ 4.0 combines OBD-II diagnostic data and GPS telemetry data into a single JSON payload prior to transmission. The unified payload contains nested JSON objects for each data type, wrapped in a common data structure with a single header, timestamp, and device identifier. This unified payload is then compressed, encrypted, and transmitted as a single unit over the cellular data connection. Dr. Yeoh's analysis confirms that Mode A operation likely satisfies the "aggregated data packet" limitation under the Court's construction, as the data from two different sensor types (OBD-II and GPS) is combined into a single data structure prior to transmission.
Deployment Statistics. According to VMS's internal deployment records and configuration management data, approximately 60% of currently deployed DriveLink™ 4.0 units operate in Mode A (unified mode) and approximately 40% operate in Mode B (split-payload mode). The default configuration for new deployments is Mode A, although fleet operators can configure either mode through the FleetPulse™ administrative console. The distribution of operating modes across the installed base is relevant to the scope of potential infringement liability and damages exposure.
Net Assessment — Claim 1. The non-infringement argument with respect to Claim 1 is mixed. VMS has a strong position for units operating in Mode B (approximately 40% of the installed base), but the argument does not exculpate Mode A deployments (approximately 60% of the installed base). If the case proceeds to trial, Pinnacle will likely focus its infringement case on Mode A operation, where the "aggregated data packet" limitation appears to be satisfied. VMS may argue that Mode A operation was not the commercially significant mode at the time of the alleged infringement, but this is a damages argument rather than a liability argument. We assess the overall probability of prevailing on non-infringement for Claim 1 at 50–55%, reflecting the strength of the Mode B argument offset by the Mode A vulnerability.
C. Non-Infringement Position — Claim 7
Claim 7 is the most technically complex of the asserted claims and presents both VMS's strongest non-infringement argument and its most significant residual risk. The analysis turns on two claim limitations: "adaptive interval" and "network congestion metric."
"Adaptive Interval" Limitation. Under the Court's construction — "a time period between successive data transmissions that is dynamically adjusted based on one or more measured parameters" — VMS has a strong argument that DriveLink™ 4.0 does not practice this limitation during normal operation. The DriveLink™ 4.0 uses a server-configurable but fixed transmission schedule. The default transmission interval is 30 seconds, and fleet operators can adjust this interval to 15, 30, 60, or 120 seconds through the FleetPulse™ administrative console. Once configured, the interval remains fixed and is not changed by the device itself in real time based on any measured parameter. The transmission interval is determined by a human operator making a configuration choice, not by the device autonomously responding to measured conditions.
The strength of this argument derives directly from the Court's construction, which requires "dynamic" adjustment — a term that connotes real-time, autonomous, parameter-driven change by the device itself, as opposed to manual reconfiguration by a human operator. VMS's product design clearly falls outside this construction during normal operation.
However, there is a significant counterargument that Pinnacle will likely pursue. DriveLink™ 4.0 firmware includes a "retry backoff" algorithm that is invoked when a data transmission fails. Specifically, when a transmission attempt is unsuccessful (due to cellular connectivity loss, server timeout, or other transmission error), the firmware automatically increases the interval between successive retransmission attempts according to an exponential backoff schedule. The backoff interval starts at the configured transmission interval and doubles with each successive failed attempt, up to a maximum backoff interval of 600 seconds (10 minutes). The retry backoff algorithm operates autonomously without human intervention.
Pinnacle may argue that the retry backoff algorithm constitutes "dynamic adjustment" of the transmission interval "based on one or more measured parameters" (specifically, the measured parameter being the success or failure of the preceding transmission attempt). If the Court or jury accepts this characterization, the DriveLink™ 4.0 could be found to practice the "adaptive interval" limitation through its retry backoff behavior.
VMS's rebuttal to this argument is that retry backoff is an error-recovery mechanism, not a proactive, congestion-aware scheduling system. The '312 Patent specification describes the "adaptive interval" in the context of a system that affirmatively monitors network congestion conditions and adjusts its transmission schedule to optimize bandwidth utilization — not a system that simply retries failed transmissions with increasing delays. Retry backoff is a ubiquitous feature of virtually all networked communication systems and was well-known long before the '312 Patent. Characterizing retry backoff as "adaptive interval" scheduling would render the limitation so broad as to encompass nearly every networked device, which would undermine the construction the Court adopted.
"Network Congestion Metric" Limitation. This is the principal area of residual risk in VMS's non-infringement defense for Claim 7. The Court's construction — "a parameter indicative of the level of traffic or availability on a cellular data network" — is ambiguous with respect to whether the "parameter" must be an explicit metric received from the cellular network infrastructure or whether implicit, indirect measures of network conditions qualify.
As discussed in Section II.E, DriveLink™ 4.0 monitors transmission latency and retry success rates as part of its retry backoff logic. Specifically, the firmware tracks the round-trip time (RTT) for each transmission attempt and maintains a running average of RTT values. The firmware also records the number of consecutive failed transmission attempts and the success rate of recent transmissions. These metrics are used internally by the retry backoff algorithm to determine when to reattempt transmission and how aggressively to back off.
Pinnacle will likely argue that these metrics — transmission latency and retry success rates — are "parameters indicative of the level of traffic or availability on a cellular data network" within the Court's construction. Elevated transmission latency and low success rates, Pinnacle will contend, are symptoms of network congestion, and therefore monitoring them constitutes receiving a "network congestion metric." Under this theory, the retry backoff algorithm — which adjusts the transmission interval based on these metrics — would satisfy both the "adaptive interval" and "network congestion metric" limitations of Claim 7.
VMS's rebuttal is multi-faceted:
First, transmission latency and retry failures are not "network congestion metrics" in the sense contemplated by the '312 Patent specification. The specification describes the network congestion metric as an explicit signal received from the cellular network infrastructure — for example, a congestion notification from the base station or a network load indicator provided through control channel signaling. See '312 Patent, col. 9, ll. 14–38. DriveLink™ 4.0 does not query or receive any explicit congestion signal from the cellular infrastructure. The device has no awareness of the congestion status of the cellular network apart from the indirect inference that can be drawn from transmission failures and elevated latency.
Second, transmission latency and retry failures can result from numerous causes other than network congestion, including signal strength variations (the vehicle may be in a low-coverage area), server-side processing delays, hardware malfunctions, or transient radio interference. These metrics are not reliable or specific indicators of network congestion.
Third, the '312 Patent prosecution history supports a narrow interpretation of "network congestion metric." During prosecution, Dr. Prescott distinguished prior art by arguing that the prior art did not disclose receiving a "specific congestion indicator from the network" and instead relied on "general transmission quality metrics." This argument suggests that the inventors intended "network congestion metric" to refer to an explicit, dedicated congestion signal rather than a general-purpose quality metric like latency or packet loss.
Assessment — Claim 7. VMS's non-infringement position for Claim 7 is stronger than for Claims 1 and 14 due to the favorable "adaptive interval" construction, but the "network congestion metric" ambiguity creates meaningful residual risk. We assess the probability of prevailing on non-infringement for Claim 7 at 55–60%. The resolution of the "network congestion metric" construction ambiguity — whether through further briefing, a summary judgment ruling, or jury instruction — will be the single most important factor in determining the outcome of the Claim 7 infringement analysis.
D. Non-Infringement Position — Claim 14
Claim 14 is a system claim whose limitations parallel those of Claim 1, reciting a telematics control unit with an OBD-II interface, GPS receiver, processor, and cellular modem configured to perform the aggregation, compression, encryption, and cellular transmission steps. The non-infringement analysis for Claim 14 therefore largely tracks the Claim 1 analysis, with the Mode A/Mode B distinction serving as the primary basis for the defense.
In addition to the Mode A/Mode B argument, VMS has an incremental architectural distinction argument with respect to Claim 14. Claim 14 recites a specific hardware architecture in which the processor is "configured to aggregate" the OBD-II and GPS data. Dr. Yeoh identified minor differences between the DriveLink™ 4.0 hardware architecture and the architecture described in the '312 Patent and recited in Claim 14. Specifically, in DriveLink™ 4.0, the aggregation function (in Mode A) is performed by a dedicated microcontroller that operates as a co-processor alongside the main application processor, rather than being performed by a single processor as suggested by the claim language. However, Dr. Yeoh assessed these architectural distinctions as relatively minor and unlikely to carry the day independently. The claim language "a processor configured to aggregate" is sufficiently broad to encompass a system architecture in which the aggregation is performed by one of multiple processors or a co-processor, as the claim does not recite a single-processor architecture.
Assessment — Claim 14. We assess the probability of prevailing on non-infringement for Claim 14 at 50–55%. This assessment is somewhat weaker than the Claim 7 assessment because Claim 14 does not include the "adaptive interval" or "network congestion metric" limitations that provide VMS's strongest non-infringement arguments, and the Mode A exposure (60% of deployed units) is the dominant factor.
E. Doctrine of Equivalents Exposure
Even if VMS establishes literal non-infringement on one or more claim limitations, Pinnacle may pursue infringement under the doctrine of equivalents (DOE). Under DOE, a limitation is met if the accused element performs substantially the same function, in substantially the same way, to achieve substantially the same result as the corresponding claim limitation. This theory creates residual infringement risk, particularly with respect to the "aggregated data packet" limitation in the context of Mode B operation (where OBD-II and GPS data are transmitted in separate payloads that are arguably "substantially the same" as a single aggregated payload in function and result).
However, VMS has a strong prosecution history estoppel defense that should substantially limit Pinnacle's ability to pursue DOE. During the prosecution of the '312 Patent, Dr. Prescott amended the claims on November 8, 2017, in response to an Office Action rejecting the original, broader claims. The amendments added the "aggregated data packet" limitation (original claims recited only "data packet" without requiring aggregation of data from multiple sensor types) and the "adaptive interval" limitation (original claims recited only "transmitting at intervals" without requiring adaptive adjustment). These amendments narrowed the claim scope in response to prior art rejections, and under the doctr

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION / ATTORNEY WORK PRODUCT

MEMORANDUM

Record

Parties

Dates

Amounts