JP2004303188A - Method and system for managing license - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method and a system for managing a license which can supply neither more nor less information even though none of corresponding license cannot be identified within the EXE file information installed. <P>SOLUTION: The system for managing the license comprises a client s1, a server s2 for managing the licenses, and a server s3 for collecting an event. The client s1 comprises a management unit s11 for managing machines possessed by a department which changes, adds, and deletes the computer information (possessing department user, etc.) possessed by the departments; a software management unit s12 with functions to add, change, and delete the software information (possessing department purchased prices, etc.) possessed by the departments; a calculating unit s13 for calculating neither more nor less license fees which displays a neither more nor less difference value between an ownership number for each license and a number for the licenses installed; and a software defining unit s14 with functions to add, change, and delete the information to define the software. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a license management system and method, and more particularly to a license management system and method for managing licenses related to ownership and use of software owned by a company, a government office, or another organization.

As a technique related to software license management, for example, a technique described in Patent Document 1 or the like is known. This conventional technology is used when one application is provided in different packages (for example, the same Microsoft Word is provided in Microsoft Office Standard and Professional versions) or when one package contains multiple applications. In such a case (Microsoft Office or the like), the license of the corresponding software is specified from the EXE file information installed in the machine or the character string of the registry.
JP 2001-222424 A

  In the above-described related art, in practice, it may not be possible to narrow down the installed software licenses to one from the EXE file information or the character string of the registry. For example, with the conventional technology described above, if you install Microsoft Office after installing Microsoft Word, it is possible to determine whether both Microsoft Word and Microsoft Office are installed or only Microsoft Office is installed Can not.

  In other words, the above-described prior art responds to the case where one application is provided in a different package or the case where one package includes a plurality of applications, based on the EXE file information installed in the machine. The software license to be used cannot be specified as one. For this reason, in the above-described conventional technology, since the information of the owned license and the installation license cannot be associated one-to-one, it is possible to accurately calculate the number of license excess / deficiency, which is the difference between the owned license and the installation license. Can not.

  In addition, in the case of Microsoft Office, etc., only one specific user is given a regular license and is permitted to use it. Unless it is used at the same time, it can be used on another computer, for example, a portable computer Rights (hereinafter referred to as secondary licenses). However, the above-mentioned prior art does not consider the license management in such a case, and cannot perform the management of the secondary license.

  Generally, when managing licenses, the number of licenses is compared with the number of installed licenses, the number of licenses is determined, and the number of licenses that are insufficient is additionally purchased. However, due to the existence of the secondary license as described above, it is not possible to calculate the correct number of licenses by using the difference between the number of licenses and the number of installed licenses.

  An object of the present invention has been made in view of the above points, and provides accurate license excess / deficiency information even if a single license corresponding to the EXE file information cannot be specified from installed EXE file information. To provide a license management system and method that enables more detailed license management and also manages a secondary license for a license whose license usage cannot be determined from installation information. is there.

  According to the present invention, the object is to provide a software license management system that manages software installation information and owned license information, in which software is licensed to be installed on a computer or licensed to a user. A means for allocating and registering each owned license to its use computer or user. If the required license cannot be identified as one from the EXE file information installed in the computer, Means for identifying the installed license from the information and calculating the excess or deficiency of the license.

  In addition, the object is to provide a software license management system that manages software installation information and owned license information, in order to manage a secondary license of the software, a secondary license definition table different from the software table in order to define the secondary license. This is achieved by providing a means for storing secondary license allocation information in a secondary machine allocation table different from the machine allocation table.

  Further, the object is to provide a software license management method for managing software installation information and owned license information, in which a license is permitted to be installed on a computer or a user is permitted to use software individually. If the required license cannot be identified from the EXE file information installed on the computer by allocating and registering the owned license of the user to the computer or user of the use destination, the license is installed from the information of the allocation registration. This is achieved by specifying the licenses that have been obtained and calculating the number of licenses.

  According to the present invention having the above-described means, as the number of license allocation registrations increases, the number of excess and deficiency of the owned software and the installed software can be accurately grasped, and the usage status of the license is grasped from the installation information. Even when there are licenses and secondary licenses that cannot be used, it is possible to register and refer to the use status of the owned software and the machines and users who use the software.

  According to the present invention, accurate license excess / deficiency information can be provided even when a single license corresponding to the EXE file information cannot be identified from installed EXE file information, and the license usage status can be determined by using the installation information. Even for licenses that cannot be determined from the license, more detailed license management can be performed. Further, according to the present invention, it is possible to total and display the number of license excess and deficiency in consideration of the number of used secondary licenses, and to improve the accuracy of the license excess and deficiency in consideration of the secondary license. Can be managed.

  Hereinafter, embodiments of a license management system and method according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram illustrating a system configuration of a license management system according to an embodiment of the present invention, and FIG. 2 is a diagram illustrating a configuration of various tables provided in a license management system server. 1 and 2, s1 is a client, s2 is a license management system server, s3 is an inventory collection server, s11 is an owned machine management unit, s12 is an owned software management unit, s13 is a license excess / deficiency totaling unit, and s14 is a software definition. Unit, s15 is a secondary license definition unit, s31 is an inventory database, s201 is a software table, s202 is a secondary license table, s203 is a owned software table, s204 is a user allocation table, s205 is a machine allocation table, s206 is a secondary machine allocation table, s207 is a computer table, s208 is an EXE file / software table, s209 is an EXE file table, s210 is an installed EXE file table, s2. 1 is a user table.

  As shown in FIG. 1, the license management system according to one embodiment of the present invention includes a client s1, a license management system server s2, and an inventory collection system server s3. The client s1 includes a possessed machine management unit s11 having a function for adding, changing, and deleting computer information (owned department, user, etc.) owned by the organization, and information on software (owned department) owned by the organization. , Acquisition price, etc.), a owned software management unit s12 having a function of performing addition, change, deletion, and list display, and a license having a function of displaying the number of owned, allocated, installed, and excess / deficiency for each license. An excess / deficiency totaling unit s13, a software defining unit s14 having a function of adding, changing, and deleting software definition information and displaying a list, and a function of adding, changing, deleting, and displaying a list of secondary license definition information. And a secondary license definition unit s15. In the above description, the software definition information defined by the software definition unit s14 includes software name, manufacturer, information on license allocation type (machine, user), and EXE file information (file name, file version, product version, etc.). The secondary license information defined by the secondary license definition unit s15 includes a secondary license name, a software ID, and a license use condition.

  The inventory collection system server s3 includes an inventory database s31. The inventory database s31 stores inventory information (hardware specifications, installed EXE file information) of computers connected on the network.

  The license management system server s2 is configured to include various tables as shown in FIG. 2. Next, these tables will be described with reference to FIG.

  The software table s201 is a table for storing software definition information, and includes a software ID, a software name, a maker, and a license assignment destination type as shown in FIG.

  The secondary license table s202 is a table for storing information on secondary licenses, and as shown in FIG. 2B, includes a secondary license ID, a secondary license name, a software ID, and license usage conditions.

  The owned software table s203 is a table for registering information for the data owned by the software table s201 for only the owned software, as shown in FIG. 2C, owned software ID, software ID, owned department, acquired Consists of price, acquisition date, and quantity.

  The user allocation table s204 is a table that stores the owned software, the users of the organization that is the destination of the use, and the allocation information, and as shown in FIG. 2D, includes the owned software ID and the allocation destination user ID.

  The machine assignment table s205 is a table for registering assignment information between owned software and a computer that is a destination of the owned software, and as shown in FIG. 2E, includes a owned software ID and an assigned computer ID.

  The secondary machine assignment table s206 is a table for registering assignment information between the secondary license of the owned software and the computer that is the destination of the use, and as shown in FIG. 2 (f), includes a owned software ID and an assigned computer ID. Is done.

  As shown in FIG. 2G, the computer table s207 includes a computer ID, a computer name, an owner signature, and a user ID.

  The EXE file / software table s208 is a table for registering the correspondence between the software and the EXE file in order to determine the presence / absence of software installation. As shown in FIG. Be composed.

  The EXE file table s209 is a table for storing EXE file information, and is composed of an EXE file ID, a file name, a file version, a product version, and a file size, as shown in FIG.

  The installed EXE file table s210 is a table for registering a correspondence between a computer and an EXE file installed in the computer, and includes a computer ID and an EXE file ID as shown in FIG.

  The user table s211 is a table for storing information on users of the organization, and includes a user ID and a name as shown in FIG.

  The management of the software license according to the embodiment of the present invention is performed by managing the various tables configured as described above in the license management system server s2 from the client s1. Next, processing by each functional unit in the client s1, processing by the license management system server s2, and processing by the inventory collection system server s3 will be described.

  The owned machine management unit s11 executes three functions of a owned machine list, addition of an owned machine, and deletion of an owned machine. The possessed machine list is a function of taking in the computer table s207 and displaying a list of computer information registered in the table. At this time, each row of the displayed list displays a check box for “Add Owned Machine”, “Change Owned Machine”, and “Delete Owned Machine”.

  “Add own machine” is a function to display the “machine information addition screen” when the “add own machine” button of the check box displayed on the owned machine list is clicked. On the machine information addition screen, input fields for a computer name, an owning department, and a user user ID, and a “register” button and a “cancel” button are displayed. The user inputs information of the computer to be newly added to each of the input fields described above. When the “register” button is clicked, the data entered by the user in each input field is registered in the computer table s207, and when the “cancel” button is clicked, the screen returns to the owned machine list screen.

  “Change owned machine” is a function for displaying a “machine information change screen” when the “change owned machine” button of the check box displayed on the owned machine list is clicked. On the machine information change screen, input fields for a computer name, an owning department, and a user user ID, and a “register” button and a “cancel” button are displayed. The data in the computer table s207 has been set in each input field, and the user performs the change by inputting the information of the computer to be changed into each of the above-described input fields. When the “register” button is clicked, the data entered by the user in each input field is registered in the computer table s207, and when the “cancel” button is clicked, the screen returns to the owned machine list screen.

  "Delete owned machine" displays the "Delete machine information screen" when the "Delete owned machine" button of the check box displayed in the owned machine list is clicked, and displays the data in the checked computer table. Is a function to delete.

  The owned software management unit s12 executes six functions: owned software list, addition of owned software, change of owned software, deletion of owned software, machine assignment of license, and user assignment of license.

  The “owned software list” is a function of creating and displaying a list of software information from information registered in the owned software table s203 and the software table s201. Items to be displayed are owned software ID, software name, owned department, acquisition price, acquisition date, quantity, license assignment destination type, and license assignment destination machine name (user ID). The displayed contents of the license assignment destination machine name (user ID) are changed depending on the contents of the license assignment destination type. That is, when the license assignment destination type is a machine, the license assignment destination machine name (user ID) is determined from the machine assignment table s205 and the computer table s207. When the license assignment destination type is a user, the license assignment destination machine name (user ID) is determined from the user assignment table s204 and the user table s211.

  To the left of each line in the “owned software list” displayed as described above, “add owned software”, “change owned software”, and “delete owned software” check boxes are displayed, and to the right , A button of “Change assignment destination” is displayed.

  “Add Owned Software” is a function that displays the screen for adding owned software when the “Add Owned Software” button is clicked in the “List of Owned Software”. For details of this function, see FIGS. 4 will be described later.

  “Change owned software” is a function for displaying a owned software change screen when a “change owned software” button is clicked in the “owned software list”. Details of this function are shown in FIG. The flow will be described later.

  "Delete owned software" displays a "owned software deletion screen" when the "Delete owned software" button of the check box displayed on the owned software list is clicked, and the checked owned software table s203 is displayed. This is the function to delete the data.

  “Allocate License to Machine” is a function to display the “Allocated Software” screen when the “Change Allocation” button is clicked on the row of “License Allocation Type =“ Machine ”in the list”. It is. The display here displays a list of computers registered in the computer table s207, and an “assign” button is displayed on the right of each row in the list. When the "assign" button is clicked, a license is assigned to the corresponding computer.

  "License user assignment" is a function to display the user assignment screen when the "Change assignment destination" button is clicked on the row of license assignment type = "User" in the list of "owned software list". It is. The display here displays a list of users registered in the user table s211. An "assign" button is displayed on the right of each row in the list. When the “assign” button is clicked, a license is assigned to the corresponding user.

  The license excess / deficiency totalizing unit s13 is a function of displaying a list described later with reference to FIG. The characteristic feature of the present invention in this list display is that the “number of allocations”, “the number of installations on allocated PCs”, and the “number of installations on unallocated PCs” are displayed.

  The software definition unit s14 has a function of displaying a software definition list that displays a list of software information (software name, maker, license assignment destination type) registered in the software table s201. On the left side of the display of the software definition list, check boxes for "add software", "change software", and "delete software" are displayed.

  “Add software definition” is a function that displays a software definition addition screen when the “Add software” button is clicked in the “Software definition list”. On the displayed software definition addition screen, input fields of a software name, a maker, and a license assignment destination type, a “register” button, and a “cancel” button are displayed. When the user inputs information of software to be added to each input field and clicks a “register” button, data set in each field is registered in the software table s201. When the “cancel” button is clicked, the screen returns to the software definition list display screen.

  “Change software definition” is a function for displaying a software definition change screen when a “change software” button is clicked in the “software definition list”. On the software definition change screen, input fields for a software name, a maker, and a license assignment destination type, a “register” button, and a “cancel” button are displayed. In each input field, software information registered in the software table s201 is set, and the user changes the information set in this input field. Then, when the “register” button is clicked, the data changed and set in each field is registered in the software table s201. When the “cancel” button is clicked, the screen returns to the software definition list display screen.

  "Delete software definition" displays the "Software definition deletion screen" when the "Delete software definition" button of the check box displayed in the "Software definition list" is clicked, and displays the checked software table. This is a function for deleting the data of s201.

  The license management system server s2 has a function of taking in inventory information collected by the inventory collection system server s3. This inventory information capturing function stores the installed EXE file information of the inventory collection system server s3 and the installed EXE file data of the license management system server s2 in the installed EXE file table s210.

  The inventory collection system server s3 has a function of collecting inventory information. This inventory information collection function collects installed EXE file information collected and transmitted by the agent program installed in the client s1, and stores this information in the inventory database s31.

  FIG. 3 is a flowchart for explaining the processing operation of the license management system according to the embodiment of the present invention, FIG. 4 is a flowchart for explaining the details of the processing in the processing steps c1 and c3 shown in FIG. 3, and FIG. Next, the processing procedure will be described with reference to these figures.

