JP4370018B2 - Software transfer system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention selects necessary software when transferring software between computers via a network.System and its transferIt is about the method.
[0002]
[Prior art]
In a computer system that transfers data between two or more devices, for example, there is an online load system in which software desired by a user is transferred via a network.
[0003]
FIG. 14 is a configuration diagram of a system for online loading software via a conventional network. In the figure, at least one server computer 1 and at least one client computer 2 are connected via a network 3.
The server computer 1 is composed of communication means 6 for communicating with other computers via the network 3, software transfer server processing means 4 for controlling software transfer, storage means 5 for storing software, and the like. Yes.
The client computer 2 includes communication means 6 for communicating with other computers via the network 3, software transfer client processing means 7 for controlling software transfer, storage means 5 for storing software, and displaying information to the user. Display means 8 to be operated, and operation means 9 for the user to operate the software transfer client processing means 7.
[0004]
Next, in the system shown in the figure, the operation when transferring software will be described with reference to FIG. 15 showing a communication sequence between them.
First, when the user designates the server computer 1 to be connected by the operation means 9 of the client computer 2, the connection is requested to the designated server computer 1 and the connection is established. Next, the client computer 2 requests and receives a list of software from the server computer 1 and presents it to the user by the display means 8. Next, when the user selects software to be transferred by the operation means 9 of the client computer 2, the selected software is requested from the server computer 1, received, and stored in the storage means 5. Repeat this process for all software to be transferred.
When all the software has been transferred, the connection between the client computer 2 and the server computer 1 is disconnected by the user's operation.
[0005]
[Problems to be solved by the invention]
The conventional software transfer method operates as described above and transfers without checking the reliability of the transfer source server or the software of the server, so that the received software is the client's existing software or data. There has been a problem that concerns remain about whether or not it will adversely affect the environment.
Furthermore, since only the software name is transferred at the time of transfer, there is a problem that the already installed software is transferred again to waste time.
[0006]
  The present invention has been made to solve the above-mentioned problems, and software transfer that has already been installed and is safe without affecting the data and prevents unnecessary transfer.systemThe purpose is to obtain.
[0007]
[Means for Solving the Problems]
  According to this inventionSoftware transfer system
  A server computer for transferring software over a network;
  A client computer having resources used by the software;
In a software transfer system with
  The server computer
  Storage means for storing software that uses a predetermined resource as a required resource at the time of execution;
  A list of software that can be provided that describes the software names of the software stored in the storage means and the necessary resources used by the software;
  Software transfer server processing means for controlling the transfer of software;
  Server communication means for communicating with a client computer via a network;
With
  The above client computer,
  A resource information table for storing resource information indicating allocated resources allocated to the server computer among the resources of the client;
  Software transfer client processing means for controlling the transfer of software;
  Client communication means for communicating with a server computer via a network;
With
  The client computer
  The client communication means receives the software list that can be provided from the server computer,
  The software transfer client processing means compares the necessary resource of the software described in the available software list with the allocated resource indicated by the resource information stored in the resource information table, and sends it to the server computer that has transmitted the available software list. Determining whether the corresponding allocated resource satisfies the necessary resource of the software described in the list of available software,
  The client communication means requests the server computer as transfer request software for software in which the allocated resource satisfies the required resource,
  The server computer
  The software transfer server processing means selects the requested software as the transfer request software from the software stored in the storage means as the transfer software,
  The transfer software is transmitted to the client computer by server communication means.
It is characterized by that.
[0008]
  The above list of available software is
  Enter the software hash value along with the software name and required resources of the software,
  The client computer further includes:
  It has a received software list that contains the software name of the installed software and the hash value of the installed software,
  The client computer
  Software whose software name and hash value described in the list of available software are the same as the software name of installed software and the hash value of installed software described in the received software list. transferrequestIt is excluded from the software.
