• 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
• Mediatek Inc. v. Parkervision, Inc.All claims unpatentable
  PTAB · May 22, 2026 · IPR2024-00796 · APJ Iftikhar Ahmed · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious over Nevo and Avitabile, Young and Estabrook, and Young, Estabrook-1988, and Estabrook-1989.

  RulingsFinal written decision

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

    “Network LLC, 929 F.3d 1350, 1357 (Fed. Cir. 2019). On its face, the language “energy transfer signal” does not specify any restrictions on the type of system in which it is utilized, nor its characteristics. In the context of claims 1 and 11, the “energy transfer signal” is the basis on which the “switch” operates, so as to “sub-sample and transfer energy from a first electromagnetic (EM) signal.” Ex. 1001, 50:63–65, 51:56–58. Accordingly, based on the claim language, the term “energy transfer signal” need only be a signal for operating a switch to sub-sample and transfer energy from an electromagnetic signal. That is its plain and ordinary meaning.” slip op. at 15

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

    “’686 patent broadly includes knowledge and experience as to RF circuit design. See supra § III.B. Petitioner contends that “Nevo’s transceivers [102a/102b] are for Bluetooth and IEEE 802.11,” and that a person of ordinary skill in the art would have understood that both protocols “required down-conversion in their receivers to obtain a baseband signal.” Id. at 35 (citing Ex. 1004, 4:45–50; Ex. 1002 ¶ 118). Nevo’s disclosure would have motivated a person of ordinary skill in the art to look to Avitabile, which provides the circuit level detail for down-converters. See Ex. 1006, Abstract. Avitabile specifically provides circuitry for down-conversion in the s-band frequency range, which is in the range of Bluetooth and IEEE 802.11 (2.4 GHz). Id. at Abstract, Figs. 6, 7. Accordingly, we determine a person of ordinary skill in the art would have been motivated to look to down-converters in the range of frequency needed, and would have been motivated to combine Avitabile’s teachings with those of Nevo, with a reasonable expectation of success.” slip op. at 55

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

  Patent outcomesUS 7,483,686 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,483,686
• Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentable
  PTAB · Feb 6, 2026 · IPR2024-01340 · APJ Terrence W Mcmillin · IPR · Final written decision

  Claims 1–12 and 14–18 are unpatentable as obvious over Whitehead, alone or with Marcus ’904; claims 13 and 19–24 were not shown unpatentable.

  RulingsFinal written decision

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

    “establishes that the subject matter of independent claim 19 would have been obvious in view of Whitehead. Claim 19 recites “an aggregator having a memory and a processor, the processor adapted for . . . providing an output signal including data indicative of the selection and of user data.” Ex. 1001, 15:51–16:3. As discussed above (Section II.C.2), we construe claim 19 as requiring a signal including both “data indicative of the selection and of user data.” Accordingly, we consider whether Petitioner has shown that Whitehead teaches or suggests that the “aggregator” “provid[e] an output signal including” both “data indicative of the selection and of user data.”” slip op. at 46

  • Expert testimonyOther

    “Cristofalo’s “user identifiers” represent data about users that Cristofalo’s system uses to “select a specific media object” (advertisements) from received “multi-object programming data.” Cristofalo at ¶ [0048]. For example, a user identifier may indicate that a given user is a Coca-Cola drinker, and when the receiving system receives the multi-object programming data it can select a particular media object out of several possible media objects (e.g., a Pepsi advertisement) to push to the user. Id. This user data exists independently of, and does not relate to, any particular media stream or streams. See Goodrich PO Resp. Decl. at ¶ 135. Petitioner seems to recognize this when tersely referring to “user identifiers” as “data,” not “data relating to a plurality of streams.” Pet. at 71. Accordingly, Cristofalo’s “user identifiers” are not the claimed “data related to the plurality of media streams.” Goodrich PO Resp. Decl. at ¶ 136.” slip op. at 73

  Patent outcomesUS 8,145,704 mixed
  § 103 obviousnesscites Graham
  Patents in suitUS 8,145,704
• Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentable
  PTAB · Jan 23, 2026 · IPR2024-01342 · APJ Terrence W Mcmillin · IPR · Final written decision

  Claims 1–4 and 6–10 are unpatentable as obvious over each asserted ground; claim 5 was not shown unpatentable because the petitions failed to establish its additional feed and time-period limitations.

  RulingsFinal written decision

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

    “1b, 1c, and 1e of claim 1 and in claims 4 and 5 of the ’753 patent. Patent Owner contends that the plain and ordinary meaning of “feed” is “one or more associated media elements.” See, e.g., PO Resp. 4. However, as discussed below, this alleged plain and ordinary meaning of feed is not supported by the claim language, the specification of the ’753 patent, or dictionary definitions of feed as contended by Patent Owner. We reject this contention and the related contentions that the cited art may be distinguished from the claims of the ’753 patent based on the recited term “feed.” Patent Owner relies on the language of claim 1 to support its” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The parties’ definitions are similar, although we observe that Patent Owner proposes that the person of ordinary skill would have a bachelor’s degree or an equivalent or professional experience, whereas Petitioner proposes that such a person would have both a degree and experience. Neither party presents any arguments relating or referring to the level of ordinary skill in the art. Determining the level of ordinary skill in the art involves various factors, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The prior art of record also reflects the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt Petitioner’s assessment of the level of skill in the art. Petitioner’s assessment is supported by the testimony of Dr. Almeroth and is consistent with the ’753 patent and the asserted prior art. However, our obviousness analysis would be the same under either party’s assessment. See Ex. 2014 ¶ 17 (Patent Owner’s declarant, Dr. Goodrich, stating that “I note that my definition of a POSITA is similar to that of Dr. Almeroth” and “My opinions in this declaration would not change were I to adopt the definition of a POSITA offered by Dr. Almeroth.”).” slip op. at 11

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “16 With regard to claim 5, the Petition cites paragraphs 97 and 98 of the Almeroth Declaration (Ex. 1002). See Pet. 28–29. We have considered the cited paragraphs in the Almeroth Declatation and found that they consist of nothing more than the inadequate and conclusory contentions in the Petition preceded by, in paragraph 97, “[i]n my opinion” and “it is my opinion” and, in paragraph 98, “[i]t is also my opinion.” Ex. 1003 ¶¶ 97, 98. As related to claim 5, we accord the Almeroth Declaration little or no weight. See 37 C.F.R. § 42.65 (a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”). that might become out-of-date before a user accesses access [sic] them. Ex. 1003, 11:49–58 (emphasis added). The cited passage in Whitehead mentioning “near real-time” does not support finding that Whitehead teaches or suggests the elements recited in claim 5.” slip op. at 39

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

    “Petitioner contends, “[a] POSITA would have modified Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm (running on Marcus ’904’s receiver) for receiving, selecting, ordering, and assembling different media streams (both for content and advertising).” Pet. 33. Petitioner supports this contention by articulating the following reasons for the asserted modification of Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm: “makes it more likely the system will identify content best suited for a particular user,” “allows for more targeted advertising and/or an opportunity to maximize revenue,” “improves Whitehead’s ability to target content and advertising to a particular user,” “would unlock new revenue sources for Whitehead,” “Marcus ’904’s content selection and concatenation algorithm improves Whitehead’s efficiency,” “[b]oth Whitehead and Marcus ’904 generate custom media programming based on a user profile,” “incorporating Marcus ’904’s teachings would not require redesigning Whitehead’s architecture and instead merely supplements Whitehead’s disclosure,” and “Petitioner’s proposed modification can be implemented entirely in software and does not require any hardware modifications. Indeed, Whitehead acknowledges that such modifications are possible. EX1003 at 19:64-20:6, 22:26-40.” Id. at 33–35 (citing Ex. 1002 (Almeroth Decl.) ¶¶ 110–115) (emphasis omitted). Based on this undisputed showing, we find that one of ordinary skill would have had a motivation to combine the teachings of Whitehead and Marcus ’904 as asserted in the Petition with a reasonable expectation of success.” slip op. at 48

  Patent outcomesUS 8,886,753 mixed
  Claim construction§ 103 obviousnesscites Graham
  Patents in suitUS 8,886,753
