MPEP § 2106.04(d) — Integration of a Judicial Exception Into A Practical Application (Annotated Rules)

§2106.04(d) Integration of a Judicial Exception Into A Practical Application

USPTO MPEP version: BlueIron's Update: 2026-01-17

This page consolidates and annotates all enforceable requirements under MPEP § 2106.04(d), including statutory authority, regulatory rules, examiner guidance, and practice notes. It is provided as guidance, with links to the ground truth sources. This is information only, it is not legal advice.

Integration of a Judicial Exception Into A Practical Application

This section addresses Integration of a Judicial Exception Into A Practical Application. Contains: 5 guidance statements, 3 permissions, and 15 other statements.

Key Rules

Topic

Patent Eligibility

23 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-9d1e9629e266298fd6880082]
Principles vs Practical Applications Must Be Integrated
Note:
The rule requires distinguishing between principles themselves, which are not patent eligible, and their integration into practical applications, which are patent eligible.

The Supreme Court has long distinguished between principles themselves (which are not patent eligible) and the integration of those principles into practical applications (which are patent eligible). See, e.g., Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66, 80, 84, 101 USPQ2d 1961, 1968-69, 1970 (2012) (noting that the Court in Diamond v. Diehr found ‘‘the overall process patent eligible because of the way the additional steps of the process integrated the equation into the process as a whole,’’ but the Court in Gottschalk v. Benson ‘‘held that simply implementing a mathematical principle on a physical machine, namely a computer, was not a patentable application of that principle’’). Similarly, in a growing body of decisions, the Federal Circuit has distinguished between claims that are ‘‘directed to’’ a judicial exception (which require further analysis to determine their eligibility) and those that are not (which are therefore patent eligible), e.g., claims that improve the functioning of a computer or other technology or technological field. See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981); Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972). See, e.g., MPEP § 2106.06(b) (summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016), McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 120 USPQ2d 1091 (Fed. Cir. 2016), and other cases that were eligible as improvements to technology or computer functionality instead of being directed to abstract ideas).

Jump to MPEP SourcePatent EligibilityStep 2A Prong 1 – Judicial Exception
MPEP GuidancePermittedAlways
[mpep-2106-04-d-04ac579bc6a0dbd07125e4cd]
Step 2A Prong Two: Practical Application Check for Eligibility
Note:
Determines if the claim integrates a judicial exception into a practical application, requiring further analysis or concluding eligibility.
In the context of the flowchart in MPEP § 2106, subsection III, Step 2A Prong Two determines whether:
  • • The claim as a whole integrates the judicial exception into a practical application, in which case the claim is not directed to a judicial exception (Step 2A: NO) and is eligible at Pathway B. This concludes the eligibility analysis.
  • • The claim as a whole does not integrate the exception into a practical application, in which case the claim is directed to the judicial exception (Step 2A: YES), and requires further analysis under Step 2B (where it may still be eligible if it amounts to an inventive concept). See MPEP § 2106.05 for discussion of Step 2B.
Jump to MPEP SourcePatent Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-d8c543e118801fb6677bdcaf]
Claim as a Whole Integrates Judicial Exception into Practical Application
Note:
The claim integrates the judicial exception into a practical application, concluding it is not directed to an exception and is eligible at Pathway B.

In the context of the flowchart in MPEP § 2106, subsection III, Step 2A Prong Two determines whether • The claim as a whole integrates the judicial exception into a practical application, in which case the claim is not directed to a judicial exception (Step 2A: NO) and is eligible at Pathway B. This concludes the eligibility analysis.

Jump to MPEP SourcePatent Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-f9873710fcf4b88b43e165b2]
Claim Not Integrated into Practical Application Requires Step 2B Analysis
Note:
If the claim as a whole does not integrate the judicial exception into a practical application, further analysis under Step 2B is required to determine eligibility.

In the context of the flowchart in MPEP § 2106, subsection III, Step 2A Prong Two determines whether • The claim as a whole does not integrate the exception into a practical application, in which case the claim is directed to the judicial exception (Step 2A: YES), and requires further analysis under Step 2B (where it may still be eligible if it amounts to an inventive concept). See MPEP § 2106.05 for discussion of Step 2B.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-340299f16319db1153764ddf]
Evaluating Additional Elements for Patent Eligibility
Note:
The Supreme Court and Federal Circuit have identified multiple considerations to determine if additional elements make a claim patent-eligible.

