JP2011180724A - Method and system for distributing resource - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce power consumption of a relay server by enabling the relay server in which a power supply is turned off when the relay server is not in use to be started when in use concerning a technique for distributing various sorts of files from a resource distribution server to distribution destination equipment through the relay server. <P>SOLUTION: When a resource request to the relay server SV-A comes into time-out state, the distribution destination equipment SV-A1 issues a resource request to the resource distribution server 100. The resource distribution server 100 receives the resource request, divides files to be distributed and successively transmits the divided files. The resource distribution server 100, when detecting deviation from a threshold of its own data transmission capacity, issues power supply start instruction to the relay server SV-A selected in accordance with the distribution destination equipment SV-A1 and continues transmission operation of the divided files. The resource distribution server 100, when receiving a power supply start completion notification from the relay server SV-A, transmits transfer information to the server SV-A and ends the transmission operation of the files to be distributed. The started relay sever SV-A takes over the transmission of divided files to the distribution destination equipment SV-A1. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for distributing various files from a resource distribution server to a distribution destination device via a relay server.

  In the resource distribution system, a correction program and a definition file (hereinafter referred to as “distribution target file”) are distributed from the resource distribution server to each server / client (hereinafter referred to as “distribution destination device”) that constitutes the system. By applying corrections, etc., the files distributed to each distribution destination device are maintained.

  Such a resource distribution system is applied to maintenance of various program files and data files that operate in, for example, bank ATM terminal devices, automatic transaction devices, POS devices, and the like.

In the resource distribution system, a relay server is installed between the resource distribution server and the distribution destination device under the following conditions.
-If the number of distribution destination devices that are distribution destinations is large and the distribution time is limited due to system requirements, install relay servers and distribute the processing of resource distribution servers.
-If there are many delivery destination devices in places where the amount of communication is limited by the network, such as in remote locations, a relay server is installed in the remote location to reduce the amount of communication.

  FIG. 25 is a configuration diagram of a resource distribution system in which a relay server is installed. A relay server 2503 is installed between the resource distribution server 2501 and the distribution destination device 2502. In this case, the distribution destination device 2502 defined under the relay server 2503 needs to be determined in advance and is fixed. For example, the distribution destination devices 2502 that distribute from the relay server 2503 (SV-A) are SV-A1, SV-A2, and SV-A3, and cannot be distributed to SV-B1.

FIG. 26 is an explanatory diagram of the basic operation of the resource distribution system, and shows a general flow of resource distribution. The flow of the resource distribution operation is as follows.
Step 1: A distribution target file (denoted as “modified PG” in the figure) is distributed from the resource distribution server 2501 to the relay server 2503.
Step 2: The distribution destination device 2502 makes an inquiry to the relay server 2503, and if there is a distribution target file to be applied to itself, download is performed. The execution trigger of step 2 is determined by system characteristics. For example, when the server is started or manually triggered by the operator.

JP 2004-178031 A JP 2002-124945 A JP-A-9-160820 JP 2007-58729 A

  However, the relay server 2503 in the above-described conventional resource distribution system is not used unless resource distribution is performed, so that it is unused and has a lot of time for activation, and the corresponding power consumption is wasted. Had problems.

  Therefore, an object of the present invention is to reduce the power consumption of the relay server by turning off the power supply of the relay server when not in use and enabling the relay server to be activated appropriately when in use.

In one example, this is realized as a resource distribution method for distributing a distribution target file from a resource distribution server to a distribution destination device via a relay server, and has the following configuration.
First, during normal times, the relay server is powered off.

The distribution destination device issues a resource request for the distribution target file to the relay server to which the own device belongs when a distribution trigger for the distribution target file occurs.
When the resource request times out, the distribution destination device issues the resource request to the resource distribution server again.

Next, when the resource distribution server receives a resource request from the distribution destination device, the resource distribution server sequentially transmits the divided files of the distribution target file to the distribution destination device.
The resource distribution server detects whether its own device does not violate the threshold of the data transmission capability, and when it detects the violation of the threshold, it selects it corresponding to the distribution destination device that is currently performing transmission A power activation instruction is issued to the relay server, and the transmission operation of the distribution target file to the distribution destination device is continued.

  When the resource distribution server receives a power-on completion notification from the relay server, the resource distribution server transmits to the relay server the takeover information of the distribution target file currently being transmitted to the distribution destination device and the distribution target file transmission operation. Exit.

When the power supply control device connected to the relay server receives a power supply start instruction, it starts supplying power to the relay server and starts the relay server.
When the activation of the own device is completed, the relay server transmits an activation completion notification to the resource distribution server.

  When the relay server receives the transfer information from the resource distribution server, the relay server determines the transmission start file in the distribution target file and the address of the distribution destination device based on the transfer information, and determines the split file in the distribution target file after the transmission start file. Start transmission to the distribution destination device.

  The distribution destination device receives the respective divided files in the distribution target file transmitted from the resource distribution server or the relay server, and combines the received divided files to complete the reception of the distribution target file.

  According to the present invention, it is possible to reduce the power consumption of the relay server. For example, in the case of a resource distribution system in which distribution processing of distribution target files is concentrated in one hour at the start of business, the power consumption for the number of servers per day × 23 hours is reduced.

