• Crowdstrike, Inc. v. Gosecure, Inc.Some claims unpatentable
  PTAB · Aug 12, 2026 · IPR2025-00070 · APJ Neil T Powell · IPR · Final written decision

  Claims 1, 3–7, and 9–21 are unpatentable as obvious; claims 2 and 8 were not shown unpatentable because the asserted art did not meet their construed limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “III. ANALYSIS LEVEL OF ORDINARY SKILL A. Petitioner explains the applicable level of skill in the art as follows: As of June 24, 2010, a person of ordinary skill in the art (POSITA) would be a person having a bachelor’s degree in computer science, computer engineering, or an equivalent, as well as two years of industry experience and who would have had a working knowledge of software security analysis, and dynamic malware analysis. Additional graduate education could substitute for professional experience, or significant experience in the field could substitute for formal education. Pet. 8 (Ex. 1003 ¶¶ 30–31). Patent Owner does not dispute Petitioner’s explanation of the level of skill in the art. See Ex. 2031 ¶¶ 15–16. We adopt Petitioner’s uncontested proposed level of ordinary skill in the art, which we find consistent with the level of ordinary skill in the art reflected by the ’872 patent and the prior art of record. See Okajima v.” slip op. at 12

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “We begin with the claim language in view of the Specification, which weighs heavily against Patent Owner’s position that we should rewrite “computer system” as narrowly referring to a “computing device.” PO Resp. 24. As Petitioner notes, the ’872 patent’s Specification uses “computer system” to refer to a wide range of equipment, from a component of a computing device, to a whole computing device, to a collection of computing devices. Reply 9–10 (citing Ex. 1001, 4:5–8, 11:15–18, 16:50–55). In one example, the Specification refers to “one or more other computer systems (e.g., protected network devices 136).” Ex. 1001, 18:52–53. Thus, the Specification lists “protected network devices 136” as only an example of “other computer systems,” demonstrating that “computer systems” refers to things other than protected network devices. Although Patent Owner may be correct that this passage more than a single computing device,” we find that other disclosures in the ’872 patent do. Specifically, the Specification uses the language “distributed computer system” when referring to numerous components, including “protected network devices” and an “IDS/IPS system.” Ex. 1001, 3:26–28; Reply 10. In addition to showing that a “computer system” is not limited to a single computing device, this conveys that a “computer system” according to the ’872 patent can include an IDS/IPS.” slip op. at 14

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

    “Based on our review of the complete record, we find Petitioner’s arguments and evidence to be more persuasive. Patent Owner does not dispute Petitioner’s argument and evidence that capturing detailed information like Goel’s activity sources, activity targets, and association was recognized as enhancing threat analysis. Pet. 44 (citing Ex. 1003 ¶ 79); see PO Resp. 55–59; Sur-Reply 15–17. Additionally, contrary to Patent Owner’s suggestion, we find that the Petition does not propose incorporating Goel’s kernel hooks into Capalik’s system. See Pet. 41–46. Patent Owner contends that the Petition’s reference to modifying Capalik by “adding lines of code” suggests implementing the code disclosed in Goel include kernel hooks. Id. Notwithstanding Patent Owner’s assertion otherwise, this is an unpersuasive bodily incorporation argument, as the Petition never says an ordinarily skilled artisan would have used the exact lines of code from Goel in Capalik. Rather, the Petition says that an ordinarily skilled artisan would have had sufficient skill to implement straightforward code modifications to identify activity sources, targets, and associations: a [person of ordinary skill in the art] would have understood that modifying Capalik’s system (e.g., Linux-based) to additionally monitor, identify, and store each individual activity of an attack including “activity sources, activity targets, and associations” would have required straightforward modifications to programs/code instructions, which would have been well-within the skillset of a [person of ordinary skill in the art]. Pet. 46. Patent Owner argues that Petitioner does not explain how an ordinarily skilled artisan would have modified Capalik without using kernel hooks. Sur-Reply 17. But Patent Owner does not cite any evidence to counter Dr. Jakobsson’s testimony that an ordinarily skilled artisan would have had the skill to apply Goel’s general teaching of identifying sources, targets, and associations to Capalik’s system. Ex. 1003 ¶ 182. On the whole, the evidence does not support Patent Owner’s position that the combination would have required substantially increased detection risk. Moreover, even if the combination would have somewhat increased detection risk, Petitioner persuades us that an ordinarily skilled artisan still would have had reason to combine the references teachings. Patent Owner’s allegations of increased detection risk do not negate the undisputed evidence that the combination would have provided the advantage of improved threat analysis. Pet. 44 (citing Ex. 1003 ¶¶ 175–182). Ultimately, Patent Owner’s that activity logging be undetectable.” PO Resp. 56 (emphasis added) (citing Ex. 1004 ¶ 6). This exaggerates Capalik’s disclosure. Although the cited paragraph suggests that certain systems unfortunately may be detectable by some users, it does not convey that it is a requirement for the system to be categorically undetectable. See Ex. 1004 ¶ 6.8 In sum, Petitioner persuades us by a preponderance of the evidence that it would have been obvious to modify Capalik “to identify and store unauthorized activities including the activity source, activity target, and association of each activity.” Pet. 41–46; PO Resp. 55–59; Reply 20–22; Sur-Reply 15–17.” slip op. at 47

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for patent owner

    “arguments and evidence, we determine that Patent Owner fails to sufficiently show a nexus between any of its objective indicia evidence and the claimed invention. See Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (“The patentee bears the burden of showing that a nexus exists”). A showing of sufficient nexus is required to establish that the evidence relied upon traces its basis to a novel element in the claim, not to something in the prior art. Institut Pasteur & Universite Pierre Et Marie Curie v. Focarino, 738 F.3d 1337, 1347 (Fed. Cir. 2013). Objective evidence that results from something that is not “both claimed and novel in the claim” lacks a nexus to the merits of the invention. In re Kao, 639 F.3d 1057, 1068 (Fed. Cir. 2011) (emphasis omitted). Thus, establishing nexus involves a showing that novel elements in the claim, not prior-art elements, account for the objective evidence of nonobviousness. Id. As discussed above, Petitioner shows that Capalik teaches all limitations of claim 1. Petitioner persuades us that none of claim 1’s elements individually nor any combination thereof is novel over Capalik’s disclosure. Accordingly, claim 1 is not novel over Capalik, which disproves Patent Owner’s assertion of nexus. PO Resp. 73–76. Moreover, even if claim 1 were novel, Patent Owner otherwise fails to show nexus for its commercial success, praise, or copying assertions. Patent Owner’s evidence does not show that Petitioner’s commercial product embodies claim 1. For example, we agree with Petitioner that Patent Owner “failed to analyze any meaningful detail regarding” how the Falcon Platform allegedly meets limitation 1(d). Reply 28–29. In particular, Patent Owner has not sufficiently addressed limitation 1(d) with the following argument: “1[D] The Falcon Platform transmitted to other computer systems” slip op. at 37

  Patent outcomesUS 9,954,872 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 9,954,872
• Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentable
  PTAB · Mar 31, 2026 · IPR2024-01450 · APJ Peter D Shapiro · IPR · Final written decision

  Claims 1–4, 6–11, and 13–20 were not shown unpatentable because Dziong and Sathyanath do not teach the claimed sharing definition for existing connections with allocated bandwidth.

  RulingsFinal written decision

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

    “First, the claims use present-tense language, “one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection.”3 Ex. 1001, claim 1 (emphasis added). The exclusive use of the present tense have indicates “other connections” must have current possession of the bandwidth. For these other connections to share bandwidth with a newly established connection, they must already exist and have bandwidth ready for immediate use, rather than merely holding a dormant “reservation” pending a network failure. See PO Supp. Br. 1. The Federal Circuit addressed a similar situation where the Court found the present-tense limitation “is connected to the computer network” means a device was required to be connected at the” slip op. at 15

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “combination, do not teach or suggest limitations 1.2 and 1.3 requiring: providing a sharing definition specifying one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection, such that a total bandwidth allocated jointly to the new connection and to the other connections in any given segment is equal to a maximum of the requested bandwidth and of the bandwidths of the other connections in the given segment Ex. 1001, limitations 1.2, 1.3 (emphasis added); see PO Resp. 17–22; Sur-reply 4–5, 12–14. As discussed above in Section II.C.2, we interpret “other connections” to mean “existing connections in the network that already have bandwidth allocated to them.” Because the information shared in Dziong and Sathyanath, described below, relates to reserved protection paths, rather than existing connections that have bandwidth that can currently transmit network traffic, the references do not teach or suggest the “other connections” part of the sharing definition in limitations 1.2 and 1.3. Dziong describes advertising, across the network, the amount of bandwidth reserved for recovery on each link that would be activated when a protected link fails. See, e.g., Ex. 1005 ¶ 60; Pet. 36. Once activated, network traffic from a “primary path” failure is rerouted to these recovery paths. See Ex. 1005 ¶¶ 7–9, 70, 83. Petitioner points to this advertising of the reserved bandwidth information as teaching the claimed “sharing definition.” Pet. 33–36 (arguing that the “protection paths [in Dziong] have bandwidth reservations” and “share an overall protection bandwidth reservation”); Reply 21–23. However, since the advertised information only contains information about the recovery paths “that would be activated” upon a primary path failure, such paths are not existing connections that already have bandwidth allocated to them, and therefore do not teach the claimed “other connections” that are part of the sharing definition. See, e.g., Ex. 1005 ¶ 60.” slip op. at 43

  Patent outcomesUS 7,596,088 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,596,088
