Intermediate Node Routing for Reliable Slice-Based Web Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication over the Internet is hindered by 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 effectively addressed by current TCP/IP protocols.

Innovation Solution

The use of intermediate nodes that function as both end-user and intermediate devices to enhance communication by improving data routing and delivery, leveraging advanced protocols and architectures to optimize TCP/IP operations and reduce network congestion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

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

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidpacket loss and network congestion
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces intermediate nodes (gateway devices) that act as mediators between end devices and the network. These gateway devices receive data from end devices, encapsulate it in packets with unique identifiers, and manage packet routing. The intermediate nodes buffer and retransmit packets as needed, ensuring reliable delivery even when network conditions are poor, thus resolving the contradiction between achieving data transmission and avoiding packet loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If intermediate nodes are introduced to improve data delivery reliability, then packet loss is minimized, but network complexity increases

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidnetwork architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The gateway devices serve multiple functions: they act as intermediate nodes for packet routing, function as end devices for receiving and sending data, and can also serve as intermediate nodes for other end devices. This multi-functionality reduces the need for dedicated intermediate infrastructure, thereby limiting the increase in network complexity while maintaining improved reliability.

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

3Productivity

If advanced protocols and architectures are used to optimize TCP/IP operations, then network performance is improved, but implementation complexity increases

Engineering Contradiction:
Improvenetwork performanceVSAvoidprotocol implementation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the network functionality into distinct layers: end devices generate data, gateway devices handle packetization and routing, and intermediate nodes manage forwarding. Each component implements a simplified version of the protocol suitable for its specific function, rather than requiring full TCP/IP stack implementation at every node. This segmentation improves network performance while limiting implementation complexity at each individual device.

Inventive Principle:
Principle #1Segmentation

Data Source

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