Tunnel Node Content Slicing for Congestion-Resilient Web 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

The implementation of intermediate nodes that function as both end-user and intermediate nodes to enhance communication by optimizing data routing and managing network congestion, using devices like web cache servers and HTTP proxy servers to improve response times and reduce network traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional Internet communication protocols are used, then basic data transmission is achieved, but network congestion and unpredictable network behavior cause packet loss, duplication, and out-of-order delivery

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork congestion and packet loss
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 protocol data units (PDUs), and manage transmission through the network. The intermediate nodes handle routing, congestion control, and packet reassembly, thereby resolving the reliability issues caused by network congestion and packet loss without requiring changes to end devices or core network infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If more network infrastructure is added to handle congestion, then network capacity increases, but system complexity and cost increase

Engineering Contradiction:
Improvenetwork throughputVSAvoidnetwork infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent enables end devices to function as their own gateways by implementing the gateway functionality within the end devices themselves. Each end device runs a gateway application that performs data encapsulation, routing decisions, and protocol conversion. This self-service approach allows the network to handle increased traffic loads without adding dedicated intermediate infrastructure, as each device independently manages its own data transmission and can act as an intermediate node for other devices.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If dedicated gateway devices are deployed, then network management and congestion control improve, but device complexity and deployment cost increase

Engineering Contradiction:
Improvenetwork management easeVSAvoidgateway device complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent designs the gateway functionality to be universal and multi-functional, capable of operating in different modes and configurations. The gateway application can function as a standalone device, be integrated into existing end devices, or operate as a virtualized service. It provides multiple functions including data encapsulation, routing, congestion control, and protocol conversion within a single unified system, thereby simplifying deployment and reducing the need for specialized dedicated gateway hardware.

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

Data Source

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