• SAP America, Inc. v. Lakshmi ArunachalamAll claims unpatentable
  PTAB · Aug 17, 2015 · IPR2014-00414 · APJ Brian J Mcnamara · IPR · Final written decision

  Claims 1–19 are unpatentable under the instituted §103 grounds because Petitioner proved unpatentability by a preponderance of the evidence.

  RulingsFinal written decision

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Denied

    “Seventh, having reviewed my financial disclosure, Patent Owner is well aware that even if Microsoft were a party to these proceedings, the de minimis value of stock I own in Microsoft, is far below the $15,000 recusal threshold. 5 C.F.R. § 2640.202(a). Patent Owner’s allegations of a financial conflict of interest in this proceeding are unjustified and not supported by any evidence. Finally, after obtaining my financial disclosure, it appears that Patent Owner arranged to publish it, along with a threatening photo of me superimposed on a target with a skull and crossbones, on an Internet site of uncertain ownership and operation. See, Paper 21, 2 (describing public release of this information on November 26, 2014). These actions suggest an attempt to intimidate. In any case, Patent Owner’s conduct has not influenced and will not influence the outcome of any proceeding before us. Thus, to the extent that Patent Owner has supplemented her Motion to Recuse, Patent Owner’s Motion is DENIED.” slip op. at 6

  • Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateDecided for petitioner

    “To provide support for a negative claim limitation, the written description must describe, at a minimum, a reason to exclude the relevant limitation. Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). As discussed above, Petitioner has demonstrated that the specification essentially is silent on excluding CGI to connect to the value 10 Patent Owner does not cite a specific page, but appears to be referring to page 6 of Ex. 2004). added service provided by the Web merchant. Patent Owner has not rebutted Petitioner’s contentions. Thus, the earliest written description of the limitation “to connect in real time to the value-added network service of the Web merchant without executing Common Gateway Interface (CGI) scripts” is in the claims of the application for the ’894 Patent. For the reasons discussed above, the claimed subject matter in the ’894 Patent is entitled to a priority date of Nov. 30, 2009. See X2Y Attenuators, LLC v. Int'l Trade Comm'n, 757 F.3d 1358, 1366 (Fed. Cir. 2014) (“[E]ntitlement to priority is decided on a claim-by-claim basis, and various claims may be entitled to different priority dates.”).” slip op. at 19

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “CONCLUSION Patent Owner does not respond specifically to the grounds on which we instituted this inter partes review. Having reviewed the Patent Owner Response and Petitioner Reply, and in consideration of the matters discussed above and in the Decision to Institute, we conclude that Petitioner has established by a preponderance of the evidence that claims 1–19 are unpatentable for the reasons stated in our Decision to Institute.” slip op. at 23

  Patent outcomesUS 8,346,894 unpatentable
  § 103 obviousness§ 112 disclosure
  Patents in suitUS 8,346,894
• SAP America, Inc. v. Lakshmi ArunachalamRehearing denied
  PTAB · May 22, 2015 · CBM2014-00018 · APJ Brian J Mcnamara · CBM · Rehearing

  The Board denied Patent Owner’s rehearing request, leaving claims 4–6 and 9–10 unpatentable based on the prior final written decision.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “§ 42.6(a)(3). We consider only those arguments advanced in Patent Owner’s Request for Rehearing concerning subject matter Patent Owner contends we overlooked or misapprehended in our Final Written Decision. 37 C.F.R. § 42.71(d). We are not persuaded by Patent Owner’s argument that we misapprehended or overlooked that the subject matter of the ’158 Patent is drawn to a technical solution to a technical problem because Patent Owner coined terms such as POSvc application, VAN service, object routing, service network, and VAN switch. Req. Rh’g. 3–4. We addressed these issues extensively in our Final Written Decision, noting that claim 1, from which claim 4 depends, is directed to a method of performing a transaction that includes providing a webpage for display, providing an application the user can select to access checking and savings accounts, accepting signals from an input device, and transferring funds. Final Dec. 14. We also addressed the terminology used in the claims and determined that none of these features changes the non-technological nature of the claim. Id. at 13–15. Patent Owner has not identified any matter that we overlooked or failed to apprehend on this issue.” slip op. at 5

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Not reached

    “In a conclusory fashion, Patent Owner states that we have erroneously applied the Supreme Court’s Decision in Alice Corp. Pty, Ltd. v. CLS Bank Int’l, 134 S. Ct. 2347 (2014). Req. Rh’g. 15. However Patent Owner does not otherwise address our conclusion that claims 9 and 10 are unpatentable subject matter under 35 U.S.C. § 101 and does not explain how we misapplied the Court’s decision in Alice.” slip op. at 7

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached

    “Patent Owner takes a similar approach to our analysis of the prior art, stating that SFCU and Computerworld did not conduct real-time transactions and that Lawlor operates over phone lines. Id. at 15. However, the Request for Rehearing does not address our combinations of the art, i.e., Lawlor and Computerworld, Final Dec. 20–23, and EB and SFCU, id. at 23–26, along with CORBA 1 and CORBA 2, id. at 26–36. Patent Owner does not address the further combination with respect to claims 5 and 6 with SNMP.” slip op. at 7

  § 101 eligibility§ 103 obviousnesscites Alice
  Patents in suitUS 8,037,158
