• 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
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.No claims unpatentable
  PTAB · Jun 9, 2026 · IPR2025-00321 · APJ Christopher M Kaiser · IPR · Final written decision

  The Board held claims 1, 2, 5–7, 9, 16, and 17 not unpatentable because the asserted combinations did not establish the required purge-tower teachings or prior-art status.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that one of ordinary skill in the art “would have had (1) at least a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a related field, and (2) at least two years of research or industry experience in 3D printing or materials used for 3D printing.” Pet. 5 (citing Ex. 1003 ¶¶ 14–16). Petitioner also argues that “[a]dditional experience could substitute for a formal degree or formal training (and vice versa).” Id. Patent Owner proposes a slightly different level of skill, arguing that a person of ordinary skill in the art “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” Prelim. Resp. 24. Neither party explains why the outcome of this case would be affected by the adoption of any of the proffered definitions of a person of ordinary skill in the art. We adopt Petitioner’s assessment of the level of ordinary skill in the art, as it appears consistent with the ’324 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “According to the ’713 patent, “[p]urge tower 24 itself may be . . . recycled or otherwise discarded as desired.” Ex. 1001, 8:27–28. This description provides some support for Patent Owner’s view, because a purge tower too intimately integrated with the part would be difficult or impossible to recycle or discard. This is further supported by the ’713 patent’s statement that “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Id. at 8:30–34. It also is supported by Dr. Hickner’s testimony that the ’713 patent “clearly shows . . . the 24 purge tower separated from the part” and that “the purge tower is a separate physical object.” Ex. 2016, 28:8–10, 64:1–9. On the other hand, there is evidence supporting Petitioner’s view that, as long as the purge tower is generally separate from the part and the support structure, it may still make contact with those portions of the print. As noted above, “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Ex. 1001, 8:30–34. This language does not exclude locations adjacent to or in contact with the part or the support structure. Thus, determine that a “purge tower,” as that term is used in the context of the ’713 patent, may not be an integrated portion of a printed part or support structure but need not be free of all contact with the printed part or support structure.” slip op. at 9

  • BurdenNot shown unpatentable

    “There is evidence of record to support both Petitioner’s view and Patent Owner’s view. On the record developed at trial, however, we cannot say that the preponderance of the evidence favors Petitioner, who bears the burden of proof. See 35 U.S.C. § 316(e). Accordingly, Petitioner has not shown by a preponderance of the evidence that KISSlicer teaches printing a layer of a purge tower each time the printer switches one extruder to the operating mode. Because proving the obviousness of claims 1 and 16 requires such a showing, Petitioner has not shown by a preponderance of the evidence that claims 1 and 16 would have been obvious over the combination of Priedeman and KISSlicer. 5. Analysis of Remaining Claims Claims 2, 6, 7, 9, and 17 all depend, directly or indirectly, from claim 1 or claim 16. Accordingly, they all include the limitations of either claim 1 or claim 16. Because, as discussed above, Petitioner has not shown that the combination of Priedeman and KISSlicer teaches or suggests all the limitations of claims 1 and 16, Petitioner also has not proven by a preponderance of the evidence that claims 2, 6, 7, 9, and 17 would have been obvious over that combination of references.” slip op. at 21

  • Obviousness (§103) › Analogous artAnalogous artOther

    “On the record developed at trial, we agree with Petitioner. According to several industry forum posts, people interested in three-dimensional printing located the website where KISSlicer was posted between February 2012 and April 2012. Ex. 1028, 1 (post discussing and directing others to KISSlicer on April 11, 2012); Ex. 1031, 1 (two posts discussing KISSlicer on March 16, 2012, and March 21, 2012); Ex. 1032, 1 (two posts discussing KISSlicer on February 11, 2012, and February 14, 2012). Thus, not only was it possible for people of ordinary skill in the art to locate KISSlicer; people of ordinary skill in the art actually did locate it. Accordingly, Petitioner has shown by a preponderance of the evidence that KISSlicer was publicly accessible.” slip op. at 19

  Patent outcomesUS 9,421,713 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,421,713
