- Guardant Health, Inc. v. University Of WashingtonNo claims unpatentablePTAB · Oct 14, 2026 · IPR2022-00817 · APJ Zhenyu Yang · IPR · Remand
On remand, the Board found Travers ’075 did not enable RCR amplification followed by SMRT sequencing and held claims 1–30 not shown unpatentable under the asserted obviousness grounds.
RulingsRemand decision- RemandOther
“B. Scope on Remand On remand, we are bound by the terms of the Federal Circuit’s mandate. Intell. Pixels Ltd. v. Sony Interactive Ent. LLC, 181 F.4th 1216, 1220 (Fed. Cir. 2026) (“An administrative agency is bound by the mandate of a reviewing court much as a lower court is bound by the mandate of a higher court.”). According to the Federal Circuit, on appeal, Patent Owner “UW argues that ‘Travers ’075 does not enable the sequencing of an RCR concatemer using PacBio’s SMRT sequencing,’ and therefore because paragraph 122 is not enabled, it cannot be relied on for disclosing amplification followed by sequencing.” Paper 50, 14. Because “[t]he Board did not reach this issue,” the Federal Circuit “remand[ed] the case for consideration of this issue by the Board in the first instance.” Id. Thus, consistent with the court’s mandate, we must decide “whether Travers ’075 enabled RCR amplification followed by SMRT sequencing.” Id. at 8.” slip op. at 4
- BurdenNot shown unpatentable
“A prior art reference is presumed to be enabled. Amgen, Inc. v. Hoechst Marion Roussel, Inc., 314 F.3d 1313, 1355 (Fed. Cir. 2003) (holding that “a presumption arises that both the claimed and unclaimed disclosures in a prior art patent are enabled”); In re Antor Media Corp., 689 F.3d 1282, 1288 (Fed. Cir. 2012) (extending the presumption to prior art printed publications). A patent owner, however, may present persuasive evidence that the relevant disclosures of a prior art are not enabled and therefore are not pertinent prior art. Amgen, 314 F.3d at 1355; In re Antor Media, 689 F.3d at 1289 (discussing the applicant’s burden to submit rebuttal evidence of nonenablement during prosecution); Apple Inc. v. Corephotonics, Ltd., 861 Fed. App’x. 443, 450 (Fed. Cir. 2021) (“[R]egardless of the forum, prior art patents and publications enjoy a presumption of enablement, and the patentee/applicant has the burden to prove nonenablement for such prior art.”). “[T]here is no absolute requirement for a relied-upon reference to be self-enabling in the § 103 context, so long as the overall evidence of what was known at the time of invention establishes that a skilled artisan could have made and used the claimed invention.” Raytheon Techs. Corp. v. Gen. Elec. Co., 993 F.3d 1374, 1376–77 (Fed. Cir. 2021). But, “if an obviousness case is based on a non-self-enabled reference, and no other prior art reference or evidence would have enabled a skilled artisan to make the claimed invention, then the invention cannot be said to have been obvious.” Id. at 1377.” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“The Federal Circuit stated that “the elements of the challenged claim are expressly taught by Travers ’075. Travers ’075 discloses performing RCR amplification followed by SMRT sequencing in a single embodiment.” Paper 50, 14. As a result, “no finding regarding a motivation to combine to arrive at those claimed elements is required.” Id. at 9. In addition, it was error to require Petitioner to show that a skilled artisan “would have had a reasonable expectation of success in performing RCR replication of SMRTbell templates followed by SMRT sequencing.” Id. at 13. “Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.” Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999). Therefore, the only issue for us to decide is “whether Travers ’075 enabled RCR amplification followed by SMRT sequencing.” Paper 50, 8.” slip op. at 14
- Expert testimonyPatent owner expert creditedDecided for patent owner
“polymerase-template complexes in the same ZMW.” Id. (citing Ex. 1035, 39). Citing the Larrea Declaration, Petitioner contends that loading of multiple templates “is easily mitigated.” Id. at 18 (citing Ex. 1033 ¶ 19; Ex. 1035, 39). We are not persuaded by this argument either. Dr. Larrea testifies that one of the two methods to “easily mitigate[]” loading multiple templates into a single ZMW is “bioinformatically trimming the read to only the high-quality region (HQR).” Ex. 1033 ¶ 19. Dr. Larrea, however, provides no support for this testimony. In fact, he does not even explain what a “high-quality region (HQR)” is. We, thus, accord little weight to this testimony. See Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 (August 24, 2022) (precedential) (holding “conclusory and unsupported” declaration testimony is entitled to little weight).” slip op. at 26
Patent outcomesUS 10,760,127 not shown unpatentable§ 103 obviousnessPatents in suitUS 10,760,127 - Uatp IP LLC v. Slick Slide LLCSome claims unpatentablePTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision
Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20
Patent outcomesUS 11,998,854 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · NautilusPatents in suitUS 11,998,854 - Altria Client Services LLC v. Yiwu Jingangke Trading Co., Ltd.Adverse judgmentPTAB · Oct 1, 2026 · PGR2026-00035 · APJ Robert L Kinder · PGR · Adverse judgment
The Board entered adverse judgment against Patent Owner for abandoning the contest and canceled the sole challenged claim.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“Pursuant to our rules, “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” 37 C.F.R. § 42.73(b)(4). Our prior order warned that a failure to respond would be construed as an abandonment of the contest under 37 C.F.R. § 42.73(b)(4), and that entry of judgment adverse to Patent Owner and cancellation of the challenged claim may follow. Show Cause Order, 2. Because Patent Owner did not respond by the September 15, 2026, deadline and has not entered an appearance in this proceeding, we determine that Patent Owner has abandoned the contest. Under these circumstances, we enter judgment adverse to the Patent Owner and cancel the challenged design claim.” slip op. at 2
None - CSPC Pharmaceutical Group Limited / CSPC Ouyi Pharmaceutical Co., Ltd. et al. v. Ipsen Biopharm Ltd.Some claims unpatentablePTAB · Aug 13, 2026 · IPR2025-01531 · APJ Zhenyu Yang · IPR · Final written decision
Claims 1, 3–6, and 8–14 are unpatentable as obvious; claims 2, 7, and 15 were not shown unpatentable because the prior art did not establish the claimed drug sequence.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner states that, for purposes of this proceeding, it does not dispute Petitioner’s proposed definition of a POSA. PO Resp. 8. Based on the entirety of the trial record, we adopt Petitioner’s proposed definition of a POSA’s skill level because it is consistent with the skill level reflected in the disclosures of the ’552 patent and prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 9
- Expert testimonyPatent owner expert creditedDecided for patent owner
“We decline to discount Dr. Oberstein’s opinion based on the alleged conflict of interest and bias. Dr. Oberstein testified that the consulting fees he receives from Patent Owner reflect a small fraction of his income. Ex. 1210, 402:21–403:9. We also agree with Patent Owner that an oncologist prescribing an FDA-approved regimen does not evince bias. See Sur-reply 23; see also Ex. 1206, 49 (showing NALIRIFOX is a category 1, NCCN-preferred first-line therapy for metastatic pancreatic cancer), 69 (explaining category 1 is based upon high-level evidence). Petitioner also contends that Dr. Oberstein “offers conclusory opinions,” “fails to properly apply the law, continues to look at each reference in isolation, refuses to acknowledge logical suggestions in the art, and imports new limitations into the claims.” Reply 3–4. We evaluate each piece of evidence, including Dr. Oberstein’s opinion, as it relates to our substantive patentability analysis, and accord it proper weight.” slip op. at 9
- ExcludeMotion to exclude, deniedDenied
“Petitioner, as the moving party, bears the burden of proving that the material sought to be excluded is inadmissible under the Federal Rules of Evidence. See 37 C.F.R. §§ 42.20(c), 42.62(a); see also Trial Practice Guide (“TPG”)15 § II.K (“A motion to exclude must explain why the evidence is not admissible.”). For the reasons explained below, we deny Petitioner’s Motion.” slip op. at 17
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“only on a ground that could be raised under section 102 or 103 and only on the basis of prior art consisting of patents or printed publications.” 35 U.S.C. § 311(b). Whether a reference qualifies as a “printed publication” involves a case-by-case inquiry into the facts and circumstances surrounding the reference’s disclosure to the public. In re Klopfenstein, 380 F.3d 1345, 1350 (Fed. Cir. 2004). A reference is publicly accessible upon a satisfactory showing that such document has been disseminated or otherwise made available to the extent that persons interested and ordinarily skilled in the subject matter or art exercising reasonable diligence can locate it. Kyocera Wireless Corp. v. ITC, 545 F.3d 1340, 1350–51 (Fed. Cir. 2008). Conroy was published on May 12, 2011. Ex. 1003, 1. Conroy refers to Conroy Protocol (Ex. 1004), stating that “[t]he protocol, including the statistical analysis plan, is available with the full text of this article at NEMJ.org.” Ex. 1003, 3. When questioned whether he has “any reason to believe that the protocol would not have been provided on NEJM.org with this text when it was published,” Dr. Oberstein testified that “if they say they provided it, then I think they probably provided it.” Ex. 1210, 165:20–166:2. 17 Alternatively, to the extent necessary, under the circumstances of this case, we waive the requirement of § 42.63(b). See 37.C.F.R. § 42.5(b). In addition, Dr. Ratain testified that “most top journals require that the protocol be submitted at the time of initial submission, and it’s always published alongside any major paper.” Ex. 2073, 42:2–5. According to Dr. Ratain, “[c]ertainly, New England Journal of Medicine does that.” Id. at 42:6–7. We credit the testimony from both Dr. Oberstein and Dr. Ratain on this issue. Accordingly, we find Exhibit 1004 was publicly accessible at the same time Conroy was published. slip op. at 28
Patent outcomesUS 11,344,552 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,344,552 - CSPC Pharmaceutical Group Limited / CSPC Ouyi Pharmaceutical Co., Ltd. et al. v. Ipsen Biopharm Ltd.Some claims unpatentablePTAB · Aug 13, 2026 · IPR2025-00505 · APJ Zhenyu Yang · IPR · Final written decision
Claims 1, 3–6, and 8–14 are unpatentable as obvious over the first § 103 combination; claims 2, 7, and 15 were not shown unpatentable because the art did not support the claimed drug sequence.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts that [t]he person of ordinary skill in the art (POSA) would have been an M.D. and/or Pharm. D who would have completed training in medical oncology, particularly in the field of gastrointestinal (GI) cancers, or a Ph.D. in clinical pharmacology, pharmaceutical sciences, pharmaceutics, and/or drug delivery, also particularly in the field of GI cancers, or their equivalents, along with at least 1-2 years of post-doctoral experience. Pet. 26 (citing Ex. 1002 ¶¶ 44–46). Patent Owner states that, for purposes of this proceeding, it does not dispute Petitioner’s proposed definition of a POSA. PO Resp. 8. Based on the entirety of the trial record, we adopt Petitioner’s proposed definition of a POSA’s skill level because it is consistent with the skill level reflected in the disclosures of the ’552 patent and prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 9
- Expert testimonyPatent owner expert creditedDecided for patent owner
“We decline to discount Dr. Oberstein’s opinion based on the alleged conflict of interest and bias. Dr. Oberstein testified that the consulting fees he receives from Patent Owner reflect a small fraction of his income. Ex. 1210, 402:21–403:9. We also agree with Patent Owner that an oncologist prescribing an FDA-approved regimen does not evince bias. See Sur-reply 23; see also Ex. 1206, 49 (showing NALIRIFOX is a category 1, NCCN-preferred first-line therapy for metastatic pancreatic cancer), 69 (explaining category 1 is based upon high-level evidence). Petitioner also contends that Dr. Oberstein “offers conclusory opinions,” “fails to properly apply the law, continues to look at each reference in isolation, refuses to acknowledge logical suggestions in the art, and imports new limitations into the claims.” Reply 3–4. We evaluate each piece of evidence, including Dr. Oberstein’s opinion, as it relates to our substantive patentability analysis, and accord it proper weight.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“In the DI, the Board stated that the ordinary understanding of a claim reciting a “method of treating metastatic adenocarcinoma of the pancreas” that comprises “administering an antineoplastic therapy to the patient” in order “to treat the metastatic adenocarcinoma of the pancreas” is that the “treatment” would have more than a de minimis therapeutic benefit or efficacy for the patient being treated. DI 14. We, however, rejected the notion that the claims “would require some particular degree of clinical efficacy” because “the level of clinical efficacy is not a claim limitation.” Id.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Not reached
“The parties, however, disagree over whether each recited dose must be the starting dose. Petitioner argues that “claim 1 requires that the method of treatment is a first-line therapy, but does not require that the claimed doses be used as a starting dose.” Paper 51, 1. In contrast, Patent Owner argues that “[t]he specification describes that the recited dose of each drug is a ‘starting’ or ‘initial’ dose.” Paper 50, 2 (citing Ex. 1001, 13:38–45, 30:5–7). For purposes of this Decision, we do not need to resolve this dispute. See Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (stating that claim terms need only be construed to the extent necessary to resolve the controversy). As explained below, we agree with Petitioner that, even if claim 1 recites the starting dose for each drug, Petitioner has shown, by a preponderance of the evidence, that the prior art teaches each dose and a POSA would have had a reason to start with the recited doses. See infra Section II.G.3; Paper 51, 3 n.2. Because we find that the prior art teaches or suggests the claimed subject matter even under Patent Owner’s proposed narrower claim interpretation, we need not further construe the disputed claim language.” slip op. at 16
Patent outcomesUS 11,344,552 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,344,552 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 7,370,035 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision
Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10
- Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner
“Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27
Patent outcomesUS 10,552,490 not shown unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision
Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther
“Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable
“We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightMotivation not foundNot shown unpatentable
“Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42
Patent outcomesUS 9,633,139 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - Dr. Falk Pharma GmbH v. Ellodi Pharmaceuticals, L.P.Adverse judgmentPTAB · Jun 3, 2026 · PGR2025-00086 · APJ Tawen Chang · PGR · Adverse judgment
The Board granted Patent Owner’s request for adverse judgment and terminated the PGR as to claims 1–34 after Patent Owner disclaimed all challenged claims.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request judgment against itself at any time during a proceeding,” including by “[d]isclaimer of the involved application or patent” or “[c]ancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” 37 C.F.R. §§ 42.73(b)(1)–(b)(2). Accordingly, we grant Patent Owner’s Request for Adverse Judgment and terminate the proceeding. slip op. at 2
NonePatents in suitUS 12,290,598 - PTAB · May 26, 2026 · IPR2025-00425 · APJ Kristina M Kalan · IPR · Remand
The Board denied institution of IPR2025-00425 because it instituted the earlier-considered IPR2025-00424 challenging the same patent.
RulingsRemand decision- RemandOther
“Request for Director Review. See Paper 35; IPR2025-00424, Paper 35. The request was denied without prejudice and the cases were remanded to the Board to “allow discovery, narrowly tailored to resolve the RPI and privity issues.” Paper 41, 4. Following such discovery, we were instructed to “then determine on the full record whether Petitioners have met their burden of demonstrating that the Petitions are not time-barred under § 315(b), applying the framework set forth in Worlds Inc. v. Bungie, Inc., 903 F.3d 1237, 1242– 44 (Fed. Cir. 2018).” Id. A later-issued Order Supplementing Director Review Decision instructed that “if the Board determines that Petitioners met their burden to identify all RPIs in the Petitions, then the Board should maintain at most one IPR challenging” the ’225 patent. Paper 64, 3. Concurrently herewith, we issue a decision in IPR2025-00424 finding that Petitioner has met its burden of demonstrating that the Petition in that case is not time-barred under 35 U.S.C. § 315(b).” slip op. at 3
- Other 314aInstitution denied discretionary otherInstitution denied
“In connection with the ’225 patent, Petitioner filed two petitions requesting inter partes review: the petition in this proceeding (IPR2025- 00425), and the petition in IPR2025-00424. In this proceeding and in IPR2025-00424, Petitioner filed an Explanation regarding the necessity of multiple petitions. Paper 2; IPR2025-00424, Paper 2. Petitioner requested that, “if the Board uses its discretion to institute the Petitions, the Board consider the merits of IPR2025-00424 . . . before IPR2025-00425.” Paper 2,” slip op. at 2
Discretionary denialPatents in suitUS 10,589,225
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.