• SAP America, Inc. v. Lakshmi ArunachalamAll claims unpatentable
  PTAB · Mar 6, 2015 · CBM2014-00018 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 4–6 are unpatentable under § 103, and claims 9–10 are unpatentable under § 101 as directed to patent-ineligible subject matter.

  RulingsFinal written decision

  • Prior constructionPrior construction adoptedDecided for patent owner

    “Web application We addressed the construction of this term in our Final Written Decision in IPR2013-00194. See SAP Am., Inc. v. Arunachalam, Case IPR2013-00194, slip op. at 11–14 (PTAB Sep. 18, 2014) (Paper 67). We apply the same construction in this proceeding. For the reasons discussed in IPR2013-00194, we construe “Web application” to mean a computer program to perform a certain type of work using the Web. Point-of-service (POSvc) application We addressed the construction of this term in our Final Written Decision in related case IPR2013-00194. See SAP Am., Inc. v. Arunachalam, Case IPR2013-00194, slip op. at 14-16 (PTAB Sep. 18, 2014) (Paper 67). We apply the same construction in this proceeding. Thus, we construe POSvc application to mean a software program that facilitates execution of transactions requested by a user. Service network running atop the World Wide Web We addressed the construction of “service network (running on top of a facilities network)” in our Final Written Decision in related case IPR2013- 00194. See SAP Am., Inc. v. Arunachalam, Case IPR2014-00194, slip op. at 16–18 (PTAB Sep. 18, 2014) (Paper 67). In that proceeding, we construed “service network” to mean a network on which services, other than underlying network communication services, are provided. We apply a similar construction to this similar term in this proceeding. We construe “service network running atop the World Wide Web” to mean a network on which services other than underlying network communications services are provided over the Web. Utilizing a routed transactional data structure that is both complete and non-deferred In our Decision to Institute, we construed this term to mean “using a data structure that facilitates switching a user who selects a transactional application to a service provider program that provides immediate processing.” Dec. to Institute 11–12. In our Final Written Decision in CBM2013-00013, we reconsidered our construction of this term and concluded that “utilizing a routed transaction data structure” encompasses using a data structure that facilitates switching the processing of information associated with a user selected transactional application that provides immediate processing. We apply this broadest reasonable construction for purposes of our analysis under 35 U.S.C. §§ 101 and 103 in this proceeding.11 11 In CBM2013-00013, we also concluded that this term is indefinite under 35 U.S.C. § 112, second paragraph. That challenge is not before us in this proceeding, although we determined that claims 4–6 are unpatentable over Object routing In related proceeding CBM2013-00013, we construed “object routing” in claim 4 to mean the use of individual network objects to route a user from a selected transactional application to the processing provided by the service provider. We apply the same construction in this proceeding. Virtual Information Store In our Decision to Institute, we construed “virtual information store” to mean an information store in which information entries and attributes are associated with a networked object identity. We apply that construction in this final written decision.” slip op. at 10

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “under 35 U.S.C. §101, applying the most recent guidance from the Supreme Court in Alice Corp. Pty, Ltd. v. CLS Bank Int’l, 134 S. Ct. 2347 (2014), which was decided after the Patent Owner Response was filed. To determine whether a claim recites patent-ineligible subject matter, the first step is to determine whether the subject claim is drawn to a law of nature, a natural phenomenon, or an abstract idea. Id. at 134 S. Ct. 2356 (citing Mayo Collaborative Services v. Prometheus Laboratories, Inc., 132 S. Ct. 1289, 1296–97 (2012)). If the claim is directed to patent-ineligible subject matter, the second step is to consider the elements of each claim both individually and “as an ordered combination” to determine whether the additional elements “transform the nature of the claim” into a patent-eligible application. Id. This second step of the analysis searches for an element or combination of elements that is “sufficient to ensure that the patent in practice amounts to significantly more than a patent upon the [ineligible concept] itself.” Id. (internal quotations omitted). Applying the broadest reasonable construction, claim 1 recites a method of carrying out a transaction from a Web application (a computer program to perform a certain type of work on the Web) in which a user selects a POSvc application (a software program that facilitates execution of transactions requested by a user). Thus, claim 1 recites an abstract method, i.e., performing a real-time Web transaction by displaying and providing at least one application a user selects to access checking and savings accounts, and transferring funds (i.e., debiting or crediting) in response to user signals from an input device. Patent Owner contends that our Decision to Institute ignores concrete limitations of claim 1, e.g., the routed transactional data” slip op. at 16

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

    “of routing a data structure as a whole, does not compare a routed data structure to standard I/O, and recites only that the point of service application provides access to the checking and savings account. Although claim 1 recites that transferring funds from checking to savings utilizes a routed transactional data structure that is specific to the POSvc application, claim 1 does not recite specifically what steps are taken to transfer funds in this manner. This recitation does not impose a meaningful limitation on the scope of claim1 because it does not play a significant part in permitting the claimed method to be performed.12 See SiRF Tech. Inc. v. Int’l Trade Comm., 601 F.3d 1319, 1333 (Fed. Cir. 2010). The Specification does not describe clearly how a data structure is transactional, as opposed to non-transactional, or routed, as opposed to non-routed. To the extent that “utilizing a routed transactional data structure that is both complete and nondeferred,” can be construed, we have interpreted it to mean using a data structure that facilitates switching the processing of information associated 12 Claim 1 does not recite what, if any, role is played by the claimed “routed transactional data structure.” with a user- selected transactional application that provides immediate processing. Switching the processing of information from one resource to another, such as from one data base or program, e.g., the claimed point-of service application, to another, is a well-known abstract concept that is not limited to any particular technical approach. The remaining limitations in claim 1 do not contribute any patent- eligible subject matter. The service network atop the Web, which we have construed to mean a network on which services other than underlying network communications services are provided over the Web, is an abstract concept under which customers and service providers communicate over a network so that the service provider can service the customer, in this case to allow the user to transfer funds between checking and savings accounts. This does not impose a meaningful limitation on the scope of the claim. See SiRF Tech, 601 F.3d at 1333. Thus, we conclude that claim 1 does not recite patent-eligible subject matter. Claims 9 and 10 do not add limitations that contribute to patent eligibility. Thus, we conclude that Petitioner has demonstrated by a preponderance of the evidence that claims 9 and 10 do not recite patentable subject matter under 35 U.S.C. § 101.” slip op. at 18

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “We agree with Petitioner that a person of ordinary skill in the art would have considered it obvious to include accessing banking services over the Internet using a browser (as taught in Computerworld) in the system of Lawlor. Pet. 54–56. Lawlor discloses “a new central/communications system performing new functions” and an ATM network linking to a digital packet switched network, such as the Internet, of which the World Wide Web is a part. Ex. 1006, col. 7, ll. 40–50. Petitioner notes that the combination of Lawlor and Computerworld is nothing more than combining the remote banking services of Lawlor with the World Wide Web banking Web sites described in Computerworld without any significant modification and that, like the ’158 Patent, both Lawlor and Computerworld address providing real-time transactional capabilities. Pet. 54. Petitioner points out that both references discuss home banking systems, i.e., the disclosed Computerworld systems operate on the World Wide Web, while Lawlor operates over standard phone networks. Id. at 55. Citing the Declaration of Dr. Sirbu (Ex. 1003) (“Sirbu 1 Decl.”), Petitioner persuasively argues that one of ordinary skill in the art would have found it obvious to adapt the Lawlor system to the World Wide Web, as Computerworld discusses banks that were performing money transfers over the World Wide Web. Id. In view of the above, we conclude that the combination of Lawlor and Computerworld discloses all of the limitations of claim 1, from which claims 4–6 directly or indirectly depend.” slip op. at 23

  Patent outcomesUS 8,037,158 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo
  Patents in suitUS 8,037,158
