AI & ML · § 101 Patent Eligibility
Machine Learning Patents
Neural networks, training methods, and inference systems are patentable — but Alice § 101 rejections are the dominant obstacle. Claim strategies that survive examination, global jurisdictional differences, and the patents-vs-trade-secrets calculus for AI companies.
The bottom line
ML inventions are patentable when claims are tied to a specific technical problem solved by specific technical means producing a concrete technical result. A claim to “train a neural network” is abstract math — rejected. A claim to “a system for detecting turbine blade fatigue using a recurrent neural network trained on 10 kHz vibration data” is a concrete technical application — eligible. The 2019 USPTO Revised Guidance and cases like Enfish and McRO form the practical framework.
Claim Strategies
Five approaches that survive § 101 analysis
Each of these strategies addresses the core Alice problem differently. The best ML patent applications typically combine several — using system claims with hardware anchors, method claims tied to specific data pipelines, and dependent claims adding implementation details as fallback positions.
Strategy 1
Tie the ML model to a specific technical problem
A system for detecting anomalies in network traffic, comprising: a neural network trained on packet-level timing features to classify traffic sequences as malicious or benign...
Why it works: Framing the claim around a concrete technical problem (network intrusion detection) rather than an abstract mathematical process anchors it to a 'practical application' under Alice Step 2A, Prong 2. The patent does not merely claim the math — it claims a specific application of ML to a specific domain.
Strategy 2
Claim the trained model as a system with specific parameters
A computer system comprising: a non-transitory memory storing model weights of a transformer-based neural network trained to minimize cross-entropy loss on a dataset of [X], the model weights encoding learned associations between [Y] and [Z]...
Why it works: A saved, trained model is a specific machine configuration — not just math. Claiming the weights, architecture, and the specific learned behavior ties the claim to a concrete instantiation rather than an abstract category of algorithms.
Strategy 3
Describe the training data characteristics concretely
...wherein the training set comprises at least 100,000 labeled examples each including a [specific feature], and wherein the neural network is trained using stochastic gradient descent with a batch size of 64 and a learning rate schedule that decays from 0.001 to 0.0001 over 50 epochs...
Why it works: Specificity in training methodology, data characteristics, and hyperparameters distinguishes the claim from a generic 'train a neural network' description. It also strengthens the written-description and enablement analysis — a specification describing these details is easier to defend.
Strategy 4
Claim the data pipeline and preprocessing as part of the invention
A method comprising: receiving sensor data from [X]; normalizing the data by subtracting the mean and dividing by the standard deviation computed from a sliding window of 60 seconds; inputting the normalized data into a convolutional neural network having [N] layers; outputting a classification label...
Why it works: Data preprocessing, feature engineering, and integration with hardware sensors are often the genuinely novel parts of an ML system. Claiming the full pipeline — from raw input through preprocessing through model through output — makes the claim more concrete and harder to design around.
Strategy 5
Use system claims with hardware anchors
A system comprising: one or more processors; memory storing instructions that, when executed, cause the processors to: receive image data from a depth sensor; apply a convolutional neural network having weights pre-trained on a dataset of [X]; output a 3D mesh...
Why it works: System claims with specific hardware components (sensor, processor, memory) are more resistant to Alice rejections than pure method claims. The 'when executed' language is standard but the hardware components must be real constraints, not mere 'apply it on a computer' drafting.
§ 101 Pitfalls
ML claim patterns that regularly fail
These claim patterns draw § 101 rejections at the USPTO and invalidity challenges in litigation. Recognizing them early — before filing — saves years of prosecution or a failed enforcement campaign.
Pure mathematical algorithms
A claim to 'a method of computing a gradient using backpropagation' is just math — it is an abstract idea per se. Backpropagation is a mathematical procedure that predates modern deep learning and is not patentable as such. The same applies to loss functions, activation functions, and optimization algorithms described without application to a specific technical problem.
Generic 'apply it on a computer' claims
Simply reciting that an abstract mathematical process (like regression, clustering, or classification) runs 'on a computer' or 'using a processor' does not confer patent eligibility under Alice. Alice Corp. v. CLS Bank International (2014) specifically addressed this — adding generic computer implementation to an abstract idea is not enough.
Naturally occurring data relationships
A model that learns naturally occurring correlations in data — e.g., 'a model trained on medical records that predicts disease outcomes' — may be challenged as describing natural phenomena (the statistical relationships in patient data). The claim needs to focus on the specific technical implementation, not just the discovered correlation.
Business method applications of standard ML
Using a neural network to optimize ad bids, predict churn, or score leads — without any technical innovation in the ML itself or in how it integrates with hardware — often fails § 101 because the abstract idea is 'optimize a business process' and ML is just the mechanism. The technical improvement must be in the ML system, not just the business outcome.
Global Landscape
AI/ML patent eligibility by jurisdiction
Alice is a U.S. problem. Other major patent offices use different frameworks, and understanding them shapes where to file and how to sequence prosecution to use foreign allowances for PPH at the USPTO.
United States
Alice/Mayo two-step: Step 1 — is the claim directed to an abstract idea, natural phenomenon, or law of nature? Step 2A — does it integrate a practical application (Prong 2) or add an inventive concept beyond a generic computer (Prong 2)? The 2019 Revised Guidance created structured analysis, but rejections remain common. Success rate for AI/ML applications has improved but rejections at Step 2A remain the primary obstacle.
Europe (EPO)
Technical character is the key — the EPO requires that the claim solves a 'technical problem' by 'technical means.' An ML model that produces a technical effect (better image compression, faster drug simulation, more efficient resource allocation in a technical system) can be patentable. Business method exclusions are strict, but well-framed ML claims in technical domains (industrial, medical, scientific) fare better than at the USPTO.
China (CNIPA)
China's patent examination guidelines for AI have evolved significantly since 2017 amendments. Functional claims using 'modules' or 'units' must be grounded in technical features. Neural network architectures, training methods, and inference systems are broadly eligible if tied to a technical solution to a technical problem. CNIPA has become more AI-patent friendly, and Chinese AI patent filings now exceed U.S. filings by volume.
Japan (JPO)
Japan has broad patentability for software and AI-implemented inventions if the claimed software controls hardware or produces information in a technically meaningful way. The JPO's 2019 Examination Guidelines for AI-related inventions explicitly describe how to claim neural networks, training methods, and learned models. PPH between the JPO and USPTO makes a Japanese allowance highly valuable as a foundation for U.S. prosecution.
FAQ
Frequently asked questions
Can machine learning models be patented?
Yes — machine learning models, training methods, inference systems, and AI-powered applications can be patented in the United States, Europe, China, Japan, and most other major patent jurisdictions. But they face specific eligibility challenges that other types of inventions do not. In the United States, the central obstacle is 35 U.S.C. § 101 patent-eligibility under the Alice/Mayo framework: courts and the USPTO examine whether the claims are directed to an abstract idea (which includes mathematical concepts, mental processes, and certain methods of organizing human activity) and, if so, whether the claims include an 'inventive concept' that goes beyond applying the abstract idea using a generic computer. A claim to 'train a neural network to classify inputs' is essentially a claim to a mathematical procedure — an abstract idea — and is not patentable as stated. But a claim to 'a system for detecting anomalous sensor readings in a wind turbine, comprising a recurrent neural network trained on 10 Hz vibration data, that outputs a maintenance alert when a learned threshold is exceeded' is far more concrete — it is directed to a specific technical problem (predictive maintenance), with specific technical means (recurrent neural network, specific input data, specific output), in a specific application domain (turbines). The line between 'abstract ML math' and 'patentable ML application' runs through the specificity and technicality of the claim. The USPTO's 2019 Revised Guidance on Subject Matter Eligibility provides a structured framework, and AI/ML applications have had improving (though still challenging) success rates since then.
What makes an ML patent claim survive Alice § 101 analysis?
Under the USPTO's 2019 Revised Guidance (implementing Alice/Mayo), a claim survives § 101 if: (Step 1) It is in a statutory category — process, machine, manufacture, or composition of matter — which ML system claims easily satisfy. (Step 2A, Prong 1) If it recites a 'judicial exception' (abstract idea, natural phenomenon, law of nature). Most ML claims recite some mathematical concept — neural networks are math, loss functions are math, optimization is math — so they often reach Prong 1 analysis. (Step 2A, Prong 2) Whether the claim 'integrates the judicial exception into a practical application' — this is where the key analysis happens. Indicators of integration into a practical application include: the claim applies the mathematical concept to 'effect a particular treatment or prophylaxis for a disease or medical condition' (medical diagnostics is a strong area); reflects an 'improvement in the functioning of a computer or other technology' (a more efficient neural network training algorithm that reduces computation); uses the mathematical concept 'with a particular machine' (a neural network combined with specific sensors, hardware, or actuators); or 'transforms or reduces a particular article to a different state or thing.' (Step 2B, fallback) If Step 2A Prong 2 fails, whether there is an inventive concept beyond well-understood, routine, conventional activity. Practically: the claims most likely to survive describe (1) a specific technical improvement (faster inference, lower memory, better accuracy on a defined task), (2) in a specific application domain (medical imaging, industrial control, network security), (3) with specific technical means (model architecture details, training data characteristics, hardware integration), and (4) producing a specific, concrete technical result. Boilerplate 'apply it to a computer' drafting fails; genuine technical specificity survives.
Can you patent a trained neural network model?
This is an evolving and unsettled area. A trained neural network model — the artifact consisting of a specific architecture with learned weight values — is arguably a 'machine' or 'manufacture' under § 101: it is a physical configuration of data stored in memory that causes a computer to perform specific functions. Several lines of argument support its patentability: (1) A trained model with specific weights is a machine in a particular configuration — analogous to a circuit with specific component values, not a generic computer. (2) The model encodes a specific, non-obvious learned function (the weights are not derivable by routine math — they emerge from training on specific data). (3) Case law on software patents (Enfish, McRO, Berkheimer) supports eligibility when the claims are directed to a specific, concrete technical improvement rather than an abstract result. However: (4) Competitors can potentially design around or reverse-engineer a claimed model architecture; weights are often proprietary as trade secrets, not patents. (5) The § 101 analysis for claims reciting 'a model comprising weights' may still hit abstract-idea objections if framed too broadly. Best practice: claim the trained model as part of a system — 'a memory storing weights of a neural network trained to [specific task] and a processor configured to execute the network' — rather than as a standalone data artifact. Include method claims directed to the training process with specific training data characteristics, and system claims anchored to specific hardware. This multi-claim strategy protects different aspects of the ML invention and increases the likelihood that at least some claims survive examination.
How should companies protect AI inventions — patents or trade secrets?
The patents-versus-trade-secrets question is more acute for AI/ML than for most technologies, because the core of an ML model — the trained weights — is typically undetectable in the output. A model's weights cannot be reverse-engineered from its predictions in most practical settings, making trade secret protection naturally strong for the model itself. The strategic calculus: Patent when (1) the inventive method is visible in the output or in the deployed system — i.e., a competitor using the same approach can be detected, which is necessary to enforce a patent. (2) You want the legal right to exclude competitors who independently develop the same approach, not just protect your specific implementation. (3) The invention is in the training data pipeline, hardware integration, or application domain in ways that are observable and enforceable. (4) You need 'patent pending' status for licensing leverage, investor valuation, or competitive signaling. Protect as trade secret when (1) the model weights themselves are the invention and they are not inferable from output. (2) The training data, data preprocessing steps, and feature engineering are novel but not observable externally. (3) The competitive advantage derives from the specific trained model, not from the architectural choices. (4) The marginal cost of independent invention by a competitor is high — if it took your team 3 years of specialized work to develop, trade secret protection plus a head start may be more valuable than a patent that discloses your approach. Many AI companies do both: patent the system architecture, application methods, and training pipelines (observable and enforceable), while protecting trained model weights, proprietary datasets, and data preprocessing as trade secrets.
Who owns an AI-generated invention?
As of 2024, the USPTO requires that every patent application name a human inventor — an AI system cannot be listed as an inventor, and a patent naming only an AI as inventor would be invalid. This rule was established through a series of USPTO decisions rejecting applications filed by Stephen Thaler naming his DABUS AI system as inventor (2020–2022), affirmed by the Federal Circuit in Thaler v. Vidal (Fed. Cir. 2022), and confirmed by the Supreme Court declining to review the case in 2023. The legal status of AI-generated inventions where no human contributed to the conception is therefore: currently unpatentable in the U.S. under existing statute (35 U.S.C. § 100(f): 'inventor means the individual or, if a joint invention, the individuals collectively who invented or discovered the subject matter of the invention'). The USPTO issued guidance in February 2024 (following Executive Order 14110 on AI) clarifying that AI-assisted inventions — where humans use AI as a tool but humans contribute to the conception — can be patented, with the human contributors listed as inventors. The inventorship determination focuses on who contributed to the conception of the claimed subject matter; using AI to generate, screen, or refine candidates does not automatically make the AI an inventor if humans directed the process and evaluated the results. Companies using AI tools in R&D should document human decision-making in the inventive process — which AI outputs were selected, how they were modified, which problems the humans defined — to support inventorship claims. This is an evolving area: the USPTO has launched rulemaking on AI and inventorship, and Congressional action is possible.
Related Guides