JP2013020481A - Software distribution server, software distribution method, software distribution program, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To execute software distribution without inviting pressure on a network band, an increased load on an object terminal, any delay in the progress of software distribution, or concentration of software distribution on adjoining terminals.SOLUTION: A software distribution server comprises: a memory unit 102B that stores a distribution state table 111 that stores, in association with one another, terminal identifying information for identifying terminals, operational information on terminals, and band information on a network; a status determining unit 104 that determines an operational state of the terminals and causes the result of determination to be stored as part of the operational information; a band determining unit 106 that determines whether or not the band of the network satisfies requirements for distribution of software and causes the result of determination to be stored as part of the band information; and a distribution control unit 103 that causes the software to be distributed to a terminal identified by the terminal identifying information, when no halt of the terminal is stored as operational information and satisfaction by the network band of the requirements for distribution of software is stored as band information.

Description

  The present invention relates to a software distribution server, a software distribution method, a software distribution program, and a recording medium that realize software distribution in consideration of a network usage situation with respect to a software distribution target terminal and a state of the target terminal.

  In the prior art, there is known a method for restricting the distribution of software to terminals in a predetermined time zone (for example, Patent Document 1).

Japanese Patent Laid-Open No. 2001-166943

  In the technique disclosed in Patent Document 1 described above, software distribution restrictions based on time zones are provided as predefinable items in software distribution. However, only in consideration of this item, the following (1) to (3) There are issues as shown in.

  First, (1) the network usage status with the target terminal is not taken into consideration, and there is a possibility that network bandwidth will be compressed. Next, because (2) the status of the target terminal (operating, inactive, out of service) has not been considered, there is concern about the target terminal load caused by software distribution to the operating terminal, Priority distribution and distribution to stopped terminals cannot be controlled. Furthermore, (3) the selection method of the target terminal is sequential, and there is a possibility that software distribution to adjacent terminals is concentrated.

  The object of the present invention is to solve these problems of the prior art and execute software distribution without causing network bandwidth pressure, increased load on target terminals, delay in software distribution progress, and concentration of software distribution to neighboring terminals. A software distribution server, a software distribution method, a software distribution program, and a recording medium.

  In order to achieve the above-described object, a software distribution server according to the present invention is a software distribution server that distributes software to terminals connected via a network, terminal identification information for identifying the terminals, The terminal operation information including at least the operation status indicating whether or not the terminal is stopped is associated with the band information indicating whether or not the network band satisfies a condition necessary for distribution of the software. A storage unit that stores a distribution status table to be stored, a status determination unit that determines an operation status of the terminal, stores the determined result in the operation information, and a condition that the network bandwidth is necessary for distributing the software And a bandwidth determination unit that stores the determined result in the bandwidth information; and In the case where it is not stored that the terminal is stopped, and the bandwidth information stores that the bandwidth of the network satisfies the conditions necessary for distribution of the software, A distribution control unit that distributes the software to the terminal identified by the terminal identification information.

  The present invention also provides a software distribution method, a software distribution program, and a recording medium storing the software distribution method executed by the software distribution server.

  According to the present invention, it is possible to execute software distribution without causing network bandwidth pressure, target terminal load increase, delay of software distribution progress, and concentration of software distribution to adjacent terminals, resulting in high quality. Secure software distribution.

