JP6129698B2 - Software distribution system and software distribution method - Google Patents

Description

  The present invention relates to a software distribution system and a software distribution method.

  2. Description of the Related Art Conventionally, when distributing software from a server to a client, there is a technique for redistributing the software when it cannot be distributed due to circumstances on the client side. For example, in Patent Document 1, when the server distributes distribution information, when a redistribution request is received from the MFP, the data is returned to the checkpoint by rollback and the data is returned to the checkpoint. A technique for resuming processing from the above is disclosed.

JP 2008-24206 A

  In Patent Document 1 described above, when the MFP requests redistribution of distribution information, the distribution information is redistributed by returning the processing to a checkpoint where data consistency is confirmed. Therefore, for example, when the size of the transmission file is excessive with respect to the line, the line becomes overloaded, the transmission file is not correctly distributed, and the client has to make a redistribution request again. Such problems become more prominent because the number of transmission files increases as the number of clients to which transmission files are distributed increases. Considering distribution conditions such as the size of transmission files and bandwidth of lines. It was desired to distribute transmission files with priorities.

  The present invention has been made in view of the above, and provides a software distribution system and a software distribution method capable of distributing a transmission file with priority given in consideration of distribution conditions. Objective.

  In order to solve the above-described problems and achieve the object, a software distribution system according to the present invention is a software distribution system in which a distribution server distributes data to a plurality of terminals via a network, the network and the data A software distribution system comprising: an order determination unit that determines a distribution order of the data based on a plurality of distribution conditions; and a distribution unit that distributes the data to the terminal in a predetermined distribution order Is done.

  The present invention also relates to a software distribution method performed by the software distribution system.

  According to the present invention, a transmission file can be distributed after priorities are set in consideration of distribution conditions.

