DCT

2:25-cv-00785

Aprese Systems Texas LLC v. Hyundai Motor Co

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:25-cv-00785, E.D. Tex., 03/23/2026
  • Venue Allegations: Venue is asserted on the basis that the Defendant, Hyundai Motor Company, is a foreign corporation and has placed the accused products into the stream of commerce with the expectation that they will be used by customers in the judicial district.
  • Core Dispute: Plaintiff alleges that Defendant’s vehicle infotainment systems that support Android Auto functionality infringe patents related to systems and methods for enabling the delivery and access of applications and services based on contextual information.
  • Technical Context: The technology at issue addresses the integration of smartphone applications with vehicle infotainment systems, a standard and commercially significant feature in the modern automotive market.
  • Key Procedural History: U.S. Patent 9207924 was the subject of an ex parte reexamination proceeding filed on March 26, 2021. A reexamination certificate for the patent was issued on August 7, 2024, suggesting that the patent's claims survived a validity challenge before the U.S. Patent and Trademark Office.

Case Timeline

Date Event
2010-08-04 Earliest Priority Date ('924 and '378 Patents)
2014-12-31 '924 Patent Application Filing Date
2015-12-08 '924 Patent Issue Date
2021-03-26 '924 Patent Ex Parte Reexamination Filing Date
2022-12-30 '378 Patent Application Filing Date
2024-02-06 '378 Patent Issue Date
2024-08-07 '924 Patent Reexamination Certificate Issue Date
2026-03-09 Alleged Notice Date for '924 Patent
2026-03-23 Amended Complaint Filing Date

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

U.S. Patent No. 11,893,378: “METHOD, APPARATUS, AND SYSTEMS FOR ENABLING DELIVERY AND ACCESS OF APPLICATIONS AND SERVICES” (Issued Feb. 6, 2024)

The Invention Explained

  • Problem Addressed: The patent's background describes the process of discovering, installing, and using applications on consumer devices as potentially "tedious and/or impractical," particularly when the user's context changes (e.g., visiting different stores or interacting with different segments of a media broadcast) (U.S. Patent No. 11,893,378, col. 2:30-51). Traditional methods like scanning bar-codes or manually entering URLs are described as not being practical or user-friendly ('378 Patent, col. 2:1-24).
  • The Patented Solution: The invention proposes a system to automate and simplify access to applications by using "contextual information" ('378 Patent, field of invention). The system determines the "context" of a user or their device—describing their environment or activity—and generates a corresponding "contextual tag" ('378 Patent, abstract). This tag enables the computing device to identify and access one or more relevant applications, facilitating a more seamless user experience ('378 Patent, abstract; '378 Patent, col. 3:25-40). The architecture generally involves communication between a "consumer device" that accesses the application and a "provider device" that helps generate and transmit the contextual tags ('378 Patent, FIG. 1A).
  • Technical Importance: This approach aims to make application discovery dynamic and responsive to a user's real-world situation, reducing the friction of manually searching for and launching appropriate software for a given task.

Key Claims at a Glance

  • The complaint asserts independent claim 1 and dependent claims 2-7, 9, and 10 (Compl. ¶30).
  • Independent Claim 1 (System): The claim recites a "consumer device" for enabling application access, comprising a non-transitory storage medium with instructions that, when executed, enable the device to perform steps including:
    • Enabling user interaction via a touch screen and displaying information.
    • Determining the presence of a connected "ANDROID smartphone" which has several sets of applications installed.
    • Receiving "generator information" (comprising a "third tag type") from the smartphone.
    • Sending "provider information" (comprising a "fourth tag type") to the smartphone.
    • Receiving "a first tag related information" from the smartphone.
    • Determining a "first tag" based on that information.
    • Sending the "first tag" to the ANDROID smartphone, which in turn enables the smartphone to determine, access, and execute a "first application."
    • Enabling a "user interface element" on the consumer device that allows a user to initiate the sending of the "first tag."

U.S. Patent No. 9,207,924: “APPARATUS FOR ENABLING DELIVERY AND ACCESS OF APPLICATIONS AND INTERACTIVE SERVICES” (Issued Dec. 8, 2015)

The Invention Explained

  • Problem Addressed: As a parent to the '378 patent, the '924 patent addresses the same fundamental problem: the difficulty and tedium for users in finding and managing applications that are relevant to their immediate context or task (U.S. Patent No. 9,207,924, col. 1:47-2:20).
  • The Patented Solution: The solution is architecturally consistent with the '378 patent, describing a system where a "provider device" associates with a "consumer device" to facilitate access to applications using contextual information, or "tags" (U.S. Patent No. 9,207,924, abstract; '924 Patent, col. 5:25-45). The system is designed to simplify provisioning and management of applications based on a user's environment and activities ('924 Patent, summary).
  • Technical Importance: The technology provides a framework for context-aware computing, where the availability and accessibility of software applications adapt dynamically to the user's situation.

