LibraFlow Offloads IP Traffic to Video Channels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The exponential growth of internet video traffic over Hybrid Fiber Coax (HFC) networks causes DOCSIS channels to become overloaded, leading to negative customer satisfaction and increased costs for broadband operators, as DOCSIS channels are designed for burst traffic rather than steady-state flows, and there is no efficient way to utilize the available bandwidth in video channels for IP data transfer.

Innovation Solution

The LibraFlow system transparently offloads IP traffic from DOCSIS channels to non-DOCSIS channels, utilizing available bandwidth in video channels through a performance-enhancing proxy and local caching, allowing for multicast distribution of repetitive content, thereby reducing latency and increasing download speeds without requiring significant upgrades to the HFC plant.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If IP traffic is transferred over DOCSIS channels, then download speed is fast, but network capacity is insufficient and channels become overloaded during peak hours

Engineering Contradiction:
Improvedownload speedVSAvoidnetwork capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments IP traffic into different categories (video streaming, file downloads, P2P, interactive services) and routes them through different channels (DOCSIS for burst traffic, video channels for steady-state traffic). This segmentation allows each channel type to be optimized for its specific traffic pattern, preventing overload while maintaining high download speeds.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension for traffic transport by utilizing video channels (MPEG-2 Transport Stream) alongside the traditional DOCSIS channels. This creates a hybrid transport architecture where traffic can be offloaded from the congested DOCSIS channels to the underutilized video channels, effectively increasing the network capacity dimension.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If video channels are used for IP data transfer, then network capacity is increased, but latency increases due to high delay in video channels

Engineering Contradiction:
Improvenetwork capacityVSAvoidlatency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent implements dynamic traffic routing that adapts to real-time network conditions. The system dynamically decides whether to route traffic through DOCSIS or video channels based on current load, available bandwidth, and traffic type. This dynamic adaptation allows the system to optimize the latency-capacity tradeoff continuously.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary mechanism (traffic classification and routing engine) that sits between the client and the channels. This intermediary classifies traffic, selects the appropriate channel, and manages the transition, thereby mediating the conflict between latency requirements and capacity needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If DOCSIS channels are upgraded to accommodate video traffic, then network capacity is increased, but infrastructure costs increase significantly

Engineering Contradiction:
Improvenetwork capacityVSAvoidinfrastructure cost
Core Design Contradiction:
Quantity of substanceVSEase of manufacture

Solution Approach 1:

The patent makes the video channels serve multiple functions: traditional video broadcasting and IP data transfer. By enabling video channels to carry IP traffic (via MPEG-2 Transport Stream encapsulation), the system extracts the IP traffic function from DOCSIS channels and places it in video channels, making the infrastructure more versatile and reducing the need for expensive DOCSIS upgrades.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent creates a copy of the traffic handling mechanism by replicating the channel infrastructure. Instead of upgrading the expensive DOCSIS channels, the system uses the existing video channel infrastructure (which is cheaper and already deployed) to handle IP traffic, effectively copying the service function to a different physical medium.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If all users share bandwidth on service groups, then infrastructure costs are reduced, but customer satisfaction decreases during peak hours

Engineering Contradiction:
Improveinfrastructure costVSAvoidcustomer satisfaction
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent applies local quality by providing different service characteristics to different traffic types and user groups. Instead of uniform shared access, the system provides prioritized access for video streaming and file downloads through dedicated routing, while maintaining cost-effective shared access for other traffic. This local differentiation improves customer satisfaction without requiring complete infrastructure redesign.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8064479B2Methods and system for efficient data transfer over hybrid fiber coax infrastructure
Publication Date: 2011.11.22 HARMONIC INC
  • US8064479B2 patent drawing
  • US8064479B2 patent drawing
  • US8064479B2 patent drawing

AI summary

The invention is directed to a method for providing client-server data transfer over a Hybrid Fiber Coax network, comprising interfacing, at a client, a channel, wherein the channel is one of a video channel and a DOCSIS channel, intercepting a content request made from an end-user computing device, notifying a server of a relevant intercepted message via one of using an interactive channel and tagging the request, selecting content sent by the server over the channel, processing the content selected so as to return it to its IP traffic format, and forwarding the content in its IP traffic format to the end-user computing device.