Packet Traffic Management Device Reverse Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Load balancing systems in networked environments face challenges in maintaining connection flow persistence when servers initiate requests to clients, as existing solutions do not effectively manage reverse persistence information, leading to transparency issues and potential intervention detection by clients.
Innovation Solution
A Packet Traffic Management Device (PTMD) intercepts server requests, generates reverse persistence information, and includes it in the request to clients, allowing it to identify and forward responses back to the originating server while removing evidence of its intervention, thus maintaining connection flow persistence and transparency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a server initiates a communication session by sending a request to a client device through a load balancer, then the server can actively initiate connections, but the load balancer cannot maintain connection flow persistence and clients can detect the load balancer's intervention
Solution Approach 1:
The load balancer acts as an intermediary by injecting persistence tokens into server requests and extracting client identity information from client responses. This mediator approach enables the load balancer to maintain connection flow persistence without clients detecting its intervention, resolving the contradiction between server-initiated communication capability and connection flow persistence reliability
Solution Approach 2:
The load balancer performs preliminary action by injecting persistence tokens into server requests before they reach clients. This preliminary modification of request packets enables the load balancer to track and maintain connection flow persistence throughout the communication session, preventing client detection of the intervention while ensuring reliable connection maintenance
2Reliability
If the load balancer maintains state information to forward server responses to appropriate clients, then connection flow persistence is maintained, but the system complexity increases
Solution Approach 1:
The load balancer extracts only the necessary client identity information from client responses and stores minimal state information (persistence tokens) in its tables. This extraction approach maintains connection flow persistence reliability while significantly reducing the complexity of state information management compared to tracking complete communication sessions
Solution Approach 2:
The load balancer creates simplified copies of client identity information and persistence tokens in its state tables, rather than maintaining complete communication session state. This copying approach preserves the essential information needed for connection flow persistence while reducing the complexity and memory requirements of state management
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments may be directed towards enabling one or more load balance servers to maintain connection flow persistence if the server initiates to the communication to a client. A packet traffic management device may (PTMD) intercept the request from the server and generate reverse persistence information. The PTMD may include a portion of the reverse persistence information in the request before forwarding the request to the targeted client device. The client device may send the response to the PTMD. The PTMD may employ reverse persistence information to identify the target server. The PTMD may remove the reverse persistence information from the response sent by the client and forward the response to the determined server. Removing the reverse persistence information may remove evidence that the PTMD intervened in the connection between the client and server.