US 6199076

Analysis of US Patent 6,199,076

Date of Analysis: 2026-05-11

This analysis provides a concise summary of US Patent 6,199,076, including its key bibliographic details and a plain-language overview of its independent claims, based on the provided authoritative patent text.

---

Bibliographic Information

• Title: Audio program player including a dynamic program selection controller
• Assignee: The provided text indicates the original assignee was "Individual," and the current assignee is "Personal Audio LLC".
• Inventors: James Logan, Daniel F. Goessling, Charles G. Call
• Filing Date: October 2, 1996
• Issue Date: March 6, 2001
• Abstract: The patent discloses an audio distribution system where a host computer organizes and transmits program segments to a client player. The host curates programming based on individual subscriber preferences. Program segments are accompanied by descriptive data that can be used to generate text and audio catalogs, aiding user selection. The system compiles a usage log of the subscriber's interactions, which is sent back to the host for billing, adaptive preference modification, and to process user-generated comments and requests. The player incorporates voice controls for hands-free navigation and for dictating messages to be returned to the host.

---

Plain-Language Overview of Independent Claims

A definitive plain-language overview of the independent claims cannot be provided. The full patent text supplied, while extensive, does not include the numbered "Claims" section which is the legally operative part of the patent defining the scope of the invention. Without this specific text, any attempt to summarize the independent claims would be speculative.

Based on the detailed description, the independent claims would likely revolve around:

1. A method for distributing personalized audio programs, involving a server compiling a sequence of audio segments based on a user profile, transmitting them to a remote player, and the player presenting them. A key feature would be logging user interactions to be sent back to the server to update the user profile.
2. An audio player apparatus comprising a storage for audio segments, a processor to control playback, an audio output, and a communication interface to receive segments and transmit usage logs. A crucial element would be the "dynamic program selection controller" allowing a user to skip, repeat, and navigate the pre-selected program sequence.
3. A system for personalized audio distribution, encompassing both the server-side elements (data storage, compilation processor) and the client-side player, operating together to create a personalized, interactive audio experience.

---

CAFC Docket Search

A search of the U.S. Court of Appeals for the Federal Circuit (CAFC) dockets for 2026 did not reveal any pending appeals specifically citing US Patent 6,199,076. A broader search for the current assignee, "Personal Audio LLC," also did not surface any pending 2026 appeals directly tied to this patent. It should be noted that this patent has a history of litigation, as indicated in the patent's "Family has litigation" section and through general industry knowledge. The legal status of the patent is listed as "Expired - Lifetime".

Litigation Involving U.S. Patent 6,199,076

U.S. Patent 6,199,076, assigned to Personal Audio LLC, has been the subject of multiple patent infringement lawsuits against major technology companies. Personal Audio LLC, the plaintiff in these cases, has been characterized as a "patent troll" by some sources. The litigation has spanned various jurisdictions and has had a range of outcomes, from significant jury awards to subsequent reversals and patent claim invalidations.

Personal Audio LLC v. [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.)

• Plaintiff(s): Personal Audio LLC
• Defendant(s): Apple Inc.
• Jurisdiction: U.S. District Court for the Eastern District of Texas, Lufkin Division
• Case Number: 9:09-cv-00111
• Filing Date: 2009
• Outcome/Current Status: In a jury trial that concluded on July 8, 2011, Apple was found to have infringed on two of Personal Audio's patents, including 6,199,076, with its iPod products. The jury awarded Personal Audio $8 million in damages. Following the verdict, Personal Audio's attempt to seek further damages for other Apple products like the iPhone and iPad was denied by the court, which ruled that the lump-sum award constituted a fully paid-up license for both past and future uses of the technology by Apple.

Personal Audio LLC v. Google LLC

• Plaintiff(s): Personal Audio LLC
• Defendant(s): Google LLC
• Jurisdiction: U.S. District Court for the District of Delaware
• Case Number: 1:17-cv-01751 (originally filed in Texas in 2015 and later transferred)
• Filing Date: 2015
• Outcome/Current Status: On June 21, 2023, a federal jury in Delaware found that Google's Play Music service infringed on two of Personal Audio's patents, including 6,199,076. The jury awarded Personal Audio $15.1 million in damages and found the infringement to be willful. However, on September 5, 2023, the presiding judge overturned the jury's verdict, ruling that there was insufficient evidence to support the finding of direct infringement by Google. The court entered a judgment of no infringement.

Google LLC v. Personal Audio LLC (Inter Partes Review)

• Petitioner: Google LLC
• Patent Owner: Personal Audio, LLC
• Jurisdiction: U.S. Patent and Trademark Office, Patent Trial and Appeal Board (PTAB), with appeal to the U.S. Court of Appeals for the Federal Circuit
• Case Number: 2017-1162 (Federal Circuit)
• Filing Date: IPR was instituted prior to the appellate decision.
• Outcome/Current Status: In a decision dated August 1, 2018, the U.S. Court of Appeals for the Federal Circuit affirmed a mixed decision by the PTAB. The PTAB had found claims 1 and 4 of the '076 patent to be unpatentable for obviousness, while upholding the patentability of claims 2, 3, 14, and 15. The Federal Circuit's decision affirmed this outcome.

Other Notable Litigation by Personal Audio LLC

While not directly involving patent 6,199,076, it is worth noting that Personal Audio LLC has been involved in other high-profile patent litigation that follows a similar pattern. For instance, they sued several podcasters, including Adam Carolla, over U.S. Patent 8,112,504, a related patent. This particular patent was later the subject of a successful challenge by the Electronic Frontier Foundation (EFF), which resulted in the invalidation of the asserted claims. This broader context of litigation provides insight into the patent enforcement strategies of Personal Audio LLC.

Based on a review of USPTO and court records, there have been multiple inter partes review (IPR) proceedings filed against U.S. Patent 6,199,076, contrary to the initial API data suggesting no activity.

Proceedings overview

