US 6721489

I'll search for current information on this patent, then summarize.

Let me get the specific claim language and check for any appellate activity.

Summary — US 6,721,489 B1 ("Play list manager")

Note on dates: your prompt states the current date as April 26, 2026, but my operating environment sets today as September 28, 2026, and search results I retrieved include docket material dated August 2026. I'm flagging this rather than silently picking one.

Note on identifiers: I searched and report only on US 6,721,489 B1. Beware the collision with JP 6721489 B2 (a Hitachi magnetic-resonance-imaging patent, registered 2020-06-22) — that is a different document from a different office and is not the patent you asked about.

Bibliographic data

Foreign family members include PCT/US2001/040209 and WO 01/67753 A1, plus AU 2001250015 A1 (all claiming the 2000-03-08 priority).

Abstract (verbatim)

"A play list manager is disclosed that can be used to create and update play lists. The play lists can be used for audio information, visual information, or a combination of audio and visual information. The user of the play list manager creates a play list and specifies certain criteria for automatically adding tracks to the play list. When a new track is added to the environment, the system tests whether the track's properties satisfy the criteria for the play list. If so, the new track is automatically added to the play list. In one alternative, a user can select a predefined play list, whose criteria has already been created. Upon selection of the predefined play list, the play list manager accesses each track and adds the track to the play list if the track's properties satisfy the criteria for the predefined play list."

Claims — what I can and cannot verify

Verified (claim 1, verbatim, from the USPTO Official Gazette text):

"1. A method for updating a play list, comprising the steps of:
comparing a set of one or more properties of a first track to criteria of a first play list; and
automatically adding said first track to said first play list if said set of properties of said first track satisfy said criteria of said first play list."

Plain-language: A computer compares one or more attributes of a track (e.g., artist, year, genre) against rules the user set for a play list, and adds the track to that list on its own when the attributes match the rules. No human has to drag the track in.

Independent claims I can only describe at a summary level, with uncertainty: The specification's own summary of the invention describes at least two further distinct inventive groupings that are almost certainly mirrored in independent claims, but I could not retrieve the verbatim text of claims other than claim 1 and will not reconstruct them:

1. Detect-then-compare variant — the comparing step happens automatically in response to detecting that a track has become available (specification: "detecting that the first track is available such that the step of comparing is performed automatically in response to the step of detecting").
2. Multi-list variant — properties of one track are compared against the criteria of a plurality of play lists, and the track is added to each list whose criteria it satisfies.
3. Predefined/"one-click" list generation variant — receiving a request to generate a play list having predefined criteria, determining which tracks satisfy those criteria, and automatically adding them (FIG. 20, the "one click" play list buttons of GUI 1200).

Given 51 total claims, dependent claims almost certainly cover specifics such as ID3 tag fields as the source of "properties" (FIG. 16), similarity information stored in a database, and the prompt-to-confirm alternative in step 1412. I do not have authoritative text confirming the numbering or exact wording of any claim other than claim 1. For a claim-by-claim reading you should pull the granted claims directly from USPTO PatentCenter or the Google Patents "Claims" tab — the patent text supplied to me was truncated inside the detailed description and did not include the claims section.

Context worth noting

• The patent is one of three applications filed the same day by the same team; the other two are Ser. No. 09/521,182 ("Audio/Visual Server") and Ser. No. 09/521,186 ("Vehicle Sound System"), each incorporated by reference.
• Commercially, this is the PhatNoise car-audio "digital jukebox" system: a removable 2½-inch hard-disk cartridge, a docking station wired to a PC over USB (USB-to-IDE interface, OnSpec 90C36), and an in-vehicle server that emulates a disc changer to a stock Sony head unit (the FIG. 11 state machine and Table 1 packets are keyed to a Sony XR-C5120).
• Much of the disclosure (head-unit emulation, firmware re-flashing via the /microcontroller config directory, directory layout /MP3, /playlist, /playlist config, /microcontroller config, /OS) is outside the claimed play-list subject matter.

Litigation / post-grant status

• Google Patents' "Family has litigation" panel lists 15 U.S. district court cases spanning 2019–2022 in E.D. Tex., W.D. Tex., N.D. Tex., D. Colo., S.D.N.Y., and D. Del. — consistent with the patent being asserted by Cedar Lane Technologies after the 2019-10-17 assignment from AVInnov, LLC. Third-party reporting describes Cedar Lane suits naming the '489 patent against Dish Network and LiveXLive Media.
• Assignment chain of record: PhatNoise → (security agreement to Silicon Valley Bank) → PLAYLIST, Inc. (2005) → Sayre Holdings JP LLC (2006) → Mineral Lassen LLC (2015) → Intellectual Ventures Assets 125 LLC (2018) → AVInnov LLC (2019) → Cedar Lane Technologies Inc. (2019).
• On the CAFC question: I did not find a Federal Circuit docket or appeal decision specifically captioned to US 6,721,489. My searches surfaced 2026 Federal Circuit activity involving Cedar Lane and various 2025–2026 Cedar Lane district court complaints, but the retrieved snippets do not tie any of those to the '489 patent, and Cedar Lane's recent filings appear to involve a different patent portfolio (financial-services defendants). I cannot confirm or deny a 2026 CAFC appeal of the '489 patent. Treat "no CAFC 2026 docket found" as a search limitation, not a finding of fact. The patent itself expired (anticipated) on 2020-03-08, which is relevant context for what relief could remain available and for any appeal.

I'll research litigation involving US 6721489. Let me run several searches.

Let me dig deeper into specific cases and outcomes.

Litigation Involving U.S. Patent No. 6,721,489 ("Play list manager")

Bottom line: Yes — the '489 patent has an extensive U.S. litigation history. It was asserted primarily by Cedar Lane Technologies Inc. (a Canadian NPE) starting in 2020, in a large multi-defendant campaign that also included sibling patents (6,502,194; 6,526,411; 7,173,177; 7,610,394; 6,806,889; 6,452,609; 8,545,097; 8,805,830). I found no Federal Circuit appeal specifically involving the '489 patent, and no PTAB proceeding (IPR/PGR/CBM) against the '489 patent in my search results. The patent itself expired 2020‑03‑08 (20 years from the 2000‑03‑08 filing), which caps recoverable damages to pre‑expiration conduct.

Ownership chain (relevant to who could sue)

From the Google Patents record for US 6,721,489 B1:

