• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Oct 15, 2026 · PGR2025-00030 · APJ Susan L C Mitchell · PGR · Final written decision

  Claims 1, 2, and 6–30 are unpatentable under §112(a) for lack of written description and lack of enablement; the §103 ground was not reached.

  RulingsFinal written decision

  • Additional discoveryAdditional discovery, deniedDenied

    “Patent Owner filed a Motion for Additional Discovery (Paper 42), Petitioner opposed the motion (Paper 44), and the Board denied the motion (Paper 47).” slip op. at 3

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

    “of the ’758 patent supports an understanding that some activity is required for a polypeptide to be a “modified PH20 polypeptide,” and it is the enzymatic activity of hyaluronidase specifically that is the most frequently identified activity recited in the Definitions section of the ’758 patent. Indeed, both the definitions of “PH20” and “modified PH20 polypeptide” require hyaluronidase activity. See Ex. 1001, 45:54–55, 50:39–41 (“PH20 refers to a type of hyaluronidase that . . . is neutral-active” and “neutral active refers to the ability . . . to enzymatically catalyze the cleavage of hyaluronic acid at neutral pH”); 48:43–46 (“A modified PH20 polypeptide can have up to 150 amino acid replacements so long as the resulting modified PH20 polypeptide exhibits hyaluronidase activity.”). Similar language is used later in the definition of a “conjugate” to explain that even when the modified PH20 polypeptide is linked to another polypeptide or chemical moiety it “retains hyaluronidase activity.” Id. at 63:39–46. In contrast, the discussion regarding the potential use of “modified PH20 polypeptides that are inactive” as antigens in contraception vaccines appears only in non-definitional sections of the ’758 patent. Id. at 72:63–65, 75:60–62. Accordingly, we find that this disclosure does not modify the definition’s explicit requirement that the claimed “modified PH20 polypeptide” exhibit hyaluronidase activity. Id. at 48:38–46.” slip op. at 21

  • Skill levelOther

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

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “this testimony to at most describe a research plan (i.e., a “tool to engage in further modification”16) 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–125) 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. See Ex. 1133 ¶¶ 111–251 (identifying problems with the approaches proposed by Patent Owner’s experts). 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 ’758 patent.” slip op. at 56

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

  Claims 1–17 are unpatentable for lack of written description, lack of enablement, and indefiniteness; the Board did not find them unpatentable as obvious.

  RulingsFinal written decision

  • Skill levelOther

    “II. ANALYSIS A. 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 board ownDecided for petitioner

    “Specification of the ’345 patent supports an understanding that some activity is required for a polypeptide to be a “modified PH20 polypeptide,” and it is the enzymatic activity of hyaluronidase specifically that is the most frequently identified activity recited in the Definitions section of the ’345 patent. Indeed, the definitions of “PH20” and “modified PH20 polypeptide” both require hyaluronidase activity. See Ex. 1001, 44:20–21, 49:4–7 (“PH20 refers to a type of hyaluronidase that . . . is neutral-active” and “neutral active refers to the ability . . . to enzymatically catalyze the cleavage of hyaluronic acid at neutral pH”); 47:8–11 (“A modified PH20 polypeptide can have up to 150 amino acid replacements so long as the resulting modified PH20 polypeptide exhibits hyaluronidase activity.”). Similar language is used later in the definition of a “conjugate” to explain that even when the modified PH20 polypeptide is linked to another polypeptide or chemical moiety it “retains hyaluronidase activity.” Id. at 61:60–67. In contrast, the discussion regarding the potential use of “modified PH20 polypeptides that are inactive” as antigens in contraception vaccines appears only in non-definitional sections of the ’345 patent. Id. at 71:16-18, 74:11–13. Accordingly, we find that this disclosure does not modify the definition’s explicit requirement that the claimed “modified PH20 polypeptide” exhibit hyaluronidase activity. Id. at 47:3–11.” slip op. at 20

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

    “description (see Capon, 418 F.3d at 1357–58), Patent Owner is trying to extend that to include that which is at most obvious from the prior art, as opposed to what is actually described. That is, it may have been obvious to a POSA to align PH20 sequences with other known hyaluronidase enzymes and to use the crystal structure of a different hyaluronidase (Hyal-1) in SWISS-MODEL to generate a three-dimensional structure, but none of that is described in the common disclosure itself. “[A] description that merely renders the invention obvious does not satisfy the [written description] requirement.” Ariad, 598 F.3d at 1352. While a POSA might be able to embark on their own research program to try to find suitable multiply-modified PH20 polypeptides, the four corners of the written description do not demonstrate possession of such. See id. at 1356‒57 (recognizing that “[p]erhaps one of ordinary skill could discover this information, but this does not alter our conclusion that the description . . . just represent[s] a wish or arguably a plan for future research”) (internal quotation omitted).” slip op. at 66

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

    “instances of epistasis are “rare” and an inactive PH20 polypeptide “will stay inactive . . . absent intentional ‘rescue’ mutations.” See Sur-reply 12–14. But the claims encompass far more than combinations of just two substitutions, and even Dr. Petsko concedes there are “billions” of sequences within the recited sequence space that will not properly fold. See Ex. 2070 ¶ 347; see also Ex. 1133 ¶ 237 (“While some [residues critical to protein structure] can be predicted (e.g., highly conserved positions), many others cannot without experimentation.”). Accordingly, we find Petitioner’s position more persuasive than Patent Owner’s competing position and evidence.” slip op. at 108

  Patent outcomesUS 12,264,345 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · Nautilus
  Patents in suitUS 12,264,345
