JP2016095748A - License consumption number counting system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a license consumption number counting system capable of correctly counting the number of consumed licenses in a virtual terminal system.SOLUTION: A license consumption number counting system 1 includes: a database 11 that records physical terminal data, virtual terminal data, and operation log data; and an arithmetic unit 12 that counts the number of consumed licenses of target software on the basis of those data pieces obtained from the database 11. The arithmetic unit 12 detects a first physical terminal that is a physical terminal where the target software is installed, on the basis of the physical terminal data; detects a second physical terminal that is a physical terminal that operates a virtual terminal where the target software is installed, on the basis of the virtual terminal data and operation log data; and counts the number of consumed licenses of the target software on the basis of the results of detection of the first physical terminal and second physical terminal.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a license consumption number counting system for counting the number of licenses consumed by software executed in a virtual terminal system that converts a physical terminal into a virtual terminal.

  In recent years, for the purpose of preventing information leakage and the like, a technique for virtualizing a physical terminal (for example, various electronic devices such as a stationary personal computer, a notebook personal computer, a tablet computer, and a smartphone) has been developed. Making a physical terminal virtual is to operate another virtual terminal (virtual terminal) on the physical terminal.

  However, the virtual terminal is realized (created) by a virtual terminal server to which the physical terminal is connected. Specifically, a physical terminal that is connected to a virtual terminal server and converted into a virtual terminal acquires and displays display screen data indicating a display screen of the virtual terminal realized by the virtual terminal server, and the virtual terminal input by the user Is transmitted to the virtual terminal server. At this time, all data processing in the virtual terminal is performed by the virtual terminal server, and only display screen data indicating the processing result is transmitted to the physical terminal. As a result, data handled by the virtual terminal is retained in the virtual terminal server and is not read out by the physical terminal, thereby preventing information leakage.

  In a virtual terminal system that converts a physical terminal into a virtual terminal as described above, when software is executed on the virtual terminal, it is the virtual terminal server that processes the data, but it benefits from the execution of the software. Is a physical terminal converted into a virtual terminal. For this reason, in the virtual terminal system, a physical terminal converted into a virtual terminal instead of a virtual terminal server is regarded as a substantial software execution entity.

  For this reason, if the license of software executed on the virtual terminal is a device license set for the terminal, as many licenses are required as the number of physical terminals that operate the virtual terminal in principle. .

  By the way, in a virtual terminal system, software is executed on a virtual terminal that is an ideal entity, so that management of software licenses becomes difficult. Therefore, Patent Document 1 proposes a license check system for managing a license of software executed on a virtual terminal.

  The license check system proposed in Patent Document 1 is based on a software license system (software unit, version unit, edition unit, etc., in which unit a license is required, a virtual terminal unit, and a virtual terminal CPU. (Central Processing Unit) units, virtual terminal server CPU units, virtual terminal server CPU core units, etc., which unit is required for the configuration of the virtual terminal and virtual terminal server, etc.) Using the method, the number of licenses consumed for software executed on the virtual terminal is counted. In addition, when the remaining number of licenses prepared in advance decreases, the license check system prevents the license from being exhausted by urging the administrator of the virtual terminal system to purchase additional licenses.

