JP2006059163A - License management system, license management program and license management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a license management system, a license management program and a license management method for managing licenses of a number of software commodities for every customer, which can easily realize a license management while enabling inexpensive use of various kinds of software commodities used by a number of employees of a customer company for an optional period. <P>SOLUTION: This system comprises an agent provided on each user terminal of customers, which starts a software commodity based on a unique license key in the user terminal installed with this software commodity to enable the use thereof; and a management center managing, in response to a key issuing request from a user terminal of a customer, the number of issued licenses of the customer, and also forming and returning a unique license key to this user terminal to store it therein. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a license management system, a license management program, and a license management method for managing licenses of a large number of software products for each customer.

  Conventionally, software products have been purchased in batches for a number of licenses to be used by employees at customer companies, installed on each employee's terminal (PC) connected to the in-house LAN, and used individually.

  As mentioned above, since the customer company purchased the software product and installed it on the employee's computer, it is necessary to purchase the maximum number of licenses used by the employee. Each employee used a software product, but at this time, there was a problem that a lot of unused licenses were generated because the software products for the maximum number of purchased licenses were not used and was wasted. .

  In addition, there is a problem that a customer company that has purchased a software product is required to perform complicated management such as not to use more than the maximum number of purchased licenses.

  In order to solve these problems, the present invention provides a management server for managing a large number of user terminals and user terminals on the customer side, as well as managing the number of licenses of software products and issuing keys for a plurality of customers. For the purpose of providing a center and managing the issuance and revocation of unique keys for each user terminal or medium of each customer at the same time, and purchasing and distributing licenses for each software product at a low cost Yes.

  Accordingly, various types of software products used by a large number of employees of a customer company can be used at a low cost for an arbitrary period, and license management can be easily realized.

  The present invention provides a management server for managing a large number of user terminals and user terminals on the customer side, and also provides a management center for managing the number of licenses of software products and issuing keys to a plurality of customers. It is used by many employees of customer companies by managing the issuance and revocation of unique keys for each customer's user terminal or medium, as well as by purchasing and distributing licenses for each software product at a low cost and redistributing them. Various types of software products can be used at any cost for any period of time, and license management can be easily realized.

  The present invention provides a management server for managing a large number of user terminals and user terminals on the customer side, and also provides a management center for managing the number of licenses of software products and issuing keys to a plurality of customers. In addition to managing the issuance and revocation of unique keys for each customer's user terminal or medium, the licenses for each software product can be purchased in a batch and distributed and redistributed at low cost.

FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, a management server 1 is a server provided in a customer company. Here, the management server 1 manages a large number of user terminals 2 connected to a LAN in the customer company. The operating status recording means 12, the license management table 13, and the like are included.

  The license validity confirmation unit 11 confirms the validity of the license of the software product used by many user terminals 2 connected to the LAN in the customer company (confirms whether the license is valid for a predetermined period, for example, every month). (See FIGS. 2 to 6).

  The operation status recording means 12 confirms the operation status of the license of the software product used by many user terminals 2 connected to the LAN in the customer company (confirms the license usage status for a predetermined period, for example, every month). (See FIGS. 2 to 6).

  The license management table 13 registers and manages licenses for software used by a large number of user terminals 2 connected to a LAN in a customer company (see FIG. 6C).

  The user terminal 2 is a terminal (personal computer) connected to a LAN in a customer company, which installs a software product, activates it, and performs business processing, and is composed of an agent 21, an IC card adapter 22, and the like. It is.

  The agent 21 activates the software product based on the key (license key) when the installed software product is activated. Based on the key, the agent 21 encrypts the unique ID of the user terminal 2 (for example, the unique ID of the hard disk or the unique ID of the CPU) or the unique ID of the medium (for example, the IC card 23) connected to the user terminal 2 in the key. The software product is activated when the value matches the stored value (cannot be rewritten) (described later with reference to FIGS. 2 to 6).

  The IC card adapter 22 is for connecting a medium such as the IC card 23 and for reading an ID unique to the medium of the IC card 23. When the unique ID read from the IC card 23 matches the encrypted ID included in the key, the agent 21 can start the corresponding software product of the user terminal 2 to which the IC card 23 is connected. Is to do.

  The IC card 23 is an example of a medium that is connected to the user terminal 2 and is for reading a unique ID of the medium as described above. In addition to the IC card 23, the medium includes various external attachment devices such as an HD (hard disk device) and a communication adapter for communication.

  The management center 3 is connected to the management server 1 of the customer company via the network and further to the user terminal 2 to collectively manage licenses of software products. Here, the license issuing means 31 and the license management means 32 are used. The software transaction table 33, the customer management table 34, the license management table 35, the license key table 36, and the like.

  The license issuing means 31 issues a license key specific to the user terminal 2 of the customer company (see FIGS. 2 to 6).

  The license management means 32 collectively manages licenses (number of licenses) issued and revoked to the user terminal 2 of the customer company (see FIGS. 2 to 6).

  The software transaction table 33 is a table in which software products are contracted collectively from a manufacturer and the contents are registered (see (a) of FIG. 6).

  The customer management table 34 registers and manages software products contracted for each customer, contract period, opening key, medium key, maximum number of contracts, etc. (see FIG. 6B).

  The license management table 35 manages license information (user terminal name, contract type, contract period, operation record, etc.) for each user terminal of the customer (see (c) in FIG. 6).

  The license key table 36 registers and manages a unique license key issued to the user terminal 2 of the customer (see (d) in FIG. 6).

  Next, the operation of the configuration of FIG. 1 will be described in detail in the order of the flowcharts of FIGS. 2 to 5 with reference to the table of FIG. Here, the user terminal 2, the management server 1, and the management center 3 correspond to the user terminal 2, the management server 1, and the management center 3 of FIG. A manufacturer is a manufacturer (such as a company) that licenses software products.

