Devices that combine electronics with moving parts offer competitors many places to make a change: a different sensor, a different motor, a different location for a component, or logic moved into an app. We draft claims so that changes like these do not take a competing product outside the patent.
Where these devices are usually designed around
A typical consumer device in this category has a mechanism (a hinge, a pump, a drive train, a latch), one or more sensors, an actuator or motor, a controller, and often a companion app. The inventive idea is frequently not the mechanism itself, but what the device does in response to what it senses: a stroller that brakes when the handle is released, a pet feeder that dispenses differently based on weight, a fan that adjusts speed based on proximity. Competitors tend to keep that behavior and change the hardware around it.
The most common design-arounds we plan for are:
- replacing one sensing technology with another (an optical sensor for a Hall-effect sensor, a load cell for a pressure switch);
- moving the sensor to a different part of the device;
- using a different actuator (a solenoid in place of a motor, a linear actuator in place of a cam);
- moving decision-making from the device to a phone app or a cloud server;
- combining two claimed parts into one, or splitting one into two.
Claim the control logic separately from the mechanism
When the invention lies in how the device responds to conditions, we usually write at least one independent claim focused on that response, with the mechanism described only as far as needed. A separate independent claim may then cover the mechanism, for cases where it is also new. If the two are combined in one claim, a competitor who uses a different mechanism with the same logic, or the same mechanism with different logic, may avoid both.
Narrow: a capacitive touch sensor mounted in the handle; a DC gear motor coupled to a rear axle; and a microcontroller programmed to energize the motor to engage a disc brake when the touch sensor no longer detects a hand.
Broader: a sensor configured to detect whether a user is gripping the handle; a brake operable to resist rotation of at least one wheel; and a controller configured to cause the brake to engage in response to the sensor indicating that the user is no longer gripping the handle.
The broader version does not depend on the sensing technology, the motor type, the brake type, or where the components sit.
We describe the relationship, "in response to" a sensed condition, because that relationship is usually what a competitor cannot remove without losing the benefit of the product.
Avoid locking the claim to one sensor or actuator
A claim that names a specific sensor type, a specific mounting location, or a specific actuator can be avoided by a competitor who chooses a different one. We use generic terms such as "sensor", "actuator", "drive" or "biasing member" and support them in the specification with several examples of each: for a sensor that detects presence, we might describe capacitive, resistive, infrared, pressure-based and mechanical-switch versions, and several mounting locations.
Those examples matter for two reasons. They give the generic term written-description support under 35 U.S.C. § 112(a), and they reduce the risk that the claim is limited to the one example shown in the drawings. They also give us the material for dependent claims and, if needed, for continuation claims directed at a competitor's specific choice.
"Configured to" and the means-plus-function question
Phrases such as "a controller configured to" are common in this field. Courts have generally read "configured to" as meaning designed or programmed to perform the function, not merely capable of being modified to perform it. That is usually what we want: it reaches a competitor's device as sold.
Functional language must still convey structure. A term like "control module configured to" can risk interpretation as a means-plus-function limitation under 35 U.S.C. § 112(f), which would limit it to the algorithm and hardware actually disclosed. We reduce that risk by using terms that the field understands as structural ("controller", "processor", "circuit"), by reciting the inputs and outputs the controller acts on, and by disclosing the control logic in the specification with flowcharts or step-by-step descriptions, so that even under a § 112(f) reading the claim has adequate support and a reasonable scope.
When the app or the cloud does the work
Many devices now share their logic with a phone app or a server. A claim that requires the device, the phone and the server each to perform certain steps may be infringed by no single party, because the steps are divided among the manufacturer, the user and a cloud provider. Under current Federal Circuit law, direct infringement of a method claim generally requires that one entity perform or direct and control all of the steps.
We therefore write claim sets for each actor: a claim to the device alone, a claim to the app as a non-transitory computer-readable medium storing instructions, and where relevant a claim to the server. Each is drafted so that one company's product satisfies every element. Our software and electronics guide discusses this further.
Merging and splitting parts
If a claim recites "a first housing" and "a second housing", a competitor may argue that its one-piece housing does not meet the claim; if it recites "a housing" containing two functions, a competitor may split the functions into two components. We address this by stating in the specification that described components may be integral or separate, by claiming relationships rather than part counts where possible, and by including dependent claims for both the integrated and the separate versions.
Rounding out the claim set
Besides apparatus and control-logic claims, we consider a method of operating the device (useful where the method is distinctive even if the hardware varies), claims to a replaceable module or accessory a competitor might sell on its own, and claims to a retrofit kit for adding the feature to existing products. Each is drafted so that the party selling that item infringes directly. For real-world examples in this field, see claim examples from patents we drafted. Our overview of claim drafting principles explains the general approach behind each of these choices.
This page is general information, not legal advice for your situation.
Questions and answers
My device uses a specific sensor. Should the claim name it?
Usually not in the main independent claim, unless the sensor itself is what makes the invention new. We describe your sensor and several alternatives in the specification, claim the sensing function generically, and name your specific sensor in a dependent claim as a fallback.
Can I patent the app separately from the device?
Often yes. The app can be claimed as a non-transitory computer-readable medium storing instructions, or as a method performed by a mobile device. Eligibility rules for software apply, so the claim should be tied to a concrete technical operation such as controlling the device.
What if a competitor moves the logic to a cloud server?
That is one reason we write separate claim sets for the device, the app and the server. A claim that one party practices on its own is generally easier to enforce than one requiring several parties to act together.
Will describing many alternatives make my application expensive?
It adds some drafting time, mainly in the specification. We focus on alternatives a competitor could realistically adopt, since those are the ones most likely to matter later.
Talk to us about your invention
Feigin & Fridman, LLC is a patent and trademark firm in Clifton, New Jersey. We draft and prosecute utility and design patents for inventors and companies in the United States and abroad.
Attorney advertising. This website is for information purposes only and is not legal advice. Prior results do not guarantee a similar outcome.