Cellspin Soft Inc v. Garmin Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Cellspin Soft, Inc. (California)
  • Defendant: Garmin Corporation (Taiwan) and Garmin Ltd. (Switzerland)
  • Plaintiff's Counsel: Garteiser Honea, PLLC
• Case Identification: 2:25-cv-00950, E.D. Tex., 04/02/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant conducts substantial business in the district, including selling the accused products through authorized retail and distribution channels. The complaint also notes that related litigation involving the same patents against other parties has occurred in the district.
• Core Dispute: Plaintiff alleges that Defendant's smartwatches, avionics, marine, and automotive products, when used with associated mobile applications, infringe three patents related to methods and systems for automatically transferring data from a peripheral capture device to a mobile device and subsequently to a web service.
• Technical Context: The technology addresses the automated, wireless transfer of user-generated data (e.g., fitness, navigation, health metrics) from a sensor device to a smartphone and then to cloud-based services, a foundational process for the modern Internet of Things (IoT) and wearable device market.
• Key Procedural History: The complaint alleges that Defendant had pre-suit notice of the patents-in-suit via a licensing letter sent in June 2017, a fact that forms the basis for the willfulness allegations. The complaint also references prior litigation in the same district involving the same patents against Fossil Group, Inc.

Case Timeline

Date	Event
2007-12-28	Priority Date for '794, '752, and '847 Patents
2014-05-27	U.S. Patent No. 8,738,794 Issued
2014-11-18	U.S. Patent No. 8,892,752 Issued
2017-06-XX	Alleged pre-suit notice of patents sent to Defendant
2017-08-29	U.S. Patent No. 9,749,847 Issued
2022-01-XX	Garmin Venu 2 Plus, Fenix 7 Series, Epix (Gen 2) Released
2022-02-XX	Garmin Instinct 2 Series, inReach Mini 2 Released
2026-04-02	Complaint Filed

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

U.S. Patent No. 8,738,794 - "Automatic Multimedia Upload for Publishing Data and Multimedia Content"

• Patent Identification: U.S. Patent No. 8,738,794, titled "Automatic Multimedia Upload for Publishing Data and Multimedia Content," issued on May 27, 2014.

The Invention Explained

• Problem Addressed: The patent background describes the process of transferring media from a capture device (e.g., a digital camera) to a website as cumbersome and time-consuming, requiring manual steps like connecting the device to a PC with a cable and then uploading the content online ʼ794 Patent, col. 1:36-49
• The Patented Solution: The invention discloses a method to automate this process. A "digital data capture device" is paired with a "Bluetooth enabled mobile device" (e.g., a smartphone) running a client application ʼ794 Patent, abstract As illustrated in Figure 1, the system architecture involves the client application detecting when new data is captured on the peripheral device, automatically initiating a transfer of the data via Bluetooth, and then publishing the data to one or more web services with minimal user intervention ʼ794 Patent, col. 2:4-14 '794 Patent, col. 4:22-39
• Technical Importance: This automated two-step transfer architecture (device-to-phone, phone-to-cloud) simplified content sharing and provided a framework for connected devices before the widespread adoption of direct-to-cloud IoT devices. Compl. ¶23

Key Claims at a Glance

• The complaint asserts "certain claims" of the '794 Patent Compl. ¶77 Independent claim 1, a method claim, is representative.
• Essential elements of independent claim 1 include:
  • Providing a software module on a Bluetooth enabled data capture device and a separate software module on a Bluetooth enabled mobile device.
  • Establishing a paired connection between the devices.
  • Acquiring new data on the capture device after pairing is established.
  • Detecting and signaling the new data for transfer, wherein the capture device's software module sends a data signal to the mobile device.
  • Automatically transferring the new data from the capture device to the mobile device.
  • Applying a user identifier to the new data on the mobile device.
  • Transferring the new data and user identifier from the mobile device to one or more web services for publication.
• The complaint's allegation of infringement of "certain claims" suggests the potential assertion of dependent claims.

U.S. Patent No. 8,892,752 - "Automatic Multimedia Upload for Publishing Data and Multimedia Content"

• Patent Identification: U.S. Patent No. 8,892,752, titled "Automatic Multimedia Upload for Publishing Data and Multimedia Content," issued on November 18, 2014.

The Invention Explained

