• 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
• 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
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Fendgo, LLCNo claims unpatentable
  PTAB · Apr 30, 2025 · IPR2024-00114 · APJ Jon M Jurgovan · IPR · Final written decision

  Claims 1–8 were not shown unpatentable because DiPerna964 and Strack do not teach or suggest the panic button readying itself to perform the claimed functions.

  RulingsFinal written decision

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

    “After review of the ’404 patent’s description, we find no disclosure that pressing the panic button together with another button causes the panic button to ready itself to perform functions (1) and (2) as recited in limitation 1[d]. The closest descriptions we find to limitation 1[d] are that the safety switch readies the panic button to contact 911 (Ex. 1001, 6:59–62), that the panic button may be activated by pressing the panic button with another button (id., 3:59–67, and that the panic button may start a speech recognition process that can trigger the device (id., 7:61–62). Consequently, claim 1 is itself the best source for determining what the claim language means. We determine that the ordinary and customary meaning of the “ready itself” feature of claim 1 is that the panic button “prepares itself to be triggered to perform the panic button functions (1) and (2).” Since the intrinsic evidence is sufficiently clear to discern the meaning of the “ready itself” limitation, we do not resort to extrinsic evidence. See Phillips, 415 F.3d at 1317 (explaining that extrinsic evidence is less significant than intrinsic evidence); Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1287 (Fed. Cir. 2021) (Court of Appeals gives primacy to intrinsic evidence and resorts to extrinsic evidence only if consistent with intrinsic evidence); Sequoia Tech., LLC v. Dell, Inc., 66 F.4th 1317, 1324 (Fed. Cir. 2023) (Court of Appeals stating that its “decision rests solely on the intrinsic evidence”).” slip op. at 9

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “Thus, the ’353 application describes that moving the safety switch into position readies the panic button to contact 911, which is not the same as the panic button being activated to ready itself to perform functions (1) and (2) required by claim 1 of the ’404 patent. Patent Owner’s reliance on disclosures elsewhere in the ’353 application is unavailing. PO Resp. 5–8 (citing Ex. 1006, 15, 17, 19–21, 23, 25); PO Sur-Reply 2–3 (citing Ex. 1006, 15, 17, 19–20, 24–25)). For example, while the ’353 application does mention voice activation with a codeword and activation by depressing of the panic button together with another button (see, e.g., Ex. 1006, 17, 21, 24–25), it does not mention that depressing the panic button together with another button causes the panic button to ready itself to perform recited functions (1) and (2). The application explains that “[t]he [panic] button can send a signal to a controller inside the device to activate [the code word activation] process” and “[t]he [panic] button can start the speech recognition process in one embodiment, to trigger the device.” Ex. 1006, 25. But that describes readying the device for activation by the code word, not readying the button to perform the recited functions. The ’353 application also mentions the word “ready” in relation to using a self-defense mechanism such as pepper spray, which does not appear to be related the readying of the panic button recited in claim 1. Ex. 1006, 15, 19–20. Petitioner has thus met its burden to demonstrate that claims 1–8 of the ’404 patent lack written description support for a panic button adapted to “ready itself” to perform the recited functions because the limitation is not present in the ’353 application to which the ’404 patent claims priority.3 Pet. 8–10. The burden of production thus shifted to Patent Owner to demonstrate that the ’353 application has written description support for limitation 1[d], which it has not done on this record. PO Resp. 5–8; PO Sur-Reply 2–3.” slip op. at 15

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

    “DiPerna964 discloses a separate “safety” switch that readies the panic button to contact 911 upon being pressed (Ex. 1028 ¶ 41), but there is no mention of pressing the panic button together with another button to cause the panic button to “ready itself” to perform panic button functions (1) dialing a public or private network for an emergency purpose and (2) activating the transmitting unit, as limitations 1[d] and 1[e] require. DiPerna964 mentions pressing two buttons together to activate the panic button (see, e.g., Ex. 1028 ¶¶ 17, 23–25, 27), but not to “ready itself” to perform recited functions (1) and (2). Petitioner relies on Strack’s triggering the collection of audio, video, and location data for transmission to a remote location as equivalent to a panic button readying itself to, when activated, perform the panic button functions (1) dialing a public or private network for an emergency purpose and (2) activating the transmitting unit. Pet. 15–17 (citing Ex. 1002 ¶¶ 76–88). We do not agree with Petitioner’s contention because Petitioner fails to explain how Strack’s button press that collects and then transmits audio, video, and location data would ready the panic button to perform recited functions (1) and (2). It appears that Strack’s button press readies the device, not the button, to perform the functions. As neither DiPerna964 nor Strack nor their combination teach or suggest limitations 1[d] and 1[e], we determine it is unnecessary to proceed further with the obviousness analysis. PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1194 (Fed. Cir. 2014) (citing Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1164 (Fed.Cir.2006) (stating that we consider motivation to combine and reasonable expectation of success only “if all the elements of an invention are found in a combination of prior art references”)).” slip op. at 21

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s proposed level of skill in the art, which appears consistent with the educational level, technology, problems and solutions identified in the ’404 patent and prior art references asserted by Petitioner. Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill). Accordingly, we apply Petitioner’s proposed level in this Decision.” slip op. at 18

  Patent outcomesUS 11,265,404 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,265,404
