- Microsoft Corporation v. Sterling Computers CorporationAll claims unpatentablePTAB · Sep 14, 2026 · IPR2025-00270 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–13, 15, 18, 20, 21, and 27 are unpatentable as obvious over Rohall and Schiavone, with Gomes added for claims 9 and 27.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Our Institution Decision adopted Petitioner’s definition of a person of ordinary skill in the art. Inst. Dec. 9–10. In its Response, Patent Owner adopts Petitioner’s proposed level of ordinary skill. See PO Resp. 16 (“Patent Owner and its expert adopt the Board’s definition for purposes of this Response.”). Having considered the record, we continue to adopt Petitioner’s proposed level of skill, as articulated above. We are satisfied that Petitioner’s proposal comports with the level of skill necessary to understand and implement the teachings of the ’911 Patent. Accord Inst. Dec. 9–10.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We agree with Petitioner and determine that the construction of “relational references” does not require the use of a relational model and, further, includes pointers that point to related messages exchanged among users. The intrinsic evidence leads us to this construction. First, the relevant language of claim 1 recites “a message container containing relational references pointing to a plurality of sent submessages stored externally to the message container in the message database.” Ex. 1001, 15:56–59. A relational model is not recited in that language or anywhere else in the claim. See id. at 15:51–16:14. Therefore, the claim does not expressly require a relational model. Furthermore, the claim language supports Petitioner’s interpretation that “relational references” include pointers that point to related messages because the claim states that the “relational references” perform the task of “pointing to a plurality of sent submessages.” Pet. Reply 7. Accordingly, the language of the claim supports a construction that does not require a relational model and at least suggests relational references include pointers.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“No other claim terms need construction for our decision here and we decline unnecessarily doing so. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentableDecided for petitioner
“We agree with Petitioner that the ordinarily skilled artisan would have been motivated to combine Rohall and Schiavone because Schiavone provides reasons to apply its techniques to email systems such as Rohall’s. Schiavone describes a need for “ensuring compliance of e-mail messages with applicable standards and/or laws and/or otherwise determining appropriateness of a message for an intended recipient,” especially because there is “a patchwork of local, federal and international laws.” Ex. 1006 ¶ 6. Schiavone also states that filtering emails, e.g., to remove spam, is beneficial. Id. ¶¶ 1–2. As Schiavone describes problems in email systems, which its rules-based email processing technique addresses, we determine that the ordinarily skilled artisan would have been motivated to combine Rohall and Schiavone. See KSR, 550 U.S. at 401 (a reference which teaches, suggests, or motivates its combination may “identify a reason that would have prompted a person of ordinary skill in the art to combine the elements”).” slip op. at 19
Patent outcomesUS 8,073,911 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 8,073,911 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 1, 2026 · IPR2025-00914 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–19 are unpatentable as obvious over Menon, Trefethen, RS6000, and POEref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In determining 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) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’679 patent, the prior art of record, and the testimony of both experts.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Petition relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard. Pet. 12–13 (citing 37 C.F.R. § 42.100(b)). The Petition also addresses the construction of “peer-to-peer architecture” recited in independent claim 1 of the ’679 patent, a limitation we need not construe to resolve the parties’ dispute in this proceeding. Id. at 13; see, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Owner relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard without further analysis. Resp. 7.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“RS6000 with Menon, namely because RS6000 provides an overview of the IBM SP2 multiprocessor and Menon teaches the use of “IBM SP2, a modern high performance distributed memory multiprocessor” used in the MultiMATLAB system. Id. at 24–25 (citing Ex. 1003 ¶¶ 142–145; Ex. 1005, 5–6, 14; Ex. 1007, 1, 11). The Petition also explains why POEref pertains to the field of cluster computing in a parallel operating environment. Id. at 26 (citing Ex.1008, 11 (“PE Software is designed to run on an … RS/6000 network cluster”)); (further citing Ex. 1001, 1:14–15; Ex. 1003 ¶¶ 146–149). The Petition contends that a POSITA would have been motivated to combine the teachings of POEref with Menon “because Menon suggests the combination by teaching that MultiMATLAB uses ‘POE, IBM's Parallel Operating Environment.’” Id. at 26–27 (citing Ex. 1005, 6); (further citing Ex. 1003 ¶¶ 150–153; Ex. 1005, 14; Ex. 1008, 11, 46). We agree with Petitioner’s analysis. We find the Petition’s argument and evidence of a motivation to combine the asserted prior art references in the manner claimed to be compelling, persuasive, consistent with the disclosures in the references, which include internal cross-references to each other, and supported by the expert testimony of Dr. Bajaj.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner
“skill, upon reading the reference, would be discouraged from following the path set out in the reference, or would be led in a direction divergent from the path that was taken by the applicant.” In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). Patent Owner argues that Menon teaches away from a combination with Trefethen because “Menon expressly states that Trefethen’s first-generation architecture is inadequate for the objectives that motivated the newer design.” Resp. 35–37. The evidence does not support Patent Owner’s position. First, Patent Owner’s teaching away argument is inconsistent with the strong evidence of a motivation to combine Menon and Trefethen discussed above. Second, Patent Owner’s teaching away argument is contrary to the evidence of record for the reasons given in Petitioner’s Reply. Reply 13–15 (e.g., “Menon explicitly cites Trefethen and explains that Menon builds on the teachings of Trefethen.”) (citing Pet. 22; Ex. 1003 ¶ 70; Ex. 1005, 1–3; Ex. 1163 ¶¶ 47–53). We are further persuaded by Dr. Bajaj’s reply testimony: the “MultiMATLAB teachings in Trefethen. In fact, Menon describes enhancing the system of Trefethen. For example, Menon describes a list of “goals” already achieved by MultiMATLAB and then states that the architecture has been “redesigned to achieve two further goals.” One of these two “further goals” is “extensibility,” which Menon achieves by its description of adding “MEX routines” to the system of Trefethen. Far from showing an “incompatibility” between Menon and Trefethen as the POR argues, Menon’s addition of the “MEX routines” to MultiMATLAB shows that such a modification was within the capabilities of a POSITA, because the authors of the Menon paper actually implemented the modification. Ex. 1163 ¶ 49 (citing Ex. 1005, 1–3). Dr. Bajaj’s testimony is unrebutted, credible, and supported by the record. We agree with Dr. Bajaj’s reasoning, which is based on direct quotes in Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶¶ 50–52. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine the teachings of Menon and Trefethen. RS6000 and POEref are specifically referenced in Menon-Trefethen and add operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Such facts are inconsistent with Patent Owner’s teaching away and lack of motivation arguments.” slip op. at 24
Patent outcomesUS 12,021,679 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 12,021,679 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Aug 26, 2026 · IPR2025-00913 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–25, 27–28, and 30 as obvious over Menon, Trefethen, RS6000, and POEref; claims 26 and 29 over those references plus MPIref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“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) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and experience of a POSITA. We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’034 patent, the prior art of record, and the testimony of both experts.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther
“processor,” “multi-core” processor, or “singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’” as Patent Owner contends. Resp. 11–12, 21; see also Ex. 1163 ¶ 22 (“The claim does not recite ‘single chip,’ ‘single package,’ ‘single die,’ or ‘single multi-core microprocessor.’”). Nor do the claims recite a plurality of processing cores “within” a single-chip package or read as “multi-core within a processor” as argued by Patent Owner. Resp. 12–14; Sur-Reply 2; see Reply 6 (citing Ex. 1163 ¶ 23 (“Thus, the phrase ‘with a plurality of processing cores’ identifies the required processing resources associated with the hardware processor; it does not import a packaging limitation.”)). The claims do recite a hardware processor “with” a plurality of processing cores; a critical distinction even Patent Owner reads as open-ended, i.e., as a hardware processor that “comprises” a plurality of processing cores. See Resp. 11 (“the claims require a singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’”). Consequently, the claim language does not support Patent Owner’s proposed construction of “a . . . hardware processor with a plurality of processing cores” as a single multi-core processor. cores it contains” in reliance on a parsed description in the ’034 patent specification: The specification explains: “Each processor can contain one or more processor cores that are capable of single-threaded execution. Processor cores are generally independent microprocessors, but more than one can be included in a single-chip package.” Id. at 1212 (partially quoting Ex. 1001, 5:11–16); Sur-Reply 2. The quoted description does not support Patent Owner’s contention that the claimed “a . . . hardware processor with a plurality of processing cores” must be limited to a “single multi-core processor” that “locates multiple cores within a ‘single-chip package,’” i.e. limited to a single multi-core microprocessor such as “a Core 2 Duo is one processor package with two cores.” Resp. 12– 13, 21 (citing Ex. 1001, 7:15–25). The description quoted above from column 5, moreover, describes a “processor” that “can contain one or more processor cores” each of which can be an independent microprocessor. Reply 2–3 (citing Ex. 1001, 5:11–16; Ex. 1163 ¶¶ 10–14). As Petitioner emphasizes, the specification distinguishes a “processor” from a “microprocessor” and describes a “processor” that “can be one or more general purpose single-core or multi-core microprocessors,” rather than limiting a “processor” to a single multi-core microprocessor. Reply 3–5 (citing Ex. 1001, 7:14–36, Fig. 1; Ex. 1163 ¶¶ 15–18).” slip op. at 13
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“art because they pertain to the same “field of cluster computing” as the ’034 patent and “are reasonably pertinent to the problem of the ’034 patent, namely, executing a single program on multiple nodes.” Pet. 22 (citing Ex. 1001, 1:14–15; Ex. 1003, ¶¶ 65–69; Ex. 1005, 2; Ex. 1006, Abstract). The Petition emphasizes that Menon expressly cites and builds on the MultiMATLAB system taught by Trefethen. Id. (citing Ex. 1003 ¶ 71; Ex. 1005, 1–2). The Petition contends that: combination of prior art elements according to known methods (executing MATLAB code on a multiprocessor system) to yield the predictable result discussed in both papers: the MultiMATLAB system executing MATLAB in parallel to perform mathematical calculations. Id. at 22–23 (citing Ex. 1003 ¶ 70; Ex. 1005, Abstract; Ex. 1006, 2–7). The Petition further contends that a POSITA would have found it predictable to combine Trefethen with Menon with a reasonable expectation of success “because researchers had a strong desire to parallelize MATLAB.” Id. at 23–24 (citing Ex. 1003 ¶ 73; Ex. 1005, 2; Ex. 1006, 11–12.)” slip op. at 27
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“A POSITA would have had an especially strong reason to read these references together because they address the same project, the same MATLAB-based parallel-computing problem, and the same MultiMATLAB command environment. Menon expressly identifies Trefethen’s MultiMATLAB work and then describes a redesigned architecture that preserves the same user-level objective––parallel MATLAB computations—while improving implementation details and extensibility. A POSITA therefore would not view the references as mutually exclusive alternatives. Rather, a POSITA would understand Trefethen as teaching specific MultiMATLAB commands and examples, including Eval, Send, Recv, and the architecture was implemented and improved in a later version. Ex. 1163 ¶¶ 71–72 (emphases added). We find the above reasoning persuasive and adopt it as our own. Petitioner and Dr. Bajaj demonstrate a sound technical motivation for a POSITA—someone having a bachelor’s degree in computer science, computer engineering, or electrical engineering and two years of experience working in the field of cluster computing or parallel processing—to combine Menon and Trefethen: to improve MATLAB’s operational performance and extensibility in a parallel operating environment. Menon builds on Trefethen to improve and extend the parallel processing capabilities of MultiMATLAB: “This system will enable users to access high-performance parallel routines from within the MATLAB environment, to extend the environment with new parallel routines, and to use these routines to develop parallel applications with the MATLAB language.” Ex. 1005 Abstract. Menon is intended to be read in conjunction with Trefethen, as would be expected from two references generated by the same research group at the same university addressed to the same technical subject matter about a year apart. Ex. 1005, 1; Ex. 1006, Ex. 1086 ¶¶ 65, 101, 102. The very first citation in Menon is to Trefethen. Ex. 1005, 2, 16.” slip op. at 30
Patent outcomesUS 11,570,034 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,570,034 - Meta Platforms, Inc. v. Sterling Computers CorporationAll claims unpatentablePTAB · Aug 3, 2026 · IPR2025-00430 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–3, 5–9, 13–15, 18, 19, and 22 are unpatentable as obvious over Dumais, Rose, and Rose with Bieganski.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Our Institution Decision adopted Petitioner’s definition of a person of ordinary skill in the art. Inst. Dec. 7–8. In its Response, Patent Owner adopts Petitioner’s proposed level of ordinary skill. See PO Resp. 13–14 (“Patent Owner and its expert adopt the Board’s definition for purposes of this Response”). Having considered the record, we continue to adopt Petitioner’s proposed level of skill, as articulated above. We are satisfied that Petitioner’s proposal comports with the level of skill necessary to understand and implement the teachings of the ’217 Patent. Accord Inst. Dec. 7–8.” slip op. at 8
- ExcludeMotion to exclude, deniedOther
“We have not considered any of the evidence Patent Owner moves to exclude in reaching our findings and conclusions set for in this Decision. As a result, Patent Owner’s Motion to Exclude this evidence is dismissed as moot.” slip op. at 55
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference is prior artPriority date, deniedDecided for petitioner
“We determine that Patent Owner has not carried its temporary burden of production to support its contention that the inventors were reasonably diligent throughout the critical period. See Parus Holdings, 70 F.4th at specifically cite the relevant record evidence combined with an explanation of the significance of the produced material in briefs. See id. at 1372 (explaining that “[t]he burden of production cannot be met without some combination of citing the relevant record evidence with specificity and explaining the significance of the produced material in briefs”). Patent Owner states that it “submitted extensive evidence.” PO Sur-reply 14. But simply submitting dozens of exhibits is not enough. As our reviewing court has admonished, the “burden of production cannot be met simply by throwing mountains of evidence at the Board without explanation or identification of the relevant portions of that evidence.” See Parus Holdings, 70 F.4th at 1371. Instead of citing what specific portions of those exhibits are relevant and why, Patent Owner cites entire exhibits and asserts, without analysis or explanation, that they show diligence. See PO Resp. 49– 50 (citing numerous exhibits without pinpoint citations). Patent Owner’s Sur-reply asserts that Patent Owner’s Response was adequate (PO Sur-reply 17), but an examination of the Response shows that it was not. For example, in its Response, Patent Owner states “numerous documents corroborating [the inventors’] testimony that, during the critical period, they were refining the formulas to implement the BlueSpace relevance model” by citing the entirety of so-called “corroborating documentation” spanning Exhibits 2032 through 2074 as well as the entirety of Justin Marston’s Second Supplemental Declaration (Ex. 2030) and Paul Marston’s Declaration (Ex. 2031). See PO Resp. 49. However, there is not a single pinpoint citation to any particular paragraph, page, or entry for any of those exhibits (a number of which approach 100 pages in length) in Patent Owner’s discussion. See id. Even less helpful, the Response does not inventors actually worked on the claimed invention. See id. That is, the Response does not state exactly what in the “corroborating documentation” actually corroborates the inventors’ testimony or itself shows diligence. If anything, the Response points out that the inventors were engaged in other activities: “Justin Marston had numerous other obligations running the company BlueSpace, and Paul Marston was working a full-time position as a lecturer on statistics.” PO Resp. 49; PO Sur-reply 15–16. We do not fault the Marstons for engaging in other activities, but Patent Owner’s discussion of the Marstons’ other activities and mere conclusory assertions of diligence, without more, do not show that the Marstons were reasonably diligent as to the relevant activities during the critical time period. Simply put, Patent Owner’s Response does not adequately explain exactly how or why the evidence supports its argument that the inventors were reasonably diligent throughout the critical period. We decline the invitation to sift through the hundreds of pages spanning dozens of exhibits in search of evidence and reasons supporting Patent Owner’s assertion of diligence.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“combined Rose and Bieganski. Rose and Bieganski are both concerned with recommending content to a user based on other users’ content preferences. Ex. 1006, code (57); Ex. 1007, code (57). Petitioner, supported by Dr. Fox, adequately shows that Bieganski discloses an improved technique for selecting which other users’ preferences are considered in a recommendation. Pet. 71 (citing Ex. 1003 ¶¶ 235–236), 75 (citing Ex. 1003 ¶¶ 247–248). We agree that improving Rose’s content ranking system using Bieganski’s content recommendation technique sufficiently motivates the combination. See KSR Int’l, 550 U.S. 417 (noting that where “a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious”). Patent Owner’s argument that Bieganski’s approach is not an improvement over Rose because Rose “teach[es] that feedback from all users is valuable” (PO Sur-reply 9–10 (citing Ex. 2029 ¶ 199)) has two faults. First, that argument mischaracterizes Rose. We find no description in Rose which states that feedback from all users is “valuable” such that selecting certain users is not an improvement. Rather, Rose aligns with Bieganski’s selection of relevant users because Rose emphasizes feedback from similar users by adjusting the weight given to feedback from users who are more or less correlated. Ex. 1006, 6:64–7:1, 7:10–34 (“Rjk is the correlation of users i and k, the Vkj is the weight indicating the feedback of user k on document j.”). Second, even if Rose describes an embodiment where feedback from all users is considered, that does not preclude motivating improvement. See PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1197–98 (Fed. Cir. 2014) (noting it is not necessary to show that a combination is “the best option, only that it be a suitable option”).” slip op. at 47
Patent outcomesUS 7,716,217 unpatentable§ 102 anticipation§ 103 obviousnesscites Phillips · KSRPatents in suitUS 7,716,217 - X Corp. v. Sterling Computers CorporationAll claims unpatentablePTAB · Jun 9, 2026 · IPR2025-00299 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–22 are unpatentable as obvious over the stated Dumais-based and Kircher/Krug grounds; Patent Owner’s and Petitioner’s motions to exclude are dismissed as moot.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Our Institution Decision adopted Petitioner’s definition of a person of ordinary skill in the art. Inst. Dec. 8–9. In its response, Patent Owner adopts Petitioner’s proposed level of ordinary skill. See PO Resp. 14–15 (“Patent Owner and its expert adopt the Board’s definition for purposes of this Response”). Having considered the record, we continue to adopt Petitioner’s proposed level of skill, as articulated above. We are satisfied that Petitioner’s proposal comports with the level of skill necessary to understand and implement the teachings of the ’217 Patent. Accord Inst. Dec. 8–9.” slip op. at 9
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)No construction neededNot reached
“1. “computer program modules” The parties dispute whether four “computer program modules comprising” (1) “a monitoring module,” (2) “a first relevance measurement module,” (3) “a second relevance measurement module,” and (4) “a relevance analysis module” (collectively, “module limitations”) invoke 35 U.S.C. § 112 ¶ 6 and should be treated as means-plus-function limitations. See Pet. 8–18; PO Resp. 15–18; Pet. Reply 3–5; PO Sur-reply 4–7. However, the parties do not argue that the construction of these terms affects the analysis of Petitioner’s challenges. See PO Resp.; Pet. Reply; PO Sur-reply. Moreover, our analysis does not rely on any particular construction of these terms and, so, we need not resolve this dispute.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“2. “one or more measures derived from the group consistent of” Petitioner asserts limitations 1[g] and 1[g][i]–1[g][iv] recite an open Markush group listing alternatively useable members. Pet. 20–21 (citing Gillette Co. v. Energizer Holdings, Inc., 405 F.3d 1367, 1372 (Fed. Cir. 2005); Abbot Lab’ys v. Baxter Pharm. Prod., Inc., 334 F.3d 1274, 1281 (Fed. Cir. 2003) (explaining that the listing of specified alternatives within a claim is referred to as a Markush group or Markush grouping)); See Ex. 1001, 47:47–58. Patent Owner does not dispute Petitioner’s construction. See PO Resp; PO Sur-reply. As these terms are not in controversy, we need not opine on this construction.” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITANo construction neededNot reached
“Petitioner’s and Patent Owner’s respective constructions overlap in their requirement that “cognate” users share similar past user actions and assessments or are defined by similar direct input by the user. See Pet. 18; PO Resp. 20–21; PO Sur-reply 10. Petitioner argues that Patent Owner’s construction “exclude[s] ‘groups’ from the claims” and further limits the scope of to users who share actions (Pet. Reply 8–9), but Patent Owner states that its proposed construction does not so limit the claims (PO Sur-reply 10). As such, there is no disagreement that “cognate” users share similar past user actions and assessments or are defined by similar direct input by the user. As there is no controversy, we need not, and do not, construe the meaning of “cognate.” However, Patent Owner’s requirement that “at least one other of the plurality of users” is specifically cognate to “the user” who was sent the content is plainly recited in the claim language itself. The claim recites a “relevance score of a piece of electronic content sent from a sender to a user” in the preamble and similarly again in limitation 1[g]. See Ex. 1001, 47:25–28 (emphasis added), 45:62–64. The limitation in question directly references the claimed “user” when reciting the cognate relationship: “identify at least one other of the plurality of users . . . that is cognate to the user.” Ex. 1001, 47:43–45 (emphasis added). As such, the claim language plainly supports Patent Owner’s requirement and Petitioner does not contest that requirement. See Pet. Reply 8. least one other of the plurality of users . . . that is cognate to the user” as requiring that the identified other user is cognate specifically to the user whose relevance score is being determined.” slip op. at 12
Patent outcomesUS 7,716,217 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 7,716,217 - Google LLC v. Mindbasehq, LLCAll claims unpatentablePTAB · Mar 16, 2026 · IPR2021-01252 · APJ Kara L Szpondowski · IPR · Remand
On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious; the Federal Circuit’s affirmed findings leave claims 1–13, 20–32, 41, and 42 unpatentable as well.
RulingsRemand decision- RemandOther
“to both cases vacating and remanding in part and affirming in part our Final Written Decisions. Appeal Dec. With respect to Petitioner’s appeals, the Federal Circuit addressed the “dictionary routine” claims (claims 14–19 and 33–40) and the “normalization” claims (claims 43–46). Appeal Dec. 7–14. For the “dictionary routine” claims, the Federal Circuit vacated and remanded, stating that In sum, as Google contends and we now hold, the “dictionary routine” claims can be practiced by use of an already-created dictionary, and do not also require the automatic creation of a dictionary. The Board needs to consider Google’s evidence and argument by applying this construction of the automatically classifying and storing limitation, and using this understanding to determine whether Conlon may, in fact, render the “dictionary routine” claims obvious (and, relatedly, whether its prior distinctions of Conlon may be immaterial). Appeal Dec. 10–11. For the “normalization” claims, the Federal Circuit also vacated and remanded, stating that our “decision to exclude Google’s rebuttal argument and supplemental declaration is based on a clear factual error,” so on remand we “must include evaluation of the evidence and argument Google provided in reply.” Id. at 13–14. With respect to Patent Owner’s cross-appeals, the Federal Circuit affirmed. Id. at 14–16.” slip op. at 3
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“The Federal Circuit concluded that Petitioner’s construction of “automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“We agree with Petitioner that claim 43 is obvious over the combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations. After considering the properly presented evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that the combination of Conlon, Miller, and Fong teaches the limitations in claim 43, that one of ordinary skill in the art would have been motivated to combine the teachings of Conlon, Miller, and Fong, and that claim 44 would have been obvious over Conlon, Miller, and Fong. 2. Analysis of Dependent Claims 44–46 Claims 44–46 depend, directly or indirectly, from claim 41. We, likewise, determine whether the combination renders obvious claims 44–46, taking into account the arguments made in Petitioner’s Reply Briefs and Dr. Jansen’s Supplemental Rebuttal Declarations. Petitioner contends that dependent claims 44–46, would have been obvious over Conlon, Miller, and Fong, and provides explanation as to how the prior art teaches each claim limitation. Pet. 84–86; Reply 35–39; Pet. Remand Br. 13–14. Patent Owner does not provide further briefing on dependent claims 44–46. 14 Available at https://www.uspto.gov/patents/ptab/trial-practice-guide#step2. Patent Owner did not specifically challenge Petitioner’s contentions as” slip op. at 31
- Strike new argumentNew argument disregardedDecided for petitioner
“Patent Owner’s arguments do not undermine Petitioner’s showing. Patent Owner did not specifically challenge Petitioner’s contentions as to the sufficiency of Conlon’s disclosure for claim 1410 in the Patent Owner Response. In the Sur-replies, Patent Owner argues that the claim requires that at least some relationships are created “automatically,” and “these automatic embodiments . . . are represented in this group of claims.” Sur-reply 9. Along these lines, in the additional briefing Patent Owner argues that Conlon does not teach “automatic,” but merely teaches “semi-automatic.” PO Remand Br. 9–10. The crux of Patent Owner’s argument, however, is that the Federal Circuit did not properly construe the limitation, and ignored certain disclosures in the ’433 (and ’680) patent. Id. at 10–11; see Pet. Remand Resp. Br. 1–4; PO Remand Resp. Br. 4–5. The Federal Circuit held that “the dictionary routine claims can be satisfied by mere use of a lexical database, and do not also require the automatic creation of additional definitions.” Appeal Dec. 10. Moreover, the statements from Conlon that Patent Owner relies upon relate to creating a database, not using the database. See id. As discussed above, on remand we are directed to apply the Federal Circuit’s construction. Patent Owner does not explain 10 As discussed in the original Final Written Decisions, Patent Owner raised several arguments that generally applied to all the claims, challenging, for example, the level of ordinary skill in the art, whether Conlon, Miller, and Beckwith were analogous art, and several general arguments relating to Conlon and the motivation to combine Conlon with a DBMS. See Final Dec. 14–23, 25–27. We were not persuaded by Patent Owner’s arguments; the Federal Circuit affirmed, determining that our findings were supported by substantial evidence. Appeal Dec. 14–16. why Petitioner’s contentions are not persuasive in light of the Federal Circuit’s construction of this limitation. In addition, Patent Owner argues in the Sur-replies that “[c]laims 14– 19 are not disclosed by the proffered prior art” and cites to paragraphs 78–83 of the Ranka Rebuttal Declarations. Sur-reply 10. As discussed in the original Final Written Decisions, Patent Owner’s reliance on six paragraphs of Dr. Ranka’s Rebuttal Declarations is an improper incorporation by reference, as Patent Owner did not discuss that testimony or further elaborate on these arguments in the Sur-replies. 37 C.F.R. § 42.6(a)(3); Cisco Systems, Inc. v. C-Cation Techs., LLC, IPR2014-00454, Paper 12 at 9–10 (PTAB Aug. 29, 2014) (informative); see, e.g., Final Dec. 37–39, 45, 48–50, 52. Therefore, we will not consider arguments that are not made in the Sur-replies, but are instead improperly incorporated by reference to the cited paragraphs in Dr. Ranka’s Rebuttal Declarations. Accordingly, after considering the evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that Conlon teaches limitation [14.3], and that claim 14 would have been obvious over Conlon.” slip op. at 21
Patent outcomesUS 6,665,680 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,665,680 - Google LLC v. Mindbasehq, LLCAll claims unpatentablePTAB · Mar 16, 2026 · IPR2021-01251 · APJ Kara L Szpondowski · IPR · Remand
On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious over Conlon alone or Conlon, Miller, and Fong; the affirmed unpatentability of claims 1–13, 20–32, 41, and 42 remains.
RulingsRemand decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 31
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 32
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“4. Summary of Ground 1 Having considered the Graham factors,11 including the level of ordinary skill in the art, the scope and content of the prior art, and the differences between the prior art and the challenged claims, we are persuaded, based on the current record, that Petitioner has shown, by a preponderance of the evidence, that claims 14–19 and 33–40 would have been obvious over Conlon.” slip op. at 24
Patent outcomesUS 6,510,433 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,510,433 - Qualcomm Incorporated v. Cobblestone Wireless, LLCSome claims unpatentablePTAB · Mar 5, 2026 · IPR2024-01336 · APJ Russell E Cass · IPR · Final written decision
Claims 1–4, 6–9, 24, and 25 are unpatentable; claims 10, 13, 14, 17, and 21–23 were not shown unpatentable, principally due to missing limitations or insufficient motivation to combine.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“information” should be given its plain and ordinary meaning as “data,” and that Patent Owner’s narrower construction of “first information” and “second information” lacks sufficient support in the intrinsic record. We agree with Petitioner that the ’802 patent Specification defines “information” as data when it uses the phrase “information (i.e., data).” See Ex. 1001, 5:60–62 (“Information (i.e., data) to be transmitted may be received in a baseband digital system 250, such as a wireless digital baseband processor.” (emphasis added)), 11:30–32 (“In this example, the signals 911 and 912 carry the same information (data).” (emphasis added)). As the Federal Circuit has explained, a “specification’s use of ‘i.e.’ signals an intent to define the word to which it refers.” Edwards Lifesciences LLC v. Cook Inc., 582 F.3d 1322, 1334 (Fed. Cir. 2009). slip op. at 13
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“argument based on Fernandez alone, we find that Petitioner has not provided a sufficient evidentiary basis to support a motivation to remove the amplification from each of Fernandez’s signal generators 10A-10E and add a single power amplifier instead. See Pet. 76–77 Ex. 1003 ¶ 235. Petitioner’s only rationale for this modification to Fernandez is that “[a] single amplifier has several advantages compared to multiple amplifiers, including lower complexity, a single (vs. multiple) potential point of failure, and lower cost,” and that one of ordinary skill “would have found a single amplifier to be a simple matter of design preference.” Pet. 76–77. Dr. Almeroth simply repeats these cursory allegations without providing any further explanation or evidentiary support. Ex. 1003 ¶ 235. Moreover, Dr. Cooklev provides credible testimony that replacing Fernandez’s amplification in signal generators 10A–10E with a single amplifier would not necessarily have the advantages that Petitioner suggests. See Ex. 2013 ¶¶ 99, 104–105. For example, Dr. Cooklev testifies that a single amplifier would need to have a wider bandwidth than the multiple amplifiers used in Fernandez, which could cause potential stability issues. Id. ¶ 105. According to Dr. Cooklev, this wider bandwidth would require more circuit elements, and thus would not provide the reduction in space usage and power consumption that Petitioner asserts. Id. According to Dr. Cooklev, Montojo also points to several “substantial, and potentially impractical, drawbacks” of using a single amplifier for multiple signal generators, including power constraints imposed by spectral emission requirements and on-board battery capacity. Id. ¶ 104 (citing Ex. 1006 ¶¶ 7– 8). In light of this testimony, which we find credible, Petitioner has failed to provide sufficient explanation or evidence to support its assertion that one of ordinary skill would have found it obvious to replace the multiple amplifiers in Fernandez’s signal generators with a single amplifier.” slip op. at 65
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“argument based on Fernandez alone, we find that Petitioner has not provided a sufficient evidentiary basis to support a motivation to remove the amplification from each of Fernandez’s signal generators 10A-10E and add a single power amplifier instead. See Pet. 76–77 Ex. 1003 ¶ 235. Petitioner’s only rationale for this modification to Fernandez is that “[a] single amplifier has several advantages compared to multiple amplifiers, including lower complexity, a single (vs. multiple) potential point of failure, and lower cost,” and that one of ordinary skill “would have found a single amplifier to be a simple matter of design preference.” Pet. 76–77. Dr. Almeroth simply repeats these cursory allegations without providing any further explanation or evidentiary support. Ex. 1003 ¶ 235. Moreover, Dr. Cooklev provides credible testimony that replacing Fernandez’s amplification in signal generators 10A–10E with a single amplifier would not necessarily have the advantages that Petitioner suggests. See Ex. 2013 ¶¶ 99, 104–105. For example, Dr. Cooklev testifies that a single amplifier would need to have a wider bandwidth than the multiple amplifiers used in Fernandez, which could cause potential stability issues. Id. ¶ 105. According to Dr. Cooklev, this wider bandwidth would require more circuit elements, and thus would not provide the reduction in space usage and power consumption that Petitioner asserts. Id. According to Dr. Cooklev, Montojo also points to several “substantial, and potentially impractical, drawbacks” of using a single amplifier for multiple signal generators, including power constraints imposed by spectral emission requirements and on-board battery capacity. Id. ¶ 104 (citing Ex. 1006 ¶¶ 7– 8). In light of this testimony, which we find credible, Petitioner has failed to provide sufficient explanation or evidence to support its assertion that one of ordinary skill would have found it obvious to replace the multiple amplifiers in Fernandez’s signal generators with a single amplifier.” slip op. at 65
- Expert testimonyPatent owner expert creditedPetitioner expert discountedOther
“We find credible and agree with Dr. Cooklev’s testimony that the predistortion signals from tables 17-1 and 17-2 “are cancelled out by Suzuki’s amplifier” 28. Ex. 2013 ¶ 50. Dr. Cooklev supports his opinion by referring to paragraph 1 of Suzuki, which states that Suzuki’s invention is directed to “a multi-band lookup table type predistorter” (such as the one implemented using lookup tables 17-1 and 17-2 in Figure 6) that “compensates for a distortion of a power amplifier.” Ex. 2013 ¶ 54; Ex. 1004 ¶ 1. Dr. Cooklev’s opinion is also supported by paragraph 3 of Suzuki, which explains that a conventional digital predistorter uses a lookup table “for linearizing non-linear characteristics of an amplifier.” Ex. 1004 ¶ 3; Ex. 2013 ¶ 54. Dr. Cooklev further supports his opinion by relying on Suzuki’s disclosure in paragraph 46 that power amplifier 28 is “subject to distortion compensation” by the predistorter, and that distortion components in the signal output by the amplifier are canceled by “distortion compensation data [that] are read out from the lookup tables 17-1 and 17-2 and provided to the adders 13-1 and 13-2, respectively.” Ex. 1004 ¶ 46; Ex. 2013 ¶ 54. And, Dr. Cooklev’s opinion is supported by Suzuki’s disclosure in paragraph 47 that the distortion compensation added by adders 13-1 and 13-2 add the distortion compensation data from lookup tables 17-1 and 17-2 “to perform distortion compensation (addition of predistortion)” to “signals to be transmitted.” Ex. 1004 ¶ 47; Ex. 2013 ¶ 54. Petitioner agrees that the distortion compensation data from lookup tables 17-1 and 17-2 “are added to the respective frequency band from” input signal ST “in order to predistort the output signal, which is then transmitted,” and does not dispute that the distortion compensation data from lookup tables 17-1 and 17-2 is ultimately cancelled out by the distortion created by amplifier 28. Pet. Reply 8. In light of the above evidence, we agree with Patent Owner that Suzuki’s distortion components from lookup tables 17-1 and 17-2 in Figure 6 (which Petitioner relies on for the first and second digital signals in limitations 10a and 10b) are cancelled out by the distortion created by power amplifier 28 before the signal is ultimately transmitted. We agree with Petitioner that these first and second digital signals include data in the form of distortion compensation data. However, because these signals are cancelled by the distortion from amplifier 28 before transmission, the data from these signals is never transmitted. Thus, the first and second digital signals identified by Petitioner (the distortion compensation data from lookup tables 17-1 and 17-2) do not comprise data “to be transmitted,” as limitations 10a and 10b require.” slip op. at 35
Patent outcomesUS 7,924,802 mixedClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,924,802 - Apple Inc. v. Varia Holdings LLCAll claims unpatentablePTAB · Feb 27, 2026 · IPR2024-01364 · APJ Norman H Beamer · IPR · Final written decision
Claims 1–39 are unpatentable under § 103 over Willgert and Mooney; claims 3–9, 15–19, 22–28, and 34–38 are also unpatentable over Willgert, Mooney, Holloway, and Pitroda.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Based on a review of the record, we adopt Patent Owner’s proposed level of ordinary skill in the art, with its inclusion of a Computer Science background, because it is consistent with the evidence of record, including the asserted prior art and ‘984 patent specification. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our Decision would not be altered if Petitioner’s definition applied.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“d) Analysis Re Construing “Voice Call Signals” We conclude that it is unnecessary to define “voice call signal.” Patent Owner’s construction would read into the term additional limitations that are for the most part already set forth in the claims: “a switchable mobile communications device capable of . . . voice call communication” (claims 1, 13, 21, 32); “output . . . a voice call signal for transmission . . . over a wireless network” (claims 13, 21, 32); “wherein the mobile communication device is a selected one of a wireless mobile phone and a personal digital assistant equipped with communication capability” (claims 12, 20, 31, 39). Thus the claims require a mobile communications device that is capable of communicating a voice call signal, but do not restrict the voice call signal to only be communicated by a mobile communications device. Likewise, claims 13, 21, and 32 (but not claim 1) require the voice call signal to be transmitted over a wireless network, but do not restrict transmission to only a wireless network, and do not restrict the wireless network to “a network of a wireless network service provider,” as Patent Owner would require.” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed board ownDisclaimer not foundDecided for petitioner
“construction for the RFID transponder signal or data terms — it is sufficient for purposes here to conclude that the claims encompass Petitioner’s “functional emulation” articulation. See Reply 11–12. That is, the purpose of the frequent references to “emulated,” “emulation,” or the like in the ‘984 patent is to emphasize the fact that the mobile communications device of the claims has a dual role: to provide voice call communications, and to transmit RFID transponder data. In the latter role, transmitted RFID transponder data appears to an RFID reader to have been transmitted from an ordinary RFID transponder. But there is no need to rewrite the claims to restore the emulation terms, given that, as we discuss further below, Patent Owner deliberately removed those terms during prosecution. The functional emulation implicit in the ‘984 specification and claims” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“the fact that Willgert teaches that integrating its communications unit into a mobile telephone designed for Bluetooth communication was a “highly user-friendly application,” and that it was well known practice to use a Bluetooth headset wirelessly communicating with the phone to enable hands-free phone calls, as specifically taught by Mooney. Pet. 12–14 (citing Ex. 1004 ¶¶ 8, 30–32; Ex. 1005, Fig. 3, ¶¶ 7, 39, 46–48; Ex. 1021; Ex. 1003 ¶¶ 72–76). Petitioner further argues that Bluetooth headsets were widely available, that incorporating the headset involved known methods yielding predictable results, and that one of ordinary skill would have reasonably expected to succeed in combining the teachings of Willgert and Mooney. Id. at 15–16 (citing Ex. 1004 ¶¶ 8, 10; Ex. 1005, ¶ 8; Ex. 1017, 1, 3; Ex. 1021, 2; Ex. 1003 ¶¶ 77–79). Patent Owner does not specifically address the issue of motivation to combine Willgert and Mooney. See generally PO Resp. We find, based on the record, that Petitioner has proved by a preponderance of the evidence that a person of ordinary skill in the art would have been motivated to combine Willgert and Mooney as proffered by Petitioner with a reasonable expectation of success.” slip op. at 31
Patent outcomesUS 8,127,984 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,127,984 - Apple Inc. v. Varia Holdings LLCAll claims unpatentablePTAB · Feb 27, 2026 · IPR2024-01363 · APJ Norman H Beamer · IPR · Final written decision
Claims 1–32 are unpatentable under § 103 over Willgert and Mooney, or Willgert, Mooney, Holloway, and Pitroda, as applicable.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner “disputes the narrow range of educational experiences in the Petition’s POSITA definition, but does not otherwise dispute the remaining portion of the definition.” PO Resp. 13. Patent Owner contends that person of ordinary skill in the art: [W]ould have been someone “with at least a Bachelor’s degree in Electrical Engineering, Computer Science, or a related field, with a background in radio frequency communications and software development, as well as approximately two years of experience working with or researching radio frequency communication systems. Lack of work experience can be remedied by additional education, and vice versa.” PO Resp. 13–14 (citing Ex. 2004 ¶ 34).7 Based on a review of the record, we adopt Patent Owner’s proposed level of ordinary skill in the art, with its inclusion of a Computer Science background, because it is consistent with the evidence of record, including the asserted prior art and ’947 patent specification. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our Decision would not be altered if Petitioner’s definition applied.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Not reached
“d) Analysis Re Construing “Voice Call Signals” We conclude that it is unnecessary to define “voice call signal.” Patent Owner’s construction would read into the term additional limitations that are for the most part already set forth in the claims: “the voice call signal is output over a wireless network” (claims 1 ); “outputting the voice call signal over a wireless network” (claim 9); “output a voice call signal for transmission over a wireless network” (claim 16); transmit voice call signals . . . over a wireless network” (claim 26); “wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability” (claims 8, 15, 25, 32). Thus the claims require the voice call signal to be transmitted over a wireless network, but do not restrict transmission to only a wireless network, and do not restrict the wireless network to “a network of a wireless network service provider,” as Patent Owner would require. We also agree that there is nothing in the ’984 prosecution history that supports Patent Owner’s assertion that the Examiner found that the Bluetooth signal of Cooper was not a voice call signal. Cooper was distinguished because: The term “transceiver,” however, is well understood by those of ordinary skill in the art. One of ordinary skill in the art would not reasonably interpret a “transceiver” so broadly as to incorporate an entire mobile device’s circuitry, and in particular to be read on by two separate transmitters, as Cooper teaches. Ex. 1008, 40. On the other hand, we agree with Patent Owner that Petitioner’s” slip op. at 14
- Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed petitioner constructionDecided for petitioner
“This functional emulation solution is served regardless of how the specific RFID transceiver is implemented — the ’947 specification specifically provides for both software and hardware implementations. Id. at 2:24–28 (“Embodiments of the present invention includes . . . certain hardware and/or software embodied therein for the practice of the emulated RFID method”), 3:35–36 (“mobile communication device 102 is equipped with hardware and/or software elements”), 3:52–54 (“substantial portions of the hardware and/or software elements employed to provide a RFID”), 5:16 (“A Hardware/Software Implementation”). There is no reason why one version of the hardware used to emulate the RFID function could not be RFID transponder circuitry. The issue is not whether an RFID transponder can emulate itself, but rather whether RFID transponder circuitry incorporated into a mobile communications device can be used to allow the mobile communications device to emulate a separate RFID transponder. For example, rather than requiring the person described in the Background of the ’947 patent to carry both a mobile phone and a “key with remote control for gaining access to his/her vehicle,” they need only carry the mobile communications device of the claims. The statement in the ’947 patent that “the present invention is related to an emulated radio frequency data input method” (Ex. 1001, 1:22–24), and the other references to emulation, are consistent with a conclusion that the claims encompass the “functional emulation” option as described above. However, there is no basis for adding the negative limitation proposed by Patent Owner (“without the use of a physical RFID transponder”). Omega Engineering, 334 F.3d at 1333 (rejecting a construction because “neither the plain text of the claims, the specification, nor the file wrapper justifies the imposition of this negative limitation”). See also BillJCo, LLC v. Apple Inc., No. 2023-2189, 2023-2190, 2025 WL 1417957, at *1 (Fed. Cir. May 16, 2025): Our court has “identified claim constructions that exclude a particular element as including a ‘negative limitation’ and held that such exclusions must find support either in ‘the words of the claim’ or through an ‘express disclaimer or independent lexicography in the written description that would justify adding that negative limitation.’” Ethicon LLC v. Intuitive Surgical, Inc., 847 F. App’x 901, 907 (Fed. Cir. 2021). Moreover, the prosecution history of the ’984 grandfather patent is not” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Petitioner argues that this combination would have been motivated by the fact that Willgert teaches that integrating its communications unit into a mobile telephone designed for Bluetooth communication was a “highly user- friendly application,” and that it was well known practice to use a Bluetooth headset wirelessly communicating with the phone to enable hands-free phone calls, as specifically taught by Mooney. Pet. 16–18 (citing Ex. 1004 ¶¶ 8, 30, 32; Ex. 1005, Fig. 3, ¶¶ 7, 39, 48; Ex. 1021; Ex. 1003 ¶¶ 62–65). Petitioner further argues that Bluetooth headsets were a well-known concept and widely available, that incorporating the headset involved known methods yielding predictable results, and that one of ordinary skill would have reasonably expected to succeed in combining the teachings of Willgert and Mooney. Id. at 19–21 (citing Ex. 1004 ¶¶ 8, 10, 30; Ex. 1005, ¶ 8; Ex. 1016; Ex. 1017, 1, 3; Ex. 1021, 2; Ex. 1003 ¶¶ 66–68). Patent Owner does not specifically address the issue of motivation to combine Willgert and Mooney. See generally PO Resp. We find, based on the record, that Petitioner has proved by a preponderance of the evidence that a person of ordinary skill in the art would have been motivated to combine Willgert and Mooney as proffered by Petitioner with a reasonable expectation of success.” slip op. at 29
Patent outcomesUS 9,405,947 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,405,947
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.