Tunnel Node Slice Fetching for Congestion-Resilient Web Transfer

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, duplication, and out-of-order delivery, which affect the overall performance and reliability of data transmission.

Innovation Solution

The implementation of a system that utilizes devices capable of functioning as both end-users and intermediate nodes, leveraging advanced protocols such as TCP/IP and HTTP, to enhance communication by optimizing network traffic management and error correction mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional TCP/IP protocols are used for internet communication, then basic data transfer functionality is provided, but network congestion and unpredictable network behavior cause packet loss, duplication, and out-of-order delivery

Engineering Contradiction:
Improvedata transfer reliabilityVSAvoidnetwork congestion and unpredictable behavior
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary system that sits between the application layer and the TCP/IP protocol stack. This intermediary monitors network conditions, detects congestion patterns, and dynamically adjusts communication parameters before data is transmitted through the network, thereby preventing packet loss and delivery issues caused by network congestion and unpredictable behavior.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-assessing network conditions and pre-adjusting communication parameters before actual data transmission occurs. This includes proactive congestion detection, pre-negotiation of transmission parameters with intermediate nodes, and advance error prevention measures, which eliminate the need for reactive error correction after packet loss occurs.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If intermediate nodes are introduced to improve communication reliability, then error correction and traffic management are enhanced, but system complexity increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements intermediate nodes that can function in multiple roles: they act as standard TCP/IP routing nodes for basic packet forwarding, while simultaneously providing enhanced error correction, congestion management, and reliability monitoring functions. This multi-functionality allows the same infrastructure to handle both simple and complex communication requirements without adding separate dedicated systems for each function.

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

Solution Approach 2:

The intermediate nodes are designed with self-configuring capabilities that automatically detect network conditions and adjust their behavior without requiring manual configuration or complex centralized control. The nodes autonomously negotiate parameters with neighboring nodes, dynamically adapt to changing network conditions, and self-optimize their error correction and traffic management functions, thereby reducing overall system complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12166843B2System and method for improving internet communication by using intermediate nodes
Publication Date: 2024.12.10 BRIGHT DATA LTD
  • US12166843B2 patent drawing
  • US12166843B2 patent drawing
  • US12166843B2 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.