• Google LLC v. Sandpiper CDN, LLCAll claims unpatentable
  PTAB · Oct 9, 2026 · IPR2025-00826 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–23 are unpatentable under § 103, including over Glines alone and the additional asserted combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art (“POSITA”) at the critical time “would have had at least a bachelor’s degree in computer science, electrical engineering, or a related field, and at least two years of work or research experience in the field of content delivery management or networks,” and that “additional education could substitute for work experience.” Pet. 3 (citing Ex. 1008 ¶¶ 51–53). Patent Owner provides substantially the same assessment. PO Resp. 16. We adopt Petitioner’s proposed level of ordinary skill, as it appears to be consistent with the specification of the ’112 patent and the prior art of record.” slip op. at 7

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

    “claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. [§] 282(b).” 37 C.F.R. § 42.100(b). Under this standard, the words of a claim generally are given their “ordinary and customary meaning,” which is the meaning the term would have to a person of ordinary skill at the time of the invention, in the context of the entire patent including the specification. Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Neither party proposes any express claim construction. Pet. 3; PO Resp. 16. We address the parties’ interpretation of the scope of “causing said hostname to be resolved” in our discussion of Petitioner’s assertions for limitation [1.d]. Based on the record before us, we determine that no claim term requires express construction.” slip op. at 8

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Strike new argumentNew argument consideredDecided for petitioner

    “We do not agree. The Petition states that Glines discloses that the anycast is resolved by an ISP DNS server. Pet. 20. The Petition identifies Glines’s local ISP DNS resolver 18 as the claimed ISP DNS server. Id. The Petitioner further asserts that Glines’s ISP DNS resolver 18 sends the request to the DNS server 38, but states that “Glines’s local DNS resolver, an ISP DNS server, thus causes the hostname . . . to be resolved.” Id. at 21–22. The Petition also drew an analogy with the ’112 patent and the role of local DNS server 70a in the Petition. See Pet. 20–21. Because the Petition and the Reply both identify Glines’s local ISP DNS resolver 18 as causing the hostname to be resolved, Petitioner has not advanced a new theory of unpatentability in its Reply. 6 At oral argument, Patent Owner suggested a narrower claim reading, but admitted that this had not been briefed. Tr. 36:15–38:9, 44:9–16. We do not address this reading because it was not set forth in the briefing. In the briefing, Patent Owner took the broader reading discussed here. See Tr. 41:12–23; PO Sur-reply 7.” slip op. at 13

  Patent outcomesUS 9,021,112 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,021,112
• 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
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co. Ltd.Adverse judgment
  PTAB · May 19, 2026 · IPR2025-01327 · APJ Sheila F Mcshane · IPR · Adverse judgment

  The Board entered adverse judgment against Throughtek on claims 1–19 after finding it abandoned the contest by failing to file mandatory notices or respond to the show-cause order.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “The Order to Show Cause explained that under 37 C.F.R. § 42.73(b), “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” Paper 8, 3. The Order to Show Cause also explained that failure to participate in a proceeding, such as failure to file mandatory notices as required under 37 C.F.R. § 42.8, may be considered abandonment of the contest and result in adverse judgment against Patent Owner under 37 C.F.R. § 42.73(b). Id. (citing Cellpak, Inc. v. Mambate USA Inc., IPR2021-00007, Paper 4 at 2 (PTAB Mar. 23, 2021)). The Order to Show Cause gave Patent Owner ten calendar days to show cause why adverse judgment should not be entered against it. Id. Patent Owner did not respond to the Order to Show Cause. More than ten calendar days have elapsed since the date the Order to Show Cause was entered, and Patent Owner has not filed mandatory notices. In view of Patent Owner’s failure to file mandatory notices within the specified time period, we determine that Patent Owner has abandoned the contest. Pursuant to 37 C.F.R. § 42.73(b)(4), we construe Patent Owner’s abandonment of the contest as a request for adverse judgment. Under these circumstances, we determine that entry of judgment against Patent Owner is appropriate.” slip op. at 3

  None
  Patents in suitUS 9,727,655
