JP4052049B2 - License management terminal and application execution terminal - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a license management terminal that performs license management of an application, and an application execution terminal.
[0002]
[Prior art]
There is known a license management system that manages application usage rights so that an application execution terminal (client terminal) that receives license information issued from a license management terminal (management server) uses the application (for example, see Japanese Patent Application Laid-Open (JP-A)). 2001-142689). The management server issues license information to the client terminal that has requested the license information, and permits the client terminal to use the application. The management server manages the number of license information issued, and prohibits subsequent issuance when the number reaches the limit value.
[0003]
[Problems to be solved by the invention]
In the management server described above, when there is an application execution terminal that is not used while the application is activated, it is not possible to distinguish between an application execution terminal that is being used and an application execution terminal that is not being used. For this reason, when the number of license information issued reaches the limit value, even if there is a terminal that is not used while the application is activated, the license information cannot be issued to a terminal that has newly obtained license information.
[0005]
[Means for Solving the Problems]
(1) A license management terminal according to the present invention includes a license information issuing unit that issues license information that permits application activation in response to an issuance request transmitted from an application execution terminal, and the number of license information issued by the license information issuing unit. A counting means for counting the license information, a prohibiting means for instructing the license information issuing means to prohibit the issuance when the count number by the counting means reaches a limit value, and if the difference between the count number and the limit value is less than a predetermined number, When the monitoring means starts monitoring whether or not the application is being executed on the issued application execution terminal and the monitoring means obtains information indicating that the application is not being executed at the application execution terminal, the count number is subtracted from the count means. Subtracting instruction means for instructing And wherein the door.
[0006]
(2) An application execution terminal according to the present invention receives license information request means for sending a license information issuance request for starting an application to the license management terminal in response to an application starting operation, and license information issued by the license management terminal. Application launching means for launching an application, and if the difference between the license limit value and the number of issued licenses is less than a predetermined number, a command sent from the license management terminal is received to determine whether the launched application is being executed A determination unit that performs a predetermined warning when the determination unit determines that the non-execution is being performed, and an application end unit that terminates the application when the determination unit determines that the non-execution is being performed after the warning, and the determination unit executes If it is judged as medium, go to the license management terminal Sends information indicating that the application running, determining means, characterized in that it comprises a determination information sending means for sending information indicating that the application is not executed to the license management terminal when it is determined in a non-running after warning.
(3) In the application execution terminal according to claim 2, the warning may be a notice that the application is to be terminated.
(4) The application execution terminal according to claim 3 may further include a time measuring unit that starts measuring a predetermined time when the determination unit determines that the non-execution is being performed. In this case, the application ending unit terminates the application when the determination unit determines that the non-execution is in progress after the predetermined time is measured by the time measuring unit, and the determination information sending unit measures the predetermined time by the time measuring unit. If the determination means determines that the application is being executed after that, information indicating that the application is being executed is sent to the license management terminal. If the determination means determines that the application is not being executed after a predetermined time has been counted by the time measurement means, the license management terminal It is preferable to send information indicating that the application is not being executed.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a configuration diagram of a license management system using a license management terminal and an application execution terminal according to an embodiment of the present invention. In FIG. 1, a license management system includes a plurality of terminals (hereinafter referred to as clients) 10A to 10F that execute applications and license management terminals (hereinafter referred to as servers) 20 that perform license management of applications. Are connected to each other. The network may be a wired connection or a wireless connection.
[0008]
FIG. 2 is a diagram illustrating the configuration of the client 10 (10A to 10F). The client 10 includes a CPU 11, a memory 12, an I / O port 13, an input device 14, and an output device 15, which are connected to each other via a system bus 16. The memory 12 includes data storage media such as RAM, ROM, and hard disk drive. The input device 14 includes a keyboard, a pointing device, a data reading device, and the like. The output device 15 includes a display device, a playback device such as a speaker, and a printer.
[0009]
The memory 12 stores programs such as an OS (Operating System), client license management software, and application software. Of the application software, usage restrictions are given to the applications that are subject to license management. The use restriction is to limit the number of clients that use the application at the same time to the number determined by the license agreement or less. When executing the license management target application, the client 10 receives the permission from the server 20, reads the program from the memory 12 as necessary, and executes the program on the CPU 11. When the client 10 executes a non-target application for license management, the client 10 reads the program from the memory 12 and executes it on the CPU 11 as necessary.
[0010]
FIG. 3 is a diagram for explaining the configuration of the server 20. The server 20 includes a CPU 21, a memory 22, an I / O port 23, an input device 24, and an output device 25, which are connected to each other via a system bus 26. The memory 22 includes data storage media such as RAM, ROM, and hard disk drive. The input device 24 includes a keyboard, a pointing device, a data reading device, and the like. The output device 25 is configured by a display device, a printer, or the like.
[0011]
The memory 22 stores an OS and a server license management software program for managing licenses of applications executed on the client 10. The server 20 reads out the management program from the memory 22 and executes it by the CPU 21, thereby managing the license of the application. The memory 22 may store a program for executing other applications in addition to license management.
[0012]
The memory 22 further stores contract information related to the application for license management. The server 20 performs license management for the application corresponding to the contract information. The contract information includes an application name for each license contract, an expiration date, the number of licenses N, and the like. The expiration date is a period during which use of the application is permitted by the license agreement. The number of licenses N is the number of clients (limit value) that are permitted to use the application at the same time according to the license agreement.
[0013]
In the license management system according to the present embodiment, the server 20 gives the client 10 permission to execute an application to be licensed, and monitors whether the client 10 is actually using the application. Is.
[0014]
FIG. 4 is a flowchart for explaining the flow of the client license management process performed by the CPU 11 of the client 10. The program for executing the processing shown in FIG. 4 is started when a starting operation is performed by an operator on the client side. In step S10 in FIG. 4, the CPU 11 determines whether or not there is a request for starting an application to be licensed. The CPU 11 makes a positive determination in step S10 when the activation operation of the application is performed, and proceeds to step S11. If the activation operation of the application is not performed, the CPU 11 makes a negative determination in step S10, and performs the determination process of step S10. repeat.
[0015]
In step S11, the CPU 11 transmits information indicating a license issuance request to the server 20, and proceeds to step S12. In step S12, the CPU 11 determines whether or not the execution of the application is permitted. The CPU 11 makes an affirmative decision in step S12 when information indicating execution permission is received from the server 20 and proceeds to step S13, and makes a negative determination in step S12 when information indicating execution impossibility is received from the server 20. FIG. The process by is terminated.
[0016]
In step S <b> 13, the CPU 11 reads the application software program from the memory 12 and executes it. When starting to use the application, the CPU 11 proceeds to step S13A. In step S <b> 13 </ b> A, the CPU 11 determines whether or not the monitoring process has been activated on the server 20. When the CPU 11 receives an instruction to check whether or not the application is being used from the server 20, the CPU 11 makes an affirmative determination in step S13A and proceeds to step S14. If the CPU 11 does not receive an instruction to check whether or not the application is being used from the server 20, the CPU 11 makes a negative determination in step S13A and repeats the determination process.
[0017]
In step S14, the CPU 11 determines whether an application is being used. The CPU 11 calculates the load status of the CPU 11 from the number of processing instructions per predetermined time, the number of memory accesses, and the like. If the load status is equal to or greater than the predetermined value, an affirmative determination is made in step S14 and the process proceeds to step S15. On the other hand, if the load status is less than the predetermined value, the CPU 11 makes a negative determination in step S14 and proceeds to step S16.
[0018]
If the CPU 11 makes a positive determination in step S14, the CPU 11 considers that the application is being used. In step S15, the CPU 11 transmits information indicating that the application is being used to the server 20, and returns to step S14. If the CPU 11 makes a negative determination in step S14, the CPU 11 considers that the application is not being used. In step S16, the CPU 11 activates the warning process and proceeds to step S18 when a predetermined time has elapsed since the activation of the warning process. In the warning process, for example, a warning content “Exiting the application” is displayed in a pop-up on the screen of the display device, or the warning content is reproduced by sound from a speaker. The warning process program is stored in the memory 12.
[0019]
In step S18, the CPU 11 determines again whether or not the application is being used. The CPU 11 calculates the load status of the CPU 11 in the same manner as in step S14. If the load status is equal to or greater than the predetermined value, the CPU 11 makes an affirmative determination in step S18 and proceeds to step S17. If the load status is less than the predetermined value, the CPU 11 denies step S18. Determine and proceed to step S19. In step S17, the CPU 11 transmits information indicating that the application is being used to the server 20, and returns to step S14. In step S19, the CPU 11 starts a stop process and proceeds to step S20. The stop process program is stored in the memory 12.
[0020]
In step S20, the CPU 11 saves the file used in the application in the memory 12, and saves the set operating environment such as various data and flags in the memory 12, and proceeds to step S21. In step S21, the CPU 11 ends the application and proceeds to step S22. In step S22, the CPU 11 transmits an application end notification to the server 20, and ends the processing of FIG.
[0021]
FIG. 5 is a flowchart for explaining the flow of the server license management process performed by the CPU 21 of the server 20. The program for executing the processing in FIG. 5 is started when a start operation is performed by an operator on the server side. In step S30 in FIG. 5, the CPU 21 determines whether or not there is a license issue request. When receiving information indicating a license issuance request from the client 10, the CPU 21 makes a positive determination in step S30 and proceeds to step S31. When no information indicating the license issuance request is received from the client 10, the CPU 21 makes a negative determination in step S30. The determination process in step S20 is repeated.
[0022]
In step S31, the CPU 21 reads the contract information from the memory 22 and proceeds to step S32. In step S32, the CPU 21 determines whether or not the application can be executed. If the expiration date or the number of issued licenses matches the contract information, the CPU 21 makes an affirmative decision in step S32 and proceeds to step S34, where the expiration date has passed or the number of issued licenses has reached the number of licenses N indicated by the contract information. If it has reached, a negative determination is made in step S32 and the process proceeds to step S33.
[0023]
In step S33, the CPU 21 transmits information indicating that execution is impossible to the client 10 that has transmitted the license issuance request, and the process returns to step S30.
[0024]
In step S34, the CPU 21 transmits information indicating execution permission (license issuance) to the client 10 that has transmitted the license issuance request, and proceeds to step S35. In step S35, the CPU 21 increments the count value I of the number of issued licenses by 1, and proceeds to step S36. In step S36, the CPU 21 determines whether or not the following expression (1) is satisfied.
[Expression 1]
I> N−k (1)
Here, I is a count value of the number of issued licenses, N is the number of licenses (limit value) defined in the license agreement, and k is a predetermined value (for example, 5).
[0025]
When the above equation (1) is established, the CPU 21 makes an affirmative decision in step S36 and proceeds to step S37. When the above equation (1) is not established, the CPU 21 affirms the determination in step S36 and returns to step S30. When the determination in step S36 is affirmative, the remaining number of licenses that can be issued is divided by k (five in the above example). The negative determination in step S36 is a case where the remaining number of licenses that can be issued is k (five in the above example) or more.
[0026]
In step S37, the CPU 21 starts a monitoring process. The monitoring process program is stored in the memory 22. The CPU 21 instructs all the clients 10 that have transmitted the execution permission (issued the license) to check whether or not the application is being used, and proceeds to step S38. In step S <b> 38, the CPU 21 determines whether an application is being used in each client 10. When the CPU 21 receives information indicating that the application is being used from all the license-issued clients 10, the CPU 21 makes a positive determination in step S38 and returns to step S30.
[0027]
On the other hand, when the CPU 21 does not receive information indicating that the application is being used from at least one of the license-issued clients 10, the CPU 21 makes a negative determination in step S38 and proceeds to step S39. In step S <b> 39, the CPU 21 determines whether an application end notification has been received from the client 10. When the CPU 21 receives the information indicating the end of the application, the CPU 21 makes a positive determination in step S39 and proceeds to step S40. When the information indicating the end of the application is not received, the CPU 21 makes a negative determination in step S39 and repeats the determination process.
[0028]
In step S40, the CPU 21 decrements the count value I of the number of issued licenses by 1 in accordance with the number of clients 10 that have transmitted the application end notification, and ends the processing in FIG. For example, I-3 is set when an application end notification is received from three of the clients 10 that have issued licenses, and I-1 is set when an application end notification is received from one client 10.
[0029]
According to the embodiment described above, the following effects can be obtained.
(1) The server 20 not only gives the client 10 permission to execute the application (issues a license) (step S34), but also checks whether the client 10 is using the application (step S38). Therefore, it is possible to grasp the existence of the client 10 that is left unused in a state where it is not used after the application is executed (determination of step S38 is negative).
[0030]
(2) The client 10 checks whether or not the application is used (step S14), and gives a warning if it is not used (step S16). The client 10 further terminates the application (step S19 to S21) when the application is not used even after a predetermined time has passed from the warning (No at step S18), and sends an application termination notification to the server 20 (step S22). . The server 20 subtracts the count value I of the number of issued licenses according to the number of application end notifications (step S40). As a result, the server 20 can manage the number of clients 10 in which applications are actually used without including the abandoned clients 10, so that the number of licenses N by contract can be used effectively.
[0031]
(3) When the client 10 terminates the application, the operating environment at the time of use is stored in the memory 12, so that when the user uses the application again, the work can be continued.
[0032]
(4) The server 20 starts a monitoring process when the remaining number of licenses that can be issued is divided by k (five in the above example) and decreases (step S37), and the client 10 executes the monitoring process on the server 20 side. When activated (Yes in step S13A), the process proceeds to the warning process (step S16) and the stop process (steps S19 to S21) described in (2) above. As a result, the processing of the server 20 and the client 10 can be reduced as compared with the case where each process is always started.
[0033]
In the above description, when determining whether or not an application is being used, the load status of the CPU 11 is calculated, and the determination is made according to the calculation result. Instead, the determination may be made based on the access status to the input device 14 and the output device 15. In this case, the access status to each device is stored in the memory 12 every predetermined time, and it is determined whether or not the application is in use from the date and time of the last access. For example, when one hour has passed since the last access date / time, it is considered that the application is not being used.
[0034]
When the client 10 executes an application to be calculated by the server 20, data is transmitted and received between the client 10 and the server 20 while the client 10 is using the application. In this case, whether or not the application is in use can be determined based on whether or not the number of data to be transmitted and received is equal to or greater than a predetermined value.
[0035]
In the above example, the application execution program is stored in the memory 12 of the client 10, but may be stored in the memory 22 of the server 20.
[0036]
In the above description, the condition that the server 20 activates the monitoring process is the case where the above expression (1) is satisfied. However, the condition may be activated at a predetermined time or every predetermined time.
[0038]
【The invention's effect】
In the license management terminal and the application execution terminal according to the present invention, the monitoring process can be reduced as compared with the case where the monitoring for effectively using the license is always performed.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of a license management system using a license management terminal and an application execution terminal according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of a client.
FIG. 3 is a diagram illustrating a configuration of a server.
FIG. 4 is a flowchart for explaining a flow of client license management processing;
FIG. 5 is a flowchart for explaining the flow of server license management processing;
[Explanation of symbols]
10 (10A-10F) ... client,
11, 21 ... CPU, 12, 22 ... memory,
20 ... Server