JP 2012-33096 A

  In the license check system proposed in Patent Literature 1, the number of consumed licenses of software executed on a virtual terminal (virtual terminal server) is counted based only on the virtual terminal (virtual terminal server). For this reason, there may be a discrepancy between the number of license consumptions counted by this license check system and the actual number of license consumptions, which is a problem.

  For example, it is assumed that one physical terminal in which certain software is installed and a license is set (consumed) operates one virtual terminal and the software is executed on the virtual terminal (first case). To do.

  In the first case, since the execution of the software on the physical terminal is permitted, in principle, the execution of the software on the virtual terminal operated by the physical terminal is performed on the physical terminal. Within the set license range. Therefore, in the first case, only the license set (consumed) for the physical terminal is sufficient, and the setting of other licenses (especially, execution of the software on the virtual terminal) is unnecessary.

  However, in the license check system proposed in Patent Document 1, as long as software is executed on a virtual terminal (virtual terminal server) regardless of whether a software license is set for a physical terminal, It is determined that the license is consumed unconditionally. Therefore, in the first case, in the license check system proposed in Patent Document 1, it is determined that the license has been consumed for execution of the software on the virtual terminal, and the license check system erroneously counts (that is, This is a problem because the number of licenses consumed is larger than the actual number).

  Also, for example, when a plurality of physical terminals for which a license for a certain software is not set operate a common virtual terminal at different timings, and the software is executed on the virtual terminals at each timing (second) Case).

  In the second case, since execution of the software is not permitted in any physical terminal, in principle, when the software is executed on the virtual terminal operated by each physical terminal, each physical terminal It is necessary to set a plurality of licenses corresponding to the number of licenses (that is, a plurality of licenses are consumed).

  However, in the license check system proposed in Patent Document 1, one license is consumed when software is executed on one virtual terminal regardless of the number of physical terminals that operate the virtual terminal. It is determined that Therefore, in the second case, in the license check system proposed in Patent Document 1, the number of second and subsequent physical terminals that operate the virtual terminal is overlooked without being erroneously counted (that is, This is a problem because the number of licenses consumed is less than actual).

  Accordingly, an object of the present invention is to provide a license consumption number counting system capable of correctly counting the number of licenses consumed in a virtual terminal system.

  In order to achieve the above object, the present invention provides physical terminal data indicating software installed in a physical terminal, virtual terminal data indicating software installed in a virtual terminal, and the physical in which the virtual terminal is operated. A database for recording operation log data indicating a history of the terminal, and at least one of the physical terminal and the virtual terminal based on the physical terminal data, the virtual terminal data, and the operation log data acquired from the database. An operation unit that performs a device license consumption number counting operation that counts the number of licenses consumed by the target software that is one of the installed software, and when the device license consumption number counting operation is performed, The target software is based on the physical terminal data. A first physical terminal that is the physical terminal in which the target software is installed, and based on the virtual terminal data and the operation log data, the physical terminal that operates the virtual terminal in which the target software is installed Provided is a license consumption number counting system which detects a certain second physical terminal and counts the number of license consumptions of the target software based on detection results of the first physical terminal and the second physical terminal. To do.

  According to this license consumption number counting system, it is possible to correctly count the license consumption number of the target software by paying attention to the first physical terminal and the second physical terminal that are the entities that consume the license of the target software. Become.

  In the license consumption number counting system having the above characteristics, when the device license consumption number counting operation is performed, the calculation unit is configured to count the number of physical terminals included in the union of the first physical terminal and the second physical terminal. Is preferably counted as the first consumption number of the license of the target software.

  According to this license consumption number counting system, it is possible to prevent the first physical terminal and the second physical terminal from being counted repeatedly when counting the number of consumed licenses of the target software.

  Furthermore, in the license consumption number counting system having the above characteristics, when the operation log data indicates software executed in the virtual terminal, and the device license consumption number counting operation is performed, the calculation unit includes the operation Based on the log data, it is determined that the operated virtual terminal does not execute the target software from among the physical terminals that do not correspond to the first physical terminal but correspond to the second physical terminal A number obtained by detecting a third physical terminal which is a physical terminal and subtracting the number of the third physical terminals from the number of the physical terminals included in the union of the first physical terminal and the second physical terminal Is preferably counted as the second consumption number of the license of the target software.

  According to this license consumption number counting system, when counting the number of consumptions of the license of the target software, the physical terminal that cannot be said to consume the license because the target software is not executed substantially or absolutely It becomes possible to exclude the 3rd physical terminal which is.

  Furthermore, in the license consumption number counting system having the above characteristics, the operation log data indicates an execution time for each software executed on the virtual terminal, and the calculation unit that performs the device license consumption number counting operation includes: If the execution time of the target software executed by the virtual terminal is equal to or shorter than a predetermined time, it is preferable to determine that the target software is not executed.

  According to this license consumption number counting system, it is possible to easily determine whether or not the target software is executed (applicability of the third physical terminal).

  Furthermore, in the license consumption number counting system of the above feature, the database is set for any of a plurality of setting target types including a terminal, in which a license of software installed in at least one of the physical terminal and the virtual terminal is set. Software data indicating whether or not, the calculation unit, based on the software data acquired from the database, when detecting that the setting target type of the license of the target software is a terminal, It is preferable to perform the device license consumption number counting operation.

  According to the license consumption number counting system, it is possible to count the number of license consumptions of the target software by an appropriate method according to the target setting type (especially the terminal) of the target software.

  In the license consumption number counting system of the above feature, the physical terminal data indicates a user of the physical terminal, the virtual terminal data indicates a user of the virtual terminal, and the software data is The software license installed in at least one of the physical terminal and the virtual terminal is set for a plurality of setting target types including the user and the terminal, and the calculation The unit performs a user license consumption number counting operation when detecting that the setting target type of the license of the target software is a user based on the software data acquired from the database, and the user license consumption number When performing the counting operation, the calculation unit is configured to transmit the physical terminal data. A first user who is a user of the physical terminal in which the target software is installed is detected, and a user of the virtual terminal in which the target software is installed is detected based on the virtual terminal data. Preferably, two users are detected, and the number of users included in the union of the first user and the second user is counted as the third consumption number of the license of the target software.

  According to the license consumption number counting system, when the target setting type of the license of the target software is a user, the target software is focused on the first user and the second user who consume the license of the target software. It is possible to correctly count the number of licenses consumed. Furthermore, when counting the number of licenses consumed for the target software, it is possible to prevent the first user and the second user from being counted repeatedly.

  According to the license consumption number counting system having the above characteristics, it is possible to correctly count the license consumption number of the target software by paying attention to the first physical terminal and the second physical terminal, which are the entities that consume the license of the target software. It becomes possible. Therefore, it is possible to correctly count the number of licenses consumed in the virtual terminal system.

