• Axon Enterprise, Inc. / Dedrone Holdings, Inc. et al. v. Airspace Defense, Inc.Some claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00629 · APJ Scott C Moore · IPR · Final written decision

  Original claim 12 is not unpatentable; substitute claim 37 is added, while substitute claims 21–28 and 30–36 are denied as obvious.

  RulingsFinal written decision

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

    “F.3d at 1279–80, we begin our analysis with the Specification of the ’711 Patent. The Specification indicates when a UAV (such as the recited “reference aerial vehicle”) navigates autonomously, it flies without manual control, and can, for example, track and fly to a target using information captured onboard the vehicle itself. See Ex. 1001, 3:24–28 (“[I]t may not be desirable to manually control the interceptor aerial vehicle to follow the target UAV. In some embodiments, the interceptor aerial vehicle is able to autonomously track and fly to the target UAV using machine vision based on images captured by a camera of the interceptor aerial vehicle.”). The Specification also indicates that “autonomous” means more than just “automatic flight,” and clarifies that autonomous navigation occurs when a UAV that previously received a target location from an external source subsequently turns and flies itself towards the received location. See, e.g., id. at 4:15–17 (disclosing that the detected location of a target may be provided to an interceptor “to allow it to automatically and autonomously fly toward the direction of the detected location”); 15:64–16:3 (automatic and autonomous navigation occurs when an interceptor’s navigation component and/or flight controller receive the location of a target, and adjust the interceptor “to turn and fly towards the received location . . . based on the received location”); 16:49–60 (“For example, a flight direction and/or speed of an interceptor aerial vehicle are automatically and autonomously adjusted based on a location and size of the target within the captured image. . . . This allows the flight path of the interceptor aerial vehicle to be dynamically adjusted to track and follow a moving target.”).” slip op. at 11

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

    “have had reason to combine Beard and Laufer in the manner proposed by Petitioner, the combination would not satisfy the Autonomous Navigation limitation required by claim 12 because Laufer’s autopilot commands are generated by and transmitted from a remote command center (i.e., Laufer’s central controller 115). PO Resp. 15–16. In its Reply, Petitioner does not dispute that Laufer’s autopilot commands are generated by Laufer’s central controller 115, which is remote from the aircraft being controlled. See Reply 13–17. Petitioner asserts, however, that the combination still satisfies the Autonomous Navigation limitation because these autopilot commands are generated without human input. See id. Based on the complete trial record, Patent Owner’s arguments are persuasive. See PO Resp. 15–16; PO Sur-reply 42, 1–6; Ex. 2025 ¶¶ 84–87. The flight of Beard’s UAV 100 under the control of Laufer’s autopilot commands does not satisfy the Autonomous Navigation limitation of claim 12, as we have construed that limitation, because Laufer’s autopilot commands are generated at a location that is remote from UAV 100 (Laufer’s central controller 115.) See, e.g., Ex. 1010 ¶ 40 (“Central controller 115 uses autopilot command module 440 to generate autopilot aircraft commands”), ¶¶ 26, 30 (clarifying that central controller 115 and the controlled interceptor aircraft are separate devices that may communicate through a “wireless connection”), Fig. 4 (depicting “aircraft control commands 475” being generated externally from the depicted “Interceptor Aircraft”); see also Ex. 2025 ¶¶ 95–95. Petitioner never disputes that, in the proposed combination, Laufer’s central controller 115 would remain external to Beard’s UAV 100. See Reply 13–17. Instead, Petitioner relies on its proposed construction of the Autonomous Navigation limitation, which would have encompassed such an arrangement. See id. Our construction of the Autonomous Navigation limitation, which did not adopt Petitioner’s claim construction position, is dispositive of Petitioner’s argument. We thus determine that Petitioner has not shown by a preponderance of the evidence that claim 12 would have been obvious over Beard and Laufer.” slip op. at 15

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part

    “the legal requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121. Lectrosonics, Paper 15 at 4, 7–8. For the reasons that follow, we determine that Patent Owner has satisfied this burden. 1. Proposal of a Reasonable Number of Substitute Claims A motion to amend must “propose a reasonable number of substitute claims.” 35 U.S.C. § 316(d)(1)(B); see also 37 C.F.R. § 42.121(a)(3) (“A motion to amend may cancel a challenged claim or propose a reasonable number of substitute claims.”). “There is a rebuttable presumption that a reasonable number of substitute claims per challenged claim is one (1) substitute claim.” Lectrosonics, IPR2018-01129, Paper 15 at 4; see also 37 C.F.R. § 42.121(a)(3). Patent Owner has shown it proposes a reasonable number of substitute claims by proposing a single substitute claim for each of challenged claims 1–4, 8–11, and 13–20. MTA 1–2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 2. Amendments Respond to a Ground of Unpatentability “A motion to amend may be denied where … [t]he amendment does not respond to a ground of unpatentability involved in the trial.” 37 C.F.R. § 42.121(a)(2)(i). Patent Owner has responded to the grounds of unpatentability involved in this proceeding by amending the claims in response to the Petition’s asserted prior art. See MTA 2, 25, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 3. No Enlargement of the Scope of the Claims An amendment may not seek to enlarge the scope of the claims of the patent. 35 U.S.C. § 316(d)(3); 37 C.F.R. §§ 42.121(b)(1)–(b)(2). Patent Owner asserts that the amendments in the Motion do not enlarge the scope of the claims of the patent because each proposed substitute claim “retains all of the limitations of the corresponding challenged claim, and each proposed independent substitute claim adds further limitations.” See MTA 2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 4. No Introduction of New Matter An amendment may not introduce new matter. 35 U.S.C. § 316(d)(3);” slip op. at 22

  • 112 supportDecided for patent owner

    “Having considered the evidence and argument cited by both parties, we determine there is sufficient written description support for the disputed portions of limitations [37.e1], [37.e3,] and [37.e4]. The ’452 application discloses selecting between groups of processing schemes (e.g., algorithms) depending on a confidence level, where the groups are, for example: high cost, high robustness algorithms; medium cost, medium robustness algorithms; and low cost, low robustness algorithms. See Ex. 2019 ¶¶ 146–147. These schemes or algorithms may be neural networks. See, e.g., id. ¶ 50 (including neural network as a type of algorithm); see also id. ¶¶ 109–110); see generally MTA Opp 1 (not disputing that schemes may be neural networks). Specifically, the ’452 application describes “algorithms that process video frames of one or more video data streams,” and “produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Id. ¶ 141. The ’452 application also discloses the concept of switching between neural networks based on confidence levels. In particular, the ’452 application discloses that a “process cycles through the processing schemes to produce a detection of an object,” for example, where “if the confidence number is higher than an activation number, an action is performed to stop or change a running group (i) and select or switch to group (ii).” Id. ¶ 146. More particularly, “a processing scheme from the group of (i) High cost (low refresh rate), high robustness algorithm[s] can select a cheaper processing scheme from the group of (ii) Medium cost, medium robustness algorithms.” Id. The ’452 application additionally discloses that schemes or algorithms (e.g., neural networks) are applied to individual video frames, and that the confidence levels that determine which neural network will be applied in the future are also derived from individual video frames. For example, as discussed above, the ’452 application describes that “[t]he processing schemes produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Ex. 2019 ¶ 141 (emphases added). The ’452 application also describes selecting and applying an individual neural network, rather than only selecting and applying a group of processing schemes. For example, as highlighted above, the ’452 application describes that “a processing scheme from the” “High” group “can select a cheaper processing scheme from the” “Medium” group. Id. ¶ 146 (emphases added). In our view, these disclosures, read together, would reasonably convey to one skilled in the art that the inventor had possession of the disputed subject matter described above. See Ariad, 598 F.3d at 1351.” slip op. at 24

  Patent outcomesUS 10,514,711 mixed
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
  Patents in suitUS 10,514,711