• Problem Addressed: As a continuation in the same patent family, the '752 Patent addresses the same general problem of inconvenient, manual data uploading from peripheral devices ʼ752 Patent, col. 1:39-54
• The Patented Solution: The '752 Patent refines the solution by detailing a more secure and specific communication protocol. It describes establishing a secure paired Bluetooth connection using a "cryptographic encryption key" '752 Patent, col. 12:53-56 The data transfer is triggered by an "event notification" sent from the capture device to the mobile device '752 Patent, col. 12:5-14 The capture device then encrypts the new data and transfers it to the mobile device, which decrypts it and sends it to a remote internet server using a specified method like HTTP '752 Patent, col. 12:15-40
• Technical Importance: The invention's focus on cryptographic security and a specific event-based signaling mechanism addresses key requirements for reliably and securely handling potentially sensitive user data from wearable and other personal devices Compl. ¶23

Key Claims at a Glance

• The complaint asserts "certain claims" of the '752 Patent Compl. ¶90 Independent claim 1 is a representative method claim.
• Essential elements of independent claim 1 include:
  • At the capture device: establishing a secure paired Bluetooth connection with a mobile device using a cryptographic key.
  • Detecting and signaling new data for transfer by sending an "event notification" to the mobile device.
  • Encrypting the new data using the cryptographic key.
  • Transferring the encrypted data to the mobile device.
  • At the mobile device: receiving the encrypted data, decrypting it, attaching a user identifier and other information, and sending the data to a remote internet server.
• The complaint's general assertion implies the right to pursue dependent claims.

U.S. Patent No. 9,749,847 - "Automatic Multimedia Upload for Publishing Data and Multimedia Content"

• Patent Identification: U.S. Patent No. 9,749,847, titled "Automatic Multimedia Upload for Publishing Data and Multimedia Content," issued on August 29, 2017.
• Technology Synopsis: This patent, also in the same family, claims a system comprising a Bluetooth-enabled data capture device and a Bluetooth-enabled cellular phone '847 Patent, abstract The system is configured for the capture device to send an "event notification" and the acquired data to the phone, which then uses HTTP to transfer the data and associated user information over a cellular network to a website '847 Patent, Claim 1 The claim focuses on the complete, end-to-end architecture combining these specific components and communication protocols.
• Asserted Claims: The complaint asserts "certain claims," including system claim 1 '847 Patent, Claim 1 Compl. ¶103
• Accused Features: The complaint alleges that the combination of Garmin's various Bluetooth-enabled products (smartwatches, avionics, etc.) with a smartphone running a corresponding Garmin app (e.g., Garmin Connect, Garmin Pilot) creates the infringing system, which automatically transfers data to Garmin's servers Compl. ¶¶104-107

III. The Accused Instrumentality

Product Identification

The complaint identifies a wide range of Garmin products, grouped into four categories: (1) Garmin Smartwatch Products (e.g., Venu, Fenix, Forerunner series); (2) Garmin Avionics Products (e.g., GTN 750Xi, G1000 NXi); (3) Garmin Marine Products (e.g., inReach Mini 2); and (4) Garmin Automotive Products (e.g., DriveSmart series) (Compl. ¶¶26; Compl. ¶57; Compl. ¶65; Compl. ¶68). These hardware devices are accused in combination with their corresponding mobile software applications (e.g., Garmin Connect, Garmin Pilot, Garmin Explore, Garmin Drive) Compl. ¶9

Functionality and Market Context

• The accused hardware devices are Bluetooth-enabled peripherals designed to capture specific data types, such as fitness and health metrics (heart rate, SpO2), navigation data (GPS coordinates, waypoints), or aviation data (flight plans) Compl. ¶23 Compl. ¶57
• The complaint alleges that these devices are designed to be paired with a smartphone and "automatically transfer data via a secure Bluetooth connection to a mobile device" running a Garmin application Compl. ¶9 Compl. ¶66
• The Garmin mobile application then allegedly uploads this data to Garmin's web services (e.g., Garmin's servers, flyGarmin.com) using HTTP/HTTPS Compl. ¶26 Compl. ¶57 The complaint asserts this entire process occurs "with minimal user intervention post-setup" Compl. ¶56 A screenshot from Garmin's website displays several of the accused smartwatch models, including the Fenix, Venu, Forerunner, and Instinct series Compl. p. 1

