Management device, management method, and program
The management device addresses software license understanding and management challenges by identifying violations and suggesting licenses, enhancing compliance and efficiency in IT asset management systems.
Patent Information
- Application Number
- JP2023223002
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-28
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-08-19
AI Technical Summary
Software users often fail to understand license terms, leading to unintentional violations, and it is challenging to manage licenses across multiple versions and organizations, especially in large companies.
A management device that collects inventory information, determines license violations, and provides alerts or suggests appropriate licenses through a scoring system based on rule-based and collaborative filtering methods.
Supports effective software license management by identifying violations and suggesting suitable licenses, reducing compliance risks and administrative burdens.
Smart Images

Figure 0007581475000001 
Figure 0007581475000002 
Figure 0007581475000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a management device, a management method, and a program. [Background technology]
[0002] In companies and the like, there are a large number of information devices (for example, various terminals such as PCs (personal computers), server devices, etc.) within the network, and the number of software installed on these information devices is also enormous. For this reason, companies and the like often introduce IT (Information Technology) asset management systems to efficiently manage the software assets and licenses they possess.
[0003] IT asset management systems provide a mechanism for ensuring appropriate use of software by checking the usage of software, for example, software that requires paid license management, or software that uses non-commercial licenses that limit use within the company. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2001-005659 A Summary of the Invention [Problem to be solved by the invention]
[0005] Generally, software has license agreement terms (also called "end user agreement terms"), and software users are expected to fully understand and agree to the contents of these license agreement terms before using the software. However, license agreement terms are generally difficult to understand, and software users do not necessarily understand all of the terms correctly. As a result, software users may unintentionally violate the license agreement terms.
[0006] Furthermore, when software that has not been assigned a license is found among the software installed in each information device (terminal, server device, etc.) (i.e., when software that is being used illegally is found), it is necessary to assign a license to this software to eliminate the illegal use. However, for example, even for the same software, the licenses may differ depending on the version or purchase form, and in large companies, etc., there may be multiple license management organizations, making it difficult to determine which license should be assigned.
[0007] The embodiment of the present invention has been made in consideration of the above points, and has an object to support software license management. [Means for solving the problem]
[0008] In order to achieve the above-mentioned object, a management device in an embodiment of the present invention is a management device that manages licenses for software installed on multiple information devices, and has a first judgment means that judges whether a license violation has occurred in the software installed on the information device based on inventory information collected from the information device and license information stored in a memory unit, a second judgment means that judges the type of the license violation if it is judged that a license violation has occurred in the software installed on the information device, and a creation unit that creates presentation content to be presented to a specified terminal based on the confirmation result of whether or not there is a license that can be assigned to the software if the type of license violation judged by the second judgment means is unauthorized use. Effect of the Invention
[0009] It can assist with software license management. [Brief description of the drawings]
[0010] [Figure 1]1 is a diagram illustrating an example of an overall configuration of an asset management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of a functional configuration of a management device according to the present embodiment. [Diagram 3] FIG. 2 illustrates an example of hardware inventory information. [Figure 4] FIG. 11 illustrates an example of software inventory information. [Diagram 5] FIG. 2 is a diagram illustrating an example of hardware asset management ledger information. [Figure 6] 11 is a diagram illustrating an example of software-property management ledger information. [Figure 7] FIG. 2 is a diagram illustrating an example of license management register information. [Figure 8] FIG. 11 illustrates an example of license allocation information. [Figure 9] 10 is a flowchart illustrating an example of a license management process according to the embodiment. [Figure 10] FIG. 13 illustrates an example of an alert screen. [Figure 11] FIG. 13 illustrates an example of an allocation license candidate presentation screen. [Figure 12] FIG. 13 is a diagram illustrating an example of a rule table used in rule-based score calculation. [Figure 13] FIG. 13 is a diagram for explaining an example of score calculation by collaborative filtering (user-based). [Figure 14] FIG. 13 is a diagram for explaining an example of score calculation by collaborative filtering (item-based). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, an embodiment of the present invention (hereinafter also referred to as "the present embodiment") will be described with reference to the drawings. In this embodiment, an asset management system 1 that manages software licenses and the like as IT assets will be described. Note that the embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0012] <Overall composition> First, the overall configuration of an asset management system 1 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the overall configuration of an asset management system 1 according to this embodiment.
[0013] As shown in FIG. 1, an asset management system 1 according to this embodiment includes a management device 10, a collection device 20, one or more information devices 30, and an administrator terminal 40.
[0014] The information device 30 is various terminals (for example, a PC, a smartphone, a tablet terminal, etc.), a server device, etc. For example, various software programs are installed in the information device 30. The software installed in the information device 30 and the licenses for this software are managed by the management device 10. Furthermore, the information device 30 itself (or various devices and various apparatuses included in the information device 30) is managed as a hardware asset by the management device 10.
[0015] Furthermore, the information device 30 has installed therein dedicated software (inventory collection software) that transmits to the collection device 20 software inventory information indicating information related to software installed in the information device 30, and hardware inventory information indicating information related to the information device 30 itself (or various devices and equipment included in the information device 30). Note that hereinafter, the software inventory information and hardware inventory information are collectively referred to as "inventory information."
[0016] Here, inventory is a term that indicates owned assets, and is a term that is widely used in the field of IT asset management, etc. Note that the inventory collection software itself may be included in the software managed by the management device 10.
[0017] However, if the collection device 20 is able to obtain software inventory information and hardware inventory information from the information device 30 (i.e., for example, if agentless inventory collection software is installed in the collection device 20), the inventory collection software does not need to be installed in the information device 30.
[0018] The collection device 20 is a computer or computer system that collects software inventory information and hardware inventory information transmitted from the information device 30. The collection device 20 transmits the software inventory information and hardware inventory information collected from the information device 30 to the management device 10.
[0019] The collection device 20 may be configured integrally with the management device 10. That is, the management device 10 may have the function of the collection device 20 (i.e., the function of collecting software inventory information and hardware inventory information).
[0020] The management device 10 is a computer or computer system that manages IT assets (software assets, licenses, hardware assets, etc.). The management device 10 uses the software inventory information and hardware inventory information collected by the collection device 20 to provide notifications and the like to support software license management and to support license allocation. That is, the management device 10 determines whether a license violation has occurred in the information device 30, and if a license violation has occurred, provides notifications such as warnings and supports license allocation. This makes it possible to resolve software license violations and, for example, reduce the risk of compliance violations in a company or the like, and also reduce the burden of license allocation work on the administrator or the like.
[0021] In this embodiment, there are two types of license violations: license violation and unauthorized use. A license violation means that although a license has been assigned to the software, the contractual terms of the license (license terms) are violated. Examples of license violations include when the number of devices that can be used with the same license is exceeded or when a non-commercial license is used commercially. On the other hand, unauthorized use means that a license has not been assigned to the software.
[0022] The administrator terminal 40 is a terminal (such as a PC, a smartphone, a tablet terminal, etc.) used by an administrator (such as a system administrator) of the information device 30. For example, notifications transmitted from the management device 10 are displayed on the administrator terminal 40. The administrator terminal 40 may be configured integrally with the management device 10.
[0023] <Functional configuration> Next, the functional configuration of the management device 10 according to the present embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the functional configuration of the management device 10 according to the present embodiment.
[0024] 2, the management device 10 according to this embodiment includes an acquisition unit 101, a hardware identification unit 102, a software identification unit 103, a determination unit 104, an alert notification unit 105, a score calculation unit 106, and a candidate presentation unit 107. Each of these functional units is realized by a process executed by a processor such as a CPU (Central Processing Unit) by one or more programs installed in the management device 10.
[0025] Moreover, the management device 10 according to the present embodiment has a storage unit 108. The storage unit can be realized using a storage device such as a hard disk drive (HDD) or a solid state drive (SSD). The storage unit may also be realized using a storage device connected to the management device 10 via a communication network.
[0026] The storage unit 108 stores hardware asset management ledger information 220, software dictionary information 230, software asset management ledger information 240, license management ledger information 250, and license allocation information 260. Each of these pieces of information may be stored in the storage unit 108 realized using one storage device, or may be stored in the storage unit 108 realized using multiple storage devices.
[0027] The hardware asset management ledger information 220 is information that indicates a hardware asset management ledger for managing hardware assets. The hardware asset management ledger information 220 will be described in detail later.
[0028] The software dictionary information 230 is information indicating a software dictionary used for software name matching. Software name matching refers to converting a software name included in software inventory information into a software name that uniquely identifies the software (this conversion is also called "software name normalization").
[0029] Generally, the software names included in the software inventory information are often not names that can uniquely identify the software. For example, the software names included in the software inventory information may be expressed using symbols or may be expressed using an abbreviated name. Furthermore, the software names included in the software inventory information may contain a mixture of half-width and full-width characters. Therefore, the software dictionary information 230 is used to convert such software names into software names that can uniquely identify the software.
[0030] For example, software names included in the software inventory information are associated with normalized software names in the software dictionary information 230. Note that the software dictionary information 230 may further be associated with the type of license for the software (for example, information indicating whether the license is paid or free).
[0031] The software-property management ledger information 240 is information that indicates a software-property management ledger for managing software properties. The software-property management ledger information 240 will be described in detail later.
[0032] The license management ledger information 250 is information that indicates a license management ledger for managing licenses. The license management ledger information 250 will be described in detail later.
[0033] The license allocation information 260 is information that indicates the license allocation status. The license allocation information 260 will be described in detail later.
[0034] The acquiring unit 101 acquires the inventory information 210 by receiving the inventory information 210 transmitted from the collecting device 20. Here, the inventory information 210 is composed of hardware inventory information 211 and software inventory information 212. Details of the hardware inventory information 211 and the software inventory information 212 will be described later. It is assumed that one piece of inventory information 210 is composed of the hardware inventory information 211 of a certain information device 30 and the software inventory information 212 of the information device 30.
[0035] The hardware identification unit 102 uses the hardware asset management ledger information 220 stored in the storage unit 108 to identify the hardware (that is, the information device 30) indicated by the hardware inventory information 211 acquired by the acquisition unit 101.
[0036] The software identifying unit 103 identifies software indicated by the software inventory information 212 acquired by the acquiring unit 101, using the software dictionary information 230 and the software-property management ledger information 240 stored in the storage unit .
[0037] The determination unit 104 uses the license management ledger information 250 and the license allocation information 260 stored in the storage unit 108 to determine whether a license violation has occurred in the hardware identified by the hardware identification unit 102 (i.e., the information device 30). When the determination unit 104 determines that a license violation has occurred, it determines whether the license violation is a license violation or an unauthorized use. Here, when a license is assigned to the software identified by the software identification unit 103 but the contract terms of the license (license terms) are violated, the determination unit 104 determines that the license violation has occurred, whereas when a license is not assigned to the software identified by the software identification unit 103, it determines that the software is unauthorized use.
[0038] Furthermore, when the determining unit 104 determines that the license violation is unauthorized use, it determines whether or not there is a license that can be assigned to the software that is being unauthorizedly used (that is, software to which no license has been assigned).
[0039] The alert notification unit 105 sends an alert to a specified notification destination (e.g., the administrator terminal 40 or the information device 30 where the license violation is occurring) when the judgment unit 104 judges that the license violation is a violation of the usage permission or when it judges that there is no license that can be assigned to the software that is being misused.
[0040] When the determining unit 104 determines that there is a license that can be assigned to the software that is being misused (i.e., a license with an available number of licenses), the score calculation unit 106 calculates the scores of these licenses using a predetermined score calculation method. Here, the score is an index value that indicates how appropriate it is to assign the license to the software.
[0041] The candidate presentation unit 107 uses the score calculated by the score calculation unit 106 to present candidates for licenses that can be assigned to the software being misused to a predetermined presentation destination (for example, the administrator terminal 40 or the information device 30 where the license violation is occurring). At this time, the candidate presentation unit 107 presents the license candidates, for example, in ascending order of score (or descending order of score). This enables the administrator or the like who assigns the license to assign an appropriate license to the software where misuse is occurring.
[0042] <Hardware inventory information 211> Here, the hardware inventory information 211 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the hardware inventory information 211. Note that the hardware inventory information 211 is collected by the collection device 20 for each information device 30.
[0043] As shown in FIG. 3, the hardware inventory information 211 includes a "device identification number," a "manufacturer name," a "model number," a "serial number," a "computer name," and a "MAC (Media Access Control) address."
[0044] The "device identification number" is a number generated by inventory collection software installed in the information device 30, and is an ID that uniquely identifies the information device 30. The "device identification number" may be called something else, such as a "device number" or a "terminal identification number."
[0045] "Manufacturer name" is the name of the manufacturer of information device 30. "Model number" is the model number of information device 30. "Serial number" is the serial number of information device 30 (e.g., a manufacturing specific number, etc.). "Computer name" is the name set for information device 30. "MAC address" is the MAC address of information device 30.
[0046] Note that the manufacturer name, model number, serial number, computer name, and MAC address are examples of information about the information device 30 collected by the inventory collection software, and the information about the information device 30 collected by the inventory collection software is not limited to these.
[0047] <Software inventory information 212> Next, the software inventory information 212 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the software inventory information 212. The software inventory information 212 is collected by the collection device 20 for each information device 30.
[0048] 4, the software inventory information 212 includes one or more records. Each record includes a "software name," a "manufacturer name," and an "installation date."
[0049] "Software name" is the name of the software. As described above, the software name in the software inventory information 200 is often not a name that can uniquely identify the software.
[0050] "Manufacturer name" is the name of the manufacturer of the software. "Installation date" is the date on which the software was installed in the information device 30. Note that the "installation date" may be the date and time when the software was installed in the information device 30.
[0051] Note that the software inventory information 212 is associated with, for example, an "equipment identification number," and this "equipment identification number" associates the hardware inventory information 211 with the software inventory information 212. Also, the software name, manufacturer name, and installation date are examples of software information collected by the inventory collection software, and the software information collected by the inventory collection software is not limited to these.
[0052] <Hardware asset management ledger information 220> Next, the hardware asset management ledger information 220 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the hardware asset management ledger information 220.
[0053] 5, the hardware asset management ledger information 220 includes one or more records. Each record includes a "hardware management ID," a "device identification number," a "manufacturer name," a "model number," a "serial number," a "computer name," a "MAC address," a "management department," a "manager," a "user ID," and a "status."
[0054] The "device identification number", "manufacturer name", "model number", "serial number", "computer name", and "MAC address" are as described above.
[0055] "Hardware management ID" is an ID that uniquely identifies information device 30. "Management department" is the department that manages information device 30. "Administrator" is an ID that uniquely identifies the administrator of information device 30. "User ID" is an ID that uniquely identifies the user who is using information device 30.
[0056] "Status" refers to the state of the hardware. Examples of hardware states include "in use," "idle," and "discarded." "In use" refers to a state in which the information device 30 is being used by a user. "Idle" refers to a state in which the information device 30 is not being used by a user (i.e., a state in which the information device 30 is not assigned to a user). "Discarded" refers to a state in which the information device 30 has been discarded.
[0057] For example, when a piece of hardware to be managed is added or deleted, the administrator uses the administrator terminal 40 to add or delete a record in the hardware asset management ledger information 220 .
[0058] <Software Asset Management Register Information 240> Next, the software-property management ledger information 240 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the software-property management ledger information 240.
[0059] 6, software-property management ledger information 240 includes one or more records. Each record includes a "software management ID," a "software name," a "manufacturer name," a "version," a "paid / free classification," and a "type."
[0060] "Software name" and "manufacturer name" are as described above. "Software management ID" is an ID that uniquely identifies software of the same type. "Version" is the version of the software. Note that the version may also include the revision of the software. "Paid / free classification" is a classification that indicates whether the software is paid or free.
[0061] "Type" is the type of software. Examples of software types include "business," "utility," and "other." "Business" software is software that provides functions that directly or indirectly support various business operations, such as various application software such as word processing software and spreadsheet software. "Utility" is software that provides auxiliary functions, such as printer drivers and encryption software. "Other" is software other than "business" and "utility," such as software update programs and security patches.
[0062] For example, when software to be managed is added or deleted, the administrator uses the administrator terminal 40 to add or delete a record in the software-property management ledger information 240 .
[0063] <License management ledger information 250> Next, the license management ledger information 250 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the license management ledger information 250.
[0064] 7, license management ledger information 250 includes one or more records. Each record includes a "license management ID," a "software management ID," a "license type," an "additional license," a "purchase date," a "management department," an "administrator," a "original license management ID," a "number of licenses held," a "total number of uses," and "other conditions."
[0065] The "license management ID" is an ID that uniquely identifies a software license. The "software management ID" is, as described above, an ID that uniquely identifies software of the same type.
[0066] "License type" is the type of license. Examples of license types include "user license", "device license", and "freeware". A "user license" is, for example, a license that allows one user to use the software. A "device license" is, for example, a license that allows the installation of the software in one information device 30. "Freeware" is, for example, a license that does not require a license agreement. In addition to these, there are various other license types, such as a "processor license".
[0067] An "additional license" is a right (contract) that accompanies a license agreement. Examples of such rights include "upgrade rights" and "downgrade rights." Upgrade rights are the right to use software with a higher version than the version of the software licensed. Downgrade rights are the right to use software with a lower version than the version of the software licensed. In addition to these, there are various other types of additional licenses, such as "dual installation rights."
[0068] "Purchase date" is the date when the license was purchased. "Management department" is the department that manages the licenses. "Administrator" is the person who manages the licenses. Here, even if the licenses are for the same software (i.e., the same software management ID), if the management departments, etc. are different, they are managed as different licenses (i.e., managed with different license management IDs). For example, in the example shown in Figure 6, the record with license management ID "LC01" and the record with license management ID "LC02" are licenses for the same software (i.e., software management ID "SW01"), but are managed as different licenses.
[0069] The "original license management ID" refers to the license management ID of the parent license (i.e., the license management ID of the software before the upgrade or downgrade) when the license agreement includes upgrade or downgrade rights.
[0070] "Number of owned licenses" is the number of owned licenses. For example, if the number of owned licenses is "10" and the license type is a "device license", it indicates that licenses for 10 devices are owned. Similarly, if the number of owned licenses is "10" and the license type is a "user license", it indicates that licenses for 10 users are owned.
[0071] "Total number of uses" refers to the number of licenses actually being used out of the number of owned licenses (i.e., licenses assigned to software). "Other conditions" refers to various conditions regarding the use of the software (i.e., conditions set out in the license agreement clauses (license terms)). Examples of such conditions include "conditions regarding the number of devices that can use the software simultaneously with one license," "conditions regarding the period for which the software can be used," "conditions allowing the software to be used only for non-commercial use," etc.
[0072] In addition to the above, each record of the license management ledger information 250 includes a "license name" indicating the name of the license, a "use mode" indicating whether the license is a permanent license or a non-permanent license, etc. In addition to this, for example, if the use mode of the license is non-permanent, a "license expiration date" indicating the expiration date of the license may be included.
[0073] Furthermore, for example, when a new license agreement is concluded or when a license agreement expires, the administrator uses the administrator terminal 40 to add or delete records to or from the license management ledger information 250 .
[0074] <License allocation information 260> Next, the license allocation information 260 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the license allocation information 260.
[0075] 8, the license allocation information 260 includes one or more records. Each record includes an "allocation management ID", a "hardware management ID", and a "license management ID".
[0076] The "allocation management ID" is an ID that uniquely identifies each record of the license allocation information 260. The "hardware management ID" is an ID that uniquely identifies the information device 30, as described above. The "license management ID" is an ID that uniquely identifies a software license, as described above.
[0077] This allows management of which information device 30 the software license is assigned to, installed on which software. For example, the record for assigned management ID "AS01" indicates that the license with license management ID "LC01" (i.e., the license for the software with software management ID "SW01") is assigned to the software installed on the information device 30 with hardware management ID "HW01" (the software with software management ID "SW01").
[0078] For example, when a license allocation is added or deleted, a record is added or deleted from the license allocation information 260.
[0079] <License management process> Hereinafter, a process (license management process) for managing a software license by the management device 10 according to the present embodiment will be described with reference to Fig. 9. Fig. 9 is a flowchart showing an example of the license management process according to the present embodiment.
[0080] First, the acquiring unit 101 acquires the inventory information 210 by receiving the inventory information 210 transmitted from the collecting device 20 (step S101). As described above, the inventory information 210 is composed of hardware inventory information 211 and software inventory information 212.
[0081] Next, the hardware identification unit 102 uses the hardware asset management ledger information 220 stored in the storage unit 108 to identify the hardware indicated by the hardware inventory information 211 acquired in the above step S101 (i.e., the hardware management ID of the information device 30) (step S102). More specifically, the hardware identification unit 102 identifies the record of the hardware asset management ledger information 220 stored in the storage unit 108 (i.e., the hardware management ID of this record) based on the manufacturer name, model number, serial number, computer name, MAC address, etc. included in the hardware inventory information 211. As a result, the hardware management ID of the information device 30 indicated by the hardware inventory information 211 is identified.
[0082] Next, using the software dictionary information 230 and the software-asset management ledger information 240 stored in the storage unit 108, the software identification unit 103 identifies each piece of software indicated by the software inventory information 212 acquired in step S101 above (i.e., the software management ID of each piece of software) (step S103). More specifically, the software identification unit 103 first uses the software dictionary information 230 to match the software names included in the software inventory information 212 and identify a normalized software name. Then, the software identification unit 103 identifies a record in the software-asset management ledger information 240 (i.e., the software management ID of this record) using the normalized software name. As a result, the software management ID of each piece of software indicated by the software inventory information 212 is identified.
[0083] Next, the judgment unit 104 judges whether or not a license violation has occurred in the information device 30 identified in the above step S102, using the license management ledger information 250 and the license allocation information 260 stored in the storage unit 108 (step S104). That is, the judgment unit 104 judges whether or not a license violation or unauthorized use has occurred in the software of the software management ID identified in the above step S103, in the information device 30 of the hardware management ID identified in the above step S102.
[0084] Here, when determining whether or not a license violation has occurred, the determination unit 104, for example, first refers to the license allocation information 260 to identify the allocation management ID corresponding to the hardware management ID. Then, the determination unit 104 may refer to the license management ledger information 250 to determine whether or not the information device 30 satisfies the "other conditions" corresponding to the allocation management ID. In this case, if the information device 30 satisfies all of the "other conditions", it is determined that no license violation has occurred, and if the information device 30 does not satisfy at least some of the "other conditions", it is determined that a license violation has occurred.
[0085] On the other hand, when determining whether unauthorized use has occurred, the determination unit 104, for example, first refers to license allocation information 260 to identify the allocation management ID corresponding to the hardware management ID. Then, the determination unit 104 refers to license management ledger information 250 to determine whether the software management ID identified in step S103 above is present among the software management IDs corresponding to the allocation management ID. In this case, if the software management ID identified in step S103 above is present, it is determined that unauthorized use has not occurred, and if the software management ID identified in step S103 above is not present, it is determined that unauthorized use has occurred.
[0086] If it is determined in step S104 that a license violation has occurred, the determination unit 104 determines whether the license violation is a usage permission violation or an unauthorized use (step S105). Note that if it is determined in step S104 that multiple license violations have occurred, the process from step S105 onward may be executed for each of the multiple license violations.
[0087] If it is determined in step S105 above that unauthorized use has occurred as a license violation, the determination unit 104 determines whether or not there is a license that can be assigned to the software in which unauthorized use has occurred (i.e., software to which no license has been assigned) (step S106). More specifically, the determination unit 104 refers to the license management ledger information 250 and determines whether or not there is a record that includes the software management ID of the software in which unauthorized use has occurred and has available licenses (i.e., "number of owned licenses > total number of uses"). If such a record exists, it is determined that there is an assignable license, and if not, it is determined that there is no assignable license. Hereinafter, the software in which unauthorized use has occurred is also referred to as "allocation target software," and the license that can be assigned to this allocation target software is also referred to as "allocation license candidate."
[0088] If it is determined in step S105 above that a license violation has occurred, or if it is determined in step S106 above that there is no license that can be assigned (candidate license for assignment), the alert notification unit 105 notifies a predetermined notification destination (e.g., the administrator terminal 40 or the information device 30 where the license violation has occurred) of an alert, thereby displaying an alert notification screen (step S107).
[0089] An example of an alert notification screen displayed on the administrator terminal 40 or the information device 30 is shown in Fig. 10. The alert notification screen 1000 shown in Fig. 10 includes, for example, an "occurrence date" when the alert occurred, a "status" indicating whether the alert has been resolved, a "message" indicating the contents of the alert, a "computer name" indicating the computer name of the information device 30 in which the alert occurred, a "management department name" indicating the name of the management department of the information device 30, an "administrator name" indicating the administrator of the information device 30, and a "user name" indicating the name of the user of the information device 30. Also included is a "details" button for displaying more detailed information about the alert.
[0090] By referring to such an alert notification screen 1000, the administrator terminal 40 or the user of the information device 30 can know an alert that has occurred on the information device 30 (i.e., an alert indicating that a license violation has occurred or an alert indicating that unauthorized use has occurred). Therefore, in order to resolve this alert, it is possible to resolve the license violation state or assign a license. The alert notification screen 1000 can be displayed, for example, by a browser or a predetermined application program installed on the administrator terminal 40 or the information device 30.
[0091] Returning to the description of Fig. 9, if it is determined in step S106 that there are licenses that can be assigned (allocated license candidates), the score calculation unit 106 calculates the scores of the assigned license candidates by a predetermined score calculation method (step S108). The score calculation method will be described in detail later.
[0092] Next, the candidate presentation unit 107 displays an allocation license presentation screen by transmitting the score calculated in step S108 above and the allocation license candidates that can be assigned to the software being misused (allocation target software) to a predetermined presentation destination (for example, the administrator terminal 40 or the information device 30 where the license violation is occurring). At this time, the allocation license presentation screen displays the allocation license candidates in ascending order of score (or descending order of score), for example. Note that the number of allocation license candidates and their scores displayed on the license presentation screen may be all the allocation license candidates and their scores, or may be some of the allocation license candidates and their scores (for example, the allocation license candidates with the top N scores and their scores).
[0093] An example of an allocation license presentation screen displayed on the administrator terminal 40 or the information device 30 is shown in Fig. 11. The allocation license candidate presentation screen 2000 shown in Fig. 11 includes, for example, a "license name" indicating the name of the allocation license candidate, a "management department name" indicating the name of the management department of the allocation license candidate, a "use mode" indicating the usage mode of the allocation license candidate, a "total number of uses / number of owned licenses" indicating the total number of uses and the number of owned licenses of the allocation license candidate, a "license type" indicating the license type of the allocation license candidate, a "score" indicating the score of the allocation license candidate, etc. Also included is an "assign" button 2001 for assigning the allocation license candidate to the allocation target software.
[0094] At this time, each allocation license candidate is displayed, for example, in ascending order of score (or descending order of score). For example, if the higher the score, the more appropriate it is to assign the allocation license candidate to the allocation target software, the allocation license candidates are displayed in descending order of score. On the other hand, if the lower the score, the more appropriate it is to assign the allocation license candidate to the allocation target software, the allocation license candidates are displayed in ascending order of score. This allows the user of the administrator terminal 40 or the information device 30 to easily know which allocation license candidate is appropriate to assign to the allocation target software. Then, when the user presses the "Assign" button 2001, the allocation license candidate corresponding to the "Assign" button 2001 is assigned to the allocation target software.
[0095] In this embodiment, the scores and the allocation license candidates sorted in ascending or descending order of the scores are presented to a user (such as a user of the administrator terminal 40 or a user of the information device 30), and the license is assigned to the allocation target software by the user's operation. However, this is not limited to the above, and the management device 10 may automatically assign licenses to the allocation target software according to the scores. For example, the management device 10 may automatically assign the allocation license candidate with the highest score (or the allocation license candidate with the lowest score) among the allocation license candidates to the allocation target software. In addition, at this time, for example, the management device 10 may automatically assign only when the maximum score is equal to or greater than a predetermined threshold (or the minimum score is equal to or less than a predetermined threshold), and may display an allocation license candidate presentation screen in other cases.
[0096] <Score calculation method> In the following, a method for calculating the score of each assigned license candidate in step S109 of FIG. 9 will be described.
[0097] Score calculation method 1: Rule-based As a first score calculation method, a case where the score of each assigned license candidate is calculated by a rule base will be described. In this case, the score calculation unit 106 calculates the score of each assigned license candidate by using a table (rule table) in which rules are defined in advance. For example, the rule table includes items and conditions (rules), and the score calculation unit 106 calculates the score by determining whether the assigned license candidate satisfies the condition for each item. Here, an example of a rule table used in the rule base is shown in FIG. 12. The rule table shown in FIG. 12 includes, for example, an item "user / management department" and its condition, an item "total number of uses / number of licenses held" and its condition, an item "license type" and its condition, etc. The score calculation unit 106 calculates the score by determining whether the assigned license candidate satisfies the condition corresponding to each item, and then assigning a score according to the condition.
[0098] For example, in the rule table shown in Fig. 12, the condition corresponding to the item "user / management department" is "if the organization to which the user belongs / the management department of the hardware matches the management department of the license, assign a score of a1." In this case, if the organization to which the user of the information device 30 in which the software to be allocated is installed or the management department of the information device 30 matches the management department of the allocated license candidate, the score calculation unit 106 assigns a1 to the score of the allocated license candidate. The sum of the scores assigned in this way becomes the score of the allocated license candidate.
[0099] Note that the items and conditions in the rule table shown in Fig. 12 are merely examples, and various other items and conditions are possible. For example, "if the license usage type is 'permanent', a score a5 is assigned, and if it is 'non-permanent', a score a6 is assigned (a5>a6)", "if the software to be assigned is running on a virtual machine, a score a7 is assigned to a license that has already been assigned to software running on the same host hardware", "a score a8 is assigned to a second license", etc. Note that the scores may be normalized to be between 0 and 1.
[0100] · Score calculation method 2: User-based collaborative filtering As a second score calculation method, a case where the score of each assigned license candidate is calculated by user-based collaborative filtering will be described. In this case, the score calculation unit 106 calculates the scores of the assigned license candidates so that the scores of licenses used by other users who use licenses similar to those of the user of the information device 30 in which the assigned software is installed are increased.
[0101] 13, for example, the user of the information device 30 in which the software to be allocated (this software is referred to as "Software X") is installed is referred to as "U10", and the other users are referred to as "U1" to "U9". In this case, it is assumed that there are "Software X License 1" and "Software X License 2" as licenses to be calculated (i.e., candidates for allocated licenses).
[0102] Also, in Fig. 13, it is assumed that the license being used by the user is set to "1." For example, in the example shown in Fig. 13, the licenses being used by "U1" are "Software A License 1," "Software B License 1," and "Software X License 1." Similarly, for example, the licenses being used by "U9" are "Software A License 3," "Software C License 2," and "Software X License 2."
[0103] In this case, the score calculation unit 106 calculates the number of times the same license is used by user "U10" and each of the other users "U1" to "U9" as the similarity, and then sets the maximum similarity of users using "Software X License 1" as the score for "Software X License 1," and sets the maximum similarity of users using "Software X License 2" as the score for "Software X License 2."
[0104] For example, user "U10" and user "U1" are using the same license, "Software B License 1." Therefore, the similarity for user "U1" is "1." For example, user "U10" and user "U4" are using the same licenses, "Software A License 2," "Software B License 1," and "Software C License 1." Therefore, the similarity for user "U4" is "3." The similarities for other users are calculated in the same way.
[0105] 13, the score of "Software X License 1" is "3," and the score of "Software X License 2" is "2." These scores may be normalized to be between 0 and 1. However, instead of the maximum value of the similarity, for example, the average value of the similarity of users who use the allocated license candidate may be used as the score of the allocated license candidate.
[0106] When calculating scores using user-based collaborative filtering, unlike rule-based filtering, there is no need to define rules in advance, and the more learning data (i.e., records of license allocation information) is accumulated, the more accurately the score can be calculated.
[0107] In the above, the scores of the candidate licenses to be assigned are calculated so that the scores of licenses used by other users who are using licenses similar to those of the user of the information device 30 in which the software to be assigned is installed are increased. However, this is not limited to this. For example, if the license type is a "device license," the score of a license applied to another information device 30 to which a license similar to that of the information device 30 in which the software to be assigned is installed is applied may be calculated.
[0108] Score calculation method 3: Item-based collaborative filtering As a third score calculation method, a case where the score of each allocation license candidate is calculated by item-based collaborative filtering will be described. In this case, the score calculation unit 106 calculates the score of the allocation license candidate for each license so that the score of the license that is likely to be allocated together is high.
[0109] Specifically, for example, as shown in Fig. 14, users are "U1" to "U9", licenses are "L1" to "L9", and licenses used by users are represented by "◯". Also, the user of the information device 30 in which the allocation target software is installed is "U9".
[0110] For example, in the example shown in Fig. 14, user "U1" is using licenses "L1", "L4", and "L7". Similarly, user "U2" is using licenses "L2", "L6", and "L8". The same is true for other users.
[0111] At this time, the score calculation unit 106 calculates the degree of co-occurrence between the licenses to calculate a co-occurrence matrix. For example, the users who use both licenses "L1" and "L4" are "U1", "U3", "U4", "U7", and "U9", so the degree of co-occurrence between licenses "L1" and "L4" is "5". For example, the user who uses both licenses "L1" and "L6" is "U8", so the degree of co-occurrence between licenses "L1" and "L6" is "1". By calculating the degree of co-occurrence between each license in this way, a co-occurrence matrix is calculated in which the elements are the degrees of co-occurrence between licenses, as shown in FIG. 14. In the co-occurrence matrix shown in FIG. 14, elements with a value of 0 are represented by blanks.
[0112] When calculating a score for a single license, the score calculation unit 106 calculates the total degree of co-occurrence with other licenses as the score. For example, in the example shown in Fig. 14, the score of license "L2" is "4".
[0113] In addition, when calculating the score by multiplying the license used by the user "U9" of the information device 30 in which the software to be allocated is installed, the score calculation unit 106 sets the sum of the co-occurrence with the license used by the user as the score of the other license. For example, in the example shown in FIG. 14, the user "U9" uses licenses "L1" and "L4". Therefore, the sum of the co-occurrence with the license "L1" and the co-occurrence with the license "L4" is set as the score of the relevant license. Specifically, the score of the license "L6" is "1", the score of the license "L7" is "6", the score of the license "L8" is "2", and the score of the license "L9" is "1". Since the licenses "L1" and "L4" are already used by the user "U9", the scores may not be calculated.
[0114] When calculating scores using item-based collaborative filtering, unlike rule-based filtering, there is no need to define rules in advance, and the more learning data (i.e., records of license allocation information) is accumulated, the more accurately the score can be calculated.
[0115] In the above, the degree of co-occurrence between licenses used by users of information devices 30 in which the software to be assigned is installed is calculated. However, this is not limited to this. For example, if the license type is a "device license", the degree of co-occurrence between licenses applied to these information devices 30 may be calculated between the information devices 30.
[0116] Score calculation method 4: Extracting similar licenses using Word2Vec As a fourth score calculation method, a case where the score of each assigned license candidate is calculated using Word2Vec will be described. In this case, the score calculation unit 106 calculates the score of the assigned license candidate for each license so that the score of a license that is likely to be assigned together with the license is increased.
[0117] Specifically, for example, time-series data indicating a list of licenses applied to each information device 30 is prepared, and the score calculation unit 106 converts the time-series data into vector data in a vector space with the number of licenses as the number of dimensions using Word2Vec. Then, the score calculation unit 106 calculates the similarity (for example, the distance in the vector space) between the vector data corresponding to the information device 30 in which the software to be allocated is installed and the vector data corresponding to the information device 30 to which the candidate license to be allocated is applied, and sets the average value of these similarities as the score.
[0118] The score calculation method 1 to the score calculation method 4 may be appropriately combined and used depending on the situation. For example, when there is a small amount of learning data (i.e., records of license allocation information), the score calculation method 1 may be used, and after a certain amount of learning data has been accumulated, the score calculation method 2 to the score calculation method 4 may be used. When a plurality of score calculation methods are combined, for example, the average of the scores calculated in each score calculation may be calculated. When this average is calculated, for example, the scores calculated in each score calculation method may also be presented to the user.
[0119] The present invention is not limited to the above-described specifically disclosed embodiment, and various modifications and variations are possible without departing from the scope of the claims. [Explanation of symbols]
[0120] 1. Asset Management System 10 Management device 20 Collection Device 30 Information equipment 101 Acquisition Department 102 Hardware Specifications 103 Software Specific Department 104 Judgment section 105 Alert notification section 106 Score Calculation Section 107 Candidate presentation section 108 Memory unit
Claims
1. A management device for managing licenses of software installed in a plurality of information devices, comprising: a first determination means for determining whether or not a license violation has occurred in software installed in the information device based on inventory information collected from the information device and license information stored in a storage unit; a second determination means for determining a type of the license violation when it is determined that a license violation has occurred in the software installed in the information device; a third determination means for determining whether or not there is a license that can be assigned to the software based on the license information when the type of the license violation determined by the second determination means is unauthorized use; a display means for displaying on a predetermined terminal, according to the type of license violation, either an alert screen for warning that a license violation has occurred in the software, or a presentation screen the presentation content of which is to display the license in a display mode according to an index value that indicates how appropriate it is to assign the license to the software; The display means includes: displaying the alert screen on the terminal when it is determined that the type of the license violation is a violation of a license agreement or when it is determined that the type of the license violation is the unauthorized use and that there is no license that can be assigned to the software; a management device that, when it is determined that the type of the license violation is the unauthorized use and that an assignable license exists for the software, causes the terminal to display the presentation screen.
2. A management device that manages licenses for software installed on multiple information devices, a first determination step of determining whether or not a license violation has occurred in software installed on the information device based on inventory information collected from the information device and license information stored in a storage unit; a second determination step of determining a type of the license violation when it is determined that a license violation has occurred in the software installed in the information device; a third determination step of determining whether or not there is a license that can be assigned to the software based on the license information when the type of the license violation determined in the second determination step is unauthorized use; a display step of displaying on a predetermined terminal, according to a type of the license violation, either an alert screen for warning that a license violation has occurred in the software, or a presentation screen the content of which is to display the license in a display mode according to an index value that indicates how appropriate it is to assign the license to the software; The display procedure includes: displaying the alert screen on the terminal when it is determined that the type of the license violation is a violation of a license agreement or when it is determined that the type of the license violation is the unauthorized use and that there is no license that can be assigned to the software; the management method, when it is determined that the type of the license violation is the unauthorized use and that there is an allocatable license for the software, displaying the presentation screen on the terminal.
3. A program causing a computer to function as the management device according to claim 1.
Citation Information
Patent Citations
Method for managing software license
JP2001005659A
Numerical controller and program for program license
JP2008234561A
Software license management system
JP2009080682A
Purchase software license automatic calculation system
JP2013109576A
Management device, method and program
JP2018084931A
