Alice Rejection Response

The response framework follows the 2019 USPTO Revised Guidance structure: STEP 0 — READ THE REJECTION CAREFULLY: identify exactly which step the examiner rejected at (Prong 1 or Prong 2 of Step 2A; or Step 2B); identify which abstract idea grouping the examiner cited (mathematical concept; mental process; certain methods of organizing human activity); determine if the examiner correctly identified the abstract idea or is applying a strained interpretation of the claim; CHECK: many § 101 rejections are boilerplate — they may not correctly analyze the specific claims; STEP 1 — DETERMINE IF THE CLAIMS EVEN RECITE AN ABSTRACT IDEA: under the 2019 Revised Guidance, examine whether the claim recites a concept in one of the three specific groupings: mathematical concept (formula; equation; calculation; mathematical relationship); mental process (something that can be practically performed in the human mind or with paper and pencil); certain methods of organizing human activity (economic practices; commercial interactions; managing relationships or behavior); if the claim does not fall into any of these three categories → argue the claim is NOT directed to an abstract idea → eligible; STEP 2 — IF ABSTRACT IDEA FOUND, ASSESS PRACTICAL APPLICATION: even if the claim recites an abstract idea, argue it integrates the abstract idea into a practical application; PRACTICAL APPLICATION INDICATORS (MPEP 2106.05): improvement to the functioning of a computer or other technology; reflects a particular practical application of the abstract idea; applies or uses the abstract idea in some other meaningful way beyond generally linking it to the claimed field; particular machine integral to the claim (not merely a general-purpose computer); transformation or reduction of a particular article; medical/diagnostic claim applying natural relationship in a meaningful treatment step; STEP 3 — IF NO PRACTICAL APPLICATION, ASSESS SIGNIFICANTLY MORE: additional elements beyond the abstract idea; specific non-routine; unconventional technical steps; non-generic hardware or software specifically configured for a technical purpose.

Certain arguments consistently succeed at the USPTO and Federal Circuit: ARGUMENT 1 — TECHNICAL IMPROVEMENT TO COMPUTER TECHNOLOGY: the strongest Alice argument; the claims are directed to a specific technical improvement to the functioning of the computer system itself; this argument is supported by: Enfish, LLC v. Microsoft (Fed. Cir. 2016): claims to a 'self-referential' database table improved computer memory efficiency and search speed; eligible because they improved the functioning of the computer; DDR Holdings v. Hotels.com (Fed. Cir. 2014): patent-eligible because claims addressed an Internet-specific problem in a way that was not merely applying an offline concept to the Internet; McRO, Inc. v. Bandai Namco Entertainment (Fed. Cir. 2016): specific rules for automatically synchronizing animated characters' lip movements to audio were eligible — the ordered combination produced a technical improvement to animation; Core Wireless Licensing v. LG Electronics (Fed. Cir. 2018): claims to a specific improved user interface for small-screen devices were eligible technical improvements; HOW TO MAKE THIS ARGUMENT: articulate in the response what specific technical problem the claims solve; describe the specific technical improvement (reduced computation; improved memory usage; faster processing; reduced network traffic; better security); include citations to the specification sections that describe the technical improvement; distinguish from cases that merely automate an existing process; ARGUMENT 2 — SPECIFIC TECHNICAL ELEMENTS NOT PERFORMABLE IN THE HUMAN MIND: if the method involves data processing at speeds or scales impossible without a computer, it is not a 'mental process'; argue that the specific technical operations claimed cannot be practically performed by a human mind; example: 'real-time processing of 1 million network packets per second to identify anomalies' cannot be done in the human mind; ARGUMENT 3 — TRANSFORMATION OF SPECIFIC ARTICLE: the claimed method transforms specific real-world data (video frames; medical images; network packets; sensor readings) in a technically specific way.