IV. Analysis of Infringement Allegations

'794 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
providing a software module on the Bluetooth enabled data capture device;	Garmin's firmware on its smartwatches, avionics, marine, and automotive products enables data capture and Bluetooth transfer functionality.	¶¶27-74	col. 6:16-19
providing a software module on the Bluetooth enabled mobile device;	The Garmin Connect, Explore, Golf, Pilot, and Drive mobile applications for iOS and Android.	¶56	col. 5:66-6:15
establishing a paired connection between the Bluetooth enabled data capture device and the Bluetooth enabled mobile device;	The accused products are designed to "pair[] via Bluetooth" with a smartphone running a corresponding Garmin app.	¶28; ¶63	col. 4:6-21
acquiring new data in the Bluetooth enabled data capture device, wherein new data is data acquired after the paired connection is established;	The accused devices acquire data such as fitness metrics, navigation waypoints, or flight-related data after being paired with a smartphone.	¶78	col. 4:22-24
detecting and signaling the new data for transfer... by the software module on the Bluetooth enabled data capture device automatically...	The system is alleged to utilize "event notifications (e.g., new data availability)" to trigger "automatic data capture."	¶56	col. 4:54-6:2
transferring the new data from the Bluetooth enabled data capture device to the Bluetooth enabled mobile device automatically...	The accused system is alleged to "automatically transfer" captured data via Bluetooth from the Garmin device to the paired mobile device.	¶78	col. 4:35-39
applying, using the software module on the Bluetooth enabled mobile device, a user identifier to the new data...	The Garmin apps are alleged to upload data to a web service "with a user identifier" and include "account authentication details."	¶78; ¶63	col. 12:21-25
transferring the new data received by the Bluetooth enabled mobile device... to the one or more web services...	The Garmin apps upload the received data to Garmin's servers (e.g., flyGarmin.com) using HTTP/HTTPS.	¶26; ¶57; ¶80	col. 2:41-49

• Identified Points of Contention:
  • Scope Questions: The patent's examples for a "digital data capture device" focus on cameras '794 Patent, col. 2:15-18 A point of contention may be whether this term's scope, as understood by a person of ordinary skill in the art at the time, extends to the diverse range of accused products, including smartwatches and integrated avionics systems.
  • Technical Questions: Claim 1 requires that the "software module on the Bluetooth enabled data capture device" sends a "data signal" to the mobile device. The complaint alleges "event notifications" Compl. ¶56 but does not specify which device initiates the signal. The analysis may turn on whether the accused system uses a "push" model initiated by the Garmin peripheral as claimed, or a "pull" model where the mobile app polls the peripheral for new data.

'752 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
establishing a secure paired Bluetooth connection... wherein the secure paired Bluetooth connection uses a cryptographic encryption key;	The accused system is alleged to use a "secure paired Bluetooth connection" and features "cryptographic authentication."	¶23	col. 11:51-56
detecting and signaling the new data for transfer... sending an event notification to the Bluetooth enabled mobile device...;	The system allegedly uses "event notifications (e.g., new data availability)" to facilitate automatic data transfer.	¶56	col. 12:5-14
encrypting, using the cryptographic encryption key, the new data acquired in the Bluetooth enabled data capture device;	The complaint alleges a "secure Bluetooth connection," which inherently involves encryption, but does not specify that the capture device itself performs application-level encryption on the data payload prior to transfer.	¶9; ¶23	col. 12:15-17
transferring the encrypted data from the Bluetooth enabled data capture device to the Bluetooth enabled mobile device...;	The system is alleged to "automatically transfer data via a secure Bluetooth connection."	¶9; ¶67	col. 12:18-22
...the Bluetooth enabled mobile device is configured to... obtain the new data from the encrypted data using the cryptographic encryption key...;	This is alleged to occur when the Garmin mobile app receives data over the secure connection and processes it for upload. The complaint does not detail the decryption step.	¶56	col. 12:22-26
...attach a user identifier, an action setting and a destination web address of a remote internet server...;	The Garmin apps are alleged to upload data with a "user identifier" to Garmin's servers (the destination) using HTTP/HTTPS (the action setting).	¶91; ¶26; ¶57	col. 12:26-40

