throbber
RESTRICTED – CONFIDENTIAL SOURCE CODE
`
`UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`ECOFACTOR, INC.,
`
`Civil Action No. 6:20-cv-00075 (ADA)
`
`Plaintiff,
`
`JURY TRIAL DEMANDED
`
`v.
`GOOGLE LLC,
`
`Defendant.
`
`REBUTTAL EXPERT REPORT OF DR. DON TURNBULL REGARDING THE NON-
`INFRINGEMENT OF U.S. PATENT NOS. 8,412,488, 8,738,327 AND 10,534,382
`
`Dated: October 22, 2021
`
`___________________________________
`Don Turnbull, Ph.D.
`
`GOOGLE 1028
`
`

`

`
`
`RESTRICTED – CONFIDENTIAL SOURCE CODE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`XI.
`
`THE ACCUSED PRODUCTS DO NOT PRACTICE ANY OF THE ASSERTED
`CLAIMS OF THE ’382 PATENT
`335.
`I am of the opinion that Google does not directly or indirectly infringe the ’382
`Patent and that Google’s Nest Thermostat, Nest Thermostat E, and Nest Learning Thermostat
`Third Generation do not practice the asserted claims of the ’382 Patent.
`336.
`I understand that EcoFactor accuses the Home/Away features of Google’s Nest
`Thermostat, Nest Thermostat E, and Nest Learning Thermostat Third Generation devices of
`infringing the asserted claims.
`A.
`Claim 1
`1.
`Claim element 1[b]: “one or more processors with circuitry and code
`designed to execute instructions”
`337. As EcoFactor conceded in its August 16, 2021 Patent Owner’s Response, the “one
`or more processors with circuitry and code designed to execute instructions” required by claim
`element 1[b] must include at least a single processor that meets all of the limitations of the ’382
`
`108
`
`

`

`
`
`RESTRICTED – CONFIDENTIAL SOURCE CODE
`
`Patent. See August 16, 2021 Patent Owner’s Response (IPR2021-00054) at 13 (“all of the ‘one
`or more processors’ must be able to perform the functions recited in claim elements [1d], [1e],
`[1f], [1g], [1i], [1k], and [1l]. That is, there needs to be at least a single processor that meets all
`of the limitations of claim elements [1d], [1e], [1f], [1g], [1i], [1k], and [1l]. Put another way, if a
`processor only met the limitations of claim elements [1d] and [1f], it would not meet the full
`limitations [sic] of claim 1.”); Id. at 17 (“More troublesome is that the Petition provides no
`mapping of the specific ‘embodiment’ of memory or processors in Gaedelmann and Ehlers that
`meets the claim limitations of the ’382 patent. Instead, [i]t mixes and matches different
`processors, often asserting that two or three processors meet a particular claim limitation.”).
`338. Each of the claim elements that reference “one or more processors with circuitry
`and code designed to execute instructions” specifically refer to “the one or more processors with
`circuitry and code.” See ’382 Patent at 8:17-62. As EcoFactor concedes, a POSITA looking at
`this claim language would recognize that “the one or more processors with circuitry and code
`designed to execute instructions” referenced in the claim limitations refers to the same “one or
`more processors.”
`339. None of the processors identified in Mr. de la Iglesia’s Infringement Report
`perform all the limitations of the ’382 Patent claims that reference “the one or more processors
`with circuitry and code” throughout Claim 1. For example,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`109
`
`

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