Portus Singapore Pte Ltd & Portus Pty Ltd v. Amazon.com Services LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Portus Singapore Pte Ltd (Singapore) & Portus Pty Ltd (Australia)
  • Defendant: Amazon.com Services LLC (Washington)
  • Plaintiff’s Counsel: Ramey LLP
• Case Identification: 2:26-cv-00127, E.D. Tex., 02/16/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains a regular and established place of business in the district and has allegedly committed acts of infringement there.
• Core Dispute: Plaintiff alleges that Defendant’s unspecified systems and devices infringe two patents related to architectures for remotely monitoring and controlling home networks using a standard web browser and an intermediary external network.
• Technical Context: The patents address foundational concepts for the Internet of Things (IoT) and smart home technology, describing a system where a remote user connects to a cloud-like intermediary network, which in turn establishes an on-demand connection to a gateway device within a user's premises.
• Key Procedural History: The complaint states that Plaintiff is a non-practicing entity and has previously entered into settlement licenses with other parties. It proactively argues that these licenses did not create a patent marking requirement under 35 U.S.C. § 287(a), potentially to preempt a common defense related to damages.

Case Timeline

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

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

The Invention Explained

• Problem Addressed: The patent describes the difficulty in the late 1990s of remotely controlling and monitoring home automation and security systems ʼ526 Patent, col. 1:31-34 Existing methods were described as cumbersome, requiring platform-specific software, special technical knowledge, or expensive direct connections to the home, such as a long-distance telephone call ʼ526 Patent, col. 1:47-67 ʼ526 Patent, col. 2:1-3
• The Patented Solution: The invention proposes a three-part architecture to solve this problem: (1) a user with a standard Internet browser, (2) an "extranet" network external to the home that hosts a communications server, and (3) a "connection gateway" located inside the user's home ʼ526 Patent, abstract When a user accesses a specific web address (URL) on the extranet, the communications server is prompted to establish an "on-demand" connection to the specific user's home gateway, creating a temporary link that allows the user to monitor and control their home devices through a standard web interface ʼ526 Patent, col. 2:31-49 ʼ526 Patent, Fig. 1 The extranet acts as a secure, centralized intermediary, removing the need for the user to connect directly to their home.
• Technical Importance: This architecture laid out a blueprint for using a centralized, server-based intermediary to manage remote access to local devices over the public internet, a model that anticipates the cloud-based backends used by many modern smart home and IoT products.

Key Claims at a Glance

• The complaint asserts infringement of "one or more claims" of the ’526 Patent without specifying them Compl. ¶16 Independent claim 1 is representative of the invention's core architecture.
• The essential elements of independent claim 1 include:
  • An Internet browser hardware device running a browser.
  • An "extranet" located external to the user's premises.
  • A plurality of "connection gateways," each located in a respective user's premises.
  • At least one "communications server" located on the extranet, adapted to "interconnect on-demand" with the gateways.
  • The system operates in response to a user inputting a URL to access the extranet, which causes the communications server to determine the user's authority and then create a "new communications session" with the correct home gateway.
  • During this session, the extranet obtains information from the gateway and "serves a webpage to the Internet browser" to provide that information to the user.
• The complaint does not explicitly reserve the right to assert dependent claims.

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

The Invention Explained

• Problem Addressed: As a continuation of the application that led to the ’526 Patent, the ’097 Patent addresses the same technical problems of providing simple, platform-independent remote access to home devices ʼ097 Patent, col. 1:58-67 ʼ097 Patent, col. 2:9-14
• The Patented Solution: The ’097 Patent describes the same fundamental architecture as its parent, comprising a user-facing component ("first hardware processing circuitry"), an external network component ("second hardware processing circuitry located in a first network"), and an in-home device ("connection gateway") ʼ097 Patent, claim 1 The system is configured so that a user accessing a URL on the external network initiates a sequence that results in the external network serving information from the in-home gateway to the user's device ʼ097 Patent, abstract ʼ097 Patent, claim 1
• Technical Importance: The technical importance is identical to that of the ’526 Patent, as it shares the same specification and priority date.

Key Claims at a Glance

