Connected Orange LLC v. Google LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Connected Orange LLC (Texas)
  • Defendant: Google LLC (Delaware)
  • Plaintiff's Counsel: Nelson Bumgardner Conroy PC; Cherry Johnson Siegmund James, PC
• Case Identification: 7:25-cv-00512, W.D. Tex., 02/24/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Google maintains a regular and established place of business in the district, including multiple large offices and a retail store in Austin, data centers, and numerous employees.
• Core Dispute: Plaintiff alleges that a wide range of Google's hardware and software products-including Android devices, the Pixel phone line, Google Wallet/Pay, Google Home/Nest devices, and the Google Fast Pair service-infringe five patents related to electronic payments, image display processing, wireless device pairing, and short-range communication.
• Technical Context: The asserted patents cover technologies central to the functionality of modern consumer electronics, such as secure mobile payments, efficient image gallery browsing, and seamless connectivity for smart home and peripheral devices.
• Key Procedural History: Plaintiff states it provided Defendant with pre-suit notice of infringement via a letter on August 28, 2025, which identified the asserted patents and accused products. The complaint also notes that prior licensing discussions had occurred with Allied Security Trust (AST), a defensive patent organization of which Google is a member. The complaint references the prosecution histories of the '088 and '016 patents to support its arguments for patent eligibility.

Case Timeline

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

U.S. Patent No. 8,341,088 - "Multipurpose Electronic Payment Method and System"

The Invention Explained

• Problem Addressed: The patent describes prior electronic payment systems as facing "security problems," being "practically independent, and, in all cases, too partial," and having "high implementation cost" Compl. ¶14 '088 Patent, col. 1:60-64
• The Patented Solution: The invention proposes a "multipurpose electronic payment method and system" implemented on a multimedia terminal (e.g., a mobile phone) Compl. ¶15 '088 Patent, col. 1:66-2:2 Its core component is a "payment proxy" that sits between a user application and the device's communication interface '088 Patent, col. 2:40-45 This proxy intercepts a payment order and, based on specific criteria, discriminates whether to process the payment locally on the device or transmit it to a remote payment server '088 Patent, abstract Compl. ¶16 The complaint provides a diagram from the '088 patent, illustrating a payment proxy architecture with modules for discriminating, local processing, and transmitting payment orders Compl. p. 6
• Technical Importance: This approach aimed to create a flexible and secure payment architecture on a single device, capable of handling different transaction types (e.g., proximity, remote) intelligently based on context like network availability.

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶48
• Essential elements of claim 1 include:
  • Transmitting a payment order from an application to a local payment proxy.
  • Determining in the proxy whether the order should be processed locally or remotely.
  • Processing the order locally if the determination is for local payment.
  • Transmitting the order to a remote system if the determination is for remote payment.
  • The determination step is based on a specific condition: processing remotely if the payment is a proximity or telepayment type AND a network connection is available; otherwise, processing locally.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 9,703,453 - "Image Display Apparatus and Processing Method for a Thumbnail Index Mode in a Device"

The Invention Explained

• Problem Addressed: At the time of the invention, the increasing resolution of digital camera images outpaced the display capabilities of devices, and existing methods for displaying parts of large images were inefficient, using too much memory and suffering from slow processing speeds, particularly when scrolling Compl. ¶22 '453 Patent, col. 1:32-36 '453 Patent, col. 2:25-36
• The Patented Solution: The patent describes a method to reduce CPU load and enable faster, higher-quality image display by creating and managing cache files '453 Patent, abstract Compl. ¶22 The system creates "shrunken images" (both high-resolution for single-image view and low-resolution thumbnails for index view) and "map data" that indexes the location of image data within the full encoded file, enhancing processing speed Compl. ¶23 '453 Patent, col. 3:66-4:2 This allows a device to quickly display a cached version of an image while partially decoding the full-resolution data in the background as needed Compl. ¶24
• Technical Importance: This technology addresses the fundamental challenge of providing a smooth user experience for browsing large photo galleries on memory-constrained mobile devices.

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶60
• Essential elements of claim 1 include:
  • A control section for a thumbnail index mode.
  • A cache file creation section that performs a "first cache file creation process" for displayed thumbnails.
  • The cache file creation section then performs a "second cache file creation process" to "preferentially" create cache files for other thumbnails within a predetermined range of the displayed ones.
  • A shrunken image output section that displays a shrunken image from the cache file "while the encoded image corresponding to the selected thumbnail is being decoded."
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 9,924,448 - "Device for Short-Range Communication, Adapted to Provide Access to a Remote Service"

Technology Synopsis