The block diagram shown about an example of the structure of the virtual terminal system to which the license consumption number counting system which concerns on embodiment of this invention is applied. The figure shown about an example of the display screen of a physical terminal at the time of making a physical terminal into a virtual terminal. The block diagram shown about an example of the structure of the license consumption number counting system which concerns on embodiment of this invention. The block diagram which showed notionally the example of the physical terminal and the user of a virtual terminal, the relationship between a physical terminal and a virtual terminal, and the software installed in each of a physical terminal and a virtual terminal in a virtual terminal system. The figure shown about an example of physical terminal data. The figure shown about an example of virtual terminal data. The figure shown about an example of software data. The figure shown about an example of operation log data. FIG. 4 is a flowchart illustrating an example of a method for counting the number of software licenses consumed by the arithmetic unit in FIG. 3. FIG. It is a conceptual diagram of the method of counting the 1st consumption number of the license of object software. It is a conceptual diagram of the method of counting the 2nd consumption number of the license of object software. It is a conceptual diagram of the method of counting the 3rd consumption number of the license of object software.

<< Virtual terminal system >>
Before describing a license consumption number counting system according to an embodiment of the present invention, an outline of a virtual terminal system to which a license consumption number counting system according to an embodiment of the present invention is applied will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of a configuration of a virtual terminal system to which a license consumption number counting system according to an embodiment of the present invention is applied. FIG. 2 is a diagram illustrating an example of a display screen of the physical terminal when the physical terminal is converted into a virtual terminal.

  As shown in FIG. 1, the virtual terminal system S includes a physical terminal PM and a virtual terminal server PS. In FIG. 1, only one physical terminal PM is shown for simplification of illustration, but a plurality of physical terminals PM can be connected to the virtual terminal server PS.

  The physical terminal PM is, for example, a stationary personal computer, a notebook personal computer, a tablet computer, a smartphone, or the like, and is a computer mainly configured for an individual user. On the other hand, the virtual terminal server PS is, for example, a stationary computer having a higher processing capacity than the physical terminal PM and the like, and is a computer mainly configured for a server.

  Further, at least a part of the physical terminal PM is converted into a virtual terminal by communicating with the virtual terminal server PS through a network capable of bidirectional data transmission / reception represented by a LAN (Local Area Network). To do. Here, a state in which a part of the physical terminal PM is converted into a virtual terminal means, for example, that the physical terminal PM connected to the virtual terminal server PS not only operates as a virtual terminal but also has a unique operation as the physical terminal PM. If you get it. On the other hand, the state in which all physical terminals PM are virtual terminals means that, for example, the physical terminal PM connected to the virtual terminal server PS operates only as a virtual terminal and does not perform a specific operation as the physical terminal PM. State. FIG. 2 shows a state in which a part of the physical terminal PM is converted into a virtual terminal.

  As shown in FIG. 2, when a part of the physical terminal PM becomes a virtual terminal, a part of the display screen PD of the physical terminal PM becomes a virtual terminal display screen area VA that is an area representing the display screen of the virtual terminal. The virtual terminal display screen area VA is displayed when the physical terminal PM performs display processing of virtual terminal display screen data transmitted from the virtual terminal server PS. Note that when all of the physical terminals PM become virtual terminals, for example, the entire display screen PD of the physical terminal PM becomes the virtual terminal display screen area VA.

  When an operation is performed on the virtual terminal display screen area VA in a state where the display screen PD of the physical terminal PM as shown in FIG. 2 is displayed, the operation is converted into a virtual terminal in the physical terminal PM. Received as an operation on the physical terminal PM (hereinafter referred to as “virtual terminal target operation”). Then, as illustrated in FIG. 1, the physical terminal PM generates virtual terminal operation data indicating the operation content of the virtual terminal target operation, and transmits the virtual terminal operation data to the virtual terminal server PS.

  The virtual terminal operation data is, for example, data indicating an operation position (for example, coordinate position in the display screen VA of the virtual terminal) and an action (for example, touch or click) of a pointing device such as a touch panel or a mouse, or a keyboard press. This is simple data indicating only the input content to the input device, such as data indicating a key.

  Based on the virtual terminal operation data transmitted from the physical terminal PM, the virtual terminal server PS performs actual execution processing of application software that is apparently executed by the virtual terminal operating on the physical terminal PM. Then, the virtual terminal server PS generates virtual terminal display screen data indicating a display screen (virtual terminal display screen area VA) reflecting the processing result, and transmits the virtual terminal display screen data to the physical terminal PM.

  As described above, in the virtual terminal system S, the physical terminal PM that has been turned into a virtual terminal functions as an input device for the virtual terminal server PS and a display device for displaying the processing result of data in the virtual terminal server PS. That is, data processing, temporary data storage, data recording, and the like are all performed by the virtual terminal server PS. This prevents data from being read and processed by the physical terminal PM, and no data remains in the physical terminal PM, thereby reducing the risk of information leakage through the physical terminal PM. It becomes possible.