• Reed Semiconductor Corp. v. Monolithic Power Systems, Inc.All claims unpatentable
  PTAB · Jan 22, 2026 · IPR2024-01158 · APJ Ken B Barrett · IPR · Final written decision

  Claims 1–5, 7–15, 17, and 18 are unpatentable: claims 1–4, 9–14, 17, and 18 as anticipated by Tateishi, and claims 5, 7, 8, and 15 as obvious over Tateishi.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We discern no material difference between the parties’ definitions. Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art. We note, however, that were we to adopt Patent Owner’s assessment, the outcome of this Decision would be the same.” slip op. at 13

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

    “After considering the parties’ arguments and evidence, we determine that Patent Owner has not offered persuasive evidence that a person of ordinary skill in the art reading the claims in light of the Specification would understand the plain and ordinary meaning of “control signal” to be as narrow as Patent Owner proposes. We do not construe the claims such that the “control signal” must be the exclusively controlling factor of a component, as Patent Owner urges. Petitioner’s position, on the other hand, is consistent with the evidence of record. We construe “control signal” as having its plain and ordinary meaning, namely a signal configured to control a circuit component. D. The Asserted Anticipation of Claims 1–4, 9–14, 17, and 18 by Tateishi” slip op. at 24

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “We determine that Petitioner has demonstrated by a preponderance of the evidence that Tateishi discloses the “control signal” recited in limitations 1B2 and 1D of independent claim 1.” slip op. at 37

  • BurdenNot shown unpatentable

    “based on the Tateishi application publication (Ex. 1007), that the Tateishi Patent (Ex. 1005) also anticipates claims 1–4, 9–14, 17, and 18. See Pet. 23–24 (“The Tateishi Patent is also prior art under (pre-AIA) §102(e)”; identifying Ground 1 as anticipation “under §102 by Tateishi and/or the Tateishi Patent”). However, we are unable to locate in the Petition or Petitioner’s Reply a discussion of or citation to the Tateishi Patent other than under the Petitioner’s heading “Identification of Challenge and Relief Requested” on pages 23 and 24 of the Petition. Cf. id. at i–x (Table of Contents identifying a section of the Petition discussing the Tateishi (Application) anticipation ground but not a section discussing a Tateishi Patent anticipation ground). Although the issued patent may be substantively identical to the published application, Petitioner does not assert that, and we decline to compare the documents to determine whether that is the case. In light of Petitioner’s silence on the alternative ground, Petitioner has not demonstrated by a preponderance of the evidence that the Tateishi Patent anticipates 1–4, 9–14, 17, and 18.” slip op. at 47

  Patent outcomesUS 9,041,377 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,041,377
