Some patent claims describe what an element does rather than what it is — "means for actuating," "means for detecting," with no nuts and bolts recited. This is a means-plus-function claim, and U.S. law treats it differently from an ordinary structural claim. The trade is deliberate: an applicant is allowed to claim by function, but in exchange the law limits the claim's reach to the specific structure the patent's specification discloses for performing that function, plus equivalents of that structure. A claim that reads broadly on its face can therefore be narrow in effect.

The authority is 35 U.S.C. 112(f), which both permits the form and dictates how it is read:

"An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof."— 35 U.S.C. 112(f), source

The phrase that carries the consequence is "construed to cover the corresponding structure ... described in the specification and equivalents thereof." A means-plus-function element does not cover every conceivable way to perform the function. It covers the way (or ways) the specification describes, and structural equivalents of those. If the specification discloses one implementation for a "means," a competitor practicing a meaningfully different structure to achieve the same function may fall outside the claim — and, separately, a means-plus-function element with no corresponding structure disclosed at all can render the claim indefinite under section 112(b).

Why this matters in automotive control patents

Automotive control and actuation inventions are a natural home for functional language, because the contribution is often the control behavior rather than a single mechanical part. Consider Ford's granted US 12,145,673 B2 ("Steer-by-wire system and method," issued November 19, 2024). Its independent claim recites a steering wheel, a feedback actuator connected to the steering wheel, a detection device, and an electronic control system that holds the wheel at a target rotational position by generating a holding torque. These are written largely as structural elements — "a feedback actuator," "an electronic control system" — with the functions they perform attached.

That drafting choice is exactly the lever section 112(f) governs. A claim element written as "a feedback actuator configured to" perform a function generally recites structure and is read as an ordinary limitation. An element written as "means for generating a holding torque," with no structure, would instead trigger 112(f) and be limited to the holding-torque mechanism the specification describes. Whether a steer-by-wire or ADAS claim is broad or narrow can hinge on which side of that line each element falls — and the determination depends on the words of the claim and the structure in the specification, not on the abstract.

The Ford steer-by-wire claim illustrates why the distinction is not academic. Its electronic control system is recited as performing concrete functions — holding the steering wheel at a target rotational position, generating a holding torque, and continuously approximating a turning angle using a time-based adjustment function. A reader assessing scope must ask, element by element, whether each is anchored to recited structure or left purely functional. If the control behaviors are tied to named structural components and a disclosed algorithm, they are read as structural limitations; if any were cast as a bare "means" for a function, that element would be pulled back to whatever the specification discloses as performing it. The same words can yield very different scope depending on how the element is framed, which is precisely why claim construction in control-system patents so often turns on this single statutory provision.

The reading rule

For anyone analyzing automotive IP, 112(f) is a reminder that claim breadth is not a matter of how sweeping the language sounds. A claim element invoking "means" for a function reaches only as far as the specification's disclosed structure and its equivalents; an element reciting actual structure is read on its own terms.

When 112(f) is triggered — and the word "means"

The statute keys off function-without-structure, and the classic trigger is the literal phrase "means for." Use of that phrasing creates a presumption that the element is to be read under 112(f), tying it to the specification's disclosed structure. Conversely, reciting actual structure — "a feedback actuator," "a processor configured to," "an electronic control system" — generally keeps an element out of 112(f), so it is read as an ordinary structural limitation with its plain claim scope. Drafters make this choice deliberately. Avoiding "means" language and instead naming structural components is a common way to keep a claim from being narrowed to specific disclosed embodiments. The flip side is that an element written purely in functional terms with no structure recited, and no corresponding structure described in the specification, risks being held indefinite under section 112(b) — the function has been claimed but never tied to anything that performs it.

The equivalents question and software-implemented functions

The closing words of 112(f) — "and equivalents thereof" — keep a means-plus-function element from being trivially easy to design around. The element reaches not only the exact structure the specification discloses but structures that are equivalent to it for performing the recited function. For automotive control inventions, this matters most where the "structure" is a computer carrying out an algorithm: when a claimed function is performed by a processor, the corresponding structure the claim is limited to is generally the specific algorithm the specification discloses for that function, plus its equivalents — not any processor that could conceivably achieve the result. A steer-by-wire or ADAS patent that recites a "means for" computing a control output is therefore tethered to the control algorithm its specification actually describes. The discipline for an analyst is mechanical but essential: read each element of a control or actuation claim, flag the ones written in functional terms, determine whether 112(f) is triggered, and then turn to the specification to find the structure — including any algorithm — the element is limited to. Scope assessed any other way overstates what the claim covers. The statutory text is the authoritative source for how a means-plus-function element is construed.