Authentication System Data Synchronization Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication systems face issues with data synchronization among multiple servers, leading to information loss when one server malfunctions, which can prevent proper authentication and render IC cards unusable.
Innovation Solution
An authentication system with a prioritization mechanism between two servers ensures seamless data synchronization without information loss by using synchronization flags and method tables to manage and reflect updates between user, card, group, and user-group information databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If data synchronization is carried out among authentication servers, then data consistency is improved, but information loss occurs when one server malfunctions
Solution Approach 1:
The patent applies preliminary action by establishing synchronization flags and method tables before synchronization occurs. The system pre-configures priority relationships and synchronization methods for different data types, so that when synchronization is needed, the pre-established rules prevent information loss by determining which server's data takes precedence without overwriting critical information.
Solution Approach 2:
The patent introduces synchronization flags and method tables as intermediary mechanisms between authentication servers. These intermediaries mediate the synchronization process by carrying metadata about data priority and synchronization rules, allowing servers to coordinate updates without directly overwriting each other's data, thus preventing information loss while maintaining consistency.
2Reliability
If authentication data is synchronized across multiple servers, then system reliability is improved, but device complexity increases
Solution Approach 1:
The patent segments the synchronization mechanism into distinct components: synchronization flags for indicating update status, method tables for storing synchronization rules, and priority configurations for different data types. This segmentation allows each component to handle specific aspects of synchronization independently, reducing overall system complexity while improving reliability through modular error handling.
Solution Approach 2:
The patent uses parameter changes by introducing synchronization flags and method tables that encode synchronization state and rules. Instead of complex real-time negotiation between servers, the system changes the state representation to include metadata about data priority and synchronization status, simplifying the synchronization logic while maintaining high reliability.
3Loss of time
If user information is updated from one server to another, then data freshness is improved, but risk of overwriting critical information increases
Solution Approach 1:
The patent uses method tables as intermediaries that carry synchronization method information between servers. When user information needs to be updated, the method table specifies whether to use overwrite, merge, or selective update based on data type and priority, preventing critical information from being overwritten while still propagating fresh data appropriately.
Solution Approach 2:
The patent applies local quality by treating different types of user information differently during synchronization. Instead of applying a uniform overwrite rule, the system assigns different synchronization methods to different data fields based on their criticality and update frequency, ensuring that critical information is protected while non-critical data is kept fresh.
Data Source
AI summary
First user information is to be associated with a first user identifier stored in a first authentication apparatus to second user information associated with a second user identifier stored in a second authentication apparatus or the second user information is to be updated to the first user information, if the second user identifier received from the second authentication apparatus is the same as the first user identifier. First card information is to be associated with the first user identifier and stored in the first storage unit, if the first card information corresponding to the second card information stored in the second authentication apparatus is not stored in the first authentication apparatus and a user having the second user identifier associated with the second card information further has the first user identifier stored in the first authentication apparatus.