• Inventors: Daniel Benyamin, Dannie C. Lau, Brendan T. Dowling
• Original assignee: PhatNoise, Inc. (application 09/521,874, filed 2000‑03‑08)
• 2005‑08‑22: assigned to Playlist, Inc.
• 2006‑12‑13: assigned to Sayre Holdings JP LLC
• 2015‑11‑18: Mineral Lassen LLC (merger)
• 2018‑12‑18: Intellectual Ventures Assets 125 LLC
• 2019‑02‑06: AVINNOV LLC
• 2019‑10‑17: Cedar Lane Technologies Inc.

Cedar Lane is the plaintiff in essentially all identified 2020–2022 filings.

Known cases (per Google Patents "Family has litigation" + corroborating reporting)

The Google Patents page also records a "First worldwide family litigation" entry via Darts‑IP (family 24078499), and Unified Patents portal litigation links for each case:

• https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A19-cv-00368
• https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A19-cv-00369
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/6%3A22-cv-00043
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/6%3A20-cv-00988
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/6%3A20-cv-00949
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/6%3A20-cv-00947
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/1%3A20-cv-00501
• https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/1%3A20-cv-00472
• https://portal.unifiedpatents.com/litigation/Texas%20Northern%20District%20Court/case/3%3A20-cv-01103
• https://portal.unifiedpatents.com/litigation/Colorado%20District%20Court/case/1%3A19-cv-03189
• https://portal.unifiedpatents.com/litigation/New%20York%20Southern%20District%20Court/case/1%3A20-cv-03635
• https://portal.unifiedpatents.com/litigation/New%20York%20Southern%20District%20Court/case/1%3A20-cv-03159
• https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A21-cv-00676
• https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A20-cv-01370
• https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A20-cv-00473
• https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A19-cv-00373
• https://portal.unifiedpatents.com/litigation/Colorado%20District%20Court/case/1%3A20-cv-03037

Outcomes / current status

• No case reached trial or a merits judgment that I could identify. The Cedar Lane campaign was a high-volume licensing/settlement program. Independent analyses report that ~87% of Cedar Lane's cases terminated by likely settlement / voluntary dismissal, with a small number of procedural resolutions, transfers, and remaining open cases.
• Specific documented dispositions: Dai Nippon Printing — voluntary dismissal with prejudice (W.D. Tex., Nov. 2021). Other defendants resolved by settlement or voluntary dismissal. I cannot confirm disposition-by-disposition outcomes for most of the cases above.
• Unified Patents, LLC v. Cedar Lane Technologies Inc. appears as a related matter (Patexia), indicating at least one third-party validity challenge effort in the campaign.
• No CAFC appeal involving the '489 patent was found.
• Patent status: "Expired – Lifetime"; anticipated expiration 2020‑03‑08. Any remaining claims are for pre‑expiration infringement only.

Important caveats and verification notes

1. Case numbers vs. defendants: I could directly tie defendants to case numbers only for the cases in the table above (rows 1–9). For the remaining case numbers (rows 9–19), the Google Patents litigation list confirms the case exists and asserts the '489 patent family, but I could not verify plaintiff/defendant/jurisdiction mapping within my search budget. Those should be confirmed on PACER, Unified Patents' litigation portal, or RPX/Insight.
2. Rows 18–19 (E.D. Tex. 2:19-cv-00368 / -369): These predate Cedar Lane's Oct. 2019 acquisition, so the plaintiff was likely a predecessor (AVINNOV LLC / Mineral Lassen / IV entity). I did not confirm this — do not rely on it without checking.
3. A "6721489" hit that is NOT this patent: Japanese Patent No. JP 6721489 B2 (Hitachi, MRI apparatus) appeared in results. It is unrelated and must not be conflated with US 6,721,489.
4. Search result caution: Some retrieved documents contained USPTO EAST search-history listings citing "6721489" — those are prior-art search logs in unrelated applications, not evidence of litigation or PTAB proceedings against the '489 patent.

