• 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
• Digital Global Systems, Inc. v. Deepsig, Inc.Some claims unpatentable
  PTAB · Mar 6, 2026 · IPR2024-01358 · APJ William V Saindon · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

  • BurdenNot shown unpatentable

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

  Patent outcomesUS 11,018,704 mixed
  Claim construction§ 103 obviousness
  Patents in suitUS 11,018,704
• Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentable
  PTAB · Feb 24, 2026 · IPR2024-01256 · APJ Miriam L Quinn · IPR · Final written decision

  Claims 1–6, 10–14, 16, and 17 were not shown unpatentable because Ahn and Chaudhri did not teach or suggest the claimed movement of an object during the gesture.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for patent owner

    “interface objects and, more specifically, the display of user interfaces on applications, in accordance with contacts on the touch-sensitive surface of a display. Ex. 1001, (54), Abstr. Consistent with the scope of the ’727 patent, we find that the level of skill in the art is reflected in a person having a bachelor’s degree in computer science, computer engineering, electrical engineering, human-computer interaction, or a comparable field and at least two years of professional experience working with graphical user interfaces, human-computer interfaces, or equivalents.” slip op. at 6

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

    “Because there is no dispute as to the scope and meaning of these terms, and for consistency with the Decision on Institution, we apply the meaning of the terms “blur” and “distance magnitude” as stated above where applicable. However, we note that our determination does not hinge on the meaning of these terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (only those terms that are in controversy need 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 8

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

    “it was “known to utilize ‘cues’ to help the user know what gesture to utilize and whether they are correctly performing the gesture (e.g., graphics such as movable images that help the user visualize the correct gesture and how to complete it successfully).” Pet. 40 (citing Ex. 1005, Abstract, ¶¶ 54, 62, 73). This sentence does not cure the deficiency noted above regarding Petitioner’s reliance on Ahn’s graphic shadow moving with a gesture. Chaudhri is relied on for the proposition that, Ahn’s graphic shadow is “[i]ndeed” a movable image known to give a user a visual cue. Id. But no such “cue” is provided in Ahn by the graphical shadow alone, because there is no movement of that object. The Petition does not present argument that a Chaudhri object is the movable object or how any of Chaudhri’s teachings of movable objects would have suggested to modify Ahn “to thereby move” the graphical shadow.” slip op. at 18

  • Strike new argumentNew argument disregardedDecided for patent owner

    “the theory that Ahn’s graphic shadow moves. Reply 3−4. Petitioner interprets the sentences in Ahn we have analyzed above in conjunction with testimony of Dr. Terveen to argue that temporal descriptions in Ahn make it obvious for a person of ordinary skill in the art to drag in the right direction while continuing to press the graphic 1800. Id. (citing Exs. 1004 ¶¶ 117−119, Ex. 1023 ¶ 10). The Petition, however, relies on an Ahn disclosing a moving graphic shadow according to the embodiment of Figure 18(a), as described in paragraph 118. Petitioner now changes its theory of how Ahn’s graphic shadow would move according to paragraph 119, i.e., that although the graphic shadow is merely pressed (in the embodiment shown in Figure 18(b)) it would also be dragged while pressed. Reply 3. Not only is this a shift from the theory Petitioner presents in the Petition, it is not persuasive. As Patent Owner argues, and we agree, there is no cogent explanation for modifying the graphic shadow embodiment of Figure 18(b), especially in light of Ahn’s disclosure that the graphic shadow disappears when pressed and the menu list is displayed as emerging. Sur-reply 2−3. In other words, Petitioner’s new argument does not account for Ahn’s teaching that the objective of the graphic shadow is merely to notify the user of the start of the gesture, and once that start of the gesture is detected (the press on the graphic shadow), paragraph 119 informs us that there is no longer a need for the graphic shadow—it disappears from the display. Ex. 1004 ¶ 119. The Petition does not offer any argument for a theory in which the gesture of paragraph 119 (the press, not a touch and drag operation) results in graphic 1800 disappearing, while also moving during the disappearance. We are mindful that “[i]t is impermissible within the framework of section 103 to pick and choose from any one reference only so much of it as will support a given position to the exclusion of other parts necessary to the full appreciation of what such reference fairly suggests to one skilled in the art.” Bausch & Lomb, Inc. v. Barnes-Hind / Hydrocurve, Inc., 796 F.2d 443, 448 (Fed. Cir. 1986)). Consequently, we determine that Petitioner’s argument in Reply belatedly relying on the different embodiment of paragraph 119 is improper new argument, and that even if considered it is not persuasive.” slip op. at 20

  Patent outcomesUS 11,740,727 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,740,727
