IOEngine LLC v. Garmin Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: IOEngine, LLC (Delaware)
  • Defendant: Garmin Ltd. (Switzerland); Garmin International, Inc. (Kansas); and Garmin USA, Inc. (Kansas)
  • Plaintiff’s Counsel: Peretz Chesal & Herrmann, P.L.
• Case Identification: 1:26-cv-26708, S.D. Fla., 09/25/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Southern District of Florida because Defendants maintain a regular and established place of business—a Garmin retail store—at 515 Lincoln Road, Miami Beach, from which infringing acts are alleged to have been committed.
• Core Dispute: Plaintiff alleges that Defendant’s smartwatches and fitness bands, when used with the Garmin Connect mobile application, infringe four patents related to a system where a portable computing device securely uses the user interface and network connection of a larger host device.
• Technical Context: The technology addresses the challenge of providing small, portable computers with robust user interfaces and network access by enabling them to securely "tunnel" through and leverage the resources of a connected host computer, such as a smartphone.
• Key Procedural History: The patents-in-suit belong to a single patent family sharing a common specification. Plaintiff IOENGINE alleges it granted a single license for its '969 patent to Interactive Media Corporation ("IMC") in May 2018 and that IMC has complied with patent marking requirements for its licensed products.

Case Timeline

Date	Event
2004-03-23	Earliest Priority Date for all Patents-in-Suit
2015-06-16	U.S. Patent No. 9,059,969 Issues
2018-05-01	Approximate date license granted to Interactive Media Corporation
2019-08-27	U.S. Patent No. 10,397,374 Issues
2019-10-15	U.S. Patent No. 10,447,819 Issues
2021-04-27	U.S. Patent No. 10,992,786 Issues
2024-03-23	Alleged expiration of U.S. Patent Nos. 10,447,819 and 10,397,374
2024-04-10	Alleged expiration of U.S. Patent No. 9,059,969
2024-04-13	Alleged expiration of U.S. Patent No. 10,992,786
2026-09-25	Complaint Filed

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

U.S. Patent No. 9,059,969 - Apparatus, Method and System for a Tunneling Client Access Point

The Invention Explained