• Fidelity National Information Services, Inc. v. Checkfree CorporationAll claims unpatentable
  PTAB · Dec 22, 2014 · CBM2013-00030 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 1–21 are unpatentable under § 101 because they claim an abstract payment-intermediation concept implemented with generic computer functions.

  RulingsFinal written decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “BACKGROUND On December 23, 2013, we entered a Decision to Institute a covered business method patent review, Paper 16 (“Dec. to Inst.”), of U.S. Patent No. 7,853,524 B2 (“the ’524 Patent”) on the grounds that claims 1–21 do not recite patent-eligible subject matter under 35 U.S.C. § 101.” slip op. at 2

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “terms “electronic bill” and “EBP” do not even appear in the specification, Petitioner argues that Patent Owner is attempting to recast abstract ideas recited in the ’524 Patent claims in a manner that requires machines or transformations. Pet. Reply 2, 6. We agree with Petitioner that Patent Owner’s construction arguments attempt to read into the claims features that are not recited in them. For example, although there is no EBP system mentioned in the claims, citing the testimony of its expert, Dr. John Kelly, Patent Owner argues that a payment request is captured through an automated interaction with a user over a telephone or is conveyed by transferring data to the EBP system over a data network from a computer. PO Resp. 21–22. As discussed below, we decline to alter any of the constructions we applied in our Decision to Institute.” slip op. at 4

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

    “Merchant credit limit associated with a payee Patent Owner contends that our construction of the “merchant credit limit associated with a payee” as the maximum amount of credit a merchant extends to a payer is contrary to the plain language of the claims because the limit is associated with the payee. PO Resp. 51. Our construction is consistent with the limit being associated with the payee, i.e., the party to whom the payment is made. Patent Owner’s proposed construction, “a value reflecting the credit limit used by the EBP system which is associated with a particular payee,” PO Resp. 52, reads into the claim an extrinsic EBP system not discussed in the specification. In addition, the value reflecting the credit limit is the amount of credit a payee, i.e., a merchant, extends to a payer. Claims 1, 11, and 21 each recite comparing a payment amount associated with the received request, i.e., the request received on behalf of the payer, to a merchant credit limit associated with the payee. The only credit limits described in the specification are limits on the amount of credit extended to a payer. Although the specification describes a merchant credit limit, it does not describe specifically such a limit associated with the payee. The specification describes comparing the payment amount to a merchant credit limit, and making the payment as an electronic payment or a service provider check, if the payment amount is under a specified amount. Ex. 1001, col. 5, l. 65–col. 6, l. 5. Any amount within the merchant’s (i.e., the payee’s) credit limit is added to the consumer’s (i.e., payer’s) monthly ACH balance, and any transaction can be compared to the consumer’s credit limit parameters stored in a database. Id. at col. 6, ll. 5–10. The specification also describes releasing the payment as a draft written on the consumer’s account, rather than the service provider’s account, if the payment amount exceeds the consumer’s, i.e., the payer’s, credit limit. Id. at col. 6, ll. 10– 16. Because the consumer’s credit limit described in the specification protects the service provider, id. at col. 5, ll. 35–37, 65–66, it is a limit associated with the service provider rather than the payee. Claims 1, 11, and 21, however, recite the merchant credit limit associated with the payee. Because each merchant may extend a different amount of credit to each customer, the merchant credit limit associated with the payee limitation appears to require the service provider computer to select a payment means based on comparing the requested payment amount to the amount of credit the merchant, i.e., the payee, extends to the payer. That is, the amount of the payment is compared to the payer’s credit limit with the payee. In any case, as discussed below, this limitation is not material to our determination of the issues under 35 U.S.C. § 101.” slip op. at 8

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “and 21 of the ’524 Patent recites a method or apparatus in which a service provider receives a request to pay a payee, selects a form of crediting the payee based on comparing the payer’s account number to the payee’s merchant account scheme and the payment amount to a merchant credit limit associated with the payee, and directs the payment to the payee in the selected form. Thus, each of the independent claims is drawn to a computer-implemented process or apparatus in which a third party intermediary, i.e., the payment service provider, receives a request to make payment, applies certain criteria to determine what form of payment to use, and then directs the payment to the payee in that form. In Alice, the Supreme Court considered claims that, on their face, were drawn to the fundamental economic concept of exchanging financial obligations between two parties using a third-party intermediary to mitigate settlement risk. The Court, concluded that, like the hedging in Bilski, the claims were drawn to an “abstract idea” beyond the scope of § 101. Alice Corp., 134 S. Ct. at 2355–57.1 In the ’524 Patent, the service provider intermediates payment between the payer and the payee, acting much like the third party intermediary in Alice. The payment service provider mitigates settlement risk by crediting the payee or issuing a check to the payee drawn on the service provider’s funds, or in other circumstances, issuing a draft drawn on the payer’s funds, i.e., determining the form of payments based on the comparisons recited in the claims. Ex. 1001, col. 5, l. 25–col. 6, l. 15. The computer implementation associated with comparing the account number and 1 In Bilski v. Kappos, 561 U.S. 593 (2010) the Court found upatentable, as abstract ideas, claims drawn to hedging against the financial risk of commodity price fluctuations where the claims recited the steps of initiating a series of financial transactions between commodity providers and consumers, identifying market participants with a counterrisk for the same commodity and initiating a series of risk balancing transactions between those market participants and the commodity provider. the credit limit are incidental to the fundamental economic concept of having a third party intermediate a settlement either by crediting the payee from the third party’s funds (as in a credit transaction) or from the payer’s funds (as when the amounts exceed the payer’s credit limit with the service provider). Thus, we conclude that each of independent claims 1, 11, and 21 is directed to an abstract concept.” slip op. at 12

  Patent outcomesUS 7,853,524 unpatentable
  Claim construction§ 101 eligibilitycites Alice · Mayo · Bilski
  Patents in suitUS 7,853,524
