The decision

On November 16, 2026, a panel of Administrative Patent Judges Jeffrey S. Smith, Sheila F. McShane, and Michael T. Cygan entered a final written decision in Google LLC v. Sandpiper CDN, LLC, IPR2025-00860, Paper 32. Judge McShane wrote for the panel. The decision is captioned as a judgment under 35 U.S.C. 318(a), "Determining All Challenged Claims Unpatentable." The order states that Petitioner has demonstrated by a preponderance of the evidence that claims 1-20 of U.S. Patent 10,924,573 B2 are unpatentable, and that, because this is a final written decision, parties seeking judicial review must comply with the notice and service requirements of 37 C.F.R. 90.2.

The patent and the parties

Google LLC is the petitioner, and Sandpiper CDN, LLC is the patent owner. Each identifies itself as its sole real party in interest. The challenged patent is U.S. Patent 10,924,573 B2, titled "Handling Long-Tail Content in a Content Delivery Network (CDN)." The decision states that the patent issued on February 16, 2021. U.S. Application No. 16/284,791, the '791 application, was filed on February 25, 2019. The decision states that the patent relates to a content delivery network with tiers of servers, and describes a popularity service that, depending on an object's popularity, instructs the edge server to redirect the client's request to the origin server or cache, or to a parent server, or to serve the content itself. Claims 1, 11, and 19 are independent.

What the challenged claims cover

Claim 1 covers a method of content delivery in a content delivery network comprising: receiving, at a first server of a first tier of servers of the content delivery network, a request from a requesting device for a resource available from the content delivery network; accessing a popularity service associated with the content delivery network to determine a popularity designation associated with the requested resource; requesting the resource from a second server of the content delivery network; processing, at the first server of the first tier of servers, a redirect instruction from the second server of the content delivery network to obtain the resource from a content server of the content delivery network; receiving an instruction to not cache the portion of the resource at the first server of the first tier of servers when the portion of the resource is obtained from the content server of the content delivery network; and providing the obtained resource to the requesting device.

Claim 11 covers a content delivery network comprising: a first tier of servers comprising a first plurality of servers, an edge server of the first tier of servers receiving a request from a requesting device in communication with the first server for a resource available from the content delivery network; a second tier of servers comprising a second plurality of servers, a first server of the second plurality of servers receiving a request from the edge server for the content and, in response, transmitting a redirect instruction intended for the requesting device to the edge server to obtain the resource from a content server and transmitting an instruction to not cache the portion of the resource at the edge server when the portion of the resource is obtained from the content server; and a popularity service tracking a popularity designation associated with the requested resource; wherein the edge server processes the redirect instruction to obtain the content from the content server and provides the obtained content to the requesting device.

Claim 19 covers a method of content delivery in a content delivery network comprising: receiving, at a first server of a first tier of servers of the content delivery network, a request from a requesting device for a resource available from the content delivery network; accessing a popularity service associated with the first server of the first tier of the content delivery network to determine a popularity designation associated with the requested resource; receiving an instruction to not cache the resource at the first server of the first tier of servers when the portion of the resource is obtained from the content server of the content delivery network; requesting the resource from a second server of the content delivery network based at least on the popularity designation associated with the requested resource; and providing the obtained resource to the requesting device. Claims 2 through 10 depend from claim 1, directly or through another dependent claim. Claims 12 through 18 depend from claim 11, directly or through another dependent claim. Claim 20 depends from claim 19.

Procedural history

The petition is Paper 1, accompanied by a declaration marked Ex. 1006. The preliminary response is Paper 8, accompanied by a declaration marked Ex. 2014. On November 25, 2025, the Board instituted trial in Paper 15 on two grounds: claims 1-20 as anticipated under 35 U.S.C. 102(a) by Newton-471, and claims 1-20 as obvious under 35 U.S.C. 103 over Dilley, Pai, and Wang. Patent Owner's response is Paper 19, accompanied by a declaration marked Ex. 2016. Petitioner's reply is Paper 21, and Patent Owner's sur-reply is Paper 23. The Board held an oral hearing on August 26, 2026. The transcript is Paper 31.

