• Google LLC v. Sandpiper CDN, LLCAll claims unpatentable
  PTAB · Oct 9, 2026 · IPR2025-00826 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–23 are unpatentable under § 103, including over Glines alone and the additional asserted combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art (“POSITA”) at the critical time “would have had at least a bachelor’s degree in computer science, electrical engineering, or a related field, and at least two years of work or research experience in the field of content delivery management or networks,” and that “additional education could substitute for work experience.” Pet. 3 (citing Ex. 1008 ¶¶ 51–53). Patent Owner provides substantially the same assessment. PO Resp. 16. We adopt Petitioner’s proposed level of ordinary skill, as it appears to be consistent with the specification of the ’112 patent and the prior art of record.” slip op. at 7

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

    “claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. [§] 282(b).” 37 C.F.R. § 42.100(b). Under this standard, the words of a claim generally are given their “ordinary and customary meaning,” which is the meaning the term would have to a person of ordinary skill at the time of the invention, in the context of the entire patent including the specification. Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Neither party proposes any express claim construction. Pet. 3; PO Resp. 16. We address the parties’ interpretation of the scope of “causing said hostname to be resolved” in our discussion of Petitioner’s assertions for limitation [1.d]. Based on the record before us, we determine that no claim term requires express construction.” slip op. at 8

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Strike new argumentNew argument consideredDecided for petitioner

    “We do not agree. The Petition states that Glines discloses that the anycast is resolved by an ISP DNS server. Pet. 20. The Petition identifies Glines’s local ISP DNS resolver 18 as the claimed ISP DNS server. Id. The Petitioner further asserts that Glines’s ISP DNS resolver 18 sends the request to the DNS server 38, but states that “Glines’s local DNS resolver, an ISP DNS server, thus causes the hostname . . . to be resolved.” Id. at 21–22. The Petition also drew an analogy with the ’112 patent and the role of local DNS server 70a in the Petition. See Pet. 20–21. Because the Petition and the Reply both identify Glines’s local ISP DNS resolver 18 as causing the hostname to be resolved, Petitioner has not advanced a new theory of unpatentability in its Reply. 6 At oral argument, Patent Owner suggested a narrower claim reading, but admitted that this had not been briefed. Tr. 36:15–38:9, 44:9–16. We do not address this reading because it was not set forth in the briefing. In the briefing, Patent Owner took the broader reading discussed here. See Tr. 41:12–23; PO Sur-reply 7.” slip op. at 13

  Patent outcomesUS 9,021,112 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,021,112
