Tunnel Node Slice Fetching for Stable Internet Content Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Internet communication systems face challenges in efficiently managing network congestion and ensuring reliable data transfer due to unpredictable network behavior, leading to issues like packet loss and duplication, which existing TCP/IP protocols struggle to address effectively.

Innovation Solution

The implementation of a method that utilizes devices capable of functioning as both end-users and intermediate nodes, leveraging advanced protocols and architectures to enhance traffic management and data routing, potentially incorporating new protocols or mechanisms to improve connection stability and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If traditional TCP/IP architecture is used, then network simplicity is maintained, but network congestion management and traffic load balancing are insufficient

Engineering Contradiction:
Improvenetwork architecture simplicityVSAvoidnetwork efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements intermediate nodes that perform multiple functions simultaneously: packet routing, congestion management, load balancing, and coordination with end devices. This multi-functionality allows a single architectural addition to address multiple network performance issues without requiring separate specialized components for each function, thereby improving network efficiency while maintaining relative architectural simplicity.

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

Solution Approach 2:

The intermediate nodes serve as mediator layers between the simple end-device architecture and the complex network infrastructure. They provide intelligent traffic management and congestion control functions that enhance network productivity without requiring fundamental changes to the underlying TCP/IP architecture or end-device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If end devices directly communicate over the network, then communication speed is maximized, but network congestion and unpredictable behavior lead to packet loss and retransmission delays

Engineering Contradiction:
Improvedata transfer speedVSAvoidretransmission delay
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The intermediate nodes perform preliminary actions by validating packets, checking network conditions, and coordinating transmission timing before packets are sent across the network. This preliminary validation and coordination prevents packet loss and duplication before they occur, eliminating the need for time-consuming retransmission delays while maintaining efficient data transfer speeds.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where intermediate nodes monitor network conditions and communicate status information to end devices. This feedback enables dynamic adjustment of transmission parameters, allowing the system to optimize for speed when network conditions are good and prevent packet loss when congestion is detected, thereby reducing retransmission delays without sacrificing overall transfer speed.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11799985B2System and method for improving internet communication by using intermediate nodes
Publication Date: 2023.10.24 BRIGHT DATA LTD
  • US11799985B2 patent drawing
  • US11799985B2 patent drawing
  • US11799985B2 patent drawing

AI summary

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.