Server Switching Service Request Processing Accuracy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In civil aviation passenger transportation, the switching of servers in an electronic ticket management system can lead to errors when processing service requests due to the loss of contextual associations between requests, resulting in reduced accuracy and incorrect processing.

Innovation Solution

A method and apparatus that determine a target time period based on server switching, acquire log data to identify associated service requests, and correct operation objects to ensure accurate processing by determining if the operation objects of requests processed by different servers are consistent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If server switching is implemented to ensure system availability, then system reliability is improved, but request processing accuracy deteriorates due to loss of contextual associations

Engineering Contradiction:
Improvesystem availabilityVSAvoidrequest processing accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent creates a copy of the request context by storing request association relationships in a cache during the server switch period. This cached context information is then used by the new server to accurately process requests without losing the contextual associations that existed on the previous server, thereby maintaining request processing accuracy while enabling server switching for reliability.

Inventive Principle:
Principle #26Copying

2Productivity

If multiple contextual service requests are processed on different servers, then system throughput is improved, but request association accuracy deteriorates

Engineering Contradiction:
Improvesystem throughputVSAvoidrequest association accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent introduces a cache as an intermediary component that stores request association relationships. When requests are processed across different servers, the cache acts as a mediator that preserves the contextual connections between requests, allowing the system to maintain high throughput through server distribution while ensuring accurate request association through the cached context information.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If server switching occurs during request processing, then system fault tolerance is improved, but request processing completeness deteriorates due to missing context

Engineering Contradiction:
Improvefault toleranceVSAvoidrequest context information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent performs preliminary action by pre-storing request association relationships in the cache before server switching occurs. This ensures that when a server switch happens, the new server can immediately retrieve the necessary context information from the cache, preventing any loss of request context and ensuring complete request processing while maintaining fault tolerance through server switching.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12170706B2Service request processing method, related apparatus, and storage medium
Publication Date: 2024.12.17 TRAVELSKY TECHNOLOGY LIMITED
  • US12170706B2 patent drawing
  • US12170706B2 patent drawing

AI summary

A method and an apparatus for processing a service request, and a storage medium are provided. The method includes: determining a target time period based on a time instant when a first server is switched to a second server; acquiring log data in the target time period; acquiring a first service request and a second service request; determining whether the first service request is associated with the second service request; determining, in a case that the first service request is associated with the second service request, whether an operation object of the first service request is same as an operation object of the second service request; and determining, in a case that the operation object of the first service request is different from the operation object of the second service request, that the operation object of the second service request is incorrect.