<< License consumption counting system >>
<Overall configuration>
Next, an example of the configuration of the license consumption number counting system according to the embodiment of the present invention will be described with reference to the drawings. FIG. 3 is a block diagram showing an example of the configuration of the license consumption number counting system according to the embodiment of the present invention.

  As shown in FIG. 3, the license consumption number counting system 1 according to the embodiment of the present invention includes a database 11, a calculation unit 12, and an output unit 13. In FIG. 3, the license consumption number counting system 1 is illustrated as if it is a separate device from the virtual terminal server PS, but a part or all of the license consumption number counting system 1 is a virtual terminal server. It may constitute a part of the PS.

  The database 11 acquires and records operation log data transmitted by the virtual terminal server PS, and records software data, physical terminal data, and virtual terminal data necessary for the calculation of the calculation unit 12 (details of each data) Will be described later). For example, the database 11 is configured to include a recording device such as a hard disk or a semiconductor memory. In FIG. 3, it is illustrated as if all the above data is recorded in one database 11, but a part of the above data is recorded in another physically different recording device. You may comprise.

  The calculation unit 12 counts the number of licenses consumed by the software based on the operation log data, software data, physical terminal data, and virtual terminal data acquired from the database 11, and the license consumption number indicating the counted number. Generate and output data. For example, the calculation unit 12 includes a calculation device such as a CPU and a memory that temporarily stores data during calculation.

  The output unit 13 acquires the license consumption number data output from the calculation unit 12, and uses the numerical value indicated by the license consumption number data as an administrator (license consumption number) in charge of software purchase in an organization such as a company. To the user of the counting system 1). For example, the output unit 13 includes a display device that displays numerical values indicated by the license consumption number data as images such as characters and tables.

  Next, various data recorded in the database 11 will be described with reference to the drawings. FIG. 4 conceptually illustrates an example of a physical terminal and a user of the virtual terminal, a relationship between the physical terminal and the virtual terminal, and software installed in each of the physical terminal and the virtual terminal in the virtual terminal system. It is a block diagram. FIG. 5 is a diagram illustrating an example of physical terminal data. FIG. 6 is a diagram illustrating an example of virtual terminal data. FIG. 7 is a diagram illustrating an example of software data. FIG. 8 is a diagram illustrating an example of operation log data. 5 to 8 correspond to the users U1 to Uk, the physical terminals PM1 to PMm, the virtual terminals VM1 to VMn, and the software SW1 to SWx illustrated in FIG. 4 to 8, k and x are integers of 3 or more, and m and n are integers of 4 or more.

  In FIG. 4, the programs executed on the virtual terminal server PS are broadly shown functionally. Specifically, programs executed on the virtual terminal server PS are roughly classified into a hypervisor HV and virtual terminals (programs) VM1 to VMn. The hypervisor HV is a program that allocates the hardware resources of the virtual terminal server PS to the virtual terminals VM1 to VMn. The virtual terminals VM1 to VMn are programs including an OS (Operating System) and software executed on the OS.

  The user U1 illustrated in FIG. 4 uses two physical terminals PM1 and PM2, and operates a common virtual terminal VM1 in both of them. Specifically, for example, the user U1 operates the virtual terminal VM1 when using the physical terminal PM1 that is a stationary personal computer in a room, and uses the physical terminal PM2 that is a portable tablet computer in a workplace other than the room. In this case, the virtual terminal VM1 is also operated. In this case, since the user U1 can operate the common virtual terminal VM1 regardless of whether it is a living room or a work place, continuous work can be performed. In the virtual terminal system S, a plurality of physical terminals PM1 and PM2 are allowed to operate the common virtual terminal VM1 at different times, but they are prohibited in principle from operating simultaneously.

  On the other hand, the user U2 illustrated in FIG. 4 operates two different virtual terminals VM2 and VM3 using one physical terminal PM3, contrary to the user U1. Specifically, for example, when the user U2 uses the physical terminal PM3, which is a stationary personal computer, in the room, the user U2 operates the virtual terminal VM2 for general use purposes such as e-mail check and browser, and performs drawing and design. In the case of a special use purpose such as the virtual terminal VM3 is operated. In this case, since the user U2 can use the virtual terminals VM2 and VM3 optimized according to the purpose of use, the work efficiency can be improved.

  Further, the user Uk illustrated in FIG. 4 operates one virtual terminal VMn using one physical terminal PMm.

  In the virtual terminal system S, software is individually installed in each of the physical terminals PM1 to PMm and the virtual terminals VM1 to VMn. As illustrated in FIG. 4, the software SW1 is installed on the physical terminal PM1, the software installed on the physical terminal PM2 is not present, the software SW2 is installed on the physical terminal PM3, and the physical terminal PMm is installed. Is installed with software SW1. Further, as illustrated in FIG. 4, the software SW1 is installed in the virtual terminal VM1, the software SW1 and SW2 are installed in the virtual terminal VM2, and the software SWx is installed in the virtual terminal VM3. The software SW2 is installed in the virtual terminal VMn.

  The physical terminal data illustrated in FIG. 5 includes “physical terminal name” that is information for identifying the physical terminals PM1 to PMm and “user name” that is information for identifying the users U1 to Uk of the physical terminals PM1 to PMm. And “installed software” which is information for identifying the software SW1 to SWx installed in the physical terminals PM1 to PMm. In the physical terminal data, the correspondence (see FIG. 4) as described above is shown for the physical terminals PM1 to PMm, the users U1 to Uk, and the software SW1 to SWx.

  The virtual terminal data illustrated in FIG. 6 includes “virtual terminal name” that is information for identifying the virtual terminals VM1 to VMn and “user name” that is information for identifying the users U1 to Uk of the virtual terminals VM1 to VMn. And “installed software” that is information for identifying the software SW1 to SWx installed in the virtual terminals VM1 to VMn. In the virtual terminal data, the correspondence (see FIG. 4) as described above is shown for the virtual terminals VM1 to VMn, the users U1 to Uk, and the software SW1 to SWx.

  The physical terminal data and the virtual terminal data are acquired by, for example, an administrator connecting to the physical terminals PM1 to PMm and the virtual terminal server PS (virtual terminals VM1 to VMn), or acquiring physical information and virtual terminal data. So that information is automatically transmitted from the physical terminals PM1 to PMm and the virtual terminal server PS (virtual terminals VM1 to VMn) to the administrator's personal computer and the database 11 when the items indicated by It can be generated by any method such as configuring the system S or inputting information to a personal computer by an administrator who has received reports from the users U1 to Uk.

  The software data illustrated in FIG. 7 includes “software name” that is information for identifying software SW1 to SWx, and “license setting target type” that is information indicating the license setting target type of the software SW1 to SWx. ,It is included. In FIG. 7, in the above example (see FIG. 4), software SW1 and SW2 are device licenses (licenses set for terminals), and software SWx is a user license (licenses set for users). ).

  For example, when software SW1 to SWx is purchased, the software data can be generated by an arbitrary method such as an administrator inputting information on the software SW1 to SWx into a personal computer.

  The operation log data illustrated in FIG. 8 includes “physical terminal name” which is information for identifying the physical terminals PM1 to PMm and information for identifying the virtual terminals VM1 to VMn operated by the physical terminals PM1 to PMm. “Virtual terminal name”, “execution software” which is information for identifying software SW1 to SWx executed on the virtual terminals VM1 to VMn, and information indicating the date and time when the software SW1 to SWx is executed “ "Execution date and time" and "execution time" which is information indicating the time when the software SW1 to SWx is executed are included. In FIG. 8, only information on October 1, 2014 is illustrated, but information before and after this date (for example, information from the recording start date to the latest update date) is also included in the operation log data. included.

  The operation log data includes, for example, information related to the relationship between the physical terminals PM1 to PMm and the virtual terminals VM1 to VMn operated by the physical terminals PM1 to PMm (“physical terminal name” and “virtual terminal name” grasped by the hypervisor HV). Terminal name)) and information regarding the operations of the virtual terminals VM1 to VMn ("virtual terminal name", "execution software", "execution date", "execution time"), as grasped by the respective virtual terminals VM1 to VMn It is comprised by the combination of. In this case, the operation log data may be acquired by the database 11 by acquiring and combining each of the above information separately from the virtual terminal server PS. In this case, the virtual terminal server PS may acquire the operation log data from the database 11 by combining the above information and transmitting the combined information to the database 11.