• Shenzhen Ronglida Technology Co. Ltd. v. Pathway IP LLCInstituted
  PTAB · Jan 15, 2026 · IPR2025-01231 · APJ Mary C Hoffman · IPR · Institution

  The Board instituted IPR on claims 1–13 on all asserted grounds, finding a reasonable likelihood that at least one challenged claim is unpatentable.

  RulingsInstitution decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “petition identifies all real parties in interest. 35 U.S.C. § 312(a)(2). Whether an unnamed party is a real party in interest “is a highly fact-dependent question.” See Applications in Internet Time, LLC v. RPX Corp., 897 F.3d 1336, 1351, 1360 (Fed. Cir. 2018) (“AIT”); Ventex Co., Ltd. v. Columbia Sportswear N. Am., Inc., IPR2017-00651, Paper 152 at 4–5 (PTAB Jan. 24, 2019) (precedential) (citing Worlds Inc. v. Bungie, Inc., 903 F.3d 1237, 1242 (Fed. Cir. 2018)); Consolidated Trial Practice Guide, 13 (2019), https://www.uspto.gov/sites/default/files/documents/tpgnov.pdf (CTPG). “A common consideration is whether the non-party exercised or could have exercised control over a party’s participation in a proceeding.” CTPG at 16. Other considerations include whether the non-party is funding or directing the proceeding; the non-party’s relationship with the petitioner; the non-party’s relationship to the petition itself, including the nature and/or degree of involvement in the filing; and the nature of the entity filing the petition. Id. at 17–18.” slip op. at 8

  • Skill levelSkill level board ownOther

    “person of ordinary skill in the art (“POSITA”) “would have at least a bachelor’s degree in electrical engineering or a related field and at least two years of experience with lighting technology.” Pet. 2 (citing Ex. 1017 ¶ 35). Petitioner makes additional contentions about what a POSITA would have understood. Id. (“A POSITA would understand that all types of cameras (e.g., analog and digital, photo and video) generally involve the same lighting considerations . . . . [and] that it is important to provide light that evenly illuminates the target subject or object to minimize reflected glare and shadows.”). Patent Owner contends that a POSITA would have at least: (a) a bachelor’s degree in electrical engineering, optical engineering, or a related field; (b) two years of practical experience in designing and developing lighting systems, particularly those integrated with electronic devices such as webcams or computer monitors; and (c) knowledge of user-interface considerations for consumer electronics . . . . Additional experience can substitute for education and vice versa. Prelim. Resp. 12 (citing Ex. 2036 ¶ 48). Patent Owner disputes Petitioner’s contentions regarding what a POSITA would have understood. Prelim. Resp. 12–13 (“[O]ne of ordinary skill in the art would have understood that analog and digital cameras have different operating principles and lighting requirements [and] Petitioner’s lack of appreciation for the suitability and unsuitability of different lights for different applications infects and dooms its invalidity analysis.” (citing Ex. 2036 ¶¶ 36–47)). and years of experience required for a POSITA. Pet. 2; Prelim. Resp. 12. For purposes of this Decision, we consider a person of ordinary skill in the art to have a bachelor’s degree in electrical engineering or related field and two years of practical experience in lighting technology, and that additional experience may substitute for education and vice versa, which is consistent with the level of skill reflected in the ’729 patent and prior art of record. See Exs. 1001, 1005–1010, 1012–1015; see also 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 need for testimony is not shown” (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985))).” slip op. at 12

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

    “Patent Owner agrees that the Board need not formally construe any claim terms in order to adjudicate the merits of the Petition and argues Petitioner fails to show unpatentability of any claim under any reasonable construction of the claims. Prelim. Resp. 13 (citing Ex. 2036 ¶ 51). We determine that no express claim construction is necessary to determine whether institution is warranted in this proceeding. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (holding that only terms in controversy must be construed “and only to the extent necessary to resolve the controversy”) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 14

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “claimed subject matter and the prior art are “such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). When a ground in a petition is based on a combination of references, we consider “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” Id. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We base our obviousness inquiry on factual considerations including (1) the scope and content of the prior art, (2) any differences between the claimed subject matter and the prior art, (3) the level of skill in the art, and (4) any objective indicia of obviousness or non-obviousness that may be in evidence.14 See Graham, 383 U.S. at 17–18.” slip op. at 24

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,841,729
• Meta Platforms, Inc. v. Mullen Industries LLCAdverse judgment
  PTAB · Dec 19, 2025 · IPR2025-00740 · APJ Ken B Barrett · IPR · Adverse judgment

  The Board denied Patent Owner’s motions to dismiss and entered adverse judgment after Patent Owner disclaimed all challenged claims in the captioned trials.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “provide that “[a] party may request judgment against itself at any time during a proceeding,” and “[a]ctions construed to be a request for adverse judgment include . . . [c]ancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). “The application of the [adverse judgment] rule on its face does not turn on the patentee’s characterization of its own request.” Arthrex, Inc. v. Smith & Nephew, Inc., 880 F.3d 1345, 1349 (Fed. Cir. 2018).” slip op. at 6

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Denied

    “Constitution that there exist a case or controversy to be adjudicated by a district court. See Sanofi-Aventis, 933 F.3d at 1372–73. The Board is not a district court or any other Article III court, and Patent Owner has not shown persuasively that Sanofi-Aventis supports its argument that dismissal, as opposed to adverse judgement, is appropriate.” slip op. at 3

  None
  Patents in suitUS 10,828,559
