Nautilus Test

Nautilus, Inc. v. Biosig Instruments, Inc. (S.Ct. 2014) fundamentally reformed the standard for patent claim indefiniteness: BACKGROUND: § 112(b) (formerly § 112 ¶ 2) requires that patent claims 'particularly point out and distinctly claim' the subject matter of the invention; THE OLD STANDARD (pre-Nautilus): the Federal Circuit had held that a claim was only indefinite if it was 'not amenable to construction' or was 'insolubly ambiguous'; this standard was widely criticized as far too lenient — it allowed broad, vague claims to survive as long as ANY construction could be applied; THE NAUTILUS STANDARD: the Supreme Court unanimously reversed the Federal Circuit and announced a new, more demanding standard; QUOTED STANDARD: 'a patent is invalid for indefiniteness if its claims, read in light of the specification delineating the patent, and the prosecution history, fail to inform, with reasonable certainty, those skilled in the art about the scope of the invention'; KEY ELEMENTS OF THE NAUTILUS STANDARD: (1) PERSPECTIVE: evaluated from the perspective of a POSITA (person of ordinary skill in the art); (2) SOURCES: read in light of the specification AND prosecution history (not the claims in isolation); (3) CRITERION: 'reasonable certainty' — neither perfectly clear nor merely capable of some construction; (4) TEMPORAL POINT: assessed at the time of the patent application; WHY THE STANDARD CHANGED: the old 'insolubly ambiguous' standard undermined the public notice function of patent claims; patent claims must notify the public of what is protected; vague claims create legal uncertainty and suppress innovation; the Supreme Court held that the 'cobbled together' Federal Circuit formulations were not compatible with § 112(b)'s requirement that claims 'particularly point out and distinctly claim' the invention; REMAND TO FEDERAL CIRCUIT: the Supreme Court remanded to the Federal Circuit to apply the new 'reasonable certainty' standard to Biosig's claims (which used the term 'spaced relationship' between electrodes).

Following Nautilus, several categories of claim language present heightened indefiniteness risk: FUNCTIONAL LANGUAGE WITHOUT STRUCTURAL ANCHOR: claims that define elements purely by their function (what they DO rather than what they ARE or HOW they work) can be indefinite if the function does not clearly demarcate the scope; example: 'a mechanism configured to improve efficiency' — what counts as sufficient improvement?; RELATIVE TERMS AND TERMS OF DEGREE: terms like 'substantial,' 'approximately,' 'largely,' 'elongated,' 'heavy,' 'fast,' or 'most' are not automatically indefinite but require sufficient context in the specification to define the scope with reasonable certainty; example: 'a substantially cylindrical housing' — 'substantially' is indefinite unless the specification provides guidance on how much deviation is acceptable; FUNCTIONAL CLAIMING IN DEPENDENT CLAIMS: dependent claims that add only functional language to an independent claim can be indefinite if the function does not further narrow the scope; MEANS-PLUS-FUNCTION WITHOUT ADEQUATE STRUCTURE (§ 112(f)): 'means for [function]' claims are construed to cover the structure in the specification + equivalents; if the specification does not disclose adequate structure for the claimed function, the claim is indefinite (not just a § 112(a) written description issue — it goes to § 112(b) definiteness); 'nonce words': using generic terms like 'module,' 'unit,' 'component,' 'element,' 'mechanism' followed by a function may trigger § 112(f) treatment if they do not connote specific structure to a POSITA; OPEN-ENDED NUMERICAL RANGES: claims with ambiguous range endpoints (e.g., 'at least 3%' — 3% of WHAT, measured HOW?); TERMS DEFINED INCONSISTENTLY: terms used with different meanings in different parts of the specification or prosecution history; COINED TERMS WITHOUT DEFINITION: inventor-coined terms that appear only in the claims without a clear definition or context in the specification; PROSECUTION HISTORY CREATED AMBIGUITY: statements made during prosecution that make claim scope unclear — e.g., arguments that appear to give the same term different meanings in different contexts.

