• Google LLC v. Mindbasehq, LLCAll claims unpatentable
  PTAB · Mar 16, 2026 · IPR2021-01252 · APJ Kara L Szpondowski · IPR · Remand

  On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious; the Federal Circuit’s affirmed findings leave claims 1–13, 20–32, 41, and 42 unpatentable as well.

  RulingsRemand decision

  • RemandOther

    “to both cases vacating and remanding in part and affirming in part our Final Written Decisions. Appeal Dec. With respect to Petitioner’s appeals, the Federal Circuit addressed the “dictionary routine” claims (claims 14–19 and 33–40) and the “normalization” claims (claims 43–46). Appeal Dec. 7–14. For the “dictionary routine” claims, the Federal Circuit vacated and remanded, stating that In sum, as Google contends and we now hold, the “dictionary routine” claims can be practiced by use of an already-created dictionary, and do not also require the automatic creation of a dictionary. The Board needs to consider Google’s evidence and argument by applying this construction of the automatically classifying and storing limitation, and using this understanding to determine whether Conlon may, in fact, render the “dictionary routine” claims obvious (and, relatedly, whether its prior distinctions of Conlon may be immaterial). Appeal Dec. 10–11. For the “normalization” claims, the Federal Circuit also vacated and remanded, stating that our “decision to exclude Google’s rebuttal argument and supplemental declaration is based on a clear factual error,” so on remand we “must include evaluation of the evidence and argument Google provided in reply.” Id. at 13–14. With respect to Patent Owner’s cross-appeals, the Federal Circuit affirmed. Id. at 14–16.” slip op. at 3

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

    “The Federal Circuit concluded that Petitioner’s construction of “automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its” slip op. at 17

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

    “We agree with Petitioner that claim 43 is obvious over the combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations. After considering the properly presented evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that the combination of Conlon, Miller, and Fong teaches the limitations in claim 43, that one of ordinary skill in the art would have been motivated to combine the teachings of Conlon, Miller, and Fong, and that claim 44 would have been obvious over Conlon, Miller, and Fong. 2. Analysis of Dependent Claims 44–46 Claims 44–46 depend, directly or indirectly, from claim 41. We, likewise, determine whether the combination renders obvious claims 44–46, taking into account the arguments made in Petitioner’s Reply Briefs and Dr. Jansen’s Supplemental Rebuttal Declarations. Petitioner contends that dependent claims 44–46, would have been obvious over Conlon, Miller, and Fong, and provides explanation as to how the prior art teaches each claim limitation. Pet. 84–86; Reply 35–39; Pet. Remand Br. 13–14. Patent Owner does not provide further briefing on dependent claims 44–46. 14 Available at https://www.uspto.gov/patents/ptab/trial-practice-guide#step2. Patent Owner did not specifically challenge Petitioner’s contentions as” slip op. at 31

  • Strike new argumentNew argument disregardedDecided for petitioner

    “Patent Owner’s arguments do not undermine Petitioner’s showing. Patent Owner did not specifically challenge Petitioner’s contentions as to the sufficiency of Conlon’s disclosure for claim 1410 in the Patent Owner Response. In the Sur-replies, Patent Owner argues that the claim requires that at least some relationships are created “automatically,” and “these automatic embodiments . . . are represented in this group of claims.” Sur-reply 9. Along these lines, in the additional briefing Patent Owner argues that Conlon does not teach “automatic,” but merely teaches “semi-automatic.” PO Remand Br. 9–10. The crux of Patent Owner’s argument, however, is that the Federal Circuit did not properly construe the limitation, and ignored certain disclosures in the ’433 (and ’680) patent. Id. at 10–11; see Pet. Remand Resp. Br. 1–4; PO Remand Resp. Br. 4–5. The Federal Circuit held that “the dictionary routine claims can be satisfied by mere use of a lexical database, and do not also require the automatic creation of additional definitions.” Appeal Dec. 10. Moreover, the statements from Conlon that Patent Owner relies upon relate to creating a database, not using the database. See id. As discussed above, on remand we are directed to apply the Federal Circuit’s construction. Patent Owner does not explain 10 As discussed in the original Final Written Decisions, Patent Owner raised several arguments that generally applied to all the claims, challenging, for example, the level of ordinary skill in the art, whether Conlon, Miller, and Beckwith were analogous art, and several general arguments relating to Conlon and the motivation to combine Conlon with a DBMS. See Final Dec. 14–23, 25–27. We were not persuaded by Patent Owner’s arguments; the Federal Circuit affirmed, determining that our findings were supported by substantial evidence. Appeal Dec. 14–16. why Petitioner’s contentions are not persuasive in light of the Federal Circuit’s construction of this limitation. In addition, Patent Owner argues in the Sur-replies that “[c]laims 14– 19 are not disclosed by the proffered prior art” and cites to paragraphs 78–83 of the Ranka Rebuttal Declarations. Sur-reply 10. As discussed in the original Final Written Decisions, Patent Owner’s reliance on six paragraphs of Dr. Ranka’s Rebuttal Declarations is an improper incorporation by reference, as Patent Owner did not discuss that testimony or further elaborate on these arguments in the Sur-replies. 37 C.F.R. § 42.6(a)(3); Cisco Systems, Inc. v. C-Cation Techs., LLC, IPR2014-00454, Paper 12 at 9–10 (PTAB Aug. 29, 2014) (informative); see, e.g., Final Dec. 37–39, 45, 48–50, 52. Therefore, we will not consider arguments that are not made in the Sur-replies, but are instead improperly incorporated by reference to the cited paragraphs in Dr. Ranka’s Rebuttal Declarations. Accordingly, after considering the evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that Conlon teaches limitation [14.3], and that claim 14 would have been obvious over Conlon.” slip op. at 21

  Patent outcomesUS 6,665,680 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,665,680
