throbber
Case 3:20-cv-06754-WHA Document 447 Filed 01/12/23 Page 1 of 2
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES DISTRICT COURT
`
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`GOOGLE LLC,
`
`
`
`Plaintiff,
`
`v.
`
`SONOS, INC.,
`
`Defendant.
`
`
`
`
`No. C 20-06754 WHA
`
`
`
`ORDER GRANTING MOTION TO
`AMEND INFRINGEMENT
`CONTENTIONS
`
`Sonos has filed a motion for leave to amend its infringement contentions as to U.S.
`
`Patent No. 10,779,033 pursuant to Patent Local Rule 3-6 (Dkt. No. 407). Sonos asserts that the
`
`amendments are necessary because it discovered new information during the deposition of a
`
`Google 30(b)(6) witness on November 11, 2022 (Br. 2). Google opposes, arguing that Sonos
`
`is using the deposition as a Trojan horse to smuggle in a broad new theory. Google further
`
`argues that any amendment at this late stage would be prejudicial. This motion is suitable for
`
`resolution on the papers. Civ. L.R. 7-6.
`
`Patent Local Rule 3-6 states: “Amendment of the Infringement Contentions or the
`
`Invalidity Contentions may be made only by order of the Court upon a timely showing of good
`
`cause.” “[T]he primary question of good cause is a party’s diligence, and in considering the
`
`party’s diligence, the critical question is whether the party could have discovered the new
`
`information earlier had it acted with the requisite diligence.” Fluidigm Corp. v. IONpath, Inc.,
`
`2020 WL 5073938, at *4 (N.D. Cal. Aug. 25, 2020) (citation omitted).
`
`
`
`
`
`
`
`
`
`
`
`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
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:20-cv-06754-WHA Document 447 Filed 01/12/23 Page 2 of 2
`
`
`
`Upon review, Sonos has adequately shown diligence. Sonos served its first 30(b)(6)
`
`deposition notice seeking testimony on its “stream transfer” infringement theory for the ’033
`
`patent on January 5, 2022. Google first designated two different witnesses to testify on the
`
`subject, both of whom Sonos objected to as not competent. After Google declined to designate
`
`a third witness, Sonos moved to compel on October 14, 2022 (Dkt. No. 378). Before any
`
`ruling on the motion, however, Google designated a third witness, rendering the dispute moot.
`
`Sonos deposed that witness, Tavis Maclellan, on November 11, 2022. Sonos then filed the
`
`instant motion on the basis that Maclellan’s testimony had “confirmed” aspects of its
`
`infringement theory (Br. 2). This order finds that this sequence of events satisfies the diligence
`
`requirement.
`
`Google objects that Sonos could have articulated its new theory by investigating source
`
`code that Google had previously provided (Opp. 6). Sonos, however, is entitled to pursue
`
`discovery as to how that source code works. See, e.g., Delphix Corp. v. Actifio, Inc., No. C 13-
`
`04613, 2015 WL 5693722, at *3 (N.D. Cal. Sept. 29, 2015) (Judge Howard R. Lloyd). Google
`
`further objects that Sonos’s proposed amendments are overbroad because they belatedly add a
`
`“completely new theory of infringement” (Opp. 12 (citing Dkt. No. 406-2 at 84–85)). The
`
`amendments on those pages, however, simply cite to the new testimony and related source
`
`code. Any prejudice, then, is the result of Google’s failure to timely and appropriately respond
`
`to Sonos’s discovery request.
`
`In sum, Sonos has good cause to amend, and the motion is GRANTED. Any motion to
`
`modify the case schedule as a result of this order must be submitted within FIVE DAYS.
`
`IT IS SO ORDERED.
`
`Dated: January 12, 2023.
`
`
`
`
`
`
`
`WILLIAM ALSUP
`UNITED STATES DISTRICT JUDGE
`
`2
`
`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
`
`Northern District of California
`
`United States District Court
`
`

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