- PTAB · Apr 7, 2022 · PGR2021-00042 · APJ Sheridan K Snedden · PGR · Rehearing
The Board granted rehearing, reversed its discretionary denial, and instituted PGR on claims 6–8 based on the threshold showing of likely lack of enablement and anticipation.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“We agree with Petitioner that a rehearing of our prior decision to deny institution is appropriate due to the changed circumstances of claims 6–8 of” slip op. at 6
- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner
“institution is appropriate due to the changed circumstances of claims 6–8 of” slip op. at 6
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“35 U.S.C. § 324(a) provides that a post-grant review may not be instituted “unless the Director determines that the information presented in the petition filed under section 321, if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” After considering the Petition and the Preliminary Response, and the evidence cited therein, we determine that Petitioner has shown that it is more likely than not that at least one of the claims challenged in the Petition is unpatentable. Therefore, we grant institution of a post-grant review.” slip op. at 3
- Skill levelSkill level petitioner adoptedDecided for petitioner
“For purposes of this Decision, we accept Petitioner’s proposed definition, which is supported by Dr. Lambert’s testimony (Ex. 1002 ¶ 20) and is consistent with the scope and content of the ’039 patent and the asserted prior art.” slip op. at 17
Claim construction§ 102 anticipation§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 10,808,039 - PTAB · Apr 7, 2022 · PGR2021-00030 · APJ Sheridan K Snedden · PGR · Rehearing
Granted Petitioner’s rehearing request and instituted PGR on claims 1–5, 9, and 10 based on the more-likely-than-not enablement showing and efficiency considerations.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“As acknowledged by both Petitioner and Patent Owner, this proceeding and PGR2021-00042 involve essentially identical issues. See 6 Reh’g Req. 15; Prelim. Resp. 19 n.3. In particular, we note that claims 6–8 of the ’039 patent challenged in PGR2021-00042 depend from claim 1 of the ’039 patent challenged in this proceeding, and are challenged under essentially identical written description, enablement and prior art issues. Reh’g Req. 15. Thus, our decision to institute post-grant review in PGR2021-00042 effectuates our review of issues almost identical to those in this proceeding. Petitioner further argues that this proceeding and PGR2021-00042 involve related issues, and that “considerations of efficiency . . . therefore counsel in favor of the Board reviewing the patentability of claims 1–5, 9, and 10 of the ’039 patent as well.” Id. We agree with Petitioner that, because we are to review practically the same issues of this proceeding in PGR2021-00042, considerations of efficiency (i.e., efficient use of the Board’s resources) strongly weigh in favor of also instituting trial in this proceeding. See Reh’g Req. 15. Considering all the factors together as a whole, we determine that, under the particular circumstances of this case, the interests of efficiency and integrity of the patent system weigh against exercising discretionary denial under § 324(a). Accordingly, we grant Petitioner’s Request for Rehearing and decline to exercise our discretion to deny institution. We consider the merits of the Petition with respect to the threshold for institution below.” slip op. at 6
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“3. Analysis “[T]o be enabling, the specification of a patent must teach those skilled in the art how to make and use the full scope of the claimed invention without ‘undue experimentation.’” Genentech Inc. v. Novo Nordisk A/S, 108 F.3d 1361, 1365 (Fed. Cir. 1997) (quoting In re Wright, 999 F.2d 1557, 1561 (Fed. Cir. 1993)) (alteration in original). “The enablement requirement ensures that the public knowledge is enriched by the patent specification to a degree at least commensurate with the scope of the claims. The scope of the claims must be less than or equal to the scope of the enablement. The scope of enablement, in turn, is that which is disclosed in the specification plus the scope of what would be known to one of ordinary skill in the art without undue experimentation.” National Recovery Techs. Inc. v. Magnetic Separation Sys., Inc., 166 F.3d 1190, 1195–96 (Fed Cir. 1999). [Although] a specification need not disclose what is well known in the art . . . , that general, oft-repeated statement is merely a rule 24 of supplementation, not a substitute for a basic enabling disclosure. . . . [W]hen there is no disclosure of any specific starting material or of any of the conditions under which a process can be carried out, undue experimentation is required; there is a failure to meet the enablement requirement that cannot be rectified by asserting that all the disclosure related to the process is within the skill of the art. It is the specification, not the knowledge of one skilled in the art, that must supply the novel aspects of an invention in order to constitute adequate enablement. Genentech Inc., 108 F.3d at 1366. Having considered the parties’ positions and evidence of record, summarized above, we determine that Petitioner has established that it is more likely than not that claims 1–5, 9, and 10 of the ’039 patent lack enablement. In particular, we are persuaded based on the record at this stage of the proceeding that the Specification does not enable the full scope of the claims. The Specification focuses on dolastatin/auristatin derivatives and does not describe novel ADCs having non-dolastatin/auristatin derivative drug moieties. Ex. 1001, Abstract. For example, the Specification states that “there is a clear need in the art for dolastatin/auristatin derivatives having significantly lower toxicity, yet useful therapeutic efficiency [sic]” and purports that “[t]hese and other limitations and problems of the past are addressed by the present invention.” Id. at 4:25–29 (emphasis added). Moreover, each embodiment, example, figure, and assay disclosed in the Specification appears to use a drug moiety that is a dolastatin/auristatin derivative. See, e.g., Ex. 1001, Abstract, 4:22–29, 50:56–52:30, 71:19–22, 131:23–48, Figs. 1–19, Examples 2–16. Claim 1, however, recites ADCs” slip op. at 24
- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Denied
“As acknowledged by both Petitioner and Patent Owner, this proceeding and PGR2021-00042 involve essentially identical issues. See 6 Reh’g Req. 15; Prelim. Resp. 19 n.3. In particular, we note that claims 6–8 of the ’039 patent challenged in PGR2021-00042 depend from claim 1 of the ’039 patent challenged in this proceeding, and are challenged under essentially identical written description, enablement and prior art issues. Reh’g Req. 15. Thus, our decision to institute post-grant review in PGR2021-00042 effectuates our review of issues almost identical to those in this proceeding. Petitioner further argues that this proceeding and PGR2021-00042 involve related issues, and that “considerations of efficiency . . . therefore counsel in favor of the Board reviewing the patentability of claims 1–5, 9, and 10 of the ’039 patent as well.” Id. We agree with Petitioner that, because we are to review practically the same issues of this proceeding in PGR2021-00042, considerations of efficiency (i.e., efficient use of the Board’s resources) strongly weigh in favor of also instituting trial in this proceeding. See Reh’g Req. 15. Considering all the factors together as a whole, we determine that, under the particular circumstances of this case, the interests of efficiency and integrity of the patent system weigh against exercising discretionary denial under § 324(a). Accordingly, we grant Petitioner’s Request for Rehearing and decline to exercise our discretion to deny institution. We consider the merits of the Petition with respect to the threshold for institution below.” slip op. at 6
- Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Instituted
“skilled in the art how to make and use the full scope of the claimed invention without ‘undue experimentation.’” Genentech Inc. v. Novo Nordisk A/S, 108 F.3d 1361, 1365 (Fed. Cir. 1997) (quoting In re Wright, 999 F.2d 1557, 1561 (Fed. Cir. 1993)) (alteration in original). “The enablement requirement ensures that the public knowledge is enriched by the patent specification to a degree at least commensurate with the scope of the claims. The scope of the claims must be less than or equal to the scope of the enablement. The scope of enablement, in turn, is that which is disclosed in the specification plus the scope of what would be known to one of ordinary skill in the art without undue experimentation.” National Recovery Techs. Inc. v. Magnetic Separation Sys., Inc., 166 F.3d 1190, 1195–96 (Fed Cir. 1999). [Although] a specification need not disclose what is well known in the art . . . , that general, oft-repeated statement is merely a rule 24 of supplementation, not a substitute for a basic enabling disclosure. . . . [W]hen there is no disclosure of any specific starting material or of any of the conditions under which a process can be carried out, undue experimentation is required; there is a failure to meet the enablement requirement that cannot be rectified by asserting that all the disclosure related to the process is within the skill of the art. It is the specification, not the knowledge of one skilled in the art, that must supply the novel aspects of an invention in order to constitute adequate enablement. Genentech Inc., 108 F.3d at 1366.” slip op. at 24
Claim construction§ 102 anticipation§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 10,808,039 - Autodesk, Inc. v. Uniloc USA, Inc. And Uniloc Luxembourg, S.A.All claims unpatentablePTAB · Sep 11, 2017 · CBM2016-00043 · APJ Christopher M Kaiser · CBM · Final written decision
Claims 1, 2, 4–7, and 12–19 are unpatentable under § 101; claims 3, 8–11, and 20 are subject to adverse judgment after disclaimer.
RulingsFinal written decision- Adverse judgmentAdverse judgmentGranted
“B. Statutory Disclaimer During the pendency of this proceeding, Patent Owner filed a disclaimer pursuant to 35 U.S.C. § 253(a) and 37 C.F.R. § 1.321(a). Ex. 2014. According to this disclaimer, Patent Owner disclaims claims 3, 8–11, and 20 of the ’820 patent. Id.; see also Resp. 1 (“Contemporaneously with the filing of this Response, Patent Owner is disclaiming claims 3, 8, 9, 10, 11, and 20 of the ’820 Patent.”). Our rules provide for entry of adverse judgment against a Patent Owner who disclaims “a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). Although Patent Owner does not disclaim all the challenged claims, and although Patent Owner therefore has some claims remaining in this trial, we construe the disclaimer of claims 3, 8–11, and 20 as a request for the entry of adverse judgment solely with respect to those claims. We grant the request and enter adverse judgment with respect to claims 3, 8–11, and 20.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed patent owner constructionDecided for patent owner
“1. Add-On Computer Software Code Both parties propose construing “add-on computer software code,” a term that appears in every challenged claim. Ex. 1001, 78:43–82:36. Petitioner argues that this term should be interpreted as a “set of computer code that cannot be run independently from a parent program.” Pet. 22. Patent Owner argues that the term should be interpreted as “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.” Resp. 42–43. We agree with Patent Owner. Patent Owner’s construction is taken directly from the written description of the ’820 patent, which provides a reasonably clear, deliberate, and precise definition of the term. See Paulsen, 30 F.3d at 1480; Ex. 1001, 61:42–51 (“The plug-in (add-on) computer software code is . . . .”). To the extent that Petitioner’s proposed construction seeks to limit add-on software code further by requiring that the software code be incapable of running independently from a parent program, as opposed merely to being designed to run within the parent program as an internal component, this further limitation is inconsistent with the lexicography undertaken by the patentee of the ’820 patent. Accordingly, we construe “add-on computer software code” as a “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.”” slip op. at 6
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“As discussed above, the ’820 patent describes solving problems with the generation of cost estimates of construction projects, including that the process takes significant time and effort, that the estimates produced are difficult to revise, and that the estimates can be inaccurate, leading to cost overruns and difficulties obtaining construction loans. Ex. 1001, 1:15–62. The claims recite a computer readable medium or system for automating the process of generating a price schedule, which is used to develop the overall project cost estimate. Id. at 78:43–82:36. In so doing, the claims do not recite any “specific asserted improvement in computer capabilities,” such as the “self-referential table for a computer database” in Enfish, 822 F.3d at 1336. Instead, the claims of the ’820 patent “invoke[]” known aspects of computer technology, including “[a] non-transitory computer readable medium,” “a computer that includes a processor and a memory,” “an add-on computer software code,” “a software design tool,” and “a database,” “merely as a tool” for solving the problem of improving the known process of generating construction project cost estimates. Id.; Ex. 1001, 78:43–60. Accordingly, the claims of the ’820 patent are not like those considered in Enfish, where the claims were determined at the first step of the Alice framework not to be directed to abstract ideas because they were directed to “[a] specific asserted improvement in computer capabilities.” 822 F.3d at 1336. Instead, Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent are focused “on a process that qualifies as an ‘abstract idea.’” Id. The ’820 patent makes clear that the heart of the claimed subject matter is generating prices for construction projects, a process that can be accomplished without automation technology. Ex. 1001, 1:15–62. The claims themselves recite “[a] non-transitory computer readable medium [that] causes [a] computer to generate a price schedule” and “[a] system for creating a pricing schedule.” Id. at 78:43–51, 82:4. As discussed above, the computer technology recited in the claims is used merely as a tool to automate the process of determining the price of a construction project. Determining a price is an abstract idea. See Versata Dev. Grp., 793 F.3d at 1333–34 (Fed. Cir. 2015). Thus, on the current record, Petitioner has made a sufficient showing that the claims of the ’820 patent are directed to an abstract idea under the first step of the Alice analysis.” slip op. at 20
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“application of an abstract idea. Mayo, 566 U.S. at 78. Petitioner argues that the challenged claims have no such elements, because “the challenged claims add nothing more than well-understood, routine, conventional activity to the abstract idea of calculating a price.” Pet. 32–48. Patent Owner argues that the presence of the add-on computer software code limitations in the challenged claims transforms those claims into patent-eligible applications. Resp. 49–50. We are persuaded that Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent do not add an inventive concept sufficient to ensure that the patent in practice amounts to significantly more than a patent on the abstract idea itself. Alice, 134 S. Ct. at 2355.” slip op. at 23
Patent outcomesUS 8,515,820 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · EnfishPatents in suitUS 8,515,820
Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.