Obviousness

Obviousness Analysis of U.S. Patent 8,949,206 under 35 U.S.C. § 103

This analysis evaluates whether the invention claimed in U.S. Patent 8,949,206 ('206 patent) would have been obvious to a Person of Ordinary Skill in the Art (POSITA) at the time the invention was made. The priority date is October 4, 2012. A POSITA would have been an engineer or computer scientist with experience in video encoding, content delivery networks (CDNs), and adaptive bitrate streaming protocols like HTTP Live Streaming (HLS) and the nascent MPEG-DASH standard.

The core of the '206 patent's invention, as detailed in independent claims 1 and 14, is a system and method for creating multiple, customized versions of a media presentation by manipulating a descriptor file (like an HLS playlist or a DASH MPD) based on a set of rules, without transcoding or creating new media segment files. This allows for efficient, dynamic versioning for purposes such as ad insertion, content rating enforcement, or regional blackouts.

Based on the prior art cited during the patent's prosecution, the claims appear vulnerable to an obviousness challenge under 35 U.S.C. § 103. The primary argument is that the '206 patent combines known techniques for manifest file manipulation with well-understood business or content management rules.

Primary Obviousness Combination: Akamai '418 in view of DISH '499

1. Base Reference: U.S. Patent Application Pub. No. US 2013/0117418 A1 ("Akamai '418")

• What Akamai '418 Teaches: Filed on November 6, 2011, Akamai '418 teaches a content delivery system that dynamically modifies a manifest file "on-the-fly." It explicitly discloses:

  • Receiving a Manifest and Segments: The system, operating within a CDN, receives a manifest file and the associated media segments for distribution (fulfills step 1 of the '206 claims).
  • Manipulating the Manifest without Transcoding: It describes altering the manifest to filter out streams or otherwise modify it based on certain parameters (fulfills step 3).
  • Distributing the Modified Manifest: The modified manifest is then delivered to the requesting client device (fulfills step 4).
  • Rule-Based Modification: Akamai '418 discloses that these modifications can be based on "rules" such as the requesting device type or network conditions (partially fulfills step 2).

• What Akamai '418 Lacks: Akamai '418 primarily focuses on technical rules (device capabilities, network bandwidth) for manifest modification. While it teaches the core mechanism, it does not explicitly detail the use of content-based rules like ad insertion schedules, content ratings, or user profiles as described in the '206 patent.

2. Secondary Reference: U.S. Patent Application Pub. No. US 2013/0142499 A1 ("DISH '499")

• What DISH '499 Teaches: Filed on December 6, 2011, DISH '499 focuses on a remote/cloud DVR system. Its disclosure is relevant for its teaching of:
  • Playlist (Descriptor) Modification for Content Versioning: DISH '499 explicitly describes creating and managing playlists that are modified for dynamic ad insertion. A playlist for a recorded program can be altered to include references to ad segments.
  • Content-Based Rules: The motivation for modifying the playlist is a clear content-based rule: "insert an advertisement at this specific point." This directly teaches the application of non-technical, business-driven rules to create a different version of a media presentation.

3. Motivation to Combine and Reasonable Expectation of Success:

A POSITA, familiar with the on-the-fly manifest manipulation system taught by Akamai '418, would have been motivated to incorporate the content-based playlist modification techniques from DISH '499 for several reasons:

• Expanding Functionality: The most common and commercially valuable reason to alter a video stream is to insert or replace advertising. A POSITA would see the ad-insertion-by-playlist-modification method in DISH '499 as a natural and logical application for the dynamic manifest generation engine described in Akamai '418. Instead of just filtering bitrates, the same engine could be used to splice in ad segments by adding their URLs to the manifest at the appropriate points.

• Solving a Known Industry Problem: By 2012, dynamic ad insertion (DAI) was a well-known goal for streaming services. The industry was actively seeking ways to move beyond static, pre-packaged content and deliver personalized ads, enforce regional blackouts, and customize content for different users. Combining Akamai's dynamic manifest generation with DISH's application of playlist modification for ads would have been an obvious solution to this problem.

• Predictable Results: The combination would have yielded predictable results. A system that can already parse and rewrite a manifest file to remove a high-bitrate stream (as in Akamai '418) could, with simple modifications, be taught to add a reference to a different media segment (an ad, as in DISH '499). There were no technical hurdles that would have prevented a POSITA from successfully implementing this combination.

Therefore, the combination of Akamai '418 and DISH '499 teaches all elements of the '206 patent's independent claims. Akamai '418 provides the core system for on-the-fly manifest manipulation, and DISH '499 provides the motivation and teaching to apply this manipulation for content-based rules like ad insertion.

Secondary Obviousness Combination: Divx '958 in view of Common Industry Knowledge

1. Base Reference: U.S. Patent Application Pub. No. US 2013/0054958 A1 ("Divx '958")

• What Divx '958 Teaches: Filed on August 31, 2011, Divx '958 is a very strong reference that teaches:
  • Receiving Segments and Index Files: The system uses "track-level index files" (equivalent to single-track playlists) and their associated media segments.
  • Generating a "Top-Level" Index File (Descriptor): The core of the Divx invention is to automatically generate a "top-level index file" (equivalent to a master MPD or playlist) by combining different tracks.
  • Rule-Based Generation: This generation is based on rules, explicitly including "user preferences" and "device capabilities" (fulfills step 2).
  • No Transcoding: The system works by referencing existing media segments, not by creating new ones. The top-level file is then sent to the client. This fulfills all four steps of the '206 claims.

2. Argument for Obviousness:

Divx '958 alone comes very close to anticipating the '206 patent. An obviousness argument would be that extending the disclosed "user preferences" to include specific content-related rules like "parental controls" or "preferred language" was a simple and obvious design choice.

A POSITA in 2012 would have understood that "user preferences" in a media system commonly include:

• Language Selection: Choosing an audio track or subtitle language.
• Content Filtering: Setting parental controls based on content ratings (e.g., TV-PG, R).
• Accessibility: Enabling descriptive audio tracks.

Applying these well-known types of user preferences as rules to the system described in Divx '958 would lead directly to the invention claimed in the '206 patent. For example, a "user profile" (as mentioned in '206) could state a preference for "no violent content." The Divx system, which already generates a playlist based on user preferences, could easily be adapted to read this rule and generate a top-level index file that omits the "track-level index files" corresponding to violent scenes. This would be an obvious and straightforward implementation of the Divx system.

Conclusion

The independent claims of US Patent 8,949,206 are likely obvious under 35 U.S.C. § 103. The core inventive concept—manipulating a descriptor file based on rules without re-encoding media—was disclosed by multiple prior art references. The Akamai '418 reference teaches the fundamental system architecture for on-the-fly manifest modification, and the DISH '499 reference teaches the application of this technique for content-based rules like ad insertion. Furthermore, the Divx '958 reference teaches a nearly identical system, and extending its concept of "user preferences" to include common content-management rules would have been an obvious design choice for a person of ordinary skill in the art in 2012.