US 8719886

I'll search for information on US patent 8719886, including any CAFC 2026 docket activity.

Let me search for additional litigation and CAFC docket information, and verify the claim structure.

Let me search for CAFC docket activity specifically and confirm the independent claims.

Based on my searches, here is a concise summary. I'll note where information is confirmed versus uncertain.

US Patent 8,719,886 B2 — "Dynamic Processing of Streamed Content"

Bibliographic data (confirmed via Google Patents, the USPTO-issued PDF, and the IPR record)

• Patent number: US 8,719,886 B2 (application no. 12/604,518; published as US 2010/0122305 A1 on May 13, 2010)
• Title: Dynamic processing of streamed content
• Inventor: Ian Maloney, Dublin (IE) — sole named inventor
• Original assignee: Level 3 Communications, LLC (Broomfield, CO)
• Current assignee: Sandpiper CDN, LLC (assignment from Level 3 recorded April 26, 2024; Reel/Frame 067244/0690; also referenced as Reel 068256)
• Filing date: October 23, 2009
• Priority date: November 12, 2008 (a provisional application; the specific provisional number was not visible in the sources I retrieved)
• Issue date: May 6, 2014
• Legal status: Active; adjusted expiration shown as 2032-02-01 (patent term adjusted by 831 days under 35 U.S.C. § 154(b))
• Classifications (high level): G06F21/10 (DRM/protected content), G06Q30/02 and subclasses (targeted advertising), H04L63/10 and 63/107 (location-dependent access control), H04N21/2225, H04N21/25875, H04N21/61, H04N21/812 (advertisement data), H04N7/173

Abstract (as printed)

"Embodiments generally disclosed herein include computer-implemented methods for delivery of video content across a network. Such methods comprise a content delivery manager capable of receiving a video stream from a content source for delivery to a end user of a content publisher. The content delivery manager is further capable of detecting a trigger signal within the video stream. For example, the trigger signal can indicate a temporal mark injected into the video stream by the content publisher. During general operation, the content delivery manager processes the trigger signal to determine whether to modify delivery of the video stream to the end user. According to another general embodiment, a computer-implemented method is provided for authorizing delivery of a video stream to an end user."

Independent claims — plain-language overview

Caveat: The full claims section was not included in the patent text provided to me, and my searches did not surface the verbatim claim language. The overview below is derived from the specification's two "general embodiments," which is what the abstract summarizes. I cannot confirm the exact wording or number of independent claims with certainty, so treat this as a faithful description of the claimed subject matter as disclosed rather than verbatim claim text.