[0009]
DETAILED DESCRIPTION OF THE INVENTION
Embodiment 1 FIG.
If reliable software from a specific contracted server can be used, there is no problem, but if the client uses software that has not yet been installed from the destination to transfer from a nearby server, there is a safety concern. . A transfer method that is secure even for such a transfer in need is described.
FIG. 9 is a flowchart showing the basic operation of the client computer according to Embodiment 1 of the present invention. 1 is a flowchart showing details of step ST006 in FIG. 9, FIG. 2 is a flowchart showing details of step ST105 in FIG. 1, and FIG. 3 shows details of step ST101-1 in FIG. It is a flowchart.
[0010]
FIG. 4 shows a system configuration according to Embodiment 1 of the present invention. In FIG. 4, at least one server computer 1 and at least one client computer 2 are connected via a network 3. The server computer 1 stores communication means 6 for communicating with other computers via the network 3, software transfer server processing means 4 for controlling software transfer, and software that can be provided to the client computer 2. The storage unit 5 and the software provision list 10 that is a list of attribute information of each software are configured.
[0011]
FIG. 5 is a diagram showing an example of the software list 10 that can be provided in the server computer 1, and is indispensable for using the software name, size, date of last update, hash value, and corresponding software as attribute information of each software. The necessary resources that are assets (resources) are included.
The necessary resource 10-1 shown in the figure requires 25 KB as a memory and a display device having a size of 480 × 200 dots, or a file requires writing and reading operations, or software is application B. It is necessary to use the program.
The hash value 10-2 is a compressed value of software data compressed by a hash function that compresses arbitrary length data to a smaller data length (for example, 128 bits). This hash function called a message digest is used in cryptography and has a property that it is difficult to find original data having the same hash value. Therefore, if the hash values of the two data are compared, it can be almost certainly determined whether the contents of the data are the same.
[0012]
The client computer 2 is stored in the communication means 6, software transfer client processing means 7 for controlling the transfer of software, storage means 5 for storing software transferred from the server computer 1, and storage means 5. Received software list 11 that is a list of attribute information of each software, use restricted resource information table 12 that is resource information that can be used by the transferred software, display means 8 that displays information to the user, user The operation means 9 for operating the software transfer client processing means is connected and configured via a bus.
[0013]
FIG. 6 is a diagram illustrating an example of the received software list 11 in the client computer 2, and includes software name, size, last update date / time, hash value 11-2, transfer source server computer, and the like as attribute information of each software. It is.
FIG. 7 is a diagram showing an example of the use restricted resource information table 12 and shows resources (resources) that can be used by the software transfer source for each server computer. For example, software transferred from server A can use file reading / writing, network connection and memory up to 50 KB, and software transferred from server B can use file reading and memory up to 10 KB. This shows that the software transferred from the server C can read and write files and use up to 80 KB of memory. The software transferred from all server computers (all servers) indicates that a 640 × 400 dot display device can be used.
[0014]
Next, operations performed by the system shown in FIG. 4 will be described with reference to FIG. 8 showing the communication sequence between the server and the client and FIG. 9 showing the basic operation flow of the client computer.
Here, the software is transferred from the server computer 1 to the client computer 2.
First, the client computer 2 requests a software list that can be provided to the server computer 1 (ST001). At this time, if the server computer 1 is unknown, the request may be made by broadcast transmission (transmission to all computers connected to the network 3). The server computer 1 responds to this inquiry with a software list that can be provided (ST002).
[0015]
In response to this request, the server computer 1 first transmits a software list that can be provided. Receiving this, the client computer 2 checks whether or not the transmitted server computer 1 is a server included in its use restriction resource information table 12 (ST003). If the responding server computer 1 is not included in the use restricted resource information table 12, the display unit 8 inquires of the user about available resources to be given to the transferred software (ST004). The user inputs the use restriction resource for the server computer responded by the operation means 9, and updates the use restriction resource information table 12 (ST005).
Of course, it is also possible not to allocate available resources to server computers that are not stored in the restricted use resource information table 12 without making an inquiry to the user.
[0016]
  Next, in step ST006, the client computer 2 selects the software to be transferred from the received available software list 10 by the process shown in the detailed flow in FIG. The client computer 2 performs processing ST101-1 for creating an available resource list.
  FIG. 3 is a flowchart showing further details of the available resource list and creation processing step ST101-1 in FIG. Here, a list of all resources that can be used by the software transmitted from the transmission source server (available resource list) is created.
  First, the available resource list is initialized (ST601).
  Next, it is checked whether or not there is a transmission source server column in the use restricted resource information table 12 (ST602), and if there is, the available resource is added to the available resource list (ST603).
  Next, it is checked whether or not there is a column for all servers in the use restricted resource information table 12 (ST604). If there is, the available resource is added to the available resource list (ST605).
  The available resource list in FIG. 16 is an example of the available resource list created as described above. The available resource list that is different for each transfer source server in FIG. 7 and the available resources common to all servers are combined. It has become a thing. FIG.IsFIG. 7 is an available resource list created when software is transferred from the server A in the example of the usage restriction information table of FIG. 7, and combines the available resources for the server A and the available resources for all servers. Yes.
  Next, the client computer 2 initializes a transfer request software list, which is a list of software requesting the server computer 1 to transfer (FIG.1, ST101-2), the following processing (ST102 to ST107) is repeated for each software included in the available software list.