The patent describes a hub device that improves the security and functioning of connecting wireless terminals to remote services like cloud storage or streaming media Compl. ¶27 The hub receives an access request with identification parameters from a terminal, temporarily stores them to make a separate request to the remote service, and then transfers data upon receiving a response, ensuring one user cannot access another's service data '448 Patent, abstract Compl. ¶27

Asserted Claims

Independent claim 1 is asserted Compl. ¶72

Accused Features

The complaint accuses Google Home and Nest devices, such as the Nest Hub (2nd gen) and Nest Hub Max, which utilize Google Assistant and the Google Home app Compl. ¶70

U.S. Patent No. 9,955,347 - "Technique of Pairing In a Wireless Network"

Technology Synopsis

The patent addresses security and accuracy flaws in prior art device pairing techniques, where encryption keys could be intercepted or devices could be wrongly paired in environments with multiple networks Compl. ¶30 The invention uses a temporary, device-specific network where the device to be paired can securely obtain the private network's identifier and encryption key before switching over to the private network for final association '347 Patent, abstract Compl. ¶30

Asserted Claims

Independent claim 1 is asserted Compl. ¶84

Accused Features

The complaint accuses Google wireless devices, such as the Pixel phone line, that utilize Google's Fast Pair Service, a proprietary Bluetooth Low Energy pairing standard Compl. ¶82

U.S. Patent No. 10,096,016 - "Method of Communicating and Transmitting a Message Relating to a Transaction of a Contactless Application, Associated Terminal, Secure Module and System"

Technology Synopsis

The patent aims to improve the user experience of contactless transactions on mobile terminals by providing timely feedback without the high power consumption of constant polling Compl. ¶34 The invention describes a method where, upon detecting the end of a transaction, the system obtains and communicates a message to the user identifying the application used and confirming the transaction's completion, enabling synchronous, real-time feedback '016 Patent, abstract Compl. ¶37

Asserted Claims

Independent claims 1 and 16 are asserted Compl. ¶¶96-97

Accused Features

The complaint accuses Android wireless devices, including Pixel phones, that support Google Wallet and/or Google Pay Compl. ¶94

III. The Accused Instrumentality

Product Identification

The complaint names a broad set of Google products and services, categorized as the "Accused Products" Compl. ¶46 Compl. ¶58 Compl. ¶70 Compl. ¶82 Compl. ¶94 These include:

• Mobile Devices & OS: Android wireless devices, specifically including the Pixel phone line (e.g., Pixel 9 and 10 series).
• Payment Services: Google Wallet and Google Pay.
• Connectivity Services: Google's Fast Pair Service proprietary Bluetooth Low Energy pairing standard.
• Smart Home Devices: Google Home and Nest devices, including Nest Hub (2nd gen) and Nest Hub Max, which utilize Google Assistant and/or the Google Home app.

Functionality and Market Context

The accused functionalities are core features of Google's ecosystem. The complaint targets how these devices handle mobile payments ('088 and '016 Patents), display image galleries ('453 Patent), pair with peripherals ('347 Patent), and act as hubs for accessing remote services ('448 Patent) Compl. ¶49 Compl. ¶61 Compl. ¶73 Compl. ¶85 Compl. ¶97 These features are central to the user experience and commercial positioning of Google's hardware and the Android platform.

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits for each asserted patent, but these exhibits were not provided with the filed complaint document. The narrative infringement theories are summarized below.

'088 Patent Infringement Allegations

Narrative Summary

The complaint alleges that Google's Android devices supporting Google Wallet/Pay infringe at least claim 1 (Compl. ¶¶48-49). The infringement theory posits that these devices embody a method where a payment application generates a payment order that is intercepted by a "payment proxy" function. This proxy allegedly determines whether to conduct the transaction locally (on-device) or remotely (via a network), based on factors like payment type and network status, thereby meeting the limitations of claim 1 (Compl. ¶¶15-16).

Identified Points of Contention

• Scope Question: A likely point of dispute is whether the software architecture of Android's payment system constitutes a "payment proxy" that "intercepts" an order from a separate application, as described in the patent, or if it is a more integrated system falling outside the claim's scope.
• Technical Question: The analysis may focus on whether the accused devices perform the specific two-part logical test required by claim 1-evaluating both the "payment type" (proximity or telepayment) and "network" availability-to decide between local and remote processing.

'453 Patent Infringement Allegations

Narrative Summary

The complaint alleges that Google's display devices, including the Pixel 9 and 10 series, infringe at least claim 1 (Compl. ¶¶60-61). The theory centers on how these devices manage and display image galleries. It is alleged that the devices perform a "first" cache creation process for thumbnails currently on screen, and then "preferentially" create additional cache files for adjacent, off-screen thumbnails in a "second" process to enable smooth scrolling, which maps to the claim language (Compl. ¶¶23-24). The theory also alleges that a lower-resolution "shrunken image" is displayed from the cache while the full-resolution image is decoded in the background.

