• 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
• Arashi Vision (U.S.) LLC (D/B/A Insta360) v. Gopro, Inc.No claims unpatentable
  PTAB · Dec 10, 2025 · IPR2024-01186 · APJ Brian D Range · IPR · Final written decision

  Claims 1–20 were not shown unpatentable because Kwatra does not teach or suggest minimizing rotational velocity and acceleration as required by the claims.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art (POSITA) would have the following characteristics: “a bachelor’s degree in engineering or computer science, or equivalent field, and two years of experience working on image or video processing or digital cameras.” Pet. 6 (citing Ex. 1002 ¶¶ 36–37). Petitioner states that, “[a]lternatively, a POSITA would have four years of experience working on image or video processing 6 Patent Owner asserts objective evidence of nonobviousness. Prelim. Resp. 19–27. or digital cameras.” Id. Petitioner further contends “[a]n advanced graduate degree in the disciplines cited above may make up for the work experience indicated above.” Id. Patent Owner does not dispute the level of ordinary skill in the art. Prelim Resp. 14–15. For purposes of this Decision, we adopt Petitioner’s proposal as reasonable and consistent with the ’894 patent specification and the prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “Petitioner “does not believe any terms require a formal construction.” Pet. 6. Patent Owner agrees “no claim terms presently require construction to resolve any current dispute between the parties.” PO Resp. 15. We do not discern a need to construe explicitly any claim language at this juncture because doing so would have no effect on our analyses below of Petitioner’s asserted grounds and will not assist in resolving the present controversy between the parties. 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) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “Kwatra teaches, at Equation 7, minimizing velocity and acceleration of a function representing camera path (P). FF ¶¶ 6, 8–9. Kwatra does not state that this camera path function considers rotation. Rather, the words “camera path” suggest x, y, z movement of the camera rather than rotation of the camera. Dr. Foroosh’s testimony that Kwatra’s minimization of a smoothed camera path does not result in minimizing rotational velocity and acceleration is credible because this testimony is consistent with Kwatra as a whole and consistent with the other evidence of record. Id. ¶ 10. Kwatra recognizes that image rotation angle (“θ”) may not remain smooth. Id. ¶ 12. But rather than attempting to minimize velocity and acceleration of rotation of the camera housing, Kwatra states that applying a smoothness constraint on rotation angle “may be non-linear.” Id. ¶ 13. Consistent with Kwatra, Dr. Foroosh credibly explains the difficulty of applying linear techniques to rotation. Id. Thus, Kwatra proposes instead constraining the sine and cosine of theta. Id. ¶ 14. The Kwatra provisional application is part of the Kwatra reference (id. ¶ 15), and it similarly opts for simpler schemes rather than estimating all parameters for all frames jointly. Id. ¶ 16. The provisional explains that the rotational component is relatively small such that non-linear computations minimizing velocity and rotation can be avoided. Id. ¶¶ 17–18. The testimony of Patent Owner’s witness, Dr. Foroosh, explaining the provisional is credible (Ex. 2018 ¶ 72) because it is consistent with Kwatra’s complete disclosure. Dr. Foroosh’s testimony is more credible than the testimony of Petitioner’s witness, Dr. Katsaggelos, because Dr. Katsaggelos did not review the Kwatra provisional application and, thus, did not review the entire disclosure of Kwatra. Id. ¶ 19; see also In re Etter, 756 F.2d 852, 859 (Fed. Cir. 1985) (en banc) (obviousness analysis considers whether “the claimed inventions are rendered obvious by the teachings of the prior art as a whole” (emphasis added)).” slip op. at 28

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “(id. ¶ 15), and it similarly opts for simpler schemes rather than estimating all parameters for all frames jointly. Id. ¶ 16. The provisional explains that the rotational component is relatively small such that non-linear computations minimizing velocity and rotation can be avoided. Id. ¶¶ 17–18. The testimony of Patent Owner’s witness, Dr. Foroosh, explaining the provisional is credible (Ex. 2018 ¶ 72) because it is consistent with Kwatra’s complete disclosure. Dr. Foroosh’s testimony is more credible than the testimony of Petitioner’s witness, Dr. Katsaggelos, because Dr. Katsaggelos did not review the Kwatra provisional application and, thus, did not review the entire disclosure of Kwatra. Id. ¶ 19; see also In re Etter, 756 F.2d 852, 859 (Fed. Cir. 1985) (en banc) (obviousness analysis considers whether “the claimed inventions are rendered obvious by the teachings of the prior art as a whole” (emphasis added)).” slip op. at 28

  Patent outcomesUS 10,574,894 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,574,894
