Iridescence LLC v. Belkin Intl Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Iridescence LLC (New Mexico)
  • Defendant: Belkin International, Inc. (Delaware)
  • Plaintiff's Counsel: Silverman, McDonald & Friedman
• Case Identification: 1:26-cv-00356, D. Del., 04/01/2026
• Venue Allegations: Plaintiff alleges venue is proper in the District of Delaware because Defendant, a Delaware corporation, has an established place of business in the district.
• Core Dispute: Plaintiff alleges that Defendant's unspecified products infringe a patent related to systems and methods for remotely controlling power to electrical devices over a network.
• Technical Context: The technology relates to the smart home and home automation market, specifically focusing on network-enabled power outlets that can be controlled and monitored locally or remotely via the Internet.
• Key Procedural History: The complaint does not mention any prior litigation, inter partes review proceedings, or licensing history related to the patent-in-suit.

Case Timeline

Date	Event
2011-10-04	U.S. Patent No. 8,666,560 Priority Date
2013-04-29	Application for U.S. Patent No. 8,666,560 Filed
2014-03-04	U.S. Patent No. 8,666,560 Issued
2026-04-01	Complaint Filed

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

U.S. Patent No. 8,666,560 - "Power control system and method"

• Patent Identification: U.S. Patent No. 8,666,560, "Power control system and method," issued March 4, 2014 (the "'560 Patent").

The Invention Explained

• Problem Addressed: The patent describes challenges with existing home automation systems, including the difficulty for consumers to access and control devices both locally and remotely, intrusive network setup requirements (e.g., replacing a home gateway), and the integration of disparate network technologies like Wi-Fi and ZIGBEE® '560 Patent, col. 3:5-18 '560 Patent, col. 4:5-18
• The Patented Solution: The invention proposes a "Smart Gateway Power Controller" (SGPC), a device that functions as a "sub-gateway" on a home network '560 Patent, abstract The SGPC connects to the user's primary home gateway (e.g., a Wi-Fi router) to access the Internet, but it also creates its own separate, secondary wireless network or "subnet" '560 Patent, col. 11:49-64 This architecture allows devices to connect directly to the SGPC's stable subnet for local control, while the SGPC manages the connection to the broader Internet for remote access, often using a proxy server to overcome challenges posed by dynamic IP addresses assigned by Internet Service Providers '560 Patent, col. 12:47-59 Figure 4 illustrates this dual-network topology, with the SGPC (0412) bridging the main "WiFi Home Network" (0402) and a separate "WiFi Automation Network" (0403) '560 Patent, Fig. 4
• Technical Importance: This sub-gateway architecture aims to provide a more stable and easily accessible control environment for home automation devices, insulating them from the dynamic and often complex configuration of a user's primary home network '560 Patent, col. 15:1-12

Key Claims at a Glance

• The complaint asserts "one or more claims" but does not identify any specific independent or dependent claims '560 Patent, col. 11 For illustrative purposes, an analysis of independent system claim 1 is provided below.
• Independent Claim 1: A system comprising a Smart Gateway Power Control (SGPC) system with a computing device configured to perform a series of steps for remote access, including:
  • Sending a periodic message from the SGPC to a proxy server containing its ID, password, router IP address, port, and subnet vector or path.
  • Storing that message in a translation database on the proxy server.
  • Receiving a request from a user's communication device for a translation of the SGPC ID.
  • Validating the SGPC ID and password provided by the user.
  • Returning the router IP address and other path information to the user's device if the credentials are valid.
• The complaint does not explicitly reserve the right to assert dependent claims but refers generally to "one or more claims" of the patent '560 Patent, col. 11

III. The Accused Instrumentality

Product Identification

The complaint does not identify any accused products by name '560 Patent, col. 11 It refers to them generically as "Exemplary Defendant Products" that are purportedly detailed in claim charts attached as Exhibit 2, which was not provided with the complaint documents for this analysis '560 Patent, col. 11 '560 Patent, col. 16