• Stingray Group Inc. / Stingray Music USA, Inc. v. Edwin A. Hernandez-MondragonNo claims unpatentable
  PTAB · May 29, 2026 · IPR2025-00349 · APJ Jason M Repko · IPR · Final written decision

  Claims 1–21 were not shown unpatentable because Avellan did not disclose the claimed sequence of screen captures used to assemble a media stream.

  RulingsFinal written decision

  • Skill levelOther

    “Patent Owner submits a similar definition and does not dispute the Petition’s characterization of the level of ordinary skill in the art. PO Resp. 22. No express finding is necessary. The level of ordinary skill in the art is reflected by the prior art of record. Any perceived difference in how each party characterizes a POSITA does not change our analysis or conclusions.” slip op. at 5

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

    “on ordinary and customary meaning. Pet. 14–15; PO Resp. 22. We determine that construction of claim terms is not necessary to resolve the disputes raised by the parties in this proceeding.” slip op. at 6

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

    “c. Analysis “A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros. v. Union Oil Co. of California, 814 F.2d 628, 631 (Fed. Cir. 1987). We are persuaded by Patent Owner’s argument that Avellan does not anticipate claim 1 because it does not assemble a media stream of multimedia items using the recited screen captures. See PO Resp. 26–29. We agree with Patent Owner that the plain language of the claim requires more than transmitting individual media items. Sur-reply 21. To the extent that Avellan captures images, those images do not meet the claimed requirements for a “temporal sequence of screen captures” in the independent claims, which must (1) be of the web page rendered by a browser, (2) “define all the content of the web page at a given time,” (3) “illustrate a dynamic change of at least a portion of the content over time” when two of them are compared, and (4) used to assemble “the at least one media stream.” Rather, the record better supports Patent Owner’s argument that Avellan transmits the multimedia items separate from any media stream assembled from screen captures. PO Resp. 26–29; Sur-reply 21.” slip op. at 8

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

    “All other challenged claims require the “generating” and “assembling” operations because they depend from claims 1, 12, or 17. Petitioner does not allege that the additional references—Durante, Ma, Suzuki, Wanamaker, Heikens, Matthews, or Wilsher—teach or suggest the “temporal sequence of screen captures” recited in claim 1. Rather, Petitioner’s reasoning in the challenges to the dependent claims pertaining to the screen captures mirror the rationale presented in the independent claim. See, e.g., Pet. 25 (arguing that Avellan’s screen captures correspond to the video content in the challenge to claim 2), 26–27 (arguing that Avellan obtains screen captures from a playback of a video on the webpage in the challenge to claim 4). Petitioner’s argument that Avellan teaches or suggests these operations in the grounds based on obviousness under 35 U.S.C. § 103 depend on the reasoning and insufficiently supported characterizations of Avellan in the challenges based on 35 U.S.C. § 102, as discussed above. See Pet. 40–60. grounds based on anticipation under 35 U.S.C. § 102 or teaches or suggests these operations in the grounds based on obviousness under 35 U.S.C. § 103, Petitioner has not met its burden to show that any challenged claim is unpatentable as anticipated by Avellan or obvious over any of the combinations of Avellan and the other cited references.” slip op. at 15

  Patent outcomesUS 10,123,074 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 10,123,074
