- 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 - 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 - PTAB · Nov 22, 2024 · PGR2024-00034 · APJ Patrick R Scanlon · PGR · Institution
Instituted PGR on claims 1–19 and all asserted grounds after finding at least one claim more likely than not unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We have authority to determine whether to institute a post-grant review. See 35 U.S.C. § 324 (2018); 37 C.F.R. § 42.4(a) (2022). To institute a post-grant review, we must determine that “the information presented in the petition . . . would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a). For the reasons set forth below, we determine that the information presented shows that it is more likely than not that Petitioner would prevail in establishing unpatentability of at least one challenged claim. Accordingly, we institute a post-grant review of the challenged claims on the grounds set forth in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“We note that the identification of a Ph.D. as an example of “more formal education” creates a vast range of education relative to a bachelor’s degree. Thus, we treat the identification of a Ph.D. just as it is—an example—and not a requirement. In this case, “more formal education” can be satisfied by a level of education less than a Ph.D (but greater than a bachelor’s degree). Based on our review of the record before us, we determine that Petitioner’s stated level of ordinary skill in the art is reasonable because it appears consistent with the evidence of record, definition, limited as discussed above, for the purposes of this Decision.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“On the present record, we do not discern a need to construe explicitly any claim language because doing so would have no effect on our analyses below of Petitioner’s asserted grounds and will not assist in resolving the present controversy between the parties. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundInstituted
“would have understood Unger’s disclosure to “suggest the use of a torsion spring to facilitate attachment and detachment, because torsion springs are designed to impart this functionality.” Id. (citing Ex. 1002 ¶ 118). Petitioner also asserts that one of ordinary skill in the art would have “understood that there were a limited number of ways to impart the referenced resilient or flexible ‘manipulation,’” and “would have been motivated to look to various known solutions to impart the suggested functionality, including the torsional spring mechanism of Smith that is used in a similar hearing protection device application for a similar purpose as Unger’s mounting arms (to apply a clamping force).” Id. at 32 (citing Ex. 1002 ¶¶ 120–121).” slip op. at 17
Claim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 11,736,855 - PTAB · Nov 14, 2024 · PGR2024-00026 · APJ Hyun J Jung · PGR · Institution
Instituted PGR on claims 1–7 and all grounds because Petitioner showed it was more likely than not that at least one challenged claim lacks written-description support.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“At this stage, Petitioner’s arguments, cited portions of the Specification, and supporting testimonial evidence demonstrate that it is more likely than not that claims 1–7 are unpatentable.” slip op. at 20
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateDecided for petitioner
“patent describes that “angular position transducer 78 is placed on top of swing leg pivot shaft 24” and that “pivot shaft 24 is rotationally fixed to the connector plate and duplicates the angular movements of swing leg 20 about the pivot shaft.” Ex. 1001, 12:15–16, 12:20–22, Figs. 5, 7. The ’723 patent also describes that “[a]ngular position transducer 78 is mounted inside . . . protective can 90 . . . which is bolted to hinge bracket 28 via an upright holding arm 92” and that “trigger pin 94 projects upwardly from the top surface of pivot shaft 24 and cooperates with angular position transducer 78 to generate an angular position signal.” Id. at 12:28–33, Fig. 5. These descriptions expressly convey that angular position transducer 78 is on pivot shaft 24 and mounted inside protective can 90 that is bolted to hinge bracket 28. Id. at 12:15–16, 12:20–22, 12:28–30, Figs. 5, 7; see also Prelim. Resp. 17 (describing the same embodiment shown in Figs. 5 and 7). According to Petitioner, the ’723 patent describes the pivot shaft as part of the hinge bracket, not the modular frame or swing leg. Pet. 109–110 (citing Ex. 1001, 7:42–46, 12:17–22). On the preliminary record, we agree because the cited portions of the Specification describe that a “hinge bracket is interposed between each swing leg and an associated surface of the bolsters and includes a fixed, upright pivot shaft that pivotally engages the swing leg for pivotal movements” and “pivot shaft 24 is rotationally fixed to the connector plate.” Ex. 1001, 7:42–45, 12:20–21. We also agree that “even if one were to find that the hinge bracket is part of either the modular frame or swing leg (contrary to the claims and specification treating these all as separate components), the specification would only provide written description for one of the claimed alternatives.” Pet. 110 (citing Ex. 1002 ¶ 199).” slip op. at 19
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“At this preliminary stage, we determine that express claim interpretation is not necessary to determine whether it is more likely than not that at least one of the claims challenged in the petition is unpatentable. 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 16
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner
“We will also not use our discretion under § 325(d) to deny the Petition based on arguments previously presented in IPR2021-00135, because Petitioner relies on a Board determination regarding claim 8 from IPR2021- 00136, not arguments previously made for claim 1 in IPR2021-00135. Pet. 111–115, 119; Prelim. Resp. 8–9; Prelim. Sur-reply 5. Furthermore, we determined the effective filing date of claim 8 of the ’571 patent without deciding, that other challenged claims, such as claim 1, were entitled to their earliest possible effective filing date. See Godberson-Smith, Paper 61 at 11, 12.” slip op. at 12
Claim construction§ 112 disclosureDiscretionary denialcites Phillips · KSR · GrahamPatents in suitUS 11,772,723 - Bj’S Wholesale Club Holdings, Inc. v. Walmart Apollo, LLCAll claims unpatentablePTAB · Apr 10, 2024 · IPR2022-01564 · APJ Patrick R Scanlon · IPR · Final written decision
Claims 1–14 are unpatentable as anticipated by Keith; the Board did not reach the alternative obviousness ground over Hanson and Keith.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“claims of the later-filed application must be supported by the written description in the parent ‘in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.’” Anascape, Ltd. v. Nintendo of Am. Inc., 601 F.3d 1333, 1335 (Fed. Cir. 2010) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997)). “[T]he hallmark of written description is disclosure,” and the test “is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date” of that application. Ariad Pharms., Inc. v. Eli Lilly and Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc) (citing Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1562–63 (Fed. Cir. 1991)). “[T]he test requires an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Id. But, “[i]t is not sufficient for purposes of the written description requirement of [35 U.S.C.] § 112 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, 107 F.3d at 1572.” slip op. at 33
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros. Inc., v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Moreover, “[b]ecause the hallmark of anticipation is prior invention, the prior art reference—in order to anticipate under 35 U.S.C. § 102—must not only disclose all elements of the claim within the four corners of the document, but must also disclose those elements ‘arranged as in the claim.’” Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008). Whether a reference anticipates is assessed from the perspective of an ordinarily skilled artisan. See Dayco Prods., Inc. v. Total Containment, Inc., 329 F.3d 1358, 1368 (Fed. Cir. 2003) (“‘[T]he dispositive question regarding anticipation [i]s whether one skilled in the art would reasonably understand or infer from the [prior art reference’s] teaching’ that every claim element was disclosed in that single reference.”). slip op. at 13
- BurdenFwd all claims unpatentableDecided for petitioner
“preponderance of the evidence that the claims are unpatentable. 35 U.S.C. § 316(e) (2018); 37 C.F.R. § 42.1(d) (2022). “In an IPR, the petitioner has the burden from the onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (2012) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015) (discussing the burden of proof in inter partes review).” slip op. at 12
Patent outcomesUS 10,803,435 unpatentable§ 102 anticipation§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,803,435 - Apple Inc. v. Rfcyber Corp.All claims unpatentablePTAB · Jan 19, 2024 · IPR2022-01256 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–11 are unpatentable as obvious over Buhot, GPC, and Zhu.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“earlier applications, in particular Application No. 11/534,653 (“the ’653 application”), which issued as U.S. Patent No. 8,118,218 B2 (“the ’218 patent”). “‘It is elementary patent law that a patent application is entitled to the benefit of the filing date of an earlier filed application only if the disclosure of the earlier application provides support for the claims of the later application, as required by 35 U.S.C. § 112.’” PowerOasis, Inc. v. T- Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008). The test for determining compliance with the written description requirement under § 112(a) is whether the original disclosure of the earlier-filed application reasonably would have conveyed to one with ordinary skill in the art that the inventor had possession of the claimed subject matter at the time of the earlier-filed application. Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). It is well settled that “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571−72 (Fed. Cir. 1997). “It is not sufficient for purposes of the written description requirement of § 112 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.” Id. We agree with Petitioner there does not appear to be support for limitation [1(j)] in the ’653 application. We find that the disclosure of the ’653 application—limited to general teachings of a smart card, an operating system, and a smart card manager—is insufficient to show possession of limitation [1(j)]. See Ex. 2001 (’218 patent), 4:47–56. As we explained above, “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood, 107 F.3d at 1571−72. The ’653 Application contains no disclosure of replacing applications, even if the disclosure might render such replacing obvious, it is not sufficient to show the possession required to establish entitlement to a priority date. Accordingly, we agree with Petitioner that the challenged claims of the ’724 patent are entitled to a priority date no earlier than March 4, 2012.” slip op. at 7
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Relying on the declaration testimony of Mr. Smith, Petitioner contends that an ordinarily skilled artisan for the ’724 patent “would have had at least a bachelor’s degree in computer engineering, computer science, electrical engineering, or a related field, with at least one year of experience in the field of mobile payment technology. Additional pertinent education might substitute for the requisite experience and vice versa.” Pet. 6–7 (citing Ex. 1007 (Smith Decl.) ¶¶ 34–35). Patent Owner states that “[t]he parties agree on the level of skill in the art.” PO Resp. 11. Accordingly, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’724 patent and the asserted prior art, and we apply it in our obviousness evaluations below. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art, itself, can reflect appropriate level of ordinary skill in art).” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner contends that it applies “the plain and ordinary meaning as understood by a [person of ordinary skill in the art] for all terms not expressly construed below,” and indicates that in parallel District Court litigation, the parties agreed to claim construction for the term “emulator device” to mean “hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.” Pet. 8. Petitioner proposes that the term “application” should be construed to mean “‘software program suitable for being executed on a portable device,’” but that the “distinction between the parties’ respective proposals need not be resolved for this proceeding.” Id. at 8–9. Petitioner finally contends that the phrase “a portion of or in entirety” in each independent claim means “in its entirety or partially,” but not both. Id. at 9. Patent Owner submits that “[t]he parties agree that the Board should construe ‘emulator device’ as ‘hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.’” PO Resp. 11. Patent Owner “does not believe that any other terms require construction to resolve the issues presented in this proceeding.” Id. We apply the agreed upon constructions above, but otherwise find that no express constructions are necessary for this decision.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“We agree with Petitioner that, even if the applications were stored in “generic memory” as Patent Owner contends, Zhu provides adequate security and would not undermine Petitioner’s motivation to combine. See Intel, 61 F.4th at 1380 (“It’s not necessary to show that a combination is the best option, only that it be a suitable option.”). Indeed, Zhu addresses the problem Patent Owner contends it would cause in the combination.3 As Zhu 3 Patent Owner argues that Petitioner should be precluded from discussing Zhu’s encryption embodiment because it was not raised in the Petition. See Sur-Reply 6–7. We disagree. The claims do not recite anything about how the data should be stored. Thus, it is not surprising that the Petition did not address it. Patent Owner raised the teaching away argument regarding the security of the data. See PO Resp. 12–16. Petitioner relies on the exact same mapping, same motivation, and same arguments why Zhu accounted for certain limitations. See Reply 4–11. Petitioner’s Reply merely explained that Zhu did address the problem Patent Owner contended would “teach away” from the combination. Indeed, Patent Owner was aware of Zhu’s teachings and addressed them in their Patent Owner Response. The Federal recognizes, “[l]oading one of the smart card applications already resident on the smart card to another memory location on the mobile device can provide sufficient memory for the selected smart card application, but can also create a security problem.” Ex. 1006 (Zhu), 3:25–34. To address this problem, Zhu proposes encrypting these applications in generic memory which “reduces the possibility of unauthorized access to the information.” Id. at 3:59–61, 8:30–55, 9:28–33; Ex. 1033 (Smith Supp. Decl.) ¶¶ 5–6. Although acknowledging this disclosure, Patent Owner’s expert, Dr. Weaver, testifies that Zhu’s encryption is inadequate and that encryption would have certain drawbacks. See Ex. 2002 (Weaver Decl.) ¶ 69. We find this testimony, which directly contradicts the teachings of Zhu that encryption is an adequate solution, lacks sufficient support to be entitled to much weight. Dr. Weaver provides no citations to support his contention that a person of ordinary skill at the time of the invention would find encryption so inadequate or problematic as he now contends. Moreover, we find that Dr. Weaver’s testimony on cross examination provides an additional, independent basis to give this testimony little weight. On cross examination, Dr. Weaver contended that there was nothing uniquely inadequate about the particular encryption scheme disclosed in Zhu, but rather that his “opinion was more general, that encryption schemes known in the 2012 time frame were all breakable with computing power and time,” and thus, inadequate Circuit has explained that “the petitioner in an inter partes review proceeding may introduce new evidence after the petition stage if the evidence is a legitimate reply to evidence introduced by the patent owner.” Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018). That is the case here, so we find that Petitioner’s arguments and evidence regarding Zhu’s encryption are proper. for storing payment applications in a mobile device’s general memory. Ex. 1027 (Weaver Tr.), 26:11–23; see also id. at 23:3–8 (“[D]oes encryption ever provide a sufficiently high security to permit storing payment application on a mobile device’s general memory? A. No”); 24:15–25:23 (testifying all publicly known encryption schemes in 2012 were breakable). However, when confronted with the fact that the ’724 patent discloses storing payment application on general baseband memory using an encryption method that was breakable, id. at 26:24–29:7, Dr. Weaver testified that this encryption method was sufficient to allow storing payment applications in general baseband memory even though it was “not perfectly secure,” id. at 29:8–14. Dr. Weaver provides no explanation or rationale why the encryption method in the ’724 patent, which he admits suffers from the same drawbacks he identified with respect to Zhu, is sufficient, but other encryption methods would not be sufficient. In its Sur-reply, Patent Owner attempts to rehabilitate Dr. Weaver’s testimony with justifications and qualifications not found in his original testimony. Sur-Reply 7–8. Yet, Dr. Weaver’s testimony discussed above was clear and unequivocal. See Ex. 1027 (Weaver Tr.), 24:15–29:14. Patent Owner made no effort to redirect his testimony at his deposition, so it cannot now do so through mere attorney argument. We find the inconsistency between Dr. Weaver’s treatment of Zhu and his treatment of similar disclosure in the ’724 patent exposes the insufficient reasoning supporting his opinions regarding the adequacy of Zhu’s use of encryption in the combination. Accordingly, we give no weight to his testimony that a skilled artisan would not have combined Zhu with a Buhot/GPC system due to security concerns. In contrast, we find the testimony of Mr. Smith regarding the use of encryption and the tradeoffs with the benefits of adopting Zhu’s memory management technique, which he offers in his Supplemental Declaration, to be well-reasoned, consistent with the disclosure of Zhu and the ’724 patent4, and entitled to substantial weight. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. As Petitioner recognizes, “‘[a] given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.’” Allied Erecting & Dismantling Co. v. Genesis Attachments, LLC, 825 F.3d 1373, 1381 (Fed. Cir. 2016). As Mr. Smith and Dr. Weaver testified, decryption without access to the security keys is an extremely computationally intensive and time-consuming process. Ex. 1033 (Smith Supp. Decl.) ¶¶ 6–8; Ex. 1027 (Weaver Tr.), 23:17–25:2; see also Ex. 10175, 132. Mr. Smith testifies that the benefits of using encryption would be sufficient to resolve the security concerns Patent Owner raises, and that any burden of generating a certificate would be outweighed by the benefits of using encryption and the memory advantages Zhu’s technique would offer. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. Accordingly, we find that Patent Owner’s security concerns would be” slip op. at 25
Patent outcomesUS 11,018,724 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 11,018,724 - Vivint, Inc. v. SB IP Holdings LLCAll claims unpatentablePTAB · Oct 19, 2023 · IPR2022-00810 · APJ Karl D Easthom · IPR · Final written decision
Claims 1–10 and 13–21 are unpatentable: Vaios anticipates some claims, and the listed Vaios, Klein, and Naidoo-068 combinations render the remaining claims obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Pet. 8 (citing Ex. 1002 ¶¶ 21–24). Patent Owner responds that “Petitioner and its expert rely on conclusory statements regarding a person of ordinary skill in the art” such that Dr. “Hochwald’s conclusory opinion should be given no weight.” PO Resp. 4–5 (citing Ex. 1002 ¶¶ 21–24). Notwithstanding Patent Owner’s arguments, Dr. Hochwald declares that “[a]ll of the opinions contained in this declaration are based on the documents I have reviewed and my professional judgment, as well as my education, experience, and professional knowledge.” Ex. 1002 ¶ 17. Such documents include the “’098 patent (EX1001), the prosecution history of the ’098 patent (EX1017), the prior art references cited herein, and other Hochwald bases his proposed level of ordinary skill on the relevant documents. Moreover, Patent Owner does not offer a proposed level of ordinary skill in the art or even argue that a different level would result in a different analysis by Dr. Hochwald or any other declarant. See id. Based on a review of the record, we adopt Petitioner’s proposed level of ordinary skill in the art because it is consistent with the evidence of record, including the asserted prior art and ’098 patent specification. See 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 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notNot reached
“Phillips. See Pet. 7–8. The parties disagree over whether the preamble is limiting. Compare PO Resp. 2–3 (arguing the preamble is limiting), with Reply 2–3 (arguing that “‘for receiving a person at an entrance’ clearly states an intended purpose of the invention”). As the analysis of the grounds art renders the claims unpatentable.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“In any event, even if we generally adopt what Patent Owner refers to as an agreed upon plain and ordinary meaning and construe “detecting a person at the entrance” as limited to “detecting a person at an exterior,” and further construe “exterior” as referring to the exterior of an area defined by some type of a “demarcation line” according to the ’098 patent’s description of Figure 1 (see Ex. 1001, 6:40–50), the Petitioner persuasively shows that the prior art teaches the limitation (including when the “demarcation line” defines the exterior of a building), as discussed further below. Accordingly, it is not necessary to explicitly construe the limitation any further or to construe any other claim terms, because any construction would not impact the analysis of Petitioner’s asserted grounds. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (stating that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 11
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner
“shows that the ’384 provisional does not contemplate transmitting “video of the person at the entrance” to a “remote peripheral device by which a user of the remote peripheral device may view the video of the person at the entrance,” using “a graphic user interface,” as claim step 1c requires. Disclosure in the ’384 provisional of a generic laptop or other remote peripheral device that may be capable of viewing video in isolation is not possession of the claimed invention. In other words, as Petitioner persuasively shows, “[c]ommunication of actual video to the remote peripheral device was not countenanced in the provisional, and [Patent Owner] fails to identify evidence to the contrary.” Id. at 9. That is, as Petitioner also argues, “[w]ritten description support is not established simply by identifying peripheral devices such as PDAs and laptop[s] in the provisional and arguing that such devices were ‘capable of’ displaying video, nor by the provisional’s disclosure of ‘communications’ between the central computer and said peripheral devices.” Id. at 8–9 (citing Tech. Licensing Corp. v. Videotek, Inc., 545 F.3d 1316, 1331–32 (Fed. Cir. 2008)). Under the rationale and holding of Tech. Licensing Corp., even if “a person skilled in the art might conclude” that the ’384 provisional’s disclosed system is capable of performing the same function of viewing the particular video at a remote peripheral device, this is not enough to show adequate written description. See id. at 1334 (“This evidence persuaded the trial court that a person skilled in the art might conclude that R21 and R26 establishing a level shifted signal [as recited in the ’250 patent claims at issue], but that was all,” and that evidence is insufficient to satisfy written description for a level shifted signal), 1333–34 (“The pertinent question is not whether a person skilled in the art could look at both Figure 3 [from the earlier-filed ’323 application] and Figure 16 [from the ’250 patent at issue] and determine that the resistors in the former perform a similar function to the resistors in the latter. Rather, the issue is whether a person skilled in the art would understand from the earlier application alone, without consulting the new matter in the ’250 patent, that the inventor had possession of the claimed ‘other circuit’ in 1992 when the ′323 application was filed.”). Even if there is a disclosure in the ’384 provisional of a system that merely is capable of providing for the viewing of live streaming or recorded video at the remote peripheral device of “the person at the entrance,” this still is not sufficient written description for claim 1, step 1c. Rather, claim 1 requires “a graphic user interface” (which facilitates and controls the viewing) at “the remote peripheral device,” because it requires “providing a [GUI] to a remote peripheral device by which a user of the remote peripheral device may view the video of the person at the entrance.”14 There is no disclosure in the ’384 provisional for providing a GUI to a remote peripheral device. See Inst. Dec. 9 (indicating a lack of showing as to the claimed” slip op. at 19
Patent outcomesUS 8,139,098 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 8,139,098
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.