The decision

On November 13, 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-01010, Paper 38. Judge Cygan 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 established by a preponderance of the evidence that claims 1-15 are unpatentable, and that parties seeking judicial review of the decision 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 a real party-in-interest. The challenged patent is U.S. Patent 10,057,322 B2, titled "Network Address Resolution." The decision states that the patent issued on August 21, 2018, from U.S. Application No. 14/985,968, filed on December 31, 2015, which claims the benefit of U.S. Provisional Application No. 62/098,930, filed on December 31, 2014. Google requested inter partes review of claims 1-15.

What the challenged claims cover

Claim 1, which the Board treats as illustrative, covers a content delivery method comprising receiving, by an origin system, a request from a client device for a content resource, the content resource including at least one embedded resource with a tag; upon identification of the tag, using at least one delivery parameter to obtain, by the origin system, a modified embedded resource from a content delivery network that is separate from the origin system; and delivering, by the origin system, the content resource to the client device with the modified embedded resource, wherein the modified embedded resource includes a direct link to a node within the content delivery network that can deliver content associated with the embedded resource.

Claim 15, also treated as illustrative, covers a method comprising providing, at a content delivery network, an application programming interface (API); at the API, receiving, from an origin system that is separate from the content delivery network, an embedded resource and at least one parameter associated with the embedded resource; generating a modified embedded resource providing a direct link to a node within the content delivery network for obtaining content associated with the embedded resource; delivering, by the content delivery network, the modified embedded resource to the origin system; receiving, at the node, a request from a client device to obtain the content; and providing the content to the client device.

Claim 11 covers a content delivery network comprising at least one processor in communication with a non-transitory computer readable medium including computer readable instructions for performing steps that parallel the method of claim 15: providing an API; at the API, receiving, from an origin system that is separate from the content delivery network, an embedded resource and at least one parameter associated with the embedded resource; generating a modified embedded resource providing a direct link to a node within the content delivery network for obtaining content associated with the embedded resource; delivering, by the content delivery network, the modified embedded resource to the origin system; receiving, at the node, a request from a client device to obtain the content; and providing the content to the client device. Claims 2 and 8 through 10 depend from claim 1, and claims 3 through 7 depend from claim 2. Claims 12 through 14 depend from claim 11.

Procedural history

The final written decision states that, based on the preliminary record, the Board instituted an inter partes review of the '322 patent (Paper 17), and that Patent Owner's request for Director Review of the Institution Decision was denied in Paper 22. An order dated January 12, 2026, by John A. Squires, Under Secretary of Commerce for Intellectual Property and Director of the United States Patent and Trademark Office, denied the requests for Director Review. That order is also captioned in IPR2025-00806 (U.S. Patent 8,645,517 B2), IPR2025-00826 (U.S. Patent 9,021,112 B2), and IPR2025-00969 (U.S. Patent 8,478,903 B2). The Board held an oral hearing on September 1, 2026.

The prior art and the asserted grounds

The Board's evidence table identifies four references. Verma is U.S. Patent Application Publication No. 2009/0132640 A1, titled "Content Timing Method and System" and published May 21, 2009. Raciborski is U.S. Patent Application Publication No. 2007/0067424 A1, published March 22, 2007. Lewin is U.S. Patent Application Publication No. 2014/0052811 A1, published February 20, 2014. Drai is U.S. Patent Application Publication No. 2009/0172167 A1, published July 2, 2009.

The decision states that Petitioner asserts that claims 1-15 would have been unpatentable on these grounds, as the decision lists them, citing page 10 of the petition: claim 15 under 35 U.S.C. 102(a)(1) and 102(a)(2) over Verma; claims 11, 12, 14, and 15 under 35 U.S.C. 103 over Verma; claims 11, 12, 14, and 15 under section 103 over Verma and Raciborski; claims 1, 8, 10, and 13 under section 103 over Verma and Lewin; claims 2, 4, 5, 7, 9, and 13 under section 103 over Verma, Raciborski, and Lewin; and claims 3 and 6 under section 103 over Verma, Raciborski, Lewin, and Drai. In a footnote, the Board states that it applies AIA 35 U.S.C. 103 to the '322 patent because the patent was filed after March 16, 2013, and does not include any claim for priority on or before that date.

Claim construction

The Board construed the claims under 37 C.F.R. 42.100(b), using the same standard that would be used in a civil action under 35 U.S.C. 282(b). It adopted Petitioner's construction of "direct link" as "a link pointing to a specific server," and it did not adopt a construction that requires avoidance of DNS processing. It construed "API" as "an interface that allows the client to communicate with an application executing on the server," and it did not adopt Patent Owner's proposed construction of a "programmatic interface layer that receives defined external inputs, passes the inputs to a computational functionality, and provides defined outputs from the computational functionality." It declined to construe "embedded resource with a tag" as requiring the tag to be embedded inside, or the same as, the embedded resource. The decision also recounts that, at institution, the Board determined that a "modified embedded resource" encompasses a "modified link."

The Board's determinations

On the anticipation ground, the Board determined that Petitioner has shown by a preponderance of the evidence that claim 15 is unpatentable as anticipated by Verma. On the obviousness ground over Verma alone, it determined that claims 11, 12, 14, and 15 are unpatentable as obvious over Verma. On the ground over Verma and Raciborski, it determined that claims 11, 12, 14, and 15 would have been obvious over the combined teachings of Verma and Raciborski.

On the ground over Verma and Lewin, the Board determined that a person having ordinary skill in the art would have had sufficient reason to combine the teachings of Lewin and Verma as proposed, and that Petitioner had sufficiently shown a reasonable expectation of success in the combination to achieve limitation [1b]. In that same section, the Board determined that Petitioner had shown by a preponderance of the evidence that claims 8, 10, and 13 are unpatentable, and the decision's summary table lists claims 1, 8, 10, and 13 as shown unpatentable under 35 U.S.C. 103 over Verma and Lewin.

On the remaining obviousness grounds, the Board determined that claims 2, 4, 5, 7, 9, and 13 are unpatentable as obvious over Verma, Raciborski, and Lewin, and that claims 3 and 6 are unpatentable as obvious over Verma, Raciborski, Lewin, and Drai.

The decision's summary table, introduced with the words "In summary," lists each of those grounds, and its overall-outcome row lists claims 1-15 as shown unpatentable. After reviewing the record and weighing the evidence offered by both parties, the Board determined that Petitioner showed by a preponderance of the evidence that claims 1-15 are unpatentable.

Related litigation the decision names

The parties represent, and the decision reports, that the '322 patent is involved in Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951, in the Central District of California, filed May 10, 2024. 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.