Intermediate Node Slice Fetching for Reliable Web Delivery

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 struggle to address effectively.

Innovation Solution

Implementing a system that utilizes devices capable of functioning as both end-users and intermediate nodes to enhance communication by optimizing TCP/IP protocols, specifically through improved connection management and packet routing techniques.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP/IP protocols are used for reliable data delivery, then data integrity is improved, but network congestion and packet loss increase due to retransmission requests

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidnetwork congestion
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent introduces intermediate nodes (relay devices) that act as mediators between end devices in the network. These intermediate nodes receive, buffer, and forward data packets, reducing the direct communication burden between end devices and minimizing network congestion by distributing traffic through multiple paths.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network into multiple hierarchical levels with end devices, intermediate nodes, and core network infrastructure. This segmentation allows localized data handling at intermediate nodes, reducing the need for long-distance retransmissions and improving overall network efficiency.

Inventive Principle:
Principle #1Segmentation

2Productivity

If intermediate nodes are introduced to improve routing efficiency, then network performance is improved, but device complexity increases

Engineering Contradiction:
Improvenetwork communication efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent designs intermediate nodes with multi-functional capabilities, allowing them to perform routing, buffering, forwarding, and protocol translation functions simultaneously. This universal design reduces the need for specialized devices for each function, thereby managing complexity while improving productivity.

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

Solution Approach 2:

The patent combines multiple network functions (routing, buffering, forwarding) into single intermediate node devices. This merging reduces the total number of separate components needed in the network, simplifying the overall system architecture while maintaining improved communication efficiency.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If end devices directly communicate over the network, then communication speed is improved, but packet loss increases due to network congestion

Engineering Contradiction:
Improvecommunication speedVSAvoidpacket delivery reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements preliminary buffering and routing decisions at intermediate nodes before data packets enter the core network. This preliminary action prepares data for efficient transmission, reducing congestion-related packet loss while maintaining high communication speeds through optimized routing paths.

Inventive Principle:
Principle #10Preliminary action

Data Source

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