JP2000207199A - Method, device and system for managing software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent with the simple operation of a user the unauthorized use of a software. SOLUTION: This software managing method is provided with a step for generating a second key 3 for identifying the peculiar use of a software on a computer machine on the basis of a first key 1 applied, corresponding to a user permission of the software and an identification code 2 characteristic of each computer machine for operating that software at least and a step for discriminating whether or not the software can be used based only on the second key 3 at the time of using the software. A license code 1 applied at license registration and the software use key 3 deciding whether or not each software can be used within the range of the license thereof are independently managed/ operated.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software management method, a software management device, and a software management system. More particularly, in electronic commerce on a network for which software is to be traded, software is easily operated by a user. The present invention relates to technology for preventing unauthorized use of software and realizing flexible and efficient license management of software.

[0002]

2. Description of the Related Art A general procedure for selling and managing software by electronic commerce via a network such as the Internet will be described.

[0003] A user downloads desired software via a network and receives free distribution of the software. After the payment, the user is notified of a code (hereinafter, referred to as a license code) indicating the grant of a license for permitting use of the software from the store. When the user uses the software, the input license code is checked, and it is determined whether or not the use is a valid use based on the license.

On the other hand, software is characterized in that it can be copied very easily. For this reason, in reality, in many cases, one piece of licensed software is illegally copied and then illegally used by a plurality of computer machines without permission.

[0005] In order to prevent unauthorized copying of this software, it is required to manage on which computer machine the use of each piece of software is permitted. That is, in order to prevent a plurality of uses for a license for one piece of software, the use of each piece of software on each computer machine must be managed by a machine-specific identification code or the like.

[0006] As a conventional method of checking unauthorized use, there has been firstly a method using a license code. This first
In this method, a user inputs a license code when using software. Check that this license code is used as a key.

[0007] However, in this first method, if another user only needs to know a single license code, even if there is only a license for one piece of software, the software is duplicated on a plurality of computer machines. And easy to use. Therefore, unauthorized use could not be sufficiently prevented. In addition, if the keys are highly complicated, the operation of the user becomes complicated.

As a second method, there is a method using an identification code unique to a computer machine. In the second method, the identification code of the downloaded machine is embedded in the software when the user downloads the software. When software is used, the identification code in the software and the identification code of the machine on which the software is running are automatically checked. Therefore, it is possible to prevent unauthorized use on a machine other than the permitted machine without inputting a key when the user uses the key.

However, according to the second method, a license at the time of download is fixedly associated with the identification code of the computer machine at the download destination.
For this reason, software version upgrades or modifications cannot be processed as changes within the same license. In addition, the operation of the downloaded software cannot be checked before the license is registered. Also in these cases, it is necessary to re-execute the license registration procedure similar to that at the time of new purchase, forcing the user to perform a complicated operation. On the other hand, the license manager also needs to manage the information of the same software on the same machine redundantly, and the license management is complicated.

[0010]

As described above, according to the present invention, since the use check is carried out by a single key such as a sales key or a machine identification code in the prior art, unauthorized use of software is easy. Alternatively, it is made to solve the problem that the operation on the user side and the operation on the license manager side are complicated.

An object of the present invention is to provide a software management method, a software management device, and a software management system that can prevent unauthorized use of software by a simple operation of a user. is there.

Another object of the present invention is to realize license management of general-purpose software capable of supporting various sales forms in electronic commerce.

[0013]

A feature of the present invention for realizing the above-mentioned object is that a license code assigned at the time of licensing software and a key for use check at the time of using the software are mutually independent. It is in the point to let. That is, the key at the time of license issuance and the key at the time of license check are separated.

A key used for checking software use (hereinafter referred to as a software use key) is provided with a unique key for each software and for each machine.

In order to realize such a function, the invention according to claim 1 is a software management method for managing use of software via a network.
A unique use of the software on the computer machine is determined based on a first key assigned in accordance with the license of the software and a unique identification code of each computer machine running the software. The second to identify
And a step of determining whether or not to use the software based on only the second key when using the software.

According to the above configuration, it is possible to check whether the use is licensed for each computer machine independently of the first key given at the time of licensing. Therefore, it is possible to sufficiently prevent unauthorized use of the software by a simple operation of the user.

According to a second aspect of the present invention, there is provided a software management method for managing use of software via a network, the method comprising: providing a first key corresponding to a license of software; Generating, when the first key is present, a second key identifying a unique use of the software on each computer machine running the software; Determining whether or not the software can be used based on only the second key.

