• Google LLC v. Sandpiper CDN, LLCAll claims unpatentable
  PTAB · Oct 9, 2026 · IPR2025-00826 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–23 are unpatentable under § 103, including over Glines alone and the additional asserted combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art (“POSITA”) at the critical time “would have had at least a bachelor’s degree in computer science, electrical engineering, or a related field, and at least two years of work or research experience in the field of content delivery management or networks,” and that “additional education could substitute for work experience.” Pet. 3 (citing Ex. 1008 ¶¶ 51–53). Patent Owner provides substantially the same assessment. PO Resp. 16. We adopt Petitioner’s proposed level of ordinary skill, as it appears to be consistent with the specification of the ’112 patent and the prior art of record.” slip op. at 7

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

    “claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. [§] 282(b).” 37 C.F.R. § 42.100(b). Under this standard, the words of a claim generally are given their “ordinary and customary meaning,” which is the meaning the term would have to a person of ordinary skill at the time of the invention, in the context of the entire patent including the specification. Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Neither party proposes any express claim construction. Pet. 3; PO Resp. 16. We address the parties’ interpretation of the scope of “causing said hostname to be resolved” in our discussion of Petitioner’s assertions for limitation [1.d]. Based on the record before us, we determine that no claim term requires express construction.” slip op. at 8

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Strike new argumentNew argument consideredDecided for petitioner

    “We do not agree. The Petition states that Glines discloses that the anycast is resolved by an ISP DNS server. Pet. 20. The Petition identifies Glines’s local ISP DNS resolver 18 as the claimed ISP DNS server. Id. The Petitioner further asserts that Glines’s ISP DNS resolver 18 sends the request to the DNS server 38, but states that “Glines’s local DNS resolver, an ISP DNS server, thus causes the hostname . . . to be resolved.” Id. at 21–22. The Petition also drew an analogy with the ’112 patent and the role of local DNS server 70a in the Petition. See Pet. 20–21. Because the Petition and the Reply both identify Glines’s local ISP DNS resolver 18 as causing the hostname to be resolved, Petitioner has not advanced a new theory of unpatentability in its Reply. 6 At oral argument, Patent Owner suggested a narrower claim reading, but admitted that this had not been briefed. Tr. 36:15–38:9, 44:9–16. We do not address this reading because it was not set forth in the briefing. In the briefing, Patent Owner took the broader reading discussed here. See Tr. 41:12–23; PO Sur-reply 7.” slip op. at 13

  Patent outcomesUS 9,021,112 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,021,112