• Orca Security Ltd. v. Wiz, Inc.Instituted
  PTAB · Dec 15, 2025 · IPR2025-01084 · APJ Nabeel U Khan · IPR · Institution

  Instituted IPR on claims 1–29 over Ross, Agarwal, and Biran because Petitioner showed a reasonable likelihood of prevailing on at least one challenged claim.

  RulingsInstitution decision

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

    “An inter partes review may not be instituted “unless . . . the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has demonstrated a reasonable likelihood of prevailing on at least one of the challenged claims of the ’896 patent. We institute inter partes review as to all the challenged claims of the ’896 patent on all the grounds of unpatentability set forth in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person of ordinary skill in the art (POSITA) “would have had a bachelor’s degree in an academic area emphasizing computer science (i.e., computer science, computer information systems, computer engineering, etc.) or cybersecurity and (2) at least two years of work experience with cybersecurity and cloud computing.” Pet. 5 (citing Ex. 1003 ¶ 53–54). Petitioner further argues that “[a]dditional education or experience might substitute for the above requirements.” Id. Patent Owner does not contest Petitioner’s proposed definition of a POSITA at this stage of the proceeding. See generally, Prelim. Resp. ordinary skill because it is consistent with the level of skill in the art at the time of the invention as reflected by the ’896 patent and the cited prior art.” slip op. at 7

  • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner

    “1[Pre] A method for generation of unified graph models for network entities, comprising: Petitioner contends that the preamble is not limiting, but to the extent by teaching the remaining limitations of the claim which are the steps in generating unified graph models for network entities, as the preamble recites. Pet. 9–10. Patent Owner does not dispute Petitioner’s contentions. At this stage of the proceeding, we agree with Petitioner that the preamble is not limiting because it merely states the purpose or intended use of an invention and because none of the subsequent limitations rely upon the preamble for completeness or antecedent basis. See Catalina Marketing Int’l., Inc. v. Coolsavings.com, Inc., 289 F.3d 801, 808 (Fed. Cir. 2002); Bicon, Inc. v. Straumann Co., 441 F.3d 945, 952 (Fed. Cir. 2006); In re Hirao, 535 F.2d 67 (CCPA 1976).” slip op. at 14

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

    “sufficiently established a motivation to combine Ross, Agarwal, and Biran in the manner proposed. For example, Petitioner contends for limitation 1[b] that a POSITA would have been motivated to implement Ross’s system to genericize network entities as taught by Agarwal and that Agarwal provides an express motivation to do so, explaining that “[t]he grouping of nodes can be helpful when attempting to understand system properties in a cloud environment, like availability, security and performance, where the system includes a large number of nodes.” Pet. 21 (citing Ex. 1005, 4:13–26, 13:21–27; Ex. 1003 ¶¶ 103–108). Similarly, for limitation 1[d] Petitioner argues that “Biran provides express motivation to implement Ross to gather information on host-less components . . . to generate an accurate, service-aware view of the system infrastructure.” Id. at 32 (citing Ex. 1006, 1:59– 61; Ex. 1003 ¶¶ 134–136). These disclosures demonstrate that Petitioner’s motivation to combine stems from the prior art references themselves rather than from hindsight. Moreover, Petitioner’s contentions are supported by credible testimony from Dr. Easttom. See Ex. 1003 ¶¶ 103–108, 122–123, Addressing a motivation to combine on a limitation-by-limitation basis, as Petitioner has done in its Petition, is not necessarily improper, and may in fact be more suitable in certain situations depending on the proposed combination. Patent Owner does not provide any authority supporting its contention that providing a motivation to combine in the manner asserted in the Petition is contrary to proper obviousness analysis under Graham.” slip op. at 25

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,929,896
• Orca Security Ltd. v. Wiz, Inc.Instituted
  PTAB · Dec 15, 2025 · IPR2025-01087 · APJ Lisa A Murray · IPR · Institution

  The Board instituted IPR on claims 1–17 because Orca showed a reasonable likelihood of prevailing on its § 103 obviousness ground over Shua and Lang.

  RulingsInstitution decision

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

    “An inter partes review may be instituted only if “the information presented in the petition . . . and any [preliminary] 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 given below, on this record, Petitioner has established a reasonable likelihood that it would prevail in showing the unpatentability of at least one of the challenged claims. We determine that institution of an inter partes review of the challenged claims is appropriate. B. Real Parties in Interest” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “35 U.S.C. § 103 involves determining the level of ordinary skill in the pertinent art at the time the invention was made. Graham, 383 U.S. at 17. The level of skill in the art is “a prism or lens” through which we view the prior art and the claimed invention. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). The person of ordinary skill in the art is a hypothetical person who knows the relevant art. In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995). Factors to consider include the types of problems encountered in the art, the sophistication of the technology, and the educational level of active workers in the field. Id. One or more factors may predominate. Id. Petitioner asserts that one of ordinary skill in the field of the ’529 Patent would have had “a bachelor’s degree in computer engineering, computer science, electrical engineering, or a similar degree, with 2–3 years additional education or experience might substitute for these requirements.” Pet. 5; Ex. 1003 ¶¶ 32–33. Patent Owner’s Preliminary Response does not address this issue. We find Petitioner’s formulation to be consistent with the evidence of record at this stage of the proceedings, including the asserted prior art and the ’529 Patent, and we preliminarily adopt and apply that definition for purposes of this Decision. C. Claim Construction” slip op. at 6

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther

    “Owner contends that Petitioner’s argument “inverts the appropriate understanding: just because the challenged patent identifies an example security database that stores a representation of a computing environment as nodes and edges does not mean that anything that stores a representation of a computing environment as nodes and edges is necessarily a security database.” Prelim. Resp. at 7–8. We agree with the logic of Patent Owner’s argument, but disagree that Petitioner necessarily “relies on this inverted understanding for its prior art mapping.” Id. at 8. We understand Dr. Zadok’s explanation to mean only that the claim term “security database” encompasses graph databases that include a representation of the computing environment, meaning that some (but not necessarily all) security databases are graph databases. See Ex. 1003 ¶ 100. The language in the Petition to which Patent Owner objects can be read consistently with Dr. Zadok’s declaration. Petitioner does not, however, take a position on what the outer bounds of the claim term “security database” should be. Without attempting a full construction of the term “security database,” it is possible to determine from the current record, at least on a preliminary basis, some of the database types that would fall within its scope. The ’529 Patent explains that the claimed “security database” is part of an “inspection cybersecurity threats. Specifically, it provides as follows: In certain embodiments, the cloud computing environment 110 is monitored for cybersecurity objects, threats, risks, and the like, by an inspection environment 130. In an embodiment, the inspection environment 130 is configured to monitor the cloud computing environment 110 for cybersecurity objects, threats, risks, combinations thereof, and the like. Ex. 1001, 6:1–7; see id. Fig. 1. The ’529 Patent also provides: “In an embodiment, the inspection environment 130 further includes a security database 136. In some embodiments, the security database 136 is configured to store a representation of the cloud computing environment 110, for example based on a predetermined data schema.” Id. at 7:46–50. Thus, we can conclude that the term “security database,” as used in the ’529 Patent, encompasses at least a database within an inspection environment that monitors for cybersecurity threats and is configured to store a representation of a cloud computing environment that is monitored by the inspection environment. An example of such a security database is the Neo4j® graph database. Id. at 7:58–60. As discussed below, another example is the “context map” disclosed in Shua ’048. See Ex. 1005, 15, 25.” slip op. at 19

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

    “We find nothing contradictory in Petitioner’s argument that “100% of an organization’s assets” would include its AI models. Pet. 11, 21. Shua ’048 appears to contemplate treating multiple layers of structures as assets to be mapped and monitored. Ex. 1005 ¶ 30 (Shua’s Orca system “automatically assesses the security state of discovered asset[s] throughout the technology stack, including all four cloud layers: I/S, OS, apps, and data.”). On the current record, a VM is an asset that contains other assets, including an AI model.10 We conclude that for the purposes of institution, Petitioner’s mapping, as elucidated by Dr. Zadok, adequately demonstrates that the combination of Shua and Lang discloses limitation 1[c] and the corresponding limitations in claims 9 and 10. We further conclude that Petitioner’s identification of a motivation to combine Shua with Lang is adequate for institution purposes.” slip op. at 23

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 12,003,529
• Orca Security Ltd. v. Wiz, Inc.Instituted
  PTAB · Dec 15, 2025 · IPR2025-01085 · APJ Karl D Easthom · IPR · Institution

  The Board instituted IPR on claims 1–21, finding a reasonable likelihood of prevailing on both § 103 grounds: Calvo and Nguyen, and Calvo, Nguyen, and Datsenko.

  RulingsInstitution decision

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

    “presented in a petition and preliminary 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 explained below, we determine that Petitioner establishes a reasonable likelihood that it would prevail with respect to at least one challenged claim. Accordingly, we institute an inter partes review as to the challenged claims and the grounds raised in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner contends that a person of ordinary skill in the art (POSITA) at the time of the ’693 Patent would have had a bachelor’s degree in computer engineering, computer science, electrical engineering, or a similar degree, with at least two years of experience in the field of cybersecurity; additional education or experience might substitute for these requirements. Pet. 7 (citing Ex. 1003 ¶¶ 63–64). Patent Owner does not provide a level of ordinary skill in the art. See generally Prelim. Resp. Based on a review of the record, we adopt Petitioner’s proposed level of ordinary skill in the art because it is consistent with the evidence of record, including the asserted prior art and ’693 patent specification.” slip op. at 6

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

    “support a construction that is similar to Petitioner’s construction of a “network path” as “a link between two machines.” See Pet. 17. That is, limitation 1(a) recites “selecting a reachable resource having a network path to access the reachable resource, wherein the reachable resource is a cloud object . . . having access to an external network which is external to the cloud computing environment,” and limitation 1(b) recites “actively inspecting the network path to determine if the network path of the reachable resource is accessible from the external network.” This plain language shows that a network path is simply a connection (link) between an external network object and a resource in a cloud (or cloud object). The specification provides an example of accessing “port 22”: “Active inspection allows to [sic] generate instructions directed at the reachable resource over a network path, which when received by the reachable resource cause the reachable resource to send a response.” Ex. 1001, 5:40–45. The specification also states that “a network path may include sequential representations of possible data/control flows between two or more objects in a graph.” Ex. 1001, 12:49–52; accord Ex. 1001, 12:60–62 (describing “a path show[ing] a connection between security objects and/or computing objects that communicate over a network”), 12:42–44 (“A network path is a connection of two or more security objects accessible from an external or internal network, and/or an external or internal object.”). In other words, the specification indicates that a transmitting testing object may be an object external to the cloud connected via a network path to another object (a cloud resource for testing). The “network path” may also include resources/objects (represented as graph vertices) on the path. See id. at 12:51–59 (“A path may be a vertexonly path, describing a sequence of vertex-to-vertex ‘hops,’ an edge-only path, describing only the edges included in the sequence without description of the associated vertices, or a combined edge-vertex path, describing both edges and vertexes included in the sequence.” (emphasis added)). Accordingly, for purposes of institution, we construe a “network path” as “a connection between an external object and a cloud resource, wherein the connection itself include objects and/or cloud resources.”” slip op. at 9

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

    “4. Remaining Terms No express construction of any other claim term is necessary to determine whether to institute inter partes review. 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))). D.” slip op. at 12

  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,936,693
