• Microsoft Corporation v. Edge Networking Systems, LLCAdverse judgment
  PTAB · Mar 25, 2026 · IPR2025-00618 · APJ Nabeel U Khan · IPR · Adverse judgment

  After Patent Owner disclaimed all challenged claims, the Board entered adverse judgment against Patent Owner under 37 C.F.R. § 42.73(b)(2).

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentOther

    “Our rules state that “disclaimer of a claim such that a party has no remaining claim in the trial” is “construed to be a request for adverse judgment.” 37 C.F.R. § 42.73(b). Because Patent Owner has disclaimed all challenged claims and no claims remain in this proceeding, adverse judgment is appropriate. We, therefore, enter judgment adverse to the Patent Owner.” slip op. at 2

  None
  Patents in suitUS 11,695,823
• 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
• Google LLC v. Mindbasehq, LLCAll claims unpatentable
  PTAB · Mar 16, 2026 · IPR2021-01251 · APJ Kara L Szpondowski · IPR · Remand

  On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious over Conlon alone or Conlon, Miller, and Fong; the affirmed unpatentability of claims 1–13, 20–32, 41, and 42 remains.

  RulingsRemand decision

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

    “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 successMotivation foundReasonable expectation foundUnpatentable

    “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.” slip op. at 31

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “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.” slip op. at 32

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

    “4. Summary of Ground 1 Having considered the Graham factors,11 including the level of ordinary skill in the art, the scope and content of the prior art, and the differences between the prior art and the challenged claims, we are persuaded, based on the current record, that Petitioner has shown, by a preponderance of the evidence, that claims 14–19 and 33–40 would have been obvious over Conlon.” slip op. at 24

  Patent outcomesUS 6,510,433 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,510,433
• Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentable
  PTAB · Feb 6, 2026 · IPR2024-01340 · APJ Terrence W Mcmillin · IPR · Final written decision

  Claims 1–12 and 14–18 are unpatentable as obvious over Whitehead, alone or with Marcus ’904; claims 13 and 19–24 were not shown unpatentable.

  RulingsFinal written decision

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

    “establishes that the subject matter of independent claim 19 would have been obvious in view of Whitehead. Claim 19 recites “an aggregator having a memory and a processor, the processor adapted for . . . providing an output signal including data indicative of the selection and of user data.” Ex. 1001, 15:51–16:3. As discussed above (Section II.C.2), we construe claim 19 as requiring a signal including both “data indicative of the selection and of user data.” Accordingly, we consider whether Petitioner has shown that Whitehead teaches or suggests that the “aggregator” “provid[e] an output signal including” both “data indicative of the selection and of user data.”” slip op. at 46

  • Expert testimonyOther

    “Cristofalo’s “user identifiers” represent data about users that Cristofalo’s system uses to “select a specific media object” (advertisements) from received “multi-object programming data.” Cristofalo at ¶ [0048]. For example, a user identifier may indicate that a given user is a Coca-Cola drinker, and when the receiving system receives the multi-object programming data it can select a particular media object out of several possible media objects (e.g., a Pepsi advertisement) to push to the user. Id. This user data exists independently of, and does not relate to, any particular media stream or streams. See Goodrich PO Resp. Decl. at ¶ 135. Petitioner seems to recognize this when tersely referring to “user identifiers” as “data,” not “data relating to a plurality of streams.” Pet. at 71. Accordingly, Cristofalo’s “user identifiers” are not the claimed “data related to the plurality of media streams.” Goodrich PO Resp. Decl. at ¶ 136.” slip op. at 73

  Patent outcomesUS 8,145,704 mixed
  § 103 obviousnesscites Graham
  Patents in suitUS 8,145,704
• Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentable
  PTAB · Jan 23, 2026 · IPR2024-01342 · APJ Terrence W Mcmillin · IPR · Final written decision

  Claims 1–4 and 6–10 are unpatentable as obvious over each asserted ground; claim 5 was not shown unpatentable because the petitions failed to establish its additional feed and time-period limitations.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “1b, 1c, and 1e of claim 1 and in claims 4 and 5 of the ’753 patent. Patent Owner contends that the plain and ordinary meaning of “feed” is “one or more associated media elements.” See, e.g., PO Resp. 4. However, as discussed below, this alleged plain and ordinary meaning of feed is not supported by the claim language, the specification of the ’753 patent, or dictionary definitions of feed as contended by Patent Owner. We reject this contention and the related contentions that the cited art may be distinguished from the claims of the ’753 patent based on the recited term “feed.” Patent Owner relies on the language of claim 1 to support its” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The parties’ definitions are similar, although we observe that Patent Owner proposes that the person of ordinary skill would have a bachelor’s degree or an equivalent or professional experience, whereas Petitioner proposes that such a person would have both a degree and experience. Neither party presents any arguments relating or referring to the level of ordinary skill in the art. Determining the level of ordinary skill in the art involves various factors, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The prior art of record also reflects the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt Petitioner’s assessment of the level of skill in the art. Petitioner’s assessment is supported by the testimony of Dr. Almeroth and is consistent with the ’753 patent and the asserted prior art. However, our obviousness analysis would be the same under either party’s assessment. See Ex. 2014 ¶ 17 (Patent Owner’s declarant, Dr. Goodrich, stating that “I note that my definition of a POSITA is similar to that of Dr. Almeroth” and “My opinions in this declaration would not change were I to adopt the definition of a POSITA offered by Dr. Almeroth.”).” slip op. at 11

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “16 With regard to claim 5, the Petition cites paragraphs 97 and 98 of the Almeroth Declaration (Ex. 1002). See Pet. 28–29. We have considered the cited paragraphs in the Almeroth Declatation and found that they consist of nothing more than the inadequate and conclusory contentions in the Petition preceded by, in paragraph 97, “[i]n my opinion” and “it is my opinion” and, in paragraph 98, “[i]t is also my opinion.” Ex. 1003 ¶¶ 97, 98. As related to claim 5, we accord the Almeroth Declaration little or no weight. See 37 C.F.R. § 42.65 (a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”). that might become out-of-date before a user accesses access [sic] them. Ex. 1003, 11:49–58 (emphasis added). The cited passage in Whitehead mentioning “near real-time” does not support finding that Whitehead teaches or suggests the elements recited in claim 5.” slip op. at 39

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

    “Petitioner contends, “[a] POSITA would have modified Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm (running on Marcus ’904’s receiver) for receiving, selecting, ordering, and assembling different media streams (both for content and advertising).” Pet. 33. Petitioner supports this contention by articulating the following reasons for the asserted modification of Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm: “makes it more likely the system will identify content best suited for a particular user,” “allows for more targeted advertising and/or an opportunity to maximize revenue,” “improves Whitehead’s ability to target content and advertising to a particular user,” “would unlock new revenue sources for Whitehead,” “Marcus ’904’s content selection and concatenation algorithm improves Whitehead’s efficiency,” “[b]oth Whitehead and Marcus ’904 generate custom media programming based on a user profile,” “incorporating Marcus ’904’s teachings would not require redesigning Whitehead’s architecture and instead merely supplements Whitehead’s disclosure,” and “Petitioner’s proposed modification can be implemented entirely in software and does not require any hardware modifications. Indeed, Whitehead acknowledges that such modifications are possible. EX1003 at 19:64-20:6, 22:26-40.” Id. at 33–35 (citing Ex. 1002 (Almeroth Decl.) ¶¶ 110–115) (emphasis omitted). Based on this undisputed showing, we find that one of ordinary skill would have had a motivation to combine the teachings of Whitehead and Marcus ’904 as asserted in the Petition with a reasonable expectation of success.” slip op. at 48

  Patent outcomesUS 8,886,753 mixed
  Claim construction§ 103 obviousnesscites Graham
  Patents in suitUS 8,886,753