• Apple Inc. v. Ferid AllaniAll claims unpatentable
  PTAB · Aug 25, 2026 · IPR2025-00857 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–27 are unpatentable: claims 24 and 26 over Rossmann and Himmel; claims 1–2, 4–6, 10–23, 25, and 27 over Rossmann, Himmel, King, and Adar; claims 3 and 7–9 over those references and Boyle.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “we consider the type of problems encountered in the art, the prior art solutions to those problems, the rapidity with which innovations are made, the sophistication of the technology, and the educational level of active workers in the field. See Custom Accessories, Inc. v. Jeffrey-Allan Industries, Inc., 807 F.2d 955, 962 (Fed. Cir. 1986); see Orthopedic Equip. Co. v. United States, 702 F.2d 1005, 1011 (Fed. Cir. 1983).” slip op. at 6

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “meaning of “icon” as claimed, including the dependent claims, the specification, the prosecution history, and the extrinsic evidence including expert testimony and dictionary definitions, we determine that the plain meaning of “icon” is readily apparent from the claims themselves. See Phillips, 415 F.3d at 1314 (“In some cases, the ordinary meaning of claim language as understood by a person of ordinary skill in the art may be readily apparent even to lay judges.”). We find that the plain meaning of “icon” as claimed encompasses at least “textual elements” because claim 20 recites “the icons comprise textual elements.” See id. (“Other claims of the patent in question, both asserted and unasserted, can also be valuable sources of enlightenment as to the meaning of a claim term.”). We highlight that the additional intrinsic evidence cited by the parties is consistent with the plain meaning. For example, Figures 1 and 2 of the specification show icons comprising textual elements. As another example, during prosecution of the ’058 patent, the Examiner found that the claimed icons were taught by textual hyperlinks. Ex. 1002, 586, 592. In order to overcome the Examiner’s rejection and obtain an allowance (id. at 641–50), applicant subsequently amended the claims to recite “specifically designed,” thus implicitly conceding to the Examiner’s interpretation of icon as encompassing textual hyperlinks. Id. at 625–640; see PO Resp. 43–44 (citing Ex. 1002, 626–27, 645–46) (acknowledging that the Examiner allowed the claims because applicant amended the claims to recite “specifically designed for containing a set of icons.”).” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed petitioner constructionDecided for petitioner

    “Requiring an element to be "specifically designed" for another element narrows the claim because it requires more than the first element being merely capable of being used with the second element. The term "configured to" is generally construed narrowly to mean "made to" and "designed to" rather than broadly to require merely "capable of". See In re Giannelli, 739 F. 3d 1375, 1379-80 (Fed. Cir. 2014) (the phrase "configured to" requires more than "mere capability." Rather, that term is synonymous with "made to" and "designed to."). However, rather than use "configured to", in order to avoid any confusion as to the narrower scope of the claims as amended, Applicant herein directly and explicitly requires "designed to." In re Giannelli at 1379-80 (Fed. Cir. 2014) (reversing an obviousness rejection because (1) the claims were properly construed narrowly to mean "designed to" and not broadly to encompass merely "capable of", and (2) the USPTO had not explained the motivation for modifying the prior art to meet the "design to" requirement) See also MPEP 2111.04, citing to In re Giannelli, for the proposition that a claim can be narrowed to require that it be "designed and constructed to be used" in a specific manner (as a rowing machine in the case of In re Giannelli). Logan has not been specifically designed and constructed in the required manner, so it does not cure all deficiencies of the primary reference Iki (which lacks any tree menu structure). Logan describes only "remote web" pages 90, 95 that are merely pages retrieved from Web browsing and stored in a web computer 25. Iki as modified by Logan would result on in a tree menu structure wherein not all levels of the tree included the required selection pages specifically designed for containing the claimed set of icons. Ex. 1002, 626–27 (emphasis omitted).” slip op. at 14

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

    “Petitioner contends that a person of ordinary skill in the art would have modified Rossmann to include several advantages expressly taught by Himmel: Himmel’s consumer hot list bookmark set for the benefits of providing a user with a consistent user interface when accessing a website; to simplify navigation for the user by providing an additional navigation aid; to provide more immediate access to commonly used web actions; to reduce the network traffic required to navigate through webpages to arrive at a particular web function; and to reduce usage charges and data usage. Pet. 22–23 (citing Ex. 1003 ¶¶ 94–99; Ex. 1004, 2:38–56, 12:24–34, 14:35–44; Ex. 1005, 18:63–65, 20:11–16). Petitioner contends that modifying Rossmann’s Figures 4A through 4G to include Himmel’s consumer hot list bookmark set yields each selection page including both selection icons for navigating to other local pages along with direct access icons such as on sale today to directly navigate to a predetermined web site to perform a common web action. Id. at 23–25 (citing Ex. 1003 ¶¶ 96–100; Ex. 1004, Figs. 4D–F). Petitioner contends that the selection page of Rossmann as modified by the bookmark set of Himmel teaches a first locally stored page specifically designed to include a direct access icon because the selection page is “used to include” a direct access icon, such as on sale today, and that during use, this selection page is programmed to display the set of direct access icons for selection by the user. Pet. 25 (citing Ex. 1003 ¶¶ 96–100); see id. at 21–24. Petitioner contends that a person of ordinary skill in the art would have had a reasonable expectation of success because technology for bookmarking websites and web actions was known at the time of invention, modifying Rossmann to utilize known bookmark manager software would have been straight forward, Rossmann already includes hardware and programming instructions to access a web server, and Himmel teaches that known prior art methods utilized both selection and direct access icons on a single page. Id. at 25–26 (citing Ex. 1003 ¶¶ 101–103; Ex. 1004, 2:38–41, 14:21–44; Ex. 1005, Fig. 6A, 21:27–34).” slip op. at 19

  Patent outcomesUS 10,943,058 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 10,943,058
