JPH11154086A - Network installation method - Google Patents

Abstract

(57) [Summary] [Problem] A side that supplies a software product provides information that sets whether or not the software product can be used and the number of usable clients for each software product to a side that uses the software product in a state that is difficult to falsify. . The system ID is a system identification symbol.
An installation consisting of a product ID indicating the type of software product permitted to be used, a version symbol indicating the version name of the software product, and a use permitted number indicating the number of clients permitted to use the system The conditions are grouped for each product ID and encrypted as a symbol string, the input symbol string is decrypted on the server, the decrypted installation conditions and the system ID input from the IC card, software products stored in advance, and the server Check the number of clients connected to the server and install them when they match.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network installation method for installing, on a plurality of software products mounted on a server as a host, software products permitted to be used by a request from a server or a request from a client. It is related to the improvement of.

[0002]

2. Description of the Related Art Generally, when a software product that is permitted to be used by a contract between a side that supplies the software product and a side that uses the software product is used, the software product to be used is supplied each time a contract is made. It is cumbersome to do so, and it is not possible to take prompt action, so all software products that can be used in the delivery system are stored in the delivery system in advance, and only software products that are permitted to use can be used. The delivery system is set in advance. Further, when a software product is used by a plurality of users on the side that uses the software product, it is necessary to set in advance the number of clients to be used in accordance with both contracts.

When a software product is used by a plurality of users, a required number of software products are copied and used on the side using the software product, instead of being individually supplied. Therefore, there is a risk of illegal copying, and how to prevent such illegal copying is an important problem.

Japanese Patent Laid-Open No. 4-1043 discloses a protection system for protecting such illegal copies.
There is an invention disclosed in JP-A-25. According to the present invention, a machine ID assigned to the machine in advance is compared with a machine ID registered in a machine information table, and if they match, the AP (application program) body is loaded. In the case of a mismatch, if the maximum number of available machines is not exceeded, the machine ID is additionally registered in the machine information table to load the AP itself, and if the maximum number of available machines is exceeded, the AP is loaded. Refuse to load the main unit. Further, at the start of the execution of the AP, the machine ID and the machine ID registered in the machine information table are collated again, and if they match, the execution of the AP itself is started, and if they do not match, the execution of the AP itself is rejected. It is an invention.

[0005] In the above invention, collation of an AP as a software product is not described, but all APs are referred to.
Is assumed to be usable. In addition, the contents of the machine information table are not encrypted, and the machine ID registered in the machine information table is compared with the machine ID registered in the machine information table based on the machine ID previously assigned to the actual machine. To prevent fraudulent acts by not exceeding the maximum number of available machines.

[0006]

Since the conventional network installation method is configured as described above, the condition is that a client ID as a machine is assigned to an actual machine, and when the client ID is falsified. There was a risk of unauthorized copying. There is also a problem that the number of available machines cannot be set for each software product.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and a software product supply side uses information that sets whether or not the software product can be used and the number of available clients for each software product. It is an object of the present invention to provide a software product to a user using the software product in a state in which it is difficult to falsify.

[0008]

A network installation method according to the present invention is a network installation method in which a plurality of software products are stored in advance in a server and software products permitted to be used from the server are installed in a client through a network. In the installation system, a system ID which is an identification symbol of the system, a product ID indicating a type of the software product which is permitted to use the above, a version symbol indicating a version name of the software product, and use of the system on the above system. The installation conditions including the number of permitted clients indicating the number of permitted clients are grouped for each of the product IDs and encrypted as a symbol string. The input symbol string is decrypted on the server, and the decrypted installation condition and Enter from IC card Has been above Provides system ID, the software product, collates the number of clients connected to the server that is stored in advance, in which they are installed when aligned.

The above-mentioned installation condition is represented by a string of numbers, and is encrypted as a symbol string by arithmetic processing.

Further, the installation conditions are compared with the number of clients connected to the server, and if they do not match, after a preset grace period elapses,
The network installation system is forcibly terminated.

When changing the software product or the number of authorized users, the newly encrypted symbol string is input to the server.

