Intermediate Tunnel Nodes for Slice-Based Web Traffic Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current internet communication systems face inefficiencies due to network congestion, traffic load balancing, and unpredictable network behavior, leading to issues like packet loss, duplication, and out-of-order delivery, which existing protocols like TCP/IP struggle to fully address.

Innovation Solution

Implementing intermediate nodes that can function both as end-users and intermediate nodes, utilizing advanced protocols and architectures to enhance data routing, error correction, and congestion management, potentially integrating new protocols like HTTP persistent connections for improved communication efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP/IP protocol is used for internet communication, then reliable data delivery is achieved, but network congestion and packet loss occur due to unpredictable network behavior

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidnetwork communication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces intermediate nodes (gateway devices) that act as mediators between end devices and the network. These gateway devices monitor network conditions, buffer data packets, and intelligently route traffic to avoid congestion, thereby maintaining reliable data delivery while improving overall network efficiency

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway devices perform preliminary actions by pre-buffering data packets and pre-assessing network conditions before actual transmission. This allows the system to proactively manage potential congestion points and optimize routing decisions before packets are lost or delayed

Inventive Principle:
Principle #10Preliminary action

2Productivity

If intermediate nodes are added to manage network traffic, then congestion management improves, but device complexity increases

Engineering Contradiction:
Improvecongestion management capabilityVSAvoidnetwork architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The gateway devices are designed to perform multiple functions: they act as both end devices and intermediate nodes, providing data buffering, network monitoring, traffic routing, and error correction capabilities. This multi-functionality reduces the need for separate dedicated network management devices, thereby managing complexity while improving congestion handling

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

3Reliability

If existing TCP protocol is used, then error-checked delivery is provided, but packet duplication and out-of-order delivery cannot be fully prevented

Engineering Contradiction:
Improveerror-checked deliveryVSAvoidpacket loss and duplication
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The gateway devices implement feedback mechanisms where they monitor the status of transmitted packets and adjust their buffering and retransmission strategies accordingly. This feedback loop enables the system to detect and correct packet loss, duplication, and out-of-order delivery issues that TCP alone cannot handle

Inventive Principle:
Principle #23Feedback

Data Source

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