(1) Software definition registration processing step c1 is a function of registering a software maker and software name and registering a correspondence between software and an EXE file, and is executed by the software definition unit s14. As described above, when the client s1 accesses the software definition registration screen, the software definition registration screen is displayed. As described above, the administrator specifies the processing to be executed such as “add software definition” or “change software definition” and inputs the software name, manufacturer, and license assignment destination type (step F11). .

(2) After that, if the administrator clicks the “cancel” button, the processing of the processing step c1 is ended, and if the “register” button is clicked, an EXE file information registration screen is displayed. Here, input fields for a file name, a file version, a product version, and a file size, and a “register” button and a “cancel” button are displayed. The administrator inputs a file name, a file version, a product version, and a file size into the input fields and registers them as EXE file information from this display screen (steps F12 and F13).

(3) Finally, the software table s201, the EXE file table s209, and the EXE file / software table s208 are updated, and the processing of the processing step c1 ends (step F14).

(4) The process c2 for registering the owning machine is a process executed by the owning machine management unit s11. As described above, the computer name of the owning computer, the owning department, the user user ID, etc. This is a process for registering information.

(5) Owned software information registration processing step c3 is processing for registering owned software from the software registered in software definition registration processing step c1, and is executed by owned software management unit s12. This is the process to be performed. As described above, the "select" button and the "cancel" button are displayed together with the owned software list (step F21).

