- 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 - Phison Electronics Corporation v. Vervain, LLCInstitution deniedPTAB · Apr 28, 2025 · PGR2024-00048 · APJ Stacey G White · PGR · Institution
The Board denied institution because Petitioner did not show it was more likely than not that claims 1–6 were unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“review under 35 U.S.C. § 324 and 37 C.F.R. § 42.4(a). We may not institute a post-grant review unless “the information presented in the petition . . . , if such information is not rebutted, 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) (2024). Upon considering the evidence and arguments presented, we determine, as discussed below, that Petitioner has not demonstrated that it is more likely than not that at least 1 of the claims challenged in the Petition is unpatentable. Therefore, we deny1 Petitioner’s request to institute post-grant review of claims 1–6.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner’s declarant, Dr. Khatri, proposes a definition of the person of ordinary skill in the art. Ex. 2001 ¶ 24. Dr. Khatri, however, notes that his opinions would be the same under either his proposal or Petitioner’s proposal. Id. ¶¶ 25–26. Patent Owner states that, for purposes of the Preliminary Response, it “adopts Petitioner’s definition of a person of ordinary skill in the art.” Prelim. Resp. 13 (citing Pet. 22–23; Ex. 2001 ¶¶ 22–26). We determine that the current record supports Petitioner’s description of an ordinarily skilled artisan. For purposes of this Decision, therefore, we adopt Petitioner’s description of an ordinarily skilled artisan. We also note that the applied prior art reflects the appropriate level of skill at the time of the claimed invention. See Okajima, 261 F.3d at 1355.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner proposes constructions for the claim terms “MLC memory modules” and “SLC memory module.” Pet. 23–28. Patent Owner disagrees with Petitioner’s constructions, but does not contest them because it argues that construction of these terms is not necessary to resolve the parties’ disputes. Prelim. Resp. 14. Based on the record presented, we determine that no claim term requires an explicit construction to decide whether Petitioner satisfies the “more likely than not” standard for instituting a post- grant review. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017).” slip op. at 13
- Disclosure Requirements (§112) › Written description (Ariad)Written description adequateNot shown unpatentable
“using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same.” The Federal Circuit has held that “[t]he written description requirement is met when the disclosure relied on for support ‘reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date.’” RAI Strategic Holdings, Inc. v. Philip Morris Prods. S.A., 92 F.4th 1085, 1088 (Fed. Cir. 2024) (quoting Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc) (citation omitted)). The written description inquiry is a question of fact, is context specific, and must be determined on a case-by-case basis. Ariad, 598 F.3d at 1351 (citing Ralston Purina Co. v. Far-Mar-Co, Inc., 772 F.2d 1570, 1575 (Fed. Cir. 1985); Capon v. Eshhar, 418 F.3d 1349, 1357–58 (Fed. Cir. 2005)). “[T]he level of detail required to satisfy the written description requirement varies depending on the nature and scope of the claims and on the complexity and predictability of the relevant technology.” Id. (citing Capon, 418 F.3d at 1357–58). Factors used to evaluate the sufficiency of a disclosure include: 1) “the existing knowledge in the particular field”; 2) “the extent and content of the prior art”; 3) “the maturity of the science or technology”; and 4) “the predictability of the aspect at issue.” Id. (citing Capon, 418 F.3d at 1359). As support for the term “memory space,” the ’612 patent explains that because “the SLC NAND flash is used to boost the lifetime (endurance) of the storage system, it can be considerably lesser in amount than the MLC NAND flash.” Ex. 1001, 5:20–23; see Ex. 2001 ¶ 51. As an example, the ’612 specification states that “a system may set SLC NAND flash equal to 12.5% or 25% of MLC NAND flash (total non-volatile memory storage space=MLC+SLC).” Ex. 1001, 5:23–25; see Ex. 2001 ¶¶ 51, 62. In addition, we find persuasive Dr. Khatri’s testimony that one of ordinary skill in the art would have understood that “there are two spaces—MLC and SLC—where data is stored, and the total memory space is the combination of the two.” Ex. 2001 ¶ 51. Further, the ’612 patent’s Figure 1 depicts “memory space,” e.g., dynamic random-access memory (DRAM) 20, one or more disks 24, MLC NAND flash memory module 26, and SLC NAND flash memory module 28. Ex. 1001, 5:37–45, Fig. 1; see Ex. 2001 ¶ 64. The ’612 patent’s Figure 4 also depicts “memory space,” e.g., NAND flash memory bank 56 comprising “a plurality of MLC NAND flash memory modules 60a and a plurality of SLC NAND flash memory modules 62a” and NAND flash memory bank 58 comprising “a plurality of MLC NAND flash memory modules 60b and a plurality of SLC NAND flash memory modules 62b.” Ex. 1001, 7:8–14, Fig. 4; see Ex. 2001 ¶ 64. On the record before us, we find the above noted disclosures to be sufficient to support the disputed claim language. For these reasons, the ’612 patent’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.” See Ariad, 598 F.3d at 1351.” slip op. at 15
Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · NautilusPatents in suitUS 11,854,612 - Phison Electronics Corporation v. Vervain, LLCInstitution deniedPTAB · Mar 17, 2025 · PGR2024-00047 · APJ Steven M Amundson · PGR · Institution
The Board denied institution because Petitioner did not show it was more likely than not that any of claims 1–7 was unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“to institute a post-grant review. We may not institute a post-grant review unless we determine that “the information presented in the petition filed under section 321, if such information is not rebutted, 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) (2024).” slip op. at 2
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Not shown unpatentable
“2. PETITIONER’S CONTENTIONS Petitioner challenges the ’546 patent’s claims as encompassing a” slip op. at 20
- Disclosure Requirements (§112) › Written description (Ariad)Not shown unpatentable
“2. PETITIONER’S CONTENTIONS Petitioner challenges the ’546 patent’s claims as failing to satisfy” slip op. at 26
- Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not shown unpatentable
“2. PETITIONER’S CONTENTIONS Petitioner challenges the ’546 patent’s claims as failing to satisfy” slip op. at 36
§ 101 eligibility§ 103 obviousness§ 112 disclosureDiscretionary denialcites Alice · Mayo · Phillips · KSR · Graham · NautilusPatents in suitUS 11,830,546 - Unified Patents, LLC v. Ideahub Inc.All claims unpatentablePTAB · Feb 5, 2024 · PGR2022-00044 · APJ Monica S Ullagaddi · PGR · Final written decision
Claims 1–13 are unpatentable for lack of written description under § 112(a); the Board did not reach the anticipation and obviousness grounds based on HEVC265.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner contends that: A person of ordinary skill in the art at the priority date for the ’274 Patent (“POSITA”) would have had a bachelor’s degree in electrical or computer engineering, or a closely related scientific field such as physics or computer science, and two years of work experience with video processing. A lack of experience can be remedied with additional education (e.g., a Master’s degree), and likewise, a lack of education can be remedied with additional work experience (e.g., 4–5 years). This definition would apply at the earliest claimed priority date of the ’274 Patent as well as any later date. Pet. 12 (citing Ex. 1005 ¶¶ 50–52). Patent Owner does not dispute the level of ordinary skill in the art. See generally PO Resp. We adopt Petitioner’s definition as it appears to be consistent with the Specification of the ’274 patent and the cited reference.” slip op. at 14
- PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner
“A party is collaterally estopped from relitigating an issue if: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the prior action featured full representation of the estopped party. VirnetX Inc. v. Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)).” slip op. at 21
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner
“For the reasons that follow, we determine that the ’928 application does not provide sufficient written description support, for at least independent claim 1 of the ’274 patent, so as to “reasonably convey[] to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date” of the ’928 application. Ariad, 598 F.3d at 1351. Accordingly, we are persuaded that the ’928 application lacks sufficient written description support for the invention recited in claim 1 of the ’274 patent, and thus, claim 1 does not receive an effective filing date as early as that of the ’928 application (i.e., December 23, 2010). We further determine that Petitioner filed the Petition within the 9-month statutory period for requesting post-grant review in accordance with 35 U.S.C. § 321(c). The ’274 patent issued on September 14, 2021 (see Ex. 1001, code (45)), and the present Petition was accorded a filing date of June 9, 2022 (see Paper 5). Accordingly, the Petition was filed less than 9 months after the date of issuance of the ’274 patent. In view of the above, we are persuaded that the ’274 patent is eligible for post-grant review.” slip op. at 16
Patent outcomesUS 11,122,274 unpatentable§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 11,122,274 - Unified Patents, LLC v. Ideahub Inc.InstitutedPTAB · Feb 6, 2023 · PGR2022-00044 · APJ Monica S Ullagaddi · PGR · Institution
The Board instituted post-grant review of claims 1–13 on all grounds, finding it more likely than not that at least claim 1 lacks written-description support.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. 35 U.S.C. § 324(c); 37 C.F.R. § 42.4(a) (2021). Under 35 U.S.C. § 324(a), a post-grant review may not be instituted “unless . . . the information presented in the petition . . . , if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” After considering the Petition, Patent Owner’s Preliminary Response, Petitioner’s Preliminary Reply, Patent Owner’s Preliminary Sur-reply, as well as all supporting evidence, we determine that Petitioner satisfies its burden under 35 U.S.C. § 324(a) to show that it is more likely than not that at least one of the challenged claims of the ’274 patent is unpatentable. Therefore, we authorize a post-grant review to be instituted as to all grounds and all challenged claims. 37 C.F.R. § 42.208(a) (“When instituting post-grant 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.”).” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther
“Id. at 7:24–8:4 (emphasis added). The ’928 application repeatedly makes clear that directionality and intra mode are related, but distinct concepts. They are not interchangeable as Patent Owner argues. On this point, we find Dr. Freedman’s explanation in paragraph 85 of his Declaration on the relationship between “intra mode” and “directionality” to be particularly well-reasoned and persuasive. As Dr. Freedman explains, [t]hroughout the ’928 application, the text uses the term “directionality” to refer to characteristics of neighboring blocks, whereas the term “intra mode” is used when referring to the current block. For example, the ’928 application describes that “directionality” of neighboring blocks is “estimated from the neighboring blocks” that “have already been reconstructed” while the “intra mode” is selected for the current block for purposes of reconstructing that current block. This is likely because the neighboring blocks “have already been reconstructed” and thus, the intra mode number that was used in reconstructing those blocks is no longer pertinent. Instead, what is pertinent in the ’928 application’s method is the directionality characteristic of those neighboring blocks. Phrased differently, in the ’928 application, directionality is a concept that is evaluated after performance of intra prediction (i.e., after reconstruction), whereas the intra mode or number is a concept used during performance of intra prediction. They are not equivalent in the context of the ’928 application. Ex. 1005 ¶ 86 (citing Ex. 1028, 11:14–12:4, 25:10–15; Ex. 1036, 706 (“The DCT coefficients gathered from the MPEG 2 process are used to estimate the directional features in a picture. The estimated directional features are then used to compute the intra prediction modes in the H.264 encoding stage.”)).8 Thus, we are persuaded by Dr. Freedman’s testimony, supported by Kalva, that these terms are not synonymous, as is Patent Owner’s and its expert’s position.” slip op. at 31
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityNot reached
“Patent Owner argues that HEVC265 is not prior art because it was published in 2013. Prelim. Resp. 24. Insofar as we determine that the ’928 application does not provide sufficient written description support for at least claim 1, and insofar as no other patent or application in the priority chain of the ’274 patent was filed before 2013 (see Pet. 19), Patent Owner’s argument is unavailing as to this claim. As we preliminarily conclude that Petitioner demonstrates that it is more likely than not to prevail on its challenge to independent claim 1 based on lack of written description support, we institute review on all challenged claims on all grounds set forth in the Petition, including Petitioner’s anticipation and obviousness challenges to claims 1–4 and 6 applying HEVC265. See SAS, 138 S. Ct. at 1354; PGS, 891 F.3d at 1360.” slip op. at 38
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not reached
“F. Anticipation and Obviousness Challenges Based on HEVC265 Petitioner contends that claims 1–4 and 6 are anticipated by, or alternatively, rendered obvious in view of HEVC265. Pet. 49–52. Patent Owner argues that HEVC265 is not prior art because it was published in 2013. Prelim. Resp. 24. Insofar as we determine that the ’928 application does not provide sufficient written description support for at least claim 1, and insofar as no other patent or application in the priority chain of the ’274 patent was filed before 2013 (see Pet. 19), Patent Owner’s argument is unavailing as to this claim. As we preliminarily conclude that Petitioner demonstrates that it is more likely than not to prevail on its challenge to independent claim 1 based on lack of written description support, we institute review on all challenged claims on all grounds set forth in the Petition, including Petitioner’s anticipation and obviousness challenges to claims 1–4 and 6 applying HEVC265. See SAS, 138 S. Ct. at 1354; PGS, 891 F.3d at 1360.” slip op. at 38
Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 11,122,274 - Kiosoft Technologies, LLC / Techtrex, Inc. v. Payrange Inc.Some claims unpatentablePTAB · Dec 14, 2022 · PGR2021-00093 · APJ Ken B Barrett · PGR · Final written decision
Claims 1–6, 8–10, 14, 15, and 18–25 are unpatentable under § 101; claims 7, 11–13, 16, and 17 were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. The Level of Ordinary Skill in the Art In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (internal quotation marks and citation omitted). Petitioner contends: A [person of ordinary skill in the art (“POSITA” or “POSA”)] at the time of the earliest claimed filing date of the ’614 Patent would have had an education background of, or practical experience providing an equivalent to, a Bachelor of Science in Electrical Engineering, Computer Science, Information Technology, or a related/equivalent field and at least 3 years of academic or industry experience in electronic payment systems. Pet. 16 (citing Ex. 1003 ¶¶ 5–6). Patent Owner affirmatively states that it does not dispute Petitioner’s asserted educational background of a person of ordinary skill in the art. PO Resp. 7. Patent Owner does not dispute Petitioner’s proposed number of years of experience, instead contending that “the claims are patentable regardless of the number of years of work experience a POSA would have had.” Id. (citing Ex. 2019 ¶¶ 49–58). Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). We adopt Petitioner’s definition of the person of ordinary skill in the art.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“construction disputes to find that Petitioners have failed to satisfy their burden of proof.” PO Resp. 8. Patent Owner goes on to state its agreement with Petitioner’s proposed construction for the “identifying” limitation (id. at 9) and indicate its disagreement with certain of Petitioner’s proposals (id. at 9–14). Patent Owner confirmed at the oral argument that no claim term needs to be construed to reach a dispositive issue. Tr. 33:23–34:5. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes.” slip op. at 11
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner
“All of the claimed method steps of claim 1 occur “at the mobile device” (element 1.1), and the method includes a step of enabling user interaction with the user interface to complete the vending transaction (element 1.9). Id. at 46:61–65, 47:24–28. Claim 1 does not recite completing the purchase. The ’614 patent describes a commercial transaction completed at the payment accepting unit (i.e. the vending machine), not at the mobile device. Ex. 1001, 7:15–19; see also id. at 16:46–50; 17:57–59; 19:17–20; 19:35–38. We, thus, agree with Patent Owner that the claimed method does not require completing or conducting the transaction, but only enabling the completion of the transaction. On this complete record, we are persuaded that the elements block quoted above recite the concept of identifying a merchant and enabling completion of a purchase from the merchant. See Pet. 20 (arguing that the claimed method “is no less abstract than a customer noticing a store, making a purchase, and receiving a receipt.”); Pet. Reply 5 (arguing that the claim describes “nothing more than a customer noticing and identifying a store amongst multiple stores based on the unique visual image of that store, entering the store and communicating with the merchant, making a purchase, and receiving a receipt—all while using conventional tools.”). In particular, claim 1 recites a step for identifying a merchant based on its advertised presence—identifying a nearby vending machine that is available to accept payment from a mobile payment application, with that identifying involving the broadcasting of predefined radio messages.8 Claim 1 also recites steps for enabling completion of a purchase from the merchant— establishing a communication connection between the user’s device and the vending machine; displaying an interface that allows a user to select a vending machine, to trigger payment for the vending transaction, and to enable the completion of the transaction; and updating the user interface after receiving information from the vending machine regarding the transaction (which, as indicated by dependent claim 3, may be information indicating that the vending transaction was completed). Our slight revision of the abstract idea from what we previously stated in our Institution Decision does not impact the patentability analysis. Apple, Inc. v. Ameranth, Inc., 842 F.3d 1229, 1241 (Fed. Cir. 2016).” slip op. at 17
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptMixed
“As discussed above, the Specification indicates that the short-range communication between the vending machine and mobile device can be not only conventional technologies such as Bluetooth, near-field communication (NFC), and radio frequency identification (RFID), but also could be “any wired or wireless technology that could be used to communicate a small distance (approximately a hundred feet or closer) that is known.” Ex. 1001, 9:57–67. The Specification ties that technology to the “broadcast” in claim 1 (id. at 47:2–5). For example, the Specification explains that “[e]ach adapter module 100 [of the vending machine] advertises its presence by broadcasting signals (advertising broadcast signals) to mobile devices in the zones 102, 104, 106.” Id. at 10:43–45. “The outermost range is the Bluetooth range 106 . . . [and] is the area in which the adapter module 100 is able to broadcast its presence.” Id. at 18:29–33. Further, Dr. Shamos testified that the Bluetooth protocol requires that two devices wishing to interact with each other identify themselves to each other. Ex. 1030, 102:3– 24. Dr. Shamos also testified that the Low prior art reference discloses that a vending machine identifies itself to the user. Id. at 100:9–20; see Ex. 1007, 2:25–28 (Low stating that, “in some embodiments, multiple machines may send their unique identifiers, such that the user is able to select one or more machines to purchase from.”). Thus, the abstract idea of identifying a merchant is implemented by nothing more than well-known, routine, and conventional wireless communications.” slip op. at 39
Patent outcomesUS 10,891,614 mixedClaim construction§ 101 eligibility§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Mayo · Bilski · Phillips · KSR · Graham · NautilusPatents in suitUS 10,891,614
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.