It is a functional block diagram of a delivery destination apparatus. It is a functional block of a resource distribution server. It is a functional block diagram of a relay server. It is explanatory drawing (the 1) of the basic operation | movement of this embodiment. It is explanatory drawing (the 2) of the basic operation | movement of this embodiment. It is explanatory drawing (the 3) of basic operation | movement of this embodiment. It is explanatory drawing (the 4) of basic operation | movement of this embodiment. It is explanatory drawing (the 5) of basic operation | movement of this embodiment. It is explanatory drawing (the 6) of the basic operation | movement of this embodiment. It is an operation | movement flowchart which shows the control operation | movement of a delivery destination apparatus. It is an operation | movement flowchart which shows the control operation | movement of a resource delivery server. It is an operation | movement flowchart which shows the control operation of a relay server. It is a figure which shows the message | telegram format of this embodiment. It is a figure which shows the example of an operation sequence at the time of normal time (at the time of a relay server power-off). It is a figure which shows the example of the data flow at the time of normal time (at the time of a relay server power-off). It is a figure which shows the operation | movement sequence example (the 1) at the time of distribution origin server switching. It is a figure which shows the operation | movement sequence example (the 2) at the time of a distribution origin server switch. It is a figure which shows the example of the flow of data at the time of a distribution origin server switch. It is a figure which shows the example of an operation | movement sequence at the time of relay server starting. It is explanatory drawing of the power activation process of a relay server. It is explanatory drawing of the power-off process of a relay server. It is a data block diagram of a base connection multiplicity table and a distribution destination device list. 12 is an operation flowchart showing a more detailed control operation of the threshold violation detection process in step S1106 of FIG. It is a hardware block diagram of the computer which can apply this embodiment. It is a block diagram of a resource delivery system. It is explanatory drawing of the basic operation | movement of a resource delivery system.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings.
The configuration of the resource delivery system in this embodiment is the same as that shown in FIG. However, in the following description, the resource distribution server 2501 in FIG. 25 is referred to as the resource distribution server 200, the distribution destination device 2502 is referred to as the distribution destination device 100, and the relay server 2503 is referred to as the relay server 300.

  FIG. 1 is a functional block diagram of the distribution destination device 100. The functional block configuration of the distribution destination device 100 in FIG. 1 is realized as an operation in which the CPU 2401 is stored in the memory 2402 and executes the control program in a computer system having a hardware configuration as shown in FIG.

  In FIG. 1, when a distribution trigger of file data occurs in the distribution destination device 100, the data transmission request control unit 101 first issues a resource request regarding a distribution target file to the relay server 300 to which the data transmission request control unit 101 belongs. At this time, the resource request timer unit 102 is activated.

  The data transmission request destination control unit 103 monitors the resource request timer unit 102 to determine whether the resource request issued from the data transmission request destination control unit 103 to the relay server 300 has timed out.

  When the resource request does not time out and a response is received from the relay server 300, the data reception control unit 104 receives the data of the distribution target file sent from the relay server 300.

  When the resource request times out and there is no response from the relay server 300, the data transmission request destination control unit 103 causes the data transmission request control unit 101 to reissue the resource request to the resource distribution server 200. Thereafter, the data reception control unit 104 receives the distribution target file data transmitted from the resource distribution server 200. The data reception control unit 104 continues to receive the distribution target file as it is even when the transmission source of the distribution target file is switched from the resource distribution server 200 to the relay server 300 in the middle.

  FIG. 2 is a functional block diagram of the resource distribution server 200. The functional block configuration of the resource distribution server 200 in FIG. 2 is realized as an operation in which the CPU 2401 is stored in the memory 2402 and executes the control program in a computer system having a hardware configuration as shown in FIG.

  In FIG. 2, the data transmission request reception control unit 201 receives a resource request transmitted from the data transmission request control unit 101 of the distribution destination device 100, and thereafter, the data transmission control unit 202 sends a request to the distribution destination device 100. The divided files of the distribution target file requested in this way are sent sequentially.

  The threshold violation detection unit 203 detects whether or not the transmission operation by the data transmission control unit 202 violates a threshold of data transmission capability that can be transmitted by the resource distribution server 200. When the threshold violation detecting unit 203 detects a threshold violation, the relay server activation control unit 204 issues a power activation instruction to the relay server 300 to which the distribution destination device 100 currently executing transmission belongs. During this time, the data transmission control unit 202 continues the operation of transmitting the split file of the distribution target file to the distribution destination device 100.

  When the relay server activation control unit 204 receives the power activation completion notification from the relay server 300, the relay server activation control unit 204 transmits to the relay server 300 transfer information of the distribution target file currently being transmitted to the distribution destination device 100, and the data The transmission control unit 202 terminates the transmission operation. This takeover information includes the address of the delivery destination device 100 to be taken over and information on the transmission start file in the delivery target file.

  FIG. 3 is a functional block diagram of the relay server 300. The functional block configuration of the relay server 300 in FIG. 3 is realized as an operation in which the CPU 2401 is stored in the memory 2402 and executes the control program in a computer system having a hardware configuration as shown in FIG. However, the power supply control device 301 is realized as dedicated power supply control hardware different from the hardware configuration of FIG.

  In FIG. 3, when the relay server 300 is in a power-off state, the power control apparatus 301 receives a power activation instruction from the resource distribution server 200, turns on the relay server 300, and sets the operating system of the relay server 300. to start. When the power-on is completed, the relay server 300 automatically transmits a power activation completion notification to the resource distribution server 200 by a function not shown in particular. The power control device 301 also accepts a power-on instruction based on a manual operation or a predetermined schedule operation, and powers on the relay server 300.

  The transmission takeover control unit 302 accepts takeover information of the distribution target file transmitted from the resource distribution server 200 after the power is turned on. Thereafter, the transmission handover control unit 302 determines the transmission start file in the distribution target file divided into a plurality of addresses and the address of the distribution destination device 100, and issues a transmission instruction to the data transmission control unit 202.

  The data transmission control unit 202 starts transmission of the divided file from the transmission start file instructed from the transmission takeover control unit 302 to the distribution destination device 100 instructed from the transmission takeover control unit 302.

  On the other hand, the data transmission request reception control unit 304 receives a resource request transmitted from the data transmission request control unit 101 of the distribution destination device 100 while the relay server 300 itself is running. When this resource request is received, thereafter, the data transmission control unit 202 sequentially transmits the requested divided files of the distribution target file to the distribution destination device 100.

