• 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
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.No claims unpatentable
  PTAB · Jun 9, 2026 · IPR2025-00321 · APJ Christopher M Kaiser · IPR · Final written decision

  The Board held claims 1, 2, 5–7, 9, 16, and 17 not unpatentable because the asserted combinations did not establish the required purge-tower teachings or prior-art status.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that one of ordinary skill in the art “would have had (1) at least a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a related field, and (2) at least two years of research or industry experience in 3D printing or materials used for 3D printing.” Pet. 5 (citing Ex. 1003 ¶¶ 14–16). Petitioner also argues that “[a]dditional experience could substitute for a formal degree or formal training (and vice versa).” Id. Patent Owner proposes a slightly different level of skill, arguing that a person of ordinary skill in the art “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” Prelim. Resp. 24. Neither party explains why the outcome of this case would be affected by the adoption of any of the proffered definitions of a person of ordinary skill in the art. We adopt Petitioner’s assessment of the level of ordinary skill in the art, as it appears consistent with the ’324 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “According to the ’713 patent, “[p]urge tower 24 itself may be . . . recycled or otherwise discarded as desired.” Ex. 1001, 8:27–28. This description provides some support for Patent Owner’s view, because a purge tower too intimately integrated with the part would be difficult or impossible to recycle or discard. This is further supported by the ’713 patent’s statement that “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Id. at 8:30–34. It also is supported by Dr. Hickner’s testimony that the ’713 patent “clearly shows . . . the 24 purge tower separated from the part” and that “the purge tower is a separate physical object.” Ex. 2016, 28:8–10, 64:1–9. On the other hand, there is evidence supporting Petitioner’s view that, as long as the purge tower is generally separate from the part and the support structure, it may still make contact with those portions of the print. As noted above, “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Ex. 1001, 8:30–34. This language does not exclude locations adjacent to or in contact with the part or the support structure. Thus, determine that a “purge tower,” as that term is used in the context of the ’713 patent, may not be an integrated portion of a printed part or support structure but need not be free of all contact with the printed part or support structure.” slip op. at 9

  • BurdenNot shown unpatentable

    “There is evidence of record to support both Petitioner’s view and Patent Owner’s view. On the record developed at trial, however, we cannot say that the preponderance of the evidence favors Petitioner, who bears the burden of proof. See 35 U.S.C. § 316(e). Accordingly, Petitioner has not shown by a preponderance of the evidence that KISSlicer teaches printing a layer of a purge tower each time the printer switches one extruder to the operating mode. Because proving the obviousness of claims 1 and 16 requires such a showing, Petitioner has not shown by a preponderance of the evidence that claims 1 and 16 would have been obvious over the combination of Priedeman and KISSlicer. 5. Analysis of Remaining Claims Claims 2, 6, 7, 9, and 17 all depend, directly or indirectly, from claim 1 or claim 16. Accordingly, they all include the limitations of either claim 1 or claim 16. Because, as discussed above, Petitioner has not shown that the combination of Priedeman and KISSlicer teaches or suggests all the limitations of claims 1 and 16, Petitioner also has not proven by a preponderance of the evidence that claims 2, 6, 7, 9, and 17 would have been obvious over that combination of references.” slip op. at 21

  • Obviousness (§103) › Analogous artAnalogous artOther

    “On the record developed at trial, we agree with Petitioner. According to several industry forum posts, people interested in three-dimensional printing located the website where KISSlicer was posted between February 2012 and April 2012. Ex. 1028, 1 (post discussing and directing others to KISSlicer on April 11, 2012); Ex. 1031, 1 (two posts discussing KISSlicer on March 16, 2012, and March 21, 2012); Ex. 1032, 1 (two posts discussing KISSlicer on February 11, 2012, and February 14, 2012). Thus, not only was it possible for people of ordinary skill in the art to locate KISSlicer; people of ordinary skill in the art actually did locate it. Accordingly, Petitioner has shown by a preponderance of the evidence that KISSlicer was publicly accessible.” slip op. at 19

  Patent outcomesUS 9,421,713 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,421,713
• Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Jun 9, 2026 · IPR2025-00311 · APJ Christopher M Kaiser · IPR · Final written decision

  Claims 1, 3–11, and 17–22 are unpatentable as obvious over grounds using Mazumder and Mori; grounds relying on Henke fail because Henke is not analogous art.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Electrical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printers including remote control of rapid fabrication systems.” Pet. 6 (citing Ex. 1003 ¶¶ 40–42). Petitioner also argues that “[a]dditional years of experience could substitute for an advanced-level degree (and vice versa).” Id. Patent Owner proposes a slightly different level of skill, arguing that a person of ordinary skill in the art “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Electrical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” PO Resp. 11–12. Neither party explains why the outcome of this case would be affected by the adoption of either of the proffered definitions of a person of ordinary skill in the art. We adopt Petitioner’s assessment of the level of ordinary skill in the art, as it appears consistent with the ’324 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 9

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

    “There is also evidence that supports Petitioner’s proposed construction, under which a user interface may display both the image and the projection if it displays them at different times. This evidence includes statements in the specification that describe displaying an image “instead” of “a rendering of a three-dimensional model” and that describe displaying a “video image and/or model projection” rather than merely a video image and a model projection. Ex. 1001, 22:43–53, 24:52–55, Figs. 5, 7. It also includes arguments in the prosecution history distinguishing Taminger on the basis of failure of disclose any display of both an image and a projection at all, rather than on the basis of failure to disclose simultaneous display of both visualizations. Ex. 1002, 160, 161. Based on our review of all the probative evidence, we find that the preponderance of the evidence supports Petitioner’s view, so we construe the challenged claims as not requiring simultaneous display of the image and the projection.” slip op. at 15

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

    “With the problem solved by the ’324 patent defined as monitoring automated three-dimensional fabrication processes, we find that Mori is at least reasonably pertinent to the problem. Mori discloses “[a] machining status monitoring apparatus.” Ex. 1005, code (57), ¶ 43. That apparatus uses “actual CCD cameras . . . to image the workpiece.” Id. ¶ 49. It also has a “virtual image generating section” with “virtual CCD cameras” having “view points” that “match the view points of the actual CCD cameras.” Id. ¶¶ 59, 61, 62. This disclosure relates quite closely to monitoring an automated three-dimensional fabrication process and thus is at least reasonably pertinent to solving that problem. d) Conclusion For the reasons discussed above, Mori is both in the same field as the ’324 patent and at least reasonably pertinent to the problem solved by the ’324 patent. Accordingly, it is analogous art to the ’324 patent.” slip op. at 21

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

    “Regarding combining the teachings of Mazumder with those of Mori, the evidence of record shows that the print head of Mazumder’s three-dimensional printer could obscure portions of the actual camera’s view of the object being printed and that displaying Mori’s virtual image of the object in addition to Mazumder’s actual image of the object “would have allowed the user to of the remote computer to monitor the progress of the object even when the actual view of the object is partially or totally obscured.” Ex. 1003 ¶ 86. c) Conclusion Regarding Claim 1 For the reasons discussed above, the preponderance of the evidence shows that claim 1 would have been obvious over the combination of Mazumder and Mori.” slip op. at 26

  Patent outcomesUS 8,562,324 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,562,324
• Shenzhen Tuozhu Technology Co. Ltd. v. Stratasys, Inc.All claims unpatentable
  PTAB · Jun 3, 2026 · IPR2025-00257 · APJ Lilan Ren · IPR · Final written decision

  Claims 1–15 are unpatentable because Petitioner proved by a preponderance of the evidence that the asserted § 103 grounds render them unpatentable.

  RulingsFinal written decision

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

    “proceeding, we determine Petitioner has proven by a preponderance of the evidence that each of claims 1–15 of the ’660 patent is unpatentable.” slip op. at 85

  Patent outcomesUS 9,592,660 unpatentable
  § 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,592,660
