JP6736862B2 - License management system, server, terminal, license management method, and program - Google Patents

Description

The present invention relates to a license management system, a server, a terminal, a license management method, and a program, and in particular, a license management system using a software identification tag (Software Identification (SWID) tag), a server, a terminal, a license management method, and Regarding the program.

In recent years, there has been an increasing interest in software asset management (SAM) in order to improve corporate value by complying with software licenses and enhance organization reliability. Further, as an international standard (international standard) regarding SAM, ISO (International Organization for Standardization)/IEC (International Electrotechnical Commission) 19770 has been released.

Patent Document 1 describes a license information management system for centrally managing software licenses. Specifically, Japanese Patent Laid-Open No. 2004-242242 discloses a method of unifying management of software license information and usage registration information that is different for each vendor by translating software license information and usage registration information into an XML (Extensible Markup Language) software definition format. Is disclosed.

JP 2012-108618 A

The entire disclosure contents of the above patent documents are incorporated herein by reference. The following analysis was made by the present inventor.

There are two tasks related to software management: "inventory" for investigating the software installation status on each terminal and "license management" for collecting licenses held by the organization and paying them out on demand. Broadly divided.

Regarding the former “inventory”, management software for inventory is provided. That is, a method is adopted in which an agent is installed in each terminal, installed software is searched by various companies for various methods, and the software is reported to the manager. However, according to such a method, there is a possibility that the detection accuracy may differ depending on the type of management software, and there is also a problem that the names of the detection software cannot be unified.

In order to solve such a problem, international standard ISO/IEC 19770-2 is defined. According to this standard, a "Software Identification (SWID) tag" file that describes the features of the software is copied to the terminal at the same time as the software is installed. As a result, it becomes possible to easily acquire the correct software feature information described by the software provider (vendor) by the management software. However, the software identification tag is stored in a readable format on the terminal only after the software is installed. Therefore, there is a problem that it is not suitable for the operation of installing or uninstalling software as needed.

For the latter "license management", a method is used in which the total number of installations and the total number of licenses held are compared by registering the license and the terminal to which the license is granted when the software is purchased, and registering the pair regularly. Has been. However, according to this method, it is difficult to flexibly deal with each terminal by issuing a license each time due to the complexity of management.

Furthermore, in order to simplify the management of the medium, a system configuration is adopted in which the installation package can be downloaded at the same time as the license is paid out. However, according to such a system configuration, when new software is deployed in the organization or when a patch is released, the load on the server that manages the license and contents temporarily increases, which makes operation and management difficult. There is.

From the above, in the related technology related to software asset management (SAM), there are the following demands, for example.
・When performing SAM, I want to complete the tasks that are roughly divided into inventory and license management with the former as much as possible.
・I want to flexibly install/uninstall software on each terminal that uses the software.
・I want to simplify the operation management by separating the content (or installation) management from the license management.

An object of the present invention is to provide a license management system, a server, a terminal, a license management method, and a program that enable license management of software regardless of the software installation status.

A license management system according to a first aspect of the present invention provides a terminal that uses software and first software identification information that grants a license for the software to the terminal before the software is installed on the terminal. A first server for issuing and issuing second software identification information for granting the software license to the terminal in association with the installation of the software on the terminal ; the first software identification information ; A second server that detects whether or not there is any fraud regarding the license of the software in the terminal using the second software identification information .

A server according to the second aspect of the present invention receives a license request for software from a terminal, and issues first software identification information in response to the license request before the software is installed in the terminal. Then, an issuance unit that issues second software identification information that grants a license for the software to the terminal when the software is installed in the terminal .

A terminal according to a third aspect of the present invention includes a transmitter that transmits a license request for software to a first server, and the first server in response to the license request before the software is installed in the terminal. A receiving unit that receives the first software identification information issued by, and receives the second software identification information that licenses the software to the terminal in association with the installation of the software on the terminal. I have it.

Server according to the fourth aspect of the present invention, the first software identification information issued by the other server before the software to the terminal in response to a license request from a terminal using a software is installed A receiving unit that receives from the terminal second software identification information that is received from the terminal and that licenses the software to the terminal when the software is installed in the terminal; and the first software identification information. And a detection unit for detecting whether or not there is any fraud regarding the license of the software in the terminal using the second software identification information .

