• 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
• Cisco Systems, Inc. v. Umbra Technologies Ltd.No claims unpatentable
  PTAB · Aug 28, 2025 · IPR2024-00270 · APJ Gregg I Anderson · IPR · Final written decision

  Claims 15–20 were not shown unpatentable because Hankins did not teach limitation 15.3; claims 1–14 were disclaimed.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s proposal of the level of ordinary skill in the art. PO Resp. 6. Petitioner’s proposal is supported by the Reddy Declaration and is consistent with the ’595 patent and the asserted prior art. Accordingly, we apply Petitioner’s articulation in our obviousness evaluation below.” slip op. at 14

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

    “B. Claim Construction Beyond plain and ordinary meaning, Petitioner does not propose any term for claim construction. Pet. 13. Patent Owner does not argue any claim construction issue. See generally PO Resp. The argument and evidence provided by the parties regarding limitation 15.3 is dispositive. See Section II.E. below. Our analysis of limitation 15.3 does not turn on any claim construction question. Id. Accordingly, we do not need to construe any claim term. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we 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))). We apply the plain and ordinary meaning of all claim terms, as would have been understood by a person of ordinary skill in the art, in the context of the ’595 patent.” slip op. at 14

  • Adverse judgmentAdverse judgmentOther

    “D. Claims 1–14 as Obvious Over Kommula As already noted, Patent Owner has disclaimed claims 1–14. Ex. 3001. We do not analyze claims 1–14 as the challenge is mooted by the filing of the Statutory Disclaimer.” slip op. at 15

  • BurdenNot shown unpatentable

    “350 receiving a request for a listing of “services” from a gateway device and provisioning one or more tunnel servers has not been shown to teach generating “a list of available servers.” There is no persuasive evidence to support Petitioner’s assertion. Petitioner relies on unsupported argument because, at best, Hankins discloses gateway devices 311 and 321, each of which is located in different logical broadcast domains, requesting services from one another. Ex. 1005, 12:9–16. This particular disclosure, however, does not appear to implicate the functionality of Hankins’s controller 350, much less result in controller 350 generating a list of available tunnel servers that would allow gateway devices 311 and 312 to exchange a listing of “services” therebetween. Petitioner’s reliance on Hankins’s controller 350 provisioning additional tunnel servers both to improve performance and without human intervention fares no better. Ex. 1005, 25:45–55. There is no indication in Hankins that this provisioning performed by controller 350 is done in response to receiving a request for a list of available tunnel servers from either gateway device 311 or 312.” slip op. at 20

  Patent outcomesUS 11,108,595 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,108,595
• 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
• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00398 · APJ George R Hoskins · IPR · Final written decision

  Claims 1–22 were not shown unpatentable as obvious over Dill, Vadhri, and Akashika because Dill was not shown to disclose the claimed Integration Tier Limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We adopt Petitioner’s undisputed formulation of ordinary skill in the art as set forth above, because we are satisfied this formulation generally comports with the level of skill necessary to understand and implement the teachings of the ’196 patent and the asserted prior art. We do not adopt Patent Owner’s annotation to Petitioner’s formulation as requiring knowledge of “mobile wallets” specifically, because we determine knowledge of “mobile payment systems and techniques” per Petitioner’s formulation is tied sufficiently to the claims of the ’196 patent to reflect the level of ordinary skill in the pertinent art. At the same time, even if we were to include knowledge of “mobile wallets” in our formulation, it would not materially change our Decision as set forth below. That is, we would still determine Petitioner has not shown by a preponderance of the evidence that Dill discloses the Integration Tier Limitation.” slip op. at 10

  • Expert testimonyNot reached

    “We need not resolve the parties’ dispute as to whether Dr. Houh qualifies as an ordinarily skilled artisan. Even assuming that Dr. Houh possesses, at a minimum, ordinary skill in the art—as we have done in this Decision—we determine Petitioner still fails to show that any of the challenged claims are unpatentable.” slip op. at 12

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

    “The Integration Tier Limitation requires no further construction for purposes of this proceeding. See Pet. Reply 7 (“[N]o specific construction is required.”). The claim clearly specifies that the claimed “web services communication mechanisms” must serve as an interface between the integration tier and (1) the claimed mobile wallet application and, separately, (2) “a plurality of different device types over a plurality of different communication channels.” For purposes of this Decision, we assume that this interface may be direct or indirect. See id. at 6 (asserting that “communication channels that interface, even indirectly, with the ‘web services communication mechanisms’ still interface with the ‘web services communication mechanisms’”).” slip op. at 28

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

    “However, we find that of those four channels (1)–(4), only the first channel (1) is associated with web interface 137 such that it qualifies as a “communication channel,” as required by claim 1. There is no indication in the Dill disclosures cited by Petitioner that any of the other three channels (2)–(4) are associated with web interface 137. For example, Figure 9 of Dill includes a double-headed arrow to illustrate communication between web interface 137 and transfer options module 145, but Figure 9 does not include any arrows to illustrate communication between web interface 137 and any one or more of IVR interface 136, other interfaces 138, agent system 135, or mobile network 115. See Ex. 1005, Fig. 9. In other words, Petitioner fails to show Dill teaches web interface 137 interfaces with any devices over any of channels (2)–(4), as would be required by Petitioner’s mapping. In the Petition, Petitioner never clearly (or persuasively) addresses this requirement of the claim. Petitioner does contend that transfer options module 145 is coupled to various devices via interfaces 136–138 and exchanges transaction information (see Pet. 25–26; see also Pet. Reply 10– 11), but that contention misses the mark. The salient question is whether Dill’s web interface 137 (i.e., the claimed “web services communication mechanisms”) interfaces with the different device types over the channels, not whether transfer options module 145 (i.e., the claimed “integration tier”) does so.” slip op. at 30

  Patent outcomesUS 10,438,196 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,438,196
• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00399 · APJ Juliet Mitchell Dirba · IPR · Final written decision

  Claims 1–22 were not shown unpatentable under § 103 over Dill, Vadhri, and Akashika because Dill did not teach or render obvious the hardware SIM card and integration tier limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Institution Decision, we determined that a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering, computer science, or equivalent training, and approximately two years of work experience in software development with a basic knowledge of accounting” and “working knowledge of mobile payment systems and techniques,” as Petitioner proposes. Inst. Dec. 9 (quoting Pet. 3–4). We stated that “this definition generally comports with the level of skill necessary to understand and implement the teachings of the ’488 patent and the asserted prior art.” Id. (citing Ex. 1003 ¶ 22; Ex. 2001 ¶ 35).” slip op. at 10

  • Expert testimonyPetitioner expert discountedMixed

    “In addition, Petitioner’s reliance on Dr. Houh’s testimony (see Pet. 23–24) is unavailing. Although Dr. Houh agrees with the arguments in the Petition and includes quotes from the cited portions of Dill and Bykov (see Ex. 1002 ¶¶ 95–97), he provides no additional analysis or explanation beyond what was provided in the Petition. As a result, his testimony suffers the same deficiencies as the Petition. Also, we do not credit his conclusion that Dill includes the requisite disclosure (see id. ¶ 97) because he fails to provide sufficient supporting explanation or evidence (see 37 C.F.R. § 42.65(a)). Finally, we note that Petitioner misrepresents Dr. Shamos’s testimony by stating that Dr. Shamos “agrees that if a mobile device executes a mobile wallet over a cellular network, the mobile device has a SIM card for the mobile wallet.” Pet. Reply 22 (emphasis added) (citing Ex. 1022, 29:4–7, 40:9–10). In the cited testimony, Dr. Shamos agrees that mobile devices have SIM cards, but he does not address where a mobile wallet application would be installed. Ex. 1022, 29:4–7, 40:9–10. Thus, contrary to Petitioner’s argument, we determine that Dr. Shamos’s testimony does not support Petitioner’s position.” slip op. at 27

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

    “for the term “hardware SIM card” because the important points are undisputed. In particular, the parties agree that a “hardware SIM card” is a SIM card implemented in hardware rather than software. See Pet. Reply 9 (citing Ex. 1021 ¶ 36); Tr. 40:25–41:2 (Patent Owner’s counsel explaining that the language in its proposed construction was “to differentiate it from a software SIM card”); see also PO Resp. 16, 19 (asserting that the term refers to a specific type of hardware, namely a “chip” or a “smart card”) (citing Ex. 2003 ¶¶ 32–33). The parties also agree that an ordinarily skilled artisan would have known that a “SIM card” is a component in a mobile device involved in identifying and authenticating a user to a mobile network. See Tr. 30:23–31:3 (Petitioner’s counsel stating “a SIM card, just as known in the art . . . would allow the user to be able to access the mobile network” 10 Each page in Exhibit 2021 includes at least two page numbers. For clarity, we refer to the page number of the exhibit (shown in the bottom right corner), and we have adjusted Patent Owner’s citation accordingly. given “the user’s identification information on it”), 39:24–40:2 (Patent Owner’s counsel stating that “I think everyone is in agreement that the critical aspect of what makes a SIM card a SIM card is that it can authenticate a mobile device to a wireless network”). The evidence supports the parties’ understanding. The word “SIM” is an acronym for “subscriber identity module” (see, e.g., Ex. 1001, 6:58–67; Ex. 2021, 5), and the record shows that a SIM is a specific component in a mobile device that is involved in identifying and authenticating a user to a mobile network (see Ex. 2003 ¶¶ 30–31; see also e.g., Ex. 2021, 7 (stating that a SIM’s “primary function” is “to authenticate the subscriber to the network”); Ex. 2025, 3 (describing the SIM)).11 Consequently, we determine that an ordinarily skilled artisan would have understood a “hardware SIM card” to be a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. We do not need to further construe the term, or determine whether the additional requirements proposed by Patent Owner are appropriate, because Petitioner fails to show that the prior art teaches or suggests the claimed “hardware SIM card,” as explained below. See infra § II.D.2.a (analyzing the parties’ substantive contentions).” slip op. at 13

  • BurdenNot shown unpatentable

    “Petitioner has not shown, by a preponderance of the evidence, that Dill discloses “a mobile wallet application installed on a hardware SIM card,” as required by element 1.3B. See Pet. 23–24. In particular, even assuming that Dill teaches installing a mobile wallet application somewhere on a mobile device (see Pet. 23),14 Dill does not teach installing it on a hardware SIM card,15 as specifically required by the claim. Petitioner relies upon paragraph 106 of Dill (see Pet. 23), but that paragraph does not disclose this claim limitation (see Ex. 1005 ¶ 106). In relevant part, that paragraph of Dill simply states: 14 Patent Owner disagrees with this premise, arguing that Dill does not disclose a mobile device that includes a mobile wallet application. See PO Resp. 52–56. We need not resolve that dispute because, even assuming Petitioner’s premise (as we have done in this Decision), Petitioner still fails to show that the claims are unpatentable. 15 As noted above, a “hardware SIM card” is a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. See supra § II.C.1 (addressing meaning of term). It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software. Ex. 1005 ¶ 106 (emphases added). This teaches storing instructions on “other types of machine-readable mediums,” but it fails to teach storing instructions on a hardware SIM card, much less storing Dill’s mobile wallet application there. In short, Dill is silent with respect to this issue, and silence is not disclosure. Notably, Petitioner does not contend (or show) that a mobile wallet application installed on a mobile device would necessarily be installed on a hardware SIM card. See Pet. 23–24; Ex. 1003 ¶¶ 95–97. Indeed, the record indicates that a mobile wallet application installed on a mobile device could instead be installed on a different component. See, e.g., Ex. 1001, 7:1–3, 9:33–35 (identifying device memory as alternate component); Ex. 2021, 5 (describing SIM as the “smaller of two computer chips inside a GSM mobile handset”); cf. Pet. Reply 9 (distinguishing between hardware SIM cards and software ones). Thus, Petitioner fails to show that this claim limitation is inherent in Dill. See PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1196 (Fed. Cir. 2014) (explaining that inherency requires a showing that “the limitation at issue necessarily must be present”).” slip op. at 22

  Patent outcomesUS 9,208,488 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,208,488
