• 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
• Jumio Corporation v. Facetec, Inc.No claims unpatentable
  PTAB · Jun 17, 2026 · IPR2025-00109 · APJ Bach V Hoang · IPR · Final written decision

  Claims 1–24 were not shown unpatentable because the petitioner failed to establish motivation to combine the references and failed to show the claimed different-distance image capture.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Having considered the full record at trial, we maintain the preliminary finding regarding the level of ordinary skill in the art. See Inst. Dec. 11–12. In particular, based on the teachings of the ’910 Patent and the asserted prior art, we are persuaded that an ordinarily skilled artisan would have had a work experience related to biometrics, facial authentication, computer vision, and/or optics as at least one of those fields is respectively implicated by the ’910 Patent and the asserted prior at. Moreover, our decision would be the same under either proposed level of skill.” slip op. at 10

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

    “C. Claim Construction We interpret claim terms using “the same claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. 282(b).” 37 C.F.R. § 42.100(b). Under the principles set forth by the Federal Circuit, the “words of a claim ‘are generally given their ordinary and customary meaning,’” as would be understood by a person of ordinary skill in the art at the time of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc) (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The parties do not dispute any claim terms or phrases and our decision does not require construing any particular claim terms or phrases, therefore, we do not expressly construe any particular claim term or phrase. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’”” slip op. at 10

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

    “We find that these reasons would not have adequately motivated a person having ordinary skill in the art to combine and modify the references in Petitioner’s asserted manner to reach the claimed features. Petitioner’s motivations — “substitution,” “obvious alternative . . . approaches,” “use of a known technique,” and “complimentary” techniques — are all similarly based on swapping or adding techniques for verifying three dimensionality. See Pet. 13–17; Pet. Reply 16–17. Those motivations might have been suitable had Tanii described techniques to verify three dimensionality, but Petitioner has not shown that Tanii describes any technique to verify three dimensionality. See Pet. 13–17, 25–28. Instead, as discussed above, Tanii describes the existence of the perspective distortion phenomenon and a technique for correcting it. As such, substituting the knowledge that perspective distortion exists and techniques to correct it does not correspond adequately motivate Petitioner’s combination. Put another way, because Tanii does not teach an approach for verifying three-dimensionality, Tanii’s techniques cannot be used as a substitute for approaches that do verify three dimensionality simply because Tanii discloses the concept of perspective distortion.” slip op. at 16

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

    “distance from the user. Derakhshani teaches two different approaches (1) focus-distance approach and (2) parallax approach. Petitioner acknowledges that the focus-distance approach does not expressly disclose capturing a second image at a second distance. Pet. 13 (distinguishing “focus distances” from “actual distances.”). This is because focus-distance, by definition, is not actual distance. Ex. 1005, 16:47–48 (“Focus distance is the distance from a sensor to a point in its field of view that is perfectly in focus.”) In Derakhshani’s focus-distance approach the camera stays the same distance from its subject—only the focus distance changes. Id. at 16:66–17:2 (“By comparing degree of focus for a landmark in images with different focus distances, the distance from the sensor to the landmark may be estimated.”) Derakhshani’s parallax approach also does not expressly disclose capturing a second image at a second distance. In the parallax approach the camera is rotated or slid about the user to create images with different perspectives. Ex. 1005, 17:59–64 (“In some implementations, the sensor is moved about the subject during image capture to collect image data from different orientations relative to the subject. For example, a single camera may be rotated or slid slightly or multiple cameras at different positions may be used for image capture.”). Rotating a camera around a user does not change the distance of the camera from the user. At the hearing Petitioner, indicating that Derakhshani takes a second image at a second distance. Tr. 16:9–12 (“[Petitioner’s Counsel: . . . Dr. Daft is talking about some of the terms that Derakhshani is using. For example, the term slid and shown in the images, he talks about how slid refers to the different distances between the sensor and the user.”). We determine that it is more likely that the word “slid,” as used in the relevant portion of Derakhshani, further describes the rotation of the camera about the user. Derakhshani indicates as much by describing that both rotating and sliding the camera are examples of how the camera sensor is “moved about the subject during image capture.” Ex. 1005, 17:60–61. Thus, sliding the camera does not necessarily disclose moving the camera to a second distance from the subject. Zhang also does not expressly disclose capturing a second image at a second distance. Petitioner acknowledges as much stating “[a]lthough Zhang does not expressly say that the second image is captured at a second distance different from the distance of the first image, this would have been obvious to a POSITA.” Pet. 61 (citing Ex. 1003 ¶ 1046). Because Zhang does not expressly disclose capturing a second image at a second distance, Petitioner once again relies on expert testimony to argue that the multiple images disclosed in Zhang would have been taken at different perspectives resulting from rotating or translating the position of the camera and that taking images at different distances would have enhanced Zhang’s homography-transformation procedure. Pet. 61–62 (citing Ex. 1003 ¶ 1046). From here Petitioner repeats many of the same arguments it made regarding the parallax approach from Derakhshani, except that these arguments are on even weaker footing because Zhang does not mention taking images by translating the position of the camera, nor even that the multiple images taken should be from different perspectives. Each of these assertions are made solely on the basis of Petitioner’s expert testimony, and as such are not persuasive. Pet. 61–62 (citing Ex. 1003 ¶¶ 1046). Petitioner’s argument that Zhang teaches capturing a second image at a second distance simply lacks sufficient support from Zhang’s disclosure.” slip op. at 25

  Patent outcomesUS 11,874,910 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,874,910
• Jumio Corp. v. Facetec, Inc.No claims unpatentable
  PTAB · Jun 17, 2026 · IPR2025-00108 · APJ Nabeel U Khan · IPR · Final written decision

  Claims 1–24 were not shown unpatentable because the asserted combinations lacked adequate motivation to combine and did not teach capturing images at different distances.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner argues Petitioner’s proffered level of skill is too broad with respect to work experience. PO Resp. 27–28. Patent Owner counters that a person having ordinary skill in the art would have had a Bachelor’s degree in electrical engineering, computer engineering, computer science, physics, or a related field, and two years’ work experience related to biometric security, facial authentication, and three-dimensional computer vision such that they would have had significant academic and/or work experience in both facial biometrics and computer vision. Id. at 28–29. Having considered the full record at trial, we maintain the preliminary finding regarding the level of ordinary skill in the art. See Inst. Dec. 13–14. In particular, based on the teachings of the ’938 patent and the asserted prior art, we are persuaded that an ordinarily skilled artisan would have had a work experience related to biometrics, facial authentication, computer vision, and/or optics as at least one of those fields is respectively implicated by the ’938 patent and the asserted prior at. Moreover, our decision would be the same under either proposed level of skill.” slip op. at 9

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

    “C. Claim Construction We interpret claim terms using “the same claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. 282(b).” 37 C.F.R. § 42.100(b). Under the principles set forth by the Federal Circuit, the “words of a claim ‘are generally given their ordinary and customary meaning,’” as would be understood by a person of ordinary skill in the art at the time of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc) (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The parties do not dispute any claim terms or phrases and our decision does not require construing any particular claim terms or phrases, therefore, we do not expressly construe any particular claim term or phrase. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 10

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

    “images are three dimensional—let alone a technique that captures two images at different distances, compares the images for certain differences, and verifies three dimensionality based on those differences, as recited by the claim. Instead, Tanii describes a system that “corrects warp in which the perspective is exaggerated when an image is captured with the user’s face at close range.” Ex. 1007, code (57). In particular, Tanii recognizes the physical phenomenon of perspective distortion (fish-eye distortion) where “[i]f the image of the face of a person or the like is captured from a point that is relatively nearby, an image is obtained in which the perspective appears exaggerated,” i.e., the user image is warped or distorted. Id. ¶ 6; see id. ¶ 48, Fig. 4B. Tanii corrects such warped images by enlarging peripheral areas of the user image. Id. ¶¶ 55–56.” slip op. at 17

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

    “distance from the user. Derakhshani teaches two different approaches: (1) focus-distance approach and (2) parallax approach. Petitioner acknowledges that the focus-distance approach does not expressly disclose capturing a second image at a second distance. Pet. 12 (distinguishing “focus distances” from “actual distances.”). This is because focus-distance, by definition, is not actual distance. Ex. 1005, 16:47–48 (“Focus distance is the distance from a sensor to a point in its field of view that is perfectly in focus.”) In Derakhshani’s focus-distance approach the camera stays the same distance from its subject—only the focus distance changes. Id. at 16:66–17:2 (“By comparing degree of focus for a landmark in images with different focus distances, the distance from the sensor to the landmark may be estimated.”) Derakhshani’s parallax approach also does not expressly disclose capturing a second image at a second distance. In the parallax approach the camera is rotated or slid about the user to create images with different perspectives. Derakhshani, 17:59–64 (“In some implementations, the sensor is moved about the subject during image capture to collect image data from different orientations relative to the subject. For example, a single camera may be rotated or slid slightly or multiple cameras at different positions may be used for image capture.”). Rotating a camera around a user does not change the distance of the camera from the user. At the hearing Petitioner, instead, focused specifically on the use of the word “slid” in Derakhshani as indicating that Derakhshani takes a second image at a second distance. Tr. 16:9–12 (“[Petitioner’s Counsel: . . . Dr. Daft is talking about some of the terms that Derakhshani is using. For example, the term slid and shown in the images, he talks about how slid refers to the different distances between the sensor and the user.”). We determine that it is more likely that the word “slid,” as used in the relevant portion of Derakhshani, further describes the rotation of the camera about the user. Derakhshani indicates as much by describing that both rotating and sliding the camera are examples of how the camera sensor is “moved about the subject during image capture.” Derakhshani, 17:60–61. Thus, sliding the camera does not necessarily disclose moving the camera to a second distance from the subject.” slip op. at 27

  Patent outcomesUS 11,693,938 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 11,693,938
• Jumio Corporation v. Facetec, Inc.No claims unpatentable
  PTAB · Jun 17, 2026 · IPR2025-00107 · APJ Bach V Hoang · IPR · Final written decision

  Claims 1–20 were not determined unpatentable because the petition did not establish motivation to combine the references or that they taught capturing images at different distances.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for patent owner

    “Patent Owner argues Petitioner’s proffered level of skill is too broad with respect to work experience. PO Resp. 27–28. Patent Owner counters that a person having ordinary skill in the art would have had a Bachelor’s degree in electrical engineering, computer engineering, computer science, physics, or a related field, and two years’ work experience related to biometric security, facial authentication, and three-dimensional computer vision such that they would have had significant academic and/or work experience in both facial biometrics and computer vision. Id. at 28–29. Having considered the full record at trial, we maintain the preliminary finding regarding the level of ordinary skill in the art. See Inst. Dec. 8. In particular, based on the teachings of the ’606 Patent and the asserted prior art, we are persuaded that an ordinarily skilled artisan would have had a work experience related to biometrics, facial authentication, computer vision, and/or optics as at least one of those fields is respectively implicated by the ’606 Patent and the asserted prior at. Moreover, our decision would be the same under either proposed level of skill.” slip op. at 9

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

    “The parties do not dispute any claim terms or phrases and our decision does not require construing any particular claim terms or phrases, therefore, we do not expressly construe any particular claim term or phrase. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 10

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

    “We find that these reasons would not have adequately motivated a person having ordinary skill in the art to combine and modify the references in Petitioner’s asserted manner to reach the claimed features. Petitioner’s motivations—“substitution,” “obvious alternative . . . approaches,” “use of a known technique,” and “complimentary” techniques—are all similarly based on swapping or adding techniques for verifying three dimensionality. See Pet. 12–16; Pet. Reply 6–7. These motivations might have been suitable had Tanii described techniques for verifying three dimensionality, but Petitioner has not shown that Tanii describes any technique to verify three dimensionality. See Pet. 12–16, 19–23. Instead, as discussed above, Tanii describes the existence of the perspective distortion phenomenon and a technique for correcting it. As such, substituting the knowledge that perspective distortion exists and techniques to correct it does not correspond with approaches for verifying three-dimensionality, and so does not adequately motivate Petitioner’s combination. Put another way, because Tanii does not teach an approach for verifying three-dimensionality, Tanii’s techniques cannot be used as a substitute for approaches that do verify three dimensionality simply because Tanii discloses the concept of perspective distortion.” slip op. at 16

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia with nexusObjective indicia outweighedDecided for patent owner

    “Patent Owner has demonstrated a nexus by showing that certain objective indicia, discussed below, are the direct result of the unique characteristics of the claimed invention. As discussed above in our summary of the ’606 Patent and reflected in our discussion of Petitioner’s obviousness challenges (see §§ I.F, II.E.1, II.E.2, II.E.3), the unique characteristics of the claim relate to verification of three dimensionality by comparing two images taken at different distances for perspective distortion. Indeed, those features are what distinguish over the prior art. See id. Furthermore, Patent Owner, supported by testimony from its Chief Technology Officer, Mr. Rose, asserts the unique characteristics claimed are reflected in the “3D liveness checks” its ZoOm software product provides because ZoOm “confirms that a user is 3D by comparing images taken at different distances for expected differences in biometric data, such as the presence of appropriate perspective distortion and differences.” PO Resp. 25 (citing Ex. 2059 ¶ 49). Patent Owner’s assertion is further supported by a “FaceTec Software Explanation” stating that its software uses “near & far image data . . . to determine if the expected differences in perspective distortion are present in the image data” and, from that, “decides if there is sufficient evidence in the image data to conclude with a high degree [of] confidence that the image data contains first-generation biometric data captured in real-time from a live, physically present user.” Ex. 2067; see PO Resp. 25–26. As such, the 3D liveness checks provided by Patent Owner’s software are indicative of the unique characteristics of the claimed invention and, as we discuss below, certain objective indicia of nonobviousness have a direct nexus to the 3D liveness checks of its software.” slip op. at 30

  Patent outcomesUS 11,157,606 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,157,606
• Jumio Corp. v. Facetec, Inc.No claims unpatentable
  PTAB · Jun 17, 2026 · IPR2025-00106 · APJ Nabeel U Khan · IPR · Final written decision

  The Board determined claims 1–20 were not unpatentable because Jumio did not show sufficient motivation to combine the references or that they taught capturing images at different distances.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner argues Petitioner’s proffered level of skill is too broad with respect to work experience. PO Resp. 28. Patent Owner counters that a person having ordinary skill in the art would have had a Bachelor’s degree in electrical engineering, computer engineering, computer science, physics, or a related field, and two years’ work experience related to biometric security, facial authentication, and three-dimensional computer vision such that they would have had significant academic and/or work experience in both facial biometrics and computer vision. Id. at 28–29. Having considered the full record at trial, we maintain the preliminary finding regarding the level of ordinary skill in the art. See Inst. Dec. 11–12. In particular, based on the teachings of the ’471 patent and the asserted prior art, we are persuaded that an ordinarily skilled artisan would have had a work experience related to biometrics, facial authentication, computer vision, and/or optics as at least one of those fields is respectively implicated by the ’471 patent and the asserted prior at. Moreover, our decision would be the same under either proposed level of skill.” slip op. at 10

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

    “that would be used to construe the claim in a civil action under 35 U.S.C. 282(b).” 37 C.F.R. § 42.100(b). Under the principles set forth by the Federal Circuit, the “words of a claim ‘are generally given their ordinary and customary meaning,’” as would be understood by a person of ordinary skill in the art at the time of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc) (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The parties do not dispute any claim terms or phrases and our decision does not require construing any particular claim terms or phrases, therefore, we do not expressly construe any particular claim term or phrase. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 10

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

    “We find that these reasons would not have adequately motivated a person having ordinary skill in the art to combine and modify the references in Petitioner’s asserted manner to reach the claimed features. Petitioner’s motivations—“substitution,” “obvious alternative . . . approaches,” “use of a known technique,” and “complimentary” techniques—are all similarly based on swapping or adding techniques for verifying three dimensionality. See Pet. 12–16; Pet. Reply 6–7. These motivations might have been suitable had Tanii described techniques for verifying three dimensionality, but Petitioner has not shown that Tanii describes any technique to verify three dimensionality. See Pet. 13–17, 25–28. Instead, as discussed above, Tanii describes the existence of the perspective distortion phenomenon and a technique for correcting it. As such, substituting the knowledge that perspective distortion exists and techniques to correct it does not correspond with approaches for verifying three-dimensionality, and so does not adequately motivate Petitioner’s combination. Put another way, because Tanii does not teach an approach for verifying three-dimensionality, Tanii’s techniques cannot be used as a substitute for approaches that do verify three dimensionality simply because Tanii discloses the concept of perspective distortion.” slip op. at 18

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

    “none of the relied upon references teach capturing two images at two different distances, as required by limitations 1[d3] and 1[d4]. These limitations recite “moving the camera from a first location to a second location, the second location being a second distance from the user” and “capturing at least one second image of the user taken with the camera of the computing device at the second distance from the user, the second distance being different than the first distance.” Derakhshani does not teach capturing a second image at a second distance from the user. Derakhshani teaches two different approaches: (1) focus-distance approach and (2) parallax approach. Petitioner acknowledges that the focus-distance approach does not expressly disclose capturing a second image at a second distance. Pet. 13 (distinguishing “focus distances” from “actual distances.”). This is because focus-distance, by definition, is not actual distance. Ex. 1005, 16:47–48 (“Focus distance is the distance from a sensor to a point in its field of view that is perfectly in focus.”) In Derakhshani’s focus-distance approach the camera stays the same distance from its subject—only the focus distance changes. Id. at 16:66–17:2 (“By comparing degree of focus for a landmark in images with different focus distances, the distance from the sensor to the landmark may be estimated.”) Derakhshani’s parallax approach also does not expressly disclose capturing a second image at a second distance. In the parallax approach the camera is rotated or slid about the user to create images with different perspectives. Ex. 1005, 17:59–64 (“In some implementations, the sensor is moved about the subject during image capture to collect image data from different orientations relative to the subject. For example, a single camera may be rotated or slid slightly or multiple cameras at different positions may be used for image capture.”). Rotating a camera around a user does not change the distance of the camera from the user. At the hearing Petitioner, instead, focused specifically on the use of the word “slid” in Derakhshani as indicating that Derakhshani takes a second image at a second distance. Tr. 16:9–12 (“[Petitioner’s Counsel: . . . Dr. Daft is talking about some of the terms that Derakhshani is using. For example, the term slid and shown in the images, he talks about how slid refers to the different distances between the sensor and the user.”). We determine that it is more likely that the word “slid,” as used in the relevant portion of Derakhshani, further describes the rotation of the camera about the user. Derakhshani indicates as much by describing that both rotating and sliding the camera are examples of how the camera sensor is “moved about the subject during image capture.” Derakhshani, 17:60–61. Thus, sliding the camera does not necessarily disclose moving the camera to a second distance from the subject.” slip op. at 27

  Patent outcomesUS 10,776,471 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,776,471
• Taiwan Semiconductor Manufacturing Company Ltd. v. Marlin Semiconductor LimitedAdverse judgment
  PTAB · May 13, 2026 · IPR2025-01082 · APJ David C Mckone · IPR · Adverse judgment

  The Board granted Patent Owner’s request for adverse judgment after it disclaimed the entire patent term, entering judgment against claims 1–10.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “A party may request entry of adverse judgment against itself at any time during an inter partes review proceeding. See 37 C.F.R. § 42.73(b). In addition, “[a]ctions construed to be a request for adverse judgment include: (1) Disclaimer of the involved application or patent; [and] (2) Cancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” Id. Because Patent Owner has explicitly requested adverse judgment against itself pursuant to Rule 42.73(b), and has disclaimed the entire term of the ’181 patent, Patent Owner’s request for adverse judgment is granted.” slip op. at 3

  None
  Patents in suitUS 6,888,181
• Samsung Display Co., Ltd. v. Pictiva Displays International Ltd.No claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01223 · APJ Garth D Baer · IPR · Final written decision

  Claims 34–37 and 40–46 were not shown unpatentable because Suzuki’s organic barrier layer was not shown to meet the agreed construction of “planarization layer.”

  RulingsFinal written decision

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

    “layer of material that planarizes such that the propagation of defects from one layer to another layer can be interrupted and the topography of the underlying layer and/or structure is not reproduced.” PO Resp. 10. According to Patent Owner, we should adopt this construction because the parties agreed to it in a related district court proceeding and it is supported by the intrinsic evidence. Id. at 10–14. Petitioner does not dispute this 1 Japanese Published Application No. H09-245964, Pub. Sep. 19, 1997 (Ex. 1010, “Kijima”) (English translation). 2 US 6,198,217, Pub. Mar. 6, 2001 (Ex. 1012, “Suzuki”). 3 US 6,087,196, Pub. July 11, 2000 (Ex. 1013, “Sturm”). 4 WO 2001/08242, Pub. Feb. 1, 2001 (Ex. 1016, “Duthaler”). 5 Japanese Published Application No. H10-41069, Pub. Feb. 13, 1998 (Ex. 1014, “Fujimori”) (English translation). construction. Paper 33, 6:17–8:1; see Pet. Reply 5. We adopt the parties’ agreed-to construction.” slip op. at 4

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

    “Petitioner argues Suzuki’s organic barrier layer does not reproduce the underlying layer’s/structure’s topography because “Suzuki’s organic barrier layer 20 ‘makes a smooth surface on the relatively irregular surface of the cathode 18.’” Pet. Reply 7 (quoting Ex. 1012, 5:59–67). We disagree. Instead, we agree with Patent Owner that Suzuki’s irregular-surface smoothing describes covering defects, not suppressing the underlying cathode’s topography. PO Sur-reply 5. The smooth-surface passage that Petitioner highlights comes immediately after two sentences describing inevitable “defects,” “pinholes,” and “foreign matter” on the cathode surface and before a sentence describing “ensuring the formation of the layer 22, which is substantially defect-free.” Ex. 1012, 5:52–67. Suzuki’s organic barrier 20 “makes a smooth surface” by covering defects because the defects are the only source of the “irregularity” that Suzuki refers to here. Id. We note Mr. Humphrey’s testimony, which we credit in this regard, that the “defects are created incidentally on the surface of the underlying layer and are generally not considered to be part of the underlying layer’s topography, which is a macroscopic property by design” and that the organic layer is not a planarization layer because it would reproduce the topography of the underlying layer. Ex. 2018 ¶¶ 47–48. Because the parties’ agreed-to construction of “planarization layer” “requires ‘a layer of material that planarizes’ for two distinct functions,” Petitioner’s showing of just one of those functions is insufficient. PO Sur-reply 2.” slip op. at 8

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “G. Level of Skill in the Art Petitioner argues a person of ordinary skill in the art “would have had a bachelor’s degree in Electrical Engineering, Materials Science, or a related field, and at least one year of experience in display technologies” and that “[a]dditional education might compensate for a deficiency in experience, and vice-versa.” Pet. 14–15. Patent Owner does not dispute the level of ordinary skill in the art. We agree with and adopt Petitioner’s proposal as reasonable and consistent with the level of skill reflected in both the prior art and the ’389 patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 6

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “which is substantially defect-free.” Ex. 1012, 5:52–67. Suzuki’s organic barrier 20 “makes a smooth surface” by covering defects because the defects are the only source of the “irregularity” that Suzuki refers to here. Id. We note Mr. Humphrey’s testimony, which we credit in this regard, that the “defects are created incidentally on the surface of the underlying layer and are generally not considered to be part of the underlying layer’s topography, which is a macroscopic property by design” and that the organic layer is not a planarization layer because it would reproduce the topography of the underlying layer. Ex. 2018 ¶¶ 47–48. Because the parties’ agreed-to construction of “planarization layer” “requires ‘a layer of material that planarizes’ for two distinct functions,” Petitioner’s showing of just one of those functions is insufficient. PO Sur-reply 2.” slip op. at 9

  Patent outcomesUS 6,949,389 not shown unpatentable
  Claim construction§ 103 obviousness
  Patents in suitUS 6,949,389
• Samsung Display Co., Ltd. v. Pictiva Displays International Ltd.All claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01222 · APJ Garth D Baer · IPR · Final written decision

  Claims 34–37 and 40–46 are unpatentable as obvious over the Yamazaki-based and Weaver-based grounds.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “Patent Owner bears the burden of production to establish that its claimed invention is entitled to an earlier priority date for this fact-intensive issue. See In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1375–76 (Fed. Cir. 2016). We agree with Petitioner that the email chain does not support Patent Owner’s conception claim because it “does not discuss depositing a planarization layer, as required by both independent claims.” Pet. Reply 3. Patent Owner asserts that the inventor’s discussion of “PML” (polymer multi-layer) encapsulation in the email chain shows their conception of the claimed planarization layer because the ’389 patent describes that PMLs “‘[t]ypically’ include[e] ‘a planarization layer’ that ‘is provided to give a planar surface’ for deposition of an upper layer,” and “‘address ‘any point defects (i.e. pin holes)’ that might appear in the barrier layer’s surface.” PO Resp. 6 (quoting Ex. 1001, 1:31–37, 1:41–44, 1:56–62). We disagree with Patent Owner for two reasons. First, the challenged patent’s specification does not corroborate that the inventors conceived the claimed planarization before the challenged patent’s priority because it did not exist at the time of the email. Whether the inventors, at the time of filing, considered PMLs to typically include a planarization layer as of the claimed priority date does not support the allegation that they conceived of that same planarization layer more than a year earlier. Moreover, the ’389 patent’s teaching that “[t]ypically, for PML structures, a planarization layer 106 is formed” (Ex. 1001, 1:30–31) shows that the inventors recognized PML structures and planarization layers were distinct because only a subset of PML structures formed planarization layers, even if they do so typically. Thus, the inventor’s discussion of a PML layer in the email chain does not evidence their conception of the claimed planarization layer, as Patent Owner contends. Additionally, even if we were to understand the inventors’ mention of PML encapsulation in the emails, together with the discussion of patterning techniques for an organic layer, as discussing a planarization layer, such discussions are evidence of brainstorming ideas, rather than documenting the path taken with the claimed invention. For instance, the inventors use phrases like “don’t know if this will work,” “these are all just ‘undeveloped’ ideas,” and “looking forward to keep this discussion rolling.” Ex. 2006, 1; see also Ex. 1034, 59:22−59:18. As Petitioner argues, and we agree, these are more theoretical and future-development discussions than an exchange of a definite idea. Pet. Reply 2−3 (citing Hybritech Inc. v. Monoclonal Antibodies, Inc., 802 F.2d 1367, 1376 (Fed. Cir. 1986). For these reasons, we agree with Petitioner that Patent Owner has not” slip op. at 6

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Applicant-admitted prior artDecided for petitioner

    “B. Whether Petitioner Relies on Applicant Admitted Prior Art Patent Owner asserts we should “not consider” Yamazaki-based challenges because Petitioner included Applicant Admitted Prior Art (AAPA) in those grounds. See PO Resp. 16 (citing Qualcomm Incorporated v. Apple Inc., 134 F.4th 1355 (Fed. Cir. 2025)) (holding that AAPA may not be part of the basis for an inter partes review). We disagree. As Petitioner notes, it “utilizes the AAPA in the alternative with Ghosh, to show that it was known to manufacture OLED devices in bulk (which [Patent Owner] does not dispute).” Pet. Reply 9. Because “[t]he Petition identifies disclosures in Ghosh that independently demonstrate the same teachings for which the AAPA is cited,” we agree with Petitioner that it does not improperly rely on AAPA for any of its challenges. Id.” slip op. at 8

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “C. Whether Yamazaki, Weaver, and Palanisamy Are Printed Publications under 35 U.S.C. § 311(b) Patent Owner asserts that Yamazaki, Weaver, and Palanisamy do not qualify as printed publications under 35 U.S.C. § 311(b) because they only qualify as prior art under § 102(e). PO Resp. 17. According to Patent Owner, “[e]ven though the Federal Circuit has held that such references are ‘printed publications’ under 311(b), to preserve arguments on appeal, Patent Owner submits that such an interpretation is inconsistent with the plain statutory language, the precedent, and non-public accessibility of an unpublished patent application.” Id. We disagree with this argument because the Federal Circuit has rejected it, as Patent Owner acknowledges. See Lynk Labs, Inc. v. Samsung Electronics Co., 2023-2346, Slip. Op. (Fed. Cir. Jan. 14, 2025).” slip op. at 8

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

    “Yamazaki does not involve multiple devices on a substrate” and Ghosh teaches “non-selective deposition of at least the barrier layer.” PO Resp. 31. We disagree with this argument because it attacks Yamazaki and Ghosh individually, rather than the combination of Yamazaki’s selective deposition and Ghosh’s plurality of devices that Petitioner asserts. See In re Keller, 642 F.2d 413, 426 (CCPA 1981). We also disagree with Patent Owner’s criticism that Petitioner fails to explain why skilled artisans would have ignored Ghosh’s non-selective deposition method for barrier layers on multiple devices. PO Resp. 32. This argument attacks a straw man as Petitioner does not propose modifying Ghosh’s method with Yamazaki’s selective deposition. See Pet. 21–23. Rather, Petitioner proposes modifying Yamazaki’s selective deposition method by applying it to Ghosh’s teaching of encapsulating a plurality of OLED devices. Id. Next, Patent Owner asserts that skilled artisans would not have extended Yamazaki’s single-device fabrication/encapsulation method to a plurality of devices on a substrate because doing so would “multiply defects and errors, drop the yield exponentially, and increase the cost.” PO Resp. 34. Patent Owner asserts that precision/defect problems would be particularly acute when using Yamazaki’s inkjet method to print devices’ electro luminescence layers. Id. at 35–36. We disagree. Even if extending Yamazaki’s method to Ghosh’s multiple devices comes at a cost of potential defects, that tradeoff would not undermine Petitioner’s proffered combination given Petitioner’s articulated benefits outline above, including facilitating manufacturing display panels for OLEDs with improved throughput, improved productivity, and reduced manufacturing costs, as compared to fabricating/encapsulating just a single device. See Winner Int’l Royalty Corp. v. Wang, 202 F.3d 1340, 1349 n.8 (Fed. Cir. 2000) (“The fact that the motivating benefit comes at the expense of another benefit, however, should not nullify its use as a basis to modify the disclosure of one reference with the teachings of another.”). It also does not matter that “inkjet printing yielded devices of half the efficiency than spin coating,” as Patent Owner asserts (PO Resp. 35), because Petitioner does not need to show that Yamazaki’s inkjet printing would be the best option for batch fabrication/encapsulation, only that it would was a suitable one from which the prior art did not teach away. See Par Pharm., Inc. v. TWi Pharms., Inc., 773 F. 3d 1186, 1197–98 (Fed. Cir 2014). That is, Petitioner does not need to show that Yamazaki’s inkjet method was an improvement over other known fabrication/encapsulation methods, so long as it was a known fabrication/encapsulation method and skilled artisans would understand that implementing it for a plurality of devices had known advantages over fabricating/encapsulating a single device, which Petitioner identifies. See Pet. 22. We also agree with Dr. Subramanian that skilled artisans would have a reasonable expectation of success in making the proposed combination given similarities between the references (both are directed to encapsulation of an OLED display device with multiple thin-film layers and at least the first encapsulation is selectively deposited) and because “as the ’389 patent admits, in the prior art it was conventional to use batch fabrication to manufacture OLED display devices with thin-film encapsulation.” Ex. 1003 ¶ 86. As Dr. Subramanian explains, a particular advantage of inkjet printing is that it scales well to larger areas and it was known at the time of the ’389 patent that inkjet could be used to print multiple devices on a glass substrate. Ex. 1032 ¶¶ 2, 27–28. Patent Owner’s argument that “Yamazaki’s methods are far from ready for manufacturing” (PO Resp. 34) goes well beyond what is necessary to show that skilled artisans would have had a reasonable expectation of achieving what is claimed. See Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1367 (Fed. Cir. 2016). Given Petitioner’s analysis outlined above, we agree with Petitioner that it would have been obvious to skilled artisans to fabricate and encapsulate multiple OLED devices on a substrate using Yamazaki’s ink-jet methods. slip op. at 15

  Patent outcomesUS 6,949,389 unpatentable
  § 102 anticipation§ 103 obviousnesscites KSR
  Patents in suitUS 6,949,389

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.