FIG. 2 is a flowchart for explaining the operation of the present invention (part 1).
In FIG. 2, S1 places an order. This is because the management center 3 places an order for a batch license of software products from the manufacturer (for example, sends a contract to the manufacturer via the network, or places an order by mailing the contract to the manufacturer separately. I do).

  S2 is accepted and shipped by the manufacturer. In response to the order placed in S1, the manufacturer accepts an order for the software product and ships the software product and license information (for example, an opening key, the number of licenses, etc.) (sent to the management center 3 via the network). Alternatively, record it on a medium and mail it).

  S3 delivers. This delivers the software product and license information shipped in S2 to the management center 3.

  S4 and S5 are registered / updated in the software transaction table 33. Accordingly, as described in the software transaction table 33 in FIG. 6A, software A, B, etc. that are delivered software products (software name, version number, license number, contract period, etc.) , Contract amount, etc.) or registered or updated as shown.

  Through the above S1 to S5, the management center 3 orders a software product from the manufacturer of the developer (sales source), receives the delivery, receives the software name, the version number, and the license number (in the transaction table 33 in FIG. 6A). The number of software licenses received in bulk and delivered), contract period, contract amount, etc. are registered / updated as shown in the figure, and preparations for issuing license keys to the user terminals 2 of many customer companies are completed. Become.

  S11 makes a contract. In this case, a contract (software product license contract) is transmitted from the user terminal 2 of the customer company to the management center 3 (or a contract is mailed separately).

  S12 is accepted. This accepts the contract (contract) sent (mailed) in S11.

  In step S13, the customer management table 34 is registered / updated. This is because, as described in the customer management table 34 in FIG. 6B, the contract received in S12 is a software name, version number, user name (customer name) for which a customer company wishes to be licensed. Register or update the contract period, opening key, maximum number of contracts (maximum contracted licenses), etc.

  In S14, the management server 1 is installed. In this case, the management server 1 in FIG. 1 is installed on the customer company side.

  In S15, an agent is installed. This allows an agent program to be installed in the user terminal 2 in the customer company so that various processes in the user terminal 2 after S16 can be executed.

  S16 generates a media key. This is the unique ID of the user terminal 2 in which the agent 21 installed in S15 is installed (for example, the unique ID of the hard disk or CPU) or the unique ID of the medium such as the IC card 23 connected to the user terminal 2. The medium key is generated by reading (for example, the read ID is generated as it is as the medium key).

  S17 installs an application. This installs the licensed application (software product) in the user terminal 2 and makes it operable.