The basic operation of the embodiment of the resource distribution system having the above configuration will be described with reference to the operation explanatory diagrams of FIGS.
First, as shown in FIG. 3, the relay server 300 is equipped with the hardware of the power supply control device 301. In normal times, the relay server 300 is turned off.

  In this state, for example, when a resource request is generated, the distribution destination device 100 (SV-A1) first transmits the resource request, as indicated by S401 in FIG. 4, to the relay server 300 (SV-A) to which it belongs. )

  When the relay server 300 (SV-A) is not responded due to power interruption, the distribution destination device 100 (SV-A1) transmits a resource request to the resource distribution server 200 as shown in S402 of FIG. The distribution server 200 starts transmitting a distribution target file to the distribution destination device 100.

Here, in the resource distribution server 200, the maximum connection multiplicity between the distribution destination devices 100 with the resource distribution server 200 is set as the allowable range of the communication load.
Other distribution destination devices 100 connect to the resource distribution server 200 in the same manner as described above.

  In the resource distribution server 200, when the number of connections to the distribution destination device 100 is small, transmission of the distribution target file from the resource distribution server 200 to the distribution destination device 100 is continued as it is.

  When the number of distribution destination devices 100 to which the resource distribution server 200 is connected exceeds the maximum connection multiplicity, the resource distribution server 200 notifies the power supply control device 301 of the relay server 300 as, for example, S501 in FIG. Instruct to start the power supply. The relay server 300 to be activated is the relay server 300 (SV-A) to which the maximum number of distribution destination devices 100 currently connected belong.

After confirming the activation completion notification from the relay server 300, the resource distribution server 200 releases the connection with the distribution destination device 100 belonging to the activated relay server 300.
For example, each distribution destination device 100 of SV-A1 and SV-A3 is connected to the relay server 300 (SV-A) and downloads the remaining divided files in the distribution target file, as shown as S601 in FIG. Start. In addition, when SV-A2 newly starts the distribution process as the distribution destination device 100 under SV-A, the SV-A relay server 300 is activated, and therefore, as shown in S602 of FIG. The distribution destination device 100 of -A2 starts the connection with the relay server 300 of SV-A as it is.

When all of the distribution processing of the distribution target file to each distribution destination device 100, SV-A1, SV-A2, and SV-A3 is completed, the SV-A relay server 300, as shown in S701 of FIG. Power off automatically.
In addition to the basic operation described above, in this embodiment, the resource distribution server 200 can set the maximum connection multiplicity as the allowable range of communication load with the remote site C.

  The SV-C1 of the distribution destination device 100 tries to connect to the SV-C of the relay server 300 at the resource request opportunity, but cannot connect due to the power failure, so that the resource distribution server 200 is shown as S801 in FIG. Connect to. Similarly, the distribution destination device 100 of the SV-C 2 is also connected to the resource distribution server 200.

  Since the number of connections of the distribution destination device 100 belonging to the remote site C exceeds the preset maximum multiplicity = 1, the resource distribution server 200 is connected to the SV-C of the relay server 300 installed at the remote site C. Instruct to start the power supply.

After confirming the activation completion notification of the SV-C relay server 300, the resource distribution server 200 releases the connection with each of the distribution destination devices 100 of SV-C1 and SV-C2. Each distribution destination device 100 of SV-C1 and SV-C2 is connected to the relay server 300 of SV-C as shown in S901 of FIG. 9, and continues to download the remaining divided files of the distribution target file.
The SV-C relay server 300 voluntarily turns off the power when the distribution processing of the distribution target files to the respective distribution destination devices 100, SV-C1, and SV-C2 is completed.

  FIG. 10 is an operation flowchart showing a control operation executed by the distribution destination device 100 in order to realize the functional block of FIG. This operation flowchart is realized as an operation in which the CPU 2401 executes a control program held in the memory 2402 in a computer system having the hardware configuration shown in FIG. 24, for example. The operation flowchart starts to be executed when a resource request opportunity for the distribution target file occurs in the distribution destination device 100.

First, a resource request timer is started (step S1001). This operation realizes the function of the resource request timer unit 102 of FIG.
Next, a data transmission request message is transmitted to the relay server (step S1002). This operation realizes the function of the data transmission request control unit 101 in FIG. The data transmission request message has, for example, a data format shown in FIG. The “own IP address” indicates the IP address of the distribution destination device 100 itself.

  Next, it is determined whether a data transmission start message has been received from the relay server 300 (step S1003). This operation realizes the function of the data transmission request control unit 101 in FIG.

  Next, when the determination in step S1003 is NO, it is determined whether or not the resource request timer has timed out (step S1004). This operation realizes the function of the data transmission request destination control unit 103 in FIG.

If the determination in step S1004 is NO, the process returns to step S1003 and a response from the relay server 300 is awaited.
In the repeat response waiting process in steps S1003 and S1004, if there is no response from the relay server 300 and the resource request timer times out and the determination in step S1004 is YES, the transmission destination of the data transmission request is changed from the relay server 300 to the resource distribution server 200. Changed to This operation realizes the function of the data transmission request destination control unit 103 in FIG.

That is, first, the resource request timer is restarted (step S1005). This operation realizes the function of the resource request timer unit 102 of FIG.
Next, a data transmission request message is transmitted to the resource distribution server (step S1006). This operation realizes the function of the data transmission request control unit 101 in FIG.

Next, it is determined whether or not a data transmission start message has been received from the resource distribution server 200 (step S1007).
If the determination in step S1007 is NO, it is determined whether the resource request timer has timed out (step S1008).

If the determination in step S1008 is YES, an error process corresponding to a communication failure is executed (step S1014).
If the determination in step S1008 is NO, the process returns to step S1007.

  When the data transmission start message is received from the resource distribution server 200 and the determination in step S1007 is YES in the repeat response waiting process of steps S1007 and S1008, the distribution target file is received from the resource distribution server 200 from the following step S1009 A series of processing up to S1013 is executed. This operation realizes the function of the data reception control unit 104 in FIG. Here, the data transmission start message has, for example, the data format of FIG. “Total data amount” is the total data amount of the distribution target file. “Checksum” is checksum information of a file before the distribution target file is divided and transmitted. “Number of divisions” is the number of divisions when the distribution target file is divided and transmitted. As described above, in this embodiment, a distribution target file that is a distribution resource is divided into a predetermined size, and the same file is stored in the resource distribution server 200 and the relay server 300. The checksum information of the file before division is also stored in the resource distribution server 200 and the relay server 300.

  First, it is determined whether or not a data transmission message has been received (step S1009). The data transmission message has a data format shown in FIG. “Division subscript” is information of a division number when the distribution target file is divided. “Division data X” is division file data obtained by dividing the distribution target file.

