JP2007094576A - Software license management system, software license management method, and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform efficient management of a license of software comprising a plurality of functions. <P>SOLUTION: A server 2 is provided with; a table which stores a weighting factor which indicates a weight of each function prepared in the software; a license information management section 201 which performs processing for management on a usable volume which indicates a usable volume of the software from now on; a use status information receiving section 203 which acquires use status information which indicates the use status of the software in a terminal device 3; and a consumption volume computing section 204 which computes consumption volume which is a consumable volume which can be consumed when the terminal device 3 uses the software based on a function used in the terminal device 3, the use volume of the function used, and a weighting factor of the function stored in the table shown in the use status information. The license information processing section 201 subtracts the consumption volume computed by the consumption volume computing section 204 from the present usable volume. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a system and method for managing software licenses.

  Generally, those who wish to use commercially available software (so-called packaged software) or paid software (so-called shareware) distributed via the Internet, etc., grant a license from the software supplier I have to get it.

  In most cases, a license is required for each terminal device that installs the software. Therefore, in an office such as a government office or a company where a plurality of terminal devices are installed, a license corresponding to the number of terminals is required. However, some of these terminal devices frequently use the software, while others rarely use or not use them at all. Therefore, if the software is installed in these terminal devices without restriction, the license fee may be unnecessarily increased.

  In order to save license fees, some offices install the software only on some terminal devices. However, this is inconvenient because the number of terminal devices that can use the software is limited when an urgent business occurs and the need for the software increases. Also, license management tends to be complicated.

