• Crowdstrike, Inc. v. Gosecure, Inc.Some claims unpatentable
  PTAB · Aug 12, 2026 · IPR2025-00070 · APJ Neil T Powell · IPR · Final written decision

  Claims 1, 3–7, and 9–21 are unpatentable as obvious; claims 2 and 8 were not shown unpatentable because the asserted art did not meet their construed limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “III. ANALYSIS LEVEL OF ORDINARY SKILL A. Petitioner explains the applicable level of skill in the art as follows: As of June 24, 2010, a person of ordinary skill in the art (POSITA) would be a person having a bachelor’s degree in computer science, computer engineering, or an equivalent, as well as two years of industry experience and who would have had a working knowledge of software security analysis, and dynamic malware analysis. Additional graduate education could substitute for professional experience, or significant experience in the field could substitute for formal education. Pet. 8 (Ex. 1003 ¶¶ 30–31). Patent Owner does not dispute Petitioner’s explanation of the level of skill in the art. See Ex. 2031 ¶¶ 15–16. We adopt Petitioner’s uncontested proposed level of ordinary skill in the art, which we find consistent with the level of ordinary skill in the art reflected by the ’872 patent and the prior art of record. See Okajima v.” slip op. at 12

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

    “We begin with the claim language in view of the Specification, which weighs heavily against Patent Owner’s position that we should rewrite “computer system” as narrowly referring to a “computing device.” PO Resp. 24. As Petitioner notes, the ’872 patent’s Specification uses “computer system” to refer to a wide range of equipment, from a component of a computing device, to a whole computing device, to a collection of computing devices. Reply 9–10 (citing Ex. 1001, 4:5–8, 11:15–18, 16:50–55). In one example, the Specification refers to “one or more other computer systems (e.g., protected network devices 136).” Ex. 1001, 18:52–53. Thus, the Specification lists “protected network devices 136” as only an example of “other computer systems,” demonstrating that “computer systems” refers to things other than protected network devices. Although Patent Owner may be correct that this passage more than a single computing device,” we find that other disclosures in the ’872 patent do. Specifically, the Specification uses the language “distributed computer system” when referring to numerous components, including “protected network devices” and an “IDS/IPS system.” Ex. 1001, 3:26–28; Reply 10. In addition to showing that a “computer system” is not limited to a single computing device, this conveys that a “computer system” according to the ’872 patent can include an IDS/IPS.” slip op. at 14

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

    “Based on our review of the complete record, we find Petitioner’s arguments and evidence to be more persuasive. Patent Owner does not dispute Petitioner’s argument and evidence that capturing detailed information like Goel’s activity sources, activity targets, and association was recognized as enhancing threat analysis. Pet. 44 (citing Ex. 1003 ¶ 79); see PO Resp. 55–59; Sur-Reply 15–17. Additionally, contrary to Patent Owner’s suggestion, we find that the Petition does not propose incorporating Goel’s kernel hooks into Capalik’s system. See Pet. 41–46. Patent Owner contends that the Petition’s reference to modifying Capalik by “adding lines of code” suggests implementing the code disclosed in Goel include kernel hooks. Id. Notwithstanding Patent Owner’s assertion otherwise, this is an unpersuasive bodily incorporation argument, as the Petition never says an ordinarily skilled artisan would have used the exact lines of code from Goel in Capalik. Rather, the Petition says that an ordinarily skilled artisan would have had sufficient skill to implement straightforward code modifications to identify activity sources, targets, and associations: a [person of ordinary skill in the art] would have understood that modifying Capalik’s system (e.g., Linux-based) to additionally monitor, identify, and store each individual activity of an attack including “activity sources, activity targets, and associations” would have required straightforward modifications to programs/code instructions, which would have been well-within the skillset of a [person of ordinary skill in the art]. Pet. 46. Patent Owner argues that Petitioner does not explain how an ordinarily skilled artisan would have modified Capalik without using kernel hooks. Sur-Reply 17. But Patent Owner does not cite any evidence to counter Dr. Jakobsson’s testimony that an ordinarily skilled artisan would have had the skill to apply Goel’s general teaching of identifying sources, targets, and associations to Capalik’s system. Ex. 1003 ¶ 182. On the whole, the evidence does not support Patent Owner’s position that the combination would have required substantially increased detection risk. Moreover, even if the combination would have somewhat increased detection risk, Petitioner persuades us that an ordinarily skilled artisan still would have had reason to combine the references teachings. Patent Owner’s allegations of increased detection risk do not negate the undisputed evidence that the combination would have provided the advantage of improved threat analysis. Pet. 44 (citing Ex. 1003 ¶¶ 175–182). Ultimately, Patent Owner’s that activity logging be undetectable.” PO Resp. 56 (emphasis added) (citing Ex. 1004 ¶ 6). This exaggerates Capalik’s disclosure. Although the cited paragraph suggests that certain systems unfortunately may be detectable by some users, it does not convey that it is a requirement for the system to be categorically undetectable. See Ex. 1004 ¶ 6.8 In sum, Petitioner persuades us by a preponderance of the evidence that it would have been obvious to modify Capalik “to identify and store unauthorized activities including the activity source, activity target, and association of each activity.” Pet. 41–46; PO Resp. 55–59; Reply 20–22; Sur-Reply 15–17.” slip op. at 47

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for patent owner

    “arguments and evidence, we determine that Patent Owner fails to sufficiently show a nexus between any of its objective indicia evidence and the claimed invention. See Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (“The patentee bears the burden of showing that a nexus exists”). A showing of sufficient nexus is required to establish that the evidence relied upon traces its basis to a novel element in the claim, not to something in the prior art. Institut Pasteur & Universite Pierre Et Marie Curie v. Focarino, 738 F.3d 1337, 1347 (Fed. Cir. 2013). Objective evidence that results from something that is not “both claimed and novel in the claim” lacks a nexus to the merits of the invention. In re Kao, 639 F.3d 1057, 1068 (Fed. Cir. 2011) (emphasis omitted). Thus, establishing nexus involves a showing that novel elements in the claim, not prior-art elements, account for the objective evidence of nonobviousness. Id. As discussed above, Petitioner shows that Capalik teaches all limitations of claim 1. Petitioner persuades us that none of claim 1’s elements individually nor any combination thereof is novel over Capalik’s disclosure. Accordingly, claim 1 is not novel over Capalik, which disproves Patent Owner’s assertion of nexus. PO Resp. 73–76. Moreover, even if claim 1 were novel, Patent Owner otherwise fails to show nexus for its commercial success, praise, or copying assertions. Patent Owner’s evidence does not show that Petitioner’s commercial product embodies claim 1. For example, we agree with Petitioner that Patent Owner “failed to analyze any meaningful detail regarding” how the Falcon Platform allegedly meets limitation 1(d). Reply 28–29. In particular, Patent Owner has not sufficiently addressed limitation 1(d) with the following argument: “1[D] The Falcon Platform transmitted to other computer systems” slip op. at 37

  Patent outcomesUS 9,954,872 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 9,954,872
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

  Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms … that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). D.” slip op. at 12

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

    “search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24

  Patent outcomesUS 7,370,035 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,370,035
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9

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

    “In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23

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

    “different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27

  Patent outcomesUS 10,552,490 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 10,552,490
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

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

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

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

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Digital Global Systems, Inc. v. Deepsig, Inc.Some claims unpatentable
  PTAB · Mar 6, 2026 · IPR2024-01358 · APJ William V Saindon · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

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

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

  • BurdenNot shown unpatentable

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

  Patent outcomesUS 11,018,704 mixed
  Claim construction§ 103 obviousness
  Patents in suitUS 11,018,704
