Patent Claims Strategy

Patent claims strategy is the deliberate design of the claim set to maximize enforceable protection while minimizing invalidity risk: WHY CLAIMS MATTER: the claims — and only the claims — define the scope of the patent right; the specification describes the invention; the claims define what competitors cannot do without a license; a broad but invalid claim provides zero protection; a narrow but valid claim provides only limited protection; the goal is the BROADEST VALID CLAIM SET; ECONOMIC VALUE OF CLAIMS: claim scope directly determines licensing leverage; broad independent claims = competitors must pay for broad exclusion; narrow dependent claims = fallback if the broad claim is invalidated; multiple independent claim categories = coverage of all forms of infringement (making, using, selling, importing); CLAIM STRATEGY OPERATES AT MULTIPLE LEVELS: (1) PROSECUTION: what claims to file initially; what amendments to make during examination; what concessions to avoid; how to manage prosecution history; (2) POST-GRANT: what continuation claims to file after the original patent issues; how to amend claims in IPR/PGR; (3) ENFORCEMENT: which claims to assert in litigation; which claims are strongest; which claims can survive invalidity challenge; STRATEGIC TRADEOFFS: broader claims → more likely to cover competitors' products → more likely to be challenged/invalidated; narrower claims → easier to obtain allowance → easier to survive validity challenge → less business value; MULTI-CLAIM STRATEGY RATIONALE: method claim covers the act of performing the steps (anyone who performs the method infringes); apparatus/system claim covers the product (easier to prove infringement by product inspection); CRM claim covers the software product (covers the sale of software); claiming the same invention from all angles prevents design-arounds that are technically equivalent.

Independent claim drafting determines the maximum scope of protection: STRUCTURE OF AN INDEPENDENT CLAIM: PREAMBLE: introduces the claim ('A method for...'; 'A system comprising...'); generally non-limiting (does not restrict the claim) UNLESS the preamble 'gives life and meaning' to the claim; keep preambles short and non-limiting; TRANSITION TERM: the pivot between the preamble and the body: 'comprising' — OPEN ENDED: the most common; the claim is not limited to the listed elements; additional elements can be present; preferred for maximum scope; 'consisting of' — CLOSED: the claim is limited to exactly the listed elements; no additional elements; used in chemistry/pharmaceutical claims to prevent infringement by mixtures; 'consisting essentially of' — MIDDLE GROUND: allows additional elements that do NOT materially affect the basic and novel characteristics of the invention; CLAIM BODY: the elements, each on a separate line; each element introduced with 'a' or 'an' or 'the' (must have antecedent basis); CLAIM ELEMENT TYPES: structural (what it is); functional (what it does); relational (how elements relate to each other); CLAIMING THE RIGHT LEVEL OF ABSTRACTION: too broad → likely anticipated by prior art; too narrow → easy to design around; BREADTH CALIBRATION APPROACH: (1) identify the core inventive concept (what makes this invention novel and non-obvious?); (2) draft the broadest claim that captures that concept without incorporating prior art; (3) check: does this broad claim have prior art problems? if yes, narrow appropriately; MULTIPLE INDEPENDENT CLAIMS: multiple independent claims in DIFFERENT CATEGORIES cover different forms of infringement; PTAB TRICK: if the patent owner amends independent claim 1 to overcome a rejection, the amendment may create prosecution history estoppel; a separate independent claim 2 that was never amended may avoid that estoppel.

Dependent claims serve multiple strategic functions beyond just narrowing the independent claim: LEGAL FUNCTION: a dependent claim incorporates all elements of the claim it depends from and adds additional limitations (35 U.S.C. § 112(d)); an independent claim can be infringed even if the dependent claim is not infringed (the dependent claim is more specific than necessary); FALLBACK FUNCTION: if the independent claim is invalidated (by prior art or other grounds), the dependent claim may survive and still provide some protection; SPECIFIC COMMERCIAL EMBODIMENT FUNCTION: dependent claims can cover the specific commercial product even if the independent claim covers a broader concept; claim the commercial product exactly as made/sold — this strengthens the nexus for secondary considerations; CLAIM DIFFERENTIATION DOCTRINE: if dependent claim 3 recites element X, there is a presumption that independent claim 1 does NOT require element X; use claim differentiation strategically to keep independent claims broad; STRATEGIC DEPENDENT CLAIMS — WHAT TO INCLUDE: specific numerical ranges (concentrations, temperatures, pressures, dimensions); specific materials or compounds; specific process steps; specific combinations of elements; specific configurations; alternative embodiments; COST CONSIDERATIONS: first 20 claims: included in basic USPTO filing fee; 21+ claims: $240 each (large entity) / $120 (small entity) / $60 (micro entity); claims over 3 independent: $460 each (large entity); PRACTICAL APPROACH: use 15-20 dependent claims; prioritize: commercially important embodiments; likely design-around targets; specific examples that support secondary considerations; DEPENDENT CLAIM HIERARCHY: claim 2 depends from claim 1 (adds one element); claim 3 depends from claim 2 (adds another element); claim 4 depends from claim 1 (alternative embodiment at same level); this creates 'claim trees' that provide layered fallbacks.

