- Uatp IP LLC v. Slick Slide LLCSome claims unpatentablePTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision
Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20
Patent outcomesUS 11,998,854 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · NautilusPatents in suitUS 11,998,854 - Altria Client Services LLC v. Yiwu Jingangke Trading Co., Ltd.Adverse judgmentPTAB · Oct 1, 2026 · PGR2026-00035 · APJ Robert L Kinder · PGR · Adverse judgment
The Board entered adverse judgment against Patent Owner for abandoning the contest and canceled the sole challenged claim.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“Pursuant to our rules, “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” 37 C.F.R. § 42.73(b)(4). Our prior order warned that a failure to respond would be construed as an abandonment of the contest under 37 C.F.R. § 42.73(b)(4), and that entry of judgment adverse to Patent Owner and cancellation of the challenged claim may follow. Show Cause Order, 2. Because Patent Owner did not respond by the September 15, 2026, deadline and has not entered an appearance in this proceeding, we determine that Patent Owner has abandoned the contest. Under these circumstances, we enter judgment adverse to the Patent Owner and cancel the challenged design claim.” slip op. at 2
None - 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 - 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 - Cisco Systems, Inc. v. Lionra Technologies LimitedAll claims unpatentablePTAB · 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 · GrahamPatents in suitUS 7,738,471 - Penumbra, Inc. v. Rapidpulse, Inc.No claims unpatentablePTAB · Feb 17, 2026 · IPR2024-01261 · APJ Jamie T Wisz · IPR · Final written decision
Claims 1–20 were not shown unpatentable because the asserted combinations did not teach the claimed predetermined cycle for controlling distal fluid flow.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“(1) a person with a B.S. in engineering or an equivalent field, with two-four years of academic or industry experience in aspiration embolectomy and thrombectomy or comparable industry experience who would, where appropriate, work or consult with others, including a physician, to develop embolectomy or thrombectomy devices; or (2) an interventional neurosurgeon with at least three years of experience developing and/or using medical devices in embolectomy or thrombectomy procedures, and who would, where appropriate, work or consult with others, including an engineer, to develop such a medical device. Pet. 11 (citing Ex. 1005 ¶ 48). Petitioner also contends that, “[a] person with less education but more relevant practical experience, or more relevant education but less practical experience, may also meet this standard.” Id. Patent Owner states that for purposes of its PO Response, it “accepts ¶ 44). We adopt Petitioner’s characterization because it is consistent with the level of skill in the art at the time of the invention as reflected by the ’402 patent and the cited prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need for testimony is not shown” (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985))).” slip op. at 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“specification explicitly includes sensors similar to those in the prior art in support of their argument that the claimed “predetermined cycle” must not exclude the use of such sensors. Pet. Reply 15 (citing Ex. 1001, 32:55–33:7, 40:66–41:5, 44:9–29). We reviewed the portions of the specification cited by Petitioner. We agree with Patent Owner that one excerpt discussing sensor use appears to be directed to triggering the predetermined cycle rather than causing timing changes during the cycle itself (Ex. 1001, 32:55–66) (describing use of a pressure sensor to “determine when the vacuum channel 3 is clogged by a thrombus and automatically perform the unclogging procedures described herein”), while another excerpt discusses a sensor that Petitioner that the ’402 patent discusses the use of sensors to “tune” the system and that such “tuning” can be done statically (setting the cycle timing in advance) or dynamically (adjusting the timing during the cycle itself). See Ex. 1001, 48:19–49:50. Overall, we find that these disclosures involving sensors demonstrate that sensors may be used in various ways in different embodiments. However, none of these disclosures explicitly discuss the use of sensors in conjunction with a “pre-determined cycle.” Therefore, we find that the ’402 patent specification’s discussion of “sensors” are not particularly informative as to the appropriate construction of a “predetermined cycle” and do not outweigh the other explicit disclosures of “predetermined cycle” in the patent. We next turn to the other intrinsic evidence discussed by the parties — the prosecution history. As discussed by Patent Owner, in the Notice of Allowance, the Examiner found that Garrison did not teach or suggest a “predetermined cycle” because Garrison’s controller “changed the cycle of opening and closing the valves based on feedback from sensors.” Ex. 1004, 86. We acknowledge that the patent applicant filed subsequent comments during prosecution in which they stated that they “do[] not concede that the Examiner’s characterizations of the terms of the claims and the prior art are correct.” Id. at 29. However, we agree with Patent Owner that the importance of the Examiner’s statement in the Notice of Allowance does not rely on it being an express disclaimer (a standard which it does not meet). PO Sur-reply 8. We also considered Petitioner’s contention that the Examiner’s interpretation of Garrison may have been in error (PO Resp. 16); however, even if this were true, the Examiner’s statement still provides helpful insight into how the Examiner was interpreting the term sensors to change the opening and closing of valves during a cycle was not a “predetermined cycle.” Id. at 86. In sum, we find that Patent Owner’s proposed construction is consistent with the usage of the term “predetermined cycle” in the ’402 patent specification and prosecution history. Thus, after considering all of the cited evidence, we construe “predetermined cycle” to mean that “the timing of the sequence of valve operations in the cycle is determined beforehand, i.e., fixed, rather than varying based on feedback after operation begins.”” slip op. at 14
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“2. Other Terms The parties also provided proposed constructions for the limitations of “[limited/limiting] to a positive amount of exit flow” and “control[ling] fluid flow in and out from the distal end of the catheter.” See Pet. 15–16; Pet. Reply 1–8; PO Resp. 22–24; PO Sur-Reply 2–6. However, having evaluated the arguments and evidence before us, we determine that construction of these terms is not necessary for purposes of this Decision. 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 16
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableNot shown unpatentable
“We agree with Patent Owner that neither Petitioner nor Mr. Brown propose any combination of Yang and Mullins that does not include Mullins’s pressure sensor in order “to control fluid flow in and out from the distal end of the catheter.” Indeed, in addressing the “predetermined cycle” limitation, Mr. Brown contends that Mullins discloses a “cycling controller that ‘varies aspiration pressure according to sensed pressure within the catheter lumen.’” Ex.1005 ¶¶ 131–32 (citing, e.g., Ex.1008, 27:40–28:20 (“[a] novel aspect of this pump system is the incorporation of feedback into the pump algorithm in order to produce more effective pressure cycling”)). This use of a sensor to change pressure during a cycle, is not a “predetermined cycle” under our construction. combinations is its discussion of distal end flow control, not for its sensors.” Pet. Reply 17 (citing Ex. 1035 ¶ 83). However, Petitioner’s obviousness grounds rely on the combination of Yang and Mullins, especially with regard to Mullins’s disclosure of “a controller” in order “to control fluid flow in and out.” As discussed above, Mullins relies on the sensor-feedback approach in order to control flow and we find that Petitioner has not presented persuasive evidence of how the combined disclosures of Yang and Mullins would control flow without using Mullins’s sensor feedback approach. See W.L. Gore & Assocs., Inc. v. Garlock, Inc., 721 F.2d 1540, 1550 (Fed. Cir. 1983) (error to “consider[] … references in less than their entireties, i.e., in disregarding disclosures in [them] … that diverge from and teach away from the invention”). Therefore, we determine that Petitioner has not sufficiently shown that the combination of Yang and Mullins discloses or renders obvious “a controller configured to open and close the vacuum valve and the vent valve in a predetermined cycle to change a level of vacuum at the distal end of the catheter and to control fluid flow in and out from the distal end of the catheter.” Accordingly, having considered the parties’ respective evidence and arguments, we find that Petitioner has not shown by a preponderance of the evidence that claim 1 of the ’402 patent would have been unpatentable as obvious over the combination of Yang and Mullins.” slip op. at 27
Patent outcomesUS 11,406,402 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,406,402 - Alpinestars S.P.A. / Alipinestars USA Inc. v. Dainese S.P.A.Rehearing deniedPTAB · Feb 9, 2026 · IPR2025-00750 · APJ Benjamin D M Wood · IPR · Rehearing
The Board denied rehearing, leaving institution denied because Petitioner did not show a reasonable likelihood of prevailing on claims 1–22 under the challenged obviousness grounds.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“Petitioner misstates the Decision’s reasoning. As is clear from the previous discussion, we determined that Petitioner’s articulated reasons for combining EP’536 with CN’180 lacked a rational underpinning, not because “EP’536 does not relate to ‘air bags,’” but because the means by which EP’536’s device inflates differs fundamentally from that of CN’180’s device. Dec. 17–18. Petitioner did not acknowledge this critical difference in the Petition, and continues not to do so in its Rehearing Request.” slip op. at 5
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“EP’536 with CN’180 lacked a rational underpinning because EP’536’s inflation mechanism differs fundamentally from CN’180’s inflation mechanism. Dec. 17–18. As we stated, whereas CN’180’s fall-protection belt uses an airbag that requires an external source of pressurized air to inflate, EP’536’s garment does not need an external inflation device because “the gas generating agent 18 in each envelope automatically generates gas and inflates the envelopes in response to rising temperatures.” Id. at 18 (citing Ex. 1004 ¶ 15; Ex. 1005 ¶¶ 5, 19). This difference reflects the fundamentally different purposes of the two devices: CN’180’s device is designed to provide “fall protection” to, e.g., “elderly people,” (Ex. 1005 ¶ 1, 3), whereas EP’536’s device provides “adaptive thermal insulation” for, e.g., garments worn by fire fighters. Ex. 1004 ¶¶ 1–3, 250. Because of the different means by which EP’536’s and CN’180’s devices inflate and the different purposes for doing so, we were not persuaded that one of ordinary skill in the art would have combined the references as Petitioner proposed. Dec. 18. We further noted that the modification would not have improved the reusability of EP’536’s device “by having only one mechanism to recharge,” because EP’536’s “gas generating agent does not need any ‘mechanism to recharge.’” Dec. 18. Instead, we noted EP’536’s teaching that its gas generating agent “automatically recombines or condenses in response to a temperature decrease to return the envelopes, and therefore the garment, to its original thickness, at which point the gas generating agent is ready for subsequent reactivation.” Id. (citing Ex. 1004 ¶¶ 139–141). Finally, we determined that replacing EP’536’s envelopes with CN’180’s airbag “would have made EP’536’s invention unsuitable for its intended purpose: providing a protective garment with ‘adaptive thermal insulation.’” Dec. 19. We stated that “Petitioner does not suggest, and we have found nothing in the record to establish, that CN’180’s airbag would provide this feature.” Id. at 20.” slip op. at 3
- Obviousness (§103) › KSR rationalesMotivation not foundNot shown unpatentable
“rationales for combining EP’536 and CN’180. Reh’g Req. 6–7. First, Petitioner asserts that we “improperly rejected Petitioner’s ‘simple substitution’ evidence in view of [the Board’s] incorrect conclusion that EP’536 does not disclose an ‘external source of inflation [EP’536’s dosing aids].’” Id. at 6 (citing Dec. 18–19). This argument is unpersuasive at least because, as we discussed above, EP’536’s dosing aids do not constitute an external source of inflation. Petitioner further argues that we incorrectly evaluated its “obvious to try” rationale because, contrary to our analysis, Petitioner did in fact identify a problem to be solved by its “finite number of solutions”: “simplify[ing] the design and reduc[ing] the number of required inflation mechanisms.” Id. at 6–7. The Petition’s entire “obvious to try” discussion is as follows: [A] POSITA would have found it obvious to try a one-piece airbag 10 with strip-shaped inflation units 12 in the EP’536- CN’180 airbag system because it would have been a selection from a finite number of identified predictable solutions (i.e., using one chamber with connected individual inflation units 12 versus multiple individual envelopes 20). 5 Petitioner also argues that dosing aids are “needed in order to make the disclosed device reusable.” Reh’g Req. 5–6. This is incorrect, as EP’536 conveys that the reusability of the device is a result of the gas generating agent condensing or recombining when temperatures fall. Ex. 1004 ¶¶ 139– 141. Even if it were true, however, it is unclear how it would support Petitioner’s argument. Pet. 16. As is evident, Petitioner did not identify a design need, market pressure, or other problem that would have been addressed by its identified “solutions,” and therefore we were not persuaded by this rationale. Dec. 19. Petitioner’s attempt to cure this deficiency in its Rehearing Request is tardy. We cannot misapprehend or overlook an assertion that Petitioner fails to make in the Petition. It is also insufficient. Petitioner does not provide any evidence of a known design need or market pressure to “simplify [EP’536’s] design” or reduce the number of “required inflation mechanism” it uses.” slip op. at 7
§ 103 obviousnessPatents in suitUS 12,012,065 - Solaris Oilfield Site Services Operating, LLC / Solaris Oilfield Site Services Personnel, LLC v. Masaba, Inc.All claims unpatentablePTAB · Jan 26, 2026 · IPR2024-01179 · APJ Carl M Defranco · IPR · Final written decision
Claims 1–25 are unpatentable under § 103 over the asserted combinations of Waldner, Dynatek, and additional references; the Board cancelled all challenged claims.
RulingsFinal written decision- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“Also, to the extent Masaba relies on extrinsic expert testimony, we note that Masaba’s expert cites absolutely no support for his understanding of the claims, much less explains why we should adopt his understanding over the plain and ordinary meaning of “conveying aggregate” and “moving aggregate.” See Ex. 2004 ¶ 34. Absent supporting citations, such extrinsic testimony is entitled to little, if any, weight. As such, we reject the notion that Waldner’s discharge chute member 242 is not a conveyor “for conveying aggregate” or “for moving aggregate,” as required by claim elements 1[h] and 1[i].” slip op. at 21
- Skill levelSkill level petitioner adoptedDecided for petitioner
“We disagree that Dr. Durham does not possess the necessary level of skill in the art to qualify as an expert in this case. Looking at the specification of the ’689 patent and the prior art of record, we think Masaba sets the bar too high. We acknowledge that one of ordinary skill in the art should have some education and/or experience in the mechanical art of conveying aggregate materials, but we do not think opining on the ’689 patent and asserted prior art necessarily requires that person to have the amount of education and experience that Masaba advocates. The ’689 patent relates generally to an “aggregate transferring system for receiving aggregate from a vehicle and elevating the aggregate to a higher vertical level for deposit into, for example, a silo.” Ex. 1001, 1:15– 18. And, as described in the ’689 patent and discussed later, the transferring system is an assembly of known types of conveyors, such as a belly-dump truck conveyor, a bucket elevator, and an articulated belt conveyor, for transferring the aggregate horizontally and vertically from a belly-dump truck to the discharge point, such as a silo. Without doubt, Dr. Durham has enough education and experience to reliably opine on the combination of known parts.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningNo construction needed
“We reject this argument for several reasons. First, nowhere does the plain language of the claims specify how the aggregate is conveyed or moved from the conveyor extension assembly’s inlet to its outlet, be it passively by means of gravity or actively by means of a conveyor belt. Instead, the claims simply use those verbs according to their plain and ordinary meaning, which is “to transfer or deliver” or “to cause to go or pass” from one place to another. See Ex. 3001, 253 (defining “convey”), 760 (defining “move”).10 Second, the specification of the ’689 patent similarly uses these terms in a plain and ordinary sense, without ever attributing to them some sort of special meaning. See, e.g., Ex. 1001, 4:9–12 (“The apparatus 10 is suitable for performing the transfer of aggregate from 10 We reference the original pagination of the dictionary in which these definitions appear. one location to another, such as, for example, from a vehicle carrying the aggregate to a silo 1 for storing the aggregate.”). The ’689 patent specification also makes clear that active conveyance of the aggregate is an option and not a requirement of the claimed invention, stating that the conveyor extension assembly “may further include a conveyor belt 150.” Ex. 1001, 10:60–66 (emphasis added). Limiting claim elements 1[h] and 1[i] to a device “for actively conveying” or “for actively moving aggregate” would improperly import limitations from the specification into the claims. Thus, based on the intrinsic evidence, we determine that claim elements 1h and 1k are properly construed to encompass passive and/or active movement of the aggregate via the conveyor extension assembly.” slip op. at 20
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)Not reached
“Owner asserts” that two claim terms—“unloader structure” and “trailer structure”—should be construed as means-plus-function limitations under 35 U.S.C. § 112(f), Solaris submits an express construction detailing the corresponding structure in the specification for performing the recited function of the claimed unloader and trailer structures. See id. at 24–25. Only in disputing Solaris’s Ground 3 does Masaba advocate that the claim term “trailer structure” should be construed under § 112(f), and then only in conjunction with dependent claims 3 and 21. See PO Resp. 58. As such, we address Masaba’s proposed construction in our analysis of Ground 3. We now turn to Solaris’s grounds of unpatentability.” slip op. at 12
Patent outcomesUS 11,780,689 unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 11,780,689
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.