MPEP § 2114 — Apparatus and Article Claims — Functional Language (Annotated Rules)

§2114 Apparatus and Article Claims — Functional Language

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

This page consolidates and annotates all enforceable requirements under MPEP § 2114, 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.

Apparatus and Article Claims — Functional Language

This section addresses Apparatus and Article Claims — Functional Language. Primary authority: 35 U.S.C. 102, 35 U.S.C. 103, and 35 U.S.C. 2186. Contains: 1 requirement, 2 prohibitions, 1 guidance statement, 3 permissions, and 7 other statements.

Key Rules

Topic

Claim Form Requirements

4 rules
StatutoryPermittedAlways
[mpep-2114-fd15ebb0dd60b908ea9158bf]
Functional Claim Covers All Capable Devices
Note:
A claim using functional language covers any device capable of performing the recited function, even if not specifically structured as claimed. If prior art discloses such a capability, it may be used to reject claims under 35 U.S.C. 102 and/or 103.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryInformativeAlways
[mpep-2114-b30e92f02303e53f638948af]
Functional Claim Language Covers All Capable Devices
Note:
Claims with functional language cover any device capable of performing the recited function, even if specific structure is not required.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryInformativeAlways
[mpep-2114-f43171b2b89f384bc580fc84]
Functional Claim Language Requires Capability Not Specific Structure
Note:
Claims using functional language must be interpreted to require capability rather than a specific structure.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryRequiredAlways
[mpep-2114-aab7b82ee27f3ce31d0c3ab1]
Claim Language Covers Capable Devices
Note:
Claims using functional language cover all devices capable of performing the recited function, even if not specifically structured as claimed.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
Topic

Interpreting Claims (MPEP 2173.01)

4 rules
StatutoryRecommendedAlways
[mpep-2114-6cdcdeb271ab7226866c41ad]
Computer Term Not Limited to Specific Characteristics
Note:
A claim containing the term 'computer' should not be construed as limited to a specific set of characteristics unless modified by other terms or clearly defined in the specification.

Computer-implemented functional claim limitations may also be broad because the term “computer” is commonly understood by one of ordinary skill in the art to describe a variety of devices with varying degrees of complexity and capabilities. In re Paulsen, 30 F.3d 1475, 1479-80, 31 USPQ2d 1671, 1674 (Fed. Cir. 1994). Therefore, a claim containing the term “computer” should not be construed as limited to a computer having a specific set of characteristics and capabilities, unless the term is modified by other claim terms or clearly defined in the specification to be different from its common meaning. Id. In Paulsen, the claims, directed to a portable computer, were rejected as anticipated under 35 U.S.C. 102 by a reference that disclosed a calculator, because the term “computer” was given the broadest reasonable interpretation consistent with the specification to include a calculator, and a calculator was considered to be a particular type of computer by those of ordinary skill in the art. Id.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2114-816274ff93dcd5e55ef5d0ca]
Computer Term Includes Calculators
Note:
The term 'computer' in claims should be interpreted broadly to include calculators, as both are considered types of computers by those skilled in the art.

Computer-implemented functional claim limitations may also be broad because the term “computer” is commonly understood by one of ordinary skill in the art to describe a variety of devices with varying degrees of complexity and capabilities. In re Paulsen, 30 F.3d 1475, 1479-80, 31 USPQ2d 1671, 1674 (Fed. Cir. 1994). Therefore, a claim containing the term “computer” should not be construed as limited to a computer having a specific set of characteristics and capabilities, unless the term is modified by other claim terms or clearly defined in the specification to be different from its common meaning. Id. In Paulsen, the claims, directed to a portable computer, were rejected as anticipated under 35 U.S.C. 102 by a reference that disclosed a calculator, because the term “computer” was given the broadest reasonable interpretation consistent with the specification to include a calculator, and a calculator was considered to be a particular type of computer by those of ordinary skill in the art. Id.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
MPEP GuidanceInformativeAlways
[mpep-2114-893cdec83c51d04f5b0a3639]
Equivalent Structures for Means-Plus-Function Claims
Note:
If a prior art device performs the same function as claimed means-plus-function elements, it must have equivalent structures to meet the claim requirements.