According to the above arrangement, it is possible to check whether or not the use is licensed for each computer machine independently of the first key given at the time of licensing. Therefore, it is possible to sufficiently prevent unauthorized use of the software by a simple operation of the user.

In a third aspect of the present invention, in the step of generating the second key, when the software is used first, the second key is generated based only on the identification code. In addition, it is possible to execute the operation check of the software before purchasing the software, and manage the operation check.

Further, the invention according to claim 4 is a first means for judging whether or not a first key given in accordance with a license of software has been received, and the first means for determining whether the first key has been received. A second key identifying a unique use of the software on the computer machine based on the unique identification code of each computer machine running the software only when it is determined that the key has been received. And a second means for generating.

According to the above configuration, it is possible to check whether the use is licensed for each computer machine independently of the first key given at the time of licensing. Therefore, it is possible to sufficiently prevent unauthorized use of the software by a simple operation of the user.

Further, the invention according to claim 5 is a license issuing server for licensing software via a network, a use management server for managing use of the software, and a user system for operating the software. A software management system comprising: the license issuing server includes a first key generation unit that assigns a first key corresponding to a license for software; and the use management server includes at least: Generating a second key identifying a unique use of the software on the computer machine based on the first key and an identification code unique to each computer machine running the software; A key generation unit, wherein the user system only uses the second key when using the software. Zui and characterized by comprising determining use determination unit whether to use the software.

According to the above configuration, the sales manager of each software and the manager of the license can be provided independently.

[0024]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a diagram for explaining a system configuration of a software management apparatus and system according to the present embodiment. As shown in FIG. 1, the software management system according to the present embodiment includes a sales management server 10, a user system 20, and a license management server 30. Sales management server 10, user system 2
0. The license management server 30 is mutually connected to a network via a network (not shown) such as the Internet.

The sales management server 10 is managed by a store that sells software under the consignment of the software maker 40 or the like. The sales management server 10
After confirming payment from the user as consideration for the sold software, a license code 1 is issued to the user system 20.

The user system 20 acquires a desired software main body 5a selected from a shop or the like on the Internet from a software maker 40. This software 5a may be downloaded to the user system 20 via the Internet 7, or may be distributed off-line in a form such as a CD-ROM 9.

The license management server 30 is managed by a store or an outsourcing company. In the license management server 30, each software sold is installed on any computer machine of any user,
Manage whether it is used. Specifically, when the license code 1 of the target software has been issued, the license management server 30
A software use key 3 is issued for 0.

Next, a system of each code and key used in this embodiment will be described.

The license code 1 is a code for identifying a license to use the sold software. The license code 1 is assigned at the time of license registration after the sale of the software, and is notified to the software purchase user. The license code 1 includes, for example, a software name, a sales number, a license ID, a password, and the like. The license code 1 corresponds to the first key in the claims.

The machine identification code 2 is a code for uniquely identifying a computer machine on which the software is to be operated after license registration. The license management server 30 uses the machine identification code 2 as a unit for software license management. The machine identification code 2 is, for example, the OS of the computer machine on which the software runs.
(Operation System) name, OS number, hard disk number in which software is installed, and the like.

The software use key 3 is a key for identifying whether the use of the software in each user system 20 is a legitimate use based on the issued license. The software use key 3 is provided with a unique key for each computer machine required when using each software. In each user system 20,
Using this software use key 3, it is determined whether or not the use of the software is within a licensed range (for example, use on one permitted computer machine). The software use key 3 includes, for example, machine identification information, software identification information, date and time information, and the like. The machine identification information may be generated from the machine identification code 2 through an arbitrary conversion process. Similarly, the software identification information may be generated from the license code 1 through an arbitrary conversion process. In addition to the above, for example, when the license is time-limited, it may be configured to include license period information.
Further, it may be configured to include a use mode. By using this use mode at the time of use determination, it is possible to determine which of the use is the operation check mode, the rental use mode, the term-limited license use mode, the perpetual license mode, and the like. The software use key 3 corresponds to the second key in the claims.

The software use key 3 is used alone as a release key of use prohibition at the time of use check. That is, the license code 1 is mutually independent.
Therefore, a plurality of software use keys 3 may be issued for one license code 1. This gives 1
Can be used when a license permits use on multiple computer machines. The software use key 3 is embedded in target software or the like and used for a use check without the user's awareness. Therefore, encryption and complication may be arbitrarily performed to prevent unauthorized use.

The system other than the above and the generation method of the license code 1, the machine identification code 2, and the software use key 3 are arbitrary, and may be generated by a generally known method.

