JPH07219763A - Method and device for registering/starting software - Google Patents

Abstract

PURPOSE:To provide a method and a device for registering and starting software, by which the illegal use of software can be prevented. CONSTITUTION:The identification number of a unit issuing a registration request to software is obtained (S1). The network address of the unit issuing the registration request is registered in a registration table storing at least the name of software corresponding to the identification number of the registered unit and the number of licenses licensed to software (S4). The number of the licenses in the registration table is updated in accordance with the registration of the unit (S7). It is informed to the supply source of software that the number of the licenses is updated (S8).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software registration / startup method and apparatus for managing, for example, accounting for software operating in a network environment.

[0002]

2. Description of the Related Art In order to prevent unauthorized use of software, it is common practice to establish a usage contract between a software supplier and a user. In such a usage contract system, one package and one user type in which one package of software is associated with one user and one package or two users of one package in which one package of software is associated and associated with a plurality of users are contracted. There are different ways.

In recent years, the capacity of a storage medium such as a disk required by one piece of software has increased, and the network environment such as a client / server type system has been improved. Without starting the software, temporarily store it on a fixed disk on the client side, or store the program part of the software on a server on the network and store the data part on each client side. , Access time is shortened, and disk space is effectively used. Therefore, it is meaningless to protect the storage medium that supplies the software to prevent unauthorized use.

[0004]

As described above, in the present situation,
The problem is that even a user who does not have a software license can illegally use the software by making illegal copies of software resources such as data and programs and without using a contract with the supplier of the software. There is. As a countermeasure against such unauthorized use, there is a method of protecting the storage medium supplied from the supplier so as to prevent unauthorized copying. However, as described above, the software is installed on the fixed disk of individual users or on the network. Since it is stored in the server and used, it is not a very effective measure.

The present invention has been made in view of the above-mentioned conventional example, and an object of the present invention is to provide a software registration / activation method and an apparatus therefor capable of preventing unauthorized use of software.

It is another object of the present invention to provide a software registration / activation method and apparatus capable of preventing activation of software by an unregistered user.

[0007]

In order to achieve the above object, the software registration method of the present invention comprises the following steps. That is, the step of acquiring the identification number of the device that issued the registration request to the software, at least storing the software name corresponding to the identification number of the registered device and the number of licenses licensed to the software. A table that registers the device that has issued the registration request, and updating the number of licenses according to the registration of the device.

In order to achieve the above object, a software starting device of the present invention has the following configuration. That is, it is determined whether or not at least the registration storage unit that stores the software name corresponding to the identification number of the registered device and the device that issued the activation request are registered by referring to the registration storage unit. And a starting means for referring to the registration storage means and starting the software when the device is registered in the registration storage means.

[0009]

With the above configuration, the identification number of the device that issued the software registration request is acquired, and at least the software name corresponding to the identification number of the registered device and the number of licenses licensed to the software are acquired. The device that has issued the registration request is registered in the table that stores, and the number of licenses in the table is updated according to the registration of the device.

Further, according to the activation device of the present invention, at least the device which issued the activation request is registered with reference to the registration storage means which stores the software name corresponding to the identification number of the registered device. To determine if
When the device is registered in the registration storage means, the device for which the activation request is issued refers to the registration storage means and operates so that the software can be activated.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT A preferred embodiment of the present invention will now be described in detail with reference to the accompanying drawings.

FIG. 2 is a block diagram showing a configuration of an information processing system to which a software billing system according to an embodiment of the present invention is applied. This information processing system
Here, there is provided one server interposed between the communication line 203 and the network 202, and a plurality (N in this case) of clients (user terminals) 201-1 to 201-N, which are connected to the network. They are connected to each other via 202. The software billing system of this embodiment operates on the server 200 side, and a software activation request from a user is sent from the client 201 side to the server 2 side.
00 shall be transmitted. The present invention is not limited to the terminal connected to such a network.

FIG. 3 shows the client-side terminal 2 of this embodiment.
It is a block diagram which shows the structure of 01.

