2:25-cv-02198
Audio Pod IP LLC v. Audible Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Audio Pod IP, LLC (Virginia)
- Defendant: Audible, Inc. (Delaware)
- Plaintiff’s Counsel: Stone Conroy LLC
- Case Identification: 2:25-cv-02198, D.N.J., 02/10/2026
- Venue Allegations: Venue is based on Defendant Audible, Inc. having its corporate headquarters and principal place of business in Newark, New Jersey, and having committed alleged acts of patent infringement within the district. The complaint also notes that in a prior related case, Audible successfully argued that claims should be transferred to the District of New Jersey.
- Core Dispute: Plaintiff alleges that Defendant’s digital audio products and services, including the Audible platform and its cross-device synchronization features, infringe three patents related to streaming, segmenting, and synchronizing digital media content.
- Technical Context: The technology at issue involves methods for efficiently delivering and synchronizing large digital media files, such as audiobooks, across multiple user devices, a cornerstone of the modern digital content streaming market.
- Key Procedural History: The complaint alleges a long history between the parties, beginning with a July 2007 meeting between Plaintiff’s predecessor and Brilliance Audio, which Amazon had recently acquired. Plaintiff alleges it sent a letter to Amazon in late 2012 or early 2013 identifying its intellectual property in relation to Defendant's "Whispersynch for Voice" and "Immersion Reading" features. The complaint also alleges Defendant had knowledge of the asserted patent family via a USPTO office action citation in May 2016 and via a prior complaint filed around March 2024.
Case Timeline
| Date | Event |
|---|---|
| 2005-12-13 | Earliest Priority Date for '740, '922, and '907 Patents |
| 2006-01-01 | Audio Pod launches subscriber-paid streaming service |
| 2007-05-01 | Amazon acquires audiobook publisher Brilliance Audio |
| 2007-07-01 | Audio Pod meets with Brilliance Audio to demonstrate technology |
| 2008-01-01 | Audio Pod's technology featured in The Ottawa Citizen newspaper |
| 2012-12-01 | Audio Pod CEO writes to Amazon regarding Kindle features and IP |
| 2014-05-27 | '740 Patent Issued |
| 2016-05-19 | USPTO cites an Audio Pod patent application against an Audible patent application |
| 2017-08-08 | '907 Patent Issued |
| 2018-04-24 | '922 Patent Issued |
| 2024-03-20 | Defendant allegedly receives notice of a first complaint filed by Plaintiff |
| 2026-02-10 | Third Amended Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,738,740 - Transmission of digital audio data
The Invention Explained
- Problem Addressed: The patent’s background section describes the drawbacks of the two primary methods for delivering digital audio at the time: mass downloading, which resulted in long wait times for large files like audiobooks, and "just-in-time" streaming, which was prone to interruptions and made repositioning within the audio (e.g., rewind/fast-forward) inefficient (U.S. Patent No. 10,735,488 B2, col. 1:30-62; U.S. Patent No. 10,735,488 B2, col. 2:1-12).
- The Patented Solution: The invention proposes segmenting a large audio stream into a plurality of smaller digital audio files, often using natural gaps in the spoken language U.S. Patent No. 10,735,488 B2, col. 2:44-48 These smaller files are then transmitted and played sequentially to create a "seamless manner" of playback for the user without requiring a full download beforehand U.S. Patent No. 10,735,488 B2, col. 2:48-52 A "virtual audio stream descriptor" file is used to manage the playback order and timing of these segments, enabling features like bookmarking and efficient navigation U.S. Patent No. 10,735,488 B2, col. 2:58-65
- Technical Importance: This approach aimed to combine the benefits of on-demand access from streaming with the stability of downloaded files, making it practical to consume long-form audio content over the internet without significant initial delays or playback interruptions Compl. ¶54
Key Claims at a Glance
- The complaint asserts independent claim 12 of the ’740 Patent Compl. ¶65
- The essential elements of claim 12, a non-transitory computer readable storage medium claim, include computer code for:
- Determining a first position within an audio stream and a corresponding time offset.
- Creating a bookmark for that position, where the bookmark includes a unique identifier for the stream and the time offset.
- Storing the audio stream as a plurality of separate digital audio files in a library.
- Using the time offset and a "descriptor file" to determine a first digital audio file from the plurality to be loaded for playback.
- Determining if that first digital audio file is already resident on the computer.
- Downloading the file from the library if it is not resident.
- Loading the file for playback.
- The complaint does not explicitly reserve the right to assert dependent claims for the ’740 Patent.
U.S. Patent No. 9,954,922 - Method and system for rendering digital content across multiple client devices
The Invention Explained
- Problem Addressed: The patent addresses "tracking problems" that arise when a user consumes media on multiple devices, noting the difficulty and time-consuming nature of resuming playback at a specific position when switching from one device to another (e.g., from a work computer to a home device) (U.S. Patent No. 10,091,266 B2, col. 1:31-39).
- The Patented Solution: The invention describes a method where a user’s position in a media stream on a first device is captured in a bookmark, which includes an identifier for the content and the user's position ’922 Patent, abstract This bookmark is transferred via a network to a second client device, which can then use the information to download the necessary content and resume rendering from the saved position, thereby enabling synchronized content consumption across devices ’922 Patent, abstract ’922 Patent, col. 2:21-25
- Technical Importance: This technology provides the foundation for cross-device media synchronization, a feature now considered standard in streaming services, allowing users to seamlessly transition between devices without losing their place in the content Compl. p. 6 screenshot
Key Claims at a Glance
- The complaint asserts independent claim 1 of the ’922 Patent Compl. ¶94
- The essential elements of claim 1, a method claim, include:
- Downloading and storing first digital content on a first client device.
- Rendering the content and tracking the current position.
- Creating a bookmark that identifies the media work and the bookmarked position.
- Transferring the bookmark to a second client device via a network.
- Downloading and storing second digital content on the second device, where the downloaded content includes the bookmarked position.
- Rendering the second digital content on the second device starting from the bookmarked position.
- Identifying a range of content to retain around the bookmark and releasing storage resources for content not identified for retention.
- If storage is insufficient, narrowing the range of content to be retained.
- The complaint does not explicitly reserve the right to assert dependent claims for the ’922 Patent.
Multi-Patent Capsule
- Patent Identification: U.S. Patent No. 9,729,907, Synchronizing a Plurality of Digital Media Streams by Using a Descriptor File, issued August 8, 2017 (the "’907 Patent").
- Technology Synopsis: The patent describes a method for synchronizing the rendering of multiple distinct but related media streams (e.g., an audiobook and an e-text of the same book) on a client device ’907 Patent, abstract Compl. ¶50 This is achieved by creating an external "descriptor file" that contains time offsets and synchronization points, which are stored in a way that indicates a correlation between points in the different media streams, allowing for synchronized playback ’907 Patent, abstract Compl. ¶51
- Asserted Claims: The complaint asserts independent claim 1 Compl. ¶127
- Accused Features: The complaint alleges that Audible's use of modern streaming protocols like MPEG-DASH infringes the ’907 patent. It alleges that the MPEG-DASH Media Presentation Description ("MPD") functions as the claimed "descriptor file" to synchronize and manage the playback of different digital media streams, such as audio narration and other related content Compl. ¶¶128-132
III. The Accused Instrumentality
Product Identification
- The accused instrumentalities are broadly defined as "Audible Products and Services" Compl. ¶8 This includes the Audible applications for various platforms, the Audible audiobook library and streaming service, related websites, and the underlying content delivery network (CDN) infrastructure, such as Amazon CloudFront Compl. ¶¶8-9 Specific accused features include "Whispersync for Voice" and "Immersion Reading," which allow users to synchronize listening and reading positions across devices Compl. ¶12 Compl. ¶61
Functionality and Market Context
- The Audible service allows users to purchase, download, and stream digital audio content, primarily audiobooks Compl. ¶8 A key feature, Whispersync, automatically syncs a user's playback position across multiple devices, allowing a user to "seamlessly go from listening to reading, and the paired audiobook and the Kindle eBook will know where you left off" Compl. p. 6 screenshot The complaint alleges that this functionality relies on technologies like HTTP Live Streaming (HLS), which breaks audio into segments and uses a manifest file to manage playback Compl. ¶66 Compl. p. 28 screenshot The service is delivered via Amazon's CloudFront CDN, which caches media fragments at edge servers to reduce latency and improve performance Compl. ¶40 Compl. ¶128 The complaint emphasizes the deep integration between Audible and its parent company, Amazon, in delivering these services Compl. ¶¶12-16 A screenshot from an Audible help page shows that its service allows users to switch devices and have their title "pick up right where you left off" Compl. p. 26 screenshot
IV. Analysis of Infringement Allegations
'740 Patent Infringement Allegations
| Claim Element (from Independent Claim 12) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| computer readable code, which when executed by a computer, causes said computer to determine a first position within an audio stream playing on a media player | The Audible system determines the current playback position of an audiobook on a media player. | ¶67 | col. 8:5-13 |
| and to determine a time offset using a point in time of the first position from a beginning of the audio stream | The Audible system determines a time offset for the current playback position relative to the start of the audiobook. | ¶68 | col. 8:10-13 |
| and to create a bookmark for the first position, the bookmark including a file, the file including a unique identifier for identifying the audio stream and including the time offset | When a user stops listening, Audible creates a bookmark containing a unique identifier for the audiobook and the time offset of the stop position. | ¶69 | col. 8:16-19 |
| wherein the audio stream is stored as a plurality of digital audio files in a library, each digital audio file including a different segment of the audio stream | The audio content is stored as multiple chunked segments (digital audio files) and delivered using protocols like HLS. A Fiddler capture shows requests for individual media segments (e.g., segment1_0_a.ts). (Compl. p. 31 screenshot). |
¶71 | col. 3:30-36 |
| and to determine a first digital audio file from the plurality of digital audio files to be loaded for playback...using the time offset and a descriptor file, the descriptor file for ordering the plurality of digital audio files... | Audible's system uses a manifest file (the alleged "descriptor file") and the time offset to determine which media segment should be loaded next for playback. | ¶72 | col. 3:55-62 |
| and to determine if the first digital audio file is resident within the computer | The Audible web player buffers media segments in its cache and determines whether a needed segment is already available locally. | ¶73 | col. 15:39-43 |
| and to download the first digital audio file from the library in dependence upon whether the first digital audio file is already resident within the computer | If a required media segment is not in the client-side buffer, it is streamed from the server (e.g., CloudFront). | ¶74 | col. 15:58-62 |
| and to load the first digital audio file for playback with the media player from the first position | The system loads the determined media segment for playback to resume or continue the audio stream. | ¶75 | col. 8:65-67 |
- Identified Points of Contention:
- Scope Questions: A primary point of contention may be whether the term "descriptor file," as described in the context of the 2005-priority patent, can be construed to read on the standardized manifest files used in modern streaming protocols like HLS (.m3u8) and MPEG-DASH (MPD), which the complaint alleges are infringing Compl. ¶72 Compl. ¶129 The defense may argue that the patent discloses a specific proprietary structure that differs from these industry standards.
- Technical Questions: The claim requires determining if a file is "resident within the computer." A question may arise as to whether transient buffering of data segments in a web browser's cache meets this limitation as alleged, or if the term implies a more permanent form of local storage.
'922 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| downloading first digital content... to a first client device... the first digital content including at least a first portion of a first media stream | A user downloads or streams at least a portion of an audiobook (e.g., the 'Introduction') to a first device, such as a smartphone. A screenshot shows the Audible app on a smartphone displaying a library and player. (Compl. p. 40 screenshot). | ¶96 | col. 1:19-20 |
| storing the first digital content on the first client device | The downloaded content is stored in the device's local storage space. | ¶97 | col. 1:21-22 |
| rendering at least a portion of the first digital content | The user plays the downloaded audiobook portion on the first device. | ¶98 | col. 1:22-23 |
| tracking a current position in the first media stream as the first digital content is rendered | The Audible app displays a time progress bar indicating the current playback position as the audiobook is played. | ¶99 | col. 8:5-9 |
| creating a bookmark by setting the current position as a bookmarked position, the bookmark including information for identifying the media work and the bookmarked position | Audible creates a bookmark for every unfinished title, showing the position where the user left off. | ¶100 | col. 8:5-13 |
| transferring the bookmark to a second client device via the network | Audible's service automatically syncs the listening position (the bookmark) to a user's account via the network, making it available to other devices. | ¶101 | col. 1:26-28 |
| downloading second digital content... to the second client device via the network, the second digital content including... the bookmarked position | A second device accesses the user's account and downloads or streams the audiobook, starting from the bookmarked position. | ¶102 | col. 1:31-33 |
| releasing storage resources allocated to all content... that is not identified as content to be retained on the second client device | Audible offers an "auto-remove" feature that automatically removes downloaded titles after they are finished, freeing up device storage. | ¶106 | col. 16:55-61 |
- Identified Points of Contention:
- Legal Questions (Divided Infringement): The method of claim 1 involves actions taken on a first client device, a second client device, and a network. A central legal question will be whether Audible can be held liable for infringement of the entire method. The complaint preemptively argues for liability under theories of direction or control and joint enterprise, asserting that users "simply run the software and applications as Audible designed and intends" and that Audible controls the entire ecosystem Compl. ¶¶10-11 The viability of this divided infringement theory will be a key issue.
- Scope Questions: The claim requires "releasing storage resources" and, if storage is insufficient, "narrowing the range of content... identified as content to be retained." The infringement theory relies on an optional "auto-remove" feature for finished books and "Chapter by Chapter streaming" for resource-constrained devices Compl. ¶¶106-107 A question for the court may be whether these specific, sometimes optional, features are sufficient to meet the claim limitations for all instances of accused infringement.
V. Key Claim Terms for Construction
The Term: "descriptor file" (from '740 Patent, claim 12)
- Context and Importance: This term is critical because the infringement allegation hinges on equating modern, industry-standard manifest files (like HLS
.m3u8or DASH MPD) with the patent's "descriptor file." Practitioners may focus on this term because if it is construed narrowly to cover only the specific embodiment in the patent, Audible’s use of standardized protocols may fall outside the claim's scope. - Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes the term functionally as an "index file (e.g., an XML document)" which "provides the information needed by a media player to reproduce the experience of a contiguous audio stream for the user without reconstructing the audio stream" ’740 Patent, col. 3:55-62 This functional description could support an interpretation that covers any file performing this role, including modern manifest files.
- Evidence for a Narrower Interpretation: Figure 5c and the accompanying text describe a "Virtual Stream Descriptor" with a specific hierarchy and fields, such as "Unique Identifier," "Segment Count," and "Segment Metrics List" ’740 Patent, Fig. 5c A defendant may argue that the term "descriptor file" should be limited to this more specific structure disclosed as an embodiment.
- Context and Importance: This term is critical because the infringement allegation hinges on equating modern, industry-standard manifest files (like HLS
The Term: "transferring the bookmark to a second client device" (from '922 Patent, claim 1)
- Context and Importance: This term is central to the cross-device synchronization allegation and implicates the doctrine of divided infringement. The dispute will likely focus on whether Audible's server-based synchronization architecture, where a second device fetches a position stored on a server, constitutes "transferring" the bookmark to the second device as required by the claim.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The abstract states, "The identifier and the first position are transferred from the first client device to a second client device via a network accessible library" ’922 Patent, abstract This language does not specify the mechanism (e.g., push vs. pull) and could be interpreted broadly to cover any system architecture that results in the bookmark data moving from a state associated with the first device to being accessible by the second.
- Evidence for a Narrower Interpretation: A defendant may argue that "transferring" implies a more active step than what occurs in a cloud-sync model, where the first device updates a central server and the second device later queries that server. The specification does not detail the specific network topology of the transfer, which may create ambiguity that a defendant could seek to resolve with a narrower construction.
VI. Other Allegations
Indirect Infringement: The complaint alleges active inducement under 35 U.S.C. § 271(b), asserting that Audible provides documentation, training materials, and user manuals that instruct and encourage customers to use the Audible Products and Services in an infringing manner (e.g., by using the cross-device sync features) Compl. ¶¶82-83 Compl. ¶¶114-115 It also alleges contributory infringement under 35 U.S.C. § 271(c), arguing that the user applications are material components of the invention especially made for infringing use and have no substantial non-infringing uses, as they cannot operate without being connected to Audible's networks Compl. ¶¶88-90 Compl. ¶¶120-122
Willful Infringement: The complaint alleges willful infringement based on Defendant’s alleged pre-suit knowledge of the patents and the infringing conduct. The basis for this allegation includes a 2007 meeting with an Amazon subsidiary, a 2012-2013 letter from Plaintiff’s CEO to Amazon’s VP of IP regarding the specific accused features, a 2016 USPTO citation of Plaintiff's patent application against an Audible application, and notice from a prior complaint filed in 2024 Compl. ¶¶78-80 Compl. ¶¶110-112 The complaint further alleges that Defendant took deliberate steps to avoid learning of the infringement, including by refusing to respond to Plaintiff’s attempts to engage in licensing discussions (Compl. ¶¶81, 113).
VII. Analyst’s Conclusion: Key Questions for the Case
A core issue will be one of definitional scope and technological evolution: Can the term "descriptor file," conceived in a 2005-priority patent, be construed to cover the standardized HLS and DASH manifest files that are foundational to modern streaming services like Audible? The outcome of this claim construction dispute could be dispositive for the allegations against the ’740 and ’907 patents.
A second key issue will be one of agency and control in a networked system: For the cross-device synchronization claims of the ’922 patent, does Audible’s control over its end-to-end service (server infrastructure and client applications) suffice to attribute the actions of its users on their personal devices to Audible itself, thereby satisfying the requirement of a single actor for direct infringement?
A final dispositive question will be one of willfulness based on historical knowledge: Can Plaintiff demonstrate that Defendant's alleged pre-suit knowledge, stemming from events as early as 2007 and specific correspondence in 2013, pertained to the specific patents-in-suit and rose to the level of "wanton, malicious, bad-faith, deliberate, consciously wrongful, flagrant, or characteristic of a pirate" required for enhanced damages?