- Kubota North America Corporation v. Vermeer Manufacturing CompanySome claims unpatentablePTAB · Jun 30, 2026 · IPR2025-00171 · APJ Eric C Jeschke · IPR · Final written decision
Claims 1–13 and 28 are unpatentable over KR996; claims 14–16 and 19–27 were not shown unpatentable over Bares and Beltrami.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“(“This language is merely exemplary, using reference numerals to refer to the embodiment’s features and qualifying ‘single weldment’ as referring ‘generally’ to specific embodiments.”). The Iowa District Court reached the same conclusion. See Ex. 1020 at 4 (holding that “‘mainframe’ will be given its plain and ordinary meaning and does not require a single weldment” (emphasis added)), cited at Pet. Init. CC Br. 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”). Turning to the prosecution history, neither Petitioner nor Patent Owner has highlighted any specific statements that impact the scope of the term “mainframe.” And from our independent review, we do not discern any such statements. For these reasons, the intrinsic evidence as a whole supports construing “mainframe” as a primary supporting structure.” slip op. at 35
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusNot shown unpatentable
“probative and cogent evidence in the record” and “may often establish that an invention appearing to have been obvious in light of the prior art was not.” Transocean Offshore Deepwater Drilling, Inc. v. Maersk Drilling USA, Inc., 699 F.3d 1340, 1349 (Fed. Cir. 2012). Thus, notwithstanding what the teachings of the prior art would have suggested to one skilled in the art, secondary considerations (objective evidence of non-obviousness) may lead to a conclusion that the challenged claims would not have been obvious. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). Our obviousness analysis includes consideration and weighing of Patent Owner’s objective indicia of non-obviousness.” slip op. at 54
- ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part
“For these reasons, we are persuaded by Petitioner to exclude, as” slip op. at 28
Patent outcomesUS 10,202,266 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 10,202,266 - Kubota North America Corporation v. Vermeer Manufacturing CompanySome claims unpatentablePTAB · Jun 30, 2026 · IPR2025-00170 · APJ Eric C Jeschke · IPR · Final written decision
Claims 1–18 are unpatentable over KR996 and the KR996/Bares combination; Petitioner did not prove claims 19–36 unpatentable over KR996, Bares, and Beltrami.
RulingsFinal written decision- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“(10) Conclusion as to Objective Indicia We have considered, as a whole, all of Patent Owner’s arguments and admissible evidence concerning secondary considerations. If we were to presume nexus, we give some weight to Patent Owner’s admissible evidence of industry praise and skepticism at the time of invention. d. Conclusion as to Claim 1 For the reasons discussed above (§§ II.F.2.a–b), the evidence” slip op. at 62
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia outweighedDecided for petitioner
“probative and cogent evidence in the record” and “may often establish that an invention appearing to have been obvious in light of the prior art was not.” Transocean Offshore Deepwater Drilling, Inc. v. Maersk Drilling USA, Inc., 699 F.3d 1340, 1349 (Fed. Cir. 2012). Thus, notwithstanding what the teachings of the prior art would have suggested to one skilled in the art, secondary considerations (objective evidence of non-obviousness) may lead to a conclusion that the challenged claims would not have been obvious. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). Our obviousness” slip op. at 52
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“lexicographical, we agree with the parties that “mainframe” is not limited to a single weldment. Pet. Init. CC Br. 1; PO Init. CC Br. 1–2. Instead, a single-weldment “mainframe” is merely one disclosed embodiment. See Pet. Init. CC Br. 3 (stating that “by including the term ‘generally’ in a statement, the feature (i.e., single weldment) is expressly identified as merely included in some, but not all embodiments”); PO Init. CC Br. 3 (“This language is merely exemplary, using reference numerals to refer to the embodiment’s features and qualifying ‘single weldment’ as referring ‘generally’ to specific embodiments.”). The Iowa District Court reached the same conclusion. See Ex. 1020 at 4 (holding that “‘mainframe’ will be given its plain and ordinary meaning and does not require a single weldment” (emphasis added)), cited at Pet. Init. CC Br. 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”). Turning to the prosecution history, neither Petitioner nor Patent Owner has highlighted any specific statements that impact the scope of the term “mainframe.” And from our independent review, we do not discern any such statements. For these reasons, the intrinsic evidence as a whole supports construing “mainframe” as a primary supporting structure.” slip op. at 33
- ExcludeMotion to exclude, grantedMotion to exclude, deniedMixed
“2. Analysis “The moving party has the burden of proof to establish that it is entitled to the requested relief.” 37 C.F.R. § 42.20. a. Exhibits 1005, 1006, and 1014 Exhibit 1005 is an English language translation of Korean Patent No. 10-1041996. Exhibit 1006 is an English language translation of Japanese document JP2004-17705A. Exhibit 1014 is an English language translation of Korean Patent No. 10-1023528. A Certification of Translation signed by Takashi Maeshiro of HC Language Solutions, Inc., accompanies each of Exhibits 1005, 1006, and 1014. Ex. 1005 at 28; Ex. 1006 at 16; Ex. 1014 at 16. Each Certification of Translation is worded substantially the same except for the references to the document at issue and the source language being either Korean or Japanese. Exhibit 1005’s Certification of Translation, for example, states: I, Takashi Maeshiro, on behalf of HC Language Solutions, Inc., do solemnly and sincerely declare, to the best of my knowledge and belief, that the attached text represents a translation of Korean Patent No. 10-1041996, that the translation was performed by HC Language Solutions, Inc., and that the translation represents a true, correct, and faithful translation from Korean to English in a form that reflects the intention and meaning of the original text. I hereby declare that all statements made herein of my own knowledge are true and that all statements made on information and belief are believed to be true; and further that these statements were made with the knowledge that willful false statements and the like so made are punishable by fine or imprisonment, or both, under Section 1001 of Title 18 of the United States Code. Ex. 1005 at 28 (emphasis added). Patent Owner argues that the Certifications of Translation do not” slip op. at 18
Patent outcomesUS 9,975,750 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 9,975,750 - 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 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01439 · APJ Frederick C Laney · IPR · Final written decision
Claims 1–11 and 13–21 are unpatentable under § 103 based on Ono and Corbett and Uchida and Grimshaw; the Board did not find Ichieda unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner contends that a person having ordinary skill in the art would have had at least a Master’s Degree in Electrical Engineering with . . . five years of work experience in computer science and embedded systems, or Master’s Degree in Computer Science with . . . five years of work experience in electrical and computer engineering and embedded systems. Additional educational experience could substitute for some of the work experience. level of skill in the art.” PO Resp. 10. We adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’951 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“determine that none of the claim terms the parties provide constructions for require an express construction in this proceeding. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019). The parties do appear to disagree on the meaning of “trigger,” however. Although neither party actually identifies that term as needing interpretation and neither party actually provides a claim construction analysis to support its respective position, the parties do dispute whether the evidence presented shows a “trigger,” both presumably giving that term its plain and customary meaning. In other words, while both parties appear to agree “trigger” carries its plain meaning, in application, the parties’ dispute regarding the particular limitations including that term appears to turn, not over what the evidence discloses, but only on whether the disclosure satisfies the plain meaning of “trigger” (see infra § II.E.2). Accordingly, while we apply the plain meaning of “trigger” in this proceeding, and in doing so, we address which party has properly applied the plain meaning and, in doing that, we address the scope properly afforded to “trigger.” That analysis, however, is done below in the context of the limitation in which this issue arises (see id.).” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“has now been developed, and in view of both parties’ arguments, we find Petitioner has persuasively shown that modifying Ono’s peripheral device (i.e., communications module 44) to include an input device/physical actuator like the one described for Ono’s remote controller 69 to control the display of image data from a particular user’s computer would have been obvious to a skilled artisan at the time of the invention. More specifically, Petitioner has shown persuasively Ono shows that the use of an input device/physical actuator to send a signal that causes a participant’s computer to transmit and control the image data presented on a shared display in an image display system was a known technique (see Ex. 1005 ¶¶ 7, 44–48, 66– 71, 77–78, 80–89, 144, Figs. 3, 6, 8, 9; Ex. 1002 ¶¶ 85–100, 121–127) and available location for such an input device/physical actuator to initiate the transmission of data (see Ex. 1007 ¶¶ 6, 18, 20, 22–23, 26, 28, 46, Fig. 1; Ex. 1002 ¶¶ 92–100). Petitioner has also persuasively shown that a skilled artisan recognized benefits to giving a participant the ability to locally control the display of their computer’s image data. See Ex. 1002 ¶¶ 87–91; Ex. 1008 ¶¶ 4, 19–20, 27–28; Ex. 1009 ¶¶ 10–13, 39–10, 70–72. When Ono and Corbett are considered together as a whole from the perspective of a skilled artisan, therefore, it is clear that applying a similar input device/physical actuator to Ono’s peripheral device would have been recognized to result in the benefit of providing a participant with the same ability to send a signal that causes a participant’s computer to transmit and control the image data presented on a shared display from their computer within an image display system. As a result, a motivation has been established because the combination is an application of a known technique to derive a known benefit using prior art elements according to their established functions. Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1380 (Fed. Cir. 2023).” slip op. at 24
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“that, from their perspective, the plain meaning of the term “trigger” does not exclude intervening steps between a user’s action on an input device and the ultimate transfer of the user selected arbitrary media content. Pet. Reply 11– 12 (indicating that “trigger” encompasses “a process that begins with and thus is triggered by a user pressing a button followed by an ‘image transfer’ from a PC to a projector”). For its part, Patent Owner maintains (at least implicitly) that intervening steps are excluded from the plain meaning. Neither party addresses with more specificity why, or why not, the scope of “trigger” supports their positions, however. Having now the complete record before us, we find that out preliminary assessment was wrong because the plain meaning of the term “trigger” does not exclude intervening steps between the cause-and-effect relationship of the trigger and the result it is intended to cause. Take, for example, a simple gun. Pulling the “trigger” to fire a gun necessarily includes intervening steps to occur: the trigger releases a hammer that, in turn, contacts a blasting cap within a bullet casing, which is what actually causes the gunpowder to ignite (i.e., fire) and expel the bullet. And there is no evidence in this record to suggest that this customary understanding of the word “trigger” is any different in the electrical arts, other than the trigger and result are generally electrical in nature, rather than mechanical. We find no clear disavowal of claim scope within the intrinsic record of the ’951 patent to indicate that the term “trigger” was intended to be understood any differently to exclude any intervening steps between a user’s action on an input device and the resulting transfer of user selected arbitrary media content. intervening steps would exist because the input device does not actually do the transferring of the media content; instead, the claims recite the transferring is “from the transmitter to the wireless communications network and [then] to the base node.” See Ex. 1001, 11:3–48, 27:62–28:1 (claim 1), 28:62–67 (claim 9), 29:42–46 (claim 16), 30:36–44 (claim 21) (emphasis added). A skilled artisan would have recognized that there would be intervening steps between the input device being acted upon and the content being displayed by base node’s display. See Ex. 1083 ¶¶ 11–12. In the claims, the input device is analogous to a gun’s trigger, the user carrying out a user action on the input device is analogous to pulling a gun’s trigger, and the transfer of user selected arbitrary media content is analogous the gun expelling a bullet. In both cases, there can be, and usually are, intervening steps, moreover, in both cases, inadvertent things can happen that may prevent the intended result (e.g., in the case of a gun, the hammer can jam; in the case of an input device, a connection can be rejected). Nevertheless, in both cases, the trigger is the thing that initiates an automated process that leads to a particular result, unless a conditional error occurs.” slip op. at 31
Patent outcomesUS 11,422,951 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,422,951 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01438 · APJ Frederick C Laney · IPR · Final written decision
Claims 1, 4, 5, 8, 14, 16, and 18–20 are unpatentable under § 103 based on the five asserted obviousness grounds.
RulingsFinal written decision- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (“[R]ejections on obviousness grounds cannot be sustained by mere conclusory statements; instead, there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” (alteration in original)). This search for answers about whether the claimed subject matter would have been obvious to a skilled artisan at the time of the invention applies “an expansive and flexible art elements would have been obvious is determined by whether the improvement is more than the predictable use of prior art elements according to their established functions. Id. at 417. Reaching this conclusion, however, “requires more than a mere showing that the prior art includes separate references covering each separate limitation in a claim under examination.” Unigene Labs., Inc. v. Apotex, Inc., 655 F.3d 1352, 1360 (Fed. Cir. 2011). “Rather, obviousness requires the additional showing that a person of ordinary skill at the time of the invention would have selected and combined those prior art elements in the normal course of research and development to yield the claimed invention.” Id.” slip op. at 6
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusDecided for petitioner
“3. Conclusion as to Secondary Considerations We have considered all of Patent Owner’s arguments and evidence concerning secondary considerations. We give Patent Owner’s evidence regarding its revenue and profits from the ClickShare product line little weight. We give some weight to Patent Owner’s evidence of licensing. We, however, do not find the licensing evidence outweighs Petitioner’s showing of obviousness.” slip op. at 86
Patent outcomesUS 11,258,676 unpatentable§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,258,676 - Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01437 · APJ Meredith C Petravick · IPR · Final written decision
Claims 1, 3, 9, 18, and 19 are unpatentable as obvious over Kaplan and Mardiks and over Maeda and Deforche.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person having ordinary skill in the art would have had at least a Master’s Degree in Electrical Engineering and five years of work experience in computer science and embedded systems, or a Master’s Degree in Computer Science and five years of work experience in electrical and computer engineering and embedded systems. Additional educational experience could substitute for some of the work experience. Pet. 9 (citing Ex. 1002 ¶¶ 36–37). ordinary skill in the art. PO Resp. 10. We adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’237 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“standard that would be used in a civil action under 35 U.S.C. § 282(b). 37 C.F.R. § 42.100(b). In applying this standard, we generally give claim terms their ordinary and customary meaning as would be understood by a person of ordinary skill in the art at the time of the invention and in the context of the entire patent disclosure. See id.; Phillips v. AWH Corp., 415 F.3d 1303, 1312–14 (Fed. Cir. 2005) (en banc). Petitioner and Patent Owner propose constructions for a number of claim terms. Pet. 9–14; PO Resp. 8–10. Only those terms in controversy, however, need to be construed, and only to the extent necessary to resolve the controversy. Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019). We need not construe explicitly any claim term.” slip op. at 8
- Expert testimonyPetitioner expert creditedDecided for petitioner
“a) Whether Dr. Almeroth’s Testimony should Be Given Little Weight Patent Owner argues that we should give little weigh to the testimony of Dr. Almeroth because Dr. Almeroth’s testimony is allegedly inconsistent across the related inter partes reviews. PO Resp. 11–16; PO Sur-reply 21– 22. We have reviewed the disputed portions of Dr. Almeroth’s testimony and, when read in context, we are not persuaded that the testimony is inconsistent so as to be afforded little weight. As Petitioner points out (Pet. Reply 2), Patent Owner’s arguments do not properly account for the context in which the testimony was given in the related inter partes reviews.” slip op. at 16
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“Two separate tests define the scope of analogous prior art: (1) whether the art is from the same field of endeavor, regardless of the problem addressed and, (2) if the reference is not within the field of the inventor’s endeavor, whether the reference still is reasonably pertinent to the Deutschland Gmbh v. Mylan Pharms. Inc., 66 F.4th 1373, 1377 (Fed. Cir. 2023) (quoting In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004) (citations omitted). We are persuaded by Petitioner that Mardiks meets at least the second test because both the ’237 patent and Mardiks “are directed to solving the same problem of using standard, pre-installed generic drivers, such as human interface device (HID) drivers, to access programs stored on peripheral devices.” Pet. Reply. 3–5; See Ex. 1001, 5:38–40; Ex. 1026 ¶¶ 3, 28. We, thus, are not persuaded by Patent Owner that Mardisk is non-analogous art. slip op. at 16
Patent outcomesUS 11,403,237 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,403,237 - Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01436 · APJ Meredith C Petravick · IPR · Final written decision
Claims 1–3, 9–11, 19, 21, and 22 are unpatentable as obvious over Kaplan, Ahmed, and Deforche, and over Maeda, Ahmed, and Deforche.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person having ordinary skill in the art (POSITA) would have had at least a Master’s Degree in Electrical Engineering and five years of work experience in computer science and embedded systems, or a Master’s Degree in Computer Science and five years of work experience in electrical and computer engineering and embedded systems. the work experience. Pet. 10 (citing Ex. 1002 ¶¶ 36–37). Patent Owner does not dispute Petitioner’s definition of the level of ordinary skill in the art. PO Resp. 12. We adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’002 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner
“term “pre-installed generic driver.” Pet. 13; PO Resp. 9–10. Those proposed constructions are consistent with the lexicographic definition provided in the ’002 patent. In a section titled “Definitions,” the ’002 patent states: The term “pre-installed generic driver” is intended to mean a driver which is installed on a processing device such as a computer as a standard driver, e.g. is installed with the installation of the operating system. Such a driver is standard for the operating system and can drive a standard class of peripheral devices coupled to or connected to the processing device. Ex. 1001, 14:32–38. We apply this lexicographic definition in our analysis below.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“a) Whether Dr. Almeroth’s Testimony should Be Given Little Weight Patent Owner argues that we should give little weigh to the testimony of Dr. Almeroth because Dr. Almeroth’s testimony is allegedly inconsistent across the related inter partes reviews. PO Resp. 13–19; PO Sur-reply 21– 22. We have reviewed the disputed portions of Dr. Almeroth’s testimony and, when read in context, we are not persuaded that the testimony is inconsistent so as to be afforded little weight. As Petitioner points out (Pet. Reply 2–3), Patent Owner’s arguments do not properly account for the context in which the testimony was given in the related inter partes review.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Patent Owner’s arguments are unpersuasive. We are not persuaded that these differences between Kaplan, Ahmed, and Deforche are dispositive. To the contrary, we find the differences establish why a POSITA would have further modified Kaplan and Ahmed with the teachings of Deforche. Deforche expressly teaches that a disadvantage of wireless modems is that they require installation of an appropriate driver before applications running on the computer device can use the functionality of the wireless modem to connect to wireless networks. Ex. 1030 ¶¶ 2–3. Deforche solves this problem by using the processing device’s pre-installed drivers, which can be for a human interface device, to set up a modem/host communication interface for communication. Id. ¶¶ 4, 9. Because “[d]ata traffic from the computer device towards the wireless communication network and vice versa is routed over this modem/host communication interface and uses the generic communication protocol provided by the preinstalled generic driver,” Deforche states this “has the advantage that the need for a specific driver for the communication between the wireless modem device and the computer device can avoided” and “the advantage that a user can use the wireless modem device on a computer device on which he has no administrator rights, i.e. a computer specific driver for the wireless modem device.” Id. ¶ 9. “The motivation-to-combine analysis is a flexible one. Any need or problem known in the field of endeavor at the time of and addressed by the patent can provide a reason for combining the elements in the manner claimed.” Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1379 (Fed. Cir. 2023) (internal quotations omitted). As the Federal Circuit held, “[t]here is a motivation to combine when a known technique has been used to improve one device, and a [skilled artisan] would recognize that it would improve similar devices in the same way.” Intel Corp., 61 F.4th at 1380. Here, Deforche establishes that utilizing an operating system’s preinstalled generic driver to provide a generic protocol communications between the processing device and a peripheral device was known for improving wireless modems because it does not require administrator rights and a specific driver to be installed to enable communications between the wireless modem device and the processing device.” slip op. at 20
Patent outcomesUS 10,762,002 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,762,002 - Fluidmaster, Inc. v. Danco, Inc.All claims unpatentablePTAB · Mar 11, 2026 · IPR2024-00635 · APJ Meredith C Petravick · IPR · Final written decision
The majority held claims 1–14 unpatentable under §103 over Guoxin, Ho, and the Quick Connection Art; one judge dissented as to claims 8, 9, 12, and 13.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“A person of ordinary skill in the art (“POSITA”) with respect to the subject matter of the ’698 patent at the time of the priority date, March 11, 2004, would have had an undergraduate degree in mechanical engineering, or other technical training in product design or equivalent work experience. This person would also possess at least one year of experience in developing and/or evaluating mechanical aspects of fluid systems. I consider myself a person of ordinary skill in the art under this definition. Ex. 1004 ¶ 28. Patent Owner argues: A POSITA in the field to which the ’698 Patent is directed would have had at least a Bachelor of Science degree in mechanical engineering or a related field or, as a substitute, at least two years of work or research experience in the design or development of toilet products, parts, and accessories. PO Resp. 6. We adopt Patent Owner’s proposed definition of a POSITA, as it is consistent with the ’698 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, we see no material difference between the level of skill proposed by Patent Owner and that proposed by Petitioner and Dr. Cameron such that our determinations would be the same under either proposed level of skill.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningDecided for petitioner
“Patent Owner asserts that, because each of the Flow Limitations relate to water flow through the bowl fill valve, these limitations require adjusting the flow rate of water exiting the flow valve. PO Resp. 15–17 (citing Ex. 2013 ¶ 97); See also PO Sur-Reply 7. Petitioner responds that “the claim language of the ’698 Patent discusses adjusting the water flow, not specifically the ‘flow rate.’” Pet. Reply 13. We are not persuaded by Patent Owner, and the conclusory testimony of Mr. Jobin (Ex. 2013 ¶ 97), that because the Flow Limitations “relate” to water flow through the bowl fill valve, that this necessarily means that the flow rate must be adjusted. As Petitioner points out, neither the term “flowrate” nor any similar term appears in any of the Flow Limitations. Thus, the plain language of the Flow Limitations requires that, contrary to Patent Owner’s position, the claim limitation should not be restricted to adjustments to “flow rate.”” slip op. at 14
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“Petitioner argues that Limitations 8B and 12B are directed to the configuration or structure of the bowl fill valve outlet port. Pet. Reply 2–4. According to Petitioner, because Limitations 8B and 12B do recite an overflow tube, the overflow tube is not separately claimed and is recited solely to define the function of the outlet port on the bowl fill valve. Id. at 3. Petitioner, thus, argues that an overflow tube is not separately claimed as a structural element, and that, to meet Limitations 8B and 12B, it is sufficient to show that the prior art discloses a bowl fill valve with an outlet port that is configured to attach directly to a tube that provides water from the outlet port to an overflow tube. Id. at 4. In contrast, Patent Owner argues that Limitations 8B and 12B separately claim the overflow tube, and that Petitioner must show that the prior art discloses a tube that transfers water from the bowl fill valve outlet port to the toilet tank overflow tube. PO Resp. 10–11; PO Sur-reply 2–3. We disagree with Patent Owner, because claims 8 and 12, on their face, require “bowl fill valve outlet port,” but do not require or recite an “overflow tube” as an element of the claimed “bowl fill valve.” When a structure is claimed as “configured to” perform a particular function, it generally requires a structure that is designed to perform the particular function claimed, i.e., it requires more than the mere capability of performing that function. See Aspex Eyewear, Inc. v. Marchon Eyewear, Inc., 672 F.3d 1335, 1349 (Fed. Cir. 2012) (claim language including the phrase “adapted to” is to be construed consistent with “configured to” language and requires that the structure must be “designed or configured to accomplish the specified objective, not simply that [it] can be made to serve that purpose.”); see also In re Giannelli, 739 F.3d 1375, 1379 (Fed. Cir. 2014). The plain language of Limitations 8B and 12B is clearly directed to the configuration of the bowl fill valve outlet port, in that these limitations recite “a bowl fill valve outlet port configured to.”8 The recited function is “attach directly to a tube that provides water from the bowl fill valve outlet port to an overflow tube.” The overflow tube is recited as part of the function in a clause identifying the tube to which the bowl fill valve outlet port is configured to attached — “that provides water from the bowl fill valve outlet port to an overflow tube.” The overflow tube, thus, is recited as part of the function defining the required structure of the bowl fill outlet port and is not separately claimed.” slip op. at 16
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“1. Petitioner’s Contentions Petitioner contends that the combination of Guoxin, Ho, and the Quick Connection Art teaches all of the limitations of claims 1–14 and provides a mapping showing where each claim limitation is found in the prior art. Pet. 21–59. We have reviewed the Petition’s mapping and determine that the Petition sufficiently shows that each limitation of claims 1–14 is disclosed by the combination of Guoxin, Ho, and the Quick Connection Art. Further, we have reviewed Petitioner’s rationale for combining the prior art and determine that the Petition sufficiently shows that it would have been obvious to a POSITA to combine Guoxin, Ho, and the Quick Connection Art.” slip op. at 23
Patent outcomesUS 10,934,698 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,934,698
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.