• Meta Platforms, Inc. v. Mullen Industries LLCAdverse judgment
  PTAB · Dec 19, 2025 · IPR2025-00703 · APJ Ken B Barrett · IPR · Adverse judgment

  The Board denied Patent Owner’s motions to dismiss and entered adverse judgment against it on claims 1, 2, 11, and 13 of the challenged patent after their disclaimer.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “provide that “[a] party may request judgment against itself at any time during a proceeding,” and “[a]ctions construed to be a request for adverse judgment include . . . [c]ancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). “The application of the [adverse judgment] rule on its face does not turn on the patentee’s characterization of its own request.” Arthrex, Inc. v. Smith & Nephew, Inc., 880 F.3d 1345, 1349 (Fed. Cir. 2018). In this case, Patent Owner, after the institution decisions, disclaimed the challenged claims such that there are no remaining claims in the trials. Patent Owner presents no persuasive reasons why we should not apply Rule 42.73 or why termination or dismissal is more appropriate. Under the IPR2025-00745 (Patent 9,662,582 B2) IPR2025-00746 (Patent 10,974,151 B2) circumstances of these cases, we construe the filing of disclaimers as requests for adverse judgment.” slip op. at 6

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Denied

    “In the Motions, Patent Owner, relying on Sanofi-Aventis U.S., LLC v. Dr. Reddy’s Lab’ys, Inc., argues that, “[b]ecause all claims at issue have been disclaimed, any case or controversy over the claims is moot,” and, “[a]ccordingly, the IPR[s] should be dismissed.” Mot. 2 (citing Sanofi- Aventis U.S., LLC v. Dr. Reddy’s Lab’ys, Inc., 933 F.3d 1367, 1373 (Fed. Cir. 2019)). Sonofi-Aventis pertains to the requirement under Article III of the Constitution that there exist a case or controversy to be adjudicated by a district court. See Sanofi-Aventis, 933 F.3d at 1372–73. The Board is not a district court or any other Article III court, and Patent Owner has not shown persuasively that Sanofi-Aventis supports its argument that dismissal, as opposed to adverse judgement, is appropriate.” slip op. at 3

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “above-captioned cases requesting inter partes review of certain claims (“the challenged claims”) of the subject U.S. Patents. See, e.g., IPR2025-00702, Paper 1. Mullen Industries LLC (“Patent Owner”) filed Preliminary Responses to the Petitions. See, e.g., IPR2025-00702, Paper 10. Because we determined that Petitioner had demonstrated a reasonable likelihood that it would prevail with respect to at least one challenged claim in each case, we instituted inter partes review of all challenged claims on all asserted grounds in all of the cases. See, e.g., IPR2025-00702, Paper 11.” slip op. at 2

  None
  Patents in suitUS 11,033,821
• Meta Platforms, Inc. v. Mullen Industries LLCAdverse judgment
  PTAB · Dec 19, 2025 · IPR2025-00702 · APJ Ken B Barrett · IPR · Adverse judgment

  The Board denied Mullen’s motions to dismiss and entered adverse judgment after Mullen disclaimed all challenged claims in the instituted trials.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “provide that “[a] party may request judgment against itself at any time during a proceeding,” and “[a]ctions construed to be a request for adverse judgment include . . . [c]ancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). “The application of the [adverse judgment] rule on its face does not turn on the patentee’s characterization of its own request.” Arthrex, Inc. v. Smith & Nephew, Inc., 880 F.3d 1345, 1349 (Fed. Cir. 2018).” slip op. at 6

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Motion to exclude, deniedDenied

    “Constitution that there exist a case or controversy to be adjudicated by a district court. See Sanofi-Aventis, 933 F.3d at 1372–73. The Board is not a district court or any other Article III court, and Patent Owner has not shown persuasively that Sanofi-Aventis supports its argument that dismissal, as opposed to adverse judgement, is appropriate.” slip op. at 3

  None
  Patents in suitUS 10,967,270

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.