Even if the prior art device performs all the functions recited in the claim, the prior art cannot anticipate the claim if there is any structural difference. It should be noted, however, that means-plus-function limitations are met by structures which are equivalent to the corresponding structures recited in the specification. In re Donaldson, 16 F.3d 1189, 1193, 29 USPQ2d 1845, 1848 (Fed. Cir. 1994). See also In re Robertson, 169 F.3d 743, 745, 49 USPQ2d 1949, 1951 (Fed. Cir. 1999) (The claims were drawn to a disposable diaper having three fastening elements. The reference disclosed two fastening elements that could perform the same function as the three fastening elements in the claims. The court construed the claims to require three separate elements and held that the reference did not disclose a separate third fastening element, either expressly or inherently.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Anticipation/Novelty
MPEP GuidanceInformativeAlways
[mpep-2114-4cfb20e5ad140ec22473e26c]
Claim Requires Three Separate Fastening Elements
Note:
The claim must specify three distinct fastening elements, and the prior art must disclose all three separately to avoid anticipation.

Even if the prior art device performs all the functions recited in the claim, the prior art cannot anticipate the claim if there is any structural difference. It should be noted, however, that means-plus-function limitations are met by structures which are equivalent to the corresponding structures recited in the specification. In re Donaldson, 16 F.3d 1189, 1193, 29 USPQ2d 1845, 1848 (Fed. Cir. 1994). See also In re Robertson, 169 F.3d 743, 745, 49 USPQ2d 1949, 1951 (Fed. Cir. 1999) (The claims were drawn to a disposable diaper having three fastening elements. The reference disclosed two fastening elements that could perform the same function as the three fastening elements in the claims. The court construed the claims to require three separate elements and held that the reference did not disclose a separate third fastening element, either expressly or inherently.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Anticipation/Novelty
Topic

Claims

3 rules
StatutoryInformativeAlways
[mpep-2114-9e411d19a8d5b17ca0d29b81]
Claimed Circuitry Must Be Capable of Performing Function
Note:
Claims using functional language must describe circuits capable of performing the recited function, not just specific structures.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryInformativeAlways
[mpep-2114-d76efb74c72ec52e3a45753d]
Claimed Circuit Must Be Capable of Receiving Input Variables
Note:
The claimed circuit does not require specific input connections; it must simply be capable of receiving first and second input variables.

Functional claim language that is not limited to a specific structure covers all devices that are capable of performing the recited function. Therefore, if the prior art discloses a device that can inherently perform the claimed function, a rejection under 35 U.S.C. 102 and/or 35 U.S.C. 103 may be appropriate. See In re Translogic Technology, Inc., 504 F.3d 1249, 1258, 84 USPQ2d 1929, 1935-1936 (Fed. Cir. 2007) (The claims were drawn to multiplexer circuit. The patent at issue claimed “coupled to” and “coupled to receive” between various portions of the circuitry. In reference to the claim phrase “input terminals ‘coupled to receive’ first and second input variables,” the court held that “the claimed circuit does not require any specific input or connection … [a]s such, ‘coupled to’ and ‘coupled to receive’ are clearly different … [a]s shown in [the figures of the] patent, input terminals … only need to be ‘capable of receiving’ an input variable for the multiplexer circuit as claimed”. Therefore, the specification supported the claim construction “that ‘coupled to receive’ means ‘capable of receiving.’”); Intel Corp. v. U.S. Int'l Trade Comm’n, 946 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991) (The court held that “programmable” claim language required only that the accused product could be programmed to perform the claimed functionality.); In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997); In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977); In re Ludtke, 441 F.2d 660, 663-64, 169 USPQ 563, 566-67 (CCPA 1971); In re Swinehart, 439 F.2d 210, 212-13, 169 USPQ 226, 228-29 (CCPA 1971) (“[I]t is elementary that the mere recitation of a newly discovered function or property, inherently possessed by things in the prior art, does not cause a claim drawn to those things to distinguish over the prior art”). See MPEP § 2112 for more information.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
MPEP GuidanceProhibitedAlways
[mpep-2114-768129a9b42aa4a030f5fe99]
Structural Differences Must Be Present For Anticipation
Note:
Claims are not anticipated by prior art if there is any structural difference, even if the prior art performs all recited functions. Means-plus-function limitations require structures equivalent to those in the specification.

Even if the prior art device performs all the functions recited in the claim, the prior art cannot anticipate the claim if there is any structural difference. It should be noted, however, that means-plus-function limitations are met by structures which are equivalent to the corresponding structures recited in the specification. In re Donaldson, 16 F.3d 1189, 1193, 29 USPQ2d 1845, 1848 (Fed. Cir. 1994). See also In re Robertson, 169 F.3d 743, 745, 49 USPQ2d 1949, 1951 (Fed. Cir. 1999) (The claims were drawn to a disposable diaper having three fastening elements. The reference disclosed two fastening elements that could perform the same function as the three fastening elements in the claims. The court construed the claims to require three separate elements and held that the reference did not disclose a separate third fastening element, either expressly or inherently.).

Jump to MPEP SourceAnticipation/NoveltyPatent Application Content
Topic

Judicial Review of Board Decisions

3 rules
StatutoryPermittedAlways
[mpep-2114-bd3c82a02d18c3881ae067bb]
Functional Claim Limitations Narrow Device Capability
Note:
Computer-implemented functional claim limitations restrict the specific structure needed to perform recited functions, narrowing device functionality.

Conversely, computer-implemented functional claim limitations may narrow the functionality of the device, by limiting the specific structure capable of performing the recited function. Nazomi Communications, Inc. v. Nokia Corp., 739 F.3d 1339, 1345, 109 USPQ2d 1258, 1262 (Fed. Cir. 2014) (The claims were drawn to a CPU that can perform processing of both register-based and stack-based instructions. Appellant alleged infringement of the claims based on claim construction requiring only hardware capable of performing the claimed functionalities. Contrasted with the finding of Intel Corp. v. U.S. Int'l Trade Comm’n, 846 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991), the court found that “[s]ince hardware cannot meet these limitations in the absence of enabling software, the claims are properly construed as claiming an apparatus comprising a combination of hardware and software capable of practicing the claim limitations.”).

Jump to MPEP SourceJudicial Review of Board DecisionsEx Parte Appeals to PTAB
StatutoryPermittedAlways
[mpep-2114-45f2dc0babea813a568fb448]
Claims Must Include Hardware and Software Capable of Functionality
Note:
The claims must be construed to require both hardware capable of performing the claimed functionalities and enabling software.

Conversely, computer-implemented functional claim limitations may narrow the functionality of the device, by limiting the specific structure capable of performing the recited function. Nazomi Communications, Inc. v. Nokia Corp., 739 F.3d 1339, 1345, 109 USPQ2d 1258, 1262 (Fed. Cir. 2014) (The claims were drawn to a CPU that can perform processing of both register-based and stack-based instructions. Appellant alleged infringement of the claims based on claim construction requiring only hardware capable of performing the claimed functionalities. Contrasted with the finding of Intel Corp. v. U.S. Int'l Trade Comm’n, 846 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991), the court found that “[s]ince hardware cannot meet these limitations in the absence of enabling software, the claims are properly construed as claiming an apparatus comprising a combination of hardware and software capable of practicing the claim limitations.”).

Jump to MPEP SourceJudicial Review of Board DecisionsEx Parte Appeals to PTAB
StatutoryProhibitedAlways
[mpep-2114-f7f3e774eb20fca586199a6c]
Claims Including Software Must Be Construed as Hardware and Software Combination
Note:
The court requires that claims including functional software limitations be construed to include both hardware and enabling software capable of practicing the claim limitations.

Conversely, computer-implemented functional claim limitations may narrow the functionality of the device, by limiting the specific structure capable of performing the recited function. Nazomi Communications, Inc. v. Nokia Corp., 739 F.3d 1339, 1345, 109 USPQ2d 1258, 1262 (Fed. Cir. 2014) (The claims were drawn to a CPU that can perform processing of both register-based and stack-based instructions. Appellant alleged infringement of the claims based on claim construction requiring only hardware capable of performing the claimed functionalities. Contrasted with the finding of Intel Corp. v. U.S. Int'l Trade Comm’n, 846 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991), the court found that “[s]ince hardware cannot meet these limitations in the absence of enabling software, the claims are properly construed as claiming an apparatus comprising a combination of hardware and software capable of practicing the claim limitations.”).

Jump to MPEP SourceJudicial Review of Board DecisionsEx Parte Appeals to PTAB
Topic

KSR Obviousness Rationales

3 rules
StatutoryInformativeAlways
[mpep-2114-d43da2e199f376a67dcff349]
Implementing Known Function on Computer Is Obvious
Note:
Using a general-purpose computer to automate a known function is considered obvious if it follows established functions of prior art elements.

When determining whether a computer-implemented functional claim would have been obvious, examiners should note that broadly claiming an automated means to replace a manual function to accomplish the same result does not distinguish over the prior art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1161, 82 USPQ2d 1687, 1691 (Fed. Cir. 2007) (“Accommodating a prior art mechanical device that accomplishes [a desired] goal to modern electronics would have been reasonably obvious to one of ordinary skill in designing children’s learning devices. Applying modern electronics to older mechanical devices has been commonplace in recent years.”); In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958); see also MPEP § 2144.04. Furthermore, implementing a known function on a computer has been deemed obvious to one of ordinary skill in the art if the automation of the known function on a general purpose computer is nothing more than the predictable use of prior art elements according to their established functions. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417, 82 USPQ2d 1385, 1396 (2007); see also MPEP § 2143, Exemplary Rationales D and F. Likewise, it has been found to be obvious to adapt an existing process to incorporate Internet and Web browser technologies for communicating and displaying information because these technologies had become commonplace for those functions. Muniauction, Inc. v. Thomson Corp., 532 F.3d 1318, 1326-27, 87 USPQ2d 1350, 1357 (Fed. Cir. 2008).

Jump to MPEP SourceKSR Obviousness RationalesObviousness
StatutoryInformativeAlways
[mpep-2114-2826a22cd6537585e33440c6]
Automating Known Functions on Computers Is Obvious
Note:
When determining obviousness for computer-implemented functional claims, automating a known function using a general-purpose computer is considered an obvious step.

When determining whether a computer-implemented functional claim would have been obvious, examiners should note that broadly claiming an automated means to replace a manual function to accomplish the same result does not distinguish over the prior art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1161, 82 USPQ2d 1687, 1691 (Fed. Cir. 2007) (“Accommodating a prior art mechanical device that accomplishes [a desired] goal to modern electronics would have been reasonably obvious to one of ordinary skill in designing children’s learning devices. Applying modern electronics to older mechanical devices has been commonplace in recent years.”); In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958); see also MPEP § 2144.04. Furthermore, implementing a known function on a computer has been deemed obvious to one of ordinary skill in the art if the automation of the known function on a general purpose computer is nothing more than the predictable use of prior art elements according to their established functions. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417, 82 USPQ2d 1385, 1396 (2007); see also MPEP § 2143, Exemplary Rationales D and F. Likewise, it has been found to be obvious to adapt an existing process to incorporate Internet and Web browser technologies for communicating and displaying information because these technologies had become commonplace for those functions. Muniauction, Inc. v. Thomson Corp., 532 F.3d 1318, 1326-27, 87 USPQ2d 1350, 1357 (Fed. Cir. 2008).

Jump to MPEP SourceKSR Obviousness RationalesObviousness
StatutoryInformativeAlways
[mpep-2114-5fabb7e65e43063cdb08a31d]
Automating Known Functions on Computer Is Obvious
Note:
When automating a known function using a computer, it is considered obvious if the automation does not add any new features or solve unexpected problems.

When determining whether a computer-implemented functional claim would have been obvious, examiners should note that broadly claiming an automated means to replace a manual function to accomplish the same result does not distinguish over the prior art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1161, 82 USPQ2d 1687, 1691 (Fed. Cir. 2007) (“Accommodating a prior art mechanical device that accomplishes [a desired] goal to modern electronics would have been reasonably obvious to one of ordinary skill in designing children’s learning devices. Applying modern electronics to older mechanical devices has been commonplace in recent years.”); In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958); see also MPEP § 2144.04. Furthermore, implementing a known function on a computer has been deemed obvious to one of ordinary skill in the art if the automation of the known function on a general purpose computer is nothing more than the predictable use of prior art elements according to their established functions. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417, 82 USPQ2d 1385, 1396 (2007); see also MPEP § 2143, Exemplary Rationales D and F. Likewise, it has been found to be obvious to adapt an existing process to incorporate Internet and Web browser technologies for communicating and displaying information because these technologies had become commonplace for those functions. Muniauction, Inc. v. Thomson Corp., 532 F.3d 1318, 1326-27, 87 USPQ2d 1350, 1357 (Fed. Cir. 2008).

Jump to MPEP SourceKSR Obviousness RationalesObviousness
Topic

35 U.S.C. 103 – Obviousness

2 rules
StatutoryRecommendedAlways
[mpep-2114-7c8eff8d9c57415a6daa4dd7]
Automated Means for Manual Functions Do Not Distinguish Over Prior Art
Note:
Examiners should not consider broadly claiming an automated method to replace a manual function as distinguishing over prior art when determining obviousness under 35 U.S.C. 103.

When determining whether a computer-implemented functional claim would have been obvious, examiners should note that broadly claiming an automated means to replace a manual function to accomplish the same result does not distinguish over the prior art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1161, 82 USPQ2d 1687, 1691 (Fed. Cir. 2007) (“Accommodating a prior art mechanical device that accomplishes [a desired] goal to modern electronics would have been reasonably obvious to one of ordinary skill in designing children’s learning devices. Applying modern electronics to older mechanical devices has been commonplace in recent years.”); In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958); see also MPEP § 2144.04. Furthermore, implementing a known function on a computer has been deemed obvious to one of ordinary skill in the art if the automation of the known function on a general purpose computer is nothing more than the predictable use of prior art elements according to their established functions. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417, 82 USPQ2d 1385, 1396 (2007); see also MPEP § 2143, Exemplary Rationales D and F. Likewise, it has been found to be obvious to adapt an existing process to incorporate Internet and Web browser technologies for communicating and displaying information because these technologies had become commonplace for those functions. Muniauction, Inc. v. Thomson Corp., 532 F.3d 1318, 1326-27, 87 USPQ2d 1350, 1357 (Fed. Cir. 2008).

Jump to MPEP SourceObviousnessKSR Obviousness Rationales
StatutoryInformativeAlways
[mpep-2114-e8e3062ea5d93a5d0e89ad38]
Adapting Existing Processes to Internet Technologies Is Obvious
Note:
It is considered obvious to adapt an existing process to incorporate internet and web browser technologies for communication and display purposes, as these have become commonplace.

When determining whether a computer-implemented functional claim would have been obvious, examiners should note that broadly claiming an automated means to replace a manual function to accomplish the same result does not distinguish over the prior art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1161, 82 USPQ2d 1687, 1691 (Fed. Cir. 2007) (“Accommodating a prior art mechanical device that accomplishes [a desired] goal to modern electronics would have been reasonably obvious to one of ordinary skill in designing children’s learning devices. Applying modern electronics to older mechanical devices has been commonplace in recent years.”); In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958); see also MPEP § 2144.04. Furthermore, implementing a known function on a computer has been deemed obvious to one of ordinary skill in the art if the automation of the known function on a general purpose computer is nothing more than the predictable use of prior art elements according to their established functions. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417, 82 USPQ2d 1385, 1396 (2007); see also MPEP § 2143, Exemplary Rationales D and F. Likewise, it has been found to be obvious to adapt an existing process to incorporate Internet and Web browser technologies for communicating and displaying information because these technologies had become commonplace for those functions. Muniauction, Inc. v. Thomson Corp., 532 F.3d 1318, 1326-27, 87 USPQ2d 1350, 1357 (Fed. Cir. 2008).