• Medivis, Inc. v. Novarad Corp.No claims unpatentable
  PTAB · Mar 6, 2024 · IPR2023-00042 · APJ Scott Raevsky · IPR · Final written decision

  Claims 1–6 and 11–20 were not shown unpatentable: Doo did not disclose the claimed volume, the Doo-Amira combination lacked a persuasive rationale, and the other references were not shown publicly accessible.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “We adopt Petitioner’s proposed level of skill, except that we excise part of Petitioner’s definition to produce the following modified version: a bachelor’s degree in computer science, electrical engineering, or a related field with several years of experience in the design, development, and study of augmented reality devices and . . . familiarity with conventional medical imaging data and visualization of data for medical procedures . . . . Our edit removes the alternative of “working with a team including someone with such familiarity” because one’s role in a team may be tangential to their personal experience with medical imaging. Regardless, had we adopted Petitioner’s original definition, our decision would not have changed.” slip op. at 7

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

    “The parties propose constructions for the claim terms “three- dimensional (3D) data,” “inner layer(s) of the patient,” “confined within a virtual 3D shape,” and “being having.” Pet. 11–14; PO Resp. 11–18. We do not need to construe any of these claim terms in order to resolve the issues presented in this proceeding. See Realtime Data, LLC v. Iancu, 912 F.3d 1368 (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 8

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

    “First, neither the Petition nor Dr. Kazanzides explains how Doo’s curved plane teaches the claimed “volume.” See Pet. 36–37; Ex. 1012 ¶¶ 74–75 (essentially repeating the Petition). The Petition merely asserts that Doo’s image in Figure 7 “is confined within the volume of the virtual 3D shape illustrated in Figure 9,” without explaining how the shape of Figure 9 has a “volume.” Pet. 37. The Reply does no better, asserting that “Doo’s shape 532 in Figure 9 and shape 432 in Figure 7 are virtual 3D shapes.” Reply 18. This statement is conclusory and does not explain how Doo’s “false 3D” shapes have volume. Petitioner further attempts to establish that Doo’s disclosure of Figure 9’s shape 532 as “mimic[ing] the surface curvature of the patient’s body” is evidence that Doo discloses a 3D shape. Id. (citing Ex. 1008 ¶ 76). This argument, however, is unpersuasive because it takes Doo’s statement out of context. Doo explains that Figure 9’s warped “two-dimensional image 532 . . . mimic[s] the surface curvature of the patient’s body,” not that it has volume. See Ex. 1008 ¶ 76 (emphasis added). In other words, even though Doo’s shape 532 of Figure 9, when projected on a patient’s body (as in Figure 7) may appear to a surgeon like a 9 Our Institution Decision did not rely on Petitioner’s theory based on Doo Figures 7–9. We discuss our Institution Decision’s reasoning below under Petitioner’s second theory based on Doo Figures 6 and 11. half-cylinder shape having a volume, Doo’s technique avoids rendering a 3D shape like a half-cylinder (hence calling these “false 3D shapes”) because it instead simulates the body’s curvature with a mere curved two-dimensional plane. Second, we find that Doo’s curved plane does not, in fact, have a volume.10 Instead, Doo’s curved plane is a 2D plane merely “wrapped around an axis.” See Ex. 1008 ¶¶ 75–76. As Patent Owner persuasively argued at the hearing, Doo’s curved plane is not “half of a cylinder. It’s just a wrapped piece of paper.” Tr. 33:14–15. Just as curving a piece of paper would not give the curved paper a half cylinder’s volume, neither does curving Doo’s flat 2D plane create a half cylinder with volume. Viewed another way, curving a 2D plane does not impart volume to the plane any more than curving a 1D line into a parabola would impart area to the 1D line.” slip op. at 12

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

    “The U.S. Supreme Court has emphasized that “rejections on obviousness grounds cannot be sustained by mere conclusory statements; instead, there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” KSR, 550 U.S. at 418 (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Petitioner’s argument fails this standard. Petitioner asserts a generic rationale that one of ordinary skill in the art would have applied Amira to Doo “to take advantage of the visualization technology disclosed in Amira (or any similar visualization software).” Pet. 41. But Petitioner’s assertion contains no explanation why one of ordinary skill would have taken advantage of Amira’s technology in the context of Doo. Petitioner’s rationale is so vague and broad that it could be applied to combine any two references because it merely asserts that one reference would “take advantage of the . . . technology disclosed in” another. See, e.g., In re Van Os, 844 F.3d 1359, 1361 (Fed. Cir. 2017) (explaining that “a finding that a combination of prior art would have been . . . ‘intuitive’ is no different than merely stating the combination ‘would have been obvious’”). This approach wholly misses KSR’s “articulated reasoning” standard. See KSR, 550 U.S. at 418. The Reply’s assertion that reducing a surgeon’s cognitive load in Doo “suggests an improvement on conventional medical imaging displays, such as disclosed in Amira,” fares no better. Reply 20. This assertion again fails to explain why one of ordinary skill in the art would have combined Amira with Doo. For instance, Petitioner provides no explanation as to how Amira’s display would further reduce cognitive load. See Reply 19–20 (only vaguely referring to Amira’s “[t]racking capabilities [that] allow for . . . interaction with the visualization” (Ex. 1005, 14, 26)). Not only that, but Doo itself presents a solution for the cognitive load problem. See Ex. 1008 ¶ 14 (“The present invention is particularly adapted to manage the multitude of medical images needed to be viewed by a surgeon during an operation so that a surgeon is not required to look away from the patient, so that the surgeon does not have to sustain heavy cognitive loading.”). Petitioner does not persuasively explain why one of ordinary skill in the art would turn to yet another reference (like Amira) for an additional solution, or even what that solution would be.” slip op. at 23

  Patent outcomesUS 11,004,271 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 11,004,271

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.