- Google LLC v. Sandpiper CDN, LLCInstitutedPTAB · Nov 25, 2025 · IPR2025-00860 · APJ Sheila F Mcshane · IPR · Institution
The Board instituted review of claims 1–20 on all asserted grounds, finding a reasonable likelihood that the Dilley, Pai, and Wang combination renders the claims obvious.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’573 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“III. ANALYSIS A. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art: 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. Work experience can substitute for formal education and additional formal education can substitute for work experience. Pet. 12 (citing Ex. 1006 ¶ 70). Patent Owner asserts that “the Board does not need to resolve the appropriate level of skill for a POSA [person of ordinary skill in the art] for purposes of deciding institution because the Petition fails under any articulation of a POSA.” Prelim Resp. 10. For the purposes of this Decision, we adopt the assessment offered by Petitioner as it is consistent with the ’573 patent and the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner asserts that no claim terms need to be expressly construed by the Board and all terms should be given their ordinary meaning. Pet. 12. Patent Owner agrees that the Phillips standard applies. Prelim. Resp. 10. We determine that we need not expressly construe any claim terms at this juncture. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 9
- Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner
“We consider the disclosures of the Provisional Application, which refer to cases 1 and 2, in which requests are redirected to an origin server for lower popularity content and to a parent server for medium popularity content at steps 522 and 524 as shown in Figure 5, respectively, wherein the edge server receives a redirect from the popularity service without a “followme” flag. See Ex. 1011 ¶¶ 43, 44. The Provisional Application also discloses that, by comparison, if there is a “follow-me” redirect sent to the edge server, it obtains and caches a resource as shown at step 528 for higher popularity content. Id. ¶ 44. On this record, as Patent Owner asserts, these disclosures are consistent with technical reasons provided in the Provisional Application for instructing the edge server not to cache unpopular resources. See Ex. 1011 ¶¶ 68–69. In light of these disclosures, we preliminarily find support for Dr. Shenoy’s testimony that, even with the words “instruction to not cache” are not literally recited in the Provisional Application, caching and not caching are alternative options that indicate the instruction to the edge server that will be implemented for each option. See Ex. 2014 ¶ 56. Further, these disclosures provide support for Dr. Shenoy’s testimony that the disclosures “reasonably convey to those skilled in the art that Patent Owner had possession of the edge server receiving an instruction to not cache the resource (and instead simply forward the redirect).” Id. In re Johnson states that “it is not true that the factual context out of which the question under § 112 arises is immaterial. Quite the contrary. Here, . . . the ‘written description’ in the [] specification supported the claims in the absence of the limitation, and that specification, having described the whole, necessarily described the part remaining.” See Johnson, 558 F.2d at 1019. This is consistent with M.P.E.P. § 2173.05(i) which states, “[i]f alternative elements are positively recited in the specification, they may be explicitly excluded in the claims.” M.P.E.P. § 2173.05(i). Further, “the failure of the specification to specifically mention a limitation that later appears in the claims is not a fatal one when one skilled in the art would recognize upon reading the specification that the new language reflects what the specification shows has been invented.” All Dental Prodx, LLC v. Advantage Dental Prod., Inc., 309 F.3d 774, 779 (Fed. Cir. 2002). Even though we do not discern that the Provisional Application explicitly discloses an “instruction to not cache,” at least on this preliminary record, and for the purposes of this Decision, there is positive recital of instructions to cache in the Provisional Application and Petitioner has provided sufficient supporting evidence that caching and not caching are alternative options. Further, there is sufficient evidence, in the context of the disclosures of written description support in the Provisional Application, providing support for Dr. Shenoy’s testimony that Patent Owner had possession of an edge server receiving an instruction to not cache the resource. Nonetheless, we invite additional briefing on these issues, including issues relating to alternative options of caching and not caching. On this preliminary record, we find that the ’573 patent has a priority date of April 2, 2008, which predates the earliest possible date on which Newton-471 could be effective as prior art, September 30, 2014 (the date on which the earliest application in the priority chain of Newton-471 was filed). Accordingly, we preliminarily find that Newton-471 is not prior art to the challenged claims. Thus, on the present record, Petitioner has not demonstrated a reasonable likelihood that it would prevail in showing that claims 1–20 are anticipated by Newton-471.” slip op. at 13
Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 10,924,573 - Google LLC v. Sandpiper CDN, LLCInstitutedPTAB · Nov 10, 2025 · IPR2025-00806 · APJ Sheila F Mcshane · IPR · Institution
The Board instituted IPR on claims 1–20 and all asserted grounds, finding a reasonable likelihood of success on the § 103 challenges.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’517 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“application must comply with the written description requirement of 35 U.S.C. § 112.” Zenon Envtl., Inc. v. U.S. Filter Corp., 506 F.3d 1370, 1378 (Fed. Cir. 2007) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571 (Fed. Cir. 1997)); see also In re Hogan, 559 F.2d 595, 609 (CCPA 1977). To comply with the “written description” requirement of 35 U.S.C. § 112, first paragraph, an applicant must “convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention. The invention is, for purposes of the ‘written description’ inquiry, whatever is now claimed.” Vas-Cath, Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (emphasis omitted). The invention claimed does not have to be described in ipsis verbis to satisfy the written description requirement. Union Oil Co. v. Atlantic Richfield Co., 208 F.3d 989, 1000 (Fed. Cir. 2000). The question of written description support should not be confused, however, with the question of what would have been obvious to the artisan. Whether one skilled in the art would find the claimed invention obvious in view of the disclosure is not an issue in the “written description” inquiry. In re Barker, 559 F.2d 588, 593 (CCPA 1977). “A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood, 107 F.3d at 1572.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundInstituted
“motivated to combine Beaumont and Hasan. Pet. 13–14. Petitioner argues that “Beaumont does not describe a specific interface for manually entering [policy and rules] preferences, Hasan discloses a GUI for exactly this type of policy specification.” Id. at 14 (citing Ex. 1003 ¶ 70). Petitioner asserts that Hasan discloses that its Java-based, “platform independent” GUI takes the form of a “familiar tree structure” and allows administrators to “configure device and service configuration data and policy information.” Id. (citing Ex. 1006, code (57), 7:7–26, 8:19–29, 18:9–20). Petitioner asserts that the combination of Beaumont and Hasan would have been straightforward, and a person of skill “would have been motivated to incorporate Hasan’s GUI so that administrators could conveniently configure preferences for Beaumont’s DNS servers through an intuitive interface.” Id. (citing, inter alia, Ex. 1003 ¶¶ 70–71; Ex. 1007 ¶ 23). Patent Owner does not present any arguments on the rationale to combine. See generally Prelim. Resp. We find that at this juncture Petitioner has presented sufficient rationale to combine Beaumont and Hasan.” slip op. at 16
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Instituted
“We agree with Patent Owner that its understanding of a policy as a rule is consistent with the disclosure in the ’517 patent that “a policy may be created by generating a decision tree representing the ATC rules.” See Ex. 1001, 9:1–3. We do not agree with Patent Owner, however, that Beaumont in combination with Hasan does not disclose the claimed policy features as claimed. As discussed above, Petitioner relies upon Beaumont in combination with Hasan with its teachings on the use of Java-based GUIs in the form of a tree structure that allows administrators to configure device and service configuration data, as well as policy information. See Ex. 1006, code (57), 7:7–26, 8:19–29. For the policy teachings, Petitioner relies upon Beaumont’s “content provider DNS server that directs requests (traffic) according to a preference table (policy).” Pet. 15–16 (citing Fig. 1, ¶¶ 6, 17, 23). Petitioner also asserts that the Beaumont-Hasan GUI would enable an administrator to set policies for a selected content delivery server to allow setting server preferences and rules. Id. at 17–18 (citing, inter alia, Ex. 1007 ¶¶ 76–77). In support, Dr. Lin testifies that: The Beaumont-Hasan GUI would enable an administrator to select a content delivery server (e.g., in Japan) and set policies for that server. Hasan, 8:30–36, 10:25–34, 10:53–67; Beaumont, [0031]. For example, given the description in Hasan, selecting a server would bring up a menu enabling an administrator to assign the preferences shown in Fig. 3 of Beaumont. Hasan, 10:25–34; Beaumont, Figs. 2, 3, [0029]–[0031]. A POSITA would thus have recognized the combined GUI to “support[] the setting of said at least one policy using a decision tree representing rules” because it is presented in a “familiar tree structure” and would allow users to set server preferences and rules. Ex. 1003 ¶ 77 (emphasis added). Beaumont provides support for Dr. Lin’s testimony. Beaumont discloses that “rules such as selecting one [a server] based on user preferences can be used . . . [f]or example, a preference number can be assigned to each content delivery server and a destination domain.” Ex. 1007 ¶ 31. Beaumont further states that “FIG. 3 shows an illustrative example of incorporating preference numbers in a column.” Id. Thus, contrary to Patent Owner’s arguments, Beaumont discloses that rules or policies, represented by the preference number, are represented in the table shown in Figure 3 of Beaumont. Dr. Lin also testifies that in the Beaumont-Hasan combination “the GUI supports the setting of” policy is taught. Ex. 1003 ¶ 77. Hasan provides support that service policies can be modified by the use of a GUI. See Ex. 1006, 8:30–36, 10:25–34, 10:53–67. Accordingly, in the combination of Beaumont and Hasan, wherein the preference database is replaced by the GUI decision tree, Petitioner has provided sufficient evidence at this juncture that the combination of Beaumont and Hasan teaches that the GUI obtains a policy, the preference number, for the direction of network traffic, where the GUI supports the setting of the policy using a decision tree representing rules.” slip op. at 19
Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 8,645,517 - PTAB · Jun 16, 2022 · IPR2022-00300 · APJ John D Hamann · IPR · Institution
The Board instituted IPR on claims 1–20 and 22 on all asserted grounds, finding a reasonable likelihood that at least one challenged claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsInstitution denied 325dDenied
“(1) whether the same or substantially the same art previously was presented to the Office or whether the same or substantially the same arguments previously were presented to the Office; and (2) if either condition of first part of the framework is satisfied, whether the petitioner has demonstrated that the Office erred in a manner material to the patentability of challenged claims.” slip op. at 7
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2018); see 37 C.F.R. § 42.108. Upon consideration of the papers, we conclude that the information presented shows that there is a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of at least one challenged claim of the ’570 patent.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field, and at least two years of experience in the research, design, development, and/or testing of touch and/or proximity sensors, human-machine interaction and interfaces, and related firmware and software, or the equivalent, with additional education substituting for experience and vice versa.” Pet. 5 (citing Ex. 1002 ¶ 46). Patent Owner does not identify a proposed level of skill in the art that one would have had at the time of the invention of the ’570 patent or identify any specific shortcoming in Petitioner’s formulation. See generally Prelim. Resp. For purposes of this Decision, and based on the current record, we adopt Petitioner’s assessment of the level of skill for one of ordinary skill in the art, except we decline to adopt “at least” as that language is vague and open-ended. Pet. 5. This assessment is consistent with the ’570 patent and the asserted prior art, and we apply it in our analysis below.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningOther
“same claim construction standard that would be used in a civil action under 35 U.S.C. § 282(b), following the standard articulated in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). 37 C.F.R. § 42.100(b). In applying such standard, claim terms are generally given their ordinary and customary meaning, as would be understood by a person of ordinary skill in the art, at the time of the invention and in the context of the entire patent disclosure. Phillips, 415 F.3d at 1312–13. “In determining the meaning of the disputed claim limitation, we look principally to the intrinsic evidence of record, examining the claim language itself, the written description, and the prosecution history, if in evidence.” DePuy Spine, Inc. v. Medtronic Sofamor Danek, Inc., 469 F.3d 1005, 1014 (Fed. Cir. 2006) (citing Phillips, 415 F.3d at 1312–17). The parties do not identify any claim terms for construction. Pet. 15; see generally Prelim. Resp. Thus, at this stage of the proceeding, we do not provide any express constructions, and we afford the claim terms their plain and ordinary meaning. See, e.g., Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”).” slip op. at 12
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites Phillips · GrahamPatents in suitUS 7,952,570 - Netskope, Inc. v. Bitglass, Inc.InstitutedPTAB · Dec 14, 2021 · PGR2021-00091 · APJ James J Mayberry · PGR · Institution
Instituted PGR on claims 1, 2, 4–10, and 12–16; the Board found the petition showed a more-likely-than-not basis that at least one challenged claim was unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We may not institute a post-grant review “unless . . . the information presented in the petition filed under section 321, if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a). Upon consideration of the arguments and evidence, we determine Petitioner has demonstrated that it is more likely than not that at least one of the Challenged Claims is unpatentable. Accordingly, we institute a post-grant review of the Challenged Claims of the ’671 patent.” slip op. at 2
- Parallel petitionsOther
“II. DISCRETIONARY DENIAL Patent Owner argues that we should exercise discretion to deny the Petition in this proceeding, or the petition in PGR2021-00092. Prelim. Resp. 15. Patent Owner argues that Petitioner filed two petitions challenging the same patent without justifying the need for two petitions. Id. at 3–15. We exercise our discretion to not institute trial in PGR2021-00092, because Petitioner did not justify two petitions challenging the ’671 patent.13 In view of the denial of institution of PGR2021-00092, we need not consider further Patent Owner’s arguments on discretionary denial in this Decision.” slip op. at 18
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not define the level of ordinary skill and, instead, states that we should “apply[] the Petition’s asserted definition of the level of ordinary skill in the art.” Prelim. Resp. 44. For the purposes of this Decision, we adopt Petitioner’s proposed level of ordinary skill in the art. We determine that Petitioner’s definition is consistent with the prior art of record and the skill reflected in the Specification of the ’671 patent, based on our review of the limited record.” slip op. at 20
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner contends that no claim terms need an express construction. Pet. 25. Patent Owner states that “the Petition does not appear to present any issues that require the Board to construe the claims to resolve the issues at the institution stage.” Prelim. Resp. 44. We agree with the parties that, at least at this stage of the proceeding, we need not expressly construe any claim term. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 20
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · GrahamPatents in suitUS 10,855,671
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.