• Fidelity National Information Services, Inc. v. Checkfree CorporationAll claims unpatentable
  PTAB · Dec 22, 2014 · CBM2013-00031 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 1–20 are unpatentable under § 101 because they claim the abstract concept of modifying account numbers to match a payee’s format using generic computer implementation.

  RulingsFinal written decision

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner

    “Claims 1 and 15 of the ’311 Patent are drawn to executing instructions on a computer. In response to receiving an account number in a format not expected by a payee, the instructions act to retrieve from a database a rule that causes the received account number to be altered into the expected format before transmitting the account number to the payee. Thus, claims 1 and 15 are directed to the abstract concept of comparing a received account number to a payee’s format, applying a rule, and modifying the account number in accordance with that rule to the expected format before transmitting it to the payee. As evidence that the computer is not a meaningful limitation and that the claims are drawn to an abstract concept, Petitioner cites testimony of inventor David Garrison demonstrating that the steps of the claimed invention could be performed manually. Pet. 12–16. (citing Ex. 1008, 175:25–180:14, 185:11– 189:25; Ex. 1009; Ex. 1010. Patent Owner’s argument that the claimed automatically performed method precludes the need for human intervention, PO Resp. 68, essentially concedes that the process could be performed manually. We conclude that the recitation of a computer in the method or system claims is not a meaningful limitation and does not change the abstract nature of the claimed subject matter. The limitations recited in claims 2–14, which depend from claim 1, and claims 16–20, which depend from claim 15, relate to the abstract concept recited in claims 1 and 15 and are not meaningful limitations that provide patent-eligible subject matter. See, e.g., claims 2 and 16, which recite receiving the consumer account number in association with the payment request. Thus, the method and system claims of the ’311 Patent are drawn to the abstract concept of establishing compatibility between account numbers by applying appropriate rules to modify an account number.” slip op. at 7

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptDecided for petitioner

    “We also agree with Petitioner that, by transforming a consumer account number into a modified account number, the claims of the ’311 Patent do not cause a physical transformation of a data structure, as argued by Patent Owner. PO Resp. 48–49. As previously discussed, the claims of the ’311 Patent do not recite data structures that are physically transformed. In addition, Petitioner points out that Patent Owner’s expert, Mr. McEntee, testified that the claims of the ’311 Patent do not require any physical transformation. Pet. Reply 11 (citing Ex. 2028, 472:19– 428:2). We further note that satisfying the machine-or-transformation test, by itself, is not sufficient to render a claim patent-eligible, as not all transformations or machine implementations infuse an otherwise ineligible claim with an inventive concept. DDR Holdings, LLC, 2014 WL 6845152, at *9. We conclude that altering an account number to be compatible with the requirements of a payee’s system, as recited in the claims of the ’311 Patent, is not the type of transformation that rises to the level of patent-eligible subject matter. Patent Owner contends that in our Decision to Institute we did not evaluate the claims as a whole to determine whether they contain additional substantive limitations that narrow, confine, or otherwise tie down the claims so that, in practical terms, they do not cover the full abstract idea itself. PO Resp. 61. According to Patent Owner, the claims include several concrete and tangible limitations that limit the use of the “putative abstract idea” to a specific application within an electronic bill payment system. Id.  As discussed above, relying on intrinsic and extrinsic evidence, Patent Owner attempts to read into the claims structures that they do not recite. Independent claims 1 and 15 recite only executing instructions to receive an account number, applying a rule to alter the account number to an expected form, and transmitting the altered account number. The specification notes that the claimed steps can be implemented using a general purpose computer, or other processing device capable of executing programmed instructions. Ex. 1001, col. 3. ll. 58–65. Thus, the limitations recited in claims concerning the payment processor and the payment processor computer are generic computer limitations. Generic computer limitations do not make an otherwise ineligible claim patent-eligible. DDR Holdings, 2014 WL 6845152, at *9.” slip op. at 12

  • ExcludeMotion to exclude, deniedOther

    “of the rebuttal testimony of Petitioner’s expert Michael Shamos, Ex. 1021 (“Shamos Decl.”), as beyond the scope of the testimony of Patent Owner’s experts. Paper 40 (“Mot. to Exclude”). Petitioner identifies subject matter the challenged paragraphs of the Shamos Declaration rebut. Paper 41 (“Opp. to Mot. to Exclude”). In reaching our decisions in this proceeding, we do not cite or rely on the portions of the testimony in the Shamos Declaration that Patent Owner moves to exclude. Therefore, Patent Owner’s Motion to Exclude is dismissed.” slip op. at 16

  Patent outcomesUS 7,996,311 unpatentable
  § 101 eligibilitycites Alice · Mayo · Bilski
  Patents in suitUS 7,996,311
• Metavante Corporation / Fidelity National Information Services, Inc. v. Checkfree CorporationAll claims unpatentable
  PTAB · Dec 22, 2014 · CBM2013-00032 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 1–60 are unpatentable under § 101 because they claim an abstract intermediary function implemented with routine computer activity.

  RulingsFinal written decision

  • ExcludeMotion to exclude, deniedDenied

    “Petitioner’s expert Michael Shamos. Paper 41 (“Mot. to Exclude”). Petitioner opposes Patent Owner's Motion to Exclude on the basis that these statements Patent Owner moves to exclude are proper rebuttal to Patent Owner's experts. Paper 42 (“Opp. to Mot. to Exclude”). Our Final Written Decision does not cite or rely on any of the subject matter Patent Owner seeks to exclude. Therefore, we dismiss Patent Owner’s Motion to Exclude.” slip op. at 23

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for petitioner

    “We agree with Petitioner. Claim 1 recites the single step of executing computer implemented instructions with one or more processors. Claim 1 recites that those instructions include ones in which the clearinghouse receives a payment request (or a request to add a payee to a payer’s pick list), accesses billing information stored in a database, identifies payee bill presentment information from the accessed information, and generates and transmits to the payer a notification of the bill presentment information.1 Although the one or more processors may also execute instructions to perform routine ancillary functions for the central clearinghouse to receive the request, access the database and transmit the information, there are no such instructions or structures recited in claim 1. Claim 1 of the ’749 Patent does not recite any structure for the bill presentment and payment central clearinghouse—nor does claim 1 recite any particular software instructions, any particular processors, any particular configuration or interconnection of the recited “one or more processors,” or any other structure to execute the claimed functions called for in the instructions. Thus, the bill presentment and payment central clearinghouse in claim 1 must be construed without structural limitations, other than being programmed to carry out the recited functions.” slip op. at 5

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

    “The ’749 Patent describes the payee-pick-list as a list of payees the user may plan to pay electronically and states that each user’s individual list is stored in the form of a database in a memory associated with the central clearinghouse station. Ex. 1001, col. 16, ll. 49–54. We disagree with Patent Owner’s characterization of the payee-pick-list as a data structure merely because it is used directly by the programmed central clearinghouse computer system. PO Resp. 40. Claim 1 recites receiving a request to add a payee to a pick-list associated with the payer, but does not recite any limitations concerning the pick-list. The specification refers to a database known as a payee-pick-list that includes certain information such as payee identifiers, street addresses, cities, states, zip codes, phone numbers and consumer account numbers. Ex. 1001, col. 16, 61–65. Nothing in this list of common information associated with the payee requires any particular data structure. Thus, we do not import a data structure limitation into the construction of "payee-pick-list” or "pick-list."” slip op. at 7

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “patentable subject matter. First, we determine whether the claims at issue are directed to one or more patent-ineligible concepts, i.e., laws of nature, natural phenomenon and abstract ideas. Id. at 2355 (citing Mayo Collaborative Servs. v. Prometheus Labs., Inc., 132 S. Ct. 1289, 1296–96 (2012)). If so, we then consider whether the elements of each claim, both individually and as an ordered combination, transform the nature of the claim into a patent-eligible application to ensure that the patent in practice amounts to significantly more than a patent upon the ineligible concept itself. Id. Thus, the first step in our analysis is to consider whether the claims of the ’749 Patent recite a patent-ineligible concept. Patent Owner describes the central clearinghouse as a necessary intermediary between payers and payees interacting with each user station and handling EBPP interactions between thousands, if not millions, of such stations, which themselves are computers. Id. at 22. In Alice, the Supreme Court considered claims drawn to a method of exchanging financial obligations between two parties using a third-party intermediary to mitigate settlement risk and concluded that on their face, claims drawn to the concept of an intermediated settlement, like the hedging in Bilski, is an “abstract idea” beyond the scope of § 101. Id. at 2355–57.2 We conclude that the claims of the ’749 Patent, which are directed to a clearinghouse that acts as an intermediary between a payer and the payee by notifying the payer about payee bill presentment information, are not directed to patent-eligible subject matter. The steps recited in claim 1, and in each 2 In Bilski v. Kappos, 561 U.S. 593 (2010), the Supreme Court found unpatentable, as abstract ideas, claims drawn to hedging against the financial risk of commodity price fluctuations where the claims recited the steps of initiating a series of financial transactions between commodity providers and consumers, identifying market participants with a counter-risk for the same commodity and initiating a series of risk balancing transactions between those market participants and the commodity provider. of independent claims 20, 40, 59, and 60, are carried out by a clearinghouse that receives a request from a payer to provide payee information or add a payee to the payer’s pick-list. The claims recite receiving a request and are not limited to any particular number of such requests. The clearinghouse retrieves the payee information from a database and generates and transmits a responsive notification message to the payer. Thus, independent claims 1, 20, 40, 59, and 60 are drawn to the patent-ineligible concept of executing instructions in which an intermediary receives a request, retrieves information from a database, and transmits the information to the requester.” slip op. at 9

  Patent outcomesUS 7,792,749 unpatentable
  Claim construction§ 101 eligibilitycites Alice · Mayo · Bilski
  Patents in suitUS 7,792,749
• SAP America, Inc. v. Lakshmi ArunachalamAll claims unpatentable
  PTAB · Sep 18, 2014 · CBM2013-00013 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 1–3 and 11 are unpatentable under §§ 101 and 103, and claims 1–6 and 11 are unpatentable under § 112, second paragraph.

  RulingsFinal written decision

  • ExcludeMotion to exclude, deniedDenied

    “Under Federal Rules of Evidence (“FRE”) 901(b)(1) a proponent may authenticate evidence through testimony that the evidence is what it is claimed to be. In Loraine v. Markel American Insurance Co., 241 F.R.D. 534, (D. Md. 2007), the court noted that a witness authenticating electronic evidence must “provide factual specificity about the process by which the electronically stored information is created, acquired, maintained, and preserved without alteration or change, or the process by which it is produced if the result of a system or process that does so.” Id. at 545. The inventor’s statements do not meet these criteria. However, under FRE 901(b)(4) a party may authenticate evidence using circumstantial evidence in conjunction with the appearance, contents, substance, internal patterns, or other distinctive characteristics of the evidence. Although Patent Owner has not provided evidence such as hash values or metadata (see Lorraine at 547), the contents and substance of the documents indicate that they are what they purport to be. Given their technical nature of the documents, this panel can assign them appropriate weight.” slip op. at 28

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

    “As discussed further in this decision, based on Patent Owner’s contentions and the language of the Specification, we conclude that the term “routed transactional data structure” fails to inform a person of ordinary skill in the art of the scope of the claim with reasonable certainty and is therefore indefinite under 35 U.S.C. § 112 , second paragraph. See, Nautilus, Inc. v. Biosig, Insts., Inc., 134 S. Ct. 2120, 2129–30 (2014) . However, to the extent that the claim can be construed in order to analyze its relationship to the prior art in this proceeding and whether the claim recites patent eligible subject matter under 35 U.S.C. § 101, we have reconsidered our use of the expression “switching a user” in the construction we applied in our Decision to Institute. Dec. to Inst. 15-16. Claim 1 recites that the “routed transactional data structure” is specific to a POSvc application, which is a software program that facilitates execution of transactions requested by a user. Upon reconsideration, we conclude that “utilizing a routed transaction data structure” encompasses using a data structure that facilitates switching the processing of information associated with a user selected transactional application that provides immediate processing.” slip op. at 11

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “In our Decision to Institute, we noted that “object routing” requires the use of individual networked objects to route a user from a selected transactional application to the processing provided by the service provider. In contrast, the limitation “routed transactional data structure,” does not impose a meaningful limit on the scope of claims 1–3 and 11 because it does not play a significant part in permitting the claimed method to be performed. See SiRF Tech. Inc. v. Int’l Trade Comm., 601 F.3d 1319, 1333 (Fed. Cir. 2010). For example, as explained below in our 35 U.S.C. § 112 , second paragraph analysis, the Specification does not describe clearly how a data structure is transactional, as opposed to non-transactional, or routed, as opposed to non-routed. As discussed above, to the extent that “utilizing a routed transactional data structure that is both complete and non-deferred,” can be construed, we have interpreted it to mean using a data structure that facilitates switching the processing of information associated with a user– selected a transactional application that provides immediate processing. Switching the processing of information from one resource to another, such as from one program or data base to another, is a well-known abstract concept that is not limited to any particular technical approach, such as object routing, as recited in claim 4. The remaining limitations in claim 1 do not contribute any patent– eligible subject matter. The service network atop the Web, which we have construed to mean a network on which services other than underlying network communications services are provided over the Web, is an abstract concept under which customers and service providers communicate over a network so that the service provider can service the customer, in this case to allow the user to transfer funds between checking and savings accounts. This does not impose a meaningful limitation on the scope of the claim. See SiRF Tech, 601 F.3d at 1333. Thus, we conclude that claim 1 does not recite patent–eligible subject matter.” slip op. at 16

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

    “The remaining limitations in claim 1 do not contribute any patent– eligible subject matter. The service network atop the Web, which we have construed to mean a network on which services other than underlying network communications services are provided over the Web, is an abstract concept under which customers and service providers communicate over a network so that the service provider can service the customer, in this case to allow the user to transfer funds between checking and savings accounts. This does not impose a meaningful limitation on the scope of the claim. See SiRF Tech, 601 F.3d at 1333. Thus, we conclude that claim 1 does not recite patent–eligible subject matter. Claims 2, 3, and 11 do not add limitations that contribute to patent eligibility. Thus, we conclude that Petitioner has demonstrated that claims 1–3 and 11 do not recite patentable subject matter under 35 U.S.C. § 101.” slip op. at 17

  Patent outcomesUS 8,037,158 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousness§ 112 disclosurecites Alice · Mayo · Nautilus
  Patents in suitUS 8,037,158
• Interthinx, Inc. v. Corelogic Solutions, LLCAll claims unpatentable
  PTAB · Jan 30, 2014 · CBM2012-00007 · APJ Brian J Mcnamara · CBM · Final written decision

  Claims 1, 6, 9, and 10 are unpatentable under § 101 and anticipated by or obvious over Jensen-1; the Board did not reach the remaining prior-art challenges.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(e) estoppelEstoppel does not applyDecided for petitioner

    “determinations are pure questions of law, not subject to the clear and convincing evidence standard, is not supported by the Federal Circuit. “[T]he analysis under [35 U.S.C.] § 101, while ultimately a legal determination, is rife with underlying factual issues.” Ultramercial, Inc. v. Hulu, LLC, 722 F.3d 1335, 1339 (Fed. Cir. 2013) (citing, e.g., CLS Bank Int'l v. Alice Corp., 717 F.3d 1269, 1304–05 (Fed. Cir. 2013) (en banc)) (Chief Judge Rader, and Judges Linn, Moore, and O'Malley, concluding that “any attack on an issued patent based on a challenge to the eligibility of the subject matter must be proven by clear and convincing evidence,” and Judges Lourie, Dyk, Prost, Reyna, and Wallach, concluding that a statutory presumption of validity applies when § 101 is raised as a basis for invalidity in district court proceedings.)). In denying Petitioner’s motion for judgment as a matter of law under 35 U.S.C. § 101, the District Court stated only that Petitioner failed to show that claims 1 and 10 of the ’201 Patent do not cover a “new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof.” Ex. 2039, 2. The District Court’s decision applied the clear and convincing evidence standard to the facts underlying its determination of law when denying Petitioner’s motion for summary judgment and motion for judgment as a matter of law that the claims of the ’201 Patent do not recite eligible subject matter. In contrast, the Board reviews the patentability of a claim, rather than its validity, and applies a preponderance of the evidence standard to the underlying factual determinations, e.g., whether the claims contain limitations that narrow or tie them to specific applications of an otherwise abstract concept. 35 U.S.C. § 326(e); Ultramercial, 722 F.3d at 1339. Because the Board applies to the underlying facts an evidentiary standard that is different from the standard applied by the courts, the issue decided by the Board is not identical to the one decided or litigated in the first action and could not have been essential to the final judgment in the first action. See In re Freeman, 30 F.3d, 1459, 1465 (Fed. Cir. 1994). Petitioner did not have an opportunity to litigate the issue in the first action. Id. Therefore, we conclude that Petitioner’s challenge under 35 U.S.C. § 101 is not barred by res judicata or collateral estoppel.” slip op. at 5

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “abstract idea, the claim instead is drawn to the abstract idea itself. Ultramercial, 722 F.3d at 1343. Inventor, Dr. Jost considers his invention to be the process for predicting the selling price of a home (a point estimate) using statistical analysis to develop the point estimate, and a co-inventor’s error model, which was also developed using statistical analysis. Ex. 1022, 72-73, 81-82. Dr. Jost’s testimony is consistent with claims 1 and 10, which recite appraising real estate by developing and storing a predictive model and generating a signal indicative of the appraised (predicted) value, and developing and storing an error model and generating a signal indicative of the error range for the appraised (predicted) value. Patent Owner’s expert Dr. Lipscomb characterizes the invention as “a way to determine the sales price of a property that may not have a recent sales transaction” and that predictive models “have been around a long time.” Ex. 1024, 42-43. Determining a price has been found to be abstract as a method of calculating. See, SAP America, Inc. v. Versata Dev. Group, Inc., CBM2012- 00001, 2013 WL 3167735, at *16 (PTAB, June 11 2013). Dr. Jost testified that it was common in statistics to provide a confidence interval around estimates. Ex. 1022, 102. The testimony of Dr. Jost and Dr. Lipscomb indicates that determining an error can be accomplished using the same well known techniques as those applied to the predictive model and that bounding a price estimate by an error range is an abstract concept. Therefore, we find the claimed development of a model to predict a value and an error model to assess the error range around the predicted value, as recited in claims 1 and 10, is an abstract concept. Similarly, claims 6 and 9 recite limitations that bound the geographic area from which data is obtained to develop the model. The limitations in claims 6 and 9 recite the abstract and well known concept of examining the geographic area around the subject property so that relevant samples can be obtained to predict the price of the property.” slip op. at 10

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptIneligibleUnpatentable
  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “54-55. Patent Owner’s argument is similar to its underlying theme that CAMA prior art does not apply to the claimed AVM system. As discussed above, we do not find this argument persuasive because the ultimate objective of each system is to determine a value for each individual parcel. The same sentence in Jensen-1 that refers to a model estimating the sales price of all the properties also refers to adjustments necessary to correct the actual sales prices of selected recent comparable sales for the property characteristic differences between the subject property being valued and each comparable sale, in order to ascertain what each comparable property would have sold for had it been identical to the subject property in a physical descriptive sense on the valuation date. Ex. 1014, p. 194. (Emphasis added). Thus, as recited in claims 1, 6, 9 and 10, Jensen-1 obtains individual property data and recognizes a relationship between individual property data and the training data. Jensen-1 also discloses using the training data to predict the individual property value, as recited in claims 1, 6, 9 and 10. Jensen-1 discusses a model in which the value of a property is based on the land value qualified by a set of adjustments. Ex. 1014, p. 198. The adjustments reflect specific property characteristics. For example, up to a point, the value of a property can be expected to increase with increasing frontage. Id. Thus, specific properties with different frontage are valued differently. Jensen-1 discloses other modeling approaches that determine various per unit rates within a market model using regression analysis, Longini and Carbone’s adaptive estimation, and Carlson’s iterative correlative estimation procedure. Id. at 200. Jensen-1’s discussion of interactive correlative estimation specifically states that, within each iteration, “the model estimate and then the residual error (the actual sale price minus the model estimate) are computed on a per parcel basis.” Ex. 1014, p. 220. Thus, Jensen-1 discloses generating an appraised value responsive to the application of individual property data to the predictive error model. Jensen-1 specifically states that “[o]nce meaningful market models have been developed from the available sales, they can be used to estimate the fair market values of all of the parcels in the jurisdiction whether recently sold or not.” Ex. 2014, p. 224. As discussed above, the reference to all parcels in the jurisdiction does not imply that all the parcels are evaluated the same. Jensen discloses that the market models take into account the various characteristics of each parcel and determine a value for each parcel. Jensen-1 notes that the model estimate, i.e., the fair market value of each parcel as determined by the market models, is an abstract number and its reliability as an approximation of true market value depends on the quality of the individual estimates. Ex. 1014, p. 224. Jensen-1 specifically notes that when an actual sale price falls below the value estimate, it may or may not indicate a problem with the appraisal. Id. Thus, Jensen-1 applies to individual appraisals and attempts to assess an error in the appraisal of each parcel.” slip op. at 13

  Patent outcomesUS 5,361,201 unpatentable
  § 101 eligibility§ 102 anticipation§ 103 obviousnesscites Mayo
  Patents in suitUS 5,361,201

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.