Next, a processing procedure of the software management method, the software management apparatus, and the software management system according to the present embodiment will be described with reference to FIGS. (1) New purchase of software The procedure for newly purchasing the desired software is shown in FIG.
This will be described below with reference to FIG.

First, the user obtains desired software by downloading or the like (S10).

Next, in order to determine whether to purchase the downloaded software, the user checks the operation of the software (S20). This operation check can be processed via the operation check registration screen, for example, when the software is first started.

At the time of operation confirmation, a use check is performed using a temporary software use key. FIG. 3 shows a temporary software use key issuing procedure at the time of operation confirmation. The license management server 30 receives, from the user system 20, a request for using software for operation confirmation together with the machine identification code 2 of the computer machine transmitting the request. The license management server 30 issues a temporary software use key 3a to the user system 20 based on the machine identification code 2. The use of the software is determined by the issued temporary software use key 3a. For this reason, the sales side can operate the software only on a predetermined machine even before the license is registered based on the intention to purchase.
Further, since the above-described processing is executed only by the license management server 30, the selling side (sales management server 10) does not need to process a frequently performed operation check request. On the other hand, the user can purchase the software as necessary after confirming the contents of the desired software.

The temporary software use key 3a
Is generated by the license management server 30 including expiration date information indicating how long the software can be used. For this reason, it is difficult for the user system to detect the expiration date information embedded in the software use key 3a, and it is possible to prevent the software from being used indefinitely by illegally modifying the expiration date information. Is done. By suppressing the alteration of the term information, it is possible to provide the above-mentioned license use mode or the like as a software use mode.

Next, when the user who has determined the purchase intention by confirming the operation deposits the software purchase price, a license code 1 corresponding to the sales data such as the name of the user who purchased the software and the number of purchases is given thereafter, The user server 20 is notified from a sales server or the like (D1 in FIG. 1). The sales management server 10 stores the license registration information in the sales database 12 together with the corresponding license code 1. This license code 1
Is also stored in the license management database 32 managed by the license management server 30 (D in FIG. 1).
2).

Next, the user who has been given the license code 1 registers the license with the license management server 30 (S30). Specifically, first, the user system 20 and the license management server 30 are connected online. For this connection, for example, a network address of the license management server 30 embedded in a general-purpose module attached to the downloaded software may be used. The user inputs the license code 1 via the initial screen of the target software or the like. By inputting the license code 1, the license code 1 and the machine identification code 2 are transmitted to the license management server 30 (D3 in FIG. 1). The machine identification code 2 can be obtained by reading identification information unique to the computer machine on which the license registration has been activated, using, for example, a generally known interrupt instruction.

After the license registration, the license management server 30 generates the software use key 3 (S
40). The process of generating the software use key may be executed immediately after the license is registered, or may be executed when the software is used for the first time.

Referring to FIG. 4, a procedure for generating a software use key after license registration will be described in detail. The license management server 30 receives the machine identification code 2 of the computer machine from the user system 20 (FIG. 1).
D3). The license management server 30 searches the license management database 32 for the received machine identification code 2 and the license code 1 corresponding to the software requested to be used. The license code 1 may be stored in the license management database 32 in advance, or may be acquired from the sales management server 10 when the software use key is issued. If the corresponding license code 1 exists, the license management server 30 issues a software use key 3b for the software to the user system 20 based on the machine identification code 2 (D4 in FIG. 1). If the corresponding license code 1 does not exist, the license management server 30
Does not generate the software use key 3b. The issued software use key 3b is received by the user system 20 and stored in the software to be licensed or stored in association with the software. On the other hand, the license management server 30 only needs to manage the machine identification code 2 in each user system 20,
There is no need to be aware of each software use key 3b. For this reason, even when the software use key 3b is changed as needed on the user system 20 side for the purpose of maintaining security or the like, it is not necessary to update data on the license management server 30 side, and license management becomes easy. .

Next, when the user starts the target software in the user system 20, a software use check process is performed (S50). The use check process is performed based on only the software use key 3 stored corresponding to the activated software. As a specific method of the use check, a generally known use determination method may be selected according to the system of the software use key 3.

In this use determination, it is not necessary to check the correlation with another license code 1. For this reason,
There is no need to connect to the sales management server 10 and the license management server 30 online,
The necessary and sufficient use check can be completed alone.

The use checking process is performed as a background process without user input. For this reason, the user does not need to be aware of the highly complicated software use key 3. Also, there is no need to remember the license code 1 and input it each time it is used. Therefore, user operability is greatly improved.

If the activation of the software on the computer machine is validated by the use check, the software is enabled (S6).
0). On the other hand, if it is determined at the time of this use check that the use is invalid, such as activation by a computer machine that is not covered by the license or modification of the software use key 3, the use of the software is determined to be unusable. can do.