• Anthony Inc. v. Controltec, LLCAll claims unpatentable
  PTAB · Sep 30, 2026 · IPR2025-00636 · APJ Barry L Grossman · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious: claims 8–12 over Carter; claims 1–20 over Carter and Bunch; claims 3, 9, 10, and 19 over Carter, Bunch, and King; and claims 2, 11–13, and 17 over Carter, …

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “testimony that we limit the level of ordinary skill to “refrigerated display cases.” Limiting the level of skill to an engineer with experience “working with refrigerated display cases” does not relate to the technology disclosed, and the invention claimed, in the ’847 patent, which is controlling condensation and conserving energy. E.g., Ex. 1001, 2:23–27 (“The invention is proactive in preventing condensation from forming by activating frame/door heaters before the dew point temperature at frame and door surfaces is reached. Power is then cycled off at a set point above dew point to save energy.” (emphases added)). An electrical engineer with a bachelor’s degree and 2 years of experience focused on lighting systems for refrigerated display cases would have “experience working with refrigerated display cases,” and thus meet Patent Owner’s proposed level of skill. Such a person, however, would not be experienced in controlling condensation, dew point sensor positioning, and condensation algorithm design, which is the focus of the disclosed and claimed invention, and which Mr. Pollock states “materially affect performance, energy use, and reliability” in controlling condensation in a refrigerated display case. Ex. 2037 ¶ 10. We also note that Mr. Pollock’s qualifications include a “B.S. in Mechanical Engineering, . . . with focus on thermal and mechanical systems, thermodynamics, and HVAC&R (Heating, Ventilation, Air Conditioning & Refrigeration).” Ex. 2037 ¶ 3. His academic focus is consistent with our determination of the level of ordinary skill. Accordingly, based on the prior art, the sophistication of the disclosed technology in the ’847 patent, finding Mr. Pollock’s testimony on this issue too general, and crediting Dr. Henze’s testimony with substantial probative weight, we adopt Petitioner’s definition of the level of ordinary skill. We” slip op. at 19

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “Accordingly, based on the prior art, the sophistication of the disclosed technology in the ’847 patent, finding Mr. Pollock’s testimony on this issue too general, and crediting Dr. Henze’s testimony with substantial probative weight, we adopt Petitioner’s definition of the level of ordinary skill. We more experience will offset less academic training, as did Dr. Henze (Ex. 1003 ¶ 31). Thus, in this proceeding a person of ordinary skill would have a bachelor’s degree in mechanical engineering, electrical engineering, or a comparable field and at least three to five years of professional experience working with heating, ventilating, air conditioning, and refrigeration (HVAC&R) systems, and that more academic training will offset less experience, and more experience will offset less academic training. 2. Dr. Henze Is a Person of Ordinary Skill Patent Owner asserts that Dr. Henze is not a person of ordinary skill and thus is not qualified to provide expert testimony in this proceeding. PO Resp. 18–21 (citing Kyocera Senco Indus. Tools Inc. v. Int’l Trade Comm’n, 22 F.4th 1369, 1377 (Fed. Cir. 2022). Patent Owner’s argument requires a level of ordinary skill based on “working with refrigerated display cases,” which we have not adopted. PO Resp. 27. Based on the level of skill adopted in the previous section, we determine that Dr. Henze is qualified to provide expert testimony in this proceeding C. Claim Construction We construe each claim “using the same claim construction standard” slip op. at 19

  • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notNot reached

    “[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co. Ltd., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). Whether the preamble is or is not limiting is not necessary to resolve this controversy because it would not affect the outcome of this case. We also note that it is beyond reasonable dispute that Bunch, applied with Carter against all the challenged claims, discloses display cases with glass doors. Ex. 1006, 1:14–16. Bunch also discloses that, in the display cases, “[t]o combat condensation and frost, heaters are installed in refrigerator doors and frames, which raise the temperature of the door or frame sufficiently to eliminate condensation.” Id. at 1:24–26. slip op. at 22

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “A reference qualifies as prior art for an obviousness determination only when it is analogous to the claimed invention. In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004) (“References within the statutory terms of 35 U.S.C. § 102 qualify as prior art for an obviousness determination only when analogous to the claimed invention.” (citing In re Clay, 966 F.2d 656, 658 (Fed. Cir. 1992))). The Federal Circuit has laid out two separate tests to determine whether a reference is analogous art to the claimed invention, i.e., whether reference. In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004). These two tests are: “(1) whether the art is from the same field of [the inventor’s] endeavor” and “(2) if the reference is not within the field of the inventor’s endeavor, whether the reference still is reasonably pertinent to the particular problem with which the inventor is involved.” Id.; see also Netflix, Inc. v. DivX, LLC, 80 F.4th 1352, 1359 (Fed. Cir. 2023) (“Importantly, ‘the scope of any field of endeavor will vary with the factual description of each invention.’ Unlike the reasonable-pertinence test, the field-of-endeavor test does not look to the problem that the patent purports to address. It is enough that the prior art reference falls within the relevant field of endeavor of the patent-in-suit.”) (citations omitted); Unwired Planet, LLC v. Google Inc., 841 F.3d 995, 1001 (Fed. Cir. 2016) (“To determine if art is analogous, we look to ‘the purposes of both the invention and the prior art.’ If a reference disclosure and the claimed invention have a same purpose, the reference relates to the same problem, which supports an obviousness rejection.” (citations omitted)); see also Nielsen Co. (US), LLC v. TVision Insights, Inc., 186 F.4th 1363, 1369–1370 (Fed. Cir. 2026) (providing a comprehensive summary and analysis of the applicable law concerning analogous art)” slip op. at 37

  Patent outcomesUS 7,421,847 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,421,847
