2:25-cv-00017
Alto Dynamics LLC v. Century Fuxuan Technology Development Beijing Co Ltd
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Alto Dynamics, LLC (Georgia)
- Defendant: Century Fuxuan Technology Development (Beijing) Co. LTD. (China) and Digitrading SAS dba DHgate (France)
- Plaintiff’s Counsel: Rozier Hardt McDonough PLLC
- Case Identification: 2:25-cv-00017, E.D. Tex., 01/07/2025
- Venue Allegations: Plaintiff alleges venue is proper because Defendants are not residents of the United States and may therefore be sued in any judicial district under the alien-venue rule.
- Core Dispute: Plaintiff alleges that Defendants’ e-commerce website, "dhgate.com", infringes five U.S. patents related to database-to-XML conversion, client-side user activity monitoring, and stateless user authentication.
- Technical Context: The patents address foundational web technologies for integrating legacy relational databases with modern web front-ends and for efficiently managing user sessions, tracking, and authentication in large-scale e-commerce environments.
- Key Procedural History: The complaint asserts two families of patents. U.S. Patent RE 46,513 is a reissue of U.S. Patent 7,020,645, and U.S. Patent 7,657,531 is a continuation of the application that led to the '645 patent; prosecution history of the original patent and the reissue may be relevant to claim scope. The remaining patents are related through a continuation application. Certificates of Correction have been issued for four of the five asserted patents.
Case Timeline
| Date | Event |
|---|---|
| 2000-02-09 | '100 Patent Priority Date |
| 2001-02-08 | '100 Patent Application Filed |
| 2001-04-19 | '531 and RE'513 Patents Priority Date |
| 2001-12-21 | '018 and '160 Patents Priority Date |
| 2002-12-18 | '018 Patent Application Filed |
| 2003-08-05 | '100 Patent Issue Date |
| 2003-11-25 | '100 Patent Certificate of Correction Issued |
| 2006-01-05 | '531 Patent Application Filed |
| 2006-03-28 | Original Patent for RE'513 (7,020,645) Issued |
| 2006-11-07 | '160 Patent Application Filed |
| 2006-12-19 | '018 Patent Issue Date & Certificate of Correction Issued |
| 2008-06-24 | '160 Patent Issue Date |
| 2010-02-02 | '531 Patent Issue Date |
| 2010-11-13 | '531 Patent Certificate of Correction Issued |
| 2012-02-08 | RE'513 Patent Reissue Application Filed |
| 2017-08-15 | RE'513 Patent Issue Date |
| 2025-01-07 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 6,604,100, "Method For Converting Relational Data Into A Structured Document", Issued August 5, 2003
The Invention Explained
- Problem Addressed: The patent describes the technical challenge of automatically converting data from traditional relational databases, which are flat and tabular, into the nested, hierarchical structure of XML required for web applications. Prior methods were allegedly inefficient, not dynamic, and often restricted to a fixed (canonical) XML format rather than an arbitrary one. (Compl. ¶¶24-26; ’100 Patent, col. 1:37-2:24).
- The Patented Solution: The invention proposes a system (termed "SilkRoute") that creates a virtual XML view of a relational database. It uses a specific method where a user's query against this virtual view is programmatically combined ("composed") with the view's definition to generate a new, efficient query. This new query is then partitioned into a data extraction part (an SQL query sent to the database) and a construction part (an XML template), allowing the system to retrieve only the necessary data and construct the required XML fragment on the fly, without materializing the entire document. (Compl. ¶28; ’100 Patent, Abstract, Fig. 1).
- Technical Importance: The described method provided a way to bridge the gap between ubiquitous legacy relational database systems and the emerging XML standard for data exchange on the internet, offering a more flexible and efficient alternative to full data exports or rigid conversion tools. (Compl. ¶25; ’100 Patent, col. 1:25-36).
Key Claims at a Glance
- The complaint asserts at least independent claim 1. (Compl. ¶32).
- Essential elements of claim 1 include:
- storing a view query that defines a structured document view of the relational database, with the view query's structure being independent of the database's data structure;
- receiving a user query against the structured document view;
- forming an executable query by determining a composition of the view query and the user query;
- partitioning the executable query into a data extraction portion and a construction portion;
- transmitting the data extraction portion to the relational database;
- receiving at least one tuple stream from the database; and
- merging the tuple stream and the construction portion to generate a structured document of arbitrary nesting depth.
U.S. Patent No. 7,152,018, "System And Method For Monitoring Usage Patterns", Issued December 19, 2006
The Invention Explained
- Problem Addressed: The patent identifies the inefficiency of server-side user tracking systems, which required significant server resources for database storage and lookups and could not take advantage of web caches. (Compl. ¶43; ’018 Patent, col. 2:1-24, col. 4:1-6).
- The Patented Solution: The invention describes a method where a "state object" (e.g., a cookie) containing a user's usage profile is stored on the client's computer. The key inventive step is that this profile is modified by scripts that are sent from the server to the client. This client-side modification is claimed to preclude manipulation by the server itself, offloading the computational work and making the system more efficient. (Compl. ¶¶41-42; ’018 Patent, Abstract, col. 6:18-25).
- Technical Importance: By shifting profile management from the server to the client, the invention offered a more scalable architecture for personalizing web content based on user behavior, a critical function for growing web applications. (Compl. ¶43; ’018 Patent, col. 4:1-6).
Key Claims at a Glance
- The complaint asserts at least independent claim 1. (Compl. ¶47).
- Essential elements of claim 1 include:
- providing at least one state object, which includes a profile representative of user usage;
- storing the state object at a client location;
- passing the state object to a central server with each subsequent interaction;
- receiving the state object back from the central server with its response;
- wherein the profile is modified to reflect the interaction by scripts provided by the server to the client, "thus precluding manipulation of the profile by the server."
Multi-Patent Capsule: U.S. Patent No. 7,392,160, "System And Method For Monitoring Usage Patterns", Issued June 24, 2008
Technology Synopsis
Continuing the theme of the ’018 patent, this patent addresses inefficient user monitoring. The solution is also a client-side profiling system using a state object. The asserted claim adds a server-side analysis step, wherein the server "audits the state object/profile passed to it, and performs analysis on the audited profile in order to direct services and/or information suited to the profile to the client location." (Compl. ¶¶55-56, 61; ’160 Patent, cl. 1).
Asserted Claims
At least independent claim 1. (Compl. ¶60).
Accused Features
The use of cookies by "dhgate.com" to track user behavior, followed by server-side analysis of that behavior to provide tailored content or services. (Compl. ¶¶59, 61).
Multi-Patent Capsule: U.S. Patent No. 7,657,531, "Systems And Methods For State-Less Authentication", Issued February 2, 2010
Technology Synopsis
The patent addresses problems with conventional authentication systems that required repeated logons for different transactions and were often inflexible. The invention provides a method of "stateless" authentication where a user authenticates once to generate a "valid security-context." This context is then sent with subsequent requests to access resources, eliminating the need for re-authentication. The system includes a mechanism for renewing the security context. (Compl. ¶¶68-71).
Asserted Claims
At least independent claim 1. (Compl. ¶75).
Accused Features
The authentication and session-management system of "dhgate.com", including the functionality for renewing user cookies after expiration and the password reset process. (Compl. ¶¶74, 76).
Multi-Patent Capsule: U.S. Patent No. RE 46,513, "Systems And Methods For State-Less Authentication", Issued August 15, 2017
Technology Synopsis
This patent, a reissue of U.S. Patent No. 7,020,645, also targets stateless authentication. The solution again involves creating a "security context" based on initial logon information. The asserted claim specifies the structure of this context, requiring that it comprise "a plaintext header and an encrypted body," where the header contains a security context ID, a key handle, and an algorithm identifier. (Compl. ¶¶83, 86).
Asserted Claims
At least independent claim 1. (Compl. ¶90).
Accused Features
The use of "secure communication sessions" by "dhgate.com", where a logon component allegedly generates a security context from user logon information to control access to resources. (Compl. ¶¶89, 91).
III. The Accused Instrumentality
Product Identification
The website https://www.dhgate.com/ and its associated hardware, software, and backend functionality (the "Accused Products"). (Compl. ¶17).
Functionality and Market Context
- The Accused Products constitute an online e-commerce platform that allows users to search for, view, and purchase items. (Compl. ¶17). Its core technical functions relevant to the lawsuit include employing database searching and viewing capabilities, tracking user activities and preferences via cookies, and providing user authentication and session management. (Compl. ¶¶17, 33, 46, 76, 91).
- The complaint alleges that Defendants use this platform to conduct substantial business and derive revenue from customers in the United States, including in the Eastern District of Texas, by directly contracting with them and shipping products worldwide. (Compl. ¶¶6, 11, 14).
IV. Analysis of Infringement Allegations
’100 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| storing a view query that defines a structured document view of the relational database, a structure of the view query being independent of a structure of data in the relational database; | The Accused Products allegedly store predefined methods for presenting relational product data to users in a structured format (e.g., a web page), independent of the backend database schema. | ¶33 | col. 2:35-38 |
| receiving a user query against the structured document view; | A user query is received when a user interacts with the website, for example, by clicking on a product category or entering a search term to view products. | ¶33 | col. 5:12-16 |
| forming an executable query by determining a composition of the view query and the user query; | The backend system allegedly forms an executable database query by combining the user's request with the stored view definition for how to display the data. | ¶33 | col. 9:11-21 |
| partitioning the executable query into a data extraction portion and a construction portion; | The system allegedly partitions the executable query into an SQL query (data extraction) and a template for rendering the results as a structured document, such as an HTML page. | ¶33 | col. 5:25-29 |
| transmitting the data extraction portion to the relational database; | The SQL portion of the query is transmitted to the backend relational database that stores product information. | ¶33 | col. 5:37-39 |
| receiving at least one tuple stream from the relational database according to the data extraction portion; and | The system receives streams of data (tuples) from the database in response to the SQL query. The complaint's Figure 1, a screenshot of a product search results page, is presented as evidence of this generated document. (Compl. p.9). | ¶33 | col. 5:40-43 |
| merging the at least one tuple stream and the construction portion to generate a structured document...of arbitrary nesting depth. | The received data is merged with the display template to generate the final structured web page presented to the user. | ¶33 | col. 5:43-46 |
Identified Points of Contention (’100 Patent)
- Technical Question: What evidence does the complaint provide that the accused system performs the specific steps of "composition" and "partitioning"? The infringement allegation is a block recitation of the claim language, raising the question of whether the ordinary operation of an e-commerce site meets the specific, multi-step method architecture required by the claim.
- Scope Question: A key issue may be whether the term "composition of the view query and the user query" can be read to cover the common practice of a web server receiving an HTTP request and generating a corresponding SQL query, or if it is limited to the more specific algorithmic process involving a "pattern matcher" and "rewriter" described in the patent's detailed description. ('100 Patent, Fig. 2).
’018 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| providing at least one state object, the object including a profile representative of user usage; | The "dhgate.com" server provides a "state object," such as a browser cookie, that contains a profile of the user's activity. | ¶48 | col. 2:26-29 |
| storing the state object at a client location; | The cookie is stored on the user's client machine (i.e., in the user's web browser). The complaint's Figure 2, showing a browser's cookie storage for the DHgate website, is offered as evidence. (Compl. p.13). | ¶48 | col. 2:29-30 |
| passing, to a central server, the state object with each subsequent interaction initiation; | With each subsequent request to the "dhgate.com" server (e.g., navigating to a new page), the user's browser passes the cookie back to the server. | ¶48 | col. 2:30-32 |
| receiving, from the central server, the state object along with the response of the central server; | The server sends the cookie back to the client along with the requested web page content. | ¶48 | col. 2:33-35 |
| wherein the profile is modified...by one of one or more scripts within or included in information/resources provided to the client location...thus precluding manipulation of the profile by the server. | The user's profile within the cookie is allegedly modified by client-side scripts (e.g., JavaScript) delivered with the web page. The complaint alleges this method of modification precludes the server from manipulating the profile, thereby meeting the claim limitation. | ¶48 | col. 2:35-43 |
Identified Points of Contention (’018 Patent)
- Scope Question: The claim includes the negative limitation "thus precluding manipulation of the profile by the server." A central dispute will be whether this requires an architecture where the server is incapable of modifying the profile, or whether it is met if the modification function is merely offloaded to client-side scripts for a given interaction, even if the server retains the ability to modify cookies via other means (e.g., HTTP
Set-Cookieheaders). - Technical Question: What evidence demonstrates that the modification of the user profile cookie is performed by client-side scripts in a manner that "precludes" server-side manipulation, as opposed to a hybrid model where both client and server can alter the cookie's contents?
V. Key Claim Terms for Construction
For the ’100 Patent
- The Term: "composition of the view query and the user query"
- Context and Importance: This term is at the heart of the claimed method. Its construction will determine whether infringement requires a specific, sophisticated query transformation algorithm (as detailed in the specification) or could cover the more general process of a web server generating a database query in response to a user's web request.
- Intrinsic Evidence for Interpretation:
- Evidence for a Narrower Interpretation: The specification describes a specific "Query Composer" module (102) that implements composition using a "Pattern Matcher" and a "Rewriter" to transform query templates. ('100 Patent, Fig. 2; col. 12:35-49). This suggests "composition" is a term of art for this specific, detailed process.
- Evidence for a Broader Interpretation: The term itself is not explicitly defined with limiting language in the claims. A plaintiff may argue that any system that logically combines a user's input with a predefined data structure to form a final database query performs a "composition."
For the ’018 Patent
- The Term: "precluding manipulation of the profile by the server"
- Context and Importance: This negative limitation is a likely point of non-infringement argument. The case may turn on whether the accused system, which likely uses standard HTTP cookies that can be set by the server, can be seen as "precluding" server manipulation.
- Intrinsic Evidence for Interpretation:
- Evidence for a Narrower Interpretation: The patent repeatedly emphasizes the "computationally efficient" nature of the invention, which stems from storing and updating profiles on the client "rather than the server machine" and not requiring "database storage and lookup on the server side." ('018 Patent, col. 4:1-6). This purpose-driven language suggests the preclusion must be real and effective to achieve the stated benefits.
- Evidence for a Broader Interpretation: The specification states that through client-side scripts, "it is possible to update and manipulate the contents of the cookie profile without requiring any server side manipulation." ('018 Patent, col. 6:18-22). A plaintiff may argue this means the invention is the provision of a client-side modification capability, which itself "precludes" the need for server manipulation, thereby satisfying the limitation.
VI. Other Allegations
Indirect Infringement
The complaint does not plead separate counts for indirect infringement. However, for its method claims, it alleges that Defendants infringe by, among other things, allowing users to perform the claimed methods and by virtue of "Defendants' direction and control of customers." (Compl. ¶¶48, 61, 76). This language appears to lay a foundation for an argument of divided infringement or induced infringement by providing the "dhgate.com" platform and instructing users on its use.
Willful Infringement
The complaint does not allege that Defendants had pre-suit knowledge of the patents or that the infringement was willful. It requests attorneys' fees for an "exceptional case" but pleads no specific facts to support such a finding. (Compl. ¶94.e).
VII. Analyst’s Conclusion: Key Questions for the Case
- A central issue will be one of technical implementation versus claim scope: Does the general operation of the "dhgate.com" e-commerce site, which necessarily converts database data for web display and manages user sessions with cookies, practice the specific, multi-step methods and system architectures defined in the asserted claims, or are the complaint's allegations a conclusory mapping of claim language onto conventional web technology?
- A key legal question will be the interpretation of a negative limitation: Can the '018 patent's requirement of "precluding manipulation of the profile by the server" be met by a system that offloads some profile updates to client-side scripts, even if the server retains the technical ability to modify cookies through standard HTTP headers, or does it require an architecture where the server is functionally prevented from such manipulation?
- A third key question will be one of definitional equivalence, particularly for the authentication patents ('531 and RE'513): Can the patents' highly structured "security context"—with its specified plaintext headers, encrypted bodies, and renewal protocols—be found in the functionality of standard website session management, or is there a fundamental mismatch in the claimed security architecture and the accused system's operation? The complaint points to a password reset page (Figure 3, Compl. p.20) and a sign-in page (Figure 4, Compl. p.24) as evidence.