- 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 - Motorola Mobility, LLC v. Intellectual Ventures I, LLCAll claims unpatentablePTAB · Mar 21, 2016 · CBM2015-00004 · APJ Phillip J Kauffman · CBM · Final written decision
Claims 1, 8, 16, and 17 are unpatentable under § 101 because they claim the abstract idea of distributing electronic content using only routine, conventional activity.
RulingsFinal written decision- BurdenDecided for petitioner
“Final Written Decision is entered pursuant to 35 U.S.C. § 328(a). For the reasons that follow, we determine that Petitioner has shown by a preponderance of the evidence that claims 1, 8, 16, and 17 of the ’464 patent are unpatentable.” slip op. at 2
- ExcludeMotion to exclude, deniedDenied
“This argument is unpersuasive for two independent reasons. First, Petitioner’s objections do not mention an alleged failure to identify all material relied upon, and consequently the objection did not identify the grounds for the objection with sufficient particularity to permit Patent Owner to correct in the form of supplemental evidence. See 37 C.F.R. § 42.64(b)(1), (c). Second, our rules provide that the opinion of an expert witness may be given little or no weight if the expert does not disclose the underlying facts or data on which the opinion relies. See 37 C.F.R. § 42.65. Therefore, the absence of such underlying facts or data is a matter relating to the weight to be given such evidence rather than to the admissibility of that evidence. Further, Petitioner does not identify a Federal Rule of Evidence that supports exclusion as requested, and Petitioner’s citation to the Federal Rules of Civil Procedure (FRCP) is unpersuasive because the Board has not adopted those rules. See Mot. 2; Opp. Reply 2; 37 C.F.R. § 42.62 (applying the Federal Rules of Evidence (“Fed. R. Evid.”) to inter partes reviews); see generally Atlanta Gas Light Company v. Bennett Regulator Guards, Inc., Case IPR2013-00453, slip op. at 8 n.5 (PTAB Jan. 6, 2015) (Paper 88) (noting that the Board has not adopted the Federal Rules of Civil Procedure).” slip op. at 10
- Expert testimonyPetitioner expert creditedDecided for patent owner
“EXHIBIT 2010 – THE DECLARATION OF DR. SHORT Petitioner presents five arguments that all or some of the Declaration of Dr. Short (Ex. 2010) should be excluded. Before addressing those arguments, we observe that Dr. Short’s qualifications align sufficiently with the challenged subject matter (software for use on a user station) such that his knowledge is helpful in understanding the evidence and determining facts in issue. For example, as noted by Patent Owner, Dr. Short has a Ph.D. in Electrical Engineering and more than 35 years of experience as a practicing engineer, which includes experience in computer programming. Opp. 2–3; Ex. 2010 ¶¶ 5–7; Ex. 2019 (Dr. Short’s personal data sheet).” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“Claim 1 is directed to a software product comprised of computer executable instructions for use at a user station that includes a processor and a storage device. Step (a) recites “enable a user at the user station to select content,” and step (b) recites “effect transport of the selected content.” Step (b) requires effecting transport of the content that was selected (i.e., “the selected content”) in step (a). Use of the past tense of select (i.e., “selected”) in step (b) indicates that selection of the content occurred before transport was effected. Consequently, the language of claim 1 indicates that step (a) (the selecting step) must occur before step (b) (the transporting step). Likewise, step (c) effects storage of “the transported content,” meaning the content transported in step (b), and step (d) requires effecting presentation of “the stored content,” meaning the content that was stored in step (c). Accordingly, the plain language of claim 1 suggests that the steps must be performed in the order presented. See PO Resp. 25; see also E-Pass Techs., Inc. v. 3Com Corp., 473 F.3d 1213, 1222 (Fed. Cir. 2007) (holding that where subsequent steps to completed results of the prior step, the steps of the claim must be performed in order). We consider this interpretation, in light of the specification, as interpreted by a person of ordinary skill in the art. See Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc) (“The construction that stays true to the claim language and most” slip op. at 7
Patent outcomesUS 6,658,464 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · PhillipsPatents in suitUS 6,658,464 - The United States Postal Service (Usps) / The United States Of America, As Represented By The Postmaster General v. Return Mail, Inc.All claims unpatentablePTAB · Oct 15, 2015 · CBM2014-00116 · APJ Kevin F Turner · CBM · Final written decision
Claims 39–44 are unpatentable under § 101 because they claim the abstract idea of relaying mailing address data without significantly more; anticipation by 1997 ACS was not shown.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for petitioner
“II. ANALYSIS A. Claim Construction We construe all terms, whether or not expressly discussed here, using the broadest reasonable construction in light of the ’548 Patent specification. See 37 C.F.R. § 42.300(b); see also In re Cuozzo Speed Techs., LLC, 93 F.3d 1268, 1278–80 (Fed. Cir. 2015) (“Congress implicitly approved the broadest reasonable interpretation standard in enacting the AIA,” and “the standard was properly adopted by PTO regulation.”). During the pre-trial stage of this proceeding, the parties submitted their constructions for specific claim terms and we adopted constructions consistent with the constructions adopted by the U.S. Court of Federal Claims (Ex. 1011). Dec. 8–10. Return Mail does not dispute the constructions adopted. PO Resp. 16–27. Upon review of the parties’ explanations and supporting evidence before us, we discern no reason to modify our claim constructions set forth in the Decision on Institution with respect to these claim terms. Dec. 8–10. For convenience, our claim constructions are reproduced in the table below:” slip op. at 6
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionIneligibleUnpatentable
“USPS has shown, by a preponderance of the evidence, that claim 39, as a whole, is directed to the processing of returned mail items, involving decoding information, obtaining an updated address, and electronically transmitting that updated address to a transferee. USPS has shown that the steps are directed to the abstract idea of relaying mailing address data, with the inclusion of an electrical transmission step. Regarding whether claim 39 includes limitations that amount to significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptIneligibleUnpatentable
“significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“deciding between the proffered constructions of “[d]ecipher information into useable form” and “[c]onvert information into useable form,” the court concluded that “using the terms ‘decipher’ and ‘deciphered’ more closely follow the customary meaning of the terms and reflects the claim language. This is because decoding must operate on encoded data,” which is recognized in the term “decipher” but not in “convert.” Ex. 1011, 22–23. USPS contends that “the carrier converts into intelligible form the participant code and endorsement thereby performing the claimed ‘decoding.’” Pet. 45. However, we find no support within 1997 ACS that the carrier decodes or deciphers the participant code or endorsement because the carrier (a person) is merely reading those indicators. The indicator “ADRESS SERVICE REQUESTED” is merely read and there is no disclosure that the carrier decodes the participant code or the keyline. We disagree with Dr. Lubenow that the plain-English endorsements “meet the plain and ordinary meaning of the term ‘code.’” Ex. 1028 ¶ 18. As such, we are not persuaded that the carrier in 1997 ACS acts to decode encoded data on the returned mail items.” slip op. at 24
Patent outcomesUS 6,826,548 unpatentableClaim construction§ 101 eligibility§ 102 anticipationcites Alice · MayoPatents in suitUS 6,826,548 - 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.