In step S18, a key issue request is transmitted.
In S19, the medium key generated in S16 at the time of the key issuance request in S18 is attached.

  S20 accepts / manages. The management server 1 receives the key issue request transmitted in S18 and S19, and registers / updates it in the license management table 13 for management.

  S21 accepts and receives the media key. In this case, the management center 3 accepts a key issuance request attached with a medium key accepted by the management server 1 in S20.

  In S22, a license key is issued. This is described in the medium key received by the management center 3 in S21 (the unique key of the medium connected to the user terminal 2 or the user terminal 2), and further in the license key table 36 of FIG. 6D. Based on the software name, the contract period, and the opening key, a falsification preventing HASH is generated by a known method. Thereby, based on the generated license key, if the software name, the contract period, the opening key, and the medium key do not match, the agent 21 installed in the user terminal 2 is controlled not to start the corresponding software.

S23 is registered in the customer management table 34.
In step S24, the license management table 35 is registered. In S23 and S24, in response to the license key being issued in S22, information (software name, version) for creating a new entry in the customer management table 34 in FIG. 6B and issuing the license key. Number, user name (customer name), contract period, opening key, medium key (user terminal 2 or key unique to the medium), maximum number of contracts (maximum number of contracts contracted by the customer)), and ( c) Create a new entry in the license management table 35 and register the information (user terminal, contract type, contract period, operation record (no registration)) that issued the license key.

  In S25, the license key is received. This is because the management server 1 receives the license key issued from the management center 3 in S22.

  S26 receives distribution. In this case, the user terminal 2 receives the distribution of the license key from the management server 1 that has received the license key in S25.

In S27, application use is started.
In step S28, it is determined whether a predetermined period (for example, one month since the start of use) has elapsed. If YES, the process proceeds to S29. If NO, repeat S28.

S29 transmits an operation report.
In S30, the operation is checked. This refers to the operation report transmitted in S29 and checks the number of activations for each software.

  In S31, it is determined whether an application is used. As a result of the operation check in S30 (for example, the number of activations check for each software (application)), it is determined whether there is a predetermined number of times (for example, 0 or more). In the case of YES, the use (activation) of the application (software) is continued in S33. On the other hand, in the case of NO, the administrator is notified in S32 (for example, a message indicating that the software name, the number of times of use for one month is 0, etc. is displayed as a list on the screen of the administrator user terminal 2).

  Through the above S11 to S33, the customer company contracts with the management center 3 (contracts the software name, the number of licenses, etc.) and the software transaction table 33 in FIG. 6A and the customer management table 34 in FIG. 6B. The management server 1 is set, the agent 21 is installed on the user terminal 2, the software (application) is installed, and a key issuance request attached with the medium key is sent from the user terminal 2 via the management server 3 to the management center 3. The license key is issued and registered in the customer management table 34 in FIG. 6B, the license management table 35 in FIG. 6C, and the license key table 36 in FIG. 6D. At the same time, the license key is transmitted to the user terminal 2 and the application (software) is based on the license key. It is possible to start a business process to start the E A). At this time, the operating status of the user terminal 2 is notified to the management server 1 every predetermined period (for example, every month), and when there is an unused application (software), a message to that effect is presented to the administrator. Is possible.

FIG. 3 shows a flowchart (part 2) for explaining the operation of the present invention.
In FIG. 3, S41 starts an application.

  In step S42, it is determined whether the key HASH check is normal or abnormal. This is done by determining whether the license key issued by the management center 3 in S22 of FIG. 2 described above is normal and has not been tampered with, and has been tampered with or abnormal. If found to be normal, the process proceeds to S43. If it is determined that the falsification is abnormal, the process proceeds to S55.

  In S43, it is determined whether it is within the contract period. This is to determine whether the date on which the application is instructed in S41 is within the contract period included in the key. If YES, the process proceeds to S44. In the case of NO, since it is determined that it is not within the contract period, the process proceeds to S55.

  In S44, it is determined whether it is within the operation report period. For example, it is determined whether the operation report period (for example, one month) has elapsed since the start of application use. If YES, the process proceeds to S52. In the case of NO, since it has been found that the operation report period (for example, one month) has elapsed, the process proceeds to S45.

    In S45, since it has been found in S44 that an operation report period (for example, one month) has elapsed, the user terminal 2 transmits a key revocation confirmation to the management server 1.

    In S46, the management server 1 receives the key revocation confirmation. Then, it is transferred to the management center 3.