• Precision Planting LLC v. Maschio Gaspardo S.P.A.No claims unpatentable
  PTAB · Mar 21, 2025 · IPR2024-00008 · APJ Benjamin D M Wood · IPR · Final written decision

  Claims 1–5, 7–14, and 16 were not shown unpatentable because the asserted anticipation and obviousness grounds failed to establish the claimed thrust-bearing element and its required location.

  RulingsFinal written decision

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for patent owner

    “We determine that the evidence of record overcomes the presumption that § 112, para. 6 does not apply because “thrust-bearing element” does not recite sufficiently definite structure in this case. See, e.g., Pet. 22 (the term is not used here according to its common meaning). First, the word “element” is a “[g]eneric term[]” or “verbal construct[]” often “used in a claim in a manner that is tantamount to using the word ‘means’” because it does not “connote sufficiently definite structure.” Williamson, 792 F.3d at 1350. We find nothing in the ’121 patent or elsewhere in the record suggesting that “element” in the term “thrust-bearing element” should be considered other than a generic placeholder term. Second, although the term “thrust bearing” may connote certain structure, “thrust-bearing element” does not. A “thrust bearing” is “a well-known term of art in engineering and is ‘a bearing which sustains axial loads and prevents axial movement of a loaded shaft.’” Ex. 1003 ¶ 46 (citing Ex. 1017, 2147). “The balls of traditional thrust bearings are positioned inline with the axial force, as thrust bearings are designed specifically to transmit axial load.” Id. Here, however, “thrust-bearing” is hyphenated, and is therefore a phrasal adjective modifying “element” rather than the noun phrase “thrust bearing.”8 Further, there are “substantial differences”” slip op. at 15

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Term construed board ownDecided for patent owner

    “We largely agree with Petitioner. “[S]tructure disclosed in the specification is ‘corresponding’ structure only if the specification or prosecution history clearly links or associates that structure to the function recited in the claim.” B. Braun Med. Inc. v. Abbott Labs., 124 F.3d 1419, 1424 (Fed.Cir.1997). The Specification of the ’121 patent “clearly links or associates” two components with the function of bearing axial thrust from the sowing disc: shaft 27 with flanging 30, and thrust-bearing plate 31. Ex. 1001, 3:25–35. Thrust-bearing plate 31 is expressly described as “bear[ing] on that surface of the disc which faces seal 24 . . . in order to withstand at least some of the axial load produced by the disc 16 on the seal 24. Ex. 1001, 3:28–31. Rotatably-mounted shaft 27 with flanging 30 is “fixed” to thrust-bearing plate 31 and therefore bears the axial load from the disc via the thrust-bearing plate. Id. at 3:25–28.10 10 Drive element 32 is described as part of thrust-bearing element 26 and permits thrust-bearing element 26 to be driven in rotation with sowing disc 16. Ex. 1001, 3:36–40. It is not described as bearing any axial load, however. Further, it is not necessary for the thrust-bearing element to rotate with the sowing disc for that element to bear axial load from the sowing disc. See id. at 3:58–59 (“Provision is also made for the thrust-bearing element 26 to be made idle and not driven in rotation by the [drive] shaft 20.”). Ultimately, however, whether drive element 32 is properly considered as part of the corresponding structure is not relevant to the outcome of this case. We disagree with Patent Owner that bearings 28 and seat 29 should be considered corresponding structure. The Specification does not associate these structures with any axial load-bearing function. Instead, bearings 28 and seat 29 are described as the means by which, and the location in which, shaft 27 is rotatably mounted. Ex. 1001, 3:25–27. Regardless, whether or not bearings 28 and seat 29 are considered corresponding structure does not affect the outcome of this case. In summary, we construe “thrust-bearing element” as a means-plus- function claim term under 35 U.S.C. § 112, para. 6. Its recited function is to bear thrust, or more specifically to “withstand at least some of the axial load produced by the disc on the seal.” The structure described in the Specification as corresponding to this function is shaft 27 with flanging 30, and thrust-bearing plate 31. We construe the limitation as directed to this structure, and equivalent structures.” slip op. at 21

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

    “The question is not whether the patentee disclaimed coverage over structures in which the thrust-bearing element is not located entirely in the movable portion of the housing. Instead, we must simply ascertain what the patentee meant by “supported rotatably in the movable portion.” To answer this question, we look to the Specification, which “is the single best guide to the meaning of a disputed term.” Phillips, 415 F.3d at 1315. “The construction that stays true to the claim language and most naturally aligns with the patent’s description of the invention will be, in the end, the correct construction.” Id. at 1316. Here, it is undisputed that in the sole embodiment described by the ’121 patent, the thrust-bearing element is supported by and entirely within the movable portion of the housing. Ex. 1001, Figs. 1, 2; Pet Post-Hearing Resp. 1; PO Post-Hearing Resp. 2. Construing “in the movable portion” to require the thrust-bearing element to be entirely within the movable portion both “stays true to the claim language and most naturally aligns” with the sole disclosed embodiment. Such a construction does not import the word “entirely” from the sole embodiment into the claims because the construction “arises from the claim language itself.” See SharkNinja Operating LLC v. iRobot Corp., 2024 WL 1132219, *2–*3 (Fed. Cir. 2024) (construing “primary brush assembly disposed within the round housing perimeter” to require that the primary brush assembly be “entirely within” the round housing perimeter is not an improper incorporation of “entirely” from embodiments into the claims because the construction “arises from the claim language itself”). Accordingly, having reviewed the complete record and the parties’ pre- and post-hearing briefing, we determine that “supported rotatably in the movable portion” means supported rotatably entirely in the space defined by the movable portion.” slip op. at 25

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

    “b. When “Thrust-Bearing Element” is Construed as a Means-Plus-Function Claim Limitation, there is Insufficient Evidence in the Record to Support a Finding that VenHuizen Discloses a Thrust- Bearing Element that is Supported Rotatably in the Movable Portion As noted above, Petitioner contends that VenHuizen’s shaft 55, retaining hub 56, and handle 58 together constitute the claimed thrust-bearing element “under a proper means-plus-function definition.” Pet. Reply 18–19.12 We do not discern sufficient evidence of record or persuasive technical reasoning from Petitioner to support a finding that these elements together are “supported rotatably in the movable portion” of the housing, as claim 1 requires. Ex. 1001, 4:38–39. We construed this limitation to require the thrust-bearing element to be supported rotatably entirely in the space defined by the movable portion (the space defined by VenHuizen’s second housing member 90). Petitioner does not contend, much less show, that these components are supported rotatably entirely in the movable second housing member 90. On the contrary, of the three components constituting VenHuizen’s thrust-bearing element, all of retaining hub 56 and most of shaft 55 are located in the fixed portion of the housing (first housing member 50), not the movable portion 90. See Ex. 1001, Fig. 6. Only handle 58 is ever located in the movable portion (when the fixed and movable portions are joined together). See id. Accordingly, Petitioner has not shown that VenHuizen discloses a thrust-bearing element rotatably supported in the movable portion.” slip op. at 35

  Patent outcomesUS 8,770,121 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 8,770,121
