MPEP § 2111.01 — Plain Meaning (Annotated Rules)

§2111.01 Plain Meaning

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

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

Plain Meaning

This section addresses Plain Meaning. Primary authority: 35 U.S.C. 102, 35 U.S.C. 112(f), and 35 U.S.C. 112. Contains: 7 requirements, 8 guidance statements, 6 permissions, and 10 other statements.

Key Rules

Topic

Interpreting Claims (MPEP 2173.01)

19 rules
StatutoryInformativeAlways
[mpep-2111-01-0c1497964c605c18d2fc8376]
Claim Terms Must Have Ordinary Artistic Meaning
Note:
Claims terms must be interpreted using the ordinary and customary meaning given to them by those skilled in the relevant art at the time of filing, as evidenced by the specification.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form RequirementsRequired Claim Content
StatutoryInformativeAlways
[mpep-2111-01-cb91bf3ed600ccf19f29ec42]
Claims Must Not Import Specification Limitations
Note:
Claims should be interpreted based on their language without incorporating limitations from the specification that are not present in the claims.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application ContentDescription of Embodiments
StatutoryRequiredAlways
[mpep-2111-01-7f497fcd2b83a16cd81e089c]
Claimed Element Must Be Constrained by Specification
Note:
When an element is claimed using means-plus-function language, it must be construed as limited to the corresponding structure, material, or acts described in the specification and their equivalents.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Corresponding Structure (MPEP 2182)Equivalents Under 112(f) (MPEP 2185)
StatutoryRecommendedAlways
[mpep-2111-01-fb4da06d449dee72261eee72]
Claims Must Be Construed Broadly
Note:
Claims must be interpreted according to their plain and ordinary meaning, not limited to specific disclosed embodiments.

In Sisvel Int’l S.A. v. Sierra Wireless, Inc., 81 F.4th 1231, 1236-37, 2023 USPQ2d 1030 (Fed. Cir. 2023), the court found that construing “connection rejection message” should be given its plain and ordinary meaning, and should not be construed in such a way as to improperly limit the claims to specific disclosed embodiments. The intrinsic evidence provided no basis to limit the claims to the preferred embodiments and a person of ordinary skill in the art would broadly interpret the claim language consistent with the broad statements in the specification.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryRequiredAlways
[mpep-2111-01-84e6713bede31d2dd932144a]
Claim Terms Must Be Consistent With Specification and Drawings
Note:
Claims terms must be interpreted consistently with their use in the specification and drawings. If the specification clearly defines a claim term, extrinsic evidence is not needed for interpretation.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryPermittedAlways
[mpep-2111-01-eed29d9f1cdc9d1c4d44c175]
Intrinsic Evidence Primarily for Claim Clarity
Note:
Use intrinsic evidence to interpret claims unless insufficient clarity exists, then extrinsic evidence may be necessary.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-726eb26f023d7ae32da25cf4]
Extrinsic Evidence Needed for pH Interpretation
Note:
The court found that the prosecution history did not clarify whether a pH of 13 includes values rounding to 13, necessitating extrinsic evidence for claim interpretation.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryRecommendedAlways
[mpep-2111-01-e71f6824d5fd3bb6bcb9e7a6]
Extrinsic Evidence for Claim Term Interpretation When Intrinsic Clarity Lacks
Note:
When the intrinsic evidence does not clearly define a claim term, extrinsic sources must be consulted to determine its meaning in the relevant art during the relevant time period.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-63fd70cb64eafe04f49a1789]
Intrinsic Evidence Must Be Consistent With Specification for Claim Terms
Note:
The claim term’s meaning must be consistent with the specification and no extrinsic evidence is needed if intrinsic evidence clearly defines the term.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-435fb5869ae559678242052a]
Plain and Ordinary Meaning of Claim Terms
Note:
The court explains that claim terms should be given their plain and ordinary meaning unless the applicant defines them differently in the specification or disavows a term's full scope.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claims Too Broad (Enablement/Written Description)Apparatus/System Claims
StatutoryRequiredAlways
[mpep-2111-01-1bd557196f51a4750dcc809d]
Inventor May Define Specific Terms With Clarity
Note:
An inventor can define specific terms used in the patent but must do so with clarity and precision, ensuring that such definitions are clearly stated within the patent disclosure.

An applicant is entitled to be their own lexicographer and may rebut the presumption that claim terms are to be given their ordinary and customary meaning by clearly setting forth a definition of the term that is different from its ordinary and customary meaning(s) in the specification at the relevant time. See In re Paulsen, 30 F.3d 1475, 1480, 31 USPQ2d 1671, 1674 (Fed. Cir. 1994) (holding that an inventor may define specific terms used to describe invention, but must do so “with reasonable clarity, deliberateness, and precision” and, if done, must “‘set out his uncommon definition in some manner within the patent disclosure’ so as to give one of ordinary skill in the art notice of the change” in meaning) (quoting Intellicall, Inc. v. Phonometrics, Inc., 952 F.2d 1384, 1387-88, 21 USPQ2d 1383, 1386 (Fed. Cir. 1992)).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-2b6fcf59c4f876f4f12c0584]
Claim Term Defined by Specification
Note:
A claim term's meaning is derived from its ordinary and customary usage in the specification, unless explicitly defined elsewhere.

Where an explicit definition is provided by the applicant for a term, that definition will control interpretation of the term as it is used in the claim. Toro Co. v. White Consolidated Industries Inc., 199 F.3d 1295, 1301, 53 USPQ2d 1065, 1069 (Fed. Cir. 1999) (meaning of words used in a claim is not construed in a “lexicographic vacuum, but in the context of the specification and drawings”). Thus, if a claim term is used in its ordinary and customary meaning throughout the specification, and the written description clearly indicates its meaning, then the term in the claim has that meaning. Old Town Canoe Co. v. Confluence Holdings Corp., 448 F.3d 1309, 1317, 78 USPQ2d 1705, 1711 (Fed. Cir. 2006) (The court held that “completion of coalescence” must be given its ordinary and customary meaning of reaching the end of coalescence. The court explained that even though coalescence could theoretically be “completed” by halting the molding process earlier, the specification clearly intended that completion of coalescence occurs only after the molding process reaches its optimum stage.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryRequiredAlways
[mpep-2111-01-68784e04fc81f20b9df22619]
Claim Terms Use Ordinary Meaning
Note:
Claims must use terms in their ordinary and customary meaning unless explicitly defined by the applicant.

Where an explicit definition is provided by the applicant for a term, that definition will control interpretation of the term as it is used in the claim. Toro Co. v. White Consolidated Industries Inc., 199 F.3d 1295, 1301, 53 USPQ2d 1065, 1069 (Fed. Cir. 1999) (meaning of words used in a claim is not construed in a “lexicographic vacuum, but in the context of the specification and drawings”). Thus, if a claim term is used in its ordinary and customary meaning throughout the specification, and the written description clearly indicates its meaning, then the term in the claim has that meaning. Old Town Canoe Co. v. Confluence Holdings Corp., 448 F.3d 1309, 1317, 78 USPQ2d 1705, 1711 (Fed. Cir. 2006) (The court held that “completion of coalescence” must be given its ordinary and customary meaning of reaching the end of coalescence. The court explained that even though coalescence could theoretically be “completed” by halting the molding process earlier, the specification clearly intended that completion of coalescence occurs only after the molding process reaches its optimum stage.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-1f0b8d22c2e99a9c3616ca24]
Claim Language Must Reflect Specification
Note:
Claims must be interpreted based on the specification, and any special meanings assigned to terms must be clear in the specification.

However, it is important to note that any special meaning assigned to a term “must be sufficiently clear in the specification that any departure from common usage would be so understood by a person of experience in the field of the invention.” Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998). See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999) and MPEP § 2173.05(a). In Apple Inc. v. Corephotonics, Ltd., 81 F.4th 1353, 1358-60, 2023 USPQ2d 1056 (Fed. Cir. 2023), the claim phrase “a point of view of the Wide camera” was held to only require a “Wide perspective point of view or Wide position point of view” after reviewing the specification. In particular, the court found that a reasonable reading of the specification defined two different types of Wide point of view – perspective and position, whereas the claim language was broad as to the point of view. The court also explained that claims should not be interpreted in a way that would omit a disclosed embodiment, absent evidence to the contrary. Thus, given the review of the intrinsic evidence, the court held that the claim language only required Wide perspective or Wide position point of view, but not both.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-514299e6f0700080f52ef8b5]
Claim Terms Have Ordinary Meaning Unless Specified
Note:
Claims terms are given their ordinary meaning unless the specification clearly defines them otherwise.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryRecommendedAlways
[mpep-2111-01-ed8daa50dc83a36e118f39cd]
About Means Approximately
Note:
The appellate court held that the term 'about' in claims should be interpreted as meaning 'approximately' rather than exactly.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-7f83c97484645c382fb5686b]
Electrochemical Sensor Excludes External Cables
Note:
The broadest reasonable interpretation of an electrochemical sensor claim term excludes sensors with external connection cables or wires as the specification consistently depicts such sensors without cables and disparages them.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryRecommendedAlways
[mpep-2111-01-35f8440602a27dfa59f9f40f]
Examiner Must Clarify Narrower Interpretation Due to Implicit Disavowal in Specification
Note:
The examiner must clarify if the broadest reasonable interpretation of a claim is narrower than what the words suggest due to implicit disavowal in the specification.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryRecommendedAlways
[mpep-2111-01-ffbbf7f2b9fe33590541188d]
Claim Term Without Clear Meaning Requires Broadest Reasonable Interpretation
Note:
If a claim term lacks an ordinary meaning, it should be interpreted broadly based on the specification and prior art. The claim must then be rejected under 35 U.S.C. 112(b) and the specification objected to under 37 CFR 1.75(d).