In S47, the management center 3 receives the key revocation confirmation.
In S48, the customer management table 34 is referred to.

    S49 generates a key confirmation result. This is because the key (license key) for which the key revocation has been confirmed is registered (not revoked and not deleted) with reference to (b) the customer management table 34 in FIG. Generate one of the key confirmation results that are not (expired and deleted). And it returns to the management server 1.

    In S50, the management server 1 receives the key confirmation result. Then, it is transferred to the user terminal 2.

  S51 determines whether the key has expired. This is because the agent 21 of the user terminal 2 determines whether the received key confirmation result is key revocation (key revocation is not registered in the customer management table 34 in FIG. 6B). In the case of YES, the key revoked in S54 is invalidated, and the process proceeds to S55. On the other hand, in the case of NO, since the key has been found to be valid without being revoked, the process proceeds to S52.

  In S52, it is determined whether or not they match with the medium key. This is because the agent 21 compares the medium key included in the key (license key) with the unique ID of the user terminal 2 or the unique ID of the medium connected to the user terminal 2 (for example, the IC card 23 in FIG. 1). Determine if they match. In the case of YES, the application is activated in S53 and starts operation. On the other hand, if NO, the process proceeds to S55. Here, the medium key is the CPU of the user terminal 2, a unique ID (device ID) of the hard disk, a security ID, a security chip ID, and the like. In the case of a medium connected to the user terminal 2, an IC For example, the ID of the card 23.

  In step S55, an error message and an inability to start are displayed to call attention. As a result, the user operating the user terminal 2 can recognize that the license of the software to be activated has expired, the key (license key) has been falsified, or cannot be used due to the expiration of the expiration date.

  As described above, when a user gives an instruction to start an application (software) on the user terminal 2, a HASH check is performed based on the key to determine whether the key has been tampered with, whether a period has elapsed, and an operation report. It is discriminated whether the period has elapsed and whether the key has expired, and when these are normal (valid), the media key included in the key and the media key of the user terminal 2 match and are valid terminals. It becomes possible to start the application (software) and start the business process when it is OK.

FIG. 4 is a flowchart for explaining the operation of the present invention (part 3).
In FIG. 4, S62 determines whether a predetermined period has elapsed. This determines whether a predetermined period (for example, one month) during which the agent 21 constituting the user terminal 2 reports the operation has elapsed. In the case of YES, an operation report is transmitted to the management server 1 in S63, and the process proceeds to S65. If NO, the process proceeds to S64 and the process is continued.

  In S65, the operation status is recorded. In this case, the management server 1 that has received the operation report in S63 records the received operation report. Then, it is transferred to the management center 3.

In S66, the management center 3 records the operation report.
S67 is recorded in the license management table 35. In the license management table 35 of FIG. 6C, the last working day in the operating state (for example, working day) in the user terminal 2 reported from the agent 21 of the user terminal 2 is extracted and registered. .

  In S68, it is determined whether the management server 1 is the closing date. This determines whether the management server 1 is a closing date (for example, a closing date once a month) when the user terminal 2 manages the operation status of the application. If YES, the process proceeds to S70. If NO, the process continues in S69.

  In S70, an operation status is created. This creates the operating status (starting count, last startup date, etc.) for each user terminal 2 (and for each application).

  S71 notifies the customer administrator. This is notified by presenting a list of operating conditions created in S70.

  In step S72, it is determined whether there is an application operation record. In this case, it is determined whether the application has been activated during a predetermined period (for example, one month) during the operation status notified in S71. If YES, the process continues at S73. If NO, the process proceeds to S74.

  S74 asks the administrator for confirmation. If the administrator specifies not to use, the process proceeds to S76. If the administrator specifies that it will be used, the process continues in S75.

  In S76, the contract is updated (the number of licenses is changed). This is because the application (software) installed in the user terminal 2 was not used and it was determined that the administrator specified that the application was not used. Decrease the number by one).

  S77 accepts key revocation. This is because it is determined in S76 that the license is unnecessary, and the expiration of the key of the license is accepted.

  In step S78, an agent key revocation process is performed. As a result, the agent 21 configuring the user terminal 2 invalidates the corresponding key (the license key that is not used and designated as unnecessary by the administrator).