• Shenzhen Root Technology Co., Ltd. v. Willow Blossom Holdco Limited And Willow Innovations, Inc.All claims unpatentable
  PTAB · Sep 25, 2026 · IPR2025-00554 · APJ Barry L Grossman · IPR · Final written decision

  Claims 17–19 and 21–33 are unpatentable as obvious under each asserted § 103 ground.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Factors pertinent to a determination of the level of ordinary skill in the art include: (1) educational level of the inventor; (2) type of problems encountered in the art; (3) prior art solutions to those problems; (4) rapidity with which innovations are made; (5) sophistication of the technology; and (6) educational level of workers active in the field. Env’t Designs, Ltd. v. Union Oil Co., 713 F.2d 693, 696–697 (Fed. Cir. 1983) (citing Orthopedic Equip. Co. v. All Orthopedic Appliances, Inc., 707 F.2d 1376, 1381–82 (Fed. Cir. 1983)). Not all such factors may be present in every case, and one or more of these or other factors may predominate in a particular case. Id. Moreover, these factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art. Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). In determining a level of ordinary skill, we also may look to the prior art, which may reflect an appropriate skill level. Okajima, 261 F.3d at 1355.” slip op. at 17

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

    “according to the Phillips standard,” and that “no formal claim constructions are necessary for purposes of resolving controversies in this proceeding. Pet. 3. We agree. Given the lack of dispute on this record, we do not perceive the need to construe any claim limitation. Claims must be construed “only to the extent necessary to resolve the controversy.” AstraZeneca AB v. Mylan Pharms. Inc., 19 F.4th 1325, 1345 (Fed. Cir. 2021) (quoting Vivid Techs., Inc. v. American Science & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999); see also Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe the claim preambles here where the construction is not ‘material to the [obviousness] dispute.’” (citations omitted)).” slip op. at 18

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We find Mr. Bauer’s testimonial evidence persuasive and undisputed as to why a person of ordinary skill, a degreed engineer with two years of experience designing human breast pump equipment, would modify Furrer to use a battery as a power source, and have a reasonable degree of confidence that it would work successfully.” slip op. at 26

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

    “We find Mr. Bauer’s testimonial evidence persuasive and undisputed as to why a person of ordinary skill, a degreed engineer with two years of experience designing human breast pump equipment, would modify Furrer to use a battery as a power source, and have a reasonable degree of confidence that it would work successfully. Concerning the proposed combination of Furrer and Alvarez, Mr. Bauer testifies why a person of ordinary skill would combine Furrer and Alvarez, explaining that: a POSITA6 would have turned to the teachings of Alvarez to implement Furrer’s vacuum pump using a conventional pump controller having a portable, battery-powered pump to not only increase portability and to allow the user to move about when using the device but also to provide improved control for the system. Ex. 1003 ¶ 138. Mr. Bauer also testifies: a POSITA would have recognized that Alvarez advantageously provides details for such a conventional vacuum pump suitable for safely and controllably delivering negative pressure using a “[c]ontroller 115 [that] “houses the power source and drive mechanism for pumping device 100, and also contains hardware for various functions, such as controlling pumping device 100, milk production quantification, and communication with other devices. 6 “POSITA” is a patent law acronym for a “person of ordinary skill in the art.” Id. ¶ 139 (citing Ex. 1005 ¶ 69). Mr. Bauer further explains that Alvarez discloses that a “pump unit2100 [disclosed in Alvarez] preferably include[es] a controller and processor 2104 as well as a motor 2102 for actuating the device.” Id. (citing Ex. 1005 ¶ 115); see also id. ¶¶ 140–142 (providing “second,” “third,” and “fourth” reasons why a person of ordinary skill would have been motivated to combine Furrer and Alvarez). Mr. Bauer concludes from his analysis that “a person skilled in the art” slip op. at 26

  Patent outcomesUS 11,806,454 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,806,454