• Medivis, Inc. v. Novarad Corp.Some claims unpatentable
  PTAB · Oct 1, 2026 · IPR2023-00042 · APJ Scott Raevsky · IPR · Remand

  Claims 1–6, 11, and 20 are unpatentable as obvious over Doo and Amira; claims 12–19 were not shown unpatentable because the asserted tissue properties were not shown in Amira.

  RulingsRemand decision

  • RemandOther

    “Federal Circuit. The court issued its decision in Medivis, Inc. v. Novarad Corp., No. 2024-1794, 2026 WL 587294 (Fed. Cir. Mar. 3, 2026) (“Medivis”) (Paper 40),1 affirming-in-part, reversing-in-part, and remanding our Final Written Decision (Paper 35) for further proceedings. In its opinion, the Federal Circuit reversed our “determination of no motivation to combine Doo and Amira” and remanded for further proceedings to evaluate whether claims 1–6 and 11–20 (“the Remanded Claims”) of U.S. Patent No. 11,004,271 B2 (“the ’271 patent,” Ex. 1001) are unpatentable in view of Petitioner’s obviousness challenge over Doo and Amira. Medivis, slip op. at 9–10. We have jurisdiction under 35 U.S.C. § 6(b). We issue this Final Written Decision on Remand pursuant to 35 U.S.C. §§ 144, 318 and 37 C.F.R. § 42.73 in an inter partes review involving Medivis, Inc. (“Petitioner”) and Novarad Corp. (“Patent Owner”). For the reasons discussed below, after considering the entirety of the record in light of the Federal Circuit’s directives in Medivis, we hold that Petitioner has demonstrated, by a preponderance of the evidence, that claims 1–6, 11, and 20 are unpatentable; however, Petitioner has not demonstrated, by a preponderance of the evidence, that claims 12–19 are unpatentable.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We adopt Petitioner’s proposed level of skill, except that we excise part of Petitioner’s definition to produce the following modified version: 4 Throughout this decision, we eliminate the parties’ italicization of reference names from quotations without noting “emphasis omitted.” 5 Doo, WO 2015/164402 A1, published October 29, 2015 (Ex. 1008). 6 Excerpt of Amira 5 User’s Guide, title through Chapter 2 (Visual Imaging 2009) (Ex. 1005). engineering, or a related field with several years of experience in the design, development, and study of augmented reality devices and . . . familiarity with conventional medical imaging data and visualization of data for medical procedures . . . . Our edit removes the alternative of “working with a team including someone with such familiarity” because one’s role in a team may be tangential to their personal experience with medical imaging. Regardless, had we adopted Petitioner’s original definition, our decision would not have changed.” slip op. at 6

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “We agree with Petitioner that the term “3D slices” has no apparent connection to the phrase “direct volume rendering.” Patent Owner’s argument appears to be that DVR “requires an image of the entire anatomical volume that is neither feature-specific nor segmented, [which] would seemingly require that all inner layers be displayed.” Reply 4; see Sur-reply 6–10 (not disputing Petitioner’s characterization). But, as Petitioner notes, the specification directly undermines this by teaching “display [of] a slice of the 3D data instead of a volume of the 3D data.” See Reply 4 n.2 (quoting Ex. 1001, 5:34–35). In other words, to the extent DVR would depict an image of the entire anatomical volume, displaying 3D slices “instead of a volume of the 3D data” implies the opposite of DVR. Even if “3D slices” somehow implied DVR, Patent Owner’s position is still untenable. Claim 1 does not recite “3D slices.” Instead, claim 1 recites “3D data” and “inner layers.” Ex. 1001, 18:54–65. Patent Owner fails to clarify the relationship between “slices,” “3D data,” and “layers,” and its expert even admits that slices and layers are two different things. See PO Resp. 13; Ex. 1022, 32:7–16 (agreeing that the words “slice” and “layer” are not “synonyms”), cited in Reply 4. We also agree with Petitioner that dependent claim 3 distinguishes slices and layers by reciting “slices of the projected inner layer.” Reply 4 (quoting Ex. 1001, 19:3–10). Thus, even if 3D slices somehow implied DVR, the language of claim 1 does not support limiting the claim this way.” slip op. at 12

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “The determination of whether a document was publicly accessible “involves a case-by-case inquiry into the facts and circumstances surrounding the reference’s disclosure to members of the public.” Medtronic, Inc. v. Barry, 891 F.3d 1368, 1380 (Fed. Cir. 2018). For instance, courts routinely rely on the Wayback Machine to determine when a reference was first made available to the public. Valve Corp. v. Ironburg Inventions Ltd., 8 F.4th 1364, 1374 (Fed. Cir. 2021) (“District courts have taken judicial notice of the contents of webpages available through the Wayback Machine ‘as facts that can be accurately and readily determined from sources whose accuracy cannot reasonably be questioned.’”). We disagree with Patent Owner’s argument that “Medivis cannot rely on additional prior art”—Exhibits 1023 and 1024—“that was submitted after its Petition to carry its burden without leave from the Board.” Sur-reply 4. As Patent Owner did not file a motion to exclude these exhibits, we decline Patent Owner’s invitation to disregard them. We also find Petitioner’s Reply argument proper because it directly responds to Patent Owner’s contention that Petitioner did not prove the public accessibility of Amira. See Chamberlain Grp., Inc. v. One World Techs., Inc., 944 F.3d, 919, 925 on issues previously raised.”). Petitioner’s Reply argument appropriately elaborates on the Petition’s contention that Amira was publicly accessible. Patent Owner also does not dispute the substance of Petitioner’s evidence. For example, Patent Owner does not address the substance of Mr. Frank-White’s declaration. We find that this evidence, including Mr. Frank- White’s declaration testimony, persuasively supports the public availability of Amira as of the date shown in the Wayback Machine URL. See Ex. 1024.” slip op. at 22

  Patent outcomesUS 11,004,271 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 11,004,271
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · 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 · Graham
  Patents in suitUS 11,563,621