The Supreme Court and Federal Circuit have identified a number of considerations as relevant to the evaluation of whether the claimed additional elements demonstrate that a claim is directed to patent-eligible subject matter. The list of considerations here is not intended to be exclusive or limiting. Additional elements can often be analyzed based on more than one type of consideration and the type of consideration is of no import to the eligibility analysis. Additional discussion of these considerations, and how they were applied in particular judicial decisions, is provided in MPEP § 2106.05(a) through (c) and MPEP § 2106.05(e) through (h).

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-3d32a8c97f48c37b984b963d]
Considerations for Patent Eligibility Not Exclusive
Note:
The list of factors to evaluate patent eligibility is not exhaustive, and additional elements can be analyzed using multiple types of considerations.

The Supreme Court and Federal Circuit have identified a number of considerations as relevant to the evaluation of whether the claimed additional elements demonstrate that a claim is directed to patent-eligible subject matter. The list of considerations here is not intended to be exclusive or limiting. Additional elements can often be analyzed based on more than one type of consideration and the type of consideration is of no import to the eligibility analysis. Additional discussion of these considerations, and how they were applied in particular judicial decisions, is provided in MPEP § 2106.05(a) through (c) and MPEP § 2106.05(e) through (h).

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-70d08d94267f208f8186da4f]
Multiple Considerations for Additional Element Eligibility
Note:
Claims can be analyzed using various types of considerations without affecting the eligibility analysis.

The Supreme Court and Federal Circuit have identified a number of considerations as relevant to the evaluation of whether the claimed additional elements demonstrate that a claim is directed to patent-eligible subject matter. The list of considerations here is not intended to be exclusive or limiting. Additional elements can often be analyzed based on more than one type of consideration and the type of consideration is of no import to the eligibility analysis. Additional discussion of these considerations, and how they were applied in particular judicial decisions, is provided in MPEP § 2106.05(a) through (c) and MPEP § 2106.05(e) through (h).

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-73fb2925e6722476a6cf8d14]
Considerations for Patent Eligibility Evaluation
Note:
Provides details on evaluating additional elements in patent eligibility analysis, as discussed in MPEP sections 2106.05(a)-(c) and (e)-(h).

The Supreme Court and Federal Circuit have identified a number of considerations as relevant to the evaluation of whether the claimed additional elements demonstrate that a claim is directed to patent-eligible subject matter. The list of considerations here is not intended to be exclusive or limiting. Additional elements can often be analyzed based on more than one type of consideration and the type of consideration is of no import to the eligibility analysis. Additional discussion of these considerations, and how they were applied in particular judicial decisions, is provided in MPEP § 2106.05(a) through (c) and MPEP § 2106.05(e) through (h).

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-30b66b7883e72fd84bb48513]
Step 2A Prong Two Evaluates Eligibility Without Considering Routine Activity
Note:
Evaluates a claim's eligibility by considering judicial exceptions without assessing whether additional elements are well-understood, routine, or conventional activities.

Step 2A Prong Two is similar to Step 2B in that both analyses involve evaluating a set of judicial considerations to determine if the claim is eligible. See MPEP §§ 2106.05(a) through (h) for the list of considerations that are evaluated at Step 2B. Although most of these considerations overlap (i.e., they are evaluated in both Step 2A Prong Two and Step 2B), Step 2A specifically excludes consideration of whether the additional elements represent well-understood, routine, conventional activity. Accordingly, in Step 2A Prong Two, examiners should ensure that they give weight to all additional elements, whether or not they are conventional, when evaluating whether a judicial exception has been integrated into a practical application. Additional elements that represent well-understood, routine, conventional activity may integrate a recited judicial exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceRecommendedAlways
[mpep-2106-04-d-323d9e03751458e9d2126644]
Weight Given to All Additional Elements During Step 2A Prong Two Evaluation
Note:
Examiners must consider all additional elements, regardless of whether they are conventional, when assessing if a judicial exception is integrated into a practical application during Step 2A Prong Two.