• Thermaltake Technology Co., Ltd. / Thermaltake Inc. v. Chien-Hao ChenAll claims unpatentable
  PTAB · Feb 17, 2026 · IPR2024-01230 · APJ Andreas Baltatzis · IPR · Final written decision

  Claims 1–5 are unpatentable; substitute claims 6 and 7 are unpatentable, and the Revised Motion to Amend is denied.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “our Institution Decision comports with the qualifications a person would have needed to understand and implement the teachings of the ’336 patent and the prior art of record. Inst. Dec. 15. Accordingly, we adopt the level of skill discussed in our Institution Decision. C.” slip op. at 11

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

    “Pharms. Inc. v. Amino Chemicals Ltd., 715 F.3d 1363, 1374 (Fed. Cir. 2013)). Accordingly, Patent Owner applies a different definition of “side,” in claim 1’s recitation of “an illumination area on at least two sides of the fan at top of the body,” to that definition used to understand “side[s] of the body,” discussed above. Specifically, Patent Owner argues that Petitioner’s dictionary definition of “side,” including “an area next to something” applies to “an illumination area on at least two sides of the fan at the top of the body.” See id. at 8–9.” slip op. at 17

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

    “Hasegawa, and Huang teaches or suggests the limitations of claim 3, and that one skilled in the art would have been motivated to combine those teachings with a reasonable expectation of success. See Ex. 1004 ¶¶ 136– 140; Ex. 1008, 8:4–15, 3:20–29. Accordingly, we determine that claim 3 would have been obvious over Lai and Huang, or Lai, Hasegawa, and Huang. F.” slip op. at 50

  • 112 supportMotion to amend, deniedDenied

    “c) Conclusion We conclude that Patent Owner's Revised Motion to Amend adds new” slip op. at 90

  Patent outcomesUS 10,690,336 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 10,690,336
• Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentable
  PTAB · Feb 10, 2026 · IPR2024-01116 · APJ Sharon Fenick · IPR · Final written decision

  Petitioner did not prove claims 1, 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191, 192, 197, 199–204, 208–216, 223, 225, or 230 unpatentable because the asserted combinations did not establish the claimed blurring …

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “(Ex. 1003), that a person of ordinary skill in the art (“POSITA”) would have had “a Bachelor of Science degree in computer science, computer engineering, electrical engineering, human-computer interaction, or a comparable field and at least two years of professional experience in the design and development of graphical user interfaces (GUIs), human-computer interfaces, or equivalents thereof,” and that “[a]dditional years of experience could substitute for an advanced-level degree (and vice-versa).” Pet. 6 (citing Ex. 1003 ¶¶ 29–30).” slip op. at 9

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

    “C. Claim Construction In these proceedings, there is no controversy that would require us to decide any claim construction issue. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe 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. Obviousness of Claims 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191,” slip op. at 10

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

    “obviousness of the menus in the Ahn-Chaudhri combination following a user’s finger as the user performs the dragging gesture to open the menu.” Pet. Reply 2 (citing 01119-Petition, 26–33, substantially identical to Pet. 32– 40). However, again, the Petition does not explain an alternative theory in which Chaudhri supplements Ahn’s menu functionality to move that menu onto the screen, as opposed to teaching visual cues provided by gradual changes of the display during a gesture or the visual cue that an unlock image may provide during the unlock gesture. See Pet. 14–18 (describing Chaudhri teaching “visual differentiation” or “transitioning an optical intensity” between a user-interface object and the background, based on, e.g., transparency), 35–40 (same). In Reply, Petitioner adds evidence to attempt to support its contention that the combination teaches a menu following a user’s finger during a dragging gesture, involving references to Chaudhri’s discussion of a visual cue, further discussing Chaudhri’s unlock image. Ex. 1005 ¶¶ 54, 62, 74–79, Figs. 5A-5C (cited at Pet. Reply 4–5). With respect to these citations and arguments, even if they had been timely presented in the Petition, we agree with Patent Owner that they do not articulate a modification of Ahn with Chaudhri or a motivation to combine. PO Sur-reply 6. Additionally, we agree that these embodiments of Chaudhri are distinct from the cited portions of Chaudhri discussed with respect to this theory in the Petition, which relate not to the movement of displayed graphics, but to variations of optical intensity and visual cues. Id. at 6–7. We evaluate the Petition’s arguments in light of Petitioner’s statement in Reply that they require a teaching regarding “menus . . . following a user’s finger as the user performs the dragging gesture.” Pet. Reply 2. To the extent that the Petition shows that the combination of Ahn and Chaudhri would show visual changes as the user performs a dragging gesture, these do not relate to the movement of a menu, but rather to other optical effects. Thus, as we do not find that the Petition supports an Ahn-Chaudhri combination in which a menu follows a user’s finger as the user performs the dragging gesture to open the menu, as Petitioner argues, we determine that Petitioner has not shown limitation 2.d of claim 2 taught or suggested by the combination of Ahn and Chaudhri according to this theory.” slip op. at 31

  • Strike new argumentNew argument disregardedDecided for patent owner

    “Petitioner argues that “even under [this] interpretation of Ahn, the only difference between Ahn and the claims is whether the animation occurs in direct correspondence with a user’s dragging gesture or after the dragging gesture is complete – a straightforward design choice if ever there was one.” Pet. Reply 3–4 (citing Ex. 1024, 99:16–108:20; Ex. 1023 ¶ 12). However, as Patent Owner argues (PO Sur-reply 7–8) this argument is presented in Reply and is an improper shift of theory from the Petition. Nevertheless, were we to consider it, we would not find it compelling; Dr. Terveen’s cited testimony repeats this bare statement and is not supported by any evidence or additional explanation. Ex. 1023 ¶ 12; see 37 CFR § 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.”); Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (Aug. 24, 2022) (precedential) (assigning little weight to opinion testimony that “merely repeats” conclusory statements in a brief, without “cit[ing] any additional supporting evidence or provid[ing] any technical reasoning to support [the declarant’s] statement”).” slip op. at 29

  Patent outcomesUS 10,656,754 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,656,754
• Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentable
  PTAB · Feb 10, 2026 · IPR2024-01115 · APJ Sharon Fenick · IPR · Final written decision

  Apple did not prove claims 1, 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191, 192, 197, 199–204, 208–216, 223, 225, and 230 unpatentable over the asserted Ahn combinations.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for patent owner

    “In the Decision on Institution in each proceeding, we noted that Petitioner’s definition left it unclear whether the bachelor’s degree in the proposed definition would be considered by Petitioner to be “an advancedlevel degree,” and did not adopt the portion of the definition relating to the substitution of years of experience for a degree. Dec. on Inst. 15–16. Patent Owner “does not agree with all aspects of Petitioner’s proposed level of ordinary skill” but did not propose an alternative definition. PO Resp. 10–11. Patent Owner’s declarant, Dr. Rosenberg, adopted Dr. Terveen’s definition for the purposes of his declaration. Ex. 2018 ¶¶ 32–33. We again adopt the main portion of Dr. Terveen’s definition, and determine that one of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, human-computer interaction, or a comparable field and at least two years of professional experience working with graphical user interfaces and applications for computers.” This definition is commensurate with the problems and solutions in the ’754 patent and prior art of record and is supported by declarant testimony.” slip op. at 9

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

    “C. Claim Construction In these proceedings, there is no controversy that would require us to decide any claim construction issue. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe 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. Obviousness of Claims 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191,” slip op. at 10

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

    “obviousness of the menus in the Ahn-Chaudhri combination following a user’s finger as the user performs the dragging gesture to open the menu.” Pet. Reply 2 (citing 01119-Petition, 26–33, substantially identical to Pet. 32– 40). However, again, the Petition does not explain an alternative theory in which Chaudhri supplements Ahn’s menu functionality to move that menu onto the screen, as opposed to teaching visual cues provided by gradual changes of the display during a gesture or the visual cue that an unlock image may provide during the unlock gesture. See Pet. 14–18 (describing Chaudhri teaching “visual differentiation” or “transitioning an optical intensity” between a user-interface object and the background, based on, e.g., transparency), 35–40 (same). In Reply, Petitioner adds evidence to attempt to support its contention that the combination teaches a menu following a user’s finger during a dragging gesture, involving references to Chaudhri’s discussion of a visual cue, further discussing Chaudhri’s unlock image. Ex. 1005 ¶¶ 54, 62, 74–79, Figs. 5A-5C (cited at Pet. Reply 4–5). With respect to these citations and arguments, even if they had been timely presented in the Petition, we agree with Patent Owner that they do not articulate a modification of Ahn with Chaudhri or a motivation to combine. PO Sur-reply 6. Additionally, we agree that these embodiments of Chaudhri are distinct from the cited portions of Chaudhri discussed with respect to this theory in the Petition, which relate not to the movement of displayed graphics, but to variations of optical intensity and visual cues. Id. at 6–7. We evaluate the Petition’s arguments in light of Petitioner’s statement in Reply that they require a teaching regarding “menus . . . following a user’s finger as the user performs the dragging gesture.” Pet. Reply 2. To the extent that the Petition shows that the combination of Ahn and Chaudhri would show visual changes as the user performs a dragging gesture, these do not relate to the movement of a menu, but rather to other optical effects. Thus, as we do not find that the Petition supports an Ahn-Chaudhri combination in which a menu follows a user’s finger as the user performs the dragging gesture to open the menu, as Petitioner argues, we determine that Petitioner has not shown limitation 2.d of claim 2 taught or suggested by the combination of Ahn and Chaudhri according to this theory.” slip op. at 31

  • BurdenNot shown unpatentable

    “(3) Conclusion For the reasons discussed above, Petitioner has not shown limitation 2.d to be taught, suggested, or otherwise rendered obvious by Ahn and Chaudhri. Thus, we determine that Petitioner does not show by a preponderance of the evidence that claim 2 would have been obvious over the combination of Ahn and Chaudhri.” slip op. at 32

  Patent outcomesUS 10,656,754 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,656,754
