{"id":3861,"date":"2024-06-03T11:35:29","date_gmt":"2024-06-03T16:35:29","guid":{"rendered":"https:\/\/patents.harnessip.com\/?p=3861"},"modified":"2024-07-09T07:12:30","modified_gmt":"2024-07-09T12:12:30","slug":"googles-products-infringe-because-they-do-what-googles-website-said-they-do","status":"publish","type":"post","link":"https:\/\/patents.harnessip.com\/?p=3861","title":{"rendered":"Google’s Products Infringe Because They Do What Google’s Website Said They Do"},"content":{"rendered":"\n

In Ecofactor, Inc. v. Google LLC<\/a>, [2023-1101] (June 3, 2023), the Federal Circuit affirmed the the denial of Google\u2019s motion for summary judgment that claim 5 of U.S. Patent No. 8,738,327 was invalid under 35 U.S.C. \u00a7 101; the denial of Google\u2019s motion for judgment
as a matter of law of non-infringement of the \u2019327 patent; and the denial of Google\u2019s motion for a new trial on damages.<\/p>\n\n\n\n

The ‘327 patent relates to the operation of smart thermostats in computer networked
heating and cooling systems to reduce strain on the electricity grid during a period of expected high demand through adjustments to the user\u2019s thermostat settings. The district court denied Google’s motion for summary judgment on Section 101, and submitted step two of the Alice inquiry to the jury, which found Google failed to meet its burden. Google filed a post-trial JMOL motion repeating its \u00a7 101 arguments, which the district court denied.<\/p>\n\n\n\n

Google appealed the order denying summary judgment but not the jury verdict of ineligibility. The Federal Circuit said that the denial of Google’s motion for Summary Judgment was not appealable, disposing of the eligibility issue.<\/p>\n\n\n\n

On the issue of infringement, the claims required a thermostat \u201cthat receives temperature
measurements from inside the structure.\u201d Google argues that because metal, plastic, and\/or glass housings, they cannot directly measure the surrounding ambient temperature \u201cinside the structure\u201d like other thermostats. Google argues that its thermostats can only derive an estimate of the ambient temperature by measuring only the temperature within the thermostat housing itself, which is not \u201cinside the structure.\u201d As a result, Google argues that the jury\u2019s verdict of infringement is unsupported by substantial evidence.<\/p>\n\n\n\n

EcoFactor\u2019s infringement expert testified that the accused thermostat products meet
the claimed limitation because the thermostats measured temperature of the structure and not just the temperature within the thermostat housing. 26:20\u2013327:6). EcoFactor\u2019s expert supported his conclusion with several forms of evidence. EcoFactor\u2019s expert relied on website guides maintained Google for the benefit of software engineers who develop applications for use with Nest thermostats. One website page states that the Nest thermostats measure the \u201c[a]mbient temperature,\u201d defined as the \u201ctemperature measured near the thermostat\u201d\u2014not just within the thermostat. Another website page explains that the temperature sensors of certain Nest products measure ambient room temperature.<\/p>\n\n\n\n

The Federal Circuit concluded that the jury\u2019s infringement verdict that the accused Nest thermostat products satisfy the claim language of \u201creceives temperature measurements from inside the structure\u201d is supported by substantial evidence.<\/p>\n\n\n\n

On the issue of damages, Google argued for a new trial because EcocFactor’s damages expert should have been excluded. Among other things, Google asserted that his proposed royalty rate was “plucked . . .out of no where.” However the Federal Circuit said that far from plucking the $X royalty rate from nowhere, Mr. Kennedy based this rate on the following admissible evidence: three license agreements and the testimony of
EcoFactor\u2019s CEO, Mr. Habib. Ultimately, the Federal Circuit noted, the jury returned a verdict of $20,019,300, which represents significantly less than Mr. Kennedy\u2019s proposed damages amount of $Y that would have resulted from applying the $X royalty rate to Google\u2019s past sales.<\/p>\n\n\n\n

Google also attacked the lack of apportionment, since the licenses relied upon were for EcoFactor’s entire patent portfolio. The Federal Circuit explained that damages owed to the patentee must reflect the value of only the patented improvement\u2014called apportionment. If a sufficiently comparable license is used for determining the appropriate reasonable royalty rate, further apportionment may not be required because the comparable license has built-in apportionment. Built-in apportionment effectively assumes that the negotiators of a comparable license settled on a royalty rate and royalty base combination embodying the value of the asserted patent.\u201d Id. (citation omitted). For built-in apportionment to apply, the license must be sufficiently comparable in that principles of apportionment were effectively
baked into the purportedly comparable license. The Federal Circuit found that Mr. Kennedy sufficiently showed, for purposes of admissibility, that the three license agreements were economically comparable to the hypothetically negotiated agreement.<\/p>\n\n\n\n

Judge Prost dissented from the damages portion of the opinion, stating that Google argues that (1) Mr. Kennedy, EcoFactor\u2019s damages expert, calculated an $X royalty rate2 from the Schneider, Daikin, and Johnson lump-sum licenses in an unreliable way; and (2) the $X rate in any event did not reflect the value of the \u2019327 patent (as distinct from that of other patents covered by those licenses). Google is right on both counts. The district court therefore, in my view, abused its discretion by not granting a new damages trial given Mr. Kennedy\u2019s flawed testimony.<\/p>\n\n\n\n

    <\/ol>\n\n\n\n


    <\/p>\n","protected":false},"excerpt":{"rendered":"

    In Ecofactor, Inc. v. Google LLC, [2023-1101] (June 3, 2023), the Federal Circuit affirmed the the denial of Google\u2019s motion for summary judgment that claim 5 of U.S. Patent No. 8,738,327 was invalid under 35 U.S.C. \u00a7 101; the denial … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3861","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3861"}],"version-history":[{"count":2,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3861\/revisions"}],"predecessor-version":[{"id":3863,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3861\/revisions\/3863"}],"wp:attachment":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}