JP2001265603A - Automatic division software distribution system and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an automatic division software distribution system and the method for automatically selecting a personal computer to perform transmission at the time of distributing software to the personal computers connected on a network. SOLUTION: When an instruction is inputted from a distribution instruction console 2, a distribution schedule preparation mechanism 7 specifies job contents to be in charge by referring to a software attribute definition chart, specifies to which personal computer object software is to be distributed by referring to a terminal attribute definition chart on the basis of the specified job contents, prepares a distribution schedule for making the specified personal computer and the software to be distributed correspond further and executes the operation of transmitting the software corresponding to the personal computer on the distribution schedule to the personal computer to be an object on the basis of the distribution schedule.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system and method for automatically distributing software over a network, and more particularly, to a system and method for automatically distributing software for reducing an instruction input required by an administrator. Regarding the method.

[0002]

2. Description of the Related Art In recent years, the development of software has become active and various companies have improved existing software.

In distributing the improved software to users (users), conventionally, a CD-ROM
Instead of a method of directly sending a storage medium such as a FD or a FD to a user, a method of transmitting software to a user terminal via a network has been developed.

FIG. 9 shows an example of an automatic distribution software distribution system according to the prior art to which such a method is applied. Referring to FIG. 9, the automatic distribution software distribution system according to the conventional example has a software distribution configuration for distributing target software, a server 101 for instructing software distribution, and a software distribution instruction for distributing software. And a distribution instruction console 102 to be created.

Here, the server 101 has the following configuration:
It has a software sending mechanism 109, and specifies and sends software to be delivered and a personal computer (PC) to which the software is sent according to an instruction from an administrator via the distribution instruction console 102. Was.

