The Drone-Fleet Claim: Modules, Functions, and FAA Rules
A client sends you claim 1 of a pending application: '1. A system for managing a fleet of delivery drones, comprising: a scheduling module configured to dynamically optimize delivery routes based on weather and battery data; a compliance engine configured to ensure each route satisfies FAA Part 107 requirements; and a memory storing a database of no-fly zones, wherein the scheduling module and the compliance engine communicate through a shared message bus.' The specification describes the scheduling module as 'a processor executing route-optimization software' and the compliance engine as 'a rules engine with a look-up table of FAA restrictions.' It does not describe any algorithm for 'dynamically optimize' beyond a citation to a textbook, and it does not define 'FAA Part 107 requirements.' The examiner has not yet acted. The client wants to know whether the claim is definite and whether the functional language will be construed under 112(f).
1. Identify which limitations invoke 35 U.S.C. 112(f) and what corresponding structure the specification must disclose.
Read the worked answer
Scheduling module and compliance engine are likely means-plus-function limitations under § 112(f). Under Williamson v. Citrix, a limitation that recites a function without sufficient structure is construed under § 112(f); the word module is a generic nonce word that does not itself connote a specific structure. Configured to dynamically optimize delivery routes is purely functional. Memory storing a database of no-fly zones is structural; a memory is a structural element, and storing a database is a physical state. Shared message bus is also structural.
For each § 112(f) limitation, the specification must disclose corresponding structure and the algorithm that performs the function. The specification's processor executing route-optimization software supplies structure for the scheduling module, but the function dynamically optimize requires a disclosed algorithm, not a citation to a textbook. The rules engine with a look-up table of FAA restrictions may supply structure for the compliance engine if the specification explains how the look-up table is applied to a route to ensure compliance. If the specification does not describe the algorithm, the claim is not entitled to the full scope of the function and may be invalid for lack of written description or indefiniteness.
2. Assess indefiniteness under Nautilus and propose specific claim amendments.
Read the worked answer
Under Nautilus, a claim is indefinite if a skilled artisan cannot understand its scope with reasonable certainty. Dynamically optimize is a term of degree with no metric; the claim does not say whether optimization means shortest time, lowest energy, or fewest drones, and the specification provides no algorithm. That is a strong indefiniteness risk. FAA Part 107 requirements is also problematic because the regulation can change and the claim does not identify a version or the specific operational limits.
Amend to concrete limitations: optimize delivery routes by minimizing total energy consumption subject to a maximum delivery time of 30 minutes and satisfy the operating limitations of 14 C.F.R. § 107.51 in effect on the filing date, including a maximum altitude of 400 feet and visual line of sight. If those specifics are not supported, add them to the specification in a continuation or CIP, not by new matter in the pending case. For the § 112(f) limitations, either recite structure in the claim (a processor programmed to execute a route-optimization algorithm that ...) or add a detailed algorithm to the specification. A claim that survives § 112 will be narrower but enforceable.
3. Explain how the claim would be construed during examination versus in litigation, and what that means for the client's enforcement strategy.
Read the worked answer
During prosecution, the examiner applies the broadest reasonable interpretation consistent with the specification. For § 112(f) limitations, the examiner will look for corresponding structure and will reject the claim if the structure is missing or the algorithm is not disclosed. In litigation, the court applies Phillips and may treat module and engine as means-plus-function terms under Williamson, but the construction is based on the issued patent and the prosecution history.
The practical difference is that a § 112(f) construction is narrow: it covers the disclosed algorithm and equivalents, not every software implementation. That narrowness can help validity but hurt infringement. The client should not assume the claim covers any scheduling module; it covers the disclosed route-optimization algorithm and equivalents. The FAA Part 107 requirements limitation may be construed to the version of the regulation at issue, creating uncertainty. Amend now to add structure and specific metrics. If the client wants broad functional coverage, the specification must disclose multiple algorithms and structural alternatives; otherwise the claim will be limited to the disclosed embodiment.