(6) If the "Cancel" button is clicked here, the processing here ends. However, if the "Select" button is clicked, the owned software selection screen can be accessed, and the owned software information input screen is displayed. The administrator inputs the information of the software to be registered into the respective input fields of the owning department, the acquisition price, the acquisition date, and the quantity. On this screen, a "register" button and a "cancel" button are also displayed (steps F22 and F23).

(7) If the “Cancel” button is clicked here, the processing here ends. However, if the “Registration” button is clicked, the owned software table s203 is updated (Steps F24 and F25).

(8) Software use assignment registration process step c4 is a process for registering the assignment of the possessed software, the computer to which the software is used, and the user. As a result, the machine assignment table and the user assignment table are updated.

(9) License audit information display processing step c5 is processing for displaying and providing license excess / deficiency information, and is executed by the license excess / deficiency totaling unit s13. The license excess / shortage information displayed here is displayed on the screen in a table as shown in FIG.

  In FIG. 5, the possession number L1 is the quantity of the target software owned by the organization, and the allocation number L2 is the quantity of the target software possession L1 that has been allocated for use to the machine or the user. The number of installations L3 to the assigned PC in the number of installations is such that the target software is installed in the machine to which the target software has been allocated, and any one of the EXE files associated with the installed EXE file table s209 is installed. Is the number of machines that are

  Also, the number of installations L4 to the unallocated PC among the number of installations is calculated from a machine in which any one of the EXE files associated with the target software by the EXE file / software table s208 is installed. This is the number of machines when software associated with the EXE file / software table s208 is excluded.

  The license excess / deficiency number L5 is obtained by subtracting the number of installations L3 to the assigned PC and the number of installations L4 to the unallocated PC from the number of possessions.

  The software described in the table shown in FIG. 5 is displayed when the number of possessions L1 is 1 or more or the number of installs L4 to an unallocated PC is 1 or more. For licenses for which the license usage cannot be determined from the installation information, the number of installations L3 to assigned PCs, the number of installations to unassigned PCs L4, and the number of licenses L5 are not displayed, as shown in Soft3 of NO3 in FIG. .

  According to the above-described embodiment of the present invention, even when the relationship between the EXE file and the software is many-to-many, the correspondence between the software and the EXE file is clarified by performing the software allocation registration. be able to. That is, as the allocated number increases, the number of unclear correspondences between the installed EXE file and the software decreases. This makes it possible to accurately determine the number of excess and deficiency of the owned software and the installed software.

  Then, for a license for which the use status cannot be grasped from the installation information, the administrator performs usage assignment registration, so that it is possible to estimate whether the license is excessive or not based on a comparison between the number of licenses and the number of assignments.

  FIG. 6 is a flowchart for explaining the processing operation in each functional unit in the client s1 when performing the secondary license management, and FIG. 7 is a view showing an example of an allocation destination machine list screen displayed in the processing of FIG. Yes, next, processing in each functional unit will be described.

