Nordic Interactive Tech LLC v. Lenovo Group Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Nordic Interactive Technologies LLC (Texas)
  • Defendant: Lenovo Group Ltd. (China)
  • Plaintiff's Counsel: Ni, Wang & Massand, PLLC
• Case Identification: 2:26-cv-00477, E.D. Tex., 08/26/2026
• Venue Allegations: Venue is alleged to be proper because the defendant, Lenovo Group Ltd., is a foreign corporation, and under 28 U.S.C. § 1391(c)(3), suits against such entities are proper in any judicial district.
• Core Dispute: Plaintiff alleges that Defendant's smartphones, tablets, and other electronic devices, which utilize Bluetooth and Wi-Fi Direct technologies, infringe a patent related to efficient device and service discovery in ad hoc wireless networks.
• Technical Context: The technology concerns methods for battery-powered mobile devices to discover each other and the services they offer without requiring constant, power-intensive scanning or manual user intervention.
• Key Procedural History: The sole asserted patent, U.S. Patent No. 7,590,097, expired on June 8, 2024, more than two years before the complaint was filed; therefore, the litigation is limited to claims for past monetary damages. The complaint alleges that the Defendant had actual notice of the patent as of April 13, 2021. A Certificate of Correction was issued for the patent, changing the term "middleware layer" to "middleware software" in several dependent claims, which may influence the interpretation of related terms in the asserted independent claim.

Case Timeline

Date	Event
2002-10-31	'097 Patent Priority Date
2009-09-15	'097 Patent Issue Date
2021-04-13	Alleged date of Defendant's actual notice of the '097 Patent
2024-06-08	'097 Patent Expiration Date
2026-08-26	Complaint Filing Date

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

U.S. Patent No. 7,590,097 - Device Detection and Service Discovery System and Method for a Mobile Ad Hoc Communications Network

• Patent Identification: U.S. Patent No. 7,590,097 ("the '097 Patent"), "Device Detection and Service Discovery System and Method for a Mobile Ad Hoc Communications Network," issued September 15, 2009. Compl. ¶17

The Invention Explained

• Problem Addressed: The patent's background section describes prior art wireless discovery protocols as inefficient for mobile ad hoc networks, noting that they either consume excessive power by requiring constant inquiry messages or necessitate manual user intervention to initiate device detection. ʼ097 Patent, col. 2:41-51 These protocols also assume a static network environment, which is unsuitable for mobile settings where devices frequently enter and leave proximity. ʼ097 Patent, col. 2:51-56
• The Patented Solution: The invention proposes a multi-stage discovery method to conserve power and automate connections. A device first sends a general inquiry. If a responding device provides a preliminary "indication" that it may contain a specialized "middleware software" for managing services, the inquiring device then establishes a connection to "confirm" the middleware's presence. Only after confirmation does it execute the middleware to perform full service discovery. ʼ097 Patent, abstract ʼ097 Patent, Fig. 5 This prevents the device from having to establish a full connection with every discovered device, saving time and battery life.
• Technical Importance: This two-phase approach (preliminary indication followed by confirmation) was designed to make peer-to-peer discovery more efficient and automatic, a critical improvement for the usability of battery-powered mobile devices in ad hoc networks. ʼ097 Patent, col. 2:56-67

Key Claims at a Glance

• The complaint asserts claims 19-24. Compl. ¶21 Independent claim 19 is the focus of the allegations.
• The essential elements of independent claim 19 are:
  • conducting an inquiry to discover nearby devices;
  • determining if a discovered device provides an "indication" that it may include "middleware software" for application and service discovery;
  • if no indication is provided, disconnecting communication session establishment;
  • if an indication is provided, creating a wireless connection to the device;
  • confirming the device includes the middleware software by requesting information over the connection;
  • if confirmed, executing the middleware software to perform service discovery.
• The complaint also asserts dependent claims 20-24. Compl. ¶21

III. The Accused Instrumentality

Product Identification

• The accused products are broadly defined to include (1) Lenovo devices running Android OS 4.1 or later with Bluetooth 2.1 or later using Extended Inquiry Response (EIR); (2) Lenovo devices running Chrome OS with Bluetooth 2.1 or later using EIR; and (3) Lenovo devices running Android OS that support Wi-Fi Direct. Compl. ¶22 A non-exhaustive list of specific smartphone and tablet models is provided, such as the Lenovo Legion series and Motorola Edge series. Compl. ¶23

Functionality and Market Context

• The accused functionality centers on the device and service discovery mechanisms inherent in the Bluetooth and Wi-Fi Direct protocols as implemented on Android and Chrome OS. Compl. ¶¶28-45 The complaint alleges that for Bluetooth, the Extended Inquiry Response (EIR) packet serves as the claimed "indication" of available services. Compl. ¶30 For Wi-Fi Direct, the initial probe response containing a P2P Information Element (IE) allegedly performs the same function. Compl. ¶40 The complaint includes an image of a representative product, the Motorola Moto Z3, to illustrate an example device. Compl. p. 8
• The complaint alleges that Lenovo directs these products into the U.S. market through various distribution channels, including its websites and authorized retailers, and derives substantial revenue from their sale. Compl. ¶4 Compl. ¶11

IV. Analysis of Infringement Allegations

• Claim Chart Summary: The complaint's infringement theory maps the steps of claim 19 onto the standard operations of Bluetooth and Wi-Fi Direct discovery.

'097 Patent Infringement Allegations