• Tesla, Inc. v. Charge Fusion Technologies, LLCAll claims unpatentable
  PTAB · May 13, 2026 · IPR2025-00032 · APJ Mitchell G Weatherly · IPR · Final written decision

  Claims 1–29 are unpatentable as obvious under §103 based on the asserted combinations of prior art.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time of the invention. Graham, 383 U.S. at 17. Petitioner submits that the ordinarily skilled artisan would have at least a bachelor’s degree in electrical or mechanical engineering (or an equivalent field) and at least two years of work experience involving automotive systems, including electric vehicle power management. . . . Additional industry experience or technical training may offset less formal education, while advanced degrees or additional formal education may offset lesser levels of industry experience. Pet. 2 (citing Ex. 1003 ¶¶ 30–32). Patent Owner “takes no position with respect to Petitioner’s proposed level of ordinary skill.” PO Resp. 17. For the purposes of our analysis below, we apply Petitioner’s proposed level of ordinary skill, which we find to be consistent with the problems addressed in the ’338 patent and the prior art.” slip op. at 10

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

    “Initially, we note that “amount of charge” reflects no express limitation on the manner of expressing the “amount” or the “charge.” And the Specification uses both “desired charge percent level” and “desired charge range level” as alternative ways for a user may specify an “amount of 3 As recited in independent claims 10, 19, and 28 charge.” For example, the Specification describes that a user may specify an amount of charge by specifying a desired travel distance as follows: “the user may indicate a desired charging level (and/or a desired charging level may be automatically calculated) based on a desired distance of travel.” Ex. 1001, 19:49–57 (emphasis added). Therefore, “amount of charge” may also refer to a desired mileage or range. Figure 7 further demonstrates that a user may select “amount of charge” in terms of a “percent” or a “range” as shown in Petitioner’s annotated version of the pertinent portion of that figure as shown below.” slip op. at 11

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

    “We disagree with Patent Owner. First, Patent Owner’s reliance on Wonderland as announcing a rule having broad effect is misplaced. Patent Owner contends that the “Federal Circuit has confirmed that where the primary reference already includes the function of the secondary reference, an allegation to incorporate that function into the primary reference is improper hindsight and no motivation to combine exists.” Id. at 29 (citing Wonderland NurseryGoods Co. v. Thorley Indus., LLC, 988 F.Supp. 2d 479, 498–99 (W.D. Pa. 2013), aff'd, 644 F. App'x 1011 (Fed. Cir. 2016); citing Kinetic Concepts, Inc. v. Smith & Nephew, Inc., 688 F.3d 1342, 1368 (Fed.Cir.2012))). Patent Owner’s citation to Wonderland does not support the proposition for which it is cited, namely that the Federal Circuit has “confirmed” that incorporating a function from a secondary reference into a primary reference is “improper hindsight” that precludes a motivation to combine teachings from the primary and secondary references. In Wonderland, the district court denied an accused infringer’s motion for summary judgment of invalidity, in part, due to its finding that genuine issues of material fact existed for the issue of whether sufficient motivation to combine prior art existed. Wonderland, 988 F. Supp. 2d at 511. The Wonderland decision does not constitute a final ruling on that issue, and the Federal Circuit’s summary affirmance of the final ruling by the district court does not address the issue or reflect how the issue was resolved at trial. Wonderland NurseryGoods Co. v. Thorley Indus., LLC, 644 F. App’x 1011 (Fed. Cir. 2016). Second, Petitioner also correctly points out that although Ferro refers to wireless charging, it provides no implementation details. Ex. 1004 ¶ 36; Ex. 2003, 54:8–55:9. Ferro also describes manual options for initiating charging, Ex. 1003¶ 146 (citing Ex. 1004 ¶ 109), and that an ordinarily skilled artisan would have been motivated to apply Oyobe’s vehicle sensor to allow a user to initiate Ferro’s charging methods more easily without the user having to leave the vehicle, Ex. 1003 ¶¶ 151, 152. Accordingly, we find that Petitioner has established that an ordinarily skilled artisan would have been motivated to incorporate Oyobe’s use of a sensor to establish presence of a vehicle near a charging station into Ferro’s system.” slip op. at 20

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

    “The test for obviousness is not whether the features of a secondary reference may be bodily incorporated into the structure of the primary reference. . . . Rather, the test is what the combined teachings of the references would have suggested to those of ordinary skill in the art.” MCM Portfolio LLC v. Hewlett-Packard Co., 812 F.3d 1284, 1294 (Fed. Cir. 2015). Patent Owner’s argument fails to account for the level of skill and creativity of an ordinarily skilled artisan, who would have possessed a bachelor’s degree in engineering and could have easily accounted for the differences in scale depicted by Letendre’s and Donnelly’s controls. Ex. 1003 ¶¶ 247–249. Accordingly, we find that Petitioner’s showing on the motivation to combine teachings of Ferro, Donnelly, and Letendre to arrive at limitation 1h is persuasive. slip op. at 30

  Patent outcomesUS 11,563,338 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,563,338