• Orthocision, Inc. v. PTL Opco LLCNo claims unpatentable
  PTAB · Sep 18, 2024 · IPR2023-00625 · APJ Ryan H Flax · IPR · Final written decision

  Claims 1, 2, 9, and 10 were not shown unpatentable under any asserted § 103 ground because Petitioner did not adequately explain how or why the prior art would be combined.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not specifically address Petitioner’s proposed definition. See generally Resp. Patent Owner’s witness, Dr. Bovinet, uses a slightly different, but not materially so, definition of the ordinarily skilled artisan than Petitioner. See Ex. 2005 ¶ 13. Thus, the parties appear to agree on who the person of ordinary skill in the art would have been in terms of education and field of work experience. We accept and adopt Petitioner’s proposed definition of the person of ordinary skill in the art (or ordinarily skilled artisan), which appears to be consistent with the level of skill in the art reflected in the prior art of record and the disclosure of the ’129 patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“the prior art itself [may] reflect[]” evidence of the ordinary level of skill in the art) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). B.” slip op. at 13

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

    “3. Summary on Claim Construction We maintain our earlier constructions of “open tip” and “releasing means . . . .” See DI 16–24. We determine that no other express construction of any claim term is necessary for purposes of rendering this Decision. See Nidec Motor Corp., 868 F.3d at 1017. Although we maintain here our constructions of “open tip” and “releasing means . . . ,” we do so only for the sake of completeness. These claim constructions, ultimately, are not determinative of the outcome of this proceeding because, regardless of the meaning of any claim term, including these disputed terms, we find that Petitioner fails to adequately explain why any claim would have been obvious under the asserted grounds. We explain this in detail below. C.” slip op. at 29

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

    “Ex. 1001, 6:28–38 (emphasis added). However, the language of claim 1 is very clear on the functionality of the “open tip,” expressly reciting that “the open tip cuts bone tissue away from the sacrum or the ilium.” Id. at 13:19– 20. Thus, the claim language itself provides the required functionality of the “open tip,” and we do not agree with Petitioner that additional functionality relating to where bone tissue might go once cut, as discussed in the Specification, should be read into the claims as a limitation. Patent Owner’s newly proposed interpretation is similar to Petitioner’s in that it requests addition of functionality discussed as an example in the Specification, but not recited in the claim’s expressly recited functional language relating to the “open tip.” We disagree with Patent Owner that the concept of dislodged tissue entering a void defined by the open tip is necessary to understanding the claim element. And, once more, Patent Owner reads too much structure from the written description into the claim language as a limitation because it is not apparent that the recited “open tip” language requires that we further clarify that any interior void defined by the open tip is on the interior of the abrading head, and behind the exterior abrading surfaces, or between interior surfaces of a first pair of opposing sides, as proposed by Patent Owner. “[W]hile it is true that claims are to be interpreted in light of the specification . . . , it does not follow that limitations from the specification may be read into the claims. . . . [T]he claims define the invention.” Sjolund v. Musland, 847 F.2d 1573, 1581–82 (Fed. Cir. 1988).” slip op. at 18

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for patent owner

    “A claim limitation is presumed to invoke 35 U.S.C. § 112(f) (or pre- AIA § 112 ¶ 6) if, as here, it explicitly uses the term “means” and includes functional language; this presumption is overcome if the limitation further includes the structure, material, or acts necessary to perform the recited function. See Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1348 (Fed. Cir. 2015) (en banc). Here, the word “means” is recited, followed by functional language, and the claim recites no structure associated with the means or function. Moreover, the parties agree that this is a means plus function limitation. See Pet. 19–20; Resp. 9. We find “releasing means” is a means plus function limitation and, based on the plain language of the claim, the recited “releasing means” is a part of the also recited “slide hammer assembly,” as the above-quoted claim language defines. Ex. 1001, 13:10–17. Construing a claim term under 35 U.S.C. § 112(f) involves two steps: (1) identifying the claimed function; and then (2) determining what structure, if any, disclosed in the Specification corresponds to the claimed function. Williamson, 792 F.3d at 1351. In conducting this analysis, we may not incorporate structure from the written description beyond that which is necessary to perform the claimed function. See Micro Chemical, Inc. v. Great Plains Chemical Co., 194 F.3d 1250, 1258 (Fed. Cir. 1999).” slip op. at 20

  Patent outcomesUS 11,020,129 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,020,129
