throbber
Case 3:20-cv-06754-WHA Document 382 Filed 10/18/22 Page 1 of 3
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES DISTRICT COURT
`
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`GOOGLE LLC,
`
`
`
`Plaintiff,
`
`v.
`
`SONOS, INC.,
`
`Defendant.
`
`
`
`
`No. C 20-06754 WHA
`
`
`ORDER ENTERING SUMMARY
`JUDGMENT IN FAVOR OF SONOS
`AS TO VALIDITY OF THE '885
`PATENT
`
`A July 2022 order granted Sonos’s motion for summary judgment of infringement of
`
`claim 1 of United States Patent No. 10,848,885 (Dkt. No. 309). That order also rejected
`
`Google’s arguments — made in both its opposition brief and its own patent showdown motion
`
`papers — that the claim was invalid. Specifically, that order rejected Google’s arguments that
`
`claim 1 of the ’885 patent covered unpatentable subject-matter under 35 U.S.C. § 101 and that
`
`the claim lacked written description support under 35 U.S.C. § 112. In light of that order,
`
`Google was ordered to show cause as to why summary judgment should not be entered in favor
`
`of Sonos on the issue of validity (Dkt. No. 339).
`
`Both parties have now responded (Dkt. Nos. 349, 351). In its response, Google
`
`abandoned the invalidity arguments it had made in its summary judgment briefing and instead
`
`shifted its focus to a bundle of new theories. In short, Google now asserts for the first time that
`
`the claim was obvious in light of Sonos prior art and online forum posts made by third-party
`
`users on Sonos’s website in 2005. Google additionally now asserts that there are material
`
`
`
`
`
`
`
`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 382 Filed 10/18/22 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
`
`issues of disputed fact as to whether third-party prior art speaker systems render the ’885
`
`patent invalid.
`
`The order to show cause, however, was not intended to provide Google a second bite at
`
`the apple. It would not have been allowed to spring new invalidity theories at trial and cannot
`
`do so now. Google objects that it should be allowed to pivot because its original “selection of
`
`arguments” relied on the construction for the term “zone scene” made by Judge Alan Albright
`
`in the Western District of Texas before this action was transferred here. Google therefore
`
`asserts that it should be allowed to recalibrate its arguments in conformance with the different
`
`construction made in the order on summary judgment (Br. 1–3).
`
`This argument does not hold water. First, Judge Albright’s oral claim construction
`
`rulings are not and were never the law of the case. See, e.g., Vazquez v. Jan-Pro Franchising
`
`Int’l, Inc., 923 F.3d 575, 586 (9th Cir. 2019), reh’g granted, opinion withdrawn on other
`
`grounds, 930 F.3d 1107 (9th Cir. 2019) (“Following a § 1404(a) transfer, the receiving court
`
`should treat pre-transfer rulings by the transferring court in much the same way as one district
`
`judge treats the ruling of a colleague.”). To the extent that Google relied on Judge Albright’s
`
`rulings, that reliance was misplaced.
`
`Second, the order on summary judgment adopted Judge Albright’s construction verbatim
`
`(see Dkt. No. 309 at 7). True, the order additionally found that the requirement that “zone
`
`scenes” must be formed “according to a common theme” could be satisfied by allowing users
`
`to name and save speaker groups. Judge Albright, however, expressly stated that his claim
`
`construction ruling would not preclude Sonos from arguing for that conclusion. See Google v.
`
`Sonos, No. C 6:20-00881-ADA (W.D. Tex. Aug. 10, 2021), Dkt. No. 106 at 37.
`
`Third, perhaps in recognition of the foregoing points, Google directly addressed in its
`
`summary judgment briefing the possibility that the “common theme” requirement can be
`
`satisfied by naming and saving speaker groups. See Dkt. No. 249 at 5–7. Google also
`
`addressed the issue at oral argument. This shows that Google was on notice that it had to put
`
`forth its best case.
`
`2
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:20-cv-06754-WHA Document 382 Filed 10/18/22 Page 3 of 3
`
`
`
`In sum, Google’s own filings repeatedly show that it was aware of the possibility that the
`
`“common theme” requirement could be satisfied by naming and saving speaker groups.
`
`Despite that awareness, Google chose to withhold certain theories addressing the issue. By
`
`way of explanation, Google laments that it “elected to focus its showdown papers on non-
`
`infringement and not on prior art invalidity” because of page limits (Br. 1). Google, however,
`
`made the strategic choice to raise invalidity in its summary judgment papers, which then forced
`
`Sonos to address it for the first time in a fifteen-page reply brief. Google cannot readjust its
`
`sails now that it knows which way the judicial winds are blowing. Those theories are therefore
`
`waived. See Pandrol USA, LP v. Airboss Ry. Prods., Inc., 320 F.3d 1354, 1366 (Fed. Cir.
`
`2003).
`
`Google’s response does not otherwise alter the conclusions made in the order on
`
`summary judgment. Accordingly, summary judgment is GRANTED in favor of Sonos on the
`
`issue of validity of the ’885 patent. See FRCP 56(f); Gonzales v. CarMax Auto Superstores,
`
`LLC, 840 F.3d 644, 654–55 (9th Cir. 2016).
`
`IT IS SO ORDERED.
`
`Dated: October 18, 2022.
`
`
`
`
`
`
`
`WILLIAM ALSUP
`UNITED STATES DISTRICT JUDGE
`
`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
`
`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