- Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 23, 2026 · IPR2025-00915 · APJ Arthur M Peslak · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–3, 5–16, and 18–30 as obvious over Menon, Trefethen, RS6000, and MPIref; claims 4 and 17 over those references plus POEref.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundTeaching away not foundDecided for petitioner
“Ex. 1163 ¶ 37 (citing Ex. 1003 ¶ 71; Ex. 1005, 1–3). We credit Dr. Bajaj’s testimony which is unrebutted and supported by the record. We, thus, agree with Dr. Bajaj’s reasoning which is based on Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶ 75. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine. RS6000 is specifically referenced in Menon-Trefethen and adds operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Considering Menon as a whole, these facts are inconsistent with Patent Owner’s teaching away arguments. For these reasons, Patent Owner’s teaching away argument is unavailing. Motivation to Combine Conclusion We have reviewed Petitioner’s evidence and contentions which we” slip op. at 42
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“For the foregoing reasons, Petitioner establishes by a preponderance” slip op. at 79
Patent outcomesUS 11,563,621 unpatentable§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,563,621 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 1, 2026 · IPR2025-00914 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–19 are unpatentable as obvious over Menon, Trefethen, RS6000, and POEref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’679 patent, the prior art of record, and the testimony of both experts.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Petition relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard. Pet. 12–13 (citing 37 C.F.R. § 42.100(b)). The Petition also addresses the construction of “peer-to-peer architecture” recited in independent claim 1 of the ’679 patent, a limitation we need not construe to resolve the parties’ dispute in this proceeding. Id. at 13; see, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Owner relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard without further analysis. Resp. 7.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“RS6000 with Menon, namely because RS6000 provides an overview of the IBM SP2 multiprocessor and Menon teaches the use of “IBM SP2, a modern high performance distributed memory multiprocessor” used in the MultiMATLAB system. Id. at 24–25 (citing Ex. 1003 ¶¶ 142–145; Ex. 1005, 5–6, 14; Ex. 1007, 1, 11). The Petition also explains why POEref pertains to the field of cluster computing in a parallel operating environment. Id. at 26 (citing Ex.1008, 11 (“PE Software is designed to run on an … RS/6000 network cluster”)); (further citing Ex. 1001, 1:14–15; Ex. 1003 ¶¶ 146–149). The Petition contends that a POSITA would have been motivated to combine the teachings of POEref with Menon “because Menon suggests the combination by teaching that MultiMATLAB uses ‘POE, IBM's Parallel Operating Environment.’” Id. at 26–27 (citing Ex. 1005, 6); (further citing Ex. 1003 ¶¶ 150–153; Ex. 1005, 14; Ex. 1008, 11, 46). We agree with Petitioner’s analysis. We find the Petition’s argument and evidence of a motivation to combine the asserted prior art references in the manner claimed to be compelling, persuasive, consistent with the disclosures in the references, which include internal cross-references to each other, and supported by the expert testimony of Dr. Bajaj.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner
“skill, upon reading the reference, would be discouraged from following the path set out in the reference, or would be led in a direction divergent from the path that was taken by the applicant.” In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). Patent Owner argues that Menon teaches away from a combination with Trefethen because “Menon expressly states that Trefethen’s first-generation architecture is inadequate for the objectives that motivated the newer design.” Resp. 35–37. The evidence does not support Patent Owner’s position. First, Patent Owner’s teaching away argument is inconsistent with the strong evidence of a motivation to combine Menon and Trefethen discussed above. Second, Patent Owner’s teaching away argument is contrary to the evidence of record for the reasons given in Petitioner’s Reply. Reply 13–15 (e.g., “Menon explicitly cites Trefethen and explains that Menon builds on the teachings of Trefethen.”) (citing Pet. 22; Ex. 1003 ¶ 70; Ex. 1005, 1–3; Ex. 1163 ¶¶ 47–53). We are further persuaded by Dr. Bajaj’s reply testimony: the “MultiMATLAB teachings in Trefethen. In fact, Menon describes enhancing the system of Trefethen. For example, Menon describes a list of “goals” already achieved by MultiMATLAB and then states that the architecture has been “redesigned to achieve two further goals.” One of these two “further goals” is “extensibility,” which Menon achieves by its description of adding “MEX routines” to the system of Trefethen. Far from showing an “incompatibility” between Menon and Trefethen as the POR argues, Menon’s addition of the “MEX routines” to MultiMATLAB shows that such a modification was within the capabilities of a POSITA, because the authors of the Menon paper actually implemented the modification. Ex. 1163 ¶ 49 (citing Ex. 1005, 1–3). Dr. Bajaj’s testimony is unrebutted, credible, and supported by the record. We agree with Dr. Bajaj’s reasoning, which is based on direct quotes in Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶¶ 50–52. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine the teachings of Menon and Trefethen. RS6000 and POEref are specifically referenced in Menon-Trefethen and add operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Such facts are inconsistent with Patent Owner’s teaching away and lack of motivation arguments.” slip op. at 24
Patent outcomesUS 12,021,679 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 12,021,679 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Aug 26, 2026 · IPR2025-00913 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–25, 27–28, and 30 as obvious over Menon, Trefethen, RS6000, and POEref; claims 26 and 29 over those references plus MPIref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and experience of a POSITA. We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’034 patent, the prior art of record, and the testimony of both experts.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther
“processor,” “multi-core” processor, or “singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’” as Patent Owner contends. Resp. 11–12, 21; see also Ex. 1163 ¶ 22 (“The claim does not recite ‘single chip,’ ‘single package,’ ‘single die,’ or ‘single multi-core microprocessor.’”). Nor do the claims recite a plurality of processing cores “within” a single-chip package or read as “multi-core within a processor” as argued by Patent Owner. Resp. 12–14; Sur-Reply 2; see Reply 6 (citing Ex. 1163 ¶ 23 (“Thus, the phrase ‘with a plurality of processing cores’ identifies the required processing resources associated with the hardware processor; it does not import a packaging limitation.”)). The claims do recite a hardware processor “with” a plurality of processing cores; a critical distinction even Patent Owner reads as open-ended, i.e., as a hardware processor that “comprises” a plurality of processing cores. See Resp. 11 (“the claims require a singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’”). Consequently, the claim language does not support Patent Owner’s proposed construction of “a . . . hardware processor with a plurality of processing cores” as a single multi-core processor. cores it contains” in reliance on a parsed description in the ’034 patent specification: The specification explains: “Each processor can contain one or more processor cores that are capable of single-threaded execution. Processor cores are generally independent microprocessors, but more than one can be included in a single-chip package.” Id. at 1212 (partially quoting Ex. 1001, 5:11–16); Sur-Reply 2. The quoted description does not support Patent Owner’s contention that the claimed “a . . . hardware processor with a plurality of processing cores” must be limited to a “single multi-core processor” that “locates multiple cores within a ‘single-chip package,’” i.e. limited to a single multi-core microprocessor such as “a Core 2 Duo is one processor package with two cores.” Resp. 12– 13, 21 (citing Ex. 1001, 7:15–25). The description quoted above from column 5, moreover, describes a “processor” that “can contain one or more processor cores” each of which can be an independent microprocessor. Reply 2–3 (citing Ex. 1001, 5:11–16; Ex. 1163 ¶¶ 10–14). As Petitioner emphasizes, the specification distinguishes a “processor” from a “microprocessor” and describes a “processor” that “can be one or more general purpose single-core or multi-core microprocessors,” rather than limiting a “processor” to a single multi-core microprocessor. Reply 3–5 (citing Ex. 1001, 7:14–36, Fig. 1; Ex. 1163 ¶¶ 15–18).” slip op. at 13
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“art because they pertain to the same “field of cluster computing” as the ’034 patent and “are reasonably pertinent to the problem of the ’034 patent, namely, executing a single program on multiple nodes.” Pet. 22 (citing Ex. 1001, 1:14–15; Ex. 1003, ¶¶ 65–69; Ex. 1005, 2; Ex. 1006, Abstract). The Petition emphasizes that Menon expressly cites and builds on the MultiMATLAB system taught by Trefethen. Id. (citing Ex. 1003 ¶ 71; Ex. 1005, 1–2). The Petition contends that: combination of prior art elements according to known methods (executing MATLAB code on a multiprocessor system) to yield the predictable result discussed in both papers: the MultiMATLAB system executing MATLAB in parallel to perform mathematical calculations. Id. at 22–23 (citing Ex. 1003 ¶ 70; Ex. 1005, Abstract; Ex. 1006, 2–7). The Petition further contends that a POSITA would have found it predictable to combine Trefethen with Menon with a reasonable expectation of success “because researchers had a strong desire to parallelize MATLAB.” Id. at 23–24 (citing Ex. 1003 ¶ 73; Ex. 1005, 2; Ex. 1006, 11–12.)” slip op. at 27
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“A POSITA would have had an especially strong reason to read these references together because they address the same project, the same MATLAB-based parallel-computing problem, and the same MultiMATLAB command environment. Menon expressly identifies Trefethen’s MultiMATLAB work and then describes a redesigned architecture that preserves the same user-level objective––parallel MATLAB computations—while improving implementation details and extensibility. A POSITA therefore would not view the references as mutually exclusive alternatives. Rather, a POSITA would understand Trefethen as teaching specific MultiMATLAB commands and examples, including Eval, Send, Recv, and the architecture was implemented and improved in a later version. Ex. 1163 ¶¶ 71–72 (emphases added). We find the above reasoning persuasive and adopt it as our own. Petitioner and Dr. Bajaj demonstrate a sound technical motivation for a POSITA—someone having a bachelor’s degree in computer science, computer engineering, or electrical engineering and two years of experience working in the field of cluster computing or parallel processing—to combine Menon and Trefethen: to improve MATLAB’s operational performance and extensibility in a parallel operating environment. Menon builds on Trefethen to improve and extend the parallel processing capabilities of MultiMATLAB: “This system will enable users to access high-performance parallel routines from within the MATLAB environment, to extend the environment with new parallel routines, and to use these routines to develop parallel applications with the MATLAB language.” Ex. 1005 Abstract. Menon is intended to be read in conjunction with Trefethen, as would be expected from two references generated by the same research group at the same university addressed to the same technical subject matter about a year apart. Ex. 1005, 1; Ex. 1006, Ex. 1086 ¶¶ 65, 101, 102. The very first citation in Menon is to Trefethen. Ex. 1005, 2, 16.” slip op. at 30
Patent outcomesUS 11,570,034 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,570,034 - Apple Inc. v. DH International Ltd.All claims unpatentablePTAB · Apr 16, 2026 · IPR2025-00172 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Suga and Gorsuch; the Board denied Patent Owner’s motion to exclude.
RulingsFinal written decision- ExcludeMotion to exclude, deniedDenied
“Patent Owner also asserts prejudice for “not knowing” which Suga Exhibit “the Petitioner and Petitioner’s expert is relying on (see Exhibit 1021 and 1022),” without further explanation. Mot. Reply 6. Exhibit 1022 is a dictionary definition of “node.” How this relates to Patent Owner’s argument of prejudice is not explained. Id. at 5–6. The Board perceives no difficulty following Petitioner’s arguments and evidence, which cite Suga Exhibit 1005, including the testimony of Dr. Buehrer regarding the English language translation of Suga, which is identical in Exhibits 1005 and 1017. Patent Owner, moreover, opted not to depose Dr. Buehrer, did not file a deposition transcript of Dr. Buehrer in this proceeding, and does not allege any difference or substantive deficiency in the English language translation in Suga Exhibits 1005 and 1017, which are identical. We fail to see any prejudice to Patent Owner.” slip op. at 84
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“d. Conclusion for Claim 1 For the reasons given above, we determine the Petition establishes by” slip op. at 60
Patent outcomesUS 9,022,294 unpatentable§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,022,294 - Google LLC v. DH International Ltd.All claims unpatentablePTAB · Feb 10, 2026 · IPR2024-01322 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Mooney; the Board also found Mooney combined with Lee renders the disputed limitations obvious.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“A person of ordinary skill in the art (“POSITA”) at the time of the alleged invention of the ’294 patent would have had at least a bachelor’s degree in electrical engineering, or a related field, and at least two years of experience in design, development, and/or testing of network-enabled consumer devices, and familiarity with payment cards, or the equivalent, with additional education substituting for experience and vice versa. Pet. 2 (citing Lipoff Decl. Ex. 1003 ¶ 57). “Patent Owner agrees with the Petitioner on the level of ordinary skill in the art.” Resp. 4. Patent Owner adds that a POSITA would have had “at least three years of relevant industry or research experience in wireless communication between devices.” Id. (citing Ex. 2001 ¶¶ 26–29). Mr. Zaheer testifies that a POSITA “would” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“The claim language and specification define and describe an “activation cue” in functional terms: a data communication from an external source is received by the cell phone and recognized as an activation cue if it causes the switching element to be assigned its first (activated) state. Ex. 1001, 9:28–31, 9:42–46, 10:14–16, 13:55–60, 14:53–59, 15:4–6, 19:20–26. Patent Owner agrees that “upon an activation cue being received by portable electronic device 10, switching element 44b switches to its activated state.” Resp. 19 (quoting Ex. 1001, 10:14–16). The activation cue may be a predetermined bit sequence, a predetermined contactless data transmission, continuously emitted, pulsed, or punctual, but these are unclaimed non-limiting embodiments of the preferred form of data transmission. Id. at 9:25–26 (“for example a predetermined bit sequence”), 11:20–22 (“One example . . . emit an activation cue in the form of a predetermined contactless data transmission”), 14:65–15:3 (continuously emitted, pulsed or punctual cue). We will not read such preferred embodiments from the specification into claim language that is not so limited. See SuperGuide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875 (Fed. Cir. 2004) (care should be taken “not to import into a claim limitations that are not part of the claim”); see also In re Van Geuns, 988 F.2d 1181, 1184 (Fed. Cir. 1993) (“limitations are not to be read into the claims from the specification”); see also IQRIS Techns. LLC v. Point Blank Enterprises, Inc., 2025 WL 727717, *4 (Fed. Cir. 2025) (“It is the claims, not the preferred embodiments, that” slip op. at 15
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“operatively linked to said electronic circuit” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. We note there is no presumption of applying means-plus-function analysis to the switching element, because the limitation does not use the words “means for” that would mandate such claim construction treatment, and “switching” may invoke structure as well as function. See Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1349–1350 (Fed. Cir. 2015) (en banc) (holding that “use of the word ‘means’ creates a presumption that § 112, ¶ 6 applies”). Regardless, we look to the meaning of the claim phrase at issue in view of the specification. We determine that the ’294 patent provides a clear, concise meaning for the switching element upon which both parties rely for construction. Patent Owner’s express agreement with Petitioner, that the claimed switching element is described in the ’294 patent as “any type of device allowing data to be conveyed according to alternate data conveyance operations in response to an activation cue being received by transceiver 18 or not,’” is particularly telling because it is not consistent with Patent Owner’s argument that the switching element means “switching of the data.” Resp. 7, 31 (citing Ex. 1001, 9:28–318). The claim language does not recite, and the specification does not describe, the switching element as a device that switches the data. Therefore, we determine the claimed “data conveyance switching element” means any type of switching device that allows data to be 8 We presume Patent Owner’s citation to “Exh. 2001, 9:28-31” on page 7 was intended to be a citation to the ’294 patent (Ex. 1001), as cited on page 31. whether or not an “activation cue” is received by the cell phone “cue receiver.”” slip op. at 21
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningDecided for petitioner
“[external] data exchange device” as a device with a data transceiver coupled to a circuit that carries out the function of exchanging data. Pet. 7–8 (citing Ex. 1001, 2:14–17, 4:7–14, 9:3–6; Ex. 1003 ¶¶ 67–68). As above, whether we construe the “[external] data exchange device” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. Patent Owner, quoting the description of a data exchange device in the ’294 patent, contends that a “[external] data exchange device” “can be any sort of data exchange device comprising an electronic circuit (not shown) therein and a data transceiver 9a.” Resp. 8 (quoting Ex. 1001, 9:4–6). Patent Owner also responds to the Petition by clarifying that “[a]n external data exchange device is not a transceiver but a device with a transceiver.” Id. (citing Ex. 2001 ¶ 48). Petitioner argues in reply that Patent Owner does not contest Petitioner’s mappings of Mooney’s “cordless telephone base unit” or “cellular network infrastructure” to the claimed data exchange devices, such that no construction is necessary to resolve the dispute. Reply 5 (citing Resp. 16–37; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011)). Limitations [1.c] and [1.d] recite “a first [second] data transceiver operatively linked to said electronic circuit [in the cell phone],” both of which are defined functionally as “for exchanging data between said electronic circuit [in the cell phone] and a first [second] external data exchange device over a first [second] communication link.” Nothing in the the other independent claims, further limits the form or function of the “[external] data exchange device,” although a device external to the cell phone may invoke additional structure. We determine the plain meaning of “[external] data exchange device” as claimed and described in the ’294 patent governs: any [external] device that comprises an electronic circuit and data transceiver for exchanging data with the electronic circuit in the cell phone over a communication link. slip op. at 22
Patent outcomesUS 9,022,294 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,022,294 - Reed Semiconductor Corp. v. Monolithic Power Systems, Inc.All claims unpatentablePTAB · Jan 22, 2026 · IPR2024-01158 · APJ Ken B Barrett · IPR · Final written decision
Claims 1–5, 7–15, 17, and 18 are unpatentable: claims 1–4, 9–14, 17, and 18 as anticipated by Tateishi, and claims 5, 7, 8, and 15 as obvious over Tateishi.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“We discern no material difference between the parties’ definitions. Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art. We note, however, that were we to adopt Patent Owner’s assessment, the outcome of this Decision would be the same.” slip op. at 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“After considering the parties’ arguments and evidence, we determine that Patent Owner has not offered persuasive evidence that a person of ordinary skill in the art reading the claims in light of the Specification would understand the plain and ordinary meaning of “control signal” to be as narrow as Patent Owner proposes. We do not construe the claims such that the “control signal” must be the exclusively controlling factor of a component, as Patent Owner urges. Petitioner’s position, on the other hand, is consistent with the evidence of record. We construe “control signal” as having its plain and ordinary meaning, namely a signal configured to control a circuit component. D. The Asserted Anticipation of Claims 1–4, 9–14, 17, and 18 by Tateishi” slip op. at 24
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“We determine that Petitioner has demonstrated by a preponderance of the evidence that Tateishi discloses the “control signal” recited in limitations 1B2 and 1D of independent claim 1.” slip op. at 37
- BurdenNot shown unpatentable
“based on the Tateishi application publication (Ex. 1007), that the Tateishi Patent (Ex. 1005) also anticipates claims 1–4, 9–14, 17, and 18. See Pet. 23–24 (“The Tateishi Patent is also prior art under (pre-AIA) §102(e)”; identifying Ground 1 as anticipation “under §102 by Tateishi and/or the Tateishi Patent”). However, we are unable to locate in the Petition or Petitioner’s Reply a discussion of or citation to the Tateishi Patent other than under the Petitioner’s heading “Identification of Challenge and Relief Requested” on pages 23 and 24 of the Petition. Cf. id. at i–x (Table of Contents identifying a section of the Petition discussing the Tateishi (Application) anticipation ground but not a section discussing a Tateishi Patent anticipation ground). Although the issued patent may be substantively identical to the published application, Petitioner does not assert that, and we decline to compare the documents to determine whether that is the case. In light of Petitioner’s silence on the alternative ground, Petitioner has not demonstrated by a preponderance of the evidence that the Tateishi Patent anticipates 1–4, 9–14, 17, and 18.” slip op. at 47
Patent outcomesUS 9,041,377 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,041,377 - Orca Security Ltd. v. Wiz, Inc.InstitutedPTAB · 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 · GrahamPatents in suitUS 11,929,896 - Orca Security Ltd. v. Wiz, Inc.InstitutedPTAB · 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 · GrahamPatents in suitUS 12,003,529 - Orca Security Ltd. v. Wiz, Inc.InstitutedPTAB · 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 · GrahamPatents in suitUS 11,936,693 - Fubotv Media Inc. / Yanka Industries, Inc. et al. v. DISH Technologies L.L.C.All claims unpatentablePTAB · Dec 5, 2025 · IPR2025-00348 · APJ Karl D Easthom · IPR · Final written decision
Claims 1–21 are unpatentable: claims 1–16 and 18–21 as obvious over Leaning, and claims 2 and 9 as obvious over Leaning and Gamble.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“This argument is misplaced. Petitioner does not propose modifying any of Leaning’s teachings. Rather, Petitioner relies on Leaning’s alternative embodiment (i.e., “employ[ing] a criterion which anticipates underflow and avoids it”). See Ex. 1004, 15:3–6; Pet. 38 (citing and quoting same). Patent Owner acknowledges this fact. See PO Sur-reply 12 (“Leaning proposes an alternative embodiment.”) (citing Ex. 1004, 14:25–15:8)). Accordingly, Petitioner need not show a reasonable expectation of success for implementing an alternative embodiment expressly disclosed in Leaning.10” slip op. at 28
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“Accordingly, we accord Patent Owner’s evidence little to no weight. v. Unexpected Results Patent Owner argues that the MOVE Media Player “achieved what” slip op. at 65
- ExcludeMotion to exclude, deniedDenied
Patent outcomesUS 8,868,772 unpatentable§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,868,772
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.