JP2004126642A - Software license management device, software license management program, software license management method and software license management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently assign the number of licenses to a base point for using software without increasing the number of software. <P>SOLUTION: This software license management device is provided with a license assignment number storing means 8 for storing the first number of software licenses being the number of software licenses assigned to each group, a license use number storing means 7 for storing the second number of software licenses being the current number of use of software licenses of each group while updating it based on a notice from a terminal 23 constituting each group and a license management means 6 for temporarily moving the software licenses of the group in which the second number of software is smaller than the first number of software to the group to which the terminal 23 which made a software use request is belonging in response to the use request of software beyond the first number of software licenses permitted to the group to which the terminal is belonging from the terminal. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a software license management device, a software license management program, a software license management method, and a software license management system for providing software use permission to a terminal used by a client (user).
[0002]
[Prior art]
2. Description of the Related Art In recent years, investment in software development has become expensive, and in particular, software applications related to design work such as CAD have a large amount of development investment due to sophistication of design functions. Under these circumstances, the price of software such as CAD is high, and the cost burden is also imposed on the user. On the other hand, the development of networks in recent years, and especially the construction industry, which has been changing to a management focused on speed, have made it necessary to perform design and confirmation work at multiple locations simultaneously and in parallel. And the cost increases.
[0003]
Therefore, as a means for minimizing the required number of software, there is known a technology in which the number of permitted software usage is provided to a user by limiting it to a certain value, and a license which is a usage license is allocated to a user terminal only when used. I have. In addition, a technology is known in which the number of licenses is managed by a certain group (base) so that software is more efficiently allocated. This technique has the advantage that the user only has to purchase a minimum number of software use licenses, the software can be used efficiently by a plurality of groups, and the cost burden on the software is reduced.
[0004]
Conventionally, on a certain host, a license server program performs license management according to license information in a software license list file, and on another host, a client program refers to a server access list file of the same computer at the time of startup, and is described there. A license is acquired from a license server operating on a computer that is operating (for example, see Patent Document 1).
[0005]
When the paid software is introduced, the MAC address is recorded as a system number in the paid data and the paid data is transmitted to the server. The server registers the serial number, the number of licenses, and the system number of the paid software, and starts the paid software on the client. The paid data is read, the system number of the paid data is compared with the MAC address, and if it is confirmed that the software is the paid software installed on the client, the server computer is inquired as to whether or not the license number condition is satisfied. When data that can be started is received from the computer, the requested paid software is started (for example, see Patent Document 2).
[0006]
Further, the mobile client connected to the network receives the license information issued from the license server and stores it in the memory. The mobile client executes software whose use is permitted by the license information stored in the memory even in a mobile environment separated from the network (for example, see Patent Document 3).
[0007]
[Patent Document 1]
JP-A-6-223040 (page 1, FIG. 1)
[Patent Document 2]
Japanese Patent Application Laid-Open No. H11-24918 (page 1, FIG. 1)
[Patent Document 3]
JP 2000-276350 A (page 1, FIG. 1)
[0008]
[Problems to be solved by the invention]
As in the prior arts described above, the technology of allocating a fixed number of licenses to a user and managing the number of licenses for each site where the user uses the software can reduce the cost burden on the user's software. The technique described above has the following problems.
[0009]
First, the number of licenses is assigned to each group of users. However, it is not possible to cope with a case where a request for the number of licenses exceeding the number of licenses is made due to business circumstances or the like.
[0010]
Second, it is not possible to cope with a case where it is necessary to reduce the number of licenses below the required number for each group of users.
[0011]
Third, if the user does not return the license while obtaining it, another user may not be able to use the software.
[0012]
The present invention has been made in view of the above circumstances, and it has been proposed that a user efficiently allocates the number of licenses to the locations where software is used without increasing the number of software licenses, and prevents inefficient use of retaining licenses even when software is not used. It is an object of the present invention to provide a software license management device, a software license management program, a software license management method, and a software license management system which are prevented.
[0013]
[Means for Solving the Problems]
In order to achieve the above object, a software license management device according to the present invention is connected to a plurality of terminals via a communication line, and connects the plurality of terminals to a plurality of terminals each including one or a plurality of terminals. In a software license management device that manages licenses of software that are permitted for each group and executed on terminals in each group when divided into groups,
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is greater than the first software license number. A license management unit that temporarily transfers software licenses of a small number of groups to the group to which the terminal requesting software use belongs.
[0014]
Further, the software license management program of the present invention is executed in a server connected to a plurality of terminals via a communication line, and the server is composed of one or a plurality of terminals each of the plurality of terminals. A software license management program that operates as a software license management device that manages software licenses that are permitted for each group when divided into a plurality of groups and executed on terminals in each group,
Said server,
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A number-of-uses storage unit that stores the number of second software licenses, which is the number of software licenses currently used in each of the groups, while updating the number of software licenses according to a notification from a terminal included in each group;
In response to a request from the terminal for use of software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. The software management device is characterized by operating as a software management device including a license management unit that temporarily transfers a software license of a group to a group to which a terminal that has made a software use request belongs.
[0015]
A software license management method according to the present invention is a software license management method for managing licenses of software executed on terminals in each of a plurality of groups each of which is permitted by one or a plurality of terminals.
The first software license number, which is the number of software licenses allocated to each of the groups, is stored, and the second software license number, which is the number of software licenses currently used in each of the groups, is stored. A first step of storing while being updated by a notification from a terminal configuring each group;
A second step of receiving, from the terminal, a use request for software exceeding the first software license number permitted to the group to which the terminal belongs;
A third step of searching a group different from the group to which the terminal belongs, for a group in which the second software license number is smaller than the first software license number;
A fourth step of temporarily transferring the software licenses of the group having the second number of software licenses smaller than the first number of software licenses detected by the search to the group to which the terminal that made the software use request belongs And characterized in that:
[0016]
Further, the software license management system of the present invention is connected to a plurality of terminals that execute the software in response to a license of the software and the plurality of terminals via a communication line, and each of the plurality of terminals is connected to the plurality of terminals. A software license management system, comprising: a server that manages a license of software that is permitted for each group when one or more terminals are divided into a plurality of groups and that is executed on a terminal in each group;
The terminal obtains a software license, and a software management unit that manages the usage status of the software for which the software license has been obtained,
A software use request unit for making a use request of the software to the server when the software to be used exceeds a first software license number which is a software license allocation number allocated to the own group;
The server comprises:
A license allocation number storage unit that stores the first software license number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number granted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. A license management unit for temporarily transferring the software license of the group to the group to which the terminal requesting the software belongs.
[0017]
In the software license management system according to the present invention, when a software activation request is issued from a terminal of a certain group, and the number of software used in the group exceeds the allotted number, the server is configured as a software of a group having a low software usage rate. The license is transmitted to a group exceeding the above-mentioned number of allocations, so that the users of the group can use the license. As a result, the number of software licenses can be efficiently allocated to each base of a group that uses software.
[0018]
The terminal includes a software usage number storage unit that calculates and stores an actual usage rate based on a software unused time during acquisition of a software license, and a license management unit of the server, the license management unit of the server, If the actual usage rate is equal to or less than the predetermined usage rate in response to the actual usage rate information stored in the software usage count storage unit, the user who used the terminal uses the license for the next license acquisition. Restrictions may be given.
[0019]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 is an overall system configuration diagram showing an embodiment of a software license management system of the present invention.
[0020]
In the figure, a license management server (hereinafter, referred to as a server) 20 and groups 21A, 21B, and 21C using the software are connected via a communication line 12. Each of the groups 21A, 21B, and 21C includes an arbitrary number (single or plural) of client terminals (hereinafter, referred to as terminals) 23 and a plurality of users 24 using the terminals 23. Here, the groups 21A, 21B, and 21C are, for example, departments, branches, and the like of companies, schools, and other arbitrary groups, and are groups in which the users 24 have a relatively deep relationship. Here, an example of three groups 21A, 21B, and 21C is shown, but the number of groups to be managed is arbitrary. Further, in this example, in the group 21A, the user 25 has six users with IDs: 001 to 006, the group 21B has five users with IDs: 007 to 0021, and the group 21C has three users with the IDs: 012 to 04. .
[0021]
FIG. 2 is a block diagram showing a specific configuration of the software license management system, and shows details of the terminal 24 and the server 20.
[0022]
The terminal 24 includes a client license management unit 1 for requesting, holding, or converting a license for each terminal 23, a software management unit 2, for managing the usage status of the software 14 holding the license, and a software for each client. Software usage rate storage means 3 for storing the usage status of the software, communication means 4 for communicating between terminal 23 and server 20, and time measurement means 5 for measuring and managing the time for calculating the software usage rate. ing.
[0023]
The server 20 includes a license management unit 6 that manages licenses to be distributed to the terminal 23, a use number storage unit 7 that stores the number of software licenses used (the second number of licenses) for each of the groups 21A to 21C, and a preset number. Software license allocation number storage means 8 for storing the number of software license allocations (first license number) available for each client group, software license usage number storage unit 7, software license allocation number storage means 8, time measuring means 5 Operating rate calculating means 9 for calculating the software operating rate (utilization rate) of the client group for each time from hour, utilization rate storing means 10 for storing the software usage rate of the client group for each fixed time, and terminal 23 The time that the license for each user is held Licensing utilization rate storage means 11, inter-group loan-relationship storage means 12 for storing software license-lease relations between groups 21A to 21C, and user information storage means for storing user IDs and groups belonging to terminals 23 13 and communication means 14.
[0024]
FIG. 3 shows a table structure for explaining the user information storage means 13 and shows correspondence between groups 21A, 21B, and 21C and user IDs. This table is stored in the user information storage unit 13.
[0025]
FIG. 4 shows a table structure for explaining the license allocation storage means and the inter-group loan-relationship storage means. The first number of licenses in the groups 21A, 21B, and 21C is 3, 2, and 2, respectively. And 21B have a lending relationship, and the group 21C does not have a lending relationship, that is, it is irrelevant to the groups 21A and 21B. This table is stored in the license allocation storage unit 8 and the inter-group balance relationship storage unit 12.
[0026]
FIG. 5 is a table configuration for explaining the number-of-uses storage means. The total number of “license usage status” = Yes in each group is the current usage number (second license number) of the group. If the second number of licenses exceeds the first number of licenses, another group having a loan relationship is selected from FIG. 4 and a license is allocated from that group.
[0027]
FIG. 6 is a flowchart for explaining software activation of the terminal. The following operation is performed by the client license management unit 1 unless otherwise specified.
[0028]
First, in response to a software activation request (step S1), a terminal identification ID (referred to as MCID1) is created by combining an OS, a MAC address, and the like (step S2), and software license (referred to as SL1) information is stored from a storage device of the terminal 23. Is acquired (step S3).
[0029]
Next, it is determined whether or not SL1 exists (step S4). If YES, a terminal identification ID (hereinafter, MCID2) is extracted from SL1 (step S5). Next, it is determined whether or not MCID1 = MCID2 (step S6). If YES, the software is started (step S7). If NO, the software is not started (step S8).
If the determination in step S4 is NO, the current date and time, and an ID (ID1) combining the user ID and MCID1 is created (step S9). Next, the ID1 is transmitted from the client license management unit 1 of the terminal 23 to the server as a software license acquisition request (step S10), and the process proceeds to FIG. 7 described later (step S11).
[0030]
In step S27 of FIG. 7, a software license (referred to as SL2) is returned from the server 20 (step S12). A software license (SL3) is created based on ID1 (created by the same logic as step S26 shown in FIG. 7) (step S13).
[0031]
It is determined whether or not SL2 = SL3 (step S14). If YES, SL2 is stored as a software license in the storage device of the software license management means 6 (step S15), and the software is activated. Is not started (step S8).
[0032]
FIG. 7 is a flowchart for explaining the software license issuance of the server. This operation is performed by the license management unit 6 unless otherwise specified.
[0033]
ID1 is received as a software license acquisition request from the terminal 23 via the communication means 14 (step S21), and it is determined whether or not use restriction is imposed on the software license (see FIGS. 13 and 14) (step S22).
[0034]
Next, the group to which the user belongs is detected (step S23), and the operating rate (utilization rate) when one license of the group to which the user belongs is issued by the following calculation is obtained (step S24).
[0035]
[Current number of use (second number of licenses) +1] / [number of available software licenses allocated to group (first number of licenses)]
Next, it is determined whether or not (operating rate when one license of the belonging group is issued) <= 100 (step S25), and if YES, the software license (SL2) based on ID1 is determined. (The same logic as in FIGS. 6 to 13) (step S26), and transmits SL2 to the terminal 23 as a software license (step S27). If NO in step S25, a software license is assigned from another group (see FIGS. 8 to 12) (step S28).
[0036]
FIGS. 8A and 8B are conceptual diagrams illustrating an example for explaining the operation rate calculation method.
[0037]
FIG. 8A shows the past operation rates of the group 21A for each time period, and shows that the software license assigned to the crew 21B is used only in the black time period Tb. FIG. 8B shows the past operating rates by time zone of the group 21B, and shows that the software license assigned to the group A is used only in the black time zone Ta.
[0038]
FIG. 9C is a conceptual diagram illustrating an example of a method of calculating the operation rate (utilization rate), in which the day of the week is taken horizontally and the time is taken vertically. Is shown.
[0039]
FIG. 10 is a flowchart for calculating the operating rate for each day of the week and hour as shown in FIG.
[0040]
The license management means 6 of the server 20 calculates (once / one day) the estimated operating rates by day of the week and time zone for each group based on past data (stored in the number-of-use storage means 7), The table of FIG. 9 is completed for each group.
[0041]
At start 1, the license management unit 6 determines whether there is a software license acquisition request (step S31), and if YES, writes the number of uses = the number of uses + 1 to the log file LF1 (step S32), and ends. (END1). The log file LF1 is stored in the usage number storage unit 7.
[0042]
At start 2, it is determined whether there is a software license return instruction (step S34). If YES, the number of uses = the number of uses-1 is written into the log file LF1 (step S35), and the process ends (END2).
[0043]
At start 3, it is determined whether or not 0 minutes 0 seconds (passes 24 times a day, minutes or seconds) (step S36), and if YES, 1 based on the information of the log file LF1. The operation rate of the time is calculated, written in the log file LF2 (step S37), and the process ends (END2). The log files LF1 and LF2 are stored in the usage number storage unit 7.
[0044]
At start 4, it is determined whether or not 10: 00: 00: 00 (it passes once a day, any time, any minutes, any seconds) is determined (step S 38), and every hour based on the information of the log file LF 2. Is obtained (step S39), an average value with past data is calculated, and written to the database DB1 (step S40). Thus, the operation rate average value having the contents shown in FIG. 9 is calculated. The database DB1 is stored in the usage rate storage unit 10.
[0045]
FIG. 11 is a flowchart for explaining the software license automatic distribution function. This operation is performed by the license management unit 6 unless otherwise specified.
[0046]
The user is inquired about how long the software will be used (scheduled use time) (step S41). Next, all groups having a loan relationship other than the group to which the user belongs are searched, and narrowing is performed under the following conditions (step S42).
[0047]
(1) Operation rate when one software license is issued <= 100%
This operation rate is calculated from the log file LF1 using the actual operation rate.
[0048]
(2) Occupancy rate when one software license is issued for all scheduled use times <= 100%
This operating rate is calculated based on the expected operating rate from DB1. This is referred to as group list 1.
[0049]
Next, it is determined whether or not a group exists in the group list 1 (step S43). If YES, the “current operation rate after issuing one software license” is determined from the group list 1 and the log file LF1. Is selected (step S44), and a software license (can be used only within the scheduled use time) is issued from the selected group (step S45).
[0050]
If “NO” in the step S46, all the groups having the lending relationship other than the group to which the user belongs are searched (step S46), and narrowing is performed under the following conditions.
[0051]
(1) Operation rate when one software license is issued <= 100%
This operation rate is calculated from the log file LF1 using the actual operation rate.
[0052]
(2) It can be used for the longest time.
[0053]
This operating rate is calculated based on the expected operating rate from DB1.
[0054]
FIG. 12 is a screen image for explaining the software license automatic distribution function.
[0055]
First, on the screen D1, a message "Obtain a license. Please enter the expected end time." Appears. For example, enter a numerical value up to 21:30 on the 21st, and on the next screen D2, There is a display saying "Obtained the license. Please return the license until the following time. 21st 21:30", and on the next screen D3, "No license was available for the desired time." , "There is a license that can be used until the following time. Do you want to acquire it?", And "21:00 on the 21st" is displayed.
[0056]
FIG. 13 is a flowchart illustrating the software management unit and the software usage rate storage unit. For calculating the software usage rate, the unused time after the acquisition of the software license is used (step S50). The unused time is, for example, the time from when the software document (CAD drawing data in CAD) is updated once to when it is updated next time (the unused time can be defined for each software). If the unused time exceeds a predetermined time, the penalty increases by one.
[0057]
When the unused time exceeds a predetermined time at the start
Penalty = penalty + 1, and this is stored in the utilization rate storage means 3 (step S51). Thereafter, the software license is returned (step S52).
[0058]
FIG. 14 is a flowchart for explaining the return of the software license.
[0059]
If the number of penalties exceeds a predetermined number, the software license that can be acquired next time is limited.
[0060]
At the start of the terminal 23, the software ends (step S61), and the return of the software license is transmitted to the server (step S62). At the same time, the number of penalties stored in the utilization rate storage means 10 of FIG. 13 is also transmitted.
[0061]
At the start of the server 20, it is determined whether or not the number of penalties exceeds a predetermined number (step S63). If YES, it is determined that the use restriction is imposed upon the next software license request, and the usage rate is determined. It is stored in the storage means 10 (step S64). In this case, the software license that can be acquired next time is limited.
[0062]
Hereinafter, various embodiments of the present invention will be described.
[0063]
(Supplementary Note 1) Each terminal is connected to a plurality of terminals via a communication line, and each of the plurality of terminals is permitted for each group when the plurality of terminals are divided into a plurality of groups each including one or a plurality of terminals. In a software license management device that manages licenses of software executed on terminals in a group,
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is greater than the first software license number. A software license management device comprising: a license management unit for temporarily transferring software licenses of a small number of groups to a group to which a terminal requesting software use belongs.
[0064]
(Supplementary Note 2) When executed in a server connected to a plurality of terminals via a communication line, and the server is divided into a plurality of groups each including one or a plurality of terminals. A software license management program that operates as a software license management device that manages software licenses that are permitted for each group and that are executed on terminals in each group.
Said server,
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A number-of-uses storage unit that stores the number of second software licenses, which is the number of software licenses currently used in each of the groups, while updating the number of software licenses according to a notification from a terminal included in each group;
In response to a request from the terminal for use of software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. A software license management program that operates as a software management device including a license management unit that temporarily transfers a software license of a group to a group to which a terminal requesting software use belongs.
[0065]
(Supplementary Note 3) In a software license management method for managing a license of software that is permitted to each of a plurality of groups each including one or a plurality of terminals and executed on the terminals in each group,
The first software license number, which is the number of software licenses allocated to each of the groups, is stored, and the second software license number, which is the number of software licenses currently used in each of the groups, is stored. A first step of storing while being updated by a notification from a terminal configuring each group;
A second step of receiving, from the terminal, a use request for software exceeding the first software license number permitted to the group to which the terminal belongs;
A third step of searching a group different from the group to which the terminal belongs, for a group in which the second software license number is smaller than the first software license number;
A fourth step of temporarily transferring the software licenses of the group having the second number of software licenses smaller than the first number of software licenses detected by the search to the group to which the terminal that made the software use request belongs And a software license management method.
[0066]
(Supplementary Note 4) A plurality of terminals that receive the software license and execute the software, and are connected to the plurality of terminals via a communication line, and each of the plurality of terminals is one or more terminals. A software license management system comprising: a server that manages software licenses that are permitted for each group and executed on terminals in each group when divided into a plurality of groups.
The terminal obtains a software license, and a software management unit that manages the usage status of the software for which the software license has been obtained,
A software use request unit for making a use request of the software to the server when the software to be used exceeds a first software license number which is a software license allocation number allocated to the own group;
The server comprises:
A license allocation number storage unit that stores the first software license number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number granted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. A software license management system comprising: a license management unit for temporarily transferring a software license of a group to a group to which a terminal that has made a software use request belongs.
[0067]
(Supplementary Note 5) The terminal includes a software usage number storage unit that calculates and stores an actual usage rate based on a software unused time while acquiring a software license,
The license management unit of the server receives the information on the actual usage rate stored in the software usage count storage unit from the terminal and uses the terminal when the actual usage rate is equal to or less than a predetermined usage rate. 4. The software license management system according to claim 4, wherein the user who gives the license is restricted from using the license when the license is acquired next time.
[0068]
(Supplementary Note 6) The second step is a step of receiving information on a use time period of the software by the terminal at the same time as receiving a use request of the software from the terminal, and further based on the information received in the second step. 5. The software license management method according to claim 3, further comprising: calculating a software usage rate of a group to which the terminal belongs.
[0069]
(Supplementary Note 7) A sixth step of receiving the return of the software license from the terminal of the group and simultaneously receiving the usage rate of the software in the group to which the terminal belongs, and wherein the received usage rate is equal to or less than a predetermined usage rate. 7. The software license management method according to claim 3, further comprising a seventh step of writing down the transmission of the software license with a limited use time when the next software license is granted.
[0070]
(Supplementary Note 8) The license use number storage unit further stores the expected use number of software licenses for each group for each day of the week and for each time zone, and the license management unit stores the actual use number of the group for each group. 4. The software license management system according to claim 4, wherein when the value is less than a predetermined value, a license use restriction is given to the user.
[0071]
【The invention's effect】
As described above, according to the present invention, when the number of software used in a certain group exceeds the assigned number, the software license of the group having the lower number of software used is transmitted to the group exceeding the assigned number, and the group is transmitted. Software licenses can be efficiently allocated to each software usage location so that software users can use the software licenses efficiently, and software users can efficiently allocate licenses to software usage locations without increasing the number of software licenses It is possible to prevent inefficient use of licenses and to retain licenses even when software is not used. Therefore, cost can be reduced by introducing only necessary software.
[Brief description of the drawings]
FIG. 1 is an overall system configuration diagram showing an embodiment of a software license management system of the present invention.
FIG. 2 is a block diagram showing a specific configuration of a software license management system.
FIG. 3 is a table configuration illustrating a user information storage unit.
FIG. 4 is a table configuration for explaining a license allocation storage unit and an inter-group loan relationship storage unit;
FIG. 5 is a table configuration illustrating a usage number storage unit.
FIG. 6 is a flowchart for explaining software activation of a terminal.
FIG. 7 is a flowchart for explaining software license issuance of a server.
FIG. 8 is a conceptual diagram illustrating an example for explaining an operation rate calculation unit.
FIG. 9 is a conceptual diagram showing an example for explaining an operation rate calculating unit.
FIG. 10 is a flowchart for calculating an operation rate for each day of the week and hour.
FIG. 11 is a flowchart illustrating a software license automatic distribution function.
FIG. 12 is a screen image for explaining a software license automatic distribution function.
FIG. 13 is a flowchart illustrating a software management unit and a software usage rate storage unit.
FIG. 14 is a flowchart illustrating the return of a software license.
[Explanation of symbols]
1 Client license management means
2 Software management means
3 Software usage rate storage means
4 Communication means
5 Time measurement means
6 License management means
7 License usage number storage means
8 License allocation number storage means
9 Usage rate calculation means
10 Usage rate storage means
11 License usage rate storage means
12 Inter-group loan relationship storage means
13 User information storage means
20 servers
21A, 21B, 21C Group
23 terminals
24 users

