Client-Server Transaction Validation With Shared Logic Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client-server environments face challenges in maintaining separate client and server codebases, leading to overhead and potential errors, especially in gaming applications where cheat applications manipulate transactions, compromising game integrity and economy.
Innovation Solution
A method and system for validating transactions using a common logic code on both the client device and server, executing commands on both sides with synchronized state data to ensure security and consistency, reducing the need for separate codebases and communication overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate client codebase and server codebase are maintained, then authoritative decisions can be taken under control, but development time and complexity increase significantly
Solution Approach 1:
The patent merges the common logic code into a single shared repository that is executed on both client and server. This unified codebase eliminates the need for maintaining separate client and server codebases while preserving the ability to make authoritative decisions about transaction validation through server-executed logic.
Solution Approach 2:
The common logic code is designed to be universal, serving multiple functions: it executes on both client devices and servers, validates transactions authoritatively, and maintains consistency across the distributed system. This multi-functional approach reduces overall system complexity while preserving reliability.
2Reliability
If separate client codebase and server codebase are maintained, then transaction validation can be performed, but communication overhead increases
Solution Approach 1:
By merging the logic code into a single shared repository, the system reduces the amount of data that needs to be communicated between client and server. The server only needs to receive transaction requests and send validation results, rather than synchronizing entire codebases, significantly reducing communication overhead.
3Reliability
If client device communicates with server only to get failure result, then transaction can be rejected, but additional communication overhead is caused
Solution Approach 1:
The server executes the common logic code in advance to determine transaction validity before the client needs to proceed. This preliminary validation allows the system to make authoritative decisions about transaction rejection without requiring additional communication cycles, as the validation result is already determined when the client sends the transaction request.
Data Source
AI summary
Disclosed is a method (300) of validating a transaction in a client-server environment, the method comprising: receiving a transaction request from a user at a client device (102); executing a command at the client device associated with the transaction request based on a state data corresponding to the user at the client device; transmitting a request by the client device to a server (104) for execution of the command at the server, upon the command being executed at the client device; executing the command by the server using a copy of the state data stored on the server, upon receiving the request from the client device, for validating the transaction associated with the transaction request at the client device by the server; and performing one of: allowing the transaction or preventing the transaction, at the client device by the server, based on the execution of the command at the server.