• 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
• 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
• Google LLC v. Brodti Inc.All claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00472 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious under § 103 over Nicholas, Laidlaw, Mayadas, and Error, with Yasnovsky added for claims 7, 8, 16, 17, and 20.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Petitioner’s and Patent Owner’s definitions for the level of ordinary skill in the art are substantially similar. In light of the record before us, we adopt Patent Owner’s proposal regarding the level of ordinary skill in the art. Based on our review of the ’898 patent and the prior art of record, we determine that the definition offered by Patent Owner comports with the qualifications a person would have needed to understand and implement the teachings of the ’898 patent and the prior art, particularly experience pertaining to Internet/web interfaces and web-based media. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need for testimony is not shown”) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). Neither party argues, nor do we determine, that the outcome of our Decision depends on which party’s definition is selected.” slip op. at 11

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

    “includ[e] a server and one or more webpages that may be provided by the server for display in a web browser.” Pet. Reply 5 (citing Ex. 1026 ¶¶ 13–15). Petitioner argues, and we agree, that the Specification strongly supports this construction (requiring a server and webpage(s)) by describing a “website” as synonymous with a server computer system: “The WWW [(World Wide Web)] service allows a server computer system (i.e., Web server or Web site) to send graphical Web pages or screens of information such as the advertising materials to a remote client computer system 10.” Ex. 1001, 3:66–4:2 (emphases added); see id. at Fig. 1 (depicting a service engine and webpages as a web server, i.e., website), 3:15–18 (describing Figure 1 as showing “a server of the website” (emphasis added)); Pet. Reply 5; see Ex. 1026 ¶ 13. Petitioner also submits a supporting (and persuasive) contemporaneous technical dictionary definition of “website,” which highlights the distinction between a lay person’s understanding of the term versus that of the relevant artisan. Pet. Reply 5–6. This definition explains that the “common but technically inaccurate” usage of “website” is to mean “Web page,” but the technically correct usage of “website” is to mean “one or more computers that are associated with a fully qualified domain name and make content available on the Web.” Id. (citing Ex. 1028, 402). Petitioner’s expert, Dr. Crovella, likewise testifies that “[a] website cannot exist without the server or computer that provides its webpages.” Ex. 1026 ¶ 15; see Ex. 1027, 36:8–20 (Patent Owner’s expert, Dr. Myler, agreeing that “it has to be some machine somewhere that’s providing the webpages for the website.”). The limitations of claim 1 also support Petitioner’s position that “website” includes a server and webpage(s). Reply 5. For example, claim 1 recites advertising material for “populat[ing] on one or more websites,” and selected “advertising buy options comprise at least one website of the respective websites.” Ex. 1001, 10:29–51 (emphases added). We find these limitations make the most technical sense where “website” implicates an Internet domain or domain name, such as brodti.com, which itself is a computer system (server) and associated webpage(s) reached via that domain name. This interpretation aligns with testimony of Patent Owner’s expert, Dr. Myler, in which he states that a “website” describes “a group of webpages at a particular domain (e.g., www.espn.com, www.espn.com/nba, www.espn.com/nfl, www.espn.com/nhl).” Ex. 2009 ¶ 68 (emphasis in italics added). In other words, brodti.com and espn.com are two different websites, with each website having one or more webpages (e.g., www.espn.com/nba, www.espn.com/nfl), and such websites include a server giving life to such webpage(s). slip op. at 15

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

    “Patent Owner proffers that placing advertising material “within” web property content means “inserting” an advertisement into particular content. PO Resp. 12. Petitioner responds that “placing . . . within” means what it says, and notes that “[t]he words ‘insert’ or ‘inserting’ appear nowhere in the [Specification].” Pet. Reply 7–8; see id. at 8 (Petitioner arguing that Patent Owner’s expert “admitted that the claim does not specify details regarding how advertising material needs to be placed within web property content.” (citing Ex. 1027, 29:18–24)). Patent Owner replies that the relevant artisan allegedly “would have understood ‘placing . . . within’ to mean ‘inserting into,’” but then submits that whether “placing . . . within” versus “inserting into” is used does not matter because Petitioner allegedly has not demonstrated the obviousness of either. PO Sur-reply 17. As Petitioner observes, “[i]t is unclear if Patent Owner intended any difference in meaning between these two terms.” Pet. Reply 8. Accordingly, based on the complete record before us, we determine that no further construction of this limitation is needed, and “placing A within B” means what it says—“placing A within B.”” slip op. at 20

  • Expert testimonyPetitioner expert creditedOther

    “determining” of impression validity feature of limitation 1[h] by disclosing “a ‘single-pixel’ image technique for determining that an impression is valid,” e.g., by using “cookies.” Pet. 42–45. Petitioner’s expert, Dr. Crovella, testifies that this “single-pixel” impression tracking technique would have been a “well-known” technique to the relevant artisan, and as described by Error, operates as follows: [A] URL link for a single pixel (or transparent) image file is embedded onto a webpage that is delivered to a web browser. The image is not meant to be viewed and will likely not be visible to the user. After the user’s browser receives the webpage, it uses the embedded URL link to request the single-pixel image from a server. The receipt of that request by the server provides an indication that the user’s web browser actually received and presented the web page to the user. Ex. 1002 ¶ 133 (citing Ex. 1007, 1:36–54, 2:6–21); see id. at ¶¶ 132–139. slip op. at 43

  Patent outcomesUS 11,416,898 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,416,898
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

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

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

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

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentable
  PTAB · Jun 11, 2026 · IPR2022-01151 · APJ Kevin F Turner · IPR · Remand

  On remand, the Board held claims 1, 24, and 25 unpatentable as obvious over Buruganahalli; the copying evidence did not outweigh the strong obviousness showing.

  RulingsRemand decision

  • RemandOther

    “Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4

  • Obviousness (§103) › Objective indicia / secondary considerations › CopyingObjective indicia outweighedDecided for petitioner

    “given to the Eastern District of Virginia court’s opinion because it was later vacated. The district court considered all of the Read factors (applying Read Corp. v. Portec, Inc., 970 F.2d 816, 826-827 (Fed. Cir. 1992)), of which only the first factor is directed to deliberate copying, although factors 2 and 9 bear indirectly on the issue of copying. The district court determined that “[t]he fact that Cisco released products with Centripetal’s functionality within a year of these meetings goes beyond mere coincidence. Therefore, the fact that Cisco’s system mirrors the functionality of the Centripetal patents is compelling evidence that damages should be enhanced for copying.” Ex. 1027, 157. Without more, it is difficult to evaluate the processes that the district court employed to reach its determination. As the Federal Circuit instructed, we need “not [] go searching throughout the entire litigation record to find the evidence of copying, but [we have] an obligation to consider the specific evidence that was put before” us. Centripetal Networks, 19. We continue to determine that the vacated finding of the district court should be provided little weight, especially in view of the strong case of obviousness discussed above.” slip op. at 40

  • Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersObjective indicia outweighedDecided for petitioner

    “need and industry recognition for the technology claimed in the ‘856 Patent because it describes the problem of detecting threats in encrypted traffic as ‘unsolvable.’” PO Resp. 68 (citing Ex. 1027, 64). Given that this is a press release by a company announcing that company’s new commercial product, however, we 8 The concurrence reevaluates Patent Owner’s evidence of industry praise and nexus, but we deem such considerations outside the remit of the Federal Circuit’s remand. are reluctant to give the “unsolvable” characterization much weight, as it may amount to puffery. But beyond that, it appears that the problem identified as “unsolvable” in the press release––“detect[ing] known attack signatures even in encrypted traffic”––had, in fact, already been solved in Buruganahalli, using the very same hello message, flow correlation, and man-in-the-middle techniques described in the ‘856 Patent. We thus cannot say that the press release identifies a long-felt need that was actually unsolved. See ZUP, 896 F.3d at 1374 (explaining that “[w]here the differences between the prior art and the claimed invention are . . . minimal . . . it cannot be said that any long-felt need was unsolved”) (quoting Geo. M. Martin Co. v. All. Mach. Sys. Int’l LLC, 618 F.3d 1294, 1304–05 (Fed. Cir. 2010) (first alteration in original)).” slip op. at 35

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “The District Court did not provide an element-by-element analysis of how the claims of the ‘856 Patent cover this description. See Ex. 1027, 41. However, from the description, we understand the Court to have concluded that the system receives rules, identifies a set of packets as part of a flow using the NetFlow logs, “determines” that encrypted packets in the flow match known malicious signatures based on unencrypted data in other packets (e.g., data in the SNI), and then filters the flow based in a URI (e.g., that from the SNI), routing it to the null interface. The Court does not describe how the system “determines” that encrypted packets match known malicious signatures based on information in unencrypted packets, but we assume that is done as in the ‘856 Patent, by correlation, i.e., an encrypted packet is “determined” to match a threat indicator if it is in the same flow as a packet with unencrypted information that matches the threat indicator.10 With that understanding, we conclude that the allegedly infringing system operates, as least at the level described in the court’s decision, in the same way Buruganahalli’s system operates, filtering encrypted packets due to their presence in a flow that includes packets with unencrypted data, such as in a handshaking packet. It follows that Patent Owner is unable to establish a nexus, because “[w]here the offered secondary consideration actually results from something other than what is both claimed and novel in the claim, there is no nexus to the merits of the claimed invention.” Novartis AG v. Torrent Pharms. Ltd., 853 F.3d 1316, 1330 10 See Ex. 1001, 9:3–10 (explaining that, at step 17, rule gate 120 may “determine . . . that the packets comprise data corresponding to the network-threat indicators, for example, by correlating the packets with one or more packets previously determined . . . to comprise data corresponding to the network-threat indicators based on data stored in [the] logs”).” slip op. at 38

  Patent outcomesUS 9,917,856 unpatentable
  § 103 obviousness
  Patents in suitUS 9,917,856
• Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentable
  PTAB · Jun 11, 2026 · IPR2022-01199 · APJ Kevin F Turner · IPR · Remand

  On remand, the Board held claims 1, 24, and 25 unpatentable as obvious over Buruganahalli; the copying evidence did not outweigh the strong obviousness showing.

  RulingsRemand decision

  • RemandOther

    “Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4

  • Director reviewDirector review, deniedDenied

    “not object to a new panel of APJs hearing this case if remanded.” Id. at 20. As such, Patent Owner requested Director Review (Paper 74), asking that the Director “de-institute,” based on an abuse of discretion. The Director (Paper 75) denied the request and directed the Board to assign a new panel on remand (see Papers 76, 77). B.” slip op. at 3

  • Skill levelOther

    “Level of Ordinary Skill in The Art We adopt the level of ordinary skill in the art adopted in the prior Decision. See Decision 25. F.” slip op. at 13

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “This argument is unpersuasive because Buruganahalli uses rules/policies to filter encrypted packets by correlating them with handshaking packets that have unencrypted data, in the same way that is done in the ‘856 Patent. The only “filtering step” in the patent that “use[s] rules to filter encrypted packets without decryption” (PO Resp. 20) is the hello message approach used, for example, at steps 19 and 23 (see id.), which is clearly disclosed in Buruganahalli.7 As explained above, the ‘856 Patent does not describe applying rules to encrypted packets. Instead, it describes (a) filtering encrypted packets by correlating them with unencrypted data in other packets and (b) by decrypting the packets and applying the rules that are recited in the claims to unencrypted data. As also explained above, the amendment added the rules of step 22, which are applied to decrypted data, to a claim that was drafted to cover filtering of encrypted packets. However, among the criteria used in the filtering performed at step 22 is a “uniform resource identifier (URI),” which, we conclude, covers Buruganahalli’s “domain name.” Thus, despite the error made during prosecution, the claims that issued cover Buruganahalli’s method of determining that a session should be filtered based on a domain name in unencrypted handshake data.” slip op. at 28

  Patent outcomesUS 9,917,856 unpatentable
  § 103 obviousness
  Patents in suitUS 9,917,856
• Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentable
  PTAB · Jun 11, 2026 · IPR2022-00182 · APJ Kevin F Turner · IPR · Remand

  On remand, claims 1, 24, and 25 are unpatentable under § 103 over Buruganahalli; the evidence of copying does not outweigh the strong obviousness showing.

  RulingsRemand decision

  • RemandOther

    “Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4

  • Obviousness (§103) › Objective indicia / secondary considerations › CopyingObjective indicia outweighedNot shown unpatentable

    “given to the Eastern District of Virginia court’s opinion because it was later vacated. The district court considered all of the Read factors (applying Read Corp. v. Portec, Inc., 970 F.2d 816, 826-827 (Fed. Cir. 1992)), of which only the first factor is directed to deliberate copying, although factors 2 and 9 bear indirectly on the issue of copying. The district court determined that “[t]he fact that Cisco released products with Centripetal’s functionality within a year of these meetings goes beyond mere coincidence. Therefore, the fact that Cisco’s system mirrors the functionality of the Centripetal patents is compelling evidence that damages should be enhanced for copying.” Ex. 1027, 157. Without more, it is difficult to evaluate the processes that the district court employed to reach its determination. As the Federal Circuit instructed, we need “not [] go searching throughout the entire litigation record to find the evidence of copying, but [we have] an obligation to consider the specific evidence that was put before” us. Centripetal Networks, 19. We continue to determine that the vacated finding of the district court should be provided little weight, especially in view of the strong case of obviousness discussed above. Examination of Aaron Striegel We also do not find the Aaron Striegel’s testimony to be particularly persuasive. The testimony provides statements such as “I found evidence that it could be plausible,” “[s]o we can see the timeline is very plausible,” and “I found it very plausible that indeed that this technology could have made its way into these respective accused products.” Ex. 1029, 31:12–32:3. This testimony suggests the possibility of copying but does not demonstrate actual evidence of copying. At most, this testimony indicates that further consideration of the underlying evidence is warranted, but does little to support an ultimate finding of copying. Again, even taking this testimony as evidence of copying, it still must stand up against the strong case of obviousness discussed above.” slip op. at 40

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “The District Court did not provide an element-by-element analysis of how the claims of the ‘856 Patent cover this description. See Ex. 1027, 41. However, from the description, we understand the Court to have concluded that the system receives rules, identifies a set of packets as part of a flow using the NetFlow logs, “determines” that encrypted packets in the flow match known malicious signatures based on unencrypted data in other packets (e.g., data in the SNI), and then filters the flow based in a URI (e.g., that from the SNI), routing it to the null interface. The Court does not describe how the system “determines” that encrypted packets match known malicious signatures based on information in unencrypted packets, but we assume that is done as in the ‘856 Patent, by correlation, i.e., an encrypted packet is “determined” to match a threat indicator if it is in the same flow as a packet with unencrypted information that matches the threat indicator.10 With that understanding, we conclude that the allegedly infringing system operates, as least at the level described in the court’s decision, in the same way Buruganahalli’s system operates, filtering encrypted packets due to their presence in a flow that includes packets with unencrypted data, such as in a handshaking packet. It follows that Patent Owner is unable to establish a nexus, because “[w]here the offered secondary consideration actually results from something other than what is both claimed and novel in the claim, there is no nexus to the merits of the claimed invention.” Novartis AG v. Torrent Pharms. Ltd., 853 F.3d 1316, 1330” slip op. at 38

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

    “need and industry recognition for the technology claimed in the ‘856 Patent because it describes the problem of detecting threats in encrypted traffic as ‘unsolvable.’” PO Resp. 68 (citing Ex. 1027, 64). Given that this is a press release by a company announcing that company’s new commercial product, however, we 8 The concurrence reevaluates Patent Owner’s evidence of industry praise and nexus, but we deem such considerations outside the remit of the Federal Circuit’s remand. are reluctant to give the “unsolvable” characterization much weight, as it may amount to puffery. But beyond that, it appears that the problem identified as “unsolvable” in the press release––“detect[ing] known attack signatures even in encrypted traffic”––had, in fact, already been solved in Buruganahalli, using the very same hello message, flow correlation, and man-in-the-middle techniques described in the ‘856 Patent. We thus cannot say that the press release identifies a long-felt need that was actually unsolved. See ZUP, 896 F.3d at 1374 (explaining that “[w]here the differences between the prior art and the claimed invention are . . . minimal . . . it cannot be said that any long-felt need was unsolved”) (quoting Geo. M. Martin Co. v. All. Mach. Sys. Int’l LLC, 618 F.3d 1294, 1304–05 (Fed. Cir. 2010) (first alteration in original)).” slip op. at 35

  Patent outcomesUS 9,917,856 unpatentable
  § 103 obviousness
  Patents in suitUS 9,917,856
• Stingray Group Inc. / Stingray Music USA, Inc. v. Edwin A. Hernandez-MondragonSome claims unpatentable
  PTAB · Jun 10, 2026 · IPR2025-00350 · APJ Jason M Repko · IPR · Final written decision

  Claims 7–12 were held unpatentable over Wannamaker alone or with Avellan; claims 1–6 and 13 were not shown unpatentable because Avellan did not teach the claimed screen-capture sequence and assembly.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “Patent Owner submits a similar definition and does not take issue with the Petition’s characterization of the level of ordinary skill in the art. PO Resp. 17. We determine that no express finding is necessary and that the level of ordinary skill in the art is reflected by the prior art of record. Any perceived difference in how each party characterizes a POSITA’s education, knowledge, and work experience does not change our analysis or conclusions.” slip op. at 5

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

    “Neither party has offered any claim construction arguments, relying on ordinary and customary meaning. Pet. 19–20; PO Resp. 18. We determine that construction of claim terms is not necessary to resolve the disputes raised by the parties in this proceeding.” slip op. at 5

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Yet paragraph 122 of Mr. Lipoff’s declaration merely repeats the Petition’s argument almost verbatim. Compare Ex. 1007 ¶ 122, with Pet. 28. Mr. Lipoff does not add any citation to Avellan or any other source that supports his testimony. See Ex. 1007 ¶ 122. Nor does Mr. Lipoff offer any additional technical reasoning than what is stated in the Petition. Testimony may be entitled to little weight if it merely restates the petition’s unsupported, conclusory assertions without adding supporting evidence or technical reasoning. Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential). That is the case here.” slip op. at 8

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “We are persuaded by Patent Owner’s argument that claim 1 is not obvious over Avellan because it does not assemble a media stream of multimedia items using the recited screen captures. See PO Resp. 21–23. We agree with Patent Owner that the plain language of the claim requires more than transmitting individual media items. PO Sur-reply 20. To the extent that Avellan captures images, those images do not meet the claimed requirements for a “temporal sequence of screen captures” in the independent claims, which must (1) be of the web page rendered by a browser, (2) “define all the content of the web page at a given time,” (3) “illustrate a dynamic change of at least a portion of the content over time” when two of them are compared, and (4) used to assemble “the at least one media stream.” Rather, the record better supports Patent Owner’s argument that Avellan transmits the multimedia items separate from any media stream assembled from screen captures. PO Resp. 21–23; PO Sur-reply 20.” slip op. at 7

  Patent outcomesUS 10,524,002 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
  Patents in suitUS 10,524,002
• Stingray Group Inc. / Stingray Music USA, Inc. v. Edwin A. Hernandez-MondragonNo claims unpatentable
  PTAB · May 29, 2026 · IPR2025-00349 · APJ Jason M Repko · IPR · Final written decision

  Claims 1–21 were not shown unpatentable because Avellan did not disclose the claimed sequence of screen captures used to assemble a media stream.

  RulingsFinal written decision

  • Skill levelOther

    “Patent Owner submits a similar definition and does not dispute the Petition’s characterization of the level of ordinary skill in the art. PO Resp. 22. No express finding is necessary. The level of ordinary skill in the art is reflected by the prior art of record. Any perceived difference in how each party characterizes a POSITA does not change our analysis or conclusions.” slip op. at 5

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

    “on ordinary and customary meaning. Pet. 14–15; PO Resp. 22. We determine that construction of claim terms is not necessary to resolve the disputes raised by the parties in this proceeding.” slip op. at 6

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “c. Analysis “A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros. v. Union Oil Co. of California, 814 F.2d 628, 631 (Fed. Cir. 1987). We are persuaded by Patent Owner’s argument that Avellan does not anticipate claim 1 because it does not assemble a media stream of multimedia items using the recited screen captures. See PO Resp. 26–29. We agree with Patent Owner that the plain language of the claim requires more than transmitting individual media items. Sur-reply 21. To the extent that Avellan captures images, those images do not meet the claimed requirements for a “temporal sequence of screen captures” in the independent claims, which must (1) be of the web page rendered by a browser, (2) “define all the content of the web page at a given time,” (3) “illustrate a dynamic change of at least a portion of the content over time” when two of them are compared, and (4) used to assemble “the at least one media stream.” Rather, the record better supports Patent Owner’s argument that Avellan transmits the multimedia items separate from any media stream assembled from screen captures. PO Resp. 26–29; Sur-reply 21.” slip op. at 8

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “All other challenged claims require the “generating” and “assembling” operations because they depend from claims 1, 12, or 17. Petitioner does not allege that the additional references—Durante, Ma, Suzuki, Wanamaker, Heikens, Matthews, or Wilsher—teach or suggest the “temporal sequence of screen captures” recited in claim 1. Rather, Petitioner’s reasoning in the challenges to the dependent claims pertaining to the screen captures mirror the rationale presented in the independent claim. See, e.g., Pet. 25 (arguing that Avellan’s screen captures correspond to the video content in the challenge to claim 2), 26–27 (arguing that Avellan obtains screen captures from a playback of a video on the webpage in the challenge to claim 4). Petitioner’s argument that Avellan teaches or suggests these operations in the grounds based on obviousness under 35 U.S.C. § 103 depend on the reasoning and insufficiently supported characterizations of Avellan in the challenges based on 35 U.S.C. § 102, as discussed above. See Pet. 40–60. grounds based on anticipation under 35 U.S.C. § 102 or teaches or suggests these operations in the grounds based on obviousness under 35 U.S.C. § 103, Petitioner has not met its burden to show that any challenged claim is unpatentable as anticipated by Avellan or obvious over any of the combinations of Avellan and the other cited references.” slip op. at 15

  Patent outcomesUS 10,123,074 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 10,123,074
