Tunnel Node Content Slicing for Congestion-Resilient Internet Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Internet communication technologies face challenges in efficiently managing network congestion, traffic load balancing, and unpredictable network behavior, leading to issues such as packet loss, duplication, and out-of-order delivery, which affect the reliability and efficiency of data transmission.

Innovation Solution

Implementing intermediate nodes that function as both end-user and intermediate devices to enhance communication by optimizing data routing and managing network congestion, utilizing devices with dual functionality to improve data transmission reliability and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If intermediate nodes are introduced to optimize routing and manage congestion, then data transmission reliability and efficiency are improved, but device complexity and network infrastructure requirements increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork infrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies multi-functionality by enabling end-user devices to simultaneously function as both endpoints and intermediate routing nodes. Devices execute application-layer routing protocols to perform packet forwarding, congestion management, and path selection while maintaining their primary end-user functions, thereby eliminating the need for dedicated intermediate networking infrastructure.

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

Solution Approach 2:

The system implements self-service through distributed end-user devices that autonomously perform routing decisions, congestion control, and packet management using application-layer protocols. Each device monitors its own network conditions and independently makes routing decisions without requiring centralized control or specialized intermediate nodes, enabling the network to self-organize and adapt to changing conditions.

Inventive Principle:
Principle #25Self-service

2Reliability

If traditional TCP protocols are used to handle packet loss and retransmission, then data delivery reliability is maintained, but network congestion and transmission delays increase

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidtransmission delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by proactively monitoring network conditions and pre-selecting alternative routing paths before packet loss occurs. The system continuously assesses link quality and congestion levels, and when degradation is detected, it preemptively redirects traffic through alternative paths, preventing packet loss and avoiding the need for time-consuming retransmissions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces application-layer routing protocols as intermediaries between the transport layer and network layer. These protocols act as mediators that monitor network conditions, make intelligent routing decisions, and manage packet flow at the application layer, thereby reducing congestion and delays while maintaining reliable delivery without relying solely on traditional TCP retransmission mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250274530A1System and Method for Improving Internet Communication by Using Intermediate Nodes
Publication Date: 2025.08.28 BRIGHT DATA LTD
  • US20250274530A1 patent drawing
  • US20250274530A1 patent drawing
  • US20250274530A1 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.