PTAB
Advanced fields
2 decisions · 512msnewest first
  • PTAB · Oct 6, 2026 · IPR2025-00530 · APJ Scott C Moore · IPR · Final written decision

    Original claims 1–9 were canceled; the non-contingent motion to add substitute claims 10–18 was denied for lack of written-description support, and claim 18 was also indefinite.

    RulingsFinal written decision
    • 112 supportMotion to amend, deniedDenied

      “that either the ’303 application or the ’838 provisional contain adequate written description support for the disputed feature of limitation [10.d]. Though the disclosures cited by Patent Owner indicate that a secondary identifier can be used to aid in verification of a UAV, these disclosures also make clear that both first and second identifiers are transmitted by and received from the UAV. See, e.g., Ex. 2002, 4:15–17, 30:24–31:6; Ex. 2003 ¶¶ 14, 66. Patent Owner’s reliance on disclosure characterized as transmitting an identifier from a remote computing system “through the UAV” (Reply 2) is not persuasive. The cited disclosures from the ’303 application and ’838 provisional generally disclose that the identifiers transmitted by a UAV can be “generated remotely,” such as by a “remote computing system.” Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45. But Patent Owner has not identified disclosure indicating that a remote computing system may transmit an identifier to the identification receiver. In the ’303 application and ’838 provisional, only the UAV (which is part of the discrimination system, and thus not “remote”) actually transmits identifiers to the identification receiver. Patent Owner is correct in its assertion that an “aerial system identifier can be generated on-board the aerial system” or “generated remotely . . . at a remote computing system.” Mot. 7 (citing Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45). But even if a UAV’s identifier was at some time in the past generated by a remote computing system, the subsequent transmission of that identifier from the UAV to the identification receiver would not satisfy the plain language of limitation [10.d]. The claim language “receive … a second identifier from a computing system that is remote to the discrimination system” requires the receipt of a transmission of the second identifier from a remote computing system. This claim language limits the source of the received transmission (i.e., where the particular transmission is “receive[d] … from”). Thus, the relevant issue is from where was the recited second identifier received. The relevant is not where the second identifier was originally generated.” slip op. at 12

    • Disclosure Requirements (§112) › Definiteness (Nautilus)DefiniteIndefiniteMixed

      “We determine that the disputed language in limitation [10.d] is not indefinite. There is no recitation in proposed substitute claim 10 that the second identifier is transmitted solely from the identifier transmission system. Thus, the alleged irreconcilable contradiction cited by Petitioner is not recited in the claims. Petitioner’s position appears to rest on the fact that the ’303 application and ’838 provisional do not disclose receiving the second identifier from a remote computing system. See Sur-reply 6 (“To manufacture written description support, [Patent Owner] argues the claim encompasses identifiers routed ‘through the UAV.’”). Though we agree that limitation [10.d] lacks adequate written description support, this defect does not render the claim indefinite because the scope of limitation [10.d] is otherwise reasonably certain based on its plain language. See supra § III.C.4.” slip op. at 18

    • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference not prior artPriority date, deniedDecided for patent owner

      “In contrast, the ’393 provisional never discloses that the described drone defense system may use the identity of a detected drone to develop a particular countermeasure. The disclosed RTSS certainly uses identity information to determine whether a drone is a threat. And if a threat is identified, the RTSS immediately starts “a series of processes … to determine what rule of engagement will be applied on the intruding drone.” Ex. 1006 ¶ 10. The ’393 provisional discloses that the system may select a particular countermeasure based on (i) the particular zone within a protected area within which a drone is located, (ii) “the behavior of the hostile drone,” or (iii) “other instructions.” Id. ¶¶ 9, 10. But the ’393 provisional never discloses that these “other instructions” may include the identity of the drone. The system disclosed in the ’393 provisional uses the identity of a drone to determine whether to activate the countermeasure system. See id. ¶¶ 16–18. But there is no disclosure in the ’393 provisional that the countermeasure system, once activated, uses the identity of the drone to develop the particular countermeasure to be employed. See generally Ex. 1006. Thus, though the Whitmarsh reference itself contains ample written description support for limitation [19e], the earlier-filed ’393 provisional does not. On this record, and having reviewed the ’393 provisional in its entirety, we determine that the ’393 provisional does not “reasonably convey[] to those skilled in the art that the inventor had possession of” the subject matter of limitation [19e] of Whitmarsh’s claim 19 “as of the filing date” of the ’393 provisional. See Ariad, 598 F.3d at 1351.” slip op. at 27

    § 102 anticipation§ 112 disclosurecites Nautilus
    Patents in suitUS 10,249,199
  • PTAB · Nov 14, 2016 · IPR2015-01243 · APJ Grace Karaffa Obermann · IPR · Final written decision

    Petitioner failed to prove claims 1–8, 10, and 11 of the ’290 patent, claims 1–8 and 10–13 of the ’173 patent, and claims 1–6 and 8–19 of the ’510 patent obvious over Fohr, Sato, and …

    RulingsFinal written decision
    • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable

      “We recognize that it may be necessary “to look to interrelated teachings of multiple patents . . . in order to determine whether there was an apparent reason to combine the known elements in the fashion claimed.” KSR Int’l, 550 U.S. at 418. Petitioner in these proceedings, however, directs us to no persuasive reason why an ordinary artisan would have turned to the heat-retaining battery module of Hallaj when working to implement a plurality of Sato’s cells in a pack to replace the capacitors in Fohr. Pet. 36–38 (nowhere addressing that critical point); Reply 13 (devoting four sentences to rebuttal of Patent Owner’s persuasive evidence that one would not have combined the disclosures of Hallaj, Fohr, and Sato in the manner claimed); see Ex. 1033, 15 (Examiner’s observation, in confirming the patentability of the challenged claims during reexamination, that Sato contains “no information as to how Sato’s cells would be implemented in a pack”). We view Petitioner’s unexplained leap from the single battery cell of Sato to the heat-retaining battery module of Hallaj as a classic example of impermissible hindsight reconstruction driven not by any teaching in the prior art, but by the claim requirement of a “plurality” of cells implemented in a battery pack. Pet. 36–38; Reply 13. Patent Owner, by contrast, comes forward with persuasive evidence, which we credit, showing that one of ordinary skill in the art would not have been led to arrange a plurality of Sato’s cells in the heat-retaining battery module of Hallaj because such a modified battery pack would have been unsuitable for use as a replacement for the capacitors in Fohr. Specifically, we credit the testimony of Dr. Blomgren, who cogently explains why a person of ordinary skill in the art would not have been led to the proposed modification. Ex. 2147 ¶¶ 79–85.” slip op. at 17

    • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

      “We are not persuaded by Dr. Riley’s testimony that Fohr effectively teaches that both lithium-based battery cells and capacitors can achieve the 20 Amp Limitation, on a theory that “it’s actually the tool that draws the power” and “the right lithium cell” would be “a drop in replacement for this application.” Ex. 2169, 121:12–16 (Dr. Riley’s deposition testimony); Resp. 17. Dr. Riley readily admitted an unfamiliarity with capacitors, and identified no suitable “drop in” ready lithium cells available at the time of the invention. Ex. 2169, 121:11–122:4 (“[I]f I had a cell that could do similar things, I’d certainly swap it in there.”). On that point, we find more credible Dr. Blomgren’s testimony that “there is no guarantee that a given pack of battery cells can provide the current that a tool tries to draw.” Resp. 17 (citing Ex. 2147 ¶ 60).” slip op. at 13

    • Skill levelSkill level board ownOther

      “B. Level of Ordinary Skill in the Art We hold that the prior art references asserted in the Petition are representative of the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (absence of specific findings on “level of skill in the art does not give rise to reversible error ‘where the prior art itself reflects an appropriate level and a need for testimony is not shown’” (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). To the extent that a more specific definition is required, we hold that an ordinary artisan would include one holding a Bachelor’s Degree in Electrical Engineering with two or three years of experience in battery design. That definition comports with the very similar definitions advanced by the parties. In that regard, Petitioner asserts that an ordinary artisan would encompass a person holding a Bachelor’s Degree in Electrical Engineering with three years of experience in battery design. Pet. 8; Ex. 1007 ¶ 9. Patent Owner similarly asserts that an ordinary artisan would include a person holding a Bachelor’s Degree in Electrical Engineering with two years of battery design experience. Resp. 8; Ex. 2105 ¶ 24.” slip op. at 9

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

      “In our Decisions to Institute, we construed the 20 Amp Limitation to require that “the battery cells, when configured together in a battery pack, are capable of producing reasonably close to 20 amps of discharge current or greater over the course of delivering their entire rated capacity.” Dec. 5. Neither party disputes that construction, which we adopt for the purposes of this Final Written Decision. To the extent that any other claim term requires express construction, we discuss the construction in our analysis below. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only claim terms in controversy need be construed, and then only to the extent necessary to resolve the controversy). The following facts are supported by a preponderance of the evidence.” slip op. at 10

    Claim construction§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 7,944,173

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.