Enhanced History Buffer Segmentation for Media Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Media devices have limited storage capacity in their history buffers, restricting users' ability to rewind and pause program events, and existing DVR functions do not seamlessly integrate with history buffers, leading to loss of content and potential DRM and parental control violations.

Innovation Solution

Implementing an enhanced history buffer that stores program events in discrete files with defined start and end locations, allowing users to rewind and save content, while managing DRM and parental controls, and integrating with DVR functions for seamless storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If the history buffer stores program content for a longer duration, then users can rewind and pause for extended periods, but the storage capacity is exceeded and content is lost

Engineering Contradiction:
Improverewind durationVSAvoidstorage capacity
Core Design Contradiction:
Duration of action of moving objectVSQuantity of substance

Solution Approach 1:

The patent divides the history buffer into multiple segments, each dedicated to storing a specific program event. Instead of using a single continuous buffer that overwrites content, the system creates separate storage regions for different programs, allowing each program to be stored independently until its associated DRM credentials expire or storage is needed for new content.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the history buffer content is transferred to DVR for permanent storage, then content preservation is improved, but DRM violations may occur without proper credential storage

Engineering Contradiction:
Improvecontent preservationVSAvoidDRM violations
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent performs preliminary actions by storing DRM credentials and parental control information in the history buffer alongside the program content before any potential transfer to DVR. This ensures that when content is moved for permanent storage, all necessary authorization data is already available, preventing DRM violations and ensuring proper content protection throughout the transfer process.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the media device retunes to a different program event, then users can access new content, but the history buffer content of the previous program is lost

Engineering Contradiction:
Improveprogram switchingVSAvoidhistory buffer content
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements segmentation by creating distinct storage segments for each program event in the history buffer. When the media device retunes to a different program, the system allocates a new segment for the incoming program while preserving existing segments for previously viewed programs. This allows users to switch between programs freely without losing access to the history buffer content of previous programs, as each program resides in its own protected segment.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9699495B2Apparatus, systems and methods for storing program events in an enhanced history buffer
Publication Date: 2017.07.04 DISH TECHNOLOGIES LLC
  • US9699495B2 patent drawing
  • US9699495B2 patent drawing
  • US9699495B2 patent drawing

AI summary

Enhanced history buffer systems and methods are operable to temporarily store program content for program events. An exemplary embodiment receives program content corresponding to each of the plurality of program events, generates a unique discrete program content file in the enhanced history buffer for each of the plurality of program events, and stores the received program content for each of the plurality of program events in the associated one of the discrete program content files. Each discrete program content file begins at a known starting location in the enhanced history buffer and ends at a known ending location in the enhanced history buffer.