• Aroma360, LLC v. Air Esscentials, Inc.Some claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00707 · APJ Eric C Jeschke · IPR · Final written decision

  Claim 5 is unpatentable over Gao-2 and over Gao-2 with Goubet; claims 1, 3, 4, and 6–8 were not shown unpatentable on any ground, and substitute claim 17 was denied.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9

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

    “Neither Petitioner nor Patent Owner propose explicit constructions for any claim terms. Pet. 16–17; PO Resp. 5–6. Based on the complete record, we need not construe explicitly any claim terms because doing so would not change the outcome of the analysis below. 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 10

  • Expert testimonyPetitioner expert creditedDecided for patent owner

    “As an initial matter, the record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration for allegedly not reviewing the parties’ claim constructions. See Pet. Reply 2–3 (citing Ex. 1046, 115:15–18). Contrary to Petitioner’s argument, in the cited 11 This refers to the recitation in clauses 1F and 5F that the “diffusion assembly is disposed between said upper chamber and said lower chamber.” discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1; see also Pet. Reply 3 (arguing that “Dr. Micklow’s opinion that the prior art does not render the claims obvious is premised on an interpretation of certain claim limitations that are inconsistent with both parties’ constructions” (emphasis added)). Instead, we read Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also id. at 115:15–18 (“I don’t know if I would even apply claim construction. I applied engineering principles to a document that had been published with the patent office.”).” slip op. at 12

  • BurdenNot shown unpatentable

    “referring to the same direction as the separation of the “upper chamber” and “lower chamber” (vertically in both Figure 6 of the challenged patent and Figure 1 of Goubet), we turn back now to Petitioner’s discussion of clause 1F, which includes the limitation at issue. There, Petitioner does not discuss why the “diffusion assembly” is allegedly “disposed between” the “upper chamber” and “lower chamber,” but instead, Petitioner discusses why a component of the “diffusion assembly”—the “atomizer assembly”—is allegedly “disposed between” the “upper chamber” and “lower chamber”: Pet. 39. In the end, we need not assess whether the “atomizer assembly” identified by Petitioner is “disposed between” the “upper chamber” and “lower chamber” under the proper construction of that term (which, again, we need not and do not determine here) because the “disposed between” limitation does not involve the “atomizer assembly.” Instead, we find that, by failing to address why the identified “diffusion assembly” is “disposed between” the identified “upper chamber” and “lower chamber,” Petitioner has failed to provide persuasive evidence that Goubet discloses or suggests the “disposed between” limitation. Pet. 38–39 (discussing the claim language “said diffusion assembly is disposed between said upper chamber and said lower chamber” but only discussing the location of the “atomizer assembly”); see 35 U.S.C. § 316(e) (“In an inter partes review . . . , the petitioner shall have the burden of proving a proposition of unpatentability by a preponderance of the evidence.”). For the reasons above, we find, based on the complete record, that Petitioner has not shown by a preponderance of the evidence that Goubet discloses or suggests the “disposed between” limitation.” slip op. at 22

  Patent outcomesUS 10,092,918 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 10,092,918