• Arashi Vision (U.S.) LLC (D/B/A Insta360) v. Gopro, IncNo claims unpatentable
  PTAB · Nov 25, 2025 · IPR2024-01165 · APJ William V Saindon · IPR · Final written decision

  Claims 1–21 were not shown unpatentable because Zhou does not teach the claimed low-light high-pass or stickiness parameter limitations.

  RulingsFinal written decision

  • BurdenFwd all claims patentableNot shown unpatentable

    “4. Conclusion for the Prior Art Analysis In sum, we find that Zhou does not disclose the low-light high-pass parameter or the stickiness parameter. Petitioner’s grounds for both independent claims 1 and 16 rely on Zhou for teaching a low-light high-pass parameter or a stickiness parameter. Pet. 23–28, 64. Because we find Zhou does not teach these limitations, all of Petitioner’s grounds fall for this reason. III. CONCLUSION For the reasons given above, we determine that Petitioner has not established by a preponderance of the evidence that any claim of the ’840 patent would have been obvious in view of the prior art cited.” slip op. at 18

  • Skill levelSkill level petitioner adoptedOther

    “A person of ordinary skill in the art (POSITA) in the field of the ’840 patent would have a bachelor’s degree in engineering or computer science, or equivalent field, and two years of experience working on image or video processing, or digital cameras. Alternatively, a POSITA would have four years of experience working on image or video processing, or digital cameras. An advanced graduate degree in the disciplines cited above may make up for the work experience indicated above. Pet. 6 (citing Ex. 1002 ¶ 32). Patent Owner applies the same standard. PO Resp. 26–27. We use this agreed-upon standard for purposes of this Decision.” slip op. at 7

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “We review this testimony based on the strength of the underlying factual basis. 37 C.F.R. § 42.65(a); Ashland Oil, Inc. v. Delta Resins & Refractories, Inc., 776 F.2d 281, 294 (Fed. Cir. 1985) (“Lack of factual support for expert opinion going to factual determinations, however, may render the testimony of little probative value . . ..”). Here, the underlying factual basis is not very strong for either witness. That said, we find that Dr. Foroosh’s testimony is more logically sound and consistent with the ’840 patent disclosure. Based on our reading of the specification, we find a clear indication that “stickiness” has to do with the past. In order to control “the extent by which preceding portion(s) . . . impacts determination of the smoothed trajectory” (emphasis added), one must control the degree by which the past frames impact determination. And to control the degree of the past’s influence, one must, as a consequence, favor the past over the future. That is, the frame of reference of the stickiness parameter is the past. The specification could have used a time-agnostic term, like a “nearness” or “adjacency” parameter, but it did not. Thus, the fact that “stickiness” is used in conjunction with “preceding” indicates that it deals with a preference for preceding frames. On this basis, we find Dr. Katsaggelos’s testimony less persuasive than Dr. Foroosh’s.” slip op. at 10

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

    “That said, we do not construe a stickiness parameter as prohibiting consideration of future frames. Instead, we determine that the stickiness parameter’s value determines the impact of the preceding portions, versus the following portions. The ’840 patent recognizes this, when it says that a stickiness parameter value of “1,” representing a “lazy” stabilizer that maximally favors the past, would not override a violation of the margin constraint based on the look-ahead (i.e., would not allow the viewing window to fall out of bounds in the event of large future motion). See Ex. 1001, 22:26–30; see also id. at 12:61–13:29 (acknowledging that favoring the past may lead to a conflict with the viewing window determination), 15:39–60 (adjusting the viewing window to ensure it does not violate a margin constraint). Thus, while a past-favoring parameter by necessity favors the past over the future, it does not prohibit consideration of the future. In view of the above, we construe the claimed “stickiness parameter” as a parameter that controls the extent by which preceding portions of the trajectory impacts determination of the smoothed trajectory, with an understanding that in order to favor preceding portions, to some extent, the parameter must relatively disfavor following portions.” slip op. at 10

  Patent outcomesUS 10,958,840 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,958,840