• Merck Sharp And Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Sep 25, 2026 · PGR2025-00039 · APJ Michael A Valek · PGR · Final written decision

  Claims 1–4 and 7–11 are unpatentable because the challenged claims lack written-description support and are not enabled.

  RulingsFinal written decision

  • Adverse judgmentAdverse judgmentOther

    “1 Although the Petition was directed to claims 1–11 of the ’185 patent, Patent Owner filed a statutory disclaimer of claims 5 and 6 prior to institution, leaving just claims 1–4 and 7–11 at issue. See Ex. 2003.” slip op. at 2

  • Skill levelOther

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

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

    “B. Claim Construction In a post-grant review, we interpret a claim “using the same claim” slip op. at 11

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

    “For these reasons, we find that a preponderance of the evidence” slip op. at 59

  Patent outcomesUS 12,104,185 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 12,104,185
• Merck Sharp And Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Sep 25, 2026 · PGR2025-00033 · APJ Michael A Valek · PGR · Final written decision

  Claims 1, 2, and 6–29 are unpatentable for lack of written description and enablement; the Board did not find them obvious over the ’429 patent and Chao.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “structural connections and three-dimensional modeling Patent Owner’s experts attempt to make (see, e.g., Ex. 2070 ¶¶ 126–212, 297–342; Ex. 2068 ¶¶ 123–125, 245, 294–313, 318) 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. See Ex. 1133 ¶¶ 111–230 (identifying problems with the approaches proposed by Patent Owner’s experts). 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 ’652 patent.” slip op. at 58

  • Skill levelOther

    “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 › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Decided for petitioner

    “exclude the use of modified PH20 polypeptides as contraceptives—the only other possible utility described in the ’652 patent—is unavailing. Resp. 39. First, “[t]he fact that a patent asserts that an invention achieves several objectives does not require that each of the claims be construed as limited to structures that are capable of achieving all of the objectives.” Phillips, 415 F.3d at 1327 (citing Liebel–Flarsheim Co. v. Medrad, Inc., 358 F.3d 898, 908 (Fed. Cir. 2004)). Second, unlike the definitions of “PH20” and “modified PH20 polypeptide” in the “Definitions” section of the Specification, the passages describing possible contraceptive use do not contain any characteristics suggesting they are definitional in nature. See Alnylam, 138 F.4th at 133 (enumerating “characteristics” such as the fact that the text appears in the “Definitions” section, sets the term off in quotation marks, and uses phrases like “refer to” that indicate that specification language is definitional in nature). Accordingly, the statement that “[a]lso provided are modified PH20 polypeptides that are inactive, and that can be used, for example, as antigens in contraception vaccines” (Ex. 1001, 75:56–58), does not redefine the term, nor otherwise void the definitional language in the Specification stating that a “modified PH20 polypeptide can have up to 150 amino acid replacements, so long as the resulting modified PH20 polypeptide exhibits hyaluronidase activity.” Id. at 48:47–49 (emphasis added).” slip op. at 26

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

    “1352. While a POSA might be able to embark on their own research program to try to find the genus of multiply-modified PH20 polypeptides recited in the challenged claims, the four corners of the written description here do not demonstrate the inventors were in possession of such. See id. at 1356–57 (recognizing that “[p]erhaps one of ordinary skill could discover this information, but this does not alter our conclusion that the description . . . just represent a wish or arguably a plan for future research”) (internal quotation omitted).” slip op. at 68

  Patent outcomesUS 12,049,652 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 12,049,652