[0006] The server 101 has a software database for storing software to be distributed (in the present description, a configuration having software A and software B as an example, and as the software database,
A software A database 105 for storing software A and a software B database 106 for storing software B are connected.

Accordingly, when a software distribution instruction is input from the administrator via the distribution instruction console 102,
The personal computer to be sent and the software to be distributed included in the instruction are specified.

After that, the distribution instruction console 10 is sent by the software sending mechanism 109 provided in the server 101.
An operation of sending software to a target personal computer is executed based on the instruction input from Step 2.

In contrast to the software distribution configuration configured as described above, the business execution configuration for receiving the transmitted software includes, for example, a personal computer 111 and a personal computer 1 in this description.
12 are configured, the personal computers 111 and 112 are configured to have software receiving mechanisms 113 and 114, respectively.

Thus, the personal computer 11
1 and 112 receive the software sent from the software sending mechanism 109 by the software receiving mechanisms 113 and 114 via the network 110, respectively.
The business is executed by the received software.

[0011]

However, the above-described prior art has the following problems. First, the first problem is that the operation required for the administrator who inputs the distribution instruction is complicated.

[0012] The reason is that, when distributing software, if the software is sent to only a part of a plurality of personal computers connected to the network 110, the administrator who instructs the distribution manually operates the respective computers. This is because it is necessary to sort whether or not to execute this distribution to a personal computer.

As a second problem, as in the first problem, since the operation required for the administrator is complicated, an erroneous instruction is input when inputting the above-mentioned instruction. That is, it exists.

The reason is that, as described above, the administrator manually inputs complicated work by himself.

[0015] Accordingly, the present invention has been made in view of the above-mentioned problems, and has been made in consideration of the above circumstances. It is an object to provide a software distribution system and a method thereof.

[0016]

To achieve the above object, according to the present invention, the invention described in claim 1 is a system in which one
An automatic distribution software distribution system having a first server as a distribution source of more than one kind of software and one or more first terminals as a distribution destination of the software, wherein the first server Means for creating a distribution schedule that associates software to be distributed with a first terminal to which the software is to be distributed; and a distribution schedule created by the first distribution schedule creation means. And a first software sending means for sending software to the first terminal, wherein the first terminal receives the software sent from the first software sending means. It is characterized by having software receiving means.

According to a second aspect of the present invention, in the automatic distribution software distribution system according to the first aspect, the first server is provided for each of one or more types of software.
First software attribute definition means for storing attribute of a job processed by each software;
And a first terminal attribute definition means for storing an attribute of a task assigned to each of the first terminals. The first distribution schedule creating means further comprises: The corresponding attribute of the business is read from the first software attribute defining means, and further, the corresponding first terminal is read from the first terminal attribute defining means on the basis of the read business attribute, and the read first terminal is read. And a software are associated with each other to create a distribution schedule.

According to the third aspect of the present invention, in the automatic distribution software distribution system according to the first or second aspect, the first software sending means and the first software receiving means are provided with a fixed length. The first software sending means notifies the first software receiving means of the distribution schedule in the regular communication, and the first software receiving means sends the notified distribution schedule to the first software receiving means. It is determined whether the first terminal storing the first software receiving means is included. If the result of the determination is that the first terminal is included, the first software sending means is sent to the first software sending means. Requesting software transmission, and the first software sending means, when receiving a software transmission request from the first software receiving means, sends the software to the first software receiving means. And wherein the Rukoto.

According to a fourth aspect of the present invention, in the automatic distribution software distribution system according to the third aspect, the first server stores the distribution schedule created by the first distribution schedule creating means. A first distribution schedule storing means for reading the distribution schedule stored in the first distribution schedule storing means in the periodic communication with the software receiving means. , First
And transmitting the data to the software receiving means.

According to a fifth aspect of the present invention, in the automatic distribution software distribution system according to any one of the second to fourth aspects, the first server stores the software to be distributed by the user. The apparatus further includes first distribution instruction input means for selecting, and the first distribution schedule creation means includes a first distribution schedule creation means.
The task attribute is read from the first software attribute definition means based on the software selected by the distribution instruction input means.

According to a sixth aspect of the present invention, in the automatic distribution software distribution system according to any one of the first to fifth aspects, the first distribution schedule creation means stores the software distribution schedule in the software distribution system. And the number of combinations of the first terminal and the first terminal are created.

According to a seventh aspect of the present invention, in the automatic distribution software distribution system according to any one of the third to sixth aspects, the first server stores one or more types of software. A first software storage unit, wherein the first software sending unit sends the first software storage unit when the first software receiving unit receives a software transmission request from the first software receiving unit; And reading the software to be transmitted to the first software receiving means.

[0023] The invention according to claim 8 is characterized in that a second server which is a distribution source of one or more types of software on the network and one or more second servers which are distribution destinations of the software.
And a relay server that holds software to be transmitted to the second terminal, wherein the second server has the software to be distributed and the software to be distributed. Second distribution schedule creating means for creating a distribution schedule that associates with the second terminal that is the distribution destination, and second software for transmitting the distribution schedule created by the second distribution schedule creating means to the relay server And a relay unit that receives the distribution schedule transmitted from the second software transmission unit and transmits the software to the second terminal based on the received distribution schedule. The second terminal has software sending means, and the second terminal has second software receiving means for receiving the software sent from the third software sending means.

According to the ninth aspect of the present invention, in the automatic distribution software distribution system according to the eighth aspect, the second server is provided for each of one or more types of software.
A second software attribute definition unit for storing attributes of a job processed by each software;
And a second terminal attribute defining means for storing an attribute of a task assigned to each of the second terminals, wherein the second distribution schedule creating means is configured based on software to be distributed. The corresponding attribute of the business is read from the second software attribute defining means, and the corresponding second terminal is read from the second terminal attribute defining means based on the read business attribute, and the read second terminal is read. And a software are associated with each other to create a distribution schedule.

According to the tenth aspect of the present invention, in the automatic distribution software distribution system according to the eighth or ninth aspect, the third software sending means and the second software receiving means comprise The third software sending means notifies the second software receiving means of the distribution schedule in the periodic communication, and the second software receiving means transmits the notified distribution schedule to the second software receiving means. It is determined whether a second terminal storing the second software receiving means is included. If the result of the determination is that the second terminal is included, the third software sending means is sent to the third software sending means. Software transmission, and the third software transmission means
When a software transmission request is received from the software receiving means, the software is transmitted to the second software receiving means.

According to an eleventh aspect of the present invention, in the automatic distribution software distribution system according to the tenth aspect, the second server stores the distribution schedule created by the second distribution schedule creating means. A second distribution schedule storing means for performing a second communication with the third software transmission means.
The distribution schedule stored in the distribution schedule storing means is read and transmitted to the third software sending means.

According to a twelfth aspect of the present invention, in the automatic distribution software distribution system according to any one of the eighth to eleventh aspects, the relay server receives the distribution received from the second software transmission means. A third distribution schedule storing unit for storing a schedule, wherein the third software sending unit and the second software receiving unit periodically communicate with each other, and the third software sending unit includes: The distribution schedule received in the periodic communication with the second software sending means is stored in the third distribution schedule storing means, and the third software sending means periodically communicates with the second software receiving means. In such communication, the second software receiving unit is notified of the distribution schedule stored in the third distribution schedule storage unit.

According to a thirteenth aspect of the present invention, in the automatic distribution software distribution system according to any one of the ninth to twelfth aspects, the second server is a software to be distributed to a user. Second distribution instruction input means for selecting software, the second distribution schedule creation means, based on the software selected by the second distribution instruction input means, second software attribute definition means It is characterized by reading the attribute of the job more.

According to a fourteenth aspect of the present invention, in the automatic distribution software distribution system according to any one of the eighth to thirteenth aspects, the second distribution schedule creating means includes:
The number of types of combinations of software and the second terminal is created for the distribution schedule.

According to a fifteenth aspect of the present invention, in the automatic distribution software distribution system according to any one of the tenth to fourteenth aspects, the relay server stores at least one type of software. The software storing means further includes a third software sending means, wherein the third software sending means, when receiving a software transmission request from the second software receiving means, sends the software sent from the second software storing means. The software is read out and transmitted to the second software receiving means.

[0031] The invention according to claim 16 is characterized in that the first server connected to the same network and serving as a distribution source of one or more kinds of software and the one or more servers connected to the same network as one or more destinations to which the software is delivered. A software distribution method using the first terminal and the first terminal, wherein the first server creates a distribution schedule that associates the software to be distributed with the first terminal to which the software is distributed. And a first software sending step of transmitting software to the first terminal based on the distribution schedule created in the first distribution schedule creating step. The terminal has a first software receiving step for receiving the software transmitted in the first software sending step.

According to the seventeenth aspect of the present invention, in the automatic distribution software distribution method according to the sixteenth aspect, the first server is provided for each of one or more types of software.
The attribute of the job processed by each software is stored in the first software attribute definition means, and the attribute of the job handled by each first terminal is stored for each of one or more first terminals. The first distribution schedule creation step reads the attribute of the corresponding task from the first software attribute definition means based on the software to be distributed, and further reads the attribute of the read task. A first terminal corresponding to the first terminal is read from the first terminal attribute defining means based on the first terminal attribute definition means, and the read first terminal is associated with the software to create a distribution schedule.

According to the invention described in claim 18, in the automatic distribution software distribution method according to claim 16 or 17, the first server and the first terminal periodically communicate with each other, The first server notifies the first terminal of the distribution schedule in the periodic communication with the first terminal, and the first terminal includes the first terminal in the notified distribution schedule. A first terminal determining step of determining whether or not the first terminal is included, and a first software requesting step of requesting the first server to transmit software when the first terminal is included as a result of the determination; And the first software sending step includes:
When a request for software transmission is made in the first software requesting step, the software is transmitted to the first terminal.

According to the nineteenth aspect, in the automatic distribution software distribution method according to the eighteenth aspect, the first server stores the distribution schedule created in the first distribution schedule creating step. The first server reads out the distribution schedule stored in the first distribution schedule storage means in the periodic communication with the first terminal, and stores the distribution schedule in the first terminal. It is characterized by transmitting.

According to a twentieth aspect of the present invention, in the automatic distribution software distribution method according to any one of the seventeenth to nineteenth aspects, the first server transmits the software to be distributed by a user. The method further includes a first distribution instruction inputting step of selecting, and the first distribution schedule creating step includes a step of the first software attribute defining means based on the software selected in the first distribution instruction inputting step. Is read out.

According to a twenty-first aspect of the present invention, in the automatic distribution software distribution method according to any one of the sixteenth to twentieth aspects, the first distribution schedule creation step includes the step of: And the number of combinations of the first terminal and the first terminal are created.

According to a twenty-second aspect of the present invention, in the automatic distribution software distribution method according to any one of the eighteenth to twenty-first aspects, the first server stores at least one type of software in the first server. Stored in the software storage means of
The first software sending step reads the software to be sent from the first software storage means when the software transmission request is made in the first software requesting step, and sends the read software to the first terminal. It is characterized by transmitting.

According to a twenty-third aspect of the present invention, the second server connected to the network and serving as a distribution source of one or more kinds of software and the one or more second servers serving as a distribution destination of software are provided. And a relay server that holds software to be transmitted to the second terminal, the automatic distribution software distribution method, wherein the second server is a software distribution destination and a distribution destination of the software. A second distribution schedule creation step of creating a distribution schedule that associates with a certain second terminal, a distribution schedule transmission step of transmitting the distribution schedule created in the second distribution schedule creation step to the relay server,
The relay server has a second software sending step of receiving the distribution schedule transmitted in the distribution schedule transmitting step and transmitting software to the second terminal based on the received distribution schedule. , The second terminal has a second software receiving step of receiving the software transmitted in the third software sending step.

According to the invention of claim 24, in the automatic distribution software distribution method of claim 23, the second server is provided for each of one or more types of software.
The attribute of the job processed by each software is stored in the second software attribute definition means, and the attribute of the job handled by each second terminal is stored in the second software attribute definition means for each of one or more second terminals. In the second distribution schedule creation step, the attribute of the corresponding task is read from the second software attribute defining means based on the software to be distributed, and the attribute of the read task is further stored. A second terminal corresponding to the second terminal is read from the second terminal attribute definition means based on the second terminal attribute definition means, and the read second terminal is associated with the software to create a distribution schedule.

According to the invention of claim 25, in the automatic distribution software distribution method of claim 23 or 24, the relay server and the second terminal perform communication periodically, and Notifies the second terminal of the distribution schedule in the periodic communication with the second terminal, and the second terminal determines whether the notified distribution schedule includes the second terminal. A second terminal determination step of determining, and a determination result,
A second software requesting step of requesting the relay server to transmit software when the second terminal is included;
The third software sending step is characterized in that, when a request for software transmission is made in the second software requesting step, the software is sent to the second terminal. .

According to a twenty-sixth aspect of the present invention, in the automatic distribution software distribution method according to the twenty-fifth aspect, the second server stores the distribution schedule created in the second distribution schedule creating step. 2, the second server reads out the distribution schedule stored in the second distribution schedule storage unit and transmits it to the relay server in the periodic communication with the relay server. Features.

According to a twenty-seventh aspect of the present invention, in the automatic distribution software distribution method according to any one of the twenty-third to twenty-third aspects, the relay server transmits the distribution schedule received in the distribution schedule transmitting step to the first server. 3, the relay server and the second terminal periodically communicate with each other, and the relay server communicates the third terminal to the second terminal in the periodic communication with the second terminal. Of the distribution schedule stored in the distribution schedule storage means.

According to a twenty-eighth aspect of the present invention, in the automatic distribution software distribution method according to any one of the twenty-fourth to twenty-seventh aspects, the second server includes software to be distributed to the user. A second distribution instruction inputting step of selecting software, wherein the second distribution schedule creating step includes a second software attribute defining means based on the software selected in the second distribution instruction inputting step. It is characterized by reading the attribute of the job more.

According to a twenty-ninth aspect of the present invention, in the automatic distribution software distribution method according to any one of the twenty-third to twenty-eighth aspects, the second distribution schedule creation step includes: And the number of types of combinations of the terminal and the second terminal are created.

According to a thirtieth aspect of the present invention, in the automatic distribution software distribution method according to any one of the twenty-fifth to twenty-ninth aspects, the relay server includes one or more types of software for the second software. The third software sending step is to read out the software to be sent from the second software storing means when a request for software transmission is made in the second software requesting step. And transmitting it to the second terminal.

[0046]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an automatic distribution software distribution system and method according to the present invention will be described in detail with reference to the drawings. FIG. 1 is a schematic diagram showing the configuration of the entire system of the automatic distribution software distribution system according to the present invention.

{Features of the Present Invention} First, referring to FIG.
The features of the automatic distribution software distribution system according to the present invention will be described in detail. Referring to FIG. 1, an automatic distribution software distribution system according to the present invention includes, as a software distribution configuration for distributing target software, a server 1 for instructing software distribution, and a software distribution instruction for distributing software. And a distribution instruction console 2 to be created.

Here, the server 1 has a distribution schedule creation mechanism 7 and a software sending mechanism 9 as its configuration.
In accordance with an instruction from the distribution instruction console 2, the software to be distributed and a personal computer (PC) to which the software is to be sent in the distribution schedule creation mechanism 7.
And a "distribution schedule" indicating the correspondence between them is created, and the software sending mechanism 9 sends the software according to the created distribution schedule.

The server 1 also includes a terminal attribute definition database 3 for storing the attributes of the tasks assigned to the personal computers to which the software is to be distributed, as a terminal attribute definition table for associating with the personal computer names. A software attribute definition database 4 for storing a software attribute definition table for associating the attribute of a task executed by each software with a software name, and a software database for storing software to be distributed (in this description, as an example, Software A
And a software B. The software database includes a software A database 5 for storing the software A and a software B database 6 for storing the software B. ) And a distribution schedule database 8 that stores distribution schedules created in the server 1 are connected.

Accordingly, when a software distribution instruction is input from the distribution instruction console 2, the distribution schedule creation mechanism 7 provided in the server 1 defines the software attribute definition based on the distribution target software included in the instruction. Database 4
The software attribute definition table is referred to to identify the task contents assigned to the software to be distributed, and based on the specified task contents, the terminal attribute definition table is referred to from the terminal attribute definition database 3 to obtain the target software. Specify which personal computer the software will be distributed to.

Further, the distribution schedule creation mechanism 7 creates a distribution schedule that associates the personal computer specified above with the software to be distributed as a table, and stores this in the distribution schedule database 8.

The software sending mechanism 9 provided in the server 1 sends the target personal computer to the target personal computer based on the distribution schedule stored in the distribution schedule database 8.
An operation of sending software corresponding to the personal computer is executed on the distribution schedule.

In contrast to the software distribution configuration thus configured, the business execution configuration for receiving the transmitted software includes, for example, a personal computer 11 and a personal computer 12 in this description.
Are configured, the personal computers 11 and 12 respectively have the software receiving mechanism 13 and
14.

Thus, the personal computer 1
1 and 12 receive the software sent from the software sending mechanism 9 by the software receiving mechanisms 13 and 14 via the network 10, respectively, and execute the business by the received software.

First Embodiment Next, a first embodiment of an automatic distribution software distribution system and method according to the present invention will be described in detail with reference to the drawings.

[Configuration of the First Embodiment] FIG. 2 is a diagram showing the configuration of the automatic distribution software distribution system according to the first embodiment. Referring to FIG. 2, the automatic distribution software distribution system according to the first embodiment has an instruction from the distribution instruction console 2 as a software distribution configuration for distributing target software, similarly to the configuration shown in FIG. Server 1 having a distribution schedule creation mechanism 7 for creating a distribution schedule according to the above and a software sending mechanism 9 for sending software according to the created distribution schedule, and a distribution for creating an instruction for software distribution Instruction console 2
And a personal computer 11 storing a software receiving mechanism 13 (or 14) as a task execution configuration for receiving target software.
(Or 12).

In the first embodiment, the server 1 and the personal computers 11 and 12 are connected to a LAN (Loacl A
rea Network) 10.

(Software Distribution Mechanism) Here, the software distribution mechanism will be described in detail with reference to FIG. The server 1 in this software distribution mechanism includes:
As in FIG. 1, the terminal attribute definition database 3 that stores the attributes of the tasks assigned to the personal computers to be distributed with software as a terminal attribute definition table for associating with the personal computer name, and the distribution target software, respectively. A software attribute definition database 4 for storing a software attribute definition table for associating an attribute of a task to be executed with a software name, and a software database for storing software to be distributed (in this description, software A is used as an example). Software B and a software database
A software A database 5 for storing the software A and a software B database 6 for storing the software B) and a distribution schedule for storing the distribution schedule created in the server 1 The database 8 is connected.

