• 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
• 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
• Aptiv Services US, LLC v. Microchip Technology, Inc.All claims unpatentable
  PTAB · Mar 20, 2026 · IPR2024-00646 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–18 are unpatentable under § 103 over Al-Shyoukh, Ivanov, and Stanescu; the Board did not reach the alternative ground.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner’s proposal is most like Petitioner’s alternative proposal which would include a bachelor’s degree and two years of experience. However, Patent Owner does not provide a specific number of years of industry experience and Patent Owner would include mixed-signal IC design as an alternative to analog circuit design. We consider analog circuit design to be most pertinent to the problems and solution discussed in the ’074 patent. See Ex. 1001, 1:15–2:44. In addition, we find credible Petitioner’s argument that an ordinarily skilled artisan with a bachelor’s degree would have had two years of experience, whereas Patent Owner’s proposal does not provide a specific number of years. Thus, we determine that a person of ordinary skill in the art would have had a bachelor’s degree and two years of experience in analog circuit design. Nevertheless, the outcome of our decision would be the same under either of the party’s proposals.” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for petitioner

    “Because neither party has argued that the district-court constructions should be modified or elaborated for this proceeding, and the constructions appear reasonable, we adopt these constructions for this decision. We also take judicial notice of the district court’s Memorandum supporting the claim construction order. Ex. 3001.9” slip op. at 10

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

    “We agree with Petitioner that “gm boosting” is the only gm enhancement referred to in the ’074 patent, that the ’074 patent uses the terms “gm enhanced” and “gm-boost” synonymously, and that Patent Owner has failed to point to any credible intrinsic evidence of this alleged distinction. Although, “[i]n the absence of any evidence to the contrary, we must presume that the use of . . . different terms in the claims connotes different meanings, CAE Screenplates Inc. v. Heinrich Fiedler GmbH, 224 F.3d 1308, 1317 (Fed. Cir. 2000), in this case there is evidence to the contrary. In particular, the ’074 patent never refers to “gm enhancement” as a function separate from “gm boosting.” Indeed, the transistors (368, 370, and 382) that Patent Owner identifies as performing the function of “gm enhancement” are disclosed as part of a “gm-boost stage.” Ex. 1001, 5:8–24. Patent Owner’s alleged separation of Figure 3B into distinct “gm boosting” and “gm enhancement” is not consistent with the intrinsic evidence and is based on the conclusory testimony of Dr. Taylor. Thus, based on the evidence of record, we disagree with Patent Owner’s proposed construction distinguishing the terms “gm enhanced” and “gm-boost” in claim 1. Rather, we find persuasive Petitioner’s argument that a person of ordinary skill in the art would have regarded these terms to be synonymous. We need not otherwise construe these two terms to resolve the contested issues in this proceeding. 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 12

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

    “We find Petitioner’s argument persuasive that a person of ordinary skill in the art would have had reason to follow Ivanov’s teachings to include an enable/disable function in Al-Shyoukh’s biasing circuit to limit that circuit’s standby current for reasons of power-efficiency. Pet. 25–26; Ex. 1002 ¶¶ 67–68. The evidence of record also suggests that an enable/disable function was well known in the art and that it would have been within the level of ordinary skill in the art to add such a function to a biasing circuit, taking into consideration any known tradeoffs. Pet. Reply 17–18; Ex. 1002 ¶¶ 60, 67–68; PO Resp. 13–14 (acknowledging that “any [person of ordinary skill in the art” would attest[ that] engineering is full of tradeoffs” and listing some of the known tradeoffs that “a [person of ordinary skill in the art] would need to consider”). We also disagree with Patent Owner’s argument that Al-Shyoukh, Rincon-Mora, or other references teach away from adding an enable/disable function to Al-Shyoukh. Patent Owner has not pointed to anything in the prior art that criticizes, discredits, or otherwise discourages investigation into the claimed invention. Meiresonne v. Google, Inc., 849 F.3d at 1382.” slip op. at 34

  Patent outcomesUS 9,471,074 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,471,074
• 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
• Genius Sports Ltd. v. Sportscastr Inc. D/B/A Panda InteractiveAll claims unpatentable
  PTAB · Mar 11, 2026 · IPR2024-01305 · APJ Jon M Jurgovan · IPR · Final written decision

  Claims 1–9 are unpatentable: claims 1, 8, and 9 as obvious over Ellis and Spivey, and claims 2–7 as obvious over Ellis, Spivey, and Herzog.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Relying on the declaration of Dr. Wicker, Petitioner contends that a person of ordinary skill in the art (POSA) at the time of the invention of the ’687 patent 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. 13 (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.” Id. Patent Owner contends that a POSA at the time of the invention of the ’687 patent 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. 13 (citing Ex. 2001 ¶ 99). The parties have not addressed whether the differences in these definitions impact the unpatentability analysis before us. We apply Patent Owner’s definition of a POSA at the time of the claimed invention because, based on the record, this proposal is consistent with the ’687 patent, the asserted prior art, and is supported by the testimony of Dr. Wicker. 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 › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “Patent Owner contends that the plain and ordinary meaning should apply to all terms of the challenged claims except for “event socket.” PO Resp. 12. Petitioner argues that an “event socket” should be construed as “uniquely addressable communication endpoints that transmit event information.” Pet. Reply 8–10. Patent Owner does not disagree with Petitioner’s proposal. See generally PO Sur-Reply. As the parties do not dispute the meaning of “event socket,” we need not, and do not, expressly construe the term beyond the parties agreed meaning. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only claim terms in controversy need to be construed, and only to the extent necessary to resolve the controversy).” slip op. at 10

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

    “We agree with Petitioner’s contention that Ellis and Spivey differ in that Ellis uses HTTP request-response messages whereas Spivey uses websocket connections between the content delivery system’s server and user equipment. Pet. 18 (citing Ex. 1001 ¶¶ 106–115). As Petitioner points out, in Ellis’s HTTPS connections, a user equipment requests the server to respond with any new messages. Id. at 8 (citing Ex. 1001 ¶¶ 50, 51); Ex. 1016 ¶¶ 37, 40. We agree with Petitioner that Spivey’s websocket connections were a known alternative to HTTP requests. Id. (citing Ex. 1001 ¶¶ 52, 53, 58, 59). We further agree that such websockets constitute bidirectional, full-duplex, stateful, and persistent connections that provide instant updates from the server to the user equipment without the need for the user equipment to request them from the server (referred to as “push” technology). Id. Accordingly, we agree with Petitioner that, under some scenarios, a POSA would have viewed Spivey’s websocket connections as more advantageous for providing video content and event data to end-users than Ellis’s HTTP request-response protocol, thus motivating simple substitution of Spivey’s LDSD and MQSD for Ellis’s SCS. Pet. 21–22 (citing Ex. 1016 ¶¶ 34, 47; Ex. 1017 ¶ 34; Ex. 1001 ¶¶ 114, 115). See KSR, 550 U.S. at 417 (simple substitution of one known element for another is a recognized rationale supporting a motivation to combine). For example, if server requests are frequent, a POSA would have recognized that the processing overhead of setting up and tearing down HTTP connections would exceed any latency disadvantages of Spivey’s persistent websocket connections. Ex. 1064 ¶ 35. Thus, under some circumstances, a POSA would have been motivated to make the Ellis-Spivey combination, and we do not agree with Patent Owner’s arguments to the contrary.” slip op. at 19

  • Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersObjective indicia no nexusDecided 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, 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 digital content, such as a video content, and audio content . . . ” (PO Resp. 64), 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 23. Further, as Petitioner also points out, “claim 1 simply requires a media source to receive the video stream and distribute the video stream.” Pet. Reply 23. 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 agree with 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 23. Furthermore, as Petitioner points out, Patent Owner does not cite to any evidence of long-felt but unresolved needs. Pet. Reply 23 (citing PO Resp. 66). In particular, Patent Owner merely provides conclusory statements that, prior to the claimed invention, “conventional video streaming systems” include “hard-embedded event information,” and that “[t]he claimed invention satisfied the long-felt need for an innovative system.” PO Resp. 64–66. Thus, considering the totality of the evidence, we agree with” slip op. at 45

  Patent outcomesUS 10,805,687 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,805,687
• Digital Global Systems, Inc. v. Deepsig, Inc.Some claims unpatentable
  PTAB · Mar 6, 2026 · IPR2024-01358 · APJ William V Saindon · IPR · Final written decision

  Claims 1–3, 7–11, 15–19, 23, and 24 are unpatentable as obvious; claims 4–6, 12–14, and 20–22 were not shown unpatentable because the prior art did not teach the claimed received-signal feedback and transmitter-model update.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that: Persons of ordinary skill in the art (“POSITA”) would have a bachelor’s degree in electrical engineering, computer engineering, or an equivalent degree and at least two years of experience working with of radio communication systems and machine learning. Additional work or research experience can substitute for less or different education, and vice-versa. Pet. 3–4 (citing Ex. 1003 ¶¶ 33–34). Patent Owner does not appear to challenge this level of skill. We use Petitioner’s definition for purposes of this Decision because it appears consistent with the level of skill reflected in the prior art and ’704 patent.” slip op. at 7

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

    “parameters “associated with the base station.” PO Resp. 31–32. In particular, Patent Owner argues that a transmitter “implemented in a base station” is not “associated with the base station.” Id. at 31. Petitioner argues that Patent Owner offers no reason to believe that a transmitter “implemented in a base station” is not “associated with the base station.” Pet. Reply 4–5; see also id. at 3–6 (entire argument). A plain reading of a “model associated with a base station” would encompass a model that operates in a base station. We do not see anything in the ’704 specification that would indicate “associated with” has any special meaning, or has a meaning contrary to our understanding of the plain meaning. We do not see the word “associated” outside the claims, whereas we see the word “implement” throughout the specification, generally in reference to an actual use of a model (consistent with our plain reading). See, e.g., Ex. 1001, 5:35–39, 6:3–17, 10:55–11:3 (discussing “implementations” where the model or some other feature of the system is used in a particular way). Accordingly, we construe a model “implemented in a base station” to be “associated with the base station.”” slip op. at 12

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

    “scenarios” (see PO Resp. 16–21), Patent Owner argues that “Jüschke does not disclose any association of the weight or bias parameters, . . . to any deployment scenario, and . . . base station” (id. at 19). For the reasons explained in our claim construction section above, we construe “deployment scenarios” to include “inline mode” models located within a base station, according to the list of deployment scenarios set out in the ’704 patent. See Ex. 1001, 2:38–65. The in-line deployment scenario depicted in Figure 6A of the ’704 patent bears a striking resemblance to the arrangement depicted in Figure 1 of Jüschke. In both figures, the analog radio signal is fed directly into the model and then the model directly outputs the signal to the amplifier. Compare Ex. 1001, Fig. 6A, with Ex. 1005, Fig. 1. As construed, the “deployment scenarios” represent the physical configurations of the device in which the model is found, such as “in-line.” Petitioner shows by a preponderance of the evidence that Jüschke’s similar in-line configuration is a “deployment scenario” as claimed because it teaches an inline model for a cellular system transmitter (i.e., base station). Pet. 26–29 (citing, e.g., Ex. 1005, Fig. 1, ¶¶ 6, 59; Ex. 1003 ¶¶ 146–147); see also Ex. 1001, 2:37–41 (stating that “[t]he particular deployment scenario[] may be . . . sending a radio transmission from a cellular base station that includes the . . . model . . . in an inline mode”).” slip op. at 26

  • BurdenNot shown unpatentable

    “Based on our claim construction analysis of claim 4, above, we agree with Patent Owner that claim 4 requires an actually transmitted signal and an update of the transmitter’s model. This claim construction eliminates Petitioner’s position regarding Holt teaching a modeled signal. See, e.g., Pet. Reply 17–23. We then turn to Petitioner’s argument that Holt teaches updating a model using an actually transmitted signal. See Pet. 59–60. There, Petitioner relies on a disclosure in Holt of an “actual communication channel 302 used to train the channel model 208.” Ex. 1006, 18:1–2. This is depicted in Figure 6 of Holt, in connection with a “fourth loss function” which is used to “train the decoder model.” Id. at 18:42–48; see generally id. at 17:58–18:51 (describing Figure 6). Whether training the channel model or the decoder model, Holt here does not disclose using the actual communication channel to train the encoder, i.e., transmitter. In sum, we find that Petitioner has not shown by a preponderance of the evidence that the prior art describes the claimed step of “obtaining a received radio signal,” and even if it did, Petitioner has not shown by a preponderance of the evidence that the prior art describes the claimed step of “updating the value of the model parameters” in the manner required by claim 4. Claims 12 and 20 are nearly identical to claim 4, and Petitioner’s ground fails for similar reasons. See Pet. 76. Claims 5, 6, 13, 14, 21 and 22 depend from claims 4, 12, and 20, and Petitioner’s ground fails for similar reasons as those claims. See id. at 77–80.” slip op. at 31

  Patent outcomesUS 11,018,704 mixed
  Claim construction§ 103 obviousness
  Patents in suitUS 11,018,704
• Genius Sports Ltd. v. Sportscastr Inc. D/B/A Panda InteractiveAll claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01309 · APJ Thu A Dang · IPR · Final written decision

  Claims 19–25 and 27–30 are unpatentable as obvious over Ellis and Spivey; the Board did not find the alternative Herzog, Spivey, and Ellis ground established.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The parties have not addressed whether the differences in these definitions impact the unpatentability analysis before us. We apply Patent Owner’s definition of a POSITA at the time of the claimed invention because, based on the record, this proposal is consistent with the ’697 patent, the asserted prior art, and is supported by the testimony of Dr. Wicker. We note that we would reach the same determination under Petitioner’s formulation of the level of ordinary skill.” slip op. at 10

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

    “And Patent Owner states that it “agree[s] with Petitioner’s construction” with respect to the MPF terms. PO Resp. 13. Although Patent Owner also contends that a “POSITA would understand the ‘means for transmitting’ to be a socket server transmitting through an event socket that implements the algorithms described in Figures 2, 3, 21A–21E and accompanying disclosures” (id.), Patent Owner’s proposed further construction is not disputed by Petitioner. See generally Pet. Reply. Furthermore, Petitioner’s proposed constructions of “socket” and “event socket” (Pet. 39) are not disputed by Patent Owner. PO Resp. 2, 13–14. In fact, by arguing that Spivey’s topic queues are neither “uniquely addressable” nor “communication endpoint[s],” Patent Owner appears to adopt Petitioner’s proposed construction of “socket” as a “uniquely addressable communication endpoint.” Id. at 2. 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:11–13.6 Thus, on this record, because there is no dispute between the parties regarding the terms “means for transmitting,” “event socket,” or “socket,” construction is not needed. Accordingly, we decline to provide further analysis or an express construction for these terms.” slip op. at 14

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

    “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,” wherein 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, . . . a POS[IT]A would have been motivated to implement real-time data delivery using Spivey’s data pushing technique to reduce latency.” Id. at 16:2–4. “[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 a POSITA would have been motivated to make the necessary modification and proposed combination.” PO Resp. 44. Here, Petitioner points out that its proposed combination would have been made to improve latency issues in Ellis’s system. Pet. 19–24. In particular, Spivey’s 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 51

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

    “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. 66), 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 22–23. Further, as Petitioner also points out, “claim 19 simply requires a media source to receive the live stream of digital content and distribute it.” Pet. Reply 23. 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 23. Nevertheless, as Petitioner points out, Patent Owner does not cite to any evidence as to any long-felt but unresolved needs. Pet. Reply 23 (citing PO Resp. 67–68). In particular, Patent Owner merely provides conclusory statements that, prior to the claimed invention, “conventional video streaming systems” include “hard-embedded event information,” and that “[t]he claimed invention satisfied the long-felt need for an innovative system.” PO Resp. 66–68. 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 59

  Patent outcomesUS 10,425,697 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,425,697

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.