If the determination in step S1009 is NO, the determination in step S1009 is repeatedly executed to maintain the reception standby state.
If the determination in step S1009 is YES, a data transmission message reception process is executed (step S1010).

  Next, it is determined whether or not the received data transmission message is the final file (step S1011). This determination is made by comparing the “division subscript” in the data transmission message (see FIG. 13C) with the “number of divisions” in the data transmission start message received in step S1007 (see FIG. 13B). It is determined by doing.

If the determination in step S1011 is NO, the process returns to step S1009 and the data transmission message reception process is continued.
If the determination in step S1011 is YES, the data transmission message reception process ends, the received divided files are combined, and the distribution target file obtained as a result is included in the data transmission start message received in step S1007. It is compared with “checksum” (see FIG. 13B) (step S1012). As a result of this comparison, when it is determined that the distribution target file is not valid, a retransmission request process (not shown) is executed.

If it is determined in step S1012 that the distribution target file is valid, a reception result message is transmitted as a reception completion notification to the transmission source that transmitted the data transmission message of the final file (step S1013). The reception result message has a data format shown in FIG.
Thus, the distribution target file reception process by the distribution destination device 100 ends.

  In the repeat response waiting process of steps S1003 and S1004 described above, when the relay server 300 is activated and there is a response and the determination in step S1003 is YES, the process proceeds to a series of data reception processes from steps S1009 to S1013 described above. In this case, the distribution target file is received from the relay server 300. The operation here realizes the function of the data reception control unit 104 in FIG.

  FIG. 11 is an operation flowchart showing a control operation executed by the resource distribution server 200 in order to realize the functional blocks of FIG. 2 in the resource distribution server 200. This operation flowchart is realized as an operation in which the CPU 2401 executes a control program held in the memory 2402 in a computer system having the hardware configuration shown in FIG. 24, for example. And this operation | movement flowchart is always performed in parallel as multi-process processing which performs a process in parallel with respect to the request | requirement from the several delivery destination apparatus 100 in the resource delivery server 200. FIG.

  First, it is determined whether or not a data transmission request message has been received from the distribution destination device 100 (step S1101). This process realizes the function of the data transmission request reception control unit 201 in FIG.

If the determination in step S1101 is NO, the process in step S1101 is repeatedly executed to maintain a data transmission request reception standby state.
If the determination in step S1101 is YES, a data transmission start message (to the distribution destination device 100 corresponding to the “own IP address” (see FIG. 13A) in the data transmission request message received in step S1101). (See FIG. 13B) is transmitted (step S1102). The operation here realizes the function of the data transmission request reception control unit 201 in FIG. Here, the data transmission start message has, for example, the data format of FIG. As described above, “total data amount”, “checksum”, and “number of divisions” are transmitted.

  Thereafter, the division file of the distribution target file, which is a data transmission message (see FIG. 13C), is sequentially transmitted to the distribution destination device 100 (step S1103). This process realizes the function of the data transmission control unit 202 in FIG.

Next, it is determined whether transmission has been completed up to the final file (step S1104).
If the determination in step S1104 is NO, it is determined whether a threshold value violation is currently detected (step S1105). Initially, the determination in step S1104 is NO. As a result, threshold violation detection processing is executed (step S1106). The processes in steps S1105 and S1106 described above realize the function of the threshold violation detection unit 203 in FIG. Although details of this processing will be described later, this processing is processing for detecting whether or not the transmission operation by the data transmission control unit 202 violates the threshold value of the data transmission capability that the resource distribution server 200 can transmit.

As a result of step S1106, it is determined whether or not a threshold violation is detected (step S1107).
If no threshold violation is detected and the determination in step S1107 is NO, the process returns to step S1103, and the transmission process of the split file of the distribution target file is continued.
When a threshold violation is detected and the determination in step S1107 is YES, a power activation instruction is transmitted to the relay server 300 to which the distribution destination device 100 currently executing transmission belongs (step S1108).

  Thereafter, the process returns to step S1103 until the power-on completion notification is received from the relay server 300, and the transmission process of the split file of the distribution target file is continued. As a result, the distribution destination device 100 can continue to download the divided file of the distribution target file without interruption.

  After the determination in step S1107 is YES, the determination in step S1105 is YES. As a result, it is determined whether or not a power activation completion notification has been received from the relay server 300 (step S1109). This operation realizes the function of the relay server activation control unit 204 in FIG.

If the determination in step S1107 is NO, the process returns to step S1103 and the split file transmission process for the distribution target file is continued.
In the repetitive processing of Steps S1103 → S1104 → S1105 → S1109 → S1103, when a power activation completion notification is received from the relay server 300 and the determination in Step S1109 is YES, a transmission handover message is transmitted to the relay server 300 (Step S1103). S1110). This operation realizes the function of the relay server activation control unit 204 in FIG. The transmission handover message has a data format shown in FIG. 13D, for example. In FIG. 13D, “Destination IP address” indicates the IP address of the distribution destination device 100. “Number of divisions” indicates the number of file divisions of the distribution target file to be inherited. “Transmission completion division subscript” indicates the division number of the division file that has been transmitted by the transmission processing in the immediately preceding step S1103.

