Non-Direct URL Fetching with Dynamic Proxy Routing to Bypass Blocking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication over the Internet faces challenges in overcoming Internet blocking and optimizing the usage and management of non-direct fetching services, particularly in scenarios involving intermediate nodes and protocols like TCP/IP, HTTP, and HTTPS, which are vulnerable to network congestion, traffic load balancing, and security threats such as man-in-the-middle attacks.
Innovation Solution
A non-direct fetching scheme is employed using intermediate nodes, such as proxy servers and tunnel devices, with dynamic selection of fetching mechanisms based on real-time updates to a Proxy Auto-Configuration (PAC) file, and implementation of quotas for data usage, to enhance communication security and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If direct URL fetching is used, then network simplicity is maintained, but Internet blocking and security threats cannot be overcome
Solution Approach 1:
The patent introduces intermediate nodes (proxies, tunnels, gateways) between the client and destination server. These intermediaries route traffic through alternative paths to bypass blocking, perform deep packet inspection to detect security threats, and enable non-direct fetching while maintaining network functionality.
2Object-affected harmful factors
If non-direct fetching service is implemented, then Internet blocking is overcome, but service management complexity increases
Solution Approach 1:
The system automatically manages non-direct fetching services by having clients configure proxy settings and PAC files without manual intervention. The infrastructure autonomously handles traffic routing, protocol translation, and connection management, reducing operational complexity despite the added functionality.
3Reliability
If intermediate nodes are used for non-direct fetching, then communication security is enhanced, but network performance decreases
Solution Approach 1:
The patent applies different handling strategies to different traffic types at intermediate nodes. Critical security-sensitive traffic receives deep inspection and encryption, while less sensitive traffic uses faster but less secure paths. This localized differentiation maintains security where needed while preserving overall network performance.
4Adaptability or versatility
If dynamic fetching mechanisms are implemented, then adaptability to network conditions improves, but system complexity increases
Solution Approach 1:
The system dynamically adjusts fetching mechanisms based on real-time network conditions, PAC file updates, and traffic characteristics. Clients automatically select optimal proxies and routing paths without manual reconfiguration, enabling adaptability through automated decision-making rather than complex manual management.
Data Source
AI summary
A method for providing and managing non-direct URL fetching service for retrieving a content from a web server to a client device is disclosed, such as for overcoming geo-blocking or a Man-In-The-Middle (MITM) attack. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. A URL request may be sent in parallel using both direct and non-direct fetching schemes, in order to verify the need for using the non-direct fetching service. Director non-direct fetching scheme may be selected by using a file that associates a fetching scheme to the requested URL. The selection of the fetching mechanism may use dynamically in real-time updating of a Proxy Auto-Configuration (PAC) file. As part of an accounting scheme, quotas may be applied to a cumulative received data or a time duration of using a non-direct fetching service.