That is, since the software use key 3b is generated from the machine identification code 2, when it is started on another computer machine, the difference of the machine identification code is easily detected and the other computer machine is used. The above use can be prevented. (2) At the time of changing license information Next, a processing procedure at the time of changing license information in the case where the license registration for the target software has already been performed will be described below. (A) Upgrading First, a case of upgrading the target software will be described. As in the case of the new purchase, the user obtains a new version of the software from the software maker 40 by downloading or the like.

Next, a license information change process is started. In FIG. 1, a license information change request from the user system 20 is transmitted to the license management server 30.
This license information change request includes information indicating the version upgrade of the software. The license management server 30 generates the software use key 3 corresponding to the new version if the license is the machine identification code 2 based on the license information change request.
The new software use key 3 is transmitted to the user system 20 and the license management database 3
Update 2.

As described above, in the present embodiment, it is only necessary to change the software use key 3 when upgrading. A new use key can be given under the same license irrespective of the license code 1. For this reason, the sales management server 10 does not need to perform processing related to version upgrade in each user system of the same license. In this embodiment, free version upgrade is also easily realized. On the other hand, the user does not need to perform the license re-registration processing every time the version is upgraded, and the operability is improved. (B) Change of Machine Used Secondly, a case of changing the computer machine that runs the licensed software will be described.

First, the user starts and executes the license cancellation processing on the licensed computer machine.

The user system 20 transmits the license cancellation information to the license management server 30 after executing the license cancellation processing. The license management server 30 generates a used machine change code (not shown) according to the license revocation information, and
Send to 0. In the user system 20, a user executes a license registration process on a computer machine where the user should use the software. The software use key 3 is updated by inputting the used machine change code given in the license registration process. This allows
Under the same license, a software use key 3 on a new computer machine can be obtained.

For this reason, the license management server 30
Can associate and manage old and new computer machines using software under the same license. On the other hand, the user can also perform the license cancellation process on the computer machine whose use is to be terminated and move the software use key by a simple operation simply by entering the assigned machine change code on the license registration screen etc. it can.

[0054]

As described above, according to the present invention,
The following effects are obtained.

That is, the software management method, the software management apparatus and the system according to the present invention provide each machine of each software which is generated from the license code and the machine identification code, not the license code itself given at the time of licensing. Provides a function to check software usage by using a unique software usage code. Therefore, an effect is obtained that unauthorized copying can be easily prevented for each computer machine without complicated operation of the user.

Further, by separating the license code and the software use key, a license management server can be provided independently, and a general-purpose software license that can support various sales forms in electronic commerce. Management can be realized.

As described above, according to the present invention, simple and flexible software license management is realized, and the convenience of both the software supplier and the software user is significantly improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a system configuration of a software management device and a system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing a processing procedure of a software management method according to the embodiment of the present invention.

FIG. 3 is a diagram illustrating a process of generating a temporary software use key for operation confirmation.

FIG. 4 is a diagram illustrating a process of generating a software use key after license registration.

[Explanation of symbols]

 D1 License code data D2 License code data D3 Machine identification code data D4 Software use key data

Claims (5)

[Claims] 1. A software management method for managing use of software via a network, the method comprising: at least a first key assigned in accordance with a license to use the software; Generating a second key identifying a unique use of the software on the computer machine based on the unique identification code of each computer machine to be used. Determining whether or not the software can be used based on only the second key. 2. A software management method for managing the use of software via a network, the method comprising: providing a first key corresponding to a license to use the software; Generating a second key identifying a unique use of the software on each computer machine running the software; and using the second key during use of the software. Determining whether or not the software can be used based only on the software management method. 3. The method of claim 1, wherein the step of generating the second key generates the second key based only on the identification code when the software is used for the first time. Software management method described. 4. A first means for judging whether or not a first key provided in response to a software license has been received, and the first means for judging reception of the first key. Second means for generating a second key identifying a unique use of the software on the computer machine based on the unique identification code of each computer machine running the software only if A software management device, comprising: 5. A software management comprising a license issuing server for licensing software via a network, a use management server for managing the use of the software, and a user system for running the software. In the system, the license issuing server includes a first key generation unit that assigns a first key corresponding to a license of software, and the use management server includes at least the first key; A second key generation unit for generating a second key for identifying a unique use of the software on the computer machine based on an identification code unique to each computer machine running the software; The user system uses the software based on only the second key when using the software. A software management system comprising a use determining unit for determining whether or not use of the software is possible.