• Uatp IP LLC v. Slick Slide LLCSome claims unpatentable
  PTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision

  Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.

  RulingsFinal written decision

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

    “1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13

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

    “5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31

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

    “form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20

  Patent outcomesUS 11,998,854 mixed
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
  Patents in suitUS 11,998,854
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Sep 28, 2026 · IPR2025-00611 · APJ Christopher L Ogden · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

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

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

  Patent outcomesUS 11,886,774 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,886,774
• Clearwater Paper Corporation v. Graphic Packaging International LLCAll claims unpatentable
  PTAB · Sep 23, 2026 · IPR2025-00878 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1–3 and 11 are unpatentable as anticipated by Cleveland and obvious over Nakagawa and over Nakagawa combined with Tanner.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “would have at least a bachelor’s degree in mechanical or chemical engineering, materials science, polymer science, or equivalent coursework, at least a year of experience developing paper-based laminates involving the application of polymer coatings to a substrate, and the appropriate industry familiarity with biodegradability standards and degradability techniques [and] . . . [l]ess work experience may be compensated by a higher level of education, such as a master’s degree, and vice versa. Pet. 16 (citing Ex. 1003 ¶ 50). Clearwater’s definition is uncontested, and we apply that definition here, as it accords with the level of skill reflected in the asserted prior art and the problems addressed in the specification of the ’126 patent. C. Claim Construction” slip op. at 6

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We have reviewed the cited testimony of Clearwater’s expert, including their calculations for arriving at a coat weight in Nakagawa that falls within the claimed range. See Ex. 1003 ¶¶ 132–33. We find that testimony, which is unrebutted, both credible and supported by the evidence of record. Thus, in light of Clearwater’s contentions, the cited portions of Nakagawa, and the unrebutted testimony of Clearwater’s expert, we are persuaded that Nakagawa discloses or otherwise suggests each and every element of claim 1. See Pet. 45–54, 60–64. Clearwater also persuades us that Cleveland discloses the additional subject matter of dependent claims 2, 3, and 11. See Pet. 64–66. Thus, we determine that Clearwater demonstrates that claims 1–3 and 11 are unpatentable as obvious over Nakagawa. F. Ground 3—Obviousness Over Nakagawa and Tanner” slip op. at 17

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference is prior artDecided for petitioner

    “qualifies as prior art under 35 U.S.C. § 102(e)(1) “based on both its provisional and non-provisional filing dates.” Inst. Dec. 4 n.5. We were persuaded by Clearwater’s proof that Cleveland’s provisional (Ex. 1006) is “virtually identical” to Cleveland itself (Ex. 1005) and that the provisional provides written description support for at least claim 1 of Cleveland. See Pet. 18–21 (citing Ex. 1006, 2–6, 9). We were also persuaded by Clearwater’s showing that the provisional provides written support for the subject matter relied upon in Cleveland. Id. at 21–40 (citing Ex. 1006, 1–9). We are still persuaded by Clearwater’s showing. Thus, we see no reason to disturb our earlier finding that Cleveland is prior art to the ’126 patent.” slip op. at 7

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

    “protectant layers has “a coat weight of from 5 to 30 lbs/3000 ft2.” As noted by Clearwater, Cleveland discloses a total coat weight for layers 14 and 16 as falling within the claimed range. Pet. 32–34 (citing Ex. 1005 ¶ 32). In particular, Cleveland discloses that “the coextruded layer of copolyester (irrespective of which side of the substrate the layer is disposed) is of a total coat weight of between about 10 and about 40 lb/3000 ft2 in any combination of between about 80/20 to 20/80 parts by weight of Ecoflex to Biomax,” of which “a total coat weight of 25 lb/3000 ft2 is preferred.” Ex. 1005 ¶ 32. As disclosed, Cleveland’s total coat weight range of 10–40 lb/3000 ft2 falls almost entirely within the claimed range, and the preferred total coat weight of 25 lb/3000 ft2 falls squarely within the claimed range. Thus, Cleveland satisfies claim elements [1.3.2] and [1.5.2]. See Titanium Metals Corp. v. Banner, 778 F.2d 775, 782 (Fed. Cir. 1985) (“[W]hen, as by a recitation of ranges or otherwise, a claim covers several compositions, the claim is anticipated if one of them is in the prior art.”) (citation omitted). As such, we find that Clearwater adequately demonstrates that Cleveland discloses all the elements of claim 1. 4. Dependent Claims” slip op. at 12

  Patent outcomesUS 8,637,126 unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,637,126
