US 9998515

I'll research US 9998515 across the sources you specified.

Let me dig into the litigation/appeal history and any 2026 CAFC activity.

Let me look specifically for the full claim set of the '515 patent to identify all independent claims.

Summary of US Patent 9,998,515 B2

Caveat on method: I ran web searches rather than querying PatentCenter/CAFC docket databases directly. Bibliographic data below comes from the granted-patent front page as republished on Google Patents, corroborated by the PTAB final written decision in IPR2020‑00648 and the Federal Circuit opinion in Netflix, Inc. v. DivX, LLC, Nos. 2022‑1203, ‑1204. Where sources conflict, I flag it rather than resolve it silently.

Bibliographic data

Priority chain (as recited in the patent's Cross Reference section): provisional App. Ser. No. 61/529,403 (Braness et al., "Automatic Generation of SMIL Files", filed Aug. 31, 2011) → App. 13/341,789 (filed Dec. 30, 2011, now US 8,787,570) → App. 14/336,392 (filed Jul. 21, 2014, now US 9,270,720) → App. 15/009,593 (now US 9,998,515). The '720 and '515 patents share a nearly identical specification; the '515 is a continuation in that chain. Note Google Patents states the prior-art date as 2011‑08‑31, while the Unified Patents portal lists 2011‑08‑30 — I use Aug. 31, 2011, consistent with the provisional's stated filing date.

Assignment history (per Google Patents reassignment records): inventors → DivX, LLC (Aug. 9, 2016); DivX, LLC → Sonic IP, Inc. (Aug. 9, 2016); DivX, LLC/Sonic IP, Inc. → DivX CF Holdings LLC (Feb. 13, 2018); change of name back to DivX, LLC (Mar. 5, 2018).

Abstract (verbatim)

"Systems and methods for automatically generating top level index files for use in adaptive bitrate streaming in accordance with embodiments of the invention are disclosed. One embodiment of the method of the invention includes receiving a request from a playback device at a playback server, where the request identifies a piece of content, retrieving a list of assets associated with the identified piece of content using the playback server, filtering the list of assets using at least one predetermined criterion using the playback server, generating a top level index file describing each asset in the filtered list of assets using the playback server, and sending the top level index file to the playback device using the playback server."

Independent claims — plain-language overview

Claim 1 (independent; method — "A method for authorizing playback of content"). Verbatim text as quoted by the Federal Circuit in the 2023 appeal:

1. A method for authorizing playback of content, comprising:
   receiving a request for content from a playback device at a playback server, where the request includes a product identifier that identifies a device configuration;
   identifying, using the playback server, based on the product identifier, a plurality of device capabilities including a device type and a device software version indicating a version number for an adaptive streaming software component implemented on the playback device;
   retrieving, using the playback server, a list of assets associated with the identified piece of content, wherein each asset is a different stream associated with the piece of content;
   filtering, using the playback server, the list of assets based on the plurality of device capabilities;
   generating, using the playback server, a top level index file describing each asset in the filtered list of assets, wherein the top level index file identifies locations and bitrates of a plurality of alternative streams capable of being used to perform adaptive streaming of the content; and
   sending the top level index file from the playback server to the playback device.

Plain language: a server tailors the playback manifest to the requesting device. The device sends a content request carrying a product ID; the server looks up what that product ID means (device type and, notably, the version number of the device's adaptive-streaming software); pulls the catalog of streams "assets" for that title; discards the ones the device cannot/should not use; writes a top-level index file listing the surviving streams with their locations and bitrates; and returns it to the device.

Claim 1 therefore requires (a) server-side, request-time generation of a device-specific index, (b) filtering keyed to a product identifier, and (c) the product identifier resolving to device capabilities that expressly include the device software version of the adaptive streaming component.

Other independent claims — not fully confirmed. The '515 patent contains additional independent claims. The patent's Summary section describes at least two further claim categories: (i) a system claim reciting "a database that stores descriptions of assets associated with specific pieces of content, and a processor configured using a playback management application" that receives the request, retrieves, filters, generates and sends the index (and optionally retrieves/provides cryptographic information); and (ii) a machine-readable medium claim whose instructions cause a processor to perform the receiving/retrieving/filtering/generating/sending process. The IPR petition in IPR2020‑00648 challenged claims 1–6, 8–10, 13, 14, 16, 17 and 19, which confirms the patent has at least 19 claims. I could not retrieve the authoritative per‑claim text of those additional independent claims from the sources available to me, so I cannot state their exact claim numbers or wording with confidence. Treat the paragraph above as an indication of claim scope drawn from the specification's summary, not as verified claim language.

Related litigation / PTAB / CAFC status (relevant to your docket question)

• District court (C.D. Cal.): DivX, LLC v. Netflix, Inc., No. 2:19‑cv‑01602, and DivX, LLC v. Hulu, LLC, No. 2:19‑cv‑01606 — both listed on the Google Patents family page and identified as co‑pending matters in the IPR.
• PTAB: Netflix, Inc. v. DivX, LLC, IPR2020‑00648 (filed Mar. 11, 2020; instituted Oct. 1, 2020; final written decision Sept. 27, 2021). Grounds: §103 over Pyle + Marusi and Lewis + Marusi. Result: Netflix did not carry its burden on the challenged '515 claims. Real parties in interest: Netflix, Inc. and Hulu, LLC; patent owner DivX, LLC and DivX CF Investors LLC. A parallel petition, IPR2020‑00647 (Hulu), addressed the '720 patent. URLs: https://portal.unifiedpatents.com/ptab/case/IPR2020-00648 and https://lowensteinweatherwax.com/wp-content/uploads/2021/09/2021-09-27-IPR2020-00648-Final-Written-Decision.pdf
• First CAFC appeal: Netflix, Inc. v. DivX, LLC, Nos. 2022‑1203, 2022‑1204 (Fed. Cir. Oct. 25, 2023) (Chen, J., joined by Linn, J.; Dyk, J., dissenting). Opinion at https://cafc.uscourts.gov/opinions-orders/22-1203.OPINION.10-25-2023_2211191.pdf. Affirmed. Netflix raised only a procedural challenge (that the Board ignored arguments in its petitions); the court held the arguments were not presented below and were forfeited, so "we affirm." These two docket numbers correspond to the two IPR decisions ('720 and '515); I did not verify which number maps to which patent.
• 2026 CAFC dockets — nothing found for 9,998,515. I searched for 2026 Federal Circuit activity tied to this patent number and found none. The 2026 Federal Circuit DivX‑related decision is Netflix, Inc. v. DivX, LLC, No. 24‑1541 (Fed. Cir. Feb. 13, 2026) — but that case concerns U.S. Patent 10,225,588 (the '588 patent), a different patent, dealing with partial‑frame encryption and common keys. That opinion merely mentions "top level index file" as claim language of the '588 patent. Per your instruction not to auto‑correct or blend identifiers: I am expressly not attributing the 2026 decision to 9,998,515. URL: https://www.cafc.uscourts.gov/opinions-orders/24-1541.OPINION.2-13-2026_2647816.pdf
• Other DivX‑family activity I saw but that does not involve 9,998,515: DivX, LLC v. Unified Patents, LLC, No. 2023‑1699 (Fed. Cir. June 24, 2025) (affirming invalidity of US 10,326,987); and EPO Enlarged Board R 0016/25 (decision of July 6, 2026) concerning EP 3,467,666 ("Video distribution system including progressive playback"), with Netflix International B.V. and Amazon EU S.à.r.l. as opponents.

Continuation family (for completeness)

Google Patents/related-family listings tie US 9,998,515 to later continuations including US 10,154,075 (App. 15/658,057), US 10,542,061 (App. 16/207,405), US 11,115,450 (App. 16/703,668), US 11,716,371 (App. 17/467,027), US 2023/0370515 A1 (App. 18/359,831) and US 2025/0168216 A1 (App. 19/030,326).

Points of uncertainty

1. Exact numbering and text of the independent system and machine-readable-medium claims of the '515 patent (see above).
2. Which of CAFC Nos. 22‑1203 / 22‑1204 corresponds to the '515 patent's IPR versus the '720 patent's IPR.
3. Issue date/grant date: patent text says June 12, 2018; Unified Patents says June 11, 2018.
4. Priority date: Aug. 31, 2011 (patent text, Google Patents) vs. Aug. 30, 2011 (Unified Patents).

Primary sources: https://patents.google.com/patent/US9998515/en; https://portal.unifiedpatents.com/patents/patent/US-9998515-B2; https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2020-00648; https://caselaw.findlaw.com/court/us-federal-circuit/115356106.html.

I'll research litigation involving US patent 9998515. Let me search multiple sources.

Let me dig deeper into specific cases and outcomes.

Let me verify additional cases and the IPR/appeal details.

Litigation involving U.S. Patent No. 9,998,515 ("9998515")

Identifier note (important): The patent you asked about is US 9998515 B2, which is cited in court and PTAB documents as U.S. Patent No. 9,998,515 (the same seven-digit number with commas). Every source below refers to this patent. I have excluded search hits that turned out to be different numbers (e.g., U.S. Pat. No. 9,994,851, which appears in unrelated Nippon Shinyaku v. Sarepta litigation). The '515 patent is titled "Systems and methods for automatically generating top level index files," was filed as application 15/009,593, granted 2018-06-12, and is owned by DivX, LLC.

The '515 patent has been the subject of two parallel district-court actions, one PTAB inter partes review, and Federal Circuit appeals. Details follow.

1. DivX, LLC v. Netflix, Inc. — C.D. Cal.

Source: Final Judgment, Dkt. 1197 — https://law.justia.com/cases/federal/district-courts/california/cacdce/2:2019cv01602/[738825/1197](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=738825-1197)/ ; docket — https://www.courtlistener.com/docket/14611853/divx-llc-v-netflix-inc/ ; WilmerHale (Netflix defense verdict) — https://www.wilmerhale.com/en/insights/news/20260408-wilmerhale-secures-complete-defense-verdict-for-netflix-in-patent-infringement-trial

Note that the four patents that actually went to the March 2026 jury (7,295,673; 8,139,651; 8,472,792; 10,212,486) do not include the '515 patent. The '515 patent was instead disposed of earlier by the § 101 summary-judgment ruling.

2. DivX, LLC v. Hulu, LLC — C.D. Cal.

Sources: Joint Stipulation & Order — https://www.courtlistener.com/docket/14613534/divx-llc-v-hulu-llc/?entry_gte=156 ; stay order minutes (Dkt. 122) — https://www.courtlistener.com/docket/14613534/divx-llc-v-hulu-llc/

3. Netflix, Inc. et al. v. DivX, LLC — PTAB IPR2020-00648

Source: https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2020-00648

4. Federal Circuit appeals — Nos. 2022-1203 and 2022-1204 (Netflix, Inc. v. DivX, LLC)

Sources: CAFC opinion (22-1203, 10/25/2023) — https://cafc.uscourts.gov/opinions-orders/22-1203.OPINION.10-25-2023_2211191.pdf ; Unified Patents CAFC case links (22-1203 and 22-1204) listed on the patent page — https://portal.unifiedpatents.com/patents/patent/US-9998515-B2

Summary of outcomes

• All district-court infringement assertions of the '515 patent have ended: the Hulu case settled/dismissed (2022); the Netflix case was resolved in Netflix's favor, with claim 1 of the '515 patent invalidated under § 101 and final judgment entered May 7, 2026.
• Netflix's validity challenge in the PTAB failed — the Board upheld the '515 patent in IPR2020-00648, and the Federal Circuit affirmed on October 25, 2023. (The § 101 invalidation came later and on a different ground in the district court.)
• The Google Patents page for this patent also notes a worldwide litigation family (Darts-IP family 47743756), the IPR2020-00648 PTAB matter, and the two CAFC appeals — https://patents.google.com/patent/US9998515/en

Caveats / items I could NOT confirm

• I could not confirm that the '515 patent was asserted in DivX's separate action against Amazon.com (that case involved U.S. Pat. Nos. 9,270,720-adjacent families, e.g., the '806, '303, and '938 patents), nor in DivX's ITC action (which concerned the '486 patent). I therefore do not list those as '515 litigation.
• A DivX-vs-Netflix injunction in Brazil appeared in a secondary (Portuguese-language) source, but I could not verify that it involved the '515 patent specifically, so I have not attributed it to this patent.
• Docket data from CourtListener/UniCourt is sourced from PACER/RECAP and may lag; some fee/counsel details may change. The dates above are taken from the cited primary documents where available.

If you need PACER-certified docket sheets or the PTAB Final Written Decision text for IPR2020-00648, those can be pulled directly from PACER and the USPTO PTAB portal.

I'll research the PTAB proceeding flagged in the patent's litigation block.

PTAB Proceedings — US 9,998,515 ("Systems and methods for automatically generating top level index files")

Note on sourcing discrepancy (flagged as required): The structured "PTAB proceedings on file" block states the USPTO ODP API returns no AIA trial proceedings. That is stale/incomplete. The patent's own Google Patents litigation block (fetched 2026-09-22) flags a PTAB proceeding — IPR2020-00648 (Final Written Decision) — plus two CAFC appeals, and the underlying FWD, the Board's papers, and the Federal Circuit opinion are all public. There is exactly one AIA trial on the '515 patent that I can verify. I did not invent any proceeding numbers; everything below is tied to a public document.

Proceedings overview

Total AIA trials on US 9,998,515: 1 — a single Inter Partes Review (IPR2020-00648), not settled, instituted in full, claims partially invalidated (3 of 15 challenged claims canceled), appealed and affirmed, now terminated. Breakdown: active — 0; claims invalidated — 1 proceeding (claims 16, 17, 19); claims sustained — same proceeding (claims 1–6, 8–10, 13, 14); settled — 0; institution denied — 0.

Defensive posture: This is not a "troll has no case" patent and not a clean "hardened" patent — it is a narrowed but battle-tested one. Claim 1 (the method claim Netflix/Hulu most wanted dead) survived the IPR and survived Federal Circuit review, so any § 103 attack built on Pyle+Marusi or Lewis+Marusi is foreclosed. But independent claim 16 and its dependents 17 and 19 are canceled, so any infringement chart that maps to the device-side claim 16 is worth nothing.

IPR2020-00648 — Netflix, Inc. (real party in interest: Hulu, LLC) v. DivX, LLC

Caption note: the Board's FWD and the district court papers refer to this case both as "Netflix, Inc. v. DivX, LLC, IPR2020-00648" and, in places, under the Hulu name. The FWD confirms the petitioner identified Netflix, Inc. and Hulu, LLC as real parties in interest, and DivX, LLC and DivX CF Investors LLC as patent-owner RPIs. The companion '720-patent IPR (IPR2020-00647) is captioned Hulu, LLC v. DivX, LLC — same panel, same petitioner group, decided the same day.

• Type: Inter Partes Review (IPR), 35 U.S.C. §§ 311–319, pre-AIA § 103(a) applied (effective filing date before 2013-03-16).
• Filed: 2020-03-11 (Paper 3, Petition, 85 pp.).
• Status: Final Written Decision issued 2021-09-27 (Paper 28); appealed; affirmed 2023-10-25; terminated. Verbatim disposition from the FWD: "claims 16, 17, and 19 of U.S. Patent No. 9,998,515 B2 are determined to be unpatentable" and "claims 1–6, 8–10, 13, and 14 of U.S. Patent No. 9,998,515 B2 are not determined to be unpatentable."
• Judge panel: Administrative Patent Judges Bart A. Gerstenblith (opinion author), Monica S. Ullagaddi, and Iftikhar Ahmed.
• Petition grounds (all challenges under 35 U.S.C. § 103(a), pre-AIA):
  • Ground 1 — claims 1, 4, 5, 8–10, 14, 16, 17, 19 obvious over Pyle (U.S. Pat. No. 8,782,268 B2) in view of Marusi (EP 2180664 A1).
  • Ground 2 — claims 1–6, 8–10, 13 obvious over Lewis (U.S. Pat. App. Pub. 2012/0047542 A1) in view of Marusi.
  • No § 112 or § 101 grounds were tried. Petitioner's expert: Clifford Reader, Ph.D. (Ex. 1003). Patent Owner's expert: Kenneth A. Zeger, Ph.D. (Ex. 2016).
• Institution decision: Instituted 2020-10-01 on all challenged claims (1–6, 8–10, 13, 14, 16, 17, 19), on both grounds as presented. No claims were dropped at institution. The Board credited Petitioner's position that Pyle's "new manifest" teaching was supported by the '515 specification and Dr. Reader's testimony ("On this record, Petitioner's position is reasonable and supported by the '720 patent and Dr. Reader's testimony.").
• Final Written Decision (2021-09-27) — claim-level verdict:

• Canceled: independent claim 16 (the playback-device claim) and its dependents claims 17 and 19. Per Petitioner's own oral argument, claims 16/17/19 rose or fell on a single limitation — the "software version indicating a version number for an adaptive streaming software component" element of the '515 device claim.
• Sustained: independent claim 1 and dependent claims 2–6, 8–10, 13, and 14 (claim 14 — "generating an XML string including a URI for each asset" — was challenged only in Ground 1 and was not shown unpatentable).
• Panel reasoning, in brief: On the Pyle ground, the Board found a "disconnect" in Petitioner's theory: Netflix used Pyle's selection of a pre-existing manifest to satisfy the "filtering" limitation, but used Pyle's creation of a new, unrelated manifest to satisfy "generating… a top level index file describing each asset in the filtered list" — so the new manifest could not describe the assets produced by the filtering step. On the Lewis ground, the Board held that Lewis's generation of a dynamic manifest file containing a list of URLs "cannot, without further explanation, render obvious an intermediate prior step of 'retrieving.'" Those two failures are why claim 1 survived.
• Settlement / termination: None. This proceeding ran to a merits FWD; there was no adverse judgment, no termination on settlement, and no confidential settlement terms to report. (DivX did win a separate, unrelated IPR against Unified Patents on U.S. 8,139,651 — that is a different patent and is not a proceeding on the '515 patent.)
• Appeal: Yes. Netflix appealed both the '720 FWD (IPR2020-00647, CAFC 22-1203) and the '515 FWD (IPR2020-00648, CAFC 22-1204), appeal filed 2021-11-24. The court issued a precedential opinion on 2023-10-25 in Netflix, Inc. v. DivX, LLC, No. 22-1203 (consolidated with 22-1204), affirming both FWDs. Key holdings:
  • Netflix's appeal was purely procedural — it "does not challenge any of the Board's substantive analysis" and argued only that the Board failed to address arguments actually made in the petitions.
  • The majority: "the Board should also not have to decode a petition to locate additional arguments beyond the ones clearly made… it is the petitioner's burden to present a clear argument." It found no error and held the remaining arguments forfeited because they were not raised below.
  • Judge Dyk dissented in part, concluding the Board improperly ignored two arguments that were properly preserved (the "filtering" limitation of the '720 patent and the "retrieving" limitation of both patents): "In my view, the Board was required to address the merits of these arguments."
  • I found no indication of a rehearing petition, en banc poll, or cert petition; I could not confirm one way or the other, and I flag that as unverified rather than asserting it did not happen. The FWD invalidation of claims 16, 17, and 19 does not appear to have been cross-appealed by DivX — the 2023 opinion addresses only Netflix's issues, which suggests those three claims are finally canceled (a certificate of cancellation follows affirmance). Treat this last point as a strong inference, not a document I read.
• Defensive value: Split decision, and the split matters. If a demand letter or complaint cites claim 16 (or 17/19) — the playback-device claim — the asserted claim has been canceled; any theory built on it is dead on arrival. If the assertion is built on claim 1 (or 2–6, 8–10, 13, 14), the patent has already withstood a full IPR and a Federal Circuit affirmance, so the "we'll just IPR it" defense is much weaker — and Netflix/Hulu's two art combinations (Pyle+Marusi, Lewis+Marusi) are now estopped as to those claims.

Strategic summary

Claim status. Of the '515 claims that were put at issue, the patent came out narrowed at the device-claim edge and intact at the core. Canceled (finally unpatentable): claims 16, 17, 19. Sustained through FWD and affirmance: claims 1, 2, 3, 4, 5, 6, 8, 9, 10, 13, 14. Never tested in any AIA trial: claims 7, 11, 12, 15, and 18 (no petition challenged them), plus any claims numbered 20 or higher — I did not verify the patent's total claim count, so do not assume there are none. The practical read: the method-side independent claim 1 is the asset DivX still owns; the apparatus-side independent claim 16 is gone.

Estoppel landscape. Under 35 U.S.C. § 315(e)(2), Netflix and Hulu — as petitioners/RPIs, and their privies — are estopped in the co-pending civil actions (and any future ones) from asserting, against claims 1–6, 8–10, 13, and 14, any ground they raised or reasonably could have raised in IPR2020-00648. That means Pyle, Marusi, and Lewis in those combinations are off the table for them, and arguably any other art a skilled searcher could have found before the March 2020 petition. For a new defendant the estoppel does not run, but the practical space is thin: a fresh IPR on the surviving claims needs materially different prior art, and the Board will weigh § 325(d) (same or substantially the same art previously presented) and General Plastic-style follow-on-petition factors against a second bite. The most promising attack surface on the surviving claims is not the "filtering"/"retrieving" limitations (Netflix lost twice there) but the claim 1 element the Board treated as dispositive at the margins: "a device software version indicating a version number for an adaptive streaming software component implemented on the playback device."

Pattern signals. The petitioner group is an operating-company coalition (Netflix + Hulu) defending themselves in DivX's C.D. Cal. campaigns (2:19-cv-01602 and 2:19-cv-01606; later Hulu I, 2:21-cv-01615), not a defensive aggregator like Unified Patents — Unified's DivX activity was confined to other patents (e.g., U.S. 8,139,651). Netflix/Hulu ran a coordinated multi-patent IPR campaign against DivX and appealed at least six FWDs; they lost the substantive fights on the '515 and '720 patents and lost a purely procedural appeal in a precedential decision that now cuts against sloppy petitions. DivX, for its part, litigates aggressively on both sides — it appeals FWDs it loses and defends FWDs it wins. Net pattern signal: this patent family has been thoroughly stress-tested and its surviving claims are proven survivors — but the invalidation of claim 16 shows the device claims were the weak flank.

Recommended next steps

• If you are a defendant and the assertion rests on claim 16, 17, or 19: say so immediately and precisely. Those claims were determined unpatentable in the FWD and the determination was affirmed. The disposition language to quote is: "ORDERED that claims 16, 17, and 19 of U.S. Patent No. 9,998,515 B2 ('the '515 patent') are determined to be unpatentable." Links: FWD — https://lowensteinweatherwax.com/wp-content/uploads/2021/09/2021-09-27-IPR2020-00648-Final-Written-Decision.pdf (originating from PTAB E2E / PTAB Decisions, https://ptacts.uspto.gov/ptacts/ and https://portal.unifiedpatents.com/ptab/case/IPR2020-00648); Federal Circuit affirmance — https://cafc.uscourts.gov/opinions-orders/22-1203.OPINION.10-25-2023_2211191.pdf and https://www.courtlistener.com/opinion/[9435057](/patent/9435057)/netflix-inc-v-divx-llc/. A plaintiff that keeps citing a canceled claim after being shown the FWD is on shaky ground, but note that pre-suit cancellation matters more than post-suit: if the claim was still live when the complaint was filed, this is a merits/defense point rather than sanction-bait.
• If the assertion rests on claim 1 (or 2–6, 8–10, 13, 14): there is no active PTAB proceeding to ride. The trial is over and the outcome on those claims was adverse to the petitioner. Frame your invalidity case on new art — not Pyle, Marusi, or Lewis — and expect a § 325(d) fight. Consider that the Board and the CAFC both focused on whether the prior art server actually retrieves a list of assets and then filters it before generating the index; a reference that expressly performs that ordered pipeline is worth more than a reference that merely produces a manifest.
• No live trial-stage milestones to track. There is no pending IPR on the '515 patent, no institution-deadline clock, no oral hearing, and no statutory 1-year FWD due date. The only calendar items are follow-on: confirm the certificate of cancellation for claims 16, 17, 19 issued after the 2023-10-25 mandate, and check the dockets in DivX, LLC v. Netflix, Inc., No. 2:19-cv-01602 (C.D. Cal.) and the Hulu actions for how the '515 claims were narrowed in the infringement contentions post-affirmance.
• Two verification gaps I am not filling with guesses: (1) whether DivX filed a cross-appeal or rehearing petition on the claim 16/17/19 invalidation, and (2) whether any second IPR on the '515 patent was filed by a different petitioner after this one. I found no evidence of either, but I could not confirm their absence from a primary docket — verify both on PTAB E2E before relying on the "closed" characterization.

I'll reconstruct this ownership chain from the authoritative patent text provided, then verify and enrich with live sources.

Excellent — the Netflix MSJ excerpt (Dkt. 797-1) and the litigation record give me the entity history. Let me pin down the recorded reel/frame numbers and correspondents.

US 9998515 B2 — Ownership Reconstruction

Patent: US 9,998,515 B2 ("Systems and methods for automatically generating top level index files") · App. 15/009,593 · filed 2016-01-28 · issued 2018-06-12 · priority 2011-08-31 (Prov. 61/529,403).

Source caveat up front. Google Patents' legal-events tab gives me the dates and parties of the recorded transfers (https://patents.google.com/patent/US9998515/en), but it does not render the reel/frame or correspondent for this patent. The reel/frames I cite below come from the prosecution-file history of a sibling DivX-family application (15/453,714) introduced as Ex. 1002 in Unified Patents LLC v. DivX, IPR2021-01476 — DivX recorded these transfers as bulk assignments, so the reels very likely cover '515 as well, but I have not independently verified the '515-specific reel/frame or the correspondent of record. Both should be confirmed in Assignment Center before filing anything.

Inventors

Patterns noted:

• The inventor→company assignment was not recorded until 2016-08-09 — roughly five years after the 2011-08-31 priority filing, and on the same day as the corporate DivX, LLC → Sonic IP, Inc. transfer. A long-delayed inventor assignment batched with a corporate transfer is a classic signature of an estate being packaged for sale; here it preceded the Feb-2018 Fortress purchase.
• I have no evidence regarding inventor departures within 12 months of filing. I will not infer a fire-sale from that; the departure question is unresolved on the record I can access.

Original assignee

DivX, LLC — the entity named as original assignee on the issued face and the entity that filed the 2016-01-28 continuation ("Application filed by DivX LLC").

• Primary business: consumer video technology — the DivX codec and the DivX Plus Streaming adaptive-bitrate/DRM platform. In DivX's own 2020 submission to the USPTO (PTO‑P‑2020‑0022‑0783) the company states its tech was "licensed … into more than 1.5 billion devices worldwide" and describes Stage6 and its internet-video/DRM work. So the original assignee was a genuine operating/licensing-technology company, not a paper entity.
• Status — the name is a trap. The original DivX, LLC did not survive. Per Netflix's motion-in-limine brief in DivX, LLC v. Netflix, Inc., No. 2:19-cv-01602 (C.D. Cal.), Dkt. 797-1:
  • Feb 13, 2018 — the old DivX, LLC renamed itself NLD, LLC;
  • Dec 15, 2017 — Fortress Investment Group created DivX CF Holdings LLC as a "to be formed entity" to buy the patents;
  • Feb 2018 — Fortress's new entity bought the portfolio from NeuLion's subsidiary and then renamed itself "DivX, LLC."
  • The resulting plaintiff "has no engineering department, employs only one engineer, is led by an attorney, and engages in litigation and patent licensing as its primary business"; it is a "pass‑through entity" whose revenue flows to DivX CF Investors LLC (97%), whose members are all Fortress entities.
• Bottom line: the named original assignee's business (video codec/streaming) is real; the current holder of the same name is a Fortress-controlled licensing vehicle. The original corporate entity now exists as NLD, LLC.

Assignment timeline

Chronological recorded events (Google Patents legal events; reel/frame flagged as sourced from the sibling-file exhibit):

• 2016-08-09 (recorded) — Reel 042819/0890 (from IPR2021-01476 Ex. 1002; not verified for '515 specifically)

  • Conveyance: Assignment (of assignors' interest)
  • Assignor: DivX, LLC
  • Assignee: Sonic IP, Inc.
  • Correspondent: unknown from available sources — verify in Assignment Center. Flag: this is the first of two recordings handled as a batch; if the same attorney/firm reappears across the 2016 and 2018 links, that is the recurrence to watch.
  • Context: internal reorg — consolidation of the DivX patent estate into Sonic IP, Inc., the NeuLion-family patent-holding subsidiary.

• 2016-08-09 (recorded) — Reel/frame not shown by Google (likely within the same bulk filing)

  • Conveyance: Assignment (original inventor assignment)
  • Assignor: Braness, Jason; Wallin, Evan; Ferreira, Ederson
  • Assignee: DivX, LLC
  • Correspondent: unknown.
  • Context: original assignment, recorded late — batched with the DivX→Sonic IP transfer five years after the 2011 priority filing.

• 2018-02-13 (recorded; agreement executed ~2018-02-16) — Reel 045310/0020 (from IPR2021-01476 Ex. 1002)

  • Conveyance: Assignment
  • Assignors: DivX, LLC (old) and Sonic IP, Inc.
  • Assignee: DivX CF Holdings LLC (Fortress-created entity)
  • Correspondent: unknown from available sources.
  • Context: transfer-to-asserter / portfolio purchase — Fortress buys the DivX patent estate out of NeuLion; this is the pivotal event that converts the portfolio into an assertion vehicle.

• 2018-03-05 (recorded) — Reel/frame not shown

  • Conveyance: Change of Name
  • Assignor: DivX CF Holdings LLC
  • Assignee: DivX, LLC
  • Correspondent: unknown.
  • Context: change of name only — the Fortress shell adopts the historic "DivX, LLC" name (same legal entity; no change of ownership).

• 2019-02-28 (recorded)

  • Conveyance: Change of Principal Place of Business
  • Assignee: DivX, LLC (no change of title)
  • Context: administrative.

Post-transfer enforcement events (sourced from the litigation record, not Assignment Center):

• 2019-03-05 — DivX, LLC v. Netflix, Inc. (2:19-cv-01602) and DivX, LLC v. Hulu, LLC (2:19-cv-01606) filed in C.D. Cal.; '515 added to the Netflix case on 3/5/2019 (AO-120 form).
• 2020-03-11 — Netflix/Hulu petition for IPR of '515 → IPR2020-00648; FWD 2021-09-27 (claim 1 upheld; claim 16 unpatentable).
• 2023-10-25 — Fed. Cir. 22-1203 / 22-1204 (Netflix, Inc. v. DivX, LLC).
• 2026-03-25 — jury verdict and final judgment: no infringement of the four tried patents; claims of '720 and claim 1 of '515 held invalid under §101.

Timeline diagram

timeline
    title Ownership of US 9998515
    2011 : Provisional filed by DivX
    2014 : Continuation filed
    2016 : Continuation application filed
         : Inventors assign to DivX LLC
         : DivX LLC transfers to Sonic IP Inc
    2017 : Fortress forms DivX CF Holdings LLC
    2018 : Sonic IP and DivX assign to DivX CF Holdings
         : DivX CF Holdings renamed DivX LLC
    2019 : DivX sues Netflix and Hulu
    2020 : Netflix and Hulu file IPR
    2026 : Jury finds no infringement

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
Reel 045310/0020 (rec. 2018-02-13) moves the patent from the operating DivX estate into DivX CF Holdings LLC, an entity created by Fortress on 2017-12-15 expressly to hold the purchased patents and then renamed "DivX, LLC." Netflix's brief (Dkt. 797-1) documents: no engineering department, one engineer, attorney-led, litigation/licensing as primary business, 97% owned by DivX CF Investors LLC, whose members are all Fortress entities. This is not "naming alone" — it is a court-filing-backed, single-purpose acquisition vehicle.

2. Known asserter in the chain — NOT PRESENT (as to the named lists).
Neither DivX, LLC, Sonic IP, Inc., NeuLion, nor DivX CF Holdings LLC appears on the classic directories (Acacia, Marathon, IV, Wi‑LAN/Conversant, Vringo, Round Rock, etc.). However the entity functions as a high-frequency assertor (multiple suits against Netflix/Hulu). I flag this as functionally equivalent to an NPE but literally off-list — do not cite it as a directory match.

3. Repeat correspondent across the chain — UNKNOWN.
I could not obtain the correspondent of record for any '515 link from the sources available to me. Because the 2016 and 2018 recordings were processed as bulk assignments (single reel/frame per batch: 042819/0890 and 045310/0020), the same recording attorney almost certainly handled each batch — but I will not name one without the Assignment Center record. Action item: pull reel 042819/0890 and 045310/0020 in Assignment Center and compare the correspondent field; a recurrence there would upgrade this to a finding.

4. Cascading transfers — PRESENT.
Three recorded link-changes inside ~18 months (2016-08-09 DivX→Sonic IP; 2018-02-13 DivX+Sonic IP→DivX CF Holdings; 2018-03-05 name change), immediately followed by the change-of-principal-place-of-business (2019-02-28). All pre-litigation.

5. Pre-litigation transfer — NOT PRESENT on timing (but intent is clear).
The acquisition was recorded 2018-02-13; the first suits naming '515 were filed 2019-03-05 — a gap of ~13 months, outside the 6-month window. So the timing criterion fails, but the 2018 purchase plainly arranged the estate for assertion.

6. Bankruptcy fire-sale — NOT PRESENT.
The Feb-2018 transfer was a negotiated portfolio sale from NeuLion's subsidiary to a Fortress vehicle, not a Chapter 7/11 sale.

7. Privateering — NOT PRESENT.
Classic privateering requires the operating company (or a proxy) to assert on the seller's behalf. Here NeuLion divested the patents outright; Fortress asserts for its own account against third parties. This is a straight portfolio buy-out, not privateering.

8. Defensive aggregator — NOT PRESENT.
The chain terminates at the Fortress-controlled DivX, LLC, which asserts offensively (Netflix, Hulu). No RPX/AST/LOT/Unified/OIN terminus.

Verdict

NPE — high confidence.

Two or more strong signals are met and are backed by a federal-court filing rather than naming inference: (a) shell-entity transfer — reel 045310/0020 (rec. 2018-02-13) conveys the patent from the operating DivX estate to DivX CF Holdings LLC, a Fortress single-purpose vehicle formed 2017-12-15 and renamed "DivX, LLC," documented in Dkt. 797-1 as having no engineering department, one engineer, an attorney CEO and licensing/litigation as its primary business; and (b) cascading transfers — three recorded link-changes (2016‑08‑09, 2018‑02‑13, 2018‑03‑05) reframed the estate for assertion, culminating in the 2019-03-05 Netflix/Hulu suits. The only missing pieces are the correspondent of record and the '515-specific reel numbers, both of which should be confirmed before this memo is relied upon.

Verify at: https://assignmentcenter.uspto.gov/ (search by patent number 9998515) and the legacy index at https://assignment.uspto.gov/patent/index.html — pull reels 042819/0890 and 045310/0020 and capture the correspondent field on each.

Key sources

• Google Patents legal events — https://patents.google.com/patent/US9998515/en
• DivX, LLC v. Netflix, Inc., 2:19-cv-01602 (C.D. Cal.) — Netflix MIL brief Dkt. 797-1 (entity history, Fortress control) — https://archive.org/download/gov.uscourts.cacd.[738825](/patent/738825)/gov.uscourts.cacd.738825.797.1.pdf
• IPR2020-00648 Final Written Decision (2021-09-27) — https://lowensteinweatherwax.com/wp-content/uploads/2021/09/2021-09-27-IPR2020-00648-Final-Written-Decision.pdf
• Fed. Cir. 22-1203 opinion (2023-10-25) — https://cafc.uscourts.gov/opinions-orders/22-1203.OPINION.10-25-2023_2211191.pdf
• Sibling-file assignment reels (IPR2021-01476 Ex. 1002) — https://www.docketalarm.com/cases/[PTAB](/ptab)/IPR2021-01476/Unified_Patents_LLC_v._DivX/docs/09-03-2021-Petitioner/Exhibit-1002-Prosecution_File_History_of_US_Application_15453,714.pdf
• Final judgment, 2:19-cv-01602 (2026) — https://law.justia.com/cases/federal/district-courts/california/cacdce/2:2019cv01602/[738825/1197](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=738825-1197)/

Two fields I could not verify and did not fabricate: the correspondent of record on each link and the '515-specific reel/frame for the 2016 and 2018 transfers. Everything else above is grounded in the cited records.

I'll research US patent 9998515 and its cited prior art. Let me start with targeted searches.

Let me find the specific "Patent Citations" section for US9998515B2.

I have significant material. Now let me retrieve the actual "References Cited" list from the patent's face and the Google Patents citations section.

Patent identification (verbatim, per sources)

Because the effective priority date is Aug 31, 2011, this is a pre‑AIA patent: the governing novelty statute is pre‑AIA 35 U.S.C. § 102(a)/(b)/(e)/(g), not the AIA § 102(a)(1)/(a)(2). That matters for how each reference qualifies.

Important methodological caveat (please read before relying on this)

I was able to retrieve (a) the authoritative full text you supplied, (b) the front‑page "(56) References Cited" data partially via the IPR exhibit reproduction, and (c) the substantive prior‑art challenges from the PTAB/Federal Circuit litigation over this patent. I could not obtain a clean, complete, verified USPTO PatentCenter "References Cited" dump for 9,998,515 in this session. Where I am extrapolating from sibling/continuation patents or from litigation documents, I flag it. No patent number or document identifier below has been auto‑corrected — all are reproduced exactly as found.

Also note: the two litigation challenges over this patent (IPR2020‑00648, Petitioner Unified Patents; IPR2020‑00647, Petitioner Hulu) were obviousness (§ 103) combinations, not anticipation (§ 102) grounds. So the "potential § 102 anticipation" column below is my own mapping, not something the Board or the Examiner found.

A. The most relevant prior art — the PTAB IPR art (Pyle, Marusi, Lewis)

These are the references the Office did not consider during prosecution and which third parties asserted against the '515 claims. They are, by any practical measure, the most relevant prior art to 9,998,515.

1. Pyle (U.S. Patent No. 8,782,268) — primary reference

• Full citation: U.S. Patent No. 8,782,268 to Pyle et al. (Exhibit 1004 in IPR2020‑00648). Application publication version cited as US 2012/0023251 A1 (published Jan. 26, 2012) — reproduced in the Hulu demonstratives as "US 2012/023251 A1 Jan. 26, 2012."
• Dates: Provisional filed July 20, 2010; non‑provisional filed Nov. 3, 2010; published Jan. 26, 2012; issued July 15, 2014.
• § 102 status: Qualifies as pre‑AIA § 102(e) prior art (U.S. patent/application publication effectively filed before the '515 priority date). This is exactly the basis Petitioner asserted.
• Brief description: Pyle concerns "the efficient representation of content such that it can be used in a wide variety of applications having a broad spectrum of content attribute requirements, without mass replication of the content." It uses manifest files — the 3GPP Media Presentation Description (MPD) — to inform a client what media elements are available for HTTP streaming. A "composition component" can select a particular manifest from a set of available manifests based upon data in a request for content and transmit it to the requesting device; Pyle also describes creating new manifests optimized for device capabilities, network conditions, and user preferences (its HDTV‑vs‑smartphone example delivers differently tailored manifests for the same content).
• Claims it could potentially anticipate (§ 102), if its disclosure is taken as teaching both "selecting an existing manifest" and "creating a new manifest":
  • Claim 1 (the independent method claim: receive request identifying content → retrieve list of assets → filter by criterion → generate top level index file describing each asset in the filtered list → send to playback device).
  • Claims dependent on the device‑capability filter (device capability / display aspect ratio / max network data rate limitations).
  • Claim 14 (XML string including a URI for each asset), to the extent a "manifest" is an XML document with URIs.
• Caveat: The Board held that Pyle's selection of an existing manifest did not meet the "filtering"/"generating" limitations; Netflix argued Pyle's new manifest did. So Pyle alone is strongest as a §102(e) reference against claim 1 only under the "new manifest" reading.

2. Marusi — secondary reference (combined with Pyle)

• Full citation: Cited in IPR2020‑00648 as "Marusi." I do not have a verified patent number or publication date for Marusi from the sources retrieved. I will not fabricate one.
• Brief description (from the petition's own framing): Marusi was combined with Pyle in Ground I. The petition argued "the combination of Pyle and Marusi teach generating new manifest files in response to a request for content," "a top level index file describing the filtered assets," and the "retrieving" and "filtering" limitations.
• Potential § 102 mapping: Marusi appears to be a secondary/§103‑style reference, not an anticipatory reference. On the record available, it is not identified as anticipating any claim of 9,998,515 standing alone. Treat it as § 103 fodder for claims 1, 4, 5, 8‑10 and 14 (the Ground I claim set).

3. Lewis — "rule‑based dynamic server‑side streaming of manifest files"

• Full citation: Cited as "Lewis" in the Hulu petition (IPR2020‑00647) and discussed in the Federal Circuit opinion in Netflix, Inc. v. DivX, LLC, Nos. 2022‑1203, 2022‑1204 (Fed. Cir. Oct. 25, 2023). I do not have a verified patent number for Lewis; I will not fabricate one.
• Brief description (verbatim from the Fed. Cir. opinion): "Lewis describes an embodiment wherein video content is processed and customized according to particular client device parameters, and 'when [a] client device requests video content represented by stored video segments, [a] dynamic manifest file server may provide [a] manifest file.'" The petition characterized Lewis as "systems and methods for rule based dynamic server side streaming of manifest files."
• Potential § 102 mapping: As with Marusi, Lewis is positioned as a secondary reference supporting the dynamic, device‑parameter‑customized manifest generation element of claim 1 (and the device‑capability dependent claims). The record treats it as § 103 combination art rather than a standalone § 102 anticipation of any claim.

B. Documents incorporated by reference in the specification (NOT prior art)

The '515 specification expressly incorporates three co‑pending applications. These all post‑date the Aug 31, 2011 priority date, so they are not § 102 prior art to the '515, but they are the references "cited" inside the patent:

C. Front‑page "(56) References Cited" — partial list (from the IPR Exhibit 1001 reproduction)

The reproduced front page of 9,998,515 shows at least the following, but the snippet I retrieved was truncated, so this is not the complete list:

Sibling/continuation US 10,542,061 (same family, same title) additionally lists U.S. references such as 6,741,252 (Hijiri et al., 5/2004); 6,868,143 (Menon et al., 3/2005); 7,103,906 (Katz, 9/2006); 7,177,818 (Nair, 2/2007); 7,295,752 (Jain et al., 11/2007); 7,925,203 (Lane et al., 4/2011); 8,148,622 (Rothkopf, 4/2012); 8,171,518 (White, 5/2012); 8,191,097 (Armstrong et al., 5/2012); 8,266,115 (Park et al., 9/2012); 8,407,753 (Kuo, 3/2013); 8,423,889 (Zagor…, 4/2013); 8,638,935 (Fasoli, 1/2014). I cannot confirm that each of these appears on the '515 face specifically — treat as family‑level, not verified for '515.

None of the front‑page items above were relied upon by the Patent Office to reject any claim, and none is identified in the litigation as anticipating the claims.

D. Bottom line — which prior art is "most relevant" and § 102 posture

1. Pyle (US 8,782,268) is the single most relevant reference. It is pre‑AIA §102(e) prior art and is the only reference realistically capable of a standalone § 102 anticipation argument — and only against claim 1 (and its device‑capability dependents), and only if Pyle's "new manifest" (not merely selected manifest) disclosure is credited. The Board's actual holding went the other way on the "existing manifest" theory, and the Fed. Cir. affirmed in part / divided on whether Netflix properly raised the "new manifest" theory. See Netflix, Inc. v. DivX, LLC, Nos. 2022‑1203, 2022‑1204 (Fed. Cir. Oct. 25, 2023).
2. Marusi and Lewis are secondary references used in § 103 combinations with Pyle; on the available record they do not independently anticipate any claim of 9,998,515. I could not verify their patent numbers/dates and have deliberately not guessed.
3. The references cited inside the specification (Kiefer '623, van der Schaar '061, Grab '598) are not prior art — they post‑date the priority date and belong to the same family of filings.

Caveats on § 102 claims mapping

• The '515 independent claim is claim 1; claim 14 (XML string with a URI per asset), claim 4 (database of assets) and claim 16 (playback‑device apparatus claim) are the notable dependents/independents discussed in the IPR. Attorney argument in DivX v. Netflix confirms claim 2 adds "information regarding a web browser on the playback device."
• No § 102 anticipation was actually established for any claim of 9,998,515 in the proceedings I found; the challenges were § 103. Any "anticipates" statement above is my analytical mapping, not an adjudicated finding.
• If you need the exact, complete front‑page citation list (every U.S. patent, foreign document, and non‑patent publication), it should be pulled directly from USPTO PatentCenter for application 15/009,593 — the fragments above are incomplete, and I will not fill gaps with invented identifiers.

I'll ground this analysis in the actual prior-art record for US 9998515. Let me pull the citation and litigation record.

Let me pin down the specific prior-art references used against this family in the IPR and any other record.

Let me verify the claim text of US 9,998,515 and the bibliographic details of the references actually used against it.

Obviousness Analysis — U.S. Patent No. 9,998,515 B2

“Systems and methods for automatically generating top level index files” (DivX, LLC)

35 U.S.C. § 103 | Prepared April 26, 2026

0. Preliminary caveats (important — please read before relying on anything below)

A. The “Prior Art section” of the fetched page.
I was instructed to use the results from the Prior Art section of the US9998515 page. I have to flag a reliability problem: the version of the page supplied to me (https://patents.google.com/patent/US9998515/en) does not contain a Prior Art/Citations section at all. It contains Classifications, Definitions, Abstract, Description, and a “Landscapes” subsection — but no list of cited references, and no Claims section. Consequently:

• I could not extract a prosecution-era citation list for the ’515 patent.
• The only “prior-art-adjacent” material actually on the page is the Cross Reference to Related Applications and the three U.S. applications incorporated by reference in the Detailed Disclosure (§ below).
• To give you a real §103 analysis rather than a hypothetical one, I grounded the analysis in the actual prior-art of record against this patent family: the PTAB record in IPR2020-00648 and the Federal Circuit opinion in Nos. 22-1203 & 22-1204 (Oct. 25, 2023).

B. Where I lack high confidence, I say so. Specifically: I could not verify the exact publication number of the Lewis reference (Ex. 1006 in IPR2020-00648) beyond its content and figure numbering; the OCR of the Pyle publication number was garbled (“US 2012/023251 A1”); and I do not have verbatim claim text for every dependent claim of the ’515 patent. I have not fabricated any of these.

C. Statutory framework. The ’515 patent carries an effective priority date of Aug. 31, 2011 (provisional 61/529,403, “Automatic Generation of SMIL Files”), and was filed Jan. 28, 2016 (Ser. No. 15/009,593) as a continuation. Because it claims priority to a pre-March 16, 2013 application, pre-AIA §102/§103 apply, which matches the IPR record (the petitioner’s expert declaration expressly walked through pre-AIA §102(a), §102(b) and §102(e)). This matters: the §102(e) branch is what made the Pyle reference available (filed Nov. 3, 2010, published/issued later).

1. The patent and the claim at issue

Per the Federal Circuit opinion (which reproduced it), claim 1 is materially:

1. A method for authorizing playback of content, comprising:

• receiving a request for content from a playback device at a playback server, where the request includes a product identifier that identifies a device configuration;
• identifying, using the playback server, based on the product identifier, a plurality of device capabilities including a device type and a device software version indicating a version number for an adaptive streaming software component implemented on the playback device;
• retrieving, using the playback server, a list of assets associated with the identified piece of content, wherein each asset is a different stream associated with the piece of content;
• filtering, using the playback server, the list of assets based on the plurality of device capabilities;
• generating, using the playback server, a top level index file describing each asset in the filtered list of assets, wherein the top level index file identifies locations and bitrates of a plurality of alternative streams capable of being used to perform adaptive streaming of the content; and
• sending the top level index file from the playback server to the playback device.

Claim 14 is the XML-string/URI dependent claim (per Petitioner’s demonstratives in IPR2020-00647/648). The ’515 patent is a continuation in the same family as US 9,270,720 (“the ’720 patent”), and the Federal Circuit described the two specifications as “nearly identical.”

Note on internal date tension: the page’s own Cross Reference says the ’515 is a continuation of 14/336,392, itself a continuation of 13/341,789 (now US 8,787,570). The Federal Circuit footnote states the ’515 “is a continuation of an application that issued as the ’720 patent.” I have not resolved this discrepancy and flag it rather than harmonizing it.

2. The prior art actually asserted against this patent

These are the references in the two grounds that the Board instituted and decided in IPR2020-00648 (Netflix, Inc. / Hulu, LLC v. DivX, LLC), FWD Sept. 27, 2021, affirmed in Netflix, Inc. v. DivX, LLC, Nos. 22-1203, -1204 (Fed. Cir. Oct. 25, 2023) (Dyk, J., dissenting in part).

Also of record but not prior art against claim 1 (all filed after the Aug. 31, 2011 priority date and therefore outside pre-AIA §102(a)/(b)/(e)): the three applications the ’515 patent itself incorporates by reference — 13/340,623 (Kiefer et al.) filed Dec. 29, 2011; 13/251,061 (van der Schaar et al.) filed Sep. 30, 2011; and 61/581,598 (Grab et al.) filed Dec. 29, 2011. (Caveat: I did not verify whether any of those carry earlier priority.) They are conceptually important — they contain the DRM/cryptographic-information, bandwidth-probe and product-ID material reflected in the ’515 specification — but they cannot be used in a §103 rejection against claim 1.

3. Level of ordinary skill

The Board in IPR2020-00648 adopted the Petitioner’s unopposed articulation of the level of ordinary skill in the art; I do not have its verbatim text in the material I retrieved. Functionally it is the standard adaptive-streaming artisan: a person with a computing/electrical-engineering background and a few years’ experience in HTTP streaming, container formats (MP4/TS), manifest/index design (SMIL, M3U8), and client-server media delivery. The Board also credited the observation that “lists” and database operations were “very well-known” concepts, and rejected an expert who could not describe the 2011 state of the art.

4. Ground I — Pyle in view of Marusi

4.1 Element-by-element mapping (as presented by the Petitioner)

4.2 Motivation to combine (this part was not the problem)

The Petitioner’s motivation argument (Dr. Reader, Ex. 1003 ¶150) was that “the teachings of Pyle and Marusi were complementary, and therefore [a POSITA] would have been motivated to combine Pyle with Marusi to enhance the efficiency of generating, storing, and delivering multimedia content tailored to the capabilities of particular playback devices.” That is a textbook KSR rationale stack:

1. Same field, same problem — both address serving a requested media item to a particular client in a form that client can handle.
2. Complementary teachings — Pyle supplies the manifest/index architecture and server-side capability-based selection/creation; Marusi supplies the concrete, well-known lookup mechanism (a database of terminal identifiers → capability information).
3. Known technique / predictable result — using a database keyed to a device identifier to select among stored representations was routine; the resulting system does what both references predict (device-appropriate delivery).
4. Design incentive independent of the ’515 disclosure — Pyle’s own abstract states the goal of letting “random devices … contact a Web server, find and play a composition matched to the given devices and users,” “without complex programming, web pages, etc. specific to each device.”

So on motivation, Ground I is legally sound. The failure was evidentiary, not motivational.

4.3 Where the combination actually failed

The Board and the Federal Circuit identified three defects, all of which are proof/pleading defects rather than findings that the subject matter was inventive:

• “Retrieving … a list of assets.” The Petitioner pointed only to a result (a manifest that contains a list of URLs) rather than giving a reason why the intermediate retrieving step would have been obvious. The Board held this lacked “articulated reasoning with some rational underpinning” (KSR / In re Kahn). (FWD discussion of Lewis is the most explicit statement of this reasoning.)
• “Filtering the list of assets.” The Petitioner primarily relied on Pyle’s selection of a pre-existing manifest, which the Board and Federal Circuit held is different from filtering a list of assets. The backup reliance on Marusi was ambiguous: the petition’s own concluding sentence mapped Pyle to filtering and Marusi only to the database component. The Federal Circuit: the petition “never suggests or explains how Marusi filters ‘a list of assets’ as claimed.”
• “Generating a top level index file describing each asset in the filtered list.” Two sub-problems:
  (i) Internal inconsistency — the index must describe “each asset in the filtered list,” but the Petitioner used Pyle’s pre-existing manifest for filtering and a separate, new manifest for generating, so the new manifest could not be the byproduct of the filtering step.
  (ii) Memory-transmission theory — “the manifest … is generated because [it] must be placed in memory for transmission” was held conclusory; transmitting/storing a file is not “generating” it. The “Pyle creates a new manifest” alternative was held not fairly presented in the petition (Fed. Cir. majority affirmed; Judge Dyk dissented, would have remanded).

4.4 Adjudicated result of Ground I

• Claims 1–6, 8–10, 13, 14: not shown obvious by a preponderance.
• Claims 16, 17, 19: unpatentable over Pyle + Marusi — the Board affirmatively adopted the Petitioner’s analysis and motivation-to-combine for those claims as its own. Affirmed by the Federal Circuit (Oct. 25, 2023).

Takeaway: a Pyle + Marusi combination is sufficient to render some claims of the ’515 patent obvious, as a matter of final adjudication. It failed on claim 1 only because of how the ground was pleaded and evidenced.

5. Ground II — Lewis in view of Marusi

• Lewis teaches a rule resolution server 320 plus a dynamic manifest file server 310 that generates data-driven, dynamic manifest files targeted to client platforms (Flash, etc.), the manifests containing URLs to video segments.
• Marusi supplies the identifier→capability database and the database-query/selection mechanism.
• Motivation: Lewis’s whole premise is rule-based targeting of streams to particular client devices; implementing device-specific rule sets requires a maintained store of device information, and Marusi is an express example of doing so. Predictable result, same field.
• Adjudicated result: failed. The Board found the Petitioner did not give a reason why a POSITA would modify/reason from Lewis to the “retrieving a list of assets” step (again pointing to an achieved result rather than the claimed prior step); the “filtering” and “generating a top level index file” steps were likewise unproven for claims 1–6, 8–10, 13. The Federal Circuit affirmed, emphasizing that the petition’s use of “would have found it obvious” itself signals a §103 modification theory that must be articulated, not assumed.

6. What follows for a §103 case against the ’515 patent

6.1 The claims that are already adjudicated obvious

Claims 16, 17, 19 are, subject to any further review, invalid over Pyle + Marusi. A future challenger can anchor on that FWD/affirmance.

6.2 The three “holes” a better-pled challenge must fill

The ’515 patent survived on claim 1 not because the subject matter was shown to be inventive, but because each ground had a gap. A well-constructed new §103 challenge would target exactly those gaps:

1. Hole — “retrieving a list of assets.” Needed: a reference that expressly discloses a server querying/building the set of available assets (all streams/representations) for the requested title, i.e., an affirmative retrieving step rather than an inferred one. Combine with Pyle (or Lewis) for the index/capability architecture; rationale: a server cannot select among alternatives it has not enumerated (the very inference the Board refused to make from a mere result). A content-management/asset-catalog reference plus Pyle+Marusi closes this.
2. Hole — “generating” an index that describes “each asset in the filtered list.” Needed: a reference teaching on-the-fly construction of a manifest/index in response to a request, from a filtered subset (as opposed to selecting a pre-existing manifest). This is the Pyle “new manifest” theory properly pleaded — i.e., relying on Pyle’s generation of a new, optimized manifest for both the filtering and generating steps so that the two are consistent. Note that the Federal Circuit majority did not hold this theory legally wrong; it held it was not in the petition. A new petition that squarely pleads it, with expert testimony that maps the new manifest to the filtered-asset set, is materially stronger.
3. Hole — the 1[c] limitation: “a device software version indicating a version number for an adaptive streaming software component.” The Board/Fed. Cir. record shows this was attacked using Marusi’s “last software upgrade of the actual phone,” and the Thoen reference was raised for the first time in the Petitioner’s Reply, so the Board held it untimely. A new challenge that puts Thoen (or its equivalent — a reference expressly tracking the version of a client player/streaming component) in the petition itself directly attacks this limitation, which is the ’515 patent’s principal point of distinction over Pyle.

6.3 Additional/alternative combinations worth developing

• Pyle + Marusi + asset-catalog reference (fills Hole 1) and Pyle + Marusi + Thoen-like player-version reference (fills Hole 3): three-reference grounds are entirely permissible; the motivation for each addition is the same “known technique applied to a known problem with predictable results” rationale already accepted by the Board for claims 16/17/19.
• Lewis + Marusi + explicit-retrieval reference: Lewis already supplies rule-based, device-targeted dynamic manifests; the missing ingredients are the enumerated retrieving step and the capability database, both of which Marusi (and an asset-catalog reference) supply.
• Dependent-claim concepts — the specification’s SMIL XML/URI generation (claim 14), SWITCH/EXCL elements, header-size and video-buffer-verifier elements, premium-content and geo-restriction filtering, language filtering — are, as a technical matter, the kind of well-documented SMIL 3.0 / IIS Smooth Streaming conventions that a POSITA would have found routine in 2011. These are largely claim-drafting features, and an obviousness case on them would be strong if an appropriate pre-2011 reference is put in the record (the record I retrieved does not contain such references beyond Pyle’s XML manifest teaching). I did not verify specific SMIL-specification citations for those limitations and therefore do not assert them as established prior art here.
• DRM / concurrency / play-event / resume-at-location subject matter in the specification is supported by DivX’s own Kiefer (13/340,623) and related filings — but those are post-priority and cannot be prior art against claim 1. If dependent claims of the ’515 recite that subject matter, the challenge must find independent pre-2011 DRM and concurrency-limit references (e.g., generic DRM license-server art and concurrent-stream limits), not DivX’s own copending applications.

6.4 Strategic caveats

• “Not shown obvious” ≠ “non-obvious.” The FWD is a burden-of-proof outcome on a weak record (conclusory petition text echoing a single declaration paragraph). It creates no affirmative patentability holding that binds a future challenger who pleads differently.
• Collateral estoppel runs both ways. For claims 16/17/19 the invalidity determination is now final; for claim 1 the PTAB’s judgment of patentability could be asserted defensively, but only as to the grounds actually decided — §103 permits, and invites, new grounds.
• Litigation context to watch: the family carries litigation flags across IPR2020-00648 (PTAB, FWD), C.D. Cal. 2:19-cv-01602 and 2:19-cv-01606, an ITC investigation in which DivX was complainant, and Federal Circuit appeals 22-1203 / 22-1204. Any new §103 theory must be evaluated against the estoppel and IPR-time-bar posture of whichever forum is chosen (IPR estoppel under §315(e) applies to the real parties in the earlier IPRs).

7. Bottom line

1. The prior art that matters against US 9,998,515 is Pyle (US 8,782,268), Marusi (EP 2 180 664), and Lewis (dynamic-manifest publication) — the Prior Art section of the fetched page does not exist, so the analysis rests on the IPR2020-00648 / Fed. Cir. record.
2. Two combinations were actually litigated: Pyle + Marusi and Lewis + Marusi, both under §103.
3. Only the Pyle + Marusi combination succeeded, and only against claims 16, 17 and 19 (FWD Sept. 27, 2021; Fed. Cir. affirmed Oct. 25, 2023). Claims 1–6, 8–10, 13 and 14 were not shown obvious.
4. The motivation to combine was never the weak link. Both grounds had facially sufficient KSR rationales (same field, complementary teachings, known identifier→capability database technique, predictable result, design incentive to avoid per-device bespoke provisioning). Both failed on articulation and evidentiary sufficiency, chiefly around the “retrieving a list of assets,” the filtered-list-to-generated-index consistency, and the outstanding “device software version / adaptive streaming software component” limitation.
5. A re-pled challenge is materially more dangerous to claim 1 if it (a) expressly enumerates a server-side retrieval of the available-asset list, (b) uses Pyle’s newly generated optimized manifest consistently for both filtering and generating, and (c) put the player/streaming-component version reference (the “Thoen” material) in the petition rather than in reply.

Sources relied on

• Full patent text: https://patents.google.com/patent/US9998515/en
• IPR2020-00648 Final Written Decision (Sept. 27, 2021): https://lowensteinweatherwax.com/wp-content/uploads/2021/09/2021-09-27-IPR2020-00648-Final-Written-Decision.pdf
• Netflix, Inc. v. DivX, LLC, Nos. 22-1203, -1204 (Fed. Cir. Oct. 25, 2023): https://cafc.uscourts.gov/opinions-orders/22-1203.OPINION.10-25-2023_2211191.pdf
• PTAB case record: https://portal.unifiedpatents.com/ptab/case/IPR2020-00648
• District-court/litigation status summary: https://storage.courtlistener.com/recap/gov.uscourts.cacd.[738825](/patent/738825)/gov.uscourts.cacd.738825.146.1.pdf
• Petition, IPR2020-00647 (reference identification: Pyle, Marusi, Lewis): https://www.docketalarm.com/cases/PTAB/IPR2020-00647/
• Unified Patents patent page: https://portal.unifiedpatents.com/patents/patent/US-9998515-B2

This is a technical/analytical assessment of the prior-art record, not legal advice, and not a substitute for a formal validity opinion or a claim-by-claim infringement/validity analysis by counsel of record.