Moving back to the first question, if a claim term does not have an ordinary and customary meaning, the examiner should check the specification to determine whether it provides a meaning to the claim term. If no reasonably clear meaning can be ascribed to the claim term after considering the specification and prior art, the examiner should apply the broadest reasonable interpretation to the claim term as it can be best understood. Also, the claim should be rejected under 35 U.S.C. 112(b) and the specification objected to under 37 CFR 1.75(d).

Jump to MPEP Source · 37 CFR 1.75(d)Interpreting Claims (MPEP 2173.01)Patent Application Content
Topic

Claims

17 rules
StatutoryPermittedAlways
[mpep-2111-01-cd06ae2a58d295d5ea3817a7]
Specification Best Source for Claim Terms
Note:
The specification is the primary source for determining the meaning of claim terms, with other sources like claims and drawings also considered.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourcePatent Application ContentClaim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-adc5a4aa15ceff1ef54b7ce6]
Specification Is Best Guide for Claim Terms
Note:
The specification is the primary source for determining the meaning of claim terms, usually providing the most clarity.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourcePatent Application ContentClaim Form Requirements
StatutoryPermittedAlways
[mpep-2111-01-7259a701d243fa0ba0317b9e]
Claim Terms Can Have Different Meanings Defined
Note:
Applicants can define claim terms differently from their ordinary meaning by clearly stating these definitions in the specification.

The presumption that a term is given its ordinary and customary meaning may be rebutted by the applicant by clearly setting forth a different definition of the term in the specification. In re Morris, 127 F.3d 1048, 1054, 44 USPQ2d 1023, 1028 (Fed. Cir. 1997) (the USPTO looks to the ordinary use of the claim terms taking into account definitions or other “enlightenment” contained in the written description); But c.f. In re Am. Acad. of Sci. Tech. Ctr., 367 F.3d 1359, 1369, 70 USPQ2d 1827, 1834 (Fed. Cir. 2004) (“We have cautioned against reading limitations into a claim from the preferred embodiment described in the specification, even if it is the only embodiment described, absent clear disclaimer in the specification.”). When the specification sets a clear path to the claim language, the scope of the claims is more easily determined and the public notice function of the claims is best served.

Jump to MPEP SourceSpecificationPatent Application Content
StatutoryPermittedAlways
[mpep-2111-01-85da27ad18b6a551a94cb514]
Specification as Glossary for Claim Terms
Note:
The specification is the best source for determining the meaning of claim terms, with other sources like claims, drawings, and prior art also considered.

The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. See, e.g., In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (construing the term “electrochemical sensor” as “devoid of external connection cables or wires to connect to a sensor control unit” to be consistent with “the language of the claims and the specification”); In re Suitco Surface, Inc., 603 F.3d 1255, 1260-61, 94 USPQ2d 1640, 1644 (Fed. Cir. 2010) (construing the term “material for finishing the top surface of the floor” to mean “a clear, uniform layer on the top surface of a floor that is the final treatment or coating of a surface” to be consistent with “the express language of the claim and the specification”); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996) (construing the term “solder reflow temperature” to mean “peak reflow temperature” of solder rather than the “liquidus temperature” of solder in order to remain consistent with the specification); Malvern Panalytical Inc. v. TA Instruments-Waters LLC, 85 F.4th 1365, 1374-75, 2023 USPQ2d 1297 (Fed. Cir. 2023) (the court construed “pipette guiding mechanism” as a mechanism that guides the pipette assembly either manually or automatically, and stated that the plain and ordinary meaning can be ascertained by examining the claim language, specification, and the prosecution history).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryRequiredAlways
[mpep-2111-01-fe9d5be852cb4155020f81fd]
Applicant Must Define Claim Terms Differently
Note:
The applicant must clearly define a claim term with a special meaning different from its ordinary meaning in the specification.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryPermittedAlways
[mpep-2111-01-d3397916a7b66399ddb049d7]
Applicant Can Define Claim Terms Differently
Note:
An applicant may define claim terms differently from their ordinary meaning by clearly setting forth the definition in the specification.

An applicant is entitled to be their own lexicographer and may rebut the presumption that claim terms are to be given their ordinary and customary meaning by clearly setting forth a definition of the term that is different from its ordinary and customary meaning(s) in the specification at the relevant time. See In re Paulsen, 30 F.3d 1475, 1480, 31 USPQ2d 1671, 1674 (Fed. Cir. 1994) (holding that an inventor may define specific terms used to describe invention, but must do so “with reasonable clarity, deliberateness, and precision” and, if done, must “‘set out his uncommon definition in some manner within the patent disclosure’ so as to give one of ordinary skill in the art notice of the change” in meaning) (quoting Intellicall, Inc. v. Phonometrics, Inc., 952 F.2d 1384, 1387-88, 21 USPQ2d 1383, 1386 (Fed. Cir. 1992)).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-2ff3957deb3e8c6b7e8da061]
Claim Term Defined by Applicant Controls Interpretation
Note:
If an applicant provides a definition for a term, that definition controls the claim's interpretation.

Where an explicit definition is provided by the applicant for a term, that definition will control interpretation of the term as it is used in the claim. Toro Co. v. White Consolidated Industries Inc., 199 F.3d 1295, 1301, 53 USPQ2d 1065, 1069 (Fed. Cir. 1999) (meaning of words used in a claim is not construed in a “lexicographic vacuum, but in the context of the specification and drawings”). Thus, if a claim term is used in its ordinary and customary meaning throughout the specification, and the written description clearly indicates its meaning, then the term in the claim has that meaning. Old Town Canoe Co. v. Confluence Holdings Corp., 448 F.3d 1309, 1317, 78 USPQ2d 1705, 1711 (Fed. Cir. 2006) (The court held that “completion of coalescence” must be given its ordinary and customary meaning of reaching the end of coalescence. The court explained that even though coalescence could theoretically be “completed” by halting the molding process earlier, the specification clearly intended that completion of coalescence occurs only after the molding process reaches its optimum stage.).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-939dec95fc503784ec300149]
Claim Phrase Requires Only Specific Point of View
Note:
The claim phrase 'a point of view of the Wide camera' in a patent must be interpreted to require either a wide perspective or position, as defined by the specification.