1 is a configuration diagram showing an embodiment of a software distribution system. It is a figure which shows the structural example of a distribution error table. It is a figure which shows the structural example of a redistribution destination table. It is a flowchart which shows the process sequence of a data redistribution process. It is a figure which shows a mode that the condition calculation part produced | generated the redistribution destination division | segmentation table. It is a figure which shows a mode that a condition calculation part calculated (distribution size / bandwidth) and added the item to the redistribution destination division | segmentation table. It is a figure which shows the example which an order determination part sets the distribution order of data in the ascending order of (distribution size / bandwidth). It is a figure which shows the example which an order determination part rearranges a record for every router, and resets a distribution order. It is a figure which shows the example which an order determination part resets a distribution order for each record to the ascending order of (distribution size / bandwidth). It is a figure which shows the example which an order determination part resets the same order as the distribution order of each record according to the addition result of (distribution size / bandwidth).

  Embodiments of a software distribution system and a software distribution method according to the present invention will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a block diagram showing an embodiment of a software distribution system according to the present invention. As shown in FIG. 1, the software distribution system 1000 includes a distribution server 100, a network 200, a router 300, a network 400, and a terminal 500. As shown in FIG. 1, a plurality of routers 300 (routers 300-1 to 300-n) are connected to the network 200. Each router 300 is connected to a network 400 (hereinafter, each network 400 is referred to as a network 400-). 1 to 400-n). Furthermore, a plurality of terminals 500 (hereinafter, the respective terminals 500 are referred to as terminals 500-1 to 500-n) are connected to the respective networks 400. Note that the network 200 and the network 400 are general public line networks.

  The distribution server 100 is a server that distributes data such as software and files (hereinafter simply referred to as data) to the terminal 500. As illustrated in FIG. 1, the distribution server 100 includes a storage unit 110, a condition calculation unit 120, an order determination unit 130, a distribution unit 140, and a communication unit 150. Each unit (for example, the condition calculation unit 120, the order determination unit 130, and the distribution unit 140) included in the distribution server 100 is actually executed as an application program by a processing device such as a CPU (Central Processing Unit). Thus, the functions of these units are realized.

  The storage unit 110 includes a storage device such as an HDD (Hard disk drive), and stores a distribution error table 1101 and a redistribution destination table 1102.

  The distribution error table 1101 is a table that stores information regarding errors that occur when data is distributed to the terminal 500. FIG. 2 is a diagram illustrating a configuration example of the distribution error table 1101. As shown in FIG. 2, the distribution error table 1101 includes a serial number indicating the number of records, the IP address of the terminal in error, the router 300 to which the terminal is connected, the terminal 500 and the router 300, , The creation date and time of the distributed data, the name of the package in which the data was created (package name), the size of the data (distribution size), the execution status indicating the distribution result, and the data to be distributed Are stored in association with a destination group indicating a group in which a predetermined number of terminals 500 are grouped as a unit. This destination group is not necessarily defined for each terminal 500 under the router 300. For example, the terminal 500 under the router 300-1 and the terminal 500 under the router 300-2 are one group. May be included, and how to determine it is arbitrary.

  In FIG. 2, for example, the record of serial number 1 is transmitted to the terminal of the IP address “xx.xx.xx.100” belonging to the destination group “A” via the distribution server 100 via “R1” which is the router 300. 500 indicates that data of distribution size “10 (MB)” is distributed, but is not correctly distributed and an execution result is an error. The distributed data relates to the package “AAA”, and indicates that the data was created on July 1, 2013. The distribution error table 1101 receives the result from the terminal 500 when the distribution unit 140 of the distribution server 100 distributes data to the terminal 500 according to a predetermined schedule, and records the above-described contents. .

  The redistribution destination table 1102 is a table that stores information obtained by extracting items necessary for redistribution of data from items recorded in the distribution error table 1101. FIG. 3 is a diagram illustrating a configuration example of the redistribution destination table 1102. As shown in FIG. 3, the redistribution destination table 1102 stores an IP address, a destination group, a distribution size, a router, and a bandwidth in association with each other. Since these items are the same as those in the distribution error table 1101, the description thereof is omitted here. Next, returning to FIG. 1, the condition calculation unit 120 will be described.

  The condition calculation unit 120 calculates the distribution size (distribution size / bandwidth) of data that can be distributed per network bandwidth for each record (that is, for each IP address) in the redistribution destination table 1102, and the calculated result is Add as a record item. Specific processing performed by the condition calculation unit 120 will be described later using a flowchart.

  The order determination unit 130 determines the redistribution order of data for the terminal 500 recorded in the redistribution destination table 1102 according to conditions such as a destination group, data distribution size, and bandwidth. Specific processing performed by the order determination unit 130 will be described later using a flowchart.

  Distribution unit 140 distributes data to terminal 500 according to a predetermined schedule. In addition, when the data distribution result (execution state) is an error, the distribution unit 140 redistributes the data according to the distribution order determined by the order determination unit 130. Specific processing performed by the distribution unit 140 will be described later using a flowchart.

  The communication unit 150 is composed of a communication device such as a NIC (Network Interface Card), and manages communication between the distribution server 100 and the router 300. The router 300 relays data received from the distribution server 100 via the network 200 to the network 400.

  The terminal 500 receives data from the router 300 via the network 400 and stores it in a storage unit (not shown). In addition, when the terminal 500 cannot correctly receive data from the router 300, the terminal 500 distributes information indicating an error (for example, information similar to the distribution error table 1101 shown in FIG. 2) via the router 300 and the networks 200 and 400. Send to server 100.

  Next, data redistribution processing performed in the software distribution system 1000 will be described. In the following, after the distribution unit 140 of the distribution server 100 distributes data to the terminal 500, information indicating an error is received from the terminal 500, and the contents are recorded in the distribution error table 1101. And

  FIG. 4 is a flowchart showing a processing procedure of data redistribution processing. As shown in FIG. 4, in the data redistribution process, first, the condition calculation unit 120 extracts items from the distribution error table 1101 shown in FIG. 2 to generate the redistribution destination table 1102 shown in FIG. Thereafter, a redistribution destination division table divided for each destination group is generated (step S401).

  FIG. 5 is a diagram illustrating a state in which the condition calculation unit 120 has generated the redistribution destination division table. As shown in FIG. 5, the condition calculation unit 120 redistributes for each destination group (in FIG. 5, “A”, “B”, and “C”) included in the redistribution destination table 1102 shown in FIG. Generate a destination partition table.

  Then, the condition calculation unit 120 sets the distribution size (distribution size / bandwidth) of data to be distributed per network band for each record (that is, the terminal 500 belonging to the destination group) included in the redistribution destination division table. Calculate and add an item to the record (step S402).

  FIG. 6 is a diagram illustrating a state in which the condition calculation unit 120 calculates (distribution size / bandwidth) and adds the item to the redistribution destination division table. In FIG. 6, for example, the condition calculation unit 120 has a file size of “10 (MB)” distributed to the terminal 500 whose destination group belongs to “A” and whose IP address is “xx.xx.xx.100”. Yes, since the bandwidth between the terminal 500 and the router 300 is “20 (Mbps)”, “0.50 (MB / Mbps)” is calculated, indicating that an item has been added. In this way, the condition calculation unit 120 calculates (distribution size / bandwidth) for each record in each group.

  After that, when the condition calculation unit 120 calculates (distribution size / bandwidth), the order determination unit 130 first sets (distribution size) for each redistribution destination division table as a condition for assigning priorities for data distribution. The distribution order of data is set in ascending order of (bandwidth) (step S403). FIG. 7 is a diagram illustrating an example in which the order determining unit 130 sets the data distribution order in ascending order of (distribution size / bandwidth). In FIG. 7, for example, the order determining unit 130 refers to (distribution size / bandwidth) of each record of the redistribution destination division table whose destination group is “A” and sets the value (from the top to 0.50, 1). .67, 1.00) in ascending order (0.50, 1.00, 1.67). Here, data is first distributed to a terminal having an IP address “xx.xx.xx.100”, then a terminal having an IP address “xx.xx.xx.102”, and an IP address “xx.xx.100”. xx.101 "terminal.

  Then, the order determination unit 130 rearranges the records for each router and resets the distribution order for each redistribution destination division table in consideration of the load on the router as a condition for assigning the next priority. (Steps S404 and S405). FIG. 8 is a diagram illustrating an example in which the order determination unit 130 rearranges records for each router and resets the distribution order. In FIG. 8, for example, the order determination unit 130 refers to the router of each record in the redistribution destination division table whose destination group is “A”, and sets the distribution order in ascending order of (distribution size / bandwidth) for each same router. Set again. Here, the distribution order is reset in the ascending order of (distribution size / bandwidth) for terminals whose IP addresses are “xx.xx.xx.100” and “xx.xx.xx.101” with the same router “R1”. The former is distributed first (“1”) and the latter is distributed next (“2”). On the other hand, for the terminal whose IP address is “xx.xx.xx.102”, since the router is “R2”, the data distribution order is reset as the first (“1”). Thus, since the distribution order is determined while sorting the records, the order can be determined efficiently.

  The order determination unit 130 resets the distribution order for each record in ascending order of (distribution size / bandwidth) for each redistribution destination division table (step S406). FIG. 9 is a diagram illustrating an example in which the order determination unit 130 resets the distribution order of each record in ascending order of (distribution size / bandwidth). In FIG. 9, for example, the order determination unit 130 refers to (distribution size / bandwidth) of each record in the redistribution destination division table whose destination group is “B” and sets (distribution size / bandwidth) for each same router. Reset the distribution order in ascending order. Here, since the routers are different, the record with the smallest value of (distribution size / bandwidth) (the record with the IP address “xx.xx.xx.202”) is rearranged as the first record. In this way, since the distribution order is determined by rearranging the records in the order of the smallest (distribution size / bandwidth) value, as much data as possible can be distributed on the same schedule.

  Then, the order determining unit 130 adds (distribution size / bandwidth) of each record for each router in ascending order for each redistribution destination division table (step S407), and the addition result is a predetermined value (terminal) When an allowable distribution size per band between 500 and the router 300 is exceeded (for example, 2.2 Mb) (step S408), and it is determined that the addition result does not exceed a predetermined value (Step S408; No), it returns to Step S407 and repeats addition.

  On the other hand, when the order determination unit 130 determines that the addition result exceeds the predetermined value (step S408; Yes), the order determination unit 130 sets the records added before determining that the addition value exceeds the predetermined value in the same distribution order (step S409). In step S407, when EOF is reached, the process proceeds to step S412.

  For example, as illustrated in FIG. 10, in the redistribution destination division table in which the destination group is “A”, the order determination unit 130 has a record having an IP address “xx.xx.xx.100” and an IP address. As a result of adding (distribution size / bandwidth) of the record of “xx.xx.xx.101”, the value is 2.17. Therefore, the distribution order of these records is the same (in this example, “1”). ). Since the (distribution size / bandwidth) of the record whose next IP address is “xx.xx.xx.102” is “1.00” and the addition result is “2.67”, it exceeds the predetermined value. This record is not set in the same distribution order, but is set in the next distribution order.

  In step S409, since it is determined whether or not the distribution size per band between the terminal 500 and the router 300 exceeds a predetermined value, even if the routers are different, the predetermined value is exceeded. The distribution order is the same as long as it is not, but when the routers are different, the distribution order may be different. In this case, the load on the router and the load on the network are further reduced.

  Then, the order determination unit 130 determines whether (distribution size / bandwidth) of the next record exceeds the above-described predetermined value (step S410), and (distribution size / bandwidth) sets the predetermined value described above. If it is determined that it does not exceed (step S410; No), the process returns to step S407 and the subsequent processing is repeated.

  On the other hand, when the order determination unit 130 determines that the (distribution size / bandwidth) of the next record exceeds the above-described predetermined value (step S410; Yes), the data is considered to have a large capacity. The distribution order is determined for the one data so as to be sent (step S411). When the processing in step S411 is completed, the distribution order of data in each redistribution destination division table is determined.

  Then, the order determining unit 130 adds (distribution size / bandwidth) of records in the same distribution order determined up to step S411 (step S412), and the addition result is a predetermined value (between the router 300 and the distribution server 100). It is determined whether or not an allowable distribution size per band (for example, 10 Mb) is exceeded (step S413), and when it is determined that the addition result does not exceed a predetermined value (step S413; No), the process proceeds to step S412. Return and repeat addition.

  On the other hand, when the order determination unit 130 determines that the addition result exceeds the predetermined value (step S413; Yes), the order determination unit 130 sets the records added before determining that the addition value exceeds the predetermined value in the same distribution order (step S414).

  For example, in the example illustrated in FIG. 10, the order determination unit 130 records in the redistribution destination division table with the destination group “A” and the distribution order is “1” (the IP address is “xx”). .Xx.xx.100 ”and IP address“ xx.xx.xx.101 ”) (distribution size / bandwidth) addition result“ 2.17 ”and destination group“ B ” In the redistribution destination division table, a record in which the distribution order is “1” (a record with an IP address “xx.xx.xx.202” and a record with an IP address “xx.xx.xx.200”) ) (Distribution size / bandwidth) addition result “0.87” and a record (IP address is “1”) in the redistribution destination division table with the destination group “C”. “Xx. “3.24” obtained by adding the “distribution size / bandwidth” addition result “0.22” of the record “x.xx.301” and “10” which is a predetermined value are compared, and the addition result is Since the predetermined value is not exceeded, the distribution order of these records is the same distribution order.

  Then, the order determining unit 130 adds “1” to the record distribution order when the addition result exceeds the predetermined value, and lowers the data distribution order (step S 415), and further to the next distribution order (that is, the carry-down). It is determined whether there is a record having the same distribution order as the distribution order (step S416). If it is determined that there is a record having the next distribution order (step S416; Yes), the process returns to step S412. The subsequent processing is repeated.

  On the other hand, when the order determination unit 130 determines that there is no record in the next distribution order (step S416; No), the distribution unit 140 passes through the router 300 in a predetermined schedule and a set distribution order. Then, the data is distributed to the terminal 500 (step S417).

  As described above, in this embodiment, the conditions for distributing data (the load on the router and the load on the plurality of networks between the distribution server and the router and between the router and the terminal) are determined in combination and the data is restored. Since the distribution order is set and the data redistribution schedule is set in the distribution order, the transmission file can be distributed efficiently and reliably by giving priority in consideration of these distribution conditions. Specifically, in this system, the load on the router 300 connected to the terminal 500, the network load between the terminal 500 and the router 300, and the network load between the router 300 and the distribution server 100 are considered. Since the data distribution order is determined so as not to apply such an excessive load, the transmission file can be distributed efficiently and reliably even when the data distribution fails.

  In this embodiment, the distribution conditions are as follows: 1) data is distributed in order from the smallest distribution size per band of data; and 2) when the routers are different, the data is distributed in the same distribution order. 3) The total distribution size per band of data that can be distributed at one time by one router does not exceed a predetermined value (for example, 2.2 MB), and 4) can be distributed from the distribution server at one time The distribution order is reset so that the four conditions that the total distribution size per band of data does not exceed a predetermined value (for example, 10 MB) and the data is distributed. Is also reduced.

  In this embodiment, the case of redistributing data that has already been distributed has been described. However, when the size of the data to be distributed, the destination group, the bandwidth, the router, and the IP address of the terminal are stored in the distribution server. Of course, this system can be applied to newly distributing data.

