Authentication Ticket Caching for Self-Contained User Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing authentication-ticket processing systems face performance drops due to frequent database access for user information when multiple decoding requests are made in a short interval, especially for self-contained tickets, where user information changes infrequently, leading to an overreaction and inefficient resource utilization.
Innovation Solution
An authentication-ticket processing apparatus and method that utilize a temporary data storage unit to cache user information, allowing faster access than the user management database, and manage expiration times to ensure accurate and efficient retrieval of user information during decoding requests, thereby reducing the need for frequent database access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user information is acquired from the user management database for each decoding request to ensure data accuracy, then the reliability of user information is improved, but the system performance deteriorates due to frequent database access
Solution Approach 1:
The patent applies preliminary action by acquiring and storing user information in the authentication ticket before the decoding request occurs. The user authentication apparatus retrieves user information from the user management database during the authentication phase (step S3), embeds it in the authentication ticket (step S4), and this cached information is then supplied to service servers without requiring repeated database accesses during subsequent decoding requests. This preliminary acquisition resolves the contradiction by ensuring reliable user information is available while avoiding performance degradation from frequent database access.
Solution Approach 2:
The patent applies copying by creating a copy of user information from the user management database and embedding it within the authentication ticket. The user authentication apparatus copies relevant user information (step S3), incorporates it into the authentication ticket structure (step S4), and this copied information is then distributed to multiple service servers. This copying mechanism allows service servers to obtain accurate user information without directly accessing the user management database, thus maintaining reliability while improving system performance.
2Productivity
If user information is cached in a temporary storage unit to improve access speed, then the system performance is improved, but the risk of providing outdated user information increases
Solution Approach 1:
The patent applies preliminary action by acquiring user information from the user management database during the authentication phase (step S3) before the user's status might change. This pre-acquired information is then embedded in the authentication ticket (step S4) and remains valid for the ticket's duration. By performing the database access preliminarily rather than repeatedly, the system achieves both fast access speed and reliable information currency within the authentication context.
Solution Approach 2:
The patent applies copying by duplicating user information from the user management database into the authentication ticket structure. This copied information is self-contained within the ticket and can be supplied to multiple service servers simultaneously without requiring updates or additional database accesses. The copy ensures that all servers receive consistent, accurate information at the time of authentication while maintaining fast access during service delivery.
3Reliability
If multiple decoding requests are processed sequentially from the user authentication apparatus, then the accuracy of user information is maintained, but the response time increases causing user wait states
Solution Approach 1:
The patent applies merging by consolidating user information acquisition into a single operation during the authentication phase (step S3), rather than performing separate acquisitions for each decoding request. The user authentication apparatus merges the user information retrieval with the authentication process itself, embedding the information in the authentication ticket (step S4). This consolidation eliminates redundant database accesses and allows multiple service servers to simultaneously obtain accurate user information from their respective decoding requests without sequential processing delays.
Solution Approach 2:
The patent applies copying by duplicating user information into the authentication ticket so that multiple service servers can receive identical, accurate copies simultaneously. When multiple decoding requests are made (as shown in FIG. 3), each service server obtains a copy of the user information from its decoded ticket without requiring sequential processing or repeated database accesses. This copying mechanism resolves the contradiction by maintaining information accuracy while enabling parallel service delivery without user wait states.
Data Source
AI summary
An authentication ticket processing apparatus includes a temporary data storage unit configured to keep user information upon receiving the user information from a user management database for managing user information, the temporary data storage unit allowing access thereto to be performed at higher speed than access to the user management database. The authentication ticket processing apparatus is configured such that, when there is a need to acquire user information in response to a decoding request from a server, a check is made whether user information corresponding to the decoding request is present in the temporary data storage unit, and the corresponding user information is acquired from the temporary data storage unit if the corresponding user information is present in the temporary data storage unit.