Routing Agents for Geographically Distributed Client Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current management systems fail to deliver requests and responses between client devices connected to different geographically dispersed management systems, leading to wasted computing, networking, and communication resources due to unidirectional information flows and lack of synchronization.
Innovation Solution
Implementing an end-to-end request-response flow routing system that uses outbound and inbound routing agents to route requests and responses across geographically distributed management systems, ensuring delivery regardless of the management systems' connection status, and persisting requests for later delivery when devices reconnect.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current management systems are used for geographically distributed client devices, then each management system can independently manage local client devices, but requests and responses cannot be delivered between different management systems, leading to resource waste
Solution Approach 1:
The patent introduces a routing agent as an intermediary component that mediates request-response communication between geographically distributed management systems. The routing agent receives requests from one management system, determines the appropriate destination management system, forwards the request, and routes the response back to the original requester. This intermediary mechanism enables reliable cross-system communication while preventing resource waste from undelivered requests.
Solution Approach 2:
The patent segments the request-response routing function into distinct components: outbound routing agents that handle request forwarding and inbound routing agents that handle response routing. Each management system can have multiple routing agents that independently manage routing decisions. This segmentation allows the system to handle distributed communication reliably without requiring complete system-wide coordination, reducing overall system complexity and resource consumption.
2Reliability
If requests are sent to client devices that may be disconnected, then requests can be queued for later delivery, but the routing process becomes more complex
Solution Approach 1:
The patent implements preliminary action by having routing agents pre-determine and cache the location information of client devices and management systems. Before routing requests, the system performs preliminary lookups to identify the correct destination. Requests can be pre-queued with routing information attached, so when client devices reconnect, the routed requests are already prepared for immediate delivery. This preliminary preparation reduces the complexity of real-time routing decisions.
Solution Approach 2:
The routing agent acts as an intermediary that maintains routing state and device location information, separating the complexity of tracking disconnected devices from the core request-processing logic. The routing agent absorbs the complexity of handling reconnection scenarios by maintaining a cache of device locations and managing the queuing/retry logic, thereby simplifying the overall system architecture.
3Ease of operation
If unidirectional information flows are used in management systems, then system operation is simpler, but resource waste occurs due to lack of synchronization
Solution Approach 1:
The patent implements feedback mechanisms through the request-response routing system. When a request is sent from one management system to another, the response flows back through the routing agent to the original requester. This feedback loop ensures that communication resources are not wasted on undelivered requests, as the system can track whether responses are successfully delivered. The feedback mechanism maintains operational simplicity by using standard request-response patterns while preventing resource waste.
Data Source
AI summary
A first device may receive, from a first client device, a request for information from a second client device, wherein the second client device is connected to a second device that is geographically separated from the first device, and the first device is hosted in a first cloud computing environment and the second device is hosted in a second cloud computing environment. A first outbound routing agent associated with the first device may route the request to a second outbound routing agent associated with the second device, wherein the second outbound routing agent routes the request to the second client device to cause the second client device to generate a response. A first inbound routing agent associated with the first device may receive the response from a second inbound routing agent associated with the second device, and may provide the response to the first client device.