• 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
• Alamar Biosciences, Inc. v. Olink Proteomics ABNo claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01353 · APJ Tawen Chang · IPR · Final written decision

  Claims 1–20 were not shown unpatentable: the asserted obviousness grounds failed, including because Kanan and Neri did not teach selecting the claimed cis-reactive cells.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Accordingly, for purposes of this decision we adopt Petitioner’s proposal of a person of ordinary skill in the art, with the following changes noted in italics below: A person with “an advanced degree, such as a Ph.D., in organic chemistry, molecular biology, biochemistry, or a related field; and about two years of experience in industry and/or laboratory experience relating to small molecules and proteins and would have been familiar with nucleic acid chemistry and conventional hybridization techniques; and (b) access to one or more team members having an advanced degree, such as a Ph.D., in organic chemistry, molecular biology, biochemistry, or a related field; and about two years of experience in industry and/or laboratory experience relating to high throughput screening techniques such as nucleic acid sequencing. A person could also have qualified as a POSA with less formal education and more technical or professional experience.11 We emphasize, however, that our decision would not change if we instead used Patent Owner’s proposed definition of a POSA.” slip op. at 13

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

    “Because the parties have placed the limitation “selecting all cis- reactive cells exhibiting the detectable trace” into controversy, we construe the term below, but only to the extent necessary to resolve the controversy. 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)). For the reasons discussed below, we agree with Patent Owner that the plain and ordinary meaning of this phrase, in light of the language of the claims, the Specification, and the prosecution history of record, requires “selecting all of the [molecular complexes or structures] meeting the defined criteria for [cis-reactive cells (CRCs)] and exhibiting the detectable trace.” Sur-reply 8 (citing Ex. 2008 ¶¶ 94, 98–119). We further agree that cis-reactive cells should be construed to mean “an association of at least two interactor moieties, joined by an associated oligonucleotide.” (PO Resp. 9 (quoting Ex. 1001, 9:35-37)). Accordingly, we determine that, properly construed, the claims require that what is “selected” at step 1(d) — what is differentiated or set apart from other molecular complexes or structures in the reaction mixture at the conclusion of step 1(d) — to be “an association of at least two interactor moieties joined by an associated oligonucleotide” that exhibits the detectable trace.” slip op. at 16

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

    “We agree that Petitioner has not shown that the combination of Kanan and Neri teaches “selecting all cis-reactive cells exhibiting the detectable trace,” as we have construed that phrase above. In particular, we determine that, properly construed, the limitation requires the selection of “all associations of at least two interactor moieties joined by an associated oligonucleotide and exhibiting the detectable trace.” Instead, as described in Kanan, what is “selected” is the molecules of interest joined by bond formation, with only one of the molecules of interest coupled to a nucleic acid moiety. Thus, the selected molecular complex or structure does not comprise two interactors (i.e., two molecules of interest coupled to NAMs). Moreover, to the extent there are two interactors, they are joined by the bond between the molecules of interest rather than an associated oligonucleotide.” slip op. at 35

  • ExcludeMotion to exclude, deniedDenied

    “III. PATENT OWNER’S MOTION TO EXCLUDE EVIDENCE Patent Owner moved to exclude Exhibit 1008, on the ground that it contains settlement statements and that Rule 408 of the Federal Rule of Evidence prohibits Petitioner from using the statements to impeach or contradict Patent Owner. Mot. 5. Because we do not rely in our analysis on this exhibit, we dismiss the Motion to Exclude as moot.” slip op. at 43

  Patent outcomesUS 7,883,848 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,883,848
