Patent Drafting

A complete US utility patent application consists of several required components: SPECIFICATION (37 C.F.R. § 1.71-1.79): TITLE: brief and technical; CROSS-REFERENCE TO RELATED APPLICATIONS: priority claims to provisional applications (35 U.S.C. § 119(e)), parent applications (§ 120), or foreign applications (§ 119(a)); TECHNICAL FIELD: brief description of the field; BACKGROUND: prior art context; the problem the invention solves; be careful: overly narrow background can limit claim scope via prosecution history estoppel; BRIEF SUMMARY: brief description of the invention; often mirrors the broadest claim; BRIEF DESCRIPTION OF DRAWINGS: one sentence per figure identifying what each figure shows; DETAILED DESCRIPTION: the most important part of the specification; must enable a POSITA to make and use the invention (§ 112(a)); must provide written description support for all claimed elements (§ 112(a)); best mode required (§ 112(a)); must define any non-standard claim terms (serves as the 'lexicographer'); include multiple embodiments — don't limit disclosure to a single embodiment; CLAIMS (37 C.F.R. § 1.75): the legally operative part of the patent; define the exclusive right; ABSTRACT (37 C.F.R. § 1.72(b)): 150-word maximum; describes the disclosure (not the claims); DRAWINGS (37 C.F.R. § 1.81-1.88): required if necessary to understand the invention; black-and-white line drawings (photographs allowed only in some cases); figures numbered consecutively; reference numerals used consistently; all elements referenced in the specification; FEES: USPTO filing fees vary by entity size: large entity: $1,960 (basic); small entity (≤500 employees): $980; micro entity: $490; TIMING: standard examination: 24-30 months; Track One (prioritized): ~6-12 months ($4,200 large entity).

Patent claim architecture is the most strategically important part of patent drafting: CLAIM HIERARCHY — INDEPENDENT CLAIMS: the broadest claims that stand alone; infringement of an independent claim = all dependent claims of that independent claim are also infringed; an independent claim has no structural prerequisite for infringement; DEPENDENT CLAIMS: narrow the independent claim by adding limitations; serve as 'fallbacks' — if the independent claim is invalidated, dependent claims may survive; add specific embodiments, ranges, materials, methods, etc.; MULTI-CLAIM STRATEGY: method claims: broader than apparatus claims in software (method can be performed on any hardware); apparatus/system claims: easier to prove infringement (product examination vs. watching a process); computer-readable medium (CRM) claims: necessary for software patents; claim the same invention from multiple angles; CLAIM BREADTH CALIBRATION: too broad → prior art will anticipate or render obvious; too narrow → easy to design around; ideal: broadest claim that is novel and non-obvious over the prior art; INDEPENDENT CLAIM DRAFTING: one element per line (readability); use transition 'comprising' (open-ended — additional elements allowed); each element must be introduced with 'a' or 'an' (antecedent basis); elements must be consistently named throughout the claim; CLAIM LIMITATIONS TO AVOID: functional claiming at the point of novelty without structural support → § 112(f) means-plus-function trap; result-based claiming without structural definition → vague and often invalid; negative limitations without clear antecedent basis; DEPENDENT CLAIM STRATEGY: 15-20 dependent claims is common; claim specific embodiments that matter commercially; claim specific ranges (especially in chemistry/materials patents); claim combinations of features; claim all commercially significant variations; MEANS-PLUS-FUNCTION CLAIMING (§ 112(f)): triggered by 'means for' language; limits claim to corresponding structure described in the specification plus equivalents; useful for some purposes but generally avoided in software patents; MULTIPLE INDEPENDENT CLAIMS: 35 U.S.C. § 112(n): multiple independent claims in different categories; allows broad independent + backup independent at narrower scope.

Software and AI patent drafting requires specific strategies to navigate § 101 Alice/Mayo challenges: FRAME AS A TECHNICAL IMPROVEMENT: the specification and claims must articulate a TECHNICAL improvement, not just a business process improvement; compare: 'a method for managing financial transactions' (abstract idea) vs. 'a method for reducing network congestion by prioritizing packet routing based on real-time bandwidth measurements' (technical improvement); the improvement must be in the computer science domain, not just 'doing it on a computer'; SPECIFIC TECHNICAL ELEMENTS: claim specific technical components: specific hardware architectures; specific data structures; specific algorithms with quantifiable parameters; specific protocols; avoid: generic computer; generic network; generic database; generic processor; ORDERED COMBINATION: even if individual elements are known, the ordered combination of specific technical elements performing a specific technical function can be eligible; ALICE/MAYO PROSECUTION STRATEGY: Step 2A Prong 2 — 'practical application': if the claim integrates a judicial exception into a practical application, it is eligible; argue the technical problem and technical solution in the response; Step 2B — 'significantly more': even if directed to an abstract idea, argue the claim adds 'significantly more' (technical improvement; unconventional combination); AI-SPECIFIC STRATEGIES: AI TRAINING CLAIMS: claim the specific training data structure; the specific neural network architecture (number of layers, connection type); the specific loss function; the specific output threshold; AI INFERENCE CLAIMS: claim the specific inference pipeline; the technical effects (latency reduction; accuracy improvement at specific thresholds); the specific hardware configuration; AVOID: 'a method of using artificial intelligence to detect fraud' → abstract; 'a neural network comprising a convolutional layer with X kernel size and Y filter count trained on Z-dimensional feature vectors to identify anomalous transaction patterns with a false positive rate below W%' → more specific and defensible; SPECIFICATION PRACTICE: include quantitative data on technical performance; describe the technical problem in terms of prior art limitations; include multiple embodiments of specific architectures; avoid business-context framing (focus on the technical, not the commercial).