• Adobe Inc. v. Jonathan E. JaffeNo claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01352 · APJ Bach V Hoang · IPR · Final written decision

  Claims 1–6 were not shown unpatentable under any asserted §103 ground because the references did not teach monitoring the physical coupling between the sensor and memory.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The Institution Decision adopted and applied Petitioner’s proposed level of ordinary skill because Petitioner’s “definition generally comports with the level of skill necessary to understand and implement the teachings” slip op. at 11

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

    “The parties present various claim construction arguments, disputing the meaning of three limitations recited in claim 1: “a sensor, which is tightly coupled to said memory”; “monitoring the integrity of the tight coupling between said memory and said sensor”; and “based on.” See Pet. 9–14; PO Resp. 5–12; Pet. Reply 4–9; PO Sur-reply 4–11. For purposes of this Decision, we do not need to discuss the construction of “based on.” 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)). As explained below, this Decision turns on whether Glass or Rieger discloses limitation [1c] reciting “monitoring the integrity of the tight coupling between said memory and said sensor.” Ex. 1001, 20:65–66; see infra §§ II.C.2, II.E.1, II.F. That limitation recites an element which overlaps with the earlier-recited limitation “a sensor, which is tightly coupled to said memory.” To reach our decision, we need only provide a limited discussion of two of the parties’ claim construction arguments. Our analysis follows.” slip op. at 13

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

    “said integrity is compromised, then also providing an indication of said compromised integrity.” Ex. 1001, 20:65–21:2. Although Petitioner points out that the limitation does not expressly recite “‘specifically’ monitoring the tight coupling” (Pet. Reply 8), the structure of the clause suggests that the tight coupling is specifically monitored. At a high level, the limitation is straightforward in its recitation that the integrity being monitored is “of the tight coupling” (Ex. 1001, 20:65–66 (emphasis added)), plainly suggesting that the tight coupling is specifically monitored. More granularly, breaking the relevant clause down to its grammatical parts, the clause recites a gerund (“monitoring”) acting on a direct object (“the integrity”) which is modified by a prepositional phrase (“of the tight coupling”). Notably, the object of the preposition (“of”) is “the tight coupling.” Altogether, this reads that the integrity being monitored is specifically of the tight coupling. Also, the claim recites that “if said integrity is compromised, then also providing an indication of said compromised integrity.” Therefore, from the claim language we know that the “integrity” of the tight coupling is something that may be “compromised,” which is consistent with Patent Owner’s proposed construction of determining whether the physical coupling has been “accessed or disturbed.” Petitioner’s interpretation effectively inserts additional language into the limitation such that the limitation includes monitoring the integrity of a device containing or surrounding the tight coupling, such as a camera (or camera housing), e.g., “monitoring the integrity of a camera that includes the tight coupling.” But, because the plain reading and the structure of the limitation reads that it is specifically the tight coupling’s integrity—not another physical structure, like a camera—which is being monitored, a monitored is not consistent with the language of the claim. See PO Resp. 9 (arguing that “Petitioner’s construction is improper because the claim language explicitly requires monitoring the physical coupling between the memory and the sensor as opposed to some third structure” (emphasis omitted)).” slip op. at 17

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

    “package 50 does not specifically monitor the integrity of the coupling between Glass’s sensor and the memory and, instead, argues that Glass detects tampering of all “the components and interconnections contained in that packaging,” e.g., control logic 44, cropper 46, compressor 47, MUX 45, code generator 48, and the various interconnections between those components. See Pet. Reply 16; Ex. 1005, 5:13–41. As explained above, we construe “monitoring the integrity of the tight coupling between said memory and said sensor” to mean determining whether the physical 7 Petitioner does not assert that a person of ordinary skill in the art would have been motivated to modify Glass’s device in any way; Petitioner solely argues that Glass teaches limitation [1c], based on Petitioner’s proposed claim construction. See Pet. 30–32 (“Glass discloses this limitation.”); Pet. Reply 16–17 (“Glass and Rieger disclose the ‘monitoring’ step.”). disturbed, which specifically requires monitoring the physical coupling between the sensor and the memory. See supra § II.C.2. As we agree with Patent Owner that this limitation requires monitoring the physical coupling between the sensor and the memory, monitoring Glass’s tamper resistant package 50 does not teach or disclose “monitoring the integrity of the tight coupling between said memory and said sensor.” Accordingly, we determine that Petitioner fails to show that Glass teaches or suggests [1c] monitoring the integrity of the tight coupling between said memory and said sensor when said at least one internal and unique parameter is generated, and, if said integrity is compromised, then also providing an indication of said compromised integrity, as required by claim 1. Consequently, we determine that Petitioner has not shown, by a preponderance of the evidence, that the subject matter of claim 1 would have been obvious over Glass.8” slip op. at 30

  Patent outcomesUS 6,757,828 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 6,757,828
• Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentable
  PTAB · Feb 10, 2026 · IPR2024-01119 · APJ Sharon Fenick · IPR · Final written decision

  Claims 1, 2, 27, 37, 58, 60-64, 67-79, 186, 187, 189, 191, 192, 197, 199-204, 208-216, 223, 225, and 230 were not proven unpatentable over the asserted combinations.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “Patent Owner “does not agree with all aspects of Petitioner’s proposed level of ordinary skill” but did not propose an alternative definition. PO Resp. 10–11. Patent Owner’s declarant, Dr. Rosenberg, adopted Dr. Terveen’s definition for the purposes of his declaration. Ex. 2018 ¶¶ 32–33. We again adopt the main portion of Dr. Terveen’s definition, and determine that one of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, human-computer interaction, or a comparable field and at least two years of professional experience working with graphical user interfaces and applications for computers.” This definition is commensurate with the problems and solutions in the ’754 patent and prior art of record and is supported by declarant testimony.” slip op. at 9

  • BurdenNot shown unpatentable

    “Given our determination of how Ahn consistently describes the “touch and drag” gesture and “dragged” to mean the movement of a finger (or other object external to the touch screen), and in the absence of persuasive evidence in the figures or in other portions of Ahn to support the movement or appearance of a menu during a user input gesture, we determine that the present record does not support a conclusion that Ahn teaches or suggests a menu sliding onto a display or appearing during an input gesture such as a touch and drag gesture, as opposed to being displayed after such a gesture is completed.” slip op. at 27

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

    “Given our determination of how Ahn consistently describes the “touch and drag” gesture and “dragged” to mean the movement of a finger (or other object external to the touch screen), and in the absence of persuasive evidence in the figures or in other portions of Ahn to support the movement or appearance of a menu during a user input gesture, we determine that the present record does not support a conclusion that Ahn teaches or suggests a menu sliding onto a display or appearing during an input gesture such as a touch and drag gesture, as opposed to being displayed after such a gesture is completed.” slip op. at 27

  • Expert testimonyDecided for patent owner

    “Petitioner argues that “even under [this] interpretation of Ahn, the only difference between Ahn and the claims is whether the animation occurs in direct correspondence with a user’s dragging gesture or after the dragging gesture is complete – a straightforward design choice if ever there was one.” Pet. Reply 3–4 (citing Ex. 1024, 99:16–108:20; Ex. 1023 ¶ 12). However, as Patent Owner argues (PO Sur-reply 7–8) this argument is presented in Reply and is an improper shift of theory from the Petition. Nevertheless, were we to consider it, we would not find it compelling; Dr. Terveen’s cited testimony repeats this bare statement and is not supported by any evidence or additional explanation. Ex. 1023 ¶ 12; see 37 CFR § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”); Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (Aug. 24, 2022) (precedential) (assigning little weight to opinion testimony that “merely repeats” conclusory statements in a brief, without “cit[ing] any additional supporting evidence or provid[ing] any technical reasoning to support [the declarant’s] statement”).” slip op. at 29

  Patent outcomesUS 10,656,754 not shown unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,656,754
• Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentable
  PTAB · Feb 10, 2026 · IPR2024-01116 · APJ Sharon Fenick · IPR · Final written decision

  Petitioner did not prove claims 1, 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191, 192, 197, 199–204, 208–216, 223, 225, or 230 unpatentable because the asserted combinations did not establish the claimed blurring …

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “(Ex. 1003), that a person of ordinary skill in the art (“POSITA”) would have had “a Bachelor of Science degree in computer science, computer engineering, electrical engineering, human-computer interaction, or a comparable field and at least two years of professional experience in the design and development of graphical user interfaces (GUIs), human-computer interfaces, or equivalents thereof,” and that “[a]dditional years of experience could substitute for an advanced-level degree (and vice-versa).” Pet. 6 (citing Ex. 1003 ¶¶ 29–30).” slip op. at 9

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

    “C. Claim Construction In these proceedings, there is no controversy that would require us to decide any claim construction issue. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 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., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Obviousness of Claims 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191,” slip op. at 10

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

    “obviousness of the menus in the Ahn-Chaudhri combination following a user’s finger as the user performs the dragging gesture to open the menu.” Pet. Reply 2 (citing 01119-Petition, 26–33, substantially identical to Pet. 32– 40). However, again, the Petition does not explain an alternative theory in which Chaudhri supplements Ahn’s menu functionality to move that menu onto the screen, as opposed to teaching visual cues provided by gradual changes of the display during a gesture or the visual cue that an unlock image may provide during the unlock gesture. See Pet. 14–18 (describing Chaudhri teaching “visual differentiation” or “transitioning an optical intensity” between a user-interface object and the background, based on, e.g., transparency), 35–40 (same). In Reply, Petitioner adds evidence to attempt to support its contention that the combination teaches a menu following a user’s finger during a dragging gesture, involving references to Chaudhri’s discussion of a visual cue, further discussing Chaudhri’s unlock image. Ex. 1005 ¶¶ 54, 62, 74–79, Figs. 5A-5C (cited at Pet. Reply 4–5). With respect to these citations and arguments, even if they had been timely presented in the Petition, we agree with Patent Owner that they do not articulate a modification of Ahn with Chaudhri or a motivation to combine. PO Sur-reply 6. Additionally, we agree that these embodiments of Chaudhri are distinct from the cited portions of Chaudhri discussed with respect to this theory in the Petition, which relate not to the movement of displayed graphics, but to variations of optical intensity and visual cues. Id. at 6–7. We evaluate the Petition’s arguments in light of Petitioner’s statement in Reply that they require a teaching regarding “menus . . . following a user’s finger as the user performs the dragging gesture.” Pet. Reply 2. To the extent that the Petition shows that the combination of Ahn and Chaudhri would show visual changes as the user performs a dragging gesture, these do not relate to the movement of a menu, but rather to other optical effects. Thus, as we do not find that the Petition supports an Ahn-Chaudhri combination in which a menu follows a user’s finger as the user performs the dragging gesture to open the menu, as Petitioner argues, we determine that Petitioner has not shown limitation 2.d of claim 2 taught or suggested by the combination of Ahn and Chaudhri according to this theory.” slip op. at 31

  • Strike new argumentNew argument disregardedDecided for patent owner

    “Petitioner argues that “even under [this] interpretation of Ahn, the only difference between Ahn and the claims is whether the animation occurs in direct correspondence with a user’s dragging gesture or after the dragging gesture is complete – a straightforward design choice if ever there was one.” Pet. Reply 3–4 (citing Ex. 1024, 99:16–108:20; Ex. 1023 ¶ 12). However, as Patent Owner argues (PO Sur-reply 7–8) this argument is presented in Reply and is an improper shift of theory from the Petition. Nevertheless, were we to consider it, we would not find it compelling; Dr. Terveen’s cited testimony repeats this bare statement and is not supported by any evidence or additional explanation. Ex. 1023 ¶ 12; see 37 CFR § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”); Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (Aug. 24, 2022) (precedential) (assigning little weight to opinion testimony that “merely repeats” conclusory statements in a brief, without “cit[ing] any additional supporting evidence or provid[ing] any technical reasoning to support [the declarant’s] statement”).” slip op. at 29

  Patent outcomesUS 10,656,754 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,656,754

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.