• Microsoft Corporation v. Edge Networking Systems, LLCInstituted
  PTAB · Sep 30, 2025 · IPR2025-00618 · APJ Nabeel U Khan · IPR · Institution

  The Board instituted IPR on claims 1–5, 7, 8, 12–15, 18, and 19 on both § 103 grounds, finding a reasonable likelihood that at least one claim under each ground is unpatentable.

  RulingsInstitution decision

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

    “An inter partes review may not be instituted “unless . . . the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has demonstrated a reasonable likelihood of prevailing on at least one of the challenged claims of the ’823 patent. We institute inter partes review as to all the challenged claims of the ’823 patent on all the grounds of unpatentability set forth in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person of ordinary skill in the art (POSITA) “would have had a bachelor’s degree in computer science, computer engineering, or equivalent degree, and approximately three years of experience working in the computer science or engineering field.” Pet. 12 (citing Ex. 1003 ¶ 58). Petitioner further argues that “[a]dditional experience might substitute for less education and vice versa” and that “POSITAs in June 2013 would have been knowledgeable about the design and management of networked systems and virtualization technologies, and techniques.” Id. Patent Owner “does not contest Petitioner’s proposed definition” of a POSITA at this stage of the proceeding. Prelim. Resp. 17. For purposes of this Decision, we adopt Petitioner’s proposed level of ordinary skill because it is consistent with the level of skill in the art at the time of the invention as reflected by the ’823 patent and the cited prior art.” slip op. at 6

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

    “given its plain and ordinary meaning in this proceeding, and that no specific claim construction of any claim term is required.” Pet. 10. Petitioner explains that the parties have proposed “different constructions for various claim terms pending in the Related Litigation” but that the Grounds “render the claims unpatentable under either party’s construction, and any reasonable construction, and thus the Board need not construe any term.” Id. at 10–11 (citing Ex. 1003 ¶ 367; Ex. 1070; Ex. 1071).2 Patent Owner does not expressly address claim construction in its Preliminary Response. We determine that, at this stage of the proceeding, no explicit constructions are required to resolve the dispute between the parties. A final determination as to claim construction will be made at the close of the proceeding, after any hearing, based on all the evidence of record. The parties are expected to assert all their claim construction arguments and evidence in the Petition, Patent Owner’s Response, Petitioner’s Reply, Patent Owner’s Sur-reply, or otherwise during trial, as permitted by our rules.” slip op. at 8

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundInstituted

    “E. Combination of Vasell, Alves, Rellermeyer, and Hall As explained above, Petitioner contends that the technical implementation details that were intended to implement Vasell’s teachings are described in Alves, Rellermeyer, and Hall. Pet. 36. Petitioner argues, therefore, that the motivation to modify Vasell to include features described in the other references is demonstrated by the references themselves. Id. at 36–37 (citing Ex. 1003 ¶¶ 375–376). For example, according to Petitioner, a POSITA would have been motivated to modify Vasell with Alves’ teaching of a centralized application repository for storing its distributed applications to provide increased scalability. Id. at 38, 39 (citing Ex. 1008, 263, 266; Ex. 1003 ¶¶ 378–379). Petitioner contends that a POSITA would have been motivated to modify Vasell with Rellermeyer’s management software to provide for load balancing, failover and elastic scalability. Id. at 38 (citing Ex. 1003 ¶ 380). Finally, Petitioner argues that a POSITA would have been motivated to modify Vasell with Hall’s management software that requires digital signatures for distributed applications to provide increased security for using third party applications. Id. at 38, 39 (citing Ex. 1003 ¶ 381). Patent Owner does not separately dispute Petitioner’s contention that a POSITA would have been motivated to combine Vasell, Alves, Rellermeyer, and Hall. to combine the prior art references and determine that Petitioner has established a reasonable likelihood that a person of ordinary skill in the art would have combined Vasell, Alves, Rellermeyer, and Hall with a reasonable expectation of success for the reasons provided by Petitioner.” slip op. at 12

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,695,823
• Microsoft Corporation v. Edge Networking Systems, LLCInstitution denied
  PTAB · Sep 30, 2025 · IPR2025-00619 · APJ Jason M Repko · IPR · Institution

  The Board denied institution because Microsoft did not show a reasonable likelihood of proving claims 1, 2, 4–7, and 9 obvious over Vasell, Alves, Hall, and Rellermeyer.

  RulingsInstitution decision

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

    “To institute an inter partes review, we must determine “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 discussed below, Petitioner has not shown a reasonable likelihood that it would prevail with respect to any claim challenged in the Petition. Thus, we do not institute an inter partes review.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “[Persons of ordinary skill in the art (“POSITAs”)] as of June 2013 would have had a bachelor’s degree in computer science, computer engineering, or equivalent degree, and approximately three years of experience working in the computer science or engineering field. Additional experience might substitute for less education and vice versa. To that end, POSITAs in June 2013 would have been knowledgeable about the design and management of networked systems and virtualization technologies, and familiar with operating/distributed systems and security and privacy techniques. Pet. 15 (citing Ex. 1003 ¶ 58).4 Patent Owner does not contest this in its Preliminary Response. Prelim. Resp. 36–37. We apply Petitioner’s definition of the level of ordinary skill in the art here.” slip op. at 5

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

    “Petitioner has not sufficiently explained how the combination of Vasell, Alves, Hall, and Rellermeyer teaches or suggests a programmable network device and a programmable cloud device that are each “powered by a sandboxing operating system,” as required by all challenged claims. Our reasoning follows.” slip op. at 10

  § 103 obviousness
  Patents in suitUS 10,686,871