Further, when updating the version name of the software product, the old software product is uninstalled and then the new software product is installed.

[0013] Further, the setting information relating to the client at the time of the installation is backed up, and the backed up setting information is restored when the installation is performed again.

Furthermore, at the time of installation or uninstallation, characters indicating that installation or uninstallation is being performed are displayed by blinking.

Further, a server standby icon is provided for waiting for a request from the server on the client at the time of installation or uninstallation.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 FIG. 1 shows a system configuration of a network installation system according to a first embodiment of the present invention, wherein 1 is a server and 2 is a LAN 3
Is a client connected by The provided software products are all provided by a medium 4 such as a CD-ROM and stored in the server 1. Reference numeral 5 denotes a license for use, which is a system I which is an identification symbol unique to each system.
D, a product ID indicating the type of the software product permitted to be used, a version symbol indicating a version name of the software product, and a permitted number of used clients indicating the number of clients permitted to use on the system. Are encrypted for each of the product IDs as a symbol string. This symbol string is input to the server 1 from the terminal device 6 of the server 1 and is decoded on the server 1 to be a criterion for determining whether or not installation is possible.

The system ID is a unique identification number for specifying a network installation system.
The information is input by being read into the server 1 from an IC card reader (not shown) connected to the server 1 by an IC card. Therefore, the network installation system is not limited to a specific server 1 but can be constructed if a system ID is set. However,
Since the encrypted symbol string needs to be decrypted on the server 1, if the decryption method is set as hardware means on the server 1, only the server 1 having conditions is valid. Further, as for the client 2, only the number of the clients 2 permitted to use on the system is set as an installation condition, so that the client 2 can be basically connected to the LAN 3 regardless of the type of the client 2, and It is only necessary to be able to communicate with.

FIG. 2 shows an example of encryption of installation conditions. For example, the installation conditions are as follows. System ID: 093 Product ID: 02 Edition A01: 0101 Permitted number of use 34: 34 Under these conditions, the symbol strings A to K of the installation conditions on the upper side of FIG. 2 are as follows. 09302010134 Here, for example, as one method of encryption, one column of the symbol string + 1, two columns + 2, three columns + 3,..., Ten columns + 10,
Assuming that the last digit of the operation result is adopted as the 11th column +11, the encrypted symbol strings L to V on the lower side of FIG. 11646788035

As described above, if all the installation conditions are represented by a sequence of numbers as an example of the encryption, various arithmetic processes can be performed, and the range of the encryption method can be expanded.

The number of clients 2 connected to the server 1 is compared with the number of clients 2 permitted to use during the installation conditions. If the numbers do not match, after a preset grace period, the network Kill the installation system. Further, after the grace period, an error message or an alarm may be displayed periodically to force the software product user to pay attention before the network installation system is forcibly terminated.

The software products to be installed on the network are a group of products that operate on the client 2 side. These product groups are provided on the server 1 side and set up by downloading from the server 1. Also, uninstallation can be performed in the same manner. Installation and uninstallation can be performed from either the server 1 or the client 2. The available software product name and its version name, and the number of available clients are managed on the server 1 side, and a client ID is set for each client 2 to determine which client 2
The server 1 also has management information as to whether it is installed in the server 1. By referring to such management information, it is also possible to manage a group of products installed in each client 2.

FIG. 3 shows an operation screen when the installation is executed from the client 2. First, the host name of the server 1 to be connected for installation is input in the input field 7. Then, when the button 8 of "connection" is clicked, the list of products that can be connected to the host and can be installed in the list box 9 is displayed, and the button 8 changes to "execute". Select the product to be installed from the list box 9 and click the button 8 to start the installation. When the process is interrupted when the button 8 changes to "execute", the process is interrupted by clicking the "cancel" display button 10.

Upgrading to update the version name of a software product is made possible by uninstalling the old software product and then installing the new software product. The new version of the software product needs to be separately stored in the server 1 by a medium 4 such as a CD-ROM.