A terminal 201 on the client side of this information processing system includes a memory 20 for storing data and programs executed / processed by the terminal 201, a display device 21 for displaying a message to an operator, and a memory. A central processing unit 22 that controls the entire terminal 201 on the client side according to a program stored in 20, a network interface unit 23 that controls the connection between the network 202 and the terminal 201 according to the method of the network 202, and a large amount of data. And an external storage device 24 for storing programs and the like, and an input device 25 equipped with a keyboard, a pointing device, etc. for an operator to input.

FIG. 4 is a block diagram showing the configuration of the server 200 of this embodiment.

The server 200 has a memory 26 for storing data and programs executed and processed by the central processing unit 28, and a network for controlling the connection between the network 202 and the server terminal 200 in accordance with the method of the network 202. An interface unit 27, a central processing unit 28 that controls the entire server 200 according to a control program stored in the memory 26, an external storage unit 29 that stores a large amount of data and programs, and an interface between the line 203 are controlled. Line interface unit 30
And have.

FIG. 5 is a diagram showing the data format of the charging system registration table held by the software charging system of this embodiment. FIG. 5 (A) shows the data format registered in the memory 26 on the server 200 side. FIG. 5B shows a data format when the data is registered in the external storage device 29 of the server 200. When this table data is stored in the external storage device 29, it is encrypted by a known method using the “key” for storing the registration table and stored in the external storage device 29 in the data format of FIG. 5B. , General users cannot change the contents arbitrarily.

In FIG. 5A, reference numeral 501 denotes a key "key" for storing a registration table stored in software to be installed, and one unique key code is assigned to each software. . 5
02 is the name of software to be installed, 503 is
The address (storage position) of the memory 26 in which the software is stored is shown. Reference numeral 504 indicates the number (license number) of clients (users) whose software is licensed. Reference numeral 505 denotes a network address of a client (terminal) connected to the network 202, and a unique network address value is stored for each client.

Further, in FIG. 5B, reference numeral 510 indicates
(A) A storage “key” corresponding to the “key” 501 for storing the registration table is shown, and 511 is 502 in FIG.
505 shows the encrypted data.

In the software billing system of this embodiment, the function of registering in the user machine and storing and transmitting the billing information based on the processing shown in the flowchart of FIG. 1 and the flowchart of FIG. It has the function of installing software and the function of checking the registration status when the software is started, as shown in the flowchart of FIG. 7. Hereinafter, each function will be described with reference to the corresponding drawings. The programs shown in the flowcharts of FIGS. 1, 6, and 7 are stored in the memory 26 of the server 200.

First, the software installation process of the software billing system in this embodiment will be described with reference to the flowchart of FIG. This process is performed in step S2 of creating a charging system registration table.
0, software name 502, number of licenses 504, and “key” 501 for storing registration table S
21, software name, number of licenses, “key” for storing registration table, step S22 for setting software storage position 503, step S23 for storing charging system registration table in external storage device 29, step S24 for actually installing software It has and.

The processing shown in the flowchart of FIG.
The process performed by the central processing unit 28 of the server 200 at the time of installing the software is shown.
When the software installation process is started via the network interface unit 27 of 00, the process proceeds to step S20, and the charging system registration table of the data format shown in FIG. This table is created one for each software ("key") to be installed.

Next, in step S21, the name of the software to be registered (software name) 502, the number of licenses 504, the registration table from the information stored in the installation medium (storage medium storing software) on the client side. The “key” 501 for storage is acquired. Then, the process proceeds to step S22, and the registration table of the memory 26 created in step S20 is added to step S21.
Set the software name obtained in step 1, the number of licenses, and the "key" for storing the registration table. Further, the storage location (path name) 503 of the software to be installed is uniquely determined and set in the registration table. It should be noted that this storage position 503 is not known to general users. When these setting processes are completed, the process proceeds to step S23, and this registration table is stored in the external storage device 29 of the server 200. At this time, the contents (FIG. 5A) of the registration table in the memory 26 of the server 200 are changed to the special format shown in FIG. 5B by using the “key” 501 for storing the registration table and external storage. It is stored in the device 29. Therefore, it is impossible for a general user to read the contents of the registration table from the external storage device 29 or change the contents. After this, the process proceeds to step S24 and step S
The software is installed in the storage location of the memory 26 determined in 22.

Next, with reference to the flow chart of FIG. 1, a description will be given of a process of registering a user and storing and transmitting accounting information in the software accounting system of this embodiment.