Claims (5)

Terminals connected to a plurality of terminals via a communication line and allowed in each group when each of the plurality of terminals is divided into a plurality of groups each composed of one or a plurality of terminals. In the software license management device that manages the license of the software executed in
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is greater than the first software license number. A software license management device comprising: a license management unit for temporarily transferring software licenses of a small number of groups to a group to which a terminal requesting software use belongs. The program is executed in a server connected to a plurality of terminals via a communication line, and the server is divided into a plurality of groups each including one or a plurality of terminals. A software license management program that operates as a software license management device that manages licenses of software executed on terminals in each group and permitted by
Said server,
A license allocation number storage unit that stores a first software license number that is a software license allocation number allocated to each of the groups;
A number-of-uses storage unit that stores the number of second software licenses, which is the number of software licenses currently used in each of the groups, while updating the number of software licenses according to a notification from a terminal included in each group;
In response to a request from the terminal for use of software that exceeds the first software license number permitted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. A software license management program that operates as a software management device including a license management unit that temporarily transfers a software license of a group to a group to which a terminal requesting software use belongs. A software license management method for managing licenses of software executed on terminals in each group, each of which is permitted to a plurality of groups each including one or a plurality of terminals,
The first software license number, which is the number of software licenses allocated to each of the groups, is stored, and the second software license number, which is the number of software licenses currently used in each of the groups, is stored. A first step of storing while being updated by a notification from a terminal configuring each group;
A second step of receiving, from the terminal, a use request for software exceeding the first software license number permitted to the group to which the terminal belongs;
A third step of searching a group different from the group to which the terminal belongs, for a group in which the second software license number is smaller than the first software license number;
A fourth step of temporarily transferring the software licenses of the group having the second number of software licenses smaller than the first number of software licenses detected by the search to the group to which the terminal that made the software use request belongs And a software license management method. A plurality of terminals that receive the software license and execute the software; and a plurality of terminals connected to the plurality of terminals via a communication line, each of the plurality of terminals being one or more terminals. In a software license management system comprising a server that manages a license of software that is permitted for each group and executed on a terminal in each group when divided into groups,
The terminal obtains a software license, and a software management unit that manages the usage status of the software for which the software license has been obtained,
A software use request unit for making a use request of the software to the server when the software to be used exceeds a first software license number which is a software license allocation number allocated to the own group;
The server comprises:
A license allocation number storage unit that stores the first software license number allocated to each of the groups;
A license use number storage unit that stores a second software license number, which is the number of software licenses currently used in each group, while updating the second software license number according to a notification from a terminal configuring each group;
In response to a request from the terminal to use software that exceeds the first software license number granted to the group to which the terminal belongs, the second software license number is smaller than the first software license number. A software license management system comprising: a license management unit for temporarily transferring a software license of a group to a group to which a terminal that has made a software use request belongs. The terminal includes a software usage number storage unit that calculates and saves an actual usage rate based on software unused time while acquiring a software license,
The license management unit of the server receives the information on the actual usage rate stored in the software usage count storage unit from the terminal and uses the terminal when the actual usage rate is equal to or less than a predetermined usage rate. 5. The software license management system according to claim 4, wherein the user who gives the license is restricted from using the license when the license is acquired next time.

Images