Bandwidth Broker for IPTV Channel Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IPTV systems face challenges in managing bandwidth efficiently to ensure Quality of Service (QoS) during channel surfing, where frequent allocation and de-allocation of bandwidth lead to inefficiencies and potential service denials due to insufficient bandwidth.

Innovation Solution

A program delivery system that includes a computational device managing bandwidth allocation using a bandwidth broker, which stores state information to determine bandwidth requests and allocates resources based on current usage and channel requirements, switching between unicast and multicast methods as needed to optimize bandwidth utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If bandwidth is allocated and de-allocated frequently during channel surfing, then channel switching capability is improved, but bandwidth management efficiency deteriorates and service denials occur

Engineering Contradiction:
Improvechannel switching speedVSAvoidbandwidth management efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-allocating bandwidth resources and maintaining state information about active programs before channel switching is requested. The bandwidth broker keeps track of allocated bandwidth and program states in advance, so when a channel change occurs, the system can quickly release only the necessary bandwidth without performing full allocation/deallocation cycles, thereby maintaining fast channel switching while improving bandwidth management efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The bandwidth broker implements a feedback mechanism that continuously monitors the state of active programs and currently allocated bandwidth. This feedback loop allows the system to make informed decisions about bandwidth allocation and release, adjusting resources dynamically based on actual usage patterns rather than relying on frequent complete reallocation cycles, thus resolving the contradiction between switching speed and management efficiency

Inventive Principle:
Principle #23Feedback

2Reliability

If bandwidth is allocated for each program request, then QoS is ensured, but bandwidth utilization efficiency deteriorates due to redundant allocations

Engineering Contradiction:
ImproveQoS guaranteeVSAvoidbandwidth utilization efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The bandwidth broker merges bandwidth allocation management for multiple programs by maintaining a consolidated view of allocated resources and their states. Instead of treating each program request as an isolated allocation event, the system combines management of multiple programs under a single broker that tracks overall bandwidth usage, identifies overlapping allocations, and consolidates resource management, thereby ensuring QoS for each program while eliminating redundant bandwidth allocations

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements discarding and recovering by releasing bandwidth resources immediately when programs are no longer active or when lower priority programs replace higher priority ones. The bandwidth broker continuously monitors program states and recovers allocated bandwidth for reallocation to new programs, preventing bandwidth hoarding and ensuring efficient utilization while maintaining QoS guarantees for active programs

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS8763056B2Bandwidth management for packet-based program service
Publication Date: 2014.06.24 VERIZON PATENT & LICENSING INC
  • US8763056B2 patent drawing
  • US8763056B2 patent drawing
  • US8763056B2 patent drawing

AI summary

Method, device, and storage medium for receiving a request for a program from a user device; querying bandwidth state information; identifying whether the bandwidth state information indicates that the user device is allocated bandwidth, based on a previous request for another program, that is at least equal to a required bandwidth to deliver the program; requesting a bandwidth based on an identification that the bandwidth state information indicates that the user device is not allocated bandwidth that is at least equal to the required bandwidth; receiving an indication that the requested bandwidth is provisioned; and deliver the program to the user device.