• Microsoft Corporation v. Sterling Computers CorporationAll claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 8,073,911
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,021,679
• Google LLC v. Wildseed Mobile, LLCNo claims unpatentable
  PTAB · Sep 1, 2026 · IPR2023-00247 · APJ Michael T Cygan · IPR · Remand

  Claim 15 was not shown unpatentable over Rothschild alone or Rothschild and Chen because Petitioner did not sufficiently explain or support how the IM modality generates the claimed hot link.

  RulingsRemand decision

  • BurdenNot shown unpatentable

    “disclaim HTML-formatted advertisements in IM,” and that there is no evidence or expert testimony that IM messages are incompatible with HTML tags. Pet. Remand Reply 4–7 (also stating, “nor did Patent Owner contest the Petition’s showing with respect to the IM limitation of claim 15”). However, in inter partes review, the burden is on Petitioner to explain and support its assertions; it is not on Patent Owner to prove that its claims are not unpatentable. In re Magnum Oil Tools, 829 F.3d at 1375; PO Remand Resp. 5. Petitioner must explain how Rothschild teaches generating a hot link message, in an instant message communication, that includes the determined action and instructions for rendering and displaying the hot link. Petitioner’s reliance on a list of communication types is insufficient because although personal communications are sent “with” an advertisement, not all members of that list (e.g., SMS) generate a hot link message having the claimed instructions in the manner (formatting) asserted by Petitioner. Ex. 1005, 8:3–6; Ex. 2009 ¶ 64.” slip op. at 12

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

    “link message by IM is that Rothschild states that “a personal communication can include, but is not limited to, an e-mail message, text message, short message service (SMS) message, chat-room message, instant messaging message, video message, voice message, and any other personalized network communications.” Pet. 40 (quoting Ex. 1005, 8:6–11); Pet. Remand Reply 2, 5–6 (arguing that this is unrebutted by Patent Owner). Such an explanation would be sufficient if each of those communications were shown to work in the same manner as email, such that no further explanation would be required to show that one having ordinary skill in the art would understand how Petitioner’s email and HTML tag explanations applied to each of the other message types. formatting step, which is required under Petitioner’s assertions for limitation [10.7]. Ex. 2009 ¶¶57 (citing Ex. 1005, Fig. 10), 60 (citing Ex. 1005, Fig. 11), 64 (“[t]here is no formatting step for the SMS message, only for e-mail.”), 76 (“SMS messages . . . do not use HTML”); PO Sur-reply 27. Nor does Petitioner assert or explain that IM messages are formatted so as to teach the generating step of limitation [1.4]/[10.7]. Pet. 32 (“Rothschild’s server generates a hot link message when the web server formats the message data into an e-mail that contains the selected interactive advertisement.”). Because Petitioner’s “generating a hot link” assertions rely on the use of HTML (in email), and one of Rothschild’s listed communication types (SMS) does not use HTML, Petitioner fails to show persuasively that an artisan of ordinary skill would have interpreted each of Rothschild’s other listed types of personal communication as using HTML to generate a hot link in the claimed manner.” slip op. at 9

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Although Dr. Houh testifies that the use of IM would have been obvious, this testimony is a verbatim copy of what the Petition says on claim 5. Compare Ex. 1003 ¶¶ 80–81, 130–31 with Pet. 41. Dr. Houh cites to Rothschild’s list of communication types, but provides no analysis or reasoning or further evidence for his obviousness conclusion in the Houh Declaration. As such, it is a bare conclusory statement entitled to little or no weight. See 37 C.F.R. § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinions is based is entitled to little or no weight.”). We further note that although Dr. Houh relies upon Rothschild’s “interactive advertisement that is displayed with a graphic and includes an embedded URL,” Dr. Houh does not explain how each of the listed communication types (which include a voice message), or IM specifically, have these properties. Ex. 1003 ¶ 58.” slip op. at 11

  Patent outcomesUS 10,869,169 not shown unpatentable
  § 103 obviousness
  Patents in suitUS 10,869,169
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,570,034
• Meta Platforms, Inc. v. Sterling Computers CorporationAll claims unpatentable
  PTAB · 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 · KSR
  Patents in suitUS 7,716,217
