PTAB
Advanced fields
1 decision · 281msnewest first
  • PTAB · 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 unpatentable
    Claim construction§ 101 eligibilitycites Alice · Mayo · Enfish
    Patents 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.