With this configuration, upon receiving a software distribution instruction from the distribution instruction console 2, the distribution schedule creation mechanism 7 provided in the server 1, based on the software distribution target personal computer included in the instruction. Referring to the terminal attribute definition table from the terminal attribute definition database 3,
The task contents assigned to the distribution destination personal computer are specified, and based on the specified task contents, the software attribute definition table is referred to from the software attribute definition database 4 to distribute which software to the target computer. Then, a distribution schedule that associates the specified software with the distribution destination personal computer as a table is created and stored in the distribution schedule database 8.

Thereafter, based on the distribution schedule stored in the distribution schedule database 8, the software sending mechanism 9 provided in the server 1 sends the software corresponding to the personal computer to the target personal computer on the distribution schedule. Execute the operation of sending the software.

(Terminal attribute definition table) The terminal attribute definition table stored in the terminal attribute definition database 3 is shown in FIG.
The table is as shown below.

Referring to FIG. 3, the terminal attribute definition table is configured to store correspondences between personal computer names and tasks performed by the personal computers in all of the types. Therefore, for example, the personal computer 1
In the case where 1 performs two types of tasks, task A and task B, the terminal attribute definition table describes two kinds of correspondence, that is, the correspondence "personal computer / task A" and the correspondence "personal computer / task B". Store each.

