- Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentablePTAB · Feb 10, 2026 · IPR2024-01116 · APJ Sharon Fenick · IPR · Final written decision
Petitioner did not prove claims 1, 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191, 192, 197, 199–204, 208–216, 223, 225, or 230 unpatentable because the asserted combinations did not establish the claimed blurring …
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“(Ex. 1003), that a person of ordinary skill in the art (“POSITA”) would have had “a Bachelor of Science 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,” and that “[a]dditional years of experience could substitute for an advanced-level degree (and vice-versa).” Pet. 6 (citing Ex. 1003 ¶¶ 29–30).” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction In these proceedings, there is no controversy that would require us to decide any claim construction issue. 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))). D. Obviousness of Claims 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191,” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“obviousness of the menus in the Ahn-Chaudhri combination following a user’s finger as the user performs the dragging gesture to open the menu.” Pet. Reply 2 (citing 01119-Petition, 26–33, substantially identical to Pet. 32– 40). However, again, the Petition does not explain an alternative theory in which Chaudhri supplements Ahn’s menu functionality to move that menu onto the screen, as opposed to teaching visual cues provided by gradual changes of the display during a gesture or the visual cue that an unlock image may provide during the unlock gesture. See Pet. 14–18 (describing Chaudhri teaching “visual differentiation” or “transitioning an optical intensity” between a user-interface object and the background, based on, e.g., transparency), 35–40 (same). In Reply, Petitioner adds evidence to attempt to support its contention that the combination teaches a menu following a user’s finger during a dragging gesture, involving references to Chaudhri’s discussion of a visual cue, further discussing Chaudhri’s unlock image. Ex. 1005 ¶¶ 54, 62, 74–79, Figs. 5A-5C (cited at Pet. Reply 4–5). With respect to these citations and arguments, even if they had been timely presented in the Petition, we agree with Patent Owner that they do not articulate a modification of Ahn with Chaudhri or a motivation to combine. PO Sur-reply 6. Additionally, we agree that these embodiments of Chaudhri are distinct from the cited portions of Chaudhri discussed with respect to this theory in the Petition, which relate not to the movement of displayed graphics, but to variations of optical intensity and visual cues. Id. at 6–7. We evaluate the Petition’s arguments in light of Petitioner’s statement in Reply that they require a teaching regarding “menus . . . following a user’s finger as the user performs the dragging gesture.” Pet. Reply 2. To the extent that the Petition shows that the combination of Ahn and Chaudhri would show visual changes as the user performs a dragging gesture, these do not relate to the movement of a menu, but rather to other optical effects. Thus, as we do not find that the Petition supports an Ahn-Chaudhri combination in which a menu follows a user’s finger as the user performs the dragging gesture to open the menu, as Petitioner argues, we determine that Petitioner has not shown limitation 2.d of claim 2 taught or suggested by the combination of Ahn and Chaudhri according to this theory.” slip op. at 31
- Strike new argumentNew argument disregardedDecided for patent owner
“Petitioner argues that “even under [this] interpretation of Ahn, the only difference between Ahn and the claims is whether the animation occurs in direct correspondence with a user’s dragging gesture or after the dragging gesture is complete – a straightforward design choice if ever there was one.” Pet. Reply 3–4 (citing Ex. 1024, 99:16–108:20; Ex. 1023 ¶ 12). However, as Patent Owner argues (PO Sur-reply 7–8) this argument is presented in Reply and is an improper shift of theory from the Petition. Nevertheless, were we to consider it, we would not find it compelling; Dr. Terveen’s cited testimony repeats this bare statement and is not supported by any evidence or additional explanation. Ex. 1023 ¶ 12; see 37 CFR § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”); Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (Aug. 24, 2022) (precedential) (assigning little weight to opinion testimony that “merely repeats” conclusory statements in a brief, without “cit[ing] any additional supporting evidence or provid[ing] any technical reasoning to support [the declarant’s] statement”).” slip op. at 29
Patent outcomesUS 10,656,754 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,656,754 - Apple Inc. v. Smith Interface Technologies, LLCNo claims unpatentablePTAB · Feb 10, 2026 · IPR2024-01115 · APJ Sharon Fenick · IPR · Final written decision
Apple did not prove claims 1, 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191, 192, 197, 199–204, 208–216, 223, 225, and 230 unpatentable over the asserted Ahn combinations.
RulingsFinal written decision- Skill levelSkill level board ownDecided for patent owner
“In the Decision on Institution in each proceeding, 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 advancedlevel degree,” and did not adopt the portion of the definition relating to the substitution of years of experience for a degree. Dec. on Inst. 15–16. Patent Owner “does not agree with all aspects of Petitioner’s proposed level of ordinary skill” but did not propose an alternative definition. PO Resp. 10–11. Patent Owner’s declarant, Dr. Rosenberg, adopted Dr. Terveen’s definition for the purposes of his declaration. Ex. 2018 ¶¶ 32–33. We again adopt the main portion of Dr. Terveen’s definition, and determine that one of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, human-computer interaction, or a comparable field and at least two years of professional experience working with graphical user interfaces and applications for computers.” This definition is commensurate with the problems and solutions in the ’754 patent and prior art of record and is supported by declarant testimony.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction In these proceedings, there is no controversy that would require us to decide any claim construction issue. 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))). D. Obviousness of Claims 2, 27, 37, 58, 60–64, 67–79, 186, 187, 189, 191,” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“obviousness of the menus in the Ahn-Chaudhri combination following a user’s finger as the user performs the dragging gesture to open the menu.” Pet. Reply 2 (citing 01119-Petition, 26–33, substantially identical to Pet. 32– 40). However, again, the Petition does not explain an alternative theory in which Chaudhri supplements Ahn’s menu functionality to move that menu onto the screen, as opposed to teaching visual cues provided by gradual changes of the display during a gesture or the visual cue that an unlock image may provide during the unlock gesture. See Pet. 14–18 (describing Chaudhri teaching “visual differentiation” or “transitioning an optical intensity” between a user-interface object and the background, based on, e.g., transparency), 35–40 (same). In Reply, Petitioner adds evidence to attempt to support its contention that the combination teaches a menu following a user’s finger during a dragging gesture, involving references to Chaudhri’s discussion of a visual cue, further discussing Chaudhri’s unlock image. Ex. 1005 ¶¶ 54, 62, 74–79, Figs. 5A-5C (cited at Pet. Reply 4–5). With respect to these citations and arguments, even if they had been timely presented in the Petition, we agree with Patent Owner that they do not articulate a modification of Ahn with Chaudhri or a motivation to combine. PO Sur-reply 6. Additionally, we agree that these embodiments of Chaudhri are distinct from the cited portions of Chaudhri discussed with respect to this theory in the Petition, which relate not to the movement of displayed graphics, but to variations of optical intensity and visual cues. Id. at 6–7. We evaluate the Petition’s arguments in light of Petitioner’s statement in Reply that they require a teaching regarding “menus . . . following a user’s finger as the user performs the dragging gesture.” Pet. Reply 2. To the extent that the Petition shows that the combination of Ahn and Chaudhri would show visual changes as the user performs a dragging gesture, these do not relate to the movement of a menu, but rather to other optical effects. Thus, as we do not find that the Petition supports an Ahn-Chaudhri combination in which a menu follows a user’s finger as the user performs the dragging gesture to open the menu, as Petitioner argues, we determine that Petitioner has not shown limitation 2.d of claim 2 taught or suggested by the combination of Ahn and Chaudhri according to this theory.” slip op. at 31
- BurdenNot shown unpatentable
“(3) Conclusion For the reasons discussed above, Petitioner has not shown limitation 2.d to be taught, suggested, or otherwise rendered obvious by Ahn and Chaudhri. Thus, we determine that Petitioner does not show by a preponderance of the evidence that claim 2 would have been obvious over the combination of Ahn and Chaudhri.” slip op. at 32
Patent outcomesUS 10,656,754 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,656,754 - Google LLC v. DH International Ltd.All claims unpatentablePTAB · Feb 10, 2026 · IPR2024-01322 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Mooney; the Board also found Mooney combined with Lee renders the disputed limitations obvious.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“A person of ordinary skill in the art (“POSITA”) at the time of the alleged invention of the ’294 patent would have had at least a bachelor’s degree in electrical engineering, or a related field, and at least two years of experience in design, development, and/or testing of network-enabled consumer devices, and familiarity with payment cards, or the equivalent, with additional education substituting for experience and vice versa. Pet. 2 (citing Lipoff Decl. Ex. 1003 ¶ 57). “Patent Owner agrees with the Petitioner on the level of ordinary skill in the art.” Resp. 4. Patent Owner adds that a POSITA would have had “at least three years of relevant industry or research experience in wireless communication between devices.” Id. (citing Ex. 2001 ¶¶ 26–29). Mr. Zaheer testifies that a POSITA “would” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“The claim language and specification define and describe an “activation cue” in functional terms: a data communication from an external source is received by the cell phone and recognized as an activation cue if it causes the switching element to be assigned its first (activated) state. Ex. 1001, 9:28–31, 9:42–46, 10:14–16, 13:55–60, 14:53–59, 15:4–6, 19:20–26. Patent Owner agrees that “upon an activation cue being received by portable electronic device 10, switching element 44b switches to its activated state.” Resp. 19 (quoting Ex. 1001, 10:14–16). The activation cue may be a predetermined bit sequence, a predetermined contactless data transmission, continuously emitted, pulsed, or punctual, but these are unclaimed non-limiting embodiments of the preferred form of data transmission. Id. at 9:25–26 (“for example a predetermined bit sequence”), 11:20–22 (“One example . . . emit an activation cue in the form of a predetermined contactless data transmission”), 14:65–15:3 (continuously emitted, pulsed or punctual cue). We will not read such preferred embodiments from the specification into claim language that is not so limited. See SuperGuide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875 (Fed. Cir. 2004) (care should be taken “not to import into a claim limitations that are not part of the claim”); see also In re Van Geuns, 988 F.2d 1181, 1184 (Fed. Cir. 1993) (“limitations are not to be read into the claims from the specification”); see also IQRIS Techns. LLC v. Point Blank Enterprises, Inc., 2025 WL 727717, *4 (Fed. Cir. 2025) (“It is the claims, not the preferred embodiments, that” slip op. at 15
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“operatively linked to said electronic circuit” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. We note there is no presumption of applying means-plus-function analysis to the switching element, because the limitation does not use the words “means for” that would mandate such claim construction treatment, and “switching” may invoke structure as well as function. See Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1349–1350 (Fed. Cir. 2015) (en banc) (holding that “use of the word ‘means’ creates a presumption that § 112, ¶ 6 applies”). Regardless, we look to the meaning of the claim phrase at issue in view of the specification. We determine that the ’294 patent provides a clear, concise meaning for the switching element upon which both parties rely for construction. Patent Owner’s express agreement with Petitioner, that the claimed switching element is described in the ’294 patent as “any type of device allowing data to be conveyed according to alternate data conveyance operations in response to an activation cue being received by transceiver 18 or not,’” is particularly telling because it is not consistent with Patent Owner’s argument that the switching element means “switching of the data.” Resp. 7, 31 (citing Ex. 1001, 9:28–318). The claim language does not recite, and the specification does not describe, the switching element as a device that switches the data. Therefore, we determine the claimed “data conveyance switching element” means any type of switching device that allows data to be 8 We presume Patent Owner’s citation to “Exh. 2001, 9:28-31” on page 7 was intended to be a citation to the ’294 patent (Ex. 1001), as cited on page 31. whether or not an “activation cue” is received by the cell phone “cue receiver.”” slip op. at 21
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningDecided for petitioner
“[external] data exchange device” as a device with a data transceiver coupled to a circuit that carries out the function of exchanging data. Pet. 7–8 (citing Ex. 1001, 2:14–17, 4:7–14, 9:3–6; Ex. 1003 ¶¶ 67–68). As above, whether we construe the “[external] data exchange device” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. Patent Owner, quoting the description of a data exchange device in the ’294 patent, contends that a “[external] data exchange device” “can be any sort of data exchange device comprising an electronic circuit (not shown) therein and a data transceiver 9a.” Resp. 8 (quoting Ex. 1001, 9:4–6). Patent Owner also responds to the Petition by clarifying that “[a]n external data exchange device is not a transceiver but a device with a transceiver.” Id. (citing Ex. 2001 ¶ 48). Petitioner argues in reply that Patent Owner does not contest Petitioner’s mappings of Mooney’s “cordless telephone base unit” or “cellular network infrastructure” to the claimed data exchange devices, such that no construction is necessary to resolve the dispute. Reply 5 (citing Resp. 16–37; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011)). Limitations [1.c] and [1.d] recite “a first [second] data transceiver operatively linked to said electronic circuit [in the cell phone],” both of which are defined functionally as “for exchanging data between said electronic circuit [in the cell phone] and a first [second] external data exchange device over a first [second] communication link.” Nothing in the the other independent claims, further limits the form or function of the “[external] data exchange device,” although a device external to the cell phone may invoke additional structure. We determine the plain meaning of “[external] data exchange device” as claimed and described in the ’294 patent governs: any [external] device that comprises an electronic circuit and data transceiver for exchanging data with the electronic circuit in the cell phone over a communication link. slip op. at 22
Patent outcomesUS 9,022,294 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,022,294 - 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 - 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 - Apple Inc. v. Smith Interface Technologies, LLCSome claims unpatentablePTAB · Jan 8, 2026 · IPR2024-01091 · APJ Jameson Lee · IPR · Final written decision
Claims 30 and 62 are unpatentable over the respective Kim and Burrough combinations; claims 1, 32, 34, and 64 were not shown unpatentable because the cited gestures lacked a common starting point.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“The difference between the parties’ positions is solely that Petitioner includes “human-computer interaction” as a relevant degree and “human computer interfaces” as relevant working experience. We need not resolve that difference, because no matter which stated level of ordinary skill is applied, all of our findings and conclusions would be the same and because neither party asserts the other party’s expert is not qualified as an expert. In the Decision on Institution, we adopted Petitioner’s stated level of ordinary skill in the art. Inst. Dec. 10. We continue to adopt Petitioner’s stated level of ordinary skill in the art.3 C.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“gesture” must refer back to the same gesture reflects the plain meaning of the claim language. In each independent claim, the structure and usage of the language in dispute are the same. Only one gesture detection is recited, and there is no language reasonably indicating repetition or reiteration of detection for any reason at any time. Patent Owner’s position that to meet “the gesture” recitations, prior art “gestures” must all share a common starting point also makes sense and is appropriate. The same gesture must start from the same starting point or else it is not the same gesture. Specifying the understanding this way avoids treating two similar gestures as the same gesture, if they have different starting points. For instance, two taps may be the same in every way, except for their starting points. They are not the same gesture in the context of these claims.” slip op. at 19
- Expert testimonyOther
“The difference between the parties’ positions is solely that Petitioner includes “human-computer interaction” as a relevant degree and “human computer interfaces” as relevant working experience. We need not resolve that difference, because no matter which stated level of ordinary skill is applied, all of our findings and conclusions would be the same and because neither party asserts the other party’s expert is not qualified as an expert. In the Decision on Institution, we adopted Petitioner’s stated level of ordinary skill in the art. Inst. Dec. 10. We continue to adopt Petitioner’s stated level of ordinary skill in the art.3 C.” slip op. at 11
- BurdenNot shown unpatentable
“Neither the tap-and-hold gesture in the bottom path of Kim’s Figure 7 nor the “long press input” and “long press event” of Kim such as that shown in Kim’s Figure 5 is the double-tap gesture Petitioner relies on to satisfy limitation [1.f]. Neither has been shown to have a common starting point with the double tap. Thus, Petitioner’s showing is inadequate. Limitation [1.i] recites: [1.i] when the magnitude of the duration of the gesture being detected on the touch screen on the object is greater than a second magnitude threshold, perform another operation. Pet. v. Petitioner explains: Kim teaches or renders [1.i] obvious. APPLE-1003, ¶62. Kim further describes “another operation” that is performed when the magnitude of the duration of the gesture is greater than a second magnitude threshold—specifically, a minimum threshold to be deemed an intentional touch. Specifically, Kim explains that, “[i]f detecting a user gesture, namely, if receiving an input event from a user through the touch screen, the mobile device determines the type of an input event.” APPLE-1004, [0053]. Kim states that, “[i]f an interrupt is not a request for the activation of the zoom mode as the result of determination in step 205, the mobile device can perform some action in connection with an interrupt (step 207),” shown in Figure 2a below. APPLE- 1004, [0050], FIG. 2a; APPLE-1003, ¶63. [Figure 2A of Kim is a flow diagram of a method for a touch-based control in a zoom mode (Ex. 1004 ¶ 20)] Kim additionally explains that if the mobile device determines that a detected user gesture does not correspond to any particular input event, “the mobile device disregards the received input event.” APPLE-1004, [0053]. Based on Kim’s disclosure of “disregarding” a received input, a POSITA would have understood that, for the detected interrupt (step 203) to be sufficient to cause the mobile device to “perform other action” (step 207), a magnitude greater than a minimum threshold value (e.g., the minimum threshold of an intentional user input) is relied upon, or rendered obvious, by Kim. APPLE-1004, FIG. 2a; APPLE-1003, ¶64. Thus, when the magnitude of the gesture is greater than a second magnitude threshold, the device “performs other action” (e.g., display requested menu). APPLE- 1004, [0050], FIG. 2a; APPLE-1003, ¶64. A POSITA would have understood that such an interrupt would be caused by a gesture that is longer in duration than the second threshold (as necessary to avoid the gesture from being disregarded), shorter than the duration necessary for a long press threshold, and a different gesture than a double tap gesture. APPLE-1003, ¶64. Pet. 24–26. As explained by Petitioner, the interrupt gesture relied on by” slip op. at 40
Patent outcomesUS 10,936,114 mixedClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,936,114
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.