§ 112(f) Claim Drafting
Functional Claiming
Claiming by what something does rather than what it is — with limits imposed by § 112(f) and the Williamson nonce word doctrine.
Williamson v. Citrix Online (Fed. Cir. 2015 en banc)
Eliminated the "strong presumption" that claims lacking "means" avoid § 112(f). Now, if a claim uses a generic nonce word (module, mechanism, unit) to recite a function without sufficient structural context, § 112(f) applies — limiting claim scope to the structures disclosed in the specification.
Nonce Word Risk Guide
Common Functional Words and § 112(f) Risk
means for [function]Automatically § 112(f)Explicit means-plus-function; spec must disclose corresponding structure or claim is indefinite
module for [function]§ 112(f) if no structureWilliamson (2015): 'module' is a nonce word; triggers § 112(f) if claim does not recite sufficient structure
mechanism for [function]§ 112(f) likelyGeneric structural term; triggers § 112(f) when used purely functionally without structural definition
unit configured to [function]§ 112(f) possibleIf no structural context; 'unit' alone is nonce; 'configured to' may save it if structural context present
circuit for [function]Low riskSome courts treat 'circuit' as structural in certain contexts; but may still trigger § 112(f) if purely functional
processor configured to [function]Generally safe'Processor' has structural meaning; combined with 'configured to' is generally not § 112(f) (Williamson analysis still applies)
§ 112(f) Trade-Off
Means-Plus-Function: Broad Language, Narrow Scope
When § 112(f) applies, the claim appears broad (covers any means to do X) but is actually narrow — it covers only the specific structures disclosed in the specification and their equivalents at the time of filing.
The Apparent Breadth
'A means for connecting two widgets' — sounds like it covers any connection method: screws, clips, welds, adhesives, magnets...
But actually, the claim only covers structures in the spec
The Actual Scope (§ 112(f))
If spec discloses only a screw connection, the 'means for connecting' claim covers only: screws + equivalents thereof at the time of filing (not later-developed clip technology).
Competitor using a clip → no infringement (structurally distinct)
Drafting Guidance
When to Use and Avoid Functional Claiming
Use functional language
When the invention is best defined by its result; in dependent claims adding functional limitations; when using 'configured to' or 'adapted to' with structural context.
Avoid pure functional language
In independent claims without structural context; whenever using generic nonce words (module, unit, mechanism) post-Williamson; when you have a narrow specific structure to protect.
If using means-plus-function intentionally
Ensure the spec contains detailed descriptions of ALL structures that should be covered; describe multiple embodiments; include equivalents discussion.
If spec is narrow, avoid § 112(f)
Use 'processor configured to' instead of 'means for processing'; add structural context for hardware claims; define 'module' with architectural description.
FAQ
What is functional claiming in patents?
Functional claiming describes a claim element by what it does (its function) rather than by what it is (its structure, material, or steps). A claim may say 'a fastener for securing the bracket' (functional) instead of 'a screw having threads engaging a nut' (structural). Functional language has legitimate uses — sometimes the best way to claim an invention is to describe the functional result achieved. But overly broad functional claiming creates two problems: (1) the claim may be so broad it preempts all ways of achieving the function, not just the inventor's specific approach; (2) if the claim uses 'means for' language or a functional nonce word without sufficient structural context, it may be interpreted under § 112(f) as a means-plus-function limitation, restricting the claim to the specific structures disclosed in the specification.
What is 35 U.S.C. § 112(f) means-plus-function claiming?
35 U.S.C. § 112(f) (formerly § 112 ¶ 6) allows a claim to express a functional limitation using the phrase 'means for [function]' or 'step for [step]'. When § 112(f) applies, the claim is construed to cover ONLY the structures, materials, or acts described in the specification that correspond to the recited function — plus equivalents thereof at the time of filing. This is a trade-off: the applicant gets to use convenient functional language, but the claim's scope is limited to the specific embodiments disclosed. If the specification does not disclose any structure corresponding to the claimed function, the claim is INDEFINITE under § 112(b) (Williamson v. Citrix). A means-plus-function claim can be non-infringed by a competitor who uses a structurally different method of achieving the same function, even if it achieves the same result.
What are nonce words and what did Williamson v. Citrix decide?
Nonce words are generic, structural-sounding words that do not actually import meaningful structural meaning — words like 'mechanism,' 'module,' 'device,' 'unit,' 'component,' 'system,' 'element,' 'member,' 'assembly,' and similar terms when used in a purely functional way. Williamson v. Citrix Online, LLC (Fed. Cir. 2015, en banc in part) eliminated the 'strong presumption' that claims using words other than 'means' do not invoke § 112(f). The new standard: if the claim uses a nonce word to recite a function without reciting sufficiently definite structure for performing that function, § 112(f) applies — the claim will be construed as means-plus-function, limited to structures disclosed in the specification. Example: 'a distributed learning control module for routing communication' — 'module' is a nonce word; if the claim does not define its structure, § 112(f) applies and the claim scope is limited to the specific software/hardware architecture described in the specification.
When is functional language acceptable in patent claims?
Functional language is acceptable in patent claims when: (1) IT DEFINES A CLAIM'S SCOPE PRECISELY ENOUGH — 'a nail configured to penetrate wood' is functional but precise enough; (2) THE FUNCTION IS AN INHERENT PROPERTY — functional language describing the intended purpose is acceptable as a limitation on what the claim covers (configured to, adapted to, for use in); (3) IN COMBINATION WITH STRUCTURAL CONTEXT — a claim that recites both structure AND function is fine ('a transistor biased to operate in saturation mode'); (4) IN DEPENDENT CLAIMS — adding a functional limitation to a structurally defined independent claim is common and appropriate; (5) IN PREAMBLES — 'a method for treating X' identifies the purpose without fully claiming the function. The danger zone: broad functional language in the body of an independent claim without structural definition, particularly for software/hardware where 'module for,' 'system for,' 'means for,' or 'unit for' can trigger § 112(f) under Williamson.
How does functional claiming affect patent infringement analysis?
Functional claiming affects infringement differently depending on whether § 112(f) applies: IF § 112(f) APPLIES (means-plus-function): the claim covers only the specific structures in the specification + equivalents AT THE TIME OF FILING. Accused products must use the same or equivalent structures disclosed in the specification. A structurally distinct but functionally similar implementation may not infringe. This can be quite narrow — it reduces the risk of overbreadth but also limits the patent owner's reach. IF § 112(f) DOES NOT APPLY (regular functional language): the functional limitation is applied literally — the accused product must perform the claimed function; but any structure that performs the function may satisfy the limitation. This is potentially much broader. PROSECUTION HISTORY ESTOPPEL: if the applicant argued during prosecution that only specific structures satisfy a functional limitation, the claim scope may be limited accordingly even without formal § 112(f) application.
Related Guides