Therefore, a method as described in Patent Document 1 has been proposed. According to such a method, a license key is given to each terminal device, and charging is performed according to the usage time or the usage count.
JP 2002-351564 A Japanese Patent No. 3506176 Japanese Patent Laid-Open No. 11-219292 JP 2002-49435 A JP 2000-276350 A

  By the way, in recent years, a plurality of types of software with different functions are often sold from the same manufacturer even though they are in the same genre. For example, from the same manufacturer, software with subtitles such as “minimum version”, “standard version”, or “full function version” is sold as business-oriented software depending on the functions equipped. This makes it possible to supply software that meets the needs of the user.

  However, in an office where a plurality of terminal devices are installed, it is difficult to select which version of software to install. If the full-function version is installed on all terminal devices, it is easy in terms of management, but there is a risk that useless license fees will be paid. Choosing which version to install on the terminal device according to the user's work contents is an appropriate method from the viewpoint of the license fee, but it is a burden on the administrator. In addition, the version to be installed on the terminal device must be changed according to changes in the environment, and license management tends to be complicated.

  However, the method described in Patent Document 1 cannot solve such problems. In addition, methods as described in Patent Documents 2 to 5 have been proposed, but it is still impossible to solve such problems.

  The present invention has been made in view of such problems, and an object thereof is to enable efficient management of licenses for software having a plurality of functions.

  A software license management system according to the present invention is a software license management system for managing licenses of software used by a plurality of terminal devices, and stores a weighting coefficient indicating a weight for each function provided in the software. , Weight coefficient storage means, usable amount management means for performing processing for management relating to the usable amount, which is the amount that the software can be used in the future, and usage status information indicating the usage status of the software in the terminal device Usage status information acquisition means for acquiring the function used in the terminal device, the usage amount used for the function, and the coefficient storage means indicated in the usage status information acquired by the usage status information acquisition means Based on the weighting factor of the function stored in Consumption amount calculating means for calculating a consumption amount that is the amount of the usable amount consumed by using the software, and the usable amount management means is calculated by the consumption amount calculating means. Further, a process of reducing the consumption amount from the usable amount is performed.

  Preferably, the usage amount of the function used in the terminal device is determined by a time when the function is used.

  The usable amount can be managed, for example, by a numerical value indicating how many hours a function having a weighting factor “1” can be used. Or, when purchasing a license, a value indicating how many hours the function with the weighting factor “1” can be used and how many hours the function with the weighting factor “1” has been used so far It can also be managed by a numerical value indicating.

  According to the present invention, it is possible to efficiently manage licenses for software having a plurality of functions.

  1 is a diagram illustrating an example of the overall configuration of the software sharing system 1, FIG. 2 is a diagram illustrating an example of a hardware configuration of the license management server 2, and FIG. 3 is an example of a functional configuration of the license management server 2. FIG. 4 and FIG. 4 are diagrams illustrating an example of a functional configuration of the terminal device 3.

  As shown in FIG. 1, the software sharing system 1 according to the present invention includes a license management server 2, a plurality of terminal devices 31, 32, 33,. The license management server 2 and each terminal device 3 can be connected to each other via the communication line 4. As the communication line 4, a LAN, the Internet, a public line, a dedicated line, or the like is used. Hereinafter, the terminal devices 31, 32, 33,... May be collectively referred to as “terminal device 3”.

  The software sharing system 1 is provided in an office such as a government office or a company. A staff member working in the office can perform various operations by using software by operating one of the terminal devices 3.

  The license management server 2 executes processing for centrally managing software licenses used in the terminal device 3. Hereinafter, a case where the software SWC for realizing a CAD (Computer Aided Design) system is used in the office X will be described as an example.

  The license management server 2 can be connected to a supplier system PRS operated by a supplier (such as a sales company or a manufacturing company) that supplies the software SWC via the Internet or the like. Then, a procedure for purchasing a software license is executed.

  As shown in FIG. 2, the license management server 2 includes a CPU 2a, a RAM 2b, a ROM 2c, a hard disk 2d, and various interfaces. The hard disk 2d includes a license information management unit 201, a usage permission / inhibition determination unit 202, a usage status information reception unit 203, a consumption volume calculation unit 204, a license purchase procedure processing unit 205, a warning message transmission unit 206, as shown in FIG. A program and data for realizing functions such as the license database 2DB are installed. These programs and data are loaded into the RAM 2b as necessary, and the programs are executed by the CPU 2a.

  In addition, predetermined values Vd, β, coefficient α, weight coefficient table TLK, and the like, which will be described later, are stored in the hard disk 10d. These are determined at the time of contract between the office X and the supplier of the software SWC, but can be appropriately changed according to the specification results of the software SWC of the office X.

  The terminal device 3 is a computer for a user (staff) to perform work, such as a personal computer or a workstation. In addition to the software SWC, the hard disk of the terminal device 3 includes programs and data for realizing functions such as a use permission request processing unit 301, a use state detection unit 302, and a use state notification unit 303 as shown in FIG. Installed.

  Alternatively, a so-called NC (Network Computer) that is not provided with a hard disk can be used as the terminal device 3. In this case, an application server that stores software SWC and programs and data for realizing the functions shown in FIG. And the terminal device 3 downloads these from an application server and uses them as needed.

  FIG. 5 is a diagram illustrating an example of the license database 2DB, and FIG. 6 is a diagram illustrating an example of a weighting factor of each function provided in the software SWC.

  Next, processing contents of each part of the license management server 2 shown in FIG. 3 and each part of the terminal device 3 shown in FIG. 4 will be described.

  In FIG. 3, the license database 2DB of the license management server 2 stores information related to the license for the office X to use the software SWC. In the present embodiment, the license permits the software SWC to be used in a predetermined amount. In other words, the purchaser of the license can use the software SWC by a predetermined amount indicated by the license, but cannot use it beyond that. Hereinafter, such an amount related to the authority to use the software SWC is referred to as “volume”.

  Specifically, as shown in FIG. 5, license information DTL is stored in the license database 2DB for each license purchased by the office X from a software SWC supplier (such as a sales company or a manufacturing company).

  The serial code CR of the license information DTL is information for identifying the license related to the license information DTL from other licenses. The purchase volume Vo indicates a volume given to the purchaser of the license. That is, the volume at the time of purchasing the license is shown. The remaining volume Vx indicates how much software SWC can be used by the purchaser of the license based on the license. When the license is purchased, the value of the remaining volume Vx is the same as the value of the purchase volume Vo.

  In the present embodiment, the license for the software SWC is defined as follows. The volume given to the purchaser is consumed according to the usage time of the software SWC. However, each function provided in the software SWC is weighted, and the volume is consumed as the function having a large weight is used. When a plurality of functions are used at the same time, the volume is consumed according to the total weight of these functions.

  Further, it is defined that one license of the software SWC can be shared by a plurality of terminal devices 3. Of course, as the number of terminal devices 3 increases, the license volume is consumed more quickly. Therefore, the office X can purchase a plurality of licenses at a time according to the environment such as the workload or the business content. is there.

  The purchase procedure flag FG indicates whether a formal procedure for purchasing the license (hereinafter referred to as “official purchase procedure”) has been performed on the supplier. When the formal purchase procedure is performed, a value “1” indicating that is stored, and when the formal purchase procedure is not yet performed, a value “0” indicating that is stored. That is, in principle, the office X can use the software SWC only after purchasing a license through a formal purchase procedure. However, for some reason, a large amount of work requiring the software SWC may occur suddenly. As a result, the existing license alone may not be enough to use the software SWC. Therefore, it is assumed that the office X has purchased the license without performing the formal purchase procedure, and the license information DTL of the license is provisionally registered in the license database 2DB so that the formal purchase procedure for the license can be performed later. In addition, a contract is made in advance with the supplier of the software SWC.

  Returning to FIG. 3, the license purchase procedure processing unit 205 connects to the supplier system PRS and transmits license request information to perform the process of the formal purchase procedure for purchasing from the supplier of the newly added software SWC. Do. In principle, such processing is performed every period (for example, January, quarter, half year, or one year) determined by the office X in advance. Hereinafter, this period is referred to as “predetermined period”. Note that the number of licenses to be added is determined in advance based on the environment such as the workload of the office X or the business content. When the license is formally granted from the supplier, the license information management unit 201 newly registers (stores) the license information DTL of the license in the license database 2DB. In addition, when the license is insufficient, a new license may be requested temporarily.

  The license information management unit 201 registers new license information DTL in the license database 2DB, updates the contents of the existing license information DTL, or deletes the existing license information DTL. I do. As described above, the new license information DTL may be registered in the license database 2DB after the formal purchase procedure is performed, or may be temporarily registered in the license database 2DB prior to the formal purchase procedure.

  In FIG. 4, the use permission request processing unit 301 of the terminal device 3 performs a process for requesting the license management server 2 to grant permission to use the software SWC.

  The use permission determination unit 202 of the license management server 2 performs processing for determining whether or not the terminal device 3 may be permitted to use the software SWC. In order to permit the use of the software SWC, it is generally necessary to satisfy the following two conditions: that the terminal device 3 or its user has an appropriate access right and that the license is valid.

  The presence / absence of an appropriate access right is determined by using a conventional access right management method. On the other hand, the validity of the license is determined as follows based on the license information DTL registered (stored) in the license database 2DB. That is, when the remaining volume Vx of any license information DTL in the license database 2DB exceeds “0”, it is determined that the license is valid. When the remaining volume Vx of all license information DTL is “0”, it is determined that the license is not valid.

  When the license is not valid (that is, when there is no remaining license), the license information management unit 201 performs processing for temporarily registering license information DTL of a part or all of the license for the next predetermined period, and the volume Is replenished.

  That is, since the license is replenished when the license is insufficient, it is determined that the use of the software SWC is permitted if there is an appropriate access right for the software SWC, and is not permitted unless there is an appropriate access right. Determine. Then, the determination result is returned to the requesting terminal device 3.

  The usage status detection unit 302 of the terminal device 3 detects the usage status of the software SWC in the terminal device 3. Specifically, the function used during the period from when the software SWC is activated until it is terminated and its time are detected. These can be detected, for example, by checking the activation status of the modules for each function constituting the software SWC.

  The usage status notification unit 303 transmits the usage status of the software SWC detected by the usage status detection unit 302 to the license management server 2 as usage status information DTU.

  The usage status information receiving unit 203 of the license management server 2 performs processing for receiving usage status information DTU from the terminal device 3.

  Based on the received usage status information DTU, the consumed volume calculation unit 204 converts the volume consumed by the current use of the software SWC (hereinafter referred to as “consumed volume Vc”) into the following method. Calculate with

  As described above, each function of the software SWC is weighted. In this embodiment, as shown in FIG. 6, a numerical value representing the magnitude of the weight is defined for each function. Hereinafter, a coefficient representing such a numerical value is referred to as a “weight coefficient”. These weighting factors are defined in the weighting factor table TLK.

  The consumption volume calculation unit 204 substitutes the usage time for each function and the weighting factor of the function indicated in the software SWC into the following equation (1).

