Tunnel Node Content Slicing for Low-Latency Reliable 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 intermediate nodes that can function both as end-users and intermediate nodes, utilizing advanced protocols like TCP/IP and HTTP to enhance communication by optimizing network traffic management and error correction, enabling persistent connections for improved data transfer efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP/IP protocols are used for reliable data delivery, then data transmission reliability is improved, but network congestion and latency increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent establishes persistent TCP connections between intermediate nodes before data transfer is needed. By pre-establishing these connections during idle periods, the system avoids the time-consuming connection setup process (handshake) when actual data transfer occurs, thereby reducing latency while maintaining reliable TCP-based transmission

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces intermediate nodes that act as mediators in the data transmission path. These nodes pre-establish persistent connections with both clients and servers, buffering and forwarding data through these pre-configured reliable TCP channels. This intermediary approach distributes the connection management burden and reduces end-to-end latency while maintaining transmission reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If persistent connections are established for improved data transfer efficiency, then communication efficiency is improved, but network resource consumption increases

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidnetwork resource consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent makes intermediate nodes doubly functional by enabling them to act both as end-users (clients) and as intermediate relay points simultaneously. This multi-functionality allows a single node to maintain persistent connections with multiple partners, amortizing the connection overhead across multiple data transfers and reducing per-transfer resource consumption while maintaining high efficiency

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

Solution Approach 2:

The intermediate nodes autonomously manage their own persistent connections, including establishing, maintaining, and tearing down connections based on traffic patterns. This self-service capability eliminates the need for external connection management overhead and allows nodes to optimize their own resource usage, balancing efficiency gains against resource consumption

Inventive Principle:
Principle #25Self-service

Data Source

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