Jump to MPEP SourceObviousnessKSR Obviousness Rationales
Topic

Inherent Feature in Prior Art

2 rules
MPEP GuidancePermittedAlways
[mpep-2114-caa51b6d9a6bfe8eb062a023]
Inherent Functional Limitation of Prior Art
Note:
If an examiner concludes that a functional limitation is inherent in the prior art, the burden shifts to the applicant to prove it does not possess the claimed characteristic.

Features of an apparatus may be recited either structurally or functionally. In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997). See also MPEP § 2173.05(g). If an examiner concludes that a functional limitation is an inherent characteristic of the prior art, then to establish a prima case of anticipation or obviousness, the examiner should explain that the prior art structure inherently possesses the functionally defined limitations of the claimed apparatus. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432. See also Bettcher Industries, Inc. v. Bunzl USA, Inc., 661 F.3d 629, 639-40, 100 USPQ2d 1433, 1440 (Fed. Cir. 2011). The burden then shifts to applicant to establish that the prior art does not possess the characteristic relied on. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432; In re Swinehart, 439 F.2d 210, 213, 169 USPQ 226, 228 (CCPA 1971) (“where the Patent Office has reason to believe that a functional limitation asserted to be critical for establishing novelty in the claimed subject matter may, in fact, be an inherent characteristic of the prior art, it possesses the authority to require the applicant to prove that the subject matter shown to be in the prior art does not possess the characteristic relied on”).
Features of an apparatus may be recited either structurally or functionally. In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997) See also MPEP § 2173.05(g).