• Posco Co., Ltd. v. ArcelormittalAll claims unpatentable
  PTAB · Jul 16, 2026 · IPR2025-00371 · APJ Brian D Range · IPR · Final written decision

  Claims 1–25 are unpatentable as obvious under § 103 over the asserted combinations of Takagi, Cornette, Suehiro, GMW14400, Laurent, and Vaissiere.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art (POSITA) “would have had an undergraduate degree in materials science, manufacturing engineering, mechanical engineering, or equivalent knowledge, training, or experience, with two years of experience working in metallurgy.” Pet. 6 (citing Ex. 1003 ¶ 15). Patent Owner does not challenge Petitioner’s definition of a POSITA for this proceeding. PO Resp. 8. Because the parties agree and because Petitioner’s proposal is reasonable and consistent with the ’227 patent specification and the prior art, we adopt Petitioner’s proposal. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 8

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

    “1. superficial layer The only independent claim at issue, claim 1, recites a “Superficial layer.” Ex. 1001, 15:6. Patent Owner argues that, based on plain and ordinary meaning, the term “superficial layer” refers to a “surface layer” or “top layer.” PO Resp. 8–9. Petitioner does not dispute this construction. See Pet. Reply 21–22 (arguing that the relevant layer of the Suehiro reference is a superficial layer because it is outermost and present at the surface). Because the parties are in agreement and because that agreement is consistent with plain language, claim language, and the ’227 specification, we construe “superficial layer” as referring to a surface layer or top layer.” slip op. at 10

  • Claim Construction › Extrinsic evidence (dictionaries, experts)Term construed petitioner constructionDecided for petitioner

    “defined stoichiometry” (Ex. 2037, 527) but the word may also be a “generic term for phases . . . which may have a narrow or extended compositional stability range” (id.). The first glossary meaning is consistent with Patent Owner’s position. The second, broader, glossary meaning is consistent with Petitioner’s position. Some of the extrinsic sources before us support the broad definition, and some support the narrow definition. See PO Sur-Reply 3–4 (arguing that Dr. Miles admitted that various treatises distinguish intermetallic compounds from alloys and solid solutions). Thus, neither Dr. Miles or Dr. Raabe is “wrong scientifically” in how they use the term “intermetallic” in this proceeding. Id. at 2 (noting that Dr. Miles agreed that Dr. Raabe’s construction is not wrong scientifically). As explained below, however, only one of these meanings is appropriate here. To decide which possible meaning applies to the ’227 patent, we focus on the patent claims and specification. Claim 1 indicates that the intermetallic layer has a “mean composition” (emphasis added). Ex. 1001, 15:1–10. This indicates, albeit weakly, that iron composition across the layer may vary rather than having ordered stoichiometry—consistent with Petitioner’s position. The specification also indicates that “intermetallic alloying” is a possibility—again, consistent with Petitioner’s position. Ex. 1001, 2:47–50. Meanwhile, nothing in the ’227 specification explicitly (or implicitly) suggests that “intermetallic layer” must be limited to elements atomically joined with defined stoichiometry in an ordered crystal structure. We also find that Dr. Miles’s testimony regarding the meaning of “intermetallic” is more credible than Dr. Rabbe’s testimony. Dr. Rabbe, in deposition, stated that Figure 2 of the challenged patent “does not show a layer that meets [his] construction of intermetallic.” Ex. 1078, 129:21–24. The ’227 patent, however, states that Figure 2 includes an “Al-rich Intermetallic layer.” Ex. 1001, Fig. 2, 3:60–64 (“FIG 2. Illustrates a coating … which does not correspond to the invention. This succession of layers (interdiffusion layer and intermetallic layer) yields inferior results in resistance spot welding.”). Also, Dr. Raabe previously referred to a layer of Takagi as having “intermetallic phase layering and structure.” Pet. Reply 4 (citing Ex. 1076 ¶ 166; Ex ¶ 1075, 17) (emphasis omitted). Thus, Dr. Raabe’s construction of “intermetallic” for this proceeding does not fully account for the ’227 patent usage of the word “intermetallic” and does not fully account for Dr. Raabe’s prior usage of the word “intermetallic.” Patent Owner argues that Petitioner’s construction “erases the meaningful distinction” between the claimed layers. PO Resp. 11. Patent Owner further argues that Petitioner’s construction renders the word “intermetallic” superfluous because allowing the intermetallic layer to be “merely a multi-element alloy erases the meaningful distinction among these layers.” Id. We disagree. The word intermetallic serves to require that the layer be composed of two or more metals or a metal and a metalloid. The word intermetallic also serves as a label to differentiate each of the four claimed layers. For example, in claim 1, the word “intermetallic” is used much like the words “interdiffusion” and “intermediate” to give each of the four layers (each having differently mean compositions) different labels.” slip op. at 16

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

    “Because IHS was a company that created an online database with the purpose of providing (selling) standards including General Motors standards to the public, we determine that a person of ordinary skill in the art would have known to look to this database and would have been able to find GMW14400. Patent Owner presents no evidence to the contrary. Because a preponderance of the evidence supports Petitioner, we determine Petitioner establishes GMW14400 is qualifies as prior art.” slip op. at 21

  Patent outcomesUS 11,326,227 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,326,227