• SAP America, Inc. v. Cyandia, Inc.All claims unpatentable
  PTAB · Mar 13, 2026 · IPR2024-01433 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–7, 10, 11, 13, 18, 19, 23, 29, 35, and 36 are unpatentable as obvious over the PCT Publication and Austin-Lane.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner asserts that a person of ordinary skill in the art at the time of filing “would have had a Bachelor’s degree in electrical engineering, computer science, or the like, and/or four or more years of experience in server-based applications” and that “[a]dditional experience may make up for a lack of education and vice versa.” PO Resp. 9. Because Petitioner’s proposed level of ordinary skill in the art appears to be consistent with the challenged patent and prior art, we adopt it and use “skilled artisans” to refer to people with such skill at the time the invention was filed. We do not perceive a substantive distinction between the parties’ definitions, but note that Petitioner’s definition provides more detail about the capabilities of skilled artisans. 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 9

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “device indicated by the session data” encompasses “determining a notification method based on” session data indicating the current state of the external device, where the current state of the device encompasses an online state as well as an offline state. See Pet. 53–54; Tr. 55:3–10 (The Board: “Are there any other states of an external device other than online or offline?” Patent Owner: “As far as I know, Your Honor, those are the only two[.]”), Tr. 65:24–66:1 (The Board: “When the claim says current state, they mean it’s online or offline?” Petitioner: “Correct.”), Tr. 20:23–21:8. The specification is consistent with the plain language of the claim in disclosing two examples of the claimed “current state,” namely, online and offline. Ex. 1101, 21:1–4. The specification discloses that the notification manager “queries session manager 456 to determine the user’s connectedness.” Id. at 21:6–8. The specification discloses that if the user is “online, notify by, for example, the user’s active session. If offline, notify by, for example, a txt [sic] message, call the user’s landline, call a friend of the user, and the like.” Id. at 21:1–4, 23:28–31.” slip op. at 13

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “Patent Owner’s expert witness, Dr. Goodrich, show written description support for providing a notification to an active external device, Patent Owner has not cited any portion of the 2009 Parent, nor any portion of the testimony of Dr. Goodrich, to show that the 2009 Parent provides written description support for determining a notification method by which to provide an alert to an external device based on the current state of the external device as offline. We highlight that Paragraphs 130 and 131 of the 2011 CIP Application disclose offline notification preferences for determining a notification method by which to provide an alert to an external device based on the current state of the external device as offline. Ex. 1110 ¶¶ 130–131. Specifically, paragraphs 130 and 131 describe that: the notification manager of the eventing and alerting subsystem 452 queries the configuration server 454 for the user's notification preferences and correlates these notification preferences with session manager 456 to determine the best notification method. That is, the notification manager queries the configuration server 454 and determines, for example, that the user has certain online notification preferences and certain offline notification preferences. If online, notify by, for example, the user's active session. If offline, notify by, for example, a txt message. . . . The notification manager of the eventing and alerting subsystem 452 then queries session manager 456 to determine the user's connectedness. Id. That is, if the user’s connectedness, or “current state” of the claimed external device, is offline, and the user’s offline notification preferences are “notify by txt message,” the notification manager will determine that the notification method for the external device having a current state of offline is by txt message. See id. Thus, the 2011 CIP Application describes a notification manager that queries a session manager to determine whether an external device is offline, and if the external device is offline, determines a notification method for providing an alert on the external device based on the current status of the external device as offline and the user’s offline notification preferences. Although we find this written description support for the determining limitation in the 2011 CIP Application, we do not find this written description support in the 2009 Parent.” slip op. at 25

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

    “As to the “determining a notification method” limitation (1.10), Petitioner asserts that Austin-Lane teaches determining: (1) the user device(s) to send the notification to (e.g., phone, PDA, notebook computer, desktop computer); (2) the communication protocol to use to send the notification, i.e., how to send the notification (e.g., SMTP (for email), SMS (for texts), HTTP (for web browsers)); and (3) the type of alert to provide, i.e., how to present the notification, (e.g., text, an icon, a pop-up window, a video, an email, an audible or tactile alarm), based on the current state of the at least one external device indicated by the session data (“presence information”), which may include whether and on which device(s) the user is online and/or whether and on which applications the user has an active session. Id. at 53 (internal citations omitted) (citing Ex. 1105 ¶¶ 4, 5, 29, 32, 33, 39, 46, 48, 61, 79, Fig. 1). We highlight that paragraph 61 of Austin-Lane discloses that: The type preferences 650 may include preferences for various notification types. . . . [A]uction alert #1 660 defines the following delivery precedence 663: (1) a web browser (if the user is online), (2) an IM client (if the user is online), (3) a mobile phone #1, (4) a PDA, (5) a mobile phone #2, (6) a pager, and (7) an email inbox. Ex. 1105 ¶ 61; see id. ¶¶ 74–77 (Describing that one of several notification methods for delivering an alert to a user’s device is determined based on the current state of the user’s device as online or offline). Thus, Austin-Lane describes determining a notification method by which to provide an alert on an external device based on the current state of the external device as online as well as offline.” slip op. at 29

  Patent outcomesUS 8,751,948 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips
  Patents in suitUS 8,751,948