Processing in Software Definition Unit s14 (1) The software definition unit s14 has a function of registering a software maker and software name, and registering a correspondence relationship between the software and the EXE file. Display the software definition registration screen. The administrator inputs the software name, manufacturer, and license assignment destination type on this screen (step H11).

(2) When the input in step H11 is completed, a screen for registering the EXE file information (file name, file version, product version, file size) is displayed. The table s201, the EXE file table s209, and the EXE file / software table s208 are updated (steps H12 and H13).

  The processing described above is basically the same as the processing in processing steps F11 to F14 in the software definition registration processing logic shown in FIG.

Processing in the secondary license definition unit s15 (1) The secondary license definition unit s15 has a function of registering a secondary license name, a corresponding software ID, and a license use condition. Then, a screen for inputting the ID of the corresponding software and the license use condition is displayed (step H14).

(2) When the administrator inputs necessary information from the screen displayed in step H14, the secondary license table s202 is updated (step H15).

Processing in Owned Machine Management Unit s11 and Owned Software Management Unit s12 Prior to the processing here, the owned machine management s11 registers information such as the computer name of the owning computer, the owning department, and the user ID of the user. The registered data is stored in the computer table s207. At the same time, the program automatically collects the installed EXE file information and stores it in the installed EXE file table s210.

