Malikie Innovations Ltd v. Abbott Laboratories Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Malikie Innovations Ltd. (Ireland) and Key Patent Innovations Ltd. (Ireland)
  • Defendant: Abbott Laboratories Inc. (Delaware) and Advanced Neuromodulation Systems, Inc. (Delaware)
  • Plaintiff's Counsel: Reichman Jorgensen Lehman & Feldberg, LLP
• Case Identification: 2:26-cv-00597, E.D. Tex., 07/21/2026
• Venue Allegations: Venue is based on Defendants allegedly maintaining a regular and established place of business in Plano, Texas, within the Eastern District of Texas, where acts of infringement are alleged to have occurred.
• Core Dispute: Plaintiff alleges that Defendant's neuromodulation systems, which include implantable medical devices and associated mobile software, infringe five patents originally developed by BlackBerry related to secure communications, policy management, and remote software updates.
• Technical Context: The technologies at issue were developed for the enterprise mobile computing environment and concern methods for securely connecting devices, managing security policies, and updating software without direct physical access.
• Key Procedural History: The complaint alleges that Plaintiff is the successor-in-interest to a substantial patent portfolio from BlackBerry. It also alleges that Defendants were on notice of their alleged infringement of the patents-in-suit prior to the lawsuit's filing, with specific notice periods for each patent family mentioned, which may form the basis for a willfulness claim.

Case Timeline

Date	Event
2004-04-30	Earliest Priority Date for '707 Patent and '696 Patent
2005-04-04	Earliest Priority Date for '323 Patent and '338 Patent
2005-10-16	St. Jude Medical acquires Defendant ANS
2010-02-16	'707 Patent Issued
2012-09-04	'338 Patent Issued
2013-05-21	'696 Patent Issued
2015-09-22	'323 Patent Issued
2017-01-04	Abbott Labs acquires St. Jude Medical
2018-08-03	Earliest Priority Date for '756 Patent
2021-09-14	'756 Patent Issued
2025-06-27	Alleged notice of '707, '338, and '696 Patents provided to Defendant
2025-10-02	Alleged notice of '323 Patent provided to Defendant
2026-07-21	Complaint Filed

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

U.S. Patent No. 9,143,323 - "Securing a Link Between Two Devices"

• Patent Identification: U.S. Patent No. 9,143,323, "Securing a Link Between Two Devices," issued September 22, 2015.

The Invention Explained

• Problem Addressed: The patent addresses the need to securely share cryptographic secrets between two communication devices, particularly mobile devices, without intervention from a third party like an IT administrator, and to verify the shared secret without exposing it '323 Patent, col. 1:17-26 Compl. ¶39
• The Patented Solution: The invention describes a multi-step process to generate a secure symmetric key (K3). Two devices first generate two initial symmetric keys (K1 and K2). Concurrently, they create a hash value (H) by hashing all the data packets exchanged during the generation of K1 and K2. Finally, both devices combine K1, K2, and H to independently generate the same final symmetric key, K3, which is then used to secure the communication link. This process is designed to protect against active network threats like replay attacks '323 Patent, col. 4:9-26 Compl. ¶40
• Technical Importance: This method provided a way for two devices to bootstrap a secure channel with enhanced protection against tampering, improving on simpler key-exchange protocols. Compl. ¶40

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶41
• The essential elements of independent claim 1 are:
  • Generating a first cryptographic key;
  • Generating a second cryptographic key;
  • Hashing packets communicated between the first and second device over the communication link to create a hash result; and
  • Hashing the first key, the second key, and the hash result to generate a third cryptographic key to secure the communication link.
• The complaint reserves the right to assert additional claims Compl. ¶41

U.S. Patent No. 7,664,707 - "System and Method for Handling Peripheral Connections to Mobile Devices"

• Patent Identification: U.S. Patent No. 7,664,707, "System and Method for Handling Peripheral Connections to Mobile Devices," issued February 16, 2010.

The Invention Explained

