• Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentable
  PTAB · Oct 14, 2026 · IPR2025-00712 · APJ Kevin W Cherry · IPR · Final written decision

  Claims 1, 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 were not shown unpatentable because Walker was not prior art and Kelly did not teach limitations 1[d.i] and 1[d.ii].

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference not prior artPriority date awardedDecided for patent owner

    “b) Walker Priority Date Under Dynamic Drinkware, the Petitioner is required to show that “the provisional application provides support for the claims of the patent or published application.” In re Riggs, 131 F.4th 1377, 1384 (Fed. Cir. 2025). Thus, Petitioner must show that (1) at least one claim of Walker is supported by its provisional (U.S. Provisional Application No. 60/378,289 (the “’289PROV”) and (2) the specific subject matter relied upon as prior art is supported by the ’289PROV. Id. Petitioner does provide a detailed explanation about how the ’289PROV supports claim 1 of Walker. See Reply 5–10. However, as Patent Owner argues, Petitioner fails to show that the ’298PROV provides support for the specific subject matter relied on in Walker. See Sur-Reply 3–9. Petitioner only explains how the ’298PROV discloses “predetermined criteria” but does not provide any other explanation for how the other subject matter relied on in Walker is supported by the ’298PROV. Thus, we find that Petitioner has failed to show that Walker is entitled a priority date before May 1, 2003. See Riggs, 131 F.3d at 1384 (noting while “a prior art patent or published application cannot be accorded the benefit of its provisional application’s filing date absent a showing that the provisional application provides support for the claims of the patent or published application,” the challenger must also show that “the specific portions of the patent specification identified and relied on” to demonstrate purported invalidity have written description support).” slip op. at 25

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

    “evidence that Kelly teaches limitations 1[d.i] and 1[d.ii]. As Patent Owner persuasively argues, “the recorded information regarding particular game play events” of limitations 1[d.i] and 1[d.ii] refers to “memory to . . . record game play information regarding particular game play events” in limitation 1[b.ii], but Petitioner does not map “the game play events” identified in limitation 1[b.ii] to limitations 1[d.i] and 1[d.ii]. In its Reply, Petitioner does not dispute Patent Owner’s assertion, but largely reiterates its arguments from the Petition. However, none of these arguments or evidence demonstrates that the “game play events” in limitations 1[d.i] and 1[d.ii] are same the “game play events” that are allegedly stored in limitation 1[b.ii]. Even if we accept Petitioner’s contention that it was not identifying button presses or the “game identifier,” but rather includes “game states and game events in the game process,” Petitioner provides no evidence or even arguments that what it has identified here relates to what it has identified for limitations 1[d.i] and 1[d.ii]. See Pet. 29–33 (citing Ex. 1005, 25:23–24, 26:59–27:1, 32:27–33, 37:1–10, 38:66–39:7 40:33–45, 56:49–51, 57:27–33). For these reasons, Petitioner has failed to show by a preponderance of the evidence that Kelly teaches or suggests limitations 1[d.i] and 1[d.ii]. Accordingly, we find that Petitioner has failed to show that claim 1 would have been obvious over Kelly. 2. Claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 Claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 all depend (either directly or indirectly) from claim 1. See PO Resp. 16 (explaining that the arguments for independent claim 1 also apply to the dependent claims inherent the deficiencies asserted with respect to the independent claims). We find Patent Owner’s arguments availing, as explained above. Accordingly, we find that Petitioner has failed to show by a preponderance of the evidence that claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 would have been obvious over Kelly.” slip op. at 44

  • Expert testimonyPetitioner expert creditedDecided for patent owner

    “programmable variable parameter sets to achieve the mandated parameters,” we find that Patent Owner sufficiently explained “the notes from the 12/4/02 meeting reflect that the inventors proposed that their invention could raise the global payout percentage ‘to 75%’ – a mandated parameter – by ‘increas[ing] % of wins by the level 2,’ i.e., a secondary game level – a variable parameter.” See PO Resp. 28–32, 37, 38; Ex. 2016; Ex. 2017 ¶¶ 23–24, 41–42; Ex. 2012 ¶ 90, 63–64. Indeed, Mr. Crevelt confirmed that that a POSITA would unequivocally regard disclosure of “win rate[s]” and “global payout percentage[s]” as disclosing the claimed “mandated parameters” that are achieved by utilizing variable parameters. See Ex. 2020, 15:7–18:4, 19:14–21:16, 24:25–25:15 (global payout percentages), 21:18– 24:24 (win rates).” slip op. at 33

  Patent outcomesUS 11,393,279 not shown unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,393,279
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentable
  PTAB · Oct 14, 2026 · IPR2025-00708 · APJ Kevin W Cherry · IPR · Final written decision

  Claims 1, 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 were not shown unpatentable over Kelly or Walker and Schneier.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art (“POSITA”). In assessing the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (quoting Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “[O]ne or more factors may predominate.” Id. Based on the testimony of Mr. Crevelt, we determine that a person of ordinary skill in the art would have had at least a bachelor’s degree in computer science or computer engineering, with at least three years of experience in game development. Pet. 14 (citing Ex. 1003 ¶¶ 62–65). Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Id. We determine that the level of ordinary skill in the art adopted above is consistent with the level of technical understanding and competence reflected in the ’336 patent Specification and the asserted prior art references, based on our review of the record. Patent Owner states that “[f]or the purposes of this response, Patent Owner does not dispute Petitioners’ proposed level of skill, and under any level of skill a POSITA would not understand the asserted Grounds to raise any unpatentability issue,” and “this POR and supporting declarations apply Petitioner’s proposed level of skill.” PO Resp. 8. Thus, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’336 patent and the asserted prior art, and we apply it in our obviousness analysis below.” slip op. at 11

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

    “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)). We determine that no terms require express construction to resolve the parties’ disputes in this case. See id. slip op. at 13

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

    “b) Walker Priority Date Under Dynamic Drinkware, the Petitioner is required to show that “the provisional application provides support for the claims of the patent or published application.” In re Riggs, 131 F.4th 1377, 1384 (Fed. Cir. 2025). Thus, Petitioner must show that (1) at least one claim of Walker is supported by its provisional (U.S. Provisional Application No. 60/378,289 (the “’289PROV”) and (2) the specific subject matter relied upon as prior art is supported by the ’289PROV. Id. Petitioner does provide a detailed explanation about how the ’289PROV supports claim 1 of Walker. See Reply 6–12. However, as Patent Owner argues, Petitioner fails to show that the ’298PROV provides support for the specific subject matter relied on in Walker. See Sur-Reply 3–8. Petitioner only explains how the ’298PROV discloses “predetermined criteria” but does not provide any other explanation for how the other subject matter relied on in Walker is supported by the ’298PROV. Thus, we find that Petitioner has failed to show that Walker is entitled a priority date before May 1, 2003. See Riggs, 131 F.3d at 1384 (noting while “a prior art patent or published application cannot be accorded the benefit of its provisional application’s filing date absent a showing that the provisional application provides support for the claims of the patent or published application,” the challenger must also show that “the specific portions of the patent specification identified and relied on” to demonstrate purported invalidity have written description support).” slip op. at 24

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

    “We find that Petitioner has failed to show by a preponderance of the evidence that Kelly teaches limitation 1[f]. As Patent Owner persuasively argues, “the game play events” of limitation 1[f] refers to “game play events” in limitation 1[d], but Petitioner does not map “the game play events” identified in limitation 1[d] to limitation 1[f]. In its Reply, Petitioner does not dispute Patent Owner’s assertion, but merely reiterates its arguments from the Petition. See Reply 23–24, 26. However, none of these arguments or evidence demonstrates that the “game play events” in limitation 1[f] are same the “game play events” that are allegedly stored in limitation 1[d]. Even if we accept Petitioner’s contention that it was not identifying button presses, but rather includes “game states and game events in the game process,” Petitioner provides no evidence or even arguments that what it has identified here relates to what it has identified for limitation 1[f]. See Pet. 25–26 (citing Ex. 1005, 25:23–24, 32:27–33, 40:33–45, 56:49–51). For these reasons, Petitioner has failed to show by a preponderance of the evidence that Kelly teaches or suggests limitation 1[f]. Accordingly, we find that Petitioner has failed to show that claim 1 would have been obvious over Kelly. 2. Claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 Claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 all depend from claim 1. See PO Resp. 16 (explaining that the arguments for independent claim 1 also apply to the dependent claims inherent the deficiencies asserted with respect to the independent claims). We find Patent Owner’s arguments availing, as explained above. Accordingly, we find that Petitioner has failed to show by a preponderance of the evidence that claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 would have been obvious over Kelly.” slip op. at 40

  Patent outcomesUS 8,529,336 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,529,336
• 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
• Axon Enterprise, Inc. / Dedrone Holdings, Inc. v. Airspace Defense, Inc.Other
  PTAB · Oct 6, 2026 · IPR2025-00525 · APJ Scott C Moore · IPR · Final written decision

  Original claim 21 was canceled; the Board denied substitute claim 22 for new matter and held it obvious under §103 based on six combinations.

  RulingsFinal written decision

  • 112 supportMotion to amend, deniedDenied

    “First, Patent Owner has not shown possession of the disputed feature of a “radio communication module [that] is configured to utilize a secure identifier, the secure identifier comprising a specified excitation.” In the ’406 application, the term “excitation” is used exclusively to refer to a light beam signal. See Ex. 2015, 7:8–13, 9:8–10, 23:9.2 The ’406 application discloses that an identification box on an aircraft may include both an RF module and a separate light sensor. See Ex. 2015, 7:3–11. But nowhere does the ’406 application describe receiving a light beam (e.g., an excitation) with the RF module of the identification box (as opposed to the light sensor), so as to provide support for proposed substitute claim 22’s recitation of a “radio communication module” configured to utilize “a secure identifier . . . comprising a specified excitation.” We disagree with Patent Owner that it suffices that one of ordinary skill in the art “would recognize that these disclosures are equally applicable to the RF-only embodiments” (Reply 5). “It is not sufficient for purposes of the written description requirement . . . that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997). On this record, and having reviewed the ’959 Patent, the ’153 provisional, and the ’406 application, we find no evidence in those documents that the named inventor was in possession of the concept of a radio communications module “configured to utilize a secure identifier” where “the secure identifier compris[es] a specified excitation.” Second, setting aside the “radio communication module” in proposed substitute claim 22, Patent Owner also has not shown that the named inventor was in possession of the feature of a “secure identifier comprising a specified excitation.” Patent Owner’s argument that the ’406 application describes a light beam directed to a particular aircraft (see Reply 4–5) is 2 The same is true of the ’153 provisional. See Ex. 2016 ¶¶ 29, 34. unavailing. The fact that the properties of a particular light beam indicate that the light beam is intended for a particular aircraft does not demonstrate that the light beam is a “secure identifier,” as we have construed that term. Patent Owner has not identified any disclosure in the ’406 application of a “secure identifier” comprising a light beam, let alone that such light beam can be utilized by a “radio communication module.” The only references to “secure” identifiers in the ’406 application describe radio frequency signals. See Ex. 2015, 2:4–6, 15:21–17:12.3 Having reviewed the ’959 Patent, the ’153 provisional, and the ’406 application, we find no evidence in those documents that the named inventor was in possession of the concept of a “secure identifier comprising a specified excitation.”” slip op. at 15

  • ScopeDecided for patent owner

    “not impermissibly broaden the scope of the claims of the ’959 Patent. As Patent Owner suggests, there were no limitations in original claim 21 on the type of radio signal the radio communication module could receive, and so it follows that proposed substitute claim 22 does not now encompass receiving a broader set of radio signals. We see no basis for Petitioner’s argument that the past tense verb “received” limited original claim 21 to “signals of a compatible ‘type’ and ‘range.’” Opp. 7. Moreover, the claim language (with the proposed deletion shown double brackets) provides that “the radio communication module is configured to receive a [[received]] radio signal.” Any radio signal that the radio communications module receives would necessarily be a “received” radio signal. Thus, deleting the redundant word “received” does not enlarge the scope of this claim limitation. We also are not persuaded by Petitioner’s suggestion that removing the term “received” broadens original claim 21 by deleting a requirement that the radio signal have already been previously received by the claimed device. See Sur-reply 9. Original claim 21 simply recited, using redundant language, that “the radio communication module is configured to receive a received radio signal.” Ex. 1001, 18:5–7. The most natural reading of this language is that the phrase “received radio signal” is just a description of a radio signal that is received by the recited radio communications module. Petitioner has cited no persuasive evidence that one of ordinary skill in the art would have counterintuitively interpreted this language to impose an additional requirement that the “received radio signal” must have been received twice—a first time by some other component of the device, and a second time by the recited radio communication module. Accordingly, we determine that the proposed amendment does not improperly broaden claim scope.” slip op. at 10

  • Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteNot shown unpatentable

    “572 U.S. 898 (2014). See Memorandum: Approach to Indefiniteness Under 35 U.S.C. § 112 in AIA Post-Grant Proceedings (Jan. 6, 2021).4 Under Nautilus, a claim is indefinite if fails to “inform those skilled in the art about the scope of the invention with reasonable certainty.” 572 U.S. at 910. We agree with Patent Owner that neither of the identified terms are indefinite. Regarding the term “low-altitude aircraft,” we determine the Specification provides a sufficient basis for understanding the scope and meaning of this term with reasonable certainty. The U.S. Court of Appeals for Federal Circuit has explained that, when a term of degree is recited in a claim, it is necessary “to determine whether the patent’s specification provides some standard for measuring that degree.” See Seattle Box Co. v. Indus. Crating & Packing, Inc., 731 F.2d 818, 826 (Fed. Cir. 1984); see also Datamize, LLC v. Plumtree Software, Inc., 417 F.3d 1342, 1350 (Fed. Cir. 2005) (“Some objective standard must be provided in order to allow the public to determine the scope of the claimed invention.”). Here, the Specification describes the related art as including “small UASs (e.g., aircrafts up to 25 pounds flying up to 500 ft of the low altitude airspace).” Ex. 1001, 1:50–52. One of ordinary skill in the art would understand from the Specification that the cited disclosure provides an objective standard for determining the scope of a low-altitude aircraft as one that is designed to fly up to a maximum altitude of about 500 feet.” slip op. at 20

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In our Institution Decision, we adopted Petitioner’s proposal that one of ordinary skill in the art would have had the following qualifications: [E]ither (1) a Bachelor of Science in Mechanical Engineering, Electrical Engineering, Aerospace engineering, or an equivalent field, as well as at least 2 years of academic or industry experience in the aerospace, avionics, telecommunications, or electronic device manufacturing industry, or (2) at least four years of industry experience in any of the above industries. Paper 13, 5 (citing Pet. 21). Patent Owner has not disputed this formulation; thus, we adopt it for purposes of this Decision. See Paper 13, 10–11 n. 8.” slip op. at 23

  § 103 obviousness§ 112 disclosurecites Graham · Nautilus
  Patents in suitUS 10,713,959
