- Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 23, 2026 · IPR2025-00915 · APJ Arthur M Peslak · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–3, 5–16, and 18–30 as obvious over Menon, Trefethen, RS6000, and MPIref; claims 4 and 17 over those references plus POEref.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundTeaching away not foundDecided for petitioner
“Ex. 1163 ¶ 37 (citing Ex. 1003 ¶ 71; Ex. 1005, 1–3). We credit Dr. Bajaj’s testimony which is unrebutted and supported by the record. We, thus, agree with Dr. Bajaj’s reasoning which is based on Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶ 75. 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. RS6000 is specifically referenced in Menon-Trefethen and adds operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Considering Menon as a whole, these facts are inconsistent with Patent Owner’s teaching away arguments. For these reasons, Patent Owner’s teaching away argument is unavailing. Motivation to Combine Conclusion We have reviewed Petitioner’s evidence and contentions which we” slip op. at 42
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“For the foregoing reasons, Petitioner establishes by a preponderance” slip op. at 79
Patent outcomesUS 11,563,621 unpatentable§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,563,621 - Apple Inc. v. Proxense, LLCAll claims unpatentablePTAB · Sep 17, 2026 · IPR2025-00562 · APJ Thu A Dang · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board also finds the claims unpatentable under the Broadcom grounds.
RulingsFinal written decision- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“IPR2024-00783, Ex. 1001, 22:36–49. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112 ¶ 6. See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112 ¶ 6 is not overcome.” slip op. at 17
- Skill levelOther
“differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
- Expert testimonyPetitioner expert creditedDecided for petitioner
“We find persuasive Dr. Wolfe’s supporting testimony that a POSITA would have understood the terms “PDK” and “RDC” to have “definite structure.” Ex. 1013 ¶¶ 35–56. In particular, we find persuasive Dr. Wolfe’s testimony that the term “PDK,” for example, “encompasses at least ‘a collection of circuit components that includes an antenna, a transceiver, and a controller and memory for storing information particular to a user.’” Id. ¶ 35. Dr. Wolfe’s testimony is consistent with the Specification of the ’188 patent. See Ex. 1001, 5:42–6:7, 3:48–62. In particular, the Specification of the ’188 patent describes a microchip that stores information in memory and responds through an antenna when probed, which is consistent with Dr. Wolfe’s testimony. Id.; Ex. 1001, 1:30–62.” slip op. at 19
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
Patent outcomesUS 9,049,188 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,049,188 - 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 - Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentablePTAB · Sep 3, 2026 · IPR2025-00673 · APJ Michael R Zecher · IPR · Final written decision
Claims 1–7 are unpatentable as obvious over the combined teachings of the asserted references, including Shin and Aoyama and Shimomura and Iwase.
RulingsFinal written decision- PTAB / AIA Trials › Motions to amend / substitute claimsOther
“1 SoundClear also filed a Contingent Motion to Amend that proposed to replace originally challenged claim 5 of the ’675 patent with proposed substitute claim 8. Paper 21. We, however, granted SoundClear’s request to withdraw its Contingent Motion to Amend and, as a result, the Contingent Motion to Amend will no longer be considered in this proceeding. Paper 30.” slip op. at 2
- Skill levelOther
“2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 21
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed
“combination because (1) configuring Shin’s processor 120 accordingly “would have been trivial, involving straightforward changes to enhance the processor’s approach to simplifying and abbreviating its output”; and (2) this approach was well-known as evidenced by Ha’s disclosure of replacing “team meeting” and “date” with “schedules” based on the user’s environment.6 Id. at 27–28 (first quoting Ex. 1011 ¶ 97, then quoting Ex. 1011 ¶ 98) (citing Ex. 1002 ¶ 102; Ex. 1011, Fig. 7).” slip op. at 33
- Expert testimonyPetitioner expert creditedDecided for petitioner
“4. Dr. Stern’s Testimony is Reliable In its Patent Owner Response, SoundClear contends that “Dr. Stern’s” slip op. at 125
Patent outcomesUS 11,244,675 unpatentable§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,244,675 - 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 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Jul 28, 2026 · IPR2025-00491 · APJ Frederick C Laney · IPR · Final written decision
Claims 1–18 are unpatentable as obvious over Beel and Dinka, with or without Christison; the Kaplan, Van de Laar, and Christison ground fails for lack of motivation to combine.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art.” PO Resp. 6. On the complete record, we adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’972 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededPlain and ordinary meaningDecided for patent owner
“Rather than addressing Petitioner’s proposals, Patent Owner states “the claims of the ’972 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Our decision in this matter does not turn on resolving any particular differences between the parties’ constructions. Therefore, because only those terms in controversy need to be construed, and only to the extent necessary to resolve the controversy, we determine that no claim term requires express construction in this proceeding and that the ordinary and customary meaning of the claim terms apply. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019).” slip op. at 11
- Expert testimonyPatent owner expert discountedDecided for petitioner
“device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125.” slip op. at 27
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“First, we agree with Patent Owner that, under the ordinary meaning of the claim language, the endpoint is an endpoint of the peripheral device, and that it must be “a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device.” Ex. 1001, 23:11–17. The limitation thus identifies a structure—an endpoint, residing on the peripheral device, that is a source or sink and that corresponds to (is “of”) the functional device—through which the communication recited in subsequent element (g) is carried out. By its terms, it imposes no requirement as to the direction in which data flows; it requires only that the endpoint be a data “source” or a data “sink” that is able to “store or emit” data. The operative transmit-and-receive communication “from the functional device to the processing device via the . . . endpoint” is recited in subsequent element (g), which we take up separately below. The disputed question under this limitation is therefore the structural one: whether Beel discloses, on the peripheral device, an endpoint that is “of the functional device.” Because the inquiry is structural and non-directional, we are not persuaded that the audio-out orientation of Beel’s described embodiment, on which Patent Owner relies, is dispositive of this limitation. device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125. Third, we find that the endpoint Beel discloses is a data source or a data sink that is “able to store or emit data, of the functional device.” We begin with the words of the limitation. The endpoint need only be “able to store or emit data”—language of capability, not a requirement that particular data actually traverse the endpoint in operation, and still less in a particular direction. And the endpoint is defined by the character of the data it handles: it is “a data source or a data sink,” which the ’972 patent instructs An audio endpoint, so understood, is characterized as an audio source or sink; its structure is not tied to any single instance of an audio device. On that understanding, Beel’s disclosure establishes the required capability directly. Beel discloses that “audio data is captured through a virtual sound card interface added as a logical device over the physical interface provided in the peripheral device,” Ex. 1005 ¶ 43, that the peripheral device “acts as a composite device comprising for instance a (virtual) audio speaker device,” id. ¶ 317, and that “audio data is captured at this interface . . . internally in the peripheral device 32” and streamed over the communications network, id. ¶ 319. Beel thus shows the endpoint on the peripheral device actually storing and emitting audio—and, correspondingly, video—data, which is the very type of data produced and consumed by the audio/visual functional devices connected to the base unit, including the microphones, cameras, speakers, and displays. Id. ¶ 120. An endpoint shown to store or emit audio and video data is necessarily one that is “able to store or emit” such data; the capability the limitation requires is thus established by Beel’s disclosure.” slip op. at 26
Patent outcomesUS 10,684,972 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,684,972 - Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentablePTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision
Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.
RulingsFinal written decision- BurdenOther
“Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2
- Skill levelOther
“2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed
“1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17
Patent outcomesUS 11,069,337 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,069,337 - 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
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.