PTAB
Advanced fields
60 decisions · 1007msnewest first
  • PTAB · 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 mixed
    Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
    Patents 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 Nautilus
    Patents 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 · Nautilus
    Patents in suitUS 10,713,959
  • PTAB · Sep 8, 2026 · PGR2025-00023 · APJ Per Curiam · PGR · Final written decision

    Claims 1–9 are unpatentable as anticipated by the ’629 publication; the claims are not entitled to the 2013 priority date.

    RulingsFinal written decision
    • Skill levelSkill level board ownOther

      “We find that a rigid requirement as to the subject of a POSITA’s doctoral degree (e.g., biochemical engineering, enzymology), or experience working specifically with horseshoe crab proteins, is not consistent with the evidence of record. See, e.g., Ex. 1067, 20:23–21:2 (Dr. Schaefer testifying that the fact the “name of [his] Ph.D. is immunology . . . does not change the fact that the core of [his] thesis training was really in molecular biology”), 22:3–15 (explaining that “the fact that the production of proteins recombinantly is mostly species agnostic”); Ex. 1069, 45:20–47:17 (Dr. Morris testifying that whether a person is a POSITA depends on the person’s “experience, [ ] publications,” and work done for the Ph.D. rather than the name of the Ph.D. program). We also find that evidence of record supports Petitioner’s assertion that, for purposes of defining a POSITA, “[m]ore education could substitute for experience, and vice versa.” See, e.g., Pet. 22; Ex. 1065, 99:14–100:3. Accordingly, based on the entirety of the trial record, we find a POSITA with respect to the claims of the ’109 patent would have had a two years of experience with cloning genes, expressing cloned genes as proteins, and/or characterizing such cloned genes and proteins, with more education being able to substitute for experience, and vice versa. A POSITA may also have collaborated with others, including those with specific experience in utilizing or assessing horseshoe crab Factor C for endotoxin detection and quantitation.” slip op. at 9

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

      “Neither party proposes an express construction of any claim term. See Pet. 22–23 (not proposing any constructions); PO Resp. 23 (“Patent Owner agrees that the terms can be afforded their plain and ordinary meaning.”). However, Patent Owner states that some of Petitioner’s arguments implicitly construe claim 1 in an erroneous manner. PO Resp. 23–28. “For example, Petitioner argues that ‘an adequate written description would have to either disclose representative examples of the possible working cascades of various proteins or some accurate structural feature of the claimed proteins that allow them to function in the claimed assay as a whole.’” Id. at 23 (quoting Pet. 35). Patent Owner argues that, contrary to what Petitioner’s argument allegedly implies, “Claim 1 is directed to a method for producing an endotoxin assay agent” and does not require the use – Owner that claim 1 does not require the use of endotoxin assay agent. However, the claimed endotoxin assay agent must be capable of performing the assay, as counsel for Patent Owner acknowledged. Tr. 83:5–9.” slip op. at 10

    • BurdenNot shown unpatentable

      “In this case, to show that the claims of the ’109 patent are unpatentable for lack of written description, Petitioner would have needed to show that the specification as filed (i.e., the ’420 application) fails to reasonably convey to those skilled in the art that Patent Owner had possession of the claimed subject matter as of the July 3, 2023, filing date. Petitioner did not. Pet. 23–24. Nor does Petitioner’s declarant offer testimony that could support such a showing. See Ex. 1003 ¶50 (“I have been asked to provide my opinions as to the state of the art in this field for purposes of determining what the inventors disclosed as their invention as of December 10, 2013.”), ¶51 (“Whenever I offer an opinion in this declaration about the knowledge of a POSA, the manner in which a POSA would have understood the claims of the ’109 patent or its description, the manner in have been led to do based on the prior art, I am referencing the December 10, 2013 timeframe.”). In our Institution Decision, we stated: Although the ’420 application is essentially identical to the ’767 application, the person of ordinary skill in 2013 is not the same as in 2023. See Ariad, 598 F.3d at 1351 (“[T]he [written description] test requires an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” (emphasis added)). Thus, the information presented in the Petition, which is limited to the perspective of a 2013 POSITA, does not demonstrate that it is more likely than not that at least 1 of the claims challenged in the Petition is unpatentable for lack of written description. Inst. Dec. 12 (alterations in original). During trial, Petitioner did not present any further arguments in support of Ground 1. See generally Pet. Reply. Petitioner has failed to prove that claims 1–9 are unpatentable for failing to meet the written description requirement set forth in 35 U.S.C. § 112(a).” slip op. at 12

    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot shown unpatentable

      “Although the evidence before us shows that, in 2013, a POSITA knew how to recombinantly express genes in expression systems such as CHO or HEK-293 cell lines, the evidence shows that this was true only for genes whose genetic sequences were known or readily available. See, e.g., Ex. 1069, 34:11–22 (“Q. Okay. So you would agree that the creation of the recombinant protein requires the underlying sequence of, as you said, the original animal? A. Of course.”) Because it is undisputed that, in 2013, the genetic sequence for Limulus polyphemus Factor C was unknown, or least not publicly available, Falko-Gunter does not support a finding of adequate written description here. See, e.g., Tr. 48:18–19 (“Patent Owner agrees that there had not been, as of 2013, the full length cDNA sequence for Limulus polyphemus Factor C published.”).” slip op. at 23

    Patent outcomesUS 11,959,109 unpatentable
    Claim construction§ 102 anticipation§ 112 disclosure
    Patents in suitUS 11,959,109
  • PTAB · Sep 8, 2026 · IPR2025-00440 · APJ Tawen Chang · IPR · Final written decision

    Claim 21 is unpatentable as obvious over Mizumura with either the ’498 PCT or McClymont; the Revised Contingent Motion to Amend proposing claim 22 is denied.

    RulingsFinal written decision
    • Skill levelSkill level patent owner adoptedDecided for patent owner

      “overlap to a significant degree, i.e., a person with a Ph.D. in a discipline related to biological sciences and having had at least two years of work experience. However, the parties’ proposals differ slightly in the specific subjects in which a POSA would have had a doctoral degree, and whether the person’s work experience must have been directly related to horseshoe crab Factor C. As an initial matter, we find that a rigid requirement as to the subject of a POSA’s doctoral degree (e.g., biochemical engineering, enzymology), or experience working specifically with horseshoe crab proteins, is not consistent with the evidence of record. See, e.g., Ex. 1067, 20:23–21:2 (Dr. Schaefer testifying that the fact the “name of [his] Ph.D. is immunology . . . does not change the fact that the core of [his] thesis training was really in molecular biology”), 22:3–15 (explaining “the fact that the production of proteins recombinantly is mostly species agnostic”); Ex. 1069, 45:20–47:17 (Dr. Morris testifying that whether a person is a POSA depends on the person’s “experience, [ ] publications,” and work done for the Ph.D. rather than the name of the Ph.D. program). We also find that evidence of record supports Petitioner’s assertion that, for purposes of defining a POSA, “[m]ore education could substitute for experience, and vice versa.” See, e.g., Pet. 19; Ex. 1065, 99:14–100:3. with respect to the claims of the ’318 patent would have had a Ph.D. in molecular biology, biochemistry, or a related discipline, and about two years of experience with cloning genes, expressing cloned genes as proteins, and/or characterizing such cloned genes and proteins, with more education being able to substitute for experience, and vice versa. A POSA may also have collaborated with others, including those with specific experience in utilizing or assessing horseshoe crab Factor C for endotoxin detection and quantitation.” slip op. at 13

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

      “C. Claim Construction The parties agree that “the terms in claim 21 can be afforded their plain and ordinary meaning for purposes of this proceeding” without further construction. Pet. 19–20; PO Resp. 11. Because express claim construction is not needed to resolve the issues in this case, we need not, and do not, construe expressly any claim term for purposes of this Decision. 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 14

    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner

      “Carrying Out the Invention section, that “[t]he Factor C of the present invention is a Factor C derived from a horseshoe crab,” and states later in the same section that “[e]xamples of the horseshoe crab include . . . Limulus polyphemus.” Ex. 1006, 40. However, none of the remaining portions of ’767 application cited by Patent Owner relate directly to L. polyphemus; instead, the remaining portions of ’767 application cited by Patent Owner are directed to other species, in particular the Japanese horseshoe crab T. tridentatus. Further, Patent Owner’s witness, Dr. Schaefer, conceded that the ’767 application does not contain Factor C sequence information for L. polyphemus. See, e.g., Ex. 1067, 44:25–45:23. Although “[n]o length requirement exists for a disclosure to adequately describe an invention,” Falko-Gunter, 448 F.3d at 1365–1366, we are persuaded that a POSA would not, based on the totality of the above disclosures, reasonably understand that the inventors were in possession of the claimed HEK-293 recombinant L. polyphemus Factor C protein, in view of the state of the art as of December 10, 2013. In this regard, we note that adequate written description of a biological molecule, such as a HEK293 recombinant L. polyphemus Factor C protein, requires “more than a mere statement that it is part of the invention and reference to a potential method for isolating it”; instead, what is required is “‘a precise definition, such as by structure, formula, chemical name, or physical properties,’ not a mere wish or plan for obtaining the claimed chemical invention.” The Regents of the” slip op. at 21

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

      “Pfizer, Inc. v. Apotex, Inc., 480 F.3d 1348, 1364 (Fed. Cir. 2007). Neither do we see Petitioner’s arguments regarding the December 10, 2013 priority date to be “mutually opposed” as Dr. Schaefer testified. Ex. 1067, 216:4– 24. Instead, we credit evidence of record, including Dr. Jain’s testimony and the February 22, 2018 Mizumura Declaration, that existence of the full sequence would permit a more complete analysis and that such an analysis would provide a POSA with a reasonable expectation that the claimed L. polyphemus recombinant protein would have a residual activity within the claimed range. See, e.g., Ex. 1029, 2–5; Ex. 1010, 48; Ex. 1065, 117:14– 130:24 (explaining that comparison of partial sequences in the Tokunaga 1991 publication showed “difference around the cleavage site” between T. tridentatus and L. polyphemus but comparison of the full sequence revealed that “the catalytic triad of histidine, serine, aspartate . . . to be more similar between Tachypleus and Limulus”). Patent Owner asserts that “Petitioner’s reliance on a statement made by Dr. Mizumura in a declaration submitted during prosecution of the ’767 Application fails to fill the gap in the analysis” regarding reasonable expectation of success, because the declaration “offers no evidence of the percentage of conserved amino acid substitutions that exist to support the conclusion that a POSA would have expected residual activity to be maintained between Tachypleus tridentatus and Limulus polyphemus” PO Resp. 47. However, as noted above, Dr. Mizumura provides an alignment of Factor C proteins from the two different species of horseshoe crab, determines that the similarity between the amino acid sequence is 99.5%, states that the amino acid residues that can undergo N-type sugar chain that L. polyphemus, like T. tridentatus, would also be less susceptible to inhibition by ions. Ex. 1029, 4–5. For the reasons discussed above, we also disagree with Patent Owner’s assertion that Petitioner’s reasonable expectation of success argument is “nothing more than conclusory assertions with no support.” PO Resp. 46. Rather, we find Petitioner has shown, by a preponderance of the evidence, that a POSA would have had reason to combine the teachings of Mizumura and the ’498 PCT, with a reasonable expectation of success in arriving at the Factor C protein recited in claim 21.” slip op. at 38

    Patent outcomesUS 11,236,318 unpatentable
    Claim construction§ 103 obviousness§ 112 disclosurecites KSR · Graham
    Patents in suitUS 11,236,318
  • PTAB · Dec 10, 2025 · PGR2025-00054 · APJ Ryan H Flax · PGR · Institution

    The Board instituted PGR on claims 1–16 on all four grounds, finding at least one claim more likely than not unpatentable based on obviousness, indefiniteness, or lack of written description.

    RulingsInstitution decision
    • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

      “institute trial in a post-grant review. We institute a post-grant review only if the information presented in the petition filed under 35 U.S.C. § 321, if unrebutted, shows that it is more likely than not that at least one claim challenged in the petition is unpatentable. 35 U.S.C. § 324. On the existing record, we conclude that Petitioner demonstrates it is more likely than not that Petitioner would prevail in showing that at least one challenged claim of the ’781 patent is unpatentable under a presented ground. See generally Pet. Therefore, we grant institution of post-grant review. Our reasoning is discussed below.” slip op. at 2

    • PTAB / AIA Trials › Real party in interest / privityDecided for petitioner

      “STANDING Petitioner states that it certifies that: (1) the ’781 patent is available for post grant review because its earliest claimed effective filing date is October 9, 2018, and the patent issued less than nine months ago, on December 3, 2024; and (2) Petitioner is not barred or estopped from requesting a post grant review on the grounds in this petition. Pet. 5. This is sufficient. See 35 U.S.C. § 100(note)(A)–(B), § 321; 37 C.F.R. § 42.204(a). Patent Owner does not contest standing. See generally Prelim. Resp. B. REAL PARTIES-IN-INTEREST Petitioner states that “[t]he real parties-in-interest are Petitioner Straumann USA, LLC and its affiliates Institut Straumann AG and JJGC Indústria e Comércio de Materiais Dentários S.A.” Pet. 3. Patent Owner raises no objection and itself identifies “Smart Denture Conversions, LLC is the real party-in-interest.” Paper 4, 2; see generally Prelim. Resp. C.” slip op. at 3

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “At this point, we find little meaningful difference between the two proposed definitions. In fact, neither does Patent Owner’s witness, Mr. Leinsing, who states that his “opinions would not change under either definition.” Ex. 2011 ¶ 42. And, as set forth above, Patent Owner asserts that, for the sake of its present arguments, it matters not which of the two proposed definitions we use for this proceeding. Prelim. Resp. 21. Thus, at this stage, we accept and use Petitioner’s proposed definition of the ordinarily skilled artisan, which, unlike Patent Owner’s, does not implicate reliance on the knowledge of people other than the individual ordinarily skilled artisan. Petitioner’s definition appears to comport with the level of skill in the art reflected in the prior art of record and the ’781 patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“[T]he prior art itself [may] reflect[] an appropriate level” of ordinary skill in the art) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). This issue may be further developed at trial by the parties, if desired. C.” slip op. at 19

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

      “same claim construction standard that is used to construe patent claims in a civil action in federal district court thus, by default, we give claim terms their ordinary and customary meaning, which is “the meaning that the term would have to a person of ordinary skill in the art in question at the time of the invention.” 37 C.F.R. § 42.200(b); Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Petitioner indicates that None of the claim terms of claims 1–16 need to be construed to determine the patentability issues presented in this petition. The petition applies the ordinary meaning of the claim language as it would be understood by a POSA after reading the ’781 patent. Ex. 1002, ¶130. Petitioner will propose a construction if Patent Owner argues or the Board determines that one is required for any term. Pet. 31 (citing Ex. 1002). And, Patent Owner presents no express position on claim construction at this point. See generally Prelim. Resp. At this stage of the proceeding, we do not expressly construe any claim terms; however, this position is preliminary and we may change it based on the fully developed record at trial.8 D.” slip op. at 19

    Claim construction§ 103 obviousness§ 112 disclosurecites Graham
    Patents in suitUS 12,156,781
  • PTAB · Nov 21, 2025 · IPR2025-00956 · APJ Ryan H Flax · IPR · Institution

    The Board instituted IPR on claims 1–12 under all asserted grounds, finding a reasonable likelihood that at least one claim is unpatentable.

    RulingsInstitution decision
    • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

      “institute trial in an inter partes review. We institute an inter partes review only if the information presented in the petition filed under 35 U.S.C. § 311, and any preliminary response filed under § 313, shows that there is a reasonable likelihood that Petitioner would prevail with respect to at least one of the claims challenged in the petition. 35 U.S.C. § 314. After reviewing the parties’ submissions in view of the existing record, we conclude that Petitioner demonstrates a reasonable likelihood it would prevail in showing that at least one challenged claim of the ’992 patent is unpatentable under the presented grounds. See Pet. Therefore, we grant institution of inter partes review. Our reasoning is discussed below. A.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “These two proposed definitions of the ordinarily skilled artisan share many consistencies, for example, the types of degrees and experience such a person would have had, but differ in the number of years of experience. Petitioner proposes the ordinarily skilled artisan would have had at least five years of experience and Patent Owner proposes at least three years (which would necessarily include five years, too). Patent Owner also proposes that the ordinarily skilled artisan would have consulted a dentist, oral surgeon, prosthodontist, or periodontist with experience in dental implants and prosthetics. At this point, we find little meaningful difference between the two proposed definitions. In fact, neither does Patent Owner’s witness, Mr. Leinsing, who states that his “opinions would not change under either definition.” Ex. 2011 ¶ 40. Thus, at this stage, we accept and use Petitioner’s proposed definition of the ordinarily skilled artisan, which, unlike Patent Owner’s, does not implicate reliance on the knowledge of people other than the individual ordinarily skilled artisan. Petitioner’s definition appears to comport with the level of skill in the art reflected in the prior art of record and the ’992 patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“the prior art itself [may] reflect[] an appropriate level” of the ordinary level of skill in the art) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). This parties may further developed this issue at trial, if desired. C.” slip op. at 13

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

      “The Board interprets claim terms in an inter partes review using the same claim construction standard that is used to construe patent claims in a civil action in federal district court. 37 C.F.R. § 42.100(b). In construing claims, district courts and the Board here, by default, give claim terms their ordinary and customary meaning, which is “the meaning that the term would have to a person of ordinary skill in the art in question at the time of the invention.” Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc).” slip op. at 14

    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner

      “Here, the first claim limitation at issue is broad, i.e., different thread pattern/profile between a definite and a temporary screw, and the Specification’s and priority applications’ disclosure is narrow and specific, asymmetric buttress style threads in a temporary screw and symmetrical threads in a definite screw (are different). Any apparent predictability in or maturity of the relevant field here must be contrasted with the fact that the Specification, considering the ’992 patent itself or any of the identified priority applications, never once even discusses the (claimed) concept of specifically differing the thread style between a temporary and a definitive screw. Any differences in thread style are not called out by the disclosure, but are described and can be discerned only in relation to the respective threads’ functionality, i.e., Fig. 75’s temporary screw 190 has buttress-style threading so it can be pulled out rather than unscrewed from the abutment; Fig. 9’s definitive screw 75 has male threads that fill the female threads of the abutment 8 for a secure permanent engagement. Ex. 1001, 15:23–30, 21:25–44, 23:3–36; Ex. 1012, 97–98, Figs. 9, 75. And, although it is possible for a single disclosed species to provide written description support for a claimed genus, “a sufficient description of a genus . . . requires the disclosure of either a representative number of species falling within the scope of the genus or structural features common to the members of the genus so that one of skill in the art can ‘visualize or recognize’ the members of the genus.” Ariad, 598 F.3d at 1350; see also Synthes USA, LLC v. Spinal Kinetics, Inc., 734 F.3d 1332, 1344 (Fed. Cir. 2013). That does not appear to be the case here—the present record does not support that the described asymmetrical buttress, serrated style of different temporary screw threading (relative to that of the definitive screw and regardless of the direction of the threads for rotation) is sufficiently representative of the genus’s “different” thread patterns/profiles. See, e.g., Ex. 1006 (a buttress style thread does not function the same as a buttress reverse or 75º joint profile or rounded, or trapezoidal thread).” slip op. at 30

    Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham
    Patents in suitUS 11,937,992
  • PTAB · Nov 18, 2025 · IPR2024-01014 · APJ Zhenyu Yang · IPR · Final written decision

    Petitioner did not show claims 1–8 unpatentable because they are entitled to the 2004 priority date, making Barbour unavailable as prior art.

    RulingsFinal written decision
    • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Entitled to earlier dateDecided for patent owner

      “For a claim to a biological material, the enablement requirement of § 112, first paragraph, does not require such assured access to a microorganism deposit as of the filing date; what is required is assurance of access (to the microorganism culture by the public upon issuance of a patent on the application) prior to or during the pendency of the application, so that, upon issuance of a U. S. patent on the application, the public will, in fact, receive something in return for the patent grant. Feldman, 517 F.2d at 1355. Patent Owner has persuaded us that such exception not only applies to a deposit, but also extends to a biological material known and readily available. See 52 Fed. Reg. 34080, 34081. In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art.” slip op. at 15

    • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

      “In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art. Because all of Petitioner’s challenges rely on Barbour (Pet. 6), all those challenges fail.” slip op. at 15

    • Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artNot shown unpatentable

      “In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art. Because all of Petitioner’s challenges rely on Barbour (Pet. 6), all those challenges fail.” slip op. at 15

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

      “would understand that the term “‘flanked by’ permits overlap between the expression cassette and the DNA sequence it is flanked by.” Pet. 24–26. Patent Owner does not propose any claim construction. PO Resp. 6–7. On this record and for purposes of this Decision, we see no need to expressly construe any claim term.” slip op. at 9

    Patent outcomesUS 8,901,378 not shown unpatentable
    Claim construction§ 102 anticipation§ 112 disclosurecites Phillips
    Patents in suitUS 8,901,378
  • PTAB · Oct 8, 2025 · IPR2025-00629 · APJ Scott C Moore · IPR · Institution

    The Board instituted IPR of claims 1–20 on all asserted grounds, finding a reasonable likelihood that claim 1 is obvious over Beard and Laufer.

    RulingsInstitution decision
    • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

      “We may institute an inter partes review when “the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). If we institute an inter partes review, the trial must encompass all claims and grounds identified in the Petition. 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”). For the reasons set forth below, we conclude that there is a reasonable likelihood that Petitioner will prevail in establishing the unpatentability of one or more claims of the ’711 Patent. We, therefore, institute inter partes review of claims 1–20 on the grounds identified in the Petition. B.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “Petitioner contends 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 or avionics fields, or (2) at least four years of experience in any of the above industries. 1 The Leahy-Smith America Invents Act (“AIA”) included revisions to 35 U.S.C. §§ 102 and 103 that became effective on March 16, 2013. Because the applications from which the ’711 Patent claims priority were all filed after this date, the post-AIA version of §103 applies. See Ex. 1001, codes (60), (63). 2 U.S. Patent No. 9,769,387 B1, iss. Sept. 19, 2017 (Ex. 1009). 3 U.S. Patent App. Pub. No. 2017/0059692 A1, pub. Mar. 2, 2017 (Ex. 1010). 4 U.S. Patent App. Pub. No. 2012/0106800 A1, pub. May 3, 2012 (Ex. 1021). 5 U.S. Patent App. Pub. No. 2017/0161911 A1, pub. June 8, 2017 (Ex. 1007). 6 U.S. Patent App. Pub. No. 2013/0301905 A1, pub. Nov. 14, 2013 (Ex. 1024). 7 U.S. Patent App. Pub. No. 2012/0004844 A1, pub. Jan. 5, 2012 (Ex. 1025). 8 PCT App. Pub. No. WO 2017/123477 A1, pub. July 20, 2017 (Ex. 1022). 9 U.S. Patent App. Pub. No. 2017/0160751 A1, pub. June 8, 2017 (Ex. 1005). Pet. 8 (citing Ex. 1003 ¶¶ 50–54). Patent Owner does not presently dispute Petitioner’s proposed formulation. See generally Prelim. Resp. For purposes of this Decision, we adopt and apply Petitioner’s formulation regarding the level of ordinary skill in the art because it is (1) consistent with the ’711 Patent and the asserted prior art; and (2) it is supported by the testimony of Dr. Singhose. B.” slip op. at 6

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

      “But the Detecting Limitations of claims 1, 19, and 20, merely require that a target be “detected.” The Detecting Limitations do not require that target detection be performed “aboard the reference UAV,” and claim 19 does not recite or require “machine learning.” Moreover, the Specification makes clear that the claims should not be limited to aspects of the disclosed embodiments, as Patent Owner proposes to do here. See, e.g., Ex. 1001, 2:56–59 (“The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims . . . .”) Patent Owner additionally fails to cite any lexicographic definition or clear and unambiguous disclaimer of claim scope sufficient to limit the claims in the manner it proposes. We, thus, are not persuaded that the Detecting Limitations require “applying aboard the reference UAV a machine learning model to the capture image for: (i) identifying a target in the captured image.”” slip op. at 8

    • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

      “Priority Date of the Challenged Claims Petitioner contends that claims 1–20 of the ’711 Patent “should not have priority to the October 9, 2016 filing date of U.S. provisional [patent] application 62/405,972 due to a lack of written description support.” Pet. 3. Petitioner thus “assumes” a priority date of October 1, 2017 (the filing date of U.S. Provisional Patent Application No. 62/556,449) for purposes of this proceeding. Id. at n.2; see also Ex. 1003, code (60). Patent Owner does not presently dispute Petitioner’s contention that the ’711 Patent is not entitled to a priority date earlier than October 1, 2017. See generally Prelim. Resp. For purposes of this decision, we accept Petitioner’s undisputed contention that the ’711 Patent is not entitled to a priority date prior to 10 Any determination, no matter how designated in this Institution Decision (except our ultimate decision to institute), is preliminary and non-binding. Our Final Written Decision, based on a fully developed record of arguments and evidence, will state our binding determinations, findings, and conclusions. If a party disagrees with this preliminary construction, or any other determination set forth in this Institution Decision, that party should present its arguments at trial. The parties are reminded that any arguments not made during trial will be considered waived. Patent Owner is further reminded that arguments in the Preliminary Response are not preserved and will be considered waived at trial unless those arguments are re-raised in the Patent Owner Response. The parties are additionally reminded that arguments raised in subsequent briefing must be set forth in full in the briefs themselves, and may not be incorporated by reference from prior filings such as the Preliminary Response. See 37 C.F.R. § 42.6(a)(3). October 1, 2017.11 Accordingly, Petitioner has made a sufficient showing that all of the cited references qualify as prior art. See Pet. 4–6. D.” slip op. at 11

    Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
    Patents in suitUS 10,514,711
  • PTAB · Oct 8, 2025 · IPR2025-00525 · APJ Scott C Moore · IPR · Institution

    The Board instituted review of claim 21 on all asserted grounds after finding a reasonable likelihood it is obvious over Beard.

    RulingsInstitution decision
    • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

      “presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). If we institute an inter partes review, the trial must encompass all claims and grounds identified in the Petition. 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”). For the reasons set forth below, we conclude that there is a reasonable likelihood that Petitioner will prevail in establishing the unpatentability of claim 21, the sole challenged claim. We, therefore, institute inter partes review of claim 21 on the grounds asserted in the Petition. B.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “[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. Pet. 21 (citing Ex. 1003 ¶ 47). Patent Owner does not presently dispute Petitioner’s proposed formulation. See generally Prelim. Resp. For 3 U.S. Patent App. Pub. No. US 2016/0253907 A1, published Sept. 1, 2016 (Ex. 1010). 4 PCT Pub. No. WO 2016/078093 A1, published May 26, 2016 (Ex. 1011). 5 PCT Pub. No. WO 2016/154949 A1, published Oct. 6, 2016 (Ex. 1012). 6 U.S. Pat. App. Pub. No. US 2016/0127890 A1, published May 5, 2016 (Ex. 1013). 7 PCT Pub. No. WO 2015/043123 A1, published Apr. 2, 2015 (Ex. 1014). purposes of this Decision, we adopt and apply Petitioner’s formulation regarding the level of ordinary skill in the art because it is (1) consistent with the ’959 Patent and the asserted prior art; and (2) it is supported by the testimony of Dr. Chowdhary. B.” slip op. at 5

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner

      “But before describing the embodiments cited by Patent Owner, the Specification plainly states: “Any terms not expressly defined herein have their conventional meaning as commonly understood by those having skill in the relevant art(s).” Ex. 1001, 4:64–67. Thus, the Specification itself cautions against construing the claim terms such as “secure identifier” as limited to the scope of the disclosed embodiments. Here, Patent Owner has not cited any express definition of “secure identifier,” or identified any explicit disclaimer of claim scope that might justify narrowing the scope of this claim term to specific embodiments disclosed in the Specification. In the absence of such a definition or disclaimer, we are not persuaded that the scope of the claim term “secure identifier” should be limited to specific aspects of the preferred embodiments cited by Patent Owner. See Prelim. Resp. 7–14. On this record, and at this stage of the proceeding, we decline to adopt Patent Owner’s proposed construction and preliminarily construe “secure identifier” as “a credential that can be used to securely verify the identity of a device, such as an airborne object or ground-based transmitter.”8” slip op. at 10

    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner

      “’071 Application lack adequate written description support for the “secure identifier” claim limitation. For a patent claim to be entitled to the priority date of an earlier-filed application, the earlier application must provide complete written description support for the claim as required by 35 U.S.C. § 112(a). L.A. Biomedical Rsch. Inst. at Harbor-UCLA Med. Ctr. v. Eli Lilly & Co., 849 F.3d 1049, 1057 (Fed. Cir. 2017) (“L.A. Biomed”). To satisfy this requirement, the written description must “reasonably convey” to a person of ordinary skill in the art that the inventor had possession on the claimed priority date of each limitation of the later-claimed subject matter. L.A. Biomed, 849 F.3d at 1057. It is not enough that an earlier application’s disclosure “renders the later-claimed invention obvious;” as “the disclosure must describe the claimed invention with all its limitations.” L.A. Biomed, 849 F.3d at 1057. On this record, we agree with Petitioner that the ’153 Provisional and ’071 Application lack adequate written description support for the “secure identifier” limitation of claim 21. We have preliminarily construed “secure identifier” as “a credential that can be used to securely verify the identity of a device, such as an airborne object or ground-based transmitter.” See supra § II.B. As discussed above, the Specification of the ’959 Patent does not use the term “secure identifier,” but the Specification contains extensive discussion of the need for an identification credential that is secure (e.g., difficult for a bad actor to clone or impersonate). See, e.g., Ex. 1001, 1:56– 65 (discussing the need for a system that is difficult to “clone”), 10:20–49 (discussing the need “trust” between a drone and ground-based equipment, and the need for a way to verifying the drone’s credentials), 11:5–12:62 (disclosing the use of encryption and a rotating SSID to generate a secure identifier for a drone). None of the portions of the Specification cited above is present in the ’153 Provisional or the ’071 Application. See generally Ex. 1006, 1007. The ’153 Provisional and ’071 Application discuss the need for identifiers for low-altitude aircraft (see, e.g., Ex. 1006, 2; Ex. 1007, 9), but there is no discussion of any need for an identification credential to be secure or resistant to cloning or impersonation. See generally Ex. 1006, 1007. The ’153 Provisional and ’071 Application do not disclose the use of encryption, SSIDs (much less rotating SSIDs), or any other technologies for the purpose of verifying the authenticity of an identification credential. See generally id. Based on our review of the ’153 Provisional and ’071 Application, we preliminarily conclude that neither of these applications would have reasonably conveyed to a person of ordinary skill in the art that the inventor then had possession of the concept of the “secure identifier” that was later claimed in the ’959 Patent.” slip op. at 12

    Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham
    Patents in suitUS 10,713,959
Page 1 of 6
← Previous12345…Next →

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.