Content Server Bandwidth Allocation via Fragment Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management systems face challenges in efficiently utilizing and preserving bandwidth, especially with increasing network data traffic, as they struggle to optimize content delivery based on varying downstream bandwidth usage levels.

Innovation Solution

A content server that sends different-sized versions of requested content based on reported downstream bandwidth usage, prioritizing the delivery of larger content fragments that fit within available bandwidth, even if they are requested later, and adjusting delivery to ensure timely receipt by client devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If the content server sends larger content fragments to maximize bandwidth usage, then bandwidth utilization improves, but content delivery timing may be delayed

Engineering Contradiction:
Improvebandwidth utilizationVSAvoidcontent delivery timing
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The content server divides content into multiple fragments of different sizes and sends them in sequence. By segmenting content delivery, the system can fill available bandwidth gaps with smaller fragments while reserving larger fragments for periods of higher bandwidth availability, thus maximizing overall bandwidth utilization while maintaining delivery timing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The content server pre-processes content into multiple size variants and prepares a delivery schedule based on predicted bandwidth patterns. This preliminary preparation allows the server to quickly adapt to actual bandwidth conditions without compromising delivery timing, as the appropriate fragment sizes are already prepared for immediate transmission.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the content server prioritizes sending content requested earlier, then content delivery reliability improves, but bandwidth utilization decreases

Engineering Contradiction:
Improvecontent delivery reliabilityVSAvoidbandwidth utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The content server dynamically adjusts the priority and size of content fragments based on real-time bandwidth conditions. When bandwidth is abundant, the server sends larger fragments for previously requested content. When bandwidth is constrained, the server adapts by sending smaller fragments or prioritizing differently requested content, thus maintaining both reliability and high bandwidth utilization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of content fragment size based on bandwidth availability. Instead of always sending the same size fragments or strictly following request order, the server varies fragment sizes and delivery priorities to match current network conditions, optimizing both reliability and bandwidth usage.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If the content server sends lower quality versions of content, then delivery timing is improved, but content quality deteriorates

Engineering Contradiction:
Improvedelivery timingVSAvoidcontent quality
Core Design Contradiction:
Loss of timeVSManufacturing precision

Solution Approach 1:

The content server segments content into multiple quality versions and transmits them as separate fragments. This allows the receiver to assemble the complete content by combining fragments of varying quality, achieving both timely delivery and high final quality through progressive refinement.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server sends a partial set of content fragments initially (enough for basic functionality or acceptable quality) and continues sending additional fragments to enhance quality over time. This partial action approach ensures timely delivery while progressively improving content quality as bandwidth becomes available.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11509744B2Resource request management using bandwidth allocation and time slots
Publication Date: 2022.11.22 COMCAST CABLE COMM LLC
  • US11509744B2 patent drawing
  • US11509744B2 patent drawing
  • US11509744B2 patent drawing

AI summary

A resource management system may use information regarding the bandwidth status of a downstream communication path to determine what portion of queued content should be sent in the current available bandwidth timeslot. In some embodiments, multiple versions of the same requested content may be available, and the system may select a lower-quality version to send if needed to meet a time deadline included in the original content request.