• Cisco Systems, Inc. v. Lionra Technologies LimitedAll claims unpatentable
  PTAB · Mar 4, 2026 · IPR2024-01281 · APJ Steven M Amundson · IPR · Final written decision

  Claims 1–3, 5–10, 12–15, and 17–21 are unpatentable as obvious over Cornett, Paatela, and Nelson; claim 8 is also unpatentable with Russell.

  RulingsFinal written decision

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

    “been motivated to combine the teachings of Cornett, Paatela, Nelson, and Russell in the way Petitioner proposes and would have had a reasonable expectation of success. See supra §§ III.E.2(a)–(b). Hence, Petitioner has shown by a preponderance of the evidence that claim 8 is unpatentable under § 103(a) because the claim would have been obvious over Cornett, Paatela, Nelson, and Russell.” slip op. at 122

  • Skill levelOther

    “B. Level of Ordinary Skill in the Art Factors pertinent to determining the level of ordinary skill in the art” slip op. at 13

  Patent outcomesUS 7,738,471 unpatentable
  § 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,738,471
• Apple Inc. v. S.M.R Innovations Ltd And Y.M.R Tech LtdAll claims unpatentable
  PTAB · Jan 27, 2026 · IPR2024-01048 · APJ Mary C Hoffman · IPR · Final written decision

  Claims 1, 5–8, 10, 11, 13, 15, 16, 18, and 19 are unpatentable as obvious under § 103 over the four stated combinations.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not contend that the differences between the parties’ formulations would affect our patentability analysis. PO Resp. 2–4. Petitioner does not dispute that Patent Owner’s declarant, Mr. Ginter, who has a bachelor’s degree and years of experience in wireless communication, qualifies as a POSITA. Tr. 43; Ex. 2009 ¶¶ 5–10. Petitioner also concedes that its challenges do not hinge on which formulation we accept. Tr. 43. We agree that our decision would be the same regardless of the differences between the formulations. We adopt Patent Owner’s proposed formulation, which is supported by declaration testimony and generally consistent with the level of skill reflected in the ’648 patent and the prior art of record. Ex. 2009 ¶¶ 21–25; Exs. 1001, 1004–1009.” slip op. at 10

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

    “We disagree. Although claim 1 recites step 1b before step 1d, method steps are not ordinarily construed to require a specific order of performance unless the claims or Specification directly or implicitly require that specific order. See Altiris, Inc. v. Symantec Corp., 318 F.3d 1363, 1369–70 (Fed. Cir. 2003). Here, nothing in the express claim language precludes performing step 1d before step 1b. The claim does not expressly recite signaling the device(s) previously “identified as available.” Nor does the claim otherwise specify that step 1b must precede step 1d. For example, the claim does not contain temporal terms like “then,” “next,” or “further.” Although Patent Owner points out that a term of step 1d (i.e., “the” one more available devices) derives antecedent basis from step 1b, this alone does not require performing step 1b before step 1d. PO Resp. 5, 10; Sur-reply 11. Rather, we agree with Petitioner that step 1d’s reliance on step 1b for antecedent basis only serves to clarify that the steps refer to the same device(s), not to determine the performance order. Reply 4, 5. We also agree with Petitioner that claim 1 inconsistently employs antecedent basis for other claim elements, which undermines Patent Owner’s argument that step 1d’s antecedent basis establishes a specific order. Reply 7 (referring to the recited “media content,” “the media content,” and “a media content”).” slip op. at 11

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

    “We disagree. Petitioner met its burden to show that the combination would have been obvious. Zhang teaches a cellular phone (which logically receives cellular calls) and routing media to audio devices on its network. Ex. 1004, 3:25–29. Missing in Zhang is an explicit teaching that its cellular calls (as opposed to other media) are routed. Pasanen explicitly teaches routing cellular calls to networked audio devices. Ex. 1006; 4:20–37. Taken together, routing Zhang’s cellular calls across its network would have been obvious to a POSITA. Patent Owner’s argument that Zhang-Fillebrown’s 802.11 or HomeRF network do not support routing cellular calls discounts Zhang’s teaching that “its network can be built on top of many different kinds of communication media” including but not limited to 802.11 and HomeRF, as well as the “optional HomeRF features” Petitioner claims would sufficient to implement the claimed functionality. Ex. 1001, 4:46–50; Reply 20–22 (citing Ex. 1037 ¶¶ 13–15); Sur-reply 3–6 (arguing that HomeRF’s isochronous mode and DECT protocol are optional and would not have been necessary to practice Zhang’s subject matter). And though Zhang does not discuss transcoding or specific HomeRF features/protocols, which Patent Owner argues are necessary for routing cellular calls across Zhang’s 802.11 or HomeRF network, we agree with Petitioner that the ’648 patent also provides scant technical details as to how its system routes cellular calls over its local network, suggesting that such was well known at the time. Reply 17 (citing, e.g., Ex. 1001 7:9–25).” slip op. at 28

  Patent outcomesUS 10,547,648 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,547,648
