Federal Circuit Affirms Summary Judgment of Non-Infringement for Sonos in Google Patent Case

The U.S. Court of Appeals for the Federal Circuit (CAFC) issued a decision Friday in Google LLC v. Sonos, Inc., affirming a summary judgment of non-infringement entered by the U.S. District Court for the Northern District of California. The CAFC agreed with the district court’s constructions of the claim terms “utilized” and “private key,” each of which resolved one of Google’s two infringement theories.

Google filed a lawsuit against Sonos for infringement of U.S. Patent No. 7,899,187, titled “Domain-Based Digital-Rights Management System with Easy and Secure Device Enrollment.” The patent describes a system that manages a domain of devices associated with an account, where devices inside the domain share protected content using a private cryptographic key and devices outside the domain cannot obtain the content in unencrypted form. Google asserted independent claims 1 and 10, which require a private key based on domain information that is “utilized by all devices within the domain of devices.”

Sonos manufactures smart speakers that customers group into a household through the Sonos application, called the Controller. Within a group, only one player receives an encrypted music stream and uses a unique private key to decrypt it before sending the content to the other members for playback. A new player joining a household receives an authorization token from an existing player and presents it to the streaming service to authenticate itself. Google and Sonos agreed that Sonos players never use the token as the key input to a cryptographic algorithm.

Under the Strong-Encryption Theory, Google asserted that every device in a household “utilizes” the private key when a single device decrypts content with it and distributes the result. Under the Authentication Theory, Google contended that the authorization token satisfied the “private key” limitation since the token is an input to a cryptographic algorithm. Judge Edward M. Chen of the district court determined that a device does not “utilize” a private key merely by receiving content that another device has decrypted. He also construed “private key” to require a key input, rather than solely a data input, to a cryptographic algorithm. Based on these constructions, the court granted Sonos summary judgment of non-infringement on each theory. Since the constructions of “utilized” and “private key” were dispositive, the CAFC did not address Google’s arguments about its expert’s possible concession or the “based on” limitation.

Google framed the issue as whether Sonos players must use the private key directly or may use it indirectly when one player decrypts content and forwards it. Sonos argued for direct use, and the CAFC agreed. Google emphasized claim language directed to using the private key to access protected content, but that language addresses only the key’s general purpose, and the claim contains additional limitations, including use of the key by all devices in the domain. According to the specification, utilizing a private key means inputting it into a cryptographic algorithm to decrypt data, and the intrinsic evidence offered no persuasive support for Google’s broader reading. The Federal Circuit held that, “we find only evidence that supports the idea that a person of ordinary skill in the art would understand that to ‘utilize’ a private key is to decrypt with it.”

Google’s claim differentiation argument based on claim 6, which adds a step of using the private key to decrypt a second encryption key, did not alter that result since claims 1 and 6 each require utilization of the private key by all devices in the domain. Sonos’s argument against ambiguity in Google’s proposed reading was persuasive to the CAFC since Google offered no limiting principle for when indirect use becomes too attenuated. The CAFC cited its rule that “constructions that are more likely to result in an indefinite claim should be avoided.” Since Google and Sonos agreed that every player other than the one performing the decryption uses the key only indirectly, the CAFC adopted Sonos’s construction and found no genuine issue of material fact on the Strong-Encryption Theory.

On the Authentication Theory, Google argued that the district court’s original construction, which required only that the private key be an input to a cryptographic algorithm, was correct and sufficient. Sonos noted that cryptographic algorithms generally require a key input and a data input, and the CAFC observed that Google’s construction could create a fact issue by permitting infringement whenever the private key is used as any input. The CAFC again agreed with Sonos that the term requires a key input rather than any input.

Since “utilized” requires actual decryption with the key, the private key is separate from the data it processes, and the intrinsic record reflects that separation throughout. The specification describes the private key as used to decrypt data, generate digital signatures, and decrypt the content encryption key. In the specification’s three examples of a key, the key controls an algorithmic operation, and claim 6 uses the private key to decrypt an encrypted second encryption key. Extrinsic evidence from Sonos showed that cryptography distinguishes a key from other data by its role in acting upon data.

The CAFC held that a person of ordinary skill in the art would understand the claimed private key “to necessarily be a key input to a cryptographic algorithm” when viewed in the context of the claim language and the specification. Ultimately, the CAFC rejected Google’s remaining arguments and affirmed the district court’s grant of summary judgment of non-infringement to Sonos on the Strong-Encryption Theory and the Authentication Theory.