Recommended next steps for a definitive docket list: search PACER for the case numbers above, the Unified Patents litigation portal (https://portal.unifiedpatents.com/litigation/caselist), RPX Insight, and Darts‑IP family 24078499.

I'll verify the "no PTAB activity" default against live sources before writing the report.

Let me check PTAB-specific sources and the litigation history in more depth.

Let me run a few more targeted checks on PTAB dockets, RPX, and Federal Circuit appeals.

PTAB Proceedings — US 6,721,489 ("Play list manager")

Bottom line up front: I found no AIA trial proceedings against US 6,721,489. The canonical structured list is empty, and my independent web verification surfaced no IPR, PGR, or CBM naming this patent. What follows states that finding plainly, identifies the closest neighboring proceeding (a different patent), and flags the limits of my verification so you don't over-rely on the negative.

Proceedings overview

Total proceedings on US 6,721,489: 0. Breakdown: 0 active, 0 with claims invalidated, 0 with claims sustained, 0 settled, 0 institution denials. The structured "PTAB proceedings on file" block (USPTO ODP, most recent ingest) contains no AIA trial records for this patent, and my web searches returned no PTAB docket naming 6,721,489. The defensive posture this gives a defendant is therefore "untested, not hardened" rather than either extreme: no claim has been canceled, so Cedar Lane's assertion set is intact — but equally, the PTAB has never blessed these claims, so the patent carries no validity patina from surviving a Board challenge. The headline fact for a defendant is different: the patent expired 2020-03-08 and its legal status is "Expired - Lifetime," which caps your damages exposure to pre-expiration conduct and makes injunctive relief unavailable for ongoing activity.

No per-proceeding entries follow, because there are no proceedings to enumerate. Rather than pad the section with empty headings, here is the nearest-neighbor analysis you should actually run down:

Closest PTAB activity in the chain (different patent — do NOT cite as an IPR on '489)

• Proceeding: IPR2020-00006, Unified Patents, LLC v. Cedar Lane Technologies Inc.
• Patent at issue: US 7,173,177 B1 ("indicating on a user interface whether items in a playlist are owned or unowned") — not 6,721,489.
• Filed: 2019-10-03. Instituted: 2020-03-18 (on all challenged claims). FWD: 2021-02-12 — the asserted independent claim held unpatentable. Rehearing denied 2021-12-08.
• Panel: Christopher M. Kaiser (writing), Norman H. Beamer, Scott B. Howard.
• Source: Unified Patents insight; Patexia case record; RPX insight.
• Why it matters to you anyway: The '177 and '489 patents came through the same acquisition chain (Intellectual Ventures → AVInnov → Cedar Lane) and were asserted together — Cedar Lane's complaint against [The Walt Disney Company](/litigations/by-plaintiff/The%20Walt%20Disney%20Company), W.D. Tex. 6:20-cv-00949, pleads 6,526,411, 7,173,177, 6,721,489, and 8,165,867 in one suit (IPWatchdog roundup). Unified is a defensive aggregator and it has already taken one Cedar Lane playlist-family patent to a full invalidation. That is a strong signal that '489 has been considered — but the docket evidence before me shows no challenge actually filed against it.

What the record does show in volume: district court litigation, not PTAB

The Google Patents structured data lists at least 16 district court cases touching this patent — E.D. Tex. (2:19-cv-00368, 2:19-cv-00369), D. Del. (1:19-cv-00373, 1:20-cv-00473, 1:20-cv-01370, 1:21-cv-00676), D. Colo. (1:19-cv-03189, 1:20-cv-03037), W.D. Tex. (6:20-cv-00947, 6:20-cv-00949, 6:20-cv-00988, 1:20-cv-00472, 1:20-cv-00501, 6:22-cv-00043), N.D. Tex. (3:20-cv-01103), and S.D.N.Y. (1:20-cv-03159, 1:20-cv-03635). Cedar Lane, a Canadian NPE (per the KIPO NPE study), is a high-volume filer with a heavy W.D. Tex. / Judge Albright footprint. Volume of district court assertion with zero PTAB filings is itself a data point: defendants in this campaign have overwhelmingly settled rather than taken the patent to the Board.

Strategic summary

Claim status. Because no IPR, PGR, or CBM has ever been instituted, all 51 claims remain unadjudicated and presumptively valid — there are no canceled claims and no sustained-by-IPR claims. The independent claim you are most likely to be accused under is claim 1, "A method for updating a play list," comprising "comparing a set of one or more properties of a first track to criteria of a first play list" and "automatically adding said first track to said first play list if said set of properties of said first track satisfy said criteria" (per the Official Gazette text). That limitation — automated criteria-based addition — is the crux of the claim (and the core of the '489 specification, which describes one-click and criteria-driven play-list generation).

Estoppel landscape. § 315(e)(2) estoppel is not a constraint here, because estoppel only attaches to petitioners who reach a final written decision. No one has. That is the upside for you: every prior-art ground, under § 102 and § 103, is fully available — nothing has been "raised or reasonably could have been raised" and then lost. The only related estoppel that exists runs against Unified Patents with respect to the grounds it litigated on 7,173,177, and only as to that patent. Note the § 315(b) clock as a planning point: if Cedar Lane served you with a complaint more than one year ago, you are time-barred from filing an IPR and your invalidity case lives in district court. Given that the most recent listed case is 6:22-cv-00043 (2022) and the patent expired 2020-03-08, a newly asserted defendant is unlikely to be within the window — but verify against your actual service date.

Pattern signals. (1) Same petitioner, sibling patent: Unified Patents has filed and won against the Cedar Lane playlist family, but on '177, not '489. (2) Patent owner behavior: Cedar Lane is a serial NPE that litigates broadly and rarely faces — or invites — PTAB review; the record shows no Cedar Lane appeal of an adverse FWD on '489 because no FWD exists. (3) No defensive aggregator on THIS patent: Unified's interest in the family has not (on the evidence before me) translated into a challenge to '489. (4) The clock has run: with expiration on 2020-03-08, the patent is in its post-expiration enforcement phase — valuable for past damages, useless for prospective injunctions.

Verification caveat — read this before relying on the negative. I could not exhaustively query PTAB E2E, RPX Insight, Docket Alarm, or CourtListener on a per-patent basis for 6,721,489; my steps were capped mid-verification. The structured ODP block is the strongest evidence ("default should be no PTAB activity on file"), and nothing I found contradicts it. But a zero-PTAB finding for a patent with this much assertion volume deserves a clean-room double-check before you tell a client or a court that no challenge exists. Treat the count as "no proceedings found" rather than "proceedings provably do not exist."

Recommended next steps

1. Confirm the negative directly, don't rely on this memo alone. Run the patent number through (a) USPTO PTAB E2E / PatentCenter "Patent Trial" tab, (b) RPX Insight and Unified Patents' litigation portal (portal.unifiedpatents.com), and (c) Docket Alarm / CourtListener filtered to the patent number. Any hit naming 6,721,489 supersedes everything above.
2. Pivot the defense to the expiration date and to § 102/§ 103 in district court. With no estoppel and no prior IPR narrowing, the full prior art universe is open. The '489 priority date is 2000-03-08 — a genuinely crowded window for playlist-management/digital-jukebox art, and claim 1's "automatically adding" limitation is where a § 103 obviousness case is most likely to land.
3. If a complaint is pending and you are within one year of service, evaluate an IPR now — you would be the first petitioner, there is no adverse claim construction from any prior Board proceeding, and the Board's institution calculus is unaffected by a prior FWD. Weigh it against the fact that the patent expires/expired and your damages exposure is already time-limited.
4. Mine Unified's '177 win for free claim-construction and expert material. IPR2020-00006 (FWD 2021-02-12; panel Kaiser, Beamer, Howard) put "playlist" claim language through the Board and produced a Harley R. declaration and art like Looney (5,969,283), DeMartin (6,226,672), and Cluts (5,616,876). Even though estoppel doesn't bind you and the patent differs, the art set and the Board's reasoning on adjacent playlist claims are useful starting points. Record: Patexia documents index.
5. Do not tell a court or an adversary that "claims 1–5 were canceled." They were not. If you cite 6,721,489 in any invalidity contentions, cite it as an untested, expired patent with 51 live claims, and build your invalidity theory from scratch.

I'll research the assignment record, correspondence attorneys, and litigation context before reconstructing the chain.

Let me dig into the ownership entities, litigation history, and any recorded attorney/correspondent details.

Sourcing caveat up front (important for this task): I was able to pull the dates and conveyance types for this chain (they mirror the USPTO assignment records via Google Patents' legal-events table, which is reproduced in the source text you supplied). I could not retrieve the reel/frame numbers or the recorded correspondent (recording attorney/firm) fields for these entries — those live only in the USPTO Assignment Center full-text view and were not surfaced by the searches available to me this session. I am therefore leaving reel/frame and correspondent blank rather than inventing them. Treat the correspondent-recurrence signal (Signal 3) as unassessed, not as "absent." This is a search limitation, not evidence of no record.

Inventors

Unusual-pattern assessment: All three inventors assigned to PhatNoise, Inc. by the 2000-03-08 instrument (same day as filing), which is the normal "we own what we file" record, not an early-departure red flag. I found no record of inventors re-acquiring rights, and no evidence of an inventor-initiated transfer. So the "all inventors bailed within 12 months" pattern is not present on the record I can see. The fire-sale, if any, happened at the corporate level in 2005–2006, not the inventor level.

Original assignee

PhatNoise, Inc. (name spelled "PHATNOISE, INC." on the original instrument; also styled PhatNoise on the patent).

• Product: Yes — the PhatNoise Car Audio System / PhatBox. The LynuxWorks case study describes it as an in-car MP3 jukebox built on BlueCat Linux with a removable cartridge, USB dock, and "patent-pending dynamic playlist-generation technology, which... organizes and updates music playlists automatically according to consumers' personal musical preferences." That is a direct product embodiment of the '489 claims.
• Line of business: Automotive digital-media jukebox hardware + music-management software. Founded 1999; won "Best Overall Product"/"Best Car Product" at MP3 Summit 2000.
• Current status: No longer independent. Discrepancy to flag: RPX states PhatNoise was "acquisition by Harman in August 2005," whereas the USPTO/Google record shows the patent assigned 2005-08-22 to PLAYLIST, INC. (assignor PhatNoise, Inc.). Either Playlist, Inc. is a Harman-linked or asset-purchase vehicle, or RPX is compressing the transaction. I cannot resolve which from available sources — treat the Harman/Playlist relationship as unclear.

Assignment timeline

All entries below are legal-event records mirrored from USPTO assignment data (Google Patents legal-events table). Reel/frame and correspondent are not populated because I could not retrieve them. Dates shown are the recorded/event dates as listed; execution dates for some instruments may precede them.

2000-03-08 / recorded 2000-03-08 — Reel not retrieved

• Conveyance: Assignment of assignors' interest (original)
• Assignor: BENYAMIN, DANIEL; DOWLING, BRENDAN T.; LAU, DANNIE C.
• Assignee: PHATNOISE, INC.
• Correspondent: not retrieved
• Context: Founding assignment — inventors convey to the operating company on filing day.

2004-11-18 / recorded 2004-11-18 — Reel not retrieved

• Conveyance: Security Agreement
• Assignor: PHATNOISE, INC.
• Assignee: SILICON VALLEY BANK
• Correspondent: not retrieved
• Context: Securitization — collateral pledge of the portfolio to a venture-debt lender (patent not sold; encumbered).

2005-08-22 / recorded 2005-08-22 — Reel not retrieved

• Conveyance: Assignment of assignors' interest
• Assignor: PHATNOISE, INC.
• Assignee: PLAYLIST, INC.
• Correspondent: not retrieved
• Context: Corporate sale / asset transfer — patent leaves the operating company (coincides with the reported Harman acquisition window; relationship to Harman unclear).

2005-08-29 / recorded 2005-08-29 — Reel not retrieved

• Conveyance: Release by Secured Party
• Assignor: SILICON VALLEY BANK
• Assignee: PHATNOISE INC.
• Correspondent: not retrieved
• Context: Lien release — lender discharges the 2004-11-18 security interest as the sale closes. Administrative, not an ownership change.

2006-12-13 / recorded 2006-12-13 — Reel not retrieved

• Conveyance: Assignment of assignors' interest
• Assignor: PLAYLIST, INC.
• Assignee: SAYRE HOLDINGS JP LLC
• Correspondent: not retrieved
• Context: Transfer to aggregator — RPX describes a "September 2006 transfer to an affiliate of IV," identifying this link as entering the Intellectual Ventures orbit. (Note the RPX "September" vs. recorded "December" date tension.)

2015-11-18 / recorded 2015-11-18 — Reel not retrieved

• Conveyance: Merger
• Assignor: SAYRE HOLDINGS JP LLC
• Assignee: MINERAL LASSEN LLC
• Correspondent: not retrieved
• Context: Internal reorganization within the IV family — by merger, not purchase.

2018-12-18 / recorded 2018-12-18 — Reel not retrieved

• Conveyance: Nunc pro tunc assignment
• Assignor: MINERAL LASSEN LLC
• Assignee: INTELLECTUAL VENTURES ASSETS 125 LLC
• Correspondent: not retrieved
• Context: Aggregator divestiture — IV packages the asset into a sale vehicle; "nunc pro tunc" signals a retroactively-effective closing document.

2019-02-06 / recorded 2019-02-06 — Reel not retrieved

• Conveyance: Assignment of assignors' interest
• Assignor: INTELLECTUAL VENTURES ASSETS 120/125 LLC
• Assignee: AVINNOV LLC
• Correspondent: not retrieved
• Context: Transfer to asserter — RPX headline frames this as the portfolio "bouncing off one NPE" (AVInnov).

2019-10-17 / recorded 2019-10-17 — Reel not retrieved

• Conveyance: Assignment of assignors' interest
• Assignor: AVINNOV LLC
• Assignee: CEDAR LANE TECHNOLOGIES INC.
• Correspondent: not retrieved
• Context: Transfer to asserter — landing at a known high-frequency plaintiff; the 2019 E.D. Tex. complaints (2:19-cv-00368, 2:19-cv-00369) cluster around this date.

2020-03-08 — Anticipated expiration (legal-status event, not an assignment).

Verification links: USPTO Assignment Center · USPTO Patent Assignment Search (patent no. lookup)

Timeline diagram

timeline
    title Ownership of US 6721489
    2000 : Inventors assign to PhatNoise Inc
         : Application filed 08 Mar
    2004 : Security agreement to Silicon Valley Bank
    2005 : PhatNoise assigns to Playlist Inc
         : Bank releases security interest
    2006 : Playlist Inc assigns to Sayre Holdings JP LLC
    2015 : Merger into Mineral Lassen LLC
    2018 : Nunc pro tunc to IV Assets 125 LLC
    2019 : Bounced to AVInnov LLC
         : Transferred to Cedar Lane Technologies
         : First NPE suits filed

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT. The patent leaves an operating company (PhatNoise, which shipped the PhatBox) at the 2005-08-22 → Playlist, Inc. step and thereafter passes exclusively through licensing/holding entities: Sayre Holdings JP LLC (2006-12-13) → Mineral Lassen LLC (2015-11-18) → Intellectual Ventures Assets 125 LLC (2018-12-18) → AVInnov LLC (2019-02-06) → Cedar Lane Technologies Inc. (2019-10-17). Names carry the "Holdings / Assets / LLC" markers; none is shown to sell a product. (Reel/frame individualization not retrieved — see caveat.)

2. Known asserter in the chain — PRESENT. Intellectual Ventures is directly on the supplied list, and it appears twice by name (the "Intellectual Ventures Assets 125 LLC" assignee at 2018-12-18, plus the IV affiliate Sayre Holdings JP LLC per RPX). Cedar Lane Technologies is an established high-frequency plaintiff — its '489 assertions are catalogued in IPWatchdog filing roundups (e.g., against Dish Network in 6:20-cv-00947 and Walt Disney in 6:20-cv-00949) and by RPX. AVInnov LLC is the intermediate assertion vehicle.

3. Repeat correspondent across the chain — UNASSESSED / UNclear. I could not retrieve any recorded correspondent name or firm for any link, so I cannot test for recurrence. No finding either way. This is the single most valuable unchecked field; pulling the Assignment Center full record (which shows the filing attorney/firm per reel/frame) would likely resolve whether one firm ran the 2018→2019 IV→AVInnov→Cedar Lane sequence.

4. Cascading transfers — PRESENT. Three consecutive transfers in under 10 months: 2018-12-18 (IV Assets 125) → 2019-02-06 (AVInnov) → 2019-10-17 (Cedar Lane). An earlier cascade runs 2006 → 2015 → 2018 inside the IV family. Common-principal/correspondent confirmation is blocked by the missing correspondent data.

5. Pre-litigation transfer — PRESENT (timing approximate). The final assignment to the asserting entity, Cedar Lane Technologies Inc., is 2019-10-17, and Cedar Lane's first '489 complaints (E.D. Tex. 2:19-cv-00368, 2:19-cv-00369) sit in the 2019 docket year; the bulk of the 15-case campaign is 2020–2022. The transfer lands immediately before the assertion wave. (I could not pull exact filing dates for the 2019 Tex. cases, so the "within 6 months" test is met only approximately.)

6. Bankruptcy fire-sale — UNCLEAR / not established. No Chapter 7/11 record for PhatNoise surfaced. The company was reportedly acquired by Harman in August 2005 (RPX), which reads as a merger/acquisition rather than an insolvency sale — but the Playlist, Inc. assignment step muddies this and I cannot confirm the transaction structure.

7. Privateering — UNCLEAR. The asset unquestionably ends up with asserters, but I found no evidence that PhatNoise (or Harman) directed or benefited from the later assertions the way classic privateering requires. The 2005–2006 exits read more like outright disposals than a deniable enforcement program on the seller's behalf.

8. Defensive aggregator — NOT PRESENT. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. Its final custodian, Cedar Lane Technologies, is an active plaintiff, so the patent was not neutralized.

Verdict

NPE — high confidence.

The chain shows (a) a clean departure from an operating company that actually shipped an embodying product — PhatNoise's PhatBox, with "dynamic playlist-generation technology" — at the 2005-08-22 Playlist, Inc. step, and (b) a documented pass through Intellectual Ventures-affiliated vehicles (Sayre Holdings JP LLC, 2006-12-13; Mineral Lassen LLC, merged 2015-11-18; Intellectual Ventures Assets 125 LLC, 2018-12-18), then a rapid two-hop bounce to asserters (AVInnov LLC, 2019-02-06; Cedar Lane Technologies Inc., 2019-10-17) immediately preceding a 15-case assertion campaign. That is two or more strong signals (shell-entity transfer + known asserter + cascading pre-suit transfer), each anchored to specific recorded dates.

Caveats that a reviewer should close out: (i) reel/frame numbers and recorded correspondents were not retrievable this session and must be pulled from the USPTO Assignment Center before the repeat-correspondent signal can be scored; (ii) the Harman vs. Playlist, Inc. discrepancy (RPX "Harman, Aug 2005" vs. recorded "Playlist, Inc., 2005-08-22") is unresolved; and (iii) the "September 2006" date RPX gives for the IV transfer does not exactly match the recorded 2006-12-13 Sayre Holdings entry — one of the two sources is imprecise. The patent itself is expired (anticipated 2020-03-08), which bounds any remaining relief.

I'll research the prior-art citations for US 6,721,489 specifically. Let me run targeted searches.

Let me find the specific "References Cited" (backward citations) list on the face of US 6,721,489.

Let me try to surface the actual "References Cited" list on the face of the patent.

Prior-Art Analysis for US 6,721,489 B1 — Scope and Honest Limitations

Bottom line up front

I was unable to retrieve the "References Cited" (front-page / item (56)) list of US 6,721,489 B1. I therefore cannot honestly provide the requested deliverable — "for each reference cited on the face of the patent, full citation, dates, description, and the claim(s) it anticipates under §102" — because I do not have that reference list.

Everything the task asks me to look at ("each patent citation for 6721489") was not available to me in this session. The full patent text supplied to me is truncated inside the detailed description (it ends mid-sentence in the discussion of FIG. 11 / Table 1), so it contains no claims section and no citation list. My web searches returned (a) forward citations (later patents citing the '489), (b) citation lists belonging to other patents, and (c) unrelated subject matter. They did not return the examiner's "References Cited" / PTO-892 for the '489 patent.

Rather than fabricate a plausible-looking prior-art table, below I give: what I did verify, the fragments I found with explicit provenance caveats, the analytic candidates that track the verified claim language, and the exact sources needed to close this out.

1. "Citation" is four different things — and they matter differently

Before analyzing, note that "patent citations" conflates distinct buckets with different legal weight:

Because the '489 patent was filed 2000-03-08, it is governed by pre-AIA 35 U.S.C. §§ 102(a),(b),(e) and (g). A reference can anticipate under §102 only if it is prior art (generally before 2000-03-08, or an earlier-effective U.S. filing under §102(e)) and discloses every limitation of the claim at issue.

Contradiction flag: The task header states "Current Date: April 26, 2026," while my environment date is 2026-09-28. This was already flagged in the previously generated summary; nothing in the analysis below turns on it.

Identifier flag (repeated for safety): Search results retrieved the PDF of JP 6721489 B2 (a Hitachi magnetic-resonance-imaging patent, publication "2020.7.15"). That is not US 6,721,489 and must not be conflated with it. Also note that several hits containing the string "6721489" are USPTO EAST prior-art search logs in unrelated applications (e.g., a 2008 search history listing "6721489".pn.) — those are not citations in or against the '489 patent.

2. The one backward-looking citation fragment my search returned — with a heavy caveat

A Google Patents page for DE 4013410 A1 ("Abspielvorrichtung fuer eine audiospeicherplatte"), whose "Similar Documents" block lists US 6,721,489 B1 and US 6,772,212 B1 (the PhatNoise siblings), also rendered citation blocks reading:

• "Citations (4)" — US 4,603,412 A; DE 3424105 C2; US 4,779,252 A; US 4,853,914 A
• "Family Cites Families (19)" — beginning US 4,445,189 A; JPS 54-51735 A; DE 2826870 A1; JPS 55-129979 A; US 4,447,786 A; JPS 61-99984 A; US 4,841,506 A; US 4,872,151 A …

I cannot attribute these lists to US 6,721,489. The page's structure strongly suggests they belong to the DE application/family member, not to the '489. Presenting them as "the references cited on the face of the '489" would be a fabrication of provenance. I list them only because they were the only backward-looking citation data that surfaced, and so you can see exactly what I could and could not tie to the patent.

If any of them are of the same subject-matter family (several are "automatic selection / random play / preselected sequence" CD-player references), the most conceptually notable would be:

• US 4,779,252 A (U.S. Philips) — "Apparatus for automatically reproducing preferred selection from a record carrier" — a candidate on "automatic" playback selection.
• US 4,841,506 A (Pioneer) — "Random playing method for disk player."
• US 4,872,151 A — compact disc player capable of playing plural selections in a preselected sequence.

Important: none of these discloses comparing a track's properties to user-defined play-list criteria and automatically adding the track to the list. They automate playback, not list membership. So even if they are on the face of the '489 (unverified), they do not appear to anticipate the verified claim 1.

3. Forward citations (verified to cite the '489) — useful context, not §102 art

The following later documents were retrieved as citing US 6,721,489 B1 (Google Patents "Cited By" blocks). They post-date 2000-03-08 and cannot be §102 prior art against the '489 claims; I include them only to show the technological neighborhood and to distinguish them from the (missing) backward citations:

• US 2004/0078382 A1 / (related family) — "Adaptive menu system for media players"
• US 2004/0078383 A1 — "Navigating media content via groups within a playlist" (Microsoft)
• US 11,825,174 B2 — "Remote playback queue" (Sonos-family)
• EP 3,690,671 A1 — "Playlist update in a media playback system"
• WO 2008/002954 A3 — "Multimedia device integration system"
• US 7,797,446 / US 8,103,793 (Apple) — "Method and system for updating playlists"; US 7,827,259 — "Method and system for configurable automatic media selection"; US 7,860,830 — "Publishing, browsing and purchasing of groups of media items"

These later filings (Apple's "Method and system for updating playlists," etc.) describe criteria/rule-based automatic playlist population — i.e., downstream of, and consistent with, the '489 disclosure. They are evidence of the field's development, not invalidating art.

4. The only prior art actually named in the '489 specification

The Background of the Invention names exactly one piece of prior art:

"An example of a digital music player is the Rio digital music player from Diamond Multimedia. This music player includes a flash memory for storing music and electronics for playing the music."

• Relevance: discloses a portable digital music player with writeable flash storage — i.e., the environment, not the claimed method.
• §102 mapping: It does not disclose "comparing a set of one or more properties of a first track to criteria of a first play list" and "automatically adding said first track … if said set of properties … satisfy said criteria." It cannot anticipate the verified claim 1. At most it supports a background/§103 framing.

The specification also describes the problem the invention addresses ("The effort to move a large number of files into the appropriate play lists is time consuming… This two step approach—(1) downloading music files and (2) moving the downloaded files to one or more play lists—is cumbersome"). That passage is the patentee's own admission of what the prior art did — manual play-list population — which is precisely the gap the claimed "automatic" step fills.

Two same-day, commonly-owned applications are named in the cross-reference section — Ser. No. 09/521,182 ("Audio/Visual Server") and Ser. No. 09/521,186 ("Vehicle Sound System"). They are incorporated by reference, and (same inventive entity, same filing day) are not §102 art against the '489. They are relevant only for claim-construction/support cross-references.

5. What the verified claim language permits me to say about § 102

From the previously generated section, claim 1 is verified verbatim:

"1. A method for updating a play list, comprising the steps of: comparing a set of one or more properties of a first track to criteria of a first play list; and automatically adding said first track to said first play list if said set of properties of said first track satisfy said criteria of said first play list."

From this, an anticipating reference under §102 would need to disclose, in a single reference: (i) a track having properties; (ii) a play list having criteria (a rule/test, per the spec's definition); and (iii) automatic addition of the track to the list upon satisfaction of the criteria, with no human selection of the track for the list.

I found no reference in the retrieved material that meets all three with respect to amassed digital audio/visual tracks. That is consistent with the examiner having allowed the case, but I cannot confirm what art the examiner actually weighed.

I did not verify the text of claims 2–51. The '489 has 51 claims (per the Official Gazette entry), and the dependent claims very likely narrow the "properties" to ID3 tag fields (FIG. 16 — tag/title/artist/album/year/comment/genre), to similarity information stored in a database (Internet server 130 or computer 124), to the detect-then-compare variant, to the plurality-of-play-lists variant, and to the prompt-to-confirm alternative in step 1412. Until those claims are pulled verbatim, no claim-by-claim §102 chart is possible. Any such chart produced now would be speculative.

6. What I could not do, and the definitive sources to fix it

I could not:

1. Retrieve the front-page (56) "References Cited" list for US 6,721,489 B1.
2. Retrieve the file-wrapper IDS / PTO-892 (what the examiner actually cited, and what was used in any rejection).
3. Confirm the verbatim text of claims 2–51, which is a prerequisite for any §102 anticipation mapping beyond claim 1.

To close this out, pull these four records (each will give you the exact cited-reference list the task requires):

1. USPTO Patent Center → US 6,721,489 → "Documents & Transactions" → find the PTO-892 ("Notice of References Cited") and any IDS/PTO-1449. Application no. 09/521,874.
2. USPTO Patent Public Search (Patent Public Search / PatFT) → US 6,721,489 B1 → the "Referenced By" / "References Cited" fields on the bibliographic page.
3. Google Patents → https://patents.google.com/patent/US6721489B1/en → the "Patent Citations (n)" and "Non-Patent Citations" sections (the supplied text was cut off before these).
4. International Search Report for PCT/US2001/040209 (family member WO 01/67753 A1) — the ISA's cited references are a close proxy for the prior art the applicants faced on the parallel international filing.

Once you have those, I can produce exactly the deliverable requested — a per-reference table of (full citation / publication & filing dates / brief description / the claim(s) each reference potentially anticipates under §102), mapped against the now-verifiable claim set.

7. Caveats I want on the record

• Provenance of §2's lists is unverified. They appeared adjacent to the '489 in a search result but most plausibly belong to DE 4013410 A1. Do not treat them as the '489's citations without checking the front page.
• Forward citations are not prior art against the '489 and are included only as context.
• Do not conflate US 6,721,489 with JP 6721489 B2 (Hitachi MRI) or with the USPTO EAST search-string "6721489" logs found in unrelated files.
• Anticipation vs. obviousness: an "automatic playlist" reference that lacks user-defined criteria may still be §103 material when combined, but that is a different analysis than the §102 mapping the task requests. I have not attempted a §103 combination theory here, and would not do so without the actual cited-record and the full claim set.
• Search limitation, not a finding: statements above like "I found no reference that anticipates" mean the material available to me contained none — not that none exists in the record.

I'll research the prior art landscape before building the obviousness analysis.

Let me verify the specific prior-art references and look for art cited on the face of the patent.

Obviousness Analysis Under 35 U.S.C. § 103 — US 6,721,489 B1 ("Play list manager")

Note on date discrepancy (carried forward): the task prompt states April 26, 2026; my environment sets today as September 28, 2026. I flag it rather than silently choosing.

Note on the "Prior Art section": the supplied page text does not include a discrete, labeled "Prior Art" heading with a citation list. What it does include is (a) the patent's own "Prior art keywords" line ("play list, track, criteria, tracks, properties") and (b) the prior-art references named earlier in this analysis as the art set from IPR2020-00006 on the sibling playlist patent US 7,173,177 — namely Looney (5,969,283), DeMartin (6,226,672), and Cluts (5,616,876). I build the § 103 case on those three, verified against their own texts, and I flag where verification is incomplete. I could not open the '489 front-page "References Cited" list directly.

Identifier caution (in addition to the JP 6721489 B2 warning already given): the Sonos v. Google district-court briefing retrieved in the prior sections refers to "the '489 patent" whose claims concern determining content availability across online sources and notification/price thresholds. That is not US 6,721,489 — the claim 1 subject matter does not match. Treat that " '489" as a different document unless verified; do not conflate.

1. Legal framework

US 6,721,489 was filed 2000-03-08, so pre-AIA § 103(a) governs. The analysis uses the Graham v. John Deere factors as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007): (1) scope and content of the prior art, (2) differences between the prior art and the claims, (3) level of ordinary skill, (4) secondary considerations. Under KSR, a combination is obvious where the elements were known, the field was one of common improvement, and there existed a design need or market pressure with predictable results — no explicit teaching, suggestion, or motivation is required.

Skill level: a POSITA here would have a bachelor's degree in computer science/electrical engineering plus ~2 years' experience in digital media management, or equivalent — i.e., someone who in 2000 knew MP3/ID3 metadata, relational or flat-file media databases, and GUI-based media players. This is a crowded, mature art at the critical date.

Status caveat relevant to remedy, not to validity: the patent is "Expired – Lifetime," anticipated expiration 2020-03-08. Expiration does not affect the § 103 analysis, but it means a validity challenge would be litigated in the past-damages posture described in the earlier sections.

2. The claim(s) at issue and what I can verify

Verified verbatim (claim 1, USPTO Official Gazette):

"1. A method for updating a play list, comprising the steps of:
comparing a set of one or more properties of a first track to criteria of a first play list; and
automatically adding said first track to said first play list if said set of properties of said first track satisfy said criteria of said first play list."

Decomposed:

• (A) comparing one or more stored properties of a track against criteria of a play list;
• (B) automatically (no human action) adding the track to that list when the properties satisfy the criteria.

Not verified: the wording of claims 2–51. Per the earlier sections, I will not reconstruct them. Based on the specification, the likely independent-claim groupings are (i) the detect-then-compare variant ("comparing is performed automatically in response to the step of detecting [that the first track is available]"), (ii) the multi-list variant ("comparing properties for a first track to play list criteria for a plurality of play lists … adding … to each of the play lists having play list criteria satisfied"), and (iii) the predefined/"one-click" variant (FIG. 20). I analyze all three below but label them as inferred, not verified.

3. Prior art relied upon

Sources: US 6,721,489; Looney '283 PDF; Looney '539 PDF; Cluts '876; DeMartin '672.

What each reference teaches the two limitations:

Looney '283/'539 — the strongest reference. The songs in the database carry category flags ("title, artists, date, speed, dance characteristics, subjective energy level and music style"). The user selects a category and a time limit; the code "search[es] the database for songs until the time is up" → "FIND SONG THAT MATCHES SPEED AND MAIN CATEGORY" → "MIX UP SONGS AND DISPLAY IN PLAYLIST." Looney also shows the system detecting and importing newly available tracks: "INSTRUCT TO INSERT MOAEC CD ROM / LIST ALL *.MPG FILES … / COPY ALL MPG FILES OVER TO MOAEC DIRECTORY, IF NOT ALREADY THERE / COMPARE SONGS ON DISK TO DATA RECORDS / UPDATE M/DATA DATABASE WITH NEW SONG RECORDS." And it discloses playing the resulting list ("PLAY SONGS AND COLORS THAT MATCH IN SEARCHLIST") plus saving/loading playlists (FIG. 10). Looney's per-category buttons are, functionally, predefined one-click playlists.

Cluts '876 — the richest "compare" teaching. Cluts claims and describes: storing items plus editorial data; responding to a user signal by "creating … a list of proposed new programming information items on the basis of said editorial data associated with said initial programming information item"; identifying items "having similar editorial data"; and "adding, in response to a third input signal …, said proposed new programming information items to a playlist." So Cluts expressly teaches (A) — criteria/property comparison driving list population — and teaches the user-confirmation alternative of the '489 spec (the "are these OK?" watch panel at step 1412), but not unconfirmed automation.

DeMartin '672 — the library/network context. DeMartin teaches reading track-identity data from a user's media library, matching it against a server database, generating a playlist for that library's contents, translating it to a control file, and transferring it to the playback device. It supplies the networked metadata-database and playlist-distribution underpinnings for claims drawn to server-side properties/similarity data.

4. Grounds of rejection

Ground 1 — Claim 1 obvious over Looney '283 (and anticipated by it)

• (A) "comparing a set of one or more properties … to criteria": Looney's "FIND SONG THAT MATCHES SPEED AND MAIN CATEGORY" is exactly a comparison of stored song properties (categories/speed) against selected criteria.
• (B) "automatically adding … if … satisfy": Looney's machine compiles the playlist itself ("MIX UP SONGS AND DISPLAY IN PLAYLIST") — no per-song user action. Looney FIG. 8's "COPY ALL … IF NOT ALREADY THERE" further shows automated population.
• Difference, if any: Looney's compiling is user-initiated each time; claim 1 says only "updating a play list," which reads on re-running the search when the library changes. On the broadest reasonable reading, claim 1 is anticipated; at minimum it is obvious.

Ground 2 — Detect-then-compare variant obvious over Looney '283

Looney FIG. 8 (insert disc → enumerate new files → compare to data records → update database) discloses detecting that tracks have become available. Combining Looney's import/compare flow with its category-search/playlist-mix flow yields "comparing … performed automatically in response to detecting" the new track. A POSITA monitoring a media library has every reason to re-run the category query when new files appear (that is precisely the two-step drudgery the '489 Background criticizes). Routine automation of a known manual step.

Ground 3 — Multi-list variant obvious over Looney '283 + Cluts '876

Looney maintains multiple category schemes and multiple saved playlists; Cluts expressly contemplates applying the same similarity/attribute query to populate lists. Running one track's property set against N stored lists and appending on match is the straightforward, predictable extension of Looney's single-query search. Motivation: the user who maintains several category-based lists wants each kept current without per-list manual work.

Ground 4 — Predefined/"one-click" list generation obvious over Looney '283 + Cluts '876

• Looney: a category button ("Jazz," "Rock," …) + a time budget auto-generates the playlist → the '489 "one click" buttons of GUI 1200 / FIG. 20.
• Cluts: "more style" auto-generates "a list of other programs that share the same style." Both teach "receiv[e] a request to generate a play list having predefined … criteria, determin[e] which tracks … have properties satisfying the … criteria and automatically add[]."
  Merely placing these behind dedicated buttons is a predictable UI choice.

Ground 5 — Dependent claims (inferred; property-source and server-database limitations)

• ID3-tag-as-properties: the '489 spec itself calls FIG. 16 "an exemplar ID 3 tag," and ID3v1 (title/artist/album/year/comment/genre) was a de facto standard from 1996. Any music-organizer art (Looney's category-flag records; Cluts' editorial records) combined with the well-known ID3 standard renders such a claim obvious. Nothing in the '489 spec suggests the ID3-field mapping was the invention.
• Properties/similarity stored in a database on a computer or Internet server: Cluts places the editorial/style data on a headend server and administrative server; DeMartin matches track identity against a server database. These render obvious any claim to where the properties live.
• Prompt-to-confirm alternative (step 1412): disclosed almost verbatim by Cluts' "yes/no" confirmation of the proposed list.
• Auto-play after list creation: Looney ("PLAY SONGS AND COLORS THAT MATCH IN SEARCHLIST") and Cluts (playlist playback) both disclose it.

5. Motivation to combine (KSR)

1. Same field, same problem. All three references are digital media organizers/players; Looney and Cluts are both cited in Looney's own reference list, showing they were known to the same artisans.
2. Express design need in the art — and in the '489 Background itself. The '489 patent frames its problem as: "The effort to move a large number of files into the appropriate play lists is time consuming. … This two step approach—(1) downloading music files and (2) moving the downloaded files to one or more play lists—is cumbersome." That is a stated motivation to automate exactly the combination, and it is the applicant's own characterization of the prior-art gap.
3. Predictable results. Automating a comparison-and-append loop produces the expected, stable result; nothing unpredictable or newly discovered happens.
4. Combination of known techniques. Looney supplies criteria-based automatic list building; Cluts supplies property/similarity comparison and the confirm/auto choice; DeMartin supplies the networked library/metadata plumbing. Combining is "a combination of familiar elements according to known methods."
5. Obvious to try. Once a machine can already rank/select tracks by stored attributes on command, having it re-evaluate newly added tracks without a command is a design choice between two known options (manual re-run vs. background re-run), with the obvious benefit of keeping lists current.

6. Expected counterarguments and rebuttals

• "Looney requires user selection of a category; '489 requires no human action." Rebutted by (i) claim 1's actual words do not require the criteria to be machine-generated — only the adding is "automatically"; and (ii) Looney's FIG. 8 shows automatic import/compare, and its FIG. 5 shows machine compilation once criteria are set. Cluts + Looney together close any residual gap.
• "Cluts requires a third input signal (user confirmation) before adding." True, and it is why Cluts alone does not anticipate claim 1 — but it is (a) a claim-differentiating detail at most for the confirm-variant dependent claim, and (b) an obvious design choice to omit, since the same specification (step 1412) treats prompting as optional. Where the difference is "drop the confirmation step," the result is predictable and the motivation (reduce user effort) is express.
• "Teaching away." None of the three references disparages automatic list population; Looney's entire premise is machine-assisted playlist assembly. A teaching-away argument is not available on this record.
• "The references are non-analogous." They are all in media-library/playlist management — plainly analogous under the field-of-invention and problem-solved tests.

7. Secondary considerations

No evidence of nexus, unexpected results, industry praise, long-felt need, or failure of others was located in the record reviewed. Commercial exploitation (the PhatNoise car-audio "digital jukebox") is a licensing/embodiment story, not proof that the claimed automation was non-obvious; absent a nexus between the objective evidence and the claim limitations, secondary considerations carry little weight here. Conversely, the crowded 1998–2000 art window (Looney, Cluts, Abecassis, DeMartin, and others all pre- or near-dating the filing) reinforces an obviousness posture.

8. What I could not verify (do not over-rely)

1. Claims 2–51 verbatim. Only claim 1 is verified. The dependent-claim analysis in Ground 5 is predictive, keyed to the specification's own disclosures, and must be confirmed against the granted claims.
2. DeMartin '672 filing date. Issued 2001-05-01, after the '489 priority date, so it is prior art only under § 102(e) if its filing date precedes 2000-03-08. Confirm the filing date before relying on it; if it post-dates the priority date it drops out entirely, and Grounds 3/5 must rest on Looney + Cluts alone.
3. Additional high-value candidates I could not pull in this session (titles/dates only — verify before use):
   • US 6,047,268, Bartoli, "User input-based play-list generation and playback system" — issued 2000-04-04; highly on-point by title and likely § 102(e) art. This could be a stronger primary reference than Looney for the "user input → playlist generation" framing.
   • US 6,192,340, Abecassis, "Integration of music from a personal library with real-time information" — 1999-10-19 → 2001-02-20.
   • US 6,256,638 / US 6,028,190 and the like — not verified at all; listed only as leads.
4. Looney '283 claim language — I verified the specification/figure legends (the strongest passages) but not the verbatim claims; if you intend an anticipation theory, punch the claim chart against Looney's actual claims.
5. No litigation/PTAB estoppel relevance: as previously established, there are no IPR/PGR/CBM proceedings against '489, so no prior claim construction binds this analysis and no § 315(e)(2) estoppel limits these grounds.

Bottom line

On the record assembled, claim 1 is at minimum obvious — and arguably anticipated — over Looney US 5,969,283, and the remaining groups (detect-then-compare, multi-list, one-click/predefined, ID3-property, and prompt-to-confirm) are obvious over Looney in view of Cluts, with DeMartin supplying the networked-library/metadata context for server-side-property claims. The motivation is not merely inferable; the '489 specification's own Background identifies the exact drudgery that the Looney/Cluts combination removes, and KSR supplies the rationale. The principal open items are (i) confirming the unverified claim language, (ii) confirming DeMartin's § 102(e) date, and (iii) pulling US 6,047,268 (Bartoli), which by title may be the single best primary reference.