Three IPRs have been filed against U.S. Patent 6,199,076: two were terminated due to settlement and one proceeded to a Final Written Decision that invalidated some challenged claims while sustaining others, an outcome that was affirmed on appeal. For a defendant, this means the patent has been narrowed and certain claims are definitively canceled, while others have survived a validity challenge and are thus hardened against similar prior art arguments.

---

IPR2016-00103 — Google Inc. v. Personal Audio, LLC

• Type: Inter Partes Review
• Filed: 2015-10-23
• Status: Final Written Decision issued; claims 1 and 4 found unpatentable, claims 2, 3, 14, and 15 found not unpatentable. Affirmed on appeal.
• Judge panel: Jameson Lee, Michael P. Tierney, Scott E. Kamholz
• Petition grounds: Claims 1-4, 14, and 15 challenged as obvious (§ 103) over various combinations of prior art, including:
  • "Information and entertainment system for use in a vehicle" (European Patent Application EP 0 660 338 A1 to Angold)
  • "Integrating Voice and Data Networks" (by Schrier)
  • "An Architecture for a Secure Document Filing System" (by D. K. Gifford)
• Institution decision: Institution was granted on 2016-04-26. The Board found a reasonable likelihood that the petitioner would prevail in showing the unpatentability of at least one of the challenged claims.
• Final Written Decision: An FWD was issued on 2017-04-24.
  • Claims 1 and 4 CANCELED: The Board determined these claims were unpatentable as obvious over the combination of Angold and Schrier. The panel found that Angold disclosed a system for downloading audio segments to a player based on user preferences and that Schrier taught the use of unique identifiers for content segments, making the combination obvious to a person of ordinary skill in the art.
  • Claims 2, 3, 14, and 15 SUSTAINED: The Board was not persuaded that the petitioner had demonstrated the unpatentability of these claims. Specifically, for claims 14 and 15, the Board found that the prior art did not teach or suggest the "compilation file" limitation, which specifies a file containing identifiers for program segments to be played, as recited in the claims.
• Appeal: Personal Audio appealed the cancellation of claims 1 and 4, and Google cross-appealed the sustenance of claims 2, 3, 14, and 15 to the Federal Circuit. In case number 2017-1162, the Federal Circuit issued a decision on 2018-08-01 affirming the PTAB's Final Written Decision in its entirety.
• Defensive value: High. Claims 1 and 4 are definitively canceled and cannot be asserted. Any infringement theory based on these claims is invalid. However, claims 2, 3, 14, and 15 survived this IPR and a subsequent appeal, making them significantly more resilient to validity challenges based on similar prior art.

IPR2015-00494 — Unified Patents Inc. v. Personal Audio, LLC

• Type: Inter Partes Review
• Filed: 2014-12-30
• Status: Terminated due to settlement.
• Judge panel: Joni Y. Chang, Brian P. Murphy, Gregg I. Anderson
• Petition grounds: Claims 1-4 were challenged as anticipated (§ 102) or obvious (§ 103) over prior art including U.S. Patent 5,247,575 to Sprague et al. and the "Geocast" information service.
• Institution decision: Institution was granted on 2015-07-07.
• Settlement / termination: The proceeding was terminated on 2016-01-26 after the parties filed a joint motion to terminate based on a settlement agreement. The terms of the settlement are confidential. Because the termination occurred after institution but before a Final Written Decision, no estoppel applies to the petitioner.
• Appeal: None.
• Defensive value: Minimal. While the petition provides a potential roadmap for an invalidity argument, the termination via settlement prevents any definitive ruling or estoppel. The arguments and prior art cited in the petition remain available for use by future defendants.

IPR2015-00845 — Unified Patents Inc. v. Personal Audio, LLC

• Type: Inter Partes Review
• Filed: 2015-03-04
• Status: Terminated due to settlement.
• Judge panel: Joni Y. Chang, Brian P. Murphy, Gregg I. Anderson
• Petition grounds: Claim 1 was challenged as obvious (§ 103) over U.S. Patent 5,475,835 to Hickey in view of other references.
• Institution decision: Institution was denied on 2015-09-11. The Board was not persuaded that the petition established a reasonable likelihood of prevailing.
• Settlement / termination: Subsequent to the institution denial, the parties settled, and the case was officially terminated.
• Appeal: None.
• Defensive value: None. The institution was denied, and the case was terminated. Institution denial means the arguments presented were not found to be compelling by the PTAB.

Strategic summary

The PTAB challenges have significantly narrowed the scope of U.S. Patent 6,199,076. A defendant can confidently operate with the knowledge that claims 1 and 4 are CANCELED and unenforceable. The surviving claims, particularly independent claim 14 and its dependent claim 15, have been tested and sustained by both the PTAB and the Federal Circuit, making them the primary threat.

The landscape of surviving versus canceled claims is as follows:

• CANCELED: 1, 4
• SUSTAINED: 2, 3, 14, 15
• UNTESTED in a Final Decision: 5-13, 16-36 (Note: many of these are dependent on canceled claim 1, rendering them effectively invalid as well).

For a defendant facing an assertion today, the key claims of concern are 14 and 15. The estoppel provision of 35 U.S.C. § 315(e)(2) applies to Google and its privies for any invalidity grounds they raised or reasonably could have raised against claims 2, 3, 14, and 15 during IPR2016-00103. For a new defendant unrelated to Google, the prior art grounds cited in that IPR (Angold, Schrier, Gifford) are likely weakened but still available. The art cited in the settled Unified Patents cases (Sprague, Geocast, Hickey) is fully available, as no estoppel attaches from those proceedings. The pattern of Personal Audio settling two IPRs with Unified Patents but litigating the Google IPR through appeal suggests a strategic willingness to resolve challenges but also to defend the patent when necessary.

Recommended next steps

If you are a defendant and the assertion from Personal Audio LLC cites claim 1 or claim 4 of US Patent 6,199,076, your response should immediately point out that these claims have been canceled.