Step 2A Prong Two is similar to Step 2B in that both analyses involve evaluating a set of judicial considerations to determine if the claim is eligible. See MPEP §§ 2106.05(a) through (h) for the list of considerations that are evaluated at Step 2B. Although most of these considerations overlap (i.e., they are evaluated in both Step 2A Prong Two and Step 2B), Step 2A specifically excludes consideration of whether the additional elements represent well-understood, routine, conventional activity. Accordingly, in Step 2A Prong Two, examiners should ensure that they give weight to all additional elements, whether or not they are conventional, when evaluating whether a judicial exception has been integrated into a practical application. Additional elements that represent well-understood, routine, conventional activity may integrate a recited judicial exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-f97b241ecc6341eeb7a784a5]
Additional Elements May Integrate Judicial Exception into Practical Application
Note:
Examiners must consider all additional elements, even if they are well-understood, routine, or conventional activities, when determining if a judicial exception is integrated into a practical application.

Step 2A Prong Two is similar to Step 2B in that both analyses involve evaluating a set of judicial considerations to determine if the claim is eligible. See MPEP §§ 2106.05(a) through (h) for the list of considerations that are evaluated at Step 2B. Although most of these considerations overlap (i.e., they are evaluated in both Step 2A Prong Two and Step 2B), Step 2A specifically excludes consideration of whether the additional elements represent well-understood, routine, conventional activity. Accordingly, in Step 2A Prong Two, examiners should ensure that they give weight to all additional elements, whether or not they are conventional, when evaluating whether a judicial exception has been integrated into a practical application. Additional elements that represent well-understood, routine, conventional activity may integrate a recited judicial exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-5e02967c74ee78814f6aa70d]
Specific Claim Limitations Are Relevant to Step 2A Prong Two Evaluation
Note:
The specificity of claim limitations is relevant when evaluating whether a claim uses a particular machine, transformation, or merely instructs the application of an exception.

In addition, a specific way of achieving a result is not a stand-alone consideration in Step 2A Prong Two. However, the specificity of the claim limitations is relevant to the evaluation of several considerations including the use of a particular machine, particular transformation and whether the limitations are mere instructions to apply an exception. See MPEP §§ 2106.05(b), 2106.05(c), and 2106.05(f). For example, in Parker v. Flook, 437 U.S. 584, 198 USPQ 193 (1978), the Supreme Court noted that the “patent application does not purport to explain how to select the appropriate margin of safety, the weighting factor, or any of the other variables” in the claimed mathematical formula, “[n]or does it purport to contain any disclosure relating to the chemical processes at work, the monitoring of process variables, or the means of setting off an alarm or adjusting an alarm system.” 437 U.S. at 586, 198 USPQ at 195. The Court found this failure to explain any specifics of how to use the claimed formula informative when deciding that the additional elements in the claim were insignificant post-solution activity and thus not meaningful enough to render the claim eligible. 437 U.S. at 589-90, 198 USPQ at 197.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-78226d6a078eb5dbc45c89eb]
Claim Must Explain Variables Used in Formula
Note:
The claim must provide a detailed explanation of the variables used in any mathematical formula to be considered eligible for patent protection.

In addition, a specific way of achieving a result is not a stand-alone consideration in Step 2A Prong Two. However, the specificity of the claim limitations is relevant to the evaluation of several considerations including the use of a particular machine, particular transformation and whether the limitations are mere instructions to apply an exception. See MPEP §§ 2106.05(b), 2106.05(c), and 2106.05(f). For example, in Parker v. Flook, 437 U.S. 584, 198 USPQ 193 (1978), the Supreme Court noted that the “patent application does not purport to explain how to select the appropriate margin of safety, the weighting factor, or any of the other variables” in the claimed mathematical formula, “[n]or does it purport to contain any disclosure relating to the chemical processes at work, the monitoring of process variables, or the means of setting off an alarm or adjusting an alarm system.” 437 U.S. at 586, 198 USPQ at 195. The Court found this failure to explain any specifics of how to use the claimed formula informative when deciding that the additional elements in the claim were insignificant post-solution activity and thus not meaningful enough to render the claim eligible. 437 U.S. at 589-90, 198 USPQ at 197.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-d16840fd7071f6c35523ac5a]
Claim Limitations Must Be Sufficiently Specific to Render Eligible
Note:
The claim limitations must provide specific details on how to use the formula, otherwise, additional elements are considered insignificant post-solution activity and do not render the claim eligible.