However, it is important to note that any special meaning assigned to a term “must be sufficiently clear in the specification that any departure from common usage would be so understood by a person of experience in the field of the invention.” Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998). See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999) and MPEP § 2173.05(a). In Apple Inc. v. Corephotonics, Ltd., 81 F.4th 1353, 1358-60, 2023 USPQ2d 1056 (Fed. Cir. 2023), the claim phrase “a point of view of the Wide camera” was held to only require a “Wide perspective point of view or Wide position point of view” after reviewing the specification. In particular, the court found that a reasonable reading of the specification defined two different types of Wide point of view – perspective and position, whereas the claim language was broad as to the point of view. The court also explained that claims should not be interpreted in a way that would omit a disclosed embodiment, absent evidence to the contrary. Thus, given the review of the intrinsic evidence, the court held that the claim language only required Wide perspective or Wide position point of view, but not both.

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryPermittedAlways
[mpep-2111-01-8371c877af86afffe25eb977]
Claim Terms Defined by Specification Context
Note:
The meaning of claim terms can be defined based on their usage in the specification context, unless the specification is ambiguous.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-a436a1adb9e9818a070b4e60]
Claim Terms Given Ordinary Meaning When Ambiguous
Note:
When the specification is unclear about whether claim terms are used with a special meaning, they should be interpreted according to their ordinary meaning.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-5d8967c4f52042d9c88020b9]
Claim Term 'About' Means Approximately
Note:
The term 'about' in a claim should be construed as meaning approximately, not exactly, according to the specification's plain and ordinary meaning.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourceInterpreting Claims (MPEP 2173.01)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-47e135f8a080f60b143a6c4a]
Specification Must Clearly Exclude Particular Features
Note:
The specification must clearly exclude a particular feature for it to be outside the claim scope, even if the claims might otherwise appear broad enough to include it.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourcePatent Application ContentClaims Too Broad (Enablement/Written Description)
StatutoryInformativeAlways
[mpep-2111-01-c7685bf07eb0838c3ebd8f2c]
Disavowal of Claim Scope Must Be Clear and Unmistakable
Note:
The specification must clearly disavow a broader claim scope for it to be considered outside the patent claims, even if the claim language is ambiguous.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourcePatent Application ContentClaims Too Broad (Enablement/Written Description)
StatutoryRecommendedAlways
[mpep-2111-01-e9bc362a16ebda4016da1890]
Claim Term Uses Ordinary Meaning If No Special Definition
Note:
If the specification does not define a claim term, use its ordinary and customary meaning in the art.

The first question is to determine whether a claim term has an ordinary and customary meaning to those of ordinary skill in the art. If so, then the examiner should check the specification to determine whether it provides a special definition for the claim term. If the specification does not provide a special definition for the claim term, the examiner should apply the ordinary and customary meaning to the claim term. If the specification provides a special definition for the claim term, the examiner should use the special definition. However, because there is a presumption that claim terms have their ordinary and customary meaning and the specification must provide a clear and intentional use of a special definition for the claim term to be treated as having a special definition, an Office action should acknowledge and identify the special definition in this situation.

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryRequiredAlways
[mpep-2111-01-dfaa794b591ac0e5b2c28829]
Claim Term Special Definition Must Be Acknowledged
Note:
Examiner must use special definition if provided in specification, but must acknowledge and identify it as such.

The first question is to determine whether a claim term has an ordinary and customary meaning to those of ordinary skill in the art. If so, then the examiner should check the specification to determine whether it provides a special definition for the claim term. If the specification does not provide a special definition for the claim term, the examiner should apply the ordinary and customary meaning to the claim term. If the specification provides a special definition for the claim term, the examiner should use the special definition. However, because there is a presumption that claim terms have their ordinary and customary meaning and the specification must provide a clear and intentional use of a special definition for the claim term to be treated as having a special definition, an Office action should acknowledge and identify the special definition in this situation.

Jump to MPEP SourceExamination ProceduresPatent Application Content
StatutoryRecommendedAlways
[mpep-2111-01-871c744053d76e3f7c960705]
Examiner Must Check Specification for Claim Term Meaning
Note:
If a claim term lacks an ordinary meaning, the examiner should refer to the specification to determine its meaning. If no clear meaning is found, apply broadest reasonable interpretation and reject under 35 U.S.C. 112(b).

Moving back to the first question, if a claim term does not have an ordinary and customary meaning, the examiner should check the specification to determine whether it provides a meaning to the claim term. If no reasonably clear meaning can be ascribed to the claim term after considering the specification and prior art, the examiner should apply the broadest reasonable interpretation to the claim term as it can be best understood. Also, the claim should be rejected under 35 U.S.C. 112(b) and the specification objected to under 37 CFR 1.75(d).

Jump to MPEP Source · 37 CFR 1.75(d)Patent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryRecommendedAlways
[mpep-2111-01-84881cdb4a7e2c10219b96e3]
Use Specification’s Claim Term Definition
Note:
Examiners must use the claim term definition provided in the specification unless otherwise specified.

If the specification provides a meaning for the claim term, the examiner should use the meaning provided by the specification. It may be appropriate for an Office action to acknowledge and identify the meaning provided by the specification in this situation.

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
Topic

Claim Form Requirements

11 rules
StatutoryInformativeAlways
[mpep-2111-01-c0737216923e9f15dc4109c9]
Claims Must Be Given Plain Meaning
Note:
Claims must be interpreted using the ordinary and customary meaning of terms as understood by those skilled in the art, unless inconsistent with the specification.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceClaim Form RequirementsRequired Claim ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-61b32e39da5c4427ee977241]
Claim Requires Single Microprocessor for All Functions
Note:
The claim must specify a single microprocessor capable of performing all generating, creating, and retrieving functions.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceClaim Form RequirementsRequired Claim Content
StatutoryInformativeAlways
[mpep-2111-01-b68a80cfb5432103e35ca94f]
Claim Requires Both Tasks, Not Just One
Note:
A claim must cover a single entity capable of performing all required tasks, not multiple entities each performing one task.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceClaim Form RequirementsRequired Claim ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-ef280c5d82b8f9b67fdecca6]
Claim Terms Must Have Ordinary Meaning
Note:
Under BRI, claim terms must be given their plain meaning unless inconsistent with the specification.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceClaim Form RequirementsRequired Claim ContentInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-1d8c710fc952588fb119fdcf]
Clear Specification Path for Claim Determination
Note:
When the specification clearly links to claim language, the scope of claims is easily determined and public notice is best served.

The presumption that a term is given its ordinary and customary meaning may be rebutted by the applicant by clearly setting forth a different definition of the term in the specification. In re Morris, 127 F.3d 1048, 1054, 44 USPQ2d 1023, 1028 (Fed. Cir. 1997) (the USPTO looks to the ordinary use of the claim terms taking into account definitions or other “enlightenment” contained in the written description); But c.f. In re Am. Acad. of Sci. Tech. Ctr., 367 F.3d 1359, 1369, 70 USPQ2d 1827, 1834 (Fed. Cir. 2004) (“We have cautioned against reading limitations into a claim from the preferred embodiment described in the specification, even if it is the only embodiment described, absent clear disclaimer in the specification.”). When the specification sets a clear path to the claim language, the scope of the claims is more easily determined and the public notice function of the claims is best served.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryPermittedAlways
[mpep-2111-01-4517ac766eb0cc5c1e514808]
Claims Must Not Import Description Limitations
Note:
Patent claims should not include limitations from the written description that are not explicitly stated in the claim language.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceClaim Form RequirementsSpecification
StatutoryInformativeAlways
[mpep-2111-01-b3963f0b498721706a10640e]
Claims Must Be Broadly Interpreted Consistent With Specification
Note:
The claims must be interpreted broadly according to the plain meaning and broad statements in the specification, not limited to specific disclosed embodiments.

In Sisvel Int’l S.A. v. Sierra Wireless, Inc., 81 F.4th 1231, 1236-37, 2023 USPQ2d 1030 (Fed. Cir. 2023), the court found that construing “connection rejection message” should be given its plain and ordinary meaning, and should not be construed in such a way as to improperly limit the claims to specific disclosed embodiments. The intrinsic evidence provided no basis to limit the claims to the preferred embodiments and a person of ordinary skill in the art would broadly interpret the claim language consistent with the broad statements in the specification.

