• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Sep 3, 2026 · IPR2025-00673 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–7 are unpatentable as obvious over the combined teachings of the asserted references, including Shin and Aoyama and Shimomura and Iwase.

  RulingsFinal written decision

  • PTAB / AIA Trials › Motions to amend / substitute claimsOther

    “1 SoundClear also filed a Contingent Motion to Amend that proposed to replace originally challenged claim 5 of the ’675 patent with proposed substitute claim 8. Paper 21. We, however, granted SoundClear’s request to withdraw its Contingent Motion to Amend and, as a result, the Contingent Motion to Amend will no longer be considered in this proceeding. Paper 30.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 21

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

    “combination because (1) configuring Shin’s processor 120 accordingly “would have been trivial, involving straightforward changes to enhance the processor’s approach to simplifying and abbreviating its output”; and (2) this approach was well-known as evidenced by Ha’s disclosure of replacing “team meeting” and “date” with “schedules” based on the user’s environment.6 Id. at 27–28 (first quoting Ex. 1011 ¶ 97, then quoting Ex. 1011 ¶ 98) (citing Ex. 1002 ¶ 102; Ex. 1011, Fig. 7).” slip op. at 33

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “4. Dr. Stern’s Testimony is Reliable In its Patent Owner Response, SoundClear contends that “Dr. Stern’s” slip op. at 125

  Patent outcomesUS 11,244,675 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,244,675
• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.

  RulingsFinal written decision

  • BurdenOther

    “Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18

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

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  Patent outcomesUS 11,069,337 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,069,337
• 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
• 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
• Mediatek Inc. v. Parkervision, Inc.All claims unpatentable
  PTAB · Mar 31, 2026 · IPR2025-00030 · APJ Barry L Grossman · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious over the combinations in Grounds 1A–1C and 2A–2C.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “stated by Patent Owner. Ex. 2001 ¶ 25. This proposed level of skill is nearly identical to that proposed by Petitioner. Unlike Dr. Larson, however, Dr. Ricketts states his “opinion,” without stating the facts, data, or factors that he considered in reaching his opinion. Accordingly, we give his testimony little probative weight. 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.”). For purposes of this Decision, based on the prior art, the sophistication of the disclosed technology in the ’593 patent, and Dr. Larson’s testimony, we adopt Petitioner’s definition of the level of ordinary skill, which is that a person of ordinary skill in the art would have had: at least a bachelor’s degree in electrical engineering or a related subject and two or more years of experience in the field of RF circuit design and/or power supplies for RF circuits, or at least five years of work experience and training in the design and development of RF circuits and/or power supplies for RF circuits. Less work experience may be compensated by a higher level of education, such as a master’s degree.” slip op. at 15

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner

    “on the construction of the claim term “power efficiency,” we agree with Petitioner and its declarant, Dr. Larson, that a person of ordinary skill (i.e., a degreed engineer with two or more years of experience in the field of RF circuit design and/or power supplies for RF circuits) would have understood that to determine the power efficiency of a circuit, one would measure the components or characteristics of power, such as voltage and current, to determine the output power of the power supply compared to its input power. Based on our construction of the claim term “power efficiency,” we also note that the claims only require performing a bypass function when the efficiency threshold is exceeded. The claims do not require a power efficiency ratio to be measured or calculated. Thus, we decline Patent Owner’s attempt to limit the claim term “power efficiency” to a ratio.” slip op. at 30

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

    “Section II.D.2 of this decision), Hau teaches a bypass controller 74 (purple) which receives a signal Pdet from a power detector (pink) and activates a bypass switch 72 (purple) when the signal Pdet exceeds a predetermined threshold (in response to a power efficiency of the power supply exceeding a predetermined threshold). Id. at 28 (citing Ex. 1007, 5:43–51, 6:57–7:20). According to Petitioner Hau discloses that the strength of the signal Pdet, the power output of the amplifier PA1, and the supply voltage Vcc2 are all proportional. Id. at 29 (citing Ex. 1007, 6:22–44; Ex. 1003 ¶¶ 122–123. Petitioner concludes, therefore, that Pdet is an indicator of the power output by the DC-DC buck regulator at Vcc2. Id. Petitioner also concludes that because input power is supplied to the DC-DC buck regulator from a fixed voltage, Pdet is also an indicator of the power efficiency of the DC-DC buck regulator because higher power indicated at Pdet indicates greater efficiency relative to the fixed input power. Pet.29 (citing Ex. 1003 ¶ 123). Dr. Larson’s testimony supports Petitioner’s conclusions. Petitioner also asserts: when Pdet exceeds the predetermined threshold, Hau’s bypass controller 74 activates bypass switch 72 and deactivates the DC- DC converter (which is a PWM switching device in the combination of Hau and Yoshida) (deactivates the switching device) to pass the input voltage directly to the output voltage Vcc2 (passes the input voltage to the output voltage node). Pet. 30 (citing Ex. 1007, 5:44-51, 6:61, 66; Ex. 1003 ¶¶ 125-126).” slip op. at 39

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightUnpatentableMotivation foundUnpatentable

    “According to Petitioner, it would have been obvious to a person of ordinary skill “to set Hau’s predetermined threshold to correspond to the point at which a fixed power supply (e.g., the bypass pathway of Hau) becomes more efficient than the down-converted power supply, as taught by Sahu.” Pet. 50–51 (citing Ex. 1007, 6:63–66; Ex. 1003 ¶¶ 166–167). Petitioner also asserts a person of ordinary skill “would have recognized that Sahu’s efficiency graph shows performance for a particular modulation scheme”, and that the resulting efficiency of the system using that modulation scheme “correlates with the efficiency of the communication waveform in that scheme (based on a communication waveform efficiency).” Id. at 51 (citing Ex. 1003 ¶ 168). Petitioner concludes that a person of ordinary skill “would have understood and found it obvious that basing the predetermined threshold of Hau on the point where a fixed power supply becomes more efficient as taught by Sahu is programming the threshold voltage based on a communication waveform efficiency.” Id. at 51 (citing Ex. 1003 ¶ 168). We find Petitioner’s contentions persuasive. Patent Owner asserts it is “hindsight” to rely on Sahu. PO Resp. 51 (a person of ordinary skill “would not have equated Sahu’s fixed-supply system with Hau’s bypass pathway without the benefit of hindsight”). According to Patent Owner, “Petitioner used the disclosures in the ’593 patent as a road map for reasons to combine Sahu and Hau/Yoshida.” Id. (citing Ex. 2001, ¶¶ 174–75). Patent Owner also asserts a person of ordinary skill “would have recognized that Figure 8(a) of Sahu “relates to specific devices that were tested in Sahu.” Id. at 50. We find these assertions unpersuasive. We have discussed above the” slip op. at 57

  Patent outcomesUS 8,498,593 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,498,593
• Valve Corporation v. Immersion CorporationAll claims unpatentable
  PTAB · Mar 23, 2026 · IPR2024-00582 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–6, 14–16, and 19 are unpatentable based on anticipation by or obviousness over Pratt, and obviousness over Pratt–Ku, Ku, or Ku–Jiang.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The parties agree that formal education could substitute for practical experience, and vice versa. Pet. 6, PO Resp. 18. The parties’ proposed levels of ordinary skill appear to be substantially similar, supported by testimonial evidence, and consistent with the asserted prior art and the types of problems and solutions identified in the ’738 patent. See, e.g., Ex. 1001, 1:6–61. Although we discern no difference in the outcome of this decision from choosing one over the other, we adopt Petitioner’s proposed level of skill for this decision. The outcome of our decision would be the same under Patent Owner’s proposal.” slip op. at 7

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

    “We find insufficient support in the specification or prosecution history to narrow the term “haptic effect” to only one that has not been modified or combined with another haptic effect. The ’738 patent still refers to combined or modified haptic effects as a “haptic effect.” Ex. 1001, 11:35–38 (“a haptic effect may further be modified or combined with another haptic effect” and “the haptic effect can include one or more haptic effects”). We also find no support for importing into the construction of “haptic effect” the ’738 patent’s example in which a haptic effect can be “based on the proximity signal and the touch sensor signal.” That is already an explicit claim limitation. Id. at 14:19–20 (“generate a haptic output signal based at least in part on the first [proximity] and second [touch] sensor signals”). Including that limitation as part of the construction of “haptic effect” would render the limitation superfluous. See Apple, Inc. v. Ameranth, Inc., 842 F.3d 1229, 1237 (Fed. Cir. 2016) (“The Board was correct to not include in its construction of ‘menu’ features of menus that are expressly recited in the claims . . . . Construing a claim term to include features of that term already recited in the claims would make those expressly recited features redundant.”). We also disagree with Patent Owner that the ’738 patent’s references to haptic effects modified or combined with other haptic effects are unclaimed embodiments. The ’738 patent discloses that a proximity-based haptic effect may be combined with a touch-based haptic effect, such as when “a particular haptic effect associated with a particular control on a user interface element [is] further . . . modified or combined with another haptic effect based on the proximity sensor signal,” or when “the haptic effect [to be output by the processor] . . . include[s] a haptic effect meant to confirm ‘pushing’ on a virtual button.” Ex. 1001, 11:32–40. These examples are consistent with the claim language and we find no credible evidence in the record that these embodiments are intended to be excluded from the claimed invention. Thus, we agree with Petitioner that it would be incorrect to construe the term “haptic effect” to include the extraneous limitations Patent Owner proposes. We also agree with Petitioner that a person of ordinary skill in the art reading the ’738 patent disclosure would have understood that a combined or modified haptic effect is still a haptic effect.” slip op. at 11

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

    “To show anticipation under § 102, a petitioner must locate every element in a claim, arranged as recited in the claim, in a single prior art reference. See Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008). The limitations may be present in the reference “either explicitly or inherently.” In re Schreiber, 128 F.3d 1473, 1477 (Fed. Cir. 1997). In making this determination, we consider the reference “together with the knowledge of one of ordinary skill in the pertinent art.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994) (citing In re Samour, 571 F.2d 559, 562 (CCPA 1978)).” slip op. at 13

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

    “We find Petitioner’s arguments persuasive and disagree with Patent Owner’s arguments to the contrary. Ku discloses summing two overlapping vibration signals, one “based at least in part on” data from a proximity sensor and another “based at least in part on” data from a touch sensor. Ex. 1008, Fig. 12 (items 705, 710, and 715). The summed signal 715 is the basis for generating what the user would perceive as a single haptic effect. See Ex. 1004 ¶ 210–212. This meets limitation 1F. We agree with Petitioner’s argument as to why there would have been a motivation to modify Pratt to include Ku’s teachings. Petitioner’s argument is not merely that Pratt was ready for improvement; Petitioner persuasively argues that a person of ordinary skill in the art would have had reason to add Ku’s method for confirming that the user has touched the intended icon to Pratt’s system. Both Pratt and Ku already disclose using both proximity and touch data in generating a haptic effect, and based on the evidence of record, we are of the view that combining the two teachings would not have been uniquely challenging or otherwise beyond the level of ordinary skill in the art. See Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157, 1162 (Fed. Cir. 2007) (“Leapfrog presents no evidence that the inclusion of a reader in [electronic children's toys] was uniquely challenging or difficult to one of ordinary skill in the art.” (citing KSR, 550 U.S. at 419–420))” slip op. at 32

  Patent outcomesUS 11,175,738 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,175,738
• Texas Instruments Incorprated v. Parkervision, Inc.All claims unpatentable
  PTAB · Nov 21, 2025 · IPR2024-00934 · APJ Michael R Zecher · IPR · Final written decision

  Claims 19–21 are unpatentable as obvious over DeMaw and, separately, over Macnally.

  RulingsFinal written decision

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

    “1. Principles of Law A claim is unpatentable under § 103(a) if the differences between the” slip op. at 16

  Patent outcomesUS 7,496,342 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,496,342
• Harbor Freight Tools USA, Inc. / Generac Power Systems, Inc. et al. v. Champion Power Equipment, Inc.Instituted
  PTAB · Nov 20, 2025 · IPR2025-00951 · APJ Eric C Jeschke · IPR · Institution

  The Board instituted IPR on claims 1–19 and all asserted grounds, finding a reasonable likelihood that claim 1 would have been obvious over DuroMax and De Vries.

  RulingsInstitution decision

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

    “review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Inter partes review may not be instituted “unless . . . the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314. Upon consideration of the evidence and arguments in the record, for the reasons below, we determine that the information presented shows a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. We thus institute inter partes review on all challenged claims on all asserted grounds. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 362–63, 369–70 (2018); 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “For purposes of this Decision, we adopt the definition of the level of ordinary skill in the art proposed by Petitioner. As to the inclusion of physics in Petitioner’s definition, Patent Owner acknowledges that an undergraduate mechanical engineering degree holder would have the requisite knowledge here but does not adequately explain why an undergraduate physics degree holder would not. In addition, Patent Owner requires “a four-year degree in mechanical engineering or a closely related field,” but fails to identify what fields are “closely related.” See Prelim. Resp. 10 (emphasis added). Based on the Winkel Declaration, we are persuaded at this stage that a hypothetical undergraduate physics degree holder would have had adequate knowledge for one of ordinary skill in the art of the invention here. See Winkel Decl. ¶ 106. As to the requisite years of experience proposed in the definitions— three for Petitioner versus “at least one” for Patent Owner—we note that Patent Owner’s definition is broader than, but includes, Petitioner’s definition. Moreover, for both the inclusion of physics and the years of experience issues, Patent Owner acknowledges that the arguments in the Preliminary Response “are not impacted based on which definition is applied.” Prelim. Resp. 10. Further, Patent Owner does not argue at this stage that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art.” slip op. at 11

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

    “At this stage of the proceeding and on the current record, we need not and do not explicitly construe the phrase “selector switch.” 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)). Although we do not expressly adopt Petitioner’s proposed construction at this stage of the proceeding, we note that it at least generally aligns with the tentative claim construction issued by the United States District Court in the California Litigation: “Mechanical device whose positioning precludes simultaneous access to two fuels.” Ex. 300310 at 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”); Memorandum from Acting Director Coke Morgan Stewart to Members of the Patent Trial and Appeal Board (Sept. 15, 2025), available at https://www.uspto.gov/sites/default/files/documents/ Memo_re_prior_findings_of_fact_and_conclusions_of_law_9_16_25.pdf (“Prior Determinations Memo”) (discussing PTAB consideration of prior findings of fact and conclusions of law). We also note that Patent Owner” slip op. at 14

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “Like the Federal Circuit in In re Ellis, although the patent classification of the reference is “some evidence of ‘non-analogy, . . . we consider the similarities and differences in structure and function of the inventions . . . to carry far greater weight.” In re Ellis, 476 F.2d at 1372 (affirming the Board and rejecting the applicant’s nonanalogous art argument). Here, the challenged patent discusses in the Background of the Invention the need for a way to “prevent both valves from being ‘on’ at the” slip op. at 21

  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,598,101

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.