Playlist Index Aggregation for Network Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing satellite television systems face challenges in efficiently sharing content playlists across set top boxes without overburdening the network, as each set top box typically only plays content to its associated television and lacks an efficient method for distributing playlist information.

Innovation Solution

A system and method that creates a playlist index with reduced data, allowing client devices to store and cache playlist data temporarily, using an aggregation server to combine playlists from multiple storage devices and generate an index list for efficient distribution to aggregation clients, thereby reducing resource usage and enabling seamless playlist sharing across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the entire playlist data is distributed to all set top boxes, then complete content availability is achieved, but network bandwidth and client storage resources are overwhelmed

Engineering Contradiction:
Improvecontent availabilityVSAvoiddata volume
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The playlist data is segmented into two parts: a compact index structure that is distributed to all clients, and full playlist data that is retrieved on-demand from the server. This segmentation allows clients to have minimal local data while maintaining access to complete content information when needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An index structure acts as an intermediary between the server and clients, containing condensed playlist information that enables clients to identify and retrieve specific content without receiving the entire playlist data set. The index serves as a reference guide that reduces the amount of data transmitted across the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If playlist data is cached in client devices, then access speed is improved, but client storage resources are consumed

Engineering Contradiction:
Improveaccess speedVSAvoidstorage space
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

Instead of caching the entire playlist data, the system implements partial caching where only the condensed index structure is stored in client devices. This partial action approach provides sufficient access speed for browsing and selection while consuming minimal storage resources. Full playlist data is retrieved from the server only when specific content is selected for viewing.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If multiple set top boxes share content playlists, then content accessibility is improved, but network burden increases

Engineering Contradiction:
Improvecontent sharing capabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

Instead of distributing full playlist data copies to multiple clients, the system distributes a single copy of the condensed index structure to all clients. This copying approach enables multiple set top boxes to share content playlists with minimal network bandwidth consumption, as the index is much smaller than the complete playlist data and can be efficiently replicated.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9258175B1Method and system for sharing playlists for content stored within a network
Publication Date: 2016.02.09 DIRECTV LLC
  • US9258175B1 patent drawing
  • US9258175B1 patent drawing
  • US9258175B1 patent drawing

AI summary

A system and method for sharing playlists within a network includes a first storage device having a first playlist comprising first playlist data corresponding to stored content and a second storage device having a second playlist comprising second playlist data corresponding to stored content. The system also includes an aggregation server in communication with the first storage device and the second storage device that receives the first playlist and the second playlist. The aggregation server aggregates the first playlist data and the second playlist data to form an aggregated playlist having aggregated playlist data and forms an index list corresponding to the aggregated playlist. A first aggregation client is in communication with the aggregation server and receives the index list from the aggregation server.