• Snap Inc. v. You Map Inc.All claims unpatentable
  PTAB · May 4, 2026 · IPR2022-00568 · APJ Jason M Repko · IPR · Remand

  Claims 1–20 remain unpatentable; the contingent motion to amend is denied because the proposed substitute claims would have been obvious over Feldman and Jackson in view of ordinary skill.

  RulingsRemand decision

  • RemandDecided for patent owner

    “challenge fails even if Petitioner’s summary of the references were correct because Petitioner did not present a sufficient reason to modify Feldman to include a current zoom level in its search request. FWD 56. The Federal Circuit vacated this finding specifically and contemplated that there would be a “consideration of obviousness” on remand. CAFC Dec. 10–11. That consideration requires more than determining whether any one reference teaches a current zoom level and a search, generally. See FWD 56 (quoting MTA Reply 10). Here, Petitioner’s challenge is based on modifying the Feldman-Jackson combination. So the Board must determine on remand whether the Feldman-Jackson combination in view of knowledge of a POSA meets the claim limitations at issue. We also disagree to the extent that Petitioner argues that the Board is precluded from considering additional arguments on the relevant issues on remand. The Board’s preliminary guidance on the Motion to Amend stated that Petitioner’s obviousness rationale was based on convenience and this reason was not sufficiently supported: reference lacks a sufficient explanation of why one of ordinary skill in the art would have added the zoom levels in the prior art to Feldman. See id. At most, Petitioner argues that it would be convenient to “specify the area the user desires to search for content” in this way. Id. at 14. But, on this record, Petitioner has not sufficiently explained why it would be convenient to do so in Feldman. See id. Nor has Petitioner sufficiently explained how or why the prior-art features confer this convenience. See id. MTA PG, 13. Because the Board’s conclusion turned on the lack of sufficient explanation, the briefing that followed was limited to Petitioner’s obviousness rationale. See, e.g., MTA Reply 9–12, MTA Sur-reply 1–12. Under these specific circumstances, we determine that it would be procedurally fair to fully consider the arguments on remand about whether the cited prior art teaches or suggests the limitations recited in the substitute claims. And, as discussed above, the Federal Circuit has directed the Board to consider obviousness. CAFC Dec. 10–11.” slip op. at 11

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not contest Petitioner’s proposed level of ordinary skill in the art. See PO Resp.; Sur-reply. Patent Owner’s expert, Dr. Shamos, and provides substantially the same expression of the level of ordinary skill in the art. Ex, 2003 ¶¶ 30–31; see FWD 6–7. In this Decision, we apply Petitioner’s proposed definition.” slip op. at 6

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied

    “In sum, Petitioner has shown that replacing Feldman’s radius with Badger’s zoom level meets all the limitations of the claim considered in the context of the Feldman-Jackson combination. Also, the evidence shows a motivation to modify the radius in Feldman’s search request to instead be based on the zoom-level parameter disclosed in Badger. See Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1380–81 (Fed. Cir. 2023) (“There is a motivation to combine when a known technique ‘has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way,’ . . . using the ‘prior art elements according to their established functions.’”) (citing KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 417 (2007)). substitute claim 21 is unpatentable over Feldman, Jackson, and knowledge of one of ordinary skill in the art. See Koninklijke Philips N.V. v. Google LLC, 948 F.3d 1330, 1337 (Fed. Cir. 2020) (“[U]nder 35 U.S.C. § 103, the obviousness inquiry turns not only on the prior art, but whether ‘the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious . . . to a person having ordinary skill in the art to which the claimed invention pertains.’”).” slip op. at 19

  • Strike new argumentNew argument consideredDecided for patent owner

    “precluded from considering additional arguments on the relevant issues on remand. The Board’s preliminary guidance on the Motion to Amend stated that Petitioner’s obviousness rationale was based on convenience and this reason was not sufficiently supported: reference lacks a sufficient explanation of why one of ordinary skill in the art would have added the zoom levels in the prior art to Feldman. See id. At most, Petitioner argues that it would be convenient to “specify the area the user desires to search for content” in this way. Id. at 14. But, on this record, Petitioner has not sufficiently explained why it would be convenient to do so in Feldman. See id. Nor has Petitioner sufficiently explained how or why the prior-art features confer this convenience. See id. MTA PG, 13. Because the Board’s conclusion turned on the lack of sufficient explanation, the briefing that followed was limited to Petitioner’s obviousness rationale. See, e.g., MTA Reply 9–12, MTA Sur-reply 1–12. Under these specific circumstances, we determine that it would be procedurally fair to fully consider the arguments on remand about whether the cited prior art teaches or suggests the limitations recited in the substitute claims. And, as discussed above, the Federal Circuit has directed the Board to consider obviousness. CAFC Dec. 10–11.” slip op. at 11

  Patent outcomesUS 10,616,727 unpatentable
  § 103 obviousnesscites KSR
  Patents in suitUS 10,616,727