(Software Attribute Definition Table) The software attribute definition table stored in the software attribute definition database 4 is a table as shown in FIG.

Referring to FIG. 4, the software attribute definition table is configured to store correspondences between software names and tasks performed by the software, all of the types.
Therefore, for example, when there are two types of software for executing the task A, software A1 and software A2, the software attribute definition table is “software A1
Two types of correspondences, that is, a correspondence of "business A" and a correspondence of "software A2 and business A" are stored.

(Distribution Schedule) The distribution schedule stored in the distribution schedule database 8 is a table as shown in FIG.

Referring to FIG. 5, the distribution schedule is a table in which software names and delivery destination personal computer names are associated with each other. Therefore, the distribution schedule created by the distribution schedule creation mechanism 7 based on the instruction input from the distribution instruction console 2 is the personal computer name and the software attribute definition read from the terminal attribute definition table by the distribution schedule creation mechanism 7. The software name read from the table is created in correspondence with the software name, and the created distribution schedule is stored in the distribution schedule database 8.

(Business Execution Configuration) As the business execution configuration for receiving the sent software, for example, in the first embodiment, similar to the description with reference to FIG.
It is assumed that the personal computer 11 and the personal computer 12 are configured. However, the personal computers 11 and 12 have software receiving mechanisms 13 and 14, respectively.

Thus, the personal computer 1
1 and 12 receive the software sent from the software sending mechanism 9 by the software receiving mechanisms 13 and 14 via the network (LAN) 10 and execute the business by the received software.

[Operation of First Embodiment] Next, the operation of the first embodiment will be described in detail with reference to the drawings.

The personal computer 1 shown in FIG.
Software receiving mechanisms 13 and 14 provided in
Is a software sending mechanism 9 provided in each server 1
And communicates regularly.

Therefore, when a distribution instruction is input from the distribution instruction console 2 and a distribution schedule is created in the distribution schedule creation mechanism 7, the software receiving mechanisms 13 and 14 store the distribution schedule in the distribution schedule database 8 in the above communication. You will be notified of the scheduled distribution.

Thus, the personal computers 11 and 12 that have received the distribution schedule from the software sending mechanism 9
The software receiving mechanisms 13 and 14 check whether the personal computer storing the software is registered as the personal computer of the distribution destination in the notified distribution schedule.
It requests the software sending mechanism 9 to send the corresponding software.

The software sending mechanism 9 that has received the software sending request starts communication with the software receiving mechanisms 13 and 14 that issued the request, and sends the target software.

(Explanation of Overall Operation) With reference to this, FIG. 6 is a flowchart showing the overall operation when distributing the software B1 in the first embodiment.

Referring to FIG. 6, first, when a start operation for distributing software is input to the distribution instruction console 2 from the administrator, the distribution instruction console 2 reads the software attribute definition table from the software attribute definition database. (Step S1-1), software B1 to be distributed
Is selected (step S1-2), and the process ends.

In step S1-2, the distribution instruction console 2 outputs a software name relating to the selected software B1 to the distribution schedule creation mechanism 7 in the server 1 as an instruction.

On the other hand, in step S2-1, the distribution schedule creation mechanism 7 receives the output instruction (step S2-1), and distributes the software information of the distribution target included in the received instruction (step S2-1). Software name)
A business attribute (business B in the present embodiment) corresponding to the software B1 is read from the software attribute definition table read from the software attribute definition database, and further,
Based on the read task B, all the corresponding personal computers are read from the terminal attribute definition table read from the terminal attribute definition database 3 (step S2-
2).

Next, the distribution schedule creation mechanism 7 executes step S
The one or more personal computers read in 2-2 and the software names received in step S2-1 are individually associated with each other, and distribution schedules are created for each corresponding type, and the created distribution schedule is created. All distribution schedules are stored in the distribution schedule database 8 (step S
2-3).

The software receiving mechanism 13 (or 1
4) periodically communicates with the software sending mechanism 9 as described above. In this communication, the software receiving mechanism 13 (or 14) performs an operation of reading the distribution schedule database 8 via the software sending mechanism 9 (step S3-1).