Identified Points of Contention

• Scope Question: A key issue will be whether the accused caching algorithm performs the distinct, sequential "first... and then preferentially" creation process as claimed, or if it uses a single, continuous caching logic that prioritizes images based on proximity to the viewport.
• Technical Question: A central factual question will be the temporal relationship between on-screen events: what evidence demonstrates that a cached "shrunken image" is displayed specifically "while the encoded image... is being decoded," as required by the claim?

V. Key Claim Terms for Construction

Term from '088 Patent, Claim 1: "payment proxy"

Context and Importance

This term is the central component of the claimed invention. The infringement case depends on whether Google's payment architecture in Android can be characterized as a "proxy." Practitioners may focus on this term because Google may argue its system is an integrated payment handler, not a distinct "proxy" that "intercepts" orders as depicted in the patent.

Intrinsic Evidence for Interpretation

• Evidence for a Broader Interpretation: The specification describes the proxy functionally as being "disconnection-mounted between this application and this communication interface, so as to intercept any payment order issued by this application" ('088 Patent, col. 2:42-45), which could support a construction not tied to a specific software structure.
• Evidence for a Narrower Interpretation: Figure 3 and the accompanying description depict the "payment proxy PP" as a distinct architectural element with specific modules (1, 2, 3) that receives an order from a separate "Multimedia application (AMM)" '088 Patent, col. 7:59-8:3 FIG. 3 This may support a narrower construction requiring a more modular software arrangement.

Term from '453 Patent, Claim 1: "preferentially creates a cache file... as a second cache file creation process"

Context and Importance

This phrase defines a specific, two-step algorithmic behavior. Infringement will turn on whether the accused devices' caching mechanism performs this sequential and preferential action. Practitioners may focus on this term because the distinction between the "first" and "second" processes is a potential non-infringement argument if Google's system uses a single, unified caching algorithm.

Intrinsic Evidence for Interpretation

• Evidence for a Broader Interpretation: The term could be construed to cover any system that, after creating an initial cache for the on-screen view, prioritizes caching for nearby thumbnails over more distant ones, fitting a functional definition of "preferentially."
• Evidence for a Narrower Interpretation: The claim's structure-"creates... as a first cache file creation process, and then preferentially creates... as a second cache file creation process"-suggests two distinct, sequential, and procedurally different steps. This phrasing may support a narrower construction requiring evidence of two separate modes of operation in the caching logic.

VI. Other Allegations

Indirect Infringement

The complaint alleges induced infringement for all five patents. The basis for these allegations is that Google knowingly encourages and instructs its customers and partners to infringe by creating and disseminating advertisements, user manuals, technical documentation, and developer tools that promote the use of the accused features (e.g., setting up Google Pay, using Google Fast Pair) Compl. ¶¶50-51 Compl. ¶¶62-63 Compl. ¶¶74-75 Compl. ¶¶86-87 Compl. ¶¶98-99

Willful Infringement

Willfulness is alleged for all five patents, based on alleged pre-suit knowledge Compl. ¶53 Compl. ¶65 Compl. ¶77 Compl. ¶89 Compl. ¶101 The complaint asserts that Google was put on notice of its infringement through a letter sent on August 28, 2025, which identified the patents and accused products, and that Google "ignored the notice of infringement" and continued its allegedly infringing activities Compl. ¶102

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

This case presents a broad challenge to core functionalities within Google's hardware and software ecosystem. The outcome will likely depend on the court's resolution of several key questions:

• A core issue will be one of architectural equivalence: For patents like the '088 (payment proxy) and '448 (communications hub), can the modular architectures described and claimed in the patents be read onto Google's deeply integrated software systems? The case may turn on whether a "proxy" or "hub" is defined by its function or by a specific, separable structure that may not exist in the accused products.
• A second key issue will be one of algorithmic specificity: For patents like the '453 (image caching) and '347 (wireless pairing), the dispute will likely focus on whether the accused services perform the precise, multi-step processes recited in the claims. For example, does Google's image caching follow the "first process, then second preferential process" of claim 1 of the '453 patent, or does it operate in a technically distinct manner?
• A significant question for damages will be one of willfulness: The complaint alleges that Google was provided with specific pre-suit notice and ignored it. Discovery regarding Google's response to the August 2025 notice letter will be critical in determining whether its continued conduct was objectively reckless, which could expose it to the risk of enhanced damages.