Indefiniteness under § 112(b) is a distinct validity challenge with its own procedural characteristics: WHEN TO RAISE INDEFINITENESS: indefiniteness is a validity challenge and must be raised as an affirmative defense (35 U.S.C. § 282); accused infringers typically raise it in their answer to the patent infringement complaint; BURDEN OF PROOF: clear and convincing evidence standard (i&TRADE v. eBay, S.Ct. 2007 established this for all patent invalidity challenges, including § 112(b)); this is a high burden — the accused infringer must show that a POSITA would not understand the claim scope with reasonable certainty; ROLE OF JUDGE vs. JURY: claim construction (determining the meaning of claim terms) is a question of LAW for the judge (Markman v. Westview Instruments, S.Ct. 1996); indefiniteness is a legal conclusion (because it depends on claim construction); therefore, indefiniteness is DECIDED BY THE JUDGE, not the jury; however, factual predicates (such as what a POSITA would have understood) may be submitted to the jury or determined by the judge based on expert testimony; MARKMAN HEARING ROLE: indefiniteness challenges are often litigated at the Markman hearing (claim construction hearing); the court first tries to construe the claim; if it CANNOT be construed with reasonable certainty, it may hold the claim indefinite; if there is a reasonable construction, the claim survives; EXPERT TESTIMONY: both sides typically submit expert declarations on what a POSITA would understand; petitioner/accused infringer argues POSITA cannot determine the scope with reasonable certainty; patent owner argues POSITA can; INTRINSIC EVIDENCE: courts look at the specification, figures, and prosecution history before extrinsic evidence; CLAIM DIFFERENTIATION AS DEFENSE: patent owners sometimes argue that a term has meaning because of how it differs from related claims (claim differentiation doctrine); INVALIDITY COUNTERCLAIM: accused infringers typically assert § 112(b) invalidity as both an affirmative defense and a counterclaim for declaratory judgment of invalidity.

Indefiniteness under § 112(b) has different availability depending on the PTAB proceeding: INTER PARTES REVIEW (IPR): IPR CAN ONLY CHALLENGE patent claims on the grounds of anticipation (§ 102) and obviousness (§ 103); IPR CANNOT raise § 112 grounds (written description, enablement, or indefiniteness); this is a statutory limitation under 35 U.S.C. § 311(b); POST-GRANT REVIEW (PGR): PGR is available only within 9 months of patent grant (for AIA patents); PGR CAN challenge claims on ANY ground of invalidity, INCLUDING § 112(b) indefiniteness; PGR allows indefiniteness challenges at the PTAB based on the Nautilus standard; EX PARTE REEXAMINATION: only § 102/§ 103 grounds (like IPR); INTER PARTES REEXAMINATION (legacy): filed before Sept. 2012; § 102/§ 103 only; COVERED BUSINESS METHOD (CBM) REVIEW: the CBM program sunset in September 2020; it had allowed § 112 challenges; ex parte proceedings now available under AIA transition practice but CBM is no longer an option; PRACTICAL CONSEQUENCE: if a patent is more than 9 months old (beyond PGR window), § 112(b) indefiniteness can ONLY be raised in district court litigation (not at PTAB); this is often why accused infringers reserve § 112 defenses for district court; CLAIM CONSTRUCTION AT PTAB vs. DISTRICT COURT: PTAB now applies Philips standard (post-2019 rule change); the same claim construction applies; however, the evidentiary standards differ (preponderance of evidence at PTAB vs. clear and convincing evidence at district court); AFTER NAUTILUS: because IPR cannot raise § 112(b), patent challengers must choose their forum carefully; if indefiniteness is the strongest challenge, go to district court.

Patent prosecutors can reduce indefiniteness risk through careful claim drafting and specification practice: DEFINE CRITICAL TERMS EXPLICITLY IN THE SPECIFICATION: for terms that are relative, functional, or coined by the inventor, add explicit definitions in the specification; example: 'As used herein, substantially cylindrical means a cylinder with a cross-sectional aspect ratio between 0.9 and 1.1'; use phrases like 'as used herein' or 'in the context of this invention' to signal intentional lexicographer definitions; CALIBRATE TERMS OF DEGREE WITH WORKING EXAMPLES: for relative terms (substantial, approximately, significant), provide working examples in the specification that bound the term; example: 'a reaction time of approximately 30 minutes, for example between 20 and 40 minutes'; PROVIDE STRUCTURAL SUPPORT FOR FUNCTIONAL LANGUAGE: if functional language is necessary, anchor the function to a specific structure in the specification; avoid 'configured to' without identifying WHAT is configured; AVOID PURE MEANS-PLUS-FUNCTION WITHOUT ADEQUATE DISCLOSURE: if using means-plus-function (§ 112(f)) claiming, ensure the specification discloses a clear, specific, corresponding structure for each function; if using nonce words (module, unit, component, mechanism), consider adding structural language or using the full-on MPF format with explicit structure; ANTICIPATE EXAMINER § 112(b) REJECTIONS: when responding to an indefiniteness rejection, argue: (1) the term has a POSITA-understood meaning in the art; (2) the specification defines or calibrates the term; (3) the prosecution history (including the rejection response itself) informs the meaning; CLAIM SCOPE CALIBRATION: the Nautilus standard rewards specificity; narrower claims with defined terms are more defensible than broad functional claims with undefined language; PROSECUTION RECORD AS CLARIFICATION: when an examiner questions a term's scope during prosecution, the attorney's arguments explaining the scope BECOME PART OF THE PROSECUTION HISTORY that courts and PTAB use to determine meaning — this record can HELP or HURT depending on how the argument is framed.