Jump to MPEP SourceClaim Form RequirementsInterpreting Claims (MPEP 2173.01)
StatutoryPermittedAlways
[mpep-2111-01-7082524ded4839b505012160]
Claim Terms Must Be Construed Consistently With Specification
Note:
Claims must interpret terms based on the specification to ensure consistency with the disclosed invention.

The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. See, e.g., In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (construing the term “electrochemical sensor” as “devoid of external connection cables or wires to connect to a sensor control unit” to be consistent with “the language of the claims and the specification”); In re Suitco Surface, Inc., 603 F.3d 1255, 1260-61, 94 USPQ2d 1640, 1644 (Fed. Cir. 2010) (construing the term “material for finishing the top surface of the floor” to mean “a clear, uniform layer on the top surface of a floor that is the final treatment or coating of a surface” to be consistent with “the express language of the claim and the specification”); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996) (construing the term “solder reflow temperature” to mean “peak reflow temperature” of solder rather than the “liquidus temperature” of solder in order to remain consistent with the specification); Malvern Panalytical Inc. v. TA Instruments-Waters LLC, 85 F.4th 1365, 1374-75, 2023 USPQ2d 1297 (Fed. Cir. 2023) (the court construed “pipette guiding mechanism” as a mechanism that guides the pipette assembly either manually or automatically, and stated that the plain and ordinary meaning can be ascertained by examining the claim language, specification, and the prosecution history).

Jump to MPEP SourceClaim Form RequirementsInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-89d72bcec01ace19aff02c86]
Claim Language Requires Intrinsic Evidence Analysis
Note:
When claim language is unclear, intrinsic evidence must be analyzed to determine its meaning.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourceClaim Form RequirementsInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-b991df1cdeac1b51a2f6e2c7]
Claims Must Specify Perspective or Position for Wide Camera View
Note:
The claims must be limited to either a perspective or position point of view as defined in the specification, not both.

However, it is important to note that any special meaning assigned to a term “must be sufficiently clear in the specification that any departure from common usage would be so understood by a person of experience in the field of the invention.” Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998). See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999) and MPEP § 2173.05(a). In Apple Inc. v. Corephotonics, Ltd., 81 F.4th 1353, 1358-60, 2023 USPQ2d 1056 (Fed. Cir. 2023), the claim phrase “a point of view of the Wide camera” was held to only require a “Wide perspective point of view or Wide position point of view” after reviewing the specification. In particular, the court found that a reasonable reading of the specification defined two different types of Wide point of view – perspective and position, whereas the claim language was broad as to the point of view. The court also explained that claims should not be interpreted in a way that would omit a disclosed embodiment, absent evidence to the contrary. Thus, given the review of the intrinsic evidence, the court held that the claim language only required Wide perspective or Wide position point of view, but not both.

Jump to MPEP SourceClaim Form RequirementsPatent Application Content
StatutoryRequiredAlways
[mpep-2111-01-4a5ecb32b09eec3247e9f74b]
Claims Must Include Disclosed Embodiments
Note:
Claims should include all disclosed embodiments unless evidence proves otherwise, ensuring that the claim language is interpreted broadly but not omitting any described features.

However, it is important to note that any special meaning assigned to a term “must be sufficiently clear in the specification that any departure from common usage would be so understood by a person of experience in the field of the invention.” Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998). See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999) and MPEP § 2173.05(a). In Apple Inc. v. Corephotonics, Ltd., 81 F.4th 1353, 1358-60, 2023 USPQ2d 1056 (Fed. Cir. 2023), the claim phrase “a point of view of the Wide camera” was held to only require a “Wide perspective point of view or Wide position point of view” after reviewing the specification. In particular, the court found that a reasonable reading of the specification defined two different types of Wide point of view – perspective and position, whereas the claim language was broad as to the point of view. The court also explained that claims should not be interpreted in a way that would omit a disclosed embodiment, absent evidence to the contrary. Thus, given the review of the intrinsic evidence, the court held that the claim language only required Wide perspective or Wide position point of view, but not both.

Jump to MPEP SourceClaim Form RequirementsInterpreting Claims (MPEP 2173.01)
Topic

Patent Application Content

7 rules
StatutoryInformativeAlways
[mpep-2111-01-e738053da5d21b50b2492c65]
Inconsistent Specification Description Requires Extrinsic Evidence
Note:
When the specification inconsistently describes a claim term, extrinsic evidence is needed to interpret its meaning.

Any meaning of a claim term taken from the prior art must be consistent with the use of the claim term in the specification and drawings. Moreover, when the specification is clear about the scope and content of a claim term, there is no need to turn to extrinsic evidence for claim interpretation. 3M Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326-28, 107 USPQ2d 1717, 1726-27 (Fed. Cir. 2013) (holding that “continuous microtextured skin layer over substantially the entire laminate” was clearly defined in the written description, and therefore, there was no need to turn to extrinsic evidence to construe the claim). See also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1290, 2021 USPQ2d 848 (Fed. Cir. 2021) (finding that where the intrinsic evidence (i.e., the claims, written description and prosecution history) clearly supports a claim interpretation, it is unnecessary to resort to extrinsic evidence.). However, in some instances where neither the claims, nor the specification, nor the prosecution history offer sufficient clarity on claim scope, extrinsic evidence may become a necessary part of claim interpretation. In Actelion, the claim language of “a pH of 13 or higher” was unclear after analysis of the intrinsic evidence. The court looked to the specification, which inconsistently described the level of specificity for a pH of 13. Finally, the court turned to the prosecution history, which also did not provide any clarity as to whether a pH of 13 includes values that round to 13, such as 12.5. The court found that in this case extrinsic evidence should be consulted to understand “the meaning of a term in the relevant art during the relevant time period”. Actelion Pharmaceuticals Ltd v. Mylan Pharmaceuticals Inc., 85 F.4th 1167, 1172-74, 2023 USPQ2d 1314 (Fed. Cir. 2023) (quoting Teva Pharmaceuticals USA, Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-a4f4c927a5c3916176e9bf77]
Specification Describes Inventor’s Intent
Note:
The specification must clearly express the inventor’s intent, which determines the meaning of claim terms unless otherwise defined by the applicant or disclaimed in the specification.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)Claims Too Broad (Enablement/Written Description)
StatutoryRecommendedAlways
[mpep-2111-01-5575ad85cafe1893143ee64c]
Claim Terms Have Ordinary Meaning Unless Disclaimed
Note:
Claims must use terms with their ordinary meaning unless the specification clearly defines them differently or disavows a term's full scope.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)Claims Too Broad (Enablement/Written Description)
StatutoryInformativeAlways
[mpep-2111-01-19b2e1e37e22b2acbe78dd2c]
Specification Must Clarify Claim Scope
Note:
The specification must clarify the scope of claim terms, even if they are described differently for different embodiments.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)Claims Too Broad (Enablement/Written Description)
StatutoryInformativeAlways
[mpep-2111-01-fe97a4ad9acfc03b0f8b7f12]
Written Description Must Reflect Actual Process Stages
Note:
The written description must reflect that the completion of coalescence occurs after the molding process reaches its optimum stage, not earlier.

Where an explicit definition is provided by the applicant for a term, that definition will control interpretation of the term as it is used in the claim. Toro Co. v. White Consolidated Industries Inc., 199 F.3d 1295, 1301, 53 USPQ2d 1065, 1069 (Fed. Cir. 1999) (meaning of words used in a claim is not construed in a “lexicographic vacuum, but in the context of the specification and drawings”). Thus, if a claim term is used in its ordinary and customary meaning throughout the specification, and the written description clearly indicates its meaning, then the term in the claim has that meaning. Old Town Canoe Co. v. Confluence Holdings Corp., 448 F.3d 1309, 1317, 78 USPQ2d 1705, 1711 (Fed. Cir. 2006) (The court held that “completion of coalescence” must be given its ordinary and customary meaning of reaching the end of coalescence. The court explained that even though coalescence could theoretically be “completed” by halting the molding process earlier, the specification clearly intended that completion of coalescence occurs only after the molding process reaches its optimum stage.).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryRequiredAlways
[mpep-2111-01-a87a9b47a49292632418a921]
Special Term Must Be Clearly Defined
Note:
Any special term used in the specification must be clearly defined so that its departure from common usage is understood by a person experienced in the field of invention.