• Apple Inc. v. S.M.R Innovations Ltd And Y.M.R Tech LtdAll claims unpatentable
  PTAB · Jan 27, 2026 · IPR2024-01048 · APJ Mary C Hoffman · IPR · Final written decision

  Claims 1, 5–8, 10, 11, 13, 15, 16, 18, and 19 are unpatentable as obvious under § 103 over the four stated combinations.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not contend that the differences between the parties’ formulations would affect our patentability analysis. PO Resp. 2–4. Petitioner does not dispute that Patent Owner’s declarant, Mr. Ginter, who has a bachelor’s degree and years of experience in wireless communication, qualifies as a POSITA. Tr. 43; Ex. 2009 ¶¶ 5–10. Petitioner also concedes that its challenges do not hinge on which formulation we accept. Tr. 43. We agree that our decision would be the same regardless of the differences between the formulations. We adopt Patent Owner’s proposed formulation, which is supported by declaration testimony and generally consistent with the level of skill reflected in the ’648 patent and the prior art of record. Ex. 2009 ¶¶ 21–25; Exs. 1001, 1004–1009.” slip op. at 10

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

    “We disagree. Although claim 1 recites step 1b before step 1d, method steps are not ordinarily construed to require a specific order of performance unless the claims or Specification directly or implicitly require that specific order. See Altiris, Inc. v. Symantec Corp., 318 F.3d 1363, 1369–70 (Fed. Cir. 2003). Here, nothing in the express claim language precludes performing step 1d before step 1b. The claim does not expressly recite signaling the device(s) previously “identified as available.” Nor does the claim otherwise specify that step 1b must precede step 1d. For example, the claim does not contain temporal terms like “then,” “next,” or “further.” Although Patent Owner points out that a term of step 1d (i.e., “the” one more available devices) derives antecedent basis from step 1b, this alone does not require performing step 1b before step 1d. PO Resp. 5, 10; Sur-reply 11. Rather, we agree with Petitioner that step 1d’s reliance on step 1b for antecedent basis only serves to clarify that the steps refer to the same device(s), not to determine the performance order. Reply 4, 5. We also agree with Petitioner that claim 1 inconsistently employs antecedent basis for other claim elements, which undermines Patent Owner’s argument that step 1d’s antecedent basis establishes a specific order. Reply 7 (referring to the recited “media content,” “the media content,” and “a media content”).” slip op. at 11

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

    “We disagree. Petitioner met its burden to show that the combination would have been obvious. Zhang teaches a cellular phone (which logically receives cellular calls) and routing media to audio devices on its network. Ex. 1004, 3:25–29. Missing in Zhang is an explicit teaching that its cellular calls (as opposed to other media) are routed. Pasanen explicitly teaches routing cellular calls to networked audio devices. Ex. 1006; 4:20–37. Taken together, routing Zhang’s cellular calls across its network would have been obvious to a POSITA. Patent Owner’s argument that Zhang-Fillebrown’s 802.11 or HomeRF network do not support routing cellular calls discounts Zhang’s teaching that “its network can be built on top of many different kinds of communication media” including but not limited to 802.11 and HomeRF, as well as the “optional HomeRF features” Petitioner claims would sufficient to implement the claimed functionality. Ex. 1001, 4:46–50; Reply 20–22 (citing Ex. 1037 ¶¶ 13–15); Sur-reply 3–6 (arguing that HomeRF’s isochronous mode and DECT protocol are optional and would not have been necessary to practice Zhang’s subject matter). And though Zhang does not discuss transcoding or specific HomeRF features/protocols, which Patent Owner argues are necessary for routing cellular calls across Zhang’s 802.11 or HomeRF network, we agree with Petitioner that the ’648 patent also provides scant technical details as to how its system routes cellular calls over its local network, suggesting that such was well known at the time. Reply 17 (citing, e.g., Ex. 1001 7:9–25).” slip op. at 28

  Patent outcomesUS 10,547,648 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,547,648