• Microsoft Corporation v. Edge Networking Systems, LLCInstitution denied
  PTAB · Sep 30, 2025 · IPR2025-00617 · APJ Jason M Repko · IPR · Institution

  The Board denied institution because Microsoft did not show a reasonable likelihood of proving claims 1, 2, 6–8, 10–13, and 15 obvious over Vasell, Alves, Hall, and Rellermeyer.

  RulingsInstitution decision

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

    “To institute an inter partes review, we must determine “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 discussed below, Petitioner has not shown a reasonable likelihood that it would prevail with respect to any claim challenged in the Petition. Thus, we do not institute an inter partes review.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “[Persons of ordinary skill in the art (“POSITAs”)] as of June 2013 would have had a bachelor’s degree in computer science, computer engineering, or equivalent degree, and approximately three years of experience working in the computer science or engineering field. Additional experience might substitute for less education and vice versa. To that end, POSITAs in June 2013 would have been knowledgeable about the design and management of networked systems and virtualization technologies, and familiar with operating/distributed systems and security and privacy techniques. Pet. 14 (citing Ex. 1003 ¶ 59).4 Patent Owner does not contest this in its Preliminary Response. Prelim. Resp. 39. We apply Petitioner’s definition of the level of ordinary skill in the art here. 2 Congress amended § 103 when it passed the Leahy-Smith America Invents Act (AIA). Pub. L. No. 112–29, § 3(c), 125 Stat. 284, 287 (2011). Petitioner asserts that the version amended by the AIA applies here. Pet. 23. 3 We use Petitioner’s nomenclature in which Petitioner collectively refers to the Vasell patent (Ex. 1004) and its corresponding provisional applications (Exs. 1015, 1016) as “Vasell.” 4 Erez Zadok, Ph.D. submitted a declaration on behalf of Petitioner. See Ex. 1003.” slip op. at 5

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

    “Petitioner has not sufficiently explained how the combination of Vasell, Alves, Hall, and Rellermeyer teaches or suggests a programmable network device and a programmable cloud device that are each “powered by a sandboxing operating system,” as required by all challenged claims. Our reasoning follows.” slip op. at 10

  • BurdenNot shown unpatentable

    “Petitioner has not sufficiently explained how the combination of Vasell, Alves, Hall, and Rellermeyer teaches or suggests a programmable network device and a programmable cloud device that are each “powered by a sandboxing operating system,” as required by all challenged claims. Our reasoning follows.” slip op. at 10

  § 103 obviousness
  Patents in suitUS 10,893,095
