- Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00572 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 because the prior-art combinations teach the limitations at issue under the Federal Circuit’s construction of “style.”
RulingsRemand decision- RemandDecided for petitioner
“We agree with Petitioner. Lemay Web discloses that the style settings of width, height, pause, and repeat for the pocket watch images can be changed by changing the values for width, height, pause, and repeat in the HTML file. Ex. 1004, 89–90. This results in changing the size, duration, and frequency of the display of the multiple pocket watch image objects without changing the image files or the Java applet. Id. That is, the 12 image objects of Lemay Web can be uniformly formatted by applying and altering the style settings of the HTML file, which is stored separately from the image objects and the Java applet. Id. at 88– 89. In our Final Written Decision, we wrote that “Lemay Web discloses that the image files that are displayed as the animation object are separate from the HTML.” Ex. 1004, 88–89.” Dec. 22. The Federal Circuit wrote that “how the Board evaluated what constitutes separateness in the prior art software is less than clear.” Opinion, 13 n.7. To be clear, the animation of Lemay Web comprises 12 different pocket watch image objects. Ex. 1004, 89. The HTML file that contains the style settings for the 12 different pocket watch image objects is stored separately from the 12 different pocket watch image objects. Id. at 88–91. The style of the 12 different pocket watch image objects can be altered by changing the values of the style settings in the separate HTML file, thus allowing the style to be uniformly applied to each of the associated 12 pocket watch image objects when the pocket watch image objects are created on the web page. Id.; see Ex. 1030 ¶¶ 28–29; Dec. 21–22. In conclusion for issue (B), we find that Lemay Web teaches applying the style located in the separate HTML file to the pocket watch image objects when creating the pocket watch image objects on the web page. Therefore, Lemay Web’s style is “defined separately from any single object” as claimed. Because Lemay Web’s style can be applied to one object and more than one object and Lemay Web’s style is defined separately from any single object, we find that the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style.”” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“As directed by the Federal Circuit, we determine whether the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style,” but otherwise do not revisit our analysis of claim 1. Remand Opinion 7, 13–14. The Federal Circuit construed “style” to mean “a collection of one or more settings that is defined separately from any single object but can be associated with one or more objects,” with the understanding that “associated with one or more” means capable of being associated with both one object and more than one object. Id. at 14.” slip op. at 4
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“Because the Specification discloses that data defines an object, we construe the plain meaning of the claimed “object,” read in light of the Specification of the ’168 patent, as encompassing data that defines the object. See Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005) (The “specification . . . is the single best guide to the meaning of a disputed term.”); Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996); (Excluding an embodiment in the specification from “the scope of the patent claim . . . is rarely, if ever, correct.”). Further, because the Specification discloses that data defines image objects, and that objects include images, we construe the plain meaning of the claimed “image object,” read in light of the Specification, as encompassing data that defines an image, such as one of the 12 different pocket watch images of Lemay Web.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“What you see in the bottom right is an excerpt from the Lemay Web book . . . [y]ou can still use the Java applet just by putting this applet code into your HTML file. So this shows the animator class is going to be run within height or how big a window within the browser should be allocated in this applet. You can . . . tell the animator class how long to pause in between each image. So that’s a style that’s being applied to all of the multiple images that make up this animation. Ex. 2029, 746:23–747:7. Patent Owner then asked GoDaddy’s expert “for each unique animation you want to create with this animator class that’s shown here, you’re going to have to have a unique set of HTML code with the settings along with any of the images you’ll want to associate with the animator class, right?” Ex. 2030, 793:7–11. GoDaddy’s expert testified, with reference to Exhibit 2027, 80, that “Yeah. I’m not a hundred percent sure I understand your question, but yes, if you had six animations on a page, for example, you’d have six blocks of markup that looked like the markup at the bottom right of that slide, starting with applet.” Id. at 793:12–16. In addressing Patent Owner’s question about “each unique animation,” GoDaddy’s expert provided a hypothetical example of a web page having six animations, and explained that the six animations have six blocks of markup. Ex. 2030, 793:13–16. We find that this testimony means that if a web page has six unique animations, then for each unique animation, a corresponding HTML file contains the style settings for the image objects of that animation, such that the “six animations on a page . . . have six blocks of markup.” Id. We find that the subsequent testimony of GoDaddy’s expert cited by Patent Owner is consistent with the expert’s initial testimony that Lemay Web’s style is “applied to all of the multiple images that make up this animation.” Ex. 2029, 747:5–7. We also find that the subsequent testimony is consistent with and supported by the disclosure of Lemay Web, which teaches that an animation has a set of image files and is added to a Web page using the Animator applet. Ex. 1004, 88 (“[Y]ou’ll learn just enough about Java applets to set up animation on your Web page. . . . To create animation using Java and the Animator applet, you’ll need . . . [a] set of image files . . . that make up your animation.”); see id. at 88–91. That is, Lemay Web, consistent with the testimony of GoDaddy’s expert, discloses that the style settings for the animation of the pocket watch in the HTML file are uniformly applied to the 12 pocket watch image objects. Id. at 88–91.” slip op. at 17
Patent outcomesUS 7,594,168 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,594,168 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00597 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 over both listed prior art combinations; Lemay Web teaches the claimed style under the Federal Circuit’s construction.
RulingsRemand decision- RemandOther
“As directed by the Federal Circuit, we determine whether the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style,” but otherwise do not revisit our analysis of claim 1. Remand Opinion 7, 13–14. The Federal Circuit construed “style” to mean “a collection of one or more settings that is defined separately from any single object but can be associated with one or more objects,” with the understanding that “associated with one or more” means capable of being associated with both one object and more than one object. Id. at 14.” slip op. at 4
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We agree with Petitioner. As discussed above, the plain meaning of an “image object” read in light of the Specification encompasses data that defines an image, such as each of the 12 different pocket watch images of Lemay Web. Ex. 1004, 89–90. Therefore, the HTML file of Lemay Web, which specifies attributes including width, height, pause value, and repeat value of the pocket watch image objects, is “capable of being applied to more than one” image object, such as each of the 12 different pocket watch image objects described by Lemay Web. Id.” slip op. at 11
- Strike new argumentNew argument consideredDecided for petitioner
“We agree with Petitioner. The Board and Petitioner understood the meaning of “or” in the phrase “one or more objects” in Patent Owner’s proposed construction of style as meaning that “a style . . . can be associated with just one object.” Dec. 22; see Reply 4–5. The Federal Circuit “ultimately conclude[d] that Express Mobile’s proposed construction, with ‘or’ properly interpreted,” means “that the claimed ‘style’ must be capable of being applied to both one and more than one ‘object,’” and “remand[ed] for further proceedings in view of the correct claim construction.” Remand Opinion 13. In doing so, the Federal Circuit stated that “[i]t may be that under the correct claim construction, the Board finds that Lemay Web teaches the claimed ‘style’; however, that is still an open fact question for the Board to decide in the first instance.” Id. at n.6. Given that the Federal Circuit has ordered the Board to determine whether the prior art teaches the claimed “style” under the proper construction, we find that Petitioner’s arguments on this issue are timely.” slip op. at 6
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“Contrary to Patent Owner’s contention, the Specification discloses, “Data that defines text button, image, paragraph, or other parent objects . . . can be stored in two-dimensional arrays (by web page and by object number).” Ex. 1001, 22:11–13 (emphasis added). The Specification further discloses that “objects . . . include colors, fonts, images, audio clips, video clips, text areas, URLs and thread objects.” Id. at 2:16–17 (emphasis added); see id. at 8:40. We highlight that the Specification’s use of “object” is consistent with a definition of “object” in the computing art at the time of the invention, which is “(2) A passive entity that contains or receives data; for example, bytes, blocks, clocks fields, files . . . .” George McDaniel, IBM Dictionary of Computing, McGraw-Hill, Inc. 1994, p. 471 (Ex. 3001). Because the Specification discloses that data defines an object, we construe the plain meaning of the claimed “object,” read in light of the Specification of the ’168 patent, as encompassing data that defines the object. See Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005) (The “specification . . . is the single best guide to the meaning of a disputed term.”); Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996); (Excluding an embodiment in the specification from “the scope of the patent claim . . . is rarely, if ever, correct.”). Further, because the Specification discloses that data defines image objects, and that objects include images, we construe the plain meaning of the claimed “image object,” read in light of the Specification, as encompassing data that defines an image, such as one of the 12 different pocket watch images of Lemay Web.” slip op. at 8
Patent outcomesUS 7,594,168 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,594,168 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2021-01226 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under § 103 over the asserted combinations because the prior art teaches the limitations under the proper construction of “style.”
RulingsRemand decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“Contrary to Patent Owner’s contention, the Specification discloses, “Data that defines text button, image, paragraph, or other parent objects . . . can be stored in two-dimensional arrays (by web page and by object number).” Ex. 1001, 22:11–13 (emphasis added). The Specification further discloses that “objects . . . include colors, fonts, images, audio clips, video clips, text areas, URLs and thread objects.” Id. at 2:16–17 (emphasis added); see id. at 8:40. We highlight that the Specification’s use of “object” is consistent with a definition of “object” in the computing art at the time of the invention, which is “(2) A passive entity that contains or receives data; for example, bytes, blocks, clocks fields, files . . . .” George McDaniel, IBM Dictionary of Computing, McGraw-Hill, Inc. 1994, p. 471 (Ex. 3001). Because the Specification discloses that data defines an object, we construe the plain meaning of the claimed “object,” read in light of the Specification of the ’168 patent, as encompassing data that defines the object. See Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005) (The “specification . . . is the single best guide to the meaning of a disputed term.”); Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996); (Excluding an embodiment in the specification from “the scope of the patent claim . . . is rarely, if ever, correct.”). Further, because the Specification discloses that data defines image objects, and that objects include images, we construe the plain meaning of the claimed “image object,” read in light of the Specification, as encompassing data that defines an image, such as one of the 12 different pocket watch images of Lemay Web.” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“We agree with Petitioner. As discussed above, the plain meaning of an “image object” read in light of the Specification encompasses data that defines an image, such as each of the 12 different pocket watch images of Lemay Web. Ex. 1004, 89–90. Therefore, the HTML file of Lemay Web, which specifies attributes including width, height, pause value, and repeat value of the pocket watch image objects, is “capable of being applied to more than one” image object, such as each of the 12 different pocket watch image objects described by Lemay Web. Id.” slip op. at 11
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Ex. 2030, 793:7–11. GoDaddy’s expert testified, with reference to Exhibit 2027, 80, that “Yeah. I’m not a hundred percent sure I understand your question, but yes, if you had six animations on a page, for example, you’d have six blocks of markup that looked like the markup at the bottom right of that slide, starting with applet.” Id. at 793:12–16. In addressing Patent Owner’s question about “each unique animation,” GoDaddy’s expert provided a hypothetical example of a web page having six animations, and explained that the six animations have six blocks of markup. Ex. 2030, 793:13–16. We find that this testimony means that if a web page has six unique animations, then for each unique animation, a corresponding HTML file contains the style settings for the image objects of that animation, such that the “six animations on a page . . . have six blocks of markup.” Id. We find that the subsequent testimony of GoDaddy’s expert cited by Patent Owner is consistent with the expert’s initial testimony that Lemay Web’s style is “applied to all of the multiple images that make up this animation.” Ex. 2029, 747:5–7. We also find that the subsequent testimony is consistent with and supported by the disclosure of Lemay Web, which teaches that an animation has a set of image files and is added to a Web page using the Animator applet. Ex. 1004, 88 (“[Y]ou’ll learn just enough about Java applets to set up animation on your Web page. . . . To create animation using Java and the Animator applet, you’ll need . . . [a] set of image files . . . that make up your animation.”); see id. at 88–91. That is, Lemay Web, consistent with the testimony of GoDaddy’s expert, discloses that the style settings for the animation of the pocket watch in the HTML file are uniformly applied to the 12 pocket watch image objects. Id. at 88–91. Contrary to Patent Owner’s contention, the testimony of GoDaddy’s expert further supports our finding that the style settings in the HTML file of Lemay Web are applied to the multiple image objects that make up the animation. Patent Owner does not identify anything else from the district court trial connected to the “style” issue raised by the Federal Circuit. We conclude that the jury verdict does not change our decision here. IV. CONCLUSION” slip op. at 18
Patent outcomesUS 7,594,168 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,594,168 - PTAB · Jan 15, 2026 · IPR2025-01231 · APJ Mary C Hoffman · IPR · Institution
The Board instituted IPR on claims 1–13 on all asserted grounds, finding a reasonable likelihood that at least one challenged claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner
“petition identifies all real parties in interest. 35 U.S.C. § 312(a)(2). Whether an unnamed party is a real party in interest “is a highly fact-dependent question.” See Applications in Internet Time, LLC v. RPX Corp., 897 F.3d 1336, 1351, 1360 (Fed. Cir. 2018) (“AIT”); Ventex Co., Ltd. v. Columbia Sportswear N. Am., Inc., IPR2017-00651, Paper 152 at 4–5 (PTAB Jan. 24, 2019) (precedential) (citing Worlds Inc. v. Bungie, Inc., 903 F.3d 1237, 1242 (Fed. Cir. 2018)); Consolidated Trial Practice Guide, 13 (2019), https://www.uspto.gov/sites/default/files/documents/tpgnov.pdf (CTPG). “A common consideration is whether the non-party exercised or could have exercised control over a party’s participation in a proceeding.” CTPG at 16. Other considerations include whether the non-party is funding or directing the proceeding; the non-party’s relationship with the petitioner; the non-party’s relationship to the petition itself, including the nature and/or degree of involvement in the filing; and the nature of the entity filing the petition. Id. at 17–18.” slip op. at 8
- Skill levelSkill level board ownOther
“person of ordinary skill in the art (“POSITA”) “would have at least a bachelor’s degree in electrical engineering or a related field and at least two years of experience with lighting technology.” Pet. 2 (citing Ex. 1017 ¶ 35). Petitioner makes additional contentions about what a POSITA would have understood. Id. (“A POSITA would understand that all types of cameras (e.g., analog and digital, photo and video) generally involve the same lighting considerations . . . . [and] that it is important to provide light that evenly illuminates the target subject or object to minimize reflected glare and shadows.”). Patent Owner contends that a POSITA would have at least: (a) a bachelor’s degree in electrical engineering, optical engineering, or a related field; (b) two years of practical experience in designing and developing lighting systems, particularly those integrated with electronic devices such as webcams or computer monitors; and (c) knowledge of user-interface considerations for consumer electronics . . . . Additional experience can substitute for education and vice versa. Prelim. Resp. 12 (citing Ex. 2036 ¶ 48). Patent Owner disputes Petitioner’s contentions regarding what a POSITA would have understood. Prelim. Resp. 12–13 (“[O]ne of ordinary skill in the art would have understood that analog and digital cameras have different operating principles and lighting requirements [and] Petitioner’s lack of appreciation for the suitability and unsuitability of different lights for different applications infects and dooms its invalidity analysis.” (citing Ex. 2036 ¶¶ 36–47)). and years of experience required for a POSITA. Pet. 2; Prelim. Resp. 12. For purposes of this Decision, we consider a person of ordinary skill in the art to have a bachelor’s degree in electrical engineering or related field and two years of practical experience in lighting technology, and that additional experience may substitute for education and vice versa, which is consistent with the level of skill reflected in the ’729 patent and prior art of record. See Exs. 1001, 1005–1010, 1012–1015; see also Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and need for testimony is not shown” (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985))).” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Patent Owner agrees that the Board need not formally construe any claim terms in order to adjudicate the merits of the Petition and argues Petitioner fails to show unpatentability of any claim under any reasonable construction of the claims. Prelim. Resp. 13 (citing Ex. 2036 ¶ 51). We determine that no express claim construction is necessary to determine whether institution is warranted in this proceeding. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (holding that only terms in controversy must be construed “and only to the extent necessary to resolve the controversy”) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 14
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“claimed subject matter and the prior art are “such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). When a ground in a petition is based on a combination of references, we consider “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” Id. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We base our obviousness inquiry on factual considerations including (1) the scope and content of the prior art, (2) any differences between the claimed subject matter and the prior art, (3) the level of skill in the art, and (4) any objective indicia of obviousness or non-obviousness that may be in evidence.14 See Graham, 383 U.S. at 17–18.” slip op. at 24
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,841,729 - Toyota Motor Corp. v. Emerging Automotive LLCAll claims unpatentablePTAB · Nov 19, 2025 · IPR2024-00814 · APJ Frances L Ippolito · IPR · Final written decision
Claims 1, 2, and 4–20 are unpatentable as obvious over the stated combinations of Rector, Kleve, and, for certain claims, additional references.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art (“POSITA” or “POSA”) at the time of the invention of the ’244 patent “would have had at least a Bachelor’s degree in electrical engineering, computer science, or closely related field, with at least two-to-four years’ experience in cloud services for settings customization” and that computer science, or equivalent) could substitute for professional experience and vice-versa.” Pet. 12 (citing Ex. 1005 ¶ 89). Patent Owner does not address the level of ordinary skill in the art. See, generally PO Resp. Patent Owner’s Declarant, Dr. Malek, adopts the definition proffered by Petitioner and its Declarant, Dr. Almeroth. Ex. 2001 ¶ 37. We adopt Petitioner’s proposal as it is reasonable and consistent with the prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“Patent Owner asserts that the term “transferring is configured to instruct” should be construed according to its plain and ordinary meaning – the limitation.” PO Resp. 11. Patent Owner contends that the challenged claims require more than that the server is capable of the recited transferring (e.g., claims 1 and 17), and must be configured to accomplish the specific purpose of the claims. Id. at 12–17. Our analysis and the outcome of this dispute, however, would not change even if we were to adopt Patent Owner’s construction. Therefore, upon review of the entire record, including arguments by the parties and the relied upon evidence, we determine no terms require express construction to reach our decision. 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
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“With regard to this testimony, we note that Dr. Malek does not provide an underlying basis for these statements to support his conclusion that it is “common knowledge” that distributed software systems are less secure than local software systems. Id. In fact, when viewed with Kleve, Dr. Malek’s testimony appears to contradict Kleve’s express teaching that the “system may be further extended to facilitate the virtual key with additional security by requiring remote credential verification at the vehicle . . . by the VCS, using a server, or allowing the Owner to verify the Temporary User’s request.” Ex. 1007 ¶ 49 (emphases added). With regard to Kleve’s disclosure, Dr. Malek further testifies that [a] POSITA would understand that in Kleve credential authorization can be performed by: (1) VCS, (2) server, or (3) owner . . . . While Kleve discloses the verification can be performed by any of these entities, it states the client-side verification at the vehicle using VCS provides additional security. A POSITA would not have been motivated to modify side verification. Rector already uses the more secure client-side verification. Ex. 2003 ¶ 79 (emphases added). Dr. Malek, however, does not explain how Kleve’s express teachings limit “additional security” to client-side verification with VCS. Id. In fact, Kleve expressly discloses the opposite. Kleve teaches that the additional security may be provided by a remote credential certification that “may be done by the VCS, using a server, or allowing the Owner to verify the Temporary User’s request.” Ex. 1007 ¶ 49 (emphasis added). Kleve further teaches that the Temporary User may enter “a credential verification password at the vehicles touchscreen visual display while having the VCS, server, or owner compare and verify authorization.” Id. (emphasis added). Even Dr. Malek acknowledges that the verification can be performed by “any of these entities,” including the server. Id. We further note Dr. Almeroth testifies that “[t]he server-side verification may be done above and beyond any verification that takes place locally. The server-side verification could also be done as a check on local verification.” Ex. 1005 ¶ 122. This testimony is consistent with and supported by Kleve’s disclosure, which expressly states that “additional security” includes remote credential verification at the vehicle using a server. Ex. 1007 ¶ 49. As such, we credit Dr. Almeroth’s testimony as his testimony better supported by prior art disclosure.” slip op. at 28
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“With regard to this testimony, we note that Dr. Malek does not provide an underlying basis for these statements to support his conclusion that it is “common knowledge” that distributed software systems are less secure than local software systems. Id. In fact, when viewed with Kleve, Dr. Malek’s testimony appears to contradict Kleve’s express teaching that the “system may be further extended to facilitate the virtual key with additional security by requiring remote credential verification at the vehicle . . . by the VCS, using a server, or allowing the Owner to verify the Temporary User’s request.” Ex. 1007 ¶ 49 (emphases added). With regard to Kleve’s disclosure, Dr. Malek further testifies that [a] POSITA would understand that in Kleve credential authorization can be performed by: (1) VCS, (2) server, or (3) owner . . . . While Kleve discloses the verification can be performed by any of these entities, it states the client-side verification at the vehicle using VCS provides additional security. A POSITA would not have been motivated to modify side verification. Rector already uses the more secure client-side verification. Ex. 2003 ¶ 79 (emphases added). Dr. Malek, however, does not explain how Kleve’s express teachings limit “additional security” to client-side verification with VCS. Id. In fact, Kleve expressly discloses the opposite. Kleve teaches that the additional security may be provided by a remote credential certification that “may be done by the VCS, using a server, or allowing the Owner to verify the Temporary User’s request.” Ex. 1007 ¶ 49 (emphasis added). Kleve further teaches that the Temporary User may enter “a credential verification password at the vehicles touchscreen visual display while having the VCS, server, or owner compare and verify authorization.” Id. (emphasis added). Even Dr. Malek acknowledges that the verification can be performed by “any of these entities,” including the server. Id. We further note Dr. Almeroth testifies that “[t]he server-side verification may be done above and beyond any verification that takes place locally. The server-side verification could also be done as a check on local verification.” Ex. 1005 ¶ 122. This testimony is consistent with and supported by Kleve’s disclosure, which expressly states that “additional security” includes remote credential verification at the vehicle using a server. Ex. 1007 ¶ 49. As such, we credit Dr. Almeroth’s testimony as his testimony better supported by prior art disclosure.” slip op. at 28
Patent outcomesUS 11,396,244 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,396,244 - Exotec Product France SAS / Exotec North America Inc. et al. v. Opex CorporationAll claims unpatentablePTAB · Oct 28, 2025 · IPR2024-00850 · APJ Arthur M Peslak · IPR · Final written decision
Claims 1, 3–12, 14, and 23–27 are unpatentable as obvious over Raizer and Hangzhou.
RulingsFinal written decision- Skill levelOther
“B. Level of Ordinary Skill in the Art We consider the asserted grounds of unpatentability in view of the” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction Neither Petitioner nor Patent Owner proposes an express construction” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableMotivation foundUnpatentable
“that it would improve similar devices in the same way, using the technique is obvious unless its actual application is beyond his or her skill.” KSR, 550 U.S. at 417. In this case, we must determine whether one of ordinary skill in the art would recognize that Hangzhou’s disclosure of driving its auto-guided trolleys 200 under shelves 100 would improve the operation of Raizer’s system in the same way. For us to resolve this question in Petitioner’s favor, Petitioner must provide “some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” Id. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). However, bodily incorporation, i.e., “an actual physical substitution of” Hangzhou’s auto-guided trolleys or operating software into Raizer’s system, is not required. See In re Mouttet, 686 F.3d 1322, 1332 (Fed. Cir. 2012) (“It is well-established that a determination of obviousness based on teachings from multiple references does not require an actual, physical substitution of elements.”); In re Nievelt, 482 F.2d 965, 968 (CCPA 1973) (“Combining the teachings of references does not involve an ability to combine their specific structures.”).” slip op. at 23
Patent outcomesUS 11,472,632 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,472,632 - Toyota Motor Corp. v. Emerging Automotive LLCSome claims unpatentablePTAB · Oct 21, 2025 · IPR2024-00786 · APJ Frances L Ippolito · IPR · Final written decision
Claims 10, 11, 13–16 were held unpatentable: claims 10, 11, 13, 15, and 16 as anticipated by Xiao, and claim 14 as obvious over Xiao and Singh.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“arguments, we agree with Patent Owner’s proposed construction that requires the server to conduct a compatibility check. We start with the express claim language. Claim 10 recites: determining, by the server, applicable settings for the selected vehicle, the applicable settings being settings that are preferred to be set as identified from the user profile and are compatible with settings that are settable in the selected vehicle. Ex. 1001, 33:10–14 (emphases added). The express claim language requires that the server determine applicable settings. Those applicable settings, determined by the server, must also be compatible with vehicle settings. As such, the plain and ordinary meaning of the claim language expressly requires that the server make a determination of applicable settings that are defined as being compatible with vehicle settings.” slip op. at 14
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art (“POSITA”) at the time of the invention of the ’268 patent “would have had at least a Bachelor’s degree in electrical engineering, computer science, or closely related field, with at least two-to-four-years-experience in cloud services for settings customization, or a Master’s degree in electrical engineering, computer science, or equivalent.” Pet. 12 (citing Ex. 1009 ¶ 82). Patent Owner does not address the level of ordinary skill in the art. See, generally PO Resp. For purposes of this Decision, we adopt Petitioner’s proposal because it is reasonable and consistent with the prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable
“However, contrary to Dr. Almeroth’s testimony and Petitioner’s position, Xiao’s server already does not attempt to command vehicles to do things they cannot do. Xiao teaches that server 118 generates commands for command codes that exist and are settable in the vehicle. Ex. 1010 ¶¶ 102– 103. As such, if there is no corresponding automobile setting, then Xiao’s server would not list those command codes for retrieval and would not send a command based on that retrieved command code to control the automobile systems to achieve the operator’s desired settings because that command code is not in the database. Our understanding of Xiao is further supported by Dr. Almeroth’s testimony: By listing them in the table of automobile command code information 606, Xiao shows that there are particular settings compatible with particular automobiles and particular desired settings. Thus, Xiao demonstrates the necessarily present characteristic that certain settings (e.g., commands) are compatible with certain automobiles. Ex. 1009 ¶ 96 (emphases added). We note that Dr. Malek further explains “the nonsensical result achieved by the combination would be that Xiao’s server, at best, in response to the command request issued by the operator, could ‘look up’ a command code to apply a vehicle-specific setting to that automobile 112, only to find that there is ‘none.’” We agree with Dr. Malek that there is a “None” command code in Xiao’s database when Xiao’s database already stores settings that are known to be settable in a specific vehicle per the operator’s preferences. Ex. 2011 ¶ 135. Thus, based on the complete record, we determine that Petitioner has not demonstrated by a preponderance of the evidence that Xiao in combination with Hayashi render claim 10 obvious.” slip op. at 79
- BurdenNot shown unpatentable
“Anticipation is not an ipsissimis verbis test, but “[a] claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal, 814 F.2d at 631. Petitioner and Dr. Almeroth both acknowledge that Xiao discloses operators on the same account. Pet. 40–41; Ex. 1009 ¶ 170. But Petitioner and Dr. Almeroth do not explain sufficiently how Xiao discloses these operators have sub-user accounts. Petitioner further contends Xiao discloses plurality of accounts. Pet. Reply 18–19 (citing Ex. 1024, 33:1–44:10, 45:22–46:2); Ex. 1010 ¶ 65. Again, Petitioner has not adequately explained how the plurality of accounts includes sub-user accounts because Xiao discloses generally that multiple operators of a vehicle are on the same, single account. Ex. 1010 ¶ 66.” slip op. at 65
Patent outcomesUS 9,171,268 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,171,268 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00653 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution on all claims because the Petition did not show a reasonable likelihood that any challenged claim was unpatentable over the asserted grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“An inter partes review may be instituted only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’504 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Additionally, only terms that are in controversy need to be construed, and these need be construed only to the extent necessary to resolve the controversy. 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)). The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 9; Prelim. Resp. 4 (citing Ex. 2009 ¶ 72); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13
- Expert testimonyPetitioner expert discountedDecided for patent owner
“Ex. 1002 ¶ 47. As reflected above, Dr. Wooley’s testimony as to element [1.2] does not even assert that Cardamone discloses a tank, let alone one or more sensors disposed at a tank as recited in element [1.2]. Thus, Dr. Wooley’s testimony does not support Petitioner’s argument on this issue.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,726,504 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00652 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–23 and 25–30 were unpatentable over the asserted grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsDenied
“presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’403 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 10; Prelim. Resp. 4 (citing Ex. 2009 ¶ 73); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We agree with Patent Owner that the Petition fails to demonstrate that Kahn discloses element [1.2] because the evidence cited does not disclose a “first computer system being configured to provide remote control of the first pump or first valve” (i.e., a fluid-handling device). Kahn is directed to providing access to fluid sensing data and analyzing and providing visual information on that data, but Petitioner has not identified any disclosure of the capability to remotely control fluid-handling devices. See, e.g., Ex. 1005, code (54), 1:27–36, 2:50–3:2. More specifically, Kahn’s disclosures that Petitioner relies on for allegedly teaching remote control are deficient. We discuss each. First, Petitioner points to the following, “[f]or instance, as illustrated in FIG. 1C, a fluid control device such as a valve 15A is located on the input side of a sen[s]or unit 110.” Ex. 1005, 8:19–21, cited in Pet. 13. This portion of Kahn, however, does not disclose remote control. Second, Petitioner cites to the following: Finally, or in addition to, the communication unit 112B can include on-site alerts such as optical (indicator lights), audible alerts (e.g., alarm sounds), tactile (e.g., vibration of the unit) or can be interfaced to an appropriate control valve for simply shutting off the supply of fluid upon the detection of emergency events, for instance. Pet. 13 (citing Ex. 1005, 10:62–67). We agree with Patent Owner that this portion of Kahn teaches on-site alerts and local control of the fluid-handling device. See Prelim. Resp. 7. This portion of Kahn does not disclose remote control.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,294,403 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00651 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–3, 6, 7, and 9–20 were unpatentable over any asserted ground.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsDenied
“presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’680 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“target value” is part of a command that is sent from a computing device to a server and then to a controller. The controller then receives a measurement of the fluid by a sensor and determines whether the measurement satisfies the “target value.” If the measurement does not satisfy the “target value,” further operations are undertaken. The recited operation sequence makes clear that the plain and ordinary meaning of “target value” is not as Dr. Wooley opines because the particular operating condition that a device is in at a particular time is represented by the measurement taken by the sensor, 11 Some claim language less relevant to construing “target value” was omitted for ease of reference. which the controller then uses to determine whether the measurement satisfies the “target value.” Additionally, claim 1 recites that the “target value” is sent as part of a command to the controller. The “target value” is not sent to the controller from the sensor, as might be expected if the plain and ordinary meaning of “target value” were as Dr. Wooley opines. Petitioner and Dr. Wooley’s construction would also result in “target value” meaning effectively the same thing as the measurement of the fluid by the sensor, a concept that is separately recited in claim 1 and to which the “target value” is compared. The Specification of the ’680 patent does not support Petitioner’s understanding of the plain and ordinary meaning of “target value.” Although the Specification does not recite “target value,” it recites “target state,” and describes “target state” sufficiently to understand the plain and ordinary meaning of “target” as used in “target value” and “target state.” In particular, the ’680 patent explains that “[i]n some embodiments, the process 104 includes receiving, via a network interface, from a remote user device, (e.g., via a command-center server) a command to change a state of a fluid-handling device to a target state.” Ex. 1001, 11:48–51. This portion reflects that the command is seeking to change a state of a fluid-handling device to a target state. In other words, the “target value” or “target state” is not generally “the particular operating condition that a device is in at a particular time”; rather, it is a value or state that the fluid-handling device is desired to be in, as Patent Owner and Dr. Durham explain. Additionally, just as claim 1 recites a directional component for the “target value” to be sent to the controller in a command, so too does the Specification describe a “target state” as being sent in a command from a remote user device. Thus, the Specification clearly supports the plain and ordinary meaning proposed by Patent Owner and Dr. Durham and not the plain and ordinary meaning proposed by Petitioner and Dr. Wooley. slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“time-stamped process data, report exception therein to the remote host, and extract and transmit time-stamped process data to the remote host.” Ex. 1005, Abst. (emphases added). Almadi explains that its remote field systems must include a plurality of controller units “to issue commands to, and gather and process data from a plurality of field devices, including remote systems and instruments, . . . [and] a database server for the storage of process data retrieved from the remote subsystems and instruments.” Id. at 2:22–30 (emphases added). Based on these disclosures, we agree with Patent Owner that Petitioner has not established that Almadi discloses element [1.4]. Specifically, the teachings from Almadi identified by Petitioner refer to process data, which is data retrieved from the remote subsystems/field devices. Thus, we understand that Almadi’s teaching—of using an Ethernet switch to transmit “process data”—describes transmitting data from the remote subsystems/field devices. See Ex. 1005, 3:13–17, cited in Pet. 15. But claim 1 and particularly element [1.4], recites “sending, with the server, the target value to the network address [which identifies a controller of the fluid-handling device13] via the network,” which is different than sending process data from the field devices to the remote host or database server for storage.” slip op. at 19
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,175,680
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.