- Apple Inc. v. Smith Interface Technologies, LLCAll claims unpatentablePTAB · Jan 26, 2026 · IPR2024-01083 · APJ Sharon Fenick · IPR · Final written decision
Claims 1–3, 7, 9, 10, and 101 are unpatentable as obvious over Ahn, Chaudhri, and Hinckley.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“As Petitioner’s description of a person of ordinary skill appears commensurate with the subject matter before us, we apply Petitioner’s definition for purposes of this Decision. Also, the level of ordinary skill in the art can be evidenced by the references cited, and we find it commensurate with the cited references in this proceeding. 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).” slip op. at 8
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“We find that a person of ordinary skill in the art had knowledge that “linear menus are not easy to use on small devices, especially in mobile situations” because “[t]he limited screen space makes it difficult to display a large . . . linear menu while keeping items large enough to be easily selected” (Ex. 1028, 2) and that “[d]istance to and size of the target are important factors that give pie menus the advantage over traditional linear menus” (Ex. 2013, 2). See Ex. 1023 ¶¶ 31–33. Given that Hinckley explicitly describes using its radial menu in a mobile telephone, and given that a person of ordinary skill in the art had knowledge of the advantages and disadvantages of Hinckley’s radial menu, we find Dr. Terveen’s testimony that a person of ordinary skill in the art would have used Hinckley’s radial menu in Ahn’s mobile device more persuasive that Dr. Rosenberg’s testimony to the contrary, because Dr. Terveen’s testimony is consistent with the teachings of Hinckley and the knowledge of a person of ordinary skill in the art, whereas Dr. Rosenberg does not reconcile his testimony with Hinckley’s express disclosure of displaying a radial menu on the touch screen of a mobile telephone. See Ex. 1003 ¶¶ 56, 63–67; 1023 ¶¶ 31–33; Ex. 2006 ¶¶ 71–79; Ex. 1006 ¶¶ 43, 53, 56; Ex. 2009, 3; Ex. 2010, 2; Ex. 2013, 2. We find that a person of ordinary skill in the art had reason to conclude that implementing Hinckley’s radial menu in Ahn’s mobile device with limited screen space yields advantages such as distance to and size of the icons as well as associating a function with a direction that outweigh disadvantages such as having less icons than a linear menu. We find that combining the bezel gestures and associated bezel menu and radial menu of” slip op. at 31
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“structure already known in the prior art that is altered by the mere substitution of one element for another known in the field, the combination must do more than yield a predictable result.” KSR, 550 U.S. at 416. We find that altering Ahn’s device by substituting Hinckley’s bezel gestures and associated bezel and radial menus for Ahn’s technique of displaying menus does no more than yield the predictable results of (a) conserving screen real estate, (b) distinguishing bezel gestures from normal gestures so that the bezel gestures do not interfere with normal gestures and vice versa, (c) providing a novice mode to help a user learn the expert way of accessing the functionality of the bezel and radial menus, and (d) providing a user user as taught by Hinckley. Ex. 1006 ¶¶ 1, 40, 46, 77–80, 110; Ex. 1003 ¶¶ 63–67.” slip op. at 27
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightDecided for petitioner
“Patent Owner’s contention that several of the icons shown in Ahn’s menus would not benefit from a radial menu because of their assigned locations and functions (PO Resp. 42–51) do not address the Petition’s contention that a person of ordinary skill in the art would have used Hinckley’s bezel menu with icon 1712 that includes radial menu icon 1714 in Ahn’s device. See Pet. 46–55. Even if some icons would not benefit from a radial menu, we agree with Petitioner that a person of ordinary skill in the art would have recognized that other icons would benefit, such as the icons that display sub-menus when selected, as shown by icon 830 in figure 8C and the answer options icon shown in figure 17 of Ahn as well as icon 1714 shown in figure 17 of Hinckley, and would have therefore provided such icons with a radial menu icon. See Reply 2 (quoting KSR, 550 U.S. at 418); see id. at 15–16 (quoting Randall Mfg. v. Rea, 733 F.3d 1355, 1362 (Fed. Cir. 2013)). With respect to the specific locations assigned to the bezel menu icons and the radial menu icons, we agree with Petitioner that a manner that improves efficiency and usability, such as locating the radial menu icon away from the end points of the bezel menu as taught by figure 17 of Hinckley.” slip op. at 29
Patent outcomesUS 10,642,413 unpatentable§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,642,413 - Apple Inc. v. Smith Interface Technologies, LLCAll claims unpatentablePTAB · Jan 26, 2026 · IPR2024-01084 · APJ Jeffrey S Smith · IPR · Final written decision
Claims 1–4, 8–18, 22–30, and 34–39 are unpatentable as obvious over Shiplacoff and over Shiplacoff combined with Nan.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“have had a bachelor’s degree in computer science, computer engineering, electrical engineering, human-computer interaction, or a comparable field and at least two years of professional experience in the design and development of graphical user interfaces (GUIs), human-computer interfaces, or equivalents thereof. Pet. 4 (citing Ex. 1003 ¶ 22). Petitioner’s declarant, Loren Terveen, Ph.D., testifies that “[s]uch experience could be obtained through research and study in a graduate program or through comparable exposure through industry employment, and additional years of experience could substitute for the advanced-level degree.” Ex. 1003 ¶ 22. Patent Owner agrees with this definition. PO Resp. 13 (citing Dec. 5). As Petitioner’s description of a person of ordinary skill appears commensurate with the subject matter before us, we apply Petitioner’s definition for purposes of this Decision. Also, the level of ordinary skill in the art can be evidenced by the references cited, and we find it commensurate with the cited references in this proceeding. 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).” slip op. at 5
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“according to the Phillips standard.” Pet. 4. Patent Owner contends that under the plain language of claim 1, the “one or more criteria” is satisfied when a “movement parameter” of “the second input” is detected to be “above a movement threshold.” PO Resp. 14. Patent Owner contends that under the plain language of claim 27, the “second one or more criteria” is satisfied when “a duration parameter” of the “second input” is detected to be “above a duration threshold.” Id. at 15. Patent Owner contends that the plain language of limitations [1j] and [1k] requires an operation capable of detecting a second input by a second contact that includes movement across a display in a direction, determining whether the second input meets or does not meet the recited criteria, and triggers performance of each of the corresponding display actions as appropriate. Id. at 15–19. Patent Owner 15. Id. at 21–23. Patent Owner contends that the plain language of limitations [27d]–[27f] recited in claim 27 require an operation that enables the device to detect a second input by a second contact that includes movement across the display in a direction, determine whether the second input meets or does not meet the two recited criteria, and trigger performance of each of the recited display actions as appropriate. Id. at 19– 20. Patent Owner contends that for “the second input” recited in limitations [1j] and [1k], “the second input” must be detected in the same operational context. Id. at 23–24. In particular, Patent Owner contends that limitations [1j] and [1k], and similar limitations recited in claims 15 and 27, “require a single, common contact event as the starting point of the claimed logic operations.” Id. at 24; see id. at 25–26. We do not need to determine whether Patent Owner’s proposed constructions are correct, because under either Petitioner’s or Patent Owner’s proposed constructions, we find that the prior art would have rendered all challenged claims obvious as discussed below in our patentability analysis.” slip op. at 6
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“at 418; see also id. at 421 (“A person of ordinary skill is . . . a person of ordinary creativity, not an automaton.”). Patent Owner’s contention and the supporting testimony of Dr. Madisetti does not address Shiplacoff’s teaching of using a gesture, such as Shiplacoff’s flick gesture, to return to launch screen. We agree with Petitioner and Dr. Terveen in finding that Shiplacoff’s disclosure that “returning to the launch screen . . . is performed by performing a gesture” (Ex. 1004 ¶ 99) such as a flicking gesture (Ex. 1004 ¶¶ 126, 129; Ex. 1023 ¶ 13) teaches using a flicking gesture to return from home screen to launch screen. See Pet. 16, 22–24; Ex. 1003 ¶¶ 52–53, 59; Ex. 1023 ¶ 13; Reply 7–10. Because Dr. Terveen’s testimony is consistent with and supported by the teachings of Shiplacoff as a whole (in contrast to that of Dr. Madisetti), we credit the testimony of Dr. Terveen in finding that using a gesture to return from home screen to launch screen as taught by Shiplacoff, where the gesture is a flick gesture as taught by Shiplacoff, yields the predictable result of using a flick gesture to return from home screen to launch screen. Ex. 1023 ¶ 13; Ex. 1003 ¶¶ 52–61; KSR, 550 U.S. at 416.” slip op. at 21
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“articulate why a person of ordinary skill in the art would have used Shiplacoff’s flicking gesture to switch from full screen mode to the launch screen. PO Resp. 47–49. Petitioner contends that Shiplacoff’s swipe up gesture teaches limitation [1j] by including a movement parameter above a movement threshold. Pet. 17–23. Petitioner contends that Shiplacoff teaches that a user can perform another gesture to return to the home screen. Id. at 23. Petitioner contends that when a gesture different from the swipe up gesture is used to return to the home screen, a person of ordinary skill would have used a flicking gesture because the flicking gesture has a different movement parameter than the swipe up gesture, namely, a movement parameter that does not meet the movement threshold. Pet. 23– 24 (citing Ex. 1004 ¶¶ 99–102, 167; Ex. 1003 ¶¶ 60–61). We agree with Petitioner for the reasons given in the Petition and as discussed above. We reiterate that using a gesture to return from home screen to launch screen as taught by Shiplacoff, where the gesture is a flicking gesture as taught by Shiplacoff, yields the predictable result of using a flicking gesture to return from home screen to launch screen. Ex. 1023 ¶ 13; Ex. 1003 ¶¶ 52–61; KSR, 550 U.S. at 416. We disagree with Patent Owner’s contention that Shiplacoff teaches away from using the flicking gesture to switch from full screen mode to the launch screen because, according to Patent Owner, Shiplacoff already uses the flick gesture to perform scrolling in full screen mode. PO Resp. 49–52 the same gesture in a given mode can be assigned to different functions depending on where, when, and how the gesture is input by the user, as discussed above. Reply 11–12 (discussing Shiplacoff’s teaching of associating the same tap gesture with different functions depending on where the tap occurs), 13–14 (discussing Duarte’s teaching of associating both a drag gesture and a scrolling gesture to the same mode). Ex. 1023 ¶¶ 16–19. We agree with Petitioner and Dr. Terveen, that based on the teachings of Shiplacoff (and, by incorporation, Duarte), a person of ordinary skill in the art would have recognized that a flick started in area 102 or near an edge of screen 101 and continuing onto screen 101 would be distinguished from a flick entirely within screen 101 based on location, and would perform a different function. Ex. 1023 ¶¶ 18–19. We also agree with Petitioner and Dr. Terveen, that Duarte teaches associating a gesture with one function when a modifier key is not pressed, and associating the same gesture with a different function when the modifier key is pressed, such that a flick performed when the key is not pressed would perform one function such as scrolling and a flick performed when the key is pressed would perform another, such as changing the display mode. Reply 15 (citing Ex. 2003 ¶ 64; Ex. 1023 ¶ 20). We agree with Petitioner that Shiplacoff does not teach away from using a flicking gesture to change from full screen mode to home screen because it “does not criticize, discredit, or otherwise discourage investigation into the invention claimed.” Reply 10 (quoting Depuy Spine, 567 F.3d at1327).” slip op. at 25
Patent outcomesUS 10,649,578 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,649,578 - Universal Electronics, Inc. / Gemstar Technology (Qinzhou) Co. Ltd. et al. v. ROKU, Inc.All claims unpatentablePTAB · Jan 21, 2026 · IPR2022-00818 · APJ Russell E Cass · IPR · Remand
On remand, the Board held claim 11 unpatentable under §103 over Wouters and Verzulli because Wouters’s fixer saves the combined codeset for reinstallation.
RulingsRemand decision- RemandOther
“We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“Additionally, the obviousness inquiry typically requires an analysis of “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (requiring “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness”)); see In re Warsaw Orthopedic, Inc., 832 F.3d 1327, 1333 (Fed. Cir. 2016) (citing DyStar Textilfarben GmbH & Co. Deutschland KG v. C.H. Patrick Co., 464 F.3d 1356, 1360 (Fed. Cir. 2006)).” slip op. at 10
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20
- Strike new argumentNew argument consideredDecided for petitioner
“We also find that Petitioner has not forfeited its argument that Wouters’s fixer and reinstallation functionality satisfies limitation 11[e]. The Petition pointed to Wouters’s “fixer” for limitation 11[e], and cited Dr. Houh’s Declaration specifically identifying and quoting Wouters’s disclosure of reinstallation at page 10, lines 14 through 24. Pet. 35 (quoting Ex. 1009, 10:14–20) (citing Ex. 1002 ¶ 167); Ex. 1003 ¶ 167 (quoting Ex. 1009, 10:14–24). We find that a person of ordinary skill in the art reading the Petition and its cited evidence (including paragraph 167 of Dr. Houh’s first Declaration) would be apprised that Petitioner was relying on the portion of Wouters describing the “fixer” and reinstallation functionality.” slip op. at 23
Patent outcomesUS 8,378,875 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,378,875 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00518 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 because the prior-art combinations teach limitations 1(c) and 1(g) under the proper construction of “style.”
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
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided 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
- 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
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-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 - Smaxtec Inc. / Smaxtec Animal Care GmbH v. St Reproductive Technologies, LLCAll claims unpatentablePTAB · Jan 16, 2026 · IPR2024-01067 · APJ Andreas Baltatzis · IPR · Final written decision
Claims 5–7, 9, and 10 are unpatentable: claims 5 and 6 are anticipated by Harvey and Riskey, claim 7 is obvious over Harvey and Rettedal, and claims 9 and 10 are obvious over Harvey and …
RulingsFinal written decision- BurdenNot shown unpatentable
“Considering the entire record, we determine that Petitioner “did not make out its obviousness case in its petition” and its arguments on reply “effectively abandoned its petition in favor of a new argument.” Wasica at 1286. To the extent Petitioner asserts the claims would have been obvious over Harvey and Riskey in the Petition, it does so using a merely conclusory statement that “[t]o the extent Patent Owner alleges that either Harvey or Riskey fails to teach any claim element, that element is provided by the other reference.” See Pet. 42; Wasica at 1286. And, as discussed in our Institution Decision, the Petition at a minimum does not explain what reference is the primary versus second reference, and what elements should be combined to reach the claimed invention. See Sisvel, 82 F.4th at 1364. reference to be modified with Riskey’s bolus and data compression. See Pet. Reply 15–17. Rather than explaining how its original petition was correct, Petitioner’s subsequent arguments amount to an entirely new theory of prima facie obviousness absent from the Petition. See Wasica, 853 F.3d at 1286; see also Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1369 (Fed. Cir. 2016) (“the expedited nature of IPRs bring with it an obligation for petitioners to make their case in their petition to institute”). We decline to engage in this new argument. Accordingly, we determine that Petitioner has not met is burden to show that claims 5 and 6 would have been obvious over Harvey and Riskey. G. Asserted Obviousness of Claim 7 over Harvey and Rettedal” slip op. at 54
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“Riskey discloses “said sensor signal varies based on a corresponding change in one or more physiological parameters of said ruminant animal” (limitation 5[B]). We find Riskey’s description of temperature sensors to be persuasive evidence on this issue. Riskey discloses sensors for measuring changing animal characteristics, e.g., temperature, over time. Ex. 1005 ¶¶ 35, 44; see also id. ¶¶ 75, 76 (detecting temperature changes). We further credit Dr. Young’s testimony that one skilled in the art would understand that generated sensor signals, e.g., temperature, would change over time, whereby the sensor signal varies based on any corresponding change in the ruminant physiological parameter that the signal represents. Ex. 1002 ¶¶ 84, 85; see Cont’l Can Co. USA v. Monsanto Co., 948 F.2d 1264, 1269 (Fed. Cir. 1991) (“This modest flexibility in the rule that ‘anticipation’ requires that every element of the claims appear in a single reference accommodates the reference; that is, where technological facts are known to those in the field of the invention.”). We consider Dr. Kan’s testimony that Riskey is silent as to details about the sensor signal, but are not persuaded because the testimony appears to contradict Riskey’s disclosure of a bolus including sensors for monitoring changes in animal characteristics, generating animal characteristic messages, i.e., signals, and wirelessly transmitting data corresponding to the monitored characteristics. See Ex. 2006 ¶¶ 170–174; Ex. 1005 ¶¶ 25, 63, 67, 68, 75–78, 101. Given Riskey’s express description of monitoring animal characteristics over time, we agree with Petitioner’s argument that Riskey discloses that said sensor signal varies based on changes to the animal’s physiological parameters.” slip op. at 16
- Skill levelSkill level board ownOther
“Petitioner asserts that a person of ordinary skill in the art (“POSA”) as of the claimed priority date would have “had at least a bachelor’s degree in electrical engineering or a related or equivalent field, and three or more years of experience researching, developing, designing and/or evaluating sensor systems for humans or other animals.” Pet. 5 (citing Ex. 1002 ¶ 35) (emphasis added). Patent Owner does not contest Petitioner’s characterization of the level of skill in the art. See PO Resp. 12 (citing Ex. 2006 ¶¶ 19–20). On the entire record, we determine this level of skill, with the exception of the open-ended phrases “at least” and “or more,” which we remove from Petitioner’s proposal, comports with the qualifications a person 5 In the present record, neither party presents arguments or evidence relating to secondary considerations.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“We construe claim terms according to the standard set forth in Phillips v. AWH Corp., 415 F.3d 1303, 1312–17 (Fed. Cir. 2005) (en banc), i.e., as construed in a civil action under 35 U.S.C. § 282(b). See 37 C.F.R. § 42.100(b). Under Phillips, claim terms are afforded “their ordinary and customary meaning.” Id. at 1312. “[T]he ordinary and customary meaning of a claim term is the meaning that the term would have to a person of ordinary skill in the art in question at the time of the invention.” Id. at 1313. “Importantly, the person of ordinary skill in the art is deemed to read the claim term not only in the context of the particular claim in which the disputed term appears, but in the context of the entire patent, including the specification.” Id. Neither party expressly seeks a specific claim construction or definition for any claim term. See Pet. 10; PO Resp. 12. To the extent Patent Owner seeks to interpret claim 7 in view of the Specification, we address that argument in our discussion of claim 7, below. See infra, § III.G.3. For purposes of this Decision, we determine that no claim terms require express construction. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”)). D. Asserted Anticipation of Claims 5 and 6 by Riskey” slip op. at 11
Patent outcomesUS 10,231,644 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,231,644 - PTAB · Jan 14, 2026 · IPR2025-00632 · APJ Mitchell G Weatherly · IPR · Remand
On remand, the Board reinstituted review of all challenged claims on all grounds after finding Petitioner sufficiently explained its differing claim-construction positions.
RulingsRemand decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Id. The Director neither addressed the merits of Petitioner’s challenges nor found that our prior consideration of those merits was faulty. Accordingly, we understand that we need not reconsider our conclusion that Petitioner had demonstrated a reasonable likelihood of proving that claims 1, 2, 7–9, 11, 12, and 20–24 were unpatentable or that the merits of patentability set forth in the Petition warranted institution of inter partes review.” slip op. at 5
- BurdenDecided for petitioner
“The question before us, therefore, is whether the Petitioner’s proffered explanation that it has proposed a different claim interpretation before the Board because the District Court may decline to adopt the narrower claim interpretations it advocates there is sufficient. We find that Petitioner’s explanation is sufficient because it follows the Director’s exemplary logic. Whether a district court has already or might in the future decline to adopt constructions that a petitioner proposes in related district court litigation merely reflects the timing of when a dispute over claim interpretation will be resolved. The Director and Patent Owner both recognize that, to resolve the dispute over claim interpretation that exists here, a decision-maker must determine “a single claim construction that best captures the true meaning of the patent claim.” Remand 4; PO Remand Br. 3. Based on the record presented by the parties to date in this proceeding, no dispute exists that the disputed claim terms mean what Patent Owner says they mean in the Litigation. Accordingly, we find that, at this stage of the proceeding, it is undisputed that Patent Owner’s interpretations of the claim terms represent the “single claim construction that best captures the true meaning of the patent claim.”8 Under that claim interpretation, we” slip op. at 8
NonePatents in suitUS 11,835,421 - Apple Inc. v. Smith Interface Technologies, LLCSome claims unpatentablePTAB · Jan 14, 2026 · IPR2024-01089 · APJ Sharon Fenick · IPR · Final written decision
Claims 1, 2, 9–11, 13, 15, 16, 56–64, and 84 are unpatentable as obvious; claim 14 was not shown unpatentable because the motivation to combine the gesture teachings was not established.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“In our Decision on Institution, we noted that Petitioner’s definition left it unclear whether the bachelor’s degree in the proposed definition would be considered by Petitioner to be “an advanced-level degree,” and did not adopt the portion of the definition relating to the substitution of years of experience for a degree. Dec. on Inst. 9. Additionally we did not adopt Petitioner’s proposed additional requirement that one of ordinary skill of the pertinent technologies employed by the ’212 patent.” Id. We adopted, for the purposes of the Decision on Institution, the portion of the definition proposed by Petitioner requiring “a bachelor’s degree in computer science, computer engineering, or a comparable field and at least two years of professional experience working with graphical user interfaces and applications for computers” as “consistent with the problems and solutions in the ’212 patent and prior art of record and . . . supported by declarant testimony.” Id. Patent Owner adopted this definition (PO Resp. 12–13), noting Dr. Cockburn’s testimony regarding this definition (Ex. 2006, 12:15– 21). Patent Owner’s declarant, Dr. Madisetti, also agreed with and adopted this definition. Ex. 2005 ¶¶ 23–25. For the same reasons discussed in the Decision on Institution, we again adopt this definition.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction The parties’ papers include some discussion of claim construction. PO Resp. 13–17; Pet. Reply 1–2; PO Sur-reply 2–3. Each party asserts, and we agree, that there is no controversy that would require us to decide any claim construction issue. Pet. Reply 2; PO Sur-reply 3; see Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe 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
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
Patent outcomesUS 10,671,212 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,671,212
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.