• The complaint asserts infringement of "one or more claims" of the ’097 Patent without specification Compl. ¶22 Independent claim 1 is representative.
• The essential elements of independent claim 1, using different terminology, include:
  • A "first hardware processing circuitry" running an access browser module (the user's device).
  • A "second hardware processing circuitry" in a "first network" (the external network/extranet).
  • A "connection gateway" in the user's local network.
  • The second hardware circuitry is external to the premises and communicates "on-demand" with the gateway.
  • The system is configured so that user input of a URL "begins a sequence" where the second hardware circuitry serves information from the gateway to the first hardware circuitry.
• The complaint does not explicitly reserve the right to assert dependent claims.

III. The Accused Instrumentality

Product Identification

• The complaint does not identify any specific accused product, method, or service by name Compl. ¶16 Compl. ¶22 It refers generally to "device(s), including but not limited to, systems" that Defendant "offers for sale, sells and manufactures" Compl. ¶16

Functionality and Market Context

• The complaint does not provide sufficient detail for analysis of the functionality or market context of any accused instrumentality. It makes only conclusory allegations that Defendant's unspecified products and services embody the claimed inventions Compl. ¶16 Compl. ¶22

IV. Analysis of Infringement Allegations

The complaint references preliminary claim charts in Exhibits B and D as support for its infringement allegations Compl. ¶17 Compl. ¶23 However, these exhibits were not filed with the public complaint. The narrative infringement theory is limited to the conclusory statement that Defendant's products and services infringe one or more claims of the patents-in-suit Compl. ¶16 Compl. ¶22 Without the claim charts or a more detailed description of the accused technology, a tabular analysis of the infringement allegations is not possible.

No probative visual evidence provided in complaint.

• Identified Points of Contention:
  • Pleading Sufficiency: The primary threshold issue is procedural. A question for the court will be whether the complaint's failure to identify any specific accused product or explain how it allegedly infringes satisfies the plausibility pleading standards set forth in Bell Atlantic Corp. v. Twombly and Ashcroft v. Iqbal.
  • Scope Questions: Assuming the case proceeds, a central dispute may involve the scope of the patent claims relative to modern technology. For instance, do the patent's descriptions of an "extranet" and "on-demand" connections, which originate from a 1998 priority date and discuss technologies like PSTN and ISDN, read on modern cloud computing architectures (such as Amazon Web Services) and "always-on" broadband-connected devices? ʼ526 Patent, col. 8:5

V. Key Claim Terms for Construction

• The Term: "extranet" ʼ526 Patent, claim 1

  • Context and Importance: This term is the architectural linchpin of the claimed system, defining the intermediary network that is external to the home. Its construction will be critical for determining whether modern cloud service platforms fall within the scope of the claims. Practitioners may focus on this term because Defendant operates one of the world's largest cloud platforms (AWS), which may be accused of functioning as the claimed "extranet".
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification defines an extranet as "a private network that uses the Internet protocols and the public telecommunication system to securely share part of a business's information or operations with suppliers, vendors, partners, customers, or other businesses" ʼ526 Patent, col. 6:27-33 It also states the extranet can be implemented as a "Virtual Private Network (VPN)" ʼ526 Patent, col. 2:47-49 This language could support a broad reading that covers any secure network operating over the public internet to connect a provider with its customers.
    • Evidence for a Narrower Interpretation: The specific examples of sharing information with "suppliers, vendors, partners" could be argued to limit the term to a business-to-business context, rather than a mass-market, consumer-facing cloud service ʼ526 Patent, col. 6:31-32

• The Term: "interconnect on-demand" ʼ526 Patent, claim 1

  • Context and Importance: This term describes how the communications server connects to the home gateway. Its definition is key to distinguishing the claimed invention from prior art and to determining if it reads on modern, persistently connected IoT devices. An "always-on" device might not be seen as connecting "on-demand."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent describes a process where the connection is initiated only after a user accesses a URL and is authenticated ʼ526 Patent, col. 7:40-67 ʼ526 Patent, col. 8:1-20 This could be interpreted broadly to mean any session-based connection established for the purpose of fulfilling a specific user request, even if the underlying hardware maintains a constant network presence.
    • Evidence for a Narrower Interpretation: The specification describes establishing a connection "across the telecommunications facility," referencing systems like PSTN and ISDN, which were not typically "always-on" ʼ526 Patent, col. 8:1-5 This may support a narrower construction requiring the creation of a network-level connection that did not previously exist, as opposed to simply sending data over an existing broadband connection.

VI. Other Allegations

• Indirect Infringement: The complaint makes a conclusory allegation that Defendant induced infringement but does not plead specific facts to support the knowledge and intent elements of such a claim, such as referencing user manuals or advertising materials that instruct customers on infringing uses Compl. ¶12
• Willful Infringement: The complaint does not allege that Defendant had pre-suit knowledge of the patents-in-suit. The prayer for relief includes a conditional request for a finding of willfulness and enhanced damages, contingent upon discovery revealing that Defendant knew of the patents prior to the lawsuit Compl. ¶e, p. 8

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

1. A Threshold Procedural Question: Will the complaint survive a motion to dismiss? The complete absence of an identified accused product or a description of any specific infringing functionality raises a significant question of whether the allegations meet the plausibility standard required for federal court pleadings.
2. A Question of Technological Evolution: Can the term "extranet", rooted in the 1998-era context of VPNs and secure business networks, be construed to cover a modern, massively scaled, public-facing cloud services platform like AWS? The outcome of this definitional dispute will likely be pivotal to the infringement analysis.
3. A Question of Functional Operation: Does a modern "always-on" IoT device, which may maintain a persistent connection to a cloud server, perform the claimed step of creating a "new communications session" to "interconnect on-demand"? The case may turn on whether the accused architecture establishes a connection in the manner contemplated by the patent or operates in a fundamentally different, continuously connected way.