This process is performed by step S1 of acquiring the address of the machine (client terminal) desired to be registered on the network 202, step S2 of reading the charging system registration table from the external storage device 29, restoring and reading it into the memory 26, machine. Step S3 of judging registration / cancellation selection, Step S4 of adding the registered machine (client terminal) to the charging system registration table, Step S5 of acquiring the current number of registered machines and the number of licenses,
Step S6 of comparing the current number of registered machines with the number of licenses, step S7 of updating the number of licenses of the charging system, step S8 of notifying the supplier of the software that the number of licenses has been updated, charging system registration table S in the external storage device 29
9. Step S10 of deleting the registration of the registered machine from the charging system registration table (deregistration).

Hereinafter, the server 20 at the time of registering the machine
The processing performed by the central processing unit 28 of No. 0 will be described with reference to the flowchart of FIG.

First, when a machine registration process from the user terminal 201 (client) to the information processing system is started via the network interface unit 27 of the server 200, the process proceeds to step S1 to issue a request for registration process. Get the network address of the terminal that did. Next, in step S2, the charging system registration table is
A “key” 5 for reading the registration table from the external storage device 29 of the server 200 to the memory 26 of the server 200
10 is used to convert from the special format (FIG. 5 (B)) to the normal registration table format (FIG. 5 (A)). Next, in step S3, it is determined whether the request processing issued by the user terminal is "registration" or "registration cancellation".

If the result of this determination is "registration", the process proceeds to step S4, and the network address of the terminal which issued the registration request is added to the charging system registration table in the memory 26 of the server 200. Next, in step S5, the current number of registered machines and the number of licenses in this table are acquired. Next, in step S6, the current number of registered machines acquired in step S5 is compared with the number of licenses. If the current number of registered machines is larger than the number of licenses, the process proceeds to step S7, and the memory of the server 200 is stored. Two
Update to increase the number of licenses in step 6, then step S
In step 8, the updated number of licenses is notified to the software supplier using a known mail system or the like.

As this known mail system, the SMTP mail protocol of TCP / IP is used in this embodiment. Then, in step S9, the server 200
The charging system registration table in the memory 26 of the computer is changed from the normal format (FIG. 5A) to the special format (FIG. 5) by using the “key” 501 for storing the registration table.
After the conversion into (B)), it is stored in the external storage device 29 and the process ends. When the current number of registered machines is equal to or smaller than the number of licenses in step S6, the process proceeds to step S9, and the charging system registration table of the memory 26 is stored in the external storage device 29.

If the result of determination in step S3 is that the request processing is "registration cancellation", the flow proceeds to step S10, after deleting the network address of the corresponding client terminal from the charging system registration table in the memory 26, then in step S9. Then, the process proceeds to step S3 to store the data in the external storage device 29.

Next, with reference to the flow chart of FIG. 7, a process of activating software through the software billing system in this embodiment will be described. This processing is step S30 of acquiring software start-up information, step S31 of acquiring the network address of the client terminal 201 in the registration table, and step S of comparing the network address with the client side address.
32, step S3 of acquiring the storage location of the software
3, Step S34 of activating the corresponding software, and Step S35 of displaying a message are provided.

Hereinafter, when the software is started, the server 20
The processing performed by the central processing unit 28 of No. 0 will be described with reference to the flowchart of FIG.

If there is a request to activate the already installed software through the network interface unit 23 of the client 201 and the server side network interface unit 27, step S30
Then, the software activation information from the client 201 side and the network address of the client 201 are acquired. Next, in step S31, the network address of the user (client 201) registered in the registration table is acquired. Next, in step S32, it is determined whether the network address of the client 201 that issued the software activation request is registered in the registration table. If "registered", step S
In step 33, the storage location 503 of the software is acquired from the registration table, and the software is activated in step S34. On the other hand, if the result of determination in step S32 is “unregistered”, the process proceeds to step S35, and an error message indicating that the user is not registered as a client of the software is displayed on the display device 21 of the client 201 and processed. To finish.

In the above embodiment, each client terminal is prepared and registered in the registration table, but may be registered for each user. In this case, the user name and password may be stored in the charging system registration table instead of the network address of the terminal.