When arguments alone are insufficient, specific claim amendments can overcome Alice rejections: AMENDMENT APPROACH 1 — ADD SPECIFIC TECHNICAL IMPROVEMENT LANGUAGE: if the specification describes a technical improvement but the claims did not capture it, amend to add the specific technical improvement; EXAMPLE: add 'wherein execution of the method reduces memory allocation by at least 30% compared to prior art approaches by performing in-place operations on a circular buffer'; the specific technical improvement language ties the claim to the specification's technical disclosure; NOTE: the amendment must be supported by the specification (§ 132 no new matter); AMENDMENT APPROACH 2 — ADD NON-GENERIC HARDWARE SPECIFICITY: replace 'a processor' with specific processor types that are integral to the claimed invention; 'a graphics processing unit (GPU) configured to parallelize the matrix multiplication operations'; 'a field-programmable gate array (FPGA) implementing the filtering algorithm in hardware logic'; 'a neural processing unit (NPU) configured to perform sparse matrix operations'; these hardware elements must not be merely 'incidental' to the abstract idea; AMENDMENT APPROACH 3 — ADD SPECIFIC DATA TYPES AND STRUCTURES: specify what type of data is being processed (not just 'data' or 'information'); 'video frames at 4K resolution captured at 120 fps'; 'medical imaging data in DICOM format'; 'network packets in HTTPS encapsulated format'; 'sensor data from an accelerometer sampled at 1 kHz'; AMENDMENT APPROACH 4 — ADD ORDERED TECHNICAL STEPS: if the claim had steps in a non-specific order, add ordering language that reflects the technical dependency; specify how the output of one step feeds the next; the ordered combination may be non-obvious even if each step is individually known; AMENDMENT APPROACH 5 — ADD MEANS OF ACHIEVING THE RESULT: rather than claiming the result, claim the specific technical means of achieving it; NOT: 'generating a secure communication channel'; YES: 'establishing a mutual TLS 1.3 handshake using elliptic-curve Diffie-Hellman key exchange with a shared session key having at least 256-bit entropy'.

Berkheimer v. HP Inc. (Fed. Cir. 2018) introduced an important factual component to Alice analysis: THE BERKHEIMER HOLDING: Berkheimer v. HP Inc. (Fed. Cir. 2018): whether additional claim elements are 'well-understood; routine; and conventional' is a question of FACT — not law; the Federal Circuit reversed the district court's eligibility ruling because there was a genuine dispute of material fact about whether the claimed elements were conventional; IMPACT ON PROSECUTION: prior to Berkheimer, examiners routinely stated that computer implementation steps are conventional and therefore not 'significantly more'; after Berkheimer, this must be supported by EVIDENCE (not just an examiner's conclusory statement); USPTO MEMORANDUM (April 19, 2018): the USPTO issued a memorandum clarifying that examiners must now provide evidentiary support for assertions that additional claim elements are well-understood; routine; and conventional; USING BERKHEIMER IN A RESPONSE: if the examiner asserts that the additional elements (beyond the abstract idea) are merely conventional, challenge this assertion: ask the examiner to provide evidence (prior art; official notice) that the specific claimed combination is well-understood, routine, and conventional; if the examiner cannot point to evidence, the § 101 rejection is improperly supported; AFFIRMATIVE USE OF BERKHEIMER: submit a § 1.132 declaration from an inventor or technical expert stating that the additional technical elements were NOT well-understood, routine, or conventional at the time the application was filed; the declaration creates a factual dispute that must be resolved in the applicant's favor (or taken to PTAB); EXAMPLE: 'the use of a self-modifying hash table with adaptive collision resolution was not a well-understood or conventional technique in the database field at the time of filing as evidenced by [technical reference showing the novelty].'

The decision to appeal rather than amend depends on the specific facts and strategic context: FACTORS FAVORING APPEAL: CLAIM SCOPE IS CRITICAL: if amending the claims to overcome the § 101 rejection would narrow them so much that they lose commercial value, preserving the broad claim through appeal may be the better strategy; EXAMINER IS WRONG: if the examiner has mischaracterized the abstract idea, failed to consider the practical application, or ignored the technical improvement, appeal allows correction of the legal error; FAVORABLE FEDERAL CIRCUIT PRECEDENT: if there are Federal Circuit cases with highly similar claims that were found eligible (Enfish; DDR Holdings; McRO; Core Wireless), appeal is strong; PURE LEGAL QUESTION: if the eligibility question is a pure matter of law (no factual dispute), PTAB and courts may resolve it more favorably than an examiner; FACTORS FAVORING AMENDMENT OVER APPEAL: CLIENT NEEDS PATENT QUICKLY: appeal takes 1-2 years at PTAB; if the client needs the patent issued soon, amendment and allowance is faster; AMENDMENT CAN PRESERVE ADEQUATE SCOPE: if a narrowing amendment still covers the commercially important embodiments, amendment is more efficient than appeal; BERKHEIMER FACTUAL DISPUTE: if the issue is whether elements are conventional (a factual question), PTAB may not resolve it better than the examiner; consider a § 1.132 declaration to create the factual record; APPEAL PROCEDURE: file Notice of Appeal ($860 small entity; $1,000 brief fee); pre-appeal brief conference is available (2-page brief; 3-examiner panel; resolves ~40% of cases; worth trying before full appeal); file Appeal Brief (60 days from notice); PTAB issues a decision; Federal Circuit appeal available; PRE-APPEAL CONFERENCE STRATEGY: the pre-appeal brief conference is often underused for § 101 rejections; a well-crafted 2-page brief arguing the examiner misapplied the 2019 Revised Guidance can often persuade a conference panel to allow examination to continue.