- 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 - Shenzhen Tuozhu Technology Co. Ltd. v. Stratasys, Inc.Institution deniedPTAB · Oct 6, 2025 · IPR2025-00585 · APJ Lilan Ren · IPR · Institution
The Board denied institution on claims 1–6, 10–19 because claim 1’s scope is ambiguous and the petition did not show a reasonable likelihood of prevailing on any asserted obviousness ground.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“review. See 35 U.S.C. § 314 (2024); 37 C.F.R. § 42.4(a) (2024). Institution of an inter partes review requires that “the information presented in the petition . . . and any response . . . 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). For the reasons set forth below, we determine that the scope of claim 1 is ambiguous and that there is not a reasonable likelihood that Petitioner will prevail with respect to at least one challenged claim, and we deny inter partes review.1” slip op. at 2
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“distinguishes and contrasts build material property from operational parameters. The diagnostic test passage therefore only describes a diagnostic test of the build material property but does not describe a subsequent diagnostic test to assess whether an operational parameter is suitable for the printer. Based solely on the diagnostic test passage and the prosecution history, a possible interpretation may be that the operational parameter determination in claim element 1b encompasses the diagnostic testing in claim element 1c. That is, “performing a diagnostic test to determine whether the operational parameter is suitable for the three-dimensional printer” in claim element 1c is subsumed as part of “determining an operational parameter of a fabrication process using the three-dimensional printer based upon the data, the operational parameter including at least one of a build platform temperature, a build volume temperature, an infill requirement, a rafting requirement, a support structure requirement, and a cooling requirement” in claim element 1b.” slip op. at 15
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther
“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); see also Research Corps. Techs. v. Microsoft Corp., 627 F.3d 859, 871–72 (Fed. Cir. 2010) (holding that claims of the later-filed application, which were not limited to a “blue noise mask,” were “not entitled to claim the benefit of their parent applications’ filing dates”); ICU Med., Inc. v. Alaris Med. Sys., 558 F.3d 1368, 1377–78 (Fed. Cir. 2009) (holding that “spikeless” claims “added years later during prosecution” were not supported by the specification which “describe[d] only medical valves with spikes”); Tronzo v. Biomet, Inc., 156 F.3d 1154, 1158–60 (Fed. Cir. 1998) (holding the generic shaped cup claims of the later-filed child application were not entitled to the filing date of the parent application that “disclosed only a trapezoidal cup and nothing more”). “To satisfy the written description requirement the disclosure of the prior application must convey with reasonable clarity to those skilled in the art that, as of the filing date sought, [the inventor] was in possession of the invention.” PowerOasis, 522 F.3d at 1306 (emphasis omitted; alteration in original). The sufficiency of written description support is based on “an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc).” slip op. at 20
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art in the field in the relevant time frame would have had “(1) at least a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a related field, and (2) at least two years of research or industry experience in 3D printing or materials used for 3D printing.” Pet. 5 (citing Ex. 1003 ¶ 20). Petitioner also contends that “[a]dditional experience could substitute for a formal degree or formal training (and vice versa).” Id. (citing the same). Patent Owner contends that an ordinarily skilled artisan “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Electrical Engineering, Chemical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” Prelim. Resp. 12. For purposes of this decision, we adopt Petitioner’s definition of the level of ordinary skill in the art as it appears unopposed and consistent with the disclosures of the ’464 patent and the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 9
Claim construction§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 11,167,464 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentablePTAB · Aug 4, 2025 · IPR2024-00509 · APJ Michael J Strauss · IPR · Final written decision
Claims 1–4 and 6–19 are unpatentable as obvious over Throughtek-2012 and the Lorex Video; claims 1–3, 6, 10, 12–14, 17, and 18 are also unpatentable under two other grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Dr. Bims, Petitioner proposes that a person of ordinary skill in the art at the time of the ’842 patent would have been a person having a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies. Pet. 11 (citing Ex. 1001 ¶¶ 15–16). Patent Owner does not provide any proposed qualifications for a person 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) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt the assessment offered by Petitioner as it is consistent with the ’842 patent and the asserted prior art.” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner asserts “no claim elements need a formal construction for purposes of resolving the controversy in this proceeding.” Pet. 11 (citing Ex. 1001 ¶ 55; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011); Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. §42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e 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 8
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner
“In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20
Patent outcomesUS RE47,842 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham - AT&T Mobility LLC / AT&T Services Inc. et al. v. Daingean Technologies Ltd.No claims unpatentablePTAB · Jul 14, 2025 · IPR2024-00402 · APJ Mary C Hoffman · IPR · Final written decision
The Board granted Patent Owner’s revised non-contingent motion to amend, canceling claims 1–4 and substituting claims 7 and 8, which Petitioner did not prove unpatentable.
RulingsFinal written decision- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted
“whether the motion to amend meets the statutory and regulatory requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121.” See Lectrosonics, Inc. v. Zaxcom, Inc., IPR2018-01129, Paper 15 at 4 (PTAB Feb. 25, 2019) (precedential). A “patent owner bears the burden of persuasion to show, by a preponderance of the evidence, that the motion to amend complies” with the applicable statutory and regulatory requirements. 37 C.F.R. § 42.121(d)(1). Specifically, a patent owner must demonstrate the following: (1) the amendment proposes a reasonable number of substitute claims; (2) the amendment responds to a ground of unpatentability involved in the trial; (3) the amendment does not seek to enlarge the scope of the claims of the patent; and (4) the amendment does not introduce new matter. See 35 U.S.C. § 316(d); 37 C.F.R. § 42.121(a)–(b). For the reasons explained below, Patent Owner satisfies its burden of persuasion to show that the amendments comply with the applicable statutory and regulatory requirements.” slip op. at 8
- Skill levelSkill level patent owner adoptedDecided for patent owner
“Both parties rely on expert testimony for their respective positions relating to the number of years of experience needed to attain ordinary skill, but neither expert cites supporting evidence for their testimony. See Ex. 1002 ¶ 33; Ex. 2002 ¶ 15. Our decision is the same regardless of whether the length of experience is two years or three. We find Patent Owner’s proposed “wireless communications” is more consistent with the ’958 patent than Petitioner’s proposed “telecommunication,” which encompasses a variety of technologies including, e.g., landline and wireless telephones, cable, and satellite. See Ex. 1001, 1:11–62 (describing the invention in terms of wireless communications). Accordingly, we adopt a modified version of Petitioner’s proffered level of ordinary skill in the art, substituting “wireless communications” for “telecommunication.” Neither party, moreover, indicates the overall result would change based on a different definition.” slip op. at 18
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“We agree with Patent Owner that the recited second type SIBs exclude first type SIBs. The plain meaning of “first type” and “second type” indicates that the first type and second type are different in kind. RMTA 22 (App. A). Our interpretation is consistent with the Specification, which explains that second type SIBs exclude first type SIBs. As Patent Owner points out, the ’958 patent discloses “first type of system information (1TYP SIB) is . . . essential . . . for initial system access” and “second type of system information (2TYP SIB) is nonessential system information . . . defined as all other types of information, and thus excludes the [] information required for initial access.” Id. at 11–12 (citing Ex. 1001, 8:34– 46); see also Ex. 1001, Abstract (interchangeably using the terms second type and non-essential). Despite Petitioner’s argument that this disclosure is non-limiting and directed to a disclaimed example embodiment (Opp. 8–9), Petitioner could not identify any embodiment, among the approximately forty disclosed embodiments, describing something other than the first type SIB being essential information and the second type SIB being non-essential information. Tr. 22:18–26. Even the Petition acknowledges that “the ’958 Patent further classifies a second type of system information, the ‘non-essential’ SI, which is defined as all other types of information excluding that first type of information required for initial access.” Pet. 5. Furthermore, the prior art of record suggests that a person of ordinary skill would have understood second type SIBs exclude first type SIBs. See Ex. 1008 ¶ 48 (describing two categories of system information, “essential SI” and “Other SI”). Patent Owner’s expert also understood the recited first and second type SIBs as being mutually exclusive. See Ex. 1011, 49:10–13. For the above reasons, we do not agree with Petitioner that the recited second type SIB lacks any requirements, nor do we interpret claims 7 and 8 such that the first type SIB could be a second type SIB.” slip op. at 19
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“(d) Limitation 7h: Analysis We agree with Patent Owner that Petitioner’s arguments with respect to limitation 7h are insufficient because they fail to address the limitation as written and improperly incorporate previous arguments by reference. For example, Petitioner did not map the recited “group identifier” when opposing Patent Owner’s Revised Motion to Amend. See Opp. 16–17. In its Sur-reply, Petitioner contends that limitation 7h’s requirement of transmitting the group identifier was previously “set out in Patent Owner’s prior papers,” but does not refer to any specific papers or exhibits. Pet. Surreply 11–12. We decline to search for and piece together Petitioner’s arguments and evidence to develop a persuasive theory of unpatentability. See 37 C.F.R. section 42.6(a)(3). Petitioner similarly failed to address adequately where Lee discloses or suggests the recited “compressed format” and “plural parameters.” See Opp. 16–17. Aside from the above concerns, we also do not see sufficient explanation with respect to limitation 7h’s requirement that the transmitting by broadcast be based on a comparison of the value tag. Petitioner argues that, because Patent Owner does not dispute limitation 7g, “it would have been obvious to a POSITA to use the same value tag[] to determine the system information broadcast in Lee’s compressed format embodiment.” Pet. Sur-reply 12. This conclusory statement is not supported by any citations to evidence and was improperly introduced in the Sur-reply. Moreover, whether it was obvious to determine what system information is broadcast is not commensurate with the claim scope because limitation 7h requires that the broadcasting (not the broadcast content) be based on a comparison of the value tag. See supra III.B.4 and IV.B. Further, we are not persuaded that Lee’s transmitting by broadcast is” slip op. at 26
Patent outcomesUS 10,841,958 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · NautilusPatents in suitUS 10,841,958 - Continental Automotive Systems, Inc. v. Intellectual Ventures II LLCAll claims unpatentablePTAB · Dec 5, 2023 · IPR2022-00972 · APJ David C Mckone · IPR · Final written decision
Claims 1–10 are unpatentable because Speight anticipates them; the Board found Peisa anticipation and Peisa–Heo obviousness unproven for the challenged claims in those grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“of ordinary skill in the art “would have had a Bachelor of Science in electrical engineering, computer engineering, or an equivalent field, as well as three years of experience in wireless communication technology, or a master’s degree in electrical engineering, or other equivalent degree,” and that “[a]dditional education could substitute for professional experience and vice versa.” Pet. 14 (citing Ex. 1004 ¶¶ 47–49). Patent Owner does not contest Petitioner’s contention or propose a level of skill. Petitioner’s proposal is consistent with the technology described in the Specification and the cited prior art. On the complete record, we adopt this level of skill.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“agreement that this claim term should be read as reciting two mutually-exclusive alternatives with respect to the “third parameter.” Dec. 11. The parties do not challenge this construction in the Patent Owner Response, Reply, or Sur-reply. On the complete record, we construe “wherein resources are allocated for data of each channel having a second parameter above zero prior to another channel’s data for transmission having a third parameter less than or equal to zero” as reciting two mutually-exclusive alternatives with respect to the “third parameter.”” slip op. at 11
- Strike new argumentNew argument disregardedDecided for patent owner
“We agree with Patent Owner. The Petition is required to identify “[h]ow the challenged claim is to be construed.” 37 C.F.R. § 42.104(b)(3). Petitioner argued in the Petition that “as properly construed, the claimed ‘first parameter,’ ‘second parameter,’ ‘third parameter,’ and ‘fourth parameter’ are four different parameters.” Pet. 17–18. In the Institution Decision, Petitioner prevailed on that point and “we agree[d] with Petitioner that the second and third parameters are separate and different parameters, and not different instances of the same parameter for separate channels.” Dec. 14. Patent Owner “relie[d] on the Board’s construction ‘that the second and third parameters are separate and different parameters, and not different instances of the same parameter for separate channels,’” and proposed distinct parameters in the Specification that it alleges are examples of second and third parameters, albeit not the same two parameters proposed by Petitioner. PO Resp. 9, 29. Petitioner now proposes new constructions for the second and third parameters that would limit those parameters to the two examples it advanced in the Petition and improperly supports these new constructions with new expert testimony and an exhibit from the prosecution of a later patent. Reply 20–25; Ex. 1040 ¶¶ 20–29; Ex. 1038. See also Consolidated Trial Practice Guide (“TPG”)10 73 (“Petitioner may not submit new evidence or argument in reply that it could have presented earlier, e.g. to make out a prima facie case of unpatentability.”). As Patent Owner observes (Sur-reply 10 Available at https://www.uspto.gov/TrialPracticeGuideConsolidated. 21), it has no opportunity to introduce rebuttal evidence contesting the new constructions. See TPG 73–74 (Nov. 2019) (“The sur-reply may not be accompanied by new evidence other than deposition transcripts of the crossexamination of any reply witness. Sur-replies should only respond to arguments made in reply briefs, comment on reply declaration testimony, or point to cross-examination testimony.”). We agree with Patent Owner that it would be unfair to consider Petitioner’s new construction. See 37 C.F.R. § 42.23(b) (“A reply may only respond to arguments raised in the corresponding opposition, patent owner preliminary response, patent owner response, or decision on institution.”). Thus, Petitioner has forfeited its new claim construction arguments and they will not be considered. See TPG 74 (“While replies and sur-replies can help crystalize issues for decision, a reply or sur-reply that raises a new issue or belatedly presents evidence may not be considered.”). Moreover, these arguments would be unpersuasive even if considered. Petitioner has, at most, cited description in the Specification to show that its identified second and third parameters are examples corresponding to the recited second and third parameters. Ex. 1005 ¶¶ 84–95. This description does not define the second and third parameters nor purport to exclude from the claims any parameter that would otherwise meet the language of the claims. The prosecution history to which Petitioner cites, that of a child application, took place after the prosecution of the ’466 patent and thus, does not constitute a definition or disclaimer of subject matter for claims of the ’466 patent. In any case, the brief argument in the cited response to office action, that “[i]n the algorithm, the first value is provided by the wireless network for each of a plurality of buffers where the buffer having the second value above a threshold transmits data first,” does not define the second and third parameters, disavow any values from those parameters, or even discuss the third parameter. Ex. 1038, 12. Petitioner’s extrinsic evidence, Dr. Akl’s testimony, does little more than repeat the arguments in the Reply and, thus, is of little value. Ex. 1040 ¶¶ 20–29. In sum, we maintain our construction that the second and third parameters are separate and different parameters, and not different instances of the same parameter for separate channels. Under this construction, RAAUq” and RAAUq’, respectively, could potentially be second and third parameters, as could RAAUq’ and RAAUq”, respectively, as long as they satisfy the rest of the pertinent language of the challenged claims.” slip op. at 15
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateNot shown unpatentable
“production, we still would find that a skilled artisan would not have been able to ascertain from the disclosure in the ’421 application that RAAUq’ could take values less than zero. Instead, even if we were to credit Dr. Lomp’s testimony, to conclude that RAAUq’ can take negative values, a skilled artisan would need to program computer software to simulate the ’421 application’s algorithm and correctly choose starting parameters and other context variables without guidance from the description in the ’421 application. This case is similar to that in New Railhead, where the written description was insufficient because “one of ordinary skill in the art must first make the patented invention before he can ascertain the claimed features of that invention.” 298 F.3d at 1295. This case also is similar to Los Angeles Biomedical Research Institute, in which an application’s written description was insufficient because assumptions and starting variables were not knowable from the disclosure in the application. 849 F.3d at 1058. Thus, even if we were to conclude that Patent Owner has met its burden of production, a preponderance of the evidence shows that the ’421 application does not provide written description support for Alternative A. In sum, we conclude that the ’421 application does not provide written description support for the challenged claims and that, therefore, Speight is prior art to the challenged claims.” slip op. at 41
Patent outcomesUS 9,681,466 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites PhillipsPatents in suitUS 9,681,466 - Facebook, Inc. v. Palo Alto Research Center LLCAll claims unpatentablePTAB · Mar 22, 2023 · IPR2021-01461 · APJ Christopher L Ogden · IPR · Final written decision
Claims 1–5, 7–11, 13–17, 19, and 20 are unpatentable under § 103; PARC’s contingent motion to amend is denied because the pending substitute claims lack written-description support and are obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Relying on Mr. Schmandt’s testimony, Facebook argues that a person of ordinary skill in the art “would have possessed at least a bachelor’s degree in electrical engineering or computer science, and two years of work experience in the field of context-based computer systems, such as the collection, processing and use of context data in computer systems capable of adapting their operation based on context.” Pet. 6 (citing Ex. 1002 ¶¶ 15– 18). Facebook also contends that a person might qualify as an ordinarily skilled artisan “with more formal education and less technical experience, or vice versa.” Id. For this proceeding, PARC does not dispute this proposed level of ordinary skill. PO Resp. 16–17. Because Facebook’s uncontroverted articulation of the level of ordinary skill in the art is supported by testimonial evidence and appears consistent with the types of problems and solutions in the ’439 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:4–33 (“Background” section of the ’439 patent, describing the field and related art as relating to the use of using contextual data in computer systems).” slip op. at 10
- Strike new argumentNew argument consideredDecided for petitioner
“construction of the term “facts and assertions” or the identification of facts and assertions within Cheng. See Paper 23, 1–2. Having reviewed the arguments, we do not consider them untimely. As we discuss in more detail below, Facebook relied on the ordinary and customary meaning of the term “facts and assertions” in its Petition, and then when PARC raised an alternative construction of the term in its Response, Facebook responded to those arguments. See infra Sections IV.B.2, IV.C.4(a). Facebook’s Reply only responded to arguments raised in PARC’s Response and was not untimely. See 37 C.F.R. § 42.23(b) (permitting a petitioner to respond to arguments in a patent owner response); Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018) (“[T]he 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, or if it is used ‘to document the knowledge that skilled artisans would bring to bear in reading the prior art identified as producing obviousness.’” (quoting Genzyme Therapeutic Prod. Ltd. P’ship v. Biomarin Pharm. Inc., 825 F.3d 1360, 1369 (Fed. Cir. 2016))). Moreover, PARC had a meaningful opportunity to address the arguments in its Sur-reply and in oral argument. See PO Sur-reply 7–12; Tr. 22–34. Thus, we do not find Facebook’s contested arguments untimely and we have considered them in our decision.7” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“We agree with Facebook. As we discuss below, Cheng teaches a graph-based model that stores data in memory on a per-user basis. See infra Section IV.C.4(a); Ex. 1003, Fig. 7. Also, as PARC acknowledges, Facebook’s expert Mr. Schmandt stated in deposition that he assumed, for his analysis, that the term “context graph” requires a “graph-based model.” PO Resp. 22 (citing Ex. 2019, 36:16–37:8); see also PO Sur-reply 4. Thus, because Facebook’s analysis of Cheng is consistent with the assumption that “context graph” has the meaning PARC proposes in this proceeding, we do not need to construe the term “context graph” to reach our decision. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e 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 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“We agree with the parties that a person of ordinary skill in the art would have understood the term “fact” to include an indication of truth, whereas an assertion need not include such an indication. However, we disagree with PARC that a person of ordinary skill would have considered the term “assertion” to exclude facts. Indeed, in its ordinary and customary meaning, a fact stored in a context graph would be a type of assertion. We appreciate PARC’s argument that when two different terms appear in a claim, they presumably refer to different things. See PO Resp. 27 (citing CAE Screenplates, 224 F.3d at 1317). And we agree that the two terms have different meanings in claim 1 based on the plain meaning of each term. However, the specification refers to “stor[ing] facts and assertions about a user’s behavior and interests,” which simply appears to identify a single category of data for storage, i.e., “facts and assertions,” without specifying a clear difference between “facts” and “assertions.” See Ex. 1001, 3:21–22. In any event, we find no evidence of record suggesting that either (1) the (citing Pet. Reply 8–9). Because Facebook appears to have been relying on what it regarded as the plain meaning of the terms without proposing an explicit construction, we do not interpret Facebook’s argument in the Petition (Pet. 20–21) to imply that there is no distinction between a fact and an assertion, and do not find Mr. Schmandt’s later testimony (see, e.g., Ex. 2019, 41:3–11) inconsistent with arguments made in the Petition. ordinary and customary meaning of the term “assertion” excludes facts, or (2) that the ’439 patent uses these terms in a way that departs from their ordinary and customary meaning. That claim 1 requires the presence of both “facts” and “assertions” does not render the two terms superfluous, as this would exclude prior art in which a context graph includes only assertions but not facts. On the other hand, a disclosure of a collection of facts would meet the term “facts and assertions” because a person of ordinary skill in the art would have regarded any subset of the facts to also be assertions.” slip op. at 15
Patent outcomesUS 9,208,439 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 9,208,439
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.