Therefore, the software receiving mechanism 13 (or 14) determines whether or not the name of the personal computer including the personal computer is included in the distribution schedule stored in the distribution schedule database in the communication (step S14). S3-2), if the result of this determination is that the name of the personal computer provided with itself is not included (step S3-
(No in No. 2), the communication is terminated, and the system waits until the next communication is started. However, as a result of the above-described determination, when the name of the personal computer including the personal computer is included (step S3-
2), a distribution reception request for transmitting the corresponding software is transmitted to the software transmission mechanism 9 (step S3-3).

Thereafter, the software receiving mechanism 13 (or 14) executes an operation of installing the software B1 received from the software sending mechanism 9 (step S3-4), and upon completion of the operation, terminates the communication. Wait until communication starts.

On the other hand, the software sending mechanism 9
Upon receiving the distribution request from the software receiving mechanism 13 (or 14), the corresponding software (software B1 in this embodiment) is stored in a software database (software B class database 6 in this embodiment). ), And the read software B1
Is transmitted to the software receiving mechanism 13 (or 14) (step S4-2), and upon completion, the processing is terminated.

(Operation of Step S2-2 in FIG. 6)
Next, the operation of automatically selecting a distribution destination personal computer in step S2-2 in FIG. 6 will be described in more detail with reference to the flowchart in FIG.

Referring to FIG. 7, the distribution schedule creation mechanism 7
In automatically selecting a distribution destination personal computer, first, a software attribute definition table is read from the software attribute definition database 4 (step S2-
2-1).

Next, based on the software attribute definition table read in step S2-2-1, step S2-1 in FIG.
"Business" corresponding to the software name entered in
The attribute is determined (step S2-2-2).

The distribution schedule creation mechanism 7 reads the terminal attribute definition table from the terminal attribute definition database 3 (step S2-2-3), and determines in step S2-2-2 from the read terminal attribute definition table. Using the job attributes thus set, all personal computer names corresponding to the corresponding job attributes are selected (step S2-2-4).

Thereafter, the distribution schedule creation mechanism 7 selects the personal computer name selected in step S2-2-4 by associating the software name received in step S2-1 in FIG. 6 with each personal computer name selected in step S2-2-4. A distribution schedule is created for each personal computer name (step S2-2-5), stored in the distribution schedule database, and the process proceeds to step S2-3 in FIG.

[Effects of First Embodiment] As described above, the configuration and operation of the first embodiment enable
Instructions required for a user (administrator) can be simplified.

The reason is that by referring to the terminal attribute definition database 3 and the software attribute definition database 4 shown in FIG. 2, an instruction requested to the user only needs to input the name of the software to be distributed. This is because it becomes possible to automatically determine the personal computer to which the information is to be distributed based on the input software name.

In the first embodiment, in addition to the above effects, it is possible to further reduce the possibility that an error is included in the input distribution instruction.

The reason is that, as described above, by simplifying the instruction requested by the user, it is possible to omit a configuration and a process relying on human judgment.

{Second Embodiment} Next, a second embodiment of the present invention will be described in detail with reference to the drawings. FIG. 8 is a block diagram showing the configuration of the automatic distribution software distribution system according to the second embodiment.

[Configuration of Second Embodiment] Referring to FIG. 8, the automatic distribution software distribution system according to the second embodiment includes a server 1 which is a software distribution source shown in the first embodiment. The configuration is such that the relay server 16 is interposed between the personal computer to which the software is to be distributed. Here, the server 1 and the relay server 16
It is connected via an AN (Wide Area Network) 15.

The relay server 16 has a software sending mechanism 17 having the same function as the software sending mechanism 9 in the server 1, and the software sending mechanism 17 periodically communicates with the software sending mechanism 9. It is configured to perform an operation of performing communication and receiving a distribution schedule stored in the distribution schedule database 8.

The distribution schedule thus received is stored in the distribution schedule database 18 connected to the relay server 16.

The personal computers 21 and 22 shown in FIG. 8 are provided with a LAN (Local Area Network) 20 by software receiving mechanisms 23 and 24 provided respectively.
, And periodically communicates with the software sending mechanism 17 provided in the relay server 16 via. Therefore, the software receiving mechanism 23 (or 24) is configured to confirm the distribution schedule stored in the distribution schedule database 18 via the software sending mechanism 17 in the above-described periodic communication.

The software receiving mechanism 23 (or 2
4) requests the software sending mechanism 17 to transmit the target software if the name of the personal computer provided in the distribution schedule is included in the above confirmation. The software sending mechanism 17 reads out the target software from the software database 19 and
(Or 24).

[Operation of Second Embodiment] Next, the operation of the second embodiment will be described in detail with reference to the drawings.

The relay server 16 and the server 1 shown in FIG. 8 regularly communicate with each other via the LAN 10, the WAN 15, and the LAN 20, and the software receiving mechanism 23 provided in the personal computers 21 and 22. ,
24 regularly communicates with a software delivery mechanism provided in the relay server 16.

Therefore, when a distribution instruction is input from the distribution instruction console 2 and a distribution schedule is created in the distribution schedule creation mechanism 7, the software delivery mechanism 9 communicates the distribution schedule with the communication partner in the above communication. Notify the software sending mechanism 17.

On the other hand, the software sending mechanism 17 in the relay server 16 that has received the distribution schedule from the software sending mechanism 9 stores the notified distribution schedule in the distribution schedule database 18 connected to the relay server 16. I do.

Also, the personal computers 21 and 22
The software receiving mechanisms 23 and 24 provided in the relay server 16 are provided with software sending mechanisms 17 and 24, respectively.
And communicates regularly.

Therefore, when a distribution instruction is input from the distribution instruction console 2 and a distribution schedule is created in the distribution schedule creation mechanism 7, the software delivery mechanism 17 receives the distribution schedule via the WAN 15 and relays it. In the server 16, the received distribution schedule is stored in the distribution schedule database 18. Therefore, the software receiving mechanism 2
3 and 24 are the distribution schedule database 1 in the above communication.
8 is notified of the distribution schedule.

As a result, the personal computers 21 and 21 that have received the distribution schedule from the software sending mechanism 17
The software receiving mechanisms 23 and 24 in 2 confirm whether or not the personal computer storing the software has been registered as the personal computer of the distribution destination in the notified distribution schedule. It requests the sending mechanism 17 to send the corresponding software.

The software sending mechanism 17 that has received the software sending request starts communication with the software receiving mechanisms 23 and 24 that issued the request, and sends the target software.

