• GD Energy Products, LLC v. Kerr Machine CompanyAll claims unpatentable
  PTAB · Jun 29, 2026 · PGR2025-00031 · APJ Ryan H Flax · PGR · Final written decision

  Claims 1–14 are unpatentable as obvious under each of four asserted grounds: Kerr; Aplex and Stanton; Blume, Stanton, and Wilkinson; and the sale of the Kerr Pump.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The person of ordinary skill in the art would have a minimum of a bachelor’s degree in mechanical or petrochemical engineering, or a comparable engineering discipline, and a minimum of 3-5 years of work experience in the design and/or manufacturing of reciprocating pumps and valves, including fluid ends and/or comparable high pressure fluid components, for industrial applications, including for use in the oil and gas industry. See, e.g., EX1003, ¶32.” slip op. at 12

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

    “[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We decline to expressly construe any claim language. slip op. at 12

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

    “Regarding the combining of Aplex and Stanton, Petitioner asserts that the ordinarily skilled artisan would have understood that providing a packing/stuffing arrangement, as taught by Stanton, within a fluid end housing, as taught by Aplex, would improve pressure and fluid isolation compared with an arrangement where the packing was bolted to the outside of the fluid end as in Aplex unmodified. Pet. 66 (citing Ex. 1003 ¶¶ 189, 236). Patent Owner does not dispute this rationale. We find this to be a reason, with rationale underpinning, why the person of ordinary skill in the art would have combined these references with a reasonable expectation of success.” slip op. at 29

  • Adverse judgmentOther

    “The record indicates that Patent Owner has statutorily disclaimed claim 15 as of April 28, 2025. Ex. 2206.” slip op. at 8

  Patent outcomesUS 12,152,582 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,152,582
• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Jun 24, 2026 · PGR2025-00009 · APJ Susan L C Mitchell · PGR · Final written decision

  Claims 1, 2, 6–14, and 16–29 are unpatentable based on written description, enablement, and obviousness grounds.

  RulingsFinal written decision

  • Director reviewDirector review, deniedDenied

    “Following institution, Patent Owner filed a Director Review Request (Paper 33), and Petitioner filed an Authorized Response (Paper 37), and the then-Acting Director issued a denial of the Director Review Request. Paper 40.” slip op. at 3

  • Additional discoveryAdditional discovery, deniedDenied

    “(Paper 46, “PO Resp.”), Petitioner filed a Reply to Patent Owner’s Response (Paper 71, “Pet. Reply”), and Patent Owner filed a Sur-reply (Paper 84, “PO Sur-reply”). Patent Owner filed a motion for additional discovery (Paper 62), Petitioner opposed the Motion for Discovery (Paper 63), and the Board denied the Motion for Discovery (Paper 77).” slip op. at 3

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art We consider the grounds of unpatentability in view of the” slip op. at 8

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

    “description itself. To the extent the experts disagree on this point, we credit the testimony of Petitioner’s experts over that of Patent Owner’s. For these reasons, we find that a preponderance of the evidence of record better supports a finding that in the 2011–2012 timeframe, it would have been unpredictable to identify which multiple mutants retained hyaluronidase activity, even with the single substitution data provided by the ’035 patent.” slip op. at 53

  Patent outcomesUS 12,123,035 unpatentable
  § 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 12,123,035
• 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
• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Jun 8, 2026 · PGR2025-00004 · APJ Susan L C Mitchell · PGR · Final written decision

  Claims 1–4, 7–19, and 22 are unpatentable under § 112(a) for lack of written description and enablement, and under § 103 as obvious.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art We consider the grounds of unpatentability in view of the” slip op. at 8

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “1. Petitioner’s Position Petitioner asserts that the “terms used in the claims are either” slip op. at 12

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

    “7. Analysis We find the preponderance of the evidence supports a finding that the” slip op. at 59

  • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not enabledUnpatentable

    “6. Analysis Petitioner has the burden to identify how the specification allegedly” slip op. at 70

  Patent outcomesUS 12,018,298 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 12,018,298
• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · May 18, 2026 · PGR2025-00006 · APJ Cynthia M Hardman · PGR · Final written decision

  Claims 1–4 and 8–13 are unpatentable under §112(a) for lack of written description and enablement, and under §103 as obvious over the ’429 patent and Chao.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art We consider the grounds of unpatentability in view of the understanding of a person of ordinary skill in the art (sometimes referred to 3 US 7,767,429 B2, issued Aug. 3, 2010 (the “’429 patent”) (Ex. 1005). 4 Chao et al., Structure of Human Hyaluronidase-1, a Hyaluronan Hydrolyzing Enzyme Involved in Tumor Growth and Angiogenesis, 46 BIOCHEMISTRY 6911–20 (2007) (Ex. 1006). 5 Patent Owner withdrew the Declaration of Dr. Triggs-Raine. PO Resp. 10 n.6. herein as “POSA”) as of the effective filing date of the challenged claims. Petitioner contends that one of ordinary skill in the art would have had an undergraduate degree, a Ph.D., and post-doctoral experience in scientific fields relevant to study of protein structure and function (e.g., chemistry, biochemistry, biology, biophysics). From training and experience, the person would have been familiar with factors influencing protein structure, folding and activity, production of modified proteins using recombinant DNA techniques, and use of biological assays to characterize protein function, as well with techniques used to analyze protein structure (i.e., sequence searching and alignments, protein modeling software, etc.). Pet. 16.” slip op. at 7

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

    “5. Evidence and Analysis “The construction of claims is simply a way of elaborating the normally terse claim language in order to understand and explain, but not to change, the scope of the claims.” Embrex, Inc. v. Serv. Eng’g Corp., 216 F.3d 1343, 1347 (Fed. Cir. 2000). We first turn to the intrinsic evidence because “the specification is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.” Phillips v. AWH Corp., 415 F.3d 1303, 1314 (Fed. Cir. 2005) (en banc). “[T]he specification may reveal a special definition given to a claim term by the patentee that differs from the meaning it would otherwise possess. In such cases, the inventor’s lexicography governs.” Id. at 1316. [T]he definition in the patent documents controls the claim interpretation. . . . Any other rule would be unfair to competitors who must be able to rely on the patent documents themselves, without consideration of expert opinion that then does not even exist, in ascertaining the scope of a patentee’s right to exclude. Southwall Tech., Inc. v. Cardinal IG Co., 54 F.3d 1570, 1578 (Fed. Cir. 1995). a) Intrinsic evidence Our analysis begins with the claims and Specification of the ’262 patent. Claim 1 recites a “modified PH20 polypeptide” that also requires the polypeptide sequence is 95% identical to one of the 35 recited SEQ ID NOs and with at least one of seven amino acids at position 317 of the reference sequence. The ’262 patent states “PH20 refers to a type of hyaluronidase that occurs in sperm and is neutral-active.”7 Ex. 1001, 45:45– 46; cf. id. at 68:33–37. The ’262 patent further explains that “[r]eference to PH20 includes precursor PH20 polypeptides and mature PH20 polypeptides (such as those in which a signal sequence has been removed), truncated forms thereof that have activity, and includes allelic variants and species variants, variants encoded by splice variants, and other variants.” Id. at 45:62–67. The ’262 patent states that “PH20 polypeptides also include those that contain chemical or posttranslational modifications and those that do not contain chemical or posttranslational modifications.” Id. at 46:4–7.” slip op. at 15

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

    “four species tested, and particularly in a primate model that is physiologically more similar to humans, shows that a POSA would not have understood even unmodified PH20 polypeptides to provide a contraceptive effect in humans and most other species. The data Patent Owner relies upon at most shows an immunocontraceptive effect for unmodified PH20 polypeptides limited to guinea pigs. It does not evidence that a POSA would have understood that the recited modified polypeptides would provide such an effect or otherwise be useful in a contraceptive vaccine. Accordingly, even if the term “modified PH20 polypeptides” were interpreted to include inactive polypeptides that can serve as antigens to provide a contraceptive effect, the preponderance of the evidence does not show that a POSA would have understood the inventors to be in possession of the full scope of the recited polypeptides capable of such use. 7. Analysis We find the preponderance of the evidence supports a finding that the claims fail to comply with the written description requirement. “Every patent must describe an invention. It is part of the quid pro quo of a patent.” Ariad, 598 F.3d at 1345. In determining compliance with the written description requirement for nucleic acid genus claims, the Federal Circuit has identified two extremes. In Capon, claims relying on known nucleotide sequences with known functions were found to satisfy the written description requirement. Capon v. Eshhar, 418 F.3d 1349, 1358 (Fed. Cir. 2005). At the other end, Juno found that for broad claims to a nucleic acid encoding a chimeric T cell receptor with a functional requirement to bind a target, “the written description ‘must demonstrate that the applicant has made a generic invention that achieves the claimed result and do so by showing that the applicant has invented species sufficient to support a claim to the functionally-defined genus.’” Juno Therapeutics, Inc. v. Kite Pharma, Inc., 10 F.4th 1330, 1337 (Fed. Cir. 2021) (quoting Ariad, 598 F.3d at 1349). As explained above, claim 1 requires modified PH20 polypeptides with some hyaluronidase activity. See supra Section II.B. Based on this claim interpretation, we find the evidence in this case closer to Juno than Capon, and that the ’262 patent does not disclose sufficient structural features in the PH20 sequences associated with hyaluronidase or” slip op. at 57

  • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not enabledUnpatentable

    “6. Analysis Petitioner has the burden to identify how the specification allegedly fails to enable the claims. We address the Wands factors and the parties’ respective arguments and evidence. a) Breadth of Claims and Nature of the Invention Dr. Park states, regarding the breadth of claim 1, that he “calculated the number of distinct polypeptides that exist that meet the specified criteria.” Ex. 1004 ¶ 173. Dr. Park’s table is reproduced below: Dr. Park’s table shows that the “number of distinct peptides is extremely large by all accounts, ranging from 1049 to 1066.” Id. Dr. Hecht agrees, stating the “sequence identity language causes the claims to encompass an immense number of distinct PH20 polypeptides.” Ex. 1003 ¶ 120. To illustrate how large a number like 1066 is, Dr. Hecht states that an “aggregate weight of the smallest set containing one molecule of each of the PH20 mutants would be . . . = 1.37 x 1027 kg. The weight of the Earth is ‘only’ ~ 5.97 x 1024 kg.” Id. ¶ 123. That is, Dr. Hecht states that a complete set of one single molecule of protein that comprises all possible mutations in PH20 as recited in claim 1 would weigh about one thousand times more than the entire mass of planet Earth. See id. In deposition, Dr. Hecht stated “my sense was that the ’262 patent lists a minuscule and highly biased sample of what would be within that fence, in the sense that it only lists single amino acid substitutions while at the same time it’s attempting to claim things that have 20 or more substitutions.” Ex. 2076, 203:6‒12. When asked if a sequence “gives you enough information to tell whether that amino acid sequence is 95 percent identical to SEQ ID NO. 3”, Dr. Hecht answered “Yes, but that’s all it tells you. It doesn’t tell you anything about active, precipitated, aggregated, folded. It doesn’t tell you anything.” Id. at 204:11‒19.” slip op. at 70

  Patent outcomesUS 12,152,262 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 12,152,262
• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · May 12, 2026 · PGR2025-00003 · APJ Jeffrey N Fredman · PGR · Final written decision

  Claims 1–4 and 8–21 are unpatentable for lack of written description and enablement; obviousness over the ’429 patent and Chao was not shown.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “VII. LEVEL OF ORDINARY SKILL IN THE ART We consider the grounds of unpatentability in view of the” slip op. at 7

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

    “term “modified PH20 polypeptide” in the ’600 patent supports the understanding that some type of activity is required for a polypeptide to be a “modified PH20 polypeptide”, and that the enzymatic activity of hyaluronidase is the most frequently identified activity recited in the definitions section of the ’600 patent. Id. at 48:38–53, 50:9‒17, 51:15‒18, 52:41–47, 55:9–23, 63:37–44, 64:14–19. In contrast, the discussion regarding the potential use of “modified PH20 polypeptides that are inactive” as antigens in contraception vaccines appears only in a non-definitional section of the ’600 patent. Id. at 75:56–58, 72:60–62. Accordingly, it does not modify the definition’s explicit requirement that the claimed “modified PH20 polypeptide” exhibit hyaluronidase activity. Id. at 48:38–53.” slip op. at 19

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

    “been able to use the data in the Specification to make reasonable predictions about the effect of multiple modifications on hyaluronidase activity, we view this testimony to at most describe a research plan (i.e., a “tool to engage in further modification”14) for finding the recited polypeptides rather than demonstrating the inventors were in possession of the full scope claimed. This is particularly so given the limits of the then-available analytical tools noted above and the fact that the structural connections and three dimensional modeling Patent Owner’s experts attempt to make (see, e.g., Ex. 2070 ¶¶ 129–213; Ex. 2068 ¶ 123) do not appear in the written description itself. To the extent the experts disagree on this point, we credit the testimony of Petitioner’s experts over that of Patent Owner’s. For these reasons, we find that a preponderance of the evidence of record better supports a finding that in the 2011–12 timeframe, it would have been unpredictable to identify which multiple mutants retained hyaluronidase activity, even with the single substitution data provided by the ’600 patent.” slip op. at 51

  • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not enabledUnpatentable

    “8. Conclusion We find that the balance of evidence supports a finding of undue” slip op. at 101

  Patent outcomesUS 11,952,600 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 11,952,600