• Arashi Vision (U.S.) LLC (D/B/A Insta360) v. Gopro, IncNo claims unpatentable
  PTAB · Nov 25, 2025 · IPR2024-01165 · APJ William V Saindon · IPR · Final written decision

  Claims 1–21 were not shown unpatentable because Zhou does not teach the claimed low-light high-pass or stickiness parameter limitations.

  RulingsFinal written decision

  • BurdenFwd all claims patentableNot shown unpatentable

    “4. Conclusion for the Prior Art Analysis In sum, we find that Zhou does not disclose the low-light high-pass parameter or the stickiness parameter. Petitioner’s grounds for both independent claims 1 and 16 rely on Zhou for teaching a low-light high-pass parameter or a stickiness parameter. Pet. 23–28, 64. Because we find Zhou does not teach these limitations, all of Petitioner’s grounds fall for this reason. III. CONCLUSION For the reasons given above, we determine that Petitioner has not established by a preponderance of the evidence that any claim of the ’840 patent would have been obvious in view of the prior art cited.” slip op. at 18

  • Skill levelSkill level petitioner adoptedOther

    “A person of ordinary skill in the art (POSITA) in the field of the ’840 patent would have a bachelor’s degree in engineering or computer science, or equivalent field, and two years of experience working on image or video processing, or digital cameras. Alternatively, a POSITA would have four years of experience working on image or video processing, or digital cameras. An advanced graduate degree in the disciplines cited above may make up for the work experience indicated above. Pet. 6 (citing Ex. 1002 ¶ 32). Patent Owner applies the same standard. PO Resp. 26–27. We use this agreed-upon standard for purposes of this Decision.” slip op. at 7

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “We review this testimony based on the strength of the underlying factual basis. 37 C.F.R. § 42.65(a); Ashland Oil, Inc. v. Delta Resins & Refractories, Inc., 776 F.2d 281, 294 (Fed. Cir. 1985) (“Lack of factual support for expert opinion going to factual determinations, however, may render the testimony of little probative value . . ..”). Here, the underlying factual basis is not very strong for either witness. That said, we find that Dr. Foroosh’s testimony is more logically sound and consistent with the ’840 patent disclosure. Based on our reading of the specification, we find a clear indication that “stickiness” has to do with the past. In order to control “the extent by which preceding portion(s) . . . impacts determination of the smoothed trajectory” (emphasis added), one must control the degree by which the past frames impact determination. And to control the degree of the past’s influence, one must, as a consequence, favor the past over the future. That is, the frame of reference of the stickiness parameter is the past. The specification could have used a time-agnostic term, like a “nearness” or “adjacency” parameter, but it did not. Thus, the fact that “stickiness” is used in conjunction with “preceding” indicates that it deals with a preference for preceding frames. On this basis, we find Dr. Katsaggelos’s testimony less persuasive than Dr. Foroosh’s.” slip op. at 10

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

    “That said, we do not construe a stickiness parameter as prohibiting consideration of future frames. Instead, we determine that the stickiness parameter’s value determines the impact of the preceding portions, versus the following portions. The ’840 patent recognizes this, when it says that a stickiness parameter value of “1,” representing a “lazy” stabilizer that maximally favors the past, would not override a violation of the margin constraint based on the look-ahead (i.e., would not allow the viewing window to fall out of bounds in the event of large future motion). See Ex. 1001, 22:26–30; see also id. at 12:61–13:29 (acknowledging that favoring the past may lead to a conflict with the viewing window determination), 15:39–60 (adjusting the viewing window to ensure it does not violate a margin constraint). Thus, while a past-favoring parameter by necessity favors the past over the future, it does not prohibit consideration of the future. In view of the above, we construe the claimed “stickiness parameter” as a parameter that controls the extent by which preceding portions of the trajectory impacts determination of the smoothed trajectory, with an understanding that in order to favor preceding portions, to some extent, the parameter must relatively disfavor following portions.” slip op. at 10

  Patent outcomesUS 10,958,840 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,958,840