• Jumio Corporation v. Facetec, Inc.Instituted
  PTAB · Jun 9, 2025 · IPR2025-00107 · APJ Garth D Baer · IPR · Institution

  The Board instituted IPR of claims 1–20 on all petitioned grounds, finding a reasonable likelihood that at least one challenged claim would be unpatentable.

  RulingsInstitution decision

  • PTAB / AIA Trials › §315(b) time barDecided for patent owner

    “interest to this proceeding and is in privity with Petitioner and that the Petition is time-barred under 35 U.S.C. § 315(b) because it served iProov 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284, 285–88 (2011), amended 35 U.S.C. §§ 102, 103, effective March 16, 2013. Because the challenged patent claims the benefit of applications filed after this date, the post-AIA version of §§ 102, 103 apply. Ex. 1001, codes (22), (60), (63). with a complaint for infringement of the ʼ606 patent more than one year before this Petition was filed. Prelim. Resp. 5–22. We addressed this same issue in our institution decision in IPR2025-00106. See IPR2025-00106, Paper 17 at 16–27. For the reasons we explained there, we do not agree that this Petition is not time-barred under 35 U.S.C. 315(b).” slip op. at 6

  • Other 314aDecided for petitioner

    “B. Discretionary Denial under § 314(a) Patent Owner argues the Board should exercise its discretion to deny institution under 35 U.S.C. § 314(a) in light of two co-pending district court cases. Prelim. Resp. 47–56. We addressed this same issue in our institution decision in IPR2025-00106. See IPR2025-00106, Paper 17 at 6–9. For the same reasons we explained there, we decline to exercise our discretion to deny institution based on the related district court cases.” slip op. at 7

  • PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner

    “C. Discretionary Denial under § 325(d) Patent Owner argues we should deny institution under 35 U.S.C. § 325(d) because Petitioner’s asserted references are the same or substantively as those the Office previously considered during prosecution. Prelim. Resp. 22–36. We addressed this same issue in our institution decision in IPR2025-00106. See IPR2025-00106, Paper 17 at 9–16. For the same reasons we explained there, we decline exercising our discretion to deny institution under § 325(d).” slip op. at 7

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

    “D. Claim Construction Neither party proposes an express construction for any claim terms. Pet. 5–6; see generally Prelim. Resp. We agree that no claim terms require express construction to determine whether to institute inter partes review. 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 7

  Claim construction§ 103 obviousnessDiscretionary denialcites KSR
  Patents in suitUS 11,157,606