• Posco Co., Ltd. v. ArcelormittalAll claims unpatentable
  PTAB · Jul 16, 2026 · IPR2025-00370 · APJ Brian D Range · IPR · Final written decision

  Claims 1–30 are unpatentable as obvious under § 103 over the asserted combinations of prior art.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art (POSITA) “would have had an undergraduate degree in materials science, manufacturing engineering, mechanical engineering, or equivalent knowledge, training, or experience, with two years of experience working in metallurgy.” Pet. 6 (citing Ex. 1003 ¶¶ 13–16). Patent Owner does not challenge Petitioner’s definition of a POSITA for this proceeding. PO Resp. 8. Because the parties agree and because Petitioner’s proposal is reasonable and consistent with the ’602 patent specification and the prior art, we adopt Petitioner’s proposal. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 8

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

    “1. superficial layer All independent claims at issue, claims 1, 21, and 24, recite a “superficial layer.” Ex. 1001, 15:11, 16:60, 17:21. Patent Owner argues that, based on plain and ordinary meaning, the term “superficial layer” refers to a “surface layer” or “top layer.” PO Resp. 8–9. Petitioner does not dispute this construction. See Pet. Reply 21–22 (arguing that the relevant layer of the Suehiro reference is a superficial layer because it is outermost and present at the surface). Because the parties are in agreement and because that agreement is consistent with plain language, claim language, and the ’602 specification, we construe “superficial layer” as referring to a surface layer or top layer.” slip op. at 10

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

    “defined stoichiometry” (Ex. 2037, 527) but the word may also be a “generic term for phases . . . which may have a narrow or extended compositional stability range” (id.). The first glossary meaning is consistent with Patent Owner’s position. The second, broader, glossary meaning is consistent with Petitioner’s position. Some of the sources before us support the broad definition, and some support the narrow definition. See PO Sur-Reply 3–4 (arguing that Dr. Miles admitted that various treatises distinguish intermetallic compounds from alloys and solid solutions) Thus, neither Dr. Miles or Dr. Raabe is “wrong scientifically” in how they use the term “intermetallic” in this proceeding. Id. at 2 (noting that Dr. Miles agreed that Dr. Raabe’s construction is not wrong scientifically). As explained below, however, only one of these meanings is appropriate here. To decide which possible meaning applies to the ’602 patent, we focus on the patent claims and specification. The claims indicate that the intermetallic layer has a “mean iron composition” (emphasis added). Ex. 1001, 15:6–10. This indicates, albeit weakly, that the iron composition across the layer may vary rather than having ordered stoichiometry— consistent with Petitioner’s position. The specification also indicates that “intermetallic alloying” is a possibility—again, consistent with Petitioner’s position. Id. at 2:50–54. Meanwhile, nothing in the ’602 specification explicitly (or implicitly) suggests that “intermetallic layer” must be limited to elements atomically joined with defined stoichiometry in an ordered crystal structure. We also find that Dr. Miles’s testimony regarding the meaning of “intermetallic” is more credible than Dr. Raabe’s testimony. Dr. Raabe, in deposition, stated that Figure 2 of the challenged patent “does not show a layer that meets [his] construction of intermetallic.” Ex. 1078, 129:21–24. The ’602 patent, however, states that Figure 2 includes an “Al-rich Intermetallic layer.” Ex. 1001, Fig. 2, 3:57–61 (“FIG 2. Illustrates a coating . . . which does not correspond to the invention. This succession of layers (interdiffusion layer and intermetallic layer) yields inferior results in resistance spot welding.”). Also, Dr. Raabe previously referred to a layer of Takagi as having “intermetallic phase layering and structure.” Pet. Reply 4 (citing Ex. 1076, 166; Ex. 1075, 17) (emphasis omitted). Thus, Dr. Raabe’s definition of “intermetallic” does not fully account for the ’602 patent usage of the word “intermetallic” and does not fully account for Dr. Raabe’s prior usage of the word “intermetallic.” Patent Owner argues that Petitioner’s construction “erases the meaningful distinction” between the claimed layers. PO Resp. 11. Patent Owner further argues that Petitioner’s construction renders the word “intermetallic” superfluous because allowing the intermetallic layer to be “merely a multi-element alloy erases the meaningful distinction among these layers.” Id. We disagree. The word intermetallic serves to require that the layer be composed of two or more metals or a metal and a metalloid. The word intermetallic also serves as a label to differentiate each of the four claimed layers. For example, in claim 1, the word “intermetallic” is used much like the words “interdiffusion” and “intermediate” to give each of the four layers (each having differently defined mean iron compositions) different labels.” slip op. at 16

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

    “have had reason to combine teachings of Takagi and Cornette with a reasonable expectation of success. Pet. 11–20 (citing, e.g., Ex. 1003 ¶¶ 28– 42; Ex. 1016 ¶ 35; Ex. 1014, 9; Ex. 1025, 5:17–20; Ex. 1026, 7; Ex. 1034 ¶ 13). In particular, Petitioner argues that Takagi discloses a pre-coating thickness of 10–20 µm but does not explicitly disclose a post hot-stamping coating thickness corresponding to the pre-coating thickness. Pet. 11. Cornette teaches that the hot-stamping thickness causes coating expansion from 25 µm to about 40 µm, an increase of 60%. Id. (citations omitted). Petitioner and Dr. Miles reason that, when hot stamping Takagi’s product, the thickness would be 32 µm. Id. (citing Ex. 1003 ¶ 32); see also Pet. Reply 20–21. Thus, Patent Owner argues that Cornette evidences Takagi’s finally coating thickness without requiring modification of Takagi. Petitioner further argues that Takagi and Cornette teach that post hot- stamping thickness could be varied and optimized as a result effective variable. Id. at 12–13; see also Pet. Reply 17–18. Cornette teaches, for example, that “[t]he average [pre-coating] layer thickness showing the best compromise between corrosion protection and weldability is 25 µm” and links this pre-coating thickness to a final thickness of “about 40 µm at the steel surface.” Ex. 1014, 9. Petitioner also argues that it would have been obvious to fill in other details of Takagi including, for example, selecting USIBOR 1500 steel, based on the teachings of Cornette. Pet. 14. Patent Owner argues that there is no reason to combine Takagi with the teachings of Cornette. PO Resp. 26. Patent Owner makes seven related arguments. Patent Owner first argues that the Petitioner’s position is speculative and lacks basis. Id. at 26–27. We disagree. Cornette evidences a final coating thickness for Takagi, and the references also suggest that final coating thickness is result effective. Second, Patent Owner argues that there would have been no incentive to seek a motivation to seek a thicker coating post-hot stamping. Id. at 28– 35. This argument does not undermine Petitioner’s position that Takagi, by itself, would have reached a thicker coating after stamping as evidenced by Cornette. Pet. 11–12. Petitioner takes the position, with evidence, that practice of Takagi alone would reach the recited thickness. No motivation to modify Takagi is required under this position.” slip op. at 25

  Patent outcomesUS 10,961,602 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,961,602