By the takeover process in step S1110, the data transmission in the resource distribution server 200 is completed, and the process returns to the reception waiting state for the transmission request message in step S1101.
In addition, in the repetitive processing of steps S1103 → S1104 → S1105 → S1109 → S1103, when transmission of the distribution target file up to the final divided file is completed and the determination in step S1104 is YES, a reception result message (figure of FIG. 13 (e)) is received, and the distribution target file transmission process is terminated (step S1111). Thereafter, the process returns to the reception waiting state for the transmission request message in step S1101.

  FIG. 12 is an operation flowchart illustrating a control operation executed by the relay server 300 in order to implement the functional blocks of FIG. This operation flowchart is realized as an operation in which the CPU 2401 executes a control program held in the memory 2402 in a computer system having the hardware configuration shown in FIG. 24, for example. This operation flowchart is always executed in parallel as multi-process processing in the relay server 300 that executes processing in parallel in response to requests from the resource distribution server 200 or the plurality of distribution destination devices 100.

  First, it is determined whether or not a transmission handover message (see FIG. 13D) has been received from the resource distribution server 200 (step S1201). This operation realizes the function of the transmission handover control unit 302 in FIG.

  If the determination in step S1201 is NO, it is determined whether or not a data transmission request message has been received from the distribution destination device 100 under its own apparatus (step S1202). This operation realizes the function of the data transmission request reception control unit 304 in FIG.

If the determination in step S1202 is also NO, the process returns to the determination in step S1201 again.
When a transmission handover message is received from the resource distribution server 200 and the determination in step S1201 is YES, a divided file whose transmission should be taken over in the distribution target file based on the “transmission completion division index” in the received transmission handover message A transmission start file is determined (step S1203). This operation realizes the function of the transmission handover control unit 302 in FIG.

  Then, sequentially from the transmission start file, the divided files in the distribution target file are transmitted to the distribution destination device 100 as a data transmission message (step S1204). The address of the distribution destination device 100 is the “destination IP address” in the transmission handover message received in step S1201. This operation realizes the function of the data transmission control unit 303 in FIG.

Next, it is determined whether or not up to the final file of the split file of the distribution target file has been transmitted (step S1205).
If the determination in step S1205 is NO, the process returns to step S1204 and data transmission is continued.

  If the determination in step S1205 is YES, a reception result message (see FIG. 13E) is received from the distribution destination device 100, and the distribution target file transmission process ends (step S1206).

Thereafter, the process returns to step S1201 and enters a standby state.
On the other hand, when the data transmission request message is received from the distribution destination device 100 and the determination in step S1202 becomes YES in the repetition of the reception standby processing in steps S1201 and S1202, the “self” in the data transmission request message received in step S1202 becomes YES. A data transmission start message (see FIG. 13B) is transmitted to the distribution destination device 100 corresponding to the “IP address” (see FIG. 13A) (step S1207). This operation realizes the function of the data transmission request reception control unit 304 in FIG. Here, the data transmission start message has, for example, the data format of FIG. As described above, “total data amount”, “checksum”, and “number of divisions” are transmitted.

  Subsequently, for the distribution destination device 100 corresponding to the “own IP address” (see FIG. 13A) in the data transmission request message received in step S1202, the first divided file in the distribution target file is sequentially Data transmission is instructed (steps S1207 → S1204). As a result, a normal distribution target file transmission process from the relay server 300 to the distribution destination device 100 is executed. This operation realizes the function of the data transmission control unit 303 in FIG.

  14 and 15 are diagrams showing an example of an operation sequence and an example of data flow at normal time (when the relay server power is turned off), which is realized based on the operation flowcharts of FIGS. 10 to 12 and the message format of FIG. It is.

  As an example of preconditions, the IP address of the distribution destination device 100 is “10.10.10.1,” the total data amount of the distribution target file is 3 Mbytes (megabytes), the checksum is “XYZ”, the number of divisions is 3, Assume that the data size is 1 Mbyte.

First, a data transmission request message is issued as a resource request from the distribution destination device 100 to the relay server 300 (S1401 in FIG. 14) (step S1002 in FIG. 10).
Due to the power-off of the relay server 300, a communication timeout is detected (S1402 in FIG. 14) (step S1004 in FIG. 10).

  A data transmission request message is issued as a resource request from the distribution destination device 100 to the resource distribution server 200 (S1403 in FIG. 14) (step S1006 in FIG. 10, step S1101 in FIG. 11). In the data transmission request message, as shown in FIG. 15A, the IP address “10.10.10.1” of the distribution destination device 100 is stored.

  The resource distribution server 200 transmits a data transmission start message to the distribution destination device 100 with this IP address (step S1102 in FIG. 11 and step S1007 in FIG. 10). In the data transmission start message, as shown in FIG. 15B, the total data amount = 3 Mbytes, the checksum = XYZ, and the number of divisions = 3 are stored.

  Subsequently, the resource distribution server 200 sequentially transmits the divided file of the distribution target file as a resource to the distribution destination device 100 that has requested the resource (S1404 in FIG. 14) (Steps S1103 and FIG. 10 in FIG. 11). Step S1010). The transmitted state is as shown in FIG.

  The distribution destination device 100 confirms that the file is the final file (S1405 in FIG. 14) (step S1011 in FIG. 10) based on the “division subscript” (see FIG. 13C) in the data transmission message.

In the distribution destination device 100, the received files are combined, and the validity of the distribution target file is confirmed by the checksum (S1406 in FIG. 14) (step S1012 in FIG. 10).
The distribution destination device 100 transmits a reception result message as a reception completion notification to the resource distribution server 200 that is the transmission source of the distribution target file (S1407 in FIG. 14) (step S1013 in FIG. 10). In this reception result message, as shown in FIG. 15D, the own IP address = 10.10.10.1 and the reception result = OK are stored.

  FIGS. 16, 17, and 18 are operation sequence examples (part 1 and part 2) and data when switching the distribution source server, which are realized based on the operation flowcharts of FIGS. 10 to 12 and the message format of FIG. It is a figure which shows the example of the flow of this.

