- Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 7,370,035 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - Google LLC v. Escapex IP LLCAll claims unpatentablePTAB · Mar 30, 2026 · IPR2025-00337 · APJ Justin T Arbes · IPR · Final written decision
Claims 1–24 are unpatentable under § 103: claims 1–3, 5–6, 13–15, 17–18 over Fuloria and Andler; the remaining claims over combinations adding WO ’100, Bartholomew, Kirk, or Cheung.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“a person of ordinary skill in the art would have had “a bachelor’s degree in computer science or a similar field and three years of professional computer programming experience, including experience with networked media and databases, where additional education can substitute for experience or vice versa.” Pet. 20 (citing Ex. 1002 ¶¶ 27–31). In the Decision on Institution, Inst. 7–8. Patent Owner adopts Petitioner’s proposed definition “because it comports with the technology and claims of the ’687 [p]atent as well as the asserted prior art.” PO Resp. 4; Tr. 36:4–18. Based on the full record developed during trial, including our review of the ’687 patent and the types of problems and solutions described in the ’687 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 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner
“37 C.F.R. § 42.100(b). Petitioner argues that the term “engagement” in independent claims 1, 11–13, 23, and 24 is defined in the Specification of the ’687 patent and should be interpreted to mean “an indication that a user should be distinguished with respect to the content over another user.” Pet. 11 (citing Ex. 1001, col. 5, ll. 53–55; Ex. 1002 ¶ 41). Patent Owner agrees that the Specification “defines” the term in that manner. PO Resp. 13. The Board did not interpret any terms in the Decision on Institution. Dec. on Inst. 9. We agree with the parties’ proposed interpretation of “engagement” and apply it for purposes of this Decision, based on the Specification’s disclosure that “[a] user engagement with content refers to an indication that a user should be distinguished with” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“No other terms require 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 11
- Expert testimonyPetitioner expert creditedDecided for petitioner
Patent outcomesUS 10,474,687 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,474,687 - Digital Global Systems, Inc. v. Deepsig, Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnessPatents in suitUS 11,018,704 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentablePTAB · Jan 23, 2026 · IPR2024-01192 · APJ Michael J Strauss · IPR · Final written decision
Claims 1–10 and 16 are unpatentable as obvious over the asserted combinations of the Lorex Manual or Lorex Video with the identified references.
RulingsFinal written decision- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for petitioner
“Patent Owner does not dispute any of Petitioner’s contentions as to the effective filing date, stating in agreement with Petitioner’s asserted Effective Filing Date of the Challenged Claims that “[t]he ’916 Patent claims a priority of a provisional application 61/924,240 filed on January 7, 2014.” PO Resp. 8. Given that the parties are in agreement on the January 7, 2014, effective filing date, we similarly use January 7, 2014, as the effective filing date of the challenged claims for purposes of this Decision.” slip op. at 4
- Skill levelSkill level petitioner adoptedDecided for petitioner
“II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Vlad Kardashov, Petitioner proposes that a person of ordinary skill in the art at the time of the invention of the ’916 patent “would have had a bachelor’s degree in electrical engineering and two 7 US 2012/0198040 A1, published August 2, 2012 (Ex. 1011, “Kuo”). 8 The subject ’916 patent claims priority to Kuo as a continuation-in-part of that earlier filed application. Ex. 1001, code (63). 9 Lorex Technology Inc., “How to set up remote access for DVR using - Lorex Stratus Connectivity” (June 18, 2013), available at https://www. youtube.com/watch?v=fMPRi9WFuTM (Ex. 1012, the “Lorex Video”). 10 US 2012/0113265 A1, published May 10, 2012 (Ex. 1013, “Galvin”). years of work experience with network and communication technologies.” Pet. 8 (citing Ex. 1003 ¶¶ 12–14). Patent Owner does not contest Petitioner’s proposal or provide a proposal of its own. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is consistent with the technology described in the ’916 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner asserts that “no claim elements need a formal construction for purposes of resolving controversies in this proceeding.” Pet. 9 (citing Ex. 1003 ¶¶ 43–44; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011), Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. § 42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. 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
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artPriority date awardedDecided for petitioner
“that Patent Owner fails to demonstrate that the Lorex Manual was based on a disclosure made by the inventor or joint inventor or by another who obtained the subject matter disclosed directly or indirectly from the inventor or a joint inventor. The Lorex Manual is relied on under Ground 1A, exclusively or in the alternative to or in combination with Kim, for all claim elements. Pet. 9– 31. Patent Owner fails to demonstrate that this subject matter was disclosed to Lorex by ThroughTek, much less by one of the inventors of the ’916 Patent.” slip op. at 22
Patent outcomesUS 9,774,916 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,774,916 - PTAB · Jan 14, 2026 · IPR2025-01191 · APJ Kara L Szpondowski · IPR · Institution
The Board instituted IPR on claims 1–24 and all asserted grounds because the petition showed a reasonable likelihood of prevailing on at least one claim.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Institution of an inter partes review is authorized when “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Based on the current record, and for the reasons explained below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one challenged claim, and we institute an inter partes review.” slip op. at 2
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsNot reached
“IV. PATENT OWNER’S 35 U.S.C. § 325(D) ARGUMENTS Patent Owner presents arguments directed to discretionary considerations under 35 U.S.C. § 325(d) and requests the Petition be denied based on these arguments. Prelim. Resp. 2–16. However, Patent Owner’s § 325(d) arguments are untimely under the “Interim Director Discretionary Process,”6 and, as such, will not be considered by the Board. See Section I.C. (“The . . . patent owner should not present discretionary considerations in the . . . Patent Owner Preliminary Response (POPR)”); Section I.E. (“[A] Board panel will issue a decision on institution addressing the merits and other non-discretionary considerations.”). 5 Available at https://www.uspto.gov/patents/ptab/trial-practice-guide#step1 6 https://www.uspto.gov/patents/ptab/interim-director-discretionary-process.” slip op. at 38
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“Petitioner bears the burden of establishing that Wang is a printed publication. Medtronic, 891 F.3d at 1380. The determination of whether a document is a “printed publication” “involves a case-by-case inquiry into the facts and circumstances surrounding the reference's disclosure to members of the public.” In re Klopfenstein, 380 F.3d 1345, 1350 (Fed. Cir. 2004). “[A]t the institution stage, the petition must identify, with particularity, evidence sufficient to establish a reasonable likelihood that the reference was publicly accessible before the critical date of the challenged patent and therefore that there is a reasonable likelihood that it qualifies as a printed publication.” Hulu, IPR2018-01039, Paper 29 at 13.” slip op. at 19
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“A claim is unpatentable as anticipated under 35 U.S.C. § 102 “if each and every limitation is found either expressly or inherently in a single prior art reference.” WhitServe, LLC v. Computer Packages, Inc., 694 F.3d 10, 21 (Fed. Cir. 2012) (quoting Celeritas Techs., Ltd. v. Rockwell Int’l Corp., 150 F.3d 1354, 1361 (Fed. Cir. 1998)). An anticipatory reference must also “disclose those elements ‘arranged as in the claim.’” Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008) (quoting Connell v. Sears, Roebuck & Co., 722 F.2d 1542, 1548 (Fed. Cir. 1983)).” slip op. at 11
Claim construction§ 102 anticipation§ 103 obviousnessDiscretionary denialcites KSR · GrahamPatents in suitUS 10,822,165 - PTAB · Dec 18, 2025 · IPR2025-01071 · APJ Benjamin D M Wood · IPR · Institution
The Board instituted IPR of claims 1–7, 12, 14, and 25 because Petitioner showed a reasonable likelihood of prevailing on its § 103 obviousness challenge over Bassompiere.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We have authority under 35 U.S.C. § 314, which provides that an inter partes review may not be instituted “unless . . . there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). On the preliminary record before us, we determine that Petitioner has satisfied this threshold requirement, and therefore we institute inter partes review of claims 1–7, 12, 14, and 25 of the ’687 patent.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not offer any reason why we should deviate from the Board’s determinations in the prior IPRs that one of ordinary skill in the art would have had knowledge of Kalman filters and quaternion mathematics. Nor are we aware of any such reason. On the contrary, the Board’s prior determinations are consistent with the level of ordinary skill reflected by prior art of record. 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). Bassompiere, for example, teaches using a data merging algorithm that is, “[a]dvantageously,” extended Kalman filtering. Ex. 1006, 4:17. Bassompiere also teaches using quaternions to determine a device’s pitch and roll about a horizontal reference frame. Id. at 6:3–8, 20:10–21:1. Patent Owner argues that Dr. Sarrafzadeh’s testimony regarding the level of skill in the art in this proceeding contradicts his testimony in the prior IPRs, which did not include knowledge of Kalman filters and quaternion mathematics in his definition of the level of ordinary skill in the art. Prelim. Resp. 24–26. Patent Owner asserts that this contradiction “undermin[es] his credibility.” Id. at 26. We disagree. The testimony Dr. Sarrafzadeh provided in the earlier IPRs obviously preceded the Board’s determinations in those proceedings that, on the whole record, including the testimony of then-Patent Owner’s declarant, the level of ordinary skill included knowledge of Kalman Filters and quaternions. Dr. Sarrafzadeh’s testimony in this proceeding reasonably aligns with those determinations. Accordingly, we adopt Petitioner’s definition of the level of ordinary skill in the art for purposes of this Decision.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“The parties agree that the claimed “spatial reference frame” is associated with a device, has its origin at the same point in the device, and has axes that are always fixed with respect to the device. The only disagreement is whether that device is a “3D pointing device” or an “electronic device.” The Specification indicates that “electronic device” encompasses 3D pointing devices as well as, e.g., smartphones and navigation equipment, and therefore is the broader term. Ex. 1001, 13:20– 23. At this stage of the proceeding, we determine that the threshold question of institution can be decided under either construction, because Patent Owner does not dispute that the primary asserted reference, Bassompiere, teaches a “spatial reference frame” associated with a 3D pointing device. Pet. 25–27. Therefore, at this stage of the proceeding, we decline to resolve the parties’ dispute. See Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those [claim] terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”); Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (approving Board decision not to construe claim language where the construction is not material to the dispute). 2. “predicted axial accelerations” Petitioner does not propose a construction for “predicted axial accelerations,” but, in the concurrent California Litigation, contends that it should be accorded its “plain and ordinary meaning.” Ex. 2007, 3. In subsequent briefing that will be discussed more fully below, Petitioner asserts that its declarant, Dr. Sarrafzadeh, “applied the ‘plain and ordinary’ meaning for all claim terms, including the ‘predicted axial accelerations’ term,” in this proceeding. Paper 14, 1. Petitioner also submits in that briefing that “the term ‘axial acceleration’ (whether predicted or measured) . . . ordinarily encompasses three types of acceleration,” i.e., “linear, centrifugal, and gravitational.” Id. at 3, 4. Patent Owner contends that “predicted axial accelerations” should be construed as “[g]ravitational acceleration along the electronic device’s axes derived from the current quaternion.” Prelim. Resp. 18. Patent Owner asserts that “[t]he claims and specification consistently define ‘predicted axial accelerations’ as gravitational accelerations along the device’s axes at time T, derived from the current quaternion.” Id. (citing Ex. 1001, claim 1, 17:18–30, 17:45–52). Patent Owner further submits that “because ‘predicted axial accelerations’ are computed from the current quaternion they only contain gravitational accelerations along the device’s axes.” Id. at 19 (citing Ex. 2023 ¶ 23). Here too, the threshold question of institution can be decided without” slip op. at 14
- BurdenDecided for petitioner
“We disagree with Patent Owner’s characterization. The teaching to use quaternions instead of Euler angles comes from Bassompiere, not Dr. Sarrafzadeh. See Ex. 1006, 20:10–11 (“A first variant embodiment consists in replacing the angles of torsion θ and ψ by a quaternion formulation of the same torsion.”). Rather than supplying a missing limitation, we understand Dr. Sarrafzadeh to be explaining how a person of ordinary skill in the art would have implemented Bassompiere’s teaching to use quaternions instead of Euler angles given that person’s knowledge of quaternion mathematics. Patent Owner also argues that “switching from Euler angles to quaternions is not a routine substitution but requires the reengineering of the EKF.” Prelim. Resp. 28. Patent Owner similarly contends that Dr. Sarrafzadeh “devotes nearly twenty pages of his declaration to rewriting Bassompiere’s Euler-based equations ‘in quaternion form,’ and explaining how to convert them back to Euler angles,” and notes that “[a]s other researchers in the field have confirmed, ‘[w]hile implementing orientation tracking using quaternions provides advantages like avoiding gimbal lock, it is significantly more complex than the Kalman filer using Euler angles.’” Prelim. Resp. 32 (citing Ex. 1002, 31–51; quoting Ex. 2027, 1). Patent Owner thus contends that replacing Euler angles with quaternions “is not a ‘trivial’ substitution.” Id. at 32. But Petitioner does not appear to be arguing that replacing Euler angles with quaternions would have been “trivial” or simple, only that doing so was taught by Bassompiere and within the knowledge and capabilities of a person of ordinary skill in the art. Pet. 33–34. We determined above that a skilled artisan had knowledge of extended Kalman filters and quaternion mathematics, and we are required to consider the knowledge and capabilities of a person of ordinary skill in our analysis. Further, at this preliminary stage, Patent Owner’s assertion that the Euler angle/quaternion switch would not have been a routine substitution is supported only with attorney argument, which is entitled to no weight. Icon Health & Fitness, Inc. v. Strava, Inc. 849 F.3d 1034, 1043 (Fed. Cir. 2017). As such, it does not outweigh Dr. Sarrafzadeh’s contrary testimony. See, e.g., Ex. 1002 ¶ 56.” slip op. at 29
Claim constructioncites Phillips · KSR · GrahamPatents in suitUS 11,698,687 - PTAB · Dec 17, 2025 · IPR2025-01023 · APJ Benjamin D M Wood · IPR · Institution
The Board instituted IPR on all asserted grounds against claims 1, 3, 7, and 9, finding a reasonable likelihood that Petitioner would prevail on at least one challenged claim.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“c. Conclusion as to Claim 1 Having reviewed the record and the parties’ arguments, we determine that Petitioner has a reasonable likelihood of prevailing with respect to claim 1, and therefore has satisfied the threshold requirement for institution of inter partes review on the basis of Ground 1. 3. Claims 3, 7, and 9 Petitioner contends that Bassompiere teaches the limitations of claim 3, 7, and 9, and supports its contentions with citations to Bassompiere and to Dr. Sharrafzadeh’s declaration. Pet. 57–63. At this stage of the proceeding, Patent Owner does not raise any arguments specifically directed to these claims. “When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.” 37 C.F.R. § 42.108(a). We must “either (1) institute as to all claims challenged in the petition and on all grounds in the petition, or (2) institute on no claims and deny institution.” CTPG at 5–6, 64; see also PGS Geophysical AS v. Iancu, 891 F.3d 1354, 1359–60 (Fed. Cir. 2018) (stating a decision to institute is “a simple yes-orno institution choice respecting a petition, embracing all challenges included in the petition”). Thus, because we have decided to grant institution on Ground 1 with respect to claim 1, we must do the same for claims 3, 7, and 9.” slip op. at 38
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not offer any reason why we should deviate from the Board’s determinations in the prior IPRs that one of ordinary skill in the art would have had knowledge of Kalman filters and quaternion mathematics. Nor are we aware of any such reason. On the contrary, the Board’s prior determinations are consistent with the level of ordinary skill reflected by prior art of record. 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). Bassompiere, for example, teaches using a data merging algorithm that is, “[a]dvantageously,” extended Kalman filtering. Ex. 1006, 4:17. Bassompiere also teaches using quaternions to determine a device’s pitch and roll about a horizontal reference frame. Id. at 6:3–8, 20:10–21:1. Nasiri teaches that quaternions can be used to represent a device’s “orientation in space.” Ex. 1008, 30:27– 30. Patent Owner argues that Dr. Sarrafzadeh’s testimony regarding the level of skill in the art in this proceeding contradicts his testimony in the prior IPRs, which did not include knowledge of Kalman filters and quaternion mathematics in his definition of the level of ordinary skill in the art. Prelim. Resp. 24–26. Patent Owner asserts that this contradiction “undermin[es] his credibility.” Id. at 26. We disagree. The testimony Dr. Sarrafzadeh provided in the earlier IPRs obviously preceded the Board’s determinations in those proceedings that, on the whole record, including the testimony of then-Patent Owner’s declarant, the level of ordinary skill included knowledge of Kalman Filters and quaternions. Dr. Sarrafzadeh’s testimony in this proceeding reasonably aligns with those determinations. Accordingly, for the above reasons, we adopt Petitioner’s definition of the level of ordinary skill in the art for purposes of this Decision.” slip op. at 13
- Expert testimonyPetitioner expert creditedDecided for petitioner
“We disagree with Patent Owner’s characterization. The teaching to use quaternions instead of Euler angles comes from Bassompiere, not Dr. Sarrafzadeh. See Ex. 1006, 20:10–11 (“A first variant embodiment consists in replacing the angles of torsion θ and ψ by a quaternion formulation of the same torsion.”). Rather than supplying a missing limitation, we understand Dr. Sarrafzadeh to be explaining how a person of ordinary skill in the art would have implemented Bassompiere’s teaching to use quaternions instead of Euler angles given that person’s knowledge of quaternion mathematics. Patent Owner also argues that “switching from Euler angles to quaternions is not a routine substitution but requires the reengineering of the EKF.” Prelim. Resp. 28. Patent Owner similarly contends that Dr. Sarrafzadeh “devotes nearly twenty pages of his declaration to rewriting Bassompiere’s Euler-based equations ‘in quaternion form,’ and explaining how to convert them back to Euler angles,” and notes that “[a]s other researchers in the field have confirmed, ‘[w]hile implementing orientation tracking using quaternions provides advantages like avoiding gimbal lock, it is significantly more complex than the Kalman filer using Euler angles.’” Prelim. Resp. 32–33 (citing Ex. 1002, 31–51; quoting Ex. 2027, 1). Patent Owner thus contends that replacing Euler angles with quaternions “is not a ‘trivial’ substitution.” Id. at 33. But Petitioner does not appear to be arguing that replacing Euler angles with quaternions would have been “trivial” or simple, only that doing so was taught by Bassompiere and within the knowledge and capabilities of a person of ordinary skill in the art. We determined above that a skilled artisan had knowledge of extended Kalman filters and quaternion mathematics such knowledge, and we are required to consider the knowledge and capabilities of a person of ordinary skill in our analysis. Further, at this preliminary stage, Patent Owner’s assertion that the Euler angle/quaternion switch would not have been a routine substitution is supported only with attorney argument, which is entitled to no weight. Icon Health & Fitness, Inc. v. Strava, Inc. 849 F.3d 1034, 1043 (Fed. Cir. 2017). As such, it does not outweigh Dr. Sarrafzadeh’s contrary testimony. See, e.g., Ex. 1002 ¶ 56.” slip op. at 30
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“The parties agree that the claimed “spatial reference frame” is associated with a device, has its origin at the same point in the device, and has axes that are always fixed with respect to the device. The only disagreement is whether that device is a “3D pointing device” or an “electronic device.” The Specification indicates that “electronic device” encompasses 3D pointing devices as well as, e.g., smartphones and navigation equipment, and therefore is the broader term. Ex. 1001, 8:35–39. At this stage of the proceeding, we determine that the threshold question of institution can be decided under either construction, because Patent Owner does not dispute that the primary asserted reference, Bassompiere, teaches a “spatial reference frame” associated with a 3D pointing device. Pet. 30–31. Therefore, at this stage of the proceeding, we decline to resolve the parties’ dispute. See Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those [claim] terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”); Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (approving Board decision not to construe claim language where the construction is not material to the dispute).” slip op. at 15
Claim construction§ 103 obviousnessDiscretionary denialcites Phillips · KSR · GrahamPatents in suitUS 10,852,846 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Technology (Shenzhen) Co., Ltd. And Throughtek Co., Ltd.All claims unpatentablePTAB · Dec 15, 2025 · IPR2024-01193 · APJ David C Mckone · IPR · Final written decision
Claims 1–3, 5, 7–13, 15–19, and 23–25 are unpatentable: claims 1, 7, 8, 10, 11, 15, 16, 18, 19, and 23–25 as anticipated by Zhang; all challenged claims also as obvious over at least one …
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“person of ordinary skill in the art “would have had a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies.” Pet. 5 (citing Ex. 1003 ¶¶ 13–15). Patent Owner does not contest Petitioner’s proposal or provide a proposal of its own. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is consistent with the technology described in the ’448 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededTerm construed board ownMixed
“construction of “feature flag” is inconsistent with the language of claim 8, which states that “the feature flag indicates that the running state of the second apparatus is the sleep state.” Petitioner also argues that Patent Owner’s proposal is not supported by claim 24, which depends from claim 23 and states that “the feature flag is located at a header of the sleep login packet.” Id. at 3. We agree with Petitioner. The plain language of claim 8 states what a feature flag indicates. Claim 24 recites where the feature flag is located. Neither claim suggests any of Patent Owner’s additional limitations.” slip op. at 13
- Expert testimonyPetitioner expert creditedDecided for petitioner
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“[A] prior art reference will anticipate if it ‘disclose[s] each and every element of the claimed invention . . . arranged or combined in the same way as in the claim.’” Blue Calypso, LLC v. Groupon, Inc., 815 F.3d 1331, 1341 (Fed. Cir. 2016) (quoting In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009) (alteration by Federal Circuit)). “However, a reference can anticipate a claim even if it ‘d[oes] not expressly spell out’ all the limitations arranged or combined as in the claim, if a person of skill in the art, reading the reference, would ‘at once envisage’ the claimed arrangement or combination.” Id. (quoting Kennametal, Inc. v. Ingersoll Cutting Tool Co., 780 F.3d 1376, 1381 (Fed. Cir. 2015) (alteration by Federal Circuit); In re Petering, 301 F.2d 676, 681 (CCPA 1962)). For the reasons explained below, we are persuaded that Petitioner has shown, by a preponderance of the evidence, that claims 1, 7, 8, 10, 11, 15, 16, 18, 19, and 23–25 are anticipated by Zhang. slip op. at 16
Patent outcomesUS 10,602,448 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 10,602,448
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.