(Explanation of Overall Operation) Referring to this, FIG. 9 is a flowchart showing the overall operation of distributing software B1 in the second embodiment.

Referring to FIG. 9, when a start operation of distributing software is input from the administrator to the distribution instruction console 2, the distribution instruction console 2 reads the software attribute definition table from the software attribute definition database. (Step S1-11), software B to be distributed
1 is selected (step S1-12), and the process ends.

In step S1-12, the distribution instruction console 2 outputs the software name relating to the selected software B1 to the distribution schedule creation mechanism 7 in the server 1 as an instruction.

On the other hand, in step S2-11, the distribution schedule creation mechanism 7 receives the output instruction (step S2-11), and distributes the software information of the distribution target included in the received instruction (step S2-11). Based on the software name), a business attribute (business B in the present embodiment) corresponding to the software B1 is read from the software attribute definition table read from the software attribute definition database. Based on this, all corresponding personal computers are read from the terminal attribute definition table read from the terminal attribute definition database 3 (step S2-
12).

Next, the distribution schedule creation mechanism 7 executes step S
Each of the one or more personal computers read in 2-12 and the software name received in step S2-11 are individually associated with each other, and a distribution schedule is created for each corresponding type. The distribution schedules are all stored in the distribution schedule database 8 (step S2-13).

The software sending mechanism 17 in the relay server 16 periodically communicates with the software sending mechanism 9 as described above. In this communication, the software sending mechanism 17 reads the distribution schedule from the distribution schedule database 8 via the software sending mechanism 9 (step S5-11).

Then, the distribution schedule read in step S5-11 is stored in the distribution schedule database 18 connected to the relay server 16 (step S5-1).
2).

On the other hand, the software receiving mechanism 23
(Or 24) periodically communicates with the software sending and transmitting mechanism 17 as described above. In this communication, the software receiving mechanism 23 (or 24) transmits the distribution schedule database 1 via the software sending mechanism 17.
8 (step S6-1).
1).

Therefore, the software receiving mechanism 23 (or 24) determines in the above communication whether or not the name of the personal computer including itself is included in the distribution schedule stored in the distribution schedule database (step S24). S6-12), if the result of this determination is that the name of the personal computer provided with itself is not included (step S6)
(No in -12), the communication is terminated, and the system waits until the next communication is started. However, as a result of the above-described determination, if the name of the personal computer including itself is included (step S).
In step S6-13, a distribution reception request for transmitting the corresponding software is transmitted to the software transmission mechanism 17 (step S6-13).

Thereafter, the software receiving mechanism 23 (or 24) executes an operation of installing the software B1 received from the software sending mechanism 17 (step S6-14), and terminates the communication as soon as it is completed. Wait until communication starts.

In contrast, the software sending mechanism 17
When receiving the above-mentioned distribution reception request from the software receiving mechanism 23 (or 24) (step S5-21), the corresponding software (the software B in the present embodiment)
1) is read from the software database (the software A / B database 19 in this embodiment),
The read software B1 is transmitted to the software receiving mechanism 23 (or 24) (step S5-2).
2) After the completion, the process ends.

[Effects of the Second Embodiment] As described above, the configuration and operation of the second embodiment enable
In implementing the present invention, it is possible to reduce the communication cost spent.

The reason is that when the relay server 16 is not installed, the software receiving mechanisms 23, 2 of the personal computers 21, 22 connected to the WAN 20
4 communicates with the software sending mechanism 9 of the server 1 via the WAN to install software stored in each software database.
The time spent for the installation depends not only on the time passing through the WAN 15 but also on the communication speed of the WAN 15 itself. Therefore, the connection time to the WAN becomes longer, whereas According to the second embodiment, since the communication with the software sending mechanism 17 is performed directly via only the relatively high-speed LAN 20 without passing through the WAN 15 which is a relatively low communication speed, the software can be more quickly operated. This is because the installation can be completed.

Such an effect can be regarded as a higher effect as the number of personal computers connected to the WAN 20 increases.

[0120]

[Effects of the First Embodiment] As described above, in the first embodiment, the user (administrator)
Can be simplified.

The reason for this is that by referring to the terminal attribute definition database 3 and the software attribute definition database 4 shown in FIG. 2, an instruction requested to the user only has to input the name of the software to be distributed. This is because it becomes possible to automatically determine the personal computer to which the information is to be distributed based on the input software name.

In the first embodiment, in addition to the above effects, it is possible to further reduce the possibility that an error is included in the input distribution instruction.

The reason is that, as described above, by simplifying the instruction requested by the user, it is possible to omit a configuration and a process relying on human judgment.

[Effects of the Second Embodiment]
According to the embodiment, it is possible to reduce the communication cost spent in implementing the present invention.

The reason is that when the relay server 16 is not installed, the software receiving mechanisms 23 and 2 of the personal computers 21 and 22 connected to the WAN 20 are used.
4 communicates with the software sending mechanism 9 of the server 1 via the WAN to install software stored in each software database.
The time spent for the installation depends not only on the time passing through the WAN 15 but also on the communication speed of the WAN 15 itself. Therefore, the connection time to the WAN becomes longer, whereas According to the second embodiment, since the communication with the software sending mechanism 17 is performed directly via only the relatively high-speed LAN 20 without passing through the WAN 15 which is a relatively low communication speed, the software can be more quickly operated. This is because the installation can be completed.

Such an effect can be regarded as a higher effect as the number of personal computers connected to the WAN 20 increases.

[Other effects] According to the automatic distribution software distribution system according to the present invention, as described above, the software receiving mechanism and the software sending mechanism communicate with each other. Since the mechanism itself checks the distribution schedule received and determines that the software is to be distributed, for example, if the personal computer to which the software is distributed is down, other It is possible to make the distribution from the server wait until the personal computer is restored without having the above.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an automatic distribution software distribution system of the present invention.

FIG. 2 is a block diagram showing a configuration of an automatic distribution software distribution system according to the first embodiment of the present invention.

FIG. 3 is a table showing a terminal attribute definition table according to the present invention.

FIG. 4 is a table showing a software attribute definition table according to the present invention.

FIG. 5 is a table showing distribution schedules according to the present invention.

FIG. 6 is a flowchart showing the entire operation of the automatic distribution software distribution system according to the first embodiment of the present invention.

FIG. 7 is a flowchart showing an operation in step S2-2 in FIG. 6;

FIG. 8 is a block diagram showing a configuration of an automatic distribution software distribution system according to a second embodiment of the present invention.

