Intermediate Tunnel Nodes for Congestion-Resilient Content Fetching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Internet communication systems face inefficiencies due to network congestion, traffic load balancing, and unpredictable network behavior, leading to issues such as packet loss, duplication, and out-of-order delivery, which are not adequately addressed by current TCP/IP protocols.

Innovation Solution

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

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP/IP protocols are used for Internet communication, then data delivery is achieved, but network congestion and unpredictable network behavior cause packet loss, duplication, and out-of-order delivery

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

Solution Approach 1:

The patent introduces an intermediary system that sits between the application layer and TCP/IP protocol stack, acting as a mediator to manage data transmission. This intermediary monitors network conditions, implements congestion control mechanisms, and ensures reliable data delivery by handling packet retransmission and ordering, thereby resolving the contradiction between achieving data delivery and avoiding network congestion-related issues.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms where the intermediary system continuously monitors network conditions, packet delivery status, and congestion levels. Based on this feedback, the system dynamically adjusts transmission parameters, implements selective retransmission, and optimizes data flow to maintain reliability while preventing congestion-related packet loss and duplication.

Inventive Principle:
Principle #23Feedback

2Reliability

If intermediate nodes are added to optimize routing and manage congestion, then data transmission reliability improves, but system complexity increases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent designs the intermediary system to perform multiple functions within a single component: it acts as a protocol adapter, congestion controller, packet manager, and routing optimizer simultaneously. By consolidating these functions into one multi-functional intermediary, the patent improves data transmission reliability while minimizing the increase in system complexity that would result from adding separate intermediate nodes for each function.

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

Data Source

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