License management system, license management method and license management program
First Claim
1. A license management system that is connected to an authentication database comprising a first data group in which user IDs and user-type IDs are associated with one another and a second data group in which application function IDs and the user-type IDs are associated with one another, the user-type IDs being each given a priority level, the license management system comprising:
- a data receiver configured to receive a user ID and an application function ID, the user ID being a code to identify a user, the application function ID being a code to identify an application function and being identified by a user'"'"'s operation of a screen for an application function;
a data reader configured to determine whether a user-type ID, which is associated with the user ID received by the data receiver and is a code to identify the type of the user, exists in the first data group of the authentication database, to read out the user-type ID from the authentication database if the user-type ID exists, to read out from the second data group of the authentication database a user-type ID associated with the application function ID received by the data receiver, to compare the priority levels given to the two user-type IDs, and to read out from the authentication database a license ID which is associated with the user-type ID whose priority level is higher, the license ID being a code to identify the license, the data reader being further configured to, when the user-type ID does not exist as a result of determination by the data reader, read out from the second data group of the authentication database a user-type ID associated with the application function ID, and to read out from the authentication database a license ID associated with the user-type ID;
a license confirmation processor configured to confirm the content of a license which is associated with the license ID read out by the reader from the authentication database and whether the license is correct on the basis of the confirmed content, and to allow login by the user only when the license is correct; and
a user-type registration processor configured to, when any user-type ID associated with the user ID does not exist in the first data group of the authentication database as a result of determination by the data reader, register the user-type ID, which is read out from the second data group of the authentication database, in the first data group of the authentication database so that the user-type ID is associated with the user ID, the user-type registration processor being further configured to, when any user-type ID associated with the user ID exists in the first data group of the authentication database as a result of determination by the data reader, register in the first data group of the authentication database the user-type ID whose priority level is higher so that the user-type ID is associated with the user ID.
1 Assignment
0 Petitions
Accused Products
Abstract
A license management system is connected to an authentication database holding information about license and user and manages a plurality of licenses. The system comprises a data receiving section, a data reading section and a license confirmation section. The data receiving section receives a user ID which is a code to identify a user. The data reading section reads out from the authentication database a user-type ID which is associated with the received user ID and is a code to identify the type of the user, and reads out from the authentication database a license ID which is associated with the user-type ID and is a code to identify the license. The license confirmation section confirms the content of a license which is associated with the read-out license ID and whether the license is correct on the basis of the confirmed content, and allows login by the user only when the license is correct.
31 Citations
8 Claims
-
1. A license management system that is connected to an authentication database comprising a first data group in which user IDs and user-type IDs are associated with one another and a second data group in which application function IDs and the user-type IDs are associated with one another, the user-type IDs being each given a priority level, the license management system comprising:
-
a data receiver configured to receive a user ID and an application function ID, the user ID being a code to identify a user, the application function ID being a code to identify an application function and being identified by a user'"'"'s operation of a screen for an application function; a data reader configured to determine whether a user-type ID, which is associated with the user ID received by the data receiver and is a code to identify the type of the user, exists in the first data group of the authentication database, to read out the user-type ID from the authentication database if the user-type ID exists, to read out from the second data group of the authentication database a user-type ID associated with the application function ID received by the data receiver, to compare the priority levels given to the two user-type IDs, and to read out from the authentication database a license ID which is associated with the user-type ID whose priority level is higher, the license ID being a code to identify the license, the data reader being further configured to, when the user-type ID does not exist as a result of determination by the data reader, read out from the second data group of the authentication database a user-type ID associated with the application function ID, and to read out from the authentication database a license ID associated with the user-type ID; a license confirmation processor configured to confirm the content of a license which is associated with the license ID read out by the reader from the authentication database and whether the license is correct on the basis of the confirmed content, and to allow login by the user only when the license is correct; and a user-type registration processor configured to, when any user-type ID associated with the user ID does not exist in the first data group of the authentication database as a result of determination by the data reader, register the user-type ID, which is read out from the second data group of the authentication database, in the first data group of the authentication database so that the user-type ID is associated with the user ID, the user-type registration processor being further configured to, when any user-type ID associated with the user ID exists in the first data group of the authentication database as a result of determination by the data reader, register in the first data group of the authentication database the user-type ID whose priority level is higher so that the user-type ID is associated with the user ID. - View Dependent Claims (2, 3, 4)
-
-
5. A license management method of managing a plurality of licenses in a license management system connected to an authentication database comprising a first data group in which user IDs and user-type IDs are associated with one another and a second data group in which application function IDs and the user-type IDs are associated with one another, the user-type IDs being each given a priority level, the method comprising:
-
a data receiving step that a data receiver receives a user ID and an application function ID, the user ID being a code to identify a user, the application function ID being a code to identify an application function and being identified by a user'"'"'s operation of a screen for an application function; a data reading step that a data reader determines whether a user-type ID, which is associated with the received user ID and is a code to identify the type of the user, exists in the first data group of the authentication database, read out the user-type ID from the authentication database if the user-type ID exists, reads out from the second data group of the authentication database a user-type ID associated with the application function ID received by the data receiver, compares the priority levels given to the two user-type IDs, and reads out from the authentication database a license ID which is associated with the user-type ID whose priority level is higher, the license ID being a code to identify the license, and the data reader further, when the user-type ID does not exist as a result of determination by the data reader, reads out from the second data group of the authentication database a user-type ID associated with the application function ID, and reads out from the authentication database a license ID associated with the user-type ID; a license confirmation step that a license confirmation processor confirms the content of a license which is associated with the read-out license ID and whether the license is correct on the basis of the confirmed content, and allows login by the user only when the license is correct; and a user-type registration step that a user-type registration processor, when any user-type ID associated with the user ID does not exist in the first data group of the authentication database as a result of determination by the data reader, registers the user-type ID which is read out from the second data group of the authentication database, in the first data group of the authentication database so that the user-type ID is associated with the user ID, and the user-type registration processor further, when any user-type ID associated with the user ID exists in the first data group of the authentication database as a result of determination by the data reader, register in the first data group of the authentication database the user-type ID whose priority level is higher on that the user-type ID is associated with the user ID. - View Dependent Claims (6)
-
-
7. A non-transitory computer-readable medium stored therein a license management program that is installed on a license management system connected to an authentication database comprising a first data group in which user IDs and user-type IDs are associated with one another and a second data group in which application function IDs and the user-type IDs are associated with one another, the user-type IDs being each given a priority level, the license management program causing a computer to function as the license management system, wherein
the license management system includes: -
a data receiver configured to receive a user ID and an application function ID, the user ID being a code to identify a user, the application function ID being a code to identify an application function and being identified by a user'"'"'s operation of a screen for an application function; a data reader configured to determine whether a user-type ID, which is associated with the received user ID and is a code to identify the type of the user, exists in the first data group of the authentication database, to read out the user-type ID from the authentication database if the user-type ID exists, to read out from the second data group of the authentication database a user-type ID associated with the application function ID received by the data receiver, to compare the priority levels given to the two user-type IDs, and to read out from the authentication database a license ID which is associated with the user-type ID whose priority level is higher, the license ID being a code to identify the license, the data reader being further configured to, when the user-type ID does not exist as a result of determination by the data reader, read out from the second data group of the authentication database a user-type ID associated with the application function ID, and to read out from the authentication database a license ID associated with the user-type ID; a license confirmation processor configured to confirm the content of a license which is associated with the read-out license ID and whether the license is correct on the basis of the confirmed content, and to allow login by the user only when the license is correct; and a user-type registration processor configured to, when any user-type ID associated with the user ID does not exist in the first data group of the authentication database as a result of determination by the data reader, register the user-type ID, which is read out from the second data group of the authentication database, in the first data group of the authentication database so that the user-type ID is associated with the user ID, the user-type registration processor being further configured to, when any user-type ID associated with the user ID exists in the first data group of the authentication database as a result of determination by the data reader, register in the first data group of the authentication database the user-type ID whose priority level is higher so that the user-type ID is associated with the user ID. - View Dependent Claims (8)
-
Specification