Tunnel Node Slice Routing 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 TCP/IP protocols are used for reliable data delivery, then data transmission reliability is improved, but network congestion and packet loss occur due to unpredictable network behavior

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork congestion and packet loss
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces intermediate nodes (relay devices) that act as mediators between end devices in the network. These intermediate nodes receive data packets, manage their transmission, and coordinate retransmissions, thereby reducing direct traffic between end devices and mitigating network congestion while maintaining reliable data delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network into multiple hops involving intermediate nodes. Instead of direct end-to-end communication, data is divided into segments transmitted through multiple intermediate nodes, allowing for better traffic management, error handling at each hop, and reduced impact of network congestion on overall transmission reliability.

Inventive Principle:
Principle #1Segmentation

2Object-affected harmful factors

If intermediate nodes are introduced to manage traffic, then network congestion is reduced, but device complexity increases

Engineering Contradiction:
Improvenetwork congestionVSAvoidintermediate node complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent designs intermediate nodes with multi-functional capabilities, allowing them to perform routing, packet forwarding, error detection, and traffic management functions. This universal design reduces the need for specialized devices for each function, managing complexity while achieving effective congestion control through versatile intermediate nodes.

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

3Reliability

If error detection and correction mechanisms are implemented, then data transmission reliability is improved, but communication efficiency decreases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidcommunication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements error detection and correction mechanisms selectively at intermediate nodes rather than requiring full error handling at every transmission point. This partial application of error correction maintains reliability while reducing the overall overhead and preserving communication efficiency by avoiding redundant error handling operations.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

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