Examples of preconditions are the same as those in FIG.
First, a data transmission request message is issued as a resource request from the distribution destination device 100 to the relay server 300 (S1601 in FIG. 16) (step S1002 in FIG. 10). This is the same as S1401 in FIG.

  Due to the power-off of the relay server 300, a communication timeout is detected (S1602 in FIG. 16) (step S1004 in FIG. 10). This is the same as S1402 in FIG.

  A data transmission request message is issued as a resource request from the distribution destination device 100 to the resource distribution server 200 (S1603 in FIG. 16) (step S1006 in FIG. 10, step S1101 in FIG. 11). In the data transmission request message, as shown in FIG. 18A, the IP address “10.10.10.1” of the distribution destination device 100 is stored. This is the same as S1403 in FIG.

  The resource distribution server 200 transmits a data transmission start message to the distribution destination device 100 with this IP address (step S1102 in FIG. 11 and step S1007 in FIG. 10). In the data transmission start message, as shown in FIG. 18B, the total data amount = 3 Mbytes, the checksum = XYZ, and the number of divisions = 3 are stored.

  Subsequently, the resource distribution server 200 sequentially transmits the divided file of the distribution target file as a resource to the distribution destination device 100 that has requested the resource (S1604 in FIG. 16) (steps S1103 and FIG. 10 in FIG. 11). Step S1010). This is the same as S1404 in FIG. The state of transmission is as shown in FIG.

  When a threshold violation that becomes a switching determination criterion in the resource distribution server 200 occurs at the start of distribution of the distribution target file or during distribution, the relay server 300 that is the activation destination is selected based on the violation event, and a power activation instruction is issued (S1605 in FIG. 16) (Steps S1107 → S1108 in FIG. 11).

  After completion of power activation at the relay server 300, an activation completion notification is transmitted to the resource distribution server 200 (S1606 in FIG. 16). Note that even during the activation of the relay server 300, transmission of the divided file of the distribution target file from the resource distribution server 200 to the distribution destination device 100 is continued (steps S1109 to S1103 in FIG. 11).

  The resource distribution server 200 that has received the activation completion notification finishes distributing the distribution target file to the distribution destination device 100, and relays the distribution status (up to which divided file has been distributed) using a transmission handover message. 300 (S1607 in FIG. 16) (step S1110 in FIG. 11). As shown in FIG. 18D, for example, the destination IP address = 10.10.10.1, the number of divisions = 3, and the transmission completion division subscript = 1 are stored in the transmission handover message. Transmission completion division subscript = 1 indicates that a threshold value violation has occurred when transmission of the first division file is completed.

  The relay server 300 receives the notification content of the transmission takeover message, determines how far the distribution has been completed from the transmission completion division subscript of the transmission takeover message, and distributes the file to be distributed from the relay server 300 to the distribution destination device 100. The remaining (unsent) divided files are transmitted to the distribution destination device 100 (S1608 in FIG. 16) (steps S1201 → S1203 → S1204 in FIG. 12). In the example of FIG. 18D, since the transmission of the first divided file is completed, the second and subsequent divided files are transferred from the relay server 300 to the distribution destination device 100 as shown in FIG. To be distributed.

  The distribution destination device 100 confirms that the file is the final file based on the “division subscript” (see FIG. 13C) in the data transmission message (S1609 in FIG. 16) (step S1011 in FIG. 10).

In the distribution destination device 100, the received files are combined, and the validity of the distribution target file is confirmed by a checksum (S1610 in FIG. 17) (step S1012 in FIG. 10).
The distribution destination device 100 transmits a reception result message that is a reception completion notification to the relay server 300 that is the current transmission source of the distribution target file (S1611 in FIG. 17) (step S1013 in FIG. 10). In this reception result message, as shown in FIG. 18 (f), own IP address = 10.10.10.1 and reception result = OK are stored.

  A check is performed on the relay server 300 to determine whether the distribution target file, which is a resource for other devices, has been distributed. If not, a notification that the relay server 300 itself will be disconnected is sent to the resource distribution server 200. And turn off its own power (S1612 in FIG. 17).

FIG. 19 is a diagram illustrating an example of an operation sequence when the relay server is activated, which is realized based on the operation flowcharts of FIGS. 10 to 12 and the message format of FIG.
Examples of preconditions are the same as those in FIG.

First, a data transmission request message is issued as a resource request from the distribution destination device 100 to the relay server 300 (S1901 in FIG. 19) (step S1002 in FIG. 10).
The active relay server 300 transmits a data transmission start message to the distribution destination device 100 having this IP address (step S1207 in FIG. 12, step S1007 in FIG. 10).

  Subsequently, the relay server 300 sequentially transmits the division file of the distribution target file as a resource to the distribution destination device 100 that has requested the resource (S1902 in FIG. 19) (Step S1204 in FIG. 12, FIG. 10). Step S1010).

  The distribution destination device 100 confirms that the file is the final file based on the “division subscript” (see FIG. 13C) in the data transmission message (S1903 in FIG. 19) (step S1011 in FIG. 10).

In the distribution destination device 100, the received files are combined, and the validity of the distribution target file is confirmed by a checksum (S1904 in FIG. 19) (step S1012 in FIG. 10).
The distribution destination device 100 transmits a reception result message that is a reception completion notification to the relay server 300 that is the transmission source of the distribution target file (S1905 in FIG. 19) (step S1013 in FIG. 10).

  A check is performed on the relay server 300 to determine whether the distribution target file, which is a resource for other devices, has been distributed. If not, a notification that the relay server 300 itself will be disconnected is sent to the resource distribution server 200. And turn off its own power (S1906 in FIG. 19).

FIG. 20 is an explanatory diagram of the power activation process of the relay server 300.
As described above as step S1108 in FIG. 11, when the resource distribution server 200 detects a threshold violation, the resource distribution server 200 transmits a power activation instruction to the relay server 300 to which the distribution destination device 100 currently performing transmission belongs. More specifically, as shown in FIG. 20, a power activation instruction is issued from the resource distribution server 200 to the power control device 301 (see FIG. 3) connected to the relay server 300 via the network. A command 2001 is input.

