Server Protocol Request Processing via Sequential State Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In interactive communication technologies between customer terminals and servers, such as online gaming, the complexity of interactive logic increases with the relevance of protocol requests, leading to higher maintenance costs and instability due to the need for caching and processing multiple requests simultaneously.
Innovation Solution
A protocol request processing method and device where a server determines if it is processing a previous request from a customer terminal before receiving a new request, allowing it to discard the new request if the first is still being processed, thereby reducing complexity and improving stability by ensuring only one request is processed at a time from each terminal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the server processes multiple protocol requests from the same customer terminal simultaneously, then the productivity of the server is improved, but the device complexity increases due to complicated interactive logic and caching requirements
Solution Approach 1:
The patent segments the request processing by introducing a request ID tracking mechanism that divides the processing state into individual trackable units. Each protocol request is assigned a unique request ID, allowing the server to monitor and manage multiple requests independently without complex inter-request dependencies, thus reducing interactive logic complexity while maintaining processing throughput.
Solution Approach 2:
The patent introduces a request tracking intermediary mechanism that mediates between incoming protocol requests and the processing system. This intermediary maintains a mapping between request IDs and their processing states, acting as a buffer that simplifies the interaction logic by centralizing request state management rather than requiring complex point-to-point request handling logic.
2Adaptability or versatility
If the server adds interactive logic for caching protocol requests to handle relevance, then the adaptability improves, but the ease of operation deteriorates due to higher maintenance cost
Solution Approach 1:
The patent creates a universal request tracking mechanism that handles all protocol requests through a common request ID mapping system. This universal approach maintains adaptability for handling relevant requests while simplifying maintenance by providing a single, consistent interface for request state management across all request types, eliminating the need for request-specific caching logic.
Solution Approach 2:
The patent changes the state representation from complex cached request objects to simple request ID status markers. By transforming the request tracking from storing full request contexts to maintaining minimal state information (request ID and processing status), the system maintains adaptability while significantly reducing maintenance complexity through parameter simplification.
3Loss of time
If the server processes protocol requests with high relevance together, then the loss of time is reduced, but the reliability decreases due to potential interference between requests
Solution Approach 1:
The patent applies preliminary action by assigning request IDs and establishing tracking relationships before actual request processing begins. This pre-establishment of request identification and state tracking infrastructure allows the server to efficiently manage multiple concurrent requests while maintaining clear boundaries between them, preventing interference and ensuring reliability without sacrificing processing speed.
Data Source
AI summary
The present disclosure provides a server having a processor-readable storage medium comprising a set of instructions for protocol request processing; and a processor in communication with the storage medium. The processor is configured to execute the set of instructions to provide a communication with a customer terminal through an online platform; receive a second protocol request sent from the customer terminal; determine if the server is processing a first protocol request sent from the customer terminal prior to the second protocol request; process the second protocol request when the server is not processing the first protocol; and discard the second protocol request when the server is processing the first protocol.