However, it is important to note that any special meaning assigned to a term “must be sufficiently clear in the specification that any departure from common usage would be so understood by a person of experience in the field of the invention.” Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998). See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999) and MPEP § 2173.05(a). In Apple Inc. v. Corephotonics, Ltd., 81 F.4th 1353, 1358-60, 2023 USPQ2d 1056 (Fed. Cir. 2023), the claim phrase “a point of view of the Wide camera” was held to only require a “Wide perspective point of view or Wide position point of view” after reviewing the specification. In particular, the court found that a reasonable reading of the specification defined two different types of Wide point of view – perspective and position, whereas the claim language was broad as to the point of view. The court also explained that claims should not be interpreted in a way that would omit a disclosed embodiment, absent evidence to the contrary. Thus, given the review of the intrinsic evidence, the court held that the claim language only required Wide perspective or Wide position point of view, but not both.

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)Claim Form Requirements
StatutoryInformativeAlways
[mpep-2111-01-01bf9851581a68d2cf8f46b0]
Specification Must Clarify Claim Terms Ambiguously Defined
Note:
The specification must clearly define claim terms that are ambiguously defined, rather than redefining them to mean exactly as claimed.

In some cases, the meaning of a particular claim term may be defined by implication, that is, according to the usage of the term in the context in the specification. See Phillips v. AWH Corp., 415 F.3d 1303, 1320-21, 75 USPQ2d 1321, 1332 (Fed. Cir. 2005) (en banc); Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996). But where the specification is ambiguous as to whether the inventor used claim terms inconsistent with their ordinary meaning, the ordinary meaning will apply. Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1370, 73 USPQ2d 1641, 1646 (Fed. Cir. 2005) (The Federal Circuit reversed the district court’s construction of the claim term “about” as “exactly.” The appellate court explained that a passage in the specification the district court relied upon for the definition of “about” was too ambiguous to redefine “about” to mean “exactly” in clear enough terms. The appellate court held that “about” should instead be given its plain and ordinary meaning of “approximately.”).

Jump to MPEP SourcePatent Application ContentInterpreting Claims (MPEP 2173.01)
Topic

Claims Too Broad (Enablement/Written Description)

5 rules
StatutoryInformativeAlways
[mpep-2111-01-b0cb710bb95bd0c50c99dac4]
Exceptions to Ordinary Claim Terms
Note:
The words in a claim generally have their ordinary and customary meaning, unless the applicant defines them differently or disavows their full scope in the specification.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourceClaims Too Broad (Enablement/Written Description)Patent Application Content
StatutoryInformativeAlways
[mpep-2111-01-92433cd1d85c9fb2cb569d84]
Claim Term Ordinary Meaning Not Modified
Note:
The specification does not redefine terms or disclaim their full scope, so claim terms should be given their ordinary and customary meaning in the art.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourceClaims Too Broad (Enablement/Written Description)Patent Application ContentInterpreting Claims (MPEP 2173.01)
StatutoryPermittedAlways
[mpep-2111-01-755315d81a2bb0b902277470]
Requirement for Clear Disavowal of Claim Scope
Note:
Applicant must clearly disavow the full scope of a claim term in the specification to rebut the presumption of plain meaning.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceClaims Too Broad (Enablement/Written Description)Interpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-c68031bea1d83b0857385178]
Prosecution History Estoppel Not Applicable During Prosecution
Note:
The doctrine of prosecution history estoppel cannot be used to limit claim scope during patent application examination.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceClaims Too Broad (Enablement/Written Description)Claim Scope and BreadthInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-1379b5c36d1ef750f8146929]
Disavowal Only Applies to Issued Patents
Note:
The doctrine of disavowing claim scope applies only to issued patents, not during prosecution.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceClaims Too Broad (Enablement/Written Description)Claim Scope and BreadthInterpreting Claims (MPEP 2173.01)
Topic

Description of Embodiments

4 rules
StatutoryInformativeAlways
[mpep-2111-01-4ea0a38371bfce73b70f4e16]
Claims Must Not Incorporate Preferred Embodiment Without Clear Disclaimer
Note:
Claims should not include limitations from the preferred embodiment in the specification unless there is a clear disclaimer stating otherwise.

The presumption that a term is given its ordinary and customary meaning may be rebutted by the applicant by clearly setting forth a different definition of the term in the specification. In re Morris, 127 F.3d 1048, 1054, 44 USPQ2d 1023, 1028 (Fed. Cir. 1997) (the USPTO looks to the ordinary use of the claim terms taking into account definitions or other “enlightenment” contained in the written description); But c.f. In re Am. Acad. of Sci. Tech. Ctr., 367 F.3d 1359, 1369, 70 USPQ2d 1827, 1834 (Fed. Cir. 2004) (“We have cautioned against reading limitations into a claim from the preferred embodiment described in the specification, even if it is the only embodiment described, absent clear disclaimer in the specification.”). When the specification sets a clear path to the claim language, the scope of the claims is more easily determined and the public notice function of the claims is best served.

Jump to MPEP SourceDescription of EmbodimentsDetailed Description
StatutoryProhibitedAlways
[mpep-2111-01-69f16b1a76d79b492810c69c]
Claims Must Not Incorporate Specific Embodiments
Note:
Claims should not include limitations from specific embodiments described in the written description if the claim language is broader.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceDescription of EmbodimentsClaim Form Requirements
StatutoryRequiredAlways
[mpep-2111-01-fbdfa0a02388182d6fa1cffc]
Claims Not Limited to Single Description
Note:
Patent claims should not be construed as limited to a single embodiment described in the specification.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceDescription of EmbodimentsDetailed DescriptionInterpreting Claims (MPEP 2173.01)
StatutoryInformativeAlways
[mpep-2111-01-9cc4058a798e35699493824d]
Order of Steps Not Required for Method Claims
Note:
The court held that method claims do not require a specific order of steps unless the language and specification explicitly mandate it.

“Though understanding the claim language may be aided by explanations contained in the written description, it is important not to import into a claim limitations that are not part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.” Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004). See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004) (discussing recent cases wherein the court expressly rejected the contention that if a patent describes only a single embodiment, the claims of the patent must be construed as being limited to that embodiment); E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1369, 67 USPQ2d 1947, 1950 (Fed. Cir. 2003) (“Interpretation of descriptive statements in a patent’s written description is a difficult task, as an inherent tension exists as to whether a statement is a clear lexicographic definition or a description of a preferred embodiment. The problem is to interpret claims ‘in view of the specification’ without unnecessarily importing limitations from the specification into the claims.”); Altiris Inc. v. Symantec Corp., 318 F.3d 1363, 1371, 65 USPQ2d 1865, 1869-70 (Fed. Cir. 2003) (Although the specification discussed only a single embodiment, the court held that it was improper to read a specific order of steps into method claims where, as a matter of logic or grammar, the language of the method claims did not impose a specific order on the performance of the method steps, and the specification did not directly or implicitly require a particular order). See also subsection IV, below. When an element is claimed using language falling under the scope of 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, 6 th paragraph (often broadly referred to as means- (or step-) plus- function language), the specification must be consulted to determine the structure, material, or acts corresponding to the function recited in the claim, and the claimed element is construed as limited to the corresponding structure, material, or acts described in the specification and equivalents thereof. In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994) (see MPEP § 2181MPEP § 2186).

Jump to MPEP SourceDescription of EmbodimentsPatent Application ContentInterpreting Claims (MPEP 2173.01)
Topic

PTAB Jurisdiction

4 rules
StatutoryInformativeAlways
[mpep-2111-01-49b648d91eee7df22619d584]
Improper Import of Limitations from Specification
Note:
The court ruled that claims should not include limitations not present in the claims and improperly imported from the specification.