1 is an overall system configuration diagram of a software distribution system according to an embodiment. It is a figure which shows the example of a terminal management table. It is a figure which shows the example of a distribution plan table. It is a figure which shows the example of a distribution status table. It is a figure which shows the example of a required bandwidth table. It is a flowchart which shows the process sequence of the software distribution process which a distribution control part performs. It is a flowchart which shows the process sequence of the software distribution process which a distribution control part performs. It is a flowchart which shows the process sequence of the software distribution process which a distribution control part performs. It is a flowchart which shows the process sequence of the status determination process which a terminal status determination part performs. It is a flowchart which shows the process sequence of the terminal remote operation process which a terminal remote control part performs. It is a flowchart which shows the process sequence of the band determination process which a band determination part performs.

  Exemplary embodiments of a software distribution server, a software distribution method, a software distribution program, and a recording medium according to the present invention will be explained below in detail with reference to the accompanying drawings.

  FIG. 1 is an overall system configuration diagram of a software distribution system 1000 according to the present embodiment. As shown in FIG. 1, the software distribution system 1000 includes a software distribution server 101 and a target terminal group 114, which are connected to each other via a network 113. The network 113 is a general communication line network such as a LAN (Local Area Network) or a WAN (Wide Area Network). First, the software distribution server 101 will be described.

  The software distribution server 101 distributes predetermined software to each terminal constituting the target terminal group 114 (hereinafter referred to as a target terminal or simply a terminal). As illustrated in FIG. 1, the software distribution server 101 includes a main control unit 102A and a storage unit 102B.

  The main control unit 102A is composed of, for example, an arithmetic device such as a CPU (Central Processing Unit), and controls various processes to be described later and the operation of each unit constituting the software distribution server 101. The main control unit 102A functionally includes a distribution control unit 103, a terminal status determination unit 104, a terminal remote operation unit 105, and a band determination unit 106.

  The distribution control unit 103 distributes software while checking the status of the terminal by referring to the terminal management table 108, the distribution plan table 110, the distribution status table 111, and the like. Specific processing performed by the distribution control unit 103 will be described later with reference to FIGS.

  The terminal status determination unit 104 determines the status of the terminal when the distribution control unit 103 distributes software. Specific processing performed by the terminal status determination unit 104 will be described later with reference to FIG.

  The terminal remote operation unit 105 remotely activates or stops the target terminal to which software is distributed. Specific processing performed by the terminal remote control unit 105 will be described later with reference to FIG.

  The bandwidth determination unit 106 confirms that a network bandwidth necessary for distributing software is secured. Specific processing performed by the band determination unit 106 will be described later with reference to FIG.

  Each unit included in the software distribution server 101 is executed by a program for realizing the functions of the distribution control unit 103, the terminal status determination unit 104, the terminal remote operation unit 105, and the bandwidth determination unit 106. These programs have, for example, a module configuration including the above-described units, and as actual hardware, a control unit such as a CPU reads these programs from a recording device such as an HDD (Hard Disk Drive) and executes them. As a result, the above-described units are loaded on the main storage device, and the distribution control unit 103, the terminal status determination unit 104, the terminal remote operation unit 105, and the bandwidth determination unit 106 are generated on the main storage device. It has become.

  The above-mentioned program is recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, and a DVD (Digital Versatile Disc) as a file in an installable or executable format. Can also be provided. Furthermore, these programs may be configured to be provided or distributed by being downloaded via a network. Next, the storage unit 102B will be described.

  The storage unit 102B is composed of a storage device such as an HDD (Hard Disk Drive), for example, and stores various data used in various processes to be described later. The storage unit 102B includes a terminal management DB (Data Base) 107, a terminal management table 108, a software distribution DB 109, a plan table 110, a distribution status table 111, and a bandwidth table 112. As shown in FIG. 1, the terminal management table 108 is stored in the terminal management DB 107, and the plan table 110, the distribution status table 111, and the bandwidth table 112 are stored in the software distribution DB 109.

  FIG. 2 is a diagram illustrating an example of the terminal management table 108. As shown in FIG. 2, the terminal management table 108 includes a terminal ID for identifying a terminal to which software is distributed, an IP address of the terminal, a MAC address of the terminal, and an employee who uses the terminal. An employee number for identification, the name of the employee, the department to which the employee belongs, and the contact information of the employee are stored in association with each other. In FIG. 2, for example, a terminal having a terminal ID “1000001”, an IP address “10.100.1.1”, and a MAC address “00-22-15-03-07-D1” belongs to the “accounting department”. This is a terminal used by “Ichiro Tanaka” of the employee number “30001”, and indicates that the contact is “00-1111-2222”. It is assumed that data stored in the terminal management table 108 is set in advance by an administrator or the like. Next, the distribution plan table 110 will be described.

  FIG. 3 is a diagram illustrating an example of the distribution plan table 110. As shown in FIG. 3, the distribution plan table 110 includes a software name for identifying software to be distributed, a start date / time indicating the date / time when distribution of the software is started, and an end / date indicating when the software distribution is ended. The date and time, a terminal selection method indicating a method for specifying a terminal to which software is to be distributed, and a target terminal status indicating the state of the specified terminal are stored in association with each other. In FIG. 3, for example, the distribution of the software “Software A” is started at “0:00 on December 24, 2010” and is scheduled to end at “12:00 on December 24, 2010”. Yes, the distribution method of the software to the terminal is a “random” method, and among the distribution target terminals specified by the “random” method, the statuses of “pause” state, “stop” state, “operation” state and This means that the software is distributed to the terminals.

  As the terminal selection method included in the distribution plan table 110, a “random” method and a “sequential” method are set. The “random” method indicates that software is distributed in an arbitrary order if the distribution target terminal is a terminal satisfying the status set in the terminal target status. In addition, the “sequential” method is determined in advance when the distribution target terminal satisfies the status set as the terminal target status, for example, terminal ID order, IP address order, MAC address order, or employee number order. It shows that software is distributed in the specified order.

  In addition, the target terminal status included in the distribution plan table 110 indicates the status of the terminal necessary for distributing the software, and includes three states of “stop” state, “pause” state, and “operation” state, or These combinations are set. The “stopped” state is a state where the distribution target terminal is not operating, the “pause” state is a state where the distribution target terminal is operating but not active, and the “active” state is a distribution target terminal. Indicates that it is up and active. Therefore, in the example of distributing the “software A” described above, it is distributed to the distribution target terminals in these three states. It is assumed that the data stored in the distribution plan table 110 is set in advance by an administrator or the like, like the terminal management table 108 described above. Next, the distribution status table 111 will be described.

  FIG. 4 is a diagram illustrating an example of the distribution status table 111. As shown in FIG. 4, the distribution status table 111 includes a terminal ID terminal ID for identifying a terminal, an installation flag indicating that the terminal is a software installation target, and a terminal indicating the status of the terminal. The status, the bandwidth flag indicating that the bandwidth on the network necessary for installing the software is satisfied, and the target status indicating that the terminal target status included in the distribution plan table 110 is satisfied are stored in association with each other. Has been. In FIG. 4, for example, a terminal with a terminal ID “1000001” is an installation target of a certain software (for example, software A), and is currently in a “pause” state. The current line status is a state in which the bandwidth for software distribution is satisfied (the bandwidth necessary for software distribution is secured), and the current terminal status is the target of the distribution plan table 110 Indicates that the terminal status is satisfied (included).

  The installation flag included in the distribution status table 111 is set to any one of “Y” (installation target), “N” (not installation target), and “-” (unset). In addition, the terminal status of the distribution status table 111 includes, in addition to the statuses of “suspended” state, “stopped” state, and “operating” state, as well as the “suspended” status, similar to the target terminal status of the distribution plan table 110 described above. One of the “remote activation” states indicating the state where the distribution target terminal in the “state” is activated by remote operation is set.

  Furthermore, the bandwidth flag included in the distribution status table 111 includes “Y” (the current line of the network to which the terminal is connected is in a state in which a bandwidth necessary for software distribution is secured), “N” (the terminal has The current line of the connected network is in a state where the bandwidth necessary for software distribution is not secured), or “-” (not set) is set. The distribution status table 111 includes “Y” (the current terminal state satisfies (includes) the target terminal status of the distribution plan table 110) and “N” (current). The status of the terminal of the distribution plan table 110 does not satisfy the target terminal status (not included)) or “-” (not set) is set. Data stored in the distribution status table 111 is set or updated according to the state of the terminal. The distribution status table 111 is created for each software to be distributed. Next, the necessary bandwidth table 112 will be described.

  FIG. 5 is a diagram illustrating an example of the necessary bandwidth table 112. As shown in FIG. 5, the necessary bandwidth table 112 stores a software name of software to be distributed and a necessary bandwidth (bandwidth condition) when the software is distributed and installed in a terminal. FIG. 5 shows that, for example, when “Software A” is installed in a distribution target terminal, at least a network line bandwidth of 10 KB is required. It is assumed that the data stored in the necessary bandwidth table 112 is set in advance by an administrator or the like, like the terminal management table 108 described above. Next, various processes performed in the software distribution system 1000 according to the present embodiment will be described.

  6A to 6C are flowcharts showing a processing procedure of software distribution processing performed by the distribution control unit 103. As shown in FIG. 6A, the distribution control unit 103 accesses the distribution plan table 110, reads the software name, the start time, and the end time, and extracts the software name that is currently scheduled to be distributed. Then, it is determined whether or not the target exists (step S601). When it is determined that there is no target (step S601; No), the software distribution process illustrated in FIG. 6 is terminated. Whether or not the software is scheduled to be distributed at this time is determined based on, for example, whether the time of a timer (not shown) is the start time or whether the date of the timer is the start date.

  On the other hand, if the distribution control unit 103 determines that there is a target (step S601; Yes), whether or not the distribution status table 111 for the software exists in the software distribution DB 203 using the software name of the software as a key. (Step S602), and when it is determined that the distribution status table 111 for the software does not exist (step S602; No), all terminals identified by the terminal IDs of the terminal management table 108 for the software are displayed. The distribution status table 111 including the information is generated (step S603), and the process proceeds to step S604. On the other hand, when the distribution control unit 103 determines that the distribution status table 111 for the software exists (step S602; Yes), the process directly proceeds to step S604.

  Next, the distribution control unit 103 accesses the distribution plan table 110, and extracts the terminal selection method and target terminal status corresponding to the software using the software name of the software as a key (step S604). Then, the distribution control unit 103 further accesses the distribution status table 111, extracts terminal IDs as distribution candidates of the software using the extracted terminal selection method as a key, and determines whether or not there is the target ( Step S605). At this time, in order not to distribute to terminals that already have the software installed, terminals other than the installation flag “Y” and the band flag “−” in the distribution status table 111 and other than the target status “−” Shall be excluded.

  Then, the distribution control unit 103 extracts a terminal ID that is a distribution candidate of the software, and when it is determined that there is no target (step S605; No), the software distribution processing illustrated in FIGS.

  On the other hand, when the distribution control unit 103 extracts a terminal ID that is a candidate for distribution of the software and determines that there is an object (step S605; Yes), the terminal management table 108 uses the terminal ID extracted in step S605 as a key. , The IP address and the MAC address corresponding to the terminal ID are extracted (step S606), and the process proceeds to the status determination process (step S607) shown in FIG. 6B.

  FIG. 7 is a flowchart illustrating a processing procedure of status determination processing performed by the terminal status determination unit 104. As illustrated in FIG. 7, the terminal status determination unit 104 transmits a 1-byte ping packet to the IP address acquired in step S606 five times to check the terminal status (step S608). Specifically, the terminal status determination unit 104 issues a command “ping-llt 5 <IP address> | find“ bytes = 1 ”> NUL” to the IP address acquired in step S606, and its return code. Whether or not is zero.

  If the terminal status determination unit 104 determines that the return code for the issued command is not zero (step S701; No), the terminal status determination unit 104 determines that the terminal is in a stopped state, and the distribution status table corresponding to the terminal ID. The terminal status 111 is updated to “stop” (step S702).

  On the other hand, if the terminal status determination unit 104 determines that the return code for the issued command is zero (step S701; Yes), the terminal status determination unit 104 determines that the terminal is at least in an operating state, and further performs a screen saver process on the terminal. It is determined whether or not it is operating (step S703). Specifically, the terminal status determination unit 104 determines whether there is a process having an extension “.scr” from among processes running on the terminal.

  If the terminal status determination unit 104 determines that the screen saver process is operating on the terminal (step S703; Yes), the terminal status determination unit 104 determines that the terminal is in the dormant state, and the distribution status corresponding to the terminal ID. The terminal status in the table 111 is updated to “pause” (step S704).

  On the other hand, if the terminal status determination unit 104 determines that the screen saver process is not operating on the terminal (step S703; No), the terminal status determination unit 104 determines that the terminal is in the operating state, and the distribution status corresponding to the terminal ID. The terminal status in the table 111 is updated to “operation” (step S705). When any one of steps S702, S704, and S705 ends, all the status determination processing illustrated in FIG. 7 ends. Subsequently, returning to FIG. 6B, each process after step S <b> 607 will be described.

  6B, when the status determination process (step S607) ends, the distribution control unit 103 uses the terminal ID extracted in step S605 as a key, the terminal status corresponding to the terminal ID, and the target terminal status extracted in step S604. Are compared to determine whether or not they match (or whether or not the terminal status is included in the target terminal status) (step S608).

  When the distribution control unit 103 determines that the two do not match (or the terminal status is not included in the target terminal status) (step S608; No), the distribution control unit 103 sets the target status in the distribution status table 111 corresponding to the terminal ID. Update to “N” and return to step S605 to repeat the subsequent processing.

  On the other hand, when the distribution control unit 103 determines that the two match (or the terminal status is included in the target terminal status) (step S608; Yes), the target status in the distribution status table 111 corresponding to the terminal ID is “ In addition, it is determined whether or not the terminal status of the distribution status table 111 corresponding to the terminal ID is “stopped” (step S609).