In addition, a specific way of achieving a result is not a stand-alone consideration in Step 2A Prong Two. However, the specificity of the claim limitations is relevant to the evaluation of several considerations including the use of a particular machine, particular transformation and whether the limitations are mere instructions to apply an exception. See MPEP §§ 2106.05(b), 2106.05(c), and 2106.05(f). For example, in Parker v. Flook, 437 U.S. 584, 198 USPQ 193 (1978), the Supreme Court noted that the “patent application does not purport to explain how to select the appropriate margin of safety, the weighting factor, or any of the other variables” in the claimed mathematical formula, “[n]or does it purport to contain any disclosure relating to the chemical processes at work, the monitoring of process variables, or the means of setting off an alarm or adjusting an alarm system.” 437 U.S. at 586, 198 USPQ at 195. The Court found this failure to explain any specifics of how to use the claimed formula informative when deciding that the additional elements in the claim were insignificant post-solution activity and thus not meaningful enough to render the claim eligible. 437 U.S. at 589-90, 198 USPQ at 197.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-48ab954f9da7399d85425495]
Claim Limitations Must Be Sufficiently Specific to Avoid Being Mere Instructions
Note:
The claim limitations must provide enough detail to avoid being considered mere instructions for applying an abstract idea, particularly in Step 2A Prong Two of the patent eligibility analysis.

In addition, a specific way of achieving a result is not a stand-alone consideration in Step 2A Prong Two. However, the specificity of the claim limitations is relevant to the evaluation of several considerations including the use of a particular machine, particular transformation and whether the limitations are mere instructions to apply an exception. See MPEP §§ 2106.05(b), 2106.05(c), and 2106.05(f). For example, in Parker v. Flook, 437 U.S. 584, 198 USPQ 193 (1978), the Supreme Court noted that the “patent application does not purport to explain how to select the appropriate margin of safety, the weighting factor, or any of the other variables” in the claimed mathematical formula, “[n]or does it purport to contain any disclosure relating to the chemical processes at work, the monitoring of process variables, or the means of setting off an alarm or adjusting an alarm system.” 437 U.S. at 586, 198 USPQ at 195. The Court found this failure to explain any specifics of how to use the claimed formula informative when deciding that the additional elements in the claim were insignificant post-solution activity and thus not meaningful enough to render the claim eligible. 437 U.S. at 589-90, 198 USPQ at 197.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceRecommendedAlways
[mpep-2106-04-d-296f8368f59158c8a9fa7d42]
Claims Must Be Examined Separately for Eligibility
Note:
Examiners must assess each claim individually for patent eligibility based on its specific elements, not in relation to other claims.

Examiners should examine each claim for eligibility separately, based on the particular elements recited therein. Claims should not be judged to automatically stand or fall with similar claims in an application. For instance, one claim may be ineligible because it is directed to a judicial exception without amounting to significantly more, but another claim dependent on the first may be eligible because it recites additional elements that do amount to significantly more, or that integrate the exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceRecommendedAlways
[mpep-2106-04-d-c9c0c17d6cfea6b57a48a5fc]
Claims Must Be Examined Separately for Eligibility
Note:
Each claim must be evaluated independently for eligibility, even if similar to other claims in the application.

Examiners should examine each claim for eligibility separately, based on the particular elements recited therein. Claims should not be judged to automatically stand or fall with similar claims in an application. For instance, one claim may be ineligible because it is directed to a judicial exception without amounting to significantly more, but another claim dependent on the first may be eligible because it recites additional elements that do amount to significantly more, or that integrate the exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-80b03c9913f8730bc222542e]
Claims Should Be Examined Individually For Eligibility
Note:
Examiners should evaluate each claim separately for patent eligibility, even if similar claims are present in the same application.

Examiners should examine each claim for eligibility separately, based on the particular elements recited therein. Claims should not be judged to automatically stand or fall with similar claims in an application. For instance, one claim may be ineligible because it is directed to a judicial exception without amounting to significantly more, but another claim dependent on the first may be eligible because it recites additional elements that do amount to significantly more, or that integrate the exception into a practical application.

Jump to MPEP SourcePatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-c4817200f326d5735afc6690]
Claim as a Whole for Prong Two Analysis
Note:
Evaluate the claim by considering both the judicial exception and additional elements together to determine if they integrate the exception into a practical application.