• Anthony Inc. v. Controltec, LLCAll claims unpatentable
  PTAB · Aug 25, 2026 · IPR2025-00559 · APJ Barry L Grossman · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious over the five asserted grounds based on Carter, Beatenbough, King, Gatling, and Kotani.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We find unpersuasive Mr. Pollock’s testimony that we limit the level of ordinary skill to “refrigerated display cases” because defining the level of skill as an engineer with experience “working with refrigerated display cases” does not relate to the technology disclosed and claimed in the ’181 patent, which is controlling condensation and conserving energy. E.g., Ex. 1001, 2:17–21 (“The invention is proactive in preventing condensation temperature at frame and door surfaces is reached. Power is then cycled off at a set point above dew point to save energy.” (emphases added)). An electrical engineer with a bachelor’s degree and 2 years of experience focused on lighting systems for refrigerated display cases would have “experience working with refrigerated display cases,” and thus meet Patent Owner’s proposed level of skill. Such a person, however, would not be experienced in controlling condensation, dew point sensor positioning, and condensation algorithm design, which is the focus of the disclosed and claimed invention, and which Mr. Pollock states “materially affect performance, energy use, and reliability” in controlling condensation in a refrigerated display case. Ex. 2014 ¶ 11. We also note that Mr. Pollock’s qualifications are a “B.S. in Mechanical Engineering, cum laude, from Drexel University (1998), with focus on thermal and mechanical systems, thermodynamics, and HVAC&R (Heating, Ventilation, Air Conditioning & Refrigeration).” Ex. 2014 ¶ 3. Accordingly, based on the prior art, the sophistication of the disclosed technology in the ’181 patent, finding Mr. Pollock’s testimony on this issue too general, and crediting Dr. Henze’s testimony with substantial probative weight, we adopt Petitioner’s definition of the level of ordinary skill. We modify it to state that more academic training will offset less experience, and more experience will offset less academic training, as did Dr. Henze (Ex. 1003 ¶ 31). Thus, in this proceeding a person of ordinary skill would have a bachelor’s degree in mechanical engineering, electrical engineering, or a comparable field and at least three to five years of professional experience working with heating, ventilating, air conditioning, and refrigeration” slip op. at 16

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “The fundamental role of expert testimony is that “the expert’s scientific, technical, or other specialized knowledge will help the trier of fact [here, the Board] to understand the evidence or to determine a fact in issue.” Fed. R. Evid. 702(a). The testimony must be “based on sufficient facts or data” (id. at 702(b)); must be “the product of reliable principles and methods” (id. at 702(c)); and must reflect “a reliable application of the principles and methods to the facts of the case” (id. at 702(d)). We determine, based on the record before us, that Dr. Henze’s Declaration testimony meets these requirements. He provides, as required, the facts and data to support his testimony. Indeed, Federal Rule of Evidence 702 and the Code of Federal Regulations require him to do so. See 37 C.F.R. § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”). Expert testimony that “merely repeats, verbatim, the conclusory assertion for which it is offered to support,” or that “does not cite to any additional supporting evidence or provide any technical reasoning to support” the testimony is entitled to little weight. Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9, 15 (PTAB Aug. 24, 2022) (Precedential) (emphasis added).” slip op. at 31

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

    “The Board is required to construe ‘only those terms that . . . are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). Here, whether the preamble is or is not limiting is not argued by Petitioner. Moreover, whether the preamble is or is not limiting is not necessary to resolve this controversy because it would not affect the outcome of this case. 2. “Adapted for” Patent Owner asserts that the term “adapted for” in independent claims 1 and 8 has its “plain and ordinary meaning.” Id. at 14. Patent Owner does not, however, provide us with a specific identification of what is the “plain and ordinary” meaning. Petitioner does not address a specific construction for this term. Thus, it is not in controversy and we need not specifically construe this term. slip op. at 21

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “only when it is analogous to the claimed invention. In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004) (“References within the statutory terms of 35 U.S.C. § 102 qualify as prior art for an obviousness determination only when analogous to the claimed invention.” (citing In re Clay, 966 F.2d 656, 658 (Fed. Cir. 1992))). The Federal Circuit has laid out two separate tests to determine whether a reference is analogous art to the claimed invention, i.e., whether one of ordinary skill in the art would even look to the teachings of that reference. In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004). These two tests are: “(1) whether the art is from the same field of [the inventor’s] endeavor” and “(2) if the reference is not within the field of the inventor’s endeavor, whether the reference still is reasonably pertinent to the particular problem with which the inventor is involved.” Id.; see also Netflix, Inc. v. DivX, LLC, 80 F.4th 1352, 1359 (Fed. Cir. 2023) (“Importantly, ‘the scope of any field of endeavor will vary with the factual description of each invention.’ Unlike the reasonable-pertinence test, the field-of-endeavor test does not look to the problem that the patent purports to address. It is enough that the prior art reference falls within the relevant field of endeavor of the patent-in-suit.”) (citations omitted); Unwired Planet, LLC v. Google Inc., 841 F.3d 995, 1001 (Fed. Cir. 2016) (“To determine if art is analogous, we look to ‘the purposes of both the invention and the prior art.’ If a reference disclosure and the claimed invention have a same purpose, the reference” slip op. at 42

  Patent outcomesUS 7,207,181 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,207,181
• Shenzhen Root Technology Co., Ltd. v. Willow Blossom Holdco LimitedAll claims unpatentable
  PTAB · Jul 30, 2026 · IPR2025-00560 · APJ Barry L Grossman · IPR · Final written decision

  Claims 1–29 are unpatentable under each asserted obviousness ground, including Chang and Fang, because Petitioner proved unpatentability by a preponderance of the evidence.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Additionally, we note that Patent Owner did not cross-examine Mr. Ryan Bauer, who provided a detailed, 169-page expert report providing, on behalf of Petitioner, his opinions about the issues in this proceeding. See Exhibit 1003. Mr. Bauer’s testimonial evidence in this proceeding remains unrebutted.” slip op. at 3

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that a person of ordinary skill in the art would have had “bachelor’s degree in mechanical engineering or a similar field and at least two years of experience designing human breast pump equipment. More education could substitute for experience and vice versa.” Pet. 8 (citing Ex. 1003 ¶¶ 15–18). Mr. Bauer’s Declaration testimony states he considered some of the factors listed above. Ex. 1003 ¶ 17. Mr. Bauer testifies that based on his background and experience, in his opinion, the level of ordinary skill is as stated by Petitioner. Id. at 18. Based on the prior art, the sophistication of the disclosed technology in the ’381 patent, and Mr. Bauer’s undisputed testimony, we adopt Petitioner’s definition of the level of ordinary skill.” slip op. at 17

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

    “Petitioner asserts that the Examiner construed the term “self- contained, in-bra wearable device” to mean “complete, or having all that is needed, in itself’ and is capable of being worn in a bra.” Pet. 8 (citing Ex. 1005, 2290).14 According to Petitioner, “[Patent Owner] did not dispute this construction, and Petitioner applies it herein.” Id. Petitioner contends that all other terms “should receive their plain and ordinary meaning.” Id. We do not perceive the need to construe any claim limitation. Claims must be construed “only to the extent necessary to resolve the controversy.” AstraZeneca AB v. Mylan Pharms. Inc., 19 F.4th 1325, 1345 (Fed. Cir. 2021) (quoting Vivid Techs., Inc. v. American Science & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999); see also Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe the claim preambles here where the construction is not ‘material to the [obviousness] dispute.’” (citations omitted)).” slip op. at 17

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

    “(3) 1[a][1] a diaphragm configured to prevent milk from reaching an air pump by forming a seal around its outer edge; Petitioner relies on Fang for the disclosure of a diaphragm, as stated in this clause. Pet. 25–26. Petitioner asserts the proposed combination of elements suggest a breast pump device that would have used a diaphragm pump including first and second diaphragm housing components and an elastic diaphragm, “in accordance with Fang’s suggestions.” Id. at 25. As also asserted by Petitioner, Fang discloses that flexible diaphragm 7 (i.e., a membrane) is configured to prevent milk from reaching the pump. Id. at 26 (citing Ex. 1009 ¶ 19 (“The elastic diaphragm 7 is used to prevent milk from flowing into the air pump main unit 8.”). Mr. Bauer testifies: The flexible diaphragm [diaphragm 7 in Fang] forms a watertight and airtight seal around its outer edge. In doing so, the diaphragm prevents the passage of milk from reaching the air pump and facilitates generation of negative pressure during operation. Fang also explains that the elastic diaphragm 7 deforms away from the nipple tunnel when a vacuum is created on a pumping chamber, which then creates negative air pressure in the nipple tunnel when a vacuum is created on a pumping chamber.” slip op. at 28

  Patent outcomesUS 11,813,381 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,813,381
• 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
• 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.