• Innoscience America, Inc. v. Infineon Technologies Americas Corp.No claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00175 · APJ Jo-Anne M Kokoski · IPR · Final written decision

  Claims 1–17 were not shown unpatentable because Petitioner failed to establish that Usui’s interconnect structure or Yu’s metal gate stacks satisfy the construed “electrode stack” limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “(“POSITA” or “POSA”) would have had “at least a four-year degree in electrical engineering or a closely related field, and at least two years of experience in semiconductor device design,” and “[a]dditional education could substitute for professional experience and vice versa.” Pet. 6 (citing Ex. 1002 ¶¶ 80–82). Patent Owner does not dispute Petitioner’s proposed level of ordinary skill. PO Resp. 1–76. Neither party explains why the outcome of this case would be affected by the adoption of the proffered definition of a person of ordinary skill in the art. In the Institution Decision, we adopted the assessment offered by Petitioner. Dec. 6–7. Because Petitioner’s definition of the level of skill in the art is consistent with the ’562 patent and the asserted prior art, we maintain Petitioner’s definition for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir 2001).” slip op. at 9

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

    “comprises the recited metals and has the recited thickness, which forms an electrical contact for use on a semiconductor device generally or a group III- V semiconductor in particular. This is consistent with our determination that “electrode stack” is a conductor that provides a path for current entering or leaving a medium such as a semiconductor device We disagree with Patent Owner that “electrode stack” as used in the challenged claims should be limited to the specific electrodes shown in the embodiments described in the Specification. See PO Resp. 4–9. Although the Specification describes embodiments using source, drain, and Schottky gate electrodes as electrical contacts, we see no reason to construe the term “electrode stack” itself to be limited to these components as Patent Owner proposes. Claims 1 and 13 expressly recite that electrode stacks comprise the claimed “electrical contact,” without expressly including or precluding any specific type of electrode. Ex. 1001, 5:54–63, 6:37–47. The Federal Circuit advises that the Specification “is not a substitute for, nor can it be used to rewrite, the chosen claim language. ‘Specifications teach. Claims claim.’” SuperGuide, 358 F.3d at 875 (quoting SRI Int’l v. Matsushita Elec. Corp. of Am., 775 F.2d 1107, 1121 n.14 (Fed. Cir. 1985) (en banc)). The Specification does teach electrical contacts that include source, drain, and Schottky gate electrodes, but claims 1 and 13 are directed to electrical contacts that are not expressly so limited. Patent Owner’s proposed construction would effectively rewrite the claim by adding limitations, which we decline to do under the guise of claim construction. See id. (“Though understanding the claim language may be aided by the explanations contained in the written description, it is important not to import into a claim limitations that are not a part of the claim.”). In view of the foregoing, we construe the claim term “electrode stack” to mean “a conductor that provides a path for current entering or leaving a medium such as a semiconductor device.”” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential). In contrast, Patent Owner’s declarant Dr. Piner testifies, with evidentiary support, that interconnects (such as Usui’s interconnect metallurgy structure) and electrical contacts (such as that claimed in the ’562 patent) are not the same thing. See Ex. 2024 ¶¶ 63–70. For example, Dr. Piner explains: In other words, not all metals in a semiconductor device have the same purpose and could not be said to be interchangeable. By August 2009 it was well known to a POSA how to discern if a metal component in a transistor is an interconnect or serves as an electrical contact such as a gate contact or ohmic contact, based on the structure and functionality of the metal component. For example, interconnects are made up of metal strips and are deposited on insulators. EX-1011 (Mishra) at 216. Interconnects are low resistance conductors that can carry very high current densities. Id., 216, 217. Unlike Schottky contacts and ohmic contacts, interconnects do not provide non-linear IV response like Schottky contacts nor inject electrons and holes into semiconductors like ohmic contacts. Id., 218. As many of the references cited by Dr. Zhao illustrate, electrical contacts had their own highly complex design challenges. EX-1008 (Pearton), 41-59 (Pages 53-71 of 383) (discussing electrical contacts); EX-1017 (Kramer), 11-126 (Pages 18-130 of 151) (same). And while Dr. Zhao cites these as supporting a POSA’s knowledge of an electrical contact, none of these references describe electrical contacts as interconnects. Id. ¶ 71. Dr. Piner further testifies that Usui’s interconnect metallurgy structure is an interconnect, and not an electrical contact, because “Usui states that ‘[t]he structures fabricated by the process of the present invention are especially useful for forming electrical connections or wiring such as between active and/or passive devices of an integrated circuit structure.’” Id. ¶ 148 (citing Ex. 1004, 1:11–14) (alteration in original); see also id. ¶¶ 150– 151 (Dr. Piner testifying that Usui’s interconnect metallization structure is not an “electrode stack” under a broad definition of electrode). Dr. Piner’s testimony in this regard rebuts Petitioner’s and Dr. Zhao’s conclusory assertions to the contrary.” slip op. at 21

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “conductor that provides a path for current entering or leaving a medium such as a semiconductor device.” Thus, Petitioner must show that Usui’s layers 13–15, 18, and 19 provide a path for current entering or leaving a medium such as a semiconductor device. After reviewing the complete trial record, we are not persuaded that Petitioner has done so. Petitioner relies on the testimony of Dr. Zhao to support its contention that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential).” slip op. at 21

  Patent outcomesUS 8,686,562 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,686,562
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

  Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those 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

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable

    “search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24

  Patent outcomesUS 7,370,035 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,370,035
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9

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

    “In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable

    “different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27

  Patent outcomesUS 10,552,490 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 10,552,490
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightMotivation not foundNot shown unpatentable

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Innoscience America, Inc. v. Infineon Technologies Americas Corp.No claims unpatentable
  PTAB · Jun 12, 2026 · IPR2025-00094 · APJ Christopher M Kaiser · IPR · Final written decision

  Claims 1–16 were not shown unpatentable under any asserted obviousness ground because Petitioner failed to establish the proposed modifications and combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that one of ordinary skill in the art “would have possessed at least a four-year degree in electrical engineering or a closely related field, and at least two years of experience in semiconductor device design.” Pet. 5 (citing Ex. 1003 ¶¶ 67–69). Petitioner also argues that “[a]dditional education could substitute for professional experience and vice versa.” Id. Patent Owner does not dispute Petitioner’s proposed level of ordinary skill. PO Resp. 1–76. Neither party explains why the outcome of this case would be affected by the adoption of the proffered definition of a person of ordinary skill in the art. Accordingly, and because it appears to be consistent with the ’003 patent and the asserted prior art, we adopt Petitioner’s assessment of the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7

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

    “Neither party proposes construing any claim terms. Pet. 6; Prelim. Resp. 1–76. In addition, as discussed below, we are able to determine the outcome of this proceeding without expressly construing any terms. Thus, we do not construe any terms for the purposes of this Decision. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 8

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable

    “challenged claim. Unigene Labs., Inc. v. Apotex, Inc., 655 F.3d 1352, 1360 (Fed. Cir. 2011). “This is so because inventions in most, if not all, instances rely upon building blocks long since uncovered, and claimed discoveries almost of necessity will be combinations of what, in some sense, is already known.” KSR, 550 U.S. at 418–419. On the other hand, an obviousness analysis “need not seek out precise teachings directed to the specific subject matter of the challenged claim, for a court can take account of the inferences and creative steps that a person of ordinary skill in the art would employ.” Id. at 418; accord In re Translogic Tech., Inc., 504 F.3d 1249, 1259 (Fed. Cir. 2007). However, a petitioner cannot satisfy its burden of proving obviousness by employing “mere conclusory statements.” In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016). Instead, a petitioner must articulate a reason why a person of ordinary skill in the art would have combined or modified the prior art references. In re NuVasive, Inc., 842 F.3d 1376, 1382 (Fed. Cir. 2016); see also Metalcraft of Mayville, Inc. v. The Toro Co., 848 F.3d 1358, 1366 (Fed. Cir. 2017) (“In determining whether there would have been a motivation to combine prior art references to arrive at the claimed invention, it is insufficient to simply conclude the combination would have been obvious without identifying any reason why a person of skill in the art would have made the combination.”); Belden Inc. v. Berk-Tek LLC, 805 F.3d 1064, 1073 (Fed. Cir. 2015) (“[O]bviousness concerns whether a skilled artisan not only could have made but would have been motivated to make the combinations or modifications of prior art to arrive at the claimed invention.”) (citing InTouch Techs., Inc. v. VGO Commc’ns, Inc., 751 F.3d 1327, 1352 (Fed. Cir. 2014)). In arguing for the obviousness of claim 1 over the combination of Bonn and Mizuta, Petitioner argues that a person of ordinary skill in the art would have modified Bonn to perform high-frequency signal amplification. Pet. 19–25. In particular, Petitioner argues that a person of ordinary skill in the art “would have found it obvious to modify the circuit of Figure 1 [of Bonn] and use Figure 7’s structure for high frequency signal amplification in place of mixer 40,” followed by additional modifications to the circuit of Figure 1. Id. at 22–25. These additional modifications include removing LO port 55, removing FET 20 (along with voltage source 80, capacitors 16, 26, and 34, resistor 18, and inductors 22 and 24), removing capacitor 34 and shorting gate structure 324 to ground, and removing resistors 46 and 48 and shorting terminal 51 to ground. Id. According to Petitioner, the motivation for these modifications was that “Bonn . . . teaches using its dual gate structures for signal amplification without signal mixing.” Id. at 22 (citing Ex. 1006, 11:26–37). On the record developed at trial, we disagree. Bonn does, as Petitioner argues, teach that “the dual gate FET structure of the present invention can be tailored to provide superior performance over the prior art dual gate FET structures in high frequency signal mixing as well as other applications such as high frequency signal amplification.” Ex. 1006, 11:33–37. But the tailoring that Bonn refers to relates to changes to the structure of the field-effect transistor itself, not to the circuitry surrounding that transistor. Id. (teaching that the reason that “the dual gate FET structure of the present invention can be tailored” is that “the parameters such as gate width, dopant concentration, and channel depth, under each gate of the dual gate FET are individually adjusted for optimum performance”). Thus, although Bonn might have motivated a person of ordinary skill in the art to have made changes to the dual-gate FET itself, we are not persuaded that it would have motivated the additional changes to the circuit of Bonn’s Figure 1.” slip op. at 11

  • Strike new argumentNew argument disregardedDecided for patent owner

    “Mishra’s Figure 5 is a second gate in favor of a new position. Petitioner’s new argument is that a person of ordinary skill in the art would have found it obvious to connect the field plate of Mishra’s Figure 5 to the source instead of the gate, converting the field plate into a second gate. Compare Pet. 83 (equating “drain side gate” with “field plate 66, Figure 5”), 86–88 (identifying field plate 66 as a “second gate”), with Reply 21–22 (identifying only the embodiment of Mishra’s Figure 10 as a source-connected field plate), 22–23 (arguing that Mishra teaches that the Figure 5 embodiment “could be arranged as ‘a single transistor with a dual gate structure’”). Although “the introduction of new evidence in the course of the trial is to be expected in inter partes review trial proceedings,” Genzyme Therapeutic Prods. LP v. Biomarin Pharm. Inc., 825 F.3d 1360, 1366 (Fed. Cir. 2016), the shifting of arguments is not, Wasica Fin. GmbH v. Cont’l Auto. Sys., Inc., 853 F.3d 1272, 1286 (Fed. Cir. 2017). Accordingly, Petitioner’s change of arguments here is inappropriate. Moreover, even if we were to consider Petitioner’s inappropriate new argument, we would conclude that Petitioner does not support the argument with sufficient evidence. “Whether [an obviousness ground] is based on combining disclosures from multiple references, combining multiple embodiments from a single reference, or selecting from large lists of elements in a single reference, there must be a motivation to make the combination and a reasonable expectation that such a combination would be successful, otherwise a skilled artisan would not arrive at the claimed combination.” In re Stepan, 868 F.3d 1342, 1346 n.1 (Fed. Cir. 2017). Petitioner’s new argument relies on a person of ordinary skill in the art modifying the Figure 5 embodiment of Mishra to connect the field plate to the source rather than the gate. Reply 21–24. Petitioner does not, however, show that a person of ordinary skill in the art would have had a motivation to make this modification or a reasonable expectation that this combination would be successful. Id. Petitioner argues instead that “[n]o ‘reason’ is needed.” Id. at 24. Thus, Petitioner does not show by a preponderance of the evidence that claim 1 would have been obvious over the combination of Mishra and Ren.” slip op. at 19

  Patent outcomesUS 8,264,003 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,264,003
• BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentable
  PTAB · Mar 5, 2026 · IPR2024-01347 · APJ Russell E Cass · IPR · Final written decision

  Claims 1–27 were not shown unpatentable because the asserted combinations did not teach switching the boot-processor role to a spare processor.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art 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). “This reference point prevents . . . factfinders from using their own insight or, worse yet, hindsight, to gauge obviousness.” Id.” slip op. at 17

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

    “processor” to the spare processor, we determine that the claim is describing this transfer of identification of “boot processor,” which is required when transferring a boot processor’s functions to a spare because of the “problems [that] arise in attempting to idle (or eject) the boot processor.” Id. at 6:25– 27. This is confirmed by the language of limitation [1d], stating that the switching of the role of boot processor involves “changing a system identifier of the spare processor to that of the boot processor.” Thus, the firmware and operating system exchange this information identifying the boot processor, which is described in the specification as a device tree. See, e.g., id. at 13:21–35. The ’302 patent makes clear that accurate identification of which processor is the boot processor remains critical during runtime. See, e.g., id. at 6:25–27. Thus, Patent Owner is correct in requiring the system to have a way to identify the boot processor and to transfer this identification during runtime. However, as made clear in the embodiments described in the ’302 patent discussed above, this identification is for runtime purposes to accommodate runtime problems, not for booting purposes. Although Patent Owner may be correct that a function of the boot processor is to boot the system (PO Sur-reply 5), the problem identified in the ’302 patent is a problem relating to the runtime reassignment of the boot processor identity, to address a runtime need to identify the boot processor. See, e.g., Ex. 1001, 11:6–9. Accordingly, based on our analysis of the claims and specification, we determine that “switching the role of boot processor to a spare processor without shutting down the system’s operating system” means causing the system to identify the spare processor as the boot processor (e.g., in a device tree), which then causes the spare processor to appear as the boot processor to the system during runtime. Ex. 1001, 6:25–41, 11:4–18 (describing why boot processors are treated differently even after the boot process has completed); compare id. at 9:65–11:3 (process for recovering from loss of lockstep of a non-boot processor without using a spare), with id. at 11:4–43 (process for recovering from loss of lockstep of a boot processor using a spare because boot processors, during runtime, need special treatment); see also 14:66–15:21 (emphasizing that spares are only needed for recovering boot processors). We construe switching a “role of boot processor” to mean transferring an identification in the system of which processor is the boot processor. This construction comports with the embodiments described in the specification. We do not adopt an additional requirement that this procedure also requires designating which processor will boot the system in the next reboot, which is not disclosed in the specification.” slip op. at 24

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

    “may swap processors that are failing, and perform the necessary bookkeeping to keep the operating system informed as to how to address the processors available, nothing in the Petition persuasively explains whether this generic processor swapping switches the boot processor role. As we explained in our claim construction section, the term “boot processor” is not merely a label of convenience to describe the processor that happened to have earlier booted the system. The role of boot processor is specifically switched to the spare; it is a piece of information tracked by the system. As we explain below, Petitioner does not adequately address the transfer of this information to make the system aware of which processor has the boot processor role. Petitioner asserts that “the BSP flag” of the IA-32 system is used to “determine whether a processor is the boot processor.” Pet. 17–18. Petitioner here is relying on a register used in IA-32 processors to identify whether or not they are the boot processor. This register is used during booting so that only the boot processor boots the system. See, e.g., Ex. 1008, 238–40, 710. This register does not appear to serve any further role, and Petitioner offers no persuasive evidence or argument that the processor register flag is exposed or copied to the operating system or APIC table. Petitioner’s proposed combination does not involve updating this register, nor does Petitioner explain how, even if the register were updated, it would meet the “switching” a “role of boot processor” in limitation [1d].” slip op. at 32

  • ExcludeOther

    “The USPTO has established Rules for objecting to and challenging evidence. 37 C.F.R. § 42.64. This process sets various timeframes and permits briefing and curative actions, all of which are designed to crystallize 5 We follow the parties’ convention of citing to the later-added “Page X of Y” pagination rather than the native pagination. the issues and ensure a full and fair opportunity for the parties to be heard. See id. In this instance, Patent Owner’s evidentiary arguments regarding Exhibits 1008 and 1028 are untimely. Accordingly, we will not exclude Exhibits 1008 or 1028 on the basis of their authenticity, admissibility, or for any reason that should have been raised under the proper procedures. See, e.g., PO Resp. 7–8; PO Sur-reply 7–8; see also Pet. Reply 11 (asserting that “Patent Owner has not filed any objection to or a motion to exclude these references”). We consider Petitioner’s citations to these documents in our prior art analysis below. Notwithstanding, as is clear from our patentability analysis below, Exhibits 1008 and 1028 do not serve to demonstrate the unpatentability of any claim.” slip op. at 26

  Patent outcomesUS 7,624,302 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,624,302
• BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentable
  PTAB · Mar 5, 2026 · IPR2024-01346 · APJ Russell E Cass · IPR · Final written decision

  Claims 1–30 were not shown unpatentable because the prior-art combinations did not establish transfer of the role of boot processor during system runtime.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for patent owner

    “Patent Owner asserts that: A person of ordinary skill in the art in the field of the ’781 patent would have been a person with at least a bachelor’s degree in Electrical Engineering, Computer Engineering, or equivalent, and at least two years of prior work experience with computer architecture, including experience relating to fault tolerant computer architecture, as of the earliest priority date of the ’781 patent—October 25, 2004. If a person did not have a bachelor’s degree, additional relevant and practical experience with fault tolerant computer systems could provide an acceptable substitute. Likewise, further education beyond a bachelor’s degree could compensate for a deficiency in practical experience. See EX2004, Declaration of Nigel A. Jones (“Jones”), ¶ 26. PO Resp. 3. Patent Owner further notes that its position is “similar, but not identical to, Petitioner’s [position]” but that “the analysis [of the claims] is identical for both proposed determinations.” Id. We agree that our analysis would not differ based on choosing one proposed level of skill over the other, but as the losing party, we select Petitioner’s proposed level of skill.” slip op. at 20

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

    “Accordingly, based on our analysis of the claims and specification, we determine that “logic . . . for transferring, during system runtime, the role of boot processor” means logic that causes the system to identify the spare processor as the boot processor (e.g., in a device tree) which then causes the spare processor to appear as the boot processor to the system during runtime. Ex. 1001, 5:39–55, 10:43–67 (describing why boot processors are treated differently even after the boot process has completed); compare id. at 9:37– 10:42 (process for recovering from loss of lockstep of a non-boot processor without using a spare), with id. at 10:43–11:42 (process for recovering from loss of lockstep of a boot processor using a spare because boot processors, during runtime, need special treatment); see also 15:21–42 (emphasizing that spares are only needed for recovering boot processors). We construe transferring a “role of boot processor” to mean transferring an identification in the system of which processor is the boot processor. This construction comports with the embodiments described in the specification. We do not adopt an additional requirement that this procedure also requires designating which processor will boot the system in the next reboot, which is not disclosed in the specification.” slip op. at 26

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Based on the clear support in the specification for the above interpretation, we see no need to resort to extrinsic evidence. Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1287 (Fed. Cir. 2021) (“If the meaning of a claim term is clear from the intrinsic evidence, there is no reason to resort to extrinsic evidence.”) (citing Profectus Tech. LLC v. Huawei Techs. Co., 823 F.3d 1375, 1380 (Fed. Cir. 2016) (“Extrinsic evidence may not be used ‘to contradict claim meaning that is unambiguous in light of the intrinsic evidence.’” (quoting Phillips, 415 F.3d at 1324)). In general, the cited portions of testimony from the declarants from both parties in the briefs do little more than point to the portions of the ’781 patent described above or argue about what a boot processor does during booting. See, e.g., Pet. Reply 2–8. The specification makes clear that it is focused on the role of boot processor during runtime because of problems encountered during runtime; it is not focused on the boot processor during booting. Ex. 1001, 5:39–55, 10:43–67. Thus, the testimony about what a boot processor does during booting, or that the primary function of the boot processor is to boot, is not particularly pertinent, and does not undo the unambiguous discussion in the ’781 patent.” slip op. at 27

  • BurdenDecided for patent owner

    “whether they are the boot processor or not (Ex. 1008, 238, 710), Petitioner does not explain how such information is exposed to the BIOS or operating system, nor how it is changed during runtime, after its purpose has been fulfilled. In sum, even if Petitioner’s proposed combination swaps the spare processor for the processor that booted the system, Petitioner’s proposed combination does not appear to transfer the role of boot processor to the spare processor. At best, Petitioner’s proposed combination transfers the tasks of one processor to another. See Ex. 1005 ¶¶ 15 (Fox describing its disclosure as “updat[ing] the ‘active’ processor list” and “[re-]allocat[ing] the threads that were running on the failing processor”), 46 (transferring “processes (instructions, threads, etc.) initially allocated to the failing processor” to the spare processor)). Of the art of record, we are only aware of the ’781 patent transferring a designation of which processor is the boot processor during the swap to a spare processor. See, e.g., Ex. 1001, 10:43– 55, 11:10–12, 16:19–21, 17:51–55; claims 1, 9, 16, 25. In conclusion, we find that Petitioner has not shown, by a preponderance of the evidence, how the prior art teaches “transferring” a “role of boot processor” as required by limitation 1[c].” slip op. at 40

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

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

  RulingsInstitution decision

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

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

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

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

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

  RulingsInstitution decision

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

    “An inter partes review may be instituted only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). For the reasons given below, on this record, Petitioner has established a reasonable likelihood that it would prevail in showing the unpatentability of at least one of the challenged claims. We determine that institution of an inter partes review of the challenged claims is appropriate. B. Real Parties in Interest” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

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

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

  RulingsInstitution decision

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

    “presented in a petition and preliminary response shows that “there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). For the reasons explained below, we determine that Petitioner establishes a reasonable likelihood that it would prevail with respect to at least one challenged claim. Accordingly, we institute an inter partes review as to the challenged claims and the grounds raised in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

    “4. Remaining Terms No express construction of any other claim term is necessary to determine whether to institute inter partes review. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D.” slip op. at 12

  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,936,693

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.