• Apple Inc. v. Smith Interface Technologies, LLCAll claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,649,578
• Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 7,594,168
• Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 7,594,168
• Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 7,594,168
• Netflix, Inc. v. VL Collective IP LLCAll claims unpatentable
  PTAB · Jan 7, 2025 · IPR2023-00891 · APJ Karl D Easthom · IPR · Final written decision

  Claims 1–22 are unpatentable, including as anticipated by Comps; the majority finds Comps’s Tracks 1 and 3 example meets the claim limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “the prior art and supported by the testimony of Dr. Bederson. See Ex. 1003 ¶¶ 28–30. Dr. Goodrich testifies that “Dr. Bederson and Petitioner offer a slightly different definition of the POSITA, which is similar to my definition” and that his “opinions would not change were” he “to adopt the definition of POSITA offered by Petitioner.” Ex. 2011 ¶ 54. Accordingly, we adopt Petitioner’s proposal, which is materially the same as Patent Owner’s proposal for purposes of this Final Written Decision, as Dr. Goodrich testifies. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 8

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

    “1. content-related data segments Claim 1 recites “content-related . . . data segments.” Patent Owner construes this phrase as “segments of content data that have a syntactical meaning within the respective data file.” PO Resp. 12. As Patent Owner notes, the ’794 patent specification states that “[t]he term ‘content-related’ is understood to mean that first and second data segments have a syntactical meaning within the respective data file, such as e.g. a plurality of succeeding second data segments represent the speech signal of a specific speaker within a dialog sequence.” Id. at 12–13 (quoting Ex. 1001, 4:9–22); Ex. 1001, 4:9–22 (second emphasis added). The ’794 specification supports Patent Owner’s position that the emphasized sentence essentially defines the term “content-related . . . data segments.” PO Resp. 13–15. However, as Petitioner argues, nothing in the sentence restricts “content-related data segments” to “content” only, for example, “sampled audio,” instead of also including information relating to the content. See Reply 3 (arguing that “the phrase ‘content data’ appears nowhere in the ’794 patent and was not part of the ‘inventors’ express lexicography’ for ‘content-related . . . data segments,’ as P[atent] O[wner] incorrectly contends”). Petitioner points out that Patent Owner’s reliance on the specification refers to “content-related . . . data segments” and “contentbased data segments.” Id. (emphasis by Petitioner) (quoting Ex. 1001, 4:9– 22). Petitioner also contends that the specification refers to describing data, contradicting Patent Owner’s position that the data segments must include content. Id. at 7 (“[A]ccording to at least one embodiment of the invention, media data, in particular video or audio data, and/or metadata, in particular encoded according to the XML standard, are described by way of the first and/or second data file.”) (emphasis by Petitioner) (quoting Ex. 1001, 3:4– 10). Moreover, as Petitioner argues, “the word ‘data’ should be given its plain and ordinary meaning,” so that “even if the [unrecited] phrase ‘content data’ is included in the Board’s construction . . . . the term ‘content data’ would include any information relating to the content.” Id. at 4. As noted above, both parties point to the specification’s definition of “content-related . . . data segments”: “The term ‘content-related’ is understood to mean that first and second data segments have a syntactical meaning within the respective data file, such as e.g. a plurality of succeeding second data segments represent the speech signal of a specific speaker within a dialog sequence.” Ex. 1001, 4:9–22. This passage indicates that data segments are content-related or include content, such as a “speech signal,” and that these segments “have a syntactical meaning” with respect to the source of the signal, such as a speaker. See Inst. Dec. 9 & n.8, 17 (observing that “[t]he term ‘content-related’ is somewhat subjective because there is not much guidance in the ’794 patent specification as to what a ‘syntactical meaning’ encompasses”). In context, one plain meaning of the term “syntax” is “[t]he way in which words are put together to form phrases and sentences.” Ex. 3002 (THE AMERICAN HERITAGE DICTIONARY OF THE ENGLISH LANGUAGE, 1305 (1976)). However, as indicated above, the ’794 patent refers to video images and audio sounds with a syntactical meaning, showing that it embraces broader subject matter than the plain meaning of “syntax.” Patent Owner’s argument that the ’794 patent refers to “content-” slip op. at 9

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “segments.’”). Comps supports Petitioner and states that “two syllables represented by the fields TEXT[1] and TEXT[2] must be presented to the user.” Ex. 1004, 3:39–40 (emphasis added). Accordingly, Petitioner persuasively maps each of these text fields to an “associated one of the content-related first data segments [Nf3 and Nf4, respectively] on the basis of an assignment rule [the SYNCH process],” as claim 1 requires.” slip op. at 34

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableUnpatentable

    “1. Claim 6 Petitioner identifies particular passages in Comps and Wan as teaching or suggesting the subject matter additionally recited in claim 6 and provides reasons for combining the teachings. Pet. 50–51. The record supports Petitioner’s showing. See id. Patent Owner does not provide separate arguments for claim 6. See generally PO Resp. Based on the full record, we determine that Petitioner shows by a preponderance of evidence that Comps and Wan render claim 6 unpatentable. 2. Claims 7, 8, and 22 Claim 7 recites “[t]he method as claimed in claim 1, further” slip op. at 68

  Patent outcomesUS 8,605,794 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,605,794
