- 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 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Maxell LtdNo claims unpatentablePTAB · Oct 31, 2025 · IPR2024-00777 · APJ Jameson Lee · IPR · Final written decision
Claims 16–27 were not shown unpatentable because Petitioner failed to account for limitations 16[b] and 16[i] and their counterparts across the asserted obviousness grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner proposes that a person of ordinary skill in the art “would have a Bachelor of Science degree in Electrical Engineering, Computer Engineering, Computer Science, Human Computer Interaction, or a related technical field, with at least one year of experience working in the field of user interfaces and/or content management.” PO Resp. 11 (citing Ex. 2040 ¶ 53). The Decision on Institution adopted Petitioner’s proposed level of ordinary skill in the art. Inst. Dec. 10. We find Patent Owner’s stated level to be less precise than that proposed by Petitioner in that the modifier “at least” used by Patent owner imposes no upper bound on the amount of experience possessed by one of ordinary skill in the art. Also, Patent Owner states: “The difference between the Board’s definition and Patent Owner’s (EX2040. ¶53) does not change the arguments set forth herein.” PO Resp. 11. Thus, we continue to adopt Petitioner’s stated level of ordinary skill in the art.4 4 All of our findings and conclusions would still be the same, however, had we applied Patent Owner’s articulation of the level of ordinary skill in the art.” slip op. at 8
- Prior constructionPrior construction adoptedDecided for patent owner
“In its Reply, Petitioner does not assert that the district court’s construction is incorrect. We agree with Patent Owner that the district court’s construction is better than Petitioner’s proposed construction, because for reasons indicated by Patent Owner, which are not disputed by Petitioner, settings in the computer, e.g., dedicated folders for each user are the user profiles, rather than simply data alone of any kind. Further, when asked about the appropriateness of the district court’s construction, counsel for Petitioner expressed that Petitioner has no objection to the Board’s adopting the district court’s construction for “user profile”: JUDGE LEE: So, you’d be fine with just going with the District Court’s construction? MR. HEINTZ: Yes, Your Honor. Tr. 15:22–24. For the foregoing reasons, we adopt the district court’s construction for “user profile,” i.e., “a collection of settings and information associated with a user.”” slip op. at 13
- BurdenNot shown unpatentable
“PO Resp. 30–31 (Figure 26 omitted). In its Reply, Petitioner still does not provide an articulated reason for placing user profile selection buttons, labeled with user names, within Horn’s panes 2601 or 2602. Reply 12–14. Although Horn does describe personalized profile, Petitioner points to no disclosure of Horn as to how a user would have selected his or her own profile from among a plurality of user profiles. Petitioner presents no reason for placing these user profile selection buttons, labeled with user names, gleaned from or suggested by Baumgartner, within either pane 2601 or pane 2602 in Horn’s workspace view. Further, pane 2602 contains “a list of all collections defined by MFS and the user,” and pane 2601 lists the source examined by the user to create his or her collections. Ex. 1005, 19:41–46. That disclosure suggests the contents of panes 2601 and 2602 are tied to one particular user. No rational basis is articulated by Petitioner to place user profile selection buttons within these panes which appear to be in the profile space of one user. For the foregoing reasons, Petitioner has not adequately accounted for limitation 16[b].” slip op. at 22
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“The test for sufficiency of a written description under 35 U.S.C. § 112 is whether the earlier application’s disclosure “reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date.” Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). The specification must “clearly allow persons of ordinary skill in the art to recognize that [the inventor] invented what is claimed.” Id. The Court of Appeals for the Federal Circuit has explained: One shows that one is “in possession” of the invention by describing the invention, with all its claimed limitations, not that which makes it obvious. Id. (“[T]he applicant must also convey to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention. The invention is, for purposes of the ‘written description’ inquiry, whatever is now claimed.”) (emphasis in original). One does that by such descriptive means as words, structures, figures, diagrams, formulas, etc., that fully set forth the claimed invention. Although the exact terms need not be used in haec verba, see Eiselstein v. Frank, 52 F.3d 1035, 1038, 34 USPQ2d 1467, 1470 (Fed.Cir.1995) (“[T]he prior application need not describe the claimed subject matter in exactly the same terms as used in the claims. . . .”), the specification must contain an equivalent description of the claimed subject matter. A description which renders obvious the invention for which an earlier filing date is sought is not sufficient. Lockwood v. American Airlines, Inc., 107 F.3d 1565 (Fed. Cir. 1997).” slip op. at 31
Patent outcomesUS 11,017,815 not shown unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 11,017,815 - 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 · GrahamPatents 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 · GrahamPatents in suitUS 10,713,959 - Microsoft Corporation v. Interdigital Patent Holdings, Inc.No claims unpatentablePTAB · Jun 23, 2025 · IPR2024-00538 · APJ Miriam L Quinn · IPR · Final written decision
The Board held all challenged claims of the ’933 and ’054 patents not unpatentable because the claims were entitled to the December 22, 2009 priority date, making the asserted prior art unavailable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“the time of the invention as someone that would have had “a bachelor’s degree in computer science, electrical engineering, computer engineering, or a closely related field, and one to three years of experience working with wirelessly connected mobile devices that used common wireless communications protocols such as Bluetooth and 802.11.” 537 Pet. 17 (citing Ex. 1203 ¶¶ 29–32). Petitioner also contends that this description “would not differ materially between December 2008 and June 2013,” the earliest possible priority date for the patents-at-issue and the priority date alleged by Petitioner, respectively. Petitioner further contends that more education “would compensate for less work experience and vice versa.” Id. Petitioner. 537 PO Resp. 6−7; 538 PO Resp. 6−7. Accordingly, for purposes of this Decision, we adopt Petitioner’s description as our own. We adopt Petitioner’s level of ordinary skill in the art particularly because it specifies having one to three years of experience working with wireless devices that use Bluetooth and 802.11.” slip op. at 16
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner construes the claims to have their “plain and ordinary meaning” and contends “that no terms invoke means-plus-function analysis.” 537 Pet. 17–18; 538 Pet. 18−19. Patent Owner does not contend that any terms require construction. 537 PO Resp. 6; 538 PO Resp. 6. We have not identified any terms that require construction for us to decide the threshold issue of priority. And given that the parties have no disputed terms, no claim terms are hereby construed.” slip op. at 17
- Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner
“The written description requirement is satisfied when “the missing descriptive matter” is necessarily present in the original “application’s specification such that one skilled in the art would recognize such a disclosure.” Tronzo v. Biomet, Inc., 156 F.3d 1154, 1159 (Fed. Cir. 1998). Thus, it is sufficient to show that the written description actually or inherently discloses the claim element. TurboCare Div. of Demag Delaval Turbomachinery Corp. v. Gen. Elec. Co., 264 F.3d 1111, 1118−20 (Fed. Cir. 2001). We also note that Patent Owner argues that the field of the 948 application is a predictable application of wireless communications, which, compared to other complex and unpredictable technologies, would require a lower level of detail to satisfy the requirement. See Hologic, Inc. v. Smith & Nephew, Inc., 884 F.3d 1357, 1361 (Fed. Cir. 2018); see also Ariad Pharmaceuticals, Inc. v. Eli Lilly and Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (“the level of detail required . . . varies depending on the nature and scope of the claims and on the complexity and predictability of the relevant technology.”); 537 PO Resp. 26−27; 537 Edwards Decl. ¶¶ 82, 87; 537 Surreply 8.” slip op. at 20
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner
“1277 (Fed. Cir. 2011); PowerOasis, Inc. v. T-Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008). At issue in the instant proceedings is the first requirement, whether the written description of the 948 application is sufficient, because Petitioner contends that the claims of the ’933 and ’054 patent are not entitled to claim priority to ancestry applications under 35 U.S.C. § 120. 537 Pet. 18.43 We disagree with Petitioner because we find that the claims are supported by the written description of the 948 application disclosure.” slip op. at 18
Patent outcomesUS 9,173,054 not shown unpatentableClaim construction§ 102 anticipation§ 112 disclosurecites PhillipsPatents in suitUS 9,173,054 - Microsoft Corporation v. Interdigital Patent Holdings, Inc.No claims unpatentablePTAB · Jun 23, 2025 · IPR2024-00537 · APJ Miriam L Quinn · IPR · Final written decision
The Board held all challenged claims of the ’933 and ’054 patents not unpatentable because the claims are entitled to priority to December 22, 2009, making Forutanpour not prior art.
RulingsFinal written decision- BurdenFwd all claims patentableNot shown unpatentable
“VI. ANALYSIS OF UNPATENTABILITY Because of our determination that the priority date of December 22, 2009 is appropriate, we conclude that the Forutanpour reference (a U.S. patent application published on April 7, 2011) is not prior art. presented in either Petition. VII. CONCLUSION Having reviewed the argument and supporting evidence of record, and after a full and fair hearing, we determine that Petitioner has not demonstrated by a preponderance of the evidence that any of the challenged claims of the ’933 and ’054 patents are unpatentable.” slip op. at 36
- Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateDecided for patent owner
“Thus, we find that the 948 application reasonably conveys to a person of ordinary skill in the art that the inventors contemplated the communication of wireless devices to continue using the known method of file/data transfers via Wi-Fi and that the technique for device discovery using Bluetooth would additionally provide environment information useful for assessing which nearby device has the TapApp functionality. Disclosure of the knowledge of wireless radio dialogue between devices to collect further information to provide a particular location of a device informs a person of ordinary skill in the art that the 948 application was not limited to using only Bluetooth for the method performed by the WTRU, culminating in data transfer.” slip op. at 23
- Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artDecided for patent owner
“sufficiency of the written description, we conclude that the 948 application sufficiently describes Wi-Fi transfer for data transmissions in WTRUs even if the method also uses Bluetooth for selecting target WTRUs. Accordingly, the claims of the ’933 and ’054 patents are entitled to the priority date of December 22, 2009, the date of the 948 application. VI. ANALYSIS OF UNPATENTABILITY Because of our determination that the priority date of December 22, 2009 is appropriate, we conclude that the Forutanpour reference (a U.S. patent application published on April 7, 2011) is not prior art.” slip op. at 36
- Skill levelSkill level petitioner adoptedDecided for petitioner
“F. Level of Ordinary Skill in the Art Petitioner identifies a person of ordinary skill in the art (“POSITA”) at the time of the invention as someone that would have had “a bachelor’s degree in computer science, electrical engineering, computer engineering, or a closely related field, and one to three years of experience working with wirelessly connected mobile devices that used common wireless communications protocols such as Bluetooth and 802.11.” 537 Pet. 17 (citing Ex. 1203 ¶¶ 29–32). Petitioner also contends that this description “would not differ materially between December 2008 and June 2013,” the earliest possible priority date for the patents-at-issue and the priority date alleged by Petitioner, respectively. Petitioner further contends that more education “would compensate for less work experience and vice versa.” Id. Petitioner. 537 PO Resp. 6−7; 538 PO Resp. 6−7. Accordingly, for purposes of this Decision, we adopt Petitioner’s description as our own. We adopt Petitioner’s level of ordinary skill in the art particularly because it specifies having one to three years of experience working with wireless devices that use Bluetooth and 802.11.” slip op. at 16
Patent outcomesUS 8,737,933 not shown unpatentable§ 102 anticipation§ 112 disclosurecites PhillipsPatents in suitUS 8,737,933 - Apple Inc. v. Carbyne Biometrics, LLCInstitution deniedPTAB · Aug 1, 2024 · IPR2024-00507 · APJ Jameson Lee · IPR · Institution
The Board denied institution because Apple did not show a reasonable likelihood of proving claims 2, 4–6, 12, 15, 21, 23–25, 31, and 34 obvious.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“review. See 35 U.S.C. § 314 (2018); 37 C.F.R. § 42.4(a) (2024). An inter partes review may not be instituted unless 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). Upon consideration of the contentions and the evidence of record before us, we conclude Petitioner has not shown a reasonable likelihood that it would prevail in establishing the unpatentability of at least one challenged claim of the ’105 patent. Accordingly, we decline to institute inter partes review.” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“The test for written description support is whether the application reasonably would have conveyed to one with ordinary skill in the art “the inventor possessed the invention at the time of that original disclosure.” Pandrol USA, LP v. Airboss Ry. Prods., Inc., 424 F.3d 1161, 1165 (Fed. Cir. 2005); see also Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (“the applicant must also convey with reasonable clarity to those skilled in the art that, as of the filing date sought, she or he was in possession of the invention”). The disclosure in the provisional application as cited by Patent Owner regarding policies is broad and does not convey with reasonable clarity what specifically are the policies, such as a policy for backup based on whether the first and second devices are of the same brand. The broad disclosure does not provide written description support for the narrow and specific limitation recited in independent claims 1, 18, and 25, i.e., “based at least in part on the first device being a same brand as a second device, initiating a backup, to the second device, of at least a portion of the at least one record.” Ex. 1001, 25:7–10, 26:30–32, 28:23–25.” slip op. at 14
- Skill levelSkill level petitioner adoptedDecided for petitioner
“ordinary skill in the art “would have had a bachelor’s degree in [] electrical engineering, computer engineering, computer science, or a related field, and at least two years of experience in the research, design, development, and/or testing of authentication techniques, and related firmware and software, or the equivalent, with additional education substituting for experience and vice versa.” Pet. 8 (citing Ex. 1003 ¶¶ 18–22). On this record, we adopt Petitioner’s statement of the level of ordinary skill in the art, except for the qualifier “at least” which applies to experience and which would improperly extend the scope of experience to the realm of an expert. It is supported by the testimony of Dr. McDaniel and not disputed by Patent Owner (Prelim. Resp. 11). Further, it appears consistent with what is reflected by the content of the applied prior art. Cf. Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill).” slip op. at 16
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not found
“and assuming that Cheng discloses backing up of data from a first user device to a second, new user device, without any user service bureau in between, Petitioner has not shown sufficient motivation to combine the teachings of Kodama with the teachings of Kesanupalli and Cheng to account for the remainder of limitation [1.8], i.e., initiate the backup “based at least in part on the first device being a same brand as a second device.” Ex. 1001, 25:7–10. Petitioner explains:” slip op. at 40
§ 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · GrahamPatents in suitUS 11,475,105 - Apple Inc. v. Carbyne Biometrics, LLCInstitution deniedPTAB · Aug 1, 2024 · IPR2024-00333 · APJ Jameson Lee · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that any challenged claim was obvious over the asserted prior-art combinations.
RulingsInstitution decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“The test for written description support is whether the application reasonably would have conveyed to one with ordinary skill in the art “the inventor possessed the invention at the time of that original disclosure.” Pandrol USA, LP v. Airboss Ry. Prods., Inc., 424 F.3d 1161, 1165 (Fed. Cir. 2005); see also Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (“the applicant must also convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention”). The disclosure in the provisional application as cited by Patent Owner regarding policies is broad and does not convey with reasonable clarity what specifically are the policies, such as a policy for backup based on whether the first and second devices are of the same brand. The broad disclosure does not indicate possession by the inventor the narrow and specific limitation recited in independent claims 1, 18, and 25, i.e., “based at least in part on the first device being a same brand as a second device, initiating a backup, to the second device, of at least a portion of the at least one record.” Ex. 1001, 25:7–10, 26:30–32, 28:23–25. Patent Owner states: “A determination ‘based on’ policies and the identity of the device would have conveyed to a POSITA that the backup could have been based on a policy including the device being of the same brand as the second device.” Prelim. Resp. 46 (emphasis in original). The assertion is misplaced because it refers to what “could have been” a policy, rather than what policy the provisional application disclosure conveys the inventor actually possessed. What potentially “could have been” is mere speculation, not written description indicating possession.” slip op. at 14
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Level of Ordinary Skill in the Art Citing testimony from Dr. McDaniel, Petitioner asserts a person of ordinary skill in the art “would have had a bachelor’s degree in [] electrical engineering, computer engineering, computer science, or a related field, and at least two years of experience in the research, design, development, and/or testing of authentication techniques, and related firmware and software, or the equivalent, with additional education substituting for experience and vice versa.” Pet. 8 (citing Ex. 1003 ¶¶ 18–22). 9 The record does not include any evidence of secondary considerations of nonobviousness. On this record, we adopt Petitioner’s statement of the level of ordinary skill in the art, except for the qualifier “at least” which applies to experience and which would improperly extend the scope of experience to the realm of an expert. It is supported by the testimony of Dr. McDaniel and not disputed by Patent Owner (Prelim. Resp. 12). Further, it appears consistent with what is reflected by the content of the applied prior art. Cf. Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill). C.” slip op. at 16
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“review. See 35 U.S.C. § 314 (2018); 37 C.F.R. § 42.4(a) (2024). An inter partes review may not be instituted unless 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). Upon consideration of the contentions and the evidence of record before us, we conclude Petitioner has not shown a reasonable likelihood that it would prevail in establishing the unpatentability of at least one challenged claim of the ’105 patent. Accordingly, we decline to institute inter partes review.” slip op. at 2
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“Petitioner asserts: Kodama recognizes “if data restoration is to be performed to a different product or a different manufacturer, the format and product proprietary information of data between the products will differ.” APPL-1010, [0157]. POSITA would recognize this differing format can create compatibility issues and thus would recognize an advantage of, and reason for, basing the initiation of data transfer to the second device on brand and thereby avoiding these compatibility issues as taught by Kodama. APPL- 1003, ¶190. Pet. 60. But the same brand requirement of Kodama is not provided to solve any problem with differing formats. Kodama states: At Step 1313 of the restoration processing, if data restoration is to be performed to a different product of a different manufacturer, the format and product proprietary information of data between the products will differ. Thus, before the restoration processing function of the online backup service system 0128 sends the data read at Step 1318 to the HDD recorder 0116, the data format is converted into the file format of the HDD recorder 0116 of the restoration destination. Ex. 1010 ¶ 157. Kodama does not describe format compatibility as presenting any problem. Requiring brand identity between the first device and the other devices of the user in Jakobsson ’351 to synchronize data among all of the user’s devices is also not an advantage. The devices of the user in Jakobsson ’351 are devices the user already owns, possesses, and uses. They are not a new device as in the case of Kodama, where a broken device may be expected to lead to the user acquiring a new device of the same brand as replacement. Petitioner provides no explanation as to why one would expect all of the user’s devices in Jakobsson ’351 would be of the same brand. Applying a same-brand requirement would substantially undermine and may even render inoperative Jakobsson ’351’s feature of synchronizing user data among all of the user’s devices. We do not see this result as either an advantage or an improvement.” slip op. at 51
§ 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · GrahamPatents in suitUS 11,475,105
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.