• Dr. Reddy’S Laboratories, Inc. v. Genentech, Inc., Hoffman-La Roche AG, And Abbvie Inc.No claims unpatentable
  PTAB · Apr 16, 2024 · IPR2023-00052 · APJ Jeffrey N Fredman · IPR · Final written decision

  The Board held claims 1–4, 8–14, and 18–26 not shown unpatentable because they were entitled to priority before the November 2018 Venclexta Label, which therefore was not prior art.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “We do not discern a substantive difference between the parties’ respective definitions for the level of ordinary skill in the art. Although Petitioner did not expressly recite hematological malignancies, Petitioner did refer to expertise in clinical oncology, which would encompass the blood cancers recited in the claims. Neither party identifies a difference in the analysis or conclusions that would be based on differences in the ordinary skill in the art analysis. Accordingly, we find the parties’ respective definitions to be equivalent and consistent with the level of ordinary skill in the art as reflected by the prior art in this proceeding. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need for testimony is not shown” (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985))).” slip op. at 7

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

    “The parties do not identify any issue relating to the preamble that would impact our analysis. We recognize that Patent Owner is suggesting that Petitioner’s expert, at least, is reading the word “clinical” into the treatment language of claim 1. However, the plain language of the claim 1 preamble states “treating lymphoma or leukemia in a human patient” and is supported by a straightforward definition in the Specification of the ’087 patent, expressly limiting the invention to treatment of human patients. See Ex. 1001, 16:25–38. We therefore find that the preamble terms do not need claim construction because there is no actual dispute suggesting that, for example, claim 1 implicitly recites the term “clinical.” See, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘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 5

  • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)EnabledEntitled to earlier dateDecided for patent owner

    “d. Analysis Considering the Wands factors as a whole, we find that the limited breadth of the claims, presence of several working examples, significant amount of direction and guidance provided by the ’087 patent, predictability in treating blood cancers with Bcl-2 inhibitors like GDC-0199, and high level of skill in the art are balanced against a large quantity of experimentation. Based on our consideration of the entirety of the evidence, we find that a preponderance of the evidence supports the conclusion that undue experimentation would not have been required to make and use the invention commensurate in scope with the claims of the ’087 patent. One underlying theme of Petitioner’s contentions and Petitioner’s expert testimony is the repeated contention that clinical trials were not completed by Patent Owner. See, e.g., Pet. 48 (“venetoclax (GDC-0199) was not FDA-approved”); Ex. 1020 ¶ 193. We find these arguments unpersuasive as we agree with Patent Owner that “[i]t is well established that a patent may be secured, and typically is secured, before the conclusion of clinical trials.” In re Montgomery, 67 F.3d 1375, 1382 (Fed. Cir. 2012). Particularly as to the dependent claims, a preponderance of the evidence of record does not support a finding that undue experimentation would have been required to administer three different doses of GDC-0199 starting with 100 mg, to use multiple daily dosing cycles of one day, to continue until disease progression occurs, or to combine with other treatment compounds. We find that a preponderance of the evidence does not support Petitioner’s position that any of the dependent claims fail to comply with the enablement requirement.” slip op. at 23

  • Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner

    “Applying Rai and Wertheim to the instant facts, we agree with Patent Owner that, factually and legally, in the ’087 patent “the claimed dosages of 100 mg, 200 mg, and/or 400 mg of GDC-0199 are adequately supported.” PO Second Suppl. Brief 2 (citing PO Resp. 11, 27–29; PO Sur-reply 19, 21– 22; Ex. 1001, 24:20–29.) In particular, the ’087 patent describes all three specific dosage values 100 mg, 200 mg, and 400 mg in the context of an escalating drug dosage series and Petitioner points to no persuasive statements in the specification that dispute either the effectiveness or the operability of GDC-0199 at any of these dosages.” slip op. at 32

  Patent outcomesUS 11,110,087 not shown unpatentable
  Claim construction§ 102 anticipation§ 112 disclosure
  Patents in suitUS 11,110,087