• Netflix, Inc. v. Videolabs, Inc.All claims unpatentable
  PTAB · Oct 2, 2024 · IPR2023-00628 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–14 are unpatentable: claims 1–4 and 8–11 as anticipated by Mehta, and claims 1–14 as obvious over Mehta and Schläpfer.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The level of ordinary skill in the art usually is evidenced by the references themselves. 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). 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.” slip op. at 9

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

    “We construe only those claim terms that require analysis to resolve the controversy. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that “only those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy”). Any special definition for a claim term must be set forth in the specification with reasonable clarity, deliberateness, and precision. In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994). Petitioner and Patent Owner agree that no claim terms require specific construction to resolve the unpatentability issues presented in the Petition. Pet. 23; PO Resp. 10–11. We agree and do not construe any terms.” slip op. at 9

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “Analysis We agree with Petitioner. Mehta discloses storing “functionally equivalent programs having the same name that are capable of running on multiple kinds of devices that even may be written using different languages.” Ex. 1003 ¶ 98. Mr. Wechselberger testifies that this disclosure shows that Mehta’s “MAS receives, stores and supports functionally equivalent programs capable of running on multiple devices because each program corresponds to a different device having different device capabilities (e.g., written using different languages).” Ex. 1002 ¶ 66. This testimony is consistent with that of Dr. Goodrich, who testifies that “each application has a single version made for a particular device type.” Ex. 2020 ¶ 66. Dr. Goodrich later testifies that paragraph 98 of Mehta describes that there could be two functionally equivalent programs with the same name that are compatible with a single user’s computer. Id. at ¶ 88; see PO Resp. 31–32 (citing Ex. 2020 ¶¶ 87–88). We do not credit this later testimony, because it is inconsistent with Dr. Goodrich’s earlier testimony that “each application,” or program of Mehta, is “made for a particular device type.” Ex. 2020 ¶ 66. We agree with Mr. Wechselberger and find that a person of ordinary skill in the art at the time of invention would have understood that Mehta’s disclosure of functionally equivalent programs having the same name that are capable of running on multiple kinds of devices means that each program corresponds to a different device having different capabilities. Further, Mehta discloses that “the MAS only lists those applications that are supported by the subscriber’s device. This allows the subscriber to avoid the problem of having to explicitly select a compatible application.” Ex. 1003 ¶ 117; see Pet. 36–37 (citing Ex. 1002 ¶¶ 75, 77). Mr. Wechselberger testifies that a person of ordinary skill in the art at the time of invention would have understood this disclosure to mean that the MAS provides the subscriber with only a single subscriber-appropriate version that will work for the subscriber. Ex. 1002 ¶ 77. Although Patent Owner contends that Mehta is silent on whether only a single description would be provided if there were multiple implementations (PO Sur-Reply 10–11), we agree with Mr. Wechselberger and find that when multiple implementations have the same name, each implementation corresponds to a different device, and therefore, the MAS would only present to the subscriber the one implementation that works with the subscriber’s device. Ex. 1002 ¶¶ 66, 75, 77.” slip op. at 28

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “piece of content, while the versions of Microsoft Word for Windows and Microsoft Word for Apple Macs are different implementations.” Ex. 2020 ¶ 39. Dr. Goodrich, in his deposition, when asked if “one of ordinary skill in the art at the time of the ’790 patent would also understand that Microsoft Word for Windows and Microsoft Word for Mac are also functionally equivalent, correct?” answered “Yes . . . . But they would be even stronger than simply functionally equivalent. They would be different implementations of the same product.” Ex. 1029, 43:14–24. However, later in his deposition, Dr. Goodrich testifies that Microsoft Word for Windows and Microsoft Word for Apple Mac are separate applications, not different implementations of the same application. Ex. 1029, 48:1–20. We disagree with this later testimony. Neither Dr. Goodrich nor Patent Owner persuasively explains why Dr. Goodrich changed his unambiguous position from both his declaration and his earlier deposition testimony. For example, Dr. Goodrich testifies in his deposition that “for the Lion King example, a .MP3 and a .MOV are different implementations of the same product. They’re also functionally equivalent, but functionally equivalent is broader.” Ex. 1029, 45:7–11. Dr. Goodrich continues, “when Mehta is disclosing functionally equivalent, it is not referring to it as different implementations of the same product. Instead, it’s [describing] how to disambiguate [applications] not clustered in terms of implementations . . . based on other metadata.” Id. at 45:14–21. This explanation is unpersuasive because it is inconsistent with Dr. Goodrich’s declaration testimony, in which Dr. Goodrich explicitly testifies that the different versions of Lion King, as well as the different versions of Microsoft Word, are different implementations of the same product. Ex. 2020 ¶ 39. Specifically, in his declaration, Dr. Goodrich testifies that the “various versions of Lion King (such as an .mp3 file or an .mov file) are the implementations of the Lion King. For another example, . . . the versions of Microsoft Word for Windows and Microsoft Word for Apple Macs are different implementations.” Ex. 2020 ¶ 39. Dr. Goodrich testifies again that “Microsoft Word for Windows and Microsoft Word for Apple Macs” are “multiple implementations of an individual item of digital content.” Ex. 2020 ¶ 70. Further, the reason given in the explanation in his deposition, that Mehta needs to disambiguate applications that are not clustered in terms of implementations based on other metadata, would also apply to the different versions of Lion King, yet Dr. Goodrich consistently testifies that these different versions are different implementations, both in his declaration and in his deposition. Id.; Ex. 1029, 45:7–10. Petitioner contends, and we agree, that the inconsistent testimony of Dr. Goodrich appears to be an attempt to cure Patent Owner’s and Dr. Goodrich’s incomplete analysis of Mehta’s disclosure. See Reply 7–8. In particular, the Petition quotes Mehta’s disclosure that the MAS stores “functionally equivalent programs having the same name that are capable of running on multiple kinds of devices that even may be written using different languages.” Pet. 28 (quoting Ex. 1003 ¶ 98). Dr. Goodrich addresses this disclosure by explaining that two applications, such as Microsoft Word and Apple Pages, are functionally equivalent but are two different applications, not multiple implementations of a single application. Ex. 2020 ¶ 70. In this analysis, Dr. Goodrich does not address the full disclosure of Mehta, which describes that the “functionally equivalent programs hav[e] the same name” (Ex. 1003 ¶ 98), such as Dr. Goodrich’s example of Microsoft Word for Windows and Microsoft Word for Apple Macs. See id. Thus, although Dr. Goodrich is correct in testifying that some functionally equivalent programs, such as Microsoft Word and Apple Pages, are not different implementations of an item of digital content, he is also correct in testifying that “Microsoft Word for Windows and Microsoft Word for Apple Macs” are “multiple implementations of an individual item of digital content.” Id. Yet Dr. Goodrich does not identify any difference between the multiple implementations of Microsoft Word and the functionally equivalent programs having the same name as described by Mehta.” slip op. at 18

  Patent outcomesUS 7,233,790 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,233,790