[0017]
First, the client computer 2 checks whether software having the same name as the software that can be provided is included in the received software list 11 (ST103). If there is software with the same name, the hash values are further compared (ST104). If the hash values are the same, it is assumed that the software is the same as the received software, no transfer request is made, and the process proceeds to the next available software.
When there is no software with the same name, or when it is considered that the software has been updated with a different hash value, the necessary resources (resources) of the software that can be provided are compared with the use restricted resource information table 12, and the resources that the software requires Are checked (ST105).
[0018]
This necessary resource determination step ST105 further comprises the detailed operation flow of FIG. 2, and is a resource availability determination process ST700 comprising ST701 to ST707. That is, it is checked whether all necessary resources of the software are available.
First, it is checked whether the name of the necessary resource 10-1 such as “MEMORY.USE” is included in the available resource list (ST702). If the required resource name is not included in the available resource list, it is determined that the required resource is not available, and the process ends (ST707).
If the necessary resource name is included in the available resource list, the option conditions that differ for each resource are also checked (ST703). This optional condition indicates a condition such as a different size for each resource, such as “25 KB” for a memory or “480 × 200 dots” for a display device, and the determination process differs for each resource. Of course, it is not always necessary to set the option condition. In this case, it is determined that the option condition is satisfied.
[0019]
If the optional condition is not satisfied, it is checked whether the necessary resource name is included in the available resource list (ST704). If it is included, the option condition is checked again (ST703). If the required resource name is not included in the available resource list, it is determined that the required resource is not available, and the process is terminated (ST707).
If the optional condition is satisfied, it is determined that the necessary resources being processed are available, and the process proceeds to the next process (ST705).
As described above, for each necessary resource of the software to be transmitted, it is repeatedly checked whether the resource is available. If it is determined that all necessary resources are available, it is determined that all necessary software resources are available, and the process is terminated (ST707).
[0020]
In the example of the software list 10 that can be provided in FIG. 5, ApplicationA requires a display device of 480 × 200 dots or more and a memory of 25 KB or more. When this is transferred from the server A to the client computer 2 having the use restricted resource information table 12 of FIG. 7, the resources that can be used by the software transferred from the server A are read from the file indicated by the available resource list of FIG. A writing and network connection, a memory within 50 KB, and a display device of 640 × 400 dots.
In the case of this example, since the resource that requires Application A is included in the available resource list (FIG. 16) created by the client computer 2, it is determined that Application A transferred from the server A is available. When all necessary software resources are available in this way, this software is added to the transfer request software list (ST106).
[0021]
The above processing (ST102 to ST107) is repeated for all the software included in the available software list received from the server computer, and a transfer request software list is created (ST108). If there is no element in the transfer request software list and there is no software to be transferred, the processing of the client computer 2 is completed (ST007 in FIG. 9).
[0022]
If there is software to be transferred, the client computer 2 sends a transfer request software list to the server computer 1 (ST008). The server computer 1 transmits each software data included in the received transfer request software list to the client computer 2. The client computer 2 receives each software and stores it in the storage means 5 (ST009). At the same time, the received software list is updated.
[0023]
Finally, the transferred software can be used by performing software installation processing such as registering software icons and activating an installer (ST010).
[0024]
As described above, in this embodiment, the client computer receives the list of software that can be provided from the server computer, compares the software included in the list with the received software, and determines the identity. . If a hash function called a message digest in the encryption field is used as the hash value, it can be almost certainly determined whether the data contents are the same.
Since the comparison is made only with a short hash value without transferring the data main body, double transfer of the data main body can be prevented, and traffic, transfer time, communication fee, etc. can be reduced. In addition, since the identity determination can be performed before the data body is transferred, the user does not hesitate to determine whether to overwrite the software with the same name. Furthermore, it is possible to confirm that the reliability of the server or its software is high by handling the hash value.
[0025]
In addition, the resource information required by the software is compared with the usage-restricted resource information table set for each transfer source server computer, and software that cannot be used on the client computer is prevented from being downloaded, improving safety, In addition, traffic and transfer time can be reduced. By setting an available resource list for each server computer, it is possible to obtain software from a reliable server computer and update to the latest version almost automatically and easily.
Further, since the use method of the resource is restricted by the available resource list for the server computer having low reliability, the software exceeding the available resource list is prevented from being transferred and is highly secure.
[0026]
Embodiment 2. FIG.
In the first embodiment, the client computer 2 has determined whether or not software transfer is possible. On the other hand, in the second embodiment, the server computer side determines whether transfer is possible. The system configuration is the same as FIG. 4 of the first embodiment.
[0027]
Next, operations performed by the system shown in FIG. 4 according to the present embodiment will be described with reference to FIG. 10 showing a communication sequence, FIG. 11 showing a server computer operation flow, and FIG. 12 showing a client computer operation flow.
Here, as in the previous embodiment, the software is transferred from the server computer 1 to the client computer 2.
[0028]
First, the server computer 1 that is the software transfer source transmits a software transfer request to the client computer 2 that is the software transfer destination (ST201). Upon receiving the software transfer request (ST301), the client computer 2 checks whether the server computer 1 that transmitted the software transfer request is included in the use restricted resource information table 12 (ST302). If the server computer 1 is not included in the use restricted resource information table 12, the user is inquired about available resources to be given to the software transferred by the display means 8 (ST303). The user inputs the usable resource 12-1 for the server computer 1 through the operating means 9, and updates the use restricted resource information table 12 (ST304). Of course, this process may be omitted and no available resources may be allocated to the new server computer 1.
[0029]
Next, the client computer 2 creates an available resource list for the server computer 1 (ST305-1). FIG. 3 is a flowchart showing details of the processing for creating the available resource list, but since this processing is the same as that of the previous embodiment, the description thereof is omitted here. Then, the available resource list and the received software list 11 for the created server computer 1 are transmitted (ST305-2).
[0030]
Next, when the server computer 1 receives the available resource list and the received software list (ST202), the software to be transferred is selected (ST203).
FIG. 13 is an operation flowchart showing details of the software selection processing step ST203 in FIG. That is, the server computer 1 initializes a transfer software list that is a list of software to be transferred to the client computer 2 (ST401), and then repeats the following processing for each software included in the software list 10 that can be provided (ST402). ~ ST407).
[0031]
First, the server computer 1 checks whether software having the same name as the software that can be provided is included in the received software list received from the client computer 1 (ST403). If there is software with the same name, the hash values are further compared (ST404). If the hash values are the same, the software is considered to be the same as the received software, the preparation for transfer is stopped, and the processing of the next available software is started.
[0032]
If there is no software with the same name, or if the hash value is different and there is a version update, the required resources (resources) of the software that can be provided are compared with the available resource list of the client computer sent, and transfer is possible Is checked (ST405). If available, this software is added to the transfer software list (ST406).
The above processing (ST402 to ST407) is repeated for all software included in the software list 10 that can be provided, and a transfer software list is created. If there is no element in the transfer software list and there is no software to be transferred, the processing of the server computer 1 is ended (ST204). If there is software to be transferred, server computer 1 transmits the software included in the transfer software list to client computer 2 (ST205).
[0033]
The client computer 2 receives each software and stores it in the storage means 5 (ST306). At the same time, the received software list is updated.
Finally, the client computer 2 can use the transferred software by performing software installation processing such as registering software icons and starting an installer (ST307).
[0034]
As described above, in this embodiment, the server computer mainly receives the list of received software from the client computer, compares the software included in this list with the software that can be provided by the hash value, and the identity. Make a decision. Since comparison is performed using only a short hash value without transferring the data body, double transfer of the data body can be prevented, and useless transfer can be prevented.
Further, the server computer receives the available resource list prepared for each server from the client computer, and compares this with the resource information required by the software to be transferred, and determines whether transfer is possible in advance. it can.
[0035]
【The invention's effect】
  As described above, the present inventionEmbodimentAccording to the present invention, the use restricted resource table describing the available resource list is provided for each transfer source computer, and the resource use availability determination processing step for checking whether this condition is met is provided. It has the effect of blocking software, preventing unnecessary transfers and improving security.
