- Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentablePTAB · 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 · GrahamPatents in suitUS 11,393,279 - Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 8,529,336 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 7,370,035 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - Silencerco Weapons Research, LLC v. Huxwrx Safety Co. LLCNo claims unpatentablePTAB · Dec 17, 2025 · IPR2024-01214 · APJ Sean P O’Hanlon · IPR · Final written decision
Claims 2, 3, 6, 9, 12–14, 18, and 20 were not shown unpatentable; the motion to amend was granted for substitute claims 23, 26, 27, 29, 30, 32, 33, 37–40, and 42, and denied for …
RulingsFinal written decision- Skill levelSkill level board ownOther
“The level of ordinary skill in the art is “a prism or lens” through which we view the prior art and the claimed invention. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). The person of ordinary skill in the art is a hypothetical person presumed to have known the relevant art at the time of the invention. In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995). In determining the level of ordinary skill in the art, we may consider certain factors, including: “(1) the educational level of the inventor; (2) type of problems encountered in the art; (3) prior art solutions to those problems; (4) rapidity with which innovations are made; (5) sophistication of the technology; and (6) educational level of active workers in the field.” Best Med. Int’l, Inc. v. Elekta Inc., 46 F.4th 1346, 1353 (Fed. Cir. 2022) (quoting Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007)). “The patent’s purpose can also be informative.” Id.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“The ’750 patent states that “the fluid pathway can be a radially serpentine fluid pathway which causes the fluids received in the off axis chamber to flow back and forth around a radius of the off axis chamber,” also using “radially serpentine fluid pathway” to refer to this rotation around the chamber radius “while also traversing a length of the off axis chamber.” Ex. 1001, 4:34–41 (emphasis added). This is the only description of “radially” serpentine flow in the ’750 patent. Notably, the ’750 patent does not use “radially” or “serpentine” to describe a fluid pathway “which causes the fluids to spiral around the central chamber within the off axis chamber along a length of the off axis chamber,” instead referring to such a fluid pathway as a “helical fluid pathway.” Id. at 4:41–44. See CAE Screenplates, Inc. v. Heinrich Fiedler GmbH & Co. KG, 224 F.3d 1308, 1317 (Fed. Cir. 2000) (“In the absence of any evidence to the contrary, we must presume that the use of . . . different terms in the claims connotes different meanings.”); Bd. of Regents of the Univ. of Tex. Sys. v. BENQ Am. Corp., 533 F.3d 1362, 1371 (Fed. Cir. 2008) (“Different claim terms are presumed to have different meanings.”). Inst. Dec. 11–12. We explained that the flow path depicted above, which is equivalent to that of Figure 14 of the ’750 patent, “flows circumferentially about the central chamber.” Id. at 14. We maintain this interpretation. Stated differently, the depicted flow is around a longitudinal axis of the chamber. See MTA PG 6 (describing the flow path depicted above as “a back and forth flow path around a longitudinal axis of the off axis chamber; that is, a circumferentially serpentine pathway”); see also Ex. 2003 ¶ 40 (Dr. Neitzel describing the flow path depicted above as “a back and forth flow path around a longitudinal axis of the off axis chamber”). The flow is not around a radius of the chamber, which Patent Owner recognizes is required for a flow path to be radially serpentine. See PO Resp. 10 (“Patent Owner agrees with the Board’s conclusion in the [Institution Decision] that ‘radially serpentine’ as recited in the claims of the ’750 patent means a back and forth flow around a radius of the off axis chamber.” (citation modified)); PO Sur-reply 2 (agreeing that “radially serpentine” requires “a back and forth flow around a radius of the off axis chamber”).” slip op. at 14
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“We agree with Patent Owner that neither Petitioner nor its witness, Mr. Nixon, has explained adequately how Thurler’s disclosure of its tube e being perforated for two thirds of its length “contemplates other lengths of perforations.” See Pet. 48; Ex. 1013 ¶ 212. Such conclusory assertions fail to apprise us of why an ordinarily skilled artisan would have been motivated to modify Thurler’s device in contradiction to Thurler’s explicit disclosure. We are also not persuaded by Petitioner’s proffered reasoning for modifying Thurler’s device. First, the modification is not a matter of design choice because the perforations allow the gases generated by firing the projectile to pass into the space between tubes e and g where they partially expand. See Ex. 1015, 1:84–91. Thus, modifying the number of perforations necessarily affects the flow of gases through the device. Next, neither Petitioner nor Mr. Nixon explains adequately how reducing the amount of perforation in tube e results in an increased fluid length. See Pet. 49; Ex. 1013 ¶ 213. Rather, although less fluid may enter into tube e with Petitioner’s modification, it appears that that fluid would travel the same distance along tubes e and h as in Thurler’s unmodified device. Finally, neither Petitioner nor Mr. Nixon explains adequately how limiting the amount of gases generated by firing the projectile from entering the expansion zones of tubes g and h provides any benefit. To the contrary, limiting the amount of gases in the manner suggested by Petitioner would reduce the suppression of such gases, resulting in a less effective device. Moreover, Thurler discloses that “there is still a space of a few millimeters between [tubes] e and g which is necessary” to prevent the application of “pressure on the projectile causing the same to deviate.” Ex. 1015, 1:106–2:3. Thus, Petitioner’s modification would not result in the passage of gases occurring only at the first three of Thurler’s tubular sleeves as asserted by Petitioner. Additionally, in the Institution Decision, we explained that Petitioner did not provide adequate reasoning to support the proposed modification of Thurler’s device regarding parent claim 1 to have concentric tubes around the central tube e. See Inst. Dec. 29–31. This shortcoming, which we maintain, carries through to dependent claim 6. Accordingly, for the foregoing reasons, Petitioner has not shown, by a” slip op. at 26
- ScopeMotion to amend granted in partGranted in part
“We agree with Petitioner that the amendment is broadening. Petitioner’s witness testified that he “wouldn’t call a BB gun a high energy device or a high energy weapon.” Paper 33, 18:4–6. Thus, per Petitioner’s witness, use of a BB gun would not be covered by claim 22, no matter what is discharged from the BB gun. However, if high energy material is discharged from that same BB gun, that use would be covered by proposed substitute claim 43 (assuming the other claim recitations were met). See id. at 21:10–12 (Dr. Neitzel agreeing that “if something produces a high energy material, it automatically is a high energy weapon”). Thus, by deleting “high energy device” and replacing that language with “weapon,” proposed substitute claim 43 impermissibly broadens the scope of claim 22. See Sisvel Int'l S.A. v. Sierra Wireless, Inc., 81 F.4th 1231, 1241 (Fed. Cir. 2023) (“But if a substitute claim ‘is broader in any respect it is considered to be broader than the original claim even though it may be narrower in other respects.’” (citation modified) (quoting Hockerson-Halberstadt, Inc. v. Converse Inc., 183 F.3d 1369, 1374 (Fed. Cir. 1999))); see also Lectrosonics, Paper 15 at 6 (“A patent owner may not seek to broaden a challenged claim in any respect that enlarges the scope of the claims of the patent . . . . Likewise, a proposed substitute claim may not remove a feature of the claim in a manner that broadens the scope of the claims of the challenged patent.”).” slip op. at 45
Patent outcomesUS 8,286,750 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,286,750 - Tesla, Inc. v. Graphite Charging Company LLCNo claims unpatentablePTAB · Aug 19, 2025 · IPR2024-00388 · APJ Ken B Barrett · IPR · Final written decision
Claims 1–20 were not shown unpatentable because Wang and Wang with AESO did not establish the claimed analysis, and Cooley did not disclose reducing current power consumption.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“the claims require a decision engine to perform those elements.” Tr. 48:17– 20. In light of this, we fail to understand the basis for Patent Owner’s objection to the characterization of the level of ordinary skill involving experience with “intelligent” techniques or devices that control grid electricity. We determine that Petitioner’s definition is consistent with the level of ordinary skill reflected in the Specification and the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). We, therefore, apply Petitioner’s definition of the person of ordinary skill in the art. We note, however, that were we to adopt Patent Owner’s assessment, the outcome of this Decision would be the same.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“Patent Owner (PO Resp. 12, 49–50) points to the Specification’s list of “[e]xamples of power reduction actions.” Ex. 1001, 8:47–63. Patent Owner asserts that the list includes numerous examples of power reductions that occur in the present and one that takes place in the future—namely, “scheduling nonessential operations at a different time (e.g., nonessential software or hardware upgrades).” Ex. 1001, 8:61–62 (cited at PO Resp. 12, 50). We are persuaded by Patent Owner’s contention (PO Resp. 12) that the applicant, by including the term “current” in the claims, intentionally narrowed the claims to power consumption reductions that occur temporally in the present, rather than those that occur in the future. See Pet. Reply 6–7 (Petitioner asserting that Patent Owner’s position is “inconsistent with the specification’s examples,” but then arguing that the Specification does not support that position rather than pointing to any purported inconsistencies). Because the independent claims recite the term “current,” construing the term in the temporal sense is not, as Petitioner argues, importing into the claims an example from the Specification. See Pet. Reply 8.” slip op. at 13
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable
“Given the interchangeable nature taught for various features of Wang’s embodiments, it would have been a routine and obvious matter for a POSA to combine aspects from Wang’s various embodiments (e.g., data acquisition, internal hardware, data analysis performed by the UMC receiver 400 and/or the display 200). Moreover, many of Wang’s embodiments–particularly of specific smart appliance types– include common components, thus further confirming combinability of aspects of the disclosed embodiments. A POSA would have had a reasonable expectation of success in combining features of the embodiments together. Id. at 77–78 (citing Ex. 1003 ¶¶ 201–203). We determine that these reasons are inadequate and too generic to satisfy Petitioner’s burden as they lack a clear explanation of what and how “aspects from Wang’s various embodiments” are proposed to be combined along with reasoning specific to that proposal. Petitioner, for example, does not explain adequately or persuasively why a person of ordinary skill in the art would have added a display that purportedly receives and analyzes data to a “smart appliance,” when that appliance already has an application processor that purportedly receives and analyzes the same data. It is not enough for Petitioner to allege that all of the elements of the challenged claims can be found somewhere in the various embodiments of Wang; Petitioner must also show that a person of ordinary skill in the art would have had a reason to combine the elements in the manner as arranged in the challenged claims. See KSR Int’l Co., 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. Although common sense directs one to look with care at a patent application that claims as innovation the combination of two known devices according to their established functions, it can be important to identify a reason that would have prompted a person of ordinary skill in the relevant field to combine the elements in the way the claimed new invention does.”). We find Petitioner has not shown an adequate reason to combine embodiments.” slip op. at 38
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightNot shown unpatentable
“We determine that these reasons are inadequate and too generic to satisfy Petitioner’s burden as they lack a clear explanation of what and how “aspects from Wang’s various embodiments” are proposed to be combined along with reasoning specific to that proposal. Petitioner, for example, does not explain adequately or persuasively why a person of ordinary skill in the art would have added a display that purportedly receives and analyzes data to a “smart appliance,” when that appliance already has an application processor that purportedly receives and analyzes the same data. It is not enough for Petitioner to allege that all of the elements of the challenged claims can be found somewhere in the various embodiments of Wang; Petitioner must also show that a person of ordinary skill in the art would have had a reason to combine the elements in the manner as arranged in the challenged claims. See KSR Int’l Co., 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. Although common sense directs one to look with care at a patent application that claims as innovation the combination of two known devices according to their established functions, it can be important to identify a reason that would have prompted a person of ordinary skill in the relevant field to combine the elements in the way the claimed new invention does.”). We find Petitioner has not shown an adequate reason to combine embodiments.” slip op. at 38
Patent outcomesUS 8,291,243 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,291,243 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Fendgo, LLCNo claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,265,404 - Nokia Of America Corporation / Ericsson Inc. et al. v. General Access Solutions, Ltd.No claims unpatentablePTAB · Apr 14, 2025 · IPR2023-01416 · APJ Ken B Barrett · IPR · Final written decision
The Board held claims 1–15 and 18 not unpatentable; the petition failed to prove the asserted anticipation and obviousness grounds, including failure to establish WiMAX as prior art.
RulingsFinal written decision- Adverse judgmentAdverse judgmentOther
“filed with the Office a statutory disclaimer disclaiming method claims 16, 17, 19, and 20. See Ex. 2007; see also Tr. 33, 21:1–12 (Patent Owner’s counsel informing the Board that the disclaimer had been filed in the USPTO Patent Center, and Petitioner’s counsel having no objection to the filing of the disclaimer as an exhibit in this inter partes review); Tr. 34:19 1 Petitioner identifies Nokia of America Corporation, Ericsson Inc., and T-Mobile USA, Inc. as real parties in interest. Pet. 72. 2 Patent Owner identifies General Access Solutions, Ltd. as the real party in interest. Paper 6, 1. (Patent Owner’s counsel stating, “General Access has disclaimed method Claims 16, 17, 19, and 20.”). We treat disclaimed claims as if they never existed. See Facebook, Inc. v. SKKY, LLC, CBM2016-00091, Paper 12 at 8 (PTAB Sept. 28, 2017) (expanded panel) (precedential) (“The Federal Circuit has held consistently that claims disclaimed under § 253(a) should be treated as though they never existed.”) (citing, inter alia, Vectra Fitness, Inc. v. TWNK Corp., 162 F.3d 1379, 1383 (Fed. Cir. 1998) (“This court has interpreted the term ‘considered as part of the original patent’ in section 253 to mean that the patent is treated as though the disclaimed claims never existed.”); Guinn v. Kopf, 96 F.3d 1419, 1422 (Fed. Cir. 1996) (“A statutory disclaimer under 35 U.S.C. § 253 has the effect of canceling the claims from the patent and the patent is viewed as though the disclaimed claims had never existed in the patent.”)). Accordingly, the remaining claims challenged in this proceeding are apparatus claims 1–15 and method claim 18.” slip op. at 2
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“of both types of parameters to be stored in the same “device” is consistent with the claim language. The claim recites “a profile parameter storage device,” “said profile parameter storage device for storing [two parameter] values,” and refers to “the values stored at said profile parameter storage device.” Ex. 1001, 13:10–16. Accordingly, the claim language speaks of a single device for storing both types of parameters.12 And, Petitioner does” slip op. at 32
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableNot shown unpatentable
“of both types of parameters to be stored in the same “device” is consistent with the claim language. The claim recites “a profile parameter storage device,” “said profile parameter storage device for storing [two parameter] values,” and refers to “the values stored at said profile parameter storage device.” Ex. 1001, 13:10–16. Accordingly, the claim language speaks of a single device for storing both types of parameters.12 And, Petitioner does” slip op. at 32
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication not establishedNot shown unpatentable
“Id. “[A] work is not publicly accessible if the only people who know how to find it are the ones who created it.” Samsung Elecs. Co. v. Infobridge Pte. Ltd., 929 F.3d 1363, 1372 (Fed. Cir. 2019) (citing SRI Int’l, Inc. v. Internet Sec. Sys., Inc., 511 F.3d 1186, 1196 (Fed. Cir. 2008) Application of Bayer, 568 F.2d 1357 (CCPA 1978)). Accordingly, in this case, Petitioner must demonstrate by a preponderance of the evidence that the WiMAX exhibit was disseminated or otherwise made available to interested ordinary artisans outside of the group that created the document. Petitioner has failed to satisfy that burden.” slip op. at 48
Patent outcomesUS 6,947,477 not shown unpatentable§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 6,947,477 - Cellco Partnership D/B/A Verizon Wireless v. General Access Solutions, Ltd.No claims unpatentablePTAB · Dec 23, 2024 · IPR2023-01147 · APJ Ken B Barrett · IPR · Final written decision
Claims 1–6 were not shown unpatentable because the asserted references did not establish that the claimed second transceiver routes information based on monitored signal characteristics.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“A person of ordinary skill in the art (“POSA”) at the time of the purported invention would have had either: (1) a Bachelor of Science degree in computer science, electrical or computer engineering, or a related field, and at least 2 years of work or research experience in digital communications systems, such as wireless communications systems and networks, or equivalent, or a Master’s degree in electrical engineering, computer engineering, computer science or similar field. Additional education could compensate for less practical experience and vice versa. Ex. 1002, ¶¶1-46. Pet. 10. Patent Owner does not address the level of ordinary skill in the art. Cf. Ex. 2007 ¶19 (Patent Owner’s declarant, after acknowledging Petitioner’s definition, stating: “Patent Owner has not offered a different understanding of a POSITA, and the PTAB accepted Petitioner’s submission. I accept and use Petitioner’s and the PTAB’s definition of a POSITA.”). Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“During oral argument, both parties confirmed their respective positions that the claim term “route” needs no construction. See, e.g., Tr. 11:7–9 (Petitioner’s counsel: “Frankly, it doesn’t make any difference to the analysis of the prior art. And so, we don’t believe that the PTAB needs to construe the term route, and so we have not proposed a construction.”); id. at 58:25–59:2 (Patent Owner’s counsel: “You know, I don’t think that you have to define routing in order to decide the case. I think you can do it, you know, just apply whatever plain and ordinary meaning is.”); cf. Tr. 40:14–18 (Patent Owner’s counsel at oral argument: “For the routing itself, you know, there is a District Court construction and that’s a construction that the other—the Petitioner did not ask for determination whether that’s appropriate or not appropriate here. We did not address that as well, so the parties aren’t arguing that that construction should be applied here.”). For the reasons discussed below, we determine that Petitioner has not proven by a preponderance of the evidence that the prior art discloses or teaches, under Petitioner’s articulated theories, that a second transceiver routes information based on monitored characteristics. This is dispositive of the inter partes review. Accordingly, we determine that no claim terms require express construction for purposes of deciding the dispositive issues.” slip op. at 13
- Expert testimonyPatent owner expert creditedDecided for patent owner
“Ex. 1004, 5:25–36 (emphasis added). Thus, Palmer discloses that the determination to roam to another cell may be done by the mobile worker’s wireless communication device 20 having a specifically-programmed processor or may be done centrally, with examples being the “network” or central host processor. We disagree that this constitutes a disclosure of the access point 40 performing the roaming determinations. Rather, we find to be persuasive and credible Dr. Chrissan’s testimony that “a POSITA recognizes that an access point does not qualify as ‘centrally, for example, by the network or a central host processor,’” and, “[i]nstead, this phrase refers to one of the centrally located devices such as network 14 or central host processor 12 (in Fig. 1), or a device in administration building 33 (in Fig. 2).” Ex. 2007 ¶ 71 (citing Ex. 1004, Figs. 1, 2). Dr. Chrissan’s opinion is consistent with Palmer’s disclosure, as we will now discuss.” slip op. at 23
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We determine that Petitioner has not established by a preponderance of the evidence its foundational assertion that Palmer discloses that “access point 40 determines whether roaming by a portable terminal 20 should take place and routes data packets accordingly.” Pet. 26–27; see Technology Licensing Corp. v. Videotek, Inc., 545 F.3d 1316, 1327 (Fed. Cir. 2008) (“Failure to prove the matter as required by the applicable standard means that the party with the burden of persuasion loses on that point—thus, if the fact trier of the issue is left uncertain, the party with the burden loses.”). As such, Petitioner has not met its burden to show that Palmer discloses, as recited in independent claim 1, a second transceiver that, “based on the first signal characteristics and the second characteristics, routes information to the first mobile station and the second mobile station, respectively,” or, as recited in independent claim 6, “based on the first signal characteristics and the second characteristics, routing, using the second transceiver, information to the first mobile station and the second mobile station, respectively.” Ex. 1001, 10:38–44, 11:19–22. The Petition does not contain a contention that this “route” aspect of the claims would have been obvious. Compare Pet. 25–26 (offering an alternative argument for the monitoring aspect; contending that, “to the extent the Board disagrees that Palmer’s access point 40 performs the monitoring, it would have nonetheless been obvious to a POSA to select the access point 40 to perform the monitoring since it directly communicates with the portable terminals 20.”), with id. at 26–27 (making the anticipationtype contention that “[t]he access point 40 routes information” without an alternative obviousness contention); see also Pet. Reply 12–13 (arguing, under the monitoring-and-routing heading, that monitoring by the access point would have been obvious, but not arguing the same for routing). Petitioner has not shown by a preponderance of the evidence that independent claims 1 and 6 and dependent claims 2–4 are anticipated by or would have been obvious over Palmer.” slip op. at 28
Patent outcomesUS 9,426,794 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,426,794
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.