In Zletz, supra, the examiner and the Board had interpreted claims reading “normally solid polypropylene” and “normally solid polypropylene having a crystalline polypropylene content” as being limited to “normally solid linear high homopolymers of propylene which have a crystalline polypropylene content.” The court ruled that limitations, not present in the claims, were improperly imported from the specification. See also In re Marosi, 710 F.2d 799, 802, 218 USPQ 289, 292 (Fed. Cir. 1983) (“'[C]laims are not to be read in a vacuum, and limitations therein are to be interpreted in light of the specification in giving them their ‘broadest reasonable interpretation.'” (quoting In re Okuzawa, 537 F.2d 545, 548, 190 USPQ 464, 466 (CCPA 1976)). The court looked to the specification to construe “essentially free of alkali metal” as including unavoidable levels of impurities but no more.).

Jump to MPEP SourcePTAB JurisdictionPTAB Contested Case ProceduresEx Parte Appeals to PTAB
StatutoryInformativeAlways
[mpep-2111-01-39c6310e1b87f3c8c8ac5fdd]
Claims Not to Include Specification Limitations
Note:
The court ruled that claims should not include limitations from the specification unless explicitly stated in the claims.

In Zletz, supra, the examiner and the Board had interpreted claims reading “normally solid polypropylene” and “normally solid polypropylene having a crystalline polypropylene content” as being limited to “normally solid linear high homopolymers of propylene which have a crystalline polypropylene content.” The court ruled that limitations, not present in the claims, were improperly imported from the specification. See also In re Marosi, 710 F.2d 799, 802, 218 USPQ 289, 292 (Fed. Cir. 1983) (“'[C]laims are not to be read in a vacuum, and limitations therein are to be interpreted in light of the specification in giving them their ‘broadest reasonable interpretation.'” (quoting In re Okuzawa, 537 F.2d 545, 548, 190 USPQ 464, 466 (CCPA 1976)). The court looked to the specification to construe “essentially free of alkali metal” as including unavoidable levels of impurities but no more.).

Jump to MPEP SourcePTAB JurisdictionPTAB Contested Case ProceduresJudicial Review of Board Decisions
StatutoryInformativeAlways
[mpep-2111-01-0b779e5fe892f7cf54c2bb86]
Claims Must Be Interpreted Consistently With Specification
Note:
Claims must be interpreted in light of the specification, not including limitations not present in the claims.

In Zletz, supra, the examiner and the Board had interpreted claims reading “normally solid polypropylene” and “normally solid polypropylene having a crystalline polypropylene content” as being limited to “normally solid linear high homopolymers of propylene which have a crystalline polypropylene content.” The court ruled that limitations, not present in the claims, were improperly imported from the specification. See also In re Marosi, 710 F.2d 799, 802, 218 USPQ 289, 292 (Fed. Cir. 1983) (“'[C]laims are not to be read in a vacuum, and limitations therein are to be interpreted in light of the specification in giving them their ‘broadest reasonable interpretation.'” (quoting In re Okuzawa, 537 F.2d 545, 548, 190 USPQ 464, 466 (CCPA 1976)). The court looked to the specification to construe “essentially free of alkali metal” as including unavoidable levels of impurities but no more.).

Jump to MPEP SourcePTAB JurisdictionPTAB Contested Case ProceduresJudicial Review of Board Decisions
StatutoryInformativeAlways
[mpep-2111-01-90d870aa2625925c11983844]
Specification Construes 'Essentially Free of Alkali Metal' Including Impurities
Note:
The court construes the term ‘essentially free of alkali metal’ to include unavoidable levels of impurities but not more.

In Zletz, supra, the examiner and the Board had interpreted claims reading “normally solid polypropylene” and “normally solid polypropylene having a crystalline polypropylene content” as being limited to “normally solid linear high homopolymers of propylene which have a crystalline polypropylene content.” The court ruled that limitations, not present in the claims, were improperly imported from the specification. See also In re Marosi, 710 F.2d 799, 802, 218 USPQ 289, 292 (Fed. Cir. 1983) (“'[C]laims are not to be read in a vacuum, and limitations therein are to be interpreted in light of the specification in giving them their ‘broadest reasonable interpretation.'” (quoting In re Okuzawa, 537 F.2d 545, 548, 190 USPQ 464, 466 (CCPA 1976)). The court looked to the specification to construe “essentially free of alkali metal” as including unavoidable levels of impurities but no more.).

Jump to MPEP SourcePTAB JurisdictionPTAB Contested Case ProceduresJudicial Review of Board Decisions
Topic

AIA vs Pre-AIA Practice

3 rules
StatutoryInformativeAlways
[mpep-2111-01-e27d1ba1615a0712e0fa624f]
Requirement for AIA and Pre-AIA Practice
Note:
This rule applies to both AIA and pre-AIA applications, defining how timeframes are determined for inventorship and prior art considerations.

[Editor Note: This MPEP section is applicable regardless of whether an application is examined under the AIA or under pre-AIA law. For applications subject to the first inventor to file (FITF) provisions of the AIA, the relevant time is "before the effective filing date of the claimed invention". For applications subject to pre-AIA 35 U.S.C. 102, the relevant time is "at the time of the invention". See MPEP § 2150 et seq. Many of the court decisions discussed in this section involved applications or patents subject to pre-AIA 35 U.S.C. 102. These court decisions may be applicable to applications and patents subject to AIA 35 U.S.C. 102 but the relevant time is before the effective filing date of the claimed invention and not at the time of the invention.]

Jump to MPEP SourceAIA vs Pre-AIA PracticeDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)
StatutoryInformativeAlways
[mpep-2111-01-c60c7d1f0ff6305409f993ee]
Relevant Time for Pre-AIA Inventions
Note:
The relevant time for determining prior art under pre-AIA law is at the time of the invention.

[Editor Note: This MPEP section is applicable regardless of whether an application is examined under the AIA or under pre-AIA law. For applications subject to the first inventor to file (FITF) provisions of the AIA, the relevant time is "before the effective filing date of the claimed invention". For applications subject to pre-AIA 35 U.S.C. 102, the relevant time is "at the time of the invention". See MPEP § 2150 et seq. Many of the court decisions discussed in this section involved applications or patents subject to pre-AIA 35 U.S.C. 102. These court decisions may be applicable to applications and patents subject to AIA 35 U.S.C. 102 but the relevant time is before the effective filing date of the claimed invention and not at the time of the invention.]

Jump to MPEP SourceAIA vs Pre-AIA PracticeDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)
StatutoryInformativeAlways
[mpep-2111-01-2a5974aa562164effa267359]
Court Decisions on Pre-AIA Patents
Note:
This rule discusses court decisions involving patents subject to pre-AIA 35 U.S.C. 102, which may be applicable to AIA cases but with different timeframes.

[Editor Note: This MPEP section is applicable regardless of whether an application is examined under the AIA or under pre-AIA law. For applications subject to the first inventor to file (FITF) provisions of the AIA, the relevant time is "before the effective filing date of the claimed invention". For applications subject to pre-AIA 35 U.S.C. 102, the relevant time is "at the time of the invention". See MPEP § 2150 et seq. Many of the court decisions discussed in this section involved applications or patents subject to pre-AIA 35 U.S.C. 102. These court decisions may be applicable to applications and patents subject to AIA 35 U.S.C. 102 but the relevant time is before the effective filing date of the claimed invention and not at the time of the invention.]

Jump to MPEP SourceAIA vs Pre-AIA PracticeDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)
Topic

Claim Scope and Breadth

3 rules
StatutoryPermittedAlways
[mpep-2111-01-9dc7dd8e4a12247544edb301]
Specification May Include Intentional Claim Scope Disavowals
Note:
The specification may intentionally limit the scope of a claim term, even if it does not act as its own lexicographer.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).
CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002) The specification may also include an intentional disclaimer, or disavowal, of claim scope.

Jump to MPEP SourceClaim Scope and BreadthPatent Application Content
StatutoryInformativeAlways
[mpep-2111-01-256832652581a07ca02a0f75]
Disavowal Must Be Clear and Unmistakable
Note:
The specification must clearly disavow any broader claim scope for it to be considered in claim interpretation.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceClaim Scope and BreadthClaims Too Broad (Enablement/Written Description)
StatutoryPermittedAlways
[mpep-2111-01-3d39b4870af51de7e8a28c0b]
Disavowal by Implication in Specification
Note:
The specification can imply disavowal of a claim scope if it contains disparaging remarks about a feature and excludes that feature in every embodiment.

