Intermediate Node Content Slicing for Congestion-Resilient Web Delivery
Find Innovative SolutionsGenerate 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 devices, utilizing advanced protocols and architectures to enhance data routing and transmission, including the use of TCP/IP, HTTP, and IP protocols, to improve communication efficiency and reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional Internet communication protocols (TCP/IP) are used, then data transmission reliability is maintained through error checking and retransmission, but network congestion and packet loss increase due to unpredictable network behavior
Solution Approach 1:
The patent introduces intermediate nodes that act as mediators between end devices and the core network. These nodes perform local routing, caching, and traffic management functions, reducing the burden on traditional TCP/IP protocols while maintaining reliability. The intermediate nodes can predict traffic patterns and pre-position data, minimizing packet loss and congestion without sacrificing transmission reliability.
Solution Approach 2:
The network architecture is segmented into multiple layers: end devices, intermediate nodes, and core network. This segmentation allows each layer to handle specific functions independently, improving overall network efficiency while maintaining reliability through layered error checking and recovery mechanisms.
2Productivity
If intermediate nodes are introduced to improve routing efficiency, then network congestion is reduced, but device complexity increases due to dual functionality requirements
Solution Approach 1:
Intermediate nodes are designed to perform multiple functions simultaneously: they act as both end devices and routing nodes, provide caching services, perform local traffic management, and maintain connection tracking. This multi-functionality reduces the need for separate dedicated infrastructure while improving routing efficiency.
Solution Approach 2:
Intermediate nodes autonomously manage their own routing tables, cache content locally, and make forwarding decisions without constant centralized control. This self-service capability reduces operational complexity while maintaining high routing efficiency through distributed intelligence.
3Reliability
If advanced protocols are implemented to minimize packet loss, then data transmission reliability improves, but processing overhead and network latency increase
Solution Approach 1:
The system performs preliminary actions by predicting traffic patterns and pre-caching frequently accessed data at intermediate nodes before actual requests arrive. This proactive approach ensures high packet delivery reliability while minimizing latency, as data is already positioned and ready for transmission when needed.
Solution Approach 2:
The patent dynamically adjusts protocol parameters such as timeout values, retransmission thresholds, and cache sizes based on current network conditions. This adaptive parameter tuning maintains high packet delivery reliability while optimizing latency by reducing unnecessary retransmissions and processing overhead during normal operating conditions.
Data Source
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.