• SAP America, Inc. v. Cyandia, Inc.All claims unpatentable
  PTAB · Mar 13, 2026 · IPR2024-01433 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–7, 10, 11, 13, 18, 19, 23, 29, 35, and 36 are unpatentable as obvious over the PCT Publication and Austin-Lane.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner asserts that a person of ordinary skill in the art at the time of filing “would have had a Bachelor’s degree in electrical engineering, computer science, or the like, and/or four or more years of experience in server-based applications” and that “[a]dditional experience may make up for a lack of education and vice versa.” PO Resp. 9. Because Petitioner’s proposed level of ordinary skill in the art appears to be consistent with the challenged patent and prior art, we adopt it and use “skilled artisans” to refer to people with such skill at the time the invention was filed. We do not perceive a substantive distinction between the parties’ definitions, but note that Petitioner’s definition provides more detail about the capabilities of skilled artisans. 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 9

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

    “device indicated by the session data” encompasses “determining a notification method based on” session data indicating the current state of the external device, where the current state of the device encompasses an online state as well as an offline state. See Pet. 53–54; Tr. 55:3–10 (The Board: “Are there any other states of an external device other than online or offline?” Patent Owner: “As far as I know, Your Honor, those are the only two[.]”), Tr. 65:24–66:1 (The Board: “When the claim says current state, they mean it’s online or offline?” Petitioner: “Correct.”), Tr. 20:23–21:8. The specification is consistent with the plain language of the claim in disclosing two examples of the claimed “current state,” namely, online and offline. Ex. 1101, 21:1–4. The specification discloses that the notification manager “queries session manager 456 to determine the user’s connectedness.” Id. at 21:6–8. The specification discloses that if the user is “online, notify by, for example, the user’s active session. If offline, notify by, for example, a txt [sic] message, call the user’s landline, call a friend of the user, and the like.” Id. at 21:1–4, 23:28–31.” slip op. at 13

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “Patent Owner’s expert witness, Dr. Goodrich, show written description support for providing a notification to an active external device, Patent Owner has not cited any portion of the 2009 Parent, nor any portion of the testimony of Dr. Goodrich, to show that the 2009 Parent provides written description support for determining a notification method by which to provide an alert to an external device based on the current state of the external device as offline. We highlight that Paragraphs 130 and 131 of the 2011 CIP Application disclose offline notification preferences for determining a notification method by which to provide an alert to an external device based on the current state of the external device as offline. Ex. 1110 ¶¶ 130–131. Specifically, paragraphs 130 and 131 describe that: the notification manager of the eventing and alerting subsystem 452 queries the configuration server 454 for the user's notification preferences and correlates these notification preferences with session manager 456 to determine the best notification method. That is, the notification manager queries the configuration server 454 and determines, for example, that the user has certain online notification preferences and certain offline notification preferences. If online, notify by, for example, the user's active session. If offline, notify by, for example, a txt message. . . . The notification manager of the eventing and alerting subsystem 452 then queries session manager 456 to determine the user's connectedness. Id. That is, if the user’s connectedness, or “current state” of the claimed external device, is offline, and the user’s offline notification preferences are “notify by txt message,” the notification manager will determine that the notification method for the external device having a current state of offline is by txt message. See id. Thus, the 2011 CIP Application describes a notification manager that queries a session manager to determine whether an external device is offline, and if the external device is offline, determines a notification method for providing an alert on the external device based on the current status of the external device as offline and the user’s offline notification preferences. Although we find this written description support for the determining limitation in the 2011 CIP Application, we do not find this written description support in the 2009 Parent.” slip op. at 25

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

    “As to the “determining a notification method” limitation (1.10), Petitioner asserts that Austin-Lane teaches determining: (1) the user device(s) to send the notification to (e.g., phone, PDA, notebook computer, desktop computer); (2) the communication protocol to use to send the notification, i.e., how to send the notification (e.g., SMTP (for email), SMS (for texts), HTTP (for web browsers)); and (3) the type of alert to provide, i.e., how to present the notification, (e.g., text, an icon, a pop-up window, a video, an email, an audible or tactile alarm), based on the current state of the at least one external device indicated by the session data (“presence information”), which may include whether and on which device(s) the user is online and/or whether and on which applications the user has an active session. Id. at 53 (internal citations omitted) (citing Ex. 1105 ¶¶ 4, 5, 29, 32, 33, 39, 46, 48, 61, 79, Fig. 1). We highlight that paragraph 61 of Austin-Lane discloses that: The type preferences 650 may include preferences for various notification types. . . . [A]uction alert #1 660 defines the following delivery precedence 663: (1) a web browser (if the user is online), (2) an IM client (if the user is online), (3) a mobile phone #1, (4) a PDA, (5) a mobile phone #2, (6) a pager, and (7) an email inbox. Ex. 1105 ¶ 61; see id. ¶¶ 74–77 (Describing that one of several notification methods for delivering an alert to a user’s device is determined based on the current state of the user’s device as online or offline). Thus, Austin-Lane describes determining a notification method by which to provide an alert on an external device based on the current state of the external device as online as well as offline.” slip op. at 29

  Patent outcomesUS 8,751,948 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips
  Patents in suitUS 8,751,948