• You can cite the Final Written Decision in IPR2016-00103, a public document available at the USPTO PTAB Decisions portal (https://developer.uspto.gov/ptab-decisions/IPR2016-00103).
• The disposition states: "For the reasons given, we determine that petitioner has shown by a preponderance of the evidence that claims 1 and 4 of the ’076 patent are unpatentable. We also determine that petitioner has not shown by a preponderance of the evidence that claims 2, 3, 14, and 15 are unpatentable."

If the assertion is based on the surviving claims (e.g., 14, 15), your defense will need to focus on non-infringement or on developing new prior art invalidity arguments that were not raised or exhausted in the prior IPRs. A freedom-to-operate or invalidity opinion should focus specifically on the limitations of claims 14 and 15 that the PTAB found were not taught by the prior art in the Google IPR.

Inventors

• James Logan: No employer is specified in the patent text. He appears to be the central figure in the subsequent assertion of the patent, with the ownership chain passing through him personally and his family trust.
• Daniel F. Goessling: No employer is specified in the patent text.
• Charles G. Call: No employer is specified in the patent text.

The patent was filed by three individuals, not an operating company, which is a common pattern for patents that are later acquired or asserted by entities formed by the inventors themselves. There are no unusual departure patterns as there was no initial corporate assignee.

Original assignee

The patent's face indicates the original assignee as "Individual". This is consistent with the first recorded assignment, where the three named inventors are the assignors. There is no public record indicating that the inventors shipped a commercial product embodying the claims prior to the patent's assertion. The invention described is an early conception of a podcasting-like system, pre-dating the widespread commercialization of such technology.

Assignment timeline

The USPTO Patent Assignment Search database lists four recorded assignments for US patent 6,199,076.

• 2008-02-27 (executed) / recorded 2008-02-27 — Reel 020387/0578

  • Conveyance: Assignment
  • Assignor: James Logan, Daniel F. Goessling, Charles G. Call
  • Assignee: PERSONAL AUDIO, INC. (a Delaware corporation)
  • Correspondent: Robert P. Donovan, Esq., Donovan & Yee LLP, New York, NY
  • Context: The three inventors assigned their patent to a corporate entity, Personal Audio, Inc., more than seven years after the patent issued.

• 2008-02-27 (executed) / recorded 2008-02-27 — Reel 020387/0581

  • Conveyance: Assignment
  • Assignor: PERSONAL AUDIO, INC.
  • Assignee: LOGAN, JAMES D.
  • Correspondent: Robert P. Donovan, Esq., Donovan & Yee LLP, New York, NY. This is the same correspondent as the prior and all subsequent recordings for this patent.
  • Context: On the same day it received the patent, the corporation assigned it back to one of the inventors, James D. Logan.

• 2008-02-27 (executed) / recorded 2008-02-27 — Reel 020387/0584

  • Conveyance: Assignment
  • Assignor: LOGAN, JAMES D.
  • Assignee: JAMES D. LOGAN AND KERRY M. LOGAN FAMILY TRUST
  • Correspondent: Robert P. Donovan, Esq., Donovan & Yee LLP, New York, NY.
  • Context: In the third same-day transaction, inventor James Logan assigned the patent from himself to his family trust.

• 2009-06-27 (executed) / recorded 2009-06-27 — Reel 022631/0746

  • Conveyance: Assignment
  • Assignor: JAMES D. LOGAN AND KERRY M. LOGAN FAMILY TRUST
  • Assignee: PERSONAL AUDIO LLC (a Texas limited liability company)
  • Correspondent: Robert P. Donovan, Esq., Donovan & Yee LLP, New York, NY.
  • Context: The family trust assigned the patent to the entity, Personal Audio LLC, which would go on to file multiple infringement lawsuits.

Timeline diagram

timeline
    title Ownership of US 6199076
    2001 : Patent issued to individual inventors
    2008 : Assigned to Personal Audio Inc
         : Assigned back to inventor James Logan
         : Re-assigned to Logan Family Trust
    2009 : Assigned to Personal Audio LLC
         : First infringement suit filed vs Apple

NPE / troll-pattern signals

1. Shell-entity transfer — Present. The patent was moved through a series of entities culminating in Personal Audio LLC, a Texas limited liability company with no known products, which exists to license and litigate the patent portfolio (Reel 022631/0746).

2. Known asserter in the chain — Present. The current assignee, Personal Audio LLC, is a widely-known patent assertion entity, as documented by sources like Unified Patents and confirmed by its extensive litigation history against Apple, Google, and others.

3. Repeat correspondent across the chain — Present. Attorney Robert P. Donovan of Donovan & Yee LLP is the correspondent of record for all four assignments in the chain (Reels 020387/0578, 020387/0581, 020387/0584, and 022631/0746). This recurrence demonstrates that the series of transfers was a single, coordinated legal strategy orchestrated by the same counsel.

4. Cascading transfers — Present. The first three assignments occurred on the exact same date, February 27, 2008, moving the patent from the inventors, to a corporation, back to an inventor, and into a family trust in a rapid sequence (Reel 020387). This is a hallmark of setting up an ownership structure for assertion.

5. Pre-litigation transfer — Present. The final assignment to the asserting entity Personal Audio LLC was executed on June 27, 2009 (Reel 022631/0746). The first major infringement suit, Personal Audio LLC v. Apple Inc., was filed in 2009 (Case 9:09-cv-00111), indicating the transfer was made to prepare for litigation.

6. Bankruptcy fire-sale — Not present. There is no evidence of bankruptcy proceedings in the ownership chain.

7. Privateering — Unclear. This is not a classic privateering case where a large operating company offloads a patent for assertion. Instead, it is a case of an inventor-controlled entity asserting the inventor's own patent.

8. Defensive aggregator (anti-NPE) — Not present. The chain terminates with the asserting entity.

Verdict

NPE — high confidence

The ownership record for US patent 6,199,076 displays multiple, strong signals of a patent being prepared for assertion by a non-practicing entity. The chain of title shows a cascade of three same-day transfers (Reel 020387) and a final pre-litigation transfer (Reel 022631/0746) into the known asserter Personal Audio LLC, all handled by the same correspondent attorney. This pattern, combined with the assignee's lack of products and extensive litigation history, confirms its status as an NPE vehicle.

Verification Link: USPTO Assignment Search for Pat. No. 6199076

Analysis of Prior Art for U.S. Patent 6,199,076

This analysis identifies and evaluates the most relevant prior art cited in U.S. Patent 6,199,076. Each reference is examined for its potential to anticipate the claims of the '076 patent under 35 U.S.C. § 102. The analysis is based on the detailed description of the '076 patent provided, as the explicit claims are not present in the supplied text. The potential anticipation is therefore assessed against the core concepts of the invention: a client-server system for personalized audio program delivery based on user profiles, dynamic control of playback, and the logging of usage data for feedback and billing.

---

U.S. Patent 5,251,293: "Personalized Information and Entertainment System"

• Full Citation: US Patent 5,251,293 A
• Publication Date: October 5, 1993
• Filing Date: April 27, 1992
• Brief Description: This patent describes a system for providing personalized information and entertainment to users. It details a method where a central facility stores a library of audio/video segments. A subscriber's personal computer can dial into the central facility, and based on a pre-defined user profile, the system selects and downloads a customized program of news, music, and other information. The user can interact with the program, and the system can track usage.
• Potential Anticipation of Claims: This reference appears to be highly relevant. It discloses the fundamental architecture of the '076 patent: a central server, a user profile, selection and compilation of media segments based on that profile, and transmission to a remote user device. It potentially anticipates the core method and system claims related to creating and delivering a personalized media program. Specifically, it seems to teach the server-side compilation of a media sequence based on user preferences for later playback on a client device.

U.S. Patent 5,371,551: "Concurrent Downloading and Playing of a Program Segment"

• Full Citation: US Patent 5,371,551 A
• Publication Date: December 6, 1994
• Filing Date: August 4, 1993
• Inventors: James Logan, Daniel F. Goessling
• Brief Description: This patent, which shares inventors with the '076 patent, discloses a method for simultaneously downloading and playing a program segment. Information is placed into a memory buffer as it is being downloaded, and concurrently read from that buffer for playback. This allows for near-instantaneous playback without waiting for a full download. The '076 patent itself cites this work, stating "the downloading and playing may proceed concurrently...as described in U.S. Pat. No. 5,371,551".
• Potential Anticipation of Claims: This patent is more specific than the '293 patent. It does not anticipate the entire system of personalization and usage logging. However, it could anticipate specific dependent claims related to the method of data delivery, particularly claims that might specify the concurrent downloading and playing of audio segments. The '076 patent builds upon this by integrating this delivery method into a broader personalization and feedback system.

U.S. Patent 5,499,393: "Method of and Apparatus for Selecting and Displaying an Interactive Program Guide"

• Full Citation: US Patent 5,499,393 A
• Publication Date: March 12, 1996
• Filing Date: November 12, 1993
• Brief Description: This patent describes an interactive television program guide. The system receives broadcast program schedule data, stores it, and allows a user to navigate through the schedule. Users can select programs for viewing or recording and can search or filter the guide based on various criteria like program title, category, or time.
• Potential Anticipation of Claims: This reference is relevant to the user interface and program selection aspects of the '076 patent. While focused on television and broadcast data, it discloses the concept of a user navigating a catalog of available media ("program catalog information 137" in the '076 patent's FIG. 1) and making selections for a personalized schedule. It could potentially anticipate claims related to the client-side functionality of reviewing, editing, and sequencing a program schedule before playback. However, it does not appear to describe the server-side compilation based on a detailed user profile or the crucial feedback loop of transmitting usage data back to the server.

U.S. Patent 5,557,541: "System for Supplying Musical Compositions to a Subscriber"

• Full Citation: US Patent 5,557,541 A
• Publication Date: September 17, 1996
• Filing Date: June 7, 1995
• Brief Description: This patent details a system for on-demand delivery of music to subscribers. A central server stores a library of musical compositions. A subscriber can connect to the server, search for music, and request specific tracks for download to their local device for playback. The system includes provisions for billing the subscriber based on the music they select and download.
• Potential Anticipation of Claims: This patent discloses a client-server architecture for delivering audio content on demand with an associated billing mechanism. It anticipates the concept of a user selecting specific audio segments from a central library for local playback and being charged for them. This could anticipate claims related to the on-demand selection and billing components of the '076 system. However, it seems to focus on a user-initiated, track-by-track selection model rather than the '076 patent's more automated, profile-driven compilation of a continuous "program schedule" or "session." The '076 patent's emphasis on adaptive personalization through usage log feedback appears to be a key distinction.

Obviousness Analysis of U.S. Patent 6,199,076 under 35 U.S.C. § 103

This analysis evaluates whether the invention described in U.S. Patent 6,199,076 would have been obvious to a person having ordinary skill in the art (POSITA) at the time the invention was made, circa its 1996 filing date. Under 35 U.S.C. § 103, an invention is unpatentable if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made. This analysis relies on combinations of the prior art references identified in the preceding section.

The core inventive concepts of the '076 patent are:

1. A client-server system where a server compiles a personalized audio program schedule based on a user's profile.
2. The download of this schedule and associated audio segments to a remote player device.
3. A user interface on the player that allows for dynamic control of playback (e.g., skipping segments or subjects).
4. A feedback loop where the player logs user interactions and uploads this usage data to the server.
5. The server's use of this feedback data for adaptive personalization of future programs and for detailed accounting (subscriber billing, advertiser charges, and content provider royalties).

Based on the cited prior art, at least two combinations would have rendered these concepts obvious to a POSITA in 1996.

---

Combination 1: U.S. Patent 5,251,293 (Personalized System) in view of U.S. Patent 5,499,393 (Interactive Program Guide)

This combination establishes the obviousness of the core system architecture, the personalization engine, and the client-side user control features.

• What the '293 Patent Teaches: The '293 patent serves as a strong foundational reference. It explicitly discloses the primary architecture of the '076 invention: a central server storing a library of media segments, a method for compiling a customized program based on a subscriber's pre-defined profile, and the downloading of that program to a user's personal computer for later playback. Crucially, the '293 patent also teaches the concept of tracking user usage of the downloaded content.

• What the '393 Patent Teaches: The '393 patent teaches a sophisticated interactive program guide for television. It discloses the client-side functionality of presenting a user with a catalog of available programming, allowing the user to navigate this catalog, and enabling the user to select and organize content into a personalized schedule. This is analogous to the '076 patent's description of a user reviewing and altering the "provisional program selections and sequence" (as described in step 211 of the patent text).

• Motivation to Combine: A person having ordinary skill in the art, starting with the personalized media delivery system of the '293 patent, would have been motivated to provide a more interactive and user-friendly way for the subscriber to manage their content. The '293 patent delivers a pre-compiled program, but the '393 patent provides a well-understood method for enhancing user control and interaction. Combining the server-side personalization of '293 with the client-side interactive guide of '393 would have been a predictable and logical improvement to increase user satisfaction. A POSITA would have recognized that allowing a user to review and edit the server's suggested playlist, as taught by the guide-based interface of '393, is a natural extension of a personalized content system. The dynamic playback controls described in the '076 patent (e.g., "SKIP TOPIC," "SKIP SUBJECT") are merely the application of the '393 patent's navigation principles (moving through a list of programs) to the context of audio playback rather than a visual guide. The result would be a system that both suggests content based on a profile and allows the user to fine-tune and navigate that content, achieving the core functionality claimed in the '076 patent.

---

Combination 2: The system of '293 and '393 in view of U.S. Patent 5,557,541 (Music Subscription System)

This combination establishes the obviousness of the feedback loop for detailed accounting and billing.

• What the Combination of '293 and '393 Teaches: As established above, this combination teaches a personalized media system where a server compiles a program based on a user profile, downloads it to a client, and the client has an interactive guide for managing and navigating the program. The '293 patent already introduces the idea of tracking usage.

• What the '541 Patent Teaches: The '541 patent teaches a specific commercial implementation for a client-server audio delivery system. It discloses a system where subscribers select specific musical tracks from a central server for download and are billed for those selections. This patent makes explicit the business method of tracking discrete user selections of audio content for the purpose of generating charges.

• Motivation to Combine: While the '293 patent mentions tracking usage, it does not detail a robust commercial application for that data. A POSITA, seeking to commercialize the system taught by the combination of '293 and '393, would naturally look for established models of billing for digital content. The '541 patent provides exactly such a model for audio content. It would have been obvious to apply the per-item selection and billing mechanism of '541 to the usage data already being tracked by the '293 system. This would allow the system provider to not only personalize content but also to create a detailed billing history based on what content was actually played, skipped, or selected. The '076 patent's detailed accounting system—which calculates subscriber charges, credits for listening to ads, and royalty payments to content providers based on a detailed usage log—is a direct and predictable application of the commercial methods taught in '541 to the personalized media system of '293. The result of this combination is a system that personalizes, delivers, and monetizes content based on fine-grained usage tracking, rendering the full scope of the '076 patent's invention obvious.

Term, Expiration, and Family Analysis for U.S. Patent 6,199,076

This analysis details the patent term, continuity data, and projected expiration for U.S. Patent 6,199,076 based on USPTO records as of May 11, 2026.

---

Patent Term and Expiration

• Filing Date: October 2, 1996
• Issue Date: March 6, 2001
• Governing Law: As the application was filed after June 7, 1995, its term is governed by the Uruguay Round Agreements Act (URAA), which sets the patent term at 20 years from the earliest effective U.S. non-provisional filing date.
• Projected Expiration Date: The patent's term is calculated from its filing date of October 2, 1996. Therefore, the patent expired 20 years later.
  • Calculated Expiration: October 2, 2016
• Current Status: Expired. The patent's term has concluded, and it is now in the public domain.

Patent Term Adjustments (PTA) and Extensions (PTE)

• Patent Term Adjustment (PTA): There is no record of any Patent Term Adjustment granted to this patent. PTA is typically granted for delays in prosecution caused by the USPTO. Given the patent issued in under five years from its filing, significant prosecution delays necessitating PTA are not indicated.
• Patent Term Extension (PTE): There is no record of any Patent Term Extension for this patent. PTE under 35 U.S.C. § 156 is related to regulatory review delays (e.g., by the FDA) and is not applicable to the subject matter of this patent.

---

Continuity and Patent Family

U.S. Patent 6,199,076 is the parent patent of a large and heavily litigated family of applications that claim priority back to its 1996 filing date. This continuity chain was used by the assignee, Personal Audio LLC, to file subsequent patents with claims directed at various aspects of media distribution, which were later asserted in litigation.

Directly Related Applications:

The application that issued as the '076 patent, Ser. No. 08/724,813, serves as the parent for a chain of subsequent applications. The most notable direct and indirect descendants are:

• U.S. Patent 7,509,178:

  • Relationship: A divisional of the '076 patent's application.
  • Application No.: 09/782,546
  • Filed: February 13, 2001
  • Titled: "Audio program distribution and playback system."
  • Status: Expired. This patent was litigated alongside the '076 patent in several cases.

• U.S. Patent 8,112,504 (the "Podcasting Patent"):

  • Relationship: A divisional of the application for the '178 patent, making it a "grandchild" of the '076 patent.
  • Application No.: 12/380,955
  • Filed: March 4, 2009
  • Titled: "System for disseminating media content representing episodes in a serialized sequence."
  • Status: Expired (Fee Related). Key claims of this patent were invalidated in an inter partes review proceeding, a decision that was affirmed by the Federal Circuit. This patent was the subject of high-profile lawsuits against podcasters and media companies.

Full Family Chain:

The provided patent text and public records indicate a large number of applications claim priority back to the original 1996 application. This forms an extensive patent family that includes, but is not limited to:

• Parent: US 6,199,076 (Application 08/724,813, filed 1996-10-02)
  • Child (Divisional): US 7,509,178 (Application 09/782,546, filed 2001-02-13)
    • Child (Continuation): US 2007/0026852 A1 (Application 11/542,379, filed 2006-10-03)
    • Child (Continuation): US 2008/0005130 A1 (Application 11/888,864, filed 2007-08-02)
    • Child (Divisional): US 8,112,504 (Application 12/380,955, filed 2009-03-04)
    • Child (Divisional): US 2009/0177303 A1 (Application 12/380,961, filed 2009-03-04)
    • Child (Divisional): US 2009/0198357 A1 (Application 12/380,908, filed 2009-03-04)
    • Child (Continuation): US 2009/0248182 A1 (Application 12/386,601, filed 2009-04-20)
      • Child (Continuation): US 2014/0156808 A1 (Application 14/181,650, filed 2014-02-15)
      • Child (Continuation): US 2014/0163707 A1 (Application 14/181,652, filed 2014-02-15)
        • Child (Continuation): US 2016/0029059 A1 (Application 14/639,016, filed 2015-03-04)

This extensive family tree demonstrates a strategy of filing numerous related applications over many years to cover different embodiments and aspects of the original 1996 invention, thereby creating a broad portfolio for licensing and assertion.

Defensive Disclosure and Prior Art Publication

Title: System and Method for Dynamic, Adaptive, and Cross-Domain Delivery of Sequenced Information Payloads
Publication Date: April 26, 2026
Reference: This document is published as a defensive disclosure to establish prior art against any future patent applications claiming the derivatives, variations, and applications of the concepts described in U.S. Patent 6,199,076. It is intended to enter the public domain and be available to patent examiners globally.

---

Preamble

This publication describes a series of methods, systems, and apparatuses that expand upon the foundational concepts of personalized, server-driven media delivery as outlined in U.S. Patent 6,199,076. The following disclosures are intended to be enabling for a person having ordinary skill in the art (POSITA) and cover component substitutions, expansions of operational parameters, cross-domain applications, integration with emerging technologies, and failure-mode or limited-functionality operations.

---

Core Concept 1: Personalized Information Payload Delivery System

The following disclosures describe variations on the core client-server architecture for compiling and delivering a personalized sequence of data segments.

1.1. Component Substitution: Embedded SoC Player with Microservice-Based Delivery

• Enabling Description: The client player apparatus described in '076 is implemented not as a general-purpose personal computer, but as a dedicated System-on-Chip (SoC) based on a low-power ARM Cortex-M series processor. The SoC integrates a digital signal processor (DSP) for hardware-accelerated audio decompression (e.g., Opus codec), a non-volatile flash memory for program segment storage, and a cellular IoT modem (e.g., LTE-M or NB-IoT) for communication. The server architecture is not a monolithic FTP/CGI server but is a distributed system of microservices orchestrated by a container management platform like Kubernetes. Communication between the client SoC and the server's API gateway utilizes gRPC over a secured TLS channel for high-performance, low-latency data exchange, replacing the FTP/HTTP protocols. The session schedule file is a Protocol Buffers (Protobuf) message, providing a strongly-typed, compact binary format for efficient transmission and parsing on the resource-constrained client.

• Mermaid Diagram:

  sequenceDiagram
      participant ClientSoC as Client (ARM Cortex-M)
      participant APIGateway as Server (gRPC Gateway)
      participant ProfileService as µService (Profile)
      participant SchedulerService as µService (Scheduler)
  
      ClientSoC->>APIGateway: AuthenticateRequest(deviceID)
      APIGateway-->>ClientSoC: AuthToken
      ClientSoC->>APIGateway: GetScheduleRequest(token)
      APIGateway->>ProfileService: GetUserProfile(deviceID)
      ProfileService-->>APIGateway: UserProfileData
      APIGateway->>SchedulerService: CompileSchedule(UserProfileData)
      SchedulerService-->>APIGateway: ScheduleResponse (Protobuf)
      APIGateway-->>ClientSoC: Stream ScheduleResponse
  

1.2. Cross-Domain Application: Agricultural Technology (AgTech) Precision Irrigation

• Enabling Description: The system is applied to precision agriculture. The "player" is a network of intelligent irrigation controllers distributed across a field, each equipped with soil moisture sensors and solenoid valve actuators. The "server" is a cloud-based AgTech platform that aggregates data from weather services, satellite imagery, and the controllers themselves. The "audio program segments" are replaced with time-stamped "irrigation instruction segments," which are data packets specifying a duration, flow rate, and nutrient mix for a specific zone. The "user profile" is a "field profile" containing crop type, growth stage, soil composition, and topography. The server compiles a dynamic daily irrigation schedule based on the field profile and real-time sensor feedback. The usage log returned to the server contains data on actual water volume and nutrients dispensed, along with resulting changes in soil moisture, enabling the system to adaptively learn the optimal watering strategy for the field.

• Mermaid Diagram:

  graph TD
      A[Cloud AgTech Platform] -- Compiles Schedule --> B(Irrigation Schedule File);
      A -- Weather & Satellite Data --> A;
      B -- Transmits via LoRaWAN --> C{Irrigation Controller};
      C -- Executes Commands --> D[Solenoid Valves & Pumps];
      E[Soil & Nutrient Sensors] -- Real-time Data --> C;
      C -- Uploads Usage Log --> F(Water/Nutrient Log);
      F -- Feedback Loop --> A;
  

1.3. Cross-Domain Application: Aerospace Flight Management

• Enabling Description: The system is adapted for use in an aircraft cockpit as a dynamic checklist and procedure management system. The "player" is an Electronic Flight Bag (EFB) tablet device. The "program segments" are individual checklist items or procedural steps, which can include audio readouts, text, and schematic diagrams. The "server," located on the ground, compiles a "mission file" based on the specific aircraft tail number, flight plan, current weather (METAR/TAF), and any applicable Notices to Airmen (NOTAMs). This mission file, containing the ordered sequence of procedures, is downloaded to the EFB before flight. During flight, pilots interact with the EFB to advance through checklists. The "usage log" meticulously records the timestamp of each checklist item's completion, any items that were skipped, and the duration of each procedure. This log is uploaded post-flight for analysis by flight operations and safety departments to identify procedural bottlenecks or deviations.

• Mermaid Diagram:

  erDiagram
      AIRCRAFT ||--o{ MISSION_FILE : "has"
      FLIGHT_PLAN ||--|{ MISSION_FILE : "informs"
      NOTAM_DATABASE ||--|{ MISSION_FILE : "informs"
      MISSION_FILE {
          string TailNumber PK
          datetime FlightDate PK
          object ChecklistSequence
          object ProcedureSequence
      }
      EFB_PLAYER ||--|| MISSION_FILE : "executes"
      EFB_PLAYER {
          string DeviceID PK
          string CurrentStep
      }
      USAGE_LOG ||--|{ EFB_PLAYER : "generates"
      USAGE_LOG {
          string LogID PK
          datetime Timestamp
          string StepID
          string Status
      }
  

1.4. Integration with Emerging Tech: AI-Driven Predictive Caching and Blockchain Royalties

• Enabling Description: The server component integrates an AI-driven recommendation engine using a collaborative filtering model (e.g., Alternating Least Squares) to generate the session schedule. It analyzes the user's historical usage data and compares it to similar users to predict content the user will find engaging. The system also employs predictive caching: based on the user's calendar, GPS location patterns from their mobile device, and time of day, the server pre-emptively pushes likely relevant program segments to the player device during off-peak network hours to ensure they are available without download delays. The "usage log" is transformed into an immutable transaction record. Each time a program segment (e.g., a song, a news story, an advertisement) is played for a predetermined threshold duration, the player device generates a cryptographically signed "proof-of-play" transaction, which is submitted to a permissioned blockchain (e.g., Hyperledger Fabric). Content providers and advertisers are participants on this blockchain, allowing for transparent, real-time, and auditable verification of content delivery for royalty and billing calculations.

• Mermaid Diagram:

  flowchart LR
      subgraph Server Side
          A[User History DB] --> B(Collaborative Filtering AI);
          C[User Context IoT Data] --> B;
          B -- Predicted Playlist --> D[Scheduler];
          D -- Pushes Segments --> E[Predictive Caching];
      end
      subgraph Client Side
          F[Player Device] -- Fetches from --> E;
          F -- Plays Segment --> G{Log Playback};
          G -- Duration > Threshold --> H(Generate Proof-of-Play);
          H -- Sign Transaction --> I(Submit to Blockchain);
      end
      I --> J[(Hyperledger Fabric)];
      Server Side -- Schedules --> F;
  

1.5. Inverse / Failure Mode: "Secure Enclave" One-Way Data Diode Mode

• Enabling Description: The invention is modified to operate in a high-security environment, such as industrial control systems (SCADA) or military communications. The "player" device is physically implemented with a hardware-enforced data diode, permitting data to be received from the server but making it physically impossible to transmit data back. The feedback loop is eliminated. The server transmits a schedule of operational commands or safety announcements. All program segments and the schedule file itself must be digitally signed with an Elliptic Curve Digital Signature Algorithm (ECDSA) key. The player's firmware, operating within a trusted execution environment (TEE), will refuse to play any segment whose signature cannot be verified against a public key stored in read-only memory. This creates a secure, one-way system for delivering authenticated instructions where feedback and adaptation are sacrificed for guaranteed security and integrity.

• Mermaid Diagram:

  stateDiagram-v2
      [*] --> Receiving
      Receiving: Waiting for Signed Schedule
      Receiving --> Verifying: Schedule Received
      Verifying: Check ECDSA Signature
      Verifying --> Receiving: Signature Invalid
      Verifying --> Executing: Signature Valid
      Executing: Play verified segments in sequence
      Executing --> Receiving: Schedule Complete
  

---

Core Concept 2: Dynamic Playback Control User Interface

The following disclosures describe variations on the user's ability to navigate and control the playback of the pre-sequenced data.

2.1. Component Substitution: Biometric Control Interface

• Enabling Description: The user control mechanism (e.g., voice commands, pushbuttons) is replaced with a brain-computer interface (BCI) or electromyography (EMG) sensors. For BCI, a wearable headband with dry EEG electrodes monitors the user's P300 event-related potential or SSVEP (Steady State Visually Evoked Potential). An on-device processor uses a machine learning model (e.g., a shallow convolutional neural network) to classify EEG signals into commands such as "skip," "bookmark," or "replay." This enables hands-free and voice-free operation for users with severe motor disabilities or for operators in environments where hands and voice are occupied. For EMG, sensors on the forearm can detect subtle, pre-trained muscle gestures to trigger the same commands.

• Mermaid Diagram:

  graph TD
      A[EEG/EMG Sensors] --> B{Signal Acquisition & Filtering};
      B --> C[Feature Extraction];
      C --> D(CNN Classifier);
      D -- Command --> E{Player Control Logic};
      subgraph Commands
          direction LR
          D1[Skip]
          D2[Bookmark]
          D3[Replay]
      end
      D --> D1 & D2 & D3
      E --> F[Audio Playback Engine];
  

2.2. Cross-Domain Application: Genomic Sequencing Navigation

• Enabling Description: The concept of playback control is applied to a genomic sequencing workflow. The "program" is the entire genome being sequenced, and "playback" is the sequencing process itself. The "program segments" are specific chromosomal regions or genes. A bioinformatician defines a "session schedule" that prioritizes the sequencing of specific exons (coding regions) while assigning lower priority to introns (non-coding regions). During the sequencing run, the operator can issue a "skip" command, causing the sequencer to halt analysis of a low-priority intron and immediately reallocate its resources to the next high-priority exon in the schedule. A "bookmark" command flags a region with anomalous readings for follow-up analysis without interrupting the primary run. This dynamic control allows for more efficient and targeted use of expensive sequencing reagents and machine time.

• Mermaid Diagram:

  sequenceDiagram
      participant Operator
      participant SequencerUI
      participant SequencerEngine
      participant DataStorage
  
      Operator->>SequencerUI: Start Run(ExonPrioritizedSchedule)
      SequencerUI->>SequencerEngine: BeginSequencing()
      loop Sequencing Intron Region 3
          SequencerEngine->>DataStorage: StoreReadData()
          Operator->>SequencerUI: IssueCommand(SKIP_SEGMENT)
          SequencerUI->>SequencerEngine: SkipToNextExon()
      end
      SequencerEngine->>SequencerEngine: Reallocate resources to Exon 4
      loop Sequencing Exon 4
           SequencerEngine->>DataStorage: StoreReadData()
      end
  

2.3. Inverse / Failure Mode: "Distraction-Free" Vehicle Operator Mode

• Enabling Description: For in-vehicle applications, the player enters a "distraction-free" low-functionality mode based on vehicle telemetry. When the vehicle's speed, as reported by the CAN bus, exceeds a predefined threshold (e.g., 10 mph), the dynamic control interface is disabled. All user inputs for "skip," "menu," "go," and "bookmark" are ignored or queued. The only available commands are "pause" and a dedicated command to interrupt the program for a high-priority vehicle alert or navigation instruction. When the vehicle's speed drops below the threshold for a set duration, the full control interface is restored, and any queued commands can be presented to the user for confirmation. The usage log explicitly flags which segments were played while the device was in this restricted mode.

• Mermaid Diagram:

  stateDiagram-v2
      state "Full Control" as Full
      state "Distraction-Free Mode" as Locked
  
      [*] --> Full: System Start
      Full --> Locked: VehicleSpeed > 10 mph
      Locked --> Full: VehicleSpeed < 10 mph for 30s
  
      Full: Accepts all commands (Skip, Menu, etc.)
      Locked: Ignores/Queues commands. Only accepts Pause & Interrupt.
  

---

Core Concept 3: Usage Log Feedback and Adaptive Personalization

The following disclosures describe variations on the mechanism for logging user interactions and using that data to adapt future content.

3.1. Integration with Emerging Tech: Federated Learning for Privacy-Preserving Personalization

• Enabling Description: The adaptive personalization system is re-architected to preserve user privacy using Federated Learning (FL). Instead of uploading a detailed usage log to the server, the player device maintains the log locally. A lightweight machine learning model for preference prediction is sent from the server to the client. The player device uses its local, private usage log to train this model on-device. The resulting model updates (gradients), not the raw data, are then encrypted and sent back to the server. The server aggregates these anonymized updates from thousands of users to improve a global personalization model, which is then used to generate improved local models for the next cycle. This method allows the system to learn from user behavior without the server ever accessing or storing personally identifiable usage history.

• Mermaid Diagram:

  flowchart TD
      A[Server: Global Model] -- 1. Send Model --> B((Client Device));
      C[Local Private Usage Log] -- 2. Train Model On-Device --> B;
      B -- 3. Compute Gradients --> D{Encrypted Model Updates};
      D -- 4. Send Updates to Server --> E[Server: Aggregation Engine];
      E -- 5. Aggregate Updates --> A;
      subgraph Privacy Boundary
          direction LR
          B
          C
      end
  

3.2. Cross-Domain Application: Adaptive E-Learning Systems

• Enabling Description: The feedback loop is applied to a personalized education platform. A student (the "user") interacts with a course module (the "player"). The "program segments" are lessons, video lectures, quizzes, and interactive exercises. The "usage log" is a rich data stream capturing not just which lessons were completed, but also quiz scores, time spent on each exercise, incorrect answers, and points in a video lecture that were re-watched. This detailed log is sent to the server. The server's "adaptive personalization" engine analyzes this data to build a dynamic "student knowledge graph." It identifies concepts the student has mastered and areas where they are struggling. Based on this analysis, it compiles the next day's session schedule, automatically inserting remedial exercises for difficult topics or providing advanced material for mastered concepts, creating a truly individualized learning path.

• Mermaid Diagram:

  erDiagram
      STUDENT ||--|{ USAGE_LOG : "generates"
      COURSE_MODULE ||--|{ USAGE_LOG : "is source of"
      USAGE_LOG {
          int StudentID PK
          int ModuleID PK
          datetime Timestamp
          string EventType
          string EventData
      }
      SERVER_ENGINE ||--|| STUDENT_KNOWLEDGE_GRAPH : "updates"
      STUDENT_KNOWLEDGE_GRAPH {
          int StudentID PK
          array MasteredConcepts
          array StrugglingConcepts
      }
      SERVER_ENGINE {
          string EngineID PK
      }
      SERVER_ENGINE ||--o{ NEXT_SESSION_SCHEDULE : "compiles"
      USAGE_LOG --|> SERVER_ENGINE : "is input to"
  

---

Combination Prior Art with Open-Source Standards

1. Combination with ActivityPub Protocol: The system described in '076 is combined with the W3C ActivityPub federated social networking protocol. A user's player device acts as an ActivityPub client. When a user "bookmarks" or "annotates" a program segment, the client generates an Activity of type Create with an Note object. This activity is posted to the user's outbox and federates to their followers. The "server" can also act as an ActivityPub server, publishing new program catalogs as Collection objects. This combination creates a decentralized, social version of the personalized audio system where users can share and discover content through a standardized, open protocol.

2. Combination with the Matter IoT Standard: The client player is implemented as a Matter-compliant device, exposing its playback controls (play, pause, skip, volume) as part of a standard "Media Player" device type cluster within the Matter specification. This allows the player to be controlled interoperably by any Matter-certified controller, such as a smart speaker, mobile app, or light switch, from any vendor (e.g., Google, Apple, Amazon). The "session schedule" is delivered over the Matter network fabric (Wi-Fi or Thread) using a custom vendor-defined cluster, while the core playback functionality adheres to the open standard.

3. Combination with OpenTelemetry (OTel): The "usage log" is implemented using the OpenTelemetry standard. Every user interaction (play, skip, pause, volume change, etc.) is recorded as a "span" within a "trace" that represents the entire listening session. This data is exported from the client player using an OTel exporter (e.g., OTLP over HTTP) to a compliant backend. This approach replaces the proprietary log format with a standardized, vendor-neutral observability framework, allowing the server-side to use off-the-shelf analysis tools like Jaeger or Prometheus to analyze user behavior, system performance, and generate billing data.