throbber

`
`Case 5:18-md-02834-BLF Document 309 Filed 11/09/18 Page 1 of 3
`
`
`
`J. DAVID HADDEN (CSB No. 176148)/
`dhadden@fenwick.com
`SAINA S. SHAMILOV (CSB No. 215636)
`sshamilov@fenwick.com
`TODD R. GREGORIAN (CSB No. 236096)
`tgregorian@fenwick.com
`PHILLIP J. HAACK (CSB No. 262060)
`phaack@fenwick.com
`RAVI R. RANGANATH (CSB No. 272981)
`rranganath@fenwick.com
`CHIEH TUNG (CSB No. 318963)
`ctung@fenwick.com
`FENWICK & WEST LLP
`Silicon Valley Center
`801 California Street
`Mountain View, CA 94041
`Telephone:
`650.988.8500
`Facsimile:
`650.938.5200
`
`Counsel for
`AMAZON.COM, INC. and
`AMAZON WEB SERVICES, INC.
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
` Case No.: 5:18-md-02834-BLF
`
`STATEMENT OF AMAZON.COM,
`INC. AND AMAZON WEB SERVICES,
`INC. REGARDING REPRESENTA-
`TIVE CASES
`
`
`
`Case No. 5:18-cv-00767-BLF
`
`IN RE PERSONALWEB TECHNOLOGIES,
`LLC, ET AL., PATENT LITIGATION
`
`AMAZON.COM, INC. and AMAZON WEB
`SERVICES, INC.,
`
`
`Plaintiffs,
`
`
`
`v.
`
`
`PERSONALWEB TECHNOLOGIES, LLC, and
`LEVEL 3 COMMUNICATIONS, LLC,
`
`
`Defendants.
`
`
`PERSONALWEB TECHNOLOGIES, LLC and
`LEVEL 3 COMMUNICATIONS, LLC,
`
`
`Counterclaimants,
`
`
`
`v.
`
`
`AMAZON.COM, INC. and AMAZON WEB
`SERVICES, INC.,
`Counter-Defendants
`
`AMAZON’S STATEMENT RE REPRESENTATIVE
`CASES
`
`
`
`
`
`CASE NO.: 5:18-MD-02834-BLF
`CASE NO.: 5:18-cv-00767-BLF
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`

`

`Case 5:18-md-02834-BLF Document 309 Filed 11/09/18 Page 2 of 3
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`In response to the Court’s request to select a representative case, the parties agreed to des-
`
`ignate PersonalWeb’s case against Twitch Interactive, Inc. (Case No. 5:18-cv-05619-BLF). Per-
`
`sonalWeb Technologies, LLC and Level3 Communications LLC (“PersonalWeb”), however, re-
`
`quest that an additional case, against Kongregate, Inc., Case No. 5:18-cv-04625-BLF, also proceed.
`
`But there is no need for another representative case. In its case against Twitch, PersonalWeb asserts
`
`all of its infringement categories. And as it admitted at the last case management conference, if the
`
`Twitch case culminates in “a verdict against PersonalWeb that no infringement was found,” “none
`
`of the customer cases could go forward because there would be findings in each of the buckets.”
`
`(Nov. 2, 2018 CMC Hrg. Tr. at 6:17-22.) The Kongregate case, which involves only a subset of
`
`the buckets, adds nothing to the already selected representative case against Twitch.
`
`During the parties’ discussions, PersonalWeb’s sole reason for requesting that the Kongre-
`
`gate case proceed as well was its “concern” that because Twitch became a wholly-owned subsidiary
`
`of Amazon.com, Inc. in 2014, its case will not adequately represent the interests of other defend-
`
`ants. But this concern is not valid. First, no defendant has raised such a concern or requested that
`
`its case be designated as representative. Kongregate itself opposes PersonalWeb’s request. Sec-
`
`ond, PersonalWeb’s concern would not even be addressed by the Kongregate case. As Kongregate
`
`told PersonalWeb in July, it used Amazon S3 during the relevant time period and is therefore no
`
`different than any other indemnified Amazon customer sued by PersonalWeb. And to be clear,
`
`every current defendant (or its predecessor) was an Amazon S3 customer before the patents expired.
`
`Third, although Twitch became an Amazon subsidiary in 2014, it retained full control of its website
`
`and its design. Accordingly, the technology to be litigated in the Twitch case is Twitch’s own, and
`
`not one controlled by Amazon (outside of the implicated S3 functionality). Indeed, PersonalWeb
`
`alleges that Twitch’s purported infringement began in 2012, years before Amazon’s acquisition.
`
`Finally, Twitch, like Amazon and any other defendant, has a significant interest in defeating all of
`
`PersonalWeb’s claims under any theory and vindicating its business and technology.
`
`Accordingly, the Court should reject PersonalWeb’s proposal to have an unnecessary and
`
`duplicative case against Kongregate proceed along with the Twitch case and Amazon’s declaratory
`
`judgment action.
`
`AMAZON’S STATEMENT RE REPRESENTATIVE
`CASES
`
`
`
`1
`
`CASE NO.: 5:18-MD-02834-BLF
`CASE NO.: 5:18-cv-00767-BLF
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`

`

`Case 5:18-md-02834-BLF Document 309 Filed 11/09/18 Page 3 of 3
`
`
`
`Dated: November 9, 2018
`
`FENWICK & WEST LLP
`
`By: /s/ Saina S. Shamilov
`Saina S. Shamilov
`
`Counsel for
`AMAZON.COM, INC. and
`AMAZON WEB SERVICES, INC.
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`AMAZON’S STATEMENT RE REPRESENTATIVE
`CASES
`
`
`
`2
`
`CASE NO.: 5:18-MD-02834-BLF
`CASE NO.: 5:18-cv-00767-BLF
`
`

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