1. Content-delivery modification claim (trigger-signal based): A computer-implemented method for delivering video content across a network in which a content delivery manager (i) receives a video stream from a content source for delivery to a client/end user of a content publisher, (ii) detects a trigger signal within the video stream — the trigger signal being a temporal mark injected into the stream by the content publisher (e.g., indicating a commercial break, program start/end, or blackout), (iii) processes the trigger signal to determine whether to modify delivery of the video stream (e.g., by querying an Electronic Programming Guide with geo-filtering/advertisement data, or applying the end user's proximity parameters/IP address), and (iv) modifies delivery of the video stream accordingly (e.g., inserting a targeted advertisement, blacking out the stream, or discontinuing delivery).

2. Authorization claim (subscription-database "dip"): A computer-implemented method for authorizing delivery of a video stream associated with a content publisher to an end user, in which an authorization manager (i) receives a request from the end user for delivery of the video stream across a network, (ii) queries a subscription database associated with the content publisher (which may be the publisher's existing satellite/cable TV subscriber database), (iii) processes the reply to determine whether the end user is authorized, (iv) transmits a notification to the end user if not authorized, and (v) initiates delivery of the video stream if authorized.

The dependent-subject matter described in the specification (FIGS. 12–15 and 19–22) includes EPG-based blackout determination, proximity/geo-filtering, targeted ad selection via an advertisement server, cookie/token-based authentication, and session-based re-authorization.

Litigation / PTAB / CAFC status (from live search results)

• District court (Google): Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951 (C.D. Cal., filed May 10, 2024). The '886 patent was among the six originally asserted. The court granted Google's motion to dismiss the '886 claim on September 16, 2024 (Dkt. 28), finding the '886 patent invalid under 35 U.S.C. § 101 (along with the '778 patent). Sandpiper reserved its right to appeal (Amended Complaint, Dkt. 45, Jan. 10, 2025).
• IPR: Google LLC v. Sandpiper CDN, LLC, IPR2025-00952 (PTAB), filed May 7, 2025, challenging the '886 patent. Status: discretionary denial / not instituted (institution decision October 10, 2025). The petition's exhibit list (P-TACTS) identifies the '886 patent as Exhibit 1001 and includes prior art such as Acharya, Carle, Schein, Fransdonk, Risan, and Kan.
• CAFC 2026 dockets: My searches returned no CAFC (Federal Circuit) docket for 2026 involving patent 8,719,886. I found no record of an appeal filed to the Federal Circuit regarding this patent as of the current date. Note that a related Microsoft IPR (IPR2026-00190, filed Dec. 29, 2025) references the '886 assignment documents, but I could not confirm that proceeding challenges the '886 patent itself rather than a different Sandpiper/Level 3 patent — do not assume it covers '886 without verifying the challenged patent number.
• Related portfolio cases: Sandpiper also sued Comcast (No. 2:24-cv-00886, E.D. Tex., Nov. 1, 2024) and Microsoft (No. 2:25-cv-00664, E.D. Tex., June 26, 2025) over the broader Level 3/Sandpiper CDN patent portfolio; the specific patents asserted in those cases vary and do not necessarily include the '886 patent.

Uncertainty notes

• I could not retrieve the verbatim independent claim text; the overview above is reconstructed from the specification's two general embodiments and the abstract.
• The provisional application number for the November 12, 2008 priority claim was not visible in the retrieved sources.
• I did not access the USPTO PAIR/PatentCenter directly; my USPTO-related confirmation comes from the USPTO-hosted P-TACTS document for IPR2025-00952 and the official PDF of the patent.

I've found several relevant matters. Let me dig deeper to confirm exactly which cases assert US 8,719,886 and their current status.

Based on my searches, here is the litigation picture for US Patent 8,719,886 ("Dynamic processing of streamed content," assigned to Sandpiper CDN, LLC, formerly Level 3 Communications LLC). I have confirmed two proceedings specifically involving the '886 patent, plus several related portfolio cases that do not appear to assert the '886 patent (noted separately to avoid confusion).

Confirmed matters involving US 8,719,886

1. Sandpiper CDN, LLC v. Google LLC

• Plaintiff: Sandpiper CDN, LLC
• Defendant: Google LLC
• Jurisdiction: U.S. District Court, Central District of California (Judge Philip S. Gutierrez; Magistrate Judge Rozella A. Oliver)
• Case No.: 2:24-cv-03951-PSG (RAOx)
• Filed: May 10, 2024
• Involvement of '886 patent: The complaint asserted the '886 patent (among a six-patent portfolio including 8,595,778; 8,645,517; 8,719,886; 9,021,112; 10,924,573, per RPX). Count IV of the First Amended Complaint was for infringement of the '886 patent.
• Outcome/Status: Dismissed. On September 16, 2024, the court granted Google's motion to dismiss the '886 patent count, holding all 19 claims invalid under 35 U.S.C. § 101 (Dkt. No. 28 at 12–15). Sandpiper expressly reserved its right to appeal the order. (The First Amended Complaint labels Count IV as "DISMISSED BY THE COURT'S SEPTEMBER 16, 2024 ORDER.") No appeal has been confirmed in my search results.
• Sources: https://dockets.justia.com/docket/california/cacdce/2:2024cv03951/[925901](/patent/925901) ; PTAB exhibit (C.D. Cal. Dkt. 28, Sept. 16, 2024) via docketalarm.com

2. Google LLC v. Sandpiper CDN, LLC (IPR)

• Petitioner: Google LLC
• Patent Owner/Respondent: Sandpiper CDN, LLC
• Jurisdiction: PTAB (Patent Trial and Appeal Board), USPTO
• Proceeding No.: IPR2025-00952
• Filed: May 7, 2025
• Involvement of '886 patent: Petition challenging all claims 1–19 of US 8,719,886 (application no. 12/604,518) on obviousness grounds (Acharya in view of Carle; plus Schein, Fransdonk, etc.).
• Outcome/Status: Not instituted — discretionary denial. Institution was denied on October 10, 2025, under 35 U.S.C. § 314(a), citing the parallel § 101 dismissal of the '886 count in the Google district court case (per the precedential Hulu v. Piranha Media line of decisions) and other discretionary factors (delay, Fintiv).
• Sources: https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2025-00952 ; https://ai-lab.exparte.com/case/ptab/IPR2025-00952/doc/1 ; https://portal.unifiedpatents.com/ptab/case/IPR2025-00952

Related Sandpiper CDN portfolio cases (not confirmed to involve the '886 patent)

To be precise: these are Sandpiper CDN cases in the same patent family/portfolio, but based on the docket listings I found, the '886 patent does not appear among the asserted patents:

• Sandpiper CDN, LLC v. Microsoft Corporation, E.D. Tex. No. 2:25-cv-00664-JRG-RSP (filed June 26, 2025; amended complaint Oct. 30, 2025 lists 8,478,903; 8,924,466; 9,456,053; 7,922,883; 9,762,692; 10,701,173 — no '886).
• Sandpiper CDN, LLC v. Microsoft Corporation, E.D. Tex. No. 2:26-cv-00681 (filed 2026; asserts 9,021,112; 7,822,871; 7,860,964; 9,660,876; 9,647,899; 10,116,738; 8,156,066; 8,645,517 — no '886).
• Sandpiper CDN, LLC v. Comcast Cable Communications, LLC, E.D. Tex. No. 2:24-cv-00886-JRG (filed Nov. 1, 2024; complaint analysis references 9,628,347 and 9,660,876 — no '886 confirmed).
• Microsoft Corporation v. Sandpiper CDN, LLC, IPR2026-00095 (PTAB) — docket references the Google/Comcast cases; I could not confirm the '886 patent is at issue there.

Summary

Known litigation specifically involving US 8,719,886 is limited to (1) the C.D. Cal. Google case where the '886 claims were dismissed under § 101 (Sept. 16, 2024), and (2) Google's IPR2025-00952, which was denied institution (Oct. 10, 2025). The Google Patents page for the patent flags "family has litigation" and lists IPR2025-00952 as "Not Instituted – Procedural," consistent with the above. If you need the full PACER docket for the Google district court case (e.g., to check for a notice of appeal of the § 101 dismissal), that would be the next step — my searches did not surface an appeal filing.

The first search surfaced IPR2025-00952 (Google LLC v. Sandpiper CDN, LLC) — note the second search's results about "the '871 patent" (IPR2015-00411 et al.) concern a different patent, U.S. 7,365,871, not 8,718,986. I'll keep those strictly separate. Let me dig deeper into IPR2025-00952 and check for any other proceedings on this specific patent.

IPR2025-00952 is confirmed as a real, recently-decided proceeding on this exact patent. I need to verify: (a) the petition grounds/claims for IPR2025-00952, and (b) whether any other IPRs (e.g., the Microsoft/Sandpiper IPR2026 batch) target 8,719,886 specifically versus other Sandpiper portfolio patents.

Proceedings overview

The USPTO Open Data Portal block in this prompt lists zero AIA trial proceedings for US 8,719,886 as of the most recent ingest — but web search surfaces one real, recently-decided proceeding that the ODP has not yet indexed: IPR2025-00952 (Google LLC v. Sandpiper CDN, LLC), which was denied institution on discretionary grounds on 2025-10-10. Status breakdown: 1 institution denied / 0 active / 0 settled / 0 claims invalidated / 0 claims sustained by Final Written Decision. Bottom line for a defendant: no PTAB proceeding has ever reached the merits on this patent — all 19 claims remain in force and PTAB-untested, so there is no IPR-based claim cancellation to exploit; the proven defensive lever is the parallel district court's § 101 ineligibility ruling, which is what caused the PTAB to decline review.

IPR2025-00952 — Google LLC v. Sandpiper CDN, LLC

• Type: Inter Partes Review
• Filed: 2025-05-07
• Status: Discretionary Denial — institution denied; proceeding closed without trial (Google Patents labels it "Not Instituted - Procedural"). No FWD, no claims canceled.
• Judge panel: Decision issued by Kalyan K. Deshpande, Acting Chief Administrative Patent Judge (the denial order covered this case and companion IPR2025-00846 (US 8,595,778) together; it does not appear to be a standard three-APJ panel — I could not confirm additional APJs).
• Petition grounds (all § 103 obviousness, challenging claims 1–19):
  • Ground 1: Claims 1–19 obvious over Acharya (US 2008/0313669) in view of Carle (US 2007/0198839) — SCTE-35 ad-cue/trigger detection plus geo-based blackout substitution.
  • Ground 2: Claims 2, 14, 16 obvious over Acharya + Carle + Schein (US 2003/0005445) — EPG limitations.
  • Ground 3: Claim 9 obvious over Acharya + Carle + Fransdonk (US 2003/0165241) — IP-address "proximity parameter" limitations.
  • Petitioner was represented by Erika Arner et al. (Finnegan); Patent Owner by Jason Eisenberg and Dan Block (Sterne Kessler).
• Institution decision: Denied — 2025-10-10, under 35 U.S.C. § 314(a). Patent Owner's discretionary-denial request was granted because the challenged claims are the subject of parallel district court litigation (Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951 (C.D. Cal.)) in which the court already entered judgment that the challenged claims are invalid under 35 U.S.C. § 101. Citing Hulu, LLC v. Piranha Media Distribution, LLC, IPR2024-01252 (informative), the Board held it is "not an efficient use of Board resources" to re-review claims a court has already found ineligible, and denied the petition (Decision Denying Institution, IPR2025-00846/-00952, Paper 9; also on PTACTS).
• Final Written Decision: None — no trial was instituted.
• Settlement / termination: No settlement. The proceeding terminated by the denial order (close date 2025-10-10).
• Appeal: No FWD to appeal; institution denials are final and non-appealable under 35 U.S.C. § 314(d). I found no mandamus petition specific to this case. (Separately, Sandpiper reserved its right to appeal the C.D. Cal. § 101 dismissal of its '886 count — that is district-court, not PTAB, litigation.)
• Defensive value: For a defendant facing assertion today, this proceeding is a nullity on the merits — claims 1–19 were not substantively reviewed, and no estoppel attached to Google. But the Board's stated reason for denying review is the real story: the '886 claims were already dismissed as patent-ineligible under § 101 in Sandpiper v. Google (Dkt. 28 at 12–15, 2024-09-16), and Sandpiper's own amended pleading confirms that count was dropped. An Alice/Mayo § 101 challenge — not an IPR — is the defense that has actually worked against this patent.

Sources: PTACTS petition (IPR2025-00952) and Decision Denying Institution; IPverse/GreyB case page; Ex Parte case page; CourtListener (Sandpiper v. Microsoft, 2:25-cv-00664, and the Google complaint exhibit showing the dismissed '886 count).

Strategic summary

Claims status: CANCELED vs. SUSTAINED vs. UNTESTED. No claim of US 8,719,886 has been canceled in any AIA trial — the only proceeding (IPR2025-00952) was denied institution, so there is no Final Written Decision and no claim has been "sustained" by the PTAB either. All of claims 1–19 remain in force and are entirely PTAB-untested on § 102/§ 103 grounds. The patent is therefore not "hardened" by an IPR win; it is simply untouched. The only merits-level finding against the patent anywhere is the C.D. Cal. § 101 dismissal in the Google case, which is district-court authority, not PTAB estoppel.

Estoppel landscape. Because institution was denied, no § 315(e) estoppel attaches — to Google or anyone else. The Acharya/Carle/Schein/Fransdonk § 103 combinations Google developed remain fully available to any defendant, both in district court and in a future, properly-postured IPR petition. The practical obstacle is not estoppel but the Board's current discretionary-denial posture (2025 Interim Memo; Hulu v. Piranha Media): where a court has already adjudicated the challenged claims invalid under § 101, the Board is signaling it will decline to re-review the same claims on other grounds. A re-filed IPR would need either a changed litigation posture or a narrowing of the challenge to claims/grounds a court has not already adjudicated.

Pattern signals. Sandpiper CDN, LLC (the 2024-04-26 assignee of Level 3 Communications' CDN portfolio) is running a broad monetization campaign against Google and Microsoft, and the PTAB docket shows a coordinated, portfolio-wide wave of petitions — IPR2025-00806, -00826, -00846, -00860, -00952, -00969, -01010 and IPR2026-00095 (Microsoft), among others, with multiple institution decisions in Nov–Dec 2025. Only IPR2025-00952 targets the '886 patent itself; the others challenge sibling Sandpiper/Level 3 patents (e.g., IPR2025-00846 concerns US 8,595,778; IPR2026-00095's PO brief references US 8,478,903). One caution: Google Patents' litigation metadata labels IPR2025-00952's petitioner as "Unified Patents PTAB Data" — that is a data-source attribution, not a real party; the actual petitioner is Google LLC (per the PTACTS decision and case dockets). There is no defensive-aggregator petition on this patent.

Recommended next steps

• No claims are invalidated, so there is no PTAB FWD canceling anything to cite. The two documents that matter are: (1) the Decision Denying Institution in IPR2025-00846/-00952 (2025-10-10, Acting Chief APJ Deshpande) — quote its holding that the challenged claims were already adjudicated invalid under § 101 and that further review would not be an efficient use of Board resources; and (2) the C.D. Cal. order in Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951, Dkt. 28 at 12–15 (2024-09-16), which dismissed the '886 count as patent-ineligible — this is your strongest, battle-tested defense.
• No active PTAB proceeding exists on this patent, so there are no pending trial-stage milestones (no institution deadline, no oral hearing, no FWD due date) to track. If Google or another party re-files, the statutory clock would be: institution decision ~3 months after filing; FWD 12 months from institution — but expect a repeat of the discretionary-denial analysis if the § 101 judgment remains standing.
• If you are a defendant served with a demand citing US 8,719,886: (a) lead with a § 101 eligibility challenge on the strength of the Google dismissal; (b) hold the Acharya/Carle/Schein/Fransdonk § 103 combinations in reserve — they are unestoppable and PTAB-ready if the litigation posture changes; (c) monitor the Federal Circuit for any appeal of the C.D. Cal. § 101 ruling (Sandpiper expressly reserved that right) — reversal there would change both the district-court and PTAB calculus.

Caveat: My web search was cut off before I could exhaustively verify whether any of the other 2025–2026 Sandpiper IPRs (IPR2025-00806, -00826, -00860, -00969, -01010) challenge this specific patent — the available docket excerpts tie them to other portfolio patents. If the ODP ingest catches up and shows additional proceedings on 8,719,886, this analysis should be updated.

I found a key lead — the Microsoft IPR exhibit referencing the Level 3 → Sandpiper assignment at Reel 068256, Frames 0091-0115. Let me dig deeper into the assignment records and Sandpiper's corporate details.

Good background — Sandpiper CDN is the Level 3/Lumen patent divestiture vehicle. Now let me pin down the exact recorded assignments, including the original Maloney → Level 3 assignment and any intermediate transfers.

I've hit my search step limit, so I'll now consolidate what the available sources support — and flag explicitly what could not be verified.

Assignment and NPE Analysis — US 8,719,886 B2

Verification caveat up front: I could not reach the USPTO Assignment Center directly in this session. Reel/frame data below comes from Google Patents legal-event records and the PTAB exhibit list in Microsoft v. Sandpiper CDN, IPR2026-00190 (Exhibit 1036, "Patent Assignment Cover Sheet from Level 3 Communications, LLC to Sandpiper CDN, LLC, Reel No. 068256, Frames 0091-0115"). One source in the earlier summary cited Reel 067244/0690 for the same transfer; I flag that discrepancy below rather than choosing between them.

Inventors

• Ian Maloney — sole named inventor; Dublin, Ireland (IE) per the patent's front page. Employer at filing: determinable only by inference — the application (US 12/604,518, filed Oct. 23, 2009) was immediately assigned to Level 3 Communications, LLC, and Level 3 maintained a Dublin office; the inventor appears to have been a Level 3 employee. This is not confirmed from a source in this session.
• Unusual patterns: None of the "all inventors depart within 12 months" type — there is only one inventor, and the inventor-to-company assignment was contemporaneous with filing (recorded Oct. 23, 2009 per Google Patents), which is the normal employment-assignment pattern.

Original assignee

• Level 3 Communications, LLC (Broomfield, CO) — the entity named on the issued patent. An operating tier-1 IP-backbone and content delivery network (CDN) operator. The '886 claims (dynamic processing of streamed content — trigger-signal-based ad insertion/blackout and subscription-database authorization) are plausibly embodied in Level 3's CDN/streaming services, which trace to the Sandpiper Networks → Digital Island → Savvis → Level 3 lineage (Jan. 2007 acquisition) described in Sandpiper's own E.D. Tex. complaint.
• Current status: Level 3 Communications, LLC was acquired by CenturyLink (Nov. 2017), which rebranded as Lumen Technologies (Sept. 2020). Level 3 Communications, LLC survives as a Lumen subsidiary; Lumen is publicly traded (NYSE: LUMN). The CDN patent portfolio (400+ patents, including '886) was moved out of Level 3 in 2024 (below).

Assignment timeline

1. ~2009-10-23 (recorded; execution date not retrievable) — Reel/frame not retrieved

• Conveyance: Assignment of Assignors Interest (inventor-to-company)
• Assignor: Ian Maloney
• Assignee: Level 3 Communications, LLC
• Correspondent: not retrievable in available sources
• Context: Standard employment assignment at filing; Google Patents legal events list "ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS), Assignors: MALONEY, IAN" dated 2009-10-23.

2. 2024-04-26 (recorded; execution date not retrievable) — Reel 068256, Frames 0091-0115 (per Microsoft IPR2026-00190, Ex. 1036 via docketalarm); earlier summary also cited Reel 067244/0690 — discrepancy unresolved; likely the same document or one is a correction

• Conveyance: Patent Assignment (cover sheet)
• Assignor: Level 3 Communications, LLC
• Assignee: Sandpiper CDN, LLC
• Correspondent: not retrievable in available sources
• Context: Transfer-to-asserter — divestiture of the Level 3 CDN patent portfolio out of the operating company into a patent-holding LLC, followed within two weeks by the first infringement suit (below). Google Patents lists "2024-04-26 Assigned to SANDPIPER CDN, LLC ... Assignors: LEVEL 3 COMMUNICATIONS, LLC."

No other recorded assignments were surfaced. The chain is short: inventor → Level 3 (2009) → Sandpiper CDN (2024).

Timeline diagram

timeline
    title Ownership of US 8719886
    2008 : Filed by Ian Maloney
    2009 : Assigned to Level 3 Communications
    2014 : Patent issued
    2024 : Assigned to Sandpiper CDN LLC
         : Google infringement suit filed
    2025 : Google IPR filed
         : IPR denied not instituted

NPE / troll-pattern signals

1. Shell-entity transfer — present. The '886 moved from an operating telecom/CDN carrier (Level 3 Communications, LLC) to Sandpiper CDN, LLC, a patent-holding LLC. Concrete evidence beyond the name: Sandpiper's own E.D. Tex. complaint describes it as the entity that "holds all rights and title to a portfolio of more than 400 patents" and does not describe any operating CDN business or products (PTACTS document, ¶32). Transfer recorded 2024-04-26, Reel 068256/0091-0115.

2. Known asserter in the chain — present. Sandpiper CDN, LLC is a high-frequency plaintiff in the Unified Patents / RPX sense: it has sued Google (C.D. Cal. 2:24-cv-03951, May 10, 2024), Comcast (E.D. Tex. 2:24-cv-00886, Nov. 1, 2024), and Microsoft (E.D. Tex. 2:25-cv-00664 and 2:26-cv-00681). Google Patents flags "family has litigation" for '886 and lists IPR2025-00952. This is a repeat-plaintiff monetization vehicle, not a one-off.

3. Repeat correspondent across the chain — unclear. I could not retrieve the correspondent names from either recorded cover sheet in this session. The prior summary did not capture them either. No finding either way.

4. Cascading transfers — not present. Only two recorded assignments, 15 years apart (2009 inventor→company; 2024 company→LLC). No chained LLC pass-throughs.

5. Pre-litigation transfer — present. The Level 3 → Sandpiper CDN assignment was recorded 2024-04-26; the first infringement suit naming the '886 patent (Sandpiper v. Google, C.D. Cal.) was filed 2024-05-10 — 14 days later, squarely inside the six-month window and consistent with arranging a clean standing record for assertion.

6. Bankruptcy fire-sale — not present. Level 3 passed to CenturyLink/Lumen via acquisition (Nov. 2017), not Chapter 7/11. No court-supervised patent sale.

7. Privateering — present, with one caveat. An operating company (Level 3, via its Lumen parent) transferred its CDN portfolio to an NPE that asserts against CDN competitors (Google, Microsoft, Comcast) — the classic privateering shape. Caveat: I could not confirm from this session's sources whether Lumen retains an economic stake in Sandpiper CDN's recoveries; the transfer could equally be an arm's-length sale to an independent assertion fund. The pattern (operating co. → LLC → immediate suits against competitors) is nonetheless documented.

8. Defensive aggregator (anti-NPE) — not present. The chain terminates at Sandpiper CDN, LLC, not at RPX, AST, LOT, Unified Patents, or OIN. Inverse signal does not apply.

Verdict

NPE — high confidence.

Three strong signals drive this: (1) the patent left an operating carrier and landed in a patent-holding LLC with no described products (Reel 068256/0091-0115, recorded 2024-04-26); (2) the transfer occurred 14 days before the first infringement suit against Google (filed 2024-05-10, C.D. Cal. 2:24-cv-03951) — a textbook pre-litigation transfer for standing/venue; and (3) Sandpiper CDN is a repeat high-frequency plaintiff (Google, Microsoft, Comcast). The privateering profile (Level 3/Lumen lineage asserted against CDN competitors) reinforces the call. Residual uncertainty is limited to the unretrieved correspondent names and the Reel 067244 vs. 068256 discrepancy, which should be reconciled by pulling the cover sheets directly.

Verify at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (search patent no. 8719886; confirm Reel 068256/0091-0115 vs. Reel 067244/0690 and capture correspondent names for both records).

I've exhausted my available search steps, so I'll answer from the verified search results I retrieved (the official patent PDF front page hosted by USPTO/Google Patent Images, FreePatentsOnline's reference listing for 8,719,886, and Google Patents family/citation pages). I'll flag everything I could not verify.

Prior Art Analysis — US 8,719,886 B2 ("Dynamic Processing of Streamed Content")

0. Preliminary caveats (read first)

1. The complete "References Cited" list is large (roughly 100+ entries) and I could not retrieve it in full within my search budget. The official PDF front page (https://patentimages.storage.googleapis.com/b8/19/11/6c23292cad533f/US8719886.pdf) contains the authoritative list; my retrieval captured (a) the recent 2006–2008 U.S. publications/patents block (via FreePatentsOnline) and (b) the older 1990–1999 U.S. patent block (via the PDF snippet). There is a gap in the middle (roughly 1999–2005, including most 6,xxx,xxx patents) that I could not retrieve. Treat the list below as a verified subset, not the complete citation list.
2. I do not have verbatim claim text (consistent with the prior sections of this analysis). The '886 patent has 19 claims (per IPR2025-00952, which challenged claims 1–19), with two independent method embodiments: (i) Claim 1-type: content delivery manager — receive video stream → detect trigger signal (temporal mark injected by content publisher) → process trigger to decide whether to modify delivery → modify delivery (ad insertion, blackout, discontinuation); and (ii) second independent claim-type: authorization manager — receive end-user request → query content publisher's subscription database → process reply → notify if unauthorized / initiate delivery if authorized. Claim-to-reference mapping below is at the feature level, not element-by-element, pending retrieval of the verbatim claims.
3. Statutory frame: The application was filed Oct. 23, 2009 with priority to Nov. 12, 2008, so pre-AIA 35 U.S.C. § 102 governs. Every reference below published before Nov. 12, 2008, so each is at least § 102(a) (known/used/publication) and § 102(b) (printed publication >1 year before) prior art. Whether any single reference anticipates (discloses every element) versus merely renders obvious (§ 103) is analyzed per reference. Notably, in IPR2025-00952, Google relied on combinations (Acharya + Carle; + Schein; + Fransdonk; + Risan; + Kan), i.e., the petitioner itself treated the closest art as § 103 combinations, not single-reference § 102 anticipation.
4. Sibling-patent distinction: The EP family member EP2353122A4's EPO search report cites 7 references (US6275825B1 Casio; US20030063752A1 General Instrument; US20070179950A1 Websense; US20040059913A1 Sun; US20040128499A1 General Instrument; US20040168052A1 Clisham; FR2893731A1 Issard). That EP application corresponds to the sibling US 8,595,778 ("User authentication in a content delivery network"), not to the '886 patent. I exclude those from the '886 citation list except where they overlap with examiner-cited '886 references (only US20070179950A1/Kester overlaps).

1. Most relevant prior art — trigger-signal / stream-modification claim (Claim 1-type)

2. Content delivery network (CDN) infrastructure art — Farber/Seed/Level 3 family (mostly background)

These are largely Level 3's own CDN applications, cited as background for the CDN delivery environment (FIGS. 9–10 content delivery networks 950/1045). They are unlikely to anticipate the trigger or authorization claims alone (none discloses the publisher-injected temporal trigger or the subscription-database "dip") but are relevant to § 103 combinations for the "delivery across a CDN" elements:

• US 2008/0215755 A1 — Farber et al., "Delivering resources to clients in a distributed computing environment with rendezvous based on load balancing and network conditions" (pub. Sep. 2008)
• US 2008/0215750 A1 — Farber et al., "Controlling subscriber information rates in a content delivery network" (pub. Sep. 2008)
• US 2008/0215735 A1 — Farber et al., "Resource invalidation in a content delivery network" (pub. Sep. 2008)
• US 2008/0140800 A1 — Farber et al., "Shared content delivery infrastructure & method of generating a web page" (pub. Jun. 2008)
• US 2008/0104268 A1 — Farber et al., "Controlling subscriber information rates in a content delivery network" (pub. May 2008)
• US 2008/0071855 A1 — Farber et al., "Distributing and accessing data in a data processing system" (pub. Mar. 2008)
• US 2007/0233884 A1 — Farber et al., "Shared content delivery infrastructure" (pub. Oct. 2007)
• US 2007/0233846 A1 — Farber et al., "Delivering resources to clients in a distributed computing environment" (pub. Oct. 2007)
• US 2007/0233706 A1 — Farber et al., "Shared content delivery infrastructure with rendezvous based on load balancing and network conditions" (pub. Oct. 2007)
• US 2007/0233705 A1 — Farber et al., "Method of generating a web page" (pub. Oct. 2007)
• US 2008/0071859 A1 — Seed et al., "Popularity-based selective replication in content delivery network" (pub. Mar. 2008)
• US 2008/0065724 A1 — Seed et al., "Peer server handoff in content delivery network" (pub. Mar. 2008)

§ 102 assessment: None of these alone plausibly anticipates either independent claim (no trigger-signal processing; no subscription-database authorization query). They are classic § 103 combination components for the CDN delivery environment.

3. Content-publication and web-services art

• US 2008/0263602 A1 — Murray et al., "System for managing distributed assets in an electronic content asset publication system" (pub. Oct. 2008) — asset publication/management; background for "content source/publisher" elements.
• US 2008/0263056 A1 — Murray et al., "Electronic content asset publication system" (pub. Oct. 2008) — companion application; same assessment.
• US 2008/0275987 A1 — Gardell et al., "Methods and apparatus for integrating services for accessing the world wide web" (pub. Nov. 2008) — web-service integration; relevant to web-server front-end/authorization request flow (FIG. 16).
• US 7,404,010 B2 — Gardell et al., same title (issued Jul. 2008) — the issued counterpart; same assessment.
• US 2007/0179950 A1 — Kester et al., "System and method for adapting an internet filter" (pub. Aug. 2007) — also in the EPO search report for the sibling '778 family; discloses policy-based filtering/access control of internet content. Most relevant of this group to the authorization-manager claim (restricting delivery based on user attributes), though it lacks the content-publisher subscription-database "dip" that defines the second independent claim.

4. Legacy EPG / television-schedule patents (1990s block — partially retrieved)

The official PDF front page shows a substantial block of 1990s EPG/television-schedule patents. These appear to have been cited for the EPG/blackout/geo-filtering and subscription-TV background (FIGS. 10, 13–14). I retrieved the beginning of this block. Titles/assignees for several entries below are from my training knowledge and are marked with confidence levels — I could not re-verify each in the search results, and OCR in the PDF snippet introduced apparent errors (e.g., "Zeresski, Jr." and "Kosterstel" are likely OCR corruptions — I have not silently corrected them).

§ 102 assessment for Group 4: These are 1990s EPG/TV-schedule systems. None plausibly anticipates either independent claim — none discloses real-time streaming over a network to an end-user client, a content delivery manager detecting a publisher-injected trigger signal in a video stream, or an authorization manager querying a content publisher's subscription database for Internet stream delivery. They are background/§ 103 components at most.

5. Bottom line

• Single-reference § 102 anticipation risk is concentrated in the 2006–2008 block, specifically US 2008/0201736 A1 (Gordon et al., "Using Triggers with Video for Interactive Content Identification") for the trigger-signal independent claim, and US 7,188,085 B1 (Pelletier), US 2007/0016926 / 2007/0033613 (Ward III), and US 2006/0288366 (Boylan III) for the targeted-ad/EPG/geo-filtering dependents.
• For the authorization-manager independent claim, the closest cited art is US 2007/0179950 A1 (Kester et al.) (policy-based internet filtering) and the subscription-TV distribution patents (US 4,977,455; US 5,151,789); none alone discloses the full "query the content publisher's existing subscription database → process reply → notify/initiate" flow, which is why the IPR petition (IPR2025-00952) proceeded on § 103 combinations rather than § 102 anticipation, and why the district court's dismissal of all 19 claims was under § 101 (eligibility), not § 102/103.
• Verification steps still needed: (i) retrieve the complete front-page "References Cited" from the USPTO PDF to fill the 1999–2005 gap and confirm the full 1990s block; (ii) pull the verbatim claims from PatentCenter to convert the feature-level mapping above into element-by-element § 102 charts; (iii) confirm the OCR-corrupted entries (5,654,856 "Zeresski"; 5,822,324 "Kosterstel") against the printed PDF — I deliberately did not auto-correct them.

Obviousness Analysis — U.S. Patent 8,719,886 B2 ("Dynamic Processing of Streamed Content")

Scope and basis of this analysis

All 19 claims of the '886 patent were challenged for obviousness in Google LLC v. Sandpiper CDN, LLC, IPR2025-00952 (petition filed May 7, 2025). The PTAB denied institution on October 10, 2025 on discretionary grounds (parallel § 101 litigation in Sandpiper v. Google, C.D. Cal. 2:24-cv-03951) — not on the merits. This analysis therefore independently assesses the § 103 case on the merits, using the prior-art combination the petition built: Acharya (US 2008/0313669 A1) in view of Carle (US 2007/0198839 A1), with Schein (US 2003/0005445 A1) and Fransdonk (US 2003/0165241 A1) as secondary references. The petition's exhibit list also includes Kan and Urdang as background evidence of the POSITA's knowledge of SCTE-35 cue signaling.

Caveat on claim text: The verbatim claims were not in the patent text provided; the element-by-element mapping below uses the claim limitations as quoted in the petition and expert declaration (e.g., [1.b], [8.b.i], [8.b.ii], [9], [12.c]–[12.d], [13], [14.a]–[14.e], [16.a]–[16.c], [18.c.i]–[18.c.ii]). The independent claims are: claim 1 (method — receive stream, detect trigger signal, process trigger, query data repository, modify delivery), claim 14 (method — pre-authorized client, human-injected trigger, EPG query, ad/geo-filter response, modify delivery), and claim 15 (system — content server with programming-schedule information). All limitations quoted below are as they appear in the IPR record.

I. The prior art (scope and content)

1. Acharya — US 2008/0313669 A1, "Targeted Advertisement Insertion with Interface Device Assisted Switching"

• Publication date: Dec. 18, 2008; priority/filing: June 18, 2007 (Swarup Acharya, Bhawna Gupta, Anurag Srivastava; Alcatel-Lucent). Issued as US 8,949,886 B2 (Feb. 3, 2015). Because it was filed before the '886 priority date (Nov. 12, 2008), it is § 102(e) prior art.
• Disclosures (confirmed from the issued patent and petition citations):
  • A signal-distribution system (cable, satellite, IPTV) with a detection server 202 that receives a live video feed 212 ("video stream") and "processes the original content stream to detect ad markers or other ad cues in that stream," including "conventional SCTE-35 signaling messages inserted into packets of an MPEG stream." (Acharya ¶¶[0034], [0054]; petition ¶82).
  • The cues are "embedded" into the video stream at service provider 106 before transmission — i.e., injected upstream by the content/service provider, and the detected cues "provide timing information indicating the beginning and duration of a given ad slot in the original content stream" — a temporal mark. (Acharya ¶[0034]; petition ¶85, comparing to '886 at 18:29–33.)
  • An ad server 204 generates a second stream with targeted information, and the user interface device 112 (set-top box) switches from the first stream to the second based on the timing information (Acharya Abstract, ¶¶[0029]–[0036], Figs. 3, 4A–4C, 5).
  • Subscribers ("client[s]") at locations 104 are "permitted to access one or more television services by virtue of his or her subscription" (Acharya ¶[0021]); demographic and regional targeting of ads.
• What Acharya does not emphasize: blackout/geo-restriction logic and querying an external programming-schedule repository — that gap is filled by Carle.

2. Carle — US 2007/0198839 A1, "Methods and systems for blackout provisioning in a communication network"

• Published Aug. 30, 2007 (well before the '886 priority date). Issued as US 8,233,623 B2.
• Disclosures (confirmed from the petition citations):
  • Media server 510 (including acquisition server 102) receives program content ("video stream") from content source 512 for delivery to users of a content provider 502 ("content publisher") (Carle ¶¶[0108]–[0113]).
  • Program substitution during blackout windows using the same SCTE-35 signaling used in Acharya (Carle ¶[0042]); the acquisition server queries acquisition service database 112 "to get configuration information, rights, and boundary keys," which "starts the program substitution" (Carle ¶[0043]).
  • Querying program guide source 514 for "program guide data" stored in "an EPG server" (petition ¶100; Carle ¶[0105] — guide data enables navigation of "broadcast programs [and other] content of interest").
  • Geographic restriction data: ZIP codes, FIPS/SAME codes, "Geographic Region Code," MAC-address-based device lists (Carle ¶[0025]); blackout/substitution event timing via "WindowStart," "WindowEnd," "Start," "End" parameters (petition ¶118).
  • Substitution can be handled "by manual input" through "a management interface ... typically used at the direction of the affected content provider," where "an operator defines" the blackout window by scheduling or manually starting it (Carle ¶¶[0023], [0026]) — i.e., a human-injected trigger.
  • Inserting targeted advertising into the blackout window and blocking access to content for unauthorized users (Carle ¶¶[0017], [0019]–[0024]; petition ¶99).

3. Schein — US 2003/0005445 A1, "Systems and methods for linking television viewers with advertisers and broadcasters"

• Published Jan. 2, 2003 (priority 1995). A canonical interactive television program guide (ITPG) reference: schedule data identifying programs per channel per time slot, local/geographic lineups, remote database delivery, viewer interaction linking to advertisers/broadcasters. Used for the EPG limitations (claims 2, 14(c), 16(a)).

4. Fransdonk — US 2003/0165241 A1

• Published Sept. 4, 2003. Per the petition, Fransdonk expressly teaches using a requester's IP address to map the user to a geographic location for controlling content access — the mechanism needed for claim 9.

5. Supporting references (POSITA-knowledge evidence)

• Kan (Ex. 1015): "Advertisement insertion in traditional solutions is often based on a set of standards known as the ... (SCTE) Nos. 35 and 30"; "By configuration, profile, or other criteria, the SCTE 35 triggers the end device ... to join a particular multicast advertisement stream of interest" (Kan ¶¶[0004], [0032]).
• Urdang (Ex. 1016): "Cue tones have been inserted into analog program streams by content providers to indicate insertion points for advertisements by cable systems"; SCTE-35 supports splicing digital streams via cue messaging (Urdang ¶¶[0014]–[0015]).

II. Level of ordinary skill and the legal framework

A POSITA at the November 12, 2008 priority date would be someone with a bachelor's degree in computer science, electrical engineering, or equivalent, and 2–4 years of experience in streaming-media delivery, IPTV/cable/satellite headend systems, ad insertion, and conditional access/geographic restriction — i.e., the overlapping fields of both primary references. (The petition's expert, Lin, opines at the same level; petition ¶¶50–52.)

Under 35 U.S.C. § 103 and KSR Int'l Co. v. Teleflex Inc. (2007), obviousness is established where combining prior-art elements "according to known methods" yields predictable results, where a technique is a "simple substitution of one known element for another to obtain predictable results," and where the combination is within the grasp of "a person of ordinary skill [who] is also a person of ordinary creativity, not an automaton." The Graham factors — scope/content of the prior art, differences, level of skill, and secondary considerations — frame the inquiry below.

III. Ground 1 — Claims 1–19 obvious over Acharya in view of Carle

A. Element-by-element mapping of independent claim 1

B. The gap and why the combination closes it

Acharya alone provides the full trigger-signal/ad-insertion engine but lacks geographic blackout rules and data-repository-driven modification decisions; Carle alone provides the blackout/substitution engine with geo-parameters, rights/boundary keys, and EPG queries but is not focused on targeted ad selection. The combination is a textbook two-reference completion: every structural element of the claim exists in one of the two references, and the references operate on the identical signaling substrate (SCTE-35) in the identical environment (cable/satellite/IPTV headend-to-STB distribution).

C. Motivation to combine (KSR)

1. Same problem, same environment, same standard: Both references address "how a headend system decides, in real time, whether and when to substitute alternate content into a program stream." Both use SCTE-35 signaling messages. A POSITA reading Acharya would immediately recognize Carle as the companion art on the "when not to show the original content" side of the same problem.
2. Explicit teaching in Carle to insert ads during blackouts: Carle itself teaches providing "alternate advertising information" during a blackout window (¶¶[0017], [0019]–[0024]). The motivation to add Acharya's targeted-ad machinery to Carle's blackout window is not hindsight — Carle already identifies the blackout window as an ad opportunity; Acharya supplies the known mechanism for filling it with targeted ads.
3. Complementary, non-competing disclosures: Acharya targets by demographic; Carle restricts by geographic region and time window. Combining them yields the "geographically-aware targeted advertising during blackouts" that the petition's expert describes, with the benefit that users not subject to the blackout retain the original content while blacked-out users receive targeted substitution (petition ¶99).
4. Predictable result / reasonable expectation of success: The combination "is nothing more than combining known elements ... to produce the expected results taught by Carle of inserting targeted advertising into a blackout window" (petition ¶99). Both systems already splice MPEG streams at SCTE-35 cue points; no new protocol, hardware, or architecture is required.

D. Dependent claims — representative mapping

• Claim 2 (EPG): Carle's "program guide data" from "an EPG server" (¶[0105]); EPGs as schedule-of-available-content repositories were "well known in the art" (petition ¶¶100–101, citing Wasilewski).
• Claim 3 (synchronization info = geo-filtering and/or ad info): Acharya's timing information synchronizes ad placement (¶[0034], [0036]); Carle's rights/boundary keys and region codes provide geo-filtering information (¶¶[0023]–[0025], [0043]).
• Claims 7–8 (proximity parameters; discontinuing delivery due to time and/or geography): Carle groups restricted devices by location ("proximity parameters") and captures substitution windows as "WindowStart"/"WindowEnd" and "Start"/"End" times — i.e., discontinuation "based on a time relative to the detection of the trigger signal" and "a geographic location associated with the client" (petition ¶¶117–122; Carle ¶[0025]).
• Claims 10–12 (ad determination; ad-server query; candidate selection by geography): Acharya's ad server selects among targeted ads based on user attributes (¶¶[0029]–[0036], [0055]–[0057]); Carle supplies the geographic dimension for selecting the candidate (petition ¶¶126–127, [12.c]–[12.d]).
• Claim 13 / [14.b] (human-injected trigger): Carle's "manual input" via a management interface "typically used at the direction of the affected content provider," where "an operator defines" the window (¶¶[0023], [0026]) is a direct disclosure — the human is associated with the content publisher.
• Claim 14 (independent, EPG-centric): Mapped element-by-element from [14.a] pre-authorized client (Acharya's subscribers; Carle's authorized device lists) → [14.b] human-injected trigger (Carle manual input) → [14.c] EPG query (Carle EPG server) → [14.d] ad/geo-filter response (Carle rights/boundary keys + Acharya ad data) → [14.e] modification (both).
• Claim 15 (system): Acharya's detection server + ad server and Carle's media server 510/acquisition server 102 with access to program-schedule databases satisfy the content-server-plus-schedule-information claim, with the same motivation.

IV. Ground 2 — Claims 2, 14, and 16 obvious over Acharya + Carle + Schein

Why Schein is needed

Carle already discloses querying an EPG server (¶[0105]), and the petition mapped claim 2's EPG limitation to Carle alone. Schein is added as belt-and-suspenders to supply conventional EPG implementation details: a schedule "identify[ing] when various content provided by the content publisher will be available," displayed per channel per time slot, delivered from a remote database, and personalized/regionalized by geography — exactly the "schedule ... for reception by authorized clients" language of claims 2, 14(c), and 16(a).

Motivation to combine

• The Acharya/Carle system already contemplates an EPG (Carle ¶[0105]); Schein merely supplies known, standard techniques for implementing that EPG.
• Schein's program guide is expressly designed to link viewers with advertisers and broadcasters — the same advertising ecosystem as Acharya and Carle — and its schedule data is geographically tailored, complementing Carle's geo-restriction regime.
• Under KSR, implementing a known feature (EPG) with a known implementation (Schein) for its known purpose (scheduling/geo-personalized content availability) is the paradigm of obviousness; the petition correctly characterized it as "implementing a feature of the Acharya/Carle system ... using known, standard techniques for EPGs as detailed in Schein" (Ex. 1007).

V. Ground 3 — Claim 9 obvious over Acharya + Carle + Fransdonk

The limitation

Claim 9 (dependent on claim 7) requires that the proximity parameters "include an Internet Protocol (IP) address of the client" and processing the IP address "to determine a geographic region associated with the network from where the client receives video content."

The gap and Fransdonk's role

Acharya/Carle teach geographic targeting using ZIP codes, FIPS/SAME codes, and Geographic Region Codes (Carle ¶[0025]) — geographic proxies, not IP addresses. Fransdonk expressly teaches IP-address-to-geographic-location mapping for controlling content access (petition Ex. 1007; Ground 3 summary).

Motivation to combine

• Simple substitution of a known equivalent: IP geolocation was, by 2008, a routine technique for approximating a client's region (and the petition's expert notes it was "well-known for a user's IP address to be used for this purpose," petition ¶124).
• Same goal, better precision: Carle already wants per-region decisions; IP-address geolocation is a more granular and Internet-native way to obtain the same "Geographic Region Code" Carle already uses. The substitution produces the predictable result of geographically targeted ad insertion/blackout in an IP-delivered stream — the exact scenario the primary combination targets.
• No incompatibility: IP addresses are available in the IPTV/Internet context of both Acharya and Carle; nothing in either reference teaches away.

VI. Secondary considerations

Nothing in the record (the IPR petition, the C.D. Cal. § 101 order, or the patent itself) evidences the kind of secondary indicia that would rebut a prima facie case: no commercial-success evidence, no long-felt-but-unmet-need showing, no unexpected results, no industry skepticism or copying. The district court's § 101 holding (all 19 claims invalid as directed to an abstract idea) is a separate, non-§ 103 basis for invalidity, but it is consistent with the overall weakness of the claimed advance.

VII. Honest caveats and counterarguments

1. Claims were never construed by the PTAB. The petition was denied on procedural grounds; claim construction (e.g., "temporal mark," "data repository," "modifying delivery") could narrow or broaden the mapping above. The district court's § 101 dismissal occurred before a full Markman order on all terms.
2. "Injected into the video stream by the content publisher" ([1.b]): Acharya's cues are embedded at the service provider 106, and Carle's substitutions are directed by the content provider — but a Patent Owner could argue "content publisher" excludes the "service provider" in Acharya. The IPR record's position — that Carle's content-provider-directed manual input satisfies the limitation — is the stronger reading, particularly for claim 13/14.b.
3. Claim 15 (system) preamble and "content server comprises information related to a content programming schedule" — the petition mapped this to Carle's media server 510 with database access; a Patent Owner could argue the "comprises" language requires the schedule in the server, though "comprises" is open-ended and Carle's acquisition server queries schedule databases.
4. Secondary references are conventional-art reinforcements, not necessities: the petition itself mapped claims 2 and 14(c) to Carle's EPG server alone, so even without Schein, Ground 1 would likely carry those claims; Schein and Fransdonk mainly foreclose "missing detail" arguments.

VIII. Conclusion

The '886 patent's claims 1–19 are strongly vulnerable under 35 U.S.C. § 103. Acharya provides the trigger-signal (SCTE-35 cue) detection and targeted-ad-insertion engine; Carle provides the geographically and temporally gated program-substitution engine, the data-repository/EPG queries, the manual (human) trigger entry, and the blackout-window ad opportunity; Schein and Fransdonk supply conventional EPG and IP-geolocation details. The combination is motivated by the shared SCTE-35 signaling substrate, the shared IPTV/cable/satellite environment, Carle's own invitation to insert ads during blackout windows, and the predictable result of geographically targeted substitution — all within the competence of a POSITA, with no teaching-away and no secondary considerations to rebut the case. This is the combination Google presented in IPR2025-00952, and while the PTAB never reached the merits (discretionary denial, Oct. 10, 2025), the merits case as reconstructed here is coherent and, in my assessment, would likely have supported institution had the Board addressed it.

Key sources: IPR2025-00952 Petition (PTACTS, May 7, 2025); Lin expert declaration (PTACTS Ex. 1007); Acharya US 2008/0313669 A1 / US 8,949,886 B2; Carle US 2007/0198839 A1 / US 8,233,623 B2; Schein US 2003/0005445 A1; Fransdonk US 2003/0165241 A1; Kan (Ex. 1015) and Urdang (Ex. 1016); institution decision (IPR2025-00952, Oct. 10, 2025 — discretionary denial).