When the distribution control unit 103 determines that the terminal status of the distribution status table 111 corresponding to the terminal ID is “stopped” (step S609; Yes), the process proceeds to step S610, and the terminal remote operation unit 105 Remote operation processing is performed (step S610).
FIG. 8 is a flowchart illustrating a processing procedure of terminal remote operation processing performed by the terminal remote operation unit 105. This terminal remote operation process is a process subsequent to step S609 described above or step S616 described later, and whether or not to remotely start the terminal depends on the timing at which each process is executed.

  As illustrated in FIG. 8, the terminal remote control unit 105 determines whether the terminal status of the distribution status table 111 corresponding to the terminal ID is “stopped” using the terminal ID extracted in step S605 as a key. (Step S801).

  If the terminal remote operation unit 105 determines that the terminal status of the distribution status table 111 corresponding to the terminal ID is “stopped” (step S801; Yes), the terminal remote operation unit 105 determines the MAC address of the terminal acquired in step S606. Then, a MagicPacket conforming to the WakeOnLan specification is transmitted (step S802), and the terminal status in the distribution status table 111 is updated to “remote activation” (step S803).

  On the other hand, when the terminal remote operation unit 105 determines that the terminal status in the distribution status table 111 corresponding to the terminal ID is not “stopped” but “remote activation” (step S801; No). Then, a shutdown command is issued to the IP address of the terminal acquired in step S606 (step S804), and the terminal status in the distribution status table 111 is updated to “−” (step S805).

  When the process of step S803 or step S805 ends, all the processes shown in FIG. 8 end. Note that the processes of steps S802 and S803 of the terminal remote operation process shown in FIG. 8 are executed when it is determined Yes in the process of step S609, and the processes of steps S804 and S805 are thereafter performed in the distribution status table 111. This is performed when it is determined YES in the process of step S616 in a state where the terminal status is updated to “remote activation”. Subsequently, returning to FIG. 6B, the processing after step S611 will be described.

  If it is determined in step S609 that the terminal status of the distribution status table 111 corresponding to the terminal ID extracted in step S605 is not “stopped” (step S609; No), or in step S610, the terminal remote operation process is performed. When performed, the band determination unit 106 performs band determination processing (step S611).

  FIG. 9 is a flowchart illustrating the processing procedure of the bandwidth determination process performed by the bandwidth determination unit 106. As shown in FIG. 9, the bandwidth determination unit 106 accesses the required bandwidth table 112 using the software name of the software that the distribution control unit 103 uses as a key in step S601, and extracts the required bandwidth corresponding to the software name. (Step S901).

  Next, the bandwidth determination unit 106 transmits a 64 kilobyte ping packet five times to the IP address acquired by the distribution control unit 103 in step S606, and acquires the average response time (step S902). Specifically, the bandwidth determination unit 106 issues the command “ping-1 64000-t 5 <IP address> | find“ Average ”” to the IP address to acquire the average response time.

  Then, the band determination unit 106 calculates a band speed (step S903). Specifically, the band determination unit 106 calculates the band speed using the calculation formula “(64 KB × 2) ÷ average response time = band speed”.

  Next, the bandwidth determination unit 106 compares the required bandwidth extracted in step S901 with the bandwidth speed calculated in step S903 to determine whether the bandwidth speed is equal to or higher than the required bandwidth (step S904). When it is determined that the speed is equal to or higher than the necessary bandwidth (step S904; Yes), the bandwidth flag in the distribution status table 111 is updated to “Y” (step S905).

  On the other hand, if the bandwidth determination unit 106 determines that the bandwidth speed is not equal to or higher than the required bandwidth (step S904; No), the bandwidth flag in the distribution status table 111 is updated to “N” (step S906). When the process of step S905 or S906 ends, all the processes shown in FIG. 9 end. Subsequently, returning to FIG. 6B, the processing after step S612 will be described.

  When the bandwidth determination process ends in step S611, the distribution control unit 103 reads the bandwidth flag from the distribution status table 111, determines whether or not the bandwidth flag is “Y” (step S612), and the bandwidth flag is “Y”. If it is determined that it is (step S612; Yes), the process proceeds to step S613 shown in FIG. 6C. On the other hand, if the distribution control unit 103 determines that the bandwidth flag is not “Y” (step S612; No), the process returns to step S605 and the subsequent processing is repeated.

  Then, the distribution control unit 103 transmits the software targeted for distribution in step S601 to the terminal having the IP address acquired in step S606, acquires the return code, and the acquired return code is “0”. It is determined whether or not there is (step S613).

  When the distribution control unit 103 determines that the acquired return code is “0” (step S613; Yes), the distribution control unit 103 further performs software installation processing to acquire the return code, and the acquired return code is “0”. ] Is determined (step S614). On the other hand, when the distribution control unit 103 determines that the acquired return code is not “0” (step S613; No), the process returns to step S605 to repeat the subsequent processing.

  When the distribution control unit 103 determines that the acquired return code is “0” (step S614; Yes), the distribution control unit 103 determines that the software has been successfully installed, and sets the installation flag of the distribution status table 111 to “Y”. (Step S615). On the other hand, when the distribution control unit 103 determines that the acquired return code is not “0” (step S614; No), the process returns to step S605 to repeat the subsequent processing.

  Next, the distribution control unit 103 reads the terminal status in the distribution status table 111, determines whether the terminal status is “remote activation” (step S616), and determines that the terminal status is “remote activation”. If it has been performed (step S616; Yes), the terminal remote control unit 105 performs the terminal remote control process shown in FIG. 8 (step S617). At this time, as described above, since the terminal status of the distribution status table 111 is updated to “remote activation” in step S803, each process of steps S804 and S805 of the terminal remote operation processing is performed at this stage. Will be. On the other hand, when the distribution control unit 103 determines that the terminal status is not “remote activation” (step S616; No), the process proceeds to step S618 without doing anything.

  The distribution control unit 103 accesses the distribution plan table 110, executes a read process of the start time and end time corresponding to the software name of the installed software, and determines whether or not the current time is within the planned time. If it is determined that the current time is within the planned time (step S618) (step S618; Yes), the process returns to step S605 and the subsequent processing is repeated. On the other hand, when the distribution control unit 103 determines that the current time is not within the planned time (step S618; No), the bandwidth flag of the distribution status table 111 is updated to “−” and the target status is set to “−”. Update and reset (step S619). When the process of step S619 ends, all the processes shown in FIGS. 6A to 6C end.

  As described above, in the software distribution system according to the present embodiment, the network bandwidth required as the software distribution condition is set in advance, the network bandwidth at the time of software distribution is measured, and software distribution is performed only when the set condition is satisfied. If the network bandwidth is congested, software distribution will be postponed. As a result, network bandwidth pressure due to software distribution can be prevented. In other words, software distribution can be performed without causing network bandwidth pressure, increased load on target terminals, delay in software distribution progress, and concentration of software distribution to neighboring terminals, resulting in high-quality software distribution. Can be provided.

  Also, the target terminals for software distribution are selected for each terminal status (operating, inactive, inactive). As a result, it is possible to prevent an increase in the load on the target terminal in operation, and to prevent the delay in progress of software distribution by remotely starting the target terminal being stopped and executing software distribution. Software distribution.

  Furthermore, sequential selection and random selection can be specified as the target terminal selection method. At the time of sequential selection, for example, by distributing software to terminals in the same network area where a certain department is arranged, the network bandwidth of that department is reduced. It is also possible to avoid the adverse effects caused by the concentration of the terminals to be installed in one place, such as crowding and a decrease in response.

  It should be noted that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. For example, when the number of target terminals to which software is distributed is large and the processing load is large, a plurality of functions of the software distribution server 101 are physically divided into two or more servers. Some components may be changed from the components, or the components may be appropriately combined.