• Røde Microphones, LLC / Freedman Electronics Pty Ltd. v. Zaxcom, Inc.No claims unpatentable
  PTAB · Jun 11, 2026 · IPR2025-00232 · APJ Miriam L Quinn · IPR · Final written decision

  The Board held that Petitioner did not prove any challenged claims of the ’207 patent unpatentable under the Strub, Woo, Nagai, and Gleissner obviousness ground.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “in these respects. The preambles of claims 17 and 59 recite the “audio device wearable by a user for storing locally generated audio.” There is neither mention of “multi-track” audio in the claim, nor is the audio device limited to capturing a single source of sound, such as a single performer. Accordingly, we are not persuaded that the ’443 and ’207 patent claims support the limited scope that Patent Owner urges for the term “locally generated audio.” None of Patent Owner’s citations to the specification define or require that the “locally generated audio” correspond to audio generated only by a single performer. See, e.g., 230 IPR, Ex. 1001, 8:59−62 (stating that the local audio input device “may be worn by the performer and connects to local audio device 102 at local audio input device port 314”). Patent Owner’s argument that the specification “teaches a single creator/performer per local audio device” is well-taken, but the teachings do not indicate the intent to exclude other sounds from being captured at the local audio device (or indicate how the device would prevent the capture of other sounds, such that the audio would be “isolated” as Patent Owner contends). See 230 Sur-Reply 10 (citing 230 IPR, Ex. 1001, 4:28−32, 10:29−34, and Insituform Techs., Inc. v. Cat Contr., Inc., 99 F.3d 1098, 1105 (Fed. Cir. 1996) (“[C]laim 1 refers to ‘a cup’ and ‘the cup’ repeatedly, suggesting that only one cup is involved . . . . [N]either the specification nor the drawings disclose the use of more than one cup.”)). For instance, the specification describes that the “independent track of audio is received from one of the performer’s local audio device 102.” 230 IPR, Ex. 1001, 10:33−34. Thus, in this description the audio track corresponds to the audio captured by a particular audio device—which was worn by the performer— but does not limit that captured audio to only sounds made by the performer. As to the “local audio data” term, Patent Owner argues that “audio data” means “mono or stereo audio files created from independent, isolated locally generated audio files, such files suitable for creation of a multi-track audio file.” 230 PO Resp. 9−10 (citing Ex. 2140 ¶¶ 131, 134). This argument is unsupported by the claim language or specification. The claim does not require the creation of audio files, much less a “multi-track audio file.” The specification describes storing audio files in memory without the specificity that Patent Owner urges we adopt. See 230 IPR, Ex. 1001, 13:1−14. Accordingly, we are not persuaded by Patent Owner’s proposed construction of “local audio data.” Rather, we understand “audio data” to have a plain and ordinary meaning, such as the one given to the term by the District Court in the underlying litigation. 230 IPR, Ex. 1037, 10. We adopt the District Court’s construction of “audio data” to mean “data comprising audio signals in digital form.” Id. This finds support in the specification as the audio is described as being converted into digital audio and stored in a file. See 230 IPR, Ex. 1001, 13:1−14. Our conclusion is consistent with the plain and ordinary meaning of the term as that would be understood by a person of ordinary skill in the art, and we see no reason to deviate from the conclusions of the District Court on this point.” slip op. at 20

  • Prior constructionPrior construction adoptedDecided for petitioner

    “data” means “mono or stereo audio files created from independent, isolated locally generated audio files, such files suitable for creation of a multi-track audio file.” 230 PO Resp. 9−10 (citing Ex. 2140 ¶¶ 131, 134). This argument is unsupported by the claim language or specification. The claim does not require the creation of audio files, much less a “multi-track audio file.” The specification describes storing audio files in memory without the specificity that Patent Owner urges we adopt. See 230 IPR, Ex. 1001, 13:1−14. Accordingly, we are not persuaded by Patent Owner’s proposed construction of “local audio data.” Rather, we understand “audio data” to have a plain and ordinary meaning, such as the one given to the term by the District Court in the underlying litigation. 230 IPR, Ex. 1037, 10. We adopt the District Court’s construction of “audio data” to mean “data comprising audio signals in digital form.” Id. This finds support in the specification as the audio is described as being converted into digital audio and stored in a file. See 230 IPR, Ex. 1001, 13:1−14. Our conclusion is consistent with the plain and ordinary meaning of the term as that would be understood by a person of ordinary skill in the art, and we see no reason to deviate from the conclusions of the District Court on this point.” slip op. at 21

  • Obviousness (§103) › Objective indicia / secondary considerations › Skepticism / industry praiseObjective indicia with nexusDecided for patent owner

    “1. Industry Praise: Academy and Emmy Awards Patent Owner argues that it “revolutionized [the] industry with the” slip op. at 97

  • Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersDecided for patent owner

    “2. Long-Felt Need Patent Owner further proffers the testimony of two witnesses as” slip op. at 104

  Patent outcomesUS 10,276,207 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,276,207