(1) First, a possessed software management screen is displayed (a software table is displayed), and it is assumed that an “add” button is clicked on this display screen (steps H21 and H22). (2) The owned software management unit s12 has a function of registering owned software from the software registered in the software definition unit s14, accesses the owned software registration screen, and displays a software selection screen ( The information of the software table is displayed) (Step H23).

(3) When the administrator selects software to be registered on the software selection screen displayed in the process of step H23, an owned software information registration screen (H23) is displayed, and the administrator displays the owned department, acquisition price, acquisition date, When the quantity is input, the owned software table s203 is updated (steps H24 and H25).

  The processing up to this point is basically the same as the processing in processing steps F21 to F25 in the possessed software registration processing logic shown in FIG.

(4) At step H22, select the software to be allocated from the owned software management screen and click the "allocate" button to display the allocation destination machine list screen as shown in FIG. 7 (step H31).

(5) Clicking the “Change Destination” button on the destination machine list screen displayed in step H31 displays the destination machine selection screen. When the administrator selects a machine to which a license is to be allocated, the machine allocation table is displayed. It is updated (steps H32 to H34).

(6) When the “assignment” button G11 of secondary assignment on the assignment destination machine list screen as shown in FIG. 7 displayed in step H31 is clicked, a secondary machine selection screen is displayed (step H41).

