- Axon Enterprise, Inc. / Dedrone Holdings, Inc. et al. v. Airspace Defense, Inc.Some claims unpatentablePTAB · Oct 6, 2026 · IPR2025-00629 · APJ Scott C Moore · IPR · Final written decision
Original claim 12 is not unpatentable; substitute claim 37 is added, while substitute claims 21–28 and 30–36 are denied as obvious.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“F.3d at 1279–80, we begin our analysis with the Specification of the ’711 Patent. The Specification indicates when a UAV (such as the recited “reference aerial vehicle”) navigates autonomously, it flies without manual control, and can, for example, track and fly to a target using information captured onboard the vehicle itself. See Ex. 1001, 3:24–28 (“[I]t may not be desirable to manually control the interceptor aerial vehicle to follow the target UAV. In some embodiments, the interceptor aerial vehicle is able to autonomously track and fly to the target UAV using machine vision based on images captured by a camera of the interceptor aerial vehicle.”). The Specification also indicates that “autonomous” means more than just “automatic flight,” and clarifies that autonomous navigation occurs when a UAV that previously received a target location from an external source subsequently turns and flies itself towards the received location. See, e.g., id. at 4:15–17 (disclosing that the detected location of a target may be provided to an interceptor “to allow it to automatically and autonomously fly toward the direction of the detected location”); 15:64–16:3 (automatic and autonomous navigation occurs when an interceptor’s navigation component and/or flight controller receive the location of a target, and adjust the interceptor “to turn and fly towards the received location . . . based on the received location”); 16:49–60 (“For example, a flight direction and/or speed of an interceptor aerial vehicle are automatically and autonomously adjusted based on a location and size of the target within the captured image. . . . This allows the flight path of the interceptor aerial vehicle to be dynamically adjusted to track and follow a moving target.”).” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“have had reason to combine Beard and Laufer in the manner proposed by Petitioner, the combination would not satisfy the Autonomous Navigation limitation required by claim 12 because Laufer’s autopilot commands are generated by and transmitted from a remote command center (i.e., Laufer’s central controller 115). PO Resp. 15–16. In its Reply, Petitioner does not dispute that Laufer’s autopilot commands are generated by Laufer’s central controller 115, which is remote from the aircraft being controlled. See Reply 13–17. Petitioner asserts, however, that the combination still satisfies the Autonomous Navigation limitation because these autopilot commands are generated without human input. See id. Based on the complete trial record, Patent Owner’s arguments are persuasive. See PO Resp. 15–16; PO Sur-reply 42, 1–6; Ex. 2025 ¶¶ 84–87. The flight of Beard’s UAV 100 under the control of Laufer’s autopilot commands does not satisfy the Autonomous Navigation limitation of claim 12, as we have construed that limitation, because Laufer’s autopilot commands are generated at a location that is remote from UAV 100 (Laufer’s central controller 115.) See, e.g., Ex. 1010 ¶ 40 (“Central controller 115 uses autopilot command module 440 to generate autopilot aircraft commands”), ¶¶ 26, 30 (clarifying that central controller 115 and the controlled interceptor aircraft are separate devices that may communicate through a “wireless connection”), Fig. 4 (depicting “aircraft control commands 475” being generated externally from the depicted “Interceptor Aircraft”); see also Ex. 2025 ¶¶ 95–95. Petitioner never disputes that, in the proposed combination, Laufer’s central controller 115 would remain external to Beard’s UAV 100. See Reply 13–17. Instead, Petitioner relies on its proposed construction of the Autonomous Navigation limitation, which would have encompassed such an arrangement. See id. Our construction of the Autonomous Navigation limitation, which did not adopt Petitioner’s claim construction position, is dispositive of Petitioner’s argument. We thus determine that Petitioner has not shown by a preponderance of the evidence that claim 12 would have been obvious over Beard and Laufer.” slip op. at 15
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part
“the legal requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121. Lectrosonics, Paper 15 at 4, 7–8. For the reasons that follow, we determine that Patent Owner has satisfied this burden. 1. Proposal of a Reasonable Number of Substitute Claims A motion to amend must “propose a reasonable number of substitute claims.” 35 U.S.C. § 316(d)(1)(B); see also 37 C.F.R. § 42.121(a)(3) (“A motion to amend may cancel a challenged claim or propose a reasonable number of substitute claims.”). “There is a rebuttable presumption that a reasonable number of substitute claims per challenged claim is one (1) substitute claim.” Lectrosonics, IPR2018-01129, Paper 15 at 4; see also 37 C.F.R. § 42.121(a)(3). Patent Owner has shown it proposes a reasonable number of substitute claims by proposing a single substitute claim for each of challenged claims 1–4, 8–11, and 13–20. MTA 1–2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 2. Amendments Respond to a Ground of Unpatentability “A motion to amend may be denied where … [t]he amendment does not respond to a ground of unpatentability involved in the trial.” 37 C.F.R. § 42.121(a)(2)(i). Patent Owner has responded to the grounds of unpatentability involved in this proceeding by amending the claims in response to the Petition’s asserted prior art. See MTA 2, 25, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 3. No Enlargement of the Scope of the Claims An amendment may not seek to enlarge the scope of the claims of the patent. 35 U.S.C. § 316(d)(3); 37 C.F.R. §§ 42.121(b)(1)–(b)(2). Patent Owner asserts that the amendments in the Motion do not enlarge the scope of the claims of the patent because each proposed substitute claim “retains all of the limitations of the corresponding challenged claim, and each proposed independent substitute claim adds further limitations.” See MTA 2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 4. No Introduction of New Matter An amendment may not introduce new matter. 35 U.S.C. § 316(d)(3);” slip op. at 22
- 112 supportDecided for patent owner
“Having considered the evidence and argument cited by both parties, we determine there is sufficient written description support for the disputed portions of limitations [37.e1], [37.e3,] and [37.e4]. The ’452 application discloses selecting between groups of processing schemes (e.g., algorithms) depending on a confidence level, where the groups are, for example: high cost, high robustness algorithms; medium cost, medium robustness algorithms; and low cost, low robustness algorithms. See Ex. 2019 ¶¶ 146–147. These schemes or algorithms may be neural networks. See, e.g., id. ¶ 50 (including neural network as a type of algorithm); see also id. ¶¶ 109–110); see generally MTA Opp 1 (not disputing that schemes may be neural networks). Specifically, the ’452 application describes “algorithms that process video frames of one or more video data streams,” and “produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Id. ¶ 141. The ’452 application also discloses the concept of switching between neural networks based on confidence levels. In particular, the ’452 application discloses that a “process cycles through the processing schemes to produce a detection of an object,” for example, where “if the confidence number is higher than an activation number, an action is performed to stop or change a running group (i) and select or switch to group (ii).” Id. ¶ 146. More particularly, “a processing scheme from the group of (i) High cost (low refresh rate), high robustness algorithm[s] can select a cheaper processing scheme from the group of (ii) Medium cost, medium robustness algorithms.” Id. The ’452 application additionally discloses that schemes or algorithms (e.g., neural networks) are applied to individual video frames, and that the confidence levels that determine which neural network will be applied in the future are also derived from individual video frames. For example, as discussed above, the ’452 application describes that “[t]he processing schemes produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Ex. 2019 ¶ 141 (emphases added). The ’452 application also describes selecting and applying an individual neural network, rather than only selecting and applying a group of processing schemes. For example, as highlighted above, the ’452 application describes that “a processing scheme from the” “High” group “can select a cheaper processing scheme from the” “Medium” group. Id. ¶ 146 (emphases added). In our view, these disclosures, read together, would reasonably convey to one skilled in the art that the inventor had possession of the disputed subject matter described above. See Ariad, 598 F.3d at 1351.” slip op. at 24
Patent outcomesUS 10,514,711 mixedClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham · NautilusPatents in suitUS 10,514,711 - 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 NautilusPatents in suitUS 10,249,199 - PTAB · Oct 6, 2026 · IPR2025-00525 · APJ Scott C Moore · IPR · Final written decision
Original claim 21 was canceled; the Board denied substitute claim 22 for new matter and held it obvious under §103 based on six combinations.
RulingsFinal written decision- 112 supportMotion to amend, deniedDenied
“First, Patent Owner has not shown possession of the disputed feature of a “radio communication module [that] is configured to utilize a secure identifier, the secure identifier comprising a specified excitation.” In the ’406 application, the term “excitation” is used exclusively to refer to a light beam signal. See Ex. 2015, 7:8–13, 9:8–10, 23:9.2 The ’406 application discloses that an identification box on an aircraft may include both an RF module and a separate light sensor. See Ex. 2015, 7:3–11. But nowhere does the ’406 application describe receiving a light beam (e.g., an excitation) with the RF module of the identification box (as opposed to the light sensor), so as to provide support for proposed substitute claim 22’s recitation of a “radio communication module” configured to utilize “a secure identifier . . . comprising a specified excitation.” We disagree with Patent Owner that it suffices that one of ordinary skill in the art “would recognize that these disclosures are equally applicable to the RF-only embodiments” (Reply 5). “It is not sufficient for purposes of the written description requirement . . . that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997). On this record, and having reviewed the ’959 Patent, the ’153 provisional, and the ’406 application, we find no evidence in those documents that the named inventor was in possession of the concept of a radio communications module “configured to utilize a secure identifier” where “the secure identifier compris[es] a specified excitation.” Second, setting aside the “radio communication module” in proposed substitute claim 22, Patent Owner also has not shown that the named inventor was in possession of the feature of a “secure identifier comprising a specified excitation.” Patent Owner’s argument that the ’406 application describes a light beam directed to a particular aircraft (see Reply 4–5) is 2 The same is true of the ’153 provisional. See Ex. 2016 ¶¶ 29, 34. unavailing. The fact that the properties of a particular light beam indicate that the light beam is intended for a particular aircraft does not demonstrate that the light beam is a “secure identifier,” as we have construed that term. Patent Owner has not identified any disclosure in the ’406 application of a “secure identifier” comprising a light beam, let alone that such light beam can be utilized by a “radio communication module.” The only references to “secure” identifiers in the ’406 application describe radio frequency signals. See Ex. 2015, 2:4–6, 15:21–17:12.3 Having reviewed the ’959 Patent, the ’153 provisional, and the ’406 application, we find no evidence in those documents that the named inventor was in possession of the concept of a “secure identifier comprising a specified excitation.”” slip op. at 15
- ScopeDecided for patent owner
“not impermissibly broaden the scope of the claims of the ’959 Patent. As Patent Owner suggests, there were no limitations in original claim 21 on the type of radio signal the radio communication module could receive, and so it follows that proposed substitute claim 22 does not now encompass receiving a broader set of radio signals. We see no basis for Petitioner’s argument that the past tense verb “received” limited original claim 21 to “signals of a compatible ‘type’ and ‘range.’” Opp. 7. Moreover, the claim language (with the proposed deletion shown double brackets) provides that “the radio communication module is configured to receive a [[received]] radio signal.” Any radio signal that the radio communications module receives would necessarily be a “received” radio signal. Thus, deleting the redundant word “received” does not enlarge the scope of this claim limitation. We also are not persuaded by Petitioner’s suggestion that removing the term “received” broadens original claim 21 by deleting a requirement that the radio signal have already been previously received by the claimed device. See Sur-reply 9. Original claim 21 simply recited, using redundant language, that “the radio communication module is configured to receive a received radio signal.” Ex. 1001, 18:5–7. The most natural reading of this language is that the phrase “received radio signal” is just a description of a radio signal that is received by the recited radio communications module. Petitioner has cited no persuasive evidence that one of ordinary skill in the art would have counterintuitively interpreted this language to impose an additional requirement that the “received radio signal” must have been received twice—a first time by some other component of the device, and a second time by the recited radio communication module. Accordingly, we determine that the proposed amendment does not improperly broaden claim scope.” slip op. at 10
- Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteNot shown unpatentable
“572 U.S. 898 (2014). See Memorandum: Approach to Indefiniteness Under 35 U.S.C. § 112 in AIA Post-Grant Proceedings (Jan. 6, 2021).4 Under Nautilus, a claim is indefinite if fails to “inform those skilled in the art about the scope of the invention with reasonable certainty.” 572 U.S. at 910. We agree with Patent Owner that neither of the identified terms are indefinite. Regarding the term “low-altitude aircraft,” we determine the Specification provides a sufficient basis for understanding the scope and meaning of this term with reasonable certainty. The U.S. Court of Appeals for Federal Circuit has explained that, when a term of degree is recited in a claim, it is necessary “to determine whether the patent’s specification provides some standard for measuring that degree.” See Seattle Box Co. v. Indus. Crating & Packing, Inc., 731 F.2d 818, 826 (Fed. Cir. 1984); see also Datamize, LLC v. Plumtree Software, Inc., 417 F.3d 1342, 1350 (Fed. Cir. 2005) (“Some objective standard must be provided in order to allow the public to determine the scope of the claimed invention.”). Here, the Specification describes the related art as including “small UASs (e.g., aircrafts up to 25 pounds flying up to 500 ft of the low altitude airspace).” Ex. 1001, 1:50–52. One of ordinary skill in the art would understand from the Specification that the cited disclosure provides an objective standard for determining the scope of a low-altitude aircraft as one that is designed to fly up to a maximum altitude of about 500 feet.” slip op. at 20
- Skill levelSkill level petitioner adoptedDecided for petitioner
“In our Institution Decision, we adopted Petitioner’s proposal that one of ordinary skill in the art would have had the following qualifications: [E]ither (1) a Bachelor of Science in Mechanical Engineering, Electrical Engineering, Aerospace engineering, or an equivalent field, as well as at least 2 years of academic or industry experience in the aerospace, avionics, telecommunications, or electronic device manufacturing industry, or (2) at least four years of industry experience in any of the above industries. Paper 13, 5 (citing Pet. 21). Patent Owner has not disputed this formulation; thus, we adopt it for purposes of this Decision. See Paper 13, 10–11 n. 8.” slip op. at 23
§ 103 obviousness§ 112 disclosurecites Graham · NautilusPatents in suitUS 10,713,959 - Aroma360, LLC v. Air Esscentials, Inc.Some claims unpatentablePTAB · Oct 6, 2026 · IPR2025-00707 · APJ Eric C Jeschke · IPR · Final written decision
Claim 5 is unpatentable over Gao-2 and over Gao-2 with Goubet; claims 1, 3, 4, and 6–8 were not shown unpatentable on any ground, and substitute claim 17 was denied.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Neither Petitioner nor Patent Owner propose explicit constructions for any claim terms. Pet. 16–17; PO Resp. 5–6. Based on the complete record, we need not construe explicitly any claim terms because doing so would not change the outcome of the analysis below. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 10
- Expert testimonyPetitioner expert creditedDecided for patent owner
“As an initial matter, the record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration for allegedly not reviewing the parties’ claim constructions. See Pet. Reply 2–3 (citing Ex. 1046, 115:15–18). Contrary to Petitioner’s argument, in the cited 11 This refers to the recitation in clauses 1F and 5F that the “diffusion assembly is disposed between said upper chamber and said lower chamber.” discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1; see also Pet. Reply 3 (arguing that “Dr. Micklow’s opinion that the prior art does not render the claims obvious is premised on an interpretation of certain claim limitations that are inconsistent with both parties’ constructions” (emphasis added)). Instead, we read Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also id. at 115:15–18 (“I don’t know if I would even apply claim construction. I applied engineering principles to a document that had been published with the patent office.”).” slip op. at 12
- BurdenNot shown unpatentable
“referring to the same direction as the separation of the “upper chamber” and “lower chamber” (vertically in both Figure 6 of the challenged patent and Figure 1 of Goubet), we turn back now to Petitioner’s discussion of clause 1F, which includes the limitation at issue. There, Petitioner does not discuss why the “diffusion assembly” is allegedly “disposed between” the “upper chamber” and “lower chamber,” but instead, Petitioner discusses why a component of the “diffusion assembly”—the “atomizer assembly”—is allegedly “disposed between” the “upper chamber” and “lower chamber”: Pet. 39. In the end, we need not assess whether the “atomizer assembly” identified by Petitioner is “disposed between” the “upper chamber” and “lower chamber” under the proper construction of that term (which, again, we need not and do not determine here) because the “disposed between” limitation does not involve the “atomizer assembly.” Instead, we find that, by failing to address why the identified “diffusion assembly” is “disposed between” the identified “upper chamber” and “lower chamber,” Petitioner has failed to provide persuasive evidence that Goubet discloses or suggests the “disposed between” limitation. Pet. 38–39 (discussing the claim language “said diffusion assembly is disposed between said upper chamber and said lower chamber” but only discussing the location of the “atomizer assembly”); see 35 U.S.C. § 316(e) (“In an inter partes review . . . , the petitioner shall have the burden of proving a proposition of unpatentability by a preponderance of the evidence.”). For the reasons above, we find, based on the complete record, that Petitioner has not shown by a preponderance of the evidence that Goubet discloses or suggests the “disposed between” limitation.” slip op. at 22
Patent outcomesUS 10,092,918 mixedClaim construction§ 103 obviousnesscites Phillips · KSRPatents in suitUS 10,092,918 - Imperative Care, Inc. v. Inari Medical, Inc.All claims unpatentablePTAB · Oct 6, 2026 · IPR2025-00728 · APJ Timothy G Majors · IPR · Final written decision
Claims 1–7, 9, 10, 15–18, and 20–24 are unpatentable as obvious over Schaffer with Hartley or Eller; claims 1–3, 5, 6, 9, 15–18, and 21–24 are also obvious over Hartley and Eller.
RulingsFinal written decision- Skill levelSkill level board ownDecided for patent owner
“Petitioner’s proposed POSA definition lacks specificity. That definition, if interpreted generically, could mean that a person may qualify as a POSA if they had, for example, a B.S. in mechanical engineering and only two years of experience designing any type of product in any field. That is too broad. We find that a POSA would have had the agreed-upon educational credentials—an undergraduate degree in mechanical engineering or a related engineering discipline. Ex. 1003 ¶ 35; Ex. 2033 ¶ 61. We find that a POSA would also have had 2–4 years of design or engineering experience related to products in the field of the invention, which involves endovascular devices and the surgical procedures that use such devices. Ex. 1001, 1:16–54 (background of the invention). Such devices include, but are not limited to, hemostasis valves and catheters for testimony of the parties’ experts, the POSA need not have had first-hand experience designing hemostasis valves. See, e.g., Ex. 1037 (Zalesky Tr.), 72:11–73:7 (testifying direct experience “designing” hemostasis valves or aspiration catheters is not necessary, but “general experience with vascular devices and procedures” is required). Further, as Dr. Zalesky testified, the POSA’s experience related to developing such devices “could be as simple as bench testing and looking at clinical data.” Id. at 74:5–75:1. Lastly, a POSA would have understood such devices’ design requirements as determined by the needs of the physician, patient, and procedure, which understanding may be informed by work experience or study. Ex. 2030, 24:5–21.” slip op. at 12
- Expert testimonyPetitioner expert creditedPatent owner expert creditedMixed
“above (supra Section III.C), a filament requires flexibility, Petitioner has not demonstrated that Schaffer describes that feature in its valves. Instead, Patent Owner persuades us that Schaffer describes “rigid U-shaped actuating members—not a ‘filament.’” PO Resp. 23–24.13 We find Dr. Zalesky’s interpretation of Schaffer more credible than Mr. Thornton’s on the question of whether a POSA would have regarded Schaffer’s actuating members as being substantially rigid structures. Ex. 2033 ¶¶ 91–100 (testifying, inter alia, that a POSA would have understood from Schaffer’s disclosure about making the actuator and actuating members from machining pre-existing amounts of metals and/or plastics, and further explaining that flexible parts would deform and be difficult to machine through conventional techniques); Ex. 1005 ¶¶ 81–82. Mr. Thornton testifies that Schaffer’s disclosed manufacturing techniques for the actuator/actuating members are only examples and “a person of ordinary skill in the art could have simply purchased pre-made [and flexible] flat wire or plastic tapes or ribbons.” Ex. 1003 ¶ 79. Such testimony invokes, at best, obviousness-based reasoning. This does not establish that Schaffer alone describes a filament sufficient to anticipate the claims. Trintec Indus., Inc. v. Top-U.S.A. Corp., 295 F.3d 1292, 1296 (Fed.” slip op. at 28
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionDecided for patent owner
“Patent Owner cites intrinsic evidence in support of its interpretation, which include claim 1’s recitation of an “active tensioning mechanism” comprising the filament and the Specification’s description of a filament that can be both “loosened” and “tightened.” PO Resp. 14–17 (citing, e.g., Ex. 1001, 9:36–37, 9:53–56 (teaching “the filament 150 is tightened” when the actuator buttons are released and “the filament 150 is loosened” when the buttons are pressed to open the valve)); see also Ex. 2025, 1288 (defining “tension” as to “tighten to a desired or appropriate degree”). These descriptions from the patent are more consistent with the view that the filament is characteristically flexible, not rigid. 10 We reached the same conclusion, based on substantially the same records, in the Institution Decision and the Final Written Decisions in the 1157, 156, and 289 IPRs. Inst. Dec. 14–18; Ex. 1042, 14–24; Ex. 1048, 16–23; Ex. 1049, 14–17 (noting the parties’ agreement at oral hearing that there was no additional argument or evidence about whether a filament requires flexibility that was not already addressed in related matters). After we construed the “filament” term to require flexibility at institution, Petitioner provided no further argument or evidence on this issue in its authorized trial briefing or at oral hearing. See generally Pet. Reply. embodiments (where the filament forms one or more loops like depicted and described in Figures 6–7) require a flexible structure. See, e.g., Ex. 2032, 15–16 (explaining that the device would not work to constrict the tubular sidewall and lumen (analogous to the elongate member defining a lumen of the claims here) if the filament forming the loop(s) was inflexible); Ex. 1001, Figs. 6–7 (filament 150, with sub-filaments 150-A and 150-B). Although flexibility of the filament in the patent’s “bight” embodiments (e.g., as shown in Figures 8 and 9) is less clear, there is a dearth of evidence from Petitioner—either intrinsic or extrinsic to the patent—showing why a POSA would have understood the bights as embracing rigid structures. See Ex. 1001, Figs. 8–9. Moreover, as admitted by Petitioner’s expert, that a filament may be made from various materials described in the patent (e.g., synthetics or metals) does not, absent more information, lead to a conclusion that a filament is “rigid.” Ex. 2030, 125:2–126:4 (testifying “the relative stiffness or rigidity is not clear from those . . . materials without knowing much more information”).” slip op. at 16
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We find that Petitioner has not shown, by a preponderance of the evidence, that Schaffer anticipates claim 1 or any of the other challenged claims, each of which requires at least one “filament.” We are unpersuaded above (supra Section III.C), a filament requires flexibility, Petitioner has not demonstrated that Schaffer describes that feature in its valves. Instead, Patent Owner persuades us that Schaffer describes “rigid U-shaped actuating members—not a ‘filament.’” PO Resp. 23–24.13 We find Dr. Zalesky’s interpretation of Schaffer more credible than Mr. Thornton’s on the question of whether a POSA would have regarded Schaffer’s actuating members as being substantially rigid structures. Ex. 2033 ¶¶ 91–100 (testifying, inter alia, that a POSA would have understood from Schaffer’s disclosure about making the actuator and actuating members from machining pre-existing amounts of metals and/or plastics, and further explaining that flexible parts would deform and be difficult to machine through conventional techniques); Ex. 1005 ¶¶ 81–82. Mr. Thornton testifies that Schaffer’s disclosed manufacturing techniques for the actuator/actuating members are only examples and “a person of ordinary skill in the art could have simply purchased pre-made [and flexible] flat wire or plastic tapes or ribbons.” Ex. 1003 ¶ 79. Such testimony invokes, at best, obviousness-based reasoning. This does not establish that Schaffer alone describes a filament sufficient to anticipate the claims. Trintec Indus., Inc. v. Top-U.S.A. Corp., 295 F.3d 1292, 1296 (Fed.” slip op. at 27
Patent outcomesUS 11,844,921 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,844,921 - Aroma360, LLC v. Air Esscentials, Inc.All claims unpatentablePTAB · Oct 6, 2026 · IPR2025-00706 · APJ Eric C Jeschke · IPR · Final written decision
Claims 1, 4, and 7–10 are unpatentable as obvious over Goubet and anticipated by Gao; proposed substitute claims 20 and 21 are denied as indefinite and lacking written-description support.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In the Response, Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner, but Patent Owner “reserves the right to address [the definition] should new issues materialize.” PO Resp. 6. Patent Owner did not address this issue in the Sur-reply. As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther
“Network LLC, 929 F.3d 1350, 1357 (Fed. Cir. 2019). At first glance, the language of the limitation at issue—which, again, recites “the compressed air and the operative fluid mix together in said mixing chamber to form the fluid dispersion”—would seem to require the “fluid dispersion” (under the stipulated construction) to be fully formed in the “mixing chamber.” In other words, the language of the limitation alone would seem to support Patent Owner’s proposed construction for the “form the fluid dispersion” limitation. But the claim construction analysis does not end with consideration of the claim language alone. Next, we turn to the Specification. The Federal Circuit has said that the specification “is the single best guide to the meaning of a disputed term.” Phillips, 415 F.3d at 1315 (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). Here, the discussion in the Specification of precisely the same language as in the limitation at issue strongly supports that “to form a fluid dispersion” in the limitation at issue requires only initial mixing of the compressed air and operative fluid in the mixing chamber, with further “formation” of the ”fluid dispersion” occurring downstream of the mixing chamber: More importantly, the “predetermined amount” of compressed air and the “preselected amount” of the operable fluid are initially mixed together in the mixing chamber 226 to form a fluid dispersion. The diffusion chamber 112" is further structured to facilitate the formation of a plurality of substantially uniform droplets, as defined hereinabove, in the fluid dispersion prior to discharge from the diffusion chamber 112" through discharge port 132. Ex. 1001, 10:62–11:2 (emphasis added) (discussing Figure 6), quoted, in part, at Pet. Reply 6–710; see also Ex. 1001, 5:64–6:4 (same language, except without double primes, in a discussion of Figures 1 and 2). To be sure, certain passages in the Specification could be read to indicate that a “fluid dispersion” must be fully formed in the “mixing chamber.” See, e.g., Ex. 1001, 6:11–12 (“More in particular, the suppression chamber 232 receives the fluid dispersion from the mixing chamber 226.”); see also id. at 7:22–33, 11:39–52 (both implying that a “fluid dispersion” is formed in the mixing chamber). But the passage block quoted directly above (and the similar one bridging columns 5 and 6) more directly addresses the issue at hand—i.e., the scope of “form the fluid dispersion”—by using the same” slip op. at 13
- Expert testimonyPatent owner expert discountedMixed
“As an initial matter, the record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration for allegedly not reviewing the parties’ claim constructions. See Pet. Reply 2 (citing Ex. 1046, 115:15–18). Contrary to Petitioner’s argument, in the cited discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1. Instead, we read Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also id. at 115:15–18 (“I don’t know if I would even apply claim construction. I applied engineering principles to a document that had been published with the patent office.”).” slip op. at 18
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“To satisfy its burden of proving obviousness, a petitioner cannot employ mere conclusory statements. The petitioner must instead articulate specific reasoning, based on evidence of record, to support the legal conclusion of obviousness.” In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016); TriVascular, Inc. v. Samuels, 812 F.3d 1056, 1066 (Fed. Cir. 2016) (“Although the KSR test is flexible, the Board ‘must still be careful not to allow hindsight reconstruction of references . . . without any explanation as to how or why the references would be combined to produce the claimed invention.’”) (citation omitted). Based on the complete record, we agree with Patent Owner that “Petitioner’s asserted motivation boils down to the conclusory statement that given Goubet and Kaiser, ‘it was well known in the field at the time of the invention that droplets of greater uniformity result in uniform droplet evaporation.’” PO Resp. 31 (quoting Pet. 59). We agree with Patent Owner that Petitioner’s discussion of the alleged reasons to combine (Pet. 59) is insufficient to support the proposed combination here. See Magnum Oil, 829 F.3d at 1380. Specifically, we are not persuaded that Kaiser’s teachings—which relate to combustion (Ex. 1014 at 43)—would have led one of ordinary skill in the art to the proposed modifications, which would allegedly “improve the smoothness (i.e., less harsh) of the aroma generated as the oil droplets evaporate in the surrounding airspace.” See Pet. 59 (emphasis added); White Pet. Decl. ¶ 251 (same); see PO Resp. 32 (“Rather, Dr. White merely describes the ability to achieve the effect as in the claimed patent, not why a [person of ordinary skill in the art] would look to the field of electrospray injection and combustion in mesoscale power-generation systems, using high-voltage electric fields to generate charged fuel droplets for controlled combustion in catalytic micro-combustors when considering atomization for scents.”). For these reasons, we determine, in light of the complete record, that Petitioner has not shown by a preponderance of the evidence that one of ordinary skill in the art at the time of the invention would have had reason to combine Goubet and Kaiser, as proposed. slip op. at 32
Patent outcomesUS 10,583,449 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · NautilusPatents in suitUS 10,583,449 - Aroma360, LLC v. Air Esscentials, Inc.All claims unpatentablePTAB · Oct 6, 2026 · IPR2025-00705 · APJ Eric C Jeschke · IPR · Final written decision
Claims 7–9 and 11 are unpatentable as obvious over Goubet; proposed substitute claim 21 is denied as indefinite.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In the Response, Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner, but Patent Owner “reserves the right to address [the definition] should new issues materialize.” PO Resp. 5. Patent Owner did not address this issue in the Sur-reply. As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for patent owner
“The record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration, as asserted in Petitioner’s overall argument. See Pet. Reply 1–2. Contrary to Petitioner’s argument, in the cited general discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1; see also Pet. Reply 2 (arguing that “Dr. Micklow’s declaration is premised on understandings of claim scope that are inconsistent with the constructions advanced by both of the parties” (emphasis added)). Instead, we read the cited portions of Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also Pet. Reply 1 (citing Ex. 1046, 112:4–12, 113:13–20, 115:15–18). Next, we turn to each of the four specific claim terms that Petitioner highlights in its further arguments.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction needed
“B. Claim Construction In inter partes reviews, the Board interprets claim language using the same claim construction standard that would be used in a civil action under 35 U.S.C. § 282(b), as described in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). See 37 C.F.R. § 42.100(b). Under that standard, we generally give claim terms their ordinary and customary meaning, as would be understood by a person of ordinary skill in the art at the time of the invention, in light of the language of the claims, the specification, and the prosecution history. See Phillips, 415 F.3d at 1313–14. Although extrinsic evidence, when available, may also be useful when construing claim terms under this standard, extrinsic evidence should be considered in the context of the intrinsic evidence. See id. at 1317–19. Neither Petitioner nor Patent Owner propose explicit constructions for any claim terms. Pet. 10–11; PO Resp. 5. Based on the complete record, we need not construe explicitly any claim terms because doing so would not change the outcome of the analysis below. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“Florida Litigation a Joint Claim Construction statement that included stipulated claim constructions and disputed claim constructions for terms in the challenged patent as well as the ’449 patent and the ’918 patent. See Ex. 1018, Exhibit A (Stipulated Claim Constructions), Exhibit B (Disputed Claim Constructions). The parties stipulated to the construction of the terms “fluid dispersion” and “baffle” as recited in the challenged claim. See id., Exhibit A.10 10 When staying the Florida Litigation, the District Court cancelled the scheduled claim construction hearing. See ECF No. 67 (April 8, 2025) (granting joint motion to stay); ECF No. 68 (April 8, 2025) (cancelling the The stipulated construction of “fluid dispersion” merely restates the express definition of “fluid dispersion” from the challenged patent (although the definition is not cited or discussed in the parties’ filing). Compare Ex. 1018, Exhibit A, with Ex. 1001, 3:8–20. Similarly, the stipulated construction of “baffle” essentially parrots one sentence in the challenged patent (again, not cited or discussed in the parties’ filing). Compare Ex. 1018, Exhibit A, with Ex. 1001, 7:57–59. To the extent necessary, we determine that the complete record supports the parties’ stipulated constructions of “fluid dispersion” and “baffle,” and we apply those constructions below.” slip op. at 10
Patent outcomesUS 9,527,094 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · NautilusPatents in suitUS 9,527,094 - Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco NVNo claims unpatentablePTAB · Oct 5, 2026 · IPR2025-00598 · APJ David C Mckone · IPR · Final written decision
Claims 1–31 were not shown unpatentable under either § 103 ground because the asserted combinations did not teach required claim limitations.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedOther
“admissions by Patent Owner in litigation, contends that a person of ordinary skill in the art would have had “a Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field” and that “[a]dditional educational experience could substitute for some of the work experience.” Pet. 5 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art (Petition, 5) at this time.” PO Resp. 6. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is uncontested and is consistent with the technology described in the ’347 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“In the Preliminary Response, “Patent Owner accept[ed] the Petition’s claim construction.” Prelim. Resp. 6. However, in the Patent Owner Response, Patent Owner argues that “the claims of the ’347 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Based on the complete record, we do not find it necessary to provide express claim constructions of any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9
- Expert testimonyPetitioner expert discountedDecided for patent owner
“Beel actually discloses the following: [0321] On the peripheral device 32 the video packets are received at the corresponding plug and play port, e.g. the USB port 11, read by the Human Interface Driver (HID) interface handler 13, unpacked to remove HID protocol headers in an unpacker 20 and then transmitted to the communications network by a transmitter 21. The network can be wireless for example WiFi or LiFi network. [0322] Having been routed over a communications network to the base unit 33, the incoming stream is read from the communications interface such as a WiFi access point 22, unpacked in an unpacker 25, decoded in a decoder 26 and then inserted into a suitable composition such as an OpenGL based composition in the compositor 29 for display on a central display device. Ex. 1005 ¶¶ 321–322 (emphasis added to portions quoted by Petitioner). Patent Owner notes that “[t]he Petition mistakenly cites to ¶ 322 of Beel but quotes ¶ 321.” PO Resp. 20 n.3. However, it appears that Petitioner has grafted together a portion of paragraph 321 that introduces peripheral device 32 with a portion of paragraph 322, which discusses features of base unit 33. However, this grafting has been done in such a way as to convey (incorrectly) that peripheral device 32, not base unit 33, includes unpacker 25, decoder 26, and compositor 29 that process the first processed video data received by the first peripheral device to generate second video data. Dr. Almeroth’s testimony, which copies Petitioner’s incorrectly altered quotation to paragraph 322 of Beel, is unreliable as to this claim limitation and is entitled to no weight.4 Thus, Petitioner has no expert testimony on which to rely for this claim limitation.” slip op. at 19
- Strike new argumentNew argument disregardedDecided for patent owner
“5 At the oral argument, when challenged on its reliance on paragraph 322, Petitioner argued that paragraph 321 of Beel teaches this limitation. Tr. 22:26–23:24. Petitioner did not make this argument in the Petition and, instead, raised it for the first time during oral argument; thus, it will not be considered. See Dell Inc. v. Acceleron, LLC, 884 F.3d 1364, 1369 (Fed. Cir. 2018) (“Unless it chose to exercise its waiver authority under 37 C.F.R. § 42.5(b), the Board was obligated to dismiss Dell’s untimely argument given that the untimely argument in this case was raised for the first time during oral argument.”). Even if we were to consider this new argument, it would not be persuasive. As Patent Owner observes (PO Resp. 20), any processing performed by peripheral device 32 in paragraph 321 is on data received from the processing device and destined for the base station via the network, rather than data flowing in the direction of the first processed video data of claim 1.” slip op. at 22
Patent outcomesUS 11,966,347 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 11,966,347 - Gettattle, Inc. v. Afterwords, Inc.All claims unpatentablePTAB · Oct 5, 2026 · IPR2025-00677 · APJ Ryan H Flax · IPR · Final written decision
Claims 1–7, 10, 13, 16, 18, and 19 are unpatentable as anticipated by Douglas and Ganesh; the revised contingent motion to amend is denied.
RulingsFinal written decision- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“record before us, we conclude that Petitioner proves by a preponderance of the evidence that each challenged claim of the ’811 patent is anticipated by Douglas and by Ganesh. Accordingly, we find that claims 1–7, 10, 13, 16, 18, and 19 of the ’811 patent are unpatentable. Moreover, we find that Patent Owner’s Revised Contingent Motion to Amend adds new matter in every proposed substitute claim, and, therefore, the motion is denied.” slip op. at 80
- 112 supportMotion to amend, deniedDenied
“Because the RMTA does not meet the foundational statutory and regulatory requirements, we decline to reach Petitioner’s arguments as to the asserted unpatentability of the proposed substitute claims. C. CONCLUSION ON REVISED MOTION TO AMEND Because the RMTA does not meet foundational statutory and regulatory requirements for a motion to amend, it is denied.” slip op. at 80
Patent outcomesUS 10,430,811 unpatentable§ 102 anticipationcites PhillipsPatents in suitUS 10,430,811 - Uatp IP LLC v. Slick Slide LLCSome claims unpatentablePTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision
Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20
Patent outcomesUS 11,998,854 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · NautilusPatents in suitUS 11,998,854
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.