Functionality and Market Context

The complaint does not provide sufficient detail for analysis of the accused products' functionality or market context. It makes only the conclusory allegation that the products "practice the technology claimed by the '560 Patent" '560 Patent, col. 16

IV. Analysis of Infringement Allegations

The complaint references claim charts in an external "Exhibit 2" to support its infringement allegations, but this exhibit was not provided for analysis Compl. ¶16 Compl. ¶17 The narrative infringement theory is that the "Exemplary Defendant Products" satisfy all elements of the asserted claims Compl. ¶16 Without the specific product identification or the claim charts, a detailed infringement analysis is not possible.

No probative visual evidence provided in complaint.

• Identified Points of Contention: Based on the patent's claims and the general nature of the allegations, the infringement analysis will likely raise several questions:
  • Architectural Questions: A central question will be whether the accused products utilize a client-server architecture that meets the specific limitations of the claims. For example, does the accused system involve a device that sends "periodic message[s]" containing its network location ("router IP ADR, port, and subnet vector or path") to a "proxy server" for storage in a "translation database" as required by claim 1?
  • Technical Questions: What evidence does the complaint provide that Defendant's system performs the claimed validation and translation steps? The functionality of modern smart home cloud platforms would need to be compared against the specific sequence of requesting, validating, and returning network path information recited in the asserted claims.

V. Key Claim Terms for Construction

• The Term: "proxy server" (from claim 1)

  • Context and Importance: This term is central to the claimed method of enabling remote access. The definition of "proxy server" will be critical, as it dictates whether Defendant's cloud infrastructure, which facilitates communication between its smart devices and users, falls within the scope of the claims. Practitioners may focus on whether the term is limited to the specific "pull mode" architecture described in the patent or if it covers any intermediary server.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claims themselves do not define "proxy server," which may support giving the term its plain and ordinary meaning as an intermediary server.
    • Evidence for a Narrower Interpretation: The specification describes a specific "Proxy Server Mode (Pull Mode)" where a "server on the Internet... keeps track of the IP address and port number of a SGPC at home" by receiving periodic updates from the SGPC '560 Patent, col. 12:47-59 The detailed flowchart in Figure 18, depicting this specific interaction, could be used to argue for a narrower construction limited to a server that performs this precise function '560 Patent, Fig. 18

• The Term: "subnet vector or path" (from claim 1)

  • Context and Importance: This term relates to the patent's core concept of the SGPC creating a separate "subnet." Infringement will depend on whether the accused system transmits information that can be defined as a "subnet vector or path."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: A party might argue this term simply means any routing information necessary to reach a device on a local network from the public Internet.
    • Evidence for a Narrower Interpretation: The specification repeatedly describes the SGPC creating a distinct "subnet" that "separates" the home automation network from the existing home network, as illustrated in Figures 4 and 5 with distinct IP address ranges '560 Patent, col. 11:58-64 '560 Patent, Figs. 4-5 This could support an argument that the term requires the accused device to create a logically separate IP subnetwork, not merely act as a client on a single, flat home network.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Defendant distributes "product literature and website materials" that instruct end users on how to use the accused products in an infringing manner Compl. ¶14
• Willful Infringement: The complaint's allegations of knowledge appear to be based solely on the service of the complaint itself, which suggests a basis for post-suit willfulness rather than pre-suit willfulness Compl. ¶13 Compl. ¶15

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

• A core issue will be one of architectural equivalence: Does the server-based infrastructure supporting Belkin's smart home products function in the specific manner claimed by the '560 Patent? The case will likely depend on evidence showing whether Belkin's devices periodically report their network location to a central server for the purpose of enabling later remote connections initiated by a user, as recited in claim 1.
• A second key issue will be one of definitional scope: Will the term "subnet vector or path" be construed broadly to mean any routing data, or will it be limited to information describing a distinct, separate subnetwork created by the accused device itself? The outcome of this claim construction dispute could be dispositive for infringement.