• Røde Microphones, LLC / Freedman Electronics Pty Ltd. v. Zaxcom, Inc.No claims unpatentable
  PTAB · Jun 11, 2026 · IPR2025-00230 · APJ Miriam L Quinn · IPR · Final written decision

  The Board determined that Petitioner had not shown any challenged claims of the ’443 or ’207 patents unpatentable, including under the asserted obviousness grounds.

  RulingsFinal written decision

  • Expert testimonySkill level petitioner adoptedOther

    “E. Level of Ordinary Skill in the Art Based on the argument and evidence presented in the Petition and Patent Owner’s preliminary response, we determined, as stated in our Decision on Institution, that “a person of ordinary skill in the art would have had a Bachelor’s degree in electrical engineering and two or more years of experience working with audio and wireless communications systems.” 230 Dec. on Inst. 16; 232 Dec. on Inst. 22−23. Patent Owner reiterates its position that a person of ordinary skill the art would have had “a bachelor’s degree in electrical engineering or a related subject and two to five years’ experience working with multi-track audio and wireless communications systems in the professional performance industry.” 230 IPR, PO Resp. 6−7 (emphasis added) (identical passage in 232 PO Resp. 8). Thus, the dispute centers on whether the level or ordinary skill includes specific work experience with multi-track audio in the professional performance industry. We do not agree that this specific work experience is necessary to the level of ordinary skill in the instant proceedings. In determining whether an invention would have been obvious at the time it was made, we consider the level of ordinary skill in the pertinent art at the time of the invention. Graham v. John Deere, 383 U.S. 1, 17−18 (1966). “The importance of resolving the level of ordinary skill in the art lies in the necessity of maintaining objectivity in the obviousness inquiry.” Ryko Mfg. Co. v. Nu‑Star, Inc., 950 F.2d 714, 718 (Fed. Cir. 1991). The “person of ordinary skill in the art” is a hypothetical construct, from whose vantage point obviousness is assessed. In re Rouffet, 149 F.3d 1350, 1357 (Fed. Cir. 1998). In determining the level or ordinary skill, we may consider various factors including “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, 57 F.3d 1573, 1579, (Fed. Cir. 1995) (quoting Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). Patent Owner’s proposed specificity of work with multi-track audio in a professional performance industry is not supported by the record. First, Patent Owner submits conclusory declaration testimony of James DeFilippis—repeating verbatim, and without any supported reasoning, Patent Owner’s proposed level of ordinary skill. Ex. 2140 ¶ 15. As such, the testimony is not persuasive. Second, Patent Owner’s additional declaration testimony of Jack” slip op. at 12

  • Prior constructionPrior construction adoptedDecided for petitioner

    “data” means “mono or stereo audio files created from independent, isolated locally generated audio files, such files suitable for creation of a multi-track audio file.” 230 PO Resp. 9−10 (citing Ex. 2140 ¶¶ 131, 134). This argument is unsupported by the claim language or specification. The claim does not require the creation of audio files, much less a “multi-track audio file.” The specification describes storing audio files in memory without the specificity that Patent Owner urges we adopt. See 230 IPR, Ex. 1001, 13:1−14. Accordingly, we are not persuaded by Patent Owner’s proposed construction of “local audio data.” Rather, we understand “audio data” to have a plain and ordinary meaning, such as the one given to the term by the District Court in the underlying litigation. 230 IPR, Ex. 1037, 10. We adopt the District Court’s construction of “audio data” to mean “data comprising audio signals in digital form.” Id. This finds support in the specification as the audio is described as being converted into digital audio and stored in a file. See 230 IPR, Ex. 1001, 13:1−14. Our conclusion is consistent with the plain and ordinary meaning of the term as that would be understood by a person of ordinary skill in the art, and we see no reason to deviate from the conclusions of the District Court on this point.” slip op. at 21

  • ExcludeMotion to exclude, deniedDenied

    “irrelevant under Federal Rules of Evidence 401–403. Patent Owner asserts that Petitioner has failed to establish that these documents reflect the understanding of a person of ordinary skill in the art, or that they are consumer-oriented documents, but not technical references or sources for understanding the meaning of claim terms. 230 IPR, Paper 64, 3−4. According to Patent Owner, these exhibits lack a “technical foundation” that establishes the technical meaning of a claim term. Id. We do not agree with Patent Owner as it conflates relevance with sufficiency of evidence to prove a contention on claim construction. Dictionary definitions are often useful when determining a claim term’s plain and ordinary meaning in the context of the specification, and as such are relevant when claim terms are disputed. Phillips, 415 F.3d at 1312. Furthermore, the evidence of record shows testimony as to whether the “Sweetwater” glossary entry for “body pack” would be relevant to the meaning of the term in the “world of wireless performance.” 230 IPR, Paper 67, 4 (citing Ex. 1073 ¶ 42). Patent Owner’s objections are overruled as to relevance.” slip op. at 116

  • BurdenFwd all claims patentableNot shown unpatentable

    “after a full and fair hearing, we determine that Petitioner has not demonstrated by a preponderance of the evidence that any of the challenged claims are unpatentable.” slip op. at 125

  Patent outcomesUS 7,711,443 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,711,443

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.