throbber
Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 1 of 5
`Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 1of5
`
`PUBLIC VERSION
`
`Exhibit A
`
`
`

`

`Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 2 of 5
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`
`ALMONDNET, INC.,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`AMAZON.COM, INC., AMAZON.COM
`SERVICES LLC, and AMAZON WEB
`SERVICES, INC.,
`
`
`Defendants.
`
`
`
`
`Civil Action No. 6:21-cv-00898-ADA
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`SUR-SUR-REPLY IN SUPPORT OF PLAINTIFF ALMONDNET, INC.’S
`OPPOSED MOTION TO ENTER FINAL JUDGMENT
`
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 3 of 5
`
`Amazon’s sur-reply does not dispute that it failed to provide any evidence AlmondNet
`
`knew of Amazon’s infringement prior to AlmondNet’s 2019 notice––a showing Amazon must
`
`make in opposing the presumptive award of prejudgment interest to establish that there was any
`
`delay. Having made no such showing, Amazon’s now argues for the first time that AlmondNet
`
`“reasonably should have known” about its infringement as early as 2012, citing to A.C. Aukerman.
`
`See Sur-Reply at 2. But the case on which Amazon relies was abrogated by the Supreme Court––
`
`a fact Amazon fails to disclose in its sur-reply. See SCA Hygiene Prod. Aktiebolag v. First Quality
`
`Baby Prod., LLC, 580 U.S. 328, 331–33 (2017) (abrogating A.C. Aukerman). Thus, Amazon fails
`
`to cite any non-abrogated authority for its manufactured “reasonably should have known”
`
`standard.
`
`Additionally, Amazon fails to show delay even under the “reasonably should have known”
`
`standard, because its arguments are based on pure speculation. While Amazon asserts that the
`
`public availability of its DSP in 2012 is sufficient to establish undue delay, its briefing lacks any
`
`evidence to support this claim. Amazon has provided no documents, testimony, or expert analyses
`
`demonstrating what specific materials regarding its DSP were available in 2012. Even if such
`
`materials existed, Amazon has not shown how they would have made infringement obvious in
`
`2012 for each of the asserted patents. The mere fact that AlmondNet’s complaint in 2021 was
`
`based on public sources does not mean that infringement was obvious in 2012. Indeed, several
`
`sources cited in AlmondNet’s complaint did not even exist until after 2020.1 The complexity of
`
`the infringement disputes that arose during this litigation only underscores that determining
`
`
`1 For example, the complaint charts for the ’139 and ’639 Patents frequently cite sources that
`were not publicly available until much later. See Dkt. 1, Exs. 1-14, 1-16. The link,
`https://www.amazon.com/gp/help/customer/display.html?nodeId=202075050, now redirects to
`https://www.amazon.com/gp/help/customer/display.html?nodeId=GLVB9XDF9M8MU7UZ,
`and has no record on the Internet Archive (web.archive.org) before September 8, 2020. The link,
`https://advertising.amazon.com/amazon-advertising-platform, repeatedly cited for the ’139
`Patent, now redirects to https://advertising.amazon.com/solutions/products/amazon-dsp, with no
`Internet Archive record before June 25, 2020. Additionally, link,
`https://aps.amazon.com/aps/unified-ad-marketplace/index.html, is cited for multiple limitations
`of the ’639 Patent chart, including exclusively for limitation 1[c], and has no Internet Archive
`record prior to August 11, 2021.
`
` 1
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 4 of 5
`
`infringement requires a highly detailed technical analysis. Not all uses of DSPs are infringing.
`
`Therefore, it cannot be assumed that AlmondNet reasonably should have been aware of Amazon’s
`
`infringement from the moment the DSP was released. Without specific evidence from Amazon,
`
`its undue delay argument remains speculative, unsubstantiated, and legally unsound.
`
`Finally, even if “reasonably should have known” were the correct standard and Amazon
`
`had provided evidence supporting such a finding, that would still be insufficient. Amazon would
`
`additionally need to show that any delay in filing suit was for some improper purpose and
`
`prejudice, which it failed to do for the reasons articulated in prior briefing.
`
`
`Date: August 28, 2024
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`/s/ Reza Mirzaie
`
`Reza Mirzaie
`Marc A. Fenster
`Benjamin T. Wang
`Adam Hoffman
`James A. Milkey
`Amy E. Hayden
`James S. Tsuei
`Jonathan Ma
`Daniel B. Kolko
`Jason M. Wietholter
`RUSS AUGUST & KABAT
`12424 Wilshire Boulevard 12th Floor
`Los Angeles, California 90025
`Tel: 310-826-7474
`Fax: 310-826-6991
`rmirzaie@raklaw.com
`mfenster@raklaw.com
`bwang@raklaw.com
`ahoffman@raklaw.com
`jmilkey@raklaw.com
`ahayden@raklaw.com
`jtsuei@raklaw.com
`jma@raklaw.com
`dkolko@raklaw.com
`jwietholter@raklaw.com
`
`Counsel for Plaintiff AlmondNet, Inc.
`
` 2
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 315 Filed 09/03/24 Page 5 of 5
`
`CERTIFICATE OF SERVICE
`
`
`
`Pursuant to the Federal Rules of Civil Procedure and Local Rule CV-5, I hereby
`
`certify that, on August 28, 2024 counsel of record who have appeared in this case are being served
`
`with a copy of the foregoing via email.
`
` /s/ Reza Mirzaie
`Reza Mirzaie
`
`
`
`
`
`
`
`
` 3
`
`PUBLIC VERSION
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket