• Genius Sports Ltd. v. Sportscastr Inc. D/B/A Panda InteractiveAll claims unpatentable
  PTAB · Aug 27, 2026 · IPR2024-01310 · APJ Stephen E Belisle · IPR · Remand

  On Director remand, the Board determined claims 1–15 unpatentable under § 103, including claims 1–11 over Ellis, Spivey, and Herzog.

  RulingsRemand decision

  • RemandOther

    “all Challenged Claims unpatentable and denying Petitioner’s Motion to Exclude. Paper 47 (“Original Final Decision”). Subsequently, Patent Owner filed a Request for Director Review and Petitioner filed an authorized Response thereto. Papers 48, 49. On July 29, 2026, the Director granted review, vacated-in-part the Original Final Decision, and remanded the case to the Board. Paper 50. In particular, the Director directed the Board “to consider Patent Owner’s arguments as to the webserver limitation in deciding whether Petitioner has established by a preponderance of the evidence that claims 1–11 are unpatentable under Petitioner’s Ground 1B.” Id. at 4. We do so in this Final Written Decision on Remand (“Remand Decision”). See infra § III.E (Ground 1B). For completeness, we repeat herein our analysis in the Original Final Decision for all other grounds.” slip op. at 2

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

    “C. Claim Construction We construe claims “using the same claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. 282(b), including construing the claim in accordance with the ordinary and customary meaning of such claim as understood by one of ordinary skill in the art and the prosecution history pertaining to the patent.” 37 C.F.R. § 42.100(b); see also Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). In this context, claim terms “are generally given their ordinary and customary meaning” as understood by a person of ordinary skill in the art in question at the time of the invention. Phillips, 415 F.3d at 1312–13; see CCS Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366 (Fed. Cir. 2002) (There is “a ‘heavy presumption’ that a claim term carries its ordinary and customary meaning.”). “In determining the meaning of the disputed claim limitation, we look principally to the intrinsic evidence of record, examining the claim language itself, the written description, and the prosecution history, if in evidence.” DePuy Spine, Inc. v. Medtronic Sofamor Danek, Inc., 469 F.3d 1005, 1014 (Fed. Cir. 2006) (citing Phillips, 415 F.3d at 1312–17). Extrinsic evidence is “less significant than the intrinsic record in determining ‘the legally operative meaning of claim language.’” Phillips, 415 F.3d at 1317. Petitioner contends that “[t]he claim terms of the ’218 [patent] should be given their plain and ordinary meaning” as understood by the relevant artisan. Pet. 6. Petitioner argues that the relevant artisan “would have understood a ‘socket’ to be a uniquely addressable communication endpoint on a server where first event information is provided to a [viewer client device] VCD.” Pet. 26 (citing Ex. 1001 ¶ 170). Petitioner argues that the relevant artisan also would have understood an “event socket,” in turn, to be “a socket where information about one sporting event is provided to VCDs.” Id. Beyond such proposed plain meanings for “socket” and “event” slip op. at 14

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

    “(6) Conclusion as to Objective Indicia of Non- Obviousness For the foregoing reasons, although we have considered Patent Owner’s evidence of objective indicia of nonobviousness, we accord it little weight, and find that it does not outweigh Petitioner’s strong countervailing evidence supporting a conclusion of obviousness.” slip op. at 53

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “engineer with substantial experience in Internet video streaming, Internet communication, and related protocols, including an understanding of relaytype and orchestrator-type webservers, would have considered the subject matter of claim 1 as a whole, including the webserver, to be obvious in light of the combined teachings of Ellis, Spivey, and Herzog. Based on the context discussed above, and for the reasons provided above, we determine that the answer is yes. See Fleming v. Cirrus Design Corp., 28 F.4th 1214, 1222 (Fed. Cir. 2022) (“That the proposed combination of [two references]—rather than one of the individual references—discloses the disputed claim limitations does not defeat the Board’s conclusion of obviousness. In this case, it is sufficient that [the relevant artisan] would have been motivated to combine the prior art in a way such that the combination discloses the claim limitations.”).” slip op. at 78

  Patent outcomesUS 11,039,218 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,039,218
• 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 Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

  Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11

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

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms … that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). D.” slip op. at 12

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

    “search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24

  Patent outcomesUS 7,370,035 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,370,035
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

    “In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23

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

    “different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27

  Patent outcomesUS 10,552,490 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 10,552,490
• 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
• 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
• AT&T Services, Inc. / Cellco Partnership D/B/A Verizon Wireless et al. v. Pegasus Wireless Innovation LLCAll claims unpatentable
  PTAB · Jun 2, 2026 · IPR2025-00083 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–9 are unpatentable as obvious over Takeda and Yan; the Board found the alternative Marinier, Yan, and R1-1711853 ground insufficient.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “had “a bachelor’s degree in electrical engineering, computer engineering, or a related discipline, knowledge of the relevant 3GPP standards” and “at least 2 years of experience working in a field involving wireless communications.” Pet. 10 (citing Ex. 1002 ¶¶ 38–40). According to Petitioner, a “person with a different degree but with additional relevant experience could still qualify if the additional experience compensates for the different educational background.” Id. Petitioner also asserts a “person with less than 2 years of experience working in a field involving wireless communications could still qualify if the person has additional education that compensate[s] for their lesser experience.” Id. Patent Owner does not dispute Petitioner’s proposed level of skill. See generally PO Resp. We find that “at least” in Petitioner’s formulation of the level of skill in the art is vague and open-ended. Otherwise, we adopt Petitioner’s formulation of the level of ordinary skill in the art, because it appears consistent with the ’463 Patent Specification and the prior art of record.” slip op. at 8

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)Not reached

    “Petitioner asserts that elements 1[b] and 1[c] constitute a mean-plus- function limitation under 35 U.S.C. § 112(f) and Patent Owner disputes Petitioner’s assertion. See Pet. 5–7; PO Resp. 11–13. As demonstrated below, there is no dispute as to whether the prior art teaches limitations 1[b] and 1[c] under Petitioner’s claim construction. Therefore, we need not address whether 35 U.S.C. § 112 (f) applies. “The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner

    “We do not agree with Patent Owner’s arguments disputing Petitioner’s backward compatibility rationale for combining the teachings of Yan and Takeda. Patent Owner’s arguments are misplaced because they are premised incorrectly on Takeda’s teachings being limited to 5G NR (i.e., standalone 5G NR), and the proposed combination requiring “mixing standards and behaviors.” To the contrary, Petitioner explicitly asserts that “Takeda states that its teachings are applicable to both 4G and 5G”––i.e., non-standalone 5G. Pet. 14 (citing Ex. 1007 ¶ 239). Likewise, instead of mixing 5G and 4G standards and behaviors as argued by Patent Owner, Petitioner merely proposes retaining Yan’s 4G method of allocating UL channel resources sets with Takeda’s teaching of 5G NR BWPs. See Pet. 14–15. We credit Dr. Roy’s testimony that a person of ordinary skill in the art would have been motivated to modify Takeda’s teachings with Yan’s teachings to provide Takeda with backwards network capability because it is supported by the cited evidence of record. See Ex. 1002 ¶¶ 105, 106 (citing Ex. 1007 ¶ 239; Ex. 1031, 1, 3; Ex. 1033, 5:23–31; Ex. 1034, 10; Ex. 1035, 1, 5; Ex. 1037, 31). Moreover, as pointed out by Petitioner, Dr. Shimony’s deposition testimony regarding the usefulness of backward compatibility and the importance of a non-standalone UE having the ability to communicate over both 4G and 5G standards supports Dr. Roy’s testimony, yet undermines Patent Owner’s arguments. See Ex. 1050, 178:16–182:16; Pet. Reply 14–15. Based on the entire record developed during trial, we are persuaded by a preponderance of the evidence that Petitioner provides sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to a person of ordinary skill in the art to modify Takeda’s teachings with Yan’s teachings to provide Takeda with backwards network compatibility.10 See Pet. 13–15; KSR, 550 U.S. at 418.” slip op. at 15

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “We credit Dr. Roy’s testimony that a person of ordinary skill in the art would have been motivated to modify Takeda’s teachings with Yan’s teachings to provide Takeda with backwards network capability because it is supported by the cited evidence of record. See Ex. 1002 ¶¶ 105, 106 (citing Ex. 1007 ¶ 239; Ex. 1031, 1, 3; Ex. 1033, 5:23–31; Ex. 1034, 10; Ex. 1035, 1, 5; Ex. 1037, 31). Moreover, as pointed out by Petitioner, Dr. Shimony’s deposition testimony regarding the usefulness of backward compatibility and the importance of a non-standalone UE having the ability to communicate over both 4G and 5G standards supports Dr. Roy’s testimony, yet undermines Patent Owner’s arguments. See Ex. 1050, 178:16–182:16; Pet. Reply 14–15. Based on the entire record developed during trial, we are persuaded by a preponderance of the evidence that Petitioner provides sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to a person of ordinary skill in the art to modify Takeda’s teachings with Yan’s teachings to provide Takeda with backwards network compatibility.10 See Pet. 13–15; KSR, 550 U.S. at 418.” slip op. at 15

  Patent outcomesUS 10,638,463 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,638,463
• Genius Sports Ltd. v. Sportscastr Inc. D/B/A Panda InteractiveAll claims unpatentable
  PTAB · Mar 13, 2026 · IPR2024-01311 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 16–30 are unpatentable: claims 16–30 as obvious over Ellis and Spivey, claims 21, 22, 27, and 28 as anticipated by Herzog, and claims 25, 26, and 30 as obvious over Herzog and Ellis.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner contends that the relevant artisan would have had “a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent degree and, in addition, approximately two years of work experience with Internet video streaming, Internet communication, and related protocols.” PO Resp. 12. Neither party argues that the outcome of this case would differ based on our adoption of any particular definition of the level of ordinary skill in the art. We apply Patent Owner’s definition of the relevant artisan because, based on the record, this proposal is most consistent with the ’218 patent and the asserted prior art, and is supported by the testimony of both Dr. Wicker and Dr. Rubin (see Ex. 1001 ¶¶ 72–76; Ex. 2001 ¶¶ 96–98). We note that we would reach the same determination under Petitioner’s formulation of the level of ordinary skill.” slip op. at 13

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

    “Accordingly, Petitioner’s proposed plain meanings of “socket” and “event socket” (Pet. 32–33) are not disputed by Patent Owner. PO Resp. 2, 12. In fact, by arguing that Spivey’s topic queues are neither “uniquely addressable” nor “communication endpoints,” Patent Owner appears to adopt Petitioner’s proposed plain meaning of “socket” as a “uniquely addressable communication endpoint.” Id. As Patent Owner acknowledged during Oral Argument, “I don’t think there’s any dispute of what we mean by socket, a uniquely addressable communication endpoint.” Tr. 73:10–12. Based on the foregoing, we construe each of “socket” and “event socket” to have its plain and ordinary meaning, where the relevant artisan would have understood “socket” to mean “a uniquely addressable communication endpoint on a server,” and “event socket” to mean “a socket where information about one sporting event is provided to a viewer client device (VCD).” 2 We further address these terms below in Section III.D.3. 2 During Oral Argument, Patent Owner argued, for the first time, that the District Court’s construction of “event socket” “should be applied equally here.” Tr. 73:13–76:24 (referring to Ex. 1069). The Court adopted Petitioner’s (Defendant’s) proposed definition of “event socket” as “a socket dedicated to a particular event” (Ex. 1069, 11–15), although in its summary of constructions, labeled “event socket” as being “a socket dedicated to a single event” (i.e., “single” event versus “particular” event) (id. at 26). Regardless, in the context of this case and this Decision, we find no meaningful difference between these articulations and Petitioner’s plain” slip op. at 15

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “As Petitioner explained during Oral Argument, Ellis “relates to the ability for the clients and the server to communicate,” which can be any system that can “provide real-time sports,” but “doesn’t discuss whether it’s a push system or a pull system,” whereas Spivey, on the other hand, “expressly indicates that it is a push type of data system which reduces latency over prior art systems that utilize push technologies.” Tr. 15:13–19. We find availing Petitioner’s contention that, “[a]s explained by Dr. Wicker, . . . [the relevant artisan] would have been motivated to implement real-time data delivery using Spivey’s data pushing technique to reduce latency.” Id. at 16:2–8. “[I]f 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 unless its actual application is beyond his or her skill.” KSR, 550 U.S. at 417. We find unavailing Patent Owner’s contention that Petitioner fails to “articulate why [the relevant artisan] would have been motivated to make the necessary modifications and proposed combination.” PO Resp. 40–41. Here, Petitioner points out that its proposed combination would have been made to improve latency issues in Ellis’s system. Pet. 23–26. In particular, Spivey discloses that its techniques “may reduce . . . delay [on the order of seconds (e.g., 30 to 45 seconds) or minutes] to an order of milliseconds (ms) (e.g., 100 ms) or less, providing a significant advantage over the conventional practices.” Ex. 1017 ¶ 28. Spivey also discloses pushing data to the “subscribed connected client devices” substantially simultaneously with the message queue server receiving the topic entry from a live data source, e.g., “with a time delay of 100 milliseconds or less,” which Spivey discloses is “at least two orders of magnitude shorter than conventional time periods of legacy devices.” Id. ¶ 96; see also id. at code (57) (disclosing pushing “the topic entry to a subscribed client device substantially simultaneously with the message queue server receiving the topic entry from a live data source”).” slip op. at 28

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

    “Considering the totality of the evidence, we find Patent Owner has not demonstrated that a long-felt but unresolved need existed for the claimed invention. See Apple v. Samsung, 839 F.3d at 1056. As Petitioner points out, although Patent Owner argues that there is a long-felt need for a system that “allows broadcasters to deliver synchronized, low-latency video and audio content” (PO Resp. 65), Patent Owner does not contest Petitioner’s showing that Ellis also discloses “a video streaming system that provided event information over a separate channel, which is not hard embedded in the video stream.” Pet. Reply 25. Further, as Petitioner points out in the context of “representative claim 12,” the claim “simply requires ‘receiv[ing] the first copy via a first video communication channel between at least one media source and the first client device,’” and “[i]n no way does that claim language relate to any synchronized, low-latency, scalable, flexible, or new and improved video streaming technique.” Pet. Reply 22. In fact, during Oral Argument, although Patent Owner argues that its invention is “the synchronization and the latency improvements through that one-to-many socket architecture,” Patent Owner conceded that the claims “could be broader than that.” Tr. 44:24–46:16. We find availing Petitioner’s argument that the “claim language” does not “relate to any synchronized, low-latency, scalable, flexible, or new and improved video streaming technique.” Pet. Reply 22. Petitioner argues that we should give “no weight” to Patent Owner’s alleged “evidence” of any long-felt but unresolved needs. Pet. Reply 22. In particular, Patent Owner merely provides conclusory statements that, prior to the claimed invention, “conventional video streaming systems” included “hard-embedded event information,” and that “[t]he claimed invention satisfied the long-felt need for an innovative system.” PO Resp. 64–65. Thus, considering the totality of the evidence, we agree with Petitioner that Patent Owner has failed to establish that there was a long-felt but unresolved need for the claimed invention.” slip op. at 51

  Patent outcomesUS 11,039,218 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,039,218
• Genius Sports Ltd. v. Sportscastr Inc. D/B/A Panda InteractiveAll claims unpatentable
  PTAB · Mar 13, 2026 · IPR2024-01310 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 1–15 are unpatentable: claims 12–15 over Ellis and Spivey, and claims 1–11 over Ellis, Spivey, and Herzog; the other grounds were not proven.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Relying on Dr. Wicker’s testimony, Petitioner contends that the relevant artisan would have had “at least a bachelor’s degree, or equivalent, in electrical engineering, computer engineering, computer science, or a related field or an equivalent number of years of working experience, and one to two years of experience in networking environments, including at least some experience with live-streaming network architecture.” Pet. 14 (citing Ex. 1001 ¶¶ 72–76). Petitioner also states that “[a]dditional education or experience in related fields could compensate for deficits in the above qualifications.” Pet. 18. Patent Owner contends that the relevant artisan would have had “a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent degree and, in addition, approximately two years of work experience with Internet video streaming, Internet communication, and related protocols.” PO Resp. 12 (citing Ex. 2001 ¶ 96). Neither party argues that the outcome of this case would differ based on our adoption of any particular definition of the level of ordinary skill in the art. We apply Patent Owner’s definition of the relevant artisan because, based on the record, this proposal is most consistent with the ’218 patent and the asserted prior art, and is supported by the testimony of both Dr. Wicker and Dr. Rubin (see Ex. 1001 ¶¶ 72–76; Ex. 2001 ¶¶ 96–98). We note that we would reach the same determination under Petitioner’s formulation of the level of ordinary skill.” slip op. at 12

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

    “Accordingly, Petitioner’s proposed plain meanings of “socket” and “event socket” (Pet. 26) are not disputed by Patent Owner. PO Resp. 2, 12. In fact, by arguing that Spivey’s topic queues are neither “uniquely addressable” nor “communication endpoints,” Patent Owner appears to adopt Petitioner’s proposed plain meaning of “socket” as a “uniquely addressable communication endpoint.” Id. As Patent Owner acknowledged during Oral Argument, “I don’t think there’s any dispute of what we mean by socket, a uniquely addressable communication endpoint.” Tr. 73:10–12. Thus, we give each of “socket” and “event socket” its plain meaning, where the relevant artisan would have understood “socket” to mean “a uniquely addressable communication endpoint on a server,” and “event socket” to mean “a socket where information about one sporting event is provided to a viewer client device (VCD).” 4 We address such terms below in Section III.D.3. After considering the arguments and information presented during trial, we determine that we do not need to otherwise expressly construe any terms in order to resolve the dispute between the parties. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”)).” slip op. at 15

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “We find Petitioner’s contentions with Dr. Wicker’s supporting testimony persuasive. In particular, we find Petitioner’s reliance on Spivey for disclosing “event socket” is supported by Spivey’s disclosures that a topic queue’s address “may resemble a uniform resource locator (URL)” and that user interface 900 “allow[s] an operator 108 of a client device to view and select . . . topics available from a message queue server.” Ex. 1017 ¶¶ 82, 84, Fig. 9. In Spivey, the message flow begins “when message queue server . . . pushes data payloads to subscribers of the topics in [the] message.” See Ex. 1017 ¶ 134. As Petitioner explains, in Spivey, “the address for connecting a topic queue may resemble a URL, and client devices can select from a list of available topics and subscribe to those queues, after which the MQSD pushes the relevant data payloads to the subscribed devices.” Pet. Reply 8 (citing Ex. 1017 ¶¶ 82–84, 134). As Petitioner explains, and as supported by Dr. Wicker’s testimony, Spivey’s “topic label may be . . . ‘gamecenter.nfl.ravensteelers,’ and client devices use these topic label text strings to connect and subscribe to the MQSD’s topic queues.” Pet. Reply 8 (citing Ex. 1001 ¶¶ 353–354). We find availing that, in Spivey, since the “client devices ‘request a live data connection’ by selecting or entering the address or connection information which ‘may resemble a uniform resource locator (URL),’” Spivey’s topic queues “are not only logically but also actually implemented as uniquely addressable communication endpoints.” Id. at 9 (citing Ex. 1064 ¶¶ 11–14). We find that Dr. Rubin’s testimony that the only potential “communication endpoint” in Spivey that is “uniquely addressable” is the live data access server (Ex. 2001 ¶ 233) merely addresses particular embodiments in Spivey. That is, Dr. Rubin does not address sufficiently Spivey’s teachings as a whole as understood from the perspective of the relevant artisan, which would include other embodiments. See Sundance, Inc. v. DeMonte Fabricating Ltd., 550 F.3d 1356, 1361 n.3 (Fed. Cir. 2008) (“What a prior art reference discloses or teaches is determined from the perspective of one of ordinary skill in the art.”); In re Hedges, 783 F.2d 1038, 1041 (Fed. Cir. 1986) (noting that when evaluating claims for obviousness, “the prior art as a whole must be considered”). Dr. Rubin does not address Spivey’s disclosure that the system “may include” the LDAS (Ex. 1017 ¶ 38), but, as Petitioner points out, merely acknowledges that “there are examples in Spivey using the language [‘may’].” Pet. Reply 4 (citing Ex. 1063, 62:8–13). As Petitioner points out, in his deposition, Dr. Rubin acknowledges” slip op. at 29

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “As Petitioner explained during Oral Argument, Ellis “relates to the ability for the clients and the server to communicate,” which can be any system that can “provide real-time sports,” but “doesn’t discuss whether it’s a push system or a pull system,” whereas Spivey, on the other hand, “expressly indicates that it is a push type of data system which reduces latency over prior art systems that utilize push technologies.” Tr. 15:13–19. We find availing Petitioner’s contention that, “[a]s explained by Dr. Wicker, . . . [the relevant artisan] would have been motivated to implement real-time data delivery using Spivey’s data pushing technique to reduce latency.” Id. at 16:2–8. “[I]f 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 unless its actual application is beyond his or her skill.” KSR, 550 U.S. at 417. We find unavailing Patent Owner’s contention that Petitioner fails to “articulate why [the relevant artisan] would have been motivated to make the necessary modifications and proposed combination.” PO Resp. 40–41. Here, Petitioner points out that its proposed combination would have been made to improve latency issues in Ellis’s system. Pet. 20–22. In particular, Spivey discloses that its techniques “may reduce . . . delay [on the order of seconds (e.g., 30 to 45 seconds) or minutes] to an order of milliseconds (ms) (e.g., 100 ms) or less, providing a significant advantage over the conventional practices.” Ex. 1017 ¶ 28. Spivey also discloses pushing data to the “subscribed connected client devices” substantially simultaneously with the message queue server receiving the topic entry from a live data source, e.g., “with a time delay of 100 milliseconds or less,” which Spivey discloses is “at least two orders of magnitude shorter than conventional time periods of legacy devices.” Id. ¶ 96; see also id. at code (57) (disclosing pushing “the topic entry to a subscribed client device substantially simultaneously with the message queue server receiving the topic entry from a live data source”). We find Patent Owner’s arguments that Petitioner fails to “explain the modifications necessary to combine such teachings” are inconsistent with the evidence of record. PO Resp. 40–47. For example, Patent Owner’s argument that the proposed combination would be inoperable because the combination “does not include the LDAS” (id. at 43–44) is not consistent with the evidence of record that Spivey does not require the LDAS to serve as intermediary between the MQSD and the user equipment. See Ex. 1017 ¶¶ 38, 46. As discussed above, Spivey states that the system “may” include an LDAS (Ex. 1017 ¶ 38), supporting Petitioner’s contention that, in Spivey, the LDAS is “optional” wherein “the MQSD may be ‘accessible to clients over the network directly.’” Pet. Reply 3. As discussed above in Section III.D.3.a, we find persuasive Petitioner’s argument that Spivey’s MQSD may push data from topic queues to the subscribers of the topics corresponding to those topic queues, which indicates that “the MQSD can deliver data directly to clients without the necessity of an LDAS.” Id. (citing Ex. 1017 ¶ 46).” slip op. at 39

  Patent outcomesUS 11,039,218 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,039,218

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.