• BTC Corporation v. TG Biotech Co., Ltd.No claims unpatentable
  PTAB · Nov 13, 2023 · IPR2022-00998 · APJ Ulrike W Jenks · IPR · Final written decision

  Claims 1–13 were not shown unpatentable under the asserted obviousness grounds; Patent Owner’s motion to strike Exhibit 1038 was granted.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We are not persuaded by Petitioner’s contention that we should disregard Dr. Naumovski’s testimony because she may have taken a leave of absence from work for a couple of years. The record supports that Dr. Naumovski not only meets the requirements of the person of ordinary skill in the art, but also appears to have relevant knowledge with respect to Gynostemma pentaphylum (“GP”) saponins. See Ex. 2015 (Appendix A). related field, and at least two years of experience using techniques for extraction and characterization of plant-based materials.” PO Resp. 11 (citing Ex. 2015 ¶ 74). Because there are more than 400 species of plants that contain saponins, Patent Owner disagrees that a person of ordinary skill in the art would be familiar with the structure and utility of saponins. Id. The level of skill in the art is a reference point for gauging what would have been obvious based on the reference disclosures. See Okajima, 261 F.3d at 1355. In other words, the lens of the level of ordinary skill in the art does not change a prior art’s disclosure, though it may change one’s understanding of what is disclosed. Patent Owner, however, does not explain how its definition provides a reference point that would meaningfully alter the Petition’s assertions of obviousness. For purposes of this decision, we analyze the asserted prior art with respect to the level of skill set forth by Petitioner, but there would be no difference in the outcome of this Decision if we were to apply the level of skill in the art set forth by Patent Owner. C.” slip op. at 13

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “during the full trial, we determine that Petitioner has not shown by a preponderance of the evidence that applying the methods of Kim 460 to the G. pentaphyllum starting material of Razmovski necessarily results in the damulin levels as claimed. We agree with Dr. Naumovski’s explanation that the use of an impure damulin B standard containing a double peak renders the results as shown in Exhibit 1013 unreliable. Ex. 2015 ¶¶ 141–143, 162–173; see Ex. 2007. Dr. Naumovski further explains that the use of an impure standard would require the application of a correction factor, but this correction factor would need to be reassessed as the purity of the standard decreases over time. See Ex. 2015 ¶ 166. As Dr. Naumovski explains that applying a correction factor to the linear regression would result in a shallower slope. Ex. 2015 ¶ 165 (citing 2006, 71:12–73:5; 99:2–9). “Reducing the calibration curve slope increases the amount of damulin B calculated from the experimental extracts.” Ex. 2015 ¶ 165. However, in the Experimental Report-1 the same correction factor for the damulin B standard was used to” slip op. at 41

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

    “Petitioner requests construction of the terms “an effective amount for improving or treating the metabolic syndrome,” which is found in claims 11–13, as meaning “an amount that produces any measurable amount of improvement in the metabolic syndrome” (Pet. 13–15 (citing Ex. 1003 ¶ 91)) and “[a] pharmaceutical composition for improving and treating a metabolic syndrome, comprising at least one of at least 0.7% damulin A and at least 0.5% damulin B . . . and a pharmacologically acceptable carrier or excipient,” which is found in claim 8, as meaning “a pharmaceutical composition that includes an extract with 0.7% and 0.5% of damulin A and damulin B[, respectively,] along with a carrier or excipient” (id. at 15–16 (citing Ex. 1002, 64–65, 251–52, 280; Ex. 1001, 12:15–67, Table 2)). Patent Owner argues that “constructions are not necessary.” PO Resp. 11–12. We agree with Patent Owner and determine that it is not necessary for purposes of this Decision to construe any claim terms. See Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only terms” slip op. at 15

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

    “Obviousness does not require absolute predictability of success . . . all that is required is a reasonable expectation of success.” In re Droge, 695 F.3d 1334, 1338 (Fed. Cir. 2012) (quoting In re Kubin, 561 F.3d 1351, 1360 (Fed. Cir. 2009) (citing In re O’Farrell, 853 F.2d 894, 903–04 (Fed.Cir.1988)); Intelligent Bio-Systems, Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359 (Fed. Cir. 2016) (explaining that the expectation of success issue involves a showing of “a reasonable expectation of achieving what is claimed”) (emphasis added). Here, Petitioner relies on Kim 460 to show that heating ginseng, which contains the ginsenosides Rb1, Rb2, Rc, Rd, Rg3, and Rg5, results in a teaches that ginseng with the higher Rg3 and Rg5 content is 50-fold more potent in their vasodilation studies than the non-treated samples. Razmovski teaches that G. pentaphyllum contains over 100 saponins and eight of those saponins are the same as protoparaxadiol-type ginsenosides Rb1, Rc, Rb3, Rd, F2, Rg3, malonyl-Rb1, and malonyl-Rd that are found in P. ginseng. Ex. 1007, 4. Knowing that G. pentaphyllum also contains ginsenosides Rb1, Rb2, Rc, Rd, Rg3, and Rg5, we find Petitioner’s conclusion that heating a G. pentaphyllum extract that contains these ginsenosides would similarly increase the ginsenoside levels of Rg3 and Rg5 is a reasonable inference from the cited references. Based on the teachings in Kim 460, we agree with Petitioner that it would have been reasonable to expect that the same source material, although derived from a different plant, would behave similarly to heat treatment. See Pet. 24. Because G. pentaphyllum is a less expensive starting material, we also agree with Petitioner that there is sufficient motivation to substitute G. pentaphyllum for ginseng in the methods of Kim 460. slip op. at 29

  Patent outcomesUS 8,357,786 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,357,786

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.