The Prong Two analysis considers the claim as a whole. That is, the limitations containing the judicial exception as well as the additional elements in the claim besides the judicial exception need to be evaluated together to determine whether the claim integrates the judicial exception into a practical application. Because a judicial exception alone is not eligible subject matter, if there are no additional claim elements besides the judicial exception, or if the additional claim elements merely recite another judicial exception, that is insufficient to integrate the judicial exception into a practical application. However, the way in which the additional elements use or interact with the exception may integrate it into a practical application. Accordingly, the additional limitations should not be evaluated in a vacuum, completely separate from the recited judicial exception. Instead, the analysis should take into consideration all the claim limitations and how those limitations interact and impact each other when evaluating whether the exception is integrated into a practical application.

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-5bd4b4ad9bdac106faa883a6]
Claim Limitations Must Be Evaluated Together for Practical Application
Note:
The judicial exception and additional claim elements must be assessed collectively to determine if they integrate the exception into a practical application.

The Prong Two analysis considers the claim as a whole. That is, the limitations containing the judicial exception as well as the additional elements in the claim besides the judicial exception need to be evaluated together to determine whether the claim integrates the judicial exception into a practical application. Because a judicial exception alone is not eligible subject matter, if there are no additional claim elements besides the judicial exception, or if the additional claim elements merely recite another judicial exception, that is insufficient to integrate the judicial exception into a practical application. However, the way in which the additional elements use or interact with the exception may integrate it into a practical application. Accordingly, the additional limitations should not be evaluated in a vacuum, completely separate from the recited judicial exception. Instead, the analysis should take into consideration all the claim limitations and how those limitations interact and impact each other when evaluating whether the exception is integrated into a practical application.

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidancePermittedAlways
[mpep-2106-04-d-3ff0322489f5ef31f57b8715]
Claim Must Include Additional Elements
Note:
A claim integrating a judicial exception into a practical application requires additional elements that meaningfully use or interact with the exception.

The Prong Two analysis considers the claim as a whole. That is, the limitations containing the judicial exception as well as the additional elements in the claim besides the judicial exception need to be evaluated together to determine whether the claim integrates the judicial exception into a practical application. Because a judicial exception alone is not eligible subject matter, if there are no additional claim elements besides the judicial exception, or if the additional claim elements merely recite another judicial exception, that is insufficient to integrate the judicial exception into a practical application. However, the way in which the additional elements use or interact with the exception may integrate it into a practical application. Accordingly, the additional limitations should not be evaluated in a vacuum, completely separate from the recited judicial exception. Instead, the analysis should take into consideration all the claim limitations and how those limitations interact and impact each other when evaluating whether the exception is integrated into a practical application.

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceRecommendedAlways
[mpep-2106-04-d-76478131156efb297edc3a7f]
Additional Elements Should Not Be Evaluated Separately
Note:
The analysis of additional claim elements must consider their interaction with the judicial exception, not in isolation.

The Prong Two analysis considers the claim as a whole. That is, the limitations containing the judicial exception as well as the additional elements in the claim besides the judicial exception need to be evaluated together to determine whether the claim integrates the judicial exception into a practical application. Because a judicial exception alone is not eligible subject matter, if there are no additional claim elements besides the judicial exception, or if the additional claim elements merely recite another judicial exception, that is insufficient to integrate the judicial exception into a practical application. However, the way in which the additional elements use or interact with the exception may integrate it into a practical application. Accordingly, the additional limitations should not be evaluated in a vacuum, completely separate from the recited judicial exception. Instead, the analysis should take into consideration all the claim limitations and how those limitations interact and impact each other when evaluating whether the exception is integrated into a practical application.

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
MPEP GuidanceRecommendedAlways
[mpep-2106-04-d-436fab7a5edb655ceb7582cd]
All Claim Limitations Must Be Considered Together for Practical Application
Note:
When evaluating if a judicial exception is integrated into a practical application, all claim limitations must be analyzed together to determine their interaction and impact.

The Prong Two analysis considers the claim as a whole. That is, the limitations containing the judicial exception as well as the additional elements in the claim besides the judicial exception need to be evaluated together to determine whether the claim integrates the judicial exception into a practical application. Because a judicial exception alone is not eligible subject matter, if there are no additional claim elements besides the judicial exception, or if the additional claim elements merely recite another judicial exception, that is insufficient to integrate the judicial exception into a practical application. However, the way in which the additional elements use or interact with the exception may integrate it into a practical application. Accordingly, the additional limitations should not be evaluated in a vacuum, completely separate from the recited judicial exception. Instead, the analysis should take into consideration all the claim limitations and how those limitations interact and impact each other when evaluating whether the exception is integrated into a practical application.

Jump to MPEP SourcePatent EligibilityJudicial Exceptions to Eligibility
Topic

Claims Directed To