When changing the software product or the number of authorized users, the user is required to newly provide an encryption key in which the installation conditions are grouped for each product ID and changed to a symbol string, and input the encryption key from the terminal 6. Thus, the license 5 can be substantially updated.

The setup information, which is the setting information on the client 2 at the time of installation, is backed up from the server via the network. For example, when a disk (not shown) on the client 2 side is broken, the environment is restored from the server via the network. Can be restored and copied to another client 2 for use.

At the time of installation or uninstallation, characters indicating that installation or uninstallation is being performed are displayed by blinking. FIG. 4 shows a state during the execution of the installation. The same screen is displayed during the execution of the uninstallation. At a glance, it is possible to determine that installation or uninstallation is being performed.
It is also possible to notify the user by voice at the same time.

When the disk on the client 2 side is broken, the software product can be reinstalled by re-installing from OS first and setting the same IP address as before the installation. The software product can be installed on the same client 2 any number of times as long as the consistency in the network installation is properly maintained. However, for some reason,
If a file managed by network installation is corrupted, an error will occur during consistency check. If recovery is possible, it will be repaired within the consistency check, but if it cannot be repaired, it will be necessary to forcibly uninstall and uninstall the product in error. When installing on the client 2 of the substitute product, another IP address is set and installed.
After repairing client 2, substitute client 2
Need to be uninstalled.

The functions that can be started from the server 1 include installation, uninstallation, backup of setting information, restoration thereof, and consistency check. There are three functions that can be started from the client 2, installation, uninstallation, and consistency check. When these functions are executed by the client,
It is necessary to activate a server program on the server 1 to be connected. At the time of installation or uninstallation, a server standby icon for waiting for a request from the server on the client is provided. By clicking the icon, the processing is led by the server 1.

Each of the server 1 and the client 2 is provided with a command file storing management information for checking consistency. Normally, the management information is processed so as to maintain the sameness. ing. The command file stores, in addition to the encrypted symbol string, a version name, an installation source, an installation destination, an installation date, and the like, so that the installation history can be managed.

Although the software product group is stored on the server 1 side, the instruction file is stored in the same directory as the directory storing the compressed file obtained by compressing the software product with a file name by which the association with the software product can be identified. Is stored. This instruction file stores cataloged procedures for performing installation, uninstallation, consistency check, backup, and restoration. The client 2 selects and executes the procedures to complete the processing. Can be. Therefore, no specific installer is required.

Below, 5 which can be started from the server 1 side
The operation flow of the three functions and the three functions that can be activated from the client 2 will be described with reference to the drawings. FIG. 5 is a processing flow showing the processing when installing from the server 1 to the client 2. After inputting a command to be installed in the client 2 in the server 1, information from the client 2 is waited. The client 2 transmits the contents of the command file, date information of the date of operation, and the like (step S1). Upon receiving this information data, the server 1 decrypts the encrypted symbol string, checks the consistency, and returns response data as a check result to the client 2 (step S2). Software Product I
If D is not a permitted one, or if the version name is not a permitted one, the installation is interrupted. However, if the number of clients 2 is not the permitted number, a preset grace period is given. After that period, the network installation system is forcibly terminated.

Next, the client 2 requests the server 1 for an installation instruction file (step S).
3). Upon receiving the request, the server 1 opens the designated installation instruction file and sends it to the client 2 (step S4). The client 2 outputs the instruction file to a temporary file, and executes processing based on the contents of the instruction file. Next, a request is made to the server 1 to copy the compressed file of the software product (step S).
5). The server 1 sends the compressed file of the designated software product to the client 2 (step S
5). The client 2 decompresses the transmitted compressed file to make it usable. Next, in the server 1,
After performing maintenance as an update of the installation history in the management information of the command file, it is transmitted to the client 2 (step S7). After completing the installation, the client 2 transmits the management information of the command file held by the client 2 to the server 1 as a result notification of the post-maintenance command file (step S).
8). Thus, the installation from the server 1 is completed.