Experienced patent prosecutors identify recurring drafting errors that create invalidity risk: ERROR 1 — INSUFFICIENT WRITTEN DESCRIPTION: the specification does not provide adequate written description support for all claim elements as ultimately issued; the Ariad Pharmaceuticals test: does the specification 'reasonably convey' to a POSITA that the inventor 'possessed' the claimed invention at the time of filing?; FIX: draft the specification as broadly as the claims; disclose multiple embodiments; do not limit the disclosure to a single implementation; ERROR 2 — CLAIM ELEMENTS NOT IN SPECIFICATION: a claim element has no corresponding description in the specification; this creates § 112(a) written description rejection; FIX: for every claim element, ensure the specification has corresponding support; ERROR 3 — INCONSISTENT CLAIM TERMINOLOGY: a term used in claim 1 is described differently in claim 5; the Phillips v. AWH lexicographer rule: if you define a term in the specification, you are bound by that definition; FIX: use consistent nomenclature throughout; define terms explicitly; ERROR 4 — EXCESSIVE PREAMBLE LIMITATION: the preamble of an independent claim includes elements that inadvertently limit the claim scope; preamble may be limiting or non-limiting (context-dependent); FIX: keep preambles short; avoid including structural elements in the preamble; ERROR 5 — CLAIMS TOO NARROW AT FILING: the application is filed with only specific narrow claims; fails to anticipate broader coverage opportunities; FIX: always include at least one broad independent claim that covers the broadest possible version of the invention; ERROR 6 — BEST MODE NOT DISCLOSED: the application does not describe the best known way to practice the invention at the time of filing; FIX: include the best mode (even though it is no longer an invalidity ground under AIA, it is still required and can be a duty of disclosure issue); ERROR 7 — NO PROVISIONAL FILED BEFORE PUBLIC DISCLOSURE: the inventor disclosed publicly before filing any patent application; FIX: file a provisional application BEFORE any public disclosure; a provisional gives 1 year to file the non-provisional and establishes priority date; ERROR 8 — SINGLE CLAIM TYPE: the application is filed with only method claims or only apparatus claims; FIX: always include method + apparatus + CRM claims for software inventions.

Continuation strategy requires specific drafting considerations: CONTINUATION CLAIMS (35 U.S.C. § 120): continuations must claim the same invention as the parent application; new claims must have written description support in the parent specification; BENEFIT: new independent claims can be added that were not in the parent application; claims can be drafted AFTER seeing competitor products (claiming the competitor's product while maintaining parent priority date); STRATEGY: file broad independent claims in the parent; file one or more continuation applications with narrower claims that cover specific commercial embodiments; CONTINUATION-IN-PART (CIP): adds new matter to the specification; claims to the new matter get the CIP filing date (not parent priority date); claims to subject matter already in the parent get the parent priority date; CAUTION: CIP weakens priority date for the new-matter claims; prosecution history of the CIP affects all continuation claims; DIVISIONAL APPLICATIONS (37 C.F.R. § 1.141-1.146): spawned from a restriction requirement from the examiner; the examiner finds two or more independent and distinct inventions in one application; the applicant must elect one invention to prosecute; the remaining invention(s) can be filed as a divisional; SAME PRIORITY DATE: divisionals get the parent's filing date; PROSECUTION LACHES RISK: continuing to file continuations/divisionals for many years without issuance can trigger prosecution laches; Symbol Technologies v. Lemelson (Fed. Cir. 2004): 18 years of continuation chain = laches; FIX: be aware of time elapsed; don't file continuations without purpose; CLAIM DESIGN ACROSS A FAMILY: METHOD CLAIMS in the parent (broadest protection); APPARATUS/SYSTEM CLAIMS in continuation 1; CRM CLAIMS in continuation 2; VARIANT EMBODIMENT CLAIMS in continuation 3; TERMINAL DISCLAIMER: when a continuation's claims are obvious variants of the parent's claims, a terminal disclaimer ties their expiration dates together; the family shares one effective term.