• Juniper Networks, Inc. v. Portsmouth Network Corp.Some claims unpatentable
  PTAB · Jan 13, 2026 · IPR2024-00913 · APJ Justin T Arbes · IPR · Final written decision

  Claims 1, 2, 4, 6, 7, 11, 12, 14, 16, and 17 are unpatentable over Blease, Weyman, and Hu, with some claims also over Deng; claims 8–10 and 18 were not shown unpatentable.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert discountedOther

    “disclosure in Weyman (or Blease) for deactivating and activating ports, or performing certain actions in the time between such actions. Again, the only portion of Weyman cited pertains to a request to join the fabric from a processing unit having a “default” configuration, which does not relate to the timing or sequence of events in initialization. See Ex. 1006 ¶¶ 69, 156, 161–162; Ex. 1103 ¶¶ 93–94. Nor does Dr. Lavian point to any other evidence in the record supporting his conclusion that a person of ordinary skill in the art would have “ensure[d] that the processing unit is deactivated prior to being updated for use . . . and then activate[d] the processing unit after updating.” See Ex. 1103 ¶ 94. Accordingly, we give little weight to Dr. Lavian’s conclusory opinion” slip op. at 75

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableUnpatentable

    “See Axonics, 73 F.4th at 957; Allied Erecting, 825 F.3d at 1381; Mouttet, 686 F.3d at 1332–33. Petitioner’s position is that, based on the teachings of Weyman, a person of ordinary skill in the art would have modified Blease’s system to distribute the functionality of control unit 44 (including its existing multicast forwarding information 48 used by OIF mapper 50). See Pet. 23–26, 38; Fleming v. Cirrus Design Corp., 28 F.4th 1214, 1222 (Fed. Cir. 2022) (“That the proposed combination of [two references]—rather than one of the individual references—discloses the disputed claim limitations does not defeat the Board’s conclusion of obviousness. In this case, it is sufficient that a person of ordinary skill in the art would have been motivated to combine the prior art in a way such that the combination discloses the claim limitations.”).” slip op. at 55

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “10 In the Cisco IPR, we determined that Cisco had proven claims 8 and 18 to be unpatentable based on a different combination of references (identified as Weyman, Jain, and LeMaire), finding that limitation 8[f.ii] was taught by Jain and LeMaire. IPR2024-00506, Paper 38 at 58–77. As explained herein, we are not persuaded by Petitioner’s arguments in this proceeding that limitation 8[f.ii] is taught or suggested by Weyman. Also, in the Decision on Institution in this proceeding, the Board found that there were questions as to Petitioner’s showing for limitation 8[f.ii] and declined to reach a conclusion on whether Petitioner had shown a reasonable likelihood of prevailing on its asserted ground based on Blease and Weyman. Dec. on Inst. 43.” slip op. at 71

  Patent outcomesUS 8,014,394 mixed
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,014,394
• Everstar Merchandise Co., Ltd. v. Willis Electric Co., Ltd.Some claims unpatentable
  PTAB · Dec 18, 2025 · PGR2019-00056 · APJ Stacey G White · PGR · Remand

  Claims 2–7, 9–19, 21–25, 27, 30, 31, and 33 are unpatentable as obvious; Petitioner did not prove claims 8, 20, 26, 28, 29, and 32 unpatentable.

  RulingsRemand decision

  • RemandMixed

    “The Federal Circuit found that “[t]he factual record and Willis’s concession on appeal conclusively establish that the cost of copper was a known problem in the art, Debladis ’120 (and Kumada) helped address that issue, and Willis has not disputed that combining the teachings of Kumada and Debladis ’120 was within the skill of an ordinary artisan,” concluding “[n]othing more is required to establish a motivation to combine.” Everstar II, 2025 WL 1501940, 4. The Federal Circuit observed that “Willis has conceded that the combination of Kumada and Debladis ’120 disclose all the limitations in claim 1,” and accordingly, “reverse[d] the Board’s patentability determination as to that claim and vacate[d] the Board’s judgment as to the remaining claims of the ’037 patent,” remanding to us for further proceedings. Id. at 4–5. With those instructions in mind, we review the Petitioner’s allegations regarding claims 2–33.” slip op. at 6

  • Skill levelSkill level board ownDecided for patent owner

    “F. Person of Ordinary Skill in the Art In the First Final Written Decision, we determined that a person of ordinary skill in the art “would have (1) at least two years of experience in the design of decorative lighting, or (2) at least a bachelor’s degree in mechanical engineering, electrical engineering, or an equivalent field, and a basic familiarity with circuits used in decorative lighting.” Paper 40, 12. We see no reason to depart from that earlier determination.” slip op. at 12

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

    “The parties agree that we do not need to construe any claim terms. Pet. 8–9; PO Resp. 16–17. We likewise agree. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”)).” slip op. at 13

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

    “Patent Owner did not dispute that the combined teachings of Kumada and Debladis ’120 disclose each limitation of claim 1. Patent Owner, however, did dispute Petitioner’s proposed reasons for combining Kumada and Debladis ’120, and argues that Debladis ’120 is not analogous art. PO Resp. 36–61. The Federal Circuit stated that substantial evidence only supports the conclusion that a POSA would have been motivated to combine the teachings of Kumada and Debladis ’120. The factual record and Willis’s concession on appeal conclusively establish that the cost of copper was a known problem in the art, Debladis ’120 (and Kumada) helped address that issue, and Willis has not disputed that combining the teachings of Kumada and Debladis ’120 was within the skill of an ordinary artisan. Nothing more is required to establish a motivation to combine. Given that Willis has conceded that the combination of Kumada and Debladis ’120 disclose all the limitations in claim 1, we reverse the Board’s patentability determination as to that claim and vacate the Board’s judgment as to the remaining claims of the ’037 patent. Everstar II, 2025 WL 1501940, 4 (internal citations omitted). The Federal Circuit further noted Patent Owner’s secondary considerations arguments as to claim 1 and stated [t]he cited evidence consists only of a temporal connection between the introduction of Willis’s invention and the UL 588 standards, and deposition testimony of a single witness who seemingly disclaimed any connection between the two. This is not sufficient to rescue a claim as to secondary considerations. Id. at 4, n. 5 (internal citations omitted). Accordingly, the Federal Circuit ruled that claim 1 would have been obvious over Kumada and Debladis ’120. 6. Analysis of Independent Claim 33” slip op. at 17

  Patent outcomesUS 10,222,037 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 10,222,037