• Charles River Laboratories, Inc. v. Seikagaku CorporationAll claims unpatentable
  PTAB · Sep 8, 2026 · PGR2025-00023 · APJ Per Curiam · PGR · Final written decision

  Claims 1–9 are unpatentable as anticipated by the ’629 publication; the claims are not entitled to the 2013 priority date.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “We find that a rigid requirement as to the subject of a POSITA’s doctoral degree (e.g., biochemical engineering, enzymology), or experience working specifically with horseshoe crab proteins, is not consistent with the evidence of record. See, e.g., Ex. 1067, 20:23–21:2 (Dr. Schaefer testifying that the fact the “name of [his] Ph.D. is immunology . . . does not change the fact that the core of [his] thesis training was really in molecular biology”), 22:3–15 (explaining that “the fact that the production of proteins recombinantly is mostly species agnostic”); Ex. 1069, 45:20–47:17 (Dr. Morris testifying that whether a person is a POSITA depends on the person’s “experience, [ ] publications,” and work done for the Ph.D. rather than the name of the Ph.D. program). We also find that evidence of record supports Petitioner’s assertion that, for purposes of defining a POSITA, “[m]ore education could substitute for experience, and vice versa.” See, e.g., Pet. 22; Ex. 1065, 99:14–100:3. Accordingly, based on the entirety of the trial record, we find a POSITA with respect to the claims of the ’109 patent would have had a two years of experience with cloning genes, expressing cloned genes as proteins, and/or characterizing such cloned genes and proteins, with more education being able to substitute for experience, and vice versa. A POSITA may also have collaborated with others, including those with specific experience in utilizing or assessing horseshoe crab Factor C for endotoxin detection and quantitation.” slip op. at 9

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

    “Neither party proposes an express construction of any claim term. See Pet. 22–23 (not proposing any constructions); PO Resp. 23 (“Patent Owner agrees that the terms can be afforded their plain and ordinary meaning.”). However, Patent Owner states that some of Petitioner’s arguments implicitly construe claim 1 in an erroneous manner. PO Resp. 23–28. “For example, Petitioner argues that ‘an adequate written description would have to either disclose representative examples of the possible working cascades of various proteins or some accurate structural feature of the claimed proteins that allow them to function in the claimed assay as a whole.’” Id. at 23 (quoting Pet. 35). Patent Owner argues that, contrary to what Petitioner’s argument allegedly implies, “Claim 1 is directed to a method for producing an endotoxin assay agent” and does not require the use – Owner that claim 1 does not require the use of endotoxin assay agent. However, the claimed endotoxin assay agent must be capable of performing the assay, as counsel for Patent Owner acknowledged. Tr. 83:5–9.” slip op. at 10

  • BurdenNot shown unpatentable

    “In this case, to show that the claims of the ’109 patent are unpatentable for lack of written description, Petitioner would have needed to show that the specification as filed (i.e., the ’420 application) fails to reasonably convey to those skilled in the art that Patent Owner had possession of the claimed subject matter as of the July 3, 2023, filing date. Petitioner did not. Pet. 23–24. Nor does Petitioner’s declarant offer testimony that could support such a showing. See Ex. 1003 ¶50 (“I have been asked to provide my opinions as to the state of the art in this field for purposes of determining what the inventors disclosed as their invention as of December 10, 2013.”), ¶51 (“Whenever I offer an opinion in this declaration about the knowledge of a POSA, the manner in which a POSA would have understood the claims of the ’109 patent or its description, the manner in have been led to do based on the prior art, I am referencing the December 10, 2013 timeframe.”). In our Institution Decision, we stated: Although the ’420 application is essentially identical to the ’767 application, the person of ordinary skill in 2013 is not the same as in 2023. See Ariad, 598 F.3d at 1351 (“[T]he [written description] test requires an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” (emphasis added)). Thus, the information presented in the Petition, which is limited to the perspective of a 2013 POSITA, does not demonstrate that it is more likely than not that at least 1 of the claims challenged in the Petition is unpatentable for lack of written description. Inst. Dec. 12 (alterations in original). During trial, Petitioner did not present any further arguments in support of Ground 1. See generally Pet. Reply. Petitioner has failed to prove that claims 1–9 are unpatentable for failing to meet the written description requirement set forth in 35 U.S.C. § 112(a).” slip op. at 12

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot shown unpatentable

    “Although the evidence before us shows that, in 2013, a POSITA knew how to recombinantly express genes in expression systems such as CHO or HEK-293 cell lines, the evidence shows that this was true only for genes whose genetic sequences were known or readily available. See, e.g., Ex. 1069, 34:11–22 (“Q. Okay. So you would agree that the creation of the recombinant protein requires the underlying sequence of, as you said, the original animal? A. Of course.”) Because it is undisputed that, in 2013, the genetic sequence for Limulus polyphemus Factor C was unknown, or least not publicly available, Falko-Gunter does not support a finding of adequate written description here. See, e.g., Tr. 48:18–19 (“Patent Owner agrees that there had not been, as of 2013, the full length cDNA sequence for Limulus polyphemus Factor C published.”).” slip op. at 23

  Patent outcomesUS 11,959,109 unpatentable
  Claim construction§ 102 anticipation§ 112 disclosure
  Patents in suitUS 11,959,109