Applicant may also rebut the presumption of plain meaning by clearly disavowing the full scope of the claim term in the specification. Disavowal, or disclaimer of claim scope, is only considered when it is clear and unmistakable. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1341, 58 USPQ2d 1059, 1063 (Fed. Cir. 2001) (“Where the specification makes clear that the invention does not include a particular feature, that feature is deemed to be outside the reach of the claims of the patent, even though the language of the claims, read without reference to the specification, might be considered broad enough to encompass the feature in question.”); see also In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1365-67, 70 USPQ2d 1827, 1831-33 (Fed. Cir. 2004) (refusing to limit claim term “user computer” to only “single-user computers” even though “some of the language of the specification, when viewed in isolation, might lead a reader to conclude that the term… is meant to refer to a computer that serves only a single user, the specification as a whole suggests a construction that is not so narrow”). But, in some cases, disavowal of a broader claim scope may be made by implication, such as where the specification contains only disparaging remarks with respect to a feature and every embodiment in the specification excludes that feature. In re Abbott Diabetes Care Inc., 696 F.3d 1142, 1149-50, 104 USPQ2d 1337, 1342-43 (Fed. Cir. 2012) (holding that the broadest reasonable interpretation of the claim term “electrochemical sensor” does not include a sensor having “external connection cables or wires” because the specification “repeatedly, consistently, and exclusively depict[s] an electrochemical sensor without external cables or wires while simultaneously disparaging sensors with external cables or wires”). But see In re Clarke, 809 Fed. Appx. 787, 794, 2020 USPQ2d 10253 (Fed. Cir. 2020) (“The doctrine of prosecution history estoppel is inapplicable during prosecution. Instead the doctrine is applicable only to issued patents.”) (emphasis in the original). If the examiner believes that the broadest reasonable interpretation of a claim is narrower than what the words of the claim otherwise suggest as the result of implicit disavowal in the specification, then the examiner should make the interpretation clear on the record.

Jump to MPEP SourceClaim Scope and BreadthPatent Application Content
Topic

Determining Whether Application Is AIA or Pre-AIA

2 rules
StatutoryInformativeAlways
[mpep-2111-01-4f74cc0092632bc4c7757b68]
Requirement for Effective Filing Date Before Invention
Note:
The rule requires that applications subject to the first inventor to file provisions of the AIA must be filed before the effective filing date of the claimed invention.

[Editor Note: This MPEP section is applicable regardless of whether an application is examined under the AIA or under pre-AIA law. For applications subject to the first inventor to file (FITF) provisions of the AIA, the relevant time is "before the effective filing date of the claimed invention". For applications subject to pre-AIA 35 U.S.C. 102, the relevant time is "at the time of the invention". See MPEP § 2150 et seq. Many of the court decisions discussed in this section involved applications or patents subject to pre-AIA 35 U.S.C. 102. These court decisions may be applicable to applications and patents subject to AIA 35 U.S.C. 102 but the relevant time is before the effective filing date of the claimed invention and not at the time of the invention.]

Jump to MPEP SourceDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)AIA vs Pre-AIA Practice
StatutoryPermittedAlways
[mpep-2111-01-a4ab231d34425b73f9ba1cf0]
Time of Invention for AIA Patents
Note:
The relevant time for court decisions on applications and patents subject to AIA is before the effective filing date, not at the time of invention.

[Editor Note: This MPEP section is applicable regardless of whether an application is examined under the AIA or under pre-AIA law. For applications subject to the first inventor to file (FITF) provisions of the AIA, the relevant time is "before the effective filing date of the claimed invention". For applications subject to pre-AIA 35 U.S.C. 102, the relevant time is "at the time of the invention". See MPEP § 2150 et seq. Many of the court decisions discussed in this section involved applications or patents subject to pre-AIA 35 U.S.C. 102. These court decisions may be applicable to applications and patents subject to AIA 35 U.S.C. 102 but the relevant time is before the effective filing date of the claimed invention and not at the time of the invention.]

Jump to MPEP SourceDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)AIA vs Pre-AIA Practice
Topic

Required Claim Content

2 rules
StatutoryRequiredAlways
[mpep-2111-01-0c605ea4e3343b52a8e8ed97]
Claim Terms Must Have Plain Meaning Unless Inconsistent With Specification
Note:
Under BRI, claim terms must be given their ordinary meaning unless it conflicts with the specification.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceRequired Claim ContentInterpreting Claims (MPEP 2173.01)
StatutoryRequiredAlways
[mpep-2111-01-5efadbc340fe28e961e249fb]
Claims Must Use Plain Language Unless Inconsistent With Specification
Note:
Claims must be interpreted using their ordinary and customary meanings unless the specification indicates otherwise.

Under a broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning, unless such meaning is inconsistent with the specification. The plain meaning of a term means the ordinary and customary meaning given to the term by those of ordinary skill in the art at the relevant time. The ordinary and customary meaning of a term may be evidenced by a variety of sources, including the words of the claims themselves, the specification, drawings, and prior art. However, the best source for determining the meaning of a claim term is the specification – the greatest clarity is obtained when the specification serves as a glossary for the claim terms. Phillips v. AWH Corp., 415 F.3d 1303, 1315, 75 USPQ2d 1321, 1327 (Fed. Cir. 2005) (en banc) (“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.’” (quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The words of the claim must be given their plain meaning unless the plain meaning is inconsistent with the specification. In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (discussed below); Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004) (Ordinary, simple English words whose meaning is clear and unquestionable, absent any indication that their use in a particular context changes their meaning, are construed to mean exactly what they say. Thus, “heating the resulting batter-coated dough to a temperature in the range of about 400 o F to 850 o F” required heating the dough, rather than the air inside an oven, to the specified temperature.). See also Salazar v. AT&T Mobility LLC, 64 F.4th 1311, 1317-1318, 2023 USPQ2d 412 (Fed. Cir. 2023) (While the claim language, “a microprocessor for generating…, said microprocessor creating…, a plurality of parameter sets retrieved by said microprocessor…, said microprocessor generating…,” does not require there be only one microprocessor, the limitations to "said microprocessor" require a singular element—“a microprocessor”—to be capable of performing all of the recited “generating,” “creating,” and “retrieving” functions. Similarly, “[f]or a dog owner to have ‘a dog that rolls over and fetches sticks,’ it does not suffice that he have two dogs, each able to perform just one of the tasks.” (quoting In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016))).

Jump to MPEP SourceRequired Claim ContentInterpreting Claims (MPEP 2173.01)
Topic

Testimony Request Procedures

2 rules
StatutoryInformativeAlways
[mpep-2111-01-a32e001702c525067a575ecb]
Claim Term Defined by Prior Art
Note:
In some cases, the meaning of claim terms can be determined by how they are used in prior art including patents, applications, trade publications, and dictionaries.

In some cases it is also appropriate to look to how the claim term is used in the prior art, which includes prior art patents, published applications, trade publications, and dictionaries. Phillips v. AWH Corp., 415 F.3d 1303, 1317, 75 USPQ2d 1321, 1329 (Fed. Cir. 2005) (“Although we have emphasized the importance of intrinsic evidence in claim construction, we have also authorized district courts to rely on extrinsic evidence, which “consists of all evidence external to the patent and prosecution history, including expert and inventor testimony, dictionaries, and learned treatises.”)

Jump to MPEP SourceTestimony Request ProceduresUSPTO Employee Testimony
StatutoryInformativeAlways
[mpep-2111-01-ba0ad6ec7013da406d671553]
Extrinsic Evidence May Be Used for Claim Construction
Note:
District courts are authorized to use extrinsic evidence, such as expert testimony and dictionaries, in claim construction alongside intrinsic evidence.

In some cases it is also appropriate to look to how the claim term is used in the prior art, which includes prior art patents, published applications, trade publications, and dictionaries. Phillips v. AWH Corp., 415 F.3d 1303, 1317, 75 USPQ2d 1321, 1329 (Fed. Cir. 2005) (“Although we have emphasized the importance of intrinsic evidence in claim construction, we have also authorized district courts to rely on extrinsic evidence, which “consists of all evidence external to the patent and prosecution history, including expert and inventor testimony, dictionaries, and learned treatises.”)