(7) When a machine to be assigned is selected on the secondary machine selection screen, the license use conditions of the secondary license table s202 are displayed, and a dialog box is displayed as to whether or not the administrator agrees with the license use conditions, and “Accept”. Only when the button is clicked, the secondary machine assignment table s206 is updated (step H42).

  In the above description, the assignment of the secondary license is based on the premise that a regular license has been assigned. Further, when the “cancel” button G12 of the secondary assignment is clicked on the assignment destination machine list screen displayed in step H31, the secondary machine information is deleted from the secondary machine assignment table s206. Furthermore, when the “cancel” button G13 of the assigned machine is clicked on the assignment destination machine list screen, the machine assignment information is deleted from the machine assignment table s205, and the secondary machine assignment information is deleted from the secondary machine assignment table s206.

  Each processing according to the above-described embodiment of the present invention can be configured as a processing program, and the processing program is provided by being stored in a recording medium such as an HD, a DAT, an FD, an MO, a DVD-ROM, and a CD-ROM. And can be provided via a network.

  FIG. 8 is a diagram for explaining license audit information when secondary license management is performed, and this will be described next.

  The license excess / shortage totaling unit s13 displays license excess / shortage information on a screen as a table as shown in FIG. In FIG. 8, the owned number L1 is the number of target software owned by the organization. This does not include secondary licenses. The allocated number L2 is the number of allocated objects to the machine or the user among the owned number L1 of the target software. Only when a secondary license is allocated, the column of the number of allocations L2 is divided into upper and lower, and the upper column L21 displays the allocated number of regular licenses, and the lower column L22 displays the allocated number of secondary licenses.

  The number of installations L3 to the assigned PC is the number of machines in which at least one of the EXE files associated with the target software has been installed by the installed EXE file table s208 for the machine to which the target software has been allocated. is there. Only when the secondary license is assigned, the column of the number of installations L3 to the assigned PC is divided vertically, the upper column L31 indicates the number of installations of the regular license to the assigned PC, and the lower column L32 indicates the assignment of the secondary license. Displays the number of installations on the PC.

  The number of installations L4 to the unallocated PC is calculated by the EXE file / software table s206 from a machine in which any one of all the EXE files associated with the target software by the EXE file / software table s206 is installed. This is the number of machines when the associated software is excluded. The total L5 is the sum of the number of installations L3 (including the secondary license) on the allocated PC and the number of installations L4 on the unallocated PC.

  The license excess / deficiency number L6 is obtained by subtracting the number L31 of installations to the assigned PC of the regular license and the number L4 of installations to the unassigned PC from the number of possessions.

  It should be noted that the software is displayed if the possession number L1 is 1 or more or the number of installations L4 to an unallocated PC is 1 or more.

  By performing the processing as described above, according to the embodiment of the present invention, it is possible to display the license excess / deficiency total number in consideration of the number of used secondary licenses, and to improve the management accuracy of the license excess / deficiency number. Can be.