Jump to MPEP SourceInherent Feature in Prior ArtAnticipation by Inherency (MPEP 2112)Anticipation/Novelty
MPEP GuidanceRecommendedAlways
[mpep-2114-4960749d2d0174f7134afb4c]
Examiner Must Explain Inherent Functionality to Establish Anticipation or Obviousness
Note:
An examiner must demonstrate that the prior art inherently possesses the functional limitations of the claimed apparatus to establish a case of anticipation or obviousness.

Features of an apparatus may be recited either structurally or functionally. In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997). See also MPEP § 2173.05(g). If an examiner concludes that a functional limitation is an inherent characteristic of the prior art, then to establish a prima case of anticipation or obviousness, the examiner should explain that the prior art structure inherently possesses the functionally defined limitations of the claimed apparatus. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432. See also Bettcher Industries, Inc. v. Bunzl USA, Inc., 661 F.3d 629, 639-40, 100 USPQ2d 1433, 1440 (Fed. Cir. 2011). The burden then shifts to applicant to establish that the prior art does not possess the characteristic relied on. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432; In re Swinehart, 439 F.2d 210, 213, 169 USPQ 226, 228 (CCPA 1971) (“where the Patent Office has reason to believe that a functional limitation asserted to be critical for establishing novelty in the claimed subject matter may, in fact, be an inherent characteristic of the prior art, it possesses the authority to require the applicant to prove that the subject matter shown to be in the prior art does not possess the characteristic relied on”).