• Stingray Group Inc. / Stingray Music USA, Inc. v. Edwin A. Hernandez-MondragonSome claims unpatentable
  PTAB · May 28, 2026 · IPR2025-00351 · APJ Brian P Murphy · IPR · Final written decision

  Claims 1–9 are unpatentable as obvious over the stated combinations; claims 10–26 were not shown unpatentable because Avellan does not teach limitations [10d]–[10f].

  RulingsFinal written decision

  • Skill levelOther

    “would have a bachelor’s or equivalent degree in computer science or a related field and at least 2 years of experience in multimedia processing or delivery using internet protocols.” Pet. 10 (citing Ex. 1002 ¶¶ 67–68). The Petition further states that “a person with less formal education but more experience, or more formal education but less experience, could have also met the relevant standard for a POSITA.” Id. Patent Owner submits a similar definition and does not take issue with the Petition’s characterization of the level of ordinary skill in the art of delivering multimedia content. Resp. 18. We determine that no express finding is necessary and that the level of ordinary skill in the art is reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Any perceived difference in how each party characterizes a POSITA’s education, knowledge, and work experience does not change our analysis or conclusions. slip op. at 7

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “Neither party has offered any claim construction arguments, relying on ordinary and customary meaning. Pet. 11; Resp. 18–19; Reply 5. We determine that construction of claim terms is not necessary to resolve the disputes raised by the parties in this proceeding. 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., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 8

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element) › Inherent disclosureInherency not foundNot shown unpatentableNot shown unpatentable

    “To establish inherency, the extrinsic evidence “must make clear that the missing descriptive matter is necessarily present in the thing described in the reference, and that it would be so recognized by persons of ordinary skill.” Continental Can Co. v. Monsanto Co., 948 F.2d 1264, 1268 (Fed. Cir. 1991). “‘Inherency, however, may not be established by probabilities or possibilities. The mere fact that a certain thing may result from a given set of circumstances is not sufficient.’” Id. at 1269 (quoting In re Oelrich, 666 F.2d 578, 581 (C.C.P.A. 1981)). Reasonable inferences of a POSITA may suffice to establish inherent disclosure in a prior art reference such as Farber. See Eli Lilly v. Los Angeles Biomedical Research Institute, 849 F.3d 1073, 1074–1075 (Fed. Cir. 2017) (“[T]he dispositive question regarding anticipation is whether one skilled in the art would reasonably understand or infer from a prior art reference that every claim element is disclosed in that reference.”). Here, however, we find the Petition’s argument and evidence insufficient to establish by a preponderance of the evidence that Farber inherently discloses limitation [1b].” slip op. at 16

  Patent outcomesUS 11,140,441 mixed
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 11,140,441

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.