In S79, the management center 3 accepts the key revocation from the management server 1.
In S80, the corresponding entry (the entry of the expired key) is deleted from the customer management table 34.

  As described above, when the agent of each user terminal 2 notifies and records the operation status of the application (software) to the management server 1 every predetermined period (for example, every month), and there is an application that is not used on the closing date. When it is designated to be not used by being presented to the administrator, it is determined to be revoked, the agent constituting the user terminal 2 is notified and the key is revoked, and the corresponding entry from the customer management table 34 is notified to the management center 3 The key can be revoked by deleting. The expired license can be reused when there is a key issuance request from another user terminal 2.

FIG. 5 shows a flowchart (part 4) for explaining the operation of the present invention.
In FIG. 5, the management center 3 places an order in S81.

  S82 accepts / ships. In this case, the manufacturer accepts the order of S81 and ships it (ships software and license information).

  S83 delivers. This delivers the software and license information shipped in S82 to the management center 3.

S84 creates an uncontracted entry.
In step S85, the software transaction table 33 is registered.

  The management center 3 orders the software from the manufacturer of the developer (sales source) through the above S81 to S85, and the software (license information) delivered from the manufacturer is shown in the software transaction table 33 of FIG. Can be registered.

In S91, the agent 21 of the user terminal 2 transmits a key issue request.
In S92, the management server 1 accepts and manages the key issuance request transmitted in S91.

  In S93, the management server 1 transmits a key issuance request management and a new issuance request to the management center 2.

S94 accepts the new issue request transmitted in S93.
In S95, it is determined whether it is within the maximum number of contracts. This is to determine whether the request for new issuance of the key (license key) accepted in S94 is within the maximum number of contracts of the customer. In the case of YES, a key is generated in S96, registered in the customer management table 34 in S97, and the key is notified to the management server 1.

  In S98, the management server 1 that received the notification in S95 accepts it, registers and manages it in the license management table 13, and transmits the key to the agent 21 of the corresponding user terminal 2.

  In S99, the agent 21 that received the transmission in S98 receives and stores the key distribution. Thus, thereafter, the agent 21 can start an application (software) based on the key.

  In S100, it is determined whether the management center 3 is within the number of orders with the manufacturer. This is because the number of licenses is increased by 1 because the key is generated in S96, and it is determined whether the total number of licenses of the application (software) is within the number of licenses ordered by the management center 3 from the manufacturer. In the case of YES, since it is found that the number of licenses ordered is within, processing is continued in S102. On the other hand, in the case of NO, since it is found that the number of licenses ordered has been exceeded, an order (additional order) is made in S101 to increase the number of licenses of the management center 3, and the processing is continued in S102.

  In S103, since it has been found that the key issuance request accepted in S95 exceeds the maximum number of licenses contracted by the customer, a notification to that effect is sent to the customer administrator (that the current key issuance request exceeds the number of contract licenses). In step S104, the administrator makes an additional contract. Then, although not shown, the steps from S94 are repeated, and the key is distributed to the agent 21 of the user terminal.

  In response to the key issuance request from the agent 21 of the user terminal 2 through the above S91 to S104, if the management center 3 is within the maximum number of contracts of the customer, the key is issued and distributed to the agent 21, When the maximum number of contracts of the customer is exceeded, it is possible to issue a key after distributing an additional contract and distribute it to the agents 21. Also, in response to the key being issued, the management center 3 can post-order to the manufacturer to increase the number of licenses when the maximum number of licenses is exceeded, and take care not to run out of licenses. .

FIG. 6 shows an example table of the present invention.
FIG. 6A shows an example of a software transaction table. The software transaction table 33 registers and manages information purchased from a software developer (seller), and here registers and manages the following information shown in association with each other.

・ Software name:
・ Version number:
・ Number of licenses:
·Contract period:
・ Contract amount:
・ Other:
Here, the software name is a unique name for distinguishing software. The version number is the version number of the software. The number of licenses is the maximum number of software that can be licensed. The contract period is a contract period during which software can be licensed. The contract amount is the contract amount for which the license has been acquired.

  As described above, the management center 3 purchases a large number of software licenses from the manufacturer at a low cost and manages them in a table, and the range does not exceed this number of licenses. It is possible to use and manage the software under the license by subdividing the user terminals 2 of a large number of customers and assigning license keys in a range that does not exceed the increase.

  FIG. 6B shows an example of a customer management table. The customer management table 34 registers and manages keys (license keys) issued by each customer (for each user), the maximum number of contracts, and the like. Here, the following information shown in FIG. To manage.

