Business Method Patents

Business method patents claim methods of conducting business, commercial transactions, financial processes, and related activities: HISTORICAL BACKGROUND: State Street Bank v. Signature Financial Group (Fed. Cir. 1998) upheld a business method patent on a hub-and-spoke mutual fund accounting system; held that the patent statute's 'useful, concrete, and tangible result' test admitted business methods; triggered an explosion in business method patent filings; subsequent Supreme Court decisions significantly restricted business method patent scope; WHAT BUSINESS METHOD PATENTS CLAIM: financial transaction processing (payment systems, currency exchange, risk hedging); e-commerce methods (online shopping carts, recommendation engines, auction systems); data processing and analysis; insurance and financial instruments; marketing systems and methods; management and organizational methods; advertising technology; health care administration; NOTABLE BUSINESS METHOD PATENTS (historical): Amazon's one-click purchasing (US 5,960,411): settled for royalties from Barnes & Noble; Priceline's 'name your own price' auction model; PayPal's escrow-based online payments; Google's AdWords auction ranking system; CURRENT STATUS: most classic 'doing business on the internet' claims that simply automate a known business process on a generic computer are invalid under Alice; business method patents that survive Alice must: (1) be directed to a specific technical improvement to a computing system or process; or (2) go beyond the abstract idea itself by adding meaningful inventive elements that are not routine, conventional, or well-understood (a 'significantly more' contribution).

Two Supreme Court decisions fundamentally changed the landscape for business method patents: BILSKI v. KAPPOS (S.Ct. 2010): challenged a patent on a method for hedging commodity risks in energy markets; Supreme Court rejected the Federal Circuit's 'machine or transformation' test as the SOLE test for eligibility; held that business methods are not categorically excluded from § 101 but may be excluded as abstract ideas; the hedging risk patent was invalid as directed to a fundamental economic practice (abstract idea); left unclear what beyond the machine-or-transformation test would satisfy § 101; ALICE CORP. v. CLS BANK INTERNATIONAL (S.Ct. 2014): unanimous decision; addressed a patent on computerized escrow management for financial transactions; ALICE TWO-STEP TEST: STEP ONE — Is the claim directed to a patent-ineligible concept (abstract idea, law of nature, natural phenomenon)? STEP TWO — If yes, does the claim add an 'inventive concept' — something significantly more than the abstract idea itself, such that the claim is meaningfully different from the abstract idea in application? WHAT ALICE DID TO BUSINESS METHOD PATENTS: implementing an abstract idea (like risk hedging, escrow, or auction) on a 'generic computer' adds nothing to make it eligible; the functions of creating accounts, maintaining records, adjusting balances, and issuing automated instructions are routine, conventional, well-understood computer operations — not inventive; POST-ALICE INVALIDATION RATE: courts have found many business method patents invalid under Alice; industry estimates suggest 60-80% of challenged software and business method patents are found ineligible.

Business method patents that survive § 101 share common characteristics: STEP 1 SURVIVAL — NOT AN ABSTRACT IDEA: if the claim is directed to a specific technical solution to a technical problem (not just an abstract concept), it may survive step 1; ENFISH LLC v. MICROSOFT (Fed. Cir. 2016): patent on a self-referential database table for improved computer function; claim was directed to specific improvement in computer function itself; not directed to abstract idea — survives step 1; McRO v. BANDAI NAMCO (Fed. Cir. 2016): patent on automatically animating lip synchronization; specific rules produce a specific technical result; not abstract; STEP 2 SURVIVAL — INVENTIVE CONCEPT: if the claim IS directed to an abstract idea but adds an inventive concept, it may survive step 2; BASCOM v. AT&T (Fed. Cir. 2016): internet content filtering; even if individual elements are routine, their specific combination and arrangement on a network was unconventional; BERKHEIMER v. HP (Fed. Cir. 2018): whether claimed elements are 'well-understood, routine, conventional' is a factual question — cannot be decided on the pleadings without evidence; WHAT SURVIVES IN PRACTICE: claims that recite: specific technical improvements to computer functioning; novel data structures with technical advantages; unconventional technical arrangements of components; specific algorithms for solving a technical problem; real-world applications with specific technical steps; WHAT DOES NOT SURVIVE: claims that recite: general computer implementation of a known business process; using a computer to store, retrieve, or transmit information in a conventional way; abstract mathematical relationships without meaningful application; generic steps (determining, transmitting, storing) without specific technical content.

Drafting a business method patent that can survive § 101 challenges requires specific strategies: FOCUS ON THE TECHNICAL PROBLEM AND TECHNICAL SOLUTION: identify the specific technical problem in the prior art computer systems that the invention solves; claim the solution in terms of the technical improvement, not just the business result; example: instead of claiming 'a method of hedging financial risk using a computer,' claim 'a method for reducing latency in real-time financial risk calculation by [specific algorithm that produces specific technical improvement]'; IDENTIFY WHAT IS TECHNICALLY UNCONVENTIONAL: what does the claimed system do that prior art computing systems didn't do? Is there a specific algorithm, data structure, process flow, or system architecture that is new and not routine? That is the 'inventive concept' for step 2; DESCRIBE TECHNICAL IMPROVEMENTS IN THE SPECIFICATION: the specification should explicitly describe: the problem with prior art computing systems; how the claimed invention specifically improves computing performance, efficiency, or capability; why the specific claimed implementation is unconventional; WHY THIS MATTERS: Berkheimer v. HP (Fed. Cir. 2018): the 'well-understood, routine, conventional' inquiry in step 2 is a factual question; a detailed specification describing why the claimed elements are unconventional creates a fact issue that cannot be resolved against the patent owner at the pleadings stage; CLAIM STRUCTURE: independent claims should include the specific technical elements that define the unconventional improvement; avoid generic claim language that reads on any computer implementation; PROSECUTION: argue specifically that the claimed combination is not routine, conventional, or well-understood; cite technical literature showing that the claimed approach was unconventional at the time of invention; submit declarations from technical experts if needed.

Alice had a dramatic impact on USPTO examination and PTAB proceedings for business method patents: USPTO EXAMINATION POST-ALICE: 2014: USPTO issued interim eligibility guidance following Alice; examiners began rejecting most business method applications under § 101; Technology Center 3600 (business methods, e-commerce, finance) rejection rates skyrocketed; 2019 REVISED GUIDANCE: USPTO issued new guidance creating a more structured approach; Step 2A, Prong 1: is the claim directed to one of three categories of abstract ideas (mathematical concepts; certain methods of organizing human activity; mental processes)? Step 2A, Prong 2: does the claim integrate the abstract idea into a practical application (a real-world application)?; Step 2B: if not, does it add a specific limitation beyond what is well-understood, routine, conventional?; 2019 guidance provided more examiner structure but has not dramatically changed allowance rates for pure business method claims; PTAB COVERED BUSINESS METHOD REVIEW (CBM): AIA created a special review proceeding for business method patents (CBM review); available for 'financial product or service' patents; CBM REVIEW STATISTICS: high invalidation rate — majority of CBM petitions resulted in claim cancellation; majority of § 101 challenges in CBM were successful; CBM SUNSET: the CBM review program expired March 16, 2020 (9 years after AIA); no new CBM petitions can be filed; pending CBMs were completed; POST-CBM ALTERNATIVES: IPR still available for prior art challenges; PGR available within 9 months of grant; district court § 101 motions remain the primary route for challenging business method patents; IMPACT ON BUSINESS METHOD PATENT FILINGS: filings in TC 3600 dropped after Alice as applicants focused on more technically oriented claims; software companies have adapted to draft claims emphasizing technical improvements.