Claim Element (from Independent Claim 19)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
conducting an inquiry to discover nearby devices	Accused devices use Bluetooth Inquiry/Scan procedures or Wi-Fi Direct's "discoverPeers()" function to find other devices.	¶29; ¶39	col. 11:22-23
determining, whether a discovered nearby device provides an indication that it may include a middleware software...	The device checks for an Extended Inquiry Response (EIR) packet (Bluetooth) or a P2P Information Element (Wi-Fi Direct) that contains information about supported services or capabilities. This is alleged to be the "indication".	¶30; ¶40	col. 11:24-28
when the discovered nearby device does not provide an indication...: disconnect communication session establishment...	If a device does not send an EIR response with service information, the inquiring device does not proceed to establish a full connection (i.e., it does not page the device), which is alleged to be a "disconnect".	¶33	col. 11:29-32
when the discovered nearby device provides an indication...: creating a wireless short-range communication connection...	If an indication is received, the device initiates a connection via Bluetooth paging or a Wi-Fi Direct connection request. The complaint provides a diagram from the Wi-Fi Direct specification illustrating this process. Compl. p. 17, fig. 5	¶35; ¶43	col. 11:38-40
confirming whether said nearby device includes the middleware software by requesting corresponding information...	After connection, the device performs a full Service Discovery Protocol (SDP) search (Bluetooth) or a Generic Advertisement Service (GAS) query (Wi-Fi Direct) to get detailed service attributes. This is alleged to be the "confirmation".	¶36; ¶44	col. 11:41-45
and when said nearby device includes the middleware software: executing the middleware software to perform application and service discovery...	After confirmation, the device executes the service, for example by opening a connection to the specific service provider to utilize it, as described in the Bluetooth specification. The complaint includes a diagram from the Wi-Fi Direct specification showing the service discovery query/response flow. Compl. p. 17, fig. 9	¶37; ¶45	col. 11:49-52

• Identified Points of Contention:
  • Scope Questions: A primary issue will be whether the term "middleware software", which the patent illustrates as a distinct software block separate from the operating system ʼ097 Patent, Fig. 2A, can be read to cover the integrated networking stacks and APIs of standard operating systems like Android and Chrome OS.
  • Technical Questions: The case may turn on whether a standard Bluetooth EIR packet or Wi-Fi P2P IE, which indicates the presence of services, meets the claim requirement of an "indication that it may include a middleware software". A court may need to decide if indicating a service is the same as indicating the specific software layer that provides it.
  • Technical Questions: The interpretation of the negative limitation "disconnect communication session establishment" will be critical. The complaint alleges that the act of not initiating a connection with a device that lacks an "indication" satisfies this element. A defendant may argue that this is not a "disconnection" of an ongoing "establishment" process.

V. Key Claim Terms for Construction

• The Term: "middleware software"

• Context and Importance: This term is foundational to the patent's claims. The infringement case rests on whether the standard networking frameworks within Android and Chrome OS qualify as the claimed "middleware software". Practitioners may focus on this term because the patent's figures depict it as a discrete architectural component. ʼ097 Patent, Fig. 2A, item 220

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification describes the middleware as "a software layer with an API that negotiates the communication between two applications to help an application find a counterpart." ʼ097 Patent, col. 6:40-44 This functional description could be argued to encompass any OS-level framework that enables inter-app communication.
  • Evidence for a Narrower Interpretation: The patent's Figure 2A explicitly shows "MIDDLEWARE SOFTWARE" (220) as a separate block from both "OPERATING SYSTEM SOFTWARE" (211) and "APPLICATION PROGRAMS" (212). This visual distinction may support an argument that the inventors contemplated a specific, add-on software layer rather than general OS functionality.

• The Term: "disconnect communication session establishment"

• Context and Importance: This negative limitation is a key step in the claimed method. The plaintiff's infringement theory equates not starting a connection with "disconnecting" an establishment process. The viability of this interpretation is central to the case.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent does not explicitly define this phrase. A plaintiff could argue that the "session establishment" process begins with the inquiry, and the decision not to proceed to the paging/connection step based on the inquiry response is a "disconnection" of that broader process.
  • Evidence for a Narrower Interpretation: The common technical meaning of "disconnect" implies terminating an existing or pending connection. A defendant may argue that simply choosing not to initiate a connection with a device is not an act of "disconnection," and that the claim requires a more affirmative severing of a process that has already advanced past the initial inquiry stage.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Defendant provides user manuals and other instructions that direct end-users to perform the claimed methods, such as connecting to Bluetooth devices. Compl. ¶53 Compl. ¶57 An excerpt from a Motorola Moto Z3 user guide is included as evidence of these instructions. Compl. p. 29
• Willful Infringement: The complaint alleges willful infringement based on Defendant's purported actual knowledge of the '097 Patent since at least April 13, 2021. Compl. ¶46 Compl. ¶48

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

• A core issue will be one of definitional scope: can the term "middleware software", which the patent depicts as a distinct architectural layer, be construed to cover the integrated, standard networking APIs and frameworks of modern mobile operating systems?
• A second central question will be one of functional interpretation: does the act of simply not proceeding to establish a connection with a device (based on its initial inquiry response) satisfy the claim requirement to "disconnect communication session establishment", or does this limitation require a more affirmative act of termination?
• An underlying evidentiary question will be one of technical mapping: do the standard signals in Bluetooth (EIR) and Wi-Fi Direct (P2P IE) function as the claimed "indication that it may include a middleware software", or do they merely indicate the presence of services, creating a potential mismatch with the patent's more specific language?