・ Software name:
・ Version number:
-User name (customer name):
·Contract period:
・ Opening key:
・ Media key:
・ Maximum number of contracts:
・ Other:
Here, the software name is a unique software name to be licensed. The version number is the version number of the software. The user name (customer name) is the customer (customer company) to whom the software is licensed. The contract period is a contract period for licensing the software. The opening key is a key for opening the software. The medium key is the medium key of the user terminal 2 that has requested software issuance after installing software (the unique ID of the hardware of the user terminal 2, the ID of a medium such as an IC card connected to the user terminal 2). The maximum number of contracts is the maximum number of licenses contracted by the customer.

  FIG. 6C shows an example of a license management table. The license management table 35 registers and manages license information of a key (license key) issued to the user terminal 2. Here, the license management table 35 registers and manages the following information shown in association with each other. is there.

・ Terminal type:
·Contract type:
·Contract period:
・ Operation records:
・ Other:
Here, the terminal type is a registered type of the user terminal 2 of the customer who issued the license key. The contract type is the name of the software that issued the license key. The contract period is the contract period of the software license that issued the license key. The operation record is a record of the last start date of the software that issued the license key.

  FIG. 6D shows an example of a license key table. The license key table 36 registers and manages information related to the license key of the software. Here, the license key table 36 registers and manages the following information shown in FIG.

・ Contract software:
·Contract period:
・ Opening key:
・ Media key:
・ HASH:
・ Other:
Here, the contract software is the name of software that issues a license key. The contract period is the license contract period. The opening key is a key used when opening the software. The medium key is a unique ID of the device of the user terminal 2 in which the software is installed or a unique ID of a medium such as the IC card 23 connected to the user terminal 2. HASH is a falsification preventing HASH for preventing falsification of contract software, contract period, opening key, and media key.

  The present invention makes it possible to use various types of software products used by a large number of employees of a customer company at a low cost for any period of time, and to easily realize license management.

It is a system configuration diagram of the present invention. It is operation | movement explanatory flowchart (the 1) of this invention. It is operation | movement description flowchart (the 2) of this invention. It is operation | movement description flowchart (the 3) of this invention. It is an operation | movement explanatory flowchart (the 4) of this invention. It is an example table of this invention.

Explanation of symbols

1: Management server 11: License validity confirmation means 12: Operation status recording means 13: License management table 2: User terminal 21: Agent 22: IC card adapter 23: IC card 3: Management center 31: License issuing means 32: License management means 33: Software transaction table 34: Customer management table 35: License management table 36: License key table

Claims (7)

In a license management system that manages licenses for many software products for each customer,
An agent that is provided on each user terminal of a customer and that activates the software product based on a unique license key on the user terminal in which the software product is installed;
A management center that manages the number of licenses issued by the customer in response to a key issuance request from the user terminal of the customer, and creates a unique license key in the user terminal and returns and stores the license key A license management system.   The license key includes at least one or more of software product information, an opening key for opening the software product, and a user terminal that can activate the software product or a unique medium key of the connected medium, and the license key is unmodifiable. The license management system according to claim 1, wherein   2. The management center according to claim 1 or 2, wherein the management center deletes and reuses the license when it is notified that the total number of licenses issued to the user terminal for each customer is managed and expired. 2. The license management system according to 2.   The management center manages the number of licenses issued to all customers, and displays a message to that effect when the number of licenses exceeds the maximum number of licenses for software products. The license management system according to any one of the above.   A management server for managing the multiple user terminals is provided on the customer side, and the management server manages the usage status of the software product every predetermined period or sequentially, presents unused user terminals, 5. The license management system according to claim 1, wherein when a revocation instruction is issued, the license is notified to the management center and the license of the user terminal is revoked. In a license management program that manages licenses for many software products for each customer,
Agent means provided on each user terminal of the customer and activated by using the software product based on a unique license key on the user terminal in which the software product is installed; and
In response to a key issuance request from the user terminal of the customer, the computer operates as a management center means for managing the number of licenses issued by the customer and creating a unique license key in the user terminal and returning and storing it. License management program to let you. In a license management method for managing licenses for many software products for each customer,
Providing each customer terminal of the customer, and starting the software product based on a unique license key on the user terminal in which the software product is installed;
A step provided in the management center for managing the number of issued licenses of the customer in response to a key issuance request from the user terminal of the customer and creating a unique license key in the user terminal and returning and storing the license key A license management method.

Images