• Identified Points of Contention:
  • Technical Questions: Claim 1 requires the capture device to perform the step of "encrypting... the new data". It is an open question whether the accused Garmin devices perform application-level encryption of the data payload itself, or if the system relies solely on the standard, link-layer encryption inherent in a secure Bluetooth connection. The distinction between data-level and link-level encryption may be a central technical dispute.
  • Scope Questions: The claim requires the mobile device to "attach" an "action setting" (defined as an RPC or HTTP method) to the data. The infringement analysis may focus on whether the Garmin app "attaches" the HTTP method to the data object as the claim might be construed to require, or whether HTTP is simply the transport protocol used by the app to communicate with the server, a potentially different implementation.

V. Key Claim Terms for Construction

'794 Patent

• The Term: "software module on the Bluetooth enabled data capture device"
• Context and Importance: This term is critical because Claim 1 assigns it the key function of "sending a data signal" to initiate the data transfer. The defendant may argue that its device firmware is an integrated operating system that does not contain a discrete "module" performing this specific function, raising questions about whether its architecture meets this limitation.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The term "software module" is generic. The specification does not provide a narrow definition, which may support an interpretation that covers any software component, including general firmware, that performs the claimed function.
  • Evidence for a Narrower Interpretation: Figure 2 of the patent depicts the "BT communication device (201a)" on the capture device as containing distinct sub-modules, including a "BT association protocol module (201b)" and a "data transfer protocol module (201c)." This could support an argument that the term requires a specific, partitioned software structure rather than a monolithic firmware implementation.

'752 Patent

• The Term: "event notification"
• Context and Importance: The '752 Patent is distinguished from its parent by its focus on this specific signaling mechanism. The technical definition of "event notification" will be central to the infringement analysis. Practitioners may focus on this term because its construction will determine whether a standard Bluetooth service alert is sufficient to infringe, or if a more complex, application-specific handshake is required.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself is simple: "sending an event notification." This could be argued to cover any signal that notifies the mobile device of a new data event, a common function in many standard Bluetooth profiles.
  • Evidence for a Narrower Interpretation: Claim 1 describes the signaling process as including a step where the mobile device sends a message "to enable event notifications" on the capture device '752 Patent, col. 12:1-5 This suggests the "event notification" is not a unilateral alert but part of a specific, two-way registration and notification protocol, potentially narrowing its scope.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement.
  • Inducement is alleged based on Defendant providing the accused products and corresponding apps, along with "detailed instructions, including user manuals, and start guides," and marketing materials that allegedly encourage users to perform the infringing method of pairing the devices and automatically syncing data Compl. ¶82 Compl. ¶95 Compl. ¶108
  • Contributory infringement is alleged on the basis that the Garmin mobile apps are material components of the claimed methods and systems and are not suitable for substantial non-infringing use, as their primary purpose is to facilitate the patented data transfer from Garmin's hardware Compl. ¶84 Compl. ¶97 Compl. ¶110
• Willful Infringement: The complaint alleges willful infringement based on Defendant's purported actual notice of the patents-in-suit "since at least June 2017, via a licensing letter sent by Cellspin" Compl. ¶83 Compl. ¶96 Compl. ¶109 Plaintiff argues that Defendant's continued infringement after this date was deliberate and warrants enhanced damages.

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

1. A core issue will be one of definitional scope: Can the term "digital data capture device," rooted in the patent's examples of digital cameras, be construed broadly enough to encompass the technologically diverse range of accused instrumentalities, from consumer smartwatches to specialized aviation and marine navigation systems?

2. A key evidentiary question will be one of architectural congruence: Does the Garmin ecosystem's method of signaling and transferring data precisely match the sequence of steps recited in the claims? Specifically, does the evidence show that the Garmin peripheral device initiates a "data signal" ('794 patent) and performs application-level data encryption ('752 patent), or does the system operate on a fundamentally different architecture, such as a mobile-app-initiated "pull" mechanism or reliance on standard Bluetooth link-layer security?

3. The case may also present a question of divided infringement: As the claimed methods involve actions taken by the capture device, the mobile device, and remote web servers, the court will likely need to analyze whether Plaintiff can prove that Defendant "directs or controls" the performance of all steps by its customers, thereby attributing all actions to a single entity for the purpose of establishing direct infringement.