[0036]
Furthermore, since the identity determination of the software to be transferred is performed with the hash value that is a compressed value, it is possible to prevent the transfer of the same version of the software and reduce the traffic and communication time.
[Brief description of the drawings]
FIG. 1 is a flowchart showing details of a received software selection processing step in Embodiment 1 of the present invention.
FIG. 2 is a flowchart showing further details of a step of determining whether the necessary resources in FIG. 1 are available.
FIG. 3 is a flowchart showing further details of an available resource list creation step in FIG. 1;
FIG. 4 is a configuration diagram of a software transfer system including a server computer and a client computer via a network according to the present invention.
FIG. 5 is a diagram showing an example of a software list 10 that can be provided in a server computer according to the first and second embodiments.
6 is a diagram showing an example of a received software list 11 in a client computer according to Embodiment 1 and Embodiment 2. FIG.
FIG. 7 is a diagram showing an example of a use restricted resource information table 12 in the client computer in the first embodiment and the second embodiment.
FIG. 8 is a communication sequence diagram between a server and a client during software transfer according to Embodiment 1 of the present invention.
FIG. 9 is an operation flowchart showing overall basic processing performed by the client computer 2 according to Embodiment 1 of the present invention;
FIG. 10 is a communication sequence diagram between a server and a client during software transfer according to Embodiment 2 of the present invention.
FIG. 11 is an operation flowchart showing overall basic processing performed by the server computer 1 according to Embodiment 2 of the present invention.
FIG. 12 is an operation flowchart illustrating overall basic processing performed by the client computer 2 according to the second embodiment.
13 is a flowchart showing details of a transfer software selection processing step in FIG. 11. FIG.
FIG. 14 is a diagram illustrating a conventional software transfer method using online loading.
FIG. 15 is a communication sequence diagram in conventional online loading.
FIG. 16 is a diagram showing an example of an available resource list in the first embodiment and the second embodiment.
[Explanation of symbols]
1 server computer, 2 client computer, 3 network, 4 software transfer server processing means, 5 storage means, 6 communication means, 7 software transfer client processing means, 8 display means, 9 operation means, 10 list of available software, 10-2 Hash Value, 11 Received Software List, 11-2 Hash Value, 12 Usage Restricted Resource Information Table, 12-1 Available Resource, ST101-1 Available Resource List Creation Step, ST105 Judge Whether Necessary Resource is Available (Resource Usage Acceptability determination process) step.