• Western Digital Technologies, Inc. v. Godo Kaisha IP Bridge 1Some claims unpatentable
  PTAB · Apr 29, 2026 · IPR2024-01493 · APJ John D Hamann · IPR · Final written decision

  Claims 1, 3, 5, 7–11, 14, and 15 are unpatentable as obvious; claims 2, 4, 6, 12, and 13 were not shown unpatentable because the references did not establish entirely crystallized CoFeB layers.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In our Decision on Institution, we adopted the definition Petitioner proposes for one having ordinary skill in the art at the time of the invention of the ’167 patent. Dec. on Inst. 6. Namely, we found that one of ordinary skill in the art would have had “a Ph.D. in electrical engineering, physics, materials science, or a related field, and at least one year of experience in the research, design, and/or development of magnetic/spintronic devices, or the equivalent,” or “a Master’s degree in electrical engineering, physics, materials science, or a related field, and four years of experience in the research, design, and/or development of magnetic/spintronic devices, or the equivalent.” Id. (citing Pet. 20 (citing Ex. 1024 ¶ 25)). We also found that “[l]ess work experience may be compensated by a higher level of relevant education, and vice versa.” Id. Patent Owner does not address Petitioner’s definition, nor provide its own. See generally PO Resp. Because Petitioner’s definition of the level of skill in the art is consistent with the ’167 patent and the asserted prior art, we maintain it for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC, 57 F.3d at 1579; In re Oelrich, 579 F.2d 86, 91 (CCPA 1978).” slip op. at 7

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

    “Here, neither party sets forth any term for claim construction. Pet. 17; see generally PO Resp. Thus, for purposes of this Decision, we afford the claim terms their plain and ordinary meaning. See, e.g., Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”)).” slip op. at 8

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

    “In addition, we agree with Petitioner and find that one of ordinary skill in the art “would have been motivated to replace either or both of Bowen’s electrodes with CoFeB to increase TMR and lower Hf [(coupling field)] and Hc [(coercivity)].” Pet. 24, 27; Ex. 1055,30 2270 (“[I]t is natural to replace both the free and pinned layers to CoFeB to further increase the TMR value.”); Ex. 105631 ¶¶ 67–68 (“[B]oth the ferromagnetic layers 5, 7 are made of an FeCoB”32 for “improvement of the TMR ratio.”); Ex. 1024 ¶¶ 129, 132. We credit Dr. Bokor’s cited testimony as it is consistent with the cited evidence. Moreover, as Petitioner explains, “[r]esearchers were . . . interested in optimizing MTJs to improve MRAM performance,” and “[h]igher TMRs long promised improved performance for MRAM.” Pet. 6 30 Dexin Wang et al., 70% TMR at room temperature for SDT sandwich junctions with CoFeB as free and reference layers, 40 IEEE Trans. Magn. 2269–71 (July 2004). 31 US 2004/0136232 A1, published July 15, 2004, to Hosomi. 32 We find persuasive Dr. Bokor’s testimony that “a skilled artisan [would have] understood that CoFeB and FeCoB refer to the same alloy.” Ex. 1024 ¶ 121. 36–44) (emphasis omitted). In addition, we agree with Petitioner that one of ordinary skill in the art “would have found it obvious to use Parkin’s CoFeB layer in place of Bowen’s electrodes to increase TMR” in light of Parkin’s explicit teachings. Pet. 27; Ex. 1024 ¶ 133. In particular, Parkin explicitly teaches that “very high TMR values are unexpectedly found for MTJs with highly textured (100) MgO tunnel barriers but with nominally amorphous storage layers.” Ex. 1062, 18:49–51. Notably, Parkin provides that “[t]he TMR of the device of F[igure] 3A is nearly two times higher than the highest TMR ever reported in prior art devices using conventional alumina tunnel barriers.” Id. at 18:63–65; Pet. 27. And as we discuss above, Parkin teaches that Figure 3A’s MTJ may be inverted, such that the storage layer is formed beneath the tunnel barrier. Ex. 1062, 17:7–10. In addition, we agree that one of ordinary skill in the art would have had a reasonable expectation of success in modifying Bowen in the manner Petitioner proposes, as forming electrodes with CoFeB alloys was known. Pet. 28. As Petitioner argues, “forming electrodes with CoFeB alloys in MTJs was known and had been successfully done,” and thus we are persuaded that “one of skill would have found it to be a straightforward, predictable, and desirable improvement to TMR, Hf, and Hc in Bowen’s” slip op. at 21

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner

    “We find unavailing Patent Owner’s arguments that Bowen teaches a “radically different manufacturing process[] from the claimed invention,” and that Bowen “went to heroic lengths to provide a crystalline (001) bottom electrode that provides a template for epitaxially growing a crystalline MgO(001) layer.” PO Resp. 2 (emphasis omitted). Patent Owner describes in detail Bowen’s specific manufacturing process, including the specific structure of the MTJ manufactured, and argues the claimed invention differs. PO Resp. 30–33. These arguments are inapposite. Petitioner cites the specific teachings Petitioner relies on from Bowen, rather than adopting the entirety of Bowen’s process or MTJ. See, e.g., Pet. 21–36 (citing the portions of Bowen—that in combination with Parkin—teach claim 1). Petitioner is not “compelled to adopt every single aspect of [Bowen’s] teaching without the exercise of independent judgment.” Lear Siegler, Inc. v. Aeroquip Corp., 733 F.2d 881, 889 (Fed. Cir. 1984). We also find unavailing Patent Owner’s argument that Bowen and Parkin each teach away from Petitioner’s combination because Parkin used boron to avoid crystalline electrodes whereas Bowen tried to achieve perfect crystalline electrodes. PO Resp. 4. As we discuss above, one of ordinary skill in the art would have been motivated to replace Bowen’s electrodes with CoFeB to increase TMR. And Patent Owner does not identify in either reference a specific teaching that criticizes, discredits, or otherwise 35 M. Jimbo et al., Thermal stability of spin valves using amorphous CoFeB, 165 J. Magnetism & Magnetic Materials 308–11 (1997) (“Jimbo”). combination. In re Fulton, 391 F.3d 1195, 1201 (Fed. Cir. 2004).” slip op. at 23

  Patent outcomesUS 10,680,167 mixed
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,680,167
• Western Digital Technologies, Inc. v. Godo Kaisha IP Bridge 1No claims unpatentable
  PTAB · Apr 28, 2026 · IPR2024-01494 · APJ Justin T Arbes · IPR · Final written decision

  The Board found claims 5, 6, and 9–20 not shown unpatentable over either Bowen and Soukup or Nagahama and Soukup under § 103.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that at the time of the ’909 patent (2004), a person of ordinary skill in the art would have had “a Ph.D. in electrical engineering, physics, materials science, or a related field, and at least one year of experience in the research, design, and/or development of magnetic/spintronic devices, or the equivalent,” or “a Master’s degree in electrical engineering, physics, materials science, or a related field, and four years of experience in the research, design, and/or development of magnetic/spintronic devices, or the equivalent,” where “[l]ess work experience may be compensated by a higher level of relevant education, and vice versa.” Pet. 18–19. In the Decision on Institution, we agreed with and applied Petitioner’s proposed definition. Dec. on Inst. 9. Patent Owner does not propose a different level of ordinary skill in the art in its Response. Both experts utilized Petitioner’s proposed definition. See Ex. 1024 ¶ 25; Ex. 2053 ¶¶ 29–30. Based on the full record developed during trial, including our review of the ’909 patent and the types of problems and solutions described in the ’909 patent and cited prior art, we maintain the previously adopted definition of the level of ordinary skill in the art and apply it for purposes of this Decision.” slip op. at 8

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

    “B. Claim Interpretation We interpret the claims of the challenged patent using the same claim construction standard that would be used to construe the [claims] in a civil action under 35 U.S.C. 282(b), including construing the [claims] in accordance with the ordinary and customary meaning of such [claims] 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). Petitioner argues that “the claim terms should be given their plain and ordinary meaning and no claim construction is necessary.” Pet. 15. We did not interpret any terms in the Decision on Institution. Dec. on Inst. 9–10. Patent Owner does not propose interpretations of any claim terms in its Response. We conclude, based on the full trial record, that no term requires express interpretation to determine whether Petitioner has met its burden to prove unpatentability of the challenged claims. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe [a particular claim limitation] where the construction is not ‘material to the . . . dispute.’” (emphasis added) (citation omitted)).” slip op. at 8

  • Strike new argumentNew argument disregardedGranted in part

    “Pursuant to 37 C.F.R. § 42.23(b), “[a] reply may only respond to arguments raised in the corresponding . . . patent owner response.” “‘Respond,’ in the context of 37 C.F.R. § 42.23(b), does not mean proceed in a new direction with a new approach as compared to the positions taken in a prior filing.” Patent Trial and Appeal Board Trial Practice Guide § II.I, available at https://www.uspto.gov/patents/ptab/trial-practice-guide (last updated Dec. 12, 2025). “While replies . . . can help crystalize issues for decision, a reply . . . that raises a new issue or belatedly presents evidence may not be considered.” Id. An indication that a new issue is improperly raised in a reply is where a petitioner submits “new evidence necessary to make out a prima facie case” of unpatentability, such as a “newly raised rationale to combine the prior art references that was not expressed in the petition.” Id. That is the case here. Petitioner’s rationale in the Petition for why a person of ordinary skill in the art would have been motivated to lower Bowen’s 0.9 eV barrier height to 0.33 eV based on Soukup was that such an artisan would have expected lowering the barrier height to increase TMR. See Pet. 34–36. Faced with Dr. Bokor’s testimony on cross-examination, Petitioner presents a new theory in its Reply that a person of ordinary skill in the art would not have known what impact lowering the barrier height would have (increase TMR, decrease it, or have no impact at all), but would have expected it to change in some “uncertain” way, which is a “legally sufficient motivation” in Petitioner’s view. See Reply 6–10, 13–16, 23–25. In other words, “[r]ather than explaining how its original” position that lowering barrier height would increase TMR “was correct,” Petitioner articulated “an entirely new theory . . . absent from the [P]etition” after Patent Owner cross-examined Dr. Bokor and “pointed out the flaws of [Petitioner’s] position” in its Response. See Wasica Finance GmbH v. Continental Auto. Sys., Inc., 853 F.3d 1272, 1286 (Fed. Cir. 2017). “Shifting arguments in this fashion is foreclosed by statute, [Federal Circuit] precedent, and Board guidelines.” Id.” slip op. at 20

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Ultimately, the cross-examination testimony above is inconsistent with Dr. Bokor’s opinions in his declaration that, for example, “[i]t was understood to one of skill that lowering the barrier height to increase tunneling would have increased the TMR,” and “[o]ne of skill would have been motivated to adjust oxygen vacancy defects to improve TMR by lowering the barrier height.” See Ex. 1024 ¶¶ 176, 277 (emphasis added); see also id. ¶ 172 (“[O]ne of skill in the art would have been motivated to use [Soukup’s 0.33 eV] or similar height in an MgO MTJ to improve tunneling and hence TMR in Bowen.”). Accordingly, we do not find Dr. Bokor’s declaration testimony regarding a motivation to lower Bowen’s barrier height credible. It is Petitioner’s burden to provide a reasoned, evidence-supported explanation for why a person of ordinary skill in the art would have been motivated to lower Bowen’s 0.9 eV barrier height to 0.33 eV as disclosed in Soukup. See NuVasive, 842 F.3d at 1383; Magnum Oil, 829 F.3d at 1380; TriVascular, 812 F.3d at 1066. Petitioner’s reasoning in the Petition that lowering the barrier height (by introducing oxygen defects) would increase TMR is unsupported by evidence.” slip op. at 31

  Patent outcomesUS 11,968,909 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,968,909