<How to count the number of licenses consumed>
Next, a method for counting the number of consumed software licenses by the calculation unit 12 will be described with reference to the drawings. FIG. 9 is a flowchart showing an example of a method for counting the number of software licenses consumed by the arithmetic unit shown in FIG. Hereinafter, a specific description will be given using the examples shown in FIGS.

  As shown in FIG. 9, the computing unit 12 first selects target software that is a target for counting the number of licenses consumed (step # 1). At this time, the calculation unit 12 selects one of the software SW1 to SWx installed in the physical terminals PM1 to PMm and the virtual terminals VM1 to VMn as the target software. For example, in order to count the number of consumed licenses for all of the software SW1 to SWx, the arithmetic unit 12 selects the software SW1 to SWx one by one in order and sets them as target software. Further, for example, the calculation unit 12 selects specific software designated by the administrator and sets it as target software.

  Next, the computing unit 12 detects the license setting target type of the target software based on the software data acquired from the database 11 (step # 2). Here, when the setting target type of the license of the target software is a terminal (device) (step # 2, YES), a device license consumption number counting operation (steps # 3 to # 6) described below is performed. On the other hand, when the setting target type of the license of the target software is not a terminal but a user (step # 2, NO), a user license consumption number counting operation (steps # 7 and # 8) described later is performed.

  In this way, by detecting the setting target type of the target software license based on the software data, the license of the target software can be determined in an appropriate manner according to the setting target type of the target software license as described below. It becomes possible to count the number of consumption.

[Device license consumption count operation]
When performing the device license consumption number counting operation, first, the computing unit 12 detects a first physical terminal that is a physical terminal in which the target software is installed, based on physical terminal data acquired from the database 11. The computing unit 12 detects a virtual terminal in which the target software is installed based on the virtual terminal data acquired from the database 11 and operates the virtual terminal based on the operation log data acquired from the database 11. The second physical terminal, which is the physical terminal with the recorded history, is detected (step # 3).

  Then, the calculation unit 12 counts the number of physical terminals included in the union of the first physical terminal and the second physical terminal detected in step # 3, and uses the count result as the first consumption number of the license of the target software. (Step # 4). FIG. 10 shows a conceptual diagram of a method of counting the first consumption number of the license of the target software in Step # 4.

  Here, the method of counting the first consumption number of the license of the target software will be specifically described using the examples shown in FIGS. Here, the first consumption number of the license of the target software is counted only for the physical terminals PM1 to PM3 and PMm.

  When the target software is software SW1, the physical terminal PM1 corresponds to both the first physical terminal and the second physical terminal, the physical terminal PM2 corresponds to the second physical terminal, and the physical terminal PM3 corresponds to the second physical terminal. The physical terminal PMm corresponds to the first physical terminal. Therefore, the first consumption number of the license of the software SW1 that is the target software is 4.

  On the other hand, when the target software is software SW2, the physical terminal PM1 does not correspond to either the first physical terminal or the second physical terminal, and the physical terminal PM2 corresponds to either the first physical terminal or the second physical terminal. The physical terminal PM3 corresponds to both the first physical terminal and the second physical terminal, and the physical terminal PMm corresponds to the second physical terminal. Therefore, the first consumption number of the license of the software SW2 that is the target software is 2.

  In this way, when counting the number of consumed licenses of the target software by counting the number of physical terminals included in the union of the first physical terminal and the second physical terminal, the first physical terminal and the second physical terminal It is possible to prevent the terminals from being counted repeatedly.

  Next, the computing unit 12 determines that the operated virtual terminal is not executing the target software from among the physical terminals that do not correspond to the first physical terminal detected in step # 3 but correspond to the second physical terminal. The third physical terminal which is the physical terminal to be detected is detected (step # 5).

  At this time, based on the operation log data acquired from the database 11, the calculation unit 12 determines that the execution time of the target software (for example, the accumulated time of each execution time or the longest time during each execution time) is a predetermined time (for example, A virtual terminal (that is, a virtual terminal that cannot be evaluated that the target software has been executed substantially or absolutely) is less than or equal to a very short time such as 1 minute or 0 minutes indicating no execution). It is determined as a virtual terminal that has not been executed.

  As described above, by using the execution time of the target software included in the operation log data, it is possible to easily determine whether the target software is executed (applicability of the third physical terminal).

  Then, the computing unit 12 subtracts the number of the third physical terminals detected in step # 5 from the first consumption number of the license of the target software counted in step # 4, and uses the subtraction result for the license of the target software. The second consumption number is set (step # 6). FIG. 11 shows a conceptual diagram of a method of counting the second consumption number of the license of the target software in step # 6.

  Here, the method of counting the second consumption number of the license of the target software will be specifically described using the examples shown in FIGS. Here, for the physical terminals PM1 to PM3 and PMm only, the second consumption number of the license of the target software is counted, and the software SW1 has never been executed in the virtual terminal VM2 operated by the physical terminal PM3. And

  When the target software is software SW1, the first consumption number of the license of the target software is four as described above. However, since the software SW1 has never been executed in the virtual terminal VM2 operated by the physical terminal PM3, the calculation unit 12 determines that the physical terminal PM3 corresponds to the third physical terminal. Accordingly, the second consumption number of the license of the software SW1 that is the target software is 3, which is a number obtained by subtracting 1 from 4 that is the first consumption number.

  On the other hand, when the target software is software SW2, there is no physical terminal corresponding to the third physical terminal. Therefore, the second consumption number of the license of the software SW2 that is the target software is 2, which is the same number as the first consumption number described above.

  As described above, when the number of consumptions of the license of the target software is counted by subtracting the number of the third physical terminals from the first consumption number, the target software is not executed substantially or absolutely. It is possible to exclude the third physical terminal that cannot be said to be consuming.

  Then, when the above-described device license consumption number counting operation (steps # 3 to # 6) is performed, the arithmetic unit 12 generates license consumption number data indicating the first consumption number and the second consumption number of the license of the target software. To the output unit 13.

  As described above, the license consumption counting system 1 correctly counts the number of licenses consumed by the target software by paying attention to the first physical terminal and the second physical terminal that are the main consumers of the license for the target software. Is possible. Therefore, the number of licenses consumed in the virtual terminal system 1 can be counted correctly.

  When software that is not installed in the virtual terminal (software that is installed only in the physical terminal) is the target software, the second physical terminal becomes 0. Therefore, the first consumption number and the second consumption number of the license of the target software are both equal to the number of the first physical terminals.

  Further, the first consumption number and the second consumption number of the license of the target software, which are counted as described above, can be used by the administrator for various purposes.

  For example, when the first consumption number of the license of the target software corresponds to the actual consumption number of the license of the target software (that is, when the deduction of the license is not permitted for the third physical terminal), the administrator By confirming the first consumption number, it is possible to confirm the consumption number of the license of the target software. Furthermore, the administrator can grasp the number of licenses consumed for the target software by checking the second consumption number together with the first consumption number.

  For example, when the second consumption number of the license of the target software corresponds to the actual consumption number of the license in the target software (that is, when the deduction of the license is permitted for the third physical terminal), the administrator By confirming the second consumption number, it is possible to confirm the consumption number of the license of the target software. Furthermore, the administrator confirms the first consumption number together with the second consumption number, thereby increasing the number of consumptions of the license of the target software (first number) that can be increased only by the change in the presence or absence of execution of the target software in the virtual terminal. It is possible to grasp the number of physical terminals that may not correspond to 3 physical terminals).

[User license consumption count operation]
When performing the user license consumption number counting operation, first, the computing unit 12 detects a first user who is a user of a physical terminal in which the target software is installed, based on physical terminal data acquired from the database 11. Moreover, the calculating part 12 detects the 2nd user who is a user of the virtual terminal in which object software is installed based on the virtual terminal data acquired from the database 11 (step # 7).

  Then, the calculation unit 12 counts the number of users included in the union of the first user and the second user detected in step # 7, and uses the counted result as the third consumption number of the license of the target software ( Step # 8). FIG. 12 shows a conceptual diagram of a method of counting the third consumption number of the license of the target software in step # 8.

  Here, the method of counting the third consumption number of the license of the target software will be specifically described using the examples shown in FIGS. Here, the third consumption number of the license of the target software is counted only for the users U1, U2, and Uk.

  When the target software is software SWx, the user U1 does not correspond to either the first user or the second user, the user U2 corresponds to the second user, and the user Uk corresponds to either the first user or the second user. Also not applicable. Therefore, the third consumption number of the license of the software SWx that is the target software is 1.

  When the calculation unit 12 performs the above-described user license consumption number counting operation (steps # 7 and # 8), the calculation unit 12 generates license consumption number data indicating the third consumption number of the license of the target software, and outputs it to the output unit 13. Output.

  As described above, in the license consumption number counting system 1, when the setting target type of the license of the target software is a user, attention is paid to the first user and the second user who are the entities that consume the license of the target software. Thus, it is possible to correctly count the number of licenses consumed for the target software. Furthermore, when counting the number of licenses consumed for the target software, it is possible to prevent the first user and the second user from being counted repeatedly.

<< Deformation, etc. >>
In the license consumption number counting system 1 according to the above-described embodiment, the calculation unit 12 counts both the first consumption number and the second consumption number of the license of the target software when performing the device license consumption number counting operation. However, the calculation unit 12 may count only one of them (see steps # 3 to # 6 in FIG. 9). For example, the calculation unit 12 may count only one of the first consumption number and the second consumption number of the license of the target software that is selected in advance by the administrator.

  Further, in the license consumption number counting system 1 according to the above-described embodiment, the calculation unit 12 determines the license in a different manner depending on whether the target setting license type of the target software is a terminal (device) or a user. Although the number of consumptions is counted (see steps # 3 to # 6 and steps # 7 and # 8 in FIG. 9), the number of licenses consumed is determined by a method according to other setting target type (for example, server). You may comprise so that it may count.

  Further, in the license consumption number counting system 1 according to the above-described embodiment, the “user name” is included in the physical terminal data (see FIG. 5), but in addition to (or instead of) the physical terminals PM1 to PM1. A “virtual terminal name” that identifies the virtual terminals VM1 to VMn associated with the PMm that can be operated may be included. The same applies to virtual terminal data (see FIG. 6), in addition to (or instead of) “user name”, identifying physical terminals PM1 to PMm associated with the virtual terminals VM1 to VMn that can be operated. "Physical terminal name" may be included. However, it is preferable that “user name” is included in at least one of the physical terminal data and the virtual terminal data in order to perform the user license consumption number counting operation.

  Further, in the license consumption number counting system 1 according to the above-described embodiment, the physical terminal data and the virtual terminal data are described and illustrated as if they are separate data (see FIGS. 3, 5, and 6). However, these may be integrated data.

  In the virtual terminal system S, the physical terminals PM1 to PMm and the virtual terminals VM1 to VMn can vary. Therefore, it is preferable to periodically check and confirm the number of consumed software licenses.

  The present invention can be used in a license consumption number counting system for counting the number of licenses consumed by software executed in a virtual terminal system that converts a physical terminal into a virtual terminal.

1: License consumption number counting system 11: Database 12: Arithmetic unit 13: Output unit S: Virtual terminal system PM, PM1 to PMm: Physical terminal PS: Virtual terminal server HV: Hypervisor VM1-VMn: Virtual terminal SW1-SWx: Software U1-Uk: User

Claims (6)

Physical terminal data indicating software installed in the physical terminal, virtual terminal data indicating software installed in the virtual terminal, and operation log data indicating the history of the physical terminal that operated the virtual terminal, A database to record,
Consumption of the license of the target software that is one of the software installed in at least one of the physical terminal and the virtual terminal based on the physical terminal data, the virtual terminal data, and the operation log data acquired from the database An operation unit that performs a device license consumption number counting operation that counts the number,
When performing the device license consumption number counting operation, the calculation unit,
Based on the physical terminal data, a first physical terminal that is the physical terminal in which the target software is installed is detected;
Based on the virtual terminal data and the operation log data, a second physical terminal that is the physical terminal that operates the virtual terminal in which the target software is installed is detected.
A license consumption number counting system, wherein the license consumption number of the target software is counted based on detection results of the first physical terminal and the second physical terminal. When performing the device license consumption number counting operation, the calculation unit,
2. The license consumption according to claim 1, wherein the number of the physical terminals included in the union of the first physical terminal and the second physical terminal is counted as a first consumption number of the license of the target software. Number counting system. The operation log data indicates software executed on the virtual terminal;
When performing the device license consumption number counting operation, the calculation unit,
Based on the operation log data, it is determined that the operated virtual terminal does not execute the target software from among the physical terminals that do not correspond to the first physical terminal but correspond to the second physical terminal. Detecting a third physical terminal which is the physical terminal,
The number obtained by subtracting the number of the third physical terminals from the number of the physical terminals included in the union of the first physical terminal and the second physical terminal is the second consumption number of the license of the target software. The license consumption number counting system according to claim 1 or 2, wherein the license consumption number counting system according to claim 1 or 2 is counted. The operation log data indicates an execution time for each software executed on the virtual terminal,
The arithmetic unit that performs the device license consumption number counting operation determines that the target software is not executed if an execution time of the target software executed by the virtual terminal is equal to or shorter than a predetermined time. The license consumption number counting system according to claim 3. Software data indicating which of the plurality of setting target types including the terminal a software license installed in at least one of the physical terminal and the virtual terminal is set in the database, Record,
The operation unit performs the device license consumption number counting operation when detecting that the setting target type of the license of the target software is a terminal based on the software data acquired from the database. Item 5. The license consumption number counting system according to any one of Items 1 to 4. The physical terminal data indicates a user of the physical terminal;
The virtual terminal data indicates a user of the virtual terminal;
The software data indicates which of a plurality of setting target types including a user and a terminal a license of software installed in at least one of the physical terminal and the virtual terminal is set. Yes,
When the calculation unit detects that the setting target type of the license of the target software is a user based on the software data acquired from the database, the calculation unit performs a user license consumption number counting operation,
When performing the user license consumption number counting operation, the calculation unit,
Based on the physical terminal data, a first user who is a user of the physical terminal in which the target software is installed is detected,
Based on the virtual terminal data, a second user who is a user of the virtual terminal in which the target software is installed is detected,
6. The license consumption number counting system according to claim 5, wherein the number of users included in the union of the first user and the second user is counted as a third consumption number of the license of the target software.