• 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
• Adobe Inc. v. Jonathan E. JaffeNo claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01352 · APJ Bach V Hoang · IPR · Final written decision

  Claims 1–6 were not shown unpatentable under any asserted §103 ground because the references did not teach monitoring the physical coupling between the sensor and memory.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The Institution Decision adopted and applied Petitioner’s proposed level of ordinary skill because Petitioner’s “definition generally comports with the level of skill necessary to understand and implement the teachings” slip op. at 11

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

    “The parties present various claim construction arguments, disputing the meaning of three limitations recited in claim 1: “a sensor, which is tightly coupled to said memory”; “monitoring the integrity of the tight coupling between said memory and said sensor”; and “based on.” See Pet. 9–14; PO Resp. 5–12; Pet. Reply 4–9; PO Sur-reply 4–11. For purposes of this Decision, we do not need to discuss the construction of “based on.” 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)). As explained below, this Decision turns on whether Glass or Rieger discloses limitation [1c] reciting “monitoring the integrity of the tight coupling between said memory and said sensor.” Ex. 1001, 20:65–66; see infra §§ II.C.2, II.E.1, II.F. That limitation recites an element which overlaps with the earlier-recited limitation “a sensor, which is tightly coupled to said memory.” To reach our decision, we need only provide a limited discussion of two of the parties’ claim construction arguments. Our analysis follows.” slip op. at 13

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

    “said integrity is compromised, then also providing an indication of said compromised integrity.” Ex. 1001, 20:65–21:2. Although Petitioner points out that the limitation does not expressly recite “‘specifically’ monitoring the tight coupling” (Pet. Reply 8), the structure of the clause suggests that the tight coupling is specifically monitored. At a high level, the limitation is straightforward in its recitation that the integrity being monitored is “of the tight coupling” (Ex. 1001, 20:65–66 (emphasis added)), plainly suggesting that the tight coupling is specifically monitored. More granularly, breaking the relevant clause down to its grammatical parts, the clause recites a gerund (“monitoring”) acting on a direct object (“the integrity”) which is modified by a prepositional phrase (“of the tight coupling”). Notably, the object of the preposition (“of”) is “the tight coupling.” Altogether, this reads that the integrity being monitored is specifically of the tight coupling. Also, the claim recites that “if said integrity is compromised, then also providing an indication of said compromised integrity.” Therefore, from the claim language we know that the “integrity” of the tight coupling is something that may be “compromised,” which is consistent with Patent Owner’s proposed construction of determining whether the physical coupling has been “accessed or disturbed.” Petitioner’s interpretation effectively inserts additional language into the limitation such that the limitation includes monitoring the integrity of a device containing or surrounding the tight coupling, such as a camera (or camera housing), e.g., “monitoring the integrity of a camera that includes the tight coupling.” But, because the plain reading and the structure of the limitation reads that it is specifically the tight coupling’s integrity—not another physical structure, like a camera—which is being monitored, a monitored is not consistent with the language of the claim. See PO Resp. 9 (arguing that “Petitioner’s construction is improper because the claim language explicitly requires monitoring the physical coupling between the memory and the sensor as opposed to some third structure” (emphasis omitted)).” slip op. at 17

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

    “package 50 does not specifically monitor the integrity of the coupling between Glass’s sensor and the memory and, instead, argues that Glass detects tampering of all “the components and interconnections contained in that packaging,” e.g., control logic 44, cropper 46, compressor 47, MUX 45, code generator 48, and the various interconnections between those components. See Pet. Reply 16; Ex. 1005, 5:13–41. As explained above, we construe “monitoring the integrity of the tight coupling between said memory and said sensor” to mean determining whether the physical 7 Petitioner does not assert that a person of ordinary skill in the art would have been motivated to modify Glass’s device in any way; Petitioner solely argues that Glass teaches limitation [1c], based on Petitioner’s proposed claim construction. See Pet. 30–32 (“Glass discloses this limitation.”); Pet. Reply 16–17 (“Glass and Rieger disclose the ‘monitoring’ step.”). disturbed, which specifically requires monitoring the physical coupling between the sensor and the memory. See supra § II.C.2. As we agree with Patent Owner that this limitation requires monitoring the physical coupling between the sensor and the memory, monitoring Glass’s tamper resistant package 50 does not teach or disclose “monitoring the integrity of the tight coupling between said memory and said sensor.” Accordingly, we determine that Petitioner fails to show that Glass teaches or suggests [1c] monitoring the integrity of the tight coupling between said memory and said sensor when said at least one internal and unique parameter is generated, and, if said integrity is compromised, then also providing an indication of said compromised integrity, as required by claim 1. Consequently, we determine that Petitioner has not shown, by a preponderance of the evidence, that the subject matter of claim 1 would have been obvious over Glass.8” slip op. at 30

  Patent outcomesUS 6,757,828 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 6,757,828

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.