Prosecution history management is a critical and often overlooked part of claims strategy: PROSECUTION HISTORY ESTOPPEL (PHE): when a patent applicant narrows claims during prosecution to overcome a prior art rejection (or a § 112 rejection), that narrowing creates estoppel; PHE bars the patent owner from later arguing, in litigation, that the doctrine of equivalents covers what was surrendered; Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co. (S.Ct. 2002): established the complete bar/flexible bar framework for PHE; ARGUMENT-BASED ESTOPPEL: even without amending claims, clear and unmistakable arguments distinguishing prior art can create prosecution history estoppel; the argument must be clear from the record; less powerful than amendment-based estoppel but still relevant; MANAGING PROSECUTION HISTORY: AMENDMENTS: narrow claims only as far as necessary; avoid over-narrowing to obtain allowance; if possible, amend only dependent claims and maintain broad independent claims; ARGUMENTS: avoid clearly disclaiming claim scope; frame arguments as the prior art not anticipating the specific claim element, rather than disclaiming the claim element itself; RECORD MANAGEMENT: responses to office actions become part of the prosecution history; be careful about language used in arguments; don't agree with examiner's interpretation without understanding the long-term impact; CONTINUATION STRATEGY AS PROSECUTION HISTORY MANAGEMENT: if the original application's prosecution history created estoppel on certain claim scope, file a continuation with fresh claims that don't have that estoppel; continuation claims can cover the same technology from a different angle; 'CLAIM WATCHING': monitor continuation applications to recapture scope as competitors' products become known; draft continuation claims specifically to cover known competitor products; INTERVIEW STRATEGY: examiner interviews can resolve rejections without creating estoppel (if not followed up with an amendment); document the interview properly; use interviews to understand the examiner's interpretation before making claim amendments.

Filing claims in multiple categories provides comprehensive coverage and withstands design-arounds: THE FOUR CATEGORIES FOR SOFTWARE/TECH PATENTS: METHOD/PROCESS CLAIMS: claim the steps performed by the computer or system; covers the use of the invention regardless of who makes/sells the implementing hardware; a user who performs the steps infringes even without buying the product; example: 'A method comprising: receiving a first data input; processing the data using a neural network having X layers...'; APPARATUS/SYSTEM CLAIMS: claim the structural components; covers the product as manufactured and sold; easier to prove infringement by examining the product; can often be shown to infringe by reading product documentation alone; example: 'A system comprising: a processor; a memory storing instructions that when executed cause the processor to: receive data input; process the data...'; COMPUTER-READABLE MEDIUM (CRM) CLAIMS: claim the software product stored on a non-transitory medium; covers the sale of the software, the distribution of software products; critical for enforcement against software publishers; IMPORTANT: 'non-transitory' must be specified to avoid § 101 eligibility issues with transitory signals; example: 'A non-transitory computer-readable medium storing instructions that when executed by a processor cause the processor to...'; NETWORK/SYSTEM CLAIMS: for distributed systems — claim the combination of devices/components; coverage of SaaS infringement patterns; STRATEGIC RATIONALE: different claims cover different actors: method claim → covers the user performing the steps (end-user use); apparatus claim → covers the manufacturer and seller; CRM claim → covers software distribution; system claim → covers the service provider; DIVIDED INFRINGEMENT RISK: Akamai Technologies v. Limelight Networks (Fed. Cir. 2015 en banc): for method claim infringement by multiple parties, need one party 'direct or control' or all parties form a 'joint enterprise'; mitigate by drafting method claims performable by a single actor; CLAIM CONSISTENCY: all claim categories should be supported by the same specification; use consistent terminology across method, apparatus, and CRM claims.