JP4061163B2 - Software license management apparatus, software license management program, software license management method, and software license management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a software license management apparatus, a software license management program, a software license management method, and a software license management system that provide a use permission of software to a terminal used by a client (user).
[0002]
[Prior art]
In recent years, investment in software development has become high. Especially, software applications related to design work such as CAD have become large due to sophistication of design functions. Under these circumstances, the price of software such as CAD has become high, and it has become a cost burden for users. On the other hand, due to the recent development of networks and the background of the change to management that emphasizes speed especially for the construction industry, it is essential to perform design and confirmation work in parallel at multiple locations, and the required number of software As a result, the cost increases.
[0003]
Therefore, as a means of minimizing the required number of software, a technology is known in which the number of permitted use of software is limited to a certain value to the user, and a license that is permitted to be used is assigned to the user's terminal only when it is used. Yes. In addition, there is known a technique for assigning software more efficiently by managing the number of licenses by a certain group (base). This technique has the advantage that the user only needs to purchase a minimum number of software use permits, can efficiently use the software in a plurality of groups, and the cost burden on the software is reduced.
[0004]
Conventionally, the license server program on one host performs license management according to the license information in the software license list file, and the client program on the other host refers to the server access list file of the same computer at startup and is described there. A license is acquired from a license server operating on a computer (for example, see Patent Document 1).
[0005]
Also, when installing paid software, record the MAC address as paid system data in paid data, send paid data to the server, register the paid software serial number, number of licenses, and system number, and start the paid software on the client. When the data is read, the system number and the MAC address of the paid data are compared, and if it is confirmed that the software is a paid software installed on the client, the server computer is inquired whether the license number condition is satisfied, and the server When data that can be activated from a computer is received, the requested paid software is activated (see, for example, Patent Document 2).
[0006]
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 permitted to be used according to the license information stored in the memory even in a mobile environment disconnected from the network (see, for example, Patent Document 3).
[0007]
[Patent Document 1]
JP-A-6-223040 (first page, FIG. 1)
[Patent Document 2]
Japanese Patent Laid-Open No. 11-24918 (first page, FIG. 1)
[Patent Document 3]
Japanese Unexamined Patent Publication No. 2000-276350 (first page, FIG. 1)
[0008]
[Problems to be solved by the invention]
As with each of the above prior arts, a technology that assigns a certain number of licenses to users and manages the number of licenses for each site where the user uses the software can reduce the cost burden on the user's software. This technology had the following problems.
[0009]
First, the number of licenses is assigned to each group of users, but it cannot be handled when there is a request for the number of uses exceeding the number of licenses due to business circumstances.
[0010]
Second, it is impossible to cope with the case where the number of licenses needs to be kept below the required number for each user group.
[0011]
Thirdly, if the user does not return the license after obtaining it, other users may not be able to use the software.
[0012]
In view of the above-described circumstances, the present invention effectively allocates the number of licenses to the use base of the software without increasing the number of software licenses, and uses the inefficient use of retaining the licenses even though the software is not used. An object of the present invention is to provide a software license management apparatus, a software license management program, a software license management method, and a software license management system.
[0013]
[Means for Solving the Problems]
In order to achieve the above object, a software license management apparatus of the present invention is connected to a plurality of terminals via a communication line, and each of the plurality of terminals is composed of a plurality of terminals each consisting of one or a plurality of terminals. In a software license management device that manages licenses of software that is allowed for each group when it is divided into groups and executed on terminals in each group,
A license allocation number storage unit for storing a first software license number that is a software license allocation number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
In response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal, the second software license number is greater than the first software license number. And a license management unit that temporarily transfers a software license of a small group to a group to which a terminal that has requested software use belongs.
[0014]
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. In a software license management program that operates as a software license management apparatus that manages licenses of software that are allowed for each group and executed on terminals in each group when divided into a plurality of groups,
The server,
A license allocation number storage unit for storing a first software license number that is a software license allocation number allocated to each of the groups;
A usage number storage unit for storing a second software license number, which is the number of software licenses currently used in each group, while being updated by notification from a terminal constituting each group;
The second software license number is smaller than the first software license number in response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal. A software management apparatus is provided that includes a license management unit that temporarily transfers a software license of a group to a group to which a terminal that has requested to use the software belongs.
[0015]
The software license management method of the present invention is a software license management method for managing software licenses that are permitted to each of a plurality of groups each consisting of one or a plurality of terminals and executed on terminals in each group.
A first software license number that is the number of software licenses assigned to each group is stored, and a second software license number that is a software license currently used in each group is stored in the group. A first step that is stored while being updated by a notification from a terminal constituting each group;
A second step of accepting a request to use software exceeding the number of the first software licenses permitted to the group to which the terminal belongs;
A third step of searching for a group in which the second software license number is smaller than the first software license number from among groups different from the group to which the terminal belongs;
A fourth step of temporarily transferring the software licenses of the group having a smaller number of second software licenses than the number of first software licenses detected by the search to the group to which the terminal that made the software use request belongs; It is characterized by including.
[0016]
The software license management system of the present invention is connected to a plurality of terminals that receive software licenses and execute 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. In a software license management system comprising a server that manages licenses of software that are permitted for each group when divided into a plurality of groups from one or a plurality of terminals and that are executed on the terminals in each group,
The terminal acquires a software license, and a software management unit that manages the usage status of the software for which the software license has been acquired;
A software usage requesting unit that requests the server to use the software when the software to be used exceeds a first software license number that is the number of software licenses assigned to the group;
The server
A license allocation number storage unit for storing the first software license number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
In response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal, the second software license number is smaller than the first software license number. And a license management unit that temporarily transfers the software license of the group to the group to which the terminal that requested the software use belongs.
[0017]
In the software license management system of the present invention, when a software activation request is made from a terminal of a certain group, if the number of software uses in the group exceeds the allocated number, the server uses the software of the group having a low software utilization rate. A license is transmitted to a group exceeding the above-mentioned allocation number, and a user of the group is made ready to use. As a result, the number of software licenses can be efficiently allocated to each base of a group that uses the software.
[0018]
The terminal includes a software usage number storage unit that calculates and stores an actual usage rate based on software unused time while acquiring a software license, and the license management unit of the server receives the software from the terminal. If the actual usage rate is less than or equal to the predetermined usage rate after receiving information on the actual usage rate stored in the software usage number storage unit, the user who used the terminal will use it for the license at the next license acquisition. Restrictions can be given.
[0019]
DETAILED DESCRIPTION OF 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 that use the software are connected via a communication line 12. Each group 21 </ b> A, 21 </ b> B, and 21 </ b> C 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, etc. of companies, schools, and other arbitrary groups, and the users 24 are in 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, there are six users 25 having IDs: 001 to 006, in the group 21B, five people having IDs: 007 to 0021, and in the group 21C, three users having 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 that performs a license acquisition request, retention, or conversion for each terminal 23, a software management unit 2 that manages the usage status of the software 14 that holds the license, and software for each client. Software usage rate storage means 3 for storing the usage status of the wearer, communication means 4 for communicating between the terminal 23 and the server 20, and time measuring 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 distributed to the terminal 23, a usage number storage unit 7 that stores the number of software licenses used (second license number) for each of the groups 21A to 21C, and a preset number. Software license allocation number storage means 8 for storing the available software license allocation number (first license number) for each client group, software license usage number storage section 7, software license allocation number storage means 8, and time measurement means 5 Operating rate calculation means 9 for calculating the software operating rate (utilization rate) of the client group for each hour from the above, usage rate storage means 10 for storing the software usage rate for the client group for a certain period of time, and the terminal 23 Remembers the time for which a license was held for each user License usage rate storage means 11, inter-group loan relationship storage means 12 for storing the software license loan relationship between the groups 21A to 21C, user information storage means for storing the ID and affiliation group of the user using the terminal 23 13 and communication means 14.
[0024]
FIG. 3 is a table configuration for explaining the user information storage means 13, and shows the correspondence between the groups 21A, 21B, and 21C and the user ID. This table is stored in the user information storage means 13.
[0025]
FIG. 4 is a table configuration for explaining the license allocation storage means and the inter-group lending relationship storage means. In the groups 21A, 21B, and 21C, the first license numbers are 3, 2, 2, and the group 21A. 21B has a lending relationship, and group 21C has no lending relationship, that is, it is unrelated to groups 21A and 21B. This table is stored in the license allocation storage unit 8 and the intergroup loan relationship storage means 12.
[0026]
FIG. 5 is a table configuration for explaining the usage number 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 lending relationship is selected from FIG. 4 and a license is assigned from that group.
[0027]
FIG. 6 is a flowchart for explaining the software activation of the terminal. The following operations are performed by the client license management means 1 unless otherwise specified.
[0028]
First, in response to a software activation request (step S1), a terminal identification ID (MCID1) is created by combining the OS, MAC address, etc. (step S2), and software license (SL1) information is stored from the 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 (referred to as MCID2) is extracted from SL1 (step S5). Next, it is determined whether or not MCID1 = MCID2 (step S6). If YES, the software is activated (step S7). If NO, the software is not activated (step S8).
If the determination in step S4 is no, an ID (ID1) that combines the current date and time, 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 in 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 with 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). Is not activated (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 means 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 to restrict use of the software license (see FIGS. 13 to 14) (step S22).
[0034]
Next, the group to which the user belongs is detected (step S23), and the operation rate (utilization rate) when one license of the user's group is issued is obtained by the following calculation (step S24).
[0035]
[Current usage number (second license number) +1] / [Number of usable software licenses assigned to the group (first license number)]
Next, it is determined whether or not (operation rate when one license of the group to which the group belongs is issued) <= 100 (step S25). If YES, a software license (SL2) based on ID1 is determined. Is created (with the same logic as in FIGS. 6 to 13) (step S26), and SL2 is transmitted as a software license to the terminal 23 (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 operating rate of the group 21A by time zone, and shows that the software license assigned to the crew 21B is used only in the black time zone Tb. FIG. 8B shows the past operating rate of the group 21B by time period, and shows that the software license assigned to the group A is used only in the black time period Ta.
[0038]
FIG. 9C is a conceptual diagram showing an example for explaining the operation rate (utilization rate) calculation method, and shows an example of the operation rate for each time on each day of the week, with the day of the week horizontally and the time vertically. Is shown.
[0039]
FIG. 10 is a flowchart for calculating the operating rate for each day of the week and time as shown in FIG.
[0040]
The license management means 6 of the server 20 calculates and calculates (once / day) the expected operating rate by day of the week and time period for each group based on past data (stored in the usage number storage means 7). The table shown in FIG. 9 is completed for each group.
[0041]
At start 1, the license management means 6 determines whether or not there is a software license acquisition request (step S31). If YES, the number of uses = the number of uses + 1 is written in the log file LF1 (step S32) and the process ends. (END1). The log file LF1 is stored in the usage number storage unit 7.
[0042]
It is determined whether or not there is a software license return instruction at start 2 (step S34). If YES, the number of uses = the number of uses-1 is written in the log file LF1 (step S35), and the process ends (END2).
[0043]
At start 3, it is determined whether or not 0 minute 0 second (24 times a day, how many minutes can be used) is determined (step S36). If YES, 1 is determined based on the information in the log file LF1. The operating rate of time is calculated, written in the log file LF2 (step S37), and the process is terminated (END2). The log files LF1 and LF2 are stored in the usage number storage unit 7.
[0044]
It is determined at start 4 whether or not it has become 10:00:00 (passed once a day, whatever hour, minutes and seconds) (step S38), and every hour based on the information in the log file LF2 Is obtained (step S39), an average value with the past data is calculated, and written in the database DB1 (step S40). In this way, the average operating rate value as shown in FIG. 9 is calculated. The database DB1 is stored in the utilization rate storage means 10.
[0045]
FIG. 11 is a flowchart for explaining an automatic software license distribution function. This operation is performed by the license management means 6 unless otherwise specified.
[0046]
The user is inquired how long the software is 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 narrowed down under the following conditions (step S42).
[0047]
(1) Operation rate when one software license is issued <= 100%
This operating rate is calculated from the actual operating rate from the log file LF1.
[0048]
(2) Occupancy rate <= 100% when one software license is issued for all scheduled use times
In addition, this operation rate is calculated by the expected operation rate from DB1. This is group list 1.
[0049]
Next, it is determined whether or not there is a group in the group list 1 (step S43). If YES, from the group list 1 and the log file LF1, “current operation rate after issuing one software license” Is selected (step S44), and a software license (usable only within the scheduled use time) is issued from the selected group (step S45).
[0050]
If NO in step S46, all groups having a loan relationship other than the group to which the user belongs are searched (step S46), and narrowing down is performed under the following conditions.
[0051]
(1) Operation rate when one software license is issued <= 100%
This operating rate is calculated from the actual operating rate from the log file LF1.
[0052]
(2) Can be used for the longest time.
[0053]
In addition, this operation rate is calculated by the expected operation rate from DB1.
[0054]
FIG. 12 is a screen image for explaining the software license automatic distribution function.
[0055]
First, on the screen D1, the message “Obtain a license. Please enter the scheduled end time” appears. For example, enter a value up to 21:30 on the 21st, and then on the next screen D2, “License has been acquired. Please return the license until the following time. 21:30 on 21st” is displayed, and on the next screen D3, “A license that can be used for the desired time was not found.” , “There is a license that can be used until the following time. Do you want to acquire it?”, “21st 20:00” is an example.
[0056]
FIG. 13 is a flowchart for explaining the software management unit and the software usage rate storage unit. For the calculation of the software usage rate, the unused time after obtaining the software license is used (step S50). The unused time is, for example, a time from when a software document (drawing data in CAD) is updated once to the next update (the unused time can be defined for each software). When 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]
When 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 is terminated (step S61), and a software license is returned to the server (step S62). At the same time, the penalty number stored in the utilization rate storage means 10 in 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 given at the next software license request, and the usage rate is determined. It preserve | saves at the memory | 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]
(Appendix 1) Connected to a plurality of terminals via a communication line, each of which is permitted for each group when the plurality of terminals are divided into a plurality of groups each consisting of 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 for storing a first software license number that is a software license allocation number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
In response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal, the second software license number is greater than the first software license number. A software license management apparatus comprising: a license management unit that temporarily transfers a software license of a small group to a group to which a terminal that has requested software use belongs.
[0064]
(Supplementary note 2) When executed in a server connected to a plurality of terminals via a communication line, and when the server is divided into a plurality of groups each consisting of one or a plurality of terminals In a software license management program that operates as a software license management apparatus that manages licenses of software that is permitted for each group and executed on terminals in each group,
The server,
A license allocation number storage unit for storing a first software license number that is a software license allocation number allocated to each of the groups;
A usage number storage unit for storing a second software license number, which is the number of software licenses currently used in each group, while being updated by notification from a terminal constituting each group;
The second software license number is smaller than the first software license number in response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal. A software license management program that operates as a software management apparatus including a license management unit that temporarily transfers a group software license to a group to which a terminal that has requested software use belongs.
[0065]
(Supplementary Note 3) In a software license management method for managing software licenses that are permitted to each of a plurality of groups each consisting of one or a plurality of terminals and executed on the terminals in each group,
A first software license number that is the number of software licenses assigned to each group is stored, and a second software license number that is a software license currently used in each group is stored in the group. A first step that is stored while being updated by a notification from a terminal constituting each group;
A second step of accepting a request to use software exceeding the number of the first software licenses permitted to the group to which the terminal belongs;
A third step of searching for a group in which the second software license number is smaller than the first software license number from among groups different from the group to which the terminal belongs;
A fourth step of temporarily transferring the software licenses of the group having a smaller number of second software licenses than the number of first 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 software licenses and execute the software, and are connected to the plurality of terminals via a communication line, each of which is one or a plurality of terminals In a software license management system comprising a server that manages software licenses that are allowed for each group and executed on terminals in each group when divided into a plurality of groups,
The terminal acquires a software license, and a software management unit that manages the usage status of the software for which the software license has been acquired;
A software usage requesting unit that requests the server to use the software when the software to be used exceeds a first software license number that is the number of software licenses assigned to the group;
The server
A license allocation number storage unit for storing the first software license number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
In response to a usage request for software exceeding the first software license number permitted to the group to which the terminal belongs from the terminal, the second software license number is smaller than the first software license number. A software license management system comprising: a license management unit that temporarily transfers a group software license to a group to which a terminal that has requested software use belongs.
[0067]
(Supplementary Note 5) The terminal includes a software usage number storage unit that calculates and stores an actual usage rate based on software unused time while acquiring a software license,
The license management unit of the server receives information on an actual usage rate stored in the software usage number storage unit from the terminal, and uses the terminal when the actual usage rate is equal to or lower than a predetermined usage rate. The software license management system according to appendix 4, wherein the user who has been given gives a use restriction to the license when the license is acquired next time.
[0068]
(Supplementary Note 6) The second step is a step of receiving information on a usage time period of the software by the terminal at the same time as receiving a software use request from the terminal, and further, based on the information received in the second step. The software license management method according to supplementary note 3, comprising a fifth step of calculating a software usage rate of the group to which the terminal belongs.
[0069]
(Supplementary note 7) Sixth step of receiving the fact that the software license from the terminal of the group is returned and simultaneously receiving the usage rate of the software in the group to which the terminal belongs, and the received usage rate is less than or equal to the predetermined usage rate In this case, the software license management method according to appendix 3, further comprising a seventh step of noting that a software license whose use time is limited is transmitted when the next software license is granted.
[0070]
(Supplementary Note 8) The license usage number storage unit further stores the expected usage number of the software license for each group by day of the week and time period, and the license management unit stores the actual usage number of the group. Item 4. The software license management system according to appendix 4, wherein a license usage restriction is given to a user when the value is lower than a predetermined value.
[0071]
【The invention's effect】
As described above, according to the present invention, when the number of software uses in a certain group exceeds the allocated number, the software license of the group having a low software used number is transmitted to the group exceeding the allocated number. The number of software licenses can be allocated efficiently to each site where software is used, so that software users can efficiently use the number of licenses at sites where software is used without increasing the number of software licenses. Can be prevented, and inefficient use of retaining licenses even when the software is not used can be prevented, and therefore the cost can be reduced by introducing only the 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 the software license management system.
FIG. 3 is a table configuration for explaining a user information storage unit;
FIG. 4 is a table configuration for explaining a license allocation storage unit and an inter-group lending relationship storage unit.
FIG. 5 is a table configuration for explaining 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 illustrating an example for similarly explaining an operation rate calculation unit.
FIG. 10 is a flowchart for calculating an operation rate for each day of the week and time.
FIG. 11 is a flowchart for explaining an automatic software license distribution function;
FIG. 12 is a screen image for explaining a software license automatic distribution function;
FIG. 13 is a flowchart for explaining a software management unit and a software usage rate storage unit;
FIG. 14 is a flowchart for explaining 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 Utilization rate storage means
11 License usage rate storage means
12 Lending relationship storage means between groups
13 User information storage means
20 servers
21A, 21B, 21C group
23 terminal
24 users