Jump to MPEP SourceTestimony Request ProceduresUSPTO Employee Testimony
Topic

Determining Level of Ordinary Skill

2 rules
StatutoryInformativeAlways
[mpep-2111-01-fb473157276722789c7d9aa3]
Determine Ordinary Meaning for Claim Terms
Note:
Examiners must first determine if a claim term has an ordinary and customary meaning in the art. If not, they should check the specification for a special definition.

The first question is to determine whether a claim term has an ordinary and customary meaning to those of ordinary skill in the art. If so, then the examiner should check the specification to determine whether it provides a special definition for the claim term. If the specification does not provide a special definition for the claim term, the examiner should apply the ordinary and customary meaning to the claim term. If the specification provides a special definition for the claim term, the examiner should use the special definition. However, because there is a presumption that claim terms have their ordinary and customary meaning and the specification must provide a clear and intentional use of a special definition for the claim term to be treated as having a special definition, an Office action should acknowledge and identify the special definition in this situation.

Jump to MPEP SourceDetermining Level of Ordinary SkillPerson of Ordinary Skill in the Art
StatutoryRecommendedAlways
[mpep-2111-01-7a690f0a8e8a67f85ac9be58]
Examiner Must Verify Special Definitions In Specification
Note:
The examiner should check the specification to determine if a claim term has a special definition, applying it if found or using ordinary meaning otherwise.

The first question is to determine whether a claim term has an ordinary and customary meaning to those of ordinary skill in the art. If so, then the examiner should check the specification to determine whether it provides a special definition for the claim term. If the specification does not provide a special definition for the claim term, the examiner should apply the ordinary and customary meaning to the claim term. If the specification provides a special definition for the claim term, the examiner should use the special definition. However, because there is a presumption that claim terms have their ordinary and customary meaning and the specification must provide a clear and intentional use of a special definition for the claim term to be treated as having a special definition, an Office action should acknowledge and identify the special definition in this situation.

Jump to MPEP SourceDetermining Level of Ordinary SkillPatent Application Content
Topic

Apparatus/System Claims

1 rules
StatutoryInformativeAlways
[mpep-2111-01-76b0dbd4989da8f496ef774a]
Attachment of Actuators to Pad Not Limited
Note:
The claims for a tactile feedback system in video game controllers are not limited to actuators attached externally, as the term 'attached' includes both external and internal attachments according to ordinary meaning.

The only exceptions to giving the words in a claim their ordinary and customary meaning in the art are (1) when the applicant acts as their own lexicographer; and (2) when the applicant disavows or disclaims the full scope of a claim term in the specification. To act as their own lexicographer, the applicant must clearly set forth a special definition of a claim term in the specification that differs from the plain and ordinary meaning it would otherwise possess. CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002). The specification may also include an intentional disclaimer, or disavowal, of claim scope. In both of these cases, “the inventor’s intention, as expressed in the specification, is regarded as dispositive.” Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005) (en banc). See also Starhome GmbH v. AT&T Mobility LLC, 743 F.3d 849, 857, 109 USPQ2d 1885, 1890-91 (Fed. Cir. 2014) (holding that the term “gateway” should be given its ordinary and customary meaning of “a connection between different networks” because nothing in the specification indicated a clear intent to depart from that ordinary meaning); Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362, 1367-68, 101 USPQ2d 1457, 1460 (Fed. Cir. 2012) (The asserted claims of the patent were directed to a tactile feedback system for video game controllers comprising a flexible pad with a plurality of actuators “attached to said pad.” The court held that the claims were not limited to actuators attached to the external surface of the pad, even though the specification used the word “attached” when describing embodiments affixed to the external surface of the pad but the word “embedded” when describing embodiments affixed to the internal surface of the pad. The court explained that the plain and ordinary meaning of “attached” includes both external and internal attachments. Further, there is no clear and explicit statement in the specification to redefine “attached” or disavow the full scope of the term.).

Jump to MPEP SourceApparatus/System ClaimsInterpreting Claims (MPEP 2173.01)

Citations

Primary topicCitation
AIA vs Pre-AIA Practice
Determining Whether Application Is AIA or Pre-AIA
35 U.S.C. § 102
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
35 U.S.C. § 112
Claims
Interpreting Claims (MPEP 2173.01)
35 U.S.C. § 112(b)
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
35 U.S.C. § 112(f)
Claims
Interpreting Claims (MPEP 2173.01)
37 CFR § 1.75(d)
AIA vs Pre-AIA Practice
Determining Whether Application Is AIA or Pre-AIA
MPEP § 2150
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
MPEP § 2173.05(a)
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
MPEP § 2181
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
MPEP § 2186
Apparatus/System Claims
Claim Scope and Breadth
Claims
Claims Too Broad (Enablement/Written Description)
Interpreting Claims (MPEP 2173.01)
Patent Application Content
CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366, 62 USPQ2d 1658, 1662 (Fed. Cir. 2002)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Required Claim Content
Chef America, Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1372, 69 USPQ2d 1857 (Fed. Cir. 2004)
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
In re Donaldson, 16 F.3d 1189, 29 USPQ2d 1845 (Fed. Cir. 1994)
PTAB JurisdictionIn re Marosi, 710 F.2d 799, 802, 218 USPQ 289, 292 (Fed. Cir. 1983)
Claim Form Requirements
Claims
Description of Embodiments
In re Morris, 127 F.3d 1048, 1054, 44 USPQ2d 1023, 1028 (Fed. Cir. 1997)
PTAB JurisdictionIn re Okuzawa, 537 F.2d 545, 548, 190 USPQ 464, 466 (CCPA 1976)
Claims
Interpreting Claims (MPEP 2173.01)
In re Paulsen, 30 F.3d 1475, 1480, 31 USPQ2d 1671, 1674 (Fed. Cir. 1994)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Required Claim Content
In re Varma, 816 F.3d 1352, 1363, 118 USPQ2d 1342, 1350 (Fed. Cir. 2016)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Required Claim Content
In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989)
Claim Form Requirements
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Inc v. Sandoz, Inc., 574 U.S. 318, 331, 135 S. Ct. 831, 841, 113 USPQ2d 1269, 1276 (2015)
LLC v. Intuitive Surgical, Inc., 334 F.3d 1294, 1298, 67 USPQ2d 1132, 1136 (Fed. Cir. 2003)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Multiform Desiccants Inc. v. Medzam Ltd., 133 F.3d 1473, 1477, 45 USPQ2d 1429, 1432 (Fed. Cir. 1998)
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Old Town Canoe Co. v. Confluence Holdings Corp., 448 F.3d 1309, 1317, 78 USPQ2d 1705, 1711 (Fed. Cir. 2006)
Apparatus/System Claims
Claim Form Requirements
Claim Scope and Breadth
Claims
Claims Too Broad (Enablement/Written Description)
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Required Claim Content
Testimony Request Procedures
Phillips v. AWH Corp., 415 F.3d 1303, 1316 (Fed. Cir. 2005)
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
See also Liebel-Flarsheim Co. v. Medrad Inc., 358 F.3d 898, 906, 69 USPQ2d 1801, 1807 (Fed. Cir. 2004)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
See also Process Control Corp. v. HydReclaim Corp., 190 F.3d 1350, 1357, 52 USPQ2d 1029, 1033 (Fed. Cir. 1999)
Claim Form Requirements
Description of Embodiments
Interpreting Claims (MPEP 2173.01)
Superguide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875, 69 USPQ2d 1865, 1868 (Fed. Cir. 2004)
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Toro Co. v. White Consolidated Industries Inc., 199 F.3d 1295, 1301, 53 USPQ2d 1065, 1069 (Fed. Cir. 1999)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Patent Application Content
Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1583, 39 USPQ2d 1573, 1577 (Fed. Cir. 1996)
Claim Form Requirements
Claims
Interpreting Claims (MPEP 2173.01)
Required Claim Content
quoting Vitronics Corp. v. Conceptronic Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)

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