Key Claims at a Glance

  • The complaint asserts independent claim 9 and dependent claims 10-13 and 15 (Compl. ¶54).
  • Independent Claim 9 (Apparatus): The claim recites a non-transitory computer-readable storage medium for a "provider device" containing instructions that, when executed, enable a processor to:
    • Associate the provider device with a "consumer device" via a wired or wireless communication interface.
    • Enable the display of content on the consumer device.
    • Enable the retrieval of a "second plurality of information" from the consumer device.
    • Enable a portion of that information to be determined based on user interaction with the consumer device.
    • Send a portion of that information to the consumer device, enabling it to determine a "first application."
    • Associate a "first user interface element" with instructions that, when executed based on user interaction, enable the determination and sending of the information.

III. The Accused Instrumentality

Product Identification

  • The accused products are Hyundai infotainment systems that support Android Auto functionality, as found in vehicles including the Santa Fe and Tucson models (Compl. ¶20).

Functionality and Market Context

  • The complaint alleges that the accused infotainment systems are designed to connect to a user's smartphone to provide interactive services through applications (Compl. ¶29; Compl. ¶53). This connection can be established via a wired USB cable or wirelessly using Wi-Fi and Bluetooth (Compl. p. 5; Compl. p. 6). Once connected, the system enables "phone mirroring," which displays and allows control of smartphone applications on the vehicle's built-in touchscreen (Compl. p. 4). A screenshot from a Hyundai manual shows the system setting to "Enable Android Auto" (Compl. p. 5). Another screenshot illustrates the "Use Wi-Fi for phone projection" setting for wireless connections (Compl. p. 6).
  • The complaint highlights Hyundai's marketing and instructional materials, including a YouTube video titled "Hyundai How-to: Android Auto™," which allegedly encourage customers to use the accused functionality (Compl. p. 7; Compl. ¶22). This suggests the feature is a significant, promoted aspect of the user experience in these vehicles.

IV. Analysis of Infringement Allegations

The complaint incorporates by reference preliminary claim charts that were not attached to the filing (Compl. ¶31; Compl. ¶55). The following analysis summarizes the infringement theory as constructed from the complaint's narrative allegations and visual evidence.

'378 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a consumer device for enabling filtering of applications... The Hyundai vehicle infotainment head unit, which provides access to applications from a connected smartphone (Compl. ¶20; Compl. ¶29). ¶20; ¶29 col. 25:25-30
determining presence of an ANDROID smartphone connected to a communication interface... The infotainment system detects the connection of an Android smartphone via USB or wireless (Wi-Fi/Bluetooth) interfaces (Compl. ¶21; Compl. pp. 5-6). ¶21 col. 27:1-5
receiving a generator information on said communication interface from said ANDROID smartphone... The head unit allegedly receives information from the connected smartphone that establishes its capabilities and available applications (Compl. ¶¶48-50). ¶¶48-50 col. 9:25-40
sending a provider information on said communication interface to said ANDROID smartphone... The head unit allegedly sends its own information to the smartphone to establish the Android Auto session (Compl. ¶¶48-50). ¶¶48-50 col. 9:25-40
sending at least said first tag to said ANDROID smartphone... User interaction with an application icon on the vehicle's touchscreen (the "user interface element") sends a command ("tag") to the connected smartphone, causing it to launch or interact with the corresponding application (Compl. p. 4). ¶50 col. 28:5-14

'924 Patent Infringement Allegations

Claim Element (from Independent Claim 9) Alleged Infringing Functionality Complaint Citation Patent Citation
a non-transitory computer-readable storage medium having at least a computer-readable program... executed by a processor enables said provider device to at least... The storage medium within the Hyundai infotainment system (the alleged "provider device") containing the software for Android Auto functionality (Compl. ¶73). ¶73 col. 51:50-57
associate said provider device with a consumer device... using at least one or more of a wired communication interface and a wireless communication interface... The Hyundai head unit connects with the user's smartphone (the alleged "consumer device") via USB or Wi-Fi/Bluetooth (Compl. pp. 5-6). A Hyundai manual provides instructions for setting up these connections (Compl. p. 5). ¶58 col. 6:49-67
enable at least one or more of: i. display of a first content on a display associated with said consumer device... The Hyundai head unit enables the display of the Android Auto user interface and application icons on its own screen, which is then used by the consumer (Compl. p. 4). ¶58 col. 26:1-12
enable retrieval of a second plurality of information... The system retrieves a list of available and compatible applications from the connected smartphone to display in the Android Auto interface (Compl. p. 5, "Smartphone connectivity"). ¶58 col. 7:1-10
associate a first user interface element with at least a first set of instructions... The on-screen application icons are the user interface elements. A user's touch interaction with an icon executes instructions to send information to the phone to launch the selected app (Compl. p. 6, "Touch an icon on the screen to access its corresponding function."). ¶58 col. 8:41-51
  • Identified Points of Contention:
    • Role Inconsistency: A potential issue for litigation is the apparent inconsistent mapping of the physical devices to the claimed roles. The infringement theory for the '378 patent appears to cast the Hyundai head unit as the "consumer device," while the theory for the '924 patent appears to cast the same head unit as the "provider device." How these roles are defined and evidenced will be a central point of contention.
    • Scope of "Tag": The infringement theory rests on the premise that the data communications within the Android Auto protocol constitute the "tags" and "tag related information" described in the patents. A key question for the court will be whether these standard communication packets fall within the scope of the patent's more specific descriptions of contextual tags (e.g., tags for voting, sales schedules, or store orders).
    • Technical Operation: A factual dispute may arise over whether the accused system's operation mirrors the specific sequence of steps claimed (e.g., receiving "generator information," then sending "provider information," then receiving "tag information"). The defense may argue that Android Auto operates on a different technical principle, such as functioning as a remote terminal that streams video from the phone and relays touch inputs back to it, rather than performing the claimed sequence of information exchange.