• 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.Institution denied
  PTAB · Dec 15, 2025 · IPR2025-01083 · APJ Nabeel U Khan · IPR · Institution

  The Board denied institution because Petitioner did not show a reasonable likelihood that Shivamoggi disclosed the required natural-language list of abnormal connections, including for the dependent-claim grounds.

  RulingsInstitution decision

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

    “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 not demonstrated a reasonable likelihood of prevailing on at least one of the challenged claims of the ’554 patent. We do not institute inter partes review as to the challenged claims of the ’554 patent.” 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, with at least two years of experience in the field of cybersecurity.” Pet. 6 (citing Ex. 1003 ¶ 49). Petitioner further argues that “additional education or experience might substitute for these requirements.” Id. Patent Owner does not contest Petitioner’s proposed definition of a POSITA at this stage of the proceeding. See generally, Prelim. Resp. 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 ’554 patent and the cited prior art.” slip op. at 7

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

    “Petitioner asserts that “no claim terms need to be construed to resolve any issues in controversy in the Petition.” Pet. 7 (citing Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011)). Patent Owner asserts that “[n]o constructions are necessary to deny institution because denial is warranted for numerous reasons that do not depend on claim construction, as further detailed below.” Prelim. Resp. 2. We determine that, at this stage of the proceeding, no explicit constructions are required to resolve the dispute between the parties.” slip op. at 8

  • BurdenNot shown unpatentable

    “Having reviewed the record presently before us, we agree with Patent Owner. Limitation 1[d] requires generating “insights, wherein the generated insights include at least a list of abnormal connections between the identified network objects.” The ʼ554 patent states that “[n]etwork insights are natural-language representations of aspects of the network graph.” 1 Ex. 1001, 10:15–17. Petitioner acknowledges that the recited “insights” are “natural-language representations.” Pet. 26 (citing Ex. 1001, 10:16–18). Dr. Easttom also agrees that insights are natural-language representations. Ex. 1003 ¶ 100 (testifying that “Shivamoggi’s insights are provided to the user as textual descriptions (i.e. natural-language representations).”). As an 1 The parties do not address whether the “wherein” clause of limitation 1[d] runs afoul of the printed matter doctrine. “[T]he petition must set forth . . . . [h]ow the challenged claim is to be construed.” 37 C.F.R. § 42.104. Even though “insights” are described in the ʼ554 patent as “natural-language representations of aspects of the network graph” (Ex. 1001, 10:15–17), Petitioner does not construe “insights, wherein the generated insights include at least a list of abnormal connections between the identified network objects,” as “printed matter” that may be disregarded because it is “not functionally related to the substrate.” See Praxair Distribution, Inc. v. Mallinckrodt Hosp. Prods. IP Ltd., 890 F.3d 1024, 1032 (Fed. Cir. 2018) (“‘Where the printed matter is not functionally related to the substrate, the printed matter will not distinguish the invention from the prior art in terms of patentability.’. . . For example, in In re Ngai, 367 F.3d 1336, 1339 (Fed. Cir. 2004) there was no functional relationship between claimed instructions and a diagnostic kit, as the instructions ‘in no way depend[ed] on the kit, and the kit [did] not depend on the’ instructions.” (quoting Ngai, 367 F.3d 1336, 1339 (Fed. Cir. 2004)). Because the parties have not addressed it, we decline to consider if the printed matter doctrine applies here. “virtual machine one to load balancer five, where port eighty is routed to port 1337 on virtual machine one, then from load balancer five to firewall two, where port eighty of firewall two is open, then from firewall two to subnet sixteen, where subnet sixteen has a network address of 10.0.1.0/24, then from subnet sixteen virtual network ten, where virtual network ten has a network address of 10.0.0.0/16, then from virtual network ten to virtual network eleven, via peering connection twelve, where peering connection twelve includes a routing rule to virtual network twelve, specifying virtual network twelve's network address, where virtual network twelve's network address is 172.31.0.0/16.” Ex. 1001, 10:31–45 (quotation marks in original). This example illustrates that an insight is provided in natural-language, or textual, format, consistent with the description of an insight in the ʼ554 patent and the testimony of Dr. Easttom. The limitation, which recites “the generated insights include at least a list of abnormal connections,” therefore requires generating a naturallanguage representation of a list of abnormal connections.” slip op. at 18

  Claim constructioncites Phillips · KSR · Graham
  Patents in suitUS 11,722,554
• Orca Security Ltd. v. Wiz, Inc.Institution denied
  PTAB · Dec 15, 2025 · IPR2025-01086 · APJ Lisa A Murray · IPR · Institution

  The Board denied institution on all challenged claims because Orca did not show a reasonable likelihood of prevailing, based on its unexplained inconsistent positions on a claim term.

  RulingsInstitution decision

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

    “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 not established a reasonable likelihood that it would prevail in showing the unpatentability of at least one of the challenged claims. Accordingly, we decline to institute an inter partes review of the challenged claims. B. Real Parties in Interest” slip op. at 2

  • Prior constructionPrior construction not adoptedDecided for patent owner

    “The Board has recently clarified that “[s]imply noting that the petitioner is adopting a patent owner’s claim construction proposals from district court . . . is not a sufficient reason for advancing different positions in the two forums.” Revvo Techs., Inc. v. Cerebrum Sensor Techs, Inc., IPR2025-00632, Paper 20, 5 (PTAB Nov. 3, 2025) (precedential). In Revvo, as in this case, the petitioner did not propose its own constructions for claim terms in the Petition, but instead accepted the patent owner’s proposed constructions from the related district court litigation. Id. at 2. Although the petitioner had proposed different constructions for the claim terms in district court, it did not explain why it was taking a different position before the Board. Id. The Board’s trial rules “do not necessarily prohibit petitioners from taking inconsistent claim construction positions before the Board and a explain why alternative positions are warranted.” Revvo, Paper 20, 3–4 (quoting Cambridge Mobile Telematics, Inc. v. Sfara, Inc., IPR2024-00952, Paper 12 at 8–9 (PTAB Dec. 13, 2024) (informative)). Petitioner has not sufficiently done so here. Moreover, the fact that Petitioner cannot raise its indefiniteness challenge in an inter partes review is not a sufficient reason to allow Petitioner to take inconsistent claim construction positions before the Board and the district court. Tesla, Inc. v. Intellectual Ventures II LLC, IPR2025- 00340, Paper 18, 3 (Nov. 5, 2025) (informative). As explained in the Board’s Tesla decision: Petitioner’s statement that it cannot raise indefiniteness challenges in an inter partes review is not a sufficient explanation. Indeed, the statement amounts to an assertion that a petitioner should be permitted to raise inconsistent invalidity challenges in the two forums. Petitioner’s explanation may have risen to a sufficient level, for example, if Petitioner had shown that, notwithstanding the alleged indefiniteness of the claim term, an ordinarily skilled artisan would understand that the asserted art satisfies the claim limitation (such as if the limitation prescribed a range and only the outer bounds of the range were unclear). Instead, Petitioner argued indefiniteness in the district court and then adopted Patent Owner’s plain and ordinary meaning construction from the district court litigation in its Petition. Allowing a petitioner to advance a claim construction before the Board when that petitioner has made inconsistent indefiniteness arguments in” slip op. at 7

  Claim constructioncites Phillips
  Patents in suitUS 12,001,549
• 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

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.