Centralized Permission Management for Card Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional permission management systems require users to manage and learn rules for each type of card, leading to cumbersome processes for preventing unauthorized use, as they need to construct separate systems for each card and handle individual lock releases.
Innovation Solution
A permission management apparatus and method that registers rights information, stores use permission status, accepts enabling instructions, provides code information for user terminals, and notifies facility devices about the enabled or disabled status of use permissions, allowing centralized management and prevention of unauthorized use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate permission management systems are constructed for each card type, then security against unauthorized use is improved, but system complexity and user management burden increase
Solution Approach 1:
The patent merges multiple card permission management systems into a single integrated permission management server that handles various card types (cash cards, point cards, etc.). The server receives permission requests from different card types through a unified interface and manages permissions centrally, reducing the number of separate systems needed while maintaining security.
Solution Approach 2:
The permission management server is designed with universal functionality to handle multiple card types through a single system. It provides a unified permission management interface that can process requests for cash cards, point cards, and other card types, making the system adaptable to diverse card types without requiring separate dedicated systems for each.
2Reliability
If separate permission management systems are constructed for each card type, then security against unauthorized use is improved, but ease of operation deteriorates
Solution Approach 1:
The permission management server provides a universal interface that users interact with regardless of card type. Users send permission requests through a single channel (e.g., mobile phone notifications) and receive unified responses, eliminating the need to learn different procedures for different card types while maintaining secure permission control.
Solution Approach 2:
The permission management server acts as an intermediary between users and the facility management systems. It receives permission requests from users via their terminals, processes them centrally, and communicates with the appropriate facility systems, simplifying the user experience by hiding the complexity of multiple underlying systems.
3Ease of operation
If centralized permission management is implemented, then ease of operation is improved, but the load on the centralized system increases
Solution Approach 1:
The system segments the permission management functionality by deploying a distributed network of permission management servers rather than a single centralized server. Each server can handle specific regions or card types, distributing the computational load across multiple nodes while maintaining centralized coordination through standard communication protocols.
Data Source
AI summary
A registration accepting unit accepts registration of a card. A storage unit stores use permission information indicating a disabled state of use permission of the registered card. An instruction accepting unit accepts a use permission enabling instruction of the card from a user terminal. A providing unit provides the user terminal with code information associated with the card for which the use permission enabling instruction has been issued. A changing unit enables the use permission of the card, for which the use permission enabling instruction has been issued and which is stored in the use permission information, for a predetermined period. When receiving the code information from an in-store device installed in a stored, a notifying unit notifies the facility device of whether the use permission of the right that is stored in the use permission information in association with the code information is enabled or disabled.