Claims (4)

A license information issuing means for issuing license information that permits application activation in response to an issue request transmitted from the application execution terminal;
Counting means for counting the number of the license information issued by the license information issuing means;
Prohibiting means for instructing the license information issuing means to prohibit issuing when the count number by the counting means reaches a limit value;
Monitoring means for starting monitoring whether or not the application is being executed on the application execution terminal that has issued the license information when the difference between the count number and the limit value is less than a predetermined number;
A license management terminal comprising: a subtracting instruction unit that instructs the counting unit to subtract the count number when the monitoring unit obtains information indicating that the application is not being executed in the application execution terminal. A license information requesting means for sending a license information issuance request for starting the application to the license management terminal in response to the application starting operation;
Application starting means for starting the application in response to the license information issued by the license management terminal ;
A determination unit that receives a command transmitted from the license management terminal when a difference between the license limit value and the number of issued licenses is smaller than a predetermined number, and determines whether the activated application is being executed ;
An application ending unit that performs a predetermined warning when the determination unit determines that the non-execution is being performed, and terminates the application when the determination unit determines the non-execution even after the warning;
When the determination means determines that the application is being executed, information indicating that the application is being executed is sent to the license management terminal. When the determination means determines that the application is not being executed after the warning, the application is sent to the license management terminal. An application execution terminal comprising: determination information sending means for sending information indicating non-execution . In the application execution terminal according to claim 2 ,
2. The application execution terminal according to claim 1, wherein the warning is for notifying the termination of the application. In the application execution terminal according to claim 3 ,
A timing unit that starts counting a predetermined time when the determination unit determines that the non-execution is in progress ;
The application ending unit terminates the application when the determination unit determines that the non-execution is in progress after the predetermined time is measured by the timing unit,
The determination information sending means sends information indicating that the application is being executed to the license management terminal when the determination means determines that the execution is in progress after the predetermined time is measured by the time measurement means, and the time measurement means An application execution terminal that sends information indicating that the application is not being executed to the license management terminal when the determination unit determines that the non-execution is being executed after the predetermined time has been counted by the above.

Images