• First Quality Retail Services, LLC / First Quality Consumer Products, LLC et al. v. Essity Hygiene And Health ABAll claims unpatentable
  PTAB · May 12, 2026 · IPR2024-01487 · APJ Kristina M Kalan · IPR · Final written decision

  Claims 1–5, 7, 8, 20–22, 24, and 25 are unpatentable, based on anticipation by Bergstrom and obviousness over the stated combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Institution Decision, we adopted Petitioner’s definition. Dec. 9–10. In its Response, Patent Owner cites to Petitioner’s definition and states that Patent Owner “applies Petitioners’ definition.” PO Resp. 7. Because Petitioner’s definition of the level of skill in the art is consistent with the ’138 patent and the asserted prior art, we maintain it for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 10

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

    “We begin our analysis with the language of the claims. Phillips, 415 F.3d at 1312; see also SuperGuide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 874–875 (Fed. Cir. 2004) (“There is a ‘heavy presumption’ that the terms used in the claims ‘mean what they say and have the ordinary meaning that would be attributed to those words by persons skilled in the relevant art.’”). Claim 1 recites, in relevant part, “said fluid flow control structure being a layered structure comprising a non-perforated fibrous polymeric layer and a first perforated polymeric layer.” Ex. 1001, 13:62–64 (limitation [1h]). The plain language of claim 1 does not address additional properties of the perforated polymeric layer; the language of the dependent claims, however, imposes additional limitations on the properties of the perforated polymeric layer such as a particular basis weight (claim 2), a particular makeup (claim 3), a particular aperture size (claim 7), a particular open area (claim 8), and that it “is a three-dimensionally formed layer having penetrating apertures extending from a first surface of the first perforated polymeric layer towards a second surface of the first perforated polymeric layer and forming protrusions on said second surface” (claim 4). The dependent claims’ additional language indicates that the term “perforated” within the term “perforated polymeric layer” in claim 1 is not limited in the manner asserted by Patent Owner’s proposed construction.” slip op. at 12

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “layer pierced through with holes or apertures,” we are persuaded that Petitioner meets its burden as to this limitation. Petitioner argues that under our construction, Bergstrom’s express disclosure of forming element 60, and Bergstrom’s explanation of the properties of forming element 60, meets the claimed “perforated polymeric layer” limitation. Pet. 38–41 (citing Ex. 1002 ¶¶ 114–117). Even under Patent Owner’s proposed construction, Petitioner argues, forming element 60 would also allow free flow of liquid bodily waste. Pet. Reply 3– 4 (citing Ex. 1021 ¶¶ 20–23). Importantly, Bergstrom expressly discloses: “suitable materials for the forming element 60 are plastic films, perforated plastic films and reinforced tissue or reinforced nonwoven materials.” Ex. 1004, 10:1–4. This express disclosure is clear. Even though the forming element 60 in Bergstrom might be “typically” liquid-impermeable (Ex. 1004, 9:24–30), that does not preclude a layer that is perforated, particularly where Bergstrom expressly discloses a perforated plastic film as one of the possibilities for forming element 60. Ex. 1004, 10:1–4. Additionally, although Patent Owner focuses on Bergstrom’s disclosure that forming element 60 is “typically liquid-impermeable” (PO Resp. 58–60; Ex. 1004, 9:24–30), we do not view Bergstrom’s use of the word “typically” as mandating that the forming element always be liquid impermeable. We agree that the word “typically” does not mean “always” and that such a reading would render “typically” superfluous. Pet. Reply. 5. We do not find any ambiguity in Bergstrom’s disclosure regarding possible use of perforated plastic films for its forming element 60; whether or not the forming element 60 provides other functions (like stiffness) does not dictate whether it may also be perforated, or be part of a fluid flow control structure. On this point, we credit Petitioner’s arguments and explanation, as supported by Dr. Pourdeyhimi’s testimony. Pet. Reply 6–7; Ex. 1021 ¶ 27–28 (“components of absorbent articles could be multifunctional”).” slip op. at 20

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

    “from the start” (PO Resp. 29), and that “using all or part of [Glaug’s] fluid-acquisition system in place of [Nakazawa’s] diffusion sheet would be antithetical to the teachings of both references” (id. at 35), we agree that the proposed combination of Nakazawa’s structure with the layers of Glaug is sufficiently motivated and reasonably expected to result in a successful article, for the reasons articulated by Petitioner. See, e.g., Pet. 59–65; Ex. 1002 ¶¶ 176–192. Namely, although fluid may flow in both Z directions in Nakazawa (PO Resp. 30), that does not foreclose the combination with Glaug in the manner proposed by Petitioner. See generally Ex. 1002 ¶¶ 176–192; see id. ¶ 184 (detailing the mechanics of the proposed combinations), ¶¶ 188–191 (discussing motivation to combine), ¶ 192 (discussing reasonable expectation of success). The combination can be achieved “either by adding the lower acquisition layer 64 [of Glaug] to diffusion sheet 63 [of Nakazawa], or by replacing diffusion sheet 63 [of Nakazawa] with the two-layer fluid acquisition system 34 [of Glaug],” and as persuasively explained by Dr. Pourdeyhimi, the arrangement constitutes a “fluid flow control structure.” See Ex. 1021 ¶¶ 45–47. Additionally, the diffusion sheet in Nakazawa can be made from the same material as used in Glaug, namely, AquiDry™. Id. ¶¶ 53–55; see also Tr. 17:25–18:3 (“although Glaug does not specify the name AquiDry in its disclosure, Patent Owner’s expert testified that it’s his understanding that Glaug is discussing the AquiDry material, the same material that is in Nakazawa . . . . they disclose using the same material, and Nakazawa says this material work[s]”). When asked if Patent Owner’s expert had any concerns that AquiDry was not the same as between Nakazawa and Glaug, Patent Owner’s counsel replied “They are the same, Your Honor. And we embrace that.” Tr. 46:8–12; see also id. at 58:19 (Petitioner’s counsel commenting about Patent Owner’s counsel: “they agree, AquiDry is used in both Nakazawa and Glaug”). Thus, Patent Owner’s argument that Nakazawa’s diffusion sheet and Glaug’s fluid acquisition layer have different purposes because Nakazawa’s diffusion sheet allegedly must promote fluid flow in the Z-directions, both toward and away from the body (PO Resp. 29–37; Ex. 2004 ¶¶ 26–28, 30– 35)) is not clearly supported by Nakazawa, and is also contravened by the shared disclosure of Nakazawa and Glaug as to the composition of the disputed layer. We have reviewed the complete record, including Patent Owner’s and Mr. Sheldon’s assertions that Nakazawa requires promoting fluid flow in both Z-directions (see id.), but find that Petitioner carries its burden to demonstrate that one of ordinary skill in the art would have been motivated to combine Nakazawa and Glaug with a reasonable expectation of success. On this complete record, Petitioner explains sufficiently why and how a person of ordinary skill would modify Nakazawa’s diffusion sheet, i.e., to use Glaug’s fluid acquisition system, or the lower non-perforated layer of its fluid acquisition system, in Nakazawa, and Petitioner provides well-supported reasons for doing so.” slip op. at 36

  Patent outcomesUS 9,308,138 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,308,138