• Arashi Vision (U.S.) LLC (D/B/A Insta360) v. Gopro, IncNo claims unpatentable
  PTAB · Nov 25, 2025 · IPR2024-01164 · APJ William V Saindon · IPR · Final written decision

  Claims 1–21 were not shown unpatentable because Shi does not disclose the claimed low-light high-pass parameter required by the asserted obviousness grounds.

  RulingsFinal written decision

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

    “Given the teachings of the specification, we agree with Patent Owner that a low-light high-pass parameter is a parameter of a smoothing function that favors high frequencies (high pass) when exposure times are long (low light). See Tr. 42:10–18 (Patent Owner’s counsel stating that “high-pass” means “there’s a bias or preference for high frequencies”); Ex. 2020, 93:23– 94:15 (Petitioner’s declarant, Dr. Katsaggelos, agreeing that a high-pass system attenuates the low frequency of a signal). Although we acknowledge Petitioner’s position that the specification provides other ways or considerations in implementing a smoothing function, based on our above analysis of the specification, we find that the specification describes the lowlight high-pass parameter as a specific component of a smoothing function. See, e.g., Ex. 1001, 21:17–25 (setting out several parameters besides the low-light high-pass parameter used in trajectory smoothing).” slip op. at 10

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “position and a real device position. Id. at 18:27–40. In other words, the blur is addressed by analyzing the image to identify motion and then shifting the image. Shi, however, does not disclose how its parameter is based on low light (or the long exposure times indicative of low light). In its Petition, Petitioner asserts that a person of ordinary skill in the art would understand that “blurs can be caused by low light conditions.” Pet. 28 (citing Ex. 1003 ¶ 111). Although this is true, that does not mean that Shi’s blurs are identified by a parameter that considers low light. As we just described, Shi identifies the blur by quantifying the amount of motion of the points in an image, not by identifying low light. This is simply a different way to determine the presence of motion blur. In Shi, blur is measured, whereas in the ’840 patent, it is inferred based on low-light conditions (e.g., by observing the exposure time). See, e.g., Ex. 1007, 18:7– 26; Ex. 1001, 19:12–26. In its Reply, Petitioner does not point to any further disclosures. Accordingly, we find that Shi does not disclose the “low-light” aspect of the claimed low-light high-pass parameter. This is sufficient to determine that Petitioner’s ground does not meet all claim limitations. Similarly, we find that Shi does not disclose the “high-pass” aspect of the parameter. Shi’s blur compensation uses a spherical interpolation to modify the image. Ex. 1007, 18:27–40. The low-light high-pass parameter, as we have construed the term, allows more high frequencies. To allow more high frequencies, this necessarily means either allowing fewer low frequencies, or allowing more high frequences as opposed to some counterfactual situation in which fewer high frequencies were going to be allowed. See Ex. 2020, 94:23–95:15; Ex. 2022. We are directed to no persuasive evidence from Petitioner that Shi’s spherical interpolation favors high frequencies over low frequencies. Accord Ex. 2018 ¶ 107 (Patent Owner’s expert stating that Shi’s spherical interpolation “reintroduce[es] both high- and low-frequency motion”). Even if Shi allows the viewing window to track the camera position “consistent with the natural blur in the image” (Ex. 1007, 17:63–67), we are not provided with sufficient evidence to conclude by a preponderance of the evidence that providing a similar visual goal as a high-pass parameter (Ex. 1001, 22:16–18, “the output motion may include high frequencies that mask motion blur”) is the same as having a high-pass parameter. Again, merely preserving high frequencies is not the same as having a “high-pass parameter” because, as construed, a “high-pass parameter” also involves some degree of attenuation of low frequencies or relative increase of high frequencies. Accordingly, we find that Shi does not disclose the “high-pass” aspect of the claimed low-light high-pass parameter.” slip op. at 18

  Patent outcomesUS 10,958,840 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,958,840