V. Key Claim Terms for Construction

  • Term: "consumer device" / "provider device"

    • Context and Importance: The plaintiff's infringement case requires mapping the Hyundai head unit and the smartphone to these distinct roles, which appear to be reversed between the two asserted patents. The construction of these terms will be foundational to determining whether the accused system's architecture meets the claims.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The specifications describe the devices in functional terms. A "consumer device" is a device for managing and accessing applications, and a "provider device" is one that can provision or manage applications using contextual information ('924 Patent, col. 5:25-35). An argument could be made that the head unit and smartphone perform both functions at different times.
      • Evidence for a Narrower Interpretation: The specifications' examples consistently depict the "consumer device" as a portable, user-centric device like a smartphone or PDA, and the "provider device" as a source of contextual data or services, like a store's system or a media broadcaster ('378 Patent, col. 1:28-32; '378 Patent, col. 2:40-51). This could support an argument that a fixed vehicle head unit does not fit the "consumer device" role and is not a "provider" of applications.

  • Term: "tag" / "tag related information"

    • Context and Importance: This term is the technical core of the invention. Whether the data exchanged in the Android Auto protocol qualifies as a "tag" will be a dispositive issue. Practitioners may focus on this term because the patents describe specific, structured, context-based tags, while the accused system uses a standardized communication protocol.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The specification provides a broad definition, stating a "tag" can "encompass any type of data that facilitates determination of an application (app)" ('924 Patent, col. 5:35-38). This could support arguing that any data packet that results in an app being identified or launched is a "tag."
      • Evidence for a Narrower Interpretation: The patents provide numerous specific examples of "contextual tags" with structured data fields, such as GroceryInfo, ParkingLot, TvLiveVoting, and UserOrderInStore ('924 Patent, FIG. 4A-4B). This detailed disclosure may support a narrower construction limited to data packets that contain explicit, structured information about the user's real-world context, rather than general command-and-control data.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement. Inducement is primarily based on Hyundai's creation and publication of instructional materials, user manuals, and promotional videos that allegedly direct and encourage customers to configure and use the infringing Android Auto functionality (Compl. ¶¶37-38; Compl. ¶¶61-62). Contributory infringement is alleged on the basis that the head unit and its Android Auto features are especially made to be used in an infringing manner and have no substantial non-infringing use (Compl. ¶¶41-44; Compl. ¶¶65-68).
  • Willful Infringement: Willfulness is alleged based on Hyundai's continued infringement after receiving notice of the patents. For the '378 Patent, notice is alleged from the date of service of the original complaint (Compl. ¶24; Compl. ¶46). For the '924 Patent, notice is alleged from "at least as early as March 9, 2026" (Compl. ¶26; Compl. ¶70).

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

This case will likely focus on fundamental questions of claim scope and the mapping of claimed concepts onto a widely used, standardized technology. The central issues for the court will be:

  1. A core issue will be one of architectural mapping: Can the distinct roles of "consumer device" and "provider device," as claimed in the patents, be consistently and coherently mapped onto the physical components of the accused system (the Hyundai head unit and the user's smartphone), particularly when the alleged role of the head unit appears to differ between the two asserted patents?
  2. A second key issue will be one of definitional scope: Does the term "tag," which is described in the patents with specific reference to structured, context-based information (e.g., store location, media content, user activity), read on the generalized data packets used in the standard Android Auto communication protocol?
  3. A third question will be one of technical function: Does the evidence show that the accused infotainment systems perform the specific, multi-step sequence of receiving and sending distinct categories of information ("generator," "provider," "tag") as recited in the claims, or does the system operate on a fundamentally different principle, such as acting as a remote display for the smartphone?
Loading Amended Complaint