• Illumina Inc. v. Molecular Loop Innovations LLCNo claims unpatentable
  PTAB · Jan 13, 2026 · IPR2024-00964 · APJ Annette R Reimers · IPR · Final written decision

  Claims 1–8 were not shown unpatentable over either asserted §103 combination because the prior art did not teach the discarding step or establish a reasonable expectation of success.

  RulingsFinal written decision

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

    “specification to interpret the meaning of a claim and importing limitations from the specification into the claim can be a difficult one to apply in practice.” Phillips, 415 F.3d at 1323. “[T]he line between construing terms and importing limitations”, however, “can be discerned with reasonable certainty and predictability if [our] focus remains on understanding how a person of ordinary skill in the art would understand the claim terms.” Id. Ultimately, we construe claim terms to “capture the scope of the actual invention more accurately than either strictly limiting the scope of the claims to the embodiments disclosed in the specification or divorcing the claim language from the specification.” Id. at 1324. Here, we are tasked with resolving the dispute between the parties as to the scope of the source of the claimed cross-over error. See Sur-reply 2. Although claim 1 does not explicitly recite cross-over error is created during cluster amplification, the specification shows otherwise. It repeatedly, consistently, and exclusively describes cross-over errors as arising from the formation of chimeric molecules during the amplification step of the sequencing workflow. See Ex. 1001, Fig. 1, Fig. 2, 4:29–52 (describing “improper molecular overlap via formation of a heteroduplex between patient A’s nucleic acid template and patient B’s nucleic acid template” “[w]hen the amplification process begins”), 5:29–58 (the same), 6:25–44 (the same), 6:64–7:23 (the same).” slip op. at 15

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that a person of skill in the art (“POSA”) “would have had (i) a Ph.D. in molecular biology, genetics, bioinformatics, or a related field and at least two years of experience in high-throughput sequencing technologies or (ii) a Master’s degree in one of the same fields with at least four years of experience in high-throughput sequencing technologies.” Pet. 17 (citing Ex. 1003 ¶¶ 19–20). Patent Owner states that it adopts Petitioner’s proposal for a POSA for purposes of this proceeding. PO Resp. 13 (citing Ex. 2001 ¶¶ 19–22). We adopt Petitioner’s proposed definition of the skill level as it is consistent with the prior art’s demonstration of the level of ordinary skill in the art at the time of the invention. We find both Dr. Spellman and Dr. Adalsteinsson are qualified to opine from the perspective of a POSA, because each has at least ordinary skill in the art. See Ex. 1003 ¶¶ 4–15; Ex. 2001 ¶¶ 4–9.” slip op. at 8

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

    “The reasonable expectation of success requirement refers to the likelihood of success in combining references to meet the limitations of the claimed invention.” Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 9 Because, as explained below, we find Petitioner has not met its burden to show reasonable expectation of success, we do not need to address whether Petitioner has shown sufficient reason to combine the asserted references. 821 F.3d 1359, 1367 (Fed. Cir. 2016); see also Allergan, Inc. v. Apotex Inc., 754 F.3d 952, 966 (Fed. Cir. 2014) (stating that “failure to consider the appropriate scope of the . . . patent’s claimed invention in evaluating the reasonable expectation of success . . . constitutes a legal error”). Here, the claimed invention is a method for reducing template cross-over error. Thus, we must determine whether, in December 2010, an ordinarily skilled artisan would have reasonably expected that the combination of Parameswaran and Gloor would reduce template cross-over error. slip op. at 26

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

    “Thus, on this record, we are persuaded by Patent Owner’s argument that Parameswaran’s “unexpected perfect pairings of unmatched forward and reverse barcodes” are not cross-over error. PO Resp. 31 (citing Ex. 2001 ¶¶ 116–123). In addition, as Petitioner acknowledges, Parameswaran merely “distinguished,” but did not “discard” sequences with mismatches. Pet. 34. Parameswaran states that “[t]he low false-discovery rate for perfect matches strengthens the argument that any sequence with both 5’ and 3’ barcode motifs will be placed with reasonable accuracy into the correct bin.” Ex. 1004, 8. But, because Parameswaran achieved a “remarkably low misassignment rate,” it did not discard, but included any sequence with a matched barcode. Id. Indeed, Parameswaran explains that “[f]or our purposes, all sequences with a match to one of the two expected sequence motifs were considered as true members of the corresponding dataset.” Id. In its Reply, Petitioner emphasizes Parameswaran’s language “[f]or our purposes.” Reply 14 (citing Ex. 1004, 8). According to Petitioner, “[a] POSA would have understood from Parameswaran that chimeric sequences could be kept or discarded, depending on the sequencing ‘purpose.’” Id. (citing Ex. 1054 ¶¶ 79–82). Petitioner is asking us to deem unpatentable a claim based on its reading of “for our purposes,” a broad, undefined statement, to mean something specific—a suggestion to discard perfect unexpected pairings, which Parameswaran explicitly did not do. See Ex. 1004, 8. Petitioner has not presented sufficient evidence and persuasive argument for us to do so.” slip op. at 24

  Patent outcomesUS 11,041,852 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,041,852
