US 7155451

I'll verify the patent details and check for any 2026 CAFC activity.

Let me check the specific CAFC docket and 2026 activity.

Let me check the Federal Circuit docket 25-1651 and the current litigation status.

US Patent 7,155,451 — Verification Summary

Search note / scope: I searched for the literal number 7155451 / 7,155,451 only. Results for related family members (8,606,819; 8,606,820; 8,965,932; 8,738,655) are continuations/divisionals of the same specification and are not the patent you asked about — they are flagged separately below only where the record itself ties them to '451.

Bibliographic data (as confirmed in the record)

Abstract (verbatim, as printed)

"A method of sequencing and scheduling web resources, via a software application that collects URLs and feeds them to a Web browser, so that the amount of clicks and decisions are reduced when browsing the Internet. The method begins after a computer user with Net-access encounters a URL that leads to a collection of other URLs that the software application has arranged to be presented in a continuous, show manner. This collection of resources then plays automatically, going from one resource to the next without the user being required to make a decision or click. The decision-making process is not inhibited, it is made optional. A method of inserting full-screen advertising, public service announcements, news, etc. has been developed. The server software application module described herein allows a publisher to stream URLs to a user who does not have the client-side software. The publishing module allows a user to format resources to a particularly desirable size and characteristic that promotes readability during a show viewing session. This same module can publish collections of nodes for others to view as a whole sequence, accessible via e-mail, screen saver or as a web resource."

Independent claims in plain language

The record I retrieved quotes four independent claims — 1, 22, 37, and 39 — all of them "method" claims for displaying content on a user's computer from a plurality of resources.

Claim 1 — "Create a playlist and auto-advance it, with user-adjustable display time."
A method with three steps: (a) create a "show structure of nodes," where each node identifies a resource out of many accessible resources; (b) without requiring user input, automatically access several of those resources; and (c) automatically display each resource's content according to the show structure — where creating the structure includes providing interactively variable duration information so the user can vary how long each item is displayed. (Text quoted in IPR2023-00590 record.)

Claim 22 — "Build the playlist automatically from search results."
Same general framework, but the trigger is an on-line search: after receiving search results and their corresponding URL resources, the system automatically creates and stores a show structure of nodes from those results; then, without user input, accesses each resource, retrieves content, and automatically delivers it for display per the show structure. (Text quoted in the Google/YouTube IPR2023-00591 petition.)

Claim 37 — "Multidimensional, concurrently spanning playlist."
Creates a multidimensional show structure of nodes; without user input, accesses the resources, where at least two nodes are spanned concurrently; and automatically displays the content such that the content of those two nodes is displayed during an overlapping time period (i.e., simultaneous/parallel presentation). (Text quoted in the IPR2023-00590 record.)

Claim 39 — "Pick a category, then auto-build the playlist."
Adds a category-selection step at the front: select a category from a predefined list, perform an on-line search related to that category, then automatically create/store a show structure of nodes from the search results, and proceed as in the search-based claims. (Preamble and step [a]–[d] quoted in the Google/YouTube IPR2023-00591 petition.)

Uncertainty flagged: I could confirm only these four independent claims. Because the patent carries 64 claims (with claims 1–21, 22–44 in the challenged ranges and claims 3–21, 33–34, 40–64 largely not quoted in the materials I retrieved), I cannot confirm from authoritative sources whether any additional independent claims (e.g., system/apparatus claims) exist beyond 1, 22, 37, and 39. Treat that list as provisional, not exhaustive.

Representative dependent claims I did verify: cl. 2 (duration information), cl. 23 (duration info), cl. 24 (downloading a file from a server), cl. 25 (transmitting dynamic content), cl. 26 (formatting dynamic content in a persistent content window), cl. 27 (inserting resource identifiers interspersed in the show structure), cl. 28 (dynamic content is an advertising message), cl. 29 (dynamic content per user profile), cl. 30 (storing content for each resource), cl. 31 (reformatting content per predetermined arrangement), cl. 32 (control buttons), cl. 35 (advertisements inserted between displayed contents), cl. 36 (ad selection based on user profiles), cl. 38 (claim 37 minus the "interactively variable"/"vary said duration" language).

Litigation / 2026 docket check

CAFC dockets (2026): I found one Federal Circuit appeal involving this patent — Robocast, Inc. v. Netflix, Inc., No. 2025-1651, docketed April 17, 2025 (notice of appeal filed April 14, 2025), Federal Circuit, nature of suit "Patent Infringement (Fed. Qst.)." The docket record I retrieved was last updated April 17, 2025 and shows only the docketing entry (entry of appearance, certificate of interest, docketing statement, appellant's brief due 06/16/2025).

• I did not find any 2026 merits decision in 25-1651, and I did not find any other 2026 CAFC docket naming 7,155,451. If a 2026 opinion or Rule 36 judgment exists, my searches did not surface it. This is a genuine gap — please treat the 2026 status as unverified.

Underlying district court outcome (why it's on appeal): In Robocast, Inc. v. Netflix, Inc., No. 1:22-cv-00305-RGA-JLH (D. Del.), Judge Jennifer L. Hall granted summary judgment of invalidity under 35 U.S.C. § 101 on February 21, 2025 (reported Feb. 24, 2025), holding the asserted claims of the '451, '819 and '932 patents "directed to organizing and displaying playlists of content" and abstract. Robocast appealed — that appeal is 25-1651. The parallel Robocast v. YouTube/Google case (1:22-cv-00304) was stayed in light of that ruling.

PTAB: Three IPRs against the '451 patent were filed and all three institution decisions were denials:

• IPR2023-00081 — Netflix, Inc. (challenged claims 1, 2, 37, 38) — institution denied, with a dissent by APJ Cygan.
• IPR2023-00590 — Google LLC / YouTube, LLC (claims 1–21, 37, 38) — institution denied (Sept. 18, 2023).
• IPR2023-00591 — Google LLC / YouTube, LLC (claims 22–32, 35, 36, 39–44) — institution denied (Sept. 18, 2023).

Earlier enforcement (all settled/terminated): Robocast v. Microsoft, No. 1:10-cv-01055 (D. Del., 2010); Robocast v. Apple, No. 1:11-cv-00235 (D. Del., 2011) — accusing iTunes, Apple TV, Front Row, Safari "Top Sites."

Key sources

• https://patents.google.com/patent/US7155451/en (full text, claims-adjacent description, family, reassignments, litigation links)
• https://portal.unifiedpatents.com/patents/patent/US-7155451-B1 (bibliographic corroboration; note conflicting filing/grant dates)
• IPR2023-00590 / IPR2023-00591 petition text (claim language for claims 1, 2, 22–32, 35–39) — https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1553613](/patent/1553613) and .../1550476
• IPR2023-00081 institution decision (deny) — https://www.docketalarm.com/cases/PTAB/IPR2023-00081/
• D. Del. SJ opinion (1:22-cv-00305, D.I. 395) — https://storage.courtlistener.com/recap/gov.uscourts.ded.78231/gov.uscourts.ded.78231.395.0.pdf
• Fed. Cir. docket 25-1651 — https://dockets.justia.com/docket/circuit-courts/cafc/25-1651

Bottom line: US 7,155,451 is Damon C. Torres's (Robocast, Inc.'s) expired automated-web-browsing/"show structure" patent, filed 1998-09-01 off a 1996 provisional, issued 2006-12-26 with a 1,072-day PTA, and expired ~Aug. 2020. Its four confirmed independent claims cover (1) auto-advancing a node playlist with user-adjustable durations, (22) auto-building that playlist from search results, (37) concurrently spanning/overlapping multidimensional playlists, and (39) category-driven search-built playlists. It was held invalid under §101 by the District of Delaware in February 2025, and that judgment is on appeal at the Federal Circuit as 25-1651 — with no 2026 CAFC disposition that I was able to verify.

I'll research litigation involving US patent 7155451, starting with the sources you named and the case links embedded in the patent record.

I have substantial results. Let me pin down the outcomes and current statuses, including the Federal Circuit appeal.

Litigation Involving U.S. Patent No. 7,155,451

Important framing: Every district-court case I found was brought by Robocast, Inc. (assignee of the '451 patent; inventor Damon C. Torres) as plaintiff. Robocast is characterized in the record as a non-practicing entity whose asserted patents have expired. I found no case in which the '451 patent was asserted against Robocast as a defendant and no third-party plaintiff asserting the '451 patent.

Note also the '451 patent expired August 9, 2020 (adjusted expiration), so all 2022-and-later assertions could only seek past damages.

1. District Court Cases

A. Robocast, Inc. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.)

