Intermediate Node Routing for Congestion-Resilient Content 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

Implementing intermediate nodes that function as both end-users and intermediate nodes to enhance communication by optimizing data routing and managing network congestion, using devices that can act as both clients and servers, thereby improving the reliability and efficiency of data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If intermediate nodes are introduced to optimize routing and manage congestion, then data transmission reliability and efficiency are improved, but device complexity and network infrastructure requirements increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork infrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies multi-functionality by enabling end-user devices to simultaneously function as both clients and intermediate nodes. Devices can act as web servers hosting content, perform caching operations, and participate in routing decisions while maintaining their primary end-user functions. This eliminates the need for dedicated intermediate infrastructure, resolving the contradiction by improving reliability without adding device complexity.

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

Solution Approach 2:

The system implements self-service through distributed caching where each device caches web content locally and serves it to other devices when requested. The network automatically routes traffic through appropriate intermediate nodes based on cache availability, without requiring centralized control or complex manual configuration. This self-organizing behavior improves transmission reliability while keeping the system simple to deploy and maintain.

Inventive Principle:
Principle #25Self-service

2Productivity

If devices function as both end-users and intermediate nodes, then network resource utilization and transmission efficiency are improved, but the difficulty of managing and coordinating multiple roles increases

Engineering Contradiction:
Improvenetwork resource utilizationVSAvoidrole management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic role assignment where devices can flexibly switch between acting as clients, servers, or intermediate nodes based on real-time network conditions and resource availability. A device may cache content during low-traffic periods and serve it during high-traffic periods, or route traffic through other devices when congestion is detected. This dynamic adaptability maximizes resource utilization while avoiding the complexity of static multi-role configurations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback mechanisms where devices continuously monitor network conditions, cache hit rates, and traffic patterns to automatically adjust their behavior. When a device detects high demand for cached content, it increases its serving capacity; when congestion is detected, it adjusts routing decisions. This feedback-driven automation improves productivity while eliminating the need for manual role management.

Inventive Principle:
Principle #23Feedback

3Speed

If intermediate nodes are used to reduce congestion and optimize routing, then data transmission speed and efficiency are improved, but the risk of packet loss and duplication in unpredictable network behavior increases

Engineering Contradiction:
Improvedata transmission speedVSAvoidpacket delivery accuracy
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies preliminary action through proactive caching, where web content is cached at intermediate devices before it is actually requested by end users. By anticipating and pre-positioning content in the network, the system reduces transmission speed requirements and minimizes the impact of network unpredictability. Content is delivered from local caches rather than remote servers, ensuring accurate packet delivery while maintaining high speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses intermediate nodes as mediators between content sources and end users. These intermediate devices receive, validate, and forward content through multiple hops, with each intermediate node verifying packet integrity. This intermediary layer isolates end users from network unpredictability, maintaining packet delivery accuracy while enabling faster local delivery from cached content.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260025424A1System and Method for Improving Internet Communication by Using Intermediate Nodes
Publication Date: 2026.01.22 BRIGHT DATA LTD
  • US20260025424A1 patent drawing
  • US20260025424A1 patent drawing
  • US20260025424A1 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.