FIG. 9 is a flowchart showing the entire operation of the automatic distribution software distribution system according to the second embodiment of the present invention.

FIG. 10 is a block diagram showing a configuration of a conventional automatic distribution software distribution system.

[Explanation of symbols]

1 server 2 distribution instruction console 3 terminal attribute definition database 4 software attribute definition database 5 software A class database 6 software B class database 7 distribution schedule creation mechanism 8, 18 distribution schedule database 9, 17 software sending mechanism 10 network ( LAN) 11, 12, 21, 22 Personal computer (P
C) 13, 14, 23, 24 Software receiving mechanism 15 Network (WAN) 16 Relay server 19 Software AB class database 20 Network (WAN)

Claims (30)

[Claims] 1. An automatic distribution system comprising: a first server on which one or more types of software are distributed; and one or more first terminals on which the software is distributed, on the same network. A software distribution system, the first server comprising: a first distribution schedule creating means for creating a distribution schedule for associating the software to be distributed with the first terminal to which the software is to be distributed; And a first software sending means for sending the software to the first terminal based on the distribution schedule created by the first distribution schedule creating means, wherein the first terminal The automatic distribution software distribution system, further comprising: first software receiving means for receiving the software transmitted from the first software sending means. 2. The first server comprises: first software attribute definition means for storing, for each of the one or more types of software, attributes of a job processed by each of the software; A first terminal attribute definition unit for storing, for each of the first terminals, an attribute of the task assigned to each of the first terminals, the first distribution schedule creating unit includes: Reading the corresponding attribute of the service from the first software attribute defining means based on the software to be executed, and further reading the corresponding attribute from the first terminal attribute defining means based on the read attribute of the task. 2. The automatic distribution software distribution system according to claim 1, wherein the first terminal is read, and the distribution schedule is created by associating the read first terminal with the software. 3. The first software sending means and the first software receiving means perform communication periodically, and the first software sending means performs the communication in the regular communication. Notifying the first software receiving means of the distribution schedule, wherein the first software receiving means stores the first software receiving means in the notified distribution schedule, the first terminal Is determined, and if the result of the determination is that the first terminal is included, a request is made to the first software sending means to transmit the software, and the first terminal is sent. The software sending means, when receiving the request for transmission of the software from the first software receiving means, sends the software to the first software receiving means. 3. The automatic distribution software distribution system according to claim 1, wherein: 4. The first server further comprises a first distribution schedule storing unit for storing the distribution schedule created by the first distribution schedule creating unit, and wherein the first software sending unit is provided. Reads out the distribution schedule stored in the first distribution schedule storage unit in the periodic communication with the software receiving unit,
4. The automatic distribution software distribution system according to claim 3, wherein the transmission is performed to the first software receiving unit. 5. The first server further includes first distribution instruction input means for allowing a user to select the software to be distributed, and wherein the first distribution schedule creation means includes a first distribution schedule creation means. 5. The automatic distribution according to claim 2, wherein the attribute of the task is read from the first software attribute definition unit based on the software selected by the distribution instruction input unit. Software distribution system. 6. The distribution schedule creation means according to claim 1, wherein the distribution schedule creation unit creates the number of types of combinations of the software and the first terminal. Automatic distribution software distribution system described in 1. 7. The first server further includes a first software storage unit that stores the one or more types of software, and the first software sending unit includes the first software storage unit. When the request for transmitting the software is received from a receiving unit, the software to be transmitted is read from the first software storage unit and transmitted to the first software receiving unit. The automatic distribution software distribution system according to any one of claims 3 to 6. 8. Automatic distribution software having a second server as a distribution source of one or more types of software on a network and one or more second terminals as a distribution destination of the software. A distribution system, further comprising: a relay server that retains the software to be transmitted to the second terminal, wherein the second server is configured to distribute the software and the destination to which the software is distributed. Second distribution schedule creating means for creating a distribution schedule that associates with the second terminal, and second software transmission means for transmitting the distribution schedule created by the second distribution schedule creation device to the relay server And the relay server receives the distribution schedule transmitted from the second software transmission means, and based on the received distribution schedule,
A third software sending unit that sends the software to the second terminal, wherein the second terminal receives the software sent from the third software sending unit. An automatic distribution software distribution system, comprising: 9. The second server, wherein, for each of the one or more types of software, a second software attribute defining means for storing an attribute of a job processed by each of the software; A second terminal attribute definition unit for storing, for each of the second terminals, an attribute of the task assigned to each of the second terminals, the second distribution schedule creating unit includes: Reading the corresponding attribute of the business from the second software attribute defining means based on the software to be executed, and further reading the corresponding attribute of the business from the second terminal attribute defining means based on the read attribute of the business. 9. The automatic distribution software distribution system according to claim 8, wherein the second terminal is read, and the distribution schedule is created by associating the read second terminal with the software. 10. The third software sending means and the second software receiving means perform communication periodically, and the third software sending means, in the periodic communication, Notifying the second software receiving means of the distribution schedule, wherein the second software receiving means stores the second software receiving means in the notified distribution schedule, the second terminal Is determined, and if the result of the determination is that the second terminal is included, a request for transmission of the software is sent to the third software sending means, and the third terminal is sent. The software sending means, when receiving the request for transmission of the software from the second software receiving means, transmits the software to the second software receiving means. 10. The automatic distribution software distribution system according to claim 8, wherein 11. The second server further comprises a second distribution schedule storage unit for storing the distribution schedule created by the second distribution schedule creation unit, wherein the second software sending unit is provided. Reads out the distribution schedule stored in the second distribution schedule storage unit and transmits the distribution schedule to the third software transmission unit in the periodic communication with the third software transmission unit. The automatic distribution software distribution system according to claim 10, characterized in that: 12. The relay server further includes a third distribution schedule storage unit that stores the distribution schedule received from the second software transmission unit, wherein the third software transmission unit and the third distribution schedule storage unit store the distribution schedule. The third software sending means periodically communicates with the second software receiving means, and the third software sending means transmits the distribution schedule received in the regular communication with the second software sending means to the third software sending means. The third software sending means stores the third distribution schedule in the second software receiving means in the periodic communication with the second software receiving means. 12. The automatic distribution software distribution system according to claim 8, wherein the distribution schedule stored in the storage unit is notified. 13. The second server further comprises a second distribution instruction input unit for allowing a user to select the software to be distributed, and wherein the second distribution schedule creating unit includes the second distribution schedule creation unit. 13. The method according to claim 9, wherein the attribute of the task is read from the second software attribute definition unit based on the software selected by the second distribution instruction input unit. Distribution software distribution system. 14. The apparatus according to claim 8, wherein said second distribution schedule creating means creates the number of types of combinations of said software and said second terminal. Automatic distribution software distribution system described in 1. 15. The relay server further includes a second software storage unit that stores the one or more types of software, and the third software sending unit includes the second software receiving unit. When the request for transmission of the software is received, the software to be transmitted is read from the second software storage unit and transmitted to the second software reception unit. Item 15. The automatic distribution software distribution system according to any one of Items 10 to 14. 16. One connected to the same network
An automatic distribution software distribution method using a first server that is a distribution source of more than one type of software and one or more first terminals that are distribution destinations of the software, A first distribution schedule creating step of creating a distribution schedule that associates the software to be distributed with the first terminal to which the software is to be distributed; A first software transmission step of transmitting the software to the first terminal based on the distribution schedule thus performed, wherein the first terminal transmits the software to the first terminal in the first software transmission step. An automatic distribution software distribution method, comprising a first software receiving step for receiving the transmitted software. 17. The first server stores, for each of the one or more types of software, an attribute of a job to be processed by the software in a first software attribute definition unit, For each of the at least one first terminal, the attribute of the task assigned to each of the first terminals is stored in a first terminal attribute definition means, and the first distribution schedule creating step includes: The first software attribute defining means reads out the corresponding attribute of the business from the first software attribute defining means based on the software, and further, the first terminal attribute defining means corresponding to the first terminal attribute defining means reads out the read-out attribute of the business. 17. The automatic distribution software distribution method according to claim 16, wherein a terminal is read, and the distribution schedule is created by associating the read first terminal with the software. 18. The first server and the first terminal periodically communicate with each other, and the first server communicates with the first terminal in the regular communication with the first terminal. A first terminal determining step of notifying the terminal of the distribution schedule, the first terminal determining whether or not the notified distribution schedule includes the first terminal; As a result, when the first terminal is included, a first software requesting step of requesting the first server to transmit the software is further provided. 17. The method according to claim 16, wherein the step of transmitting the software to the first terminal is performed when the transmission of the software is requested in the first software requesting step.
7. The automatic distribution software distribution method according to 7. 19. The first server stores the distribution schedule created in the first distribution schedule creating step in first distribution schedule storage means, and the first server stores the first distribution schedule in the first distribution schedule storing means. 19. The automatic distribution software according to claim 18, wherein in the periodic communication with the terminal, the distribution schedule stored in the first distribution schedule storage unit is read and transmitted to the first terminal. How to distribute software. 20. The first server further includes a first distribution instruction inputting step of allowing the user to select the software to be distributed, and wherein the first distribution schedule creating step includes the first distribution schedule creating step. 20. The automatic distribution according to claim 17, wherein an attribute of the task is read from the first software attribute defining means based on the software selected in the distribution instruction input step. Software distribution method. 21. The method according to claim 16, wherein, in the first distribution schedule creating step, the distribution schedule is created by the number of combinations of the software and the first terminal.
21. The automatic distribution software distribution method according to any one of the above items. 22. The first server stores the one or more types of software in first software storage means, wherein the first software sending step includes the steps of: When the transmission of the software is requested, the software to be transmitted is read out from the first software storage unit, and the first
22. The terminal of claim 18, wherein
The automatic distribution software distribution method according to any one of the above. 23. A second server connected to a network as a distribution source of one or more types of software, one or more second terminals as distribution destinations of the software, An automatic distribution software distribution method using a relay server that holds the software to be transmitted to the terminal, wherein the second server is the software to be distributed and the distribution destination of the software. A second distribution schedule creation step of creating a distribution schedule that associates with the second terminal; a distribution schedule transmission step of transmitting the distribution schedule created in the second distribution schedule creation step to the relay server; The relay server receives the distribution schedule transmitted in the distribution schedule transmitting step, and transmits the software to the second terminal based on the received distribution schedule. And a second software receiving step of receiving the software transmitted in the third software sending step. Automatic distribution software distribution method. 24. The second server stores, for each of the one or more types of software, an attribute of a job processed by each of the software in a second software attribute definition means, Storing, in a second terminal attribute defining means, an attribute of the task assigned to each of the second terminals, for each of the second terminals or more; The second software attribute defining means reads out the corresponding attribute of the task based on the software, and further, the second terminal attribute defining means responds based on the read-out attribute of the task. 24. The automatic distribution software distribution method according to claim 23, wherein a terminal is read, and the distribution schedule is created by associating the read second terminal with the software. 25. The relay server and the second terminal periodically communicate with each other, and the relay server performs the distribution to the second terminal in the periodic communication with the second terminal. Notifying a schedule, the second terminal, a second terminal determination step of determining whether the notified distribution schedule includes the second terminal, As a result of the determination, A second terminal for requesting the relay server to transmit the software if a second terminal is included;
The third software sending step further includes: when the request for transmission of the software is made in the second software requesting step, the third software sending step. 24. The transmission to two terminals.
4. The method for distributing automatic sorting software according to 4. 26. The second server stores the distribution schedule created in the second distribution schedule creating step in a second distribution schedule storage means, wherein the second server is configured to store the relay server and the relay server. 26. The automatic distribution software distribution method according to claim 25, wherein in the periodic communication, the distribution schedule stored in the second distribution schedule storage unit is read and transmitted to the relay server. 27. The relay server stores the distribution schedule received in the distribution schedule transmitting step in third distribution schedule storage means, and the relay server and the second terminal periodically communicate with each other. The relay server notifies the second terminal of the distribution schedule stored in the third distribution schedule storage means in the periodic communication with the second terminal. Item 29. The automatic distribution software distribution method according to any one of Items 23 to 26. 28. The second server further comprises a second distribution instruction inputting step of allowing the user to select the software to be distributed, and wherein the second distribution schedule creating step includes the step of: 28. The automatic operation according to claim 24, wherein the attribute of the task is read out from the second software attribute defining means based on the software selected in the second distribution instruction input step. Distribution software distribution method. 29. The method according to claim 23, wherein, in the second distribution schedule creating step, the distribution schedule is created by the number of combinations of the software and the second terminal.
29. The method for distributing automatic sorting software according to any one of claims to 28. 30. The relay server stores the one or more types of software in a second software storage means, and the third software sending step includes the step of sending the software in the second software requesting step. When the request for software transmission is made, the software to be transmitted is read out from the second software storage means, and the second
29. The terminal of claim 25, wherein
The automatic distribution software distribution method according to any one of the above.