Portus Singapore Pte Ltd v. Savant Systems Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: PORTUS SINGAPORE PTE LTD (Singapore) & PORTUS PTY LTD (Australia)
  • Defendant: SAVANT SYSTEMS, INC. (Delaware)
  • Plaintiff’s Counsel: Law Office of David J. Hoffman
• Case Identification: 1:26-cv-04691, S.D.N.Y., 06/03/2026
• Venue Allegations: Venue is alleged to be proper based on the defendant maintaining regular and established places of business in the district, including an "experience center" in New York, NY, and having committed acts of infringement within the district.
• Core Dispute: Plaintiff alleges that Defendant’s Savant Home automation systems and associated cloud services infringe two patents related to architectures for remote monitoring and control of devices within a user's premises.
• Technical Context: The technology lies in the smart home and home automation sector, focusing on systems that enable users to securely access and manage in-home devices from a remote location via the internet.
• Key Procedural History: The complaint discloses that the Plaintiff is a non-practicing entity and has previously entered into settlement licenses with other entities, noting that none of these licenses involved an admission of infringement or an agreement to produce a patented article.

Case Timeline

Date	Event
1998-12-17	Priority Date for ’526 Patent and ’097 Patent
2014-12-16	U.S. Patent No. 8,914,526 Issued
2018-05-01	U.S. Patent No. 9,961,097 Issued
2018-06-29	Article published on Savant's cloud platform launch
2026-06-03	Complaint Filed

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

U.S. Patent No. 8,914,526 - "LOCAL AND REMOTE MONITORING USING A STANDARD WEB BROWSER," issued December 16, 2014

The Invention Explained