The prior art and the asserted grounds

Newton-471 is U.S. Patent Application Publication No. 2016/0094471 A1, published March 31, 2016 (Ex. 1002). Dilley is U.S. Patent 7,133,905 B2, filed April 9, 2002, and issued November 7, 2006 (Ex. 1003). Pai is U.S. Patent Application Publication No. 2006/0271972 A1, published November 30, 2006 (Ex. 1004). Wang is U.S. Patent Application Publication No. 2005/0198250 A1, published September 8, 2005 (Ex. 1005).

The grounds instituted, and decided in the final written decision, are anticipation of claims 1-20 under 35 U.S.C. 102(a) by Newton-471, and obviousness of claims 1-20 under 35 U.S.C. 103 over Dilley, Pai, and Wang.

The priority date

The Board found that the priority date of the '573 patent is its February 25, 2019 application date, because the evidence does not support priority to an earlier application in the priority chain, including the '412 Provisional Application, as there is "no written description support for the '573 patent claim 1 limitation 'receiving an instruction to not cache' in the earlier applications." The decision states that written description support for the term "instruction to not cache," which is found in all the independent claims, is not found in the '412 Provisional Application or in all the applications in the priority chain, and concludes that "the earliest priority date for the '573 patent is February 25, 2019, the filing date of the '791 application. Thus, Newton-471 is prior art to the '573 patent." In a footnote, the Board states that the priority date is an issue only as to the Newton-471 ground, and that even if the earlier priority date of April 4, 2008 applied, which the Board does not find to be the case, Dilley, Pai, and Wang would still be prior art under pre-AIA 35 U.S.C. 102(b). The '573 patent claims priority to U.S. Provisional Application No. 61/042,412, filed April 4, 2008.

The Board's determinations

On the anticipation ground, the decision states that Patent Owner's arguments for claim 1 related to the priority date of the '573 patent relative to Newton-471, and that Patent Owner provided no arguments disputing Newton-471's disclosures of the limitations of claim 1. The Board determined that Petitioner demonstrated by a preponderance of the evidence that "claims 1-20 of the '573 patent are anticipated by Newton-471."

On the obviousness ground, the Board did not find Patent Owner's arguments on the rationale to combine Dilley and Pai persuasive, and found claims 1-20 obvious over Dilley, Pai, and Wang. For claims 2-4, 6-10, 12-14, 16-18, and 20, the decision states that "Patent Owner provides no arguments specific to these claims."

The decision's summary table lists claims 1-20 as shown unpatentable under 35 U.S.C. 102(a) over Newton-471, and claims 1-20 as shown unpatentable under 35 U.S.C. 103 over Dilley, Pai, and Wang. The overall outcome is that claims 1-20 are unpatentable.

Related litigation the decision names

The parties identify, and the decision reports, a related matter, Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951, in the Central District of California, filed May 10, 2024. The complaint in that case asserts U.S. Patent 10,924,573 and five other patents against Google. On January 22, 2026, Judge Andre Birotte Jr. granted the parties' joint stipulation and stayed that action until Google's IPRs, IPR2025-00806, IPR2025-00826, IPR2025-00860, IPR2025-00969, and IPR2025-01010, are finally resolved, including any appeals. The order vacated the case management deadlines, including the September 11, 2026 final pretrial conference and the September 28, 2026 trial, and directed the parties to file a joint status report within 30 days after Google's IPRs are finally resolved.

What to watch next

Watch for any request for rehearing or notice of appeal. Parties seeking judicial review of the decision must comply with the notice and service requirements of 37 C.F.R. 90.2. In the Central District of California action, watch for the joint status report the stay order calls for once Google's IPRs are finally resolved. The case can end at any time, including by settlement or voluntary dismissal.