• Western Digital Technologies, Inc. v. Godo Kaisha IP Bridge 1Some claims unpatentable
  PTAB · Mar 27, 2026 · IPR2024-01447 · APJ Sheila F Mcshane · IPR · Final written decision

  Claims 1–2 are unpatentable as obvious over each Bowen-based combination; claims 3–4 were not shown unpatentable, and the Nagahama-based grounds failed for all claims.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are 5 Nagahama, EP 1391942 A1, published February 25, 2004 (Ex. 1027, “Nagahama”). made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). Consistent with the Institution Decision (Dec. 7), we adopt the assessment offered by Petitioner as it is consistent with the ’134 patent and the asserted prior art. Patent Owner does not dispute that Dr. Bokor is qualified as a person of ordinary skill in the art in accordance with the assessment adopted. See Tr. 90:9–15. Patent Owner, however, questions Dr. Bokor’s knowledge on the formation of crystalline materials and seeks to exclude his related testimony. See PO Resp. 1–2, 27; PO Mot. Excl. 12–15. We address this issue infra Section V.” slip op. at 7

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

    “Petitioner “submits the claim terms should be given their plain and ordinary meaning and no claim construction is necessary to find the claims unpatentable.” Pet. 24. Patent Owner does not raise any claim construction issues in its Response. See generally PO Resp. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 9

  • Strike new argumentNew argument consideredDenied

    “A reply may only respond to arguments raised” in the patent owner response. 37 C.F.R § 42.23(b). The Consolidated Trial Practice Guide states that responding “does not mean proceed[ing] in a new direction with a new approach,” and “[w]hile replies . . . can help crystalize issues for decision, a reply . . . that raises a new issue or belatedly presents evidence may not be considered,” that is, “Petitioner may not submit new evidence or argument in reply that it could have presented earlier, e.g. to make out a prima facie case of unpatentability.” Consolidated Trial Practice Guide § II.I (last updated Dec. 12, 2025) (“CTPG”), available at https://www.uspto.gov/patents/ptab/trial-practice-guide. We are not persuaded by Patent Owner’s assertions that Petitioner’s reply arguments on Parkin should not be considered. As discussed supra Section II.D.3.i above, the Petition includes the assertion that if Parkin’s CoFeB electrodes were used to modify Bowen, the MgO polycrystalline or single-crystal layer would still have the same 001 orientation. Pet. 33–34 (citing Ex. 1024 ¶ 129; Ex. 1062, 9:58–10:2, 18:49–51; Ex. 1005, 4:30–32). Petitioner’s support in the Petition references disclosures relating to Parkin’s Figure 3A (Ex. 1062, 18:49–51), which discloses a MgO(100) tunnel barrier, and the Petition also notes that the structure of Figure 3A may be inverted. Pet. 40 (citing Ex. 1062, 17:7–10). Patent Owner’s arguments, in large part, are related to Petitioner’s arguments in the Reply relating to Parkin’s Figure 11. Parkin’s Figure 11 is an embodiment where the structure of the devices of Figure 3A is inverted. See Ex. 1062, 22:29–33. We do not find that Petitioner’s arguments that are at issue in the Reply represent a new direction in its approach—the Petition is clearly based on the assertion that if Parkin’s CoFeB electrodes are used in Bowen, the device would have a MgO(001) tunnel barrier layer. Further, the Petition refers to Parkin’s disclosure that the device in Figure 3A may be inverted, which would be encompassed by the Figure 11 embodiment. Moreover, in the Institution Decision, we invited additional briefing on whether Parkin’s storage magnetic electrode was an amorphous ferromagnetic electrode, which relates to Parkin’s Figure 11 (Dec. 28–29). We are also not persuaded by Patent Owner’s argument that the Petition’s assertions do not correspond to what Petitioner argues in the Reply because they were referred to in the section pertaining to limitation 1[e]. The Petition includes a cross-reference in the limitation 1[d] discussion on the tunnel barrier layer limitation: “if Sunai’s or Parkin’s CoFeB electrodes are used as described in Claims 1[e] and 2 in this Ground, one of skill would understand that the MgO . . . would still have the same (001) orientation.” Pet. 33. Further, Petitioner’s arguments in its Reply properly respond to arguments made on contested issues. Patent Owner’s contentions on the merits in its Response are largely based upon the assertion that the modified MTJ of Bowen would not have a MgO(001) layer as claimed. See PO Resp. 4–10, 18–48. Petitioner’s reply arguments on Parkin relate to whether there would be a MgO(001) layer in its structure, so we find that Petitioner’s arguments on Parkin in its Reply (Pet. Reply 2–5) and the related evidence are appropriately responsive. slip op. at 17

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

    “We find that there is sufficient evidence in support of Petitioner’s assertion of the rationale to replace Bowen’s electrodes with CoFeB and anneal them. As discussed supra Section II.D.ii.2, Parkin’s Figure 11 depicts and describes a storage electrode that may be composed of amorphous CoFeB, with the formation of a MgO(001) barrier layer atop it. See Ex. 1062, 22:29–66. Patent Owner argues that Parkin’s benefits are because its CoFeB electrode is amorphous (PO Resp. 51–52), but this is not accurate. In Parkin, the CoFeB amorphous electrode crystallized at the interface layer between the barrier and the electrode. Id. at 19:6–19. Parkin discloses that higher TMRs were attributable to the crystallization of CoFeB. Id. at 18:63–19:22. Parkin also discloses that its completed CoFeB- MgOH(001)-CoFeB device was annealed with resulting high TMRs. Id. at 17:60–18:16. These disclosures provide support that one of skill in the art would have been motivated to replace Bowen’s electrodes with CoFeB and anneal to crystallize them because of the known improvements of TMR. Additionally, Parkin’s disclosures support that the results of the combination would have been predictable. That is, Parkin actually discloses an amorphous CoFeB electrode, formation of a MgO(001) tunnel barrier on the amorphous electrode, and annealing the assembly, with a resulting high TMR. Accordingly, Petitioner has provided reasoning with rationale underpinning for the motivation to combine. See KSR, 550 U.S. at 415 (“[t]he combination of familiar elements according to known methods is likely to be obvious when it does no more than yield predictable results”).” slip op. at 31

  Patent outcomesUS 8,405,134 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,405,134
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Power2b, Inc.All claims unpatentable
  PTAB · Mar 13, 2026 · IPR2021-01266 · APJ John D Hamann · IPR · Remand

  On remand, the Board held claims 29, 36–38, 44–46, 48, 49, and 56–58 unpatentable as obvious over Reime, with additional grounds also supporting the challenged claims.

  RulingsRemand decision

  • ExcludeMotion to exclude, deniedDenied

    “In addition, Patent Owner filed a Motion to Exclude certain of Petitioner’s evidence (Paper 32) and Petitioner filed an Opposition (Paper 33). We denied this motion. See Final Dec. 58–61.” slip op. at 3

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

    “transmission paths. See Pet. Reply 14–15; PO Sur-reply 15. And we agree with both parties that the light that is transmitted directly through the plate to the sensor element does not have intervening reflections—such is consistent with the plain and ordinary meaning of “directly to.” See PO Resp. 31–32; Pet. Reply 14–15; PO Sur-reply 15. Nothing in claim 48’s language, however, requires that all of the reflected light be transmitted directly to the sensor element, which Patent Owner argues. Ex. 1001, 70:32–35; PO Resp. 31–32; PO Sur-reply 14–16. Rather, we agree with Petitioner that the claim language “merely requires that some light reflected by the object goes ‘directly to’ at least one sensor element once it is transmitted through the viewing plane defining plate.” Pet. Reply 14. We also agree that “none of these dependent claims purport to be exclusive of one another.” Id. at 15. Rather, claims 46–48 simply require some light be transmitted (or propagated) for their particular transmission path, without reciting all light. See Ex. 1001, 70:24–35.” slip op. at 13

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

    “We find Petitioner’s arguments based on Reime alone insufficient. Thus, we find that Petitioner does not show by a preponderance of the evidence that claim 49 is rendered obvious by Reime alone.” slip op. at 52

  • Obviousness (§103) › KSR rationalesUnpatentableUnpatentable

    “And in view of the above, we find persuasive Dr. Bederson’s testimony that “[c]hoosing a multi-element detector or a single-element detector would have been a simple design choice using commercially available detectors.” Ex. 1002 ¶ 117. Accordingly, we find that one of ordinary skill in the art would have found it obvious for Reime’s receivers to be implemented using discrete single-element detectors. See KSR, 550 U.S. at 417 (“When there is a design need or market pressure to solve a problem and there are a finite number of identified, predictable solutions, a person of ordinary skill has good reason to pursue the known options within his or her technical grasp. If this leads to the anticipated success, it is likely the product not of innovation but of ordinary skill and common sense.”). We find unavailing Patent Owner’s argument that “Petitioner relies on expert testimony to gap-fill missing elements regarding Reime’s failure to disclose or suggest the different claim arrangements of detector elements in a ‘detector assembly.’” PO Resp. 78 (citing Ex. 1002 ¶¶ 111–119; Ex. 2056 ¶ 171). Rather, in light of Reime’s teachings, coupled with the general knowledge of one of ordinary skill in the art, it would have been obvious to employ discrete single-element detectors for Reime’s receivers. See Koninklijke Philips N.V. v. Google LLC, 948 F.3d 1330, 1338 (Fed. Cir. 2020) (finding obviousness can rely on supported expert testimony to supply an element of a claim). We appropriately consider such evidence of the knowledge that one of ordinary skill in the art would have had as part of our obviousness analysis. See Randall Mfg. v. Rea, 733 F.3d 1355, 1362–63 (Fed. Cir. 2013). Moreover, “AAPA can be important evidence of general background knowledge, and general knowledge can be used to supply a missing claim 1371, 1378–79 (Fed. Cir. 2025). Here, Petitioner relies on the cited AAPA as evidence of one of ordinary skill in the art’s general knowledge at the time of the ’093 patent, and the AAPA is not the basis for this ground. See Pet. 4, 42–43; Pet. Remand 4–5. As Shockwave Med. explains, Federal Circuit “case law has long recognized numerous permissible uses for general background knowledge in an IPR such as, ‘for example, furnishing a motivation to combine, or supplying a missing claim limitation.” 142 F.4th at 1378–79 (quoting Qualcomm Inc. v. Apple Inc., 24 F.4th 1367, 1376 (Fed. Cir. 2022) (citing Randall Mfg., 733 F.3d at 1362; Koninklijke, 948 F.3d at 1337–38)).” slip op. at 31

  Patent outcomesUS 9,569,093 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 9,569,093

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.