• Aroma360, LLC v. Air Esscentials, Inc.All claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00706 · APJ Eric C Jeschke · IPR · Final written decision

  Claims 1, 4, and 7–10 are unpatentable as obvious over Goubet and anticipated by Gao; proposed substitute claims 20 and 21 are denied as indefinite and lacking written-description support.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Response, Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner, but Patent Owner “reserves the right to address [the definition] should new issues materialize.” PO Resp. 6. Patent Owner did not address this issue in the Sur-reply. As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9

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

    “Network LLC, 929 F.3d 1350, 1357 (Fed. Cir. 2019). At first glance, the language of the limitation at issue—which, again, recites “the compressed air and the operative fluid mix together in said mixing chamber to form the fluid dispersion”—would seem to require the “fluid dispersion” (under the stipulated construction) to be fully formed in the “mixing chamber.” In other words, the language of the limitation alone would seem to support Patent Owner’s proposed construction for the “form the fluid dispersion” limitation. But the claim construction analysis does not end with consideration of the claim language alone. Next, we turn to the Specification. The Federal Circuit has said that the specification “is the single best guide to the meaning of a disputed term.” Phillips, 415 F.3d at 1315 (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). Here, the discussion in the Specification of precisely the same language as in the limitation at issue strongly supports that “to form a fluid dispersion” in the limitation at issue requires only initial mixing of the compressed air and operative fluid in the mixing chamber, with further “formation” of the ”fluid dispersion” occurring downstream of the mixing chamber: More importantly, the “predetermined amount” of compressed air and the “preselected amount” of the operable fluid are initially mixed together in the mixing chamber 226 to form a fluid dispersion. The diffusion chamber 112" is further structured to facilitate the formation of a plurality of substantially uniform droplets, as defined hereinabove, in the fluid dispersion prior to discharge from the diffusion chamber 112" through discharge port 132. Ex. 1001, 10:62–11:2 (emphasis added) (discussing Figure 6), quoted, in part, at Pet. Reply 6–710; see also Ex. 1001, 5:64–6:4 (same language, except without double primes, in a discussion of Figures 1 and 2). To be sure, certain passages in the Specification could be read to indicate that a “fluid dispersion” must be fully formed in the “mixing chamber.” See, e.g., Ex. 1001, 6:11–12 (“More in particular, the suppression chamber 232 receives the fluid dispersion from the mixing chamber 226.”); see also id. at 7:22–33, 11:39–52 (both implying that a “fluid dispersion” is formed in the mixing chamber). But the passage block quoted directly above (and the similar one bridging columns 5 and 6) more directly addresses the issue at hand—i.e., the scope of “form the fluid dispersion”—by using the same” slip op. at 13

  • Expert testimonyPatent owner expert discountedMixed

    “As an initial matter, the record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration for allegedly not reviewing the parties’ claim constructions. See Pet. Reply 2 (citing Ex. 1046, 115:15–18). Contrary to Petitioner’s argument, in the cited discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1. Instead, we read Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also id. at 115:15–18 (“I don’t know if I would even apply claim construction. I applied engineering principles to a document that had been published with the patent office.”).” slip op. at 18

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

    “To satisfy its burden of proving obviousness, a petitioner cannot employ mere conclusory statements. The petitioner must instead articulate specific reasoning, based on evidence of record, to support the legal conclusion of obviousness.” In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016); TriVascular, Inc. v. Samuels, 812 F.3d 1056, 1066 (Fed. Cir. 2016) (“Although the KSR test is flexible, the Board ‘must still be careful not to allow hindsight reconstruction of references . . . without any explanation as to how or why the references would be combined to produce the claimed invention.’”) (citation omitted). Based on the complete record, we agree with Patent Owner that “Petitioner’s asserted motivation boils down to the conclusory statement that given Goubet and Kaiser, ‘it was well known in the field at the time of the invention that droplets of greater uniformity result in uniform droplet evaporation.’” PO Resp. 31 (quoting Pet. 59). We agree with Patent Owner that Petitioner’s discussion of the alleged reasons to combine (Pet. 59) is insufficient to support the proposed combination here. See Magnum Oil, 829 F.3d at 1380. Specifically, we are not persuaded that Kaiser’s teachings—which relate to combustion (Ex. 1014 at 43)—would have led one of ordinary skill in the art to the proposed modifications, which would allegedly “improve the smoothness (i.e., less harsh) of the aroma generated as the oil droplets evaporate in the surrounding airspace.” See Pet. 59 (emphasis added); White Pet. Decl. ¶ 251 (same); see PO Resp. 32 (“Rather, Dr. White merely describes the ability to achieve the effect as in the claimed patent, not why a [person of ordinary skill in the art] would look to the field of electrospray injection and combustion in mesoscale power-generation systems, using high-voltage electric fields to generate charged fuel droplets for controlled combustion in catalytic micro-combustors when considering atomization for scents.”). For these reasons, we determine, in light of the complete record, that Petitioner has not shown by a preponderance of the evidence that one of ordinary skill in the art at the time of the invention would have had reason to combine Goubet and Kaiser, as proposed. slip op. at 32

  Patent outcomesUS 10,583,449 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Nautilus
  Patents in suitUS 10,583,449