• Court/Jurisdiction: [U.S. District Court for the District of Delaware (Judge Richard G. Andrews)](/courts/district-of-delaware-judge)
• Case No.: 1:10-cv-01055-RGA
• Filed: December 2010 (First Amended Complaint for infringement of the '451 patent, 35 U.S.C. § 271)
• Asserted patent: '451 (sole patent)
• Accused products: Bing.com, MSN.com, MSNBC.com, Xbox 360 ESPN app (video playlists); Windows 8 Xbox Music and Xbox 360 "Video"/"Home" channels (changing tiles)
• Key rulings: Claim construction (D.I. 246) construing "show structure of nodes" and "node"; summary-judgment opinion Feb. 13, 2014, Robocast, Inc. v. Microsoft Corp., 21 F. Supp. 3d 320 (D. Del. 2014) — granted in part (e.g., SJ of non-infringement for Xbox 360 "Home"/"Video" channels) and denied in part (issues left for trial on "each" resource, duration, scrubber-bar as interactively variable duration, and contributory infringement). A further opinion addressed exclusion of Robocast's damages expert (Nash Bargaining Solution / EMVR issues).
• Status/Outcome: Concluded. Later briefing by Netflix refers to the "conclusion of the Microsoft and Apple litigations," confirming termination. ⚠️ I could not confirm from the retrieved sources whether the case ended by jury verdict, settlement, or dismissal; treat the precise final disposition as unverified.

B. Robocast, Inc. v. Apple Inc.

• Court/Jurisdiction: D. Del. (Judge Richard G. Andrews)
• Case No.: 1:11-cv-00235-RGA (a/k/a "11-235")
• Filed: March 21, 2011 (Complaint for infringement of the '451 patent)
• Asserted patent: '451 — claims 10, 22, 37, 38
• Accused functionalities: iTunes Showcase/Flowcase; Apple TV "Parade" and Flickr screensaver; Safari "Top Sites"
• Key rulings: Claim construction (D.I. 239); summary-judgment opinion April 2014, Robocast, Inc. v. Apple Inc., 39 F. Supp. 3d 552 (D. Del. 2014) — denied SJ on several non-infringement/invalidity issues (nodes-with-duration, concurrent spanning of two nodes, claims 10/22 limitations) and on inequitable conduct, while granting certain relief. Invalidity theories included the Escobar reference (U.S. 5,659,793), the Zellweger "Scripted Documents" article, and Helfman (U.S. 6,119,135) + Braverman (CCI Slide Show 1.0).
• Status/Outcome: Concluded (2014). ⚠️ Same caveat as Microsoft — precise final disposition not confirmed in retrieved sources.

C. Robocast, Inc. v. Netflix, Inc. (the lead recent case)

• Court/Jurisdiction: D. Del. (originally Judge Andrews per case number 1:22-cv-00305-RGA; the merits ruling was by Judge Jennifer L. Hall, 1:22-cv-00305-JLH)
• Case No.: 1:22-cv-00305
• Filed: March 7, 2022
• Asserted patents: '451, 8,606,819 ('819), 8,965,932 ('932)
• Accused functionality: Netflix autoplay during Post-Play (from March 7, 2016) and Flixtape
• Key rulings:
  • Nov. 14, 2022: Motion to dismiss granted in part — vicarious direct infringement, indirect infringement, and willfulness claims dismissed; only direct infringement remained.
  • Feb. 21, 2025: Summary judgment for Netflix — all asserted claims invalid under 35 U.S.C. § 101 (Alice/Mayo) as directed to the abstract idea of "collecting, organizing, and automatically displaying content (e.g., a playlist of Internet content)." (Robocast had invoked a "technological solution to a technological problem.")
  • Robocast had by then narrowed to claims 1, 25, 38, 41 ('451); 1 ('819); 1, 13, 25, 27, 31 ('932).
• Status/Outcome: District court judgment of invalidity for Netflix; on appeal. See below.

D. Robocast, Inc. v. YouTube, LLC and Google LLC

• Court/Jurisdiction: D. Del.
• Case No.: 1:22-cv-00304
• Filed: March 7, 2022 (same day as the Netflix complaint)
• Asserted patents: '451, '819, '932
• Key rulings: Sept. 22, 2023 opinion — granted motion to dismiss willful and indirect infringement for the '819 and '932 patents (patents expired Sept. 2, 2017, before Defendants' alleged knowledge), but found the knowledge requirement satisfied for the '451 patent (Defendants' 2019 invalidity contentions in Virentem Ventures, LLC v. YouTube, LLC, C.A. No. 1:18-cv-00917-MN, D. Del.); invalidity of the '451 for obviousness-type double patenting dismissed with leave to refile pending In re Cellect.
• Status/Outcome: Stayed in light of the Feb. 21, 2025 Netflix invalidity ruling (per Law360 reporting of the Netflix decision).

2. Federal Circuit Appeal (currently pending)

• Case: Robocast, Inc. v. Netflix, Inc., No. 25-1651 (U.S. Court of Appeals for the Federal Circuit)
• Appeal docketed: April 17, 2025 (appeal received 04/14/2025); notice of appeal from the D. Del. invalidity judgment
• Status: Pending. ⚠️ No decision identified as of the sources retrieved. (This is also the CAFC case listed in the patent record itself.)

3. PTAB Proceedings Involving the '451 Patent (and related patents)

These are inter partes reviews, not district-court litigation, but they are directly relevant:

Petitioners relied in part on the D. Del. claim-construction order from the Microsoft/Apple litigation (June 28, 2013), which the Board had adopted in denying institution in Unified Patents, LLC v. Robocast, Inc., IPR2022-01125.

4. Related / Contextual Facts

• Common priority chain: Provisional 60/025,360 (Sept. 3, 1996) → App. 08/922,063 (Sept. 2, 1997) → App. 09/144,906 (Sept. 1, 1998), which issued as the '451 patent on Dec. 26, 2006. All three asserted patents ('451, '819, '932) share a common specification.
• Inequitable-conduct allegations: In the Microsoft, Apple, and Netflix cases, defendants alleged that inventor Torres submitted a false Nov. 1999 declaration (the "Torres Declaration," with the "Hertzig Letter") during prosecution of the '063 application — the priority ancestor — and that this rendered the '451 (and later patents) unenforceable under the doctrine of "infectious unenforceability." This issue survived summary judgment in 2014; Netflix renewed it, but the 2025 Netflix judgment rested on § 101 invalidity rather than inequitable conduct. It remains a live theme of the appeal.

Summary of Known Litigation

Caveats on confidence

• I verified the Netflix, Apple, Microsoft, and YouTube/Google case identities, numbers, and key rulings against complaints, court opinions, and PTAB exhibits (see URLs below).
• ⚠️ The precise final dispositions of the 2010 Microsoft case and 2011 Apple case (verdict, settlement, or dismissal) are not stated in the documents I retrieved. I am flagging this rather than guessing.
• ⚠️ I did not locate any other defendants beyond Microsoft, Apple, Netflix, YouTube, and Google for the '451 patent. If additional suits exist (e.g., against other "Flixtape"/autoplay-type products), I did not find them in these sources.
• The case number appears variously as 1:22-cv-00305-RGA, -JLH, and -RGA-JLH across documents (judge reassignment); I have reported each as it appears literally.

Key sources

• D. Del. Apple opinion: https://www.ded.uscourts.gov/sites/ded/files/opinions/11-235_0.pdf
• Robocast v. Microsoft, 21 F. Supp. 3d 320 (D. Del. 2014): https://www.courtlistener.com/opinion/[7306561](/patent/7306561)/robocast-inc-v-microsoft-corp/
• Robocast v. Apple, 39 F. Supp. 3d 552 (D. Del. 2014): https://www.courtlistener.com/opinion/[7308169](/patent/7308169)/robocast-inc-v-apple-inc/
• Netflix SJ order excerpt (D.I. 463, Feb. 21, 2025): https://www.courtlistener.com/docket/63141325/463/robocast-inc-v-netflix-inc/
• Robocast v. YouTube (D. Del. 2022) opinion: https://www.courtlistener.com/opinion/[9635739](/patent/9635739)/robocast-inc-v-youtube-llc/
• Netflix complaint/answers (IPR exhibits): https://www.docketalarm.com/cases/Delaware_District_Court/1--22-cv-00305/Robocast_Inc._v._Netflix_Inc/docs/28.pdf
• Microsoft First Amended Complaint (10-cv-1055): https://www.docketalarm.com/cases/PTAB/IPR2023-00081/Netflix_Inc/docs/10-24-2022-Petitioner/Exhibit-1013-Ex_1013_DDE_1_10_cv_01055_40_MS_Case_Amended_Complaint.pdf
• Apple Complaint (11-cv-235): https://www.docketalarm.com/cases/PTAB/IPR2022-01125/Unified_Patents_LLC/docs/06-30-2022-Petitioner/Exhibit-1025-23-Complaint,_Robocast,_Inc_v_Apple_Inc,_111_cv__235,_Dkt_1_D_Del,_Mar_21_2011.pdf
• AO 120 patent-filing report (YouTube/Google): https://www.docketalarm.com/cases/PTAB/IPR2022-01125/Unified_Patents_LLC_v._Robocast_Inc/docs/06-30-2022-Petitioner/Exhibit-1008-Prosecution_History_of_US_Patent_8,606,819_child_of_932_Patent.pdf
• Law360 summary of Netflix decision: https://www.lw.com/en/practices/admin/upload/SiteAttachments/Netflix-Sinks-Robocast-Playlist-Patents-In-Delaware-IP-Suit.pdf
• Fed. Cir. appeal docket 25-1651: https://dockets.justia.com/docket/circuit-courts/cafc/25-1651
• Patent record (litigation links, expiration Aug. 9, 2020): https://patents.google.com/patent/[US7155451](/patent/US7155451)/en

If you'd like, I can now dig into PACER/CourtListener docket sheets for the Microsoft and Apple cases to confirm their exact final dispositions, or pull the Federal Circuit briefing in 25-1651 to report the arguments on appeal.

I'll research these three PTAB cases before writing up.

Now let me get details on IPR2023-00591, the Netflix rehearing, and any later proceedings/appeals.

Proceedings overview

Three AIA trial proceedings are on file against US 7,155,451 — IPR2023-00081 (Netflix), IPR2023-00590 and IPR2023-00591 (Google/YouTube) — all three terminated as "Not Instituted - Merits," meaning three sophisticated petitioners with full claim charts, expert declarations (Dr. Christopher M. Schmandt) and district-court incentive were each found not reasonably likely to prevail on any challenged claim; no claim of the '451 patent has ever been instituted for trial, canceled, or adjudicated patentable by the Board. The bottom line for a defendant is counter-intuitive: the PTAB record hardens the '451 patent against prior-art attacks (§ 315(e)(2) estoppel is empty because no FWD ever issued, but three failed § 103 petitions tell you the art is weak), while the patent's actual vulnerability was established elsewhere — the District of Delaware held the asserted claims invalid under 35 U.S.C. § 101 on summary judgment in 2025, and the patent expired on 2020-08-09.

A note on what "survived" means here: a denial of institution is not a holding of patentability. The Board only decided petitioners had not shown a reasonable likelihood of prevailing. No claim of the '451 was "sustained" on the merits; none was canceled either.

IPR2023-00590 — Google LLC and YouTube, LLC v. Robocast, Inc.

• Type: Inter Partes Review
• Filed: 2023-02-21
• Status: Institution Denied (verbatim ODP/Unified Patents status: "Not Instituted - Merits"). Plain English: the Board denied the petition outright on 2023-09-18 and the proceeding terminated the same day.
• Judge panel: APJs David C. McKone (opinion author), Patrick M. Boucher, Michael T. Cygan — a three-judge panel identical in composition to the Netflix panel.
• Petition grounds: § 103 obviousness against claims 1–21, 37 and 38 (i.e., independent claim 1, twenty of its dependents, and independent claim 37). Principal references identified in the petition/exhibit record: U.S. Pat. No. 5,634,062 to Shimizu, together with Fox, HTML Web Publisher's Construction Kit (1995), Benedict, Using Harvard Graphics 2 for Windows (1993), and the Microsoft Press Computer Dictionary (2d ed. 1994). Supporting declaration of Christopher M. Schmandt (EX1002). Petitioner explicitly took the positions of the prior Delaware constructions ("show structure of nodes" = "a structure that is arranged for the display of content by specifying one or more paths through a plurality of nodes"; "node" = "an identifier of a resource that includes an address to the resource and the duration for which the resource's content is to be presented by default") without conceding their correctness.
• Institution decision: Denied 2023-09-18 (Paper 12 as listed in the parties' D. Del. joint appendix; one secondary source lists Paper 10 for this case — paper numbering varies across sources, so I flag it). The decision states: "For the reasons explained below, we decline to institute an inter partes review of the '451 patent." Patent Owner had separately pressed discretionary denial under § 314(a) (all six Fintiv factors) and multiple-petition § 325(d) in its Preliminary Response, and the ODP/Unified status label "Not Instituted - Merits" indicates the Board reached the merits rather than resting on discretion; Robocast's press release likewise characterizes the ruling as a merits finding that Google/YouTube were "not reasonably likely to prevail." Because the denial is merits-labeled but the full text was not retrievable in my sources, treat the precise balance of merits vs. discretionary grounds as unverified.
• Final Written Decision: None. No institution = no FWD = no claim-level verdict.
• Settlement / termination: None — termination by denial, not settlement. Petitioner's request for refund of post-institution fees (2023-11-20) was approved 2023-11-24, confirming no trial ever began.
• Appeal: Not appealable. Denial of institution is final agency action immune from appeal under 35 U.S.C. § 314(d); Robocast's release notes the decisions "are not appealable."
• Defensive value: Claim 1 and twenty dependents were fully briefed and mapped by a well-funded petitioner and went nowhere, so a new IPR built on Shimizu/Fox/Benedict is a poor investment. Caution: no estoppel attached (§ 315(e)(2) estoppel requires an FWD), so nothing in this denial binds anyone — including Google/YouTube — in district court.

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

• Type: Inter Partes Review
• Filed: 2022-10-24
• Status: Institution Denied (verbatim: "Not Instituted - Merits"); Board termination date 2023-05-11 as reflected in the docket.
• Judge panel: APJs David C. McKone and Patrick M. Boucher, with APJ Michael T. Cygan dissenting — a split panel, and the only one of the three '451 proceedings with a published dissent. (Docket Alarm separately lists APJ Nabeel Khan in the case roster, likely for the rehearing stage.)
• Petition grounds: § 103 obviousness against claims 1, 2, 37 and 38 (corrected petition, Paper 11). The petition's claim-appendix mapping runs the independent-claim limitations [1a]–[1d] and [37a]–[37c] against a primary reference and applies the Henley reference to limitations [1c]/[37c] and to claim 38; the declaration of the petitioner's expert was EX1003, with EX1001 the '451 patent and EX1002 its file history. I identified Henley and the claim mapping from the petition text but could not retrieve the complete ground captions, so the full reference combination for every claim is unverified.
• Institution decision: Denied 2023-05-11. The Board declined to institute, reasoning that Netflix "is not reasonably likely to prevail in showing that" any challenged claim is anticipated by or obvious over the prior art (as characterized in Robocast's and counsel's public statements). Because Cygan dissented, this was a 2–1 call — the closest of the three, and the reason the Delaware court's posture mattered: Judge Andrews denied Netflix's motion to stay on 2023-01-26, noting "one of the IPR petitions has already been denied" and that the case was "moving forward," with leave to renew only if another petition instituted.
• Petitioner's follow-up: Netflix filed a Request for Rehearing on 2023-06-12; the docket shows a Board entry dated 2023-08-30. I could not retrieve that entry's text, so I cannot confirm whether it denied rehearing or was something else — treat the rehearing disposition as unverified.
• Final Written Decision: None.
• Settlement / termination: None.
• Appeal: Not appealable (§ 314(d)); no FWD existed to appeal.
• Defensive value: This is the strongest signal that the '451 patent is a hard PTAB target: Netflix, represented by Sheppard Mullin (Harper Batts, lead), fully developed § 103 grounds before the earliest-filed panel and lost, with only one judge dissenting. But note the symmetry — Netflix was not estopped, and it subsequently won invalidity in Delaware on § 101 grounds, precisely because the PTAB door closed. Source decision: IPR2023-00081, Paper 19, Decision Denying Institution (2023-05-11) · PTAB petition record · Google Patents US7155451 litigation block

IPR2023-00591 — Google LLC and YouTube, LLC v. Robocast, Inc.

• Type: Inter Partes Review
• Filed: 2023-02-21 (filed the same day as -00590, as a second, non-overlapping-claims petition under Petitioner's "Explanation of Multiple Petitions")
• Status: Institution Denied (verbatim: "Not Instituted - Merits"); terminated 2023-09-18.
• Judge panel: APJs David C. McKone, Patrick M. Boucher, Michael T. Cygan (same panel as -00590).
• Petition grounds: § 103 obviousness against a claim set different from -00590; the POPR text confirms independent claim 22 was challenged here, and Petitioner used the same Schmandt declaration (EX1102) for both -00590 and -00591, with the claim 22 analysis expressly incorporating the claim 1 analysis ("Many of the limitations of claim 22 are substantially similar to limitations recited in claim 1 that were covered above"). Robocast's counsel objected to the multiple-petition structure and argued § 325(d) discretionary denial. The complete claim list for -00591 is unverified in my sources; arithmetic on Robocast's public statement that the five Google IPRs covered "all 141 claims" of the three asserted patents implies roughly 22 claims were challenged in this petition (compared with 23 in -00590, 29 on the '819, and 67 on the '932), but that is an inference, not a documented claim list.
• Institution decision: Denied 2023-09-18 (Paper 10 as listed in the parties' D. Del. joint appendix; one source lists Paper 16 for -00592, so verify paper numbers against PTAB E2E). Denial issued simultaneously with -00590; Patent Owner had argued that "[t]he Board should exercise its discretion under § 325(d) and deny institution of either the instant Petition or the co-pending IPR2023-00590 Petition" given substantial overlap and a single shared expert declaration. Whether the Board's denial rested on § 325(d)/multiple-petition discretion, on the merits, or both is unverified — the ODP status label says "Merits."
• Final Written Decision: None.
• Settlement / termination: None.
• Appeal: Not appealable (§ 314(d)).
• Defensive value: Even the second, claim-disjoint Google petition — the kind of filing that ordinarily gets a merits look — was denied. The practical lesson for a defendant is that the § 325(d)/multiple-petition and Fintiv doctrines cut against petitioners here, but they do not create estoppel or preclusion for anyone else. Petitioner counsel: Heidi Keefe (Cooley). Patent Owner counsel: Steven J. Rizzi (McKool Smith). Sources: PTAB petition record for -00591 · Unified Patents PTAB entry · Denial of Institution exhibit filed in D. Del. 1:22-cv-00304

Strategic summary

Claim-status ledger for US 7,155,451. CANCELED: none — no claim has ever been canceled, because no petition was instituted. SUSTAINED: none in the PTAB sense — no FWD ever issued, so no claim was adjudicated patentable by the Board. UNTESTED on the PTAB merits: all 64 claims. The claims that were actually challenged and denied institution are 1, 2, 37, 38 (Netflix, IPR2023-00081) and 1–21, 37, 38 (Google/YouTube, IPR2023-00590), plus the claim set in IPR2023-00591 including claim 22. Claim coverage was therefore broad against independent claims 1, 22 and 37 but never complete — and, critically, the invalidity that actually landed came from a different statute and a different forum. In Robocast, Inc. v. Netflix, Inc., No. 1:22-cv-00305 (D. Del.), Robocast narrowed to ten asserted claims — 1, 25, 38 and 41 of the '451 patent, 1 of the '819 patent, and 1, 13, 25, 27 and 31 of the '932 patent — and Judge Jennifer L. Hall granted Netflix summary judgment of invalidity under § 101 (Alice), holding the claims "directed to the abstract idea of collecting, organizing, and automatically displaying content," with an order issued 2025-02-21 as reported 2025-02-24. The parallel YouTube/Google case (1:22-cv-00304) was stayed in light of that ruling. Netflix had also pressed inequitable conduct (a Torres declaration alleged to contain false information) and In re Cellect obviousness-type double patenting; the ODP motion was denied at the pleading stage on 2024-05-17 with leave to reraise. All three patents have expired — the '451 lapsed 2020-08-09 per the Google Patents legal-status record — so any remaining exposure is past damages only.

Estoppel landscape. § 315(e)(2) estoppel is empty across the board. Estoppel attaches only after a final written decision, and there is no FWD on this patent; three institution denials produced zero estoppel. Netflix, Google and YouTube are each free to litigate, in district court, every ground they raised or could have raised at the PTAB — and Netflix did exactly that, winning on § 101. Likewise, because § 315(e) never triggered, a new defendant is not bound by any petitioner's failed art. What limits new defendants is not estoppel but the § 315(b) one-year bar: both Delaware complaints were filed on 2022-03-07, so any party served in those actions was time-barred from filing an IPR long ago. A defendant newly served today has a fresh one-year window, but the substantive record described below should inform whether to use it.

Pattern signals. This is a three-petitioner, family-wide campaign that failed completely on the merits. Count the AIA filings across the whole family: IPR2022-01125 (Unified Patents — a defensive aggregator, exactly the entity you asked about — against the '932 patent, institution denied 2023-01-20); IPR2023-00081 (Netflix, '451) and IPR2023-00182 (Netflix, '819); and the five Google/YouTube petitions filed 2023-02-21 (IPR2023-00590, -00591, -00592, -00593, -00594) covering the '451, '819 and '932. Robocast's 2023-09-25 announcement characterizes the result as 8-for-8 institution denials on the merits across all three patents, which arithmetically corresponds to Unified (1) + Netflix (2) + Google/YouTube (5) — I have directly confirmed the '451 denials and the Unified '932 denial, but the Netflix '819 denial (IPR2023-00182) and the Google '819/'932 denials are confirmed only through that announcement and should be treated as reported-but-not-independently-verified for those specific dockets. Robocast litigated the PTAB phase aggressively (McKool Smith's Steven J. Rizzi led, with Cantor Colburn; McKool Smith publicly touted the highest PTAB patent-owner win rate for 2022), filed Preliminary Responses, Preliminary Sur-replies, a § 325(d) objection brief, and won. A CAFC appeal, No. 25-1651, appears in the Google Patents litigation block for this family; I could not retrieve the docket text to confirm the parties, the issues, or the disposition, and it is more consistent with an appeal of the Delaware § 101 judgment than with any PTAB decision (none of which are appealable). Flagged as unverified.

Recommended next steps

• Do not build a defense primarily on this patent's PTAB history — there is nothing to build on. Three institution denials, no FWD, no canceled claims, no estoppel. There is no "claims 1–5 have been canceled" argument to make here; that scenario does not exist for the '451. If your demand letter or complaint asserts the '451, the PTAB file gives you no leverage.
• Shift to the Delaware § 101 record. In Robocast v. Netflix, No. 1:22-cv-00305-JLH (D. Del.), the court granted summary judgment of invalidity of asserted claims 1, 25, 38 and 41 of the '451 patent under Alice step one and step two, reasoning that "[n]one of the asserted claims contain any specificity as to how to accomplish the tasks of generating a playlist of content…" and that "[c]alling something a technical solution does not make it so." That order is the single highest-value document for a defendant today — but note it is a district court judgment, the parallel Google/YouTube case was stayed rather than dismissed, and an appeal (reported as CAFC No. 25-1651) means the § 101 holding is not final. Pull the current docket before relying on it. Docket: CourtListener, Robocast, Inc. v. Netflix, Inc., 1:22-cv-00305.
• Check the damages window first. Because the '451 expired on 2020-08-09, any assertion is a past-damages claim; pair that with the § 101 ruling and the inequitable-conduct record (Netflix's allegations regarding the Torres declaration) as your leverage points rather than § 103.
• If you still want an IPR, note the practical constraints: the § 315(b) one-year clock from service, the Board's demonstrated hostility to this petition family under § 325(d) and the multiple-petition guidance, and the fact that Shimizu/Fox/Benedict and the Netflix grounds have already been presented and rejected. A materially different primary reference with an admission-quality teaching would be required — and you would be litigating against three prior merits denials in the same art field.
• Verify these items before filing anything: (1) the full text and rationale of the IPR2023-00590 and -00591 denials and whether they rested on merits or § 325(d) discretion; (2) the complete claim list challenged in IPR2023-00591; (3) the 2023-08-30 Board entry in IPR2023-00081 (rehearing disposition); (4) whether the Netflix '819 and Google '819/'932 petitions were in fact denied as reported; and (5) the parties, issues and status of CAFC No. 25-1651. Primary sources: PTAB E2E / PTAB Decisions, the Unified Patents litigation portal, and Google Patents US7155451.

I'll research the assignment record for US 7155451 before writing up the analysis.

Let me dig into the specific assignment records, correspondent of record, and the litigation history.

Let me try to pin down the reel/frame and correspondent of record.

Assignment Record Reconstruction — US 7,155,451 B1

Data-quality note up front: I was able to confirm the existence and content of a post-issuance assignment in this chain (via Google Patents legal events and corroborating litigation records), but I could not retrieve the reel/frame numbers or the recorded correspondent — those fields are exposed only in the USPTO Assignment Center UI, and they did not surface in any indexed source reachable here. Anything I could not verify is labelled as such. Do not read a stale reel/frame into this report; pull it live at https://assignmentcenter.uspto.gov/ (search by patent number 7155451 or by reel/frame from the Google Patents legal-events tab).

Inventors

Pattern notes:

• Sole inventor, no co-inventors — unusual for a 1997–98 web-infrastructure patent; every U.S. family member (8,606,819; 8,606,820; 8,738,655; 8,965,932) names Torres alone.
• The "inventors departing within 12 months" fire-sale tell is NOT present (trivially — one inventor, who is still tied to the assignee: Torres was Chairman/CEO into 2022 and still sits on Robocast's board per its About page).
• The materially unusual fact is the reverse of the usual pattern: the inventor filed as an individual and held the '451 patent personally for ~13 years after issuance rather than assigning to his own company at filing. The transfer to Robocast (see below) coincides with the onset of litigation, not with corporate formation.
• Prosecution-history caveat with a documented integrity finding: the § 1.131 Torres Declaration and its Exhibit A ("Hertzig Letter") were found, per the Netflix brief and the Federal Circuit-adjacent record, to be a fabricated/false affidavit that infected enforceability of the whole family. See D. Del. 1:22-cv-00305, D.I. 394 §§ 3.3–3.8 and the inequitable-conduct briefing at D.I. 395.

Original assignee

No corporate assignee appears on the face of the patent. Google Patents and Unified Patents both list the Original Assignee as "Individual" — i.e. Damon C. Torres personally. Robocast, Inc. is listed only as Current Assignee / Parent Company, consistent with the single recorded transfer in 2010.

• Entity that shipped a product embodying the claims: Robocast, Inc. (founded 1997) marketed/released RoboSurf, RoboGuide, RoboPublisher, RoboSearch, RoboStats, RoboMobile, Robocaster. Robocast's own 2022 press release describes these as available "for licensing" and states the portfolio "has been licensed to leading media companies such as music video distributor Vevo." Defendants describe the company in court filings as "a non-practicing entity" (Netflix stay motion, D. Del. 1:22-cv-00305, D.I. 28). The product-versus-licensing characterization is contested and I am not resolving it here.
• Primary line of business: historically web/media software and consulting; currently IP licensing plus a stated relaunch of "RoboSearch, Robocast Social, RoboFeed" (robocast.com/about).
• Current status: operating (Delaware corporation, New York HQ; securities/assertion activity continuing as of a 2025 Federal Circuit appeal, No. 25-1651). No bankruptcy filing by Robocast or Torres was found in any source reviewed. Note the "Damon's Assets" bankruptcy text that appears in one search result is a different matter (a Damon's restaurant/DNA entity in a W.D. Pa. adversary proceeding) — not Robocast and not this inventor.

Assignment timeline

Only one post-issuance assignment affecting the '451 patent is confirmed in any source reviewed.

• Execution date: not retrievable / recorded 2010-12-17 — Reel ██████/████ (not retrieved — see data-quality note)
  • Conveyance: Assignment
  • Assignor: Torres, Damon C. (the sole named inventor, holding personally)
  • Assignee: ROBOCAST, INC.
  • Correspondent: Not verifiable from the sources available. For completeness, the prosecution correspondence of record for the family was Sofer & Haroun, L.L.P. (attorney Joseph Sofer; see the '209/'570 file-wrapper correspondence and Sofer's deposition in the prior litigations). I could not confirm that Sofer & Haroun is the assignment correspondent, so I am not counting this toward the repeat-correspondent signal.
  • Context: Pre-assertion transfer / standing-clearing transfer. The inventor personally assigned the patent to his own company in December 2010, the same month Robocast filed its first infringement suit on this patent.

Additional corroboration of Robocast ownership (not separate recorded assignments, and not to be mistaken for reel/frame entries):

• 2011-07-06, 2012-04-18, 2012-06-13 — priority/continuation filings (13/176,818; 13/449,570; 13/495,172) leading to 8,738,655; 8,606,819; 8,606,820.
• 2012 — the 13/449,570 terminal disclaimer recites "the owner, ROBOCAST, INC. of 100 percent interest," confirming the whole family had passed to Robocast by then.
• 2014-04-21 / 2014-04-23 — filings 14/257,505 and 14/259,578 (published as US20140317519A1 / US20140317513A1).

No recorded security agreements, merger documents, change-of-name filings, licenses, releases, or corrections for the '451 patent were found. If the Assignment Center shows a security interest or a second chain I could not see, that would change the cascading-transfer analysis below.

Timeline diagram

timeline
    title Ownership of US 7155451
    1996 : Torres files provisional 60/025360
    1997 : Torres files parent 08/922063
    1998 : Torres files the 906 application
    2006 : Patent issues to Torres personally
    2010 : Torres assigns to Robocast Inc
         : Robocast sues Microsoft
    2011 : Robocast sues Apple
    2022 : Robocast sues Netflix and Google
    2023 : Unified Patents IPR petitions filed
    2025 : Netflix wins invalidity ruling
         : Robocast appeals to Federal Circuit

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. The single recorded transfer (recorded 2010-12-17) runs from the individual inventor to Robocast, Inc., a Delaware corporation (so stated in the 1:22-cv-00304/305 complaints) that was founded by that same inventor in 1997 and that markets a product suite. There is no "IP / Holdings / Ventures" successor, no single-purpose LLC, no registered-agent address of record showing in any source I reviewed.

2. Known asserter in the chain — NOT PRESENT (against the named lists) / UNCLEAR (as a category). The current assignee, Robocast, Inc., does not match any of the enumerated lists (Acacia, Marathon, IV, IPNav, Wi-LAN, Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). It is, however, labeled a non-practicing entity by defendants and appears in assertion-tracker databases as a plaintiff: Unified Patents lists the patent and four Delaware suits, and Unified itself filed IPR2023-00590 and IPR2023-00591 against Robocast patents. Treat as "assertion-active small entity," not as a listed high-frequency NPE.

3. Repeat correspondent across the chain — UNCLEAR / NOT ESTABLISHED. With only one recorded assignment, there is no chain in which a correspondent could recur. The prosecution firm Sofer & Haroun, L.L.P. (Joseph Sofer) is documented across the family's file wrappers and Sofer was deposed in the prior litigation, but I could not verify any attorney as the assignment-recordation correspondent, so I decline to make this a finding.

4. Cascading transfers — NOT PRESENT. One transfer in 2010; no chained LLCs, no transfers within 24 months of each other, no common principal-address pattern.

5. Pre-litigation transfer — PRESENT (weak-to-moderate). The assignment to Robocast was recorded 2010-12-17, and Robocast's first suit on this patent, Robocast, Inc. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), No. 1:10-cv-01055 (D. Del.), was filed in December 2010 — the same month. That timing is the classic "arrange clean standing before asserting" move. I temper the signal because the assignee is the inventor's own operating company, which is equally consistent with a benign late-stage cleanup of a personal-to-corporate title defect. The recording date is also after the apparent filing date, so the execution date (unavailable) determines whether the transfer truly preceded suit.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 proceeding involving Torres or Robocast as to these patents was found.

7. Privateering — NOT PRESENT. No operating company transferred this patent to an NPE to assert on its behalf; the chain runs inventor → inventor's own company. The licenses to Hachette Filipacci, InfoSpace, Vevo and the Microsoft/Apple settlements are the inventor's own company monetizing its own patent.

8. Defensive aggregator — NOT PRESENT (inverse applies). The chain does not terminate at RPX, AST, LOT, Unified, or OIN. Instead, Unified Patents is adverse — it petitioned against the family (IPR2023-00590, IPR2023-00591, both denied institution on the merits). Netflix separately filed IPR2023-00081 (denied). On 2025-02-21, the District of Delaware held the asserted claims of the '451, '819 and '932 patents invalid under § 101 (Robocast v. Netflix, 1:22-cv-00305), which stayed the parallel Google/YouTube case (1:22-cv-00304); the appeal is Fed. Cir. 25-1651.

Verdict

NPE — moderate confidence.

The decisive evidence is equally narrow and pointed: the patent issued to Damon C. Torres personally (Original Assignee "Individual"; no corporate assignee on the face of the patent), and the only recorded transfer moved it to Robocast, Inc., recorded 2010-12-17 — the same month as the first infringement complaint, Robocast v. Microsoft, No. 1:10-cv-01055 (D. Del.). That is one strong pre-assertion-transfer signal, and it is reinforced by the assertion history: suits against Microsoft (2010), Apple (1:11-cv-00235, 2011), Netflix (1:22-cv-00305) and Google/YouTube (1:22-cv-00304), plus defendants' own "non-practicing entity" characterization and the court's 2025 § 101 invalidity ruling on long-expired patents (adjusted expiration 2020-08-09). It does not rise to high confidence because there are no shell LLCs, no cascading transfers, no listed-NPE assignee, and no verified repeat correspondent — the chain is a single inventor's personal-to-corporate transfer, which is a normal corporate-hygiene step as much as an assertion setup.

Verify at: https://assignmentcenter.uspto.gov/ (search patent number 7155451; also try https://assignment.uspto.gov/patent/index.html). Cross-check the legal-events tab at https://patents.google.com/patent/[US7155451B1](/patent/US7155451B1)/en and the patent page at https://portal.unifiedpatents.com/patents/patent/US-7155451-B1.

I'll research the prior art cited on the face of US 7,155,451 and its prosecution record.

I have the core reference list. Let me fill in the truncated tail of the "References Cited" list and confirm dates.

Let me pin down the tail of the front-page U.S. reference list and the foreign/non-patent citations.

Prior Art Analysis — US 7,155,451 B1

Scope note first: I searched for the literal string 7155451 / 7,155,451 only. Results for the family members (8,606,819; 8,606,820; 8,965,932; 8,738,655; US 11/316,209) are the same specification and, where they appear below, are used only to reconstruct face-page text that was OCR-truncated in my reproduction of the '451 face page — they are labelled as such and are not substituted for '451's own citation list.

Date discrepancy flagged: my session metadata gives today as 2026-09-30; the task header says 2026-04-26. I cannot resolve which is authoritative and I have not used either date to make a substantive statement.

0. What "the citations for 7155451" actually comprises

Three distinct buckets exist, and they are not interchangeable for § 102 purposes:

Critical framing that governs everything below: the '451 patent is a pre-AIA patent whose priority runs to provisional 60/025,360, filed Sept. 3, 1996, with the CIP (08/922,063) filed Sept. 2, 1997, and the '451 application filed Sept. 1, 1998. Almost every face-page U.S. reference carries an issue date of 1998, 1999, or 2000 — i.e., after the invention date. Those references are therefore unavailable as § 102(a)/(b) art and can only be § 102(e) art if their own U.S. filing dates predate Torres's invention date. I flag this per-entry rather than pretending the printed issue date is an anticipating date.

And the decisive caveat: the examiner's rejections over this art were reversed. Per Robocast's own pleadings, the '451 patent "issued on December 26, 2006, after the Board of Patent Appeals and Interferences unanimously reversed the examiner's rejections." So everything in Bucket A and B is art that was raised and overcome. "Potentially anticipates" below must be read as what the reference would be asserted against, not as an established § 102 hit.

1. Bucket A — U.S. patent references printed on the '451 face page

Reproduced literally, including the OCR artifacts and the examiner's own classification/art-class annotations as they appear in the reproduction. Do not treat the art-class numbers as reliable — the OCR renders "707/500.1" as "707 500.1" and "706/11" as "706.11".

A-1. The references that map to the "show structure / auto-advance" core

A-2. The references mapping to advertising / profiling / dynamic content dependents

A-3. The earlier "background/system" references (surface only)

These appear earlier in the list as reconstructed. The following are confirmed on the '932 face page (same family, same spec), and the '451 page reproduces the overlapping portion:

3,577,189 A Cocke et al. 5/1971 · 5,109,482 A Bohman 4/1992 · 5,237,648 A Mills et al. 8/1993 · 5,287,266 A Malec et al. 2/1994 · 5,305,389 A Palmer 4/1994 · 5,363,482 A Victor et al. 11/1994 · 5,379,366 A Noyes 1/1995 · 5,485,609 A Vitter et al. 1/1996 · 5,504,675 A Cragun et al. 4/1996 · 5,515,490 A Buchanan et al. 5/1996 · 5,544,354 A May et al. 8/1996 · 5,548,702 A Li et al. 8/1996 · 5,572,643 A Judson 11/1996 · 5,583,560 A Florin et al. 12/1996 · 5,625,781 A Cline et al. 4/1997 · 5,654,886 A Zereski et al. 8/1997 · 5,659,793 A Escobar 8/1997 · 5,668,788 A Allison 9/1997 · 5,675,637 A Szlam et al. 10/1997 · 5,721,827 A Logan et al. 2/1998 · 5,732,216 A Logan et al. 3/1998 · 5,748,190 A Kjosvik 5/1998 · 5,758,151 A Milligan et al. 5/1998 · 5,760,771 A Blonder et al. 6/1998 · 5,768,528 A Blonder et al. 6/1998 · 5,774,123 A Stumm 6/1998 · 5,778,187 A Monteiro et al. 7/1998 · 5,781,186 A Jennings 7/1998 · 5,799,157 A Escallon 8/1998 · 5,806,077 A Wecker 9/1998

Of these, the ones with genuine § 102 potential are the Logan et al. pair (5,721,827 / 5,732,216 — interactive-television navigation and user-controlled concurrent delivery; potentially asserted against claims 1, 32, 37), and 5,515,490 and 5,548,702 (user-interface/windowing, potentially against the control-button claim 32). The rest read as background § 102(a)/(b) art on hypermedia, broadcast data systems and meter/display technology.

⚠ Attribution conflict flagged: 5,774,123 A is rendered on the '451-family face page as Stumm (art class 395/200.61) but as "Matson 715/854" in a different family reproduction. I am not resolving this — treat both attribution and subject matter as unverified.

Contradiction with the prior section, flagged: the earlier summary stated the '451 carries 64 claims with independent claims 1, 22, 37, 39. Nothing in the art record I retrieved contradicts that, and the claim numbers used above are taken from that section. However, because claims 3–21, 33–34 and 40–64 were never quoted in the materials I can retrieve, my claim mapping above is complete only for the claims I can see (1, 2, 22–32, 35–39 incl. 37 and 38, plus claim 2's duration element). Mappings to claims 40–64 are inferred from the specification's disclosure topics (monitoring user decisions, signature/security, local-resource scheduling) and are not verified against claim text.

2. Bucket B — Foreign documents and non-patent literature on the face page

(Note the two Braverman URLs differ slightly across reproductions — ncs2.uiuc.edu/Sdgsoftware/xmosaic/… vs ncs2.uic.edu/dg/software/xmosaic/…. Both are OCR variants of the same NCSA page; I am not auto-correcting either.)

3. Bucket C — The art that actually came closest: IPR grounds (not examiner-cited)

These are the references that a sophisticated challenger selected as the best § 102/§ 103 art for '451 — and PTAB denied institution on all three petitions, holding the petitioner "is not reasonably likely to prevail in showing that" any challenged claim is anticipated or obvious. They are therefore the most probative evidence of what the prior art does not reach.

Sources: USPTO-hosted petition documents at https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1553613](/patent/1553613) and https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1550476](/patent/1550476) (Google/YouTube, IPR2023-00590 / -00591); Netflix Ex. 1101–1112 list in IPR2023-00081.

4. § 102 subsection triage — the point most analyses get wrong

5. Ranked answer to "most relevant prior art"

1. Braverman, "CCI Slide Show" (Sep. 22, 1994) — the examiner's primary anticipation art; discloses the URL-list-plus-delay-times script that reads as claim 1's steps (a)–(c), and was distinguished only on "interactively variable duration."
2. Hauck, "Supporting Hierarchical Guided Tours in the World Wide Web" (1996) — the server-side, multi-path, guided-tour art most relevant to claim 37 (path-spanning/concurrent) and the RoboSites server-side embodiment.
3. U.S. 5,694,546 (Reisman, 12/1997) — the strongest single U.S. patent on the auto-deliver-and-display paradigm.
4. U.S. 5,740,549 (Reilly et al., 4/1998) — best match to the advertising/dynamic-content dependents (claims 28, 29, 35, 36).
5. U.S. 5,774,664 / 5,778,181 (Hidary et al., 6–7/1998) — automatic pushing of URL-addressable content to a browser.
6. U.S. 5,721,827 / 5,732,216 (Logan et al., 2–3/1998) — user-controlled concurrent delivery, mapping to claims 1, 32, 37.
7. Guinan et al. (ACM Hypertext, Nov. 1992) — dynamically planned guided tours; the most dangerous § 102(b) art in the IPR record, and yet institution was still denied.
8. U.S. 5,796,952 (Davis et al., 8/1998) — usage metering, i.e., the monitoring/feedback limitations.
9. U.S. 5,717,923 (Dedrick, 2/1998) and U.S. 5,848,396 (Gerace, 12/1998) — profiling/targeting limitations.

6. Explicit gaps and non-answers

• The U.S. reference list is incomplete in my sources. The '451 face-page reproduction I retrieved truncates mid-list (the last entry visible before the break is "6,08…", immediately after 6,038,367 A Abecassis). I therefore cannot state that the list I reproduce is the complete (56) list, and I have not verified whether any of 6,088,455 / 6,088,732 / 6,091,886 / 6,151,444 appear on the '451 face page — those numbers appear on the '932 continuation's face page and belong to its list, not necessarily to '451's.
• Filing dates for the cited references are unverified. Only the issue dates printed on the face page are reproduced here. Any § 102(e) conclusion requires pulling each reference's own filing date from the USPTO record.
• Descriptions marked ⚠ are unverified. I refused to invent subject matter for references whose text I did not retrieve. If you need element-by-element § 102 charts for those, they must be read from the reference documents themselves.
• No anticipation has been established. The BPAI reversed the examiner's rejections, and PTAB denied institution in IPR2023-00081, IPR2023-00590 and IPR2023-00591. The '451 patent was invalidated on § 101, not § 102 or § 103, by D. Del. on Feb. 21, 2025 (Robocast v. Netflix, 1:22-cv-00305), which is on appeal at the Federal Circuit as 25-1651. The prior-art question, in other words, was never adjudicated to a § 102 holding.
• 2026 status unverified, consistent with the prior section. I found no 2026 CAFC disposition in 25-1651 and no 2026 docket naming 7,155,451; I hit my search-step limit before exhausting this and I will not characterize it further.

Key sources: https://patents.google.com/patent/US7155451/en · https://portal.unifiedpatents.com/patents/patent/US-7155451-B1 · IPR2023-00081 Ex. 1001 (face page) — https://www.docketalarm.com/cases/PTAB/IPR2023-00081/Netflix_Inc/10-24-2022-Petitioner/Exhibit-1001-Ex_1001_451_US7155451/ · IPR2023-00590/00591 petitions — https://ptacts.uspto.gov/ptacts/public-informations/petitions/1553613 and https://ptacts.uspto.gov/ptacts/public-informations/petitions/1550476 · Robocast v. Microsoft / Robocast v. Apple claim construction order (D. Del., June 28, 2013) — https://www.ded.uscourts.gov/sites/ded/files/opinions/10-1055.pdf

I'll research the prior art actually at issue for this patent before analyzing § 103.

Let me pull the Google/YouTube IPR grounds and the Microsoft-case prior art.

Let me identify the Google IPR references and the remaining Netflix exhibits.

Scope note before the analysis

Two housekeeping points, then the analysis.

(1) No "Prior Art section" was actually supplied. The current task says to "use the results from the Prior Art section of this page," but no such section appears in the material provided to me — only the patent's full text (whose "Prior art keywords" field reads merely accordance / content / user / resources / displayed, which is a Google Patents search-facet artifact, not a reference list) and the two earlier generated sections. I have therefore built the prior-art inventory from the prior art of record that I could retrieve: the three PTAB petitions/decisions, the Robocast v. Apple and Robocast v. Microsoft opinions, and the references cited in the '451 specification itself. If a specific "Prior Art" list exists that you want used, paste it and I will re-run the mapping against it.

(2) Contradiction flagged against the earlier "Patent summary" section. That section listed four independent claims — 1, 22, 37, 39. The record shows that list is incomplete: the Robocast v. Apple opinion (39 F. Supp. 3d 552) and the Google IPR2023-00590 petition both treat claim 10 as an independent method claim ("A method for displaying in a sequential arrangement… by recording a sequence of said resources by dragging and dropping said icons"). Google's Ground 2 is expressly captioned "Independent Claim 10." So the independent-claim set for §103 purposes is at least 1, 10, 22, 37, 39. Treat the earlier list as superseded.

Obviousness analysis — US 7,155,451 under 35 U.S.C. § 103

1. Governing framework and the effective date problem

Pre-AIA § 103 applies (application filed Sept. 1, 1998, off a Sept. 2, 1997 CIP and a Sept. 3, 1996 provisional). The Graham factors apply: scope/content of prior art, differences from the claims, level of ordinary skill, secondary considerations.

Critical threshold point: the '451 issued from the 1998 CIP (09/144,906). If any claim element was added in the CIP (a live question — the ‑1996 provisional and the ‑1997 parent are the priority anchors for the "show structure" core, but the CIP plainly adds material), then for those claims the effective date is as late as Sept. 1, 1998, which pushes the § 102(b) bar back to Sept. 1, 1997 and makes 1996–97 "push" technology (Pointcast, Netcaster, Active Desktop) squarely available. Conversely, if all claims are supported by the Sept. 3, 1996 provisional, the § 102(b) bar is Sept. 3, 1995. Netflix/Google briefed this with a "Ground 1–3 (Escobar)" vs. "Ground 4–6 (Henley)" structure precisely because of these options. I cannot resolve the priority question from the record I have — it is the single biggest variable in any § 103 conclusion. Note also the unresolved bibliographic conflict already flagged in the earlier sections (Google Patents priority 1996‑09‑03 vs. Unified Patents 1996‑09‑02; filing 1998‑09‑01 vs. 1998‑08‑31).

Level of ordinary skill (POSITA): a bachelor's degree in CS/EE (or equivalent) with ~2 years' experience building networked document-retrieval/multimedia presentation software, familiar with HTTP/HTML, MIME, URL syntax, GUI authoring widgets, and timer-driven playback. Both sides' experts (Houh for Netflix; Schmandt for Google) proceeded on essentially this basis and used the Microsoft/Apple claim constructions from the June 28, 2013 D. Del. order (Ex. 1014), so those constructions should be the benchmark.

2. Prior-art inventory of record

(Caveat: I verified Shimizu/Benedict/Fox/Sagman/Filepp only at the level of how the Google grounds use them. I could not verify their full bibliographic identities, and my search budget was exhausted before I could pull their § 102 dates. Any assertion about their exact dates is unverified.)

3. Claim-by-claim obviousness mapping

Independent claim 1 — playlist of nodes; auto-access; auto-display; interactively variable duration

Grounds actually briefed: Escobar alone (§ 102/Ground 1 and § 103/Ground 2); Escobar + Rege (§ 103/Ground 3); Henley alone (Grounds 4–5); Henley + RFC1738 (Ground 6); Shimizu + Benedict + Fox (Google Ground 1).

Motivation to combine (Escobar + Rege): both are in the same field — authoring/delivering ordered multimedia over a network. Escobar's own disclosure identifies that its objects/assets live on different networked servers, which creates the need for "a mechanism (an address) to specify" the object's location; Rege teaches exactly that mechanism (packet-addressed content requests). This is the classic KSR "known technique addressing the same problem the primary reference identifies," reinforced by the uncontested fact that pointers and addresses were used interchangeably (Microsoft Press Computer Dictionary, 2d ed. 1994) and that URLs were ubiquitous background knowledge by 1996 (RFC 1738/1630). Netflix's rehearing request made precisely this KSR "common sense" point after the Board dismissed it as "only attorney argument."

Independent claim 10 — icon identification + drag-and-drop authoring of the sequence

Ground 2 of the Google petition: Shimizu + Benedict + Fox + Sagman. The motivation is unusually strong for § 103: drag-and-drop is a paradigm of the Windows 95-era GUI, and the '451 specification itself treats drag-and-drop as a known technique ("through the creation of a structure of nodes by a 'drag-and-drop' technique") — an applicant admission that the authoring mechanism was conventional. Once Shimizu/Benedict/Fox supply network-addressed content and an authorable ordered structure, substituting a familiar drag-and-drop front end for it is the "predictable variation" KSR makes obvious; the only asserted advantage (ease of authoring for non-technical users) is exactly the kind of market-pressure design incentive KSR credits.

Independent claim 22 — on-line search results auto-create the show structure

Apple's combination was Helfman + Braverman. Motivation: by 1995–96 search engines (Yahoo!, Excite, Lycos, AltaVista) already returned ranked lists of URL-addressed resources, and the '451 specification itself admits that "an example of such a server may be a search engine such as those available by YAHOO® or EXCITE®" and that show structures may "be prepared… based on a user's search specifications." That is an express admission that feeding search results into a topic structure was known. Braverman (CCI Slide Show, 1994) supplies the automatic timed sequential presentation of an ordered set — so the combination is the mechanical union of (a) a known result-list generator and (b) a known autoplay presenter. The result (results list → autoplaying sequence) is precisely the "predictable use of prior art elements according to their established functions" that KSR holds obvious, and the specification's own stated objective ("so that the amount of clicks and decisions are reduced") supplies the articulated reason.

Independent claim 37 — multidimensional structure; at least two nodes spanned concurrently; overlapping display period

This is the claim with the best single-reference obviousness case and the worst anticipation case.

• Zellweger (1989) is not merely analogous art — it is the same art (hypermedia path mechanisms) and expressly discloses parallel paths that "execute simultaneously" and "synchronize with activities on another branch." Combine Zellweger (concurrent/parallel and joinable paths) with Escobar or Henley (network retrieval + automatic display) and claim 37's "at least two of said nodes are spanned concurrently… displayed during an overlapping time period" reads on the combination almost verbatim. The D. Del. court itself treated the "parallel paths" passage as Apple's support for both disputed limitations.
• Escobar alone: the parties agreed Escobar teaches all limitations of claims 37/38 except “accessing two nodes at the same time” and “displaying content of at least two nodes during an overlapping time period.” The court then held that Escobar's "composite video" — combining text/graphics with decompressed video frames — "clearly refers to a graphics overlay." An overlay of a second content stream onto a first is overlapping display. So a § 103 (and arguably § 102) case under Escobar for claim 37 turns on a narrow, judge-resolved lexicography point, not on missing subject matter.

Motivation: Zellweger and the '451 are both hypermedia-path art; adding concurrency to a path mechanism is the stated purpose of Zellweger's parallel-path disclosure, not an after-the-fact rationalization.

Independent claim 39 — select a category from a predefined list, then run the search

Google's IPR2023-00591 attacked the search-based family (claims 22–32, 35, 36, 39–44). Motivation: category hierarchies were the organizing metaphor of the 1994–96 Web directory (Yahoo!'s directory was a predefined category list), and the '451 spec's own Figure 1/2 "Pick" and "Channel" features concede category-based selection. Bolt-on of a category pre-selection step to a search is, at most, an "obvious to try" ordering of known steps — KSR step 8 (a finite number of identified, predictable solutions). Pair with Helfman (or Henley/Escobar) for the automated retrieval/display core.

Dependent claims

• 2 / 23 / 38 (duration information): Escobar's timeline entries (per Ex. 1004, 11:37–60) and Braverman's per-slide timing.
• 24 (downloading a file from a server): Rege + RFC 1738; Henley.
• 25–29 (dynamic content, persistent content window, interspersed resource identifiers, advertising messages, per-profile): Filepp (Google Ground 3) for the persistent window/inserted ads; the '451 spec admits Firefly FGACF/Catalog Navigator as a commercially available personalization/collateral-filtering engine, and Pointcast as known push advertising delivery → obvious combination.
• 30–32 (storing/retrieving data files; reformatting to a predetermined arrangement; control buttons): Escobar's stored IDL entries; conventional GUI control sets (Braverman/Sagman).
• 35–36 (ads inserted between contents; ad selection by profile): Filepp + the admitted Pointcast/Firefly art.

4. Consolidated motivation-to-combine rationales (why a POSITA would have combined)

1. Same field / same problem: Escobar, Rege, Henley, Zellweger, Braverman, Shimizu all address presenting ordered multimedia/hypermedia content to a viewer — no field-of-endeavor barrier.
2. Explicit teaching/suggestion in the references: Zellweger teaches parallel/simultaneous paths; Rege teaches address-based requests; RFC 1738 defines URL addressing.
3. Predictable combination of known elements: search-result lists + timer-driven slide show; GUI drag-and-drop + ordered content list; graphics overlay + video.
4. Applicant-admitted motivation in the '451 specification: Pointcast/Netcaster/Active Desktop push delivery; "clicks… at a rate of approximately once per minute"; reducing "clicks and decisions"; Firefly filtering "commercially available"; Yahoo/Excite as show-structure servers. Admissions in the specification are usable as prior-art/motivation evidence.
5. Common sense / background knowledge (KSR): pointer≡address, URLs ubiquitous by 1996, drag-and-drop conventional.
6. Market forces: the advertising-supported "channel" model of 1996–97 (Pointcast, Netcaster) created a design incentive to package publisher content as an auto-advancing sequence.

5. Honest counterweights (why a § 103 holding is not a foregone conclusion)

• All three IPRs against the '451 were denied institution (IPR2023‑00081, ‑00590, ‑00591; the last two denied Sept. 18, 2023). On rehearing, the Board rejected Netflix's KSR argument and its "pointer = address" theory for limitation 1[a], and declined to read claim 37 as requiring simultaneous display. Whatever their precedential weight, those denials show a decisionmaker found the petition showings not even a reasonable likelihood — a real headwind for any § 103 theory at trial, especially on the "node→address" and "concurrently spanned" limitations.
• Escobar's "node" gap produced directly conflicting expert testimony in Robocast v. Apple ("whether a 'pointer' is an 'address[ ]'") — a factual dispute that defeated summary judgment of anticipation and would equally defeat summary judgment of obviousness on the same record.
• Zellweger enablement is a disputed fact (both Dr. Almeroth and Dr. Zellweger opined it was non-enabling), and the party bearing the burden on an anticipatory printed publication is unsettled law (the court presumed enablement but found a triable dispute).
• Helfman/Braverman were challenged as not prior art at all.
• Secondary considerations: Robocast's earlier campaigns against Apple and Microsoft settled, and it has contended the accused products copy the claimed functionality — settled licenses and copying evidence are classic objective indicia. Note, though, that settlements after the court noted "[t]he parties agree that Escobar discloses all limitations of claim 10 except for nodes" are weak commercial-success evidence.
• Most importantly, the claims have already fallen on other grounds: the D. Del. § 101 summary judgment of invalidity (Feb. 21, 2025, 1:22‑cv‑00305) held the claims abstract ("collecting, organizing, and automatically displaying content"), and that judgment is on appeal at the Federal Circuit, Robocast, Inc. v. Netflix, Inc., No. 25‑1651 (docketed Apr. 17, 2025). § 103 would regain practical significance only if the § 101 judgment is reversed. The inequitable-conduct theory (the Nov. 1999 "Torres Declaration"/"Hertzig Letter" in the ‑1997 parent's prosecution, and the resulting "infectious unenforceability" argument) is a parallel invalidity/enforceability theme, not a § 103 issue.

6. Bottom line and confidence

The strongest § 103 combinations, in descending confidence:

1. Zellweger + Escobar (or Henley) for claim 37 — same art, express parallel-path teaching, and agreed coverage of everything else.
2. Escobar + Rege (and/or RFC 1738/1630) for claims 1, 2, 24, 38 — the combination closest to anticipation; the only real gap is a claim-construction fight over "node"/"address."
3. Henley + RFC 1738 for claims 1–2, 37–38 — notable because Henley was used to reject and abandon the '451's own child applications, though it was withheld from '451 prosecution.
4. Shimizu + Benedict + Fox + Sagman for claims 10–12 (drag-and-drop authoring) and Shimizu + Benedict + Fox (+ Filepp) for claims 1–8, 13–20.
5. Helfman + Braverman for claim 22, and + a category-directory reference for claim 39 — the weakest links, since both references' prior-art status was contested and claim 22's search-to-structure step generated no clean single-reference mapping in the record I have.

Explicitly unverified: (i) the effective priority date of each claim (provisional 1996‑09‑03 vs. CIP 1998‑09‑01) — this is the pivotal assumption; (ii) full bibliographic details and § 102 dates for Shimizu, Benedict, Fox, Sagman, and Filepp; (iii) the content of claims 3–9, 13–21, 30–36, 40–64 beyond the limitation-by-limitation captions in the Google petition's table of contents; (iv) whether any additional independent claims exist; (v) the 2026 status of Fed. Cir. 25‑1651 (no 2026 disposition found in my prior searches).

Key sources: IPR2023‑00081 exhibit list and Houh declaration (https://www.docketalarm.com/cases/PTAB/IPR2023-00081/Netflix_Inc/); Netflix Sotera stipulation with grounds table (https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1550476](/patent/1550476)/); IPR2023‑00081 rehearing decision (https://www.docketalarm.com/cases/Delaware_District_Court/1--22-cv-00305/Robocast_Inc._v._Netflix_Inc/docs/151/9.pdf); Google IPR2023‑00590 petition and Schmandt declaration (https://www.docketalarm.com/cases/Delaware_District_Court/1--22-cv-00304/Robocast_Inc._v._Youtube_LLC._et_al/docs/124/); Robocast v. Apple, 39 F. Supp. 3d 552 (D. Del. 2014) (https://www.courtlistener.com/opinion/[7308169](/patent/7308169)/robocast-inc-v-apple-inc/); D. Del. Apple/MSJ opinion (https://www.ded.uscourts.gov/sites/ded/files/opinions/11-235_0.pdf); '451 full text (https://patents.google.com/patent/US7155451/en).