• Problem Addressed: In prior systems, authorizing a data connection between a mobile device and a peripheral (e.g., a desktop PC) was often handled by the peripheral. This created security risks (e.g., Trojan horse attacks) and was impractical for peripherals lacking a user interface to collect credentials '707 Patent, col. 1:20-34 Compl. ¶51
• The Patented Solution: The patent proposes shifting the responsibility for connection approval to the mobile device. When a peripheral attempts to connect, the mobile device itself prompts the user for approval (e.g., by asking for a password or using the device's unlock input). This allows secure connections even with simple peripherals that have no input/output capabilities of their own '707 Patent, abstract '707 Patent, col. 6:10-24 Compl. ¶51
• Technical Importance: This approach enhanced data security by centralizing authentication on the trusted mobile device, rather than the potentially untrusted peripheral, and extended secure connectivity to a broader class of accessory devices. Compl. ¶51

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶52
• The essential elements of independent claim 1 are:
  • Receiving a request from a peripheral device that an approval process for a data connection be handled by the mobile device;
  • Providing an input mechanism through the mobile device for a user to provide input;
  • Determining whether to approve the data connection based on the user's input;
  • The method applies where the peripheral itself is not capable of providing an input prompt for the approval.
• The complaint reserves the right to assert additional claims Compl. ¶52

Multi-Patent Capsule: U.S. Patent No. 8,261,338

• Patent Identification: U.S. Patent No. 8,261,338, "Policy Proxy," issued September 4, 2012.
• Technology Synopsis: The patent describes a method for managing IT policies on devices that cannot directly communicate with a central policy server. A networked device, like a mobile phone, acts as a "policy proxy" by fetching policies from the server and relaying them to nearby peripherals (e.g., via Bluetooth or Wi-Fi). This automates policy distribution, replacing error-prone manual configuration Compl. ¶¶61-62
• Asserted Claims: At least independent claim 1 Compl. ¶63
• Accused Features: The Abbott Infinity and Liberta DBS Systems, along with their related Patient Controller apps and the NeuroSphere Digital Health App, are accused of infringing Compl. ¶63

Multi-Patent Capsule: U.S. Patent No. 8,447,696

• Patent Identification: U.S. Patent No. 8,447,696, "System and Method for Handling Peripheral Connections to Mobile Devices," issued May 21, 2013.
• Technology Synopsis: Similar to the '707 Patent, this invention focuses on improving security by having a mobile device application manage and authorize connection requests from a peripheral. By shifting authorization control to the mobile device (e.g., via user prompt or device unlock), it enables secure connections for peripherals that lack their own user interface, reducing the risk of unauthorized access Compl. ¶¶72-73
• Asserted Claims: At least independent claim 1 Compl. ¶74
• Accused Features: The Abbott Infinity and Liberta DBS Systems, along with their related Patient Controller apps and the NeuroSphere Digital Health App, are accused of infringing Compl. ¶74

Multi-Patent Capsule: U.S. Patent No. 11,119,756

• Patent Identification: U.S. Patent No. 11,119,756, "System and Method for Controlling Updates to Internet-of-things Devices," issued September 14, 2021.
• Technology Synopsis: The patent discloses a system for remotely managing software updates for IoT devices using a mediating "switchboard" server. A user on a first device (e.g., a smartphone) can initiate an update on a second, target IoT device. The switchboard server coordinates the process, including checking the target device's readiness and relaying commands, which enables updates for devices that are not directly addressable or are behind firewalls Compl. ¶¶83-84
• Asserted Claims: At least independent claim 14 Compl. ¶86
• Accused Features: The Abbott Infinity and Liberta DBS Systems, along with their related Patient Controller apps and the NeuroSphere Digital Health App, are accused of infringing Compl. ¶86

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are Abbott's neurostimulation systems, including the Abbott Infinity Deep Brain Stimulation (DBS) System and Abbott Liberta RC DBS System, and their associated software, including the NeuroSphere Digital Health app, NeuroSphere Virtual Clinic app, Patient Controller NR app, and Patient Controller RC app (collectively, the "Accused Product") Compl. ¶¶9-11

Functionality and Market Context

The Accused Product is a medical device system used to treat chronic pain and movement disorders, such as Parkinson's disease Compl. ¶7 The system comprises implantable devices that are designed to be "compatible with mobile technology" Compl. ¶¶7-8 The accused software applications run on patient and clinician mobile devices (e.g., smartphones) and communicate with the implantable hardware, allegedly using Bluetooth, to facilitate remote care, manage patient conditions, and ensure data security Compl. ¶12 Compl. ¶43 The complaint alleges these products are commercially significant and generate substantial revenue Compl. ¶13 No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'323 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A method for securing a communication link between a first device and a second device, the method comprising:	The Accused Product, which includes an implantable device and a mobile app, allegedly secures communications between these components.	¶41; ¶43	col. 3:1-3
generating a first cryptographic key;	The Accused Product allegedly utilizes SSL/TLS data transfer encryption, which involves the generation of cryptographic keys to secure communications.	¶41	col. 4:4-8
generating a second cryptographic key;	The Accused Product allegedly utilizes SSL/TLS data transfer encryption, which involves the generation of multiple cryptographic keys as part of its handshake protocol.	¶41	col. 4:5-8
hashing packets communicated between said first device and said second device over said communication link to create a hash result; and	The complaint alleges the Accused Product uses encrypted communication protocols (SSL/TLS, encrypted Bluetooth) to ensure data security, which implies an authentication mechanism for the data exchanged during the connection setup.	¶41; ¶43	col. 4:9-14
hashing said first cryptographic key, said second cryptographic key and said hash result to generate a third cryptographic key to be used to secure said communication link.	The complaint alleges that the Accused Product's use of encryption protocols (SSL/TLS) results in a secure communication link, implicitly mapping this outcome to the claimed method of generating a final key from prior keys and a hash result.	¶41; ¶43	col. 4:20-26

Identified Points of Contention

• Technical Question: A central issue will be whether the standard operation of the SSL/TLS protocol, as allegedly implemented in the Accused Product, performs the specific sequence of generating two distinct keys (K1, K2), hashing the entire communication packet stream from that generation process to create a hash result (H), and then hashing K1, K2, and H together to create a final session key (K3). The complaint's allegation appears to equate the general use of an encryption standard with the highly specific method recited in the claim, raising the question of a potential mismatch in technical operation.
• Scope Question: The court may need to determine if the "first device" and "second device" of the claim, conceived in a general mobile computing context, properly read on the specialized components of the accused medical device system (e.g., an implantable neurostimulator and a smartphone controller).

'707 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a request from the peripheral device that an approval process for the data connection be handled by the mobile device;	The implantable DBS system (the "peripheral") allegedly initiates a connection with the Patient Controller app running on a smartphone or other controller (the "mobile device"), thereby requiring the mobile device to handle the authentication and approval process for the connection.	¶51; ¶52	col. 5:34-39
providing through the mobile device an input mechanism to provide input for use in determining whether to approve the data connection between the mobile device and the peripheral; and	The Patient Controller app on the mobile device serves as the user interface for managing the DBS system. The complaint alleges that securing the connection involves this app, which implies it provides the mechanism (e.g., password entry or device unlock) for user approval.	¶51; ¶52	col. 6:10-14
determining whether to approve the data connection between the mobile device and the peripheral based upon the input,	The mobile device, running the Patient Controller app, determines whether to allow the data connection to the implantable DBS system based on the user's input, thereby providing secure data management.	¶52; ¶54	col. 6:14-20
wherein the peripheral is not capable of providing an input prompt for use in determining whether to approve the data connection between the mobile device and the peripheral.	The implantable DBS device is a medical implant and, as such, lacks its own screen, keyboard, or other user interface to independently prompt a user for connection approval. All user interaction is mediated through the mobile device app.	¶51; ¶54	col. 5:56-61

Identified Points of Contention

• Scope Question: A primary point of contention may be whether an implantable, regulated medical device like the Abbott DBS system constitutes a "peripheral" as that term is used in the patent. The defense may argue the term, originating from a 2004 mobile computing context, is limited to consumer electronics accessories and does not cover components of an integrated medical therapy system.
• Technical Question: What evidence does the complaint provide that the accused system performs an application-level approval process as claimed, rather than relying solely on a standard, OS-level protocol like Bluetooth pairing? The analysis will likely focus on whether the Patient Controller app itself executes the claimed steps of receiving a specific request from the implant and handling the approval determination.

V. Key Claim Terms for Construction

'323 Patent, Claim 1

The Term: "hashing packets communicated... to create a hash result"

• Context and Importance: This step is crucial to the patent's described method for preventing replay attacks. The infringement analysis will turn on whether the accused SSL/TLS implementation performs this specific function. Practitioners may focus on this term because the strength of the infringement allegation depends on mapping a general-purpose security protocol (SSL/TLS) to this very specific claimed action of hashing the entire key-generation communication stream.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification states the hash function "may be applied to the packets as the packets are sent and received" '323 Patent, col. 4:11-13, which could be argued to encompass any hashing that occurs during the connection handshake.
  • Evidence for a Narrower Interpretation: The claim language requires hashing "packets communicated between said first device and said second device over said communication link" during the key generation phase. A defendant could argue this requires a hash of the entire, specific set of packets used to generate K1 and K2, and that standard protocols may use different methods, such as hashing only specific parts of messages or using digital signatures for authentication, which may not meet this limitation.

'707 Patent, Claim 1

The Term: "peripheral"

• Context and Importance: The applicability of this patent to the Accused Product hinges on the definition of "peripheral." Practitioners may focus on this term because its construction will determine whether a regulated, implantable medical device falls within the scope of a patent conceived in the consumer mobile-accessory ecosystem.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent's description is functional, referring to devices that "connect to the [mobile] devices" '707 Patent, col. 1:21-22 The abstract is also general. A plaintiff may argue that any device connecting to the mobile device for data transfer fits this functional definition.
  • Evidence for a Narrower Interpretation: The patent's own examples from its 2004 priority date include a "desktop computer," "smart card reader," "memory card," and "hardware crypto token" '707 Patent, col. 5:31-41 A defendant may argue that the term should be construed in light of these examples and limited to IT or consumer electronic accessories, not life-sustaining, FDA-regulated implantable medical systems which are not general-purpose peripherals.

VI. Other Allegations

Indirect Infringement

The complaint alleges both induced and contributory infringement for all asserted patents. Inducement allegations are based on Defendants allegedly encouraging and instructing customers (e.g., physicians and patients) through advertising and user manuals to use the Accused Product in an infringing manner Compl. ¶43 Compl. ¶54 Compl. ¶65 Compl. ¶76 Compl. ¶88 Contributory infringement is alleged on the basis that Defendants supply components that are a material part of the claimed inventions and are not staple articles of commerce suitable for substantial non-infringing use Compl. ¶44 Compl. ¶55 Compl. ¶66 Compl. ¶77 Compl. ¶89

Willful Infringement

The complaint alleges willful infringement for all asserted patents, based on alleged pre-suit knowledge. It specifically pleads that Defendants have been on notice since at least June 27, 2025, or October 2, 2025, and that Plaintiff provided "multiple notice letters, claim charts, and patent-specific analysis" Compl. ¶45 Compl. ¶56 Compl. ¶67 Compl. ¶78 Compl. ¶85 The complaint further alleges that Defendants failed to take a license or cease infringement despite these repeated efforts Compl. ¶46 Compl. ¶57

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

• A core issue will be one of definitional scope: can terms rooted in the 2000s-era mobile computing context, such as "peripheral" ('707 Patent) and "Internet-of-Things device" ('756 Patent), be construed to cover the highly regulated, specialized components of a modern implantable medical device system? The outcome of this question may determine the applicability of a significant portion of the asserted patent portfolio.
• A key evidentiary question will be one of technical mapping: does the alleged use of general-purpose security protocols like SSL/TLS in the accused systems actually perform the specific, multi-step cryptographic methods recited in claims, such as the key-and-hash generation sequence of the '323 patent? The case may turn on whether Plaintiff can prove an exact operational correspondence or if its allegations are deemed conclusory.
• A third central question will relate to willfulness: given the complaint's specific allegations of pre-suit notice, including the provision of claim charts, the focus will likely be on the nature of Defendants' conduct after being notified. The dispute will examine whether Defendants' actions were objectively reckless in the face of a known risk of infringement.