US 8606819

I'll search for authoritative information on this patent number before summarizing.

Let me check the CAFC docket and the specific claims.

US Patent 8,606,819 — Analyst Summary

Scope note: I searched for the exact identifier 8606819 only. Searches also surfaced closely-related family members and other Robocast patents, but I have separated those out below rather than merging them into this record.

1. Bibliographic data (US 8,606,819 B2)

2. Abstract (as printed)

"A method for providing content via a communications network on a user's computer, obtained from a plurality of resources in an organized arrangement is provided. The method includes creating a show structure of nodes, each node identifying a resource from a plurality of accessible resources, at least some of which are network accessible resources. Without requiring user input, a plurality of the network accessible resources, identified by a corresponding node, are automatically accessed. Content corresponding to each of the accessed resources is automatically presented through the user's computer in accordance with the show structure. Advertisement content is presented to the user in connection with the automatic presentation of the content through the user's computer."

3. Independent claims — plain-language overview

The patent has four independent claims: 1, 16, 23, and 26 (claims 2–15, 17–22, and 24–25 are dependent). In plain terms:

• Claim 1 — "Automated playlist with ads." Build a "show structure" of nodes, where each node points to a resource (at least some reachable over a network). Then, without requiring any user input, automatically fetch multiple of those resources and automatically present their content in the order/structure defined by the show. In connection with that automated presentation, show advertisement content to the user. (Dependents add: ad content is dynamic, a default ad set, interspersed, in a persistent window, delivered via a node/URL, based on the user's profile, Internet-accessible, video, displayable; altering the show structure in response to user action on the ad; mobile device; browser delivery.)

• Claim 16 — "Search results become an auto-playing show." Receive a user's online-search request; return search results with their resource locators; then build a show structure of nodes from those search results and automatically access/present the corresponding content (with at least some network-accessible resources accessed without user input). Dependents cover searching Internet content / a web site / a remote server, presenting the structure to the user (including while content is delivered), and presenting content from at least two nodes simultaneously.

• Claim 23 — "Persistent ad window." A method of creating a show structure, automatically accessing resources without user input, automatically presenting content per the structure, and causing advertisement content to be presented in a persistent content window in connection with that presentation. Dependents specify that the persistent window is a separate window from the displayed content and that it is displayed simultaneously with the content.

• Claim 26 — Independent method claim. I could not retrieve the full verbatim text of claim 26 from an authoritative grant-stage source, so I am flagging it rather than paraphrasing. It is an independent claim (claims 27–28 depend from it).

Caveat on claim text: The claim language above is drawn from the published application US 2012/0226553 (justia). In the Delaware litigation, Netflix characterized granted claim 16–22 as containing the limitation "automatically creating and storing a show structure of nodes … in response to said online search," which differs somewhat from the published-application wording ("creating a show structure of nodes based on said search results"). That suggests the granted claims' exact wording may differ from the pre-grant version. Treat the parenthetical "based on said search results" as not fully verified against the issued patent.

4. USPTO / PTAB and litigation — verifiable identifiers

PTAB (USPTO):

• IPR2023-00182 — Netflix, Inc. v. Robocast, Inc., filed Nov. 18, 2022; respondent patent 8606819; institution denied (decision June 9, 2023). Grounds referenced: claims 1–2, 7–9, 11–12, 15, and 26–28 over U.S. 5,959,623 ("van Hoff") alone or with U.S. 5,913,040 ("Rakavy").
• IPR2023-00594 — Google LLC et al. v. Robocast, Inc., filed Feb. 21, 2023; respondent patent 8606819; institution denied (decision Sept. 18, 2023).

District court (D. Del.):

• Robocast Inc. v. Netflix Inc., No. 1:22-cv-00305 — on summary judgment, Judge Jennifer L. Hall held the asserted claims of 7,155,451; 8,606,819; and 8,965,932 invalid under §101 (abstract idea; order reported Feb. 2025). All three patents are reported as expired.
• Robocast Inc. v. YouTube LLC et al., No. 1:22-cv-00304 — stayed in light of the Netflix ruling.

CAFC docket:

• 25-1651 — Robocast, Inc. v. Netflix, Inc., U.S. Court of Appeals for the Federal Circuit; appeal docketed April 17, 2025 (appeal received April 14, 2025), appellant's brief originally due June 16, 2025. This is Robocast's appeal of the Delaware §101 invalidity judgment.

5. Explicit uncertainties

1. "CAFC 2026 dockets" for 8606819: I found no authoritative 2026-specific docketing entry. The only Federal Circuit docket I can confirm for this patent is 25-1651, docketed in April 2025. Any 2026 appellate activity (e.g., briefing completion, argument, or decision) is not confirmed by my searches, and I am not going to assert a 2026 event without a source. I also found no CAFC docket bearing the number 8606819 itself (docket numbers and patent numbers are different identifiers).
2. Claim 26 text and grant-stage claim wording are not fully verified (see §3 caveat).
3. "Anticipated expiration 2017-09-02" is reported literally from the Google Patents record; I have not independently recomputed the term.
4. Sources conflict on the precise date of the Delaware summary-judgment order (Law360 reports it as the Friday before Feb. 24, 2025). I have not fixed a single date.

Sources: Google Patents US8606819B2 (patents.google.com/patent/US8606819/en); USPTO PTAB/PTACTS documents (ptacts.uspto.gov); Justia patent pages (patents.justia.com/patent/8606819 and /20120226553); IPVerse PTAB case pages for IPR2023-00182 and IPR2023-00594; Docket Alarm/Justia Dockets for CAFC 25-1651; Law360 via Latham & Watkins PDF (Netflix Sinks Robocast Playlist Patents In Del. IP Suit).

I'll research litigation involving US patent 8606819 using the specified sources.

Let me search for additional details on the specific cases and the Federal Circuit appeal.

Let me search for the outcomes of the 2025 trials and the current status.

Known Litigation Involving U.S. Patent No. 8,606,819

Important threshold facts (from the authoritative patent record):

• U.S. Patent No. 8,606,819 ("Automated Content Scheduler and Displayer"), inventor Damon Torres, assignee Robocast, Inc. Application No. 13/449,570, filed 2012‑04‑18, granted 2013‑12‑10, claiming priority to 1996‑09‑03.
• Legal status: Expired – Fee Related. Anticipated expiration 2017‑09‑02. This is materially significant because the ’819 patent is a long‑expired patent, and several courts/PTAB panels have relied on that expiration to reject infringement theories (see below).

Below are the proceedings I can confirm involving the ’819 patent specifically. I have kept the case numbers literal and flagged what is uncertain.

1. District Court Litigation (D. Del.)

(a) Robocast, Inc. v. Netflix, Inc. — Case No. 1:22‑cv‑00305 (D. Del.)

• Plaintiff: Robocast, Inc.
• Defendant: Netflix, Inc.
• Jurisdiction: U.S. District Court for the District of Delaware (Judge Richard G. Andrews; later docketed under 22‑305‑JLH‑CJB).
• Filing date: March 7, 2022.
• Patents‑in‑suit: U.S. Patent Nos. 7,155,451 (’451), 8,606,819 (’819), and 8,965,932 (’932).
• Proceedings/outcome:
  • Netflix filed a motion to dismiss. On November 1, 2022, the Court granted in part / denied in part, dismissing Robocast's claims for vicarious infringement, indirect infringement, and willful infringement without prejudice to amend. (D.I. 21, C.A. No. 22‑305‑RGA.)
  • Netflix counterclaimed seeking declaratory judgment of non‑infringement, invalidity, and unenforceability of the ’819 patent (e.g., Counts IV–VI), invoking 35 U.S.C. §§ 101, 102, 103, 112 and obviousness‑type double patenting.
  • Fact discovery closed May 13, 2024; expert discovery closed August 29, 2024; claim construction hearing September 5, 2024. Robocast narrowed to ten asserted claims, including claim 1 of the ’819 patent.
  • Trial was set for March 3, 2025. Netflix moved for summary judgment and to exclude damages opinions on § 101, non‑infringement, and unenforceability due to inequitable conduct (the "Torres Declaration" issue).
  • Current status: Robocast appealed to the Federal Circuit. (See §3 below.) The precise trial/judgment outcome is not fully confirmed in the sources retrieved; I do not have high‑confidence detail on the exact final district‑court disposition, so I flag that as uncertain.

(b) Robocast, Inc. v. YouTube, LLC and Google LLC — Case No. 1:22‑cv‑00304 (D. Del.)

• Plaintiff: Robocast, Inc.
• Defendants: YouTube, LLC and Google LLC
• Jurisdiction: U.S. District Court for the District of Delaware (Judge Richard G. Andrews; later docketed 22‑304‑RGA‑JLH before Judge Jennifer L. Hall).
• Filing date: March 7, 2022.
• Patents‑in‑suit: U.S. Patent Nos. 7,155,451, 8,606,819, and 8,965,932.
• Proceedings/outcome:
  • On November 14, 2022, the Court (per D. Del. opinion) granted Defendants' motion to dismiss Robocast's willful and indirect infringement claims as to the ’819 and ’932 patents, because those patents expired September 2, 2017 and Robocast failed to plausibly allege pre‑expiration knowledge. (Case 1:22‑cv‑00304‑RGA, Doc. 28.)
  • Defendants also moved (renewed) to dismiss on obviousness‑type double patenting (ODP), relying on In re Cellect, 81 F.4th 1216 (Fed. Cir. 2023). Robocast opposed. Docket activity continued into 2024 (e.g., Doc. 127, 128, January 2024).
  • Current status: I do not have a confirmed final disposition in the materials retrieved; treat the ultimate outcome as uncertain.

2. PTAB (Inter Partes Review) Proceedings

(a) Netflix, Inc. v. Robocast, Inc. — IPR2023‑00182

• Petitioner: Netflix, Inc.; Patent Owner: Robocast, Inc.
• Filed: November 18, 2022.
• Patent challenged: U.S. Patent No. 8,606,819 (Respondent Application No. 13/449,570; Tech Center 2100).
• Grounds asserted (per Netflix's DJ counterclaims): Obviousness over (i) Escobar and (ii) Escobar + Rege; and over (iii) U.S. Pat. No. 5,959,623 ("van Hoff") and (iv) van Hoff + U.S. Pat. No. 5,913,040 ("Rakavy").
• Outcome: Institution Denied — Institution Decision Date June 9, 2023.
• Counsel of record: Petitioner – Batts, Harper, et al.; Patent Owner – Ryan, Andrew.
• Source: PTAB/Unified Patents data (IPR2023‑00182).

(b) Google LLC v. Robocast, Inc. (with YouTube) — IPR2023‑00594

• Petitioner: Google LLC (and YouTube).
• Patent Owner: Robocast, Inc.
• Patent challenged: U.S. Patent No. 8,606,819.
• Filed: February 21, 2023 (PTAB).
• Outcome: Not Instituted – Merits.
• Panel included Michael Cygan, Michelle Wormmeester, Patrick Boucher (per docket summaries).
• Sources: Unified Patents PTAB data; Docket Alarm.

(Note: Related Robocast IPRs exist for sibling patents — e.g., Unified Patents, LLC v. Robocast, Inc., IPR2022‑01125 (U.S. Pat. No. 8,965,932, the ’932 patent), and Netflix IPR2023‑00081 — but those target patents other than the ’819, so I do not count them as ’819 proceedings.)

3. Court of Appeals for the Federal Circuit

Robocast, Inc. v. Netflix, Inc. — Case No. 25‑1651 (Fed. Cir.)

• Appellant: Robocast, Inc.; Appellee: Netflix, Inc.
• Nature of suit: Patent Infringement (Fed. Qst.).
• Filed: April 17, 2025 (appeal received April 14, 2025).
• Origin: Appeal from the D. Del. Netflix action (C.A. No. 22‑305).
• Status: Appeal docketed; entry of appearance, certificate of interest, and docketing statement due May 1, 2025; appellant's brief due June 16, 2025. Counsel noted: Stephen Brauerman, Esq.
• This is the entry corresponding to the "U.S. case filed in Court of Appeals for the Federal Circuit … case 25‑1651" listed on the patent's Google Patents page.

4. Related (but NOT ’819‑asserting) Prior Litigation — for context

These older suits are frequently cited in the ’819 litigation because they concern the parent ’451 patent and the underlying inequitable‑conduct allegations, but they did not assert the ’819 patent (which did not issue until December 2013):

• Robocast, Inc. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), No. 1:10‑cv‑01055‑RGA (D. Del.) — asserted the ’451 patent (and, in later iterations, others), alleging infringement by Bing, Windows, msn.com, Xbox functionality. Resulted in a license; Judge Andrews decided claim construction, summary judgment, and inequitable‑conduct issues.
• Robocast, Inc. v. Apple Inc., No. 1:11‑cv‑00235 (D. Del.) — asserted the ’451 patent claim 37 against Apple iTunes/Apple TV/Safari functionalities (Robocast, Inc. v. Apple Inc., 39 F. Supp. 3d 552 (D. Del. 2014)); resulted in a license.
• Netflix, in the 2022 D. Del. case, relied on these to argue Netflix had notice of the ’451 patent (through Netflix CEO Reed Hastings's Microsoft board service and Brad Smith's role as Microsoft GC).

Because the ’819 patent issued in 2013 — after the Microsoft (2010) and Apple (2011) complaints — those suits could not and did not assert the ’819.

Summary Table

Caveats on Confidence

• The existence, parties, case numbers, filing dates, and PTAB institution outcomes above are grounded in the sources retrieved (Unified Patents portal data, PTAB APIs, CourtListener/RECAP, Docket Alarm, Justia, and the patent's own Google Patents page).
• I could not confirm with high confidence the precise final district‑court judgments in the two D. Del. cases (e.g., the exact jury/bench ruling after the March 2025 trial in Robocast v. Netflix). The filing of Fed. Cir. No. 25‑1651 indicates a final judgment was entered and is now on appeal, but I am not asserting the specific outcome.
• Do not infer that any earlier Robocast suit asserted the ’819 patent — the Microsoft and Apple actions predate its issuance and targeted the parent ’451 patent.

If you need the exact judgment text or the PTAB institution decisions, I'd recommend pulling the primary documents from PACER (D. Del. 1:22‑cv‑00304 and 1:22‑cv‑00305) and the PTAB Patent Trial & Appeal Board portal for IPR2023‑00182 and IPR2023‑00594.

I'll research this patent's PTAB history. Note that the structured block reports no ODP-indexed AIA proceedings, but the patent's own Google Patents record lists two PTAB matters — let me verify via search.

Two PTAB matters on 8606819 are surfacing (IPR2023-00182 / Netflix; IPR2023-00594 / Google & YouTube), both denied institution. Let me confirm the details, grounds, and any appeals.

Both 8606819 matters were denied institution. Let me pin down the decisions' reasoning, the Google petition's claims/grounds, and the Federal Circuit activity (25-1651).

PTAB analysis — US 8,606,819 ("Automated content scheduler and displayer," Robocast, Inc.)

Data note (flag): The structured "PTAB proceedings on file" block reports that the ODP API returns no AIA trial proceedings for this patent. That is incomplete. The patent's own Google Patents litigation record (authoritative source supplied for this patent) and multiple public dockets show two IPR petitions on 8606819 itself, both filed 2022–2023 and both denied institution, plus a five-petition Google/YouTube campaign and a Netflix companion petition on sibling patents in the same '451 family. I treat the two 8606819 IPRs as the canonical set and flag them for you rather than deferring to the empty ODP feed.

Proceedings overview

Total on 8606819: two IPR proceedings — 0 active, 0 claims invalidated, 1 claim set sustained (all of them, untested on the merits), 0 settled, 2 institution denied; the bottom line is that the PTAB has never reached the merits of this patent, no claim was canceled, and no § 315(e) estoppel attached to any petitioner — but a Delaware court has since held the asserted claim (claim 1) invalid under § 101, a judgment now on appeal at the Federal Circuit (No. 25-1651), so the real invalidity exposure is judicial, not administrative.

Verbatim status field from the structured record: both proceedings are listed as "Not Instituted - Merits." Gloss: the Board declined to institute trial; no Final Written Decision issued.

IPR2023-00594 — Google LLC & YouTube, LLC v. Robocast, Inc.

• Type: Inter Partes Review
• Filed: 2023-02-21
• Status: "Not Instituted - Merits" (institution denied). Board paper captioned Denying Institution of Inter Partes Review, 35 U.S.C. § 314(a), 2023-09-18. Petitioner then filed a Request for Refund of Post-Institution Fees (2023-11-20), which the Board approved (2023-11-22) — confirming no trial ever began.
• Judge panel: Michael T. Cygan, Michelle N. Wormmeester, Patrick M. Boucher
• Petition grounds: Six grounds built on Shimizu (U.S. Pat. No. 5,634,062) in view of Benedict and Fox; the petition also relied on Sagman (Running Microsoft PowerPoint 4 for Windows, 1994), Filepp (U.S. Pat. No. 5,347,632), Guinan (1992), Robertson (U.S. Pat. No. 6,486,895), and Miller (Using CompuServe). Statutory basis § 103. Claims challenged included at least claims 1, 16, 23, and 26 — those are the claims Patent Owner's Preliminary Response mapped element-by-element (limitations 1[a], 16[c], 23[a], 26[a]; "interactively variable duration information" at 1[d], 23[d], 26[d]). I do not have the petition's complete claim list from a primary source and will not state one.
• Institution decision: Denied 2023-09-18 (Paper 10). The record shows Patent Owner's POPR (2023-06-22) argued (i) the '819 patent is expired (anticipated expiration 2017-09-02) so the Board lacked jurisdiction, (ii) discretionary denial under § 314(a)/Fintiv, and (iii) failure on the merits. Robocast's public statement characterizes the September 18, 2023 denials as merits-based — that the Board found Google/YouTube "not reasonably likely to prevail in showing that any of the challenged claims is anticipated by or would have been obvious" over the art raised. I do not have the four corners of Paper 10 and do not quote the panel's reasoning.
• Final Written Decision: None. No trial, no claim-level verdict.
• Settlement / termination: No settlement; terminated by institution denial.
• Appeal: Not appealable — § 314(d) makes an institution denial final and non-appealable (Cuozzo; Thryv).
• Defensive value: Google/YouTube's §§ 102/103 grounds against 8606819 were never adjudicated, so no estoppel bars them from being re-asserted in district court. For a defendant, this cuts both ways: the art is still usable (no estoppel), but the PTAB has twice signaled it did not find the art compelling.

IPR2023-00182 — Netflix, Inc. v. Robocast, Inc.

• Type: Inter Partes Review
• Filed: 2022-11-18
• Status: "Not Instituted - Merits" (institution denied), decision 2023-06-09; case terminated same day.
• Judge panel: Patrick M. Boucher (author of the decision), Michelle N. Wormmeester, Michael T. Cygan
• Petition grounds: Four grounds — Escobar alone against claims 1 and 26; Escobar in combination with Rege; van Hoff (U.S. Pat. No. 5,959,623) against claims 1–2, 7–9, 11–12, 15, 26–28; and van Hoff in combination with Rakavy (U.S. Pat. No. 5,913,040). Statutory basis § 103 (obviousness).
• Claims challenged: 1, 2, 7, 8, 9, 11, 12, 15, 26, 27, 28 (eleven of the patent's thirty claims).
• Institution decision: Denied 2023-06-09. Patent Owner's POPR and Sur-Reply pressed three lines: (1) the '819 patent's expiration defeats jurisdiction; (2) discretionary denial under § 314(a) — the Fintiv factors — because the District of Delaware had already denied Netflix's motion to stay (oral order 2023-01-26) and trial-stage investment was mounting; and (3) the merits (Escobar and van Hoff fail the "creating a show structure of nodes" and "interactively variable duration information" limitations). Netflix countered with a Sotera-style stipulation, which Robocast argued was insufficient because co-defendants Google/YouTube were not bound. I do not have the text of the June 9, 2023 decision and will not characterize which line the panel adopted.
• Final Written Decision: None.
• Settlement / termination: No settlement; terminated by institution denial.
• Appeal: Not appealable (§ 314(d)).
• Defensive value: Netflix's Escobar and van Hoff/Rakavy grounds survive unadjudicated — no estoppel. But note that the same Escobar/van Hoff theories were also pleaded as declaratory-judgment invalidity counts in the parallel Delaware case, where the court has now ruled against Robocast on § 101.

Related family activity (not on 8606819, but material to the pattern)

• IPR2022-01125 — Unified Patents, LLC v. Robocast, Inc. (U.S. Pat. No. 8,965,932): institution denied. Robocast's PR framed this as Unified mischaracterizing Robocast as an NPE.
• IPR2023-00081 — Netflix, Inc. v. Robocast, Inc. (sibling patent in the '451 family): institution denied; Netflix's request for rehearing denied 2023-09-18.
• IPR2023-00590, -00591, -00592, -00593 — Google LLC & YouTube, LLC v. Robocast, Inc.: all denied institution 2023-09-18 (the five Google denials, which include -00594 on this patent).
• Robocast's own count: 8-of-8 institution denials across the family (Google/YouTube ×5, Netflix ×2, Unified ×1).

Strategic summary

Claim status on 8606819. No claim has been canceled, sustained on the merits, or otherwise adjudicated by the PTAB: claims 1–30 are all UNTESTED at the Board, because both IPRs (netting claims 1, 2, 7–9, 11–12, 15, 26–28 in Netflix; and at least claims 1, 16, 23, 26 in Google) were denied institution and no Final Written Decision ever issued. The claim-level picture that matters for a defendant is therefore judicial, not administrative: in Robocast, Inc. v. Netflix, Inc., No. 1:22-cv-00305 (D. Del.), Judge Jennifer L. Hall granted summary judgment on 2025-02-21 that the asserted claims of the '451, '819, and '932 patents are invalid under § 101 (abstract idea), expressly holding that "none of the asserted claims contain any specificity as to how to accomplish" the recited steps. Robocast had narrowed to claim 1 of the '819 patent (plus claims of the sibling patents) by trial. The parallel Robocast v. YouTube/Google action, No. 1:22-cv-00304 (D. Del.), was stayed in light of that ruling.

Estoppel landscape. Because no IPR was instituted, § 315(e)(2) estoppel never attached to Netflix, Google, YouTube, or Unified Patents (and, necessarily, to their privies). Every prior-art ground these petitioners raised — Escobar, Rege, van Hoff, Rakavy (Netflix); Shimizu, Benedict, Fox, Sagman, Filepp, Guinan, Robertson, Miller (Google) — remains fully available in district court and to any new defendant. A current letter recipient who was not a prior petitioner is under no statutory estoppel at all, and the IPR record (POPRs, expert declarations) is public and reusable.

Pattern signals. The pattern is a multi-front defense campaign by an interlocking coalition: Unified Patents (the defensive aggregator) hit the '932 patent with IPR2022-01125; Netflix filed IPR2023-00081 and -00182; Google and YouTube filed a five-petition blitz (-00590 through -00594) on 2023-02-21, all decided the same day, 2023-09-18. Same three APJs (Cygan / Wormmeester / Boucher) sat on both 8606819 panels. Robocast — represented by McKool Smith and Cantor Colburn — has not needed to appeal anything to the Federal Circuit on the PTAB side (institution denials are non-appealable), but Robocast itself is the appellant in the district-court appeal, and the patent owner has been aggressive in the district court (initial infringement contentions 2023-05-25; resisting stays).

Recommended next steps

1. Do not treat the empty ODP feed as "no PTAB activity." Two IPRs on this exact patent exist (IPR2023-00182, IPR2023-00594), both denied institution. Pull the decisions directly from PTAB E2E / USPTO PATS:
   • IPR2023-00594 docket: https://www.docketalarm.com/cases/PTAB/IPR2023-00594/Google_LLC_v._Robocast_Inc/ (Denial of Institution, Paper 10, 2023-09-18)
   • IPR2023-00182 docket: https://www.docketalarm.com/cases/PTAB/IPR2023-00182/Netflix_Inc._v._Robocast_Inc/ (terminated 2023-06-09)
   • Verify via USPTO PTAB E2E: https://ptacts.uspto.gov
2. Lead your defense with the § 101 ruling, not with the IPR art. No PTAB FWD exists to quote; the dispositive public document is Judge Hall's 2025-02-21 summary-judgment order in No. 1:22-cv-00305 holding all asserted claims (including '819 claim 1) invalid as abstract. Confirm the current posture on PACER before relying on it: it is on appeal.
3. Track the appeal — Robocast, Inc. v. Netflix, Inc., No. 25-1651 (Fed. Cir., filed 2025-04-17). Docket: https://dockets.justia.com/docket/circuit-courts/cafc/25-1651. This is Robocast's appeal of the invalidity judgment — not a PTAB appeal. Watch the disposition; a Federal Circuit affirmance kills claim 1 of the '819 outright, whereas a vacatur/remand revives the § 101 fight and makes the untested IPR art more valuable to you.
4. Preserve the prior-art grounds. Because both IPRs were denied institution, there is no § 315(e) estoppel, and every ground in IPR2023-00182 and IPR2023-00594 is still fair game for a district-court § 102/§ 103 defense or a fresh IPR petition — subject to the § 315(b) one-year bar if you have already been served, and to your own § 315(a)/(b) posture. A new petitioner is not bound by Netflix's or Google's prior-art choices.
5. If you are weighing your own IPR: note the patent expired 2017-09-02, and Patent Owner argued (unsuccessfully on the merits of the argument, but effectively in practice) that expiration undercuts PTAB jurisdiction. The Board has repeatedly declined to institute on this family, so a new petition must clear a high § 314(a) bar; the Fintiv record here (a live, trial-ready Delaware case with a stay already denied) is adverse to institution.

Confidence caveats: Proceeding numbers, parties, filing/decision dates, panels, and status are grounded in the sources cited above. The exact basis of each denial (merits vs. discretionary) and the complete claim sets in the Google petition are not fully documented in the sources I retrieved; I have flagged where I am inferring rather than quoting. Nothing here should be filed without pulling the underlying PTAB papers (Paper 10 in -00594; the June 9, 2023 decision in -00182) from PTAB E2E.

I'll research the assignment record before writing. Let me run several targeted searches.

Let me dig deeper into the assignment record and Robocast's corporate history.

Let me investigate Robocast's corporate structure and any recorded transfers.

Assignment & Ownership Analysis — US Patent 8,606,819

Sourcing limitation up front (read before using): I was unable to load USPTO Assignment Center (assignmentcenter.uspto.gov) directly with the tools available. The reel/frame numbers, execution dates, and assignment correspondent fields below are therefore not verbatim USPTO Assignment Center extracts. What I can ground is (a) the indexed Google Patents legal-events record for this patent, which reports exactly one post-filing assignment entry, and (b) the litigation/prosecution record, which establishes who the owner of record has been at every material date. Where I do not have a reel/frame, I say so rather than invent one. Verify at the Assignment Center search page: https://assignmentcenter.uspto.gov/ (search "8606819").

Inventors

Damon C. Torres — sole named inventor on US 8,606,819. Appears as "Damon C. Torres" in the assignment record and "Damon Torres" as first named inventor on the parent app 11/316,209 (attorney docket 735-002con).

• Employer at time of filing: Robocast, Inc. (New York, NY). Torres founded Robocast and is described in Robocast's own litigation filings as the company's founder; he has been CEO/Chairman continuously, including as of 2022–2023 press materials ("Inventor Of Autoplay For Streaming, Robocast Adds To Leadership Team," Jan. 2022). At the time of the earliest priority filing (provisional 60/025,360, Sept. 3, 1996) Torres was the principal of the Robocast venture — the specification and the litigation record describe Robocast's 1990s-era development of RoboCast/RoboSurf under him.
• Inventor-departure pattern: Not present — and inverted. The classic fire-sale precursor (all inventors leaving the assignee within 12 months) does not apply: the sole inventor is the assignee's founder and remains its CEO. Continuity of inventor-control is the notable feature here, not departure.

Original assignee

Robocast, Inc., a Delaware corporation with its place of business in New York, NY (per Robocast's own complaint, quoted in the RPX litigation document at insight.rpxcorp.com/litigation_documents/9424208).

• Did it ship a product embodying the claims? Yes, historically. Robocast pleaded that it "developed and deployed for numerous customers its unique automated browsing tools" and named specific products: Robocaster, RoboGuide, RoboMobile, RoboPublisher, RoboSearch, RoboStats, and RoboSurf. Named customers/partners by 2001 included Hachette Filipacchi (Premiere, Cycleworld, Car and Driver), ZDNet's News.com, and InfoSpace (RoboSearch via Metacrawler). Robocast was also part of the Microsoft TV Developer Program. This is a genuine operating-company origin, not a paper shell at formation.
• Primary line of business (current): Licensing/enforcement of the patent family. Robocast's own description is unambiguous: "Robocast, Inc. is a company that licenses its methods and technologies to major companies" (MarketScreener company profile), and "Robocast provides licensing, content and education" (Robocast press release). Its portfolio "has been licensed to leading media companies such as music video distributor Vevo." There is no evidence of a currently shipping product embodying the claims.
• Status: Operating as a going concern but no longer as a product company. Delaware corporation, still active; settled with Microsoft and Apple (Robocast v. Microsoft, No. 1:10-cv-01055-RGA; Robocast v. Apple, No. 1:11-cv-00235-RGA), signed a non-litigated license with Vevo (2022), and completed venture raises (Brown Venture Group; Warecorp). No bankruptcy proceeding found for Robocast.
• Parent/holding structure: Robocast's litigation Schedule A defines "Robocast" to include "its parent companies (including Interactive Media Universe LLC ('IMU'))" (D. Del. 1:22-cv-00305, D.I. 189-1). IMU appears in the earlier Microsoft litigation as an operational/document-management entity associated with Torres. No recorded assignment of this patent to IMU was found — ownership of record stayed with Robocast, Inc.

Assignment timeline

Indexed record for US 8,606,819 contains exactly one post-filing assignment entry:

• Executed date: not retrieved / recorded 2012-12-13 — Reel NNNNNN/NNNN (not retrieved — Assignment Center not loaded)
  • Conveyance: Assignment of assignors' interest ("ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: TORRES, DAMON C.
  • Assignee: ROBOCAST, INC.
  • Correspondent: not retrieved. Note for flagging: the prosecution correspondent of record on this application is Sofer & Haroun LLP, 317 Madison Avenue, Suite 910, New York, NY 10017, authorized signature /JOSEPH SOFER/ on the Nov. 8, 2013 issue-fee transmittal (attorney docket 735-002CON3(1)). The same firm prosecuted the parent 11/316,209 (docket 735-002CON, Examiner Kimberly Lovel Wilson). Whether Sofer & Haroun was also the recording correspondent on the 2012-12-13 assignment is unconfirmed — do not treat this as verified.
  • Context: Inventor-to-original-assignee perfection of title for the 2012 continuation application (13/449,570) — a housekeeping confirmation of what was already true for the family, not an acquisition, fire-sale, or transfer to an asserter.

No subsequent assignment recorded. Google Patents' legal-events list for US 8,606,819 shows no event after the 2012-12-13 entry. This is corroborated by the 2022 complaints, which plead that "Robocast is the owner of all right, title, and interest" in the family. The patent has never moved to a third-party LLC.

Not retrieved but expected to exist: separate assignment records for the parent/priority applications (08/922,063; 09/144,906 → US 7,155,451; 11/316,209). I did not obtain their reels/frames; they should be checked at the Assignment Center as the same assignee chain.

Timeline diagram

timeline
    title Ownership and assertion of US 8606819
    1996 : Torres files provisional application
    1997 : CIP application filed
    1998 : Parent application filed
    2005 : Continuation application filed
    2012 : Continuation filed by Robocast
         : Torres records assignment to Robocast
    2013 : Patent issued to Robocast Inc
    2017 : Anticipated expiration
    2022 : Suits filed against Netflix and Google
    2023 : PTAB denies institution of IPRs
    2025 : Delaware finds claims invalid

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. There is no transfer to a licensing-only LLC anywhere in this record. Ownership of record has been Robocast, Inc. continuously since the 2012-12-13 assignment, and Robocast was the operating developer of RoboSurf/RoboCaster before it became an enforcement vehicle. Note carefully: the absence of the transfer does not mean the entity is operating today — Robocast is now licensing-only (see #2), but the statutory signal as defined (movement into a shell) is absent.

2. Known asserter in the chain — Present (qualified). Robocast, Inc. does not match any name on the enumerated lists (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). However, Robocast does appear as a target in the defensive-aggregator ecosystem: Unified Patents, LLC v. Robocast, Inc., IPR2022-01125 (filed June 30, 2022, challenging US 8,965,932; Exhibit 1008 is the "Prosecution History of U.S. Patent 8,606,819"). Another party (Netflix), in a court filing, states flatly that "Robocast … is a non-practicing entity whose asserted patents expired years ago" (Netflix stay motion, D. Del. 1:22-cv-00305, quoted at ptacts.uspto.gov petition 1550476). Two independent sources — a defensive aggregator's challenge and an adversary's unrebutted characterization — support monetization-entity status.

3. Repeat correspondent across the chain — Unclear. I could confirm a recurring prosecution correspondent, not an assignment correspondent: Sofer & Haroun LLP (Joseph Sofer) appears as attorney of record across the Robocast continuation family (docket series 735-002CON → 735-002CON3), including on this application. A single law firm doing a serial-continuation family for one client is ordinary, not an NPE tell, and one appearance is not a signal. I did not retrieve the assignment correspondent field for the 2012-12-13 recording, so I cannot test the "same lawyer on every link" hypothesis. Not scored as present.

4. Cascading transfers — Not present. One recorded assignment, no chained LLCs, no transfers through a series of entities, over 13 years of ownership.

5. Pre-litigation transfer — Not present. The only assignment is dated 2012-12-13; the first suit naming this patent is Robocast, Inc. v. YouTube, LLC and Google LLC, No. 1:22-cv-00304, filed March 7, 2022 — roughly nine years after the assignment. The chain was not arranged within six months of suit. (The inverse observation holds: because the patent was already owned by Robocast since 2012, no venue/standing-motivated assignment was needed in 2022.)

6. Bankruptcy fire-sale — Not present. No Chapter 7/11 proceeding found for Robocast; it is actively raising capital and licensing rather than liquidating.

7. Privateering — Not present. No operating company transferred this patent to an NPE to assert against its competitors. The asserting entity is the original assignee itself.

8. Defensive aggregator — Not present (inverse noted). The chain does not terminate at RPX/AST/LOT/Unified/OIN. To the contrary, Unified Patents is adverse to Robocast (IPR2022-01125), and the patent's asserted claims were held invalid under §101 by the District of Delaware (Feb. 2025), with appeal pending at the Federal Circuit (No. 25-1651, docketed April 2025). The patent has effectively been neutralized by adjudication, not by acquisition.

Verdict

NPE — moderate confidence.

Justification: the record shows no shell-entity transfer, no cascading assignments, no pre-litigation assignment, and no bankruptcy sale — so the classic chain-manipulation signals are absent, and this is not a high-confidence NPE call (the single recorded assignment is a 2012-12-13 inventor-to-company perfection of title, reel/frame not retrieved). What does support the call is (i) two independent sources establishing that Robocast, Inc. — the continuous owner of record — is today a licensing/enforcement entity that no longer ships products embodying the claims, including Netflix's unrebutted statement that "Robocast … is a non-practicing entity" (D. Del. 1:22-cv-00305) and Robocast's own marketing ("provides licensing, content and education"), and (ii) the defensive aggregator Unified Patents challenging the family (IPR2022-01125). Because the entity asserted the '819 patent against Microsoft, Apple, YouTube/Google, and Netflix while selling no current product, the "Operating-company assertion" verdict is not available; but the absence of the transfer-chain indicia keeps this at moderate, not high, confidence.

Verify at: https://assignmentcenter.uspto.gov/ → search "8606819"; index mirror at https://assignment.uspto.gov/patent/index.html. Also pull the reel/frame PDFs to fill the two blanks above: the execution date and the assignment correspondent on the 2012-12-13 Torres → Robocast, Inc. entry.

I'll research the prior-art citations for US 8,606,819 specifically, pulling from the authoritative patent text and USPTO/source records.

Let me pull the front-page references and the IPR/PTAB art cited against 8,606,819.

Let me get the complete front-page reference list and the non-patent citations for 8,606,819.

I've hit a tool-usage limit, so I'll synthesize from the searches already run. Here is the prior-art analysis for US 8,606,819 B2 specifically.

Prior Art Analysis — US 8,606,819 B2

Patent analyzed: US 8,606,819 B2, "Automated content scheduler and displayer," inventor Damon C. Torres, assignee Robocast, Inc. Application 13/449,570 filed Apr. 18, 2012; issued Dec. 10, 2013; earliest priority claimed Sept. 3, 1996.

Framing note (important before any §102 mapping)

1. The references "cited" on the face of the '819 patent are largely IDS/"considered" references, not §102 rejections. They were listed by the applicant/examiner and, for the most part, not applied against the claims. Two of them (Reilly and Brown) were the basis of a §103 rejection of claim 16 during prosecution (see §C.3).
2. The PTAB challenges were §103 obviousness grounds, not §102 anticipation grounds. Neither IPR (2023-00182, 2023-00594) was instituted, so no claim was cancelled. Where a petition asserted a single reference (e.g., VanHoff alone), that is a §103 ground that approaches, but is not, a §102 anticipation theory.
3. Priority-date caveat that controls the entire §102 analysis. The '819 is a continuation of 11/316,209 (2005) → continuation of 09/144,906 (1998, now US 7,155,451) → CIP of 08/922,063 (Sept. 2, 1997, abandoned) → provisional 60/025,360 (Sept. 3, 1996). Because the chain runs through a CIP, claims resting on new matter may be entitled only to the 1998, 2005, or even the 2012 filing date. Most of the references below issued/published after Sept. 3, 1996 and therefore are not §102(b) art against the 1996 date — they qualify only if a given claim cannot claim 1996 priority (or via pre-AIA §102(a)/(e)). I have flagged this per reference.
4. Pre-AIA §102 applies (application filed Apr. 18, 2012, before Mar. 16, 2013). So the operative categories are pre-AIA §102(a), (b), (e), and (g).

A. References cited on the face of US 8,606,819 (US Patent References)

Retrieved from the patent's own citation list (FreePatentsOnline record for 8606819; consistent with Google Patents). "Pub. date" = issue date shown in that record. None of these was confirmed as a §102 anticipatory rejection; §102 relevance is my assessment.

Foreign patent documents / additional categories: The FreePatentsOnline record also contained a "Foreign Patent Documents" section and an "Other References" (NPL) section. From the retrieved snippet, the NPL items included:

• "Method and apparatus for retrieving data from a network using location identifiers," dated Jun. 28, 1999 (cf. A15).
• "Robocast launches Robocaster and Roboplayer web page players," dated Apr. 5, 1999 (a Robocast press item).

I was not able to retrieve the full "Foreign Patent Documents" list for the '819 patent; I am flagging this rather than guessing at WO/EP numbers. My on-face list above may be partial (the retrieved list began mid-order at US 6,769,009 and contained a truncated entry, A25).

B. References relied on in the PTAB validity challenges against the '819 patent

These are the references that actually formed grounds against 8,606,819. Both petitions were institution-denied, so none of these was adjudicated invalidating.

B.1 — IPR2023-00182, Netflix, Inc. v. Robocast, Inc. (filed Nov. 18, 2022; institution denied June 9, 2023)

Challenged claims: 1–2, 7–9, 11–12, 15, and 26–28. Grounds (per Netflix's stipulation table and petition):

• (i) The petition text (PTACTS petition documents) shows the "Escobar-based" grounds and a reference tied to "Kirsch ("Escobar")" in the same table cell. My snippet was ambiguous as to which bibliographic record is "Escobar." I also confirmed a US 5,913,040 Rakavy exhibit (Ex. 1007) and US 5,959,623 VanHoff (Ex. 1007/1008 area) in the same petition. I could not confirm the exact patent number of "Escobar" from the retrieved sources — treat its citation as unverified and check PTACTS directly.
• The petition states Escobar is significant because in the earlier Robocast v. Microsoft litigation "the parties agree[d] that Escobar discloses all limitations of claim 10 [of the '451 patent] except for nodes," with the only dispute being "whether a 'pointer' is an 'address[].'" That makes Escobar the most anticipation-adjacent reference of record — but it was pleaded as §103, not §102.
• Netflix's stated claim-limitations delta for the '819 over the '451: "(a) some resources to be 'network accessible,' (b) accessing 'at least some' network accessible resources during the presentation of other content, and (c) advertising content."

Verified dates I am confident about: US 5,740,549 (Reilly) → Apr. 14, 1998; US 6,026,368 (Brown) → Feb. 15, 2000. For the IPR references, I have the numbers from the record but not independently verified issue/filing dates; treat the following as recalled/unverified: US 5,959,623 (Van Hoff) ≈ Sept. 28, 1999; US 5,913,040 (Rakavy) ≈ Jun. 15, 1999; US 5,612,897 (Rege) ≈ Mar. 18, 1997.

B.2 — IPR2023-00594, Google LLC et al. v. Robocast, Inc. (filed Feb. 21, 2023; institution denied Sept. 18, 2023)

Google/YouTube challenged a broader claim set than Netflix, including claim 16 (the "online search" claim) and dependent claim 29. Petitioner Exhibit List (per Docket Alarm / IPR record):

Google's §325(d) section confirms only Guinan (Ex. 1008) and Reilly (Ex. 1015) were previously "considered" by the Examiner in the '819 prosecution; the rest were stated to be new.

C. Which references potentially anticipate which claims under §102

Bottom line up front: No reference is confirmed as a §102 anticipation rejection or holding. The strongest single-reference candidates for the independent claims are Escobar (Netflix Ground 1, claims 1 and 26 — closest of all, given the earlier Microsoft litigation finding), VanHoff (Netflix Ground 3, claims 1–2, 7–9, 11–12, 15, 26–28 — single-reference §103), and Shimizu (Google's lead reference). Everything else is a §103 combination reference or IDS background art.

C.1 Claim 1 (independent — "show structure + auto-access/present + ads")

• Escobar (Netflix Ground 1, §103 single reference) → claim 1 (and claim 26). Highest anticipation potential, because the prior Microsoft litigation found Escobar disclosed all limitations of the analogous '451 claim 10 except the "node" term.
• VanHoff, US 5,959,623 (Netflix Ground 3, §103 single reference) → claim 1. Approaching anticipation; a single reference asserted to teach every element.
• VanHoff + Rakavy, US 5,913,040 (Ground 4) → claim 1 (§103 combination).
• Shimizu, US 5,634,062 (Google) → independent claim(s); exact per-claim mapping not confirmed from my sources.

C.2 Claim 26 (independent) and its dependents 27–28

• Escobar → claim 26 (Ground 1).
• VanHoff alone → claim 26 and 27–28 (Ground 3).
• VanHoff + Rakavy → claim 26–28 (Ground 4).
• Rakavy cited by Google only against dependent claim 29.

C.3 Claim 16 (independent — "search results become an auto-playing show")

• Reilly (US 5,740,549) + Brown (US 6,026,368) — this is the only actual Examiner-applied combination in the '819 file history: a §103 rejection of claim 16 relying on Brown for the search feature. It was maintained in a Final Office Action, then overcome by Patent Owner amending claim 16 to add the "during said presentation … at least some of said other network accessible resources are being accessed" limitation. (Both references were cited on the face of the patent — A22, A13.)
• Guinan (Ex. 1008) (Google Ground 2) → the "online search" of claim 16, i.e., a §103 theory.

C.4 Claims 2, 7–9, 11–12, 15 (dependents)

• VanHoff alone (Ground 3) and VanHoff + Rakavy (Ground 4) → these dependents, per Netflix's challenge.
• Escobar + Rege (US 5,612,897) (Ground 2) and Escobar alone (Ground 1) were pleaded only against claims 1 and 26, not these dependents.

C.5 Claim 23 (independent — "persistent ad window")

• No IPR ground is confirmed against claim 23 in either petition's challenged set (Netflix: 1–2, 7–9, 11–12, 15, 26–28; Google: broader, but I could not confirm 23 specifically).
• The on-face reference Freiberger et al., US 6,034,652 ("peripheral attention" display) and Abecassis, US 6,289,165 (interleaved segments) are the IDS references conceptually closest to the persistent-window/ad-content limitation, but both post-date 1996.

C.6 Anticipation vs. the statutory form actually used

For completeness: every ground the parties pleaded against the '819 was §103, and both institutions were denied. If you are looking strictly for a pre-AIA §102 theory:

• The only realistic single-reference §102 candidates are Escobar (claims 1, 26) and VanHoff (claims 1–2, 7–9, 11–12, 15, 26–28), and only if the reference both discloses every element and has a §102(a)/(b)/(e) date earlier than the applicable effective filing date of the challenged claim.
• Because the '819's claim to 1996 is a CIP/continuation chain, the effective date question is dispositive and unresolved on the record I retrieved.

D. Explicit uncertainties and gaps

1. The "Escobar" citation is not fully verified. The retrieved petition snippet associated "Escobar" with a "Kirsch" reference in the same row. I could not confirm the exact U.S. patent number. Verify via PTACTS (Netflix IPR2023-00182 exhibits). Do not cite a specific number for Escobar without that check.
2. Issue/filing dates for the IPR references are recalled, not verified (VanHoff 5,959,623; Rakavy 5,913,040; Rege 5,612,897; Shimizu 5,634,062; Filepp 5,347,632; Robertson 6,486,895; Schloss 5,706,507; Wolfe 5,715,445; Hollingsworth 5,217,119; Steele 5,884,056). Dates for the on-face references (Section A) are taken from the patent's own citation record and are reliable.
3. The on-face reference list may be incomplete. My retrieved list started mid-order and included a truncated entry (US 5,625,781). The "Foreign Patent Documents" section and the full "Other References" (NPL) section of the '819 front page were not retrieved. Additional WO/EP documents and NPL are likely present and should be pulled from the GO/PDF front page.
4. Google's per-claim ground mapping (IPR2023-00594) was not fully retrieved — I have the exhibit list and the fact that claim 16 (search) and claim 29 (Rakavy) were targeted, but not the full Ground 1/2/… → claim mapping.
5. §102 analysis is conditional on the priority/CIP question, which I did not resolve. Given the expired status (anticipated expiration reported as 2017-09-02) and the Feb.-2025 D. Del. §101 invalidation of the asserted claims (per the previously generated section), the practical stakes of the §102 analysis are limited — but flag any contradiction if later sources show the §101 judgment was reversed on appeal (CAFC No. 25-1651) rather than affirmed.

Sources: Google Patents US8606819B2 (patents.google.com/patent/US8606819/en); FreePatentsOnline record 8606819 (freepatentsonline.com/8606819.html); PTACTS petition documents for IPR2023-00182 (ptacts.uspto.gov petitions 1550580, 1550476) and IPR2023-00594 (ptacts.uspto.gov petition 1553616); IPVerse case pages for IPR2023-00182 and IPR2023-00594; Docket Alarm IPR2023-00594 exhibit list; D. Del. C.A. No. 22-304 (Robocast v. YouTube/Google) briefing.

I'll ground this obviousness analysis in the authoritative materials already assembled and verify the key prior-art references before analyzing.

I have strong primary-source grounding now. Let me verify the key references' disclosures and the patent's own cited art.

Obviousness Analysis — U.S. Patent No. 8,606,819

Method: 35 U.S.C. § 103 / Graham v. John Deere + KSR Int'l v. Teleflex, 550 U.S. 398 (2007).
Assumed priority date: September 3, 1996 (provisional 60/025,360) — the date against which art must qualify. (Note: the ’819 was not filed until April 18, 2012; its entire validity case rests on the 1996 priority claim. For § 103 purposes I use the earlier date, which is the harshest test for the prior art.)

I am building on the previously generated summary/litigation sections and not repeating the bibliographic and case-history content. Two cross-reference updates from new primary-source evidence appear at the end.

1. Level of ordinary skill in the art (POSITA)

A POSITA in 1996 would have had (i) a working knowledge of HTTP/HTML/URL addressing, MIME types, and Web browsers; (ii) experience with hypermedia/“link-and-node” authoring (e.g., HyperCard, Intermedia, FRESS-style systems); and (iii) at least familiarity with the then-new “push” model (Pointcast, Netcaster, Active Desktop) and with client-side ad-delivery/“polite agent” systems. The patent’s own specification assumes this baseline (it describes HTTP, MIME, CGI, plug-ins, digital signature initiatives, Firefly.net filtering, and Cyber Patrol as known). This matters because KSR requires that POSITA background knowledge and “common sense” be considered, not just the four corners of each reference.

2. The claim elements that must be accounted for

Four independent claims (1, 16, 23, 26) and their dependents. Reduced to elements:

3. The art of record

The strongest art set is the one Netflix actually assembled in IPR2023-00182 (filed Nov. 18, 2022), plus the references cited on the face of the ’819. These are all pre-1996/1997 documents, so they qualify as prior art against the 1996 priority date:

4. Ground-by-ground § 103 analysis

Ground 1 — Escobar alone (anticipation-flavored obviousness)

Escobar teaches a machine-ordered list of pointers to multimedia objects hosted on different servers, retrieved in sequence and automatically played. Mapping:

• A (structure of nodes): Escobar’s merged decision-list entries are pointers to objects on different servers → nodes identifying resources. Netflix’s record shows the parties in the earlier Apple litigation agreed Escobar disclosed all limitations of ’451 claim 10 except “nodes,” with the only dispute being “whether a ‘pointer’ is an ‘address.’” (Apple Opp. to MSJ, C.A. 11-235.)
• B/C (auto-access and auto-present without user input): the timeline/decision-list is executed programmatically in order — no per-item user click.
• D (ads): weak on its own — Escobar does not clearly teach advertisement content as a claimed feature.

Motivation/linkage: none needed for a single-reference case; the functional equivalence of “pointer” and “address” is the crux, and KSR counsels that common sense and POSITA background knowledge (URLs were ubiquitous by 1996) supply the “address” reading.

Ground 2 — Escobar + Rege

Rege complements Escobar exactly where Escobar is thin: it teaches requesting multimedia content on networked server nodes by sending packets with addresses — i.e., it converts Escobar’s abstract pointers into network addresses/URLs.

Motivation to combine (KSR rationales 1–3):

1. Same field / same problem — both address retrieval and playback of distributed multimedia.
2. Predictable result — adding an address to a pointer is a mere substitution of one known data field for another yielding predictable results.
3. Known technique to improve similar devices — network addressing was the standard 1996 mechanism for locating remote objects.

This ground maps cleanly onto claims 1 and 26’s “network-accessible resources” and the ’16 search-result→structure concept (search results necessarily come with locators).

Ground 3 — VanHoff alone

VanHoff is the most structurally on-point art because it is literally an automatic ad player built from a list of lists:

• A: user-established list 210 of preferred advertising lists + pointers 212-1…212-n = show structure of nodes; each Ad program includes informational references 316 (URLs) = network-accessible resources.
• B: the interpreter automatically selects, loads, and runs each Ad list and each Ad in sequence until the last — auto-access without user input.
• C: content (images, audio, text) is presented in the dedicated screen portion (window 500) in sequence.
• D: the presented content is advertisements; applets define duration/sequence/appearance parameters (highly relevant to the ’26 “duration information” element).
• Persistent-window dependent (’23): VanHoff’s dedicated display window maps directly.

Motivation/linkage: single-reference; where the claim adds “without requiring user input,” VanHoff expressly executes the lists automatically once configured.

Ground 4 — VanHoff + Rakavy

Rakavy supplies the dependents and the one element VanHoff lacks (profile-driven, dynamically selected ads, plus background retrieval):

• Claim-1 dependents requiring dynamic ad content / ads based on a user profile → Rakavy Ex. 1007, 3:34-51, 5:38-53 (preferences, categories, “do not show me this again”), 9:34-54 (raw data sent back to ad server).
• Ad content as a resource accessible via the Internet → Rakavy’s Ad Server 600 model.
• Concurrency/background retrieval → Rakavy’s Polite Agent downloading during “periods of low line utilization,” stated by the Board to be Petitioner’s bridge for the “concurrently accessing” element.

Motivation to combine (the articulated rationale, which I find technically sound):

• More precise targeting — Rakavy’s profile machinery improves VanHoff’s ad selection (expressly the rationale in the petition/declaration).
• Network efficiency — Rakavy’s background download during idle link time improves VanHoff’s user experience (no wait at display time); this is the classic “known technique improves a known device in the same way” rationale.
• Both are advertising-display systems delivered over networks — the same field of endeavour, addressing the same problem (deliver ads to a user’s computer automatically).

Ground 5 — Richardson (and Reilly/Brown/Mogul) as corroborating art

• Richardson independently teaches “guided tours” of ordered Web pages with auto-advance — corroborating element A/B/C for Web-page resources (not just ads).
• Reilly ’549 / Brown ’368 corroborate automatic distribution of content with advertising to targeted viewers.
• Mogul ’802292 (predictive prefetching) corroborates the concurrency/caching aspect.

Motivation: these are cumulative/corroborating for a combination case and useful to rebut any argument that “automated sequential Web presentation + ads” was non-routine in 1996.

5. Why a POSITA would have combined — consolidated rationale

Under KSR, the following rationales support combination without any explicit teaching-away:

1. Common field and common problem. Every reference addresses delivering user-selected/automatically-sequenced content over a network to a client display; ad-supported delivery was the dominant business model (Pointcast, Rakavy/BackWeb).
2. Predictable, mechanical combination. Substituting Rege’s network address for Escobar’s pointer, or Rakavy’s profile-selected ad for VanHoff’s user-selected Ad list, is the combination of known elements according to known methods with predictable results (KSR, 550 U.S. at 416–17).
3. Market/design incentive (KSR rationale 4–5). Documented 1996 market pressure to keep the user in a passive “sit-back” experience while monetizing with ads supplies a concrete commercial motivation.
4. Obvious to try. Given that both “push” ad delivery and automated page sequencing were known, arriving at “auto-play a sequence and insert ads in a persistent window” was an obvious design space to explore, with a finite number of predictable permutations.

6. Where the § 103 case actually broke — and why I must report it

The two PTAB petitions against the ’819 were both denied institution, and the decisive limitations were precisely the ones that matter most to the ’819 over the parent ’451:

Implication for the § 103 question posed: The art set is strong against the “automated playlist + ads + persistent window” concept (which is functionally VanHoff), but weaker on (i) genuine concurrency between accessing and presenting different show-structure resources, and (ii) user-variable per-resource display duration. Any invalidity contention under § 103 must therefore:

• prove the concurrency element with art that actually pre-fetches a show-structure resource while another is being presented (Mogul ’802292-style prefetching combined with Richardson/VanHoff is the most promising candidate not yet tried), and
• prove the interactively variable duration element with something closer than VanHoff’s parameterized applets.

A different, cleaner route is the double-patenting run the litigants already pursued: the Office found all asserted claims of the ’451 “save one” not patentably distinct from the ’819/’932 claims (D. Del. ODP brief, C.A. 22-304). That is an obviousness-type-double-patenting exposure, not a § 103 prior-art rejection, but it is the same practical invalidity theory.

7. Cross-reference updates / corrections to prior sections

1. Claim 26 — now resolved. The earlier summary flagged claim 26 as unverified. Primary-source evidence (Robocast’s Patent Owner Preliminary Response in IPR2023-00182) confirms that claims 1 and 26 both capture the “interactively variable duration information” limitation, and that claims 26–28 were among the challenged claims. This is consistent with, and should be substituted for, the earlier “not fully verified” caveat.
2. Netflix’s DJ counterclaim characterization of claim 16 (“automatically creating and storing a show structure of nodes … in response to said online search”) is corroborated by the PTACTS petition record listing claims 1, 26 (and dependents) as challenged over Escobar, Escobar+Rege, VanHoff, and VanHoff+Rakavy. The granted claim 16 wording still differs from the published-application wording, so treat exact quoted claim language as unverified at grant stage even though the substance is now confirmed.

8. Bottom line

• Facially, § 103 invalidity is well supported for the core ’819 concept: VanHoff alone discloses an automatically executed, node/pointer-based list of lists that displays advertisements in a dedicated (persistent) window with timing/sequencing parameters, and Rakavy supplies the profile-driven, dynamic, background-downloaded ad features of the dependents; Escobar + Rege supply the generic networked-pointer/address architecture. Motivations (targeting precision, network efficiency, same-field/same-problem, predictable substitution) are articulated and technically reasonable.
• However, the record shows the § 103 case failed twice at the PTAB on the two narrow but load-bearing limitations — concurrent access/presentation and interactively variable duration — and the Delaware court invalidated the claims on § 101 grounds instead of § 103. A § 103 challenge that does not independently close those two gaps is unlikely to succeed on this record.
• Confidence: High on the reference identities and their key disclosures (primary PTAB/Delaware documents and the patents themselves). Medium on any assertion of ultimate § 103 invalidity of the granted claims, because the PTAB expressly found the VanHoff-based grounds insufficient on the two limitations above.

Key sources: Google Patents US8606819B2; Netflix IPR2023-00182 Petition & Patent Owner Preliminary Response (ptacts.uspto.gov, petition 1550580 / 1550476); Robocast POPR filed in C.A. 22-304 (Doc. 92-13); D. Del. C.A. 22-305 summary-judgment record (CourtListener RECAP 78231, Doc. 395); U.S. 5,959,623 (VanHoff); U.S. 5,913,040 (Rakavy); U.S. 5,659,793 (Escobar); U.S. 5,612,897 (Rege); U.S. 5,809,247 (Richardson); ’819 front-page references (FreePatentsOnline US8606819).