FIG. 6 is a processing flow showing the processing when uninstalling from the server 1 to the client 2.
The basic processing is the same as the case of installation in FIG. 5, except that the instruction file requested in step S11 and transmitted from the server 1 in step S12 is for uninstallation.

FIG. 7 is a process flow showing a process for executing a backup from the server 1 to the client 2. After the server 1 checks the consistency, the client 2 requests the server 1 for a backup instruction file (step S16). The client 2 that has received the instruction file executes a backup process. In this backup processing, only the personal information of the user of the client 2 is extracted from the setting information of the client 2 and used as a restore file. The generated restore file is transmitted to the server 1 (step S18). The server 1 that has received the restore file transmits the response data (step S19), and the client 2 notifies the result of the completion of the backup (step S20), and ends the processing.

FIG. 8 is a processing flow showing the processing when the restoration is executed from the server 1 to the client 2. After checking consistency on server 1, client 2
Requests the server 1 for a restore instruction file (step S23). The client 2 that has received the instruction file executes a restore process. This restore process is executed after the installation process is executed, and is the user's personal information in the setting information of the client 2 collected by the backup process of FIG. When the file of the client 2 is destroyed for some reason, the software product is reinstalled, and the user's personal information in the setting information of the client 2 is restored.

FIG. 9 is a processing flow showing the processing when the server 1 checks the consistency with the management information of the client 2. As described above, the consistency check is performed by comparing the management information in the command file held by each of the server 1 and the client 2, but the installation condition as an encrypted symbol string is compared. If the files of the server 1 and the client 2 are destroyed, special measures are required.

When the file of the server 1 is destroyed, the management information of the command file is automatically recovered. This can be realized by copying the management information of the command file held by the client 2. However, when the command file held in the client 2 is destroyed, the automatic recovery is not performed. If the management information of the command file is unconditionally recovered and the software product is reinstalled, it is impossible to distinguish between a case where the file is destroyed and a case where the file is illegally copied to a separate client. By checking the date, the server 1 sends the OS to the client 2
If it is confirmed that the software product has been reinstalled, it will be given permission to reinstall the software product.

FIG. 10 is a processing flow showing the processing when the client 2 requests the server 1 to install. An installation is requested from the client 2 using the input screen of FIG. The subsequent processing is basically the same as that of FIG. 5, except that the server 1 disconnects the TCP / IP after receiving the result notification from the client 2 in step S37.
This is a process of waiting for the next request from the client 2.

FIG. 11 is a processing flow showing the processing when the client 2 requests the server 1 to uninstall. Uninstallation is requested from the client 2 on the same input screen as in FIG. Subsequent processing is basically the same as that of FIG. 6, except that the server 1 sends a TCP /
This is a process of disconnecting the IP and waiting for the next request from the client 2.

FIG. 12 shows that the client 2
9 is a process flow showing a process when a check for consistency with management information is performed. A command file is requested from the client 2 (step S43). The server 1 copies the command file held by the server 1 and sends it to the client 2 as response data (step S
44). After notifying the server 1 of the received result, the client 2 checks the consistency in the client 2 and terminates. The server 1 disconnects the TCP / IP and waits for the next request from the client 2.

In the above, the network installation system having one server has been described. However, a plurality of servers may be provided in one network installation system.
In that case, a plurality of system IDs are set, and the client connected to each server uses a software product permitted in the system ID to which the client belongs.

[0042]

Since the present invention is configured as described above, it has the following effects.

The installation conditions are grouped for each product ID, encrypted as a symbol string, the input symbol string is decoded on the server, and the decoded installation conditions and the system ID input from the IC card are stored in advance. Since the software product and the number of clients connected to the server are checked and installed when they match, information that sets whether or not the software product can be used and the number of available clients for each software product Can be provided to the user of the software product in a state that is difficult to falsify.

Further, since the installation condition is represented by a sequence of numbers and is encrypted as a symbol string by arithmetic processing, various arithmetic processing can be performed, and the range of the encryption method can be expanded. .

Further, when the installation conditions do not match the number of clients connected to the server, the network installation system is forcibly terminated after a preset grace period, so that the installation conditions are complied with. So that you can use the software product.