Jump to MPEP SourceInherent Feature in Prior ArtAnticipation by Inherency (MPEP 2112)Anticipation/Novelty
Topic

Ex Parte Appeals to PTAB

1 rules
StatutoryInformativeAlways
[mpep-2114-8bfb8c3ec02e87e65756b90b]
Computer-Implemented Functional Language Narrows Apparatus Claims
Note:
Claims with computer-implemented functional language require a combination of hardware and software capable of performing the recited functions.

Conversely, computer-implemented functional claim limitations may narrow the functionality of the device, by limiting the specific structure capable of performing the recited function. Nazomi Communications, Inc. v. Nokia Corp., 739 F.3d 1339, 1345, 109 USPQ2d 1258, 1262 (Fed. Cir. 2014) (The claims were drawn to a CPU that can perform processing of both register-based and stack-based instructions. Appellant alleged infringement of the claims based on claim construction requiring only hardware capable of performing the claimed functionalities. Contrasted with the finding of Intel Corp. v. U.S. Int'l Trade Comm’n, 846 F.2d 821, 832, 20 USPQ2d 1161, 1171 (Fed. Cir. 1991), the court found that “[s]ince hardware cannot meet these limitations in the absence of enabling software, the claims are properly construed as claiming an apparatus comprising a combination of hardware and software capable of practicing the claim limitations.”).

Jump to MPEP SourceEx Parte Appeals to PTABJudicial Review of Board Decisions
Topic

Obviousness

1 rules
StatutoryInformativeAlways
[mpep-2114-15bce3b07f66ea0facb5c3f0]
Obvious to Person of Ordinary Skill
Note:
The determination of obviousness requires assessing whether a claim would be obvious to a person with ordinary skill in the relevant art.

For more information on the obviousness determination, see MPEP § 2141.

Topic

Anticipation by Inherency (MPEP 2112)

1 rules
MPEP GuidancePermittedAlways
[mpep-2114-f861bc8c008e813736a88b7a]
Applicant Must Prove Prior Art Does Not Possess Characteristic Relied On
Note:
The Patent Office can assert that a functional limitation of the claimed invention is an inherent characteristic of the prior art, shifting the burden to the applicant to prove otherwise.

Features of an apparatus may be recited either structurally or functionally. In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997). See also MPEP § 2173.05(g). If an examiner concludes that a functional limitation is an inherent characteristic of the prior art, then to establish a prima case of anticipation or obviousness, the examiner should explain that the prior art structure inherently possesses the functionally defined limitations of the claimed apparatus. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432. See also Bettcher Industries, Inc. v. Bunzl USA, Inc., 661 F.3d 629, 639-40, 100 USPQ2d 1433, 1440 (Fed. Cir. 2011). The burden then shifts to applicant to establish that the prior art does not possess the characteristic relied on. In re Schreiber, 128 F.3d at 1478, 44 USPQ2d at 1432; In re Swinehart, 439 F.2d 210, 213, 169 USPQ 226, 228 (CCPA 1971) (“where the Patent Office has reason to believe that a functional limitation asserted to be critical for establishing novelty in the claimed subject matter may, in fact, be an inherent characteristic of the prior art, it possesses the authority to require the applicant to prove that the subject matter shown to be in the prior art does not possess the characteristic relied on”).