• Charles River Laboratories, Inc. v. Seikagaku CorporationAll claims unpatentable
  PTAB · Sep 8, 2026 · IPR2025-00440 · APJ Tawen Chang · IPR · Final written decision

  Claim 21 is unpatentable as obvious over Mizumura with either the ’498 PCT or McClymont; the Revised Contingent Motion to Amend proposing claim 22 is denied.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “overlap to a significant degree, i.e., a person with a Ph.D. in a discipline related to biological sciences and having had at least two years of work experience. However, the parties’ proposals differ slightly in the specific subjects in which a POSA would have had a doctoral degree, and whether the person’s work experience must have been directly related to horseshoe crab Factor C. As an initial matter, we find that a rigid requirement as to the subject of a POSA’s doctoral degree (e.g., biochemical engineering, enzymology), or experience working specifically with horseshoe crab proteins, is not consistent with the evidence of record. See, e.g., Ex. 1067, 20:23–21:2 (Dr. Schaefer testifying that the fact the “name of [his] Ph.D. is immunology . . . does not change the fact that the core of [his] thesis training was really in molecular biology”), 22:3–15 (explaining “the fact that the production of proteins recombinantly is mostly species agnostic”); Ex. 1069, 45:20–47:17 (Dr. Morris testifying that whether a person is a POSA depends on the person’s “experience, [ ] publications,” and work done for the Ph.D. rather than the name of the Ph.D. program). We also find that evidence of record supports Petitioner’s assertion that, for purposes of defining a POSA, “[m]ore education could substitute for experience, and vice versa.” See, e.g., Pet. 19; Ex. 1065, 99:14–100:3. with respect to the claims of the ’318 patent would have had a Ph.D. in molecular biology, biochemistry, or a related discipline, and about two years of experience with cloning genes, expressing cloned genes as proteins, and/or characterizing such cloned genes and proteins, with more education being able to substitute for experience, and vice versa. A POSA may also have collaborated with others, including those with specific experience in utilizing or assessing horseshoe crab Factor C for endotoxin detection and quantitation.” slip op. at 13

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

    “C. Claim Construction The parties agree that “the terms in claim 21 can be afforded their plain and ordinary meaning for purposes of this proceeding” without further construction. Pet. 19–20; PO Resp. 11. Because express claim construction is not needed to resolve the issues in this case, we need not, and do not, construe expressly any claim term for purposes of this Decision. 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 14

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner

    “Carrying Out the Invention section, that “[t]he Factor C of the present invention is a Factor C derived from a horseshoe crab,” and states later in the same section that “[e]xamples of the horseshoe crab include . . . Limulus polyphemus.” Ex. 1006, 40. However, none of the remaining portions of ’767 application cited by Patent Owner relate directly to L. polyphemus; instead, the remaining portions of ’767 application cited by Patent Owner are directed to other species, in particular the Japanese horseshoe crab T. tridentatus. Further, Patent Owner’s witness, Dr. Schaefer, conceded that the ’767 application does not contain Factor C sequence information for L. polyphemus. See, e.g., Ex. 1067, 44:25–45:23. Although “[n]o length requirement exists for a disclosure to adequately describe an invention,” Falko-Gunter, 448 F.3d at 1365–1366, we are persuaded that a POSA would not, based on the totality of the above disclosures, reasonably understand that the inventors were in possession of the claimed HEK-293 recombinant L. polyphemus Factor C protein, in view of the state of the art as of December 10, 2013. In this regard, we note that adequate written description of a biological molecule, such as a HEK293 recombinant L. polyphemus Factor C protein, requires “more than a mere statement that it is part of the invention and reference to a potential method for isolating it”; instead, what is required is “‘a precise definition, such as by structure, formula, chemical name, or physical properties,’ not a mere wish or plan for obtaining the claimed chemical invention.” The Regents of the” slip op. at 21

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

    “Pfizer, Inc. v. Apotex, Inc., 480 F.3d 1348, 1364 (Fed. Cir. 2007). Neither do we see Petitioner’s arguments regarding the December 10, 2013 priority date to be “mutually opposed” as Dr. Schaefer testified. Ex. 1067, 216:4– 24. Instead, we credit evidence of record, including Dr. Jain’s testimony and the February 22, 2018 Mizumura Declaration, that existence of the full sequence would permit a more complete analysis and that such an analysis would provide a POSA with a reasonable expectation that the claimed L. polyphemus recombinant protein would have a residual activity within the claimed range. See, e.g., Ex. 1029, 2–5; Ex. 1010, 48; Ex. 1065, 117:14– 130:24 (explaining that comparison of partial sequences in the Tokunaga 1991 publication showed “difference around the cleavage site” between T. tridentatus and L. polyphemus but comparison of the full sequence revealed that “the catalytic triad of histidine, serine, aspartate . . . to be more similar between Tachypleus and Limulus”). Patent Owner asserts that “Petitioner’s reliance on a statement made by Dr. Mizumura in a declaration submitted during prosecution of the ’767 Application fails to fill the gap in the analysis” regarding reasonable expectation of success, because the declaration “offers no evidence of the percentage of conserved amino acid substitutions that exist to support the conclusion that a POSA would have expected residual activity to be maintained between Tachypleus tridentatus and Limulus polyphemus” PO Resp. 47. However, as noted above, Dr. Mizumura provides an alignment of Factor C proteins from the two different species of horseshoe crab, determines that the similarity between the amino acid sequence is 99.5%, states that the amino acid residues that can undergo N-type sugar chain that L. polyphemus, like T. tridentatus, would also be less susceptible to inhibition by ions. Ex. 1029, 4–5. For the reasons discussed above, we also disagree with Patent Owner’s assertion that Petitioner’s reasonable expectation of success argument is “nothing more than conclusory assertions with no support.” PO Resp. 46. Rather, we find Petitioner has shown, by a preponderance of the evidence, that a POSA would have had reason to combine the teachings of Mizumura and the ’498 PCT, with a reasonable expectation of success in arriving at the Factor C protein recited in claim 21.” slip op. at 38

  Patent outcomesUS 11,236,318 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 11,236,318
• 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

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.