- 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 - Savant Technologies LLC D/B/A GE Lighting / Ledvance LLC et al. v. Feit Electric Company, Inc.All claims unpatentablePTAB · Aug 31, 2026 · IPR2025-00260 · APJ Kevin W Cherry · IPR · Final written decision
The Board held all challenged original claims unpatentable as obvious and denied the contingent motion to amend substitute claims 30–49.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“would have been motivated to combine the teachings of the prior art references to achieve the claimed invention, and that the skilled artisan would have had a reasonable expectation of success in doing so.’” Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1367–68 (Fed. Cir. 2016); see KSR, 550 U.S. at 418. Further, an assertion of obviousness “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; In re NuVasive, Inc., 842 F.3d 1376, 1383 (Fed. Cir. 2016) (a finding of a motivation to combine “must be supported by a ‘reasoned explanation’”).” slip op. at 10
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusObjective indicia outweighedDecided for petitioner
“7. Summary As discussed above, we find that Patent Owner has failed to show a” slip op. at 35
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied
“Motion to Amend meets the statutory and regulatory requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121 for claims 30 and 32–49. We further find that Patent Owner has not met the statutory and regulatory requirements for proposed claim 31. Accordingly, we address below whether any of the proposed substitute claims have been shown to be unpatentable.” slip op. at 86
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateDenied
Patent outcomesUS 8,604,678 unpatentable§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,604,678 - Savant Technologies LLC D/B/A GE Lighting / Ledvance LLC et al. v. Feit Electric Company, Inc.All claims unpatentablePTAB · Aug 31, 2026 · IPR2025-00260 · APJ Kevin W Cherry · IPR · Final written decision
The Board held all challenged claims 1–3, 6, 7, 9–14, 16–21, 25, 26, and 29 unpatentable as obvious and granted the motion to amend for substitute claims 30–49.
RulingsFinal written decision- Expert testimonyPetitioner expert creditedDecided for petitioner
“E. Credibility of Dr. Doolittle Patent Owner argues that we should give no weight to Dr. Doolittle’s testimony because, “[o]n cross examination, Prof. Doolittle repeatedly contradicted himself, dodged questions, and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions.” PO Resp. 25. Patent Owner raises two major complaints about Dr. Doolittle. First, Patent Owner argues that he took inconsistent positions by asserting in these IPR proceedings that the claims were entitled to their plain and ordinary meaning, while in the parallel district court proceeding, asserting that certain claim terms were indefinite. Id. at 26–28. Second, Patent Owner argues that Dr. Doolittle “repeatedly dodged questions and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions,” and that “[d]uring cross examination Patent Owner was forced to object to Prof. Doolittle’s nonresponsive answers no less than eighteen times.” Id. at 28. We strongly disagree with Patent Owner’s characterization of Dr. Doolittle’s testimony. We have reviewed the entirety of both of Dr. Doolittle’s depositions. We are impressed with his forthrightness, candor, and good humor in the face of Patent Owner’s counsel’s aggressive questioning. Contrary to Patent Owner’s assertions, we find that his testimony was well-reasoned, forthright, honest, and entitled to significant weight. Dr. Doolittle explained the different claim construction positions We also strongly disagree that Dr. Doolittle’s answers were nonresponsive or “evasive” as Patent Owner argues. Patent Owner’s numerous attempts to “strike” portions of his testimony belie Dr. Doolittle’s efforts to honestly and in good faith respond to Patent Owner’s counsel’s questions. Ex. 2025, 22:10–23:15, 25:9–26:14, 30:14–22, 40:3-9, 58:12–59:1, 60:18–61:13, 65:1–10, 83:15–84:16, 92:15–95:20, 96:18–99:9, 102:22–106:16, 135:3–136:22. An answer is not “non-responsive” simply because it does not conform to the conclusion you want or undermines the logic underlying your questioning. Dr. Doolittle explained his answers and addressed the issues Patent Owner asked about. Accordingly, we decline Patent Owner’s invitation to give Dr. Doolittle’s testimony no weight. Instead, we assess Dr. Doolittle’s testimony on a case-by-case basis as discussed below.” slip op. at 21
- Skill levelOther
“B. Level of Ordinary Skill in the Art We consider the asserted ground of unpatentability in view of the understanding of a person of ordinary skill in the art (“POSITA” or “POSA”). 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 Relying on the declaration testimony of its expert, Dr. Doolittle, Petitioner contends that an ordinarily skilled artisan for the ’678 patent “would have had an undergraduate degree (i.e., B.S., B.S.E. or the equivalent) in electrical engineering, materials science, physics, or a similar discipline” and “would also have one to two years of experience in the field of LED packaging design.” Pet. 5–6. Petitioner additionally contends that “[m]ore education could substitute for experience, and vice versa.” Id. Petitioner further contends that “[t]his person would have been capable of understanding and applying the teachings of the ’678 patent and the prior-art references discussed herein,” and “[m]oreover, the prior art reflects the level of skill at the time of the claimed invention.” Id. (citing Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); Ex. 1102 ¶¶ 38–42). Patent Owner states that “solely for the purposes of this proceeding, Patent Owner and its technical expert employ the same level of skill in the art as Petitioners.” PO Resp. 24–25. Thus, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’678 patent and the asserted prior art, and we apply it in our obviousness analysis below.” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“lower wavelength might offer, there were other drawbacks that a person of ordinary skill would have to balance. But “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006). Indeed, Petitioner has shown several references—including, Basin-2005, Shimizu, and Stokes—that made this tradeoff. Moreover, “[o]bviousness does not require absolute predictability of success. . . . [A]ll that is required is a reasonable expectation of success.” In re O’Farrell, 853 F.2d 894, 903–04 (Fed. Cir. 1988). We find that the prior art of record demonstrates that a person of ordinary skill in the art at the time of the invention would have such an expectation in making the combination of Basin-2007 and Basin-2005. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that there would have been motivation to combine Basin-2007 and Basin-2005 with a reasonable expectation of success. 4. Summary We have reviewed Petitioner’s contentions regarding claims 1–3, 6, 9, 10, 16–21, and 25 (Pet. 19–53), and find that Petitioner has shown by a preponderance of the evidence that Basin-2007 and Basin-2005 teach the limitations of those claims, and that there would have been a motivation to combine the references in the manner suggested with a reasonable considerations does not outweigh the strong showing of obviousness. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that claims 1–3, 6, 9, 10, 16–21, and 25 would have been obvious over Basin-2007 and Basin-2005.” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusDecided for petitioner
“1. Nexus In order for secondary considerations to be awarded “substantial” slip op. at 22
Patent outcomesUS 8,604,678 unpatentable§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,604,678 - Savant Technologies LLC D/B/A GE Lighting And Ledvance LLC / Savant Technologies LLC D/B/A GE Lighting, Elong International USA Inc., And Xiamen Longstar Lighting Co. Ltd v. Feit Electric Company, Inc.All claims unpatentablePTAB · Aug 31, 2026 · IPR2024-01357 · APJ Kevin W Cherry · IPR · Final written decision
The Board held all challenged original claims unpatentable as obvious and granted the contingent motion to amend for substitute claims 30 and 32–49; substitute claim 31 was denied.
RulingsFinal written decision- Expert testimonyPetitioner expert creditedDecided for petitioner
“E. Credibility of Dr. Doolittle Patent Owner argues that we should give no weight to Dr. Doolittle’s testimony because, “[o]n cross examination, Prof. Doolittle repeatedly contradicted himself, dodged questions, and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions.” PO Resp. 25. Patent Owner raises two major complaints about Dr. Doolittle. First, Patent Owner argues that he took inconsistent positions by asserting in these IPR proceedings that the claims were entitled to their plain and ordinary meaning, while in the parallel district court proceeding, asserting that certain claim terms were indefinite. Id. at 26–28. Second, Patent Owner argues that Dr. Doolittle “repeatedly dodged questions and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions,” and that “[d]uring cross examination Patent Owner was forced to object to Prof. Doolittle’s nonresponsive answers no less than eighteen times.” Id. at 28. We strongly disagree with Patent Owner’s characterization of Dr. Doolittle’s testimony. We have reviewed the entirety of both of Dr. Doolittle’s depositions. We are impressed with his forthrightness, candor, and good humor in the face of Patent Owner’s counsel’s aggressive questioning. Contrary to Patent Owner’s assertions, we find that his testimony was well-reasoned, forthright, honest, and entitled to significant weight. Dr. Doolittle explained the different claim construction positions We also strongly disagree that Dr. Doolittle’s answers were nonresponsive or “evasive” as Patent Owner argues. Patent Owner’s numerous attempts to “strike” portions of his testimony belie Dr. Doolittle’s efforts to honestly and in good faith respond to Patent Owner’s counsel’s questions. Ex. 2025, 22:10–23:15, 25:9–26:14, 30:14–22, 40:3-9, 58:12–59:1, 60:18–61:13, 65:1–10, 83:15–84:16, 92:15–95:20, 96:18–99:9, 102:22–106:16, 135:3–136:22. An answer is not “non-responsive” simply because it does not conform to the conclusion you want or undermines the logic underlying your questioning. Dr. Doolittle explained his answers and addressed the issues Patent Owner asked about. Accordingly, we decline Patent Owner’s invitation to give Dr. Doolittle’s testimony no weight. Instead, we assess Dr. Doolittle’s testimony on a case-by-case basis as discussed below.” slip op. at 21
- Skill levelOther
“B. Level of Ordinary Skill in the Art We consider the asserted ground of unpatentability in view of the” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“lower wavelength might offer, there were other drawbacks that a person of ordinary skill would have to balance. But “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006). Indeed, Petitioner has shown several references—including, Basin-2005, Shimizu, and Stokes—that made this tradeoff. Moreover, “[o]bviousness does not require absolute predictability of success. . . . [A]ll that is required is a reasonable expectation of success.” In re O’Farrell, 853 F.2d 894, 903–04 (Fed. Cir. 1988). We find that the prior art of record demonstrates that a person of ordinary skill in the art at the time of the invention would have such an expectation in making the combination of Basin-2007 and Basin-2005. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that there would have been motivation to combine Basin-2007 and Basin-2005 with a reasonable expectation of success. 4. Summary We have reviewed Petitioner’s contentions regarding claims 1–3, 6, 9, 10, 16–21, and 25 (Pet. 19–53), and find that Petitioner has shown by a preponderance of the evidence that Basin-2007 and Basin-2005 teach the limitations of those claims, and that there would have been a motivation to combine the references in the manner suggested with a reasonable considerations does not outweigh the strong showing of obviousness. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that claims 1–3, 6, 9, 10, 16–21, and 25 would have been obvious over Basin-2007 and Basin-2005.” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“1. Nexus In order for secondary considerations to be awarded “substantial” slip op. at 22
Patent outcomesUS 8,604,678 unpatentable§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,604,678 - Savant Technologies LLC D/B/A GE Lighting / Ledvance LLC et al. v. Feit Electric Company, Inc.All claims unpatentablePTAB · Aug 28, 2026 · IPR2024-01357 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–3, 6, 7, 9, 10, 16–21, 25, 26, and 29 are unpatentable; substitute claims 30–49 were not reached.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art We consider the asserted ground of unpatentability in view of the” slip op. at 10
- Expert testimonyPetitioner expert creditedDecided for petitioner
“E. Credibility of Dr. Doolittle Patent Owner argues that we should give no weight to Dr. Doolittle’s testimony because, “[o]n cross examination, Prof. Doolittle repeatedly contradicted himself, dodged questions, and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions.” PO Resp. 25. Patent Owner raises two major complaints about Dr. Doolittle. First, Patent Owner argues that he took inconsistent positions by asserting in these IPR proceedings that the claims were entitled to their plain and ordinary meaning, while in the parallel district court proceeding, asserting that certain claim terms were indefinite. Id. at 26–28. Second, Patent Owner argues that Dr. Doolittle “repeatedly dodged questions and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions,” and that “[d]uring cross examination Patent Owner was forced to object to Prof. Doolittle’s nonresponsive answers no less than eighteen times.” Id. at 28. We strongly disagree with Patent Owner’s characterization of Dr. Doolittle’s testimony. We have reviewed the entirety of both of Dr. Doolittle’s depositions. We are impressed with his forthrightness, candor, and good humor in the face of Patent Owner’s counsel’s aggressive questioning. Contrary to Patent Owner’s assertions, we find that his testimony was well-reasoned, forthright, honest, and entitled to significant weight. Dr. Doolittle explained the different claim construction positions We also strongly disagree that Dr. Doolittle’s answers were nonresponsive or “evasive” as Patent Owner argues. Patent Owner’s numerous attempts to “strike” portions of his testimony belie Dr. Doolittle’s efforts to honestly and in good faith respond to Patent Owner’s counsel’s questions. Ex. 2025, 22:10–23:15, 25:9–26:14, 30:14–22, 40:3-9, 58:12–59:1, 60:18–61:13, 65:1–10, 83:15–84:16, 92:15–95:20, 96:18–99:9, 102:22–106:16, 135:3–136:22. An answer is not “non-responsive” simply because it does not conform to the conclusion you want or undermines the logic underlying your questioning. Dr. Doolittle explained his answers and addressed the issues Patent Owner asked about. Accordingly, we decline Patent Owner’s invitation to give Dr. Doolittle’s testimony no weight. Instead, we assess Dr. Doolittle’s testimony on a case-by-case basis as discussed below.” slip op. at 21
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“lower wavelength might offer, there were other drawbacks that a person of ordinary skill would have to balance. But “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006). Indeed, Petitioner has shown several references—including, Basin-2005, Shimizu, and Stokes—that made this tradeoff. Moreover, “[o]bviousness does not require absolute predictability of success. . . . [A]ll that is required is a reasonable expectation of success.” In re O’Farrell, 853 F.2d 894, 903–04 (Fed. Cir. 1988). We find that the prior art of record demonstrates that a person of ordinary skill in the art at the time of the invention would have such an expectation in making the combination of Basin-2007 and Basin-2005. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that there would have been motivation to combine Basin-2007 and Basin-2005 with a reasonable expectation of success.” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerationsDecided for petitioner
“7. Summary As discussed above, we find that Patent Owner has failed to show a” slip op. at 35
Patent outcomesUS 8,604,678 unpatentable§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,604,678 - 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 - Rocket Media, LLC D/B/A Launch Labs v. Fullthrottle Technologies, LLCAll claims unpatentablePTAB · Jun 9, 2026 · IPR2025-00148 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Doughty and Van Boucq, and over Doughty, Van Boucq, and Maginnis.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art in June 2021 would have had “(1) at least a bachelor’s degree in computer science, computer engineering, electrical engineering, or an equivalent field plus at least one year of experience working on computer networking, or (2) at least 3 years of experience working on computer networking, even without a formal degree.” Pet. 14 (citing Ex. 1007 ¶¶ 44–47). Patent Owner does not contest Petitioner’s proffered definition. PO Resp. 23. Petitioner’s proposed definition appears to be consistent with the disclosure of the ’947 patent, and we adopt it for purposes of this Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that the prior art itself may “reflect[] an appropriate level” of ordinary skill in the art) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“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, but address certain claim construction arguments made by the parties in the analysis below. See id.; Inst. Dec. 11 (determining that “no express claim construction is necessary for any claim terms”); PO Resp. 23 (agreeing that “no express constructions are necessary to resolve this IPR”). slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageDisclaimer not foundDecided for petitioner
“We find that Petitioner has shown that the combination of Doughty and Van Boucq accounts for these limitations. We are not persuaded by Patent Owner’s arguments that claim 1 somehow excludes, what Patent Owner calls, the “Unique Identifier/Tracker Embodiment.” See PO Resp. 27, 31. Beginning with the language of the claims, the claims are silent as to where the “location data” recited in limitation 1[c] is stored. See Tr. 21:7– 16 (Patent Owner agreeing that “the stored location data does not actually have a required location at all” in the claim, and need not be stored in a database). Nor does Patent Owner direct us to any claim language that would specifically exclude “location data” stored on the user’s device. See Sur-reply 2–3. “The patentee is free to choose a broad term and expect to obtain the full scope of its plain and ordinary meaning unless the patentee clearly redefines the term (lexicography) or disavows claim scope (claim disavowal).” Aortic Innovations LLC v. Edwards Lifesciences Corp., 159 F.4th 1, 8 (Fed. Cir. 2025) (citing Thorner v. Sony Comput. Ent. Am. LLC, 669 F.3d 1362, 1367 (Fed. Cir. 2012)). Patent Owner directs us to statements in the Specification, stating “[f]or example, the computing device may access a database or other storage location that maintains a mapping of unique identifier to a browser session, a user computing device, and/or location data.” Ex. 1001, 9:52–55; see also id. at 39:26–30 (same), 43:55– 59 (same). But none of those passages amounts to lexicography or disavowal of claim scope. Indeed, when read in their full context, these passages support a broad reading, not a narrow reading, of the claims. The full passage of the Specification states: The computing device may determine, at 406, whether there is a unique identifier that is associated with the user (e.g., the user computing device, the browser, and/or the browser session) stored on the computing device. For example, the script may inform the computing device that there is no unique identifier for the user computing device. The computing device may determine that there is no unique identifier associated with the user computing device when there is no location data stored for the user computing device. For example, the computing device may access a database or other storage location that maintains a mapping of unique identifier to a browser session, a user computing device, and/or location data. Additionally or alternatively, the computing device may determine whether there is a unique identifier for associated with the user based on presence of a location tracker (e.g., cookie) installed in the browser application on the user computing device. Ex. 1001, 9:43–59. The passage above is full of language that indicates that the patentee did not intend to limit the claims to a single embodiment. Indeed, the specific portion of the passage cited by Patent Owner begins with “[f]or example” and further states “[a]dditionally or alternatively, the computing device may determine whether there is a unique identifier for associated with the user based on presence of a location tracker (e.g., cookie) installed in the browser application on the user computing device.” Id. at 9:52–59 (emphasis added). Moreover, the Specification states “[a]dditionally or alternatively, the computing device may determine the location data using the tracker installed in the browser application on the user computing device.” Id. at 10:2–5. The Specification also explains that the tracker may “maintain data related to the user and/or user computing device.” Id. at 12:62–63. Based on these disclosures, we find that the Specification supports a reading where the location data are stored in the user computing” slip op. at 25
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“We find persuasive Petitioner’s reasoning that a POSITA would have been motivated to modify Doughty, based on Doughty’s own teachings regarding cookies and similar files, and would have recognized that the techniques of Van Boucq would have offered an efficient and commonly used way to determine whether the user already has been assigned a unique identifier. See Ex. 1007 ¶ 153. Patent Owner’s arguments about the precise contents of Van Boucq’s connection cookie attack Van Boucq individually and ignore the combination and modifications that Petitioner proposes. In the combination, Petitioner proposes incorporating the unique identifier from Doughty into Van Boucq’s connection cookie. See Pet. 26 (citing Ex. 1008, 16:59–17:33; Ex. 1007 ¶ 153). As for Patent Owner’s contention that “[n]othing in the record suggests that Van Boucq’s connection cookie could contain any information about either Doughty’s table 105 Profile ID or Doughty’s hashed email address,” PO Resp. 33, as Dr. Gottesman testifies, “[a] cookie is a small piece of data (text file).” Ex. 2012 ¶ 55. We fail to see why a skilled artisan at the time of the invention would have any difficulty incorporating Doughty’s alphanumeric unique identifier into a text file. See Ex. 1007 ¶¶ 153, 166. Thus, we find that Petitioner has shown a motivation to combine Doughty and Van Boucq for these limitations.” slip op. at 30
Patent outcomesUS 11,556,947 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,556,947 - Digital Global Systems, Inc. v. Deepsig, Inc.Some claims unpatentablePTAB · Mar 6, 2026 · IPR2024-01358 · APJ William V Saindon · IPR · Final written decision
Claims 1–3, 7–11, 15–19, 23, and 24 are unpatentable as obvious; claims 4–6, 12–14, and 20–22 were not shown unpatentable because the prior art did not teach the claimed received-signal feedback and transmitter-model update.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts that: Persons of ordinary skill in the art (“POSITA”) would have a bachelor’s degree in electrical engineering, computer engineering, or an equivalent degree and at least two years of experience working with of radio communication systems and machine learning. Additional work or research experience can substitute for less or different education, and vice-versa. Pet. 3–4 (citing Ex. 1003 ¶¶ 33–34). Patent Owner does not appear to challenge this level of skill. We use Petitioner’s definition for purposes of this Decision because it appears consistent with the level of skill reflected in the prior art and ’704 patent.” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“parameters “associated with the base station.” PO Resp. 31–32. In particular, Patent Owner argues that a transmitter “implemented in a base station” is not “associated with the base station.” Id. at 31. Petitioner argues that Patent Owner offers no reason to believe that a transmitter “implemented in a base station” is not “associated with the base station.” Pet. Reply 4–5; see also id. at 3–6 (entire argument). A plain reading of a “model associated with a base station” would encompass a model that operates in a base station. We do not see anything in the ’704 specification that would indicate “associated with” has any special meaning, or has a meaning contrary to our understanding of the plain meaning. We do not see the word “associated” outside the claims, whereas we see the word “implement” throughout the specification, generally in reference to an actual use of a model (consistent with our plain reading). See, e.g., Ex. 1001, 5:35–39, 6:3–17, 10:55–11:3 (discussing “implementations” where the model or some other feature of the system is used in a particular way). Accordingly, we construe a model “implemented in a base station” to be “associated with the base station.”” slip op. at 12
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“scenarios” (see PO Resp. 16–21), Patent Owner argues that “Jüschke does not disclose any association of the weight or bias parameters, . . . to any deployment scenario, and . . . base station” (id. at 19). For the reasons explained in our claim construction section above, we construe “deployment scenarios” to include “inline mode” models located within a base station, according to the list of deployment scenarios set out in the ’704 patent. See Ex. 1001, 2:38–65. The in-line deployment scenario depicted in Figure 6A of the ’704 patent bears a striking resemblance to the arrangement depicted in Figure 1 of Jüschke. In both figures, the analog radio signal is fed directly into the model and then the model directly outputs the signal to the amplifier. Compare Ex. 1001, Fig. 6A, with Ex. 1005, Fig. 1. As construed, the “deployment scenarios” represent the physical configurations of the device in which the model is found, such as “in-line.” Petitioner shows by a preponderance of the evidence that Jüschke’s similar in-line configuration is a “deployment scenario” as claimed because it teaches an inline model for a cellular system transmitter (i.e., base station). Pet. 26–29 (citing, e.g., Ex. 1005, Fig. 1, ¶¶ 6, 59; Ex. 1003 ¶¶ 146–147); see also Ex. 1001, 2:37–41 (stating that “[t]he particular deployment scenario[] may be . . . sending a radio transmission from a cellular base station that includes the . . . model . . . in an inline mode”).” slip op. at 26
- BurdenNot shown unpatentable
“Based on our claim construction analysis of claim 4, above, we agree with Patent Owner that claim 4 requires an actually transmitted signal and an update of the transmitter’s model. This claim construction eliminates Petitioner’s position regarding Holt teaching a modeled signal. See, e.g., Pet. Reply 17–23. We then turn to Petitioner’s argument that Holt teaches updating a model using an actually transmitted signal. See Pet. 59–60. There, Petitioner relies on a disclosure in Holt of an “actual communication channel 302 used to train the channel model 208.” Ex. 1006, 18:1–2. This is depicted in Figure 6 of Holt, in connection with a “fourth loss function” which is used to “train the decoder model.” Id. at 18:42–48; see generally id. at 17:58–18:51 (describing Figure 6). Whether training the channel model or the decoder model, Holt here does not disclose using the actual communication channel to train the encoder, i.e., transmitter. In sum, we find that Petitioner has not shown by a preponderance of the evidence that the prior art describes the claimed step of “obtaining a received radio signal,” and even if it did, Petitioner has not shown by a preponderance of the evidence that the prior art describes the claimed step of “updating the value of the model parameters” in the manner required by claim 4. Claims 12 and 20 are nearly identical to claim 4, and Petitioner’s ground fails for similar reasons. See Pet. 76. Claims 5, 6, 13, 14, 21 and 22 depend from claims 4, 12, and 20, and Petitioner’s ground fails for similar reasons as those claims. See id. at 77–80.” slip op. at 31
Patent outcomesUS 11,018,704 mixedClaim construction§ 103 obviousnessPatents in suitUS 11,018,704
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.