Jump to MPEP SourceAnticipation by Inherency (MPEP 2112)Novelty / Prior ArtInherent Feature in Prior Art

Citations

Primary topicCitation
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
35 U.S.C. § 102
Claim Form Requirements
Claims
35 U.S.C. § 103
35 U.S.C. § 2186
Claim Form Requirements
Claims
MPEP § 2112
ObviousnessMPEP § 2141
35 U.S.C. 103 – Obviousness
KSR Obviousness Rationales
MPEP § 2143
35 U.S.C. 103 – Obviousness
KSR Obviousness Rationales
MPEP § 2144.04
Anticipation by Inherency (MPEP 2112)
Inherent Feature in Prior Art
MPEP § 2173.05(g)
MPEP § 2181
Claim Form Requirements
Claims
In re Best, 562 F.2d 1252, 1254, 195 USPQ 430, 433 (CCPA 1977)
Claims
Interpreting Claims (MPEP 2173.01)
In re Donaldson, 16 F.3d 1189, 1193, 29 USPQ2d 1845, 1848 (Fed. Cir. 1994)
Claims
Interpreting Claims (MPEP 2173.01)
In re Robertson, 169 F.3d 743, 745, 49 USPQ2d 1949, 1951 (Fed. Cir. 1999)
Anticipation by Inherency (MPEP 2112)
Claim Form Requirements
Claims
Inherent Feature in Prior Art
In re Schreiber, 128 F.3d 1473, 1478, 44 USPQ2d 1429, 1432 (Fed. Cir. 1997)
Anticipation by Inherency (MPEP 2112)
Inherent Feature in Prior Art
In re Swinehart, 439 F.2d 210, 213, 169 USPQ 226, 228 (CCPA 1971)
35 U.S.C. 103 – Obviousness
KSR Obviousness Rationales
In re Venner, 262 F.2d 91, 95, 120 USPQ 193, 194 (CCPA 1958)
Ex Parte Appeals to PTAB
Judicial Review of Board Decisions
Nazomi Communications, Inc. v. Nokia Corp., 739 F.3d 1339, 1345, 109 USPQ2d 1258, 1262 (Fed. Cir. 2014)

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-10