In the license management method according to the fifth aspect of the present invention, the server issues first software identification information for granting a license for the software to the terminal before the software is installed in the terminal, and sends the terminal to the terminal. Using the step of issuing second software identification information for granting the license of the software to the terminal in association with the installation of the software , the first software identification information, and the second software identification information. Detecting the presence or absence of fraud regarding the license of the software in the terminal.

According to a sixth aspect of the present invention, there is provided a license management method in which a server receives a license request for software from a terminal, and the first software according to the license request before the software is installed in the terminal. Issuing identification information, and issuing second software identification information upon installation of the software on the terminal .

A license management method according to a seventh aspect of the present invention is such that a terminal transmits a license request for software to a first server, and according to the license request before the software is installed in the terminal. Receiving the first software identification information issued by the first server, the second software identification issued by the first server or the third server in association with the installation of the software on the terminal. Receiving information .

In the license management method according to the eighth aspect of the present invention, the server issues a first server issued by another server before the software is installed in the terminal in response to a license request from the terminal using the software. Receiving software identification information from the terminal and receiving second software identification information issued by another server from the terminal upon installation of the software on the terminal; and the first software identification. Information, and using the second software identification information , detecting the presence or absence of fraud regarding the license of the software in the terminal.

A program according to a ninth aspect of the present invention is a process of receiving a license request for software from a terminal, and issuing first software identification information in response to the license request before the software is installed in the terminal. A computer provided in the server is caused to execute the process of issuing the second software identification information in association with the installation of the software in the terminal .

A program according to a tenth aspect of the present invention includes a process of transmitting a license request for software to a first server, and a process of transmitting the license request to the first server according to the license request before the software is installed in a terminal. A process of receiving the issued first software identification information and receiving the second software identification information issued by the first server or the third server in association with the installation of the software on the terminal ; , Are executed by a computer provided in the terminal.

A program according to an eleventh aspect of the present invention, the first software identification information issued by the other server before the software to the terminal in response to a license request from a terminal using a software is installed A process of receiving from the terminal second software identification information received from the terminal and issued by another server in association with the installation of the software on the terminal; the first software identification information ; And a process for detecting whether or not there is any fraud regarding the license of the software in the terminal by using the software identification information of 1.

The program can also be provided as a program product recorded in a non-transitory computer-readable storage medium.

With the license management system, server, terminal, license management method, and program according to the present invention, software license management can be performed regardless of the software installation status.

It is a figure which illustrates the structure of the license management system which concerns on one Embodiment. It is a figure which illustrates the other structure of the license management system which concerns on one Embodiment. It is a block diagram which illustrates the composition of the server (for example, license server) in one embodiment. It is a block diagram which illustrates the composition of the terminal in one embodiment. It is a block diagram which illustrates the composition of the server (for example, inventory manager) in one embodiment. It is a block diagram which illustrates the composition of the license management system concerning a 1st embodiment. It is a figure which illustrates the structure of the software identification tag in 1st Embodiment. It is a flowchart which illustrates operation|movement of the process A (license server side) in 1st Embodiment. It is a flowchart which illustrates operation|movement of the process B (terminal side) in 1st Embodiment. It is a flowchart which illustrates operation|movement of the process C (stocktaking manager side) in 1st Embodiment.

First, an outline of one embodiment will be described. Note that the reference numerals in the drawings attached to this outline are merely examples for helping understanding, and are not intended to limit the present invention to the illustrated modes.