• Problem Addressed: The patent’s background section describes that early portable computing devices like Personal Digital Assistants (PDAs) were an unsatisfying compromise, being bulky, power-hungry, and having small, uncomfortable user interfaces and limited data security (Compl. ¶¶29-31; '969 Patent, col. 2:26-39).
• The Patented Solution: The invention is a small, portable computing device, termed a "tunneling client access point" or "TCAP," that connects to a larger host computer, or "access terminal" (AT), to borrow its user interface and peripherals Compl. ¶32 This allows the portable device to remain small and power-efficient while providing a rich user experience Compl. ¶33 Critically, the '969 Patent describes an architecture where the portable device "tunnels" through the host computer to access a communications network via the host's own network connection, providing secure remote data access similar to a plug-and-play VPN (Compl. ¶¶38-39; '969 Patent, col. 4:25-41).
• Technical Importance: This architecture solved several key problems at once, enabling the creation of highly portable, secure, low-power devices that could still leverage the I/O and network capabilities of ubiquitous larger computers Compl. ¶31

Key Claims at a Glance

• The complaint asserts dependent claims 4 and 10, which incorporate independent claim 1 by reference Compl. ¶61
• The essential elements of independent claim 1 are:
  • A portable device configured to communicate with a terminal that has its own processor, I/O components, network interface, and memory storing program code.
  • The terminal program code includes a "second program code" that provides a "communications node on the terminal" to facilitate communications to the portable device and to a communications network node through the terminal's network interface.
  • The portable device comprises an external communication interface, a processor, and memory storing program code.
  • The portable device's program code includes a "third program code" configured to coordinate with the communications node on the terminal, establish a link, and facilitate communications to a network node through the terminal network communication interface.
  • The portable device's program code includes a "fourth program code" that is executed in response to user interaction with the terminal's user interface.
  • The portable device is configured to facilitate these communications through the terminal's communications node and network interface to the network node.

U.S. Patent No. 10,447,819 - Apparatus, Method and System for a Tunneling Client Access Point

The Invention Explained

• Problem Addressed: The '819 Patent addresses the same problems of early portable computing as the '969 Patent Compl. ¶¶28-31
• The Patented Solution: The '819 Patent describes a similar system of a portable device ("TCAP") interacting with a host computer ("terminal"). However, the architecture claimed in the '819 Patent is one where the portable device connects to a communications network through a network connection of its own, separate from its connection to the terminal Compl. ¶39 '819 Patent, col. 2:52-55 The portable device streams data content to the terminal for presentation while also communicating independently with a network Compl. ¶84 '819 Patent, col. 4:51-54
• Technical Importance: This provided an alternative architecture where a small device could have its own direct network access (e.g., via Wi-Fi) while still using a host terminal for display and control, enhancing its standalone capabilities.

Key Claims at a Glance

• The complaint asserts independent claim 184 Compl. ¶79
• The essential elements of independent claim 184 are:
  • A portable device configured to communicate with a communications network and a terminal.
  • The portable device comprises:
    • a. A network interface for communication between the portable device and the communications network node.
    • b. A communications interface for communication between the portable device and the terminal.
    • c. A processor configured to stream data content for presentation by the terminal.
    • d. A memory storing program code, including:
      • "second program code" to enable the portable device to communicate with the network node.
      • "third program code" which, in response to a command from the terminal, causes a communication to be transmitted through the portable device's network interface to the network node.
      • "fourth program code" to process data content received from the network node for transmission to the terminal.

U.S. Patent No. 10,397,374 - Apparatus, Method and System for a Tunneling Client Access Point

• Patent Identification: U.S. Patent No. 10,397,374 ("the '374 Patent"), "Apparatus, Method and System for a Tunneling Client Access Point," issued August 27, 2019.
• Technology Synopsis: The '374 Patent addresses the same technical problem as the other patents-in-suit Compl. ¶¶28-31 It claims an architecture where the portable device can reach a network node through either its own network connection or by leveraging the network connection of the terminal Compl. ¶39 Asserted claim 3 specifically captures an architecture where the device uses both its own connection and the terminal's connection Compl. ¶107
• Asserted Claims: Claims 1 (independent) and 3 Compl. ¶95
• Accused Features: Wi-Fi-equipped Garmin smartwatches are accused of infringement by virtue of their ability to reach Garmin's servers either directly over their own Wi-Fi connection or through the network connection of a paired smartphone (Compl. ¶¶97, 107).

U.S. Patent No. 10,992,786 - Apparatus, Method and System for a Tunneling Client Access Point

• Patent Identification: U.S. Patent No. 10,992,786 ("the '786 Patent"), "Apparatus, Method and System for a Tunneling Client Access Point," issued April 27, 2021.
• Technology Synopsis: The '786 Patent also addresses the limitations of early portable devices Compl. ¶¶28-31 Like the '374 Patent, it claims an architecture where the portable device is capable of using either its own network connection or the terminal's Compl. ¶39 Asserted claim 20 specifically covers the architecture where the portable device uses both its own connection and the terminal's connection to reach a network node Compl. ¶127
• Asserted Claims: Claims 1 (independent) and 20 Compl. ¶112
• Accused Features: The accused features are the same as for the '374 Patent: Wi-Fi-equipped Garmin smartwatches that can connect to servers directly via Wi-Fi or by using a paired smartphone's internet connection (Compl. ¶¶114, 127).

III. The Accused Instrumentality

Product Identification

The Accused Products are Garmin’s smartwatches and fitness bands (including the Venu, Fenix, and Forerunner lines, among others), together with the Garmin Connect application that runs on a smartphone or other computer, and the Garmin servers and services with which the devices communicate Compl. ¶45 The complaint focuses on the Garmin Fenix E and Fenix 5 smartwatches as primary examples Compl. ¶45

Functionality and Market Context

The complaint alleges that a Garmin smartwatch is a portable device containing a processor, memory, and communication interfaces (e.g., Wi-Fi, Bluetooth) Compl. ¶47 It is designed to be paired with a smartphone running the Garmin Connect application, which acts as the "terminal" Compl. ¶49 Users interact with the Garmin Connect app on the smartphone's touchscreen to control the watch, customize metrics, and sync data Compl. ¶48 Data is synchronized between the watch and Garmin's servers either by "tunneling" through the paired smartphone's network connection (e.g., via a Bluetooth link) or, on Wi-Fi-equipped models, by connecting directly to the servers using the watch's own Wi-Fi radio Compl. ¶¶52-53 A screenshot from a Garmin instructional video shows the Garmin Connect app interface on a smartphone screen, illustrating how a user interacts with the terminal to manage the portable device Compl. ¶66 Compl. p. 20 The complaint asserts that wearable devices are central to Garmin's business, with the company shipping over 20 million units in fiscal year 2025 Compl. ¶46

IV. Analysis of Infringement Allegations

9,059,969 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A portable device configured to communicate with a terminal...	Garmin smartwatches are the "portable device" and are configured to communicate with a smartphone, the "terminal" Compl. ¶63	¶63	col. 2:39-42
...the terminal comprising a processor, an input component, an output component, a network communication interface, and a memory configured to store executable program code...	A paired smartphone has a processor, a touchscreen (input/output), Wi-Fi/cellular radios (network interface), and memory storing the Garmin Connect app (program code) Compl. ¶64	¶64	col. 3:46-49
...second program code which... is configured to provide a communications node on the terminal to facilitate communications... to a communications network node through the terminal network communication interface...	The Garmin Connect app on the smartphone acts as the "communications node," passing communications to the watch and to Garmin's servers via the smartphone's Wi-Fi or cellular connection Compl. ¶67	¶67	col. 4:8-14
...the portable device comprising: (a) an external communication interface... (b) a processor; and (c) a memory...	The watch has Wi-Fi/Bluetooth/ANT+ radios (external interface), a processor, and memory storing executable code Compl. ¶¶68-69	¶¶68-69	col. 3:55-57
...third program code which... is configured to... facilitate communications to... a communications network node through the terminal network communication interface...	Watch code enables the watch to send messages to Garmin's servers (the network node) using the smartphone's internet connection (the terminal network interface) Compl. ¶70	¶70	col. 4:39-41
...fourth program code which is configured to be executed... in response to a communication received... resulting from user interaction with the interactive user interface...	When a user interacts with the Garmin Connect app on the smartphone, the phone sends a message to the watch, which in turn causes code on the watch to execute Compl. ¶71	¶71	col. 4:56-62

10,447,819 Infringement Allegations

Claim Element (from Independent Claim 184)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A portable device configured to communicate with a communications network... and with a terminal...	Wi-Fi-equipped Garmin smartwatches ("portable device") communicate with Garmin's servers ("communications network") and with smartphones running the Connect app ("terminal") Compl. ¶81	¶81	col. 3:46-52
a. a network interface configured to enable... communications between the portable device and the communications network node...	Wi-Fi-equipped watches have a Wi-Fi radio ("network interface") to communicate directly with Garmin's servers ("network node") to download software updates and upload activities Compl. ¶83	¶83	col. 3:55-57
b. a communications interface configured to enable... communications between the portable device and the terminal...	Watches use Bluetooth, ANT+, and Wi-Fi ("communications interface") to stream activity and health data to the Garmin Connect app on the smartphone ("terminal") Compl. ¶84	¶84	col. 3:55-57
c. a processor configured to stream data content for presentation by the terminal output component...	The watch's processor streams activity data to the app for presentation on the smartphone's touchscreen. A teardown image shows the processor on the device's circuit board Compl. ¶¶85-86	¶¶85-86	col. 4:1-4
...third program code which... causes a communication to be transmitted through the portable device network interface to the communications network node...	Interacting with the app on the smartphone causes the watch to execute code that sends a message to Garmin's servers using the watch's own Wi-Fi connection Compl. ¶89	¶89	col. 5:61-65
...fourth program code which... processes data content received from the communications network node... for transmission through the communications interface to the terminal...	When a watch downloads content (e.g., a software update) from Garmin's servers over its Wi-Fi, code on the watch processes it and transmits it to the paired smartphone for presentation in the app Compl. ¶90	¶90	col. 4:51-54

• Identified Points of Contention:
  • Scope Questions: A central question may be whether a modern smartphone running a high-level application (Garmin Connect) qualifies as a "terminal" and a "communications node on the terminal" as those terms are used in the patents, which were conceived in an era of desktop computers and device drivers (Compl. ¶¶3-5). The defense may argue that the specification's focus on "desktop or laptop computer[s]" and "traditional large user interfaces" limits the scope of "terminal" to exclude smartphones Compl. ¶31 Compl. ¶32
  • Technical Questions: For the '969 Patent, a key question is whether the Garmin Connect app functionally meets the claim requirement of a "communications node on the terminal" that "facilitates" communication to a network "through the terminal network communication interface." For the '819 Patent, the analysis will likely focus on whether the accused system's software is actually structured into the distinct "first", "second", "third", and "fourth" program codes as required by the claim, or if this is a post-hoc characterization of a more monolithic software architecture.

V. Key Claim Terms for Construction

• The Term: "terminal"

• Context and Importance: The patents were filed in 2004, with the specification describing the "terminal" (or "access terminal") in the context of desktop and laptop computers Compl. ¶32 The complaint alleges that a modern smartphone running the Garmin Connect app is a "terminal" Compl. ¶49 The viability of the infringement case depends on this term being construed broadly enough to cover smartphones.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification states a terminal may be "any number of computing devices such as servers, workstations, desktop computers, laptops, portable digital assistants (PDAs), and/or the like" '969 Patent, col. 3:46-49 The inclusion of "PDAs" and "the like" suggests the term is not limited to large computers. The specification further states, "[t]he type of AT used is not important" as long as it provides a compatible engagement mechanism and operating environment '969 Patent, col. 3:49-52
  • Evidence for a Narrower Interpretation: The specification repeatedly uses "desktop or laptop computer" as the primary exemplary embodiment '969 Patent, col. 2:41-42 The problem solved is framed as allowing users to employ "traditional large user interfaces" '969 Patent, col. 2:35-36, which may suggest a device larger and more traditional than a smartphone. The patent figures consistently depict desktop or laptop computers as the terminal.

• The Term: "communications node on the terminal" '969 Patent, claim 1

• Context and Importance: This term describes a functional software component on the host device that acts as an intermediary. The complaint alleges the Garmin Connect app itself constitutes this "node" Compl. ¶67 Whether a user-level application can be considered a "communications node" in the context of the patent will be a critical point of construction.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The claim language is purely functional, requiring a "node" that is "configured to... facilitate communications." This could be interpreted to encompass any software, regardless of its level in the OS stack, that performs the recited function.
  • Evidence for a Narrower Interpretation: The specification discusses loading a "driver" onto the AT and using an "API" to communicate '969 Patent, col. 5:15-18 This may support an argument that the "communications node" must be a lower-level system component, like a driver, rather than a user-space application. A screenshot in the complaint of the app's "Create Account" screen could be used to argue it is a standard application, not a specialized "node" Compl. p. 30

VI. Other Allegations

• Indirect Infringement: The complaint alleges facts that may support a claim for induced infringement. It states that Garmin instructs users on how to pair and sync their devices in an allegedly infringing manner through materials such as support pages and instructional videos Compl. ¶¶50, 66, 70
• Willful Infringement: The complaint does not contain an explicit count for willful infringement and does not allege pre-suit knowledge of the patents. However, the prayer for relief requests that the case be declared "exceptional under 35 U.S.C. § 285" and seeks "other damages awarded under 35 U.S.C. § 284," which provides the statutory basis for enhanced damages for willful infringement Compl. p. 39, Prayer B Compl. p. 39, Prayer D Any claim for willfulness would likely be predicated on Garmin's continued alleged infringement after the filing of the complaint.

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

• Definitional Scope: A central issue will be one of claim construction: can the term "terminal", which is described in the patent specification primarily in the context of desktop and laptop computers from the early 2000s, be construed to cover a modern smartphone running a software application?
• Architectural Equivalence: A key evidentiary question will be whether Garmin’s system architecture truly maps onto the claimed inventions. Specifically, does the portable device use the terminal's network connection as required by the '969 patent, its own network connection as required by the '819 patent, and have the capability to use either or both as required by the '374 and '786 patents, all while executing the specific program code steps recited in the claims?
• Functional Mapping: The case will likely turn on whether the accused software—the Garmin Connect app and the watch's operating system—performs the specific, partitioned functions of the claimed "first", "second", "third", and "fourth program code" elements, or if this represents a fundamental mismatch between the patent's described software structure and the technical operation of the accused products.