When the software product or the number of authorized users is changed, a newly encrypted symbol string is inputted to the server, so that accurate information can be provided without confusion of the installation conditions due to the change. Can be.

Further, when updating the version name of a software product, the configuration is such that the old version of the software product is uninstalled and then the new version of the software product is installed. The effect is that the latest version of the software product can be used.

Also, since the configuration information is configured to be restored when the uninstalled software product is backed up after the uninstallation, the operating environment can be restored and copied to another client for use.

Furthermore, since the character indicating that the installation or uninstallation is being performed is displayed by flashing at the time of installation or uninstallation, it can be determined at a glance that the installation or uninstallation is being performed. .

Further, since a server standby icon for waiting for a request from the server is provided on the client, it is possible to immediately switch to a network installation under the initiative of the server.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram showing a network installation system according to a first embodiment of the present invention.

FIG. 2 is a schematic diagram showing an encryption method according to the first embodiment of the present invention.

FIG. 3 is a schematic diagram showing an input screen for executing installation according to the first embodiment of the present invention;

FIG. 4 is a schematic diagram showing a screen display during installation of the first embodiment of the present invention.

FIG. 5 is a processing flowchart showing installation from a server according to the first embodiment of the present invention;

FIG. 6 is a processing flowchart showing uninstallation from the server according to the first embodiment of the present invention;

FIG. 7 is a processing flowchart showing backup from a server according to the first embodiment of the present invention;

FIG. 8 is a processing flowchart showing restoration from the server according to the first embodiment of the present invention.

FIG. 9 is a processing flowchart showing a consistency check from the server according to the first embodiment of the present invention.

FIG. 10 is a processing flowchart showing installation from a client according to the first embodiment of the present invention.

FIG. 11 is a processing flowchart showing uninstallation from the client according to the first embodiment of the present invention.

FIG. 12 is a processing flowchart showing a consistency check from a client according to the first embodiment of the present invention.

[Explanation of symbols]

 1 server, 2 clients.

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Kiyoshi Tomizuka 2-3-2 Marunouchi, Chiyoda-ku, Tokyo Inside Mitsubishi Electric Corporation (72) Inventor Hideki Sato 2-3-2 Marunouchi, Chiyoda-ku, Tokyo Rishi Electric Co., Ltd.

Claims (8)

[Claims] 1. A network installation system in which a plurality of software products are stored in a server in advance and permitted to be used from a server, and the client installs the software products on a client through a network, a system ID which is an identification symbol of the system.
And a product ID indicating the type of the software product permitted to be used, a version symbol indicating the version name of the software product, and a usage permitted number indicating the number of clients permitted to use the system. The installation conditions are collectively encrypted for each product ID as a symbol string, the input symbol string is decrypted on the server, and the decrypted installation conditions and the system ID input from the IC card are stored in advance. A network installation method, comprising checking the number of the above software products and the number of clients connected to a server, and installing the software products when they match. 2. The network installation method according to claim 1, wherein the installation condition is represented by a sequence of numbers, and is encrypted as a symbol sequence by a calculation process. 3. The method according to claim 1, wherein the installation condition is compared with the number of clients connected to the server, and if the two do not match, the network installation system is forcibly terminated after a preset grace period. The network installation method according to claim 1 or 2, wherein 4. The server according to claim 1, wherein when the software product or the number of authorized users is changed, the newly encrypted symbol string is input to the server. Network installation method. 5. The method according to claim 1, wherein when updating the version name of the software product, an old software product is uninstalled and then a new software product is installed. Network installation method. 6. The network according to claim 1, wherein the setting information on the client at the time of the installation is backed up, and the backed up setting information is restored when the installation is performed again. Installation method. 7. The network according to claim 1, wherein at the time of installation or uninstallation, a character indicating that installation or uninstallation is being performed is displayed by flashing. Installation method. 8. A server standby icon for waiting for a request from a server on a client at the time of installation or uninstallation.
The network installation method according to claim 7.