9 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-5f881fccf04dee4429ed3464]
Claims Must Integrate Abstract Ideas Through Specific Steps
Note:
Claims must integrate abstract ideas, such as virus screening, through specific steps that improve computer functionality to be eligible under the Alice/Mayo test.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-dfd807328b6ecff78608cd8a]
Claims Must Integrate Abstract Ideas Through Specific Steps
Note:
Claims must integrate abstract ideas, such as virus screening, through specific steps that improve computer functionality to be eligible under the Alice/Mayo test.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-b7f040ddafa3db65a7a273ed]
Security Profile Enables Protection Against Unknown Viruses and Obfuscated Code
Note:
The security profile identifies both hostile and potentially hostile operations, protecting users against previously unknown viruses and obfuscated code more effectively than traditional virus scanning.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-fcb0a059d0d6c6b5b228e5dc]
Security Profile Enables Flexible Virus Filtering and Customization
Note:
The security profile allows for more flexible virus filtering and greater user customization, improving computer functionality.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-5cd8de16b0f5f3b4b75d4ff1]
Claims Must Integrate Abstract Idea into Practical Application
Note:
The claims must integrate the abstract idea of virus screening with additional elements that improve computer functionality to be eligible.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-7673f6ce903ea9d0b61d4764]
Claims Must Describe Security Profile Benefits
Note:
The claims must describe how the security profile improves computer functionality to be eligible under Alice/Mayo test.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-977f73c19864bc81f9f40ddd]
Claims Must Integrate Abstract Ideas Into Practical Applications
Note:
The claims must integrate abstract ideas, such as virus screening, into practical applications by providing additional elements that improve computer functionality.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToPatent EligibilityClaim Subject Matter
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-d79cd38cd58efaa2a19e1023]
Claims Must Describe Security Profile Benefits
Note:
The claims must describe how the security profile improves computer functionality and integrates the abstract idea into a practical application.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-5511fd94e67b0e339a10d654]
Claims Not Directed to Abstract Idea
Note:
The claims must include additional elements that integrate the abstract idea into a practical application at Step 2A Prong Two of the Alice/Mayo test.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaims Directed ToClaim Subject MatterMethod/Process Claims
Topic

Process (Method)

6 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-b50c245d0f15ddc8208bbf04]
Physical Implementation Not a Guarantee for Eligibility
Note:
The mere physical implementation of an additional element does not ensure eligibility under the Alice/Mayo test.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Statutory Categories of InventionSequence Listing Format
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-2c743a477f43cebdd3899af2]
Mere Physical Implementation Does Not Guarantee Eligibility
Note:
The rule states that merely implementing a judicial exception in a physical form does not ensure patent eligibility under the Alice/Mayo test.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Statutory Categories of InventionSequence Listing Format
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-01a73bcd1bbd0f97695b00e9]
Mere Physical Implementation Does Not Ensure Eligibility
Note:
The physical nature of an additional element does not guarantee a process is eligible for patenting, as explained in Alice Corp. Pty. Ltd. v. CLS Bank Int’l.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Statutory Categories of InventionSequence Listing Format
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-8e1cfbb8da4d290f03b5370e]
Physical Steps Do Not Ensure Eligibility
Note:
The physical nature of steps in a process does not guarantee patent eligibility under the Alice/Mayo test.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Patent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-de9b069cc85cdce67d52f63b]
Non-Physical Elements Do Not Doom Claims Under Alice/Mayo Test
Note:
The presence of non-physical or intangible additional elements does not render claims ineligible under the Alice/Mayo test, as tangibility is not a necessary requirement for eligibility.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Statutory Categories of InventionSequence Listing Format
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-a5e1d2bb5fdc33a17a53d259]
Non-Physical Improvements Can Be Eligible
Note:
The presence of non-physical elements in a process does not disqualify it from being eligible if it improves an existing technological process.

It is notable that mere physicality or tangibility of an additional element or elements is not a relevant consideration in Step 2A Prong Two. As the Supreme Court explained in Alice Corp., mere physical or tangible implementation of an exception does not guarantee eligibility. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 224, 110 USPQ2d 1976, 1983-84 (2014) (“The fact that a computer ‘necessarily exist[s] in the physical, rather than purely conceptual, realm,’ is beside the point”). See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016) (steps of DNA amplification and analysis are not “sufficient” to render claim 1 patent eligible merely because they are physical steps). Conversely, the presence of a non-physical or intangible additional element does not doom the claims, because tangibility is not necessary for eligibility under the Alice/Mayo test. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016) (“that the improvement is not defined by reference to ‘physical’ components does not doom the claims”). See also McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1315, 120 USPQ2d 1091, 1102 (Fed. Cir. 2016), (holding that a process producing an intangible result (a sequence of synchronized, animated characters) was eligible because it improved an existing technological process).