1000 Software distribution system 100 Distribution server 110 Storage unit 120 Condition calculation unit 130 Order determination unit 140 Distribution unit 150 Communication unit 200 Network 300 Router 400 Network 500 Terminal.

Claims (3)

A plurality of routers via a first network that is a network between each of the plurality of routers and each of the plurality of terminals, and a second network that is a network between the distribution server and each of the plurality of routers . A software distribution system that distributes data to terminals,
A condition calculating unit that divides the plurality of terminals into groups and calculates a value of the data per band of the network based on the size of the data and the band of the first network or the second network;
Sorting so that the values are in ascending order, an order determining unit that determines the distribution order so that the values are in ascending order for each group and for each router ;
A distribution unit for distributing the data to the terminal in a predetermined distribution order;
A software distribution system comprising: The order determination unit sets the distribution order of the data in the same order until the value exceeds a first predetermined value indicating an allowable value of data to be distributed in the first network, and sets each group set in the same order. The distribution order of the data is set in the same order until the value of the data exceeds a second predetermined value indicating an allowable value of data distributed in the second network;
The software distribution system according to claim 1 . A plurality of routers via a first network that is a network between each of the plurality of routers and each of the plurality of terminals, and a second network that is a network between the distribution server and each of the plurality of routers. A software distribution method for distributing data to terminals,
Dividing the plurality of terminals into groups and calculating a value of the data per band of the network based on the size of the data and the band of the first network or the second network;
Sorting the values in ascending order and determining the distribution order so that the values are in ascending order for each group and for each router;
Delivering the data to the terminal in a defined distribution order;
A software distribution method comprising:

Images