• Jumio Corporation v. Facetec, Inc.Instituted
  PTAB · Jun 9, 2025 · IPR2025-00109 · APJ Bach V Hoang · IPR · Institution

  The Board instituted IPR on claims 1–24 and all asserted grounds after finding a reasonable likelihood that claim 1 was obvious over Derakhshani and Tanii.

  RulingsInstitution decision

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

    “3. Institution of Inter Partes Review As discussed above, at this stage in the proceeding, we determine Petitioner has established a reasonable likelihood that the combination of Derakhshani and Tanii teaches the limitations of claim 1 and a reasonable likelihood that Petitioner will prevail in demonstrating that claim 1 is unpatentable as obvious over Derakhshani and Tanii. Because we are persuaded that Petitioner has shown a reasonable likelihood of prevailing in demonstrating that the subject matter of claim 1 would have been obvious over Derakhshani, alone or combined with Tanii, we institute an inter partes review of all claims and all challenges raised in the Petition. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 365 (2018) (stating 35 U.S.C. § 314 “simply requires [the Director] to decide whether the petitioner is likely to succeed on ‘at least 1’ claim. Once that single claim threshold is satisfied, it doesn’t matter whether the petitioner is likely to prevail on any additional claims; the Director need not even consider any other claim before instituting review.”); 37 C.F.R. § 42.108(a).” slip op. at 22

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “Patent Owner acknowledges that, in this IPR, “the time-bar is not implicated.” Prelim. Resp. 5–6. Nevertheless, Patent Owner argues that we should reach the RPI question here because other IPRs challenging different patents implicate the time bar under 35 U.S.C. § 315(b). Id. at 5–6. Patent Owner’s request effectively asks us to extend the § 315(b) time bar to implicate patents not asserted in an applicable infringement complaint. We decline to do so. The plain language of § 315(b) does not extend the time bar to any patent other than the patent subject to the instant petition: An inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner, real party in interest, or privy of the petitioner is served with a complaint alleging infringement of the patent (emphasis added). Nor are we aware of any other authority which requires us to interpret § 315(b) to extend the time bar to patents other than the challenged one. Because Patent Owner admits this Petition challenging the ’910 Patent is not time barred, the treatment in SharkNinja controls. Accordingly, on this record, we need not consider whether iProov must be named as an RPI and decline to deny institution under 35 U.S.C. § 312(a)(2).” slip op. at 3

  • PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Denied

    “A. 35 U.S.C. § 314(a) Patent Owner argues the Board should exercise its discretion to deny institution under 35 U.S.C. § 314(a) in light of two co-pending district court decision in IPR2025-00106. See IPR2025-00106, Paper 17 at 6–9. For the same reasons we explained there, we decline to exercise our discretion to deny institution based on the related district court cases.” slip op. at 8

  • PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsInstitution denied 325dDenied

    “B. 35 U.S.C. § 325(d) Patent Owner argues we should deny institution under 35 U.S.C. § 325(d) because Petitioner’s asserted references are the same or substantively as those the Office previously considered during prosecution. Prelim. Resp. 18–33. We addressed this same issue in our institution decision in IPR2025-00106. See IPR2025-00106, Paper 17 at 9–16. For the same reasons we explained there, we decline exercising our discretion to deny institution under § 325(d).” slip op. at 9

  § 103 obviousnessDiscretionary denialcites KSR · Graham
  Patents in suitUS 11,874,910

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.