Jump to MPEP SourceProcess (Method)Statutory Categories of InventionSequence Listing Format
Topic

Step 2A Prong 1 – Judicial Exception

2 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-d1d23dc206180f33d65c9273]
Claims Directed to Judicial Exception Require Further Analysis
Note:
The Federal Circuit requires further analysis for claims that are directed to a judicial exception, distinguishing them from those that improve computer or technological functioning.

The Supreme Court has long distinguished between principles themselves (which are not patent eligible) and the integration of those principles into practical applications (which are patent eligible). See, e.g., Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66, 80, 84, 101 USPQ2d 1961, 1968-69, 1970 (2012) (noting that the Court in Diamond v. Diehr found ‘‘the overall process patent eligible because of the way the additional steps of the process integrated the equation into the process as a whole,’’ but the Court in Gottschalk v. Benson ‘‘held that simply implementing a mathematical principle on a physical machine, namely a computer, was not a patentable application of that principle’’). Similarly, in a growing body of decisions, the Federal Circuit has distinguished between claims that are ‘‘directed to’’ a judicial exception (which require further analysis to determine their eligibility) and those that are not (which are therefore patent eligible), e.g., claims that improve the functioning of a computer or other technology or technological field. See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981); Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972). See, e.g., MPEP § 2106.06(b) (summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016), McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 120 USPQ2d 1091 (Fed. Cir. 2016), and other cases that were eligible as improvements to technology or computer functionality instead of being directed to abstract ideas).

Jump to MPEP SourceStep 2A Prong 1 – Judicial ExceptionPatent Eligibility
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-de915441b846b52a1c4c9a4b]
Improvement to Technology or Computer Functionality Not Abstract Idea
Note:
Claims must improve technology or computer functionality rather than being directed to an abstract idea.

The Supreme Court has long distinguished between principles themselves (which are not patent eligible) and the integration of those principles into practical applications (which are patent eligible). See, e.g., Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66, 80, 84, 101 USPQ2d 1961, 1968-69, 1970 (2012) (noting that the Court in Diamond v. Diehr found ‘‘the overall process patent eligible because of the way the additional steps of the process integrated the equation into the process as a whole,’’ but the Court in Gottschalk v. Benson ‘‘held that simply implementing a mathematical principle on a physical machine, namely a computer, was not a patentable application of that principle’’). Similarly, in a growing body of decisions, the Federal Circuit has distinguished between claims that are ‘‘directed to’’ a judicial exception (which require further analysis to determine their eligibility) and those that are not (which are therefore patent eligible), e.g., claims that improve the functioning of a computer or other technology or technological field. See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981); Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972). See, e.g., MPEP § 2106.06(b) (summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016), McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 120 USPQ2d 1091 (Fed. Cir. 2016), and other cases that were eligible as improvements to technology or computer functionality instead of being directed to abstract ideas).

Jump to MPEP SourceStep 2A Prong 1 – Judicial ExceptionPatent EligibilityMachine
Topic

Claims

2 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-88d4d2fd6d2d1a23c18d6d2e]
Abstract Idea Requires Practical Application
Note:
The recited virus screening on a computer is an abstract idea and does not render the claim eligible unless integrated into a practical application.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourcePatent EligibilityClaims Directed To
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-ab8b5397c5a45a402f938c7a]
Specification Must Describe Security Profile Benefits
Note:
The patent’s specification must describe the security profile as identifying both hostile and potentially hostile operations to demonstrate improved computer functionality.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourcePatent Application ContentClaims Directed To
Topic

Machine

1 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-c11eab6d2d6b4df891778485]
Requirement for Integrating Judicial Exception into Practical Application
Note:
The rule requires that a judicial exception be integrated into a practical application to be patent eligible.

