throbber
Case 5:18-md-02834-BLF Document 335 Filed 01/09/19 Page 1 of 3
`
`Michael A. Sherman (SBN 94783)
`masherman@stubb salderton. com
`Jeffrey F. Gersh (SBN 87124)
`j gersh@stubbsalderton. corn
`Sandeep Seth (SBN 195914)
`sseth@stubbsalderton. com
`Wesley W. Monroe (SBN 149211)
`wmonroe@stubbsalderton. com
`Stanley H. Thompson, Jr. (SBN 198825)
`sthompson@stubbsaldeft on. com
`Viviana Boero Hedrick (SBN 239359)
`vhedri ck@stubb s alderton. com
`STUBBS, ALDERTON & MARKILES, LLP
`15260 Ventura Blvd., 20th Floor
`Sherman Oaks, CA 91403
`Telephone: (818)444-4500
`Facsimile: (818) 444-4520
`
`Attorneys for Personal\üeb Technologieso LLC
`and Level3 Communications, LLC
`fAdditional Attorneys listed below]
`
`TINITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`SAN JOSE DIVISION
`
`IN RE PERSONALWEB TECHNOLOGIES,
`LLC, ET AL., PATENT LITIGATION
`
`CASE NO.: 5:18-md-02834-BLF
`
`AMAZON.COM, INC., et al.,
`
`Plaintiffs,
`
`V
`
`PERSONALWEB TECHNOLOGIES, LLC, Et
`&1.,
`
`PERSONALWEB TECHNOLOGIES, LLC
`and LEVEL 3 COMMUNICATIONS, LLC,
`
`Counterclaimants,
`
`V.
`
`Case No.: 5: 18-cv-007 67 -BLF
`DECLARATION OF KEVIN
`BERMEISTER IN SUPPORT OF
`PERSONALWEB TECHNOLOGIES, LLC
`AND LEVEL 3 COMMUNICATIONS,
`LLC'S OPPOSITION TO AMAZON.COM,
`INC. AND AMAZON WEB SERVICES,
`INC.'S MOTION FOR SUMMARY
`JUDGMENT ON DECLARATORY
`JUDGMENT CLAIMS AND DEFENSES
`UNDER THE CLAIM PRECLUSION AND
`KESSLER DOCTRINE
`
`Date:
`Time:
`Dept.:
`Judge
`
`February 7,2019
`2:00 PM
`Courtroom 3, 5th Floor
`Hon. Beth L. Freeman
`
`AMAZON.COM, INC. and AMAZON WEB
`SERVICES, INC.,
`
`Trial Date: March 16,2020
`
`Counterdefendants.
`
`1 2 J 4 5 6 7 8 9
`
`l0
`
`11
`
`T2
`
`13
`l4
`
`15
`
`T6
`
`t7
`
`18
`
`T9
`
`20
`2I
`
`22
`
`23
`
`24
`
`25
`
`26
`2l
`28
`
`DECLARATION OF KEVIN BERMEISTER
`ISO PWEB'S OPPOSITION TO AMAZON'S
`MSJ UNDER CP AND KESSLER DOCTRINE
`
`4417-92684420,V,
`
`'l
`
`CASE NO: 5: 18-md-02834-BLF'
`CASE NO: 5: 18-cv-00767-BLF
`
`

`

`Case 5:18-md-02834-BLF Document 335 Filed 01/09/19 Page 2 of 3
`
`I, Kevin Bermeister, declare as follows:
`l.
`declaration. I reside in Sydney, Australia, and have personal knowledge of the matters set fofth
`
`My name is Kevin Bermeister. I am over the age of l8 and competent to make this
`
`below. If called as a witness I would and could competently testify thereto.
`2.
`("PersonalWeb") and was so during litigation of PersonalWeb Technologies LLC and Level 3
`
`I am the Non-Executive Chairman of PersonalWeb Technologies, LLC
`
`Comntunications v. Amazon.cont, Inc, el al.,Case No. 6:11-cv-00658, in the Eastern District of
`
`Texas ("the Texas Action"). In that capacity I had the authority to make decisions for PersonalWeb
`
`in connection with the Texas Action.
`3.
`2018), I provided some background on the transactions and business activities associated with and
`
`In an earlier declaration I gave in this case (Docket number 37-1, dafed March 23,
`
`relating to the "True-Names" patent family for how data could be more efficiently transmitted over
`
`the Internet, as well as PersonalWeb's acquisition of the "True-Names" patent family in 201l.
`4.
`understood thatit only accused the Multipart Upload functionality of Amazon Web Service's Simple
`
`In initiating the Texas Action in late 2011 and throughout its prosecution, I
`
`Storage Service ("S3") system. I also had understood from publicly available materials that a
`
`content-based value called an ETag could be used during the Multipart Upload process to verify that
`
`a part did not get corrupted during the upload process and could be used to finalize the assembly of
`
`the uploaded parts into an object for storage and retrieval on 53. I was not aware at the time of the
`
`Texas Action that there were 33 website operator customers who were using ETags for an entirely
`
`different purpose of controlling browser caches by directing browsers to use conditional HTTP GET
`
`requests containing content-based ETags in order to instruct the browsers when they were authorized
`
`to reuse previously cached content or when they must get newly authorized content in rendering the
`
`website operator' s webpages.
`5.
`Texas Action PersonalWeb had accused Amazon of inf ingement through its Multipart Upload
`
`The Texas Action ended with a stipulation of dismissal in June, 2014. During the
`
`system. As the Texas Action progressed I learned that the economic activity associated with the
`
`Multipart Upload meant that the potential damages that could be obtained for patent infringement
`
`1 2 3 4 5 6 7 8 9
`
`10
`1l
`
`12
`
`13
`t4
`
`15
`
`t6
`l7
`l8
`
`19
`
`20
`
`21
`
`22
`
`ZJ
`
`24
`
`25
`
`26
`
`27
`
`28
`
`DECLARATION OF KEVIN BERMEISTER
`ISO PWEB'S OPPOSITION TO AMAZON'S
`MSJ UNDER CP AND KESSLER DOCTRINE
`
`CASE NO: 5: l8-md-02834-BLF
`CASE NO: 5: l8-cv-00767-BLF
`
`

`

`Case 5:18-md-02834-BLF Document 335 Filed 01/09/19 Page 3 of 3
`
`did not warrant the expense of trial. I made the business decision to agree to dismiss the existing
`inf ingemelrt claims for Multipart Upload. In making that business decision in no way did I concede
`
`that PersonalWeb was agreeing to or acknowledging (a) non-infringement of the Amazon Multipart
`
`Upload feature or non-infringement of any other aspect of any other featul'e associated with 53, or
`
`(b) invalidity of the subject patents.
`6.
`defendant with Amazon in the Texas Action, when I learned that Dropbox did not use Multipart
`
`I also made the business decision to dismiss Dropbox, Inc., originally named as a co-
`
`Upload.
`
`I declare under penalty of perjury under the laws of the United States of America that the
`
`foregoing is true and correct.
`
`Executed on January 9,2019 in Sydney, Australia.
`
`Bermeister
`
`1 2 aJ 4 5 6 7 8 9
`
`10
`
`11
`
`I2
`
`13
`l4
`
`15
`l6
`
`17
`
`18
`
`T9
`
`20
`2t
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`ISO P\ryEB'S OPPOSITION TO AMAZON'S
`MSJ UNDER CP AND KESSLER DOCTRINE
`
`CASE NOI5IiT-õI-ÕO7O7.NÍF
`
`

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