- Resmed Corp. v. Cleveland Medical Devices, Inc.No claims unpatentablePTAB · Jun 29, 2026 · IPR2025-00247 · APJ Cynthia M Hardman · IPR · Final written decision
Claims 1–19 were not shown unpatentable under any of six obviousness grounds because Truitt did not teach or suggest the claimed severity calculation and index, and the Mumford combinations lacked the required sensor disclosures.
RulingsFinal written decision- PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner
“Patent Owner filed an authorized Motion to Terminate, alleging that Petitioner failed to name its corporate parent, Resmed Inc., as a real party in interest. Paper 29. Petitioner filed an opposition. Paper 31. Patent Owner filed a reply. Paper 32. We denied the Motion to Terminate. Paper 40.” slip op. at 2
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“disorder symptoms” require a “quantitative” calculation or use of an algorithm, we also disagree. See PO Resp. 14–16. First, nothing in the language of the claims themselves describes or requires a “quantitative” calculation or an algorithm. See generally Ex. 1001, 23:6–26:59. To be sure, the ’029 patent discloses embodiments that use known algorithms to “quantify the level of severity of the subject’s sleeping disorder or symptoms.” See, e.g., id. at 20:16–19. But the Specification does not require an algorithm. The Specification also indicates that quantification is merely “preferable” (i.e., not required), and is merely one embodiment. See, e.g., id. at 19:8–12 (“The signals from the one or more sensors used in various embodiments of the present invention are preferably analyzed using a processor and software that can quantitatively estimate or determine the severity of the subject’s sleeping disorder or symptoms.”) (emphasis added), 4:51–59 (“Finally, in still another embodiment, the present invention includes a sleeping disorder treatment system comprising a device for diagnosing and creating a quantitative output of a level of severity of a subject’s sleeping disorder or symptoms . . . .”) (emphasis added); see also Reply 5–6 (citing Ex. 1001, 4:3–59 and 19:8–12 and stating that the ’029 patent lists “numerous embodiments where only one of seven include a quantitative assessment”). Elsewhere, the Specification more generally states that signals from sensors are “analyzed to determine the level of severity of the symptoms,” without specifying that such analysis must be “quantitative” or performed by an algorithm. See Ex. 1001, 3:41–44. In view of these disclosures, Patent Owner does not persuade us to adopt its narrowing claim construction. Indeed, our reviewing court has “repeatedly warned against confining the claims” to specific embodiments disclosed in the Specification. Phillips, 415 F.3d at 1323. Patent Owner’s reliance on a prior Board decision in PGR2024- 00012, which related to the parent of the ’029 patent, is unavailing. See PO Resp. 15–16. We agree with Petitioner that in the cited case, “[t]he Board made no findings about the meaning of the term calculating ‘the data of a severity of the sleep disorder symptoms of the subject’ for claim construction.” Reply 8. Indeed, neither party offered any claim construction, and the Board determined that no claim construction was necessary for purposes of that decision. See ResMed Corp., PGR2024- 00012, Paper 7 at 8. The page of the decision Patent Owner cites addresses written description support in the specification for the claims challenged in that PGR, not claim construction. See id. at 16. In any event, the cited decision is a decision on institution. The Board’s statements there are, by nature, preliminary findings and conclusions based on a preliminary record, and are not binding here. For at least the above reasons, Patent Owner does not persuade us to adopt its narrowing claim construction and we find that the term “data of a severity” does not need construction because the words of the term are clear on their face.” slip op. at 31
- Strike new argumentNew argument disregardedDecided for patent owner
“skilled artisan would have incorporated only portions of Mumford’s algorithm into Truitt’s PAP (i.e., only those portions related to “the detection of sleep disordered events” and not the portions of the algorithm related to “determin[ing] sleep stage”) comes too late because this argument was not in the Petition. See, e.g., Wasica Fin. GmbH v. Cont’l Auto. Sys., Inc., 853 F.3d 1272, 1286–87 (Fed. Cir. 2017) (rejecting petitioner’s “attempts to cure the petition’s deficiencies in its subsequent briefing to the Board”). The Petition does not discuss modifying Mumford’s sleep efficacy algorithm before incorporating it into Truitt’s PAP device or incorporating only certain features of the algorithm. Indeed, the Petition and Dr. Kirkness rely on Mumford’s ability to detect sleep arousals when mapping Mumford to the claimed “data of a severity” and “index.” See Pet. 69–70; Ex. 1003 (Kirkness Decl.) ¶¶ 323–325. Mumford discloses that the mask electrodes detect arousals. See Ex. 1009 (Mumford) 2:4–10, 11:39–48. The same lack of disclosure plagues Petitioner’s belated Reply argument that Truitt’s ports 74 and 76 can incorporate electric sensing elements that would have functioned similar to Mumford’s electrodes. See Reply 22. The Petition did not mention ports 74 and 76 or otherwise suggest that a skilled artisan would have added functionality similar to Mumford’s electrodes to Truitt’s PAP, and we find that it is too late on Reply for Petitioner to posit this modification.” slip op. at 40
- Expert testimonyPetitioner expert creditedPatent owner expert creditedMixed
“significant than the intrinsic record in determining ‘the legally operative meaning of claim language.’” Phillips v. AWH Corp., 415 F.3d 1303, 1317 (Fed. Cir. 2005). This is especially applicable to Dr. Jafari’s opinions. His declaration was not prepared for this proceeding and thus Dr. Jafari was not subject to cross examination in this proceeding. See Reply 6 n.3. Moreover, Dr. Jafari was not opining on claim construction; rather, he was addressing the alleged indefiniteness. See Ex. 2020 (Jafari Decl.) 12 (heading addressing definiteness), ¶¶ 41–42, 46. Additionally, paragraphs 41–42 of Dr. Jafari’s declaration discuss claim terms phrases in a different patent (US 11,375,921), which explicitly include the terms “quantified” and “quantitative.” See Reply 6–7; Ex. 2020 (Jafari Decl.) ¶ 34. For at least these reasons, Patent Owner has not persuaded us that Dr. Jafari’s testimony is applicable here. Further, regarding the portion of Patent Owner’s proposed construction reciting “the degree of deviation from the baseline characteristics of a patient without sleep disorder symptoms,” Dr. Borkholder does not do his own analysis, but instead simply states that he “agree[s] with the litigation claim construction opinions of Dr. Jafari.” Ex. 2019 (Borkholder Decl.) ¶ 53. This is insufficient, and thus we do not credit Dr. Borkholder’s testimony regarding claim construction. We instead credit Dr. Kirkness’s statement that “[s]everity data is frequently calculated as the deviation from baseline characteristics of the patient himself, not a generic person ‘without sleep disorder symptoms.’” Ex. 1071 (Kirkness Reply Decl.) ¶ 13; Reply 9. As Dr. Kirkness explains, and Patent Owner does not dispute (see generally Sur-reply), “[t]he ‘baseline characteristics of a [generic] patient without sleep disorder symptoms’ would be irrelevant to any particular patient with their own unique breathing patterns and sleep disorder symptoms.” Ex. 1071 (Kirkness Reply Decl.) ¶ 13 (second alteration in original). For at least these reasons, we reject Patent Owner’s proposed claim construction.” slip op. at 30
Patent outcomesUS 11,872,029 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,872,029 - GD Energy Products, LLC v. Kerr Machine CompanyAll claims unpatentablePTAB · Jun 29, 2026 · PGR2025-00031 · APJ Ryan H Flax · PGR · Final written decision
Claims 1–14 are unpatentable as obvious under each of four asserted grounds: Kerr; Aplex and Stanton; Blume, Stanton, and Wilkinson; and the sale of the Kerr Pump.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“The person of ordinary skill in the art would have a minimum of a bachelor’s degree in mechanical or petrochemical engineering, or a comparable engineering discipline, and a minimum of 3-5 years of work experience in the design and/or manufacturing of reciprocating pumps and valves, including fluid ends and/or comparable high pressure fluid components, for industrial applications, including for use in the oil and gas industry. See, e.g., EX1003, ¶32.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We decline to expressly construe any claim language. slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Regarding the combining of Aplex and Stanton, Petitioner asserts that the ordinarily skilled artisan would have understood that providing a packing/stuffing arrangement, as taught by Stanton, within a fluid end housing, as taught by Aplex, would improve pressure and fluid isolation compared with an arrangement where the packing was bolted to the outside of the fluid end as in Aplex unmodified. Pet. 66 (citing Ex. 1003 ¶¶ 189, 236). Patent Owner does not dispute this rationale. We find this to be a reason, with rationale underpinning, why the person of ordinary skill in the art would have combined these references with a reasonable expectation of success.” slip op. at 29
- Adverse judgmentOther
“The record indicates that Patent Owner has statutorily disclaimed claim 15 as of April 28, 2025. Ex. 2206.” slip op. at 8
Patent outcomesUS 12,152,582 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 12,152,582 - Apple, Inc. v. Wecrevention, Inc.Institution deniedPTAB · Jun 24, 2026 · IPR2026-00241 · APJ John A Squires · IPR · Director review
The Director denied institution of the IPR, finding Apple's unexplained inconsistent claim-construction positions before the Board and district court problematic.
RulingsDirector review decision- Other 314aInstitution denied discretionary otherDenied
“As I have indicated previously, petitioners should be presenting a single construction and applying that construction consistently. See Infineon Techs. Americas Corp. v. Mosaid Techs. Corp., IPR2025-01456, Paper 27 at 3–4 (Director Mar. 17, 2026). Failure to do so, without adequate explanation, is problematic and raises concerns of strategic litigation behavior spill-over into the PTAB inconsistent with Congress’s intent to provide a quick and cost-effective alternative to district court litigation. Id.; Revvo, Paper 20 at 3–4; see H.R. Rep. No. 112-98 at 48 (2011). Here, Petitioner offers no explanation for its divergent positions.” slip op. at 3
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Other
“that “[a]ll claim terms should be construed according to their ordinary and customary meaning,” and that “no claim terms need be construed to resolve issues of controversy in the present Petition.” Paper 2, 4 (emphasis added). Petitioner also states, as part of its analysis of the challenged claims, that “Petitioner does not concede that the preambles of the Challenged Claims are limiting.” Id. at 9 n.5 (emphasis added). In district court, however, Petitioner tells a different story, arguing there that the preamble is limiting. Ex. 2016, 6, 7, 9, 12. Indeed, Petitioner specifically denotes that “[r]eview of ‘the entirety of the patent’ makes clear that the preamble phrase ‘high speed memory chip module’ contains the core of what the inventors ‘actually invented and intended to encompass by the claims,’ . . . and so the preamble should be limiting.” Id. at 7 (internal citations omitted, emphasis added).” slip op. at 2
Claim constructionDiscretionary denialPatents in suitUS 10,998,017 - Apple, Inc. v. Wecrevention, Inc.Institution deniedPTAB · Jun 24, 2026 · IPR2026-00240 · APJ John A Squires · IPR · Director review
The Director denied Apple’s petitions and instituted no trial, exercising discretion based on Apple’s unexplained inconsistent claim-construction positions before the Board and district court.
RulingsDirector review decision- PTAB / AIA Trials › Discretionary denialInstitution denied discretionary otherInstitution denied
“As I have indicated previously, petitioners should be presenting a single construction and applying that construction consistently. See Infineon Techs. Americas Corp. v. Mosaid Techs. Corp., IPR2025-01456, Paper 27 at 3–4 (Director Mar. 17, 2026). Failure to do so, without adequate explanation, is problematic and raises concerns of strategic litigation behavior spill-over into the PTAB inconsistent with Congress’s intent to provide a quick and cost-effective alternative to district court litigation. Id.; Revvo, Paper 20 at 3–4; see H.R. Rep. No. 112-98 at 48 (2011). Here, Petitioner offers no explanation for its divergent positions.” slip op. at 3
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notOther
“that “[a]ll claim terms should be construed according to their ordinary and customary meaning,” and that “no claim terms need be construed to resolve issues of controversy in the present Petition.” Paper 2, 4 (emphasis added). Petitioner also states, as part of its analysis of the challenged claims, that “Petitioner does not concede that the preambles of the Challenged Claims are limiting.” Id. at 9 n.5 (emphasis added). In district court, however, Petitioner tells a different story, arguing there that the preamble is limiting. Ex. 2016, 6, 7, 9, 12. Indeed, Petitioner specifically denotes that “[r]eview of ‘the entirety of the patent’ makes clear that the preamble phrase ‘high speed memory chip module’ contains the core of what the inventors ‘actually invented and intended to encompass by the claims,’ . . . and so the preamble should be limiting.” Id. at 7 (internal citations omitted, emphasis added).” slip op. at 2
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)Other
“IPR2026-00243 are similarly problematic. In its Petitions, Petitioner identifies “input/output unit” as a means-plus-function limitation and identifies the corresponding structure as input/output unit 106 in the challenged patent. See, e.g., IPR2026-00241, Paper 2, 4. Petitioner also asserts “the applied prior art anticipates or renders obvious the Challenged Claims, regardless of whether ‘input/output unit’ is construed as a §112(f) means-plus-function limitation,” and that “Petitioner is not conceding . . . that the ’017 Patent provides adequate structure for the ‘input/output unit.’” Id. at 5 (emphasis added). In District Court, however, Petitioner once again takes a different position, arguing that the claim term “input/output unit” should be construed as a means-plus-function limitation, identifying the function as “performing input and/or output functions with respect to memory,” and asserting that the challenged patent “[l]acks sufficient structure (indefinite).” IPR2026-00241, Ex. 2016, 12. According to Petitioner, “[t]he specification fails to disclose sufficient corresponding structure for performing input and output operations with respect to memory, much less for performing those operations within any particular voltage range.” Id. at 19. Petitioner fails to adequately explain its different positions here before the Board and those it propounds in district court. See, e.g., IPR2026-00241, Paper 9. Patent Owner well states the issue; that “[t]o the extent § 112(f) governs, then either input/output unit 106 is sufficient corresponding structure (in which case [Petitioner’s] district-court indefiniteness argument fails), or it is not (in which case [Petitioner’s] IPR mapping relies on a structure [Petitioner] itself maintains is inadequate).” IPR2026-00241, Paper 8, 8–9. I agree. Petitioner’s statement that it does not concede the challenged patent provides adequate structure for the “input/output unit” thus only compounds the problem.” slip op. at 3
Claim constructionDiscretionary denialPatents in suitUS 9,201,834 - Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentablePTAB · Jun 23, 2026 · IPR2025-00219 · APJ Frederick C Laney · IPR · Final written decision
Claims 11–22 were not shown unpatentable under any § 103 ground because the prior art did not teach or suggest receiving the claimed resource allocation and multi-level TPC command on one physical channel.
RulingsFinal written decision- BurdenNot shown unpatentable
“onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). Moreover, a petitioner should 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284 (2011), amended 35 U.S.C. § 103, effective March 16, 2013. Because the application from which the ’153 patent issued claims priority to an application filed before this date, the pre-AIA version of § 103 applies. not “place the burden on [the Board] to sift through information presented by the Petitioners, determine where each element [of the challenged claims] is found in [the cited references], and identify any differences between the claimed subject matter and the teachings of [the cited references.]” Google Inc. v. EveryMD.com LLC, IPR2014-00347, Paper 9 at 25 (PTAB May 22, 2014).” slip op. at 5
- Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner
“The second and third asserted benefits—reduced complexity and reduced latency—rest on the declaration of Dr. Kotzin (Ex. 1003 ¶ 64) rather than on any disclosure of Andersson or Khan. We accord that testimony little weight on this point because it asserts the benefits in conclusory terms without explaining why they would result from inserting a scheduling grant into Andersson’s undefined “other bits,” as distinct from Khan’s separate-slot design.” slip op. at 20
- Skill levelSkill level petitioner adoptedDecided for petitioner
“A. Level of Ordinary Skill in the Art Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 14. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’500 Patent. Therefore, we adopt it as the ordinary level of skill of an artisan in the field of the patented technology for our analysis below.” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Patent Owner offers a proposed construction for the recited “single physical channel” found in limitation 11.2 and “an accumulation of TPC commands” found in independent claims 12 and 18. PO Resp. 9–17. Petitioner likewise addresses the scope of an accumulation of TPC commands, but Petitioner does not contest directly Patent Owner’s proposed construction for “single physical channel.” Pet. Reply 2–7. We determine, however, that no express construction of any claim term is necessary to resolve the dispute between the parties. Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 8
Patent outcomesUS 9,706,500 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,706,500 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - Jumio Corporation v. Facetec, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,874,910 - Jumio Corp. v. Facetec, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 11,693,938 - Jumio Corporation v. Facetec, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,157,606
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.