• Google LLC v. Cellular South, Inc.Institution denied
  PTAB · Nov 21, 2025 · IPR2025-00877 · APJ William V Saindon · IPR · Institution

  The Board denied institution for claims 1–11 because the Zhao-Kouzani combination did not sufficiently show a fractal representation based on landmarks.

  RulingsInstitution decision

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

    “review under 35 U.S.C. § 314(b) and 37 C.F.R. § 42.4(a). The standard for instituting an inter partes review is set forth in 35 U.S.C. § 314(a), which provides that an inter partes review may not be instituted unless “there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons provided below, we determine that Petitioner has not demonstrated a reasonable likelihood that at least one claim of the ’853 patent is unpatentable, and we do not institute an inter partes review. 37 C.F.R. § 42.108(a).” slip op. at 2

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

    “generally known in the art, and that this is acknowledged by the ’853 patent. Pet. 40–41 (citing, e.g., Ex. 1001, 15:40–44). Petitioner asserts that Kouzani touts the benefits of fractal models and that it would have been obvious to use Kouzani’s fractal model as the object model in Zhou. Pet 44 (asserting that “[a] person of ordinary skill would have therefore been motivated to implement Kouzani’s techniques in Zhao’s system”); see also id. 42–45. (entire argument). Patent Owner argues that Kouzani’s fractals would not result in the claimed limitation. Prelim. Resp. 21–23. In particular, Patent Owner points out that Kouzani’s fractals use a block-based fractal system, which do not include “a representation of the object based on landmarks associated with the object” as required by claim 1. Id. at 21–22. Patent Owner’s argument is persuasive. Even if Kouzani teaches fractals, claim 1 is not broadly claiming any fractal, but rather one that is “based on landmarks” (e.g., eyes, nose, etc.). See Ex. 1001, 13:53–57. The block-based system of Kouzani is based on abstract, repeated patterns of pixels, without regard to what the pixels represent. See, e.g., Ex. 1006, 8 (describing a “search . . . through the domain pool to find a domain block whose contractive transformation best approximates the range block” and then storing all of the transformations that, together, “represent the compressed image of a person’s face”), Fig. 4 (showing example blocks). This is in contrast to looking for particular landmarks in the image. Thus, we find that Petitioner has not sufficiently established that Kouzani’s fractal is based on landmarks. In Petitioner’s ground, Petitioner asserts that Zhao already teaches the claimed landmarks (Pet. 39, citing Ex. 1003 ¶¶ 58, 65), but Petitioner’s ground replaces or modifies the object model of Zhao with the fractals of Kouzani, which are not based on landmarks. Petitioner does not explain how Zhao’s modified model, now using a block-based fractal system, would still have the landmarks of Zhao’s original model. Even if it were obvious to include fractals, we are persuaded that the fractals included by Kouzani are not based on landmarks. Alternatively, if Petitioner is asserting merely to use fractals in Zhao’s models, then Petitioner has not sufficiently accounted for the particular fractals claimed and explained persuasively how merely using fractals in Zhao would lead to the claimed subject matter, i.e., fractals based on landmarks. In either event, Petitioner has not sufficiently established that the proposed combination satisfies the “fractal includes a representation of the object based on landmarks” limitation of claim 1.” slip op. at 11

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “Patent Owner’s argument is persuasive. Even if Kouzani teaches fractals, claim 1 is not broadly claiming any fractal, but rather one that is “based on landmarks” (e.g., eyes, nose, etc.). See Ex. 1001, 13:53–57. The block-based system of Kouzani is based on abstract, repeated patterns of pixels, without regard to what the pixels represent. See, e.g., Ex. 1006, 8 (describing a “search . . . through the domain pool to find a domain block whose contractive transformation best approximates the range block” and then storing all of the transformations that, together, “represent the compressed image of a person’s face”), Fig. 4 (showing example blocks). This is in contrast to looking for particular landmarks in the image. Thus, we find that Petitioner has not sufficiently established that Kouzani’s fractal is based on landmarks. In Petitioner’s ground, Petitioner asserts that Zhao already teaches the claimed landmarks (Pet. 39, citing Ex. 1003 ¶¶ 58, 65), but Petitioner’s ground replaces or modifies the object model of Zhao with the fractals of Kouzani, which are not based on landmarks. Petitioner does not explain how Zhao’s modified model, now using a block-based fractal system, would still have the landmarks of Zhao’s original model. Even if it were obvious to include fractals, we are persuaded that the fractals included by Kouzani are not based on landmarks. Alternatively, if Petitioner is asserting merely to use fractals in Zhao’s models, then Petitioner has not sufficiently accounted for the particular fractals claimed and explained persuasively how merely using fractals in Zhao would lead to the claimed subject matter, i.e., fractals based on landmarks. In either event, Petitioner has not sufficiently established that the proposed combination satisfies the “fractal includes a representation of the object based on landmarks” limitation of claim 1.” slip op. at 11

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

    “standard set forth in Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). That is, “the words of a claim ‘are generally given their ordinary and customary meaning’ . . . that the term would have to a person of ordinary skill in the art in question at the time of the invention.” Id. at 1312–13 (quoting in Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). We do not need to construe any claim terms to reach a decision in this proceeding. Realtime, 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 6

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,126,853
• Recor Medical, Inc. / Otsuka Medical Devices Co., Ltd. v. Medtronic Ireland Manufacturing Unlimited Co.Some claims unpatentable
  PTAB · Nov 3, 2025 · IPR2022-00431 · APJ Eric C Jeschke · IPR · Remand

  On remand, claims 1–3 and 8–12 are unpatentable over the instituted grounds; claim 4 was not shown unpatentable.

  RulingsRemand decision

  • RemandOther

    “Federal Circuit (Paper 33), which vacated the original Final Written Decision and remanded the proceeding to the Board. See ReCor Med., Inc. v. Medtronic Ir. Mfg. Unlimited Co., No. 2023-2251, 2025 WL 944511 (Fed. Cir. Mar. 27, 2025) (“the Appeal Decision” or “Appeal Dec.”); see also Paper 41 (copy of the Appeal Decision). The Federal Circuit’s mandate issued on May 5, 2025. See Paper 40. We have jurisdiction under 35 U.S.C. § 6, and we issue this Final Written Decision on Remand under 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73. For the reasons below, on the complete record, we conclude that Petitioner has proven, by a preponderance of the evidence, the unpatentability of claims 1–3 and 8–12 of the challenged patent, and we conclude that Petitioner has not proven, by a preponderance of the evidence, the unpatentability of claim 4.” slip op. at 2

  • Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia outweighedNot shown unpatentable

    “and Petitioner’s rebuttal evidence. Objective evidence of nonobviousness, when present, must be considered as part of an obviousness inquiry. Transocean Offshore Deepwater Drilling, Inc. v. Maersk Drilling USA, Inc., 699 F.3d 1340, 1349 (Fed. Cir. 2012). Notwithstanding what the teachings of the prior art would have suggested to one of ordinary skill in the art, the totality of the evidence submitted, including objective evidence of nonobviousness, may lead to a conclusion that one or more of the challenged claims would not have been obvious to one of ordinary skill in the art. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984).” slip op. at 50

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

    “1. Claims 1–3 and 8–11 Because the obviousness ground based on Levin and Acker is dispositive as to challenged claims 1–3 and 8–11, we need not reach this additional ground as to those claims. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 371 (2018) (holding that a petitioner “is entitled to a final written decision addressing all of the claims it has challenged”); Boston Sci. Scimed, analysis in the appeal to the Federal Circuit. See Appeal Dec. *1–*2 (summarizing grounds at issue on appeal and not discussing anticipation based on Acker). Inc. v. Cook Grp. Inc., 809 F. App’x 984, 990 (Fed. Cir. 2020) (nonprecedential) (stating that the “Board need not address issues that are not necessary to the resolution of the proceeding,” such as “alternative arguments with respect to claims [the Board] found unpatentable on other grounds”); SK Hynix Inc. v. Netlist, Inc., IPR2017-00692, Paper 25 at 40 (PTAB July 5, 2018) (determining all challenged claims to be unpatentable and not addressing additional grounds). 2. Dependent Claim 4 As to dependent claim 4, in the context of this ground, Petitioner relies on Acker as to the additional limitations in claim 4 in the same manner as relied on in the context of the ground based on Levin and Acker. See Pet. 73 (“The combination teaches this element for the same reasons described in [the obviousness ground based on Levin and Acker], claim 4, with the exception that [one of ordinary skill in the art] would have been motivated based on his or her knowledge of prior renal denervation work, as noted above.”). Thus, for the same reasons discussed above (see § II.C.3.c), we determine, based on the complete record, that Petitioner has not demonstrated by a preponderance of the evidence that claim 4 would have been obvious based on Acker and the knowledge of one of ordinary skill in the art. G. Asserted Obviousness of Claim 12 Based on Acker, the Knowledge of a Person of Ordinary Skill in the Art, and Yock Petitioner asserts that claim 12, which depends from independent claim 1, would have been obvious based on Acker, the knowledge of one of ordinary skill in the art, and Yock. Pet. 12, 75; Pet. Reply 35–36. Patent Owner provides arguments addressing this ground. PO Resp. 57–60; PO” slip op. at 75

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

    “1. Independent Claim 1 Petitioner contends that Acker discloses each limitation of claim 1. Pet. 61–63; Pet. Reply 35. In the “Overview of the Ground” section, Petitioner references its proposed construction of the phrase “configured to” and states that “it is proper to consider whether the prior art is ‘capable of’ performing the recited functions, as opposed to requiring that a designer of a prior art device have actually conceived of the recited functional language.” Pet. 61. Petitioner continues: “If the PTAB agrees that this is the proper approach to claim construction, then Acker also anticipates the claims challenged in this ground.” Id. For the reasons below, we determine, based on the complete record, that Petitioner has not demonstrated by a preponderance of the evidence that claim 1 is anticipated by Acker. As to element 1d, which includes the phrase “configured to,”16 Petitioner states that Acker is capable of being used to target renal neural fibers outside of the blood vessel to thermally induce modulation of target neural fibers while protecting non-target tissue in the blood vessel wall from thermal injury for the reasons discussed under claim 1, limitation [1d] and in the section entitled “Reasonable Expectation of Success”, beginning on page 37 [of the Petition]. Pet. 62–63 (citing Daft Pet. Decl. ¶ 179) (first bracketed text added by Petitioner). Patent Owner argues that, in the context of this asserted ground based” slip op. at 71

  Patent outcomesUS 8,845,629 mixed
  § 102 anticipation§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 8,845,629