• Aroma360, LLC v. Air Esscentials, Inc.All claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00705 · APJ Eric C Jeschke · IPR · Final written decision

  Claims 7–9 and 11 are unpatentable as obvious over Goubet; proposed substitute claim 21 is denied as indefinite.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Response, Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner, but Patent Owner “reserves the right to address [the definition] should new issues materialize.” PO Resp. 5. Patent Owner did not address this issue in the Sur-reply. As noted in the Decision on Institution, Petitioner’s proposed definition appears generally consistent with the record, including the prior art. See Dec. Inst. 8 (citing In re GPAC Inc., 57 F.3d at 1579). We remove the phrase “at least” in both listed options, however, as that phrase adds ambiguity. Further, Patent Owner has not argued at trial that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art. In the analysis below, we continue to apply the level of ordinary skill in the art adopted in the Decision on Institution, as proposed by Petitioner.” slip op. at 9

  • Expert testimonyPetitioner expert creditedDecided for patent owner

    “The record here does not support any sound basis to disregard the entirety of Dr. Micklow’s Declaration, as asserted in Petitioner’s overall argument. See Pet. Reply 1–2. Contrary to Petitioner’s argument, in the cited general discussion, Dr. Micklow does not indicate that he applied an incorrect understanding of a claim term. Cf. Cordis Corp. v. Bos. Sci. Corp., 658 F.3d 1347, 1357–58 (Fed. Cir. 2011) (disregarding testimony “based on an incorrect understanding of the claim construction”), cited at Pet. Reply 1; see also Pet. Reply 2 (arguing that “Dr. Micklow’s declaration is premised on understandings of claim scope that are inconsistent with the constructions advanced by both of the parties” (emphasis added)). Instead, we read the cited portions of Dr. Micklow’s testimony as clarifying that he was not involved in claim construction at all and that, as stated, he “made [his] opinions based on what [he] read in the patents.” Ex. 1046, 112:11–12; see also Pet. Reply 1 (citing Ex. 1046, 112:4–12, 113:13–20, 115:15–18). Next, we turn to each of the four specific claim terms that Petitioner highlights in its further arguments.” slip op. at 12

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

    “B. Claim Construction In inter partes reviews, the Board interprets claim language using the same claim construction standard that would be used in a civil action under 35 U.S.C. § 282(b), as described in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). See 37 C.F.R. § 42.100(b). Under that 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, in light of the language of the claims, the specification, and the prosecution history. See Phillips, 415 F.3d at 1313–14. Although extrinsic evidence, when available, may also be useful when construing claim terms under this standard, extrinsic evidence should be considered in the context of the intrinsic evidence. See id. at 1317–19. Neither Petitioner nor Patent Owner propose explicit constructions for any claim terms. Pet. 10–11; PO Resp. 5. Based on the complete record, we need not construe explicitly any claim terms because doing so would not change the outcome of the analysis below. 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 9

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

    “Florida Litigation a Joint Claim Construction statement that included stipulated claim constructions and disputed claim constructions for terms in the challenged patent as well as the ’449 patent and the ’918 patent. See Ex. 1018, Exhibit A (Stipulated Claim Constructions), Exhibit B (Disputed Claim Constructions). The parties stipulated to the construction of the terms “fluid dispersion” and “baffle” as recited in the challenged claim. See id., Exhibit A.10 10 When staying the Florida Litigation, the District Court cancelled the scheduled claim construction hearing. See ECF No. 67 (April 8, 2025) (granting joint motion to stay); ECF No. 68 (April 8, 2025) (cancelling the The stipulated construction of “fluid dispersion” merely restates the express definition of “fluid dispersion” from the challenged patent (although the definition is not cited or discussed in the parties’ filing). Compare Ex. 1018, Exhibit A, with Ex. 1001, 3:8–20. Similarly, the stipulated construction of “baffle” essentially parrots one sentence in the challenged patent (again, not cited or discussed in the parties’ filing). Compare Ex. 1018, Exhibit A, with Ex. 1001, 7:57–59. To the extent necessary, we determine that the complete record supports the parties’ stipulated constructions of “fluid dispersion” and “baffle,” and we apply those constructions below.” slip op. at 10

  Patent outcomesUS 9,527,094 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Nautilus
  Patents in suitUS 9,527,094
• Evenflo Company, Inc. v. Baby Jogger II, LLCAll claims unpatentable
  PTAB · Sep 29, 2026 · IPR2025-01122 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1–16 are unpatentable as obvious over Liao or Liao and Cheng; Rolicki is not prior art, and the challenge over Offord ’341 and Offord ’797 fails.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A. Level of Ordinary Skill in the Art Baby Jogger does not dispute Evenflo’s definition of the level of ordinary skill in the art, which is that a person of ordinary skill in the art (hereinafter, “one skilled in the art”) would have had “a bachelor’s degree in a relevant field (e.g., mechanical engineering or industrial design) and at least two years of product design experience and/or industry experience with juvenile products” and that “[m]ore education can replace product design experience, and vice versa.” Pet 8 (citing Ex. 1001 ¶¶ 31–33); PO Resp. generally. We apply that definition here, as it accords with the problems addressed in the prior art and the specification of the ’682 patent.” slip op. at 7

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

    “At the outset, we note that the claim language requires only that “the first seat and the second seat” be arranged in an inline descending configuration, not that the seat’s mounting points or other physical connections be so arranged. Ex. 1010, 17:31–33. Baby Jogger improperly reads “seats” out of the claim and substitutes the seat’s “mounting points” on the frame. A proper reading of the claim language focuses on what happens when both seats are connected to the frame, not where they are so connected. In other words, “when connected to the frame” simply emphasizes that both seats must be connected to the frame to form the inline descending configuration, as opposed to the single stroller embodiment of Figure 1, where there cannot be an inline descending configuration because only one seat is connected to the frame and the other seat is removed, i.e., not connected to the frame. That reading is supported by the specification of the ’682 patent,” slip op. at 9

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

    “We find that testimony persuasive, for it shows what one skilled in the art would have recognized the 2008 Provisional as necessarily disclosing. The relevant inquiry is whether the disclosure of the prior application “convey[s] with reasonable clarity to those skilled in the art that, as of the filing date sought, the inventor was in possession of the invention.” PowerOasis, 522 F.3d at 1306 (emphasis in original; citation omitted). “While a prior application need not contain precisely the same words as are found in the asserted claims, . . . the prior application must indicate to a person skilled in the art that the inventor was ‘in possession’ of the invention as later claimed.” Id. In other words, “to satisfy the written description requirement, ‘the missing descriptive matter must necessarily be present in the [original] application’s specification such that one skilled in the art would recognize such a disclosure.’”7 Id. (quoting Tronzo v. Biomet, Inc., 156 F.3d 1154, 1159 (Fed. Cir. 1998) (emphasis added). “This requires that the written description actually or inherently disclose the claim element.” Id. at 1306–07. Moreover, a drawing may supply written description for the arrangement it depicts even though the text describes that arrangement in different terms. See Cooper Cameron Corp. v. Kvaerner Oilfield Prods., Inc., 291 F.3d 1317, 1319–23 (Fed. Cir. 2002).” slip op. at 16

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

    “Instead, Evenflo’s argument rests on isolating the statement—“A similar sub-frame arrangement is disclosed in [Offord ’797]”—from the remainder of the passage in which that statement appears in order to arrive at a reason to incorporate the reversibility teaching of Offord ’797. However, when that statement is read in the context of the full passage in which it appears, nowhere does that passage suggest reversibility as the reason for referencing Offord ’797. More accurately, it suggests a different reason that relates to a curved lug 108 by which sub-frame 100 rests on the stroller’s main frame 4 to carry the weight of the stroller’s two occupants— When the interface components 100 are attached to the frame assembly 4 they form a sub-frame of the frame assembly 4, and when the child-carrying units are mounted thereon, one behind the other, they are in a compact echelon formation, one of the connector sockets 106 of each component 100 being at a higher level in relation to the ground than the other connector sockets 106. The higher connector socket 106 and further connecting leg 102 are both connected to the respective opposite ends of an upper mounting piece 107. In addition, on the inner side of the lower connector sockets 106 there is a downwardly curved lug 108 which serves to rest upon a part of the basket frame 44, such that the weight of two infants is fully supported by the frame assembly 4. A similar sub-frame arrangement is disclosed in [Offord ’797]. Ex. 1051, 9:23–36 (emphasis added). That passage shows that, rather than reversibility of the sub-frame, the reference to Offord ’797 is more aptly directing the reader to the arrangement and details of a similarly curved lug structure in the stroller sub-frame of Offord ’797. Indeed, Figures 5 and 6 of Offord ’797, reproduced below, disclose just such a curved lug in the context of “corner pieces 20” having “channel 21.” Ex. 1054, 4:10–23.” slip op. at 53

  Patent outcomesUS 11,731,682 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 11,731,682
• Tesla, Inc. v. Charge Fusion Technologies, LLCAll claims unpatentable
  PTAB · Jul 13, 2026 · IPR2025-00153 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1–30 are unpatentable as obvious under § 103 over the asserted combinations of prior art.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of one of ordinary skill in the art at the time of the invention. Tesla submits that one of ordinary skill in the art would have had at least a bachelor’s degree in electrical or mechanical engineering (or an equivalent field) and at least two years of work experience involving automotive systems, including electric vehicle power management. . . . Additional industry 1 US 2009/0313034 A1, pub. Dec. 17, 2009 (Ex. 1004, “Ferro”). 2 EP 1,920,968 A1, pub. May 14, 2008 (Ex. 1005, “Oyobe”). 3 US 7,124,691 B2, iss. Oct. 24, 2006 (Ex. 1006, “Donnelly”). 4 Steven E. Letendre, The V2G Concept: A New Model for Power? PUBLIC UTILITIES FORTNIGHTLY, Feb. 15, 2002, at 16 (Ex. 1007, “Letendre”). 5 US 5,654,621, iss. Aug. 5, 1997 (Ex. 1078, “Seelig”). 6 US 6,662,083 B1, iss. Sep. 16, 2003 (Ex. 1010, “Knockeart”). experience or technical training may offset less formal education, while advanced degrees or additional formal education may offset lesser levels of industry experience. Pet. 2 (citing Ex. 1003 ¶¶ 14–15). Charge Fusion “takes no position with respect to Petitioner’s proposed level of ordinary skill.” PO Resp. 17. For purposes of our analysis, we apply Tesla’s proposed level of ordinary skill, which we find to be consistent with the problems addressed in the ’987 patent and the prior art. B. Claim Interpretation” slip op. at 6

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

    “1. “dynamic attribute of an electric charge provider” In the Petition, Tesla proposes that we construe “dynamic attribute of an electric charge provider,” as recited in every independent claim, to mean “a changing or otherwise fluctuating cost (or price) of electricity for purchase from an electric charge provider.” Pet. 4–5. Charge Fusion responds that Tesla improperly narrows the meaning of this claim limitation. PO Resp. 15 (arguing this claim term “is not just limited to ‘changing or otherwise fluctuating cost (or price)’ as alleged by the Petition” (emphasis added)). Although we consider Tesla’s proposed construction to identify an exemplary “dynamic attribute of an electric charge provider,” we see no need to limit the meaning of this limitation as proposed by Tesla. Indeed, Tesla agrees. See Pet. Reply. 7 (arguing only that this claim limitation “at least includes” such an example). And Charge Fusion does not contend otherwise. See PO Resp 15 (arguing only that this limitation “is not just limited to” cost fluctuations). As such, we see no need to further construe this claim limitation. 2. “determine . . . a charging schedule for the vehicle” Limitation 1[g] recites “determine, based at least on the one or more charging preferences and at least one current value of a dynamic attribute of an electric charge provider, a charging schedule for the vehicle.” Independent claim 8, 15, and 22 recite a materially identical limitation. Tesla submits that this limitation should not be construed as a means-plus- function limitation under 35 U.S.C. § 112(6). See Pet. 5. Charge Fusion agrees that “nothing in the claim invokes [§] 112(6).” PO Resp. 16. As such, we discern no dispute regarding the meaning of this claim limitation.” slip op. at 8

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

    “Initially, we note that, as claimed, there is no express restriction on the manner in which the “amount” or “charge” is specified or otherwise expressed. Indeed, the Specification uses both “desired charge percent level” and “desired charge range level” as alternative ways for a user to specify an “amount of charge.” Ex. 1001, 14:53–15:8 (emphases added). The Specification defines “desired charge range level” as meaning “a desired distance to travel.” Id. at 15:3–8. Elsewhere, the Specification describes that a user may specify the amount of charge as follows: “the user may indicate a desired charging level (and/or a desired charging level may be automatically calculated) based on a desired distance of travel.” Id. at 19:49–57 (emphasis added). More specifically, annotated Figure 7 of the ’987 patent, reproduced below, demonstrates how a user may select “amount of charge” in terms of a desired mileage range 720 or a percentage level 718. See Pet. Reply 2. As shown in red, annotated Figure 7 illustrates that a user selects “desired charge level 720” on “vehicle charge indicator 714” by moving a slider to a value specified in “miles” (e.g., 110 miles). The Specification, after discussing selecting a desired charge percent level 718, explains: The user may also or alternatively view and/or change the desired charge range level 720. An estimate of how far the vehicle can travel on a given charge amount (which may be a general average and/or may be computed based on a specific itinerary and/or past driving habits) can be determined, for example, and utilized to express the desired charge level in terms of distance capable of being traveled. In such a manner, for example, a user may determine a desired distance to travel (e.g., how far it is from home to work or vice versa) and may set the desired charge range level 720 to match the desired distance. Ex. 1001, 14:65–15:8. Thus, the Specification confirms that “amount of charge” may be expressed in terms of a desired mileage as well as a desired percentage level.” slip op. at 11

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

    “We disagree. Charge Fusion’s reliance on Wonderland is misplaced and does not support the proposition for which it is cited. In Wonderland, the district court denied the accused infringer’s motion for summary judgment of invalidity, in part, because genuine issues of material fact existed as to whether there was sufficient motivation to combine the prior art. Wonderland, 988 F. Supp. 2d at 511. As such, the district court’s Wonderland decision does not constitute a final ruling on the motivation to combine issue, and the Federal Circuit’s summary affirmance of the district court’s ruling neither addresses the issue nor reflects how the issue was resolved at trial. See Wonderland NurseryGoods Co. v. Thorley Indus., LLC, 644 F. App’x 1011 (Fed. Cir. 2016). Moreover, contrary to Charge Fusion’s assertion, Tesla correctly notes that although Ferro refers to wireless charging, it provides no implementation details. Ex. 1004 ¶ 36; Ex. 2006, 54:8–55:9. Nonetheless, Ferro does describe manual options for initiating charging, and Tesla’s expert credibly testifies that one of ordinary skill in the art would have been motivated to apply Oyobe’s vehicle sensor to allow a user to initiate Ferro’s charging methods more easily without having to leave the vehicle. See Ex. 1003 ¶¶ 146, 151, 152 (citing Ex. 1004 ¶ 109). Accordingly, we find that Tesla establishes that one of ordinary skill in the art would have been motivated to incorporate Oyobe’s use of a sensor to establish presence of a vehicle near a charging station into Ferro’s system.” slip op. at 17

  Patent outcomesUS 11,631,987 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 11,631,987
• Tesla, Inc. v. Charge Fusion Technologies, LLCAll claims unpatentable
  PTAB · Jul 13, 2026 · IPR2025-00152 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1–17 are unpatentable as obvious: claims 1–4, 6–9, and 11–14 over Sutardja, Donnelly, and Letendre; claims 5, 10, and 15 with Seelig; claims 16 and 17 with Knockeart.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of one of ordinary skill in the art at the time of the invention. Tesla submits that one of ordinary skill in the art would have had at least a bachelor’s degree in electrical or mechanical engineering (or an equivalent field) and at least two years of work experience involving automotive systems, including electric vehicle power management. . . . Additional industry experience or technical training may offset less formal education, 1 US 2008/0136371 A1, pub. Jun. 12, 2008 (Ex. 1011, “Sutardja”). 2 US 7,124,691 B2, iss. Oct. 24, 2006 (Ex. 1006, “Donnelly”). 3 Steven E. Letendre, The V2G Concept: A New Model for Power? PUBLIC UTILITIES FORTNIGHTLY, Feb. 15, 2002, at 16 (Ex. 1007, “Letendre”). 4 US 5,654,621, iss. Aug. 5, 1997 (Ex. 1078, “Seelig”). 5 US 6,622,083 B1, iss. Sep. 16, 2003 (Ex. 1010, “Knockeart”). while advanced degrees or additional formal education may offset lesser levels of industry experience. Pet. 2–3 (citing Ex. 1003 ¶ 29). Charge Fusion “takes no position with respect to Petitioner’s proposed level of ordinary skill in the art.” PO Resp. 9. For purposes of our analysis, we apply Tesla’s proposed level of ordinary skill, which we find to be consistent with the problems addressed in the ’788 patent and the prior art. B. Claim Interpretation” slip op. at 6

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

    “shown in Figure 7 of the ’788 patent. Pet. 4–5. Charge Fusion responds that Tesla’s proposed construction should be rejected because it “wrongly import[s] embodiments from the specification.” PO Resp. 14–16. We discern no dispute over the meaning of “unitary vehicle charge indicator” because, contrary to what Charge Fusion argues, Tesla does not contend that this limitation is “required to be limited to” the bar graph embodiment of Figure 7, only that it “at least includes” that embodiment. Compare Pet. 5, with PO Resp. 14–16. Tesla also argues that the “first” and “second” portions of the unitary vehicle charge indicator—which indicate the charged and uncharged capacities of the battery—recite merely “communicative content,” and thus, are “not entitled to any patentable weight” because they are directed to nonfunctional printed matter. Pet. 5–7 (citing various case law). At the same time, however, Tesla maintains that “[r]egardless, Donnelly teaches a bar graph indicating the amount of charge and uncharged capacity.” Pet. Reply 11–12 (citing Pet. 33–34); see also Hrg. Tr. 74:22–25, 75:9–11. For reasons expressed below, we agree that Tesla persuasively demonstrates that the asserted combination teaches the “unitary vehicle charge indicator element” as claimed and construed by Charge Fusion. Accordingly, we need not decide the printed matter issue.” slip op. at 8

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

    “Initially, we note that, as claimed, there is no express restriction on the manner in which the “amount” or “charge” is specified or otherwise expressed. Indeed, the Specification uses both “desired charge percent level” and “desired charge range level” as alternative ways for a user to specify an “amount of charge.” Ex. 1001, 14:63–15:18 (emphases added). In particular, the Specification defines “desired charge range level” as meaning “a desired distance to travel.” Id. at 15:8–18. Elsewhere, the Specification describes that a user may specify the amount of charge as follows: “the user may indicate a desired charging level (and/or a desired charging level may be automatically calculated) based on a desired distance of travel.” Id. at 19:59–67 (emphasis added).” slip op. at 9

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

    “full charge” for the battery, and thus, Tesla fails to explain how the combination of Sutardja with Donnelly’s battery bar graph image “would allow a user to select a specific amount of charge or how this would result in a unitary vehicle charge indicator,” as claimed. PO Resp. 30. According to Charge Fusion, “[l]imiting the single option of ‘full charge’ as described in Sutardja would defeat the purpose of implementing a slider” as taught by Donnelly. Id. (citing Ex. 2008 ¶ 72). We disagree. Charge Fusion’s argument rests on the mistaken premise that Sutardja only contemplates selecting a full amount of charge for the battery and not an amount below a full charge, i.e., a partial charge. But that is not what Sutardja says. More accurately, Sutardja teaches that the user specifies the amount of charge—"The user interface module 108 may comprise a key pad, a display, a microphone, and/or a speaker (all not shown). A user of the vehicle 102-1 may use the user interface module 108 to set charging parameters for charging the battery 14.” Ex. 1011 ¶ 243. Elsewhere, Sutardja teaches that the user may set a “predetermined level” of charge— The charge monitoring module 150 may inform the control module 112 when the battery 14 is charged to a predetermined level (e.g., full charge) that may be indicated in the charging parameters. Subsequently, the charge monitoring module 150 may stop charging the battery 14 by deactivating the converter 156 and the charging module 152. The power meter 24 may measure the amount of power received from the utility company 23 during the charging operation. Id. ¶ 270 (emphases added). Although that passage indicates that a “full charge” is an example of a “predetermined level” of charge, nowhere does it exclude the selection of a lesser amount. Indeed, the passage contemplates the ability to “stop charging the battery,” which indicates that selection of the predetermined level may be less than a full charge. Id. Thus, we are not persuaded by Charge Fusion’s argument to the contrary. Rather, in our view, Tesla demonstrates by a preponderance of the evidence that the Sutardja-Donnelly combination teaches a “unitary vehicle charge indicator” that includes at least “first” and “second” portions and that one of ordinary skill in the art would have had reason to successfully combine their respective teachings in a manner that allows a user to predetermine, i.e., specify, an amount of charge. slip op. at 17

  Patent outcomesUS 11,990,788 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 11,990,788
• GD Energy Products, LLC v. Kerr Machine CompanyAll claims unpatentable
  PTAB · Jun 29, 2026 · PGR2025-00031 · APJ Ryan H Flax · PGR · Final written decision

  Claims 1–14 are unpatentable as obvious under each of four asserted grounds: Kerr; Aplex and Stanton; Blume, Stanton, and Wilkinson; and the sale of the Kerr Pump.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The person of ordinary skill in the art would have a minimum of a bachelor’s degree in mechanical or petrochemical engineering, or a comparable engineering discipline, and a minimum of 3-5 years of work experience in the design and/or manufacturing of reciprocating pumps and valves, including fluid ends and/or comparable high pressure fluid components, for industrial applications, including for use in the oil and gas industry. See, e.g., EX1003, ¶32.” slip op. at 12

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

    “[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We decline to expressly construe any claim language. slip op. at 12

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

    “Regarding the combining of Aplex and Stanton, Petitioner asserts that the ordinarily skilled artisan would have understood that providing a packing/stuffing arrangement, as taught by Stanton, within a fluid end housing, as taught by Aplex, would improve pressure and fluid isolation compared with an arrangement where the packing was bolted to the outside of the fluid end as in Aplex unmodified. Pet. 66 (citing Ex. 1003 ¶¶ 189, 236). Patent Owner does not dispute this rationale. We find this to be a reason, with rationale underpinning, why the person of ordinary skill in the art would have combined these references with a reasonable expectation of success.” slip op. at 29

  • Adverse judgmentOther

    “The record indicates that Patent Owner has statutorily disclaimed claim 15 as of April 28, 2025. Ex. 2206.” slip op. at 8

  Patent outcomesUS 12,152,582 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,152,582
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

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

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

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

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

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

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

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

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

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

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

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

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

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

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

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

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

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

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

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

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

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139

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.