As a result, the power supply control device 301 starts supplying power from the distribution board to the relay server 300 (2002 in FIG. 20).
As a result, the relay server 300 starts activation of the operating system (OS) (2003 in FIG. 20).

Although not particularly illustrated, when the operating system is activated, the relay server 300 transmits an activation completion notification to the resource distribution server 200.
FIG. 21 is an explanatory diagram of the power-off process of the relay server 300.

  When the relay server 300 determines that it can turn off the power (S1612 in FIG. 17 and S1906 in FIG. 19), it sends a power-off request to the power supply control device 301 as a message using the RS-232C interface. (2101 in FIG. 21).

Thereafter, the relay server 300 starts a shutdown process of the operating system (2102 in FIG. 21).
After receiving the power-off request, the power supply control device 301 waits for a certain time (the time when the relay server 300 shuts down), and then cuts off the power supply to the relay server 300 (2103 in FIG. 21).

Details of the threshold violation detection process in step S1106 of FIG. 11 in the resource distribution server 200 will be described below.
In the resource distribution system as shown in FIG. 25, the line speed used for communication between the resource distribution server 200 and each relay server 300 may be different for each site. Therefore, it is assumed that each site has a condition of connection multiplicity between the resource distribution server 200 and each relay server 300.

The resource distribution server 200 holds the following information exemplified as Table 1 in FIG. 22A and Table 2 in FIG.
Base connection multiplicity table (Table 1): The maximum connection multiplicity is managed for each base.
Distribution destination device list (Table 2): A list of distribution destination devices installed at each site is managed.

In step S1106 in FIG. 11, the base where the currently connected distribution destination device 100 is installed is acquired from the distribution destination device list (Table 2) illustrated in FIG. Whether the connection multiplicity between the distribution server 200 and the distribution destination device 100 in the base exceeds the maximum connection multiplicity managed in the base connection multiplicity table (Table 1) illustrated in FIG. Check regularly.
When the maximum connection multiplicity is exceeded, the relay server 300 installed at the base is activated.

FIG. 23 is an operation flowchart showing a more detailed control operation of the threshold violation detection process in step S1106 of FIG. 11 based on the basic operation described above.
First, it is determined whether or not the distribution destination device 100 connected to the resource distribution server 200 has exceeded the maximum connection multiplicity (step S2301).

If the determination in step S2301 is YES, a power activation instruction is transmitted to the relay server 300. The relay server 300 to be activated is the relay server 300 to which the maximum number of distribution destination devices 100 currently connected belong (step S2302).
In the case of determination NO in step S2301, it is determined whether the number of connections of the distribution destination device 100 to which the resource distribution server 200 belongs to the remote base has exceeded the maximum multiplicity (step S2303).

If the determination in step S2303 is YES, the resource distribution server 200 transmits a power activation instruction to the corresponding relay server 300 installed in the remote site (step S2304).
In the case of determination NO in step S2303, it is determined whether or not the CPU usage rate of the resource distribution server 200 exceeds a specified value (step S2305).

  When downloading a distribution target file, which is a resource, from the resource distribution server 200 to the distribution destination device 100, the processing load on the resource distribution server 200 increases, and the CPU usage rate of the resource distribution server 200 may exceed a specified value. is there. When the determination in step S2305 is YES in this manner, a power activation instruction is transmitted to the relay server 300. The relay server 300 to be activated is the relay server 300 to which the maximum number of distribution destination devices 100 currently connected belong (step S2306).

In the case of determination NO in step S2305, it is determined whether or not the response time of the resource distribution server 200 has exceeded a specified value (step S2307).
When the resource distribution server 200 transmits a distribution target file, which is a resource, to the distribution destination device 100, the processing load on the resource distribution server 200 increases, and the resource distribution server 200 is in a state with no time response. There is. In this way, when the determination in step S2307 is YES, a power activation instruction is transmitted to the relay server 300. The relay server 300 to be activated is the relay server 300 to which the maximum number of distribution destination devices 100 currently connected belong (step S2308).

In the case of determination NO in step S2307, it is determined whether or not the packet communication error rate of the resource distribution server 300 has exceeded a specified value (step S2309).
When downloading a distribution target file, which is a resource, from the resource distribution server 300 to the distribution destination device 100, a communication error rate in a predetermined time is specified in a packet transmitted from the resource distribution server 300 due to a problem such as network congestion. The value may be exceeded. When the determination in step S2309 is YES in this manner, a power activation instruction is transmitted to the relay server 300. The relay server 300 to be activated is the relay server 300 to which the maximum number of distribution destination devices 100 currently connected belong (step S2310).

In the case of determination NO in step S2309, it is determined that no threshold violation has occurred, and the process of step S1106 in FIG. 11 is terminated.
According to the present embodiment described above, the power consumption of the relay server 300 can be reduced. For example, in the case of a resource distribution system in which distribution processing of distribution target files is concentrated in one hour at the start of business, the power consumption for the number of servers per day × 23 hours is reduced.

  FIG. 24 is a diagram illustrating an example of a hardware configuration of a computer capable of realizing the distribution destination device 100, the resource distribution server 200, or the relay server 300 in the resource distribution system.

  The computer shown in FIG. 24 includes a CPU 2401, a memory 2402, an input device 2403, an output device 2404, an external storage device 2405, a portable recording medium driving device 2406 into which a portable recording medium 2409 is inserted, and a network connection device 2407. However, these are connected to each other by a bus 2408. The configuration shown in the figure is an example of a computer that can implement the above system, and such a computer is not limited to this configuration.

  The CPU 2401 controls the entire computer. The memory 2402 is a memory such as a RAM that temporarily stores a program or data stored in the external storage device 2405 (or portable recording medium 2409) when executing a program, updating data, or the like. The CUP 2401 performs overall control by reading the program into the memory 2402 and executing it.

  The input device 2403 includes, for example, a keyboard, a mouse, etc. and their interface control devices. The input device 2403 detects an input operation by the user using a keyboard, a mouse, or the like, and notifies the CPU 2401 of the detection result.

  The output device 2404 includes a display device, a printing device, etc. and their interface control devices. The output device 2404 outputs data sent under the control of the CPU 2401 to a display device or a printing device.