However, Ks means the weighting coefficient of the sth function defined in FIG. Ts means the current usage time of the s-th function defined in FIG. α indicates a volume consumed per unit time when a function having a weight of “1” is used. That is, it is a coefficient for converting the usage time into a volume unit.

  When the consumption volume Vc is calculated by the consumption volume calculation unit 204, the license information management unit 201 subtracts the consumption volume Vc from the remaining volume Vx of any license registered in the license database 2DB. If the remaining volume Vx of the license is less than the consumed volume Vc, the remaining volume Vx of the license is used up and the remaining amount (that is, the volume of “Vc−Vx”) is subtracted from the remaining volume Vx of the other licenses. . If it is not sufficient to use the remaining volume Vx of all licenses registered in the license database 2DB, the process for temporarily registering the license information DTL of a part or all of the licenses for the next predetermined period is license information. This is done by the management unit 201 and consumes those licenses.

  The license purchase procedure processing unit 205 requests the software SWC supplier to grant a new software SWC license. The request is made by transmitting license request information to the supplier system PRS every period determined by the office X (for example, January, quarter, half year, or one year). Hereinafter, this period is referred to as “predetermined period”. Note that the number of licenses to be requested is determined in advance based on the environment such as the workload of the office X or the business content. When a license is granted from the supplier, the license information management unit 201 newly registers (stores) the license information DTL of the license in the license database 2DB. In addition, when the license is insufficient, a new license may be requested temporarily.

  The warning message transmission unit 206 performs processing for transmitting a notification (alarm message) for warning the administrator of the software sharing system 1 when the license of the software SWC is insufficient for a predetermined value or more. The alarm message may be sent by sending an email to the administrator's email address.

  7 is a flowchart for explaining an example of the overall processing flow of the license management server 2, FIG. 8 is a diagram showing an example of a volume at the beginning of license operation management, and FIG. FIG. 10 is a flowchart for explaining an example of the flow of use permission processing, and FIG. 11 is an example of transition of each license when newly registering a license temporarily. 12 is a flowchart for explaining an example of the flow of volume consumption processing, FIG. 13 is a flowchart for explaining an example of the flow of temporary license purchase procedure processing, and FIG. 14 is a flowchart of the temporary license purchase procedure processing. FIG. 15 is a diagram showing an example of transition of each license, FIG. 15 is a diagram showing a first example of transition of each license at the time of preparation for the next predetermined period, and FIG. 16 is preparation for the next predetermined period It is a diagram showing a second example of the transition of the license at the time.

  Next, software SWC license management will be described in more detail with reference to flowcharts, bar graphs, and the like, taking various cases as examples.

  First, the bar graphs shown in FIGS. 8, 10, and 14 to 16 will be described. Each bar in the bar graph corresponds to one license whose license information DTL is registered in the license database 2DB. The shaded portion of the bar indicates the remaining license volume Vx, and the white portion indicates the consumed volume. If there are licenses with different purchase times, a bar for newly purchased licenses is shown on the right side.

  In preparation for introducing the software SWC, the license management server 2 purchases one or more licenses for the first predetermined period (first period) by the formal purchase procedure, and license information of these licenses. The DTL is registered in the license database 2DB (# 11 in FIG. 7). Here, it is assumed that 10 items are purchased together. At this time, the remaining volumes Vx of these licenses are all equal to the purchase volume Vo as shown in FIG. Further, a value “1” is stored in the purchase procedure flag FG (see FIG. 5) of the license information DTL so as to indicate that the license has been officially purchased.

  In addition, preparations such as installing the software SWC in the terminal device 3 are made as necessary.

  After completing the preparation, the license management server 2 starts operation management of the license of the software SWC. As processing for operation management, processing such as use permission processing, volume consumption processing, and temporary license purchase procedure processing is appropriately executed. These processes will be sequentially described later.

  Through the above-described preparation process, the staff of the office X can use the software SWC on his / her terminal device 3. When the start command for the software SWC is input by the user (staff), the terminal device 3 requests the license management server 2 to give permission to use the software SWC (# 31 in FIG. 9).

  Then, the license management server 2 executes the use permission process in the procedure as shown in FIG. That is, it is checked whether or not the access right for the software SWC is given to the requesting terminal device 3 or its user (# 211), and if the access right is given, the terminal indicates that the use is permitted. A reply is sent to the device 3, and if it is not given, a reply that the use is not permitted is answered (# 212).

  Before or after the access right check and use permission / reply answer processing, the remaining license volume Vx is confirmed based on the license information DTL stored in the license database 2DB. If the remaining volume Vx is “0” or less than the predetermined value Vd as shown in FIG. 11A (Yes in # 213), the license information DTL of a part or all of the licenses for the next predetermined period Is registered in the license database 2DB prior to the formal purchase procedure (# 214). That is, temporary registration is performed. As a result, the volume of the software SWC that can be used in the current period transitions as shown in FIG. In FIG. 11B and FIGS. 14 and 15 described later, a bar whose side is a dotted line indicates a temporarily registered volume. In the purchase procedure flag FG of the license information DTL of this license, “0” indicating that the formal purchase procedure has not yet been performed is stored.

  If the license management server 2 gives permission to use the software SWC (Yes in # 32 in FIG. 9), the terminal device 3 activates the software SWC (# 33). At this point, only the basic functions of the software SWC such as two-dimensional CAD are called.

  The terminal device 3 records the usage status of the software SWC, particularly the time during which the optional function modules such as the data conversion function and the three-dimensional CAD function (see FIG. 6) are activated (# 34). . When the software SWC is terminated (# 35), usage status information DTU indicating the current usage status of the software SWC is transmitted to the license management server 2 (# 36).

  Then, the license management server 2 executes the volume consumption process according to the procedure shown in FIG. That is, the usage time of each function of the software SWC (that is, the time from the activation of the module related to the function to the end) indicated in the usage status information DTU transmitted from the terminal device 3 and the weights in FIG. Based on the coefficient, the consumed volume Vc by using the current software SWC in the terminal device 3 is calculated (# 221).

  A volume corresponding to the consumed volume Vc is subtracted from the remaining volume Vx of any one or more licenses registered in the license database 2DB (# 224). However, if the remaining volume Vx is insufficient (Yes in # 222), as shown in FIG. 11, the license information DTL of some or all licenses for the next predetermined period is temporarily registered in the license database 2DB (# 223), the shortage is subtracted from the remaining volume Vx of the license (# 224).

  Further, the license management server 2 executes the temporary license purchase procedure process at a predetermined timing (for example, every several hours) during a predetermined period according to the procedure shown in FIG. The license management server 2 checks the consumption status of license information DTL that has not yet been officially purchased from the license information DTL registered in the license database 2DB (that is, provisionally registered) (# 231). The consumption status is obtained by subtracting the remaining volume Vx from the purchase volume Vo indicated in the license information DTL. And the total value Vw of these consumption conditions is calculated | required. This total value Vw is a volume consumed without performing a formal purchase procedure, as shown by a thick frame in FIG. 14A, and means a volume that is substantially insufficient.

  It is not preferable that the total value Vw becomes too large in terms of transactions with the supplier of the software SWC. Therefore, when the total value Vw exceeds the predetermined value β (Yes in # 232), the license management server 2 transmits an alarm message to the administrator (# 233). Then, in response to a command from the administrator, by performing communication with the supplier system PRS, as shown in FIG. 14B, processing for the formal purchase procedure of the license that is currently temporarily registered, or Then, a new license is additionally purchased by a formal purchase procedure, and the license information DTL is registered in the license database 2DB (# 234). The purchase procedure flag FG of the license information DTL of these licenses is updated to “1”.

  Alternatively, when the number of temporarily registered licenses exceeds a predetermined number, the processes of steps # 233 and # 234 may be performed.

  Returning to FIG. 7, when the current predetermined period ends (Yes in # 13), if the office X continues the contract for using the software SWC (Yes in # 14), the license management server 2 Processing for preparing a license for a predetermined period is performed (# 15).

  In principle, a predetermined number of licenses are purchased from a supplier, and license information DTL of those licenses is registered in the license database 2DB. Note that the license information DTL of a license that has been used up (the remaining volume Vx has become “0”) may be deleted from the license database 2DB.

  However, at the time when the current predetermined period ends, as shown in FIG. 15A, if there is a provisional registration license with the purchase procedure flag FG being “0”, Process. Then, as shown in FIG. 15B, a new license is newly purchased by a formal purchase procedure by subtracting the number of provisionally registered licenses from the predetermined number, and the license information DTL of each license is stored in the license database 2DB. Register with.

  Alternatively, as shown in FIG. 16A, when all or a part of the volume of any license is left (the remaining volume Vx is a positive value), it is shown in FIG. As described above, for the next predetermined period, a predetermined number of licenses are newly added to the license database 2DB, and the remaining licenses can be carried over and used.

  When the license for the next predetermined period is thus prepared, the process returns to step # 12, and the operation management process for the license of the software SWC in the next predetermined period is started. Thereafter, as long as the use contract of the software SWC is updated, the above processing is appropriately executed.

  According to the present embodiment, the use authority of the software SWC is managed by the concept of “volume”, and the volume consumption is calculated according to the weight of the function used by the software SWC. With such a configuration, more efficient license management according to the usage status of the software SWC than before can be performed.

  Further, according to the present embodiment, when the volume is insufficient, it is possible to use the volume for the next predetermined period after the formal procedure. Therefore, even when an urgent business occurs and the need for the software SWC increases rapidly, the software SWC can be used and dealt with in a large number of terminal devices. For example, in a disaster countermeasure room at a government office, even if a disaster occurs unexpectedly, the terminal device in the room can be fully operated and the software SWC can be used so that the disaster can be appropriately dealt with. become.

  In the present embodiment, the terminal device 3 transmits the usage status information DTU indicating the usage status from when the software SWC is activated to when it is terminated to the license management server 2. You may make it transmit the usage status information DTU which shows a usage status at any time.

  The maximum number of licenses or volumes that can be temporarily registered may be determined. As a result, it is possible to receive an appropriate license.

  In the present embodiment, the license-type software that does not limit the number of units that can be used simultaneously has been described as an example. However, the present invention can also be applied to license-type software that limits the number of units that can be used simultaneously. it can. For example, when the number of terminals that can be used simultaneously is ten, but the eleventh terminal device 3 requests the use of software, a license for the next predetermined period is temporarily registered. When the current predetermined period ends and becomes the next predetermined period, the temporarily registered license is offset with the license for the next predetermined period. Alternatively, if the number of units that can be used simultaneously is 10 but only 9 terminal devices 3 use software this term, one unused license can be carried over to the next predetermined period. .

  In the present embodiment, the license management server 2 may calculate the consumed volume Vc, and the terminal device 3 using the software SWC may be configured to notify the license management server 2 of the calculation. That is, the terminal device 3 may be provided with a function corresponding to the consumption volume calculation unit 204 in FIG.

  In addition, the configuration, processing content, processing order, etc. of the entire software sharing system 1, license management server 2, terminal device 3 or each part can be appropriately changed in accordance with the spirit of the present invention.

In the embodiment described above, the following notes are also disclosed.
(Appendix 1)
A software license management system for managing licenses of software used by a plurality of terminal devices,
Weight coefficient storage means for storing a weight coefficient indicating a weight for each function provided in the software;
Usable amount management means for performing processing for management relating to the usable amount, which is the amount that can be used in the future,
Usage status information acquisition means for acquiring usage status information indicating the usage status of the software in the terminal device;
The function used in the terminal device, the usage amount used by the function, and the weight of the function stored in the coefficient storage unit, which are indicated in the usage status information acquired by the usage status information acquisition unit Consumption amount calculating means for calculating a consumption amount that is an amount of the usable amount consumed by using the software by the terminal device based on a coefficient;
The usable amount management means performs a process of reducing the consumption amount calculated by the consumption amount calculation means from the usable amount.
A software license management system characterized by that.
(Appendix 2)
The usage amount of the function used in the terminal device is determined by the time when the function is used.
The software license management system according to attachment 1.
(Appendix 3)
The usable amount management means includes:
When the consumption amount calculated by the consumption amount calculation means is larger than the usable amount, a process of increasing the usable amount without going through a formal procedure with the software supplier,
Each time a predetermined period elapses, a process for adding a predetermined amount to the usable amount is performed through a formal procedure with the software supplier, and a formal procedure with the software supplier is not performed. If there is an amount increased in the usable amount, a process of reducing the increased amount from the usable amount is performed.
The software license management system according to Supplementary Note 1 or Supplementary Note 2.
(Appendix 4)
A notification means for notifying the administrator when the total amount increased to the usable amount without going through a formal procedure with the software supplier exceeds a predetermined amount;
The software license management system according to attachment 3.
(Appendix 5)
A software license management method for managing licenses of software used by a plurality of terminal devices,
For each function provided in the software, a weighting factor indicating a weight is stored in a storage medium,
The usable amount that is the amount that the software can be used in the future is stored in a storage medium,
Obtaining usage status information indicating the usage status of the software in the terminal device;
Based on the function used in the terminal device, the usage amount used by the function, and the weighting factor of the function indicated in the acquired usage status information, the terminal device consumes the use of the software. A consumption amount that is an amount of the usable amount to be calculated;
Reducing the calculated consumption from the available amount;
A software license management method characterized by the above.
(Appendix 6)
A computer program used for a computer that manages software licenses used by a plurality of terminal devices according to an available amount, which is an amount by which the software can be used in the future,
Processing for obtaining usage status information indicating the usage status of the software in the terminal device;
The terminal device used the software based on the function used in the terminal device, the usage amount used by the function, and the weighting factor set for the function, which are indicated in the acquired usage status information. Processing for calculating a consumption amount that is the amount of the usable amount consumed by
A process of reducing the calculated consumption from the available amount;
A computer program for causing a computer to execute.

  The present invention is particularly suitably used for managing licenses in an office provided with a large number of terminal devices. The license can be purchased without waste for the office, and the user can use the correct license for the software provider.

It is a figure which shows the example of the whole structure of a software sharing system. It is a figure which shows the example of the hardware constitutions of a license management server. It is a figure which shows the example of a functional structure of a license management server. It is a figure which shows the example of a functional structure of a terminal device. It is a figure which shows the example of a license database. It is a figure which shows the example of the weighting coefficient of each function provided in software. It is a flowchart for demonstrating the example of the flow of the whole process of a license management server. It is a figure which shows the example of the volume at the time of the start of the operation management of a license. It is a flowchart for demonstrating the example of the whole process flow of a terminal device. It is a flowchart for demonstrating the example of the flow of a use permission process. It is a figure which shows the example of the transition of each license at the time of newly performing temporary registration of a license. It is a flowchart for demonstrating the example of the flow of a volume consumption process. It is a flowchart for demonstrating the example of the flow of a license temporary purchase procedure process. It is a figure which shows the example of the transition of each license in the case of a license temporary purchase procedure process. It is a figure which shows the 1st example of the transition of each license at the time of preparation of the following predetermined period. It is a figure which shows the 2nd example of the transition of each license at the time of preparation of the following predetermined period.

Explanation of symbols

1 Software sharing system (software license management system)
201 License information management unit (usable amount management means)
203 Usage status information receiving unit (usage status information acquisition means)
204 Consumption volume calculation unit (consumption amount calculation means)
206 Warning message transmitter (notification means)
3 Terminal equipment DTU usage status information SWC software TLK Weight coefficient table (weight coefficient storage means)

Claims (5)

A software license management system for managing licenses of software used by a plurality of terminal devices,
Weight coefficient storage means for storing a weight coefficient indicating a weight for each function provided in the software;
Usable amount management means for performing processing for management relating to the usable amount, which is the amount that can be used in the future,
Usage status information acquisition means for acquiring usage status information indicating the usage status of the software in the terminal device;
The function used in the terminal device, the usage amount used by the function, and the weight of the function stored in the coefficient storage unit, which are indicated in the usage status information acquired by the usage status information acquisition unit Consumption amount calculating means for calculating a consumption amount that is an amount of the usable amount consumed by using the software by the terminal device based on a coefficient;
The usable amount management means performs a process of reducing the consumption amount calculated by the consumption amount calculation means from the usable amount.
A software license management system characterized by that. The usable amount management means includes:
When the consumption amount calculated by the consumption amount calculation means is larger than the usable amount, a process of increasing the usable amount without going through a formal procedure with the software supplier,
Each time a predetermined period elapses, a process for adding a predetermined amount to the usable amount is performed through a formal procedure with the software supplier, and a formal procedure with the software supplier is not performed. If there is an amount increased in the usable amount, a process of reducing the increased amount from the usable amount is performed.
The software license management system according to claim 1. A notification means for notifying the administrator when the total amount increased to the usable amount without going through a formal procedure with the software supplier exceeds a predetermined amount;
The software license management system according to claim 2. A software license management method for managing licenses of software used by a plurality of terminal devices,
For each function provided in the software, a weighting factor indicating a weight is stored in a storage medium,
The usable amount that is the amount that the software can be used in the future is stored in a storage medium,
Obtaining usage status information indicating the usage status of the software in the terminal device;
Based on the function used in the terminal device, the usage amount used by the function, and the weighting factor of the function indicated in the acquired usage status information, the terminal device consumes the use of the software. A consumption amount that is an amount of the usable amount to be calculated;
Reducing the calculated consumption from the available amount;
A software license management method characterized by the above. A computer program used for a computer that manages software licenses used by a plurality of terminal devices according to an available amount, which is an amount by which the software can be used in the future,
Processing for obtaining usage status information indicating the usage status of the software in the terminal device;
The terminal device used the software based on the function used in the terminal device, the usage amount used by the function, and the weighting factor set for the function, which are indicated in the acquired usage status information. Processing for calculating a consumption amount that is the amount of the usable amount consumed by
A process of reducing the calculated consumption from the available amount;
A computer program for causing a computer to execute.