• Netflix, Inc. v. VL Collective IP LLCAll claims unpatentable
  PTAB · Oct 2, 2024 · IPR2023-00630 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–24 are unpatentable: claims 1, 2, 4, 7, 8, 10, 13, 14, 16, 19, 20, and 22 are anticipated by Cassin; all claims are also obvious over Cassin and Huston and over Huston.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The level of ordinary skill in the art usually is evidenced by the references themselves. 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). 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.” slip op. at 7

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

    “We construe only those claim terms that require analysis to resolve the controversy. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that “only those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy”). Any special definition for a claim term must be set forth in the specification with reasonable clarity, deliberateness, and precision. In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994). Petitioner contends that “no claim terms require specific construction to resolve the unpatentability issues presented” in the Petition. Pet. 15–16. Similarly, Patent Owner contends that “no express construction of any term is required.” PO Resp. 18. For purposes of this decision, we do not construe any claim terms.” slip op. at 8

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “is included in the indication. See PO Resp. 40. However, the ’559 patent does not describe what is included in the claimed “listing.” Rather, throughout the disclosure of the ’559 patent, the phrase “the listing of one or more pieces of content stored in memory” or a variation thereof is repeated without any further elaboration. Ex. 1001, 3:13–15, 3:26–36, 12:22–26, 12:50–52, 13:29–30. For example, the Specification does not disclose that the listing of one piece of content includes the title of the piece of content, nor an identification number of the piece of content, nor any other information about the piece of content. The disclosed listing is no more than an item of information that indicates that a specific piece of content is stored in the memory of the terminal. Therefore, the plain and ordinary meaning of the claim term “a listing of one . . . piece[] of content stored in the memory,” read in light of the Specification of the ’559 patent, encompasses an item of information that indicates that a specific piece of content is stored in the memory of the terminal. We agree with Petitioner and find that Cassin’s indication that the client currently has the media content item describes an item of information that indicates that a piece of content is stored in the memory of the terminal. Therefore, Cassin’s indication that the client currently has the media item describes “a listing of one . . . piece[] of content stored in the memory” as claimed.” slip op. at 33

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “Analysis We agree with Petitioner and find that Cassin’s offer to download an item describes “a response . . . that instructs the terminal to perform one or more actions” as claimed. Reply 11 (citing Pet. 25–26), 13–14. Cassin discloses that the server uses the user information received from the client to query a database in the server for a list of content to which the user is entitled. Ex. 1004 ¶¶ 162, 164. Cassin discloses that the server offers an item from the list to the client for downloading. Id. ¶ 163 (The server offers every item on the list), ¶ 164 (The server attempts to send an item on the list). Cassin discloses that the client checks to see if it already has the item. Id. ¶¶ 163, 164. If the client has the item, the client refuses the download offer. Id. If the client does not have the item, the client accepts the download of the item and stores the item in its content repository. Id. Thus, the client responds to the offer to download an item from the server by (a) checking to see if it has the offered item, and (b) either refusing the download if the client has the item or accepting the download if the client does not have the item. Therefore, we agree with Petitioner and find that “when the server offers a media item for the client to download, the server is ‘instructing the terminal to perform one or more actions to thereby control the flow of content.’” Reply 11 (citing Pet. 25–26). We agree with Petitioner that in response to the server’s offer, “the client will either ‘refuse the download’ (if it has the content) or ‘accepts the download of the media content item from the server and stores the media content in the local content repository’ (if the client does not have the content).” Id. (citing Ex. 1004 ¶ 163). We agree with Petitioner and find that by checking to see if it has the item, and “by refusing or accepting the download offer, the client is doing ‘something to control the flow of content’ in response to the server’s instruction.” Id. (quoting PO Resp. 23). We disagree with Patent Owner’s contentions to the contrary. In particular, we disagree with Patent Owner’s contention that the server’s offer “has not instructed the client to do anything—the client takes action based on other factors (whether or not it already has the media content item).” PO Sur-Reply 3; see PO Resp. 31–32; Ex. 2002 ¶¶ 91–93. We find that the client performs the actions of checking to see if it already has the item and, depending on whether it has the item, either accepting or refusing the offer, in response to receiving the offer from the server. Ex. 1004 ¶¶ 163, 164; Ex. 1003 ¶¶ 72–75. Thus, we agree with Petitioner that the server’s offer instructs the client to (a) determine whether the client has the item and (b) depending on whether the client has the item, either accept or refuse the offer, which describes “instructing the terminal to perform one or more actions to thereby control the flow of content” as claimed. We further find that, because the offered item is from the server’s list which was determined using information from the user and information from the server’s database, the offer to download the item describes “a response to the content status . . . based upon the terminal status information and the server status information” as recited in claim 1.” slip op. at 26

  Patent outcomesUS 7,440,559 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,440,559

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.