Claims (2)

A server computer for transferring software over a network;
In a software transfer system comprising a client computer having resources used by software,
The server computer
Storage means for storing software that uses a predetermined resource as a required resource at the time of execution;
A list of software that can be provided that describes the software names of the software stored in the storage means and the necessary resources used by the software;
Software transfer server processing means for controlling the transfer of software;
Server communication means for communicating with a client computer via a network,
The client computer
A resource information table for storing resource information indicating allocated resources allocated to the server computer among the resources of the client;
Software transfer client processing means for controlling the transfer of software;
Client communication means for communicating with a server computer via a network,
The client computer
The client communication means receives the software list that can be provided from the server computer,
The software transfer client processing means compares the necessary resource of the software described in the available software list with the allocated resource indicated by the resource information stored in the resource information table, and sends it to the server computer that has transmitted the available software list. Determining whether the corresponding allocated resource satisfies the necessary resource of the software described in the list of available software,
The client communication means requests the server computer as transfer request software for software in which the allocated resource satisfies the required resource,
The server computer
The software transfer server processing means selects the requested software as the transfer request software from the software stored in the storage means as the transfer software,
A software transfer system, wherein the transfer software is transmitted to the client computer by server communication means. The above list of available software is
Enter the software hash value along with the software name and required resources of the software,
The client computer further includes:
It has a received software list that includes the software name of the installed software and the hash value of the installed software,
The client computer
Software whose software name and hash value listed in the list of available software are the same as the software name of installed software and the hash value of installed software listed in the received software list. 2. The software transfer system according to claim 1, wherein the software transfer system is excluded from the transfer request software.

Images