The external storage device 2405 is, for example, a hard disk storage device. Mainly used for storing various data and programs.
The portable recording medium driving device 2406 accommodates a portable recording medium 2409 such as an optical disk, SDRAM, or Compact Flash (registered trademark), and has an auxiliary role for the external storage device 2405.

The network connection device 2407 is a device for connecting, for example, a LAN (local area network) or WAN (wide area network) communication line.
The system according to the present embodiment is realized by the CPU 2401 executing a program equipped with the functions shown in the aforementioned operation flowcharts. The program may be recorded and distributed in the external storage device 2405 or the portable recording medium 2409, for example, or may be acquired from the network by the network connection device 2407.

DESCRIPTION OF SYMBOLS 100 Distribution destination apparatus 101 Data transmission request control part 102 Resource request timer part 103 Data transmission request destination control part 104 Data reception control part 200 Resource distribution server 201, 304 Data transmission request reception control part 202, 303 Data transmission control part 203 Threshold violation Detection unit 204 Relay server activation control unit 300 Relay server 301 Power supply control device 302 Transmission takeover control unit

Claims (6)

In a resource distribution method for distributing a distribution target file from a resource distribution server to a distribution destination device via a relay server,
Normally, the relay server is turned off,
The distribution destination device issues a resource request for the distribution target file to the relay server to which the own device belongs when a distribution trigger for the distribution target file occurs,
When the resource request times out, the distribution destination device issues a resource request to the resource distribution server again,
When the resource distribution server receives the resource request from the distribution destination device, the resource distribution server sequentially transmits the divided files of the distribution target file to the distribution destination device,
The resource distribution server detects whether its own device does not violate a threshold of data transmission capability, and selects a corresponding to a distribution destination device that is currently performing transmission when the violation of the threshold is detected Issue a power activation instruction to the relay server, and continue the transmission operation of the split file of the distribution target file to the distribution destination device,
When the resource distribution server receives a power-up completion notification from the relay server, the resource distribution server transmits to the relay server the takeover information of the distribution target file currently being transmitted to the distribution destination device, and the distribution Finish sending the target file,
When the power supply control device connected to the relay server receives the power supply start instruction, the power supply control device starts supplying the power to the relay server and starts the relay server,
When the relay server completes startup of its own device, it sends a startup completion notification to the resource distribution server,
When the relay server receives the transfer information from the resource distribution server, the relay server determines the transmission start file in the distribution target file and the address of the distribution destination device based on the transfer information, and distributes the distribution after the transmission start file. Start sending the split file in the target file to the destination device,
The distribution destination device receives each divided file in the distribution target file transmitted from the resource distribution server or the relay server, and combines the received divided files to complete reception of the distribution target file.
A resource distribution method characterized by that. When the resource distribution server detects a violation of the threshold, the resource distribution server selects an optimal relay server corresponding to the distribution destination device of the connection destination according to the number of distribution destination devices currently connected and the load state of the own device. And transmits a power-on activation instruction to the relay server.
The resource delivery method according to claim 1. When the resource distribution server detects a violation of the threshold, the optimal distribution server corresponding to the distribution destination device of the connection destination according to the number of distribution destination devices currently connected and the network status of the distribution destination device And transmits a start instruction for the power supply to the relay server.
The resource delivery method according to claim 1. In a resource distribution system that distributes a distribution target file from a resource distribution server to a distribution destination device via a relay server,
Normally, the relay server is turned off,
In the distribution destination device,
A data transmission request control unit that issues a resource request regarding the distribution target file to the relay server to which the own device belongs when a distribution trigger for the distribution target file occurs;
A data transmission request control unit for causing the data transmission request control unit to reissue a resource request to the resource distribution server when the resource request times out;
A data reception control unit that receives each divided file in the distribution target file transmitted from the resource distribution server or the relay server, and combines the received divided file to complete reception of the distribution target file;
Including
In the resource distribution server,
A data transmission request reception control unit for receiving the resource request from the distribution destination device;
A data transmission control unit that sequentially transmits the split file of the distribution target file to the distribution destination device when the resource request is received;
A threshold value violation detection unit for detecting whether or not the own device does not violate the threshold value of the data transmission capability;
When a violation of the threshold is detected, a power activation instruction is issued to the relay server selected corresponding to the distribution destination device that is currently performing transmission, and the distribution is sent to the data transmission control unit. When the transmission operation of the split file of the distribution target file to the destination device is continued and a power-up completion notification is received from the relay server, the distribution target currently being transmitted to the distribution destination device is sent to the relay server A relay server activation control unit that transmits file takeover information and causes the data transmission control unit to end the transmission operation of the distribution target file;
Including
The relay server is
Upon receiving the power activation instruction from the resource distribution server, a power control device that starts and starts the supply of power to the own device, and transmits a completion notification to the resource distribution server when the activation is completed;
When the takeover information is received from the resource delivery server, a transmission start file in the delivery target file and an address of the delivery destination device are determined based on the takeover information,
A data transmission control unit that executes transmission of the divided file in the distribution target file after the transmission start file to the address of the distribution destination device;
A resource distribution system characterized by including: When the relay server activation control unit detects a violation of the threshold, the relay server activation control unit corresponds to the distribution destination device of the connection destination according to the number of distribution destination devices currently connected and the load state of the own device. And transmits a start instruction for the power supply to the relay server.
The resource distribution system according to claim 4. When the relay server activation control unit detects violation of the threshold value, the relay server activation control unit is optimally adapted to the distribution destination device of the connection destination according to the number of distribution destination devices currently connected and the network status of the distribution destination device. Select a relay server, and send a power-on start instruction to the relay server.
The resource distribution system according to claim 4.