The Supreme Court has long distinguished between principles themselves (which are not patent eligible) and the integration of those principles into practical applications (which are patent eligible). See, e.g., Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66, 80, 84, 101 USPQ2d 1961, 1968-69, 1970 (2012) (noting that the Court in Diamond v. Diehr found ‘‘the overall process patent eligible because of the way the additional steps of the process integrated the equation into the process as a whole,’’ but the Court in Gottschalk v. Benson ‘‘held that simply implementing a mathematical principle on a physical machine, namely a computer, was not a patentable application of that principle’’). Similarly, in a growing body of decisions, the Federal Circuit has distinguished between claims that are ‘‘directed to’’ a judicial exception (which require further analysis to determine their eligibility) and those that are not (which are therefore patent eligible), e.g., claims that improve the functioning of a computer or other technology or technological field. See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981); Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972). See, e.g., MPEP § 2106.06(b) (summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016), McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 120 USPQ2d 1091 (Fed. Cir. 2016), and other cases that were eligible as improvements to technology or computer functionality instead of being directed to abstract ideas).

Jump to MPEP SourceMachineProcess (Method)Alice/Mayo Two-Step Framework
Topic

Claim Subject Matter

1 rules
MPEP GuidanceInformativeAlways
[mpep-2106-04-d-842cd6c671ab219bf7a59415]
Security Profile Must Enable Practical Application
Note:
The claimed invention must use a security profile that enables practical application by identifying and protecting against both known and unknown threats, thus integrating the abstract idea into a specific technological solution.

In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018), the claimed invention was a method of virus scanning that scans an application program, generates a security profile identifying any potentially suspicious code in the program, and links the security profile to the application program. 879 F.3d at 1303-04, 125 USPQ2d at 1285-86. The Federal Circuit noted that the recited virus screening was an abstract idea, and that merely performing virus screening on a computer does not render the claim eligible. 879 F.3d at 1304, 125 USPQ2d at 1286. The court then continued with its analysis under part one of the Alice/Mayo test by reviewing the patent’s specification, which described the claimed security profile as identifying both hostile and potentially hostile operations. The court noted that the security profile thus enables the invention to protect the user against both previously unknown viruses and “obfuscated code,” as compared to traditional virus scanning, which only recognized the presence of previously-identified viruses. The security profile also enables more flexible virus filtering and greater user customization. 879 F.3d at 1304, 125 USPQ2d at 1286. The court identified these benefits as improving computer functionality, and verified that the claims recite additional elements (e.g., specific steps of using the security profile in a particular way) that reflect this improvement. Accordingly, the court held the claims eligible as not being directed to the recited abstract idea. 879 F.3d at 1304-05, 125 USPQ2d at 1286-87. This analysis is equivalent to the Office’s analysis of determining that the additional elements integrate the judicial exception into a practical application at Step 2A Prong Two, and thus that the claims were not directed to the judicial exception (Step 2A: NO).

Jump to MPEP SourceClaim Subject MatterMethod/Process Claims

Citations

Primary topicCitation
Patent EligibilityMPEP § 2106
MPEP § 2106.04
MPEP § 2106.04(d)(1)
MPEP § 2106.04(d)(2)
Patent EligibilityMPEP § 2106.05
Patent EligibilityMPEP § 2106.05(a)
Patent EligibilityMPEP § 2106.05(b)
MPEP § 2106.05(c)
Patent EligibilityMPEP § 2106.05(e)
MPEP § 2106.05(f)
MPEP § 2106.05(g)
MPEP § 2106.05(h)
Machine
Patent Eligibility
Step 2A Prong 1 – Judicial Exception
MPEP § 2106.06(b)
Process (Method)Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016)
Machine
Patent Eligibility
Step 2A Prong 1 – Judicial Exception
Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972)
Claim Subject Matter
Claims
Claims Directed To
In Finjan Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299, 125 USPQ2d 1282 (Fed. Cir. 2018)
In Solutran, Inc. v. Elavon, Inc., 931 F.3d 1161, 2019 USPQ2d 281076 (Fed. Cir. 2019)
Machine
Patent Eligibility
Step 2A Prong 1 – Judicial Exception
See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981)
Process (Method)See also Genetic Technologies Ltd. v. Merial LLC, 818 F.3d 1369, 1377, 118 USPQ2d 1541, 1547 (Fed. Cir. 2016)
Patent Eligibilityin Parker v. Flook, 437 U.S. 584, 198 USPQ 193 (1978)
Machine
Patent Eligibility
Step 2A Prong 1 – Judicial Exception
summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016)

Source Text from USPTO’s MPEP

This is an exact copy of the MPEP from the USPTO. It is here for your reference to see the section in context.

BlueIron Last Updated: 2026-01-17