Server Request Identifier Mechanism for Double Booking Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic-commerce transaction systems face challenges in preventing double booking of requests due to repeated submissions by users, leading to unintended processing of duplicate requests, which can result in financial losses and user confusion.
Innovation Solution
Implementing a server-side method that recognizes repeated booking requests and assigns prepared response data to them, preventing further processing and ensuring seamless user experience by swapping responses, thereby avoiding double booking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server returns an intermediate webpage warning the user to wait, then user patience is encouraged, but double booking may still occur due to network issues or user impatience
Solution Approach 1:
The patent introduces a request identifier mechanism as an intermediary between the client and server. The server assigns a unique identifier to each booking request and includes it in the response. The client stores this identifier and uses it to detect duplicate requests by comparing identifiers, thereby preventing double booking without requiring complex user interactions or intermediate warning pages.
Solution Approach 2:
The system implements feedback by having the server return request identifiers in responses and having the client use these identifiers to detect and prevent duplicate submissions. This feedback loop allows the system to automatically identify and block duplicate booking attempts without user intervention, resolving the contradiction between reliability and ease of operation.
2Productivity
If the server processes each request independently, then request handling is simple, but repeated requests lead to double booking and financial losses
Solution Approach 1:
The patent applies preliminary action by having the server assign a unique request identifier to each booking request at the time of receipt, before processing is complete. This identifier is stored and used in subsequent responses. When duplicate requests are detected through identifier comparison, they can be immediately rejected without full processing, thus maintaining high productivity while ensuring transaction accuracy.
Solution Approach 2:
The system replaces the mechanical approach of re-processing each request with a computational identifier comparison mechanism. Instead of independently processing each request (which risks double booking), the system uses identifier matching to detect duplicates and prevent re-processing, thereby maintaining productivity while improving transaction accuracy.
3Reliability
If the server prevents processing of repeated requests, then double booking is avoided, but legitimate repeated requests may be incorrectly blocked
Solution Approach 1:
The patent applies local quality by making the request identifier unique to each specific booking request context. The identifier includes information that allows the system to distinguish between legitimate repeated requests (such as retries after network failures) and erroneous duplicate submissions. This localized uniqueness enables selective prevention of double booking while allowing legitimate repeated requests to proceed.
Solution Approach 2:
The system changes parameters by using unique request identifiers that encode information about the request context, timing, and source. By analyzing these identifier parameters, the server can distinguish between malicious duplicate submissions and legitimate retries, thereby maintaining reliability while adapting to different request scenarios.
Data Source
AI summary
Methods, systems, and computer program products for preventing double processing of a repeated or duplicated booking request received from a client in a transaction session over a computer network. A first booking request is received from the client over the computer network and processed. When a second booking request repeating or duplicating the first booking request is received from the client, response data prepared in response to the first booking request is assigned to the repeated booking request. A response to the repeated booking request is returned to the client. The response includes the response data prepared in response to the first booking request.