Intermediate Tunnel Nodes for Slice-Based Internet Content Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication technologies over the Internet 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.

Innovation Solution

The use of intermediate nodes that function both as end-users and as intermediate nodes to improve communication efficiency by managing and optimizing network traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If intermediate nodes are used to manage network traffic, then communication reliability is improved, but device complexity increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies multi-functionality by enabling end-user devices to simultaneously function as both end-users and intermediate nodes. This allows devices to perform multiple roles (data transmission and traffic management) without adding dedicated infrastructure, thereby improving reliability while controlling complexity.

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

Solution Approach 2:

The patent introduces intermediate nodes as mediators between end-user devices and the core network. These nodes manage traffic flow, reduce congestion, and improve delivery reliability by acting as buffer and routing points, resolving the contradiction between reliability improvement and system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If intermediate nodes are deployed to optimize traffic flow, then network congestion is reduced, but system complexity increases

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

Solution Approach 1:

The patent implements self-service by enabling intermediate nodes to autonomously manage their own traffic routing and optimization functions. Devices automatically adjust traffic flow based on local conditions without requiring centralized control, improving network efficiency while avoiding the complexity of centralized management systems.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies dynamics by making traffic routing adaptive and flexible. Intermediate nodes dynamically adjust their behavior based on real-time network conditions, allowing the system to optimize performance without rigid complex infrastructure. The system evolves and adapts rather than requiring fixed complex arrangements.

Inventive Principle:
Principle #15Dynamics

3Reliability

If end-user devices function as intermediate nodes, then data delivery is improved, but energy consumption increases

Engineering Contradiction:
Improvedata deliveryVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by enabling only selected end-user devices to function as intermediate nodes based on their capabilities and current state. Not all devices participate in intermediate functions, which distributes the energy burden selectively rather than requiring all devices to consume additional energy, thus improving data delivery while controlling overall energy consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

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