• Juniper Networks, Inc. v. Portsmouth Network Corp.All claims unpatentable
  PTAB · Dec 9, 2025 · IPR2024-00893 · APJ Justin T Arbes · IPR · Final written decision

  Claims 3, 8, 11, 12, 15, 20, 23, and 24 are unpatentable as obvious over Gai and IEEE 1999.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that at the time of the application for the ’986 patent (January 2002), a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering or a related field, plus at least two years of industry experience or graduate-level academic experience with computer networking.” Pet. 20. In the Decision on Institution, the Board agreed with and applied Petitioner’s proposed definition, removing the phrase “at least” to avoid unnecessary ambiguity. Dec. on Inst. 18–19. Patent Owner uses Petitioner’s proposed definition for its Response. PO Resp. 5. Neither party made any further argument regarding the level of ordinary skill in the art in its papers during trial. In the Cisco IPR, we adopted a similar definition, determining that a person of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, electrical engineering, or in an equivalent field, or approximately two years of experience working in the field of information technology and networking,” where “[l]ack of professional experience can be substituted by additional education, and vice versa.” IPR2024-00505, Paper 29 at 10–11 (alteration in original); see Dec. on Inst. 19 n.7 (noting the proposed definition in the Cisco IPR). Based on the full record developed during trial, including our review of the ’986 patent and the types of problems and solutions described in the ’986 patent and cited prior art, we adopt the same definition of the level of ordinary skill in the art as the Cisco IPR and apply it for purposes of this Petitioner’s similar proposed definition in this proceeding.” slip op. at 12

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Gai discloses entering an Enable_Uplinkfast command at an access switch (e.g., access switch 114) to block a failed port (e.g., the root port) and configure the access switch to send dummy traffic upstream through a new active port. . . . When modified in view of IEEE 1999’s disclosure that self-healing network traffic can advantageously be sent both upstream and downstream, the command would be entered at a backbone switch (e.g., backbone switch 122) to block a failed port (e.g., a designated port connected to access switch 114) and configure the backbone switch to send dummy traffic downstream to an access switch (e.g. access switch 114) through a new active port. While Gai uses its protocol signaling command, Enable_Uplinkfast, to send dummy traffic through a new root port, [a person of ordinary skill in the art] would deem it an obvious implementation detail to modify the parameters of the port on a backbone switch. See Ex. 1003 ¶ 139 (citing Ex. 1005, col. 6, ll. 39–46).” slip op. at 34

  • Prior constructionPrior construction adoptedDecided for petitioner

    “In the Cisco IPR, we addressed four claim terms in the final written decision: “access switch” and “edge switch,” which appear in independent claims 1 and 13 and various dependent claims, and “downstream” and “upstream,” which appear in claims 11, 12, 23, and 24. IPR2024-00505, Paper 29 at 11–14. We interpreted “access switch” to mean “a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems,” interpreted “edge switch” to mean “a core switch that is directly connected to an access switch,” interpreted “downstream” to mean “away from the root switch,” and interpreted “upstream” to mean “toward the root switch.” Id. As noted above, Patent Owner did not appeal that decision. We incorporate herein our previous analysis in the Cisco IPR, but note that none of the analysis of the disputed issues below depends on such determine whether Petitioner has met its burden to prove unpatentability of the challenged claims. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe [a particular claim limitation] where the construction is not ‘material to the . . . dispute.’” (emphasis added) (citation omitted)).” slip op. at 13

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “1999, supported by the testimony of Mr. McNair, which we credit, is persuasive. See Pet. 25–30, 40–46; Ex. 1003 ¶¶ 132–145, 165–174. Based on the full trial record, we find that Gai and IEEE 1999 teach limitation [1E] and that a person of ordinary skill in the art would have been motivated to combine their teachings in the manner described by Petitioner. Based on all of the evidence of record, we determine that Petitioner has proven, by a preponderance of the evidence, that claim 3 would have been obvious over Gai and IEEE 1999 under 35 U.S.C. § 103(a). 4. Claims 8, 15, and 20 Claim 8 depends indirectly from independent claim 1. Claims 15 and 20 depend indirectly from independent claim 13, which is similar to claim 1 but recites a network switching device rather than a method. As to independent claim 13, Patent Owner refers to its earlier arguments regarding claim 1, asserting that limitation [13C] is “substantially similar” to limitation [1E]. PO Resp. 14–15. We disagree with Patent Owner’s arguments for the reasons explained above. See supra Section II.D.3.b. Patent Owner does not argue dependent claims 8, 15, and 20 separately from their respective parent claims 1 and 13. See PO Resp. 19. We have reviewed Petitioner’s contentions and supporting evidence, including the testimony of Mr. McNair, and are persuaded that Petitioner has proven, by a preponderance of the evidence, that claims 8, 15, and 20 would have been obvious based on Gai and IEEE 1999 under 35 U.S.C. § 103(a), for the reasons stated by Petitioner. See Pet. 21–46, 48–52, 55–59; Ex. 1003 ¶¶ 113–175, 179–185, 194–203.” slip op. at 41

  Patent outcomesUS 6,917,986 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,917,986