• Guangzho Eko Trading Development Co., Ltd. v. Nine Stars Group (U.S.A.) Inc.Instituted
  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 · Graham
  Patents in suitUS 10,822,165
• Everstar Merchandise Co., Ltd. v. Willis Electric Co., Ltd.Some claims unpatentable
  PTAB · Dec 18, 2025 · PGR2019-00056 · APJ Stacey G White · PGR · Remand

  Claims 2–7, 9–19, 21–25, 27, 30, 31, and 33 are unpatentable as obvious; Petitioner did not prove claims 8, 20, 26, 28, 29, and 32 unpatentable.

  RulingsRemand decision

  • RemandMixed

    “The Federal Circuit found that “[t]he factual record and Willis’s concession on appeal conclusively establish that the cost of copper was a known problem in the art, Debladis ’120 (and Kumada) helped address that issue, and Willis has not disputed that combining the teachings of Kumada and Debladis ’120 was within the skill of an ordinary artisan,” concluding “[n]othing more is required to establish a motivation to combine.” Everstar II, 2025 WL 1501940, 4. The Federal Circuit observed that “Willis has conceded that the combination of Kumada and Debladis ’120 disclose all the limitations in claim 1,” and accordingly, “reverse[d] the Board’s patentability determination as to that claim and vacate[d] the Board’s judgment as to the remaining claims of the ’037 patent,” remanding to us for further proceedings. Id. at 4–5. With those instructions in mind, we review the Petitioner’s allegations regarding claims 2–33.” slip op. at 6

  • Skill levelSkill level board ownDecided for patent owner

    “F. Person of Ordinary Skill in the Art In the First Final Written Decision, we determined that a person of ordinary skill in the art “would have (1) at least two years of experience in the design of decorative lighting, or (2) at least a bachelor’s degree in mechanical engineering, electrical engineering, or an equivalent field, and a basic familiarity with circuits used in decorative lighting.” Paper 40, 12. We see no reason to depart from that earlier determination.” slip op. at 12

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

    “The parties agree that we do not need to construe any claim terms. Pet. 8–9; PO Resp. 16–17. We likewise agree. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”)).” slip op. at 13

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

    “Patent Owner did not dispute that the combined teachings of Kumada and Debladis ’120 disclose each limitation of claim 1. Patent Owner, however, did dispute Petitioner’s proposed reasons for combining Kumada and Debladis ’120, and argues that Debladis ’120 is not analogous art. PO Resp. 36–61. The Federal Circuit stated that substantial evidence only supports the conclusion that a POSA would have been motivated to combine the teachings of Kumada and Debladis ’120. The factual record and Willis’s concession on appeal conclusively establish that the cost of copper was a known problem in the art, Debladis ’120 (and Kumada) helped address that issue, and Willis has not disputed that combining the teachings of Kumada and Debladis ’120 was within the skill of an ordinary artisan. Nothing more is required to establish a motivation to combine. Given that Willis has conceded that the combination of Kumada and Debladis ’120 disclose all the limitations in claim 1, we reverse the Board’s patentability determination as to that claim and vacate the Board’s judgment as to the remaining claims of the ’037 patent. Everstar II, 2025 WL 1501940, 4 (internal citations omitted). The Federal Circuit further noted Patent Owner’s secondary considerations arguments as to claim 1 and stated [t]he cited evidence consists only of a temporal connection between the introduction of Willis’s invention and the UL 588 standards, and deposition testimony of a single witness who seemingly disclaimed any connection between the two. This is not sufficient to rescue a claim as to secondary considerations. Id. at 4, n. 5 (internal citations omitted). Accordingly, the Federal Circuit ruled that claim 1 would have been obvious over Kumada and Debladis ’120. 6. Analysis of Independent Claim 33” slip op. at 17

  Patent outcomesUS 10,222,037 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 10,222,037
• Arashi Vision (U.S.) LLC (D/B/A Insta360) v. Gopro, Inc.No claims unpatentable
  PTAB · Dec 10, 2025 · IPR2024-01186 · APJ Brian D Range · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

    “Petitioner “does not believe any terms require a formal construction.” Pet. 6. Patent Owner agrees “no claim terms presently require construction to resolve any current dispute between the parties.” PO Resp. 15. We do not discern a need to construe explicitly any claim language at this juncture because doing so would have no effect on our analyses below of Petitioner’s asserted grounds and will not assist in resolving the present controversy between the parties. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

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

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

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

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

  Patent outcomesUS 10,574,894 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,574,894

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.