Service Providing System Temporary Use Code Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud service systems, the use of temporary use codes such as PIN codes becomes cumbersome as the number of services and users increases, leading to long codes with short validity periods, which are inconvenient for users.
Innovation Solution
A service providing system that creates and manages temporary use codes with customizable attributes like length and validity period, ensuring they are easily usable by allowing each code space to have distinct settings, preventing code collisions and optimizing code length and validity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the number of services and users increases, then the system can provide more functionality, but the temporary use codes become longer and validity periods become shorter
Solution Approach 1:
The patent divides the code space into multiple segments (first code space and second code space) with different attributes. Each segment serves specific services or user groups, allowing the system to accommodate more services and users without increasing code length or reducing validity periods for individual segments.
Solution Approach 2:
Different code spaces are assigned different properties (length, validity period, service scope) according to local needs. For example, one code space may have shorter codes with longer validity for internal services, while another has longer codes with shorter validity for external users, optimizing usability for each specific context.
2Ease of operation
If temporary use codes are made shorter for ease of use, then usability improves, but the risk of code collisions increases
Solution Approach 1:
By segmenting the code space, the patent reduces the probability of collisions within each segment. Even though individual codes are short, the divided structure ensures that codes from different segments do not collide, maintaining reliability while keeping codes user-friendly.
Solution Approach 2:
The patent introduces an intermediary verification mechanism that checks whether a temporary use code is valid before processing requests. This mediator layer prevents collision-related errors by verifying code authenticity against the server, ensuring reliability even with shorter codes.
3Ease of operation
If the validity period of temporary use codes is extended, then user convenience improves, but security risks increase
Solution Approach 1:
The patent assigns different validity periods to different code spaces based on their specific security requirements and usage scenarios. Critical services can have shorter validity periods for enhanced security, while less sensitive services can have longer validity periods for improved user convenience, achieving a balanced security-convenience trade-off.
Solution Approach 2:
The system dynamically adjusts the validity period of temporary use codes based on service type, user role, and security requirements. This dynamic configuration allows the system to optimize both security and user convenience for each specific case rather than using a fixed validity period for all codes.
4Device complexity
If a unified code space is used for all services, then system complexity is reduced, but code collisions become more frequent
Solution Approach 1:
The patent implements segmentation of the code space into multiple independent segments, each managed separately. This reduces collision frequency within segments while the overall system complexity remains manageable through standardized management mechanisms for multiple segments.
Solution Approach 2:
The patent provides universal management functions that work across all code spaces, such as unified verification protocols and code generation algorithms. This multi-functionality allows the system to manage multiple segmented code spaces without proportionally increasing complexity, as the same management principles apply to each segment.
Data Source
AI summary
A service providing system includes an application configured to provide a service to a terminal device that has made a service request including use identification information; a creator configured to create group identification information for identifying a group of the use identification information, based on a creation request from the application; an issuer configured to issue the use identification information associated with the group identification information, based on an issue request from the application, the issue request including the group identification information; and a verifier configured to verify the use identification information, based on a verification request from the application, the verification request including the group identification information and the use identification information. The application includes a verification requester configured to send the verification request to the verifier; and a process executor configured to execute a process in response to the service request, when the verification result is successful.