• Illumina, Inc. v. Molecular Loop Biosciences, Inc.No claims unpatentable
  PTAB · Apr 15, 2026 · IPR2024-01419 · APJ Susan L C Mitchell · IPR · Final written decision

  Claims 1–9 were not shown unpatentable because the asserted references failed to disclose the claimed correcting step, and Chee was not prior art to claims 1–3 and 9.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedReference not prior artDecided for patent owner

    “We have considered both parties’ arguments and evidence and determine that Patent Owner has presented sufficient evidence of reasonable the invention to practice every day during the critical period in order to demonstrate reasonable diligence. See Perfect Surgical Techniques, Inc. v. Olympus America, Inc., 841 F.3d 1004, 1009 (Fed. Cir. 2016). “[D]iligence need not be perfectly continuous—only reasonably continuous.” Arctic Cat Inc. v. GEP Power Prods., Inc., 919 F.3d 1320, 1331 (2019). The key question is whether, “in light of the evidence as a whole, the invention was not abandoned or unreasonably delayed.” Id. (internal quotations omitted). Applying this standard, we determine that Patent Owner sufficiently demonstrates reasonably continuous diligence throughout the critical period.” slip op. at 32

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

    “introduced during said workflow by collapsing target:differentiator tag combinations observed more than once into a single count.” Ex. 1001, 131:46–48 (emphasis added). The “determining step” of claim 2 recites “determining a consensus base call for the target nucleic acid molecule sequences,” but performs “collapsing all sequence reads comprising a same differentiator tag into a single read,” before the “determining step.” Id. at 131:49–53. Patent Owner proposes an interpretation of these “collapsing” and “determining” steps recited in claims 1 and 2 and asserts that they should be construed as distinct steps performed in a particular order in which the “collapsing step” is performed before the “determining step.” PO Resp. 42–45. We agree. First, Patent Owner asserts a person of ordinary skill in the art would have understood that the “collapsing step” of claim 1 is distinct from, and must occur before, the “determining step” of claim 2 based on the plain language of claims 1 and 2. PO Resp. 42–43. Patent Owner argues that the “collapsing step” and the “determining step” are distinct steps because claims 1 and 2 use different terms to describe these distinct steps that are performed sequentially according to the claim language. Id. (citing Ex. 1001, 131:47–54; Ex. 2023 ¶ 133; Ex. 2024, 57:11–58:22). More specifically, Patent Owner explains that claim 1 recites a “collapsing step,” followed by claim 2, which depends from claim 1 and refers to “collapsing” before “determining a consensus base call” such that “claim 2 describes determining a consensus base call from collapsed reads, not performing ‘collapsing’ by determining a consensus base call.” Id. at 42 (citing Ex. 1001, 131:47–54). collapsing corrects for skewing, an issue related to over- or under-amplification, which is a separate and distinct problem from the sequence errors that a consensus base call is designed to address.” Id. at 43 (citing Ex. 1001, 27:47–50, 32:29–34). Patent Owner contends further that “‘[c]ollapsing’ is a different step, performed separately from determining any consensus base call, to provide even greater accuracy when subsequently determining a consensus base call” such that “if one were to collapse by determining the consensus base call, errors from amplification bias could still be represented in the consensus base call generated.” Id. at 43–44 (emphasis omitted, citing Ex. 2023 ¶¶ 134–37). Second, Patent Owner argues a person of ordinary skill in the art would have understood that the “collapsing step” of claim 1 is distinct from the “determining step” based on the specification of the ’730 patent. PO Resp. 43–45. For example, Patent Owner explains that the specification states that “[f]or any target:differentiator tag combination observed more than once, all such reads are ‘collapsed’ into a single read before consensus basecalls are determined. This will cancel the effect of bias on consensus basecall accuracy.” Id. at 43 (emphasis omitted) (quoting Ex. 1001, 72:63– 73:5) (citing Ex. 2023 ¶¶ 133, 138–142).” slip op. at 11

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “We have considered both parties’ arguments and evidence and agree with Patent Owner’s position. As discussed above, we agree with Patent Owner that the “collapsing step” recited in claim 1 and the “determining step” recited in claim 2 are two different steps required by the challenged claims such that “collapsing” does not mean determining a consensus base call or sequence, and must occur before any determining step. As a result, we determine Chee’s step of determining a consensus sequence does not disclose the “collapsing step” recited in claim 1 that requires collapsing “target:differentiator tag combinations.” We are also unpersuaded by Petitioner’s reliance on Chee’s process of correcting for amplification bias as disclosing the claimed collapsing step. As recognized by Patent Owner, the claim language of the “collapsing step” requires “collapsing target:differentiator tag combinations,” rather than collapsing only differentiator tags. In view of this requirement, Chee does not disclose the “collapsing step” because Chee teaches quantifying the starting nucleic acid molecules using their unique identifiers, rather than target:differentiator tag combinations. As Petitioner admits, “Chee’s technique for correcting amplification bias corrects quantitative errors without correcting sequencing errors” (Reply 15), whereas claim 1’s “collapsing step” corrects both quantitative errors and sequencing errors by using target:differentiator tag combinations. See Ex. 1001, 131:47–49 target:differentiator tag combinations).” slip op. at 41

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

    “Given this claim interpretation requiring collapsing target:differentiator tag combinations, it is undisputed that McCloskey, who uses unique barcodes alone, does not teach this limitation. Petitioner does not rely on Bignell as teaching this collapsing step. Accordingly, we conclude Petitioner has not shown that the combination of Bignell and McCloskey teaches the “collapsing step” recited in claim 1. Because claims 4 through 6 depend from claim 1, they also require the “collapsing step” of claim 1 that is not taught by the combination of Bignell and McCloskey.” slip op. at 54

  Patent outcomesUS 11,840,730 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Graham
  Patents in suitUS 11,840,730

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.