1000 Software distribution system 101 Software distribution server 102A Main control unit 102B Storage unit 103 Distribution control unit 104 Terminal status determination unit 105 Terminal remote operation unit 106 Band determination unit 107 Terminal management DB
108 Terminal management table 109 Software distribution DB
110 Plan table 111 Distribution status table 112 Band table 113 Network 114 Target terminal group.

Claims (8)

A software distribution server that distributes software to terminals connected via a network,
Terminal identification information for identifying the terminal, operation information of the terminal including at least an operation status indicating whether or not the terminal is stopped, and a bandwidth of the network satisfy a condition necessary for distribution of the software A storage unit for storing a distribution status table for storing the band information indicating whether or not the band information is associated with each other;
A status determination unit that determines the operating status of the terminal and stores the determined result in the operating information;
A bandwidth determination unit that determines whether or not a bandwidth of the network satisfies a condition necessary for distribution of the software, and stores the determined result in the bandwidth information;
The fact that the terminal is stopped is not stored as the operation information, and the fact that the bandwidth of the network satisfies the conditions necessary for the software distribution is stored as the bandwidth information A distribution control unit that distributes the software to the terminal identified by the terminal identification information;
A software distribution server comprising: A remote control unit for remotely starting the terminal when operation information indicating that the terminal is stopped is stored;
The distribution control unit, when the remote operation unit remotely activates the terminal, and storing that the band of the network satisfies a condition necessary for distribution of the software as the band information Distributing the software to the terminal identified by the identification information;
The software distribution server according to claim 1. The storage unit further includes a distribution plan table for previously storing software identification information for identifying the software and target terminal status information indicating the status of the terminal necessary for distributing the software in association with each other. Remember,
The distribution control unit, when the operation information stored in the distribution status table is included in the target terminal status information stored in the distribution plan table, distributes the software to the terminal identified by the terminal identification information. Distribute
The software distribution server according to claim 1, wherein the software distribution server is a software distribution server. The distribution control unit, when a plurality of the terminals are connected to the network, to distribute the software to the terminals in a predetermined order or regardless of the order;
The software distribution server according to any one of claims 1 to 3. The remote operation unit remotely activates the terminal, and after the distribution control unit distributes the software to the terminal, the operation information is reset by returning the terminal to a stop state before remote activation.
The software distribution server according to claim 2, wherein the software distribution server is a software distribution server. A software distribution method performed by a software distribution server that distributes software to terminals connected via a network,
A status determination step of determining an operating status of the terminal, and storing the determined result as operating information of the terminal including an operating status indicating whether or not the terminal is at least stopped;
Band information indicating whether or not the network bandwidth satisfies a condition necessary for software distribution, and the result of the determination indicates whether or not the network bandwidth satisfies a condition necessary for software distribution. Bandwidth determination step to be stored in
A first determination step for determining whether or not the terminal is stopped as the operation information;
When it is determined that the fact that the terminal is stopped is not stored as the operation information, it is stored that the bandwidth of the network satisfies the conditions necessary for the software distribution as the bandwidth information. A second determination step of determining whether or not,
The terminal identified by terminal identification information for identifying the terminal when it is determined that the bandwidth of the network satisfies the condition necessary for distribution of the software as the band information A distribution step for distributing the software to
A software distribution method comprising: On the computer,
A status determination step of determining an operating status of a terminal connected via a network, and storing the determined result as operating information of the terminal including an operating status indicating whether or not the terminal is stopped;
It is determined whether or not the network bandwidth satisfies a condition necessary for software distribution, and the determined result is band information indicating whether or not the network bandwidth satisfies a condition necessary for software distribution. Bandwidth determination step for storing;
A first determination step for determining whether or not the terminal is stopped as the operation information;
When it is determined that the fact that the terminal is stopped is not stored as the operation information, it is stored that the bandwidth of the network satisfies the conditions necessary for the software distribution as the bandwidth information. A second determination step of determining whether or not,
The terminal identified by terminal identification information for identifying the terminal when it is determined that the bandwidth of the network satisfies the condition necessary for distribution of the software as the band information A distribution step for distributing the software to
Software distribution program characterized by causing   A computer-readable recording medium storing the software distribution program according to claim 7.

Images