Local Gateway Intermediary for Reducing Cross-Region Application Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network environments face high latency and decreased throughput due to unnecessary data stream detours across devices in different locations, especially when accessing application resources hosted in foreign locations.
Innovation Solution
A first device acts as an intermediary between a client and a server, evaluating requests and obtaining user context from a second device if necessary, storing it in a cache, and using it to locally route requests, thereby reducing the need for detours and SSL connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a connection proxy model is used to access services hosted on cloud or server, then service accessibility is improved, but latency increases and throughput decreases due to unnecessary data stream detours to foreign locations
Solution Approach 1:
The patent introduces a local gateway module as an intermediary between the client and remote gateway modules. This local gateway acts as a mediator that receives requests locally, determines whether user context is available locally or needs to be obtained from remote gateways, and manages the request routing. By placing this intermediary locally rather than requiring all requests to traverse to foreign locations, the system maintains service accessibility while reducing the latency caused by unnecessary detours.
Solution Approach 2:
The patent implements local context caching at the local gateway module, where user context information is stored locally when available. This allows the system to make decisions based on local quality (local context availability) rather than always requiring remote communication. When context is available locally, requests can be processed without detours to foreign locations, thereby reducing latency while maintaining accessibility.
2Measurement precision
If user context is obtained from remote devices for each request, then access accuracy is improved, but throughput decreases due to repeated round-trip traversals
Solution Approach 1:
The patent implements preliminary action by obtaining user context from remote gateway modules in advance and caching it locally at the local gateway module. Instead of obtaining context for each individual request, the system performs the context acquisition action beforehand and stores it for reuse. This preliminary caching action maintains access accuracy (by ensuring context is available) while dramatically improving throughput by eliminating repeated round-trip traversals for the same context information.
Solution Approach 2:
The patent uses copying by creating local copies of user context information from remote gateway modules. Rather than repeatedly accessing the original remote context, the system copies the necessary context data to local storage at the local gateway module. This copying mechanism ensures access accuracy by maintaining valid context information while improving throughput by allowing multiple requests to use the local copy without additional remote traversals.
3Reliability
If SSL connections are established for each request traversal, then security is improved, but latency increases due to the overhead of multiple SSL handshakes
Solution Approach 1:
The patent applies continuity of useful action by maintaining persistent SSL connections and caching session information at the local gateway module. Instead of establishing new SSL connections for each request traversal, the system maintains continuous authenticated sessions where the SSL handshake is performed once and the security context is preserved. This allows multiple requests to traverse using the established security context without repeating the expensive SSL handshake process, thereby maintaining security while reducing the latency overhead of repeated handshakes.
Data Source
AI summary
Described embodiments provide systems and methods for reducing latency in accessing application resources. The first device may be intermediary between a client and a server, and may receive a request of a user session for an application resource from the server. The first device may determine, responsive to the request that a user context of the user session is with a second device at a second location. The second location can be farther from the server than a first location of the first device. The first device may send, responsive to the determination, a request to the second device to obtain the user context of the user session. The first device may provide the client with access to the application resource via the user session. The first device may provide the client with access to the application resource according to the obtained user context.