• Problem Addressed: The patent describes prior art remote monitoring systems as cumbersome, expensive, and lacking a standardized, platform-independent interface, often requiring special technical knowledge or costly long-distance calls to operate (ʼ526 Patent, col. 1:31-54; '526 Patent, col. 2:1-4).
• The Patented Solution: The invention proposes a system architecture comprising an external network (an "extranet") and an in-home "connection gateway" (ʼ526 Patent, abstract). A user employs a standard Internet browser to access the extranet, which in turn establishes an on-demand connection to the gateway at the user's premises, allowing the user to monitor and control devices within the home securely and without needing a direct, persistent connection from the premises to the internet (ʼ526 Patent, col. 2:33-49). The system is depicted in Figure 1, showing the relationship between the user's access device, the provider extranet, and the premises network (ʼ526 Patent, Fig. 1).
• Technical Importance: This architecture provided a method for remote home automation that leveraged the ubiquity of standard web browsers, aiming to reduce cost and complexity compared to proprietary systems of the era ('526 Patent, col. 1:50-54).

Key Claims at a Glance

• The complaint's infringement chart appears to assert at least independent claim 57 (Compl. ¶16; Compl. Ex. B, p. 2).
• The essential elements of independent claim 57 include:
  • A system comprising a "first network" external to the user premises, which includes a "first arrangement of processing circuitry" and a "hardware user access browser device".
  • A "plurality of second arrangements of processing circuitry", each located in a respective user premises and forming part of the user premises network.
  • The "first circuitry arrangement" is programmed to initiate network connections to the second circuitry arrangements.
  • The "user access browser" is usable via "Uniform Resource Locators (URL)" to access the first network.
  • The first circuitry arrangement, responsive to the URL input, determines which user premises network the user is authorized to access and initiates a "new communications session" for temporary interconnection.
  • During this session, the first network "obtains information" from the user premises network and "serves" it to the user access browser.
• The complaint does not explicitly reserve the right to assert dependent claims but makes general allegations of infringement of "one or more claims" (Compl. ¶15).

U.S. Patent No. 9,961,097 - "SYSTEM FOR REMOTE ACCESS OF A USER PREMISES," issued May 1, 2018

The Invention Explained

• Problem Addressed: As a continuation of the '526 patent, the '097 patent addresses the same problems of providing simple, secure, and platform-independent remote access to home automation systems (ʼ097 Patent, col. 1:47 - col. 2:42).
• The Patented Solution: The invention claims a system with a specific sequence for remote access. A user provides input corresponding to a URL via a "first hardware processing circuitry" (e.g., a user device) to access a "second hardware processing circuitry" (e.g., a cloud server). The cloud server then obtains information from an in-home "connection gateway" without a direct communicative link between the cloud server and the end device being controlled. The cloud server then serves this information back to the user's device ('097 Patent, abstract; '097 Patent, col. 2:43-67).
• Technical Importance: The invention focuses on the secure, brokered communication path where the cloud server acts as an intermediary, authenticating the user and managing the data flow, which prevents direct external exposure of the in-home network components ('097 Patent, col. 3:1-24).

Key Claims at a Glance

• The complaint asserts at least independent claim 1 (Compl. ¶22; Compl. Ex. D, p. 4).
• The essential elements of independent claim 1 include:
  • A "first hardware processing circuitry" running an "access browser module".
  • A "second hardware processing circuitry" located in a "first network".
  • A "connection gateway" located in a local network at the user premises.
  • The system is configured such that user-input of a "URL" on the first circuitry begins a sequence where the "second hardware processing circuitry" (cloud) obtains information from the "connection gateway" "without a direct communicative coupling" between the cloud circuitry and the networked component in the home.
  • The sequence involves the first circuitry transmitting "authentication data" to the second circuitry.
• The complaint does not explicitly reserve the right to assert dependent claims but makes general allegations of infringement of "one or more claims" (Compl. ¶21).

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is the Savant smart home ecosystem, which includes the Savant Home and Savant Power products (Compl. Ex. B, p. 2). Key components are the in-home "Savant Host," the "Savant App" for user devices, dedicated "Savant Touch" panels, and the backend "Savant cloud services" (Compl. Ex. B, p. 3; Compl. Ex. B, p. 8; Compl. Ex. B, p. 9).

Functionality and Market Context

• The Savant system provides integrated control over various home subsystems like lighting, climate, security, and entertainment (Compl. Ex. B, p. 2). The Savant Host serves as the central processor or "core intelligence" within the home, communicating with various devices (Compl. Ex. B, p. 8). Users interact with the system locally or remotely through the Savant App, which connects to Savant's cloud services to manage accounts, enable remote access, and synchronize device states (Compl. Ex. B, p. 3; Compl. Ex. D, p. 4). A network diagram provided in the complaint shows the interaction between the user's app, the local Wi-Fi network, the Savant Host, and other connected devices (Compl. Ex. B, p. 10). The complaint alleges these products are offered for sale and sold throughout New York and the United States (Compl. ¶7).

IV. Analysis of Infringement Allegations

'526 Patent Infringement Allegations

Claim Element (from Independent Claim 57)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a first network (a) located external to said user premises, (b) including a first arrangement of processing circuitry comprising at least one hardware processor programmed to control network access, and (c) including a hardware user access browser device that comprises a processor running an access browser	The Savant system includes an external "Savant cloud services network" with hardware processors for network access control, and user devices (smartphones/tablets) running the Savant App, which is alleged to function as the hardware user access browser device.	¶16	col. 5:25-33
a plurality of second arrangements of processing circuitry each comprising at least one hardware processor programmed to control network access, each of at least a subset of which is located in a respective one of the user premises and part of the respective user premises network...	The system includes the "Savant Host" deployed in users' homes. The Host contains a hardware processor and acts as the second arrangement of processing circuitry, controlling access to devices on the home's local area network.	¶16	col. 5:60-65
responsive to user-input of a URL...said first circuitry arrangement subsequently, by execution of its programming: determines which one of said user premises networks...authorization data indicates authority to at least one of monitor and control	When a user makes selections in the Savant App (alleged to be input of a URL), the Savant cloud services use the user's account login and device registration (authorization data) to determine which Savant Host and associated premises the user is authorized to control.	¶16	col. 11:33-51
initiates an establishment of a network connection to said one of said second circuitry arrangements to create a new communications session for a temporary interconnection between said first network and said determined one of said user premises networks to at least one of control and monitor...	Upon authorized access, Savant cloud services establish a temporary network session (e.g., HTTPS/TLS) with the specific, registered Savant Host to enable control and monitoring of devices on the user's premises network. A screenshot from a user guide shows different user account types with varying remote access permissions (Compl. Ex. B, p. 13).	¶16	col. 11:42-51

'097 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a first hardware processing circuitry running an access browser module; a second hardware processing circuitry located in a first network;	The system includes a user's smartphone/tablet (first hardware) running the Savant App (access browser module) and the Savant cloud services (second hardware) located in an external cloud services network.	¶22	col. 2:43-54
a connection gateway that is located in, and is part of a local network of, the user premises;	The Savant Host acts as the connection gateway and is located within the user's home on the local network.	¶22	col. 2:50-54
the system is configured such that user-input of a...URL...begins a sequence in which the second hardware processing circuitry responsively serves to the first hardware processing circuitry...information...which information the second hardware processing circuitry obtains from the connection gateway without a direct communicative coupling...	User selections in the app (alleged to be URL input) trigger a sequence where the Savant cloud server obtains information from the in-home Savant Host and serves it back to the app. The complaint alleges this occurs without a direct connection between the cloud server and the end device (e.g., a light bulb) being controlled.	¶22	col. 15:50 - col. 16:4
wherein the sequence includes the first hardware processing circuitry transmitting to the second hardware processing circuitry authentication data indicating authority to access the at least one networked component of the local network...	The sequence requires the user's device (first hardware) to transmit authentication data (e.g., remote access account credentials) to the Savant cloud server (second hardware) to gain authority to access the devices connected to the Savant Host. A screenshot shows how a user can review camera recordings, which the complaint presents as accessing stored information (Compl. Ex. D, p. 29).	¶22	col. 15:50-67

• Identified Points of Contention:
  • Scope Questions: A primary issue for both patents may be whether the "Savant App," a dedicated mobile application, qualifies as a "user access browser device" ('526 patent) or an "access browser module" ('097 patent). The patents frequently reference a "standard web browser." A related question is whether tapping icons in a proprietary app constitutes "user-input of a Uniform Resource Locator (URL)" as required by the claims, an issue the complaint addresses by describing the URL input as "implicit" (Compl. Ex. B, p. 15).
  • Technical Questions: The infringement theory relies on the Savant system following the specific communication sequence claimed in the patents. A point of contention may be whether the connection between the Savant cloud and the Savant Host is truly "temporary" and "on-demand" as described, or if a more persistent connection exists. For the '097 patent, a key factual question will be what evidence demonstrates the lack of "a direct communicative coupling" between the cloud server and the end device being controlled, as required by claim 1.

V. Key Claim Terms for Construction

'526 Patent

• The Term: "user access browser device"
• Context and Importance: The infringement case hinges on this term encompassing a smartphone or tablet running the dedicated "Savant App." The patent’s title refers to a "Standard Web Browser," creating a potential point of dispute over the intended scope. Practitioners may focus on this term because its construction could determine whether the core of the accused system falls inside or outside the claim.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification states that an "Internet access device" is not limited to a computer and may include a "mobile phone with display, a WebPhone, or a Personal Digital Assistant" ('526 Patent, col. 6:13-16), which could support interpreting "user access browser device" broadly to include modern smartphones.
  • Evidence for a Narrower Interpretation: The patent’s title, abstract, and background repeatedly use the phrase "standard web browser" ('526 Patent, title; '526 Patent, abstract; '526 Patent, col. 1:4-8). This emphasis could be used to argue for a narrower construction limited to conventional browser applications like Internet Explorer or Netscape Navigator, which were prevalent at the time of the invention's priority date.

'097 Patent

• The Term: "access browser module"
• Context and Importance: Similar to the '526 patent, the definition of this term is critical to determining if the Savant App infringes. The '097 patent is a continuation and carries forward similar concepts, making the interpretation of this functional module central to the dispute.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The '097 patent focuses more on the functional sequence of operations rather than a specific type of software. A party might argue that any software "module" that performs the function of initiating a URL-based request to an external server, regardless of its user interface, meets the claim limitation. The patent defines the system functionally ('097 Patent, abstract).
  • Evidence for a Narrower Interpretation: Claim 1 requires the sequence to begin with "user-input of a Uniform Resource Locator (URL)." A party could argue that this implies an interface where a user can specify a network location (like a traditional browser's address bar), not merely interact with fixed UI elements in a closed application. The complaint's characterization of this input as "implicit" (Compl. Ex. D, p. 16) suggests this is an anticipated area of dispute.

VI. Other Allegations

• Indirect Infringement: The complaint includes a general allegation that Defendant "induced acts of infringement" (Compl. ¶11). However, the body of the complaint and the infringement counts focus on a theory of direct infringement, alleging that Defendant "put the inventions claimed... into service (i.e., used them)" by providing the integrated Savant system (Compl. ¶15; Compl. ¶21). The complaint does not plead specific facts to support a claim of induced infringement, such as alleging that Defendant's user manuals specifically instruct users to perform an infringing method.
• Willful Infringement: The complaint seeks a declaration of willful infringement but does not allege specific facts demonstrating Defendant's pre-suit knowledge of the patents-in-suit. Instead, it states that willfulness may be declared if discovery reveals that the Defendant knew of the patents prior to the lawsuit and continued to infringe (Compl., Prayer for Relief ¶e).

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

• A core issue will be one of definitional scope: can the terms "user access browser device" and "access browser module", which are rooted in the patent family’s context of "standard web browsers," be construed to cover a modern, dedicated mobile application like the Savant App? The resolution of this question will likely depend on whether the court focuses on the literal meaning prevalent at the time of invention or the broader functionality described.
• A second central question will be one of operational equivalence: does the accused Savant system’s architecture—particularly the communication protocol between the app, cloud services, and in-home host—perform the exact multi-step, on-demand, and authentication-gated sequence of operations required by the asserted claims, or does its technical implementation differ in a way that avoids infringement?
• An underlying procedural question will be the strength of the willfulness allegation, which currently appears to be pleaded based on the possibility of discovering pre-suit knowledge rather than on specific facts known at the time of filing.