FIG. 1 is a diagram illustrating a configuration of a license management system according to an embodiment. Referring to FIG. 1, a license management system 2 includes a terminal 4 that uses software (for example, a user's PC (Personal Computer), a virtual machine (Virtual Machine), a virtual container (Virtual Container), or a mobile device (Mobile Device)). ) And a first server that issues first software identification information (eg, Software Identification (SWID) tag) that licenses the software to the terminal 4 before the software is installed on the terminal 4. 6 (for example, a license server) and a second server 8 (for example, an inventory manager) that detects whether or not there is an illegality regarding the software license in the terminal 4 by using the first software identification information. According to the management system 2, it is possible to perform software license management regardless of the software installation status, because the terminal is issued with the first software identification information for giving a license before the software installation. This is because it is possible to detect the presence or absence of fraud regarding the license in the terminal using such information.

FIG. 2 is a diagram illustrating another configuration of the license management system according to the embodiment. Referring to FIG. 2, the license management system 2 includes second software identification information (for example, a software identification tag provided by a software vendor) that grants a software license to the terminal 4 as the software is installed in the terminal 4. Is provided with a third server 10 (for example, a content server), and the second server 8 (for example, an inventory server) uses the first software identification information and the second software identification information sent from the terminal 4. , Detects the presence or absence of fraud regarding licenses. In this way, by making the software identification information for license provision and the software identification information assigned at the time of installation separate information, it becomes possible to separate the content (or installation) management and the license management.

Further, when the software is installed in the terminal 4, the terminal 4 adds a flag indicating that the first software identification information is auxiliary information to the first software identification information, and the software is uninstalled from the terminal 4. Then, the flag may be deleted from the first software identification information. At this time, the second server 8 (for example, the inventory server) gives priority to the content of the first software identification information to which the flag is added over the content of the second software identification information to determine whether the license is illegal. To detect. With such a configuration, the second server (for example, the inventory server) can determine that one of the two pieces of software identification information acquired from the terminal is auxiliary information and the other is master information. Therefore, even if a plurality of pieces of software identification information are issued for a single piece of software, no problem will occur.

FIG. 3 is a block diagram illustrating the configuration of the server 6 (for example, a license server) according to the embodiment. Referring to FIG. 3, the server 6 includes a reception unit 12 that receives a license request for software from the terminal 4 (see FIG. 1), and a first software identification according to the license request before the software is installed in the terminal 4. And an issuing unit for issuing information.

FIG. 4 is a block diagram illustrating the configuration of the terminal 4 (for example, a user's PC (Personal Computer)) in the embodiment. Referring to FIG. 4, the terminal 4 sends a license request for software to a first server 6 (eg, a license server, see FIG. 1) and a license request before the software is installed on the terminal 4. And a receiving unit 18 that receives the first software identification information issued by the first server 6 accordingly.

FIG. 5 is a block diagram illustrating the configuration of the server 8 (for example, the inventory manager) according to the embodiment. Referring to FIG. 5, the server 8 may be configured to execute another server 6 (for example, a license server, see FIG. 1) before software is installed in the terminal 4 in response to a license request from the terminal 4 (see FIG. 1) using the software. ) Receiving unit 22 for receiving the first software identification information issued by the terminal 4 from the terminal 4, a detection unit 24 for detecting the presence or absence of fraud regarding the license of the software in the terminal 4 using the first software identification information, Equipped with.

With the server 6 of FIG. 3, the terminal 4 of FIG. 4, and the server 8 of FIG. 5, software license management can be performed regardless of the software installation status. This is because the first software identification information for giving a license to the terminal before the software is installed is issued to the terminal, and it is possible to detect whether or not there is any fraud regarding the license in the terminal using this information. ..

<Embodiment 1>
Next, the license management system according to the first embodiment will be described in detail with reference to the drawings.

[Constitution]
FIG. 6 is a block diagram illustrating the configuration of the license management system 2 according to this embodiment. Referring to FIG. 6, the license management system 2 includes a terminal 27, a license server 28, a content server 30, and an inventory manager 32.

The terminal 27 is a device (for example, a user's PC (Personal Computer)) that executes software that requires a license. The terminal 27 includes a transmitter 16, a receiver 18, an editor 20, and a software identification tag storage directory 26.

The transmission unit 16 transmits a license request for software to the license server 28. The transmission unit 16 also transmits a software installation request to the content server 30.

The receiving unit 18 receives the first software identification tag (hereinafter referred to as “software identification tag T”) issued by the license server 28 in response to the license request before the software is installed in the terminal 27. Further, the receiving unit 18 receives a second software identification tag (hereinafter, referred to as “master software identification tag Tm”) issued by the content server 30 in response to the installation request and which grants a software license to the terminal 27. ..

The transmitting unit 16 transmits the software identification tag T to the inventory manager 32, which detects whether or not there is any fraud regarding the software license in the terminal 27 before the software is installed. On the other hand, the transmitting unit 16 transmits the software identification tag T and the master software identification tag Tm to the inventory manager 32 after the software is installed.

When the software is installed in the terminal 27, the editing unit 20 adds a flag indicating that the software identification tag T is auxiliary information to the software identification tag T, and when the software is uninstalled from the terminal 27, the software identification is performed. The flag is deleted from the tag T.

The software identification tag storage directory 26 is a directory provided on the file system of the terminal 27, for example, and stores the software identification tag T and the master software identification tag Tm.

The license server 28 centrally manages the licenses held by the organization for software management, and issues the licenses as a software identification tag T in response to a license request. The license server 28 includes a receiving unit 12 and an issuing unit 14.

The reception unit 12 receives a license request for software from the terminal 27. The issuing unit 14 issues the software identification tag T in response to the license request before the software is installed in the terminal 27.

The content server 30 discloses the software package in a downloadable form. In response to the installation request from the terminal 27, the content server 30 sends to the terminal 27 a master software identification tag Tm for giving a software license to the terminal 27 together with the content.

The inventory manager 32 collects a list of software installed in each terminal from a terminal 27 existing in an organization (for example, a company or one of its departments), and performs an inventory of software used in the organization. The inventory manager 32 includes a receiver 22 and a detector 24.

The receiving unit 22 receives from the terminal 27 the software identification tag T issued by the license server 28 before the software is installed in the terminal 27 in response to a license request from the terminal 27 that uses the software. In addition, the receiving unit 22 receives from the terminal 27, a master software identification tag Tm issued by the content server 30 to the terminal 27 in accordance with the installation of the software on the terminal 27, which gives the terminal 27 a software license.

Before the software is installed in the terminal 27, the detection unit 24 uses the software identification tag T to detect whether or not there is any illegality regarding the software license in the terminal 27. On the other hand, when the software is installed in the terminal 27, the detection unit 24 determines the content of the software identification tag T to which the flag indicating that the software identification tag T is auxiliary information is added by the terminal 27 as the master software identification tag. The presence or absence of fraud regarding the license is detected with priority over the content of Tm.

7A and 7B are diagrams exemplifying the configuration of the software identification tag T issued by the license server 28. Referring to FIGS. 7A and 7B, the software identification tag T includes the identifier of the terminal 27 (for example, pc123.aaa.com). At this time, the detection unit 24 of the stocktaking manager 32 refers to such an identifier to detect whether or not there is a license fraud. 7A and 7B respectively show the software identification tag T before and after a flag (for example, supplemental="true") indicating that the software identification tag T is auxiliary information is added.

[motion]
Next, the operation of the license management system 2 according to this embodiment will be described. The process related to license management includes three processes A to C shown in FIG. Here, the process A is a license acquisition process, the process B is a software package acquisition and installation process, and the process C is a process related to a report for software inventory.

Process A represents a process of receiving a license payout. The terminal 27 and the license server 28 are involved in the process A. As information, the license request and the software identification tag T are exchanged. First, a process A for acquiring a license from the terminal 27 that wants to execute software that requires a license is performed.

Process B represents a process of receiving the provision of the software installation package. The terminal 27 and the content server 30 are involved in the process B. As information, a package request and a software package are exchanged. Further, as a result of the software package installation process, the master software identification tag Tm is generated on the terminal 27.

In process C, inventory information is provided. The terminal 27 and the inventory manager 32 are involved in the process C. Further, as information, the software identification tag presentation request and the software identification tag T (or the software identification tag T and the master software identification tag Tm) are exchanged. If the process B is not installed, the software identification tag T is sent to the inventory manager 32. On the other hand, after the process B is installed, both the master software identification tag Tm and the software identification tag T are returned to the inventory manager 32.

According to the processes A to C, after the process A is executed, the software identification tag T returned in the process A is sent to the process C to the inventory manager 32, so that the software inventory is normally processed. Further, after the installation by the process B, the terminal 27 has acquired the master software identification tag Tm included in the package. At this time, for the process C, the software inventory is normally processed by sending the master software identification tag Tm together with the software identification tag T to the inventory manager 32. Therefore, in the process C, the operation assumed in the above international standard is realized.

Next, details of the process A (license acquisition) will be described with reference to the drawings. FIG. 8 is a flowchart illustrating the operation on the license server 28 side in the process A.

The terminal 27 issues a license request to the license server 28 by assigning the software name to be used and the name of the terminal 27. The license server 28 acquires the license request (step A1).

The license server 28 confirms whether or not the number of remaining licenses of the software requested for the license is sufficient (step A2). If the number of remaining licenses is insufficient (for example, the number of remaining licenses is exhausted), the license server 28 presents the fact that license allocation is not possible to the terminal 27, and ends the process.

If the number of remaining licenses is sufficient, the license server 28 reduces the number of remaining licenses of the software for which the license is requested by 1 (step A3).

The license server 28 creates the software identification tag T shown in FIG. 7A and returns it to the terminal 27 (step A4). As shown in FIG. 7A, in addition to the essential information defined by the international standard, the software identification tag T has download source information of the software package shown in bold letters (http:/ in FIG. 7A). /aaa.com/content/Software.zip) and the name of the terminal 27 ("pc123.aaa.com" in FIG. 7A) are stored.

When the terminal 27 cancels the license, the terminal 27 deletes the software identification tag T and notifies the license server 28 to that effect. Upon receiving this notification, the license server 28 increases the number of remaining licenses of the corresponding software by 1 (step A5).

Next, details of the process B (software package acquisition and installation) will be described with reference to the drawings. FIG. 9 is a flowchart illustrating an operation on the terminal 27 side in the process B.

The terminal 27 searches the software identification tag storage directory 26 for the software identification tag T of the software (step B1).

The terminal 27 acquires from the Link attribute of the software identification tag T (see FIG. 7A) the rel attribute is "installationmedia" and the href attribute is defined (step B2).

The terminal 27 connects the value of the href attribute to the content server 30 using a protocol such as HTTP (Hypertext Transfer Protocol) or FTP (File Transfer Protocol) according to the schema, and downloads the defined file (that is, software package) ( Step B3).

The file downloaded in step B3 is executed as an installer (step B4).

As a part of the installation procedure, the master software identification tag Tm included in the software package is copied to the software identification tag storage directory 26 (step B5).

At this point, there are two primary software identification tags for the software. In order to eliminate such a state, the editing unit 20 changes the software identification tag T to the auxiliary software identification tag by editing the software identification tag T and setting the supplemental attribute to true (step B6). At this time, the software identification tag T shifts from the state shown in FIG. 7A to the state shown in FIG. 7B.

When the software is uninstalled, the master software identification Tm is deleted as part of the uninstall procedure. At this point, the Primary software identification tag of the software does not exist. Therefore, the editing unit 20 edits the software identification tag T and deletes the supplemental attribute to change it to the Primary tag (step B7). At this time, the software identification tag T shifts from the state of FIG. 7(b) to the state of FIG. 7(a).

Next, details of the process C (software inventory) will be described with reference to the drawings. In the process C, for example, a normal operation defined by ISO/IEC 19770-2 can be used. FIG. 10 is a flowchart illustrating an operation on the inventory manager 32 side in the process C.

The inventory manager 32 requests the terminal 27 to present the software identification tags corresponding to all the software installed in the terminal 27 (step C1).

The terminal 27 extracts the stored software identification tag from the software identification tag storage directory 26 and sends it to the inventory manager 32. With respect to the software before the execution of the installation in the process B, the software identification tag T is returned. On the other hand, for the software after the execution of the installation in the process B, the master software identification tag Tm is returned as basic information, and the software identification tag T is returned as auxiliary information. The receiving unit 22 of the inventory manager 32 receives the software identification tag T (or the software identification tag T and the master software identification tag Tm) sent from the terminal 27 (step C2).

The detection unit 24 of the inventory manager 32 confirms the content of the software identification tag T, and whether the installation destination information (deviceId attribute in the Evidence attribute of FIGS. 7A and 7B) matches the name of the terminal 27. Is confirmed (step C3). If they do not match, the detection unit 24 detects that the license is illegal and takes corrective action in the software asset management process. In addition, the detection unit 24 detects the supplementary information (supplemental is described) of the software identification tag T between the software identification tag T and the master software identification tag Tm with respect to the items described in the master software identification tag Tm. While giving priority to the described items (that is, based on the contents of the latter when a tag common to both tags is included), the contents of the tag are confirmed.

[effect]
The software identification tag adopted in the license management system of the present embodiment (for example, the software identification tag in the international standard ISO/IEC 19770-2) has an optional attribute along with the vendor name, software name, version number, etc. The device information and the download source of the package can be entered. In addition, in the present embodiment, with respect to software defined to be commonly used in organizations, the license server holds the number of licenses held for each software and information necessary for creating a software identification tag. When each terminal needs the software, it requests the license of the software from the license server. When the unpaid license remains, the license server creates a software identification tag in which the requesting terminal name is embedded and returns it to each terminal. Each terminal stores the returned software identification tag in the software identification tag storage directory defined by the standard.

According to this configuration, when the inventory is performed before the software is installed on each terminal, the terminal already has the software identification tag issued by the license server. Therefore, even if the actual installation has not been completed, it is possible to confirm that the user intends to use the software and has received the license payment. Further, by deleting the software identification tag from the terminal, the cancellation of the license payment can be solved by the user of the terminal 27 himself.

According to this embodiment, each terminal can acquire the package from the download source described in the software identification tag and install the package at an appropriate timing. In other words, downloading the package does not have to be the same as issuing the license. Further, it is possible to provide a server (for example, a content server) different from the license server and use the separately provided server as the download source. As a result, the load on the license server can be reduced.

After the software is installed in each terminal, the software identification tag (master software identification tag) provided by the software vendor is stored in the software identification tag storage directory defined in the standard. At this time, a supplemental attribute is added to the software identification tag sent from the license server to clearly indicate that the software identification tag is supplementary information for the master software identification tag. As a result, the terminal continues to hold information indicating that the installation destination permitted by the license server is the terminal. On the other hand, at the time of uninstalling the software, after the master software identification tag is deleted together with the software, the supplemental attribute is deleted from the software identification tag and kept in the terminal. This makes it possible to indicate that the license is continuously held in the terminal because the uninstall is temporary and may be used again as needed.

According to the license management system of the present embodiment, since a software inventory is originally taken, the license is granted by using the software identification tag of the international standard ISO/IEC 19770-2 which is defined so that the features of the software can be structurally described. It is possible to present the situation. Furthermore, according to the present embodiment, it becomes possible to present the license allocation status even before the software is installed.

Further, according to this embodiment, the software inventory software can be used as it is in the license management. This is because it is possible to give the license payout information to each terminal to the software identification tag used in software inventory.

Furthermore, according to the present embodiment, the license server can be dedicated to license management, the load on the license server can be reduced, and the license server can be easily managed. This is because the package download timing and the license payout timing can be set separately, and the package download server can be provided separately from the license server.

<Modification>
Various modifications can be made to the license management system according to the above embodiment. As an example, assuming that the terminal 27 of FIG. 6 is discarded, the following functions may be added.

When the terminal 27 is abandoned while holding the license without notifying the license server 28 from the terminal 27, the number of licenses issued by the license server 28 and the license in use which the inventory manager 32 grasps by the inventory operation There is a risk that the numbers will not match (ie the latter will be less).

Therefore, the inventory manager 32, for example, periodically communicates with the license server 28, and when it detects that the number of licenses in use grasped by itself and the number of licenses paid out by the license server 28 do not match, for example, management You may make it notify that person's terminal (not shown). The administrator investigates the cause of the above situation based on the notification. In this way, even if the terminal is discarded, the software license can be properly managed.

In the present invention, the following modes are possible.
[Form 1]
This is as in the license management system according to the first aspect.
[Form 2]
A terminal that uses software,
A first server that issues first software identification information that licenses the software to the terminal before the software is installed on the terminal;
A third server that issues second software identification information that licenses the software to the terminal when the software is installed on the terminal,
The second server detects the presence or absence of fraud, using the first software identification information and the second software identification information sent from the terminal,
A license management system according to mode 1.
[Form 3]
When the software is installed in the terminal, the terminal adds a flag indicating that the first software identification information is auxiliary information to the first software identification information, and the terminal deletes the software. When installed, deletes the flag from the first software identification information,
A license management system according to mode 2.
[Form 4]
The second server prioritizes the content of the first software identification information added with the flag over the content of the second software identification information to detect the presence or absence of the injustice.
A license management system according to mode 3.
[Form 5]
The first software identification information includes an identifier of the terminal,
The second server refers to the identifier to detect the presence or absence of the fraud,
The license management system according to any one of modes 1 to 4.
[Form 6]
This is the same as the server according to the second aspect.
[Form 7]
This is the same as the terminal according to the third aspect.
[Form 8]
The transmission unit transmits the first software identification information to a second server that detects whether or not there is an illegality regarding the license of the software in the terminal.
A terminal according to form 7.
[Form 9]
The transmission unit transmits an installation request for the software to a third server,
The receiving unit receives second software identification information issued by the third server in response to the installation request, which grants the license of the software to the terminal,
The transmission unit transmits the first software identification information and the second software identification information to the second server,
A terminal according to form 8.
[Form 10]
When the software is installed in the terminal, the terminal adds a flag indicating that the first software identification information is auxiliary information to the first software identification information, and the terminal deletes the software. An installation unit that, when installed, deletes the flag from the first software identification information,
A terminal according to form 9.
[Form 11]
This is the same as the server according to the fourth aspect.
[Form 12]
The receiving unit receives, from the terminal, second software identification information that is issued from another server to the terminal in association with the installation of the software on the terminal and that grants the license of the software to the terminal.
A server according to mode 11.
[Mode 13]
When the software is installed in the terminal, the detection unit detects the content of the first software identification information added by the terminal with a flag indicating that the first software identification information is auxiliary information. , Prioritizing the contents of the second software identification information to detect the presence or absence of the injustice,
A server according to mode 12.
[Form 14]
The first software identification information includes an identifier of the terminal,
The detection unit detects the presence or absence of the fraud by referring to the identifier,
14. The server according to any one of modes 11 to 13.
[Form 15]
This is as in the license management method according to the fifth aspect.
[Mode 16]
Issuing second software identification information that licenses the software to the terminal when the software is installed on the terminal;
A step of detecting the presence or absence of fraud using the first software identification information and the second software identification information.
A license management method according to mode 15.
[Form 17]
When the software is installed on the terminal, adding a flag indicating that the first software identification information is auxiliary information to the first software identification information;
Deleting the flag from the first software identification information when the software is uninstalled from the terminal.
A license management method according to mode 16.
[Form 18]
A step of detecting the presence or absence of the illegality by prioritizing the content of the first software identification information in which the flag is described with respect to the content of the second software identification information.
A license management method according to mode 17.
[Form 19]
The first software identification information includes an identifier of the terminal,
The presence or absence of fraud is detected using the identifier,
19. The license management method according to any one of modes 15 to 18.
[Form 20]
This is as in the license management method according to the sixth aspect.
[Form 21]
This is as in the license management method according to the seventh aspect.
[Form 22]
This is as in the license management method according to the eighth aspect.
[Form 23]
The program is according to the ninth aspect.
[Mode 24]
The program is according to the tenth aspect.
[Form 25]
The program is according to the eleventh aspect.

In addition, all the disclosure content of the said patent document shall be described by being quoted in this document. Modifications and adjustments of the exemplary embodiment are possible within the scope of the overall disclosure (including the claims) of the present invention and based on the basic technical concept of the invention. In addition, various combinations of various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, and the like) are possible or selected within the framework of the entire disclosure of the present invention. is there. That is, it goes without saying that the present invention includes various variations and modifications that can be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with regard to the numerical range described in this specification, any numerical value or small range included in the range should be construed as being specifically described even if not otherwise specified.

