• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Oct 5, 2026 · IPR2025-00438 · APJ Lilan Ren · IPR · Final written decision

  Claims 1–5, 7–13, and 16–20 are unpatentable; the Board found the challenged claims unpatentable on the grounds set out in its conclusions and summary table.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner’s definition of the level of ordinary skill in the art, and Petitioner’s definition appears consistent with the disclosures of the ’466 patent and the prior art of record. Accordingly, we adopt Petitioner’s definition. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). C. Claim Construction” slip op. at 12

  • BurdenUnpatentable

    “Decision under 35 U.S.C. § 318(a) as to the patentability of the challenged claims of the ’466 patent. For the reasons discussed below, we determine Petitioner has established by a preponderance of the evidence that claims 1– 5, 7–13, and 16–20 of the ’466 patent are unpatentable.” slip op. at 2

  Patent outcomesUS 10,569,466 unpatentable
  Nonecites Phillips · KSR · Graham
  Patents in suitUS 10,569,466
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Sep 29, 2026 · IPR2025-00532 · APJ Hyun J Jung · IPR · Final written decision

  Claims 1–16 are unpatentable under § 103 over Warren, Warren and Dunn, Calderon and RepRap20208, and Calderon, RepRap20208, and Dunn.

  RulingsFinal written decision

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “of ordinary skill in the art would have made the proposed combination in the manner asserted with a reasonable expectation of success. Weighing our underlying factual determinations, a preponderance of the evidence persuades us that claim 7 of the ’381 patent is unpatentable over Calderon, RepRap20208, and Dunn. Arctic Cat, 876 F.3d at 1361.” slip op. at 108

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

    “involves a case-by-case inquiry into the facts and circumstances surrounding the reference’s disclosure to members of the public.” In re Klopfenstein, 380 F.3d 1345, 1350 (Fed. Cir. 2004). Whether a document qualifies as a printed publication is a legal conclusion based on underlying factual determinations. Medtronic, Inc. v. Barry, 891 F.3d 1368, 1380 (Fed. Cir. 2018). slip op. at 69

  Patent outcomesUS 10,556,381 unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,556,381
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Sep 28, 2026 · IPR2025-00611 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–10, 12, 13, 19, and 20 are unpatentable under § 103 over the stated Douglas–Mark and Hamilton-based grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The parties agree that experience could substitute for a degree, and vice versa. Pet. 3; PO Resp. 10. The parties’ proposed levels of ordinary skill are substantially similar. For this decision, as in the Institution Decision, we adopt Petitioner’s proposed level, which is supported by credible testimonial evidence and is consistent with the problems addressed in the ’774 patent. See Ex. 1001, 1:16–52. Our decision would be the same, however, if we were to adopt Patent Owner’s proposal.” slip op. at 7

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

    “Neither Petitioner nor Patent Owner argues that we need to construe any claim terms explicitly. See Pet. 2–3; PO Resp. 10. However, the parties contest two material claim-construction issues which we address below. To the extent that the parties’ positions depend on interpreting other claim language in a particular way, we discuss the relevant claim language below in the context of the parties’ arguments regarding the prior art.” slip op. at 8

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

    “We disagree with Patent Owner that a person of ordinary skill in the art would have understood that limitation 1.2 must be performed before limitations 1.3 or 1.4. See Ex. 1001, 35:21–24. See Interactive Gift Exp., Inc. v. Compuserve Inc., 256 F.3d 1323, 1342 (Fed. Cir. 2001) (“Unless the steps of a method actually recite an order, the steps are not ordinarily construed to require one.” (citing Loral Fairchild Corp. v. Sony Corp., 181 F.3d 1313, 1322 (Fed. Cir. 1999)). The evidence suggests that a “target printer” is any printer that is ultimately selected for fabricating the object, and such a printer could send its configuration information either before or after that determination is made in limitation 1.2. This interpretation does not render the word “target” meaningless. At some point, a printer must be determined to be the target printer, which is the one intended to ultimately fabricate the three-dimensional object. But the target printer still exists, and is capable of being queried, before that determination is made. We find the examples in the ’774 patent pertinent to this question. The ’774 patent states that “the target printer may include more than one printer.” Ex. 1001, 18:66–67. In discussing the step of “query target printer for properties 306” (Fig. 3A), the ’774 patent states that “[i]n one aspect, numerous queries are sent to numerous printers, e.g., for use in selecting one or more of the printers as the target printer.” Id. at 19:8–10. Alternatively, “the query is sent to a printer that is not necessarily the target printer as described herein, e.g., when the query or information received from a response to the query is used for the selection of the target printer.” Id. at 19:11–14. Importantly, the second embodiment states that the queried printer “is not necessarily the target printer,” suggesting that the queried printer could be the target printer even before it is determined to be such. Id. at 19:11–12 (emphasis added). Based on the evidence of record, a person of ordinary skill in the art would have understood that the “target printer” can be determined after the query recited in limitation 1.3 or the reception of configuration information recited in limitation 1.4. Thus, the evidence does not impose an ordering between limitations 1.2 and 1.3 or between limitations 1.2 and 1.4. The evidence also does not support Patent Owner’s argument that the two reverse-order examples in the ’774 patent are unclaimed embodiments.” slip op. at 10

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

    “We disagree that Petitioner’s arguments are based on impermissible hindsight, because they are based on the disclosures in Douglas and Mark, and Petitioner has articulated a persuasive reason to combine those references without referring to the ’774 patent itself, as we discuss below. See In re McLaughlin, 443 F.2d 1392, 1395 (CCPA 1971) (an obvious rationale is not improper hindsight if it “takes into account only knowledge which was within the level of ordinary skill at the time the claimed invention was made and does not include knowledge gleaned only from applicant’s disclosure”).” slip op. at 29

  Patent outcomesUS 11,886,774 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,886,774
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.Some claims unpatentable
  PTAB · Sep 28, 2026 · IPR2025-00531 · APJ Hyun J Jung · IPR · Final written decision

  Claims 1–11 and 13–15 are unpatentable over the stated obviousness grounds; claim 12 was not shown unpatentable.

  RulingsFinal written decision

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

    “Petitioner filed a Petition (Paper 2, “Pet.”) requesting institution of an inter partes review of claims 1–15 of the ’698 patent. Discretionary denial of institution was determined to be not appropriate in this proceeding, and the proceeding was referred to the Board. Paper 10. Pursuant to 35 U.S.C. § 314, we instituted an inter partes review of claims 1–15 of the ’698 patent on all presented challenges. Paper 11 (“Inst. Dec.”), 15.” slip op. at 2

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed

    “Decision is issued pursuant to 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73 (2025). For the reasons that follow, we determine that Shenzhen Tuozhu Technology Co., Ltd. (“Petitioner”) has shown by a preponderance of the evidence that claims 1–11 and 13–15, but not claim 12, of U.S. Patent No. 9,168,698 B2 (Ex. 1001, “the ’698 patent”) are unpatentable.” slip op. at 2

  Patent outcomesUS 9,168,698 mixed
  § 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,168,698
• Apple Inc. v. Ferid AllaniAll claims unpatentable
  PTAB · Aug 25, 2026 · IPR2025-00857 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–27 are unpatentable: claims 24 and 26 over Rossmann and Himmel; claims 1–2, 4–6, 10–23, 25, and 27 over Rossmann, Himmel, King, and Adar; claims 3 and 7–9 over those references and Boyle.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “we consider the type of problems encountered in the art, the prior art solutions to those problems, the rapidity with which innovations are made, the sophistication of the technology, and the educational level of active workers in the field. See Custom Accessories, Inc. v. Jeffrey-Allan Industries, Inc., 807 F.2d 955, 962 (Fed. Cir. 1986); see Orthopedic Equip. Co. v. United States, 702 F.2d 1005, 1011 (Fed. Cir. 1983).” slip op. at 6

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “meaning of “icon” as claimed, including the dependent claims, the specification, the prosecution history, and the extrinsic evidence including expert testimony and dictionary definitions, we determine that the plain meaning of “icon” is readily apparent from the claims themselves. See Phillips, 415 F.3d at 1314 (“In some cases, the ordinary meaning of claim language as understood by a person of ordinary skill in the art may be readily apparent even to lay judges.”). We find that the plain meaning of “icon” as claimed encompasses at least “textual elements” because claim 20 recites “the icons comprise textual elements.” See id. (“Other claims of the patent in question, both asserted and unasserted, can also be valuable sources of enlightenment as to the meaning of a claim term.”). We highlight that the additional intrinsic evidence cited by the parties is consistent with the plain meaning. For example, Figures 1 and 2 of the specification show icons comprising textual elements. As another example, during prosecution of the ’058 patent, the Examiner found that the claimed icons were taught by textual hyperlinks. Ex. 1002, 586, 592. In order to overcome the Examiner’s rejection and obtain an allowance (id. at 641–50), applicant subsequently amended the claims to recite “specifically designed,” thus implicitly conceding to the Examiner’s interpretation of icon as encompassing textual hyperlinks. Id. at 625–640; see PO Resp. 43–44 (citing Ex. 1002, 626–27, 645–46) (acknowledging that the Examiner allowed the claims because applicant amended the claims to recite “specifically designed for containing a set of icons.”).” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed petitioner constructionDecided for petitioner

    “Requiring an element to be "specifically designed" for another element narrows the claim because it requires more than the first element being merely capable of being used with the second element. The term "configured to" is generally construed narrowly to mean "made to" and "designed to" rather than broadly to require merely "capable of". See In re Giannelli, 739 F. 3d 1375, 1379-80 (Fed. Cir. 2014) (the phrase "configured to" requires more than "mere capability." Rather, that term is synonymous with "made to" and "designed to."). However, rather than use "configured to", in order to avoid any confusion as to the narrower scope of the claims as amended, Applicant herein directly and explicitly requires "designed to." In re Giannelli at 1379-80 (Fed. Cir. 2014) (reversing an obviousness rejection because (1) the claims were properly construed narrowly to mean "designed to" and not broadly to encompass merely "capable of", and (2) the USPTO had not explained the motivation for modifying the prior art to meet the "design to" requirement) See also MPEP 2111.04, citing to In re Giannelli, for the proposition that a claim can be narrowed to require that it be "designed and constructed to be used" in a specific manner (as a rowing machine in the case of In re Giannelli). Logan has not been specifically designed and constructed in the required manner, so it does not cure all deficiencies of the primary reference Iki (which lacks any tree menu structure). Logan describes only "remote web" pages 90, 95 that are merely pages retrieved from Web browsing and stored in a web computer 25. Iki as modified by Logan would result on in a tree menu structure wherein not all levels of the tree included the required selection pages specifically designed for containing the claimed set of icons. Ex. 1002, 626–27 (emphasis omitted).” slip op. at 14

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

    “Petitioner contends that a person of ordinary skill in the art would have modified Rossmann to include several advantages expressly taught by Himmel: Himmel’s consumer hot list bookmark set for the benefits of providing a user with a consistent user interface when accessing a website; to simplify navigation for the user by providing an additional navigation aid; to provide more immediate access to commonly used web actions; to reduce the network traffic required to navigate through webpages to arrive at a particular web function; and to reduce usage charges and data usage. Pet. 22–23 (citing Ex. 1003 ¶¶ 94–99; Ex. 1004, 2:38–56, 12:24–34, 14:35–44; Ex. 1005, 18:63–65, 20:11–16). Petitioner contends that modifying Rossmann’s Figures 4A through 4G to include Himmel’s consumer hot list bookmark set yields each selection page including both selection icons for navigating to other local pages along with direct access icons such as on sale today to directly navigate to a predetermined web site to perform a common web action. Id. at 23–25 (citing Ex. 1003 ¶¶ 96–100; Ex. 1004, Figs. 4D–F). Petitioner contends that the selection page of Rossmann as modified by the bookmark set of Himmel teaches a first locally stored page specifically designed to include a direct access icon because the selection page is “used to include” a direct access icon, such as on sale today, and that during use, this selection page is programmed to display the set of direct access icons for selection by the user. Pet. 25 (citing Ex. 1003 ¶¶ 96–100); see id. at 21–24. Petitioner contends that a person of ordinary skill in the art would have had a reasonable expectation of success because technology for bookmarking websites and web actions was known at the time of invention, modifying Rossmann to utilize known bookmark manager software would have been straight forward, Rossmann already includes hardware and programming instructions to access a web server, and Himmel teaches that known prior art methods utilized both selection and direct access icons on a single page. Id. at 25–26 (citing Ex. 1003 ¶¶ 101–103; Ex. 1004, 2:38–41, 14:21–44; Ex. 1005, Fig. 6A, 21:27–34).” slip op. at 19

  Patent outcomesUS 10,943,058 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 10,943,058
• Apple Inc. v. Memoryweb, LLCAll claims unpatentable
  PTAB · Jul 8, 2026 · PGR2022-00006 · APJ Jason M Repko · PGR · Remand

  On remand, the Board held claims 1–59 unpatentable: claims 1–6, 8–37, 40–44, and 49–59 over A3UM under §103, and claims 6, 7, 38, and 39 for lack of written description under §112.

  RulingsRemand decision

  • RemandOther

    “On remand, the Board is to determine “[w]hether the alleged inconsistency in [Petitioner’s] treatment of map images compared to other first/second versions of claim elements supports rejecting [Petitioner’s] theory on claim-construction or other merits grounds is a matter for the Board to consider in the first instance on remand, constrained by any relevantly similar now-final findings of fact and conclusions of law in the ’020 PGR and related proceedings” (CAFC Dec. 16). Thus, the two issues on remand are (1) the construction of the second map image and (2) whether A3UM teaches or suggests the claimed “second map image” under that construction.” slip op. at 10

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A person of ordinary skill in the art in 2011 would have had (1) at least a bachelor’s degree in computer science, computer engineering, or electrical engineering, and (2) at least one year of experience designing graphical user interfaces for applications such as photo management systems. Pet. 12 (citing Ex. 1003 ¶¶ 44–46). In the Institution Decision and Final Written Decision, we applied Petitioner’s proposed definition. Inst. Dec. 12; FWD 30–31. Patent Owner does not dispute Petitioner’s proposed level of ordinary skill in the art. PO Resp. 7. We continue to find that the skill level identified by Petitioner (Pet. 12) is consistent with the record. Thus, we use the same definition here that we used in the Institution Decision and Final Written Decision.” slip op. at 6

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

    “c. Analysis We agree with Petitioner that the “second map image” should be construed as the map image in the second person view. Reply 5. Under Petitioner’s proposed construction, the terms “first” and “second” identify which person view that the map image is within. Id. The map image’s connection to the person view is important to how the user interacts with the interface because selecting the map image in one view does something different than selecting the map image in another, as recited in claims 14 and 46.” slip op. at 12

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “Here, we disagree with Patent Owner’s argument because it is based on the premise that the second map image is different from the first in a way that is not reflected in the claims. See Section II.C.3 supra. Even if “the claims consistently use the terms ‘first’ and ‘second’ to refer to separate and distinct elements,” A3UM’s first and second map images are separate and distinct elements for at least the reason they are included in separate and distinct views in the interface. See Pet. 63; Reply 5. As discussed in Section II.C.3, the second map image is the map image in the second person view. Here, Petitioner sufficiently shows that A3UM provides the same functionality for each person, including displaying the person in the Faces view with their name within A3UM’s overall user interface. See Pet. 62 (citing Ex. 1003, ¶215; Ex. 1005, 418–420). Patent Owner does not dispute this. See PO Resp.; Sur-reply. For the same reasons why A3UM teaches the “first map image” with respect to a first person view recited in claims 1 and 31, Petitioner has shown that A3UM also teaches the “second map image” in the second person view. See FWD 53–56. In sum, Patent Owner’s arguments are unpersuasive because they are based on an incorrect claim construction, and Petitioner has shown that claims 13 and 45 are unpatentable. 5. Claims 14–16 and 46–48 Apart from the arguments analyzed above, Patent Owner does not present separate arguments directed to the subject matter of claims 14–16 burden to show that the challenged claims are unpatentable. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). We have reviewed Petitioner’s arguments and evidence submitted in connection with the remaining limitations and find them persuasive as they are consistent with and supported by the evidence of record. See Pet. 63–64. Thus, Petitioner has shown that claims 14–16 and 46–48 are unpatentable over A3UM.” slip op. at 14

  Patent outcomesUS 11,017,020 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosure
  Patents in suitUS 11,017,020
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms … that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). D.” slip op. at 12

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

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

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

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

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

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

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

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

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

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

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

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

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

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

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

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

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Qiagen Sciences, LLC v. Tecan Genomics, Inc.All claims unpatentable
  PTAB · May 13, 2026 · IPR2025-00028 · APJ Zhenyu Yang · IPR · Final written decision

  Claims 1–15 and 17–22 are unpatentable as obvious over the specified combinations of Shapero, Delseny, and, for certain claims, Hamady or Jones.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for patent owner

    “In the DI, we addressed Patent Owner’s arguments disputing Petitioner’s proposed definition. DI 17–18 (citing Prelim. Resp. 11–12). We stated that for purposes of this Decision, we find a POSA would have had a Ph.D. in molecular biology, molecular genetics, bioinformatics, biochemistry, or a related field. Alternatively, a POSA would have had a B.S. or M.S. degree with three to five years of experience working in any of those fields. Additionally, the POSA would have had experience with NGS sequencing methods and a working knowledge of how those methods functioned. Id. at 18. After institution, Patent Owner states that, for purposes of this proceeding, it adopts the Board’s definition of a POSA. PO Resp. 12. Based on the entirety of the trial record, we maintain our finding of a POSA’s skill level.” slip op. at 9

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

    “Claim Construction In an inter partes review, we construe a claim term “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) (2020). Under that standard, the words of a claim “are generally given their ordinary and customary meaning,” which is “the meaning that the term would have to a person of ordinary skill in the art in question at the time of the invention, i.e., as of the effective filing date of the patent application.” Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Claim terms need only be construed to the extent necessary to resolve the controversy. Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011). On this record and for purposes of this Decision, we see no need to construe any claim term expressly.” slip op. at 9

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner

    “A reference teaches away “when a person of ordinary 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 Fulton, 391 F.3d 1195, 1201 (Fed. Cir. 2004). “The prior art’s mere disclosure of more than one alternative does not constitute a teaching away from any of these alternatives because such disclosure does not criticize, discredit, or otherwise discourage the solution claimed.” Id.” slip op. at 29

  Patent outcomesUS 10,036,012 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,036,012

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.