- Microsoft Corporation v. Sterling Computers CorporationAll claims unpatentablePTAB · Sep 14, 2026 · IPR2025-00270 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–13, 15, 18, 20, 21, and 27 are unpatentable as obvious over Rohall and Schiavone, with Gomes added for claims 9 and 27.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Our Institution Decision adopted Petitioner’s definition of a person of ordinary skill in the art. Inst. Dec. 9–10. In its Response, Patent Owner adopts Petitioner’s proposed level of ordinary skill. See PO Resp. 16 (“Patent Owner and its expert adopt the Board’s definition for purposes of this Response.”). Having considered the record, we continue to adopt Petitioner’s proposed level of skill, as articulated above. We are satisfied that Petitioner’s proposal comports with the level of skill necessary to understand and implement the teachings of the ’911 Patent. Accord Inst. Dec. 9–10.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We agree with Petitioner and determine that the construction of “relational references” does not require the use of a relational model and, further, includes pointers that point to related messages exchanged among users. The intrinsic evidence leads us to this construction. First, the relevant language of claim 1 recites “a message container containing relational references pointing to a plurality of sent submessages stored externally to the message container in the message database.” Ex. 1001, 15:56–59. A relational model is not recited in that language or anywhere else in the claim. See id. at 15:51–16:14. Therefore, the claim does not expressly require a relational model. Furthermore, the claim language supports Petitioner’s interpretation that “relational references” include pointers that point to related messages because the claim states that the “relational references” perform the task of “pointing to a plurality of sent submessages.” Pet. Reply 7. Accordingly, the language of the claim supports a construction that does not require a relational model and at least suggests relational references include pointers.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“No other claim terms need construction for our decision here and we decline unnecessarily doing so. 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 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentableDecided for petitioner
“We agree with Petitioner that the ordinarily skilled artisan would have been motivated to combine Rohall and Schiavone because Schiavone provides reasons to apply its techniques to email systems such as Rohall’s. Schiavone describes a need for “ensuring compliance of e-mail messages with applicable standards and/or laws and/or otherwise determining appropriateness of a message for an intended recipient,” especially because there is “a patchwork of local, federal and international laws.” Ex. 1006 ¶ 6. Schiavone also states that filtering emails, e.g., to remove spam, is beneficial. Id. ¶¶ 1–2. As Schiavone describes problems in email systems, which its rules-based email processing technique addresses, we determine that the ordinarily skilled artisan would have been motivated to combine Rohall and Schiavone. See KSR, 550 U.S. at 401 (a reference which teaches, suggests, or motivates its combination may “identify a reason that would have prompted a person of ordinary skill in the art to combine the elements”).” slip op. at 19
Patent outcomesUS 8,073,911 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 8,073,911 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 1, 2026 · IPR2025-00914 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–19 are unpatentable as obvious over Menon, Trefethen, RS6000, and POEref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’679 patent, the prior art of record, and the testimony of both experts.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Petition relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard. Pet. 12–13 (citing 37 C.F.R. § 42.100(b)). The Petition also addresses the construction of “peer-to-peer architecture” recited in independent claim 1 of the ’679 patent, a limitation we need not construe to resolve the parties’ dispute in this proceeding. Id. at 13; see, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Owner relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard without further analysis. Resp. 7.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“RS6000 with Menon, namely because RS6000 provides an overview of the IBM SP2 multiprocessor and Menon teaches the use of “IBM SP2, a modern high performance distributed memory multiprocessor” used in the MultiMATLAB system. Id. at 24–25 (citing Ex. 1003 ¶¶ 142–145; Ex. 1005, 5–6, 14; Ex. 1007, 1, 11). The Petition also explains why POEref pertains to the field of cluster computing in a parallel operating environment. Id. at 26 (citing Ex.1008, 11 (“PE Software is designed to run on an … RS/6000 network cluster”)); (further citing Ex. 1001, 1:14–15; Ex. 1003 ¶¶ 146–149). The Petition contends that a POSITA would have been motivated to combine the teachings of POEref with Menon “because Menon suggests the combination by teaching that MultiMATLAB uses ‘POE, IBM's Parallel Operating Environment.’” Id. at 26–27 (citing Ex. 1005, 6); (further citing Ex. 1003 ¶¶ 150–153; Ex. 1005, 14; Ex. 1008, 11, 46). We agree with Petitioner’s analysis. We find the Petition’s argument and evidence of a motivation to combine the asserted prior art references in the manner claimed to be compelling, persuasive, consistent with the disclosures in the references, which include internal cross-references to each other, and supported by the expert testimony of Dr. Bajaj.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner
“skill, upon reading the reference, would be discouraged from following the path set out in the reference, or would be led in a direction divergent from the path that was taken by the applicant.” In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). Patent Owner argues that Menon teaches away from a combination with Trefethen because “Menon expressly states that Trefethen’s first-generation architecture is inadequate for the objectives that motivated the newer design.” Resp. 35–37. The evidence does not support Patent Owner’s position. First, Patent Owner’s teaching away argument is inconsistent with the strong evidence of a motivation to combine Menon and Trefethen discussed above. Second, Patent Owner’s teaching away argument is contrary to the evidence of record for the reasons given in Petitioner’s Reply. Reply 13–15 (e.g., “Menon explicitly cites Trefethen and explains that Menon builds on the teachings of Trefethen.”) (citing Pet. 22; Ex. 1003 ¶ 70; Ex. 1005, 1–3; Ex. 1163 ¶¶ 47–53). We are further persuaded by Dr. Bajaj’s reply testimony: the “MultiMATLAB teachings in Trefethen. In fact, Menon describes enhancing the system of Trefethen. For example, Menon describes a list of “goals” already achieved by MultiMATLAB and then states that the architecture has been “redesigned to achieve two further goals.” One of these two “further goals” is “extensibility,” which Menon achieves by its description of adding “MEX routines” to the system of Trefethen. Far from showing an “incompatibility” between Menon and Trefethen as the POR argues, Menon’s addition of the “MEX routines” to MultiMATLAB shows that such a modification was within the capabilities of a POSITA, because the authors of the Menon paper actually implemented the modification. Ex. 1163 ¶ 49 (citing Ex. 1005, 1–3). Dr. Bajaj’s testimony is unrebutted, credible, and supported by the record. We agree with Dr. Bajaj’s reasoning, which is based on direct quotes in Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶¶ 50–52. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine the teachings of Menon and Trefethen. RS6000 and POEref are specifically referenced in Menon-Trefethen and add operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Such facts are inconsistent with Patent Owner’s teaching away and lack of motivation arguments.” slip op. at 24
Patent outcomesUS 12,021,679 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 12,021,679 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Aug 26, 2026 · IPR2025-00913 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–25, 27–28, and 30 as obvious over Menon, Trefethen, RS6000, and POEref; claims 26 and 29 over those references plus MPIref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and experience of a POSITA. We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’034 patent, the prior art of record, and the testimony of both experts.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther
“processor,” “multi-core” processor, or “singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’” as Patent Owner contends. Resp. 11–12, 21; see also Ex. 1163 ¶ 22 (“The claim does not recite ‘single chip,’ ‘single package,’ ‘single die,’ or ‘single multi-core microprocessor.’”). Nor do the claims recite a plurality of processing cores “within” a single-chip package or read as “multi-core within a processor” as argued by Patent Owner. Resp. 12–14; Sur-Reply 2; see Reply 6 (citing Ex. 1163 ¶ 23 (“Thus, the phrase ‘with a plurality of processing cores’ identifies the required processing resources associated with the hardware processor; it does not import a packaging limitation.”)). The claims do recite a hardware processor “with” a plurality of processing cores; a critical distinction even Patent Owner reads as open-ended, i.e., as a hardware processor that “comprises” a plurality of processing cores. See Resp. 11 (“the claims require a singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’”). Consequently, the claim language does not support Patent Owner’s proposed construction of “a . . . hardware processor with a plurality of processing cores” as a single multi-core processor. cores it contains” in reliance on a parsed description in the ’034 patent specification: The specification explains: “Each processor can contain one or more processor cores that are capable of single-threaded execution. Processor cores are generally independent microprocessors, but more than one can be included in a single-chip package.” Id. at 1212 (partially quoting Ex. 1001, 5:11–16); Sur-Reply 2. The quoted description does not support Patent Owner’s contention that the claimed “a . . . hardware processor with a plurality of processing cores” must be limited to a “single multi-core processor” that “locates multiple cores within a ‘single-chip package,’” i.e. limited to a single multi-core microprocessor such as “a Core 2 Duo is one processor package with two cores.” Resp. 12– 13, 21 (citing Ex. 1001, 7:15–25). The description quoted above from column 5, moreover, describes a “processor” that “can contain one or more processor cores” each of which can be an independent microprocessor. Reply 2–3 (citing Ex. 1001, 5:11–16; Ex. 1163 ¶¶ 10–14). As Petitioner emphasizes, the specification distinguishes a “processor” from a “microprocessor” and describes a “processor” that “can be one or more general purpose single-core or multi-core microprocessors,” rather than limiting a “processor” to a single multi-core microprocessor. Reply 3–5 (citing Ex. 1001, 7:14–36, Fig. 1; Ex. 1163 ¶¶ 15–18).” slip op. at 13
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“art because they pertain to the same “field of cluster computing” as the ’034 patent and “are reasonably pertinent to the problem of the ’034 patent, namely, executing a single program on multiple nodes.” Pet. 22 (citing Ex. 1001, 1:14–15; Ex. 1003, ¶¶ 65–69; Ex. 1005, 2; Ex. 1006, Abstract). The Petition emphasizes that Menon expressly cites and builds on the MultiMATLAB system taught by Trefethen. Id. (citing Ex. 1003 ¶ 71; Ex. 1005, 1–2). The Petition contends that: combination of prior art elements according to known methods (executing MATLAB code on a multiprocessor system) to yield the predictable result discussed in both papers: the MultiMATLAB system executing MATLAB in parallel to perform mathematical calculations. Id. at 22–23 (citing Ex. 1003 ¶ 70; Ex. 1005, Abstract; Ex. 1006, 2–7). The Petition further contends that a POSITA would have found it predictable to combine Trefethen with Menon with a reasonable expectation of success “because researchers had a strong desire to parallelize MATLAB.” Id. at 23–24 (citing Ex. 1003 ¶ 73; Ex. 1005, 2; Ex. 1006, 11–12.)” slip op. at 27
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“A POSITA would have had an especially strong reason to read these references together because they address the same project, the same MATLAB-based parallel-computing problem, and the same MultiMATLAB command environment. Menon expressly identifies Trefethen’s MultiMATLAB work and then describes a redesigned architecture that preserves the same user-level objective––parallel MATLAB computations—while improving implementation details and extensibility. A POSITA therefore would not view the references as mutually exclusive alternatives. Rather, a POSITA would understand Trefethen as teaching specific MultiMATLAB commands and examples, including Eval, Send, Recv, and the architecture was implemented and improved in a later version. Ex. 1163 ¶¶ 71–72 (emphases added). We find the above reasoning persuasive and adopt it as our own. Petitioner and Dr. Bajaj demonstrate a sound technical motivation for a POSITA—someone having a bachelor’s degree in computer science, computer engineering, or electrical engineering and two years of experience working in the field of cluster computing or parallel processing—to combine Menon and Trefethen: to improve MATLAB’s operational performance and extensibility in a parallel operating environment. Menon builds on Trefethen to improve and extend the parallel processing capabilities of MultiMATLAB: “This system will enable users to access high-performance parallel routines from within the MATLAB environment, to extend the environment with new parallel routines, and to use these routines to develop parallel applications with the MATLAB language.” Ex. 1005 Abstract. Menon is intended to be read in conjunction with Trefethen, as would be expected from two references generated by the same research group at the same university addressed to the same technical subject matter about a year apart. Ex. 1005, 1; Ex. 1006, Ex. 1086 ¶¶ 65, 101, 102. The very first citation in Menon is to Trefethen. Ex. 1005, 2, 16.” slip op. at 30
Patent outcomesUS 11,570,034 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,570,034 - 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 - Jumio Corp. v. Facetec, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,776,471 - X Corp. v. Sterling Computers CorporationAll claims unpatentablePTAB · Jun 9, 2026 · IPR2025-00299 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–22 are unpatentable as obvious over the stated Dumais-based and Kircher/Krug grounds; Patent Owner’s and Petitioner’s motions to exclude are dismissed as moot.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Our Institution Decision adopted Petitioner’s definition of a person of ordinary skill in the art. Inst. Dec. 8–9. In its response, Patent Owner adopts Petitioner’s proposed level of ordinary skill. See PO Resp. 14–15 (“Patent Owner and its expert adopt the Board’s definition for purposes of this Response”). Having considered the record, we continue to adopt Petitioner’s proposed level of skill, as articulated above. We are satisfied that Petitioner’s proposal comports with the level of skill necessary to understand and implement the teachings of the ’217 Patent. Accord Inst. Dec. 8–9.” slip op. at 9
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)No construction neededNot reached
“1. “computer program modules” The parties dispute whether four “computer program modules comprising” (1) “a monitoring module,” (2) “a first relevance measurement module,” (3) “a second relevance measurement module,” and (4) “a relevance analysis module” (collectively, “module limitations”) invoke 35 U.S.C. § 112 ¶ 6 and should be treated as means-plus-function limitations. See Pet. 8–18; PO Resp. 15–18; Pet. Reply 3–5; PO Sur-reply 4–7. However, the parties do not argue that the construction of these terms affects the analysis of Petitioner’s challenges. See PO Resp.; Pet. Reply; PO Sur-reply. Moreover, our analysis does not rely on any particular construction of these terms and, so, we need not resolve this dispute.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“2. “one or more measures derived from the group consistent of” Petitioner asserts limitations 1[g] and 1[g][i]–1[g][iv] recite an open Markush group listing alternatively useable members. Pet. 20–21 (citing Gillette Co. v. Energizer Holdings, Inc., 405 F.3d 1367, 1372 (Fed. Cir. 2005); Abbot Lab’ys v. Baxter Pharm. Prod., Inc., 334 F.3d 1274, 1281 (Fed. Cir. 2003) (explaining that the listing of specified alternatives within a claim is referred to as a Markush group or Markush grouping)); See Ex. 1001, 47:47–58. Patent Owner does not dispute Petitioner’s construction. See PO Resp; PO Sur-reply. As these terms are not in controversy, we need not opine on this construction.” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITANo construction neededNot reached
“Petitioner’s and Patent Owner’s respective constructions overlap in their requirement that “cognate” users share similar past user actions and assessments or are defined by similar direct input by the user. See Pet. 18; PO Resp. 20–21; PO Sur-reply 10. Petitioner argues that Patent Owner’s construction “exclude[s] ‘groups’ from the claims” and further limits the scope of to users who share actions (Pet. Reply 8–9), but Patent Owner states that its proposed construction does not so limit the claims (PO Sur-reply 10). As such, there is no disagreement that “cognate” users share similar past user actions and assessments or are defined by similar direct input by the user. As there is no controversy, we need not, and do not, construe the meaning of “cognate.” However, Patent Owner’s requirement that “at least one other of the plurality of users” is specifically cognate to “the user” who was sent the content is plainly recited in the claim language itself. The claim recites a “relevance score of a piece of electronic content sent from a sender to a user” in the preamble and similarly again in limitation 1[g]. See Ex. 1001, 47:25–28 (emphasis added), 45:62–64. The limitation in question directly references the claimed “user” when reciting the cognate relationship: “identify at least one other of the plurality of users . . . that is cognate to the user.” Ex. 1001, 47:43–45 (emphasis added). As such, the claim language plainly supports Patent Owner’s requirement and Petitioner does not contest that requirement. See Pet. Reply 8. least one other of the plurality of users . . . that is cognate to the user” as requiring that the identified other user is cognate specifically to the user whose relevance score is being determined.” slip op. at 12
Patent outcomesUS 7,716,217 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 7,716,217 - Google LLC v. Mindbasehq, LLCAll claims unpatentablePTAB · Mar 16, 2026 · IPR2021-01252 · APJ Kara L Szpondowski · IPR · Remand
On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious; the Federal Circuit’s affirmed findings leave claims 1–13, 20–32, 41, and 42 unpatentable as well.
RulingsRemand decision- RemandOther
“to both cases vacating and remanding in part and affirming in part our Final Written Decisions. Appeal Dec. With respect to Petitioner’s appeals, the Federal Circuit addressed the “dictionary routine” claims (claims 14–19 and 33–40) and the “normalization” claims (claims 43–46). Appeal Dec. 7–14. For the “dictionary routine” claims, the Federal Circuit vacated and remanded, stating that In sum, as Google contends and we now hold, the “dictionary routine” claims can be practiced by use of an already-created dictionary, and do not also require the automatic creation of a dictionary. The Board needs to consider Google’s evidence and argument by applying this construction of the automatically classifying and storing limitation, and using this understanding to determine whether Conlon may, in fact, render the “dictionary routine” claims obvious (and, relatedly, whether its prior distinctions of Conlon may be immaterial). Appeal Dec. 10–11. For the “normalization” claims, the Federal Circuit also vacated and remanded, stating that our “decision to exclude Google’s rebuttal argument and supplemental declaration is based on a clear factual error,” so on remand we “must include evaluation of the evidence and argument Google provided in reply.” Id. at 13–14. With respect to Patent Owner’s cross-appeals, the Federal Circuit affirmed. Id. at 14–16.” slip op. at 3
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“The Federal Circuit concluded that Petitioner’s construction of “automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“We agree with Petitioner that claim 43 is obvious over the combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations. After considering the properly presented evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that the combination of Conlon, Miller, and Fong teaches the limitations in claim 43, that one of ordinary skill in the art would have been motivated to combine the teachings of Conlon, Miller, and Fong, and that claim 44 would have been obvious over Conlon, Miller, and Fong. 2. Analysis of Dependent Claims 44–46 Claims 44–46 depend, directly or indirectly, from claim 41. We, likewise, determine whether the combination renders obvious claims 44–46, taking into account the arguments made in Petitioner’s Reply Briefs and Dr. Jansen’s Supplemental Rebuttal Declarations. Petitioner contends that dependent claims 44–46, would have been obvious over Conlon, Miller, and Fong, and provides explanation as to how the prior art teaches each claim limitation. Pet. 84–86; Reply 35–39; Pet. Remand Br. 13–14. Patent Owner does not provide further briefing on dependent claims 44–46. 14 Available at https://www.uspto.gov/patents/ptab/trial-practice-guide#step2. Patent Owner did not specifically challenge Petitioner’s contentions as” slip op. at 31
- Strike new argumentNew argument disregardedDecided for petitioner
“Patent Owner’s arguments do not undermine Petitioner’s showing. Patent Owner did not specifically challenge Petitioner’s contentions as to the sufficiency of Conlon’s disclosure for claim 1410 in the Patent Owner Response. In the Sur-replies, Patent Owner argues that the claim requires that at least some relationships are created “automatically,” and “these automatic embodiments . . . are represented in this group of claims.” Sur-reply 9. Along these lines, in the additional briefing Patent Owner argues that Conlon does not teach “automatic,” but merely teaches “semi-automatic.” PO Remand Br. 9–10. The crux of Patent Owner’s argument, however, is that the Federal Circuit did not properly construe the limitation, and ignored certain disclosures in the ’433 (and ’680) patent. Id. at 10–11; see Pet. Remand Resp. Br. 1–4; PO Remand Resp. Br. 4–5. The Federal Circuit held that “the dictionary routine claims can be satisfied by mere use of a lexical database, and do not also require the automatic creation of additional definitions.” Appeal Dec. 10. Moreover, the statements from Conlon that Patent Owner relies upon relate to creating a database, not using the database. See id. As discussed above, on remand we are directed to apply the Federal Circuit’s construction. Patent Owner does not explain 10 As discussed in the original Final Written Decisions, Patent Owner raised several arguments that generally applied to all the claims, challenging, for example, the level of ordinary skill in the art, whether Conlon, Miller, and Beckwith were analogous art, and several general arguments relating to Conlon and the motivation to combine Conlon with a DBMS. See Final Dec. 14–23, 25–27. We were not persuaded by Patent Owner’s arguments; the Federal Circuit affirmed, determining that our findings were supported by substantial evidence. Appeal Dec. 14–16. why Petitioner’s contentions are not persuasive in light of the Federal Circuit’s construction of this limitation. In addition, Patent Owner argues in the Sur-replies that “[c]laims 14– 19 are not disclosed by the proffered prior art” and cites to paragraphs 78–83 of the Ranka Rebuttal Declarations. Sur-reply 10. As discussed in the original Final Written Decisions, Patent Owner’s reliance on six paragraphs of Dr. Ranka’s Rebuttal Declarations is an improper incorporation by reference, as Patent Owner did not discuss that testimony or further elaborate on these arguments in the Sur-replies. 37 C.F.R. § 42.6(a)(3); Cisco Systems, Inc. v. C-Cation Techs., LLC, IPR2014-00454, Paper 12 at 9–10 (PTAB Aug. 29, 2014) (informative); see, e.g., Final Dec. 37–39, 45, 48–50, 52. Therefore, we will not consider arguments that are not made in the Sur-replies, but are instead improperly incorporated by reference to the cited paragraphs in Dr. Ranka’s Rebuttal Declarations. Accordingly, after considering the evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that Conlon teaches limitation [14.3], and that claim 14 would have been obvious over Conlon.” slip op. at 21
Patent outcomesUS 6,665,680 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,665,680 - Google LLC v. Mindbasehq, LLCAll claims unpatentablePTAB · Mar 16, 2026 · IPR2021-01251 · APJ Kara L Szpondowski · IPR · Remand
On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious over Conlon alone or Conlon, Miller, and Fong; the affirmed unpatentability of claims 1–13, 20–32, 41, and 42 remains.
RulingsRemand decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 31
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 32
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“4. Summary of Ground 1 Having considered the Graham factors,11 including the level of ordinary skill in the art, the scope and content of the prior art, and the differences between the prior art and the challenged claims, we are persuaded, based on the current record, that Petitioner has shown, by a preponderance of the evidence, that claims 14–19 and 33–40 would have been obvious over Conlon.” slip op. at 24
Patent outcomesUS 6,510,433 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,510,433
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.