• Apple Inc. v. Smith Interface Technologies, LLCAll claims unpatentable
  PTAB · Jan 26, 2026 · IPR2024-01084 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–4, 8–18, 22–30, and 34–39 are unpatentable as obvious over Shiplacoff and over Shiplacoff combined with Nan.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “have had a bachelor’s degree in computer science, computer engineering, electrical engineering, human-computer interaction, or a comparable field and at least two years of professional experience in the design and development of graphical user interfaces (GUIs), human-computer interfaces, or equivalents thereof. Pet. 4 (citing Ex. 1003 ¶ 22). Petitioner’s declarant, Loren Terveen, Ph.D., testifies that “[s]uch experience could be obtained through research and study in a graduate program or through comparable exposure through industry employment, and additional years of experience could substitute for the advanced-level degree.” Ex. 1003 ¶ 22. Patent Owner agrees with this definition. PO Resp. 13 (citing Dec. 5). As Petitioner’s description of a person of ordinary skill appears commensurate with the subject matter before us, we apply Petitioner’s definition for purposes of this Decision. Also, the level of ordinary skill in the art can be evidenced by the references cited, and we find it commensurate with the cited references in this proceeding. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978).” slip op. at 5

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

    “according to the Phillips standard.” Pet. 4. Patent Owner contends that under the plain language of claim 1, the “one or more criteria” is satisfied when a “movement parameter” of “the second input” is detected to be “above a movement threshold.” PO Resp. 14. Patent Owner contends that under the plain language of claim 27, the “second one or more criteria” is satisfied when “a duration parameter” of the “second input” is detected to be “above a duration threshold.” Id. at 15. Patent Owner contends that the plain language of limitations [1j] and [1k] requires an operation capable of detecting a second input by a second contact that includes movement across a display in a direction, determining whether the second input meets or does not meet the recited criteria, and triggers performance of each of the corresponding display actions as appropriate. Id. at 15–19. Patent Owner 15. Id. at 21–23. Patent Owner contends that the plain language of limitations [27d]–[27f] recited in claim 27 require an operation that enables the device to detect a second input by a second contact that includes movement across the display in a direction, determine whether the second input meets or does not meet the two recited criteria, and trigger performance of each of the recited display actions as appropriate. Id. at 19– 20. Patent Owner contends that for “the second input” recited in limitations [1j] and [1k], “the second input” must be detected in the same operational context. Id. at 23–24. In particular, Patent Owner contends that limitations [1j] and [1k], and similar limitations recited in claims 15 and 27, “require a single, common contact event as the starting point of the claimed logic operations.” Id. at 24; see id. at 25–26. We do not need to determine whether Patent Owner’s proposed constructions are correct, because under either Petitioner’s or Patent Owner’s proposed constructions, we find that the prior art would have rendered all challenged claims obvious as discussed below in our patentability analysis.” slip op. at 6

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “at 418; see also id. at 421 (“A person of ordinary skill is . . . a person of ordinary creativity, not an automaton.”). Patent Owner’s contention and the supporting testimony of Dr. Madisetti does not address Shiplacoff’s teaching of using a gesture, such as Shiplacoff’s flick gesture, to return to launch screen. We agree with Petitioner and Dr. Terveen in finding that Shiplacoff’s disclosure that “returning to the launch screen . . . is performed by performing a gesture” (Ex. 1004 ¶ 99) such as a flicking gesture (Ex. 1004 ¶¶ 126, 129; Ex. 1023 ¶ 13) teaches using a flicking gesture to return from home screen to launch screen. See Pet. 16, 22–24; Ex. 1003 ¶¶ 52–53, 59; Ex. 1023 ¶ 13; Reply 7–10. Because Dr. Terveen’s testimony is consistent with and supported by the teachings of Shiplacoff as a whole (in contrast to that of Dr. Madisetti), we credit the testimony of Dr. Terveen in finding that using a gesture to return from home screen to launch screen as taught by Shiplacoff, where the gesture is a flick gesture as taught by Shiplacoff, yields the predictable result of using a flick gesture to return from home screen to launch screen. Ex. 1023 ¶ 13; Ex. 1003 ¶¶ 52–61; KSR, 550 U.S. at 416.” slip op. at 21

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

    “articulate why a person of ordinary skill in the art would have used Shiplacoff’s flicking gesture to switch from full screen mode to the launch screen. PO Resp. 47–49. Petitioner contends that Shiplacoff’s swipe up gesture teaches limitation [1j] by including a movement parameter above a movement threshold. Pet. 17–23. Petitioner contends that Shiplacoff teaches that a user can perform another gesture to return to the home screen. Id. at 23. Petitioner contends that when a gesture different from the swipe up gesture is used to return to the home screen, a person of ordinary skill would have used a flicking gesture because the flicking gesture has a different movement parameter than the swipe up gesture, namely, a movement parameter that does not meet the movement threshold. Pet. 23– 24 (citing Ex. 1004 ¶¶ 99–102, 167; Ex. 1003 ¶¶ 60–61). We agree with Petitioner for the reasons given in the Petition and as discussed above. We reiterate that using a gesture to return from home screen to launch screen as taught by Shiplacoff, where the gesture is a flicking gesture as taught by Shiplacoff, yields the predictable result of using a flicking gesture to return from home screen to launch screen. Ex. 1023 ¶ 13; Ex. 1003 ¶¶ 52–61; KSR, 550 U.S. at 416. We disagree with Patent Owner’s contention that Shiplacoff teaches away from using the flicking gesture to switch from full screen mode to the launch screen because, according to Patent Owner, Shiplacoff already uses the flick gesture to perform scrolling in full screen mode. PO Resp. 49–52 the same gesture in a given mode can be assigned to different functions depending on where, when, and how the gesture is input by the user, as discussed above. Reply 11–12 (discussing Shiplacoff’s teaching of associating the same tap gesture with different functions depending on where the tap occurs), 13–14 (discussing Duarte’s teaching of associating both a drag gesture and a scrolling gesture to the same mode). Ex. 1023 ¶¶ 16–19. We agree with Petitioner and Dr. Terveen, that based on the teachings of Shiplacoff (and, by incorporation, Duarte), a person of ordinary skill in the art would have recognized that a flick started in area 102 or near an edge of screen 101 and continuing onto screen 101 would be distinguished from a flick entirely within screen 101 based on location, and would perform a different function. Ex. 1023 ¶¶ 18–19. We also agree with Petitioner and Dr. Terveen, that Duarte teaches associating a gesture with one function when a modifier key is not pressed, and associating the same gesture with a different function when the modifier key is pressed, such that a flick performed when the key is not pressed would perform one function such as scrolling and a flick performed when the key is pressed would perform another, such as changing the display mode. Reply 15 (citing Ex. 2003 ¶ 64; Ex. 1023 ¶ 20). We agree with Petitioner that Shiplacoff does not teach away from using a flicking gesture to change from full screen mode to home screen because it “does not criticize, discredit, or otherwise discourage investigation into the invention claimed.” Reply 10 (quoting Depuy Spine, 567 F.3d at1327).” slip op. at 25

  Patent outcomesUS 10,649,578 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,649,578