Further, in the above-mentioned embodiment, when the current number of registered machines exceeds the number of licenses, the fact is notified to the supplier of the software using the mail system. Each client may pay the license fee by printing a bill or the like on a connected printer or the like. In this case, if the user pays the license fee, the password for the number described in the invoice can be obtained, and even if the user terminal is newly registered by inputting the password into this system. good.

As described above, according to this embodiment, the number of licenses of the software is stored when the software is installed, and the number of registered machines exceeds the number of licenses in response to a machine registration request from the user. In that case, the charging information data indicating this is notified to the software supplier.

When a software activation request is input from a client, it is determined whether or not the terminal of the client is registered, and if it is not registered,
I try not to start the software.

As a result, the software supplier can charge the license fee of the additionally registered software to the client based on the billing data notified by the user, so that the illegal copy of the software is prevented. Will be able to. Further, since the software is not started when the client machine is not registered, it is possible to prevent an unauthorized user from using the software.

[0039]

As described above, according to the present invention, it is possible to prevent illegal use of software.

Further, according to the present invention, it is possible to prevent the activation of software by an unregistered user.

[Brief description of drawings]

FIG. 1 is a flowchart showing a function of registering a client machine and storing and notifying accounting information in an embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of an information processing system to which the software charging system according to the exemplary embodiment of the present invention is applied.

FIG. 3 is a block diagram showing a configuration of a terminal of a client of this embodiment.

FIG. 4 is a block diagram showing a configuration of a server according to the present exemplary embodiment.

5 is a diagram showing a data format of a charging system registration table of software according to an embodiment of the present invention, and FIG.
FIG. 5A shows the data format of the registration table stored in the memory, and FIG. 5B shows the data format of the registration table stored in the external storage device.

FIG. 6 is a flowchart showing a function of installing software according to an embodiment of the present invention.

FIG. 7 is a flowchart showing a function of activating software according to an embodiment of the present invention.

[Explanation of symbols]

 20, 26 memory 21 display device 22, 28 central processing unit (CPU) 23, 27 network interface unit 24, 29 external storage device 25 input device 30 line interface unit 200 server 201 client 202 network 203 communication line

Claims (11)

[Claims] 1. A step of obtaining an identification number of a device that has issued a software registration request, and at least storing a software name corresponding to the identification number of the registered device and the number of licenses licensed to the software. A method of registering software, comprising: a step of registering a device that has issued the registration request in a registered table; and a step of updating the number of licenses according to the registration of the device. 2. The software registration method according to claim 1, further comprising the step of notifying a supplier of the software of the number of licenses of the updated table. 3. The software registration method according to claim 1, further comprising a step of encrypting and storing the updated table. 4. The software registration method according to claim 1, wherein the table further stores an identification code of the software, a storage location of the software, and an identification number of a registered device. . 5. The step of obtaining the identification number of the device that issued the software activation request, and referring to at least a table storing the software name corresponding to the identification number of the registered device, the activation A step of determining whether or not the device that issued the request is registered, and a step of starting the software by referring to the table when the device is registered in the table. How to start the software. 6. The software activation method according to claim 5, further comprising the step of transmitting an error message to the device that has issued the activation request when the device is not registered in the table. 7. The method of starting software according to claim 5, wherein the table further stores an identification code of the software, a storage location of the software, and an identification number of a registered device. . 8. An acquisition unit for acquiring an identification number of a device that has issued a software registration request, and at least a software name corresponding to the identification number of the registered device and the number of licenses licensed to the software. A storage unit that stores the information; a registration unit that registers the device that issued the registration request in the storage unit; and an updating unit that updates the number of licenses stored in the storage unit according to the registration of the device. An apparatus for registering software, comprising: 9. The software registration device according to claim 8, further comprising means for encrypting and storing the updated contents of the storage means. An acquisition means for acquiring the identification number of the device that has issued the software start request, 10. At least a registration storage unit that stores a software name corresponding to an identification number of a registered device, and whether the device that issued the activation request by referring to the registration storage unit is registered. A software start-up device comprising: a determination unit that determines whether or not the device is activated, and an activation unit that activates the software by referring to the registration storage unit when the device is registered in the registration storage unit. . 11. The software activation device according to claim 10, wherein the registration storage means further stores a storage address of the software.