AlmondNet Inc v. Amazon.com Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: AlmondNet, Inc. (Delaware) and Datonics LLC (Delaware)
  • Defendant: Amazon.com, Inc., Amazon.com Services LLC, and Amazon Web Services, Inc. (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 6:24-cv-00234, W.D. Tex., 09/03/2024
• Venue Allegations: Venue is alleged to be proper based on Amazon maintaining a regular and established place of business in the district, specifically an Amazon Tech Hub located in Austin, Texas.
• Core Dispute: Plaintiff alleges that Defendant's advertising platform and Amazon Demand-Side Platform (DSP) infringe two patents related to systems and methods for network-based targeted advertising.
• Technical Context: The technology at issue involves the aggregation and use of internet user profile data from third-party sources to enable the delivery of targeted advertisements on websites and other media properties.
• Key Procedural History: The complaint alleges that Plaintiff provided Defendant with pre-suit notice of U.S. Patent No. 8,494,904 and its alleged infringement by Amazon's DSP service in communications dated July 24, 2019, and October 25, 2019.

Case Timeline

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

U.S. Patent No. 10,984,445 - "providing collected profiles to media properties having specified interests," issued April 20, 2021

The Invention Explained

• Problem Addressed: The patent describes inefficiencies in the online advertising ecosystem where media properties (e.g., websites) seeking to monetize "low-value ad space" may waste resources attempting to enhance their user profiles from databanks that lack relevant data ʼ445 Patent, col. 6:1-17 Additionally, the patent notes the challenge of tracking the usage of externally sourced profiles for the purpose of compensating the original profile providers ʼ445 Patent, col. 6:35-42
• The Patented Solution: The invention proposes a system operated by a "profile owner company" that acts as an intermediary ʼ445 Patent, col. 7:19-21 This system first records the specific types of user profiles that various media properties are interested in ʼ445 Patent, col. 8:19-29 When a visitor's profile is received from a "profile supplier," the system identifies which media properties have pre-registered an interest in that type of profile and then arranges for the visitor to be "tagged" with an identifier readable by that media property ʼ445 Patent, col. 9:17-24 The media property can then use this tag to deliver targeted advertising to the visitor and report the usage back to the system, thereby creating an efficient, monetizable exchange ʼ445 Patent, abstract ʼ445 Patent, Fig. 1
• Technical Importance: This method aims to create a more efficient marketplace for user profile data by proactively matching collected profiles with the pre-stated interests of advertisers or media properties, thereby improving the ability to monetize ad inventory that is not adjacent to highly specific content ʼ445 Patent, col. 5:6-16

Key Claims at a Glance

The complaint focuses on independent claim 1 Compl. ¶19 While the complaint does not explicitly reserve the right to assert dependent claims, this is a standard litigation practice. The essential elements of claim 1 are:

• A method of causing delivery of electronic advertisements based on provided profiles, comprising:
• (a) A computer system automatically storing profile information associated with a visitor, received from a profile owner computer, where a tag serves as a link to the profile information.
• (b) The profile owner computer is programmed to: (i) automatically select a media property based on a comparison between the visitor's profile information and stored requests from a plurality of media properties, and (ii) arrange for electronic storage of a requested profile linked to the tag when the media property is the entity controlling the main computer system.
• (c) Later, when the visitor's device is available, the computer system uses the tag to access the stored profile information and uses that information to cause the delivery of a targeted electronic advertisement.

U.S. Patent No. 8,494,904 - "method and stored program for accumulating descriptive profile data along with source information for use in targeting third-party advertisements," issued July 13, 2013

The Invention Explained

• Problem Addressed: The patent addresses a need in the art for commerce in specific "attributes of information" rather than entire databases or records ʼ904 Patent, col. 1:59-64 In the context of targeted advertising, individual attributes (e.g., a user's interest in a product, a demographic detail) have discrete economic value, but systems for managing and compensating the sources of these attributes are lacking ʼ904 Patent, col. 2:1-10
• The Patented Solution: The invention discloses a "descriptive-profile mercantile method" where a central system acts as a data brokerage ʼ904 Patent, col. 7:31-34 The system electronically receives "partial profiles" containing specific attributes about an internet entity from various unaffiliated third-party sources ʼ904 Patent, col. 15:61-65 It adds these received attributes to a maintained profile for that entity and, crucially, generates and stores an electronic record of which third party contributed which specific attributes ʼ904 Patent, abstract This maintained, aggregated profile can then be used for targeting advertisements, and the source record enables compensation to the original data providers ʼ904 Patent, col. 13:5-10
• Technical Importance: The invention provides a technical framework for a granular data economy, allowing multiple, independent data sources to contribute to a composite user profile while maintaining attribution to ensure proper compensation when that data is monetized.

Key Claims at a Glance

The complaint focuses on independent claim 1 Compl. ¶27 The essential elements are:

• An automated method of collecting profiles of Internet-using entities, comprising:
• (a) Electronically receiving, at a programmed computer system from unaffiliated third parties, a URL-redirected partial profile of an entity, where the profile is received with an identification of the third party that contributed it, and automatically storing the profile.
• (b) Automatically adding the received partial profile to a maintained profile believed to be related to the same entity.
• (c) Automatically generating and storing an electronic record of which third parties contributed particular profile attributes to the maintained profile.
• (d) The maintained profile comprises data used for targeting third-party advertisements to the entity's computer.

III. The Accused Instrumentality

Product Identification

The complaint names "Amazon's advertising platform and Amazon DSP" as the Accused Instrumentalities Compl. ¶17 Compl. ¶24

Functionality and Market Context

The complaint alleges that Amazon's advertising services, including its Demand-Side Platform (DSP), function as a system for delivering targeted advertisements based on user profiles Compl. Ex. 2, p. 1 This system allegedly ingests audience data from various third-party Data Management Platforms (DMPs) and Customer Data Platforms (CDPs), such as those operated by Oracle and Adobe Compl. Ex. 2, p. 2 The complaint asserts that this allows advertisers to use pre-existing audience segments and create "lookalike" audiences to target consumers on Amazon's properties and across the web Compl. Ex. 2, p. 1 A screenshot from an Amazon webpage describes integrations with multiple CDP vendors, enabling advertisers to stream "pseudonymized first-party signals" into Amazon's systems for "audience building, campaign execution, performance measurement, and custom insights" Compl. Ex. 2, p. 2

IV. Analysis of Infringement Allegations

'445 Patent Infringement Allegations

'904 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions: A central question for the ʼ904 Patent may be the construction of "electronically URL-redirected partial profile." The complaint alleges this covers modern data transfer via pixels and JavaScript redirects Compl. Ex. 4, p. 2 A court may need to determine if this term, from a patent with a 1999 priority date, should be limited to traditional browser redirects or can be construed more broadly to encompass modern server-to-server and client-side data sharing mechanisms.
• Technical Questions: For the ʼ445 Patent, a key technical question may be whether the accused system operates as claimed. The claim requires the "profile owner computer" (allegedly a third-party DMP) to "automatically select a media property entity" based on stored requests. The analysis may focus on whether the third-party DMPs perform this specific selection logic based on requests from Amazon, or if they simply make audiences available for Amazon to select, which could raise questions about whether the claim elements are performed by the required actors in the claimed sequence.

V. Key Claim Terms for Construction

Term: "profile owner computer" (from ʼ445 Patent, Claim 1)

• Context and Importance: The plaintiff's infringement theory casts third-party Data Management Platforms (e.g., Oracle, Adobe) as the "profile owner computer" that selects Amazon as a destination for user data Compl. Ex. 2, p. 10 The viability of the infringement claim depends on whether the functions of these third-party servers map onto the claimed functions of the "profile owner computer."
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent uses the term "profile supplier" broadly to refer to entities that transfer profile information to a "BT company" ʼ445 Patent, col. 2:24-27 This could support an interpretation where any third-party data provider's server could be considered a "profile owner computer."
  • Evidence for a Narrower Interpretation: The detailed description and figures often depict a "PO company" operating a central server that receives redirects from profile suppliers and then interacts with media properties ʼ445 Patent, Fig. 2 ʼ445 Patent, col. 7:19-21 This could suggest a more integrated architecture where the "profile owner computer" is the central server of the claimed system, not a disparate third-party entity.

Term: "electronically URL-redirected partial profile" (from ʼ904 Patent, Claim 1)

• Context and Importance: This term defines the mechanism by which the accused system allegedly receives infringing data. The complaint asserts this is met by technologies like tracking pixels and JavaScript redirects Compl. Ex. 4, p. 2 Its construction will be critical, as modern ad-tech systems also rely heavily on server-to-server API calls, and the applicability of this term to such methods will likely be disputed.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The related '445 patent, which shares a specification lineage, extensively discusses "redirects" as the mechanism for a profile supplier to send a visitor to the central system ʼ445 Patent, col. 8:31-33 One might argue the core inventive concept is the transfer of data upon a user action, not the specific technical implementation of the redirect itself.
  • Evidence for a Narrower Interpretation: The term "URL-redirected" has a specific technical meaning in the context of web protocols (e.g., an HTTP 3xx redirect). A defendant may argue that the claim is limited to this specific mechanism, common at the time of invention, and does not cover asynchronous data transfers via JavaScript or server-side API calls that do not involve a user's browser being fully redirected.

VI. Other Allegations

Indirect Infringement

The complaint alleges that Amazon and/or the users of its platform "direct and control use of the Accused Instrumentalities to perform acts that result in infringement" Compl. ¶18 Compl. ¶25 The complaint does not provide sufficient detail for analysis of specific facts supporting induced or contributory infringement.

Willful Infringement

Willfulness is alleged for the ʼ904 Patent Compl. ¶26 The complaint bases this allegation on pre-suit knowledge, asserting that the plaintiff notified Amazon of the ʼ904 Patent and its infringement by Amazon's DSP via communications on July 24, 2019, and October 25, 2019 Compl. ¶12 Compl. ¶13 Compl. ¶26 The complaint alleges that despite this knowledge, Amazon continued its infringing conduct Compl. ¶26

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

• A core issue will be one of definitional scope: can the term "electronically URL-redirected partial profile," from a patent with a 1999 priority date, be construed to cover the modern data ingestion methods used in the accused Amazon DSP system, such as API calls and pixel-based tracking, or is its meaning limited to the browser-level redirection technologies of that era?
• A key question of architectural correspondence will be central to the '445 patent analysis: does the accused ad-tech ecosystem, involving separate third-party DMPs (like Oracle) and ad-consuming platforms (like Amazon DSP), technically map onto the patent's more integrated claim structure, particularly the requirement that a "profile owner computer" performs the specific function of selecting a media property based on its stored requests?
• An evidentiary question will concern willfulness: what was the substance of the 2019 communications, and does the evidence show Amazon acted with objective recklessness regarding a high likelihood of infringement of the '904 patent after receiving the alleged notice?