• Sarepta Therapeutics, Inc. v. The Trustees Of The University Of PennsylvaniaNo claims unpatentable
  PTAB · Aug 20, 2025 · IPR2024-00580 · APJ Susan L C Mitchell · IPR · Final written decision

  The Board held claim 8 not shown unpatentable under each of three §103 grounds because Petitioner failed to establish motivation to combine the references with a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In addressing the level of ordinary skill in the art, Petitioner contends that a person of ordinary skill in the art (“POSA” or “POSITA”) would have had at least a Ph.D. in biochemistry, molecular biology, or a related field and between one and four years of post-doctoral experience in the field of gene therapy. Alternatively, a POSA would have had at least a Master’s or Bachelor’s Degree in biochemistry, molecular biology, or a related field, with a corresponding number of additional years of experience in the field of gene therapy. Pet. 12 (citing Ex. 1005 ¶¶ 111–115). Patent Owner states that it does not challenge Petitioner’s definition. PO Resp. 10. On this complete record, we accept Petitioner’s proposed definition, as it appears consistent with the level of skill in the art reflected in the prior art of record and the disclosure of the ’274 Patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“the prior art itself [may] reflect[] an appropriate level” as 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)).” slip op. at 11

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

    “Petitioner asserts that the ’274 patent “does not specify a particular program or set of program parameters that should be used to align sequences and calculate percent identity for purposes of determining whether a particular test sequence falls within the scope of the claims.” Pet. 21. Petitioner asserts that it analyzed the percent identity claim elements, as Patent Owner did in the parallel District Court litigation, Penn-II, “using the Clustal program at default settings to generate amino acid sequence alignments and calculate percent identity values.” Id. at 21–22. Petitioner, however, does not ask for any particular construction of any claim term. See id. Patent Owner states that it “does not challenge Petitioner’s articulation of the lack of a need for claim construction.” PO Resp. 10. Having considered the record, we determine that no express claim construction of any claim term is necessary to reach our decision. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms that . . . are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)); Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co. Ltd. v. Matal, 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., 200 F.3d at 803)).” slip op. at 12

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “According to the import of the complete recitation of paragraph 250 of the ’772 Publication set forth above that Petitioner relies upon for the motivation to improve efficient gene transfer in liver, AAV8 already fulfills this need. See Tr. 28:15–18. We do not read the ’772 Publication as calling for a search for a more efficient variant to improve efficient gene transfer in liver. We credit Dr. Samulski’s testimony that supports this view of the teachings of the ’772 Publication. Dr. Samulski testifies: Additionally, when the inventors compared AAV8’s expression in the liver against new serotypes AAVrh2, AAVrh10, AAVrh13, and AAVrh21, they found that AAV8 remained superior: EX1007, ¶ 253. Notably, AAV8 was shown to have over fifty percent (50%) greater expression in liver than AAVrh10. As I discuss more below, a skilled artisan in 2005 would not have expected a single amino acid substitution to significantly alter tropism in order to target to a different tissue. Thus, in my opinion, in 2005, a skilled artisan with the goal of targeting the liver would have selected the best known vector for delivery to liver at that time—AAV8. Ex. 2027 ¶ 42. We also agree with Dr. Samulski’s opinion that a POSA would have selected the best vector for liver, AAV8, instead of modifying another vector to increase tropism to liver. Dr. Samulski testifies: In my opinion, a skilled artisan in 2005 would not have looked solely to modify a vector to try to improve tropism to a particular tissue. As discussed throughout this declaration, changing tropism is difficult to predict, and a skilled artisan would not have had a reasonable expectation that changes could be made to improve or alter tropism. A skilled artisan would also have been concerned that changes, even small ones, could negatively impact other properties of the capsid protein. Therefore, rather than seek to modify a vector, a skilled artisan” slip op. at 29

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

    “The ’772 Publication, however, does not indicate as Petitioner asserts that a new variant is necessary to improve the efficiency of gene transfer to liver; the ’772 Publication indicates that AAV8 fulfills that need. See Ex. 1007 ¶ 250. In the paragraph that Petitioner relies upon for the alleged need to improve the efficiency of gene transfer to the liver, the ’772 Publication states in full: The tropism of each new vector is favorable for in vivo applications. AAV2/7 vectors appear to transduce skeletal muscle as efficiently as AAV2/1, which is the serotype that confers the highest level of transduction in skeletal muscle of the primate AAVs tested to date. Importantly, AAV2/8 provides a substantial advantage over the other serotypes in terms of efficiency of gene transfer to liver that until now has been relatively disappointing in terms of the numbers of hapatocytes stably transduced. AAV2/8 consistently achieved a 10 to 100-fold improvement in gene transfer efficiency as compared to the other vectors. The basis for the improved efficiency of AAV2/8 is unclear, although it presumably is due to uptake via a different receptor that is more active on the basolateral surface of hepatocytes. This improved efficiency will be quite useful in the development of liver-directed gene transfer where the number of transduced cells is critical, such as in urea cycle disorders and familial hypercholesterolemia. Id. (citations omitted) (emphasis added). According to the import of the complete recitation of paragraph 250 of the ’772 Publication set forth above that Petitioner relies upon for the motivation to improve efficient gene transfer in liver, AAV8 already fulfills this need. See Tr. 28:15–18. We do not read the ’772 Publication as calling for a search for a more efficient variant to improve efficient gene transfer in liver. We credit Dr. Samulski’s testimony that supports this view of the teachings of the ’772 Publication. Dr. Samulski testifies: Additionally, when the inventors compared AAV8’s expression in the liver against new serotypes AAVrh2, AAVrh10, AAVrh13, and AAVrh21, they found that AAV8 remained superior:” slip op. at 28

  Patent outcomesUS 11,680,274 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,680,274