• Innoscience America, Inc. v. Infineon Technologies Americas Corp.No claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00175 · APJ Jo-Anne M Kokoski · IPR · Final written decision

  Claims 1–17 were not shown unpatentable because Petitioner failed to establish that Usui’s interconnect structure or Yu’s metal gate stacks satisfy the construed “electrode stack” limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “(“POSITA” or “POSA”) would have had “at least a four-year degree in electrical engineering or a closely related field, and at least two years of experience in semiconductor device design,” and “[a]dditional education could substitute for professional experience and vice versa.” Pet. 6 (citing Ex. 1002 ¶¶ 80–82). Patent Owner does not dispute Petitioner’s proposed level of ordinary skill. PO Resp. 1–76. Neither party explains why the outcome of this case would be affected by the adoption of the proffered definition of a person of ordinary skill in the art. In the Institution Decision, we adopted the assessment offered by Petitioner. Dec. 6–7. Because Petitioner’s definition of the level of skill in the art is consistent with the ’562 patent and the asserted prior art, we maintain Petitioner’s definition for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir 2001).” slip op. at 9

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

    “comprises the recited metals and has the recited thickness, which forms an electrical contact for use on a semiconductor device generally or a group III- V semiconductor in particular. This is consistent with our determination that “electrode stack” is a conductor that provides a path for current entering or leaving a medium such as a semiconductor device We disagree with Patent Owner that “electrode stack” as used in the challenged claims should be limited to the specific electrodes shown in the embodiments described in the Specification. See PO Resp. 4–9. Although the Specification describes embodiments using source, drain, and Schottky gate electrodes as electrical contacts, we see no reason to construe the term “electrode stack” itself to be limited to these components as Patent Owner proposes. Claims 1 and 13 expressly recite that electrode stacks comprise the claimed “electrical contact,” without expressly including or precluding any specific type of electrode. Ex. 1001, 5:54–63, 6:37–47. The Federal Circuit advises that the Specification “is not a substitute for, nor can it be used to rewrite, the chosen claim language. ‘Specifications teach. Claims claim.’” SuperGuide, 358 F.3d at 875 (quoting SRI Int’l v. Matsushita Elec. Corp. of Am., 775 F.2d 1107, 1121 n.14 (Fed. Cir. 1985) (en banc)). The Specification does teach electrical contacts that include source, drain, and Schottky gate electrodes, but claims 1 and 13 are directed to electrical contacts that are not expressly so limited. Patent Owner’s proposed construction would effectively rewrite the claim by adding limitations, which we decline to do under the guise of claim construction. See id. (“Though understanding the claim language may be aided by the explanations contained in the written description, it is important not to import into a claim limitations that are not a part of the claim.”). In view of the foregoing, we construe the claim term “electrode stack” to mean “a conductor that provides a path for current entering or leaving a medium such as a semiconductor device.”” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential). In contrast, Patent Owner’s declarant Dr. Piner testifies, with evidentiary support, that interconnects (such as Usui’s interconnect metallurgy structure) and electrical contacts (such as that claimed in the ’562 patent) are not the same thing. See Ex. 2024 ¶¶ 63–70. For example, Dr. Piner explains: In other words, not all metals in a semiconductor device have the same purpose and could not be said to be interchangeable. By August 2009 it was well known to a POSA how to discern if a metal component in a transistor is an interconnect or serves as an electrical contact such as a gate contact or ohmic contact, based on the structure and functionality of the metal component. For example, interconnects are made up of metal strips and are deposited on insulators. EX-1011 (Mishra) at 216. Interconnects are low resistance conductors that can carry very high current densities. Id., 216, 217. Unlike Schottky contacts and ohmic contacts, interconnects do not provide non-linear IV response like Schottky contacts nor inject electrons and holes into semiconductors like ohmic contacts. Id., 218. As many of the references cited by Dr. Zhao illustrate, electrical contacts had their own highly complex design challenges. EX-1008 (Pearton), 41-59 (Pages 53-71 of 383) (discussing electrical contacts); EX-1017 (Kramer), 11-126 (Pages 18-130 of 151) (same). And while Dr. Zhao cites these as supporting a POSA’s knowledge of an electrical contact, none of these references describe electrical contacts as interconnects. Id. ¶ 71. Dr. Piner further testifies that Usui’s interconnect metallurgy structure is an interconnect, and not an electrical contact, because “Usui states that ‘[t]he structures fabricated by the process of the present invention are especially useful for forming electrical connections or wiring such as between active and/or passive devices of an integrated circuit structure.’” Id. ¶ 148 (citing Ex. 1004, 1:11–14) (alteration in original); see also id. ¶¶ 150– 151 (Dr. Piner testifying that Usui’s interconnect metallization structure is not an “electrode stack” under a broad definition of electrode). Dr. Piner’s testimony in this regard rebuts Petitioner’s and Dr. Zhao’s conclusory assertions to the contrary.” slip op. at 21

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

    “conductor that provides a path for current entering or leaving a medium such as a semiconductor device.” Thus, Petitioner must show that Usui’s layers 13–15, 18, and 19 provide a path for current entering or leaving a medium such as a semiconductor device. After reviewing the complete trial record, we are not persuaded that Petitioner has done so. Petitioner relies on the testimony of Dr. Zhao to support its contention that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential).” slip op. at 21

  Patent outcomesUS 8,686,562 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,686,562
• Luxottica Of America, Inc. v. E-Vision Smart Optics, Inc.Adverse judgment
  PTAB · Jun 29, 2026 · IPR2025-01512 · APJ Arthur M Peslak · IPR · Adverse judgment

  The Board granted Patent Owner’s request for adverse judgment, cancelled claims 1–27, and terminated the proceeding.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “A party may request entry of adverse judgment against itself at any time during an inter partes review proceeding. See 37 C.F.R. § 42.73(b). Under these circumstances, entry of judgment adverse to the Patent Owner is appropriate as to claims 1–27 of the ’612 patent. Consequently, we grant Patent Owner's request for adverse judgment.” slip op. at 2

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
  None
  Patents in suitUS 11,971,612
• 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

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.