- American Express Company / American Express Travel Related Services Company, Inc. v. Signature Systems, LLCAll claims unpatentablePTAB · Oct 30, 2019 · CBM2018-00035 · APJ Frances L Ippolito · CBM · Final written decision
Claims 1, 2, 5, 6, 9, 10, 13, and 14 are unpatentable under § 101; proposed substitute claims 17–20 are unpatentable under § 101, and the contingent motion to amend is denied.
RulingsFinal written decision- Skill levelOther
“F. Level of Skill in the Art Petitioner asserts that a person of ordinary skill in the art (“POSITA”)” slip op. at 32
- Expert testimonyOther
“For the above reasons, we are persuaded that Petitioner has met its” slip op. at 62
- Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Decided for petitioner
“1. Principles of Law Use of the word “means” in a claim gives rise to a rebuttable” slip op. at 12
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied
“Further, based on the entirety of the record, we determine that proposed substitute claims 17–20 are unpatentable by a preponderance of the evidence based on 35 U.S.C. § 101. Motion to Amend Outcome Claims Substitute Claims: Proposed in the Amendment 17–20 Substitute Claims: Motion to Amend Denied 17–20” slip op. at 101
Patent outcomesUS 8,423,402 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · Bilski · Berkheimer · EnfishPatents in suitUS 8,423,402 - 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 - The Kroger Company / Brookshire Grocery Company v. Nexuscard, Inc.All claims unpatentablePTAB · Mar 27, 2017 · CBM2015-00183 · APJ Minn Chung · CBM · Final written decision
Claims 1–11 are unpatentable under § 101 because they claim the abstract idea of collecting, storing, and processing membership discount information without an inventive concept.
RulingsFinal written decision- Burden
“Upon considering all of the evidence of record, we are persuaded Petitioner has demonstrated by a preponderance of evidence that claims 1 and 11 fail to recite any elements that individually or as an ordered combination transform the claimed abstract idea into a patent-eligible application.” slip op. at 34
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesOther
“communication means” Claimed Function: “providing real time (1, 8, 11) 2, 3 communication between [a point of purchase] member merchant’s computer terminal and [a centralized] provider’s computer” Corresponding Structure: a cash register with a communication capability, a credit card verification machine, a terminal, or a scanner, and equivalents “memory storage means” Claimed Function: “containing at least . . . (1, 11) consumer identification code” Corresponding Structure: a magnetic stripe on a card, and equivalents slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“real time “communication without intentional delay, communication” (1, 7, 11) given the processing limitations of the system and the time required to effect the communication” See Dec. on Inst. 8–11. The parties do not dispute these interpretations in their Patent Owner Response and Reply. For this Final Written Decision, after considering the complete record, we see no reason to deviate from those constructions and, therefore, maintain our constructions as set forth above. slip op. at 9
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“Under the approach described in Alice and further explained in Enfish, Internet Patents, and Electric Power Group, we are persuaded by Petitioner’s argument and evidence that claims 1 and 11 are directed to an abstract idea. As discussed above, Petitioner has shown that the claims recite a process to “collect, store, and process information about consumer memberships, merchants, manufacturers, and sales transactions” (Pet. 34), a process that qualifies as an “abstract idea” (id. at 71) of “conventional information processing” in the retail industry (id. at 72), for which conventional components, such as a magnetic stripe scanner, computers, and databases, are merely invoked as tools used in their ordinary and conventional manner (Pet. Reply 8–11). In Electric Power Group, the Federal Circuit explained that the “the realm of abstract ideas” includes “collecting information, including when limited to particular content.” Elec. Power Grp., 830 F.3d at 1353. The court determined, therefore, that the claims at issue were directed to an abstract idea because “the focus of the asserted claims” is “on collecting information, analyzing it, and displaying certain results of the collection and analysis.” Id. We are persuaded that claims 1 and 11 in this case are similarly directed to an abstract idea because Petitioner’s argument and evidence shows that the focus of the claims, the claims’ “character as a whole,” is on conventional information processing in the context of membership discount programs that use generic computers and conventional devices as tools to provide discounts without coupons.” slip op. at 18
Patent outcomesUS 5,924,080 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · Bilski · Enfish · Electric PowerPatents in suitUS 5,924,080 - NRT Technology Corp. / NRT Technologies, Inc. v. Everi Payments, Inc.Institution deniedPTAB · Jan 22, 2016 · CBM2015-00167 · APJ Michael J Fitzpatrick · CBM · Institution
The Board denied institution because Petitioner did not show any challenged claim was more likely than not unpatentable under § 101, Akel, or grounds relying on Reeder.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“We may not institute a CBM patent review “unless the Director[2] determines that the information presented in the petition . . . would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a).3 Based on our review of the record, we conclude that Petitioner is less likely than not to prevail with respect to all of the challenged claims. Accordingly, we deny the Petition to institute a CBM patent review, as set forth below.” slip op. at 2
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable
“As Patent Owner points out, Petitioner has oversimplified the challenged claims. Prelim. Resp. 31. The challenged claims are not directed simply to the idea of providing money to an account holder or using trial-and-error until success is achieved. Rather, the claims are directed to particular methods of providing money to an account holder using an ATM via a POS transaction after an ATM transaction has failed. See Alice, 134 S. Ct. at 2354 (“Applications of such concepts to a new and useful end . . . remain eligible for patent protection.”) (internal quotation marks and brackets omitted). Further, Petitioner’s analysis omits any consideration of the elements of the claims as ordered combinations to determine whether the additional elements transform the nature of the claims into a patent-eligible application. It was Petitioner’s burden to do so. Petitioner has not shown that the claims are more likely than not patent-ineligible. Alice, 134 S. Ct. at 2354 (“an invention is not rendered ineligible for patent simply because it involves an abstract concept”).” slip op. at 11
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“It is a petitioner’s burden to explain how a challenged claim should be construed and how, being so construed, it is unpatentable. 37 C.F.R. § 42.204(b)(3)–(4). Petitioner does not propose an express construction for “personal identification number” and does not show that its plain and ordinary meaning would include a password. Further, claim 1 requires entering a PIN into the terminal. In the context of the specification and surrounding claim language, this step is part of the claimed “method of providing money or an item of value to an account-holder.” The teaching on which Petitioner relies, however, relates to a system operator’s back-end access of the Akel system. See Ex. 1006, 6:58–62 (“Each system operator requires a password to access the system . . . .”) (emphasis added). Elsewhere, Akel describes a “customer” (distinct from a system operator) as using a kiosk to obtain cash. Id. at 2:56–3:11. But, Akel does not describe entering a password into a terminal, let alone a PIN, as part of that process. Thus, even if Akel’s password fell within the scope of the recited PIN, the Petition would still fail to show how its use by an operator “to access the system” (see Ex. 1006, 258–60) meets the recited “entering a personal identification number into the terminal” as part of the claimed “method of providing money or an item of value to an account-holder.” Petitioner has not shown that Akel teaches “entering a personal identification number into the terminal.” Accordingly, Petitioner has not shown that claim 1, or dependent claims 2–8, are more likely than not anticipated by Akel.” slip op. at 13
- Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artNot shown unpatentable
“The invention date of the ’792 patent is no later than its filing date, which is January 5, 1998. Although the Reeder application was filed, and thus privately known to Mr. Reeder, before the ’792 filing date, such private knowledge is not within the scope of § 102(a). See, e.g., Carella v. Starlight Archery & Pro Line Co., 804 F.2d 135, 139 (Fed. Cir. 1986) (“The statutory language, ‘known or used by others in this country’ (35 U.S.C. § 102(a)), means knowledge or use which is accessible to the public.”). Reeder was 8 The AIA took effect on March 18, 2013. Because the application from which the ’792 patent issued was filed before that date, our citations to 35 U.S.C. § 102 are to its pre-AIA version. eventually patented of course but not until after the filing date of the ’792 patent. For these reasons, Reeder is not prior art under 35 U.S.C. § 102(a), which is the only provision under which the Petition asserted Reeder. Reeder presumptively is prior art to the ’792 patent under a different subsection of the statute, namely § 102(e). However, a reference that is prior art under only § 102(e) may not be asserted in a CBM patent review. Under the AIA, a Petition for a CBM patent review may challenge novelty or non-obviousness of a claim only on the basis of: (i) prior art that is described by section 102(a) . . . ; or (ii) prior art that— (I) discloses the invention more than 1 year before the date of the application for patent in the United States; and (II) would be described by section 102(a) . . . if the disclosure had been made by another before the invention thereof by the applicant for patent. AIA § 18(a)(1)(C). Because Petitioner has not shown that Reeder is prior art that may be asserted in a Petition for a CBM patent review, all of the grounds that rely on Reeder are denied.” slip op. at 15
§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites AlicePatents in suitUS 6,081,792 - Salesforce.Com, Inc. v. Virtualagility, Inc.All claims unpatentablePTAB · Sep 16, 2014 · CBM2013-00024 · APJ Georgianna W Braden · CBM · Final written decision
Claims 1–21 are unpatentable under §§ 101 and 102 over Ito; the contingent motion to amend with substitute claims 22–30 is denied.
RulingsFinal written decision- Skill levelOther
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notTerm construed board ownPreamble limitingDecided for patent owner
“1. “system being implemented using a processor and a storage device accessible to the processor” The preamble of claim 1 recites a “system being implemented using a processor and a storage device.” Petitioner contends that the recited processor and storage device need not be components of the claimed system because they are not positively recited elements. Pet. 11 (citing Ex. 1002 ¶ 39). We are not persuaded by Petitioner’s reasoning, because the processor and storage device recited in the preamble of each independent claim of the ’413 patent serve as the antecedent basis for “said processor” and “the storage device” recited in the body of each claim. Dec. to Inst. 18– 19 (citing C.W. Zumbiel Co., Inc., v. Kappos & Graphic Packaging Int’l, 702 F.3d 1371, 1385 (Fed. Cir. 2012) (noting that a preamble constitutes a limitation when the elements in the body of a claim depend on it for antecedent basis)). Furthermore, if the plain language of a claim indicates that a system is implemented by certain components, then those components constitute required parts of the system. “Implemented,” in that setting, can mean “constituted” or “formed.” Therefore, we construe the clause as setting forth that the processor and the storage device are both components of the claimed system.” slip op. at 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“We agree with Patent Owner that the specification of the ’413 patent teaches that “model entity” is a set of assembled computer data or data item that represents fundamental components of a model. See Ex. 1001, col. 2, ll. 37–42. Patent Owner, however, does not (1) point to any disclosure in the specification that requires a data object to provide the capability for a user to perform specified operations on the model in order for the data object to qualify as a “model entity,” or (2) offer any persuasive evidence regarding the meaning of “model entity.” Therefore, we construe the phrase “model entity” as “a set of assembled computer data or data item that represents fundamental components of a model.”” slip op. at 14
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“issue are directed to a patent-ineligible concept, such as an abstract idea. See Alice, 134 S. Ct. at 2355. “[I]t is important at the outset to identify and define whatever fundamental concept appears wrapped up in the claim so that the subsequent analytical steps can proceed on a consistent footing.” CLS Bank Int’l v. Alice Corp. Pty. Ltd., 717 F.3d 1269, 1282 (Fed. Cir. 2013) (plurality opinion). Here, the challenged claims are directed to a representation of a model for use in processing management information of a collaborative activity. Ex. 1001, col. 2, ll. 37–47. To aid in the management of a collaborative activity (e.g., developing customer relationships), a computer database is created that represents a model of the collaborative activity. Ex. 1004, 116. The model includes model entities (e.g., goals and projects) organized into a plurality of hierarchies (e.g., goals to be done and project hierarchy for doing them, or domain hierarchy of functional areas) having a plurality of types. Id.; see also Ex. 1001, Fig. 3 (hierarchy of goals and projects), Fig. 8 (hierarchy of domains). The model may contain data such as the customer segment, products, needs, etc. Ex. 1001, col. 2, l. 60– col. 3, l. 16. A processor provides a graphical user interface (“GUI”) for interaction with a user. Ex. 1004, p. 0116; see Ex. 1001, Fig. 9 (GUI displaying goals belonging to a domain). Therefore, given this disclosure, we find that the challenged claims are directed to an abstract idea, the creation and use of models to aid in processing management information by organizing and making the information readily accessible by the collaborators of the project. See, e.g., Ex. 1001, col. 2, l. 9–col. 5, l. 8. The model, as described by the specification, is a disembodied concept that is not tied to a specific algorithm or specialized computer. Thus, at the first step of the analysis, we determine the claims at issue here are directed to a patent-ineligible concept: an abstract idea.” slip op. at 21
Patent outcomesUS 8,095,413 unpatentableClaim construction§ 101 eligibility§ 102 anticipationcites Alice · MayoPatents in suitUS 8,095,413
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.