• Universal Electronics, Inc. / Gemstar Technology (Qinzhou) Co. Ltd. et al. v. ROKU, Inc.All claims unpatentable
  PTAB · Jan 21, 2026 · IPR2022-00818 · APJ Russell E Cass · IPR · Remand

  On remand, the Board held claim 11 unpatentable under §103 over Wouters and Verzulli because Wouters’s fixer saves the combined codeset for reinstallation.

  RulingsRemand decision

  • RemandOther

    “We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached

    “Additionally, the obviousness inquiry typically requires an analysis of “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (requiring “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness”)); see In re Warsaw Orthopedic, Inc., 832 F.3d 1327, 1333 (Fed. Cir. 2016) (citing DyStar Textilfarben GmbH & Co. Deutschland KG v. C.H. Patrick Co., 464 F.3d 1356, 1360 (Fed. Cir. 2006)).” slip op. at 10

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

    “We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20

  • Strike new argumentNew argument consideredDecided for petitioner

    “We also find that Petitioner has not forfeited its argument that Wouters’s fixer and reinstallation functionality satisfies limitation 11[e]. The Petition pointed to Wouters’s “fixer” for limitation 11[e], and cited Dr. Houh’s Declaration specifically identifying and quoting Wouters’s disclosure of reinstallation at page 10, lines 14 through 24. Pet. 35 (quoting Ex. 1009, 10:14–20) (citing Ex. 1002 ¶ 167); Ex. 1003 ¶ 167 (quoting Ex. 1009, 10:14–24). We find that a person of ordinary skill in the art reading the Petition and its cited evidence (including paragraph 167 of Dr. Houh’s first Declaration) would be apprised that Petitioner was relying on the portion of Wouters describing the “fixer” and reinstallation functionality.” slip op. at 23

  Patent outcomesUS 8,378,875 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,378,875

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.