2 License management system 4 Terminals 6, 8, 10 Server 12 Reception unit 14 Issuing unit 16 Transmission unit 18 Reception unit 20 Editing unit 22 Reception unit 24 Detection unit 26 Software identification tag storage directory 27 Terminal 28 License server 30 Content server 32 Inventory manager Tm master software identification tag T software identification tag

Claims (20)

A terminal that uses software,
Before the software is installed in the terminal, the first software identification information for giving the license of the software to the terminal is issued, and the software is installed in the terminal in association with the installation of the software in the terminal. A first server that issues second software identification information that grants a license;
A second server that detects, by using the first software identification information and the second software identification information, whether the license of the software in the terminal is illegal or not.
A license management system characterized in that A terminal that uses software,
Before the software to the terminal is installed, and the first server that issues the first software identification information to license of the software to the terminal,
A third server that issues second software identification information that licenses the software to the terminal when the software is installed on the terminal,
The second server detects the presence/absence of fraud using the first software identification information and the second software identification information sent from the terminal,
A license management system characterized in that When the software is installed in the terminal, the terminal adds a flag indicating that the first software identification information is auxiliary information to the first software identification information, and the terminal deletes the software. When installed, deletes the flag from the first software identification information,
The license management system according to claim 2. The second server prioritizes the content of the first software identification information added with the flag over the content of the second software identification information to detect the presence or absence of the injustice.
The license management system according to claim 3. The first software identification information includes an identifier of the terminal,
The second server refers to the identifier to detect the presence or absence of the fraud,
The license management system according to claim 1. A reception unit that receives a license request for software from the terminal,
Before the software is installed in the terminal, the first software identification information is received in response to the license request, and the license of the software is given to the terminal with the installation of the software in the terminal. An issuing unit that issues second software identification information,
A server characterized by that. A transmitter for transmitting a license request for software to the first server;
Before the software is installed in the terminal, the first software identification information issued by the first server in response to the license request is received, and the terminal is accompanied by the installation of the software in the terminal. A receiving unit for receiving second software identification information for granting the software license to the.
A terminal characterized by that. The transmission unit transmits the first software identification information to a second server that detects whether or not there is an injustice regarding the license of the software in the terminal.
The terminal according to claim 7. The transmission unit transmits an installation request for the software to a third server,
The receiving unit receives second software identification information issued by the third server in response to the installation request, which grants the license of the software to the terminal,
The transmission unit transmits the first software identification information and the second software identification information to the second server,
The terminal according to claim 8. When the software is installed in the terminal, the terminal adds a flag indicating that the first software identification information is auxiliary information to the first software identification information, and the terminal deletes the software. An installation unit that, when installed, deletes the flag from the first software identification information,
The terminal according to claim 9. The first software identification information issued by another server before the software is installed in the terminal in response to a license request from the terminal using the software is received from the terminal, and the software of the software to the terminal is received. A receiving unit which receives from the terminal second software identification information for granting the software license to the terminal upon installation;
A detection unit configured to detect the presence or absence of fraud regarding the license of the software in the terminal using the first software identification information and the second software identification information.
A server characterized by that. The receiving unit receives, from the terminal, second software identification information that is issued from another server to the terminal in association with the installation of the software on the terminal and that grants the license of the software to the terminal.
The server according to claim 11. When the software is installed in the terminal, the detection unit detects the content of the first software identification information added by the terminal with a flag indicating that the first software identification information is auxiliary information. , Prioritizing the contents of the second software identification information to detect the presence or absence of the injustice,
The server according to claim 12. The first software identification information includes an identifier of the terminal,
The detection unit detects the presence or absence of the fraud by referring to the identifier,
The server according to any one of claims 11 to 13. The step of the server accepting a license request for software from the terminal,
Issuing first software identification information in response to the license request before the software is installed in the terminal, and issuing second software identification information in association with the installation of the software in the terminal And, including,
A license management method characterized by the above. The terminal sending a license request for the software to the first server;
Before the software is installed on the terminal, the first software identification information issued by the first server in response to the license request is received, and the software is installed on the terminal. Receiving the second software identification information issued by the first server or the third server.
A license management method characterized by the above. A server receives, from the terminal, first software identification information issued by another server before the software is installed on the terminal in response to a license request from the terminal using the software, Receiving second software identification information issued by another server from the terminal in association with the installation of the software,
Using the first software identification information and the second software identification information, detecting the presence or absence of fraud regarding the license of the software in the terminal.
A license management method characterized by the above. The process of receiving a license request for software from the terminal,
A process of issuing first software identification information in response to the license request before the software is installed in the terminal, and issuing second software identification information with the installation of the software in the terminal. And a computer provided on the server to execute,
A program characterized by that. A process of transmitting a license request for software to the first server,
Before the software is installed in the terminal, the first software identification information issued by the first server in response to the license request is received, and the first software identification information is installed in the terminal. A process of receiving the second software identification information issued by the first server or the third server, and causing a computer provided in the terminal to execute the process.
A program characterized by that. The first software identification information issued by another server before the software is installed in the terminal in response to a license request from the terminal using the software is received from the terminal, and the software of the software to the terminal is received. A process of receiving from the terminal the second software identification information issued by another server in association with the installation,
Causing a computer provided in a server to execute a process of detecting the presence or absence of fraud regarding the license of the software in the terminal using the first software identification information and the second software identification information.
A program characterized by that.

Images