It is a block diagram showing the system configuration of the license management system by one embodiment of the present invention. FIG. 4 is a diagram for explaining the configuration of various tables provided in a license management system server. 5 is a flowchart illustrating a processing operation of the license management system according to the embodiment of the present invention. Processing logic 4 is a flowchart illustrating details of processing in processing steps c1 and c3 illustrated in FIG. 3. FIG. 9 is a diagram illustrating license audit information. 9 is a flowchart illustrating a processing operation in each functional unit in the client when performing secondary license management. FIG. 7 is a diagram illustrating an example of an allocation destination machine list screen displayed in the processing of FIG. 6. FIG. 9 is a diagram illustrating license audit information when secondary license management is performed.

Explanation of reference numerals

s1 client machine s11 owned machine management unit s12 owned software management unit s13 license excess / shortage aggregation unit s14 software definition unit s15 secondary license definition unit s2 license management server s201 software table s202 secondary license table s203 owned software table s204 user allocation table s205 machine allocation Table s206 Secondary machine allocation table s207 Computer table s208 EXE file / software table s209 EXE file table s210 Installed EXE file table s211 User table s3 Inventory collection server s31 Inventory database

Claims (10)

  In a software license management system that manages software installation information and owned license information, a means for assigning and registering each owned license to a destination computer for software that is licensed to be installed on a computer by a license. A license management system comprising:   A software license management system that manages software installation information and owned license information, comprising means for allocating and registering each owned license to a user who uses the software for which the user is licensed by the license. A license management system characterized by the following.   In a software license management system that manages software installation information and proprietary license information, a license is granted to be installed on a computer by a license, or a user who is licensed to use a software is licensed to use the proprietary license. If the necessary license cannot be identified from the EXE file information installed in the computer and the means for registering the assignment to the computer or the user, the installed license is identified from the assignment registration information and the license Means for calculating a shortage number.   In a software license management system for managing software installation information and owned license information, a means for storing secondary license definition information in a secondary license table separate from the software table is provided for managing a secondary license of software. A license management system characterized in that:   Means for storing, in a software license management system for managing software installation information and owned license information, secondary license allocation information in a secondary machine allocation table separate from the machine allocation table in order to manage the secondary license of the software A license management system comprising:   In a software license management system that manages software installation information and owned license information, in order to manage a secondary license of software, a screen for allocating a secondary license includes a screen for allocating a secondary license for each allocated machine. A license management system comprising means for canceling.   In a software license management system that manages software installation information and owned license information, in order to manage the secondary license of software, a screen for displaying the total number of licenses in the secondary A license management system characterized by comprising means for counting so as not to include licenses   In a software license management system that manages software installation information and owned license information, the number of secondary licenses allocated and the number of secondary licenses allocated are displayed on the screen for displaying the total number of secondary licenses to manage the secondary licenses of the software. A license management system, wherein the number of installations to the assigned PC is displayed in a column different from the total value of the regular license. In a software license management method that manages software installation information and owned license information, a license is granted to be installed on a computer by a license, or an individual licensed license is used for software licensed by a user. A license management method characterized by performing assignment registration to a destination computer or a user. In a software license management method that manages software installation information and owned license information, a license is permitted to be installed on a computer by a license, or an individual licensed license is used for software licensed by a user. If the required license cannot be identified from the EXE file information installed in the computer, the installed license is identified from the information of the allocation registration, and the license is registered. A license management method comprising calculating a shortage number.

Images