Distributed Stream Server Selection via Cache Hierarchy Evaluation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

On-demand media streaming systems face inefficiencies in resource utilization and scalability due to lack of high-speed back-side interconnects in distributed architectures, leading to suboptimal cache efficiency and increased risk of service denials.

Innovation Solution

Implementing a distributed streaming system with mechanisms to maximize content uniqueness and balanced load across nodes without a high-speed back-side interconnect, using control software to direct content placement and stream requests, and employing algorithms to optimize caching and resource utilization across multiple nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a shared global cache is implemented with high-speed back-side interconnects, then cache efficiency and content uniqueness are improved, but device complexity and network infrastructure requirements increase

Engineering Contradiction:
Improvecache efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the cache functionality into distributed cache nodes across multiple servers, with each node maintaining unique content. This segmentation eliminates the need for a centralized global cache while achieving similar efficiency through distributed content placement and retrieval mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A load balancer acts as an intermediary component that intelligently directs client requests to appropriate cache nodes based on content location and node availability. This mediator enables efficient cache access without requiring direct high-speed interconnects between all cache nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If content is fractured into small uniform blocks and striped across cache nodes, then cache efficiency and access load balancing are improved, but device complexity increases

Engineering Contradiction:
Improvecache hit rateVSAvoidcontent management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Content is pre-fractured into uniform blocks and assigned to specific cache nodes using deterministic hashing algorithms before any client requests occur. This preliminary organization enables immediate efficient retrieval without requiring complex real-time decision-making about content placement.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If distributed architecture without high-speed back-side interconnect is used, then device complexity is reduced, but cache efficiency and scalability deteriorate

Engineering Contradiction:
Improvesystem simplicityVSAvoidscaling efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The load balancer continuously monitors cache node performance, content hit rates, and system load conditions, using this feedback to dynamically adjust request routing decisions. This feedback mechanism enables the simplified distributed system to achieve scaling efficiency comparable to complex centralized architectures.

Inventive Principle:
Principle #23Feedback

4Productivity

If cache resources are minimized to maximize server scalability, then scalability is improved, but cache hit rate and service reliability worsen

Engineering Contradiction:
Improvesystem scalabilityVSAvoidservice availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system combines multiple distributed cache nodes into a unified virtual cache namespace, where content can be located across any node in the system. This merging approach allows the system to maintain high cache hit rates with minimized individual node capacities, as the collective cache capacity across all nodes provides sufficient buffering while maintaining scalability.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8539103B2Apparatus, system and method for selecting a stream server to which to direct a content title
Publication Date: 2013.09.17 ARRIS ENTERPRISES LLC
  • US8539103B2 patent drawing
  • US8539103B2 patent drawing
  • US8539103B2 patent drawing

AI summary

A method of selecting a stream server of a plurality of stream servers to which to direct a content title, by (a) evaluating a cache ease-of-entry for each of a plurality of levels of a cache hierarchy for the plurality of stream servers; and (b) selecting the stream server from the plurality of stream servers to receive a content title, the selected stream server having a most favorable cache ease-of-entry over the plurality of levels of the cache hierarchy; (c) if none of the plurality of stream servers has a most favorable cache ease-of-entry over the plurality of levels of the cache hierarchy, selecting a stream server of the plurality of stream servers with a lowest miss traffic to which to direct the title; and (d) if none of the plurality of stream servers has a lowest miss traffic, selecting a stream server of the plurality of stream servers with a lowest stream traffic to which to direct the title.