• Digital Global Systems, Inc. v. Deepsig Inc.Institution denied
  PTAB · May 28, 2025 · IPR2025-00194 · APJ Robert J Weinschenk · IPR · Institution

  The Board denied institution under § 314(a), finding no reasonable likelihood for the remaining claims except claim 13, whose potential success did not justify instituting trial.

  RulingsInstitution decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “had “a bachelor’s degree in electrical engineering, computer engineering, or equivalent and at least two years of experience working with radio communication systems and machine learning.” Pet. 3 (citing Ex. 1003 ¶¶ 33–34). Petitioner’s description of the level of ordinary skill in the art is supported by the testimony of Petitioner’s declarant, Dr. Zhi Ding. Ex. 1003 ¶¶ 33–34. Patent Owner does not dispute Petitioner’s description at this stage of the proceeding. We adopt Petitioner’s description for the purposes of this Decision.” slip op. at 4

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

    “the same standard used in a civil action under 35 U.S.C. § 282(b), including construing the claim in accordance with the ordinary and customary meaning of the claim as understood by one of ordinary skill in the art and the prosecution history pertaining to the patent. 37 C.F.R. § 42.100(b). Neither party proposes an express construction for any claim terms. Pet. 13; Prelim. Resp. 16. We determine that no claim terms require express construction for purposes of this Decision.” slip op. at 5

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

    “reasonable likelihood of prevailing in showing that claims 4–6, 12, 14, and 16–22 would have been obvious over Jüschke and Holt. Petitioner may satisfy its burden for claim 13, but, as discussed below, that would not impact our decision to exercise our discretion under § 314(a) to deny institution. See Section II.F.” slip op. at 16

  • Other 314aInstitution denied discretionary otherInstitution denied

    “inter partes review. SAS Inst. v. Iancu, 584 U.S. 357, 366 (2018). Specifically, “[i]f a panel determines that a petition meets the standards for institution in relation to fewer than all the challenges presented, . . . the panel will evaluate all the challenges and determine whether, in the interests of efficient administration of the Office and integrity of the patent system, the entire petition should be denied.” See Consolidated Trial Practice Guide, 64 (Nov. 2019), available at https://www.uspto.gov/sites/default/files/ documents/tpgnov.pdf. Here, thirteen challenged claims remain after Patent Owner’s statutory disclaimer. Petitioner at most demonstrates a reasonable likelihood of prevailing for one dependent claim, which has no claims depending therefrom. See Sections II.C–II.E. Thus, based on the particular facts of this case, we find that instituting trial would not be an efficient use of the Board’s time and resources, and we exercise our discretion to deny institution under § 314(a). See Deeper, UAB v. Vexilar, Inc., IPR2018- 01310, Paper 7 at 41–43 (PTAB Jan. 24, 2019) (informative); Chevron Oronite Co. LLC v. Infineum USA L.P., IPR2018-00923, Paper 9 at 10–11 (PTAB Nov. 7, 2018) (informative).” slip op. at 16

  Claim construction§ 103 obviousnessDiscretionary denial
  Patents in suitUS 11,777,540

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.