Claims (4)

Connected to a plurality of terminals via a communication line and permitted to each group when the plurality of terminals are divided into a plurality of groups each consisting 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 for storing a first software license number that is a software license allocation number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
Said from the terminal, Keru receive software use request of said terminal exceeds the first number of software licenses granted to a group belonging use request receiving unit,
A license management unit for temporarily transferring a software license of a group in which the number of second software licenses is smaller than the number of first software licenses to a group to which a terminal that has made a software use request belongs ;
A usage rate calculation unit that acquires a usage rate of the software based on an unused time of the transferred license in the group to which the license is temporarily transferred by the license management unit;
A license transfer control unit that controls whether or not to execute a license transfer process in the license management unit to the group in accordance with the software usage rate acquired by the usage rate calculation unit;
A software license management apparatus comprising: Each group 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 consisting of one or a plurality of terminals. In a software license management program that operates as a software license management apparatus that manages licenses of software that are allowed to be executed on terminals in each group,
A license allocation number storage unit for storing a first software license number that is a software license allocation number allocated to each of the groups;
A usage number storage unit for storing a second software license number, which is the number of software licenses currently used in each group, while being updated by notification from a terminal constituting each group;
A usage request receiving unit that Ru receiving a request to use the software to which the terminal is greater than the first number of software licenses granted to a group belonging from said terminal,
A license management unit for temporarily transferring a software license of a group in which the number of second software licenses is smaller than the number of first software licenses to a group to which a terminal that has made a software use request belongs ;
A usage rate calculation unit that acquires a usage rate of the software based on an unused time of the transferred license in the group to which the license is temporarily transferred by the license management unit;
A license transfer control unit that controls whether or not to execute a license transfer process in the license management unit to the group in accordance with the software usage rate acquired by the usage rate calculation unit;
A software license management program which is operated as a software management apparatus comprising: In a software license management method for managing software licenses that are permitted to each of a plurality of groups each consisting of one or a plurality of terminals and executed on terminals in each group,
A first software license number that is the number of software licenses assigned to each group is stored, and a second software license number that is a software license currently used in each group is stored in the group. A first step that is stored while being updated by a notification from a terminal constituting each group;
A second step of accepting a request to use software exceeding the number of the first software licenses permitted to the group to which the terminal belongs;
A third step of searching for a group in which the second software license number is smaller than the first software license number from among groups different from the group to which the terminal belongs;
A fourth step of temporarily transferring the software licenses of the group having a smaller number of second software licenses than the number of first software licenses detected by the search to the group to which the terminal that made the software use request belongs; and,
A fifth step of acquiring a usage rate of the software based on a non-use time of the transferred license in the group to which the license is temporarily transferred in the fourth step;
A sixth step of controlling whether or not to execute the license transfer process in the fourth step to the group according to the software usage rate acquired in the fifth step;
A software license management method comprising: A plurality of terminals that receive software licenses and execute the software, and are connected to the plurality of terminals via a communication line, and each of the plurality of terminals is divided into a plurality of groups from one or a plurality of terminals. In a software license management system consisting of 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
The terminal
A software management unit that acquires a software license and manages the usage status of the software for which the software license has been acquired;
A software usage requesting unit that requests the server to use the software when the software to be used exceeds a first software license number that is the number of software licenses assigned to the group;
The server
A license allocation number storage unit for storing the first software license number allocated to each of the groups;
A license usage number storage unit that stores a second software license number that is the number of software licenses currently used in each group while being updated by notification from a terminal that constitutes each group;
Said from the terminal, use request acceptance unit which the terminal Ru receiving a software request to use more than the first number of software licenses granted to a group belonging,
A license management unit for temporarily transferring a software license of a group having a smaller number of second software licenses than the first software license number to a group to which a terminal that has made a software use request belongs ;
A usage rate calculation unit that acquires a usage rate of the software based on an unused time of the transferred license in the group to which the license is temporarily transferred by the license management unit;
A license transfer control unit that controls whether or not to execute a license transfer process in the license management unit to the group in accordance with the software usage rate acquired by the usage rate calculation unit;
A software license management system comprising:

Images