• Gene Company Pty Ltd v. The Trustees Of Columbia University In The City Of New YorkNo claims unpatentable
  PTAB · Jun 23, 2025 · IPR2024-00313 · APJ Tawen Chang · IPR · Final written decision

  Claims 1–54 were not shown unpatentable because Petitioner failed to establish a reasonable expectation of success for the proposed combinations; objective indicia also supported non-obviousness.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “As to the first issue, we agree with Patent Owner that defining the level of skill in view of the solution described in the patent risks improper hindsight. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) 18 (“[T]he level of skill in the art is a . . . lens through which . . . the Board views the prior art and the claimed invention,” which “prevents . . . factfinders from using their own insight or . . . hindsight[] to gauge obviousness.”). We therefore do not include “practical knowledge about . . . the deuterium isotope effect, including the patents and publications discussed [in the Petition],” as part of our definition of a person of ordinary skill in the art.” slip op. at 18

  • Expert testimonyPetitioner expert creditedMixed

    “person of ordinary skill in the art would employ” in an obviousness analysis, we give some weight to Dr. Guengerich’s testimony. KSR, 550 U.S. at 418; Plantronics, Inc. v. Aliph, Inc., 724 F.3d 1343, 1354 (Fed. Cir. 2013) (explaining that “motivation to combine may be found. . . in . . . the background knowledge, creativity, and common sense of the person of ordinary skill”). Nevertheless, even if we were to agree that an ordinarily skilled artisan would have seen the 1,5-shift in NRPE in Mata’s A2E biosynthetic pathway as a particularly desirable location for intervention, we are not persuaded that such a person would have been motivated to substitute C20 deuterated vitamin A for the vitamin A in Ortho Pharma’s composition and method, because Petitioner has not shown, by a preponderance of evidence, that such an artisan would have reasonably expected the substitution to retard the accumulation of A2E or to treat macular degeneration.” slip op. at 42

  • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble limitingDecided for patent owner

    “In our Institution Decision, we preliminarily construed the preamble of claim 28 as limiting. Inst. Dec. 30–31. Petitioner did not take issue with our construction, or dispute Patent Owner’s construction of the preambles of claims 1 and 29 as also limiting. After consideration of the full trial record, we maintain our construction of the preamble of claim 28 as limiting for the reasons set forth in our Institution Decision. For similar reasons and the reasons set forth in Patent Owner’s Response, we further construe the preambles of claims 1 and 29 as limiting. See PO Resp. 12–14. We further determine that we do not need to construe any other claim term in order to resolve the controversy between the parties. 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 26

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

    “415 F.3d 1303, 1312–19 (Fed. Cir. 2005) (en banc). Under this framework, claim terms are given their ordinary and customary meaning, as would be understood by a person of ordinary skill in the art, at the time of the invention, in light of the language of the claims, the specification, and the prosecution history of record. Id.” slip op. at 25

  Patent outcomesUS RE47,045 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
• 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

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.