4:18-cv-01433
Orostream LLC v. DPI Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Orostream LLC (Texas)
- Defendant: DPI, Inc. dba Amped Wireless (Missouri)
- Plaintiff’s Counsel: The Simon Law Firm, P.C.
- Case Identification: 4:18-cv-01433, E.D. Mo., 08/28/2018
- Venue Allegations: Venue is alleged to be proper because Defendant is a Missouri corporation with a place of business in the district, where at least a portion of the alleged infringement occurred.
- Core Dispute: Plaintiff alleges that Defendant’s Wi-Fi routers, which feature Quality of Service (QoS) traffic prioritization, infringe a patent related to efficiently transferring targeted information over a network by utilizing idle bandwidth.
- Technical Context: The technology concerns network traffic management, specifically methods for delivering secondary, "targeted" information to a user without delaying the user's primary network activity.
- Key Procedural History: The complaint notes that the patent-in-suit expired on April 11, 2017, and that Plaintiff seeks damages for infringement occurring up to six years prior to the complaint's filing. It also states the patent has been cited as prior art in over 100 subsequent U.S. patents.
Case Timeline
| Date | Event |
|---|---|
| 1996-04-15 | ’508 Patent Priority Date |
| 1997-04-11 | ’508 Patent Application Filing Date |
| 1998-06-16 | ’508 Patent Issue Date |
| 2017-04-11 | ’508 Patent Expiration Date |
| 2018-08-28 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 5,768,508 - Computer Network System and Method for Efficient Information Transfer
- Patent Identification: U.S. Patent No. 5,768,508, "Computer Network System and Method for Efficient Information Transfer," issued June 16, 1998.
The Invention Explained
- Problem Addressed: The patent describes the problem of network bandwidth being underutilized, particularly the "free space between information packets" and the waste of capacity on idle network links (’508 Patent, col. 1:31-37). It also notes the difficulty for information providers to deliver targeted content to specific user groups and to gather meaningful data on user engagement (’508 Patent, col. 1:55-64).
- The Patented Solution: The invention proposes a system to solve this by transferring "target information" (e.g., commercial or non-commercial content) to a user's machine ("user node") during idle network periods, thereby not interfering with the user's primary "non-target" traffic. A "master program" on a server accesses a database of user profiles to select appropriate target content, sends a "pointer" or reference for that content to a client on the user's machine, and the client then manages the background download of the content from an information base, dynamically adjusting the transfer rate based on network congestion (’508 Patent, Abstract; col. 2:32-51). Figure 1 illustrates this architecture, separating the "user node", "master node", "master program", and "information base".
- Technical Importance: The technology aimed to create a new channel for content distribution that could be monetized or used for targeted communication, by leveraging network downtime without degrading the primary user experience (’508 Patent, col. 2:10-16).
Key Claims at a Glance
- The complaint asserts at least independent claim 26 (’508 Patent, col. 11:15-29; Compl. ¶12).
- The essential elements of independent claim 26 are:
- A method, performed by a "master program", comprising the steps of:
- registering the user node at a master node;
- receiving, through the master node, a node ID from the user node;
- accessing a master database for profile information corresponding to the node ID; and
- transmitting to the user node, through the master node, a target information reference corresponding to the accessed profile information,
- wherein the target information reference is a pointer to target information to be delivered to the user node while transferring non-target information without additional communication delay.
- The complaint does not explicitly reserve the right to assert dependent claims.
III. The Accused Instrumentality
Product Identification
- The accused products are "Wi-Fi routers that prioritize Internet traffic," with the "Amped Wireless High Power AC1750 Wi-Fi Access Point/Router APR175P" cited as an exemplary "Accused Instrumentality" (Compl. ¶12).
Functionality and Market Context
- The complaint focuses on the router's Quality of Service (QoS) and Wi-Fi Multimedia (WMM) features (Compl. ¶17). These features are alleged to prioritize network data packets into different categories, such as "Voice," "Video," "Best Effort," and "Background" (e.g., FTP), to ensure that delay-sensitive traffic like VoIP or streaming video is not impeded by less sensitive traffic like file downloads (Compl. ¶17-18). The complaint provides a screenshot from the user guide illustrating these QoS settings. (Compl. p. 8). The router is also alleged to identify connected devices by their MAC address and manage them via an internal DHCP lease table (Compl. ¶12-14). A screenshot of the router's "Connected Devices" dashboard is provided as evidence of this functionality. (Compl. p. 4).
IV. Analysis of Infringement Allegations
’508 Patent Infringement Allegations
| Claim Element (from Independent Claim 26) | Alleged Infringing Functionality - | Complaint Citation | Patent Citation |
|---|---|---|---|
| A method of connecting an information provider and a user node of a computer network, the method, performed by a master program... | The method is allegedly performed by the Accused Instrumentality (the router), which functions as the "master program". - | ¶12 | col. 11:15-18 |
| registering the user node at a master node; | A user device ("user node") allegedly "registers with the Accused Instrumentality by connecting (wired or wirelessly)," with the router itself serving as the "master node." - | ¶12 | col. 11:19-20 |
| receiving, through the master node, a node ID from the user node; | The router allegedly receives a MAC address (the "node ID") from the connected user device. - | ¶13 | col. 11:21-22 |
| accessing a master database for profile information corresponding to the node ID; | The router allegedly "accesses an internal table or a database," such as its DHCP lease table, which contains "profile information" like the MAC address and a corresponding IP address. - | ¶14 | col. 11:23-24 |
| transmitting to the user node...a target information reference...wherein the target information reference is a pointer to target information to be delivered...while transferring non-target information without additional communication delay. | The QoS feature allegedly treats low-priority traffic (e.g., FTP) as "target information" and high-priority traffic (e.g., voice/video) as "non-target information." The "target information reference" is alleged to be the address information in a data packet's header that points to a server. The router prioritizes the "non-target information" to avoid delay. | ¶15, ¶17 | col. 11:25-29 |
- Identified Points of Contention:
- Architectural Questions: A primary question may be whether the architecture of the Accused Instrumentality (a single, local Wi-Fi router) maps onto the patent’s described system. The patent depicts a distributed system where a "master program" and "master node" are distinct from the "user node" and communicate with it over a network like the Internet (’508 Patent, Fig. 1-2). The complaint alleges the router itself embodies the "master node" and "master program", which is co-located with the "user node".
- Scope Questions: The dispute may turn on whether a standard QoS traffic prioritization scheme constitutes the claimed method. The patent describes a specific process of selecting and sending a "target information reference" to a client, which then manages a background download. The complaint alleges that simply routing a low-priority data packet (like FTP) based on its destination IP address is equivalent to the claimed method. This raises the question of whether a packet's destination address is a "target information reference" and if a traffic category (e.g., "Background") is "target information" within the meaning of the patent.
V. Key Claim Terms for Construction
The Term: "master program"
Context and Importance: The infringement theory hinges on the router's firmware being the "master program". Its definition is critical to determining if the accused router performs the claimed method. Practitioners may focus on whether this term requires a remote, server-based application as depicted in the patent's embodiments, or if it can read on local device firmware.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The term itself is generic. The claims do not explicitly limit its location or implementation details, which may support an argument that any software performing the recited steps qualifies.
- Evidence for a Narrower Interpretation: The specification describes the "master program" as "a large server preferably built on a Sybase SQL-Server platform" that interacts with a "master database" and a client on the user node (’508 Patent, col. 3:40-49). This specific embodiment could be used to argue for a narrower construction limited to a more substantial, server-side entity.
The Term: "profile information"
Context and Importance: The complaint alleges that network identifiers like a MAC address and IP address in a DHCP table constitute "profile information". The viability of the infringement read on the "accessing a master database" element depends on this interpretation.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent states the "master database" "contains user information including user profile information" without exhaustively defining it in the claims, potentially leaving room for network identifiers to qualify.
- Evidence for a Narrower Interpretation: The specification provides specific examples of "profile information" as "age, gender, educational level, work status, items of interests, and hobbies," which are collected via a user registration form (’508 Patent, col. 4:1-4). This suggests the term refers to user demographic and interest data used for targeting content, not merely technical network identifiers.
VI. Other Allegations
- Indirect Infringement: The complaint does not allege indirect or induced infringement.
- Willful Infringement: The complaint does not include a claim for willful infringement. It alleges "constructive notice" of the patent "by operation of law" but does not plead facts related to pre-suit or post-suit knowledge of infringement (Compl. ¶19).
VII. Analyst’s Conclusion: Key Questions for the Case
The resolution of this case may depend on the court’s determination of the following questions:
An Architectural Question: Can the patent’s claims, which describe a distributed client-server architecture with a remote "master program" and "database", be read to cover the functionality of a single, self-contained consumer Wi-Fi router that is local to the end-user?
A Definitional and Functional Question: Does a standard network QoS system, which prioritizes generic traffic types (e.g., "Background" vs. "Voice"), perform the specific, claimed method of accessing "profile information" (e.g., user hobbies) to transmit a "pointer" ("target information reference") for specific "target information" to a user node? The case may turn on whether these distinct technical operations can be considered equivalent.