• Merck Sharp & Dohme LLC v. Halozyme, Inc.All claims unpatentable
  PTAB · Oct 2, 2026 · PGR2025-00046 · APJ Jeffrey N Fredman · PGR · Final written decision

  Claims 1, 2, 5, and 7–33 are unpatentable because the Petitioner proved lack of written description and lack of enablement; the Board did not find the claims obvious.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

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

    “E. Ground III - Obviousness 1. Principles of Law The Supreme Court in KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398” slip op. at 117

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

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

  RulingsFinal written decision

  • Skill levelOther

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

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

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

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

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

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

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

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

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

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “structural connections and three-dimensional modeling Patent Owner’s experts attempt to make (see, e.g., Ex. 2070 ¶¶ 126–212, 297–342; Ex. 2068 ¶¶ 123–125, 245, 294–313, 318) do not appear in the written description itself. To the extent the experts disagree on this point, we credit the testimony of Petitioner’s experts over that of Patent Owner’s. See Ex. 1133 ¶¶ 111–230 (identifying problems with the approaches proposed by Patent Owner’s experts). For these reasons, we find that a preponderance of the evidence of record better supports a finding that in the 2011–2012 timeframe, it would have been unpredictable to identify which multiple mutants retained hyaluronidase activity, even with the single substitution data provided by the ’652 patent.” slip op. at 58

  • Skill levelOther

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

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Decided for petitioner

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

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

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

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

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

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

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

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

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

  • BurdenNot shown unpatentable

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

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

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

  Patent outcomesUS 11,959,109 unpatentable
  Claim construction§ 102 anticipation§ 112 disclosure
  Patents in suitUS 11,959,109
• 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

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.