• Cisco Systems, Inc. v. Portsmouth Network Corp.All claims unpatentable
  PTAB · Oct 1, 2025 · IPR2024-00506 · APJ Justin T Arbes · IPR · Final written decision

  Claims 1, 2, 4–12, and 14–18 are unpatentable as obvious over the combinations of prior art listed in the decision.

  RulingsFinal written decision

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “d) Conclusion Petitioner has shown sufficiently that Weyman and Li collectively” slip op. at 50

  Patent outcomesUS 8,014,394 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,014,394
• Qualcomm Incorporated v. Unm Rainforest InnovationsAll claims unpatentable
  PTAB · Sep 30, 2025 · IPR2021-00375 · APJ Kristen L Droesch · IPR · Remand

  Proposed substitute claims 44–47, 49, and 50 are unpatentable as obvious under collateral estoppel; the Board denied Patent Owner’s motion to amend.

  RulingsRemand decision

  • RemandOther

    “the Acting Director of the USPTO (Paper 81, “Acting Director’s Order”) and after a decision by the U.S. Court of Appeals for the Federal Circuit (“the Federal Circuit”) in ZyXEL Communications Corp. v. UNM Rainforest Innovations, 107 F.4th 1368 (Fed. Cir. 2024) (“Federal Circuit Decision”) regarding the Board’s original Final Written Decision (Paper 68, “Final Written Decision” or “Final Dec.”) in this proceeding. In particular, the court remanded to the Board to determine if proposed substitute claims 44–47, 49, and 50 are unpatentable as obvious under collateral estoppel based on the court’s holding that claims 1–4 and 6–8 are unpatentable as obvious. ZyXEL, 107 F.4th at 1371, 1384.” slip op. at 2

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “proposed substitute claim 44 presents the same issues as those litigated before the Federal Circuit: whether it would have been obvious to a person of ordinary skill in the art to include the first key element and whether it would have been obvious to a person of ordinary skill in the art to include the second key element.” slip op. at 9

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied

    “Final Written Decision, and the Federal Circuit Decision, as well as the postremand briefing, we determine that the application of collateral estoppel to proposed substitute claim 44 is appropriate. It is also appropriate to apply collateral estoppel to substitute claims 45–47, 49, and 50. This is because proposed substitute claims 45–47, 49, and 50 depend from proposed substitute claim 44 and recite identical limitations to dependent claims 2–4, 6, and 7. Therefore, the resolution of the question of obviousness of the subject matter of proposed substitute claims 45–47, 49, and 50 necessarily presents the same issues of whether it would have been obvious to a person of ordinary skill in the art to include the first key element and whether it would have been obvious to a person of ordinary skill in the art to include the second key element.” slip op. at 11

  Patent outcomesUS 8,265,096 unpatentable
  § 103 obviousness
  Patents in suitUS 8,265,096
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01271 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving institution denied for claims 1–21 because the petition did not show a reasonable likelihood that Belanger-Halevy taught limitation [1B].

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “variable data database’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 94; Ex. 2001 ¶¶ 68, 70). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties.” slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties based on the SO-class identified for the form would have been recognized by a POSA as what the ’342 patent refers to as a universal variable map.” Ex. 1003 ¶ 98 (citing Ex. 1001, 17:48– 52). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers from multiple different websites to each other in the form database, because field identifiers are mapped to the same SO-properties associated with an SO-class.” Id. (emphasis omitted). We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’342 patent. In column 17, lines 48–52, the ’342 patent explains that fields or variables may be part of forms, and variations of the data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:48–52. While this portion of the ’342 patent indicates that forms may include variations on fields or variables, it does not describe linking or mapping variables to one another. Ex. 2001 ¶ 75 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’342 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1B]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1B] of the ’342 patent.” slip op. at 5

  None
  Patents in suitUS 10,262,342
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01270 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving in place the denial of institution because the Petition did not show a reasonable likelihood that Belanger-Halevy teaches limitation [1C] of claims 1–26.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “[m]issing, however, from Halevy’s disclosure is any teaching or suggestion that a ‘plurality of computer-readable field identifiers’ are mapped ‘to one another’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 104; Ex. 2001 ¶¶ 69, 71). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties. slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties would have been recognized by a POSA as what the ’378 patent refers to as a universal variable map.” Ex. 1003 ¶ 108 (citing Ex. 1001, 17:42–46). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers (including parameter names) from multiple different websites to each other in the form database, because the field identifiers are mapped to the same SO-properties associated with an SO-class. Id. We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’378 patent. In column 17, lines 42–46, the ’378 patent explains that fields or variables may be part of forms and variations of these data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:42–46. While this portion of the ’378 patent indicates that forms may include variations on fields or variables, it does not describe any linking or mapping of variables to one another. Ex. 2001 ¶ 76 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’378 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1C]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1C] of the ’378 patent.” slip op. at 5

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “Finally, with regard to the Reply and Sur-Reply submitted by the parties (Req. 9), we note that our Decision on Institution reviewed the parties’ discussion of claim construction, but ultimately determined that “[b]ased on our review of the preliminary record, we do not need to construe any terms expressly to reach our decision.” Dec. 11. Thus, we disagree with Petitioner that we misconstrued the mapping limitation where we did not find it necessary to construe any claim term for the purposes of our institution decision because we determined the Petition deficient for failing to meet our threshold requirements as discussed above and in detail in the Decision on Institution. See Req. 1–11.” slip op. at 7

  Claim construction
  Patents in suitUS 9,633,378

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.