- Cxloyalty, Inc. v. Maritz Holdings Inc.All claims unpatentablePTAB · Dec 19, 2019 · CBM2018-00037 · APJ Justin T Arbes · CBM · Final written decision
Claims 1–15 are unpatentable under § 101; the motion to amend is granted for proposed substitute claims 16–23, which were not shown unpatentable.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“does not remove the claim from the realm of abstract ideas. See Pet. 52–53; Reply 12; SAP Am., Inc. v. InvestPic, LLC, 898 F.3d 1161, 1168 (Fed. Cir. 2018) (holding that it “does not matter to [the conclusion that the claim is directed to an abstract idea] whether the information here is information about real investments,” as “even if a process of collecting and analyzing information is ‘limited to particular content’ or a particular ‘source,’ that limitation does not make the collection and analysis other than abstract” (citation omitted)). Further, the last two clauses of claim 1 that recite how the transaction is viewed from the perspectives of the participant and vendor system, respectively, merely express the “non-physical result” of the information transfers and confirm the abstract nature of the claimed subject matter. See Pet. 57. In fact, as to the vendor system clause, the Specification indicates that the vendor system transfers information no differently than it would for any other transaction. See Ex. 1001, col. 7, ll. 15–18 (disclosing that vendor system 208 responds to purchase request 216 “in the same way that it would respond to any other purchase request from a consumer that presents a credit card”).” slip op. at 35
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“Our conclusion also is supported by the ’087 patent’s description of” slip op. at 41
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted
“transaction, . . . display[ing] an order message indicating the completion of the purchase transaction to the respective participant.” Mot., App’x A, 4. An example in which a judicial exception is not integrated into a practical application is when “an additional element adds insignificant extra-solution activity to the judicial exception.” Guidance, 84 Fed. Reg. at 55; Flook, 437 U.S. at 590 (holding that a step of adjusting an alarm limit variable was “post-solution activity”). Displaying an order message after the facilitated transaction has been completed amounts to insignificant post-solution activity, and does not support a conclusion that the abstract idea of claim 16 is integrated into a practical application.” slip op. at 75
- 101 substituteMixed
“transaction, . . . display[ing] an order message indicating the completion of the purchase transaction to the respective participant.” Mot., App’x A, 4. An example in which a judicial exception is not integrated into a practical application is when “an additional element adds insignificant extra-solution activity to the judicial exception.” Guidance, 84 Fed. Reg. at 55; Flook, 437 U.S. at 590 (holding that a step of adjusting an alarm limit variable was “post-solution activity”). Displaying an order message after the facilitated transaction has been completed amounts to insignificant post-solution activity, and does not support a conclusion that the abstract idea of claim 16 is integrated into a practical application.” slip op. at 75
Patent outcomesUS 7,134,087 unpatentable§ 101 eligibilitycites Alice · Mayo · Bilski · Berkheimer · EnfishPatents in suitUS 7,134,087 - HP Inc. / SAP America, Inc. v. Big Baboon, Inc.Institution deniedPTAB · Jun 28, 2016 · CBM2016-00020 · APJ Trenton A Ward · CBM · Institution
The Board denied institution because Petitioner did not show that claims 15 and 20–34 were more likely than not unpatentable under § 101 or any of the three § 103 grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“For the reasons that follow, Petitioner failed to establish that it is more likely than not that at least one of the challenged claims is unpatentable. Therefore, we deny the Petition.” slip op. at 2
- BurdenDenied
“We believe the same is true in this matter. Petitioner fails to identify specific documentary evidence indicating that the claim element “via Web administration, producing a software configuration in which selected ones of the modules are enabled or disabled” would have been obvious to a person of ordinary skill in the art at the time of the ’275 patent. At best, Petitioner provides a string cite to nine different documents, without pointing to any particular page or disclosure in any of those documents, as allegedly illustrating an “industry-wide push to Web-enable,” and provides a string cite to eight different paragraphs of testimony from Dr. Greenspun, as allegedly indicating why a skilled artisan “would have seen a strong need to provide Web-enabled system administration capabilities for the R/3 system described in R/3 Online and R/3 Book.” See Pet. 63–64 (citing Exs. 1017– 1021, 1023, 1026, 1027, 1030; Ex. 1032 ¶¶ 58–60, 85–86, 110–112). Petitioner, however, fails to identify with specificity which documentary evidence indicates that it would have been common knowledge to provide a Web interface for system administration of the system described by R/3 Online and the R/3 Book and, thus, that claim 15 would have been obvious to an ordinarily skilled artisan based on combining this alleged common knowledge with the system described by R/3 Online and R/3 Book. The Board, and Patent Owner, are left to speculate as to which particular evidence Petitioner is relying on. See Pet. 12, 42; 37 C.F.R. §§ 42.304(b)(4)–(5) (a petition must “specify where each element of the claim is found in the prior art” and identify “specific portions of the evidence that support the challenge”), 42.22(a)(2) (a petition must include a “full statement of the reasons for the relief requested, including a detailed explanation of the significance of the evidence”). In view of this deficiency, we determine that Petitioner fails to articulate sufficient reasoning to support its assertion of obviousness. See KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Accordingly, based on the record before us, we determine that Petitioner fails to demonstrate that it is more likely than not that independent claim 15, and claims 20–34 dependent therefrom, would have been obvious over R/3 Online and R/3 Book.” slip op. at 29
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Petitioner urges the Board to construe two claim phrases. First, Petitioner urges us to construe the claimed “end-to-end, business-to-business, e-commerce business automation software for automation business functions across multiple business domains” to mean “[s]oftware that, using a computer network, at least partially automates business functions relating to two or more businesses and from two or more business domains (such as products, payments, and financial performance).” Pet. 19. Second, Petitioner urges us to construe the claimed “via Web administration, producing a software configuration in which selected ones of the modules are enabled or disabled” to mean “producing a software configuration in which modules can be enabled or disabled by (1) changing the configuration parameters of a web server program or (2) using a Web browser to change configuration parameters of software running on a server.” Pet. 21. Patent Owner does not offer any proposed constructions of claim terms in its Preliminary Response. For the reasons explained below, in this case determining the scope of the terms proffered by Petitioner is not necessary to determine whether Petitioner has met the standard for institution of a covered business method patent review, and we decline to adopt the constructions sought by Petitioner. See, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable
“Claim 15 (the only claim substantively addressed by Petitioner), however, does not recite any “gathering” steps, and Petitioner does not explain sufficiently how the limitations of claim 15 are directed to the concept of “gathering” information. For example, claim 15 merely recites “providing . . . business automation software, “identifying multiple modules of the software,” and producing a “software configuration.” Additionally, claim 15 requires producing a “workscope/workflow structured display of complex database records,” which constitutes “an integrated decision-making environment for a particular business function.” Thus, the method of claim 15 does not expressly require that information be gathered across “multiple business domains.” Rather, claim 15 requires providing “business automation software” to produce a “structured display” of “records” pertaining to a “business transaction,” such that the display constitutes an “integrated decision-making environment for a particular business function.” Thus, even if Petitioner is correct that “gathering information from across a business and using the information to make decisions” by itself is an abstract idea, Petitioner’s analysis does not address sufficiently the specific language of claim 15 and explain why claim 15 is directed to that idea. See Pet. 27. Similarly, dependent claims 20–34 are not directed to “gathering information,” and Petitioner provides no analysis of the language of the dependent claims. In light of the above, we determine that Petitioner has failed to establish the first step of the Mayo framework; i.e., Petitioner fails to identify sufficiently an abstract idea to which claim 15 is directed.8 Petitioner combines its arguments under § 101 against dependent claims 20– 34 with its arguments against claim 15 and fails to provide any additional arguments for these dependent claims. See Pet. 25 (arguing that the “sixteen challenged claims of the ’275 patent are likewise unpatentable under §101”). Therefore, we similarly determine that Petitioner fails to establish the first step of the Mayo framework with respect to dependent claims 20–34. Based on the foregoing, we determine Petitioner has failed to establish, based on the record presented, that claims 15 and 20–34 are more likely than not directed to patent ineligible subject matter under 35 U.S.C. § 101. 8 We need not decide whether claim 15 is directed to a different abstract idea, and only determine that Petitioner has not shown sufficiently that claim 15 is directed to the alleged abstract idea that Petitioner proposes in the Petition.” slip op. at 19
Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · MayoPatents in suitUS 6,343,275
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.