JP2001166943A - Method for distributing software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for limiting distribution according to a time zone for facilitating a countermeasure to a case that line charge is made different according to the time zone, or a case that any distribution processing is not preliminarily desired by a client user according to the time zone. SOLUTION: A distributing time zone managing part 4 of a server 1 manages plural time zone and priority to distribution processing by relating them with each other. At the time of distributing software registered in a software managing part 2, a distribution schedule managing part decides the schedule of distribution based on the information managed by the distrusting time zone managing part 4. A transmitting part 5 transmits the software to a client 7 according to the schedule of distribution. The client 7 installs the software received by a receiving part 8 by an install processing part 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software distribution method in a network to which a plurality of computers are connected, and more particularly, to a software distribution system suitable for use in an operation mode in which distribution times are scheduled according to time zone priorities.

[0002]

2. Description of the Related Art When distributing software, especially when a telephone line is used, the usage fee may differ depending on the time zone. In addition, it may be an important problem to execute distribution and installation at a time that does not interfere with the work of the client user.

In a conventional distribution system, software has been automatically distributed when a time manually set by an operation manager or a client user elapses or the state is automatically determined.

A method for receiving software at a time designated by a client user is disclosed in Japanese Patent Laid-Open No. 10-5762.
No. 6.

A method for automatically distributing software when a client machine is not used is described in Japanese Patent Application Laid-Open No. H11-85689.

[0006]

The conventional method has the following problems.

[0007] That is, the conventional method only executes the distribution of the software on some occasion. For this reason, for example, there is a problem that distribution is continued even when the line usage fee has passed the cheap time zone, or distribution is executed because the client machine is temporarily unused, and it is used again Then, there was a problem that the client machine could not be used until the distribution process was completed.

[0008] An object of the present invention is to manage a plurality of time zones in a server or a client, and to add a priority to distribution or installation processing. It is another object of the present invention to provide a software distribution method for scheduling software distribution based on those priorities.

[0009]

SUMMARY OF THE INVENTION According to the present invention, in a network system, software is distributed based on a plurality of set time zones and their associated priorities in software distribution or installation processing. And perform the installation.

When the server determines a plurality of time zones and the priority of the time zones, information such as the capacity of the software to be distributed and the installation completion date and time, the priority for each time zone, and the actual data transfer for each hour Schedule distribution from ability. Distribute software based on this schedule. When the date and time to be finished has elapsed, the distribution is suspended, and the distribution is resumed at another scheduled date and time.

When the client determines a plurality of time zones and the priority of the time zone, information such as the capacity of the software to be distributed and the installation completion date and time, the priority for each time zone, and the data for each actual time are used. Decide whether to actually receive the software distributed from the transfer capability. At the same time, when receiving, the date and time of interruption are determined. When the date and time to be interrupted during the reception of the software has elapsed, the reception of the software is temporarily interrupted and the date and time to be resumed is notified to the server. When the reception is completed, an installation schedule is performed based on the priority for each time zone and the date and time when the software installation is completed.

As described above, the distribution and installation are scheduled based on the priority for each time zone, so that the line usage fee can be reduced. The effect can be reduced.

[0013]

Embodiments of the present invention will be described below in detail.

FIG. 1 is a configuration diagram of a server and a client to which a software distribution method according to the present invention is applied.

The server 1 has a software management unit 2, a distribution schedule management unit 3, a distribution time zone management unit 4, a transmission unit 5, and a transfer capability management unit 6. The software management unit 2 manages software to be distributed and its software information. When the operation manager selects software to be distributed, the distribution schedule management unit 3 determines a distribution schedule from the software management unit 2, the distribution time zone management unit 4, and the transfer capability management unit 6. Distribution time zone management unit 4
Manages the priority of the time zone for the distribution process. The transmission unit 5 transmits the software managed by the software management unit 2 to the target client 7 according to the distribution schedule determined by the distribution schedule management unit 3.
The transfer capability management unit 6 periodically acquires and manages information on the transfer capability for each time. The client 7 includes a reception unit 8, a transfer capability management unit 9, an installation processing unit 10, and a processing time zone management unit 11. The receiving unit 8 receives software transmitted from the server 1. The transfer capability management unit 9 periodically acquires and manages information on the transfer capability for each time. The installation processing unit 10 installs the software received by the receiving unit 8. The processing time zone management unit 11 manages the priority of the distribution or installation process for each time zone.

In the following, an example of an operation mode in which the server manages the priority for each time zone related to the distribution processing will be described.

FIG. 2 is a software information table for storing software information managed by the software management unit 2 of FIG. The software information table has a software name 101, a capacity 102, an installation time 103, an installation completion date and time 104, and a distribution destination 105.
The software name 101 indicates the name of software registered as a distribution target, and is a character string such as “software A” or “software X”. The capacity 102 indicates the capacity of the target software, is a numerical value such as “1000”, “4899”, and the unit is kilobytes. Installation time 10
Reference numeral 3 denotes the time required to install the target software, which is a numerical value such as "10" or "35", and the unit is minutes. The installation completion date and time 104 indicates the date and time when the target software needs to be installed on the distribution destination client. The distribution destination represents information on a client that distributes the target software, and includes “Host A”,
A character string such as “host A, host B” or the like can be listed in plurals separated by “,”. The information in the software information table is set automatically or by an operation manager.

FIG. 3 is a distribution time period table managed by the distribution time period management unit 4 of FIG. 1 and storing information on the priority for each time period for the distribution process. The distribution time zone table has a start time 201, an end time 202, and a priority 203. The start time 201 represents the start time of the time zone.
The end time 202 represents the end time of the time zone. Priority 20
Reference numeral 3 denotes a priority of a time zone for distribution, which is a numerical value.
The priority 203 indicates that the larger the number is, the more suitable the time zone in which the distribution process is executed, and the smaller the number, the time zone in which the distribution process should not be performed. In particular, when the priority 203 is “0”, it indicates that the time period is a period during which distribution is prohibited. The information of the distribution time zone table is set automatically or by the operation manager.

FIG. 4 is a distribution schedule table for storing software distribution schedule information managed by the distribution schedule management unit 3 of FIG. The distribution schedule table includes a software name 301, a distribution destination 302,
It has a start date and time 303 and an end date and time 304. The software name 301 represents the name of software to be distributed,
Character strings such as "software A" and "software B" are used. The distribution destination 302 represents information on the client of the distribution destination, and is a character string such as “host A” or “host B”. Start date and time 3
03 represents a start date and a start time of a time zone in which the target software is distributed to the target client. End date and time 304
Represents the end date and end time of the time zone in which the target software is distributed to the target client.

FIG. 5 is a transfer capacity table storing transfer capacity information for each time zone managed by the transfer capacity management unit 3 of FIG. The transfer capability table has a start time 401, an end time 402, and a transfer capability 403. Start time 401
Represents the start time of the time zone. The end time 402 indicates the end time of the time zone. The transfer capacity 403 indicates the transfer capacity in the corresponding time zone, and is a numerical value such as “1000”, and the unit is b.
ps.

Next, the operation of transmitting software in the server will be described with reference to the flowchart of FIG.

In the server 1, as a preparation for distribution, an operation manager selects software to be distributed from among the software registered in the software management unit 2, and determines a distribution destination and an installation completion date and time. However, the installation completion date and time need not be set. These pieces of information are set in the installation completion date and time 104 and the distribution destination 105 of the software information table (step 50).
1). The distribution schedule is automatically determined from the software information table in FIG. 2, the distribution time table in FIG. 3, and the transfer capability table in FIG. 5, and information is set in the distribution schedule table in FIG. 4 (step 502). . The software for which the schedule has been set is distributed based on the distribution schedule table of FIG. 4 (step 503).

Next, the operation of the distribution schedule processing in step 502 will be described in detail with reference to the flowchart of FIG.

In the server 1, if software whose information is set exists in the distribution destination 105 of the software information table, distribution schedule processing is started (step 601). It is checked whether the installation completion date and time 104 of the software information table is set for the target software (step 602). If it is set, the information of the time zone of the start time 401 and the end time 402 from the transfer capability table of FIG.
(Step 603). The distribution time zone is determined from the software capacity 102, the installation completion date and time 104, and the transfer capability 403 for each time zone. However, a time zone with a higher priority 203 is preferentially set as a distribution time zone, and a time zone with a priority 203 of 0 is not set as a distribution time zone. In addition, a schedule is set such that among the software distributed at the same time, the one whose installation completion date and time is earlier is distributed first (step 604). It is checked whether the schedule created in step 604 can be distributed by the installation completion date and time (step 60).
5). If the distribution is possible, the information of the distribution schedule is set in the distribution schedule table of FIG. 4, and the process is terminated (step 607). If the distribution is not possible in step 605, the operation manager is caused to reset the installation completion date and time, and the information of the installation completion date and time 104 is updated.

Thereafter, the processing of step 604 is performed again (step 606). In step 602, if the information of the installation completion date and time 104 is not set, the distribution schedule is determined directly. Only the time zone having the highest priority 203 is set as the distribution time zone, and the schedule is set so that the distribution is performed after other software for which the installation completion date and time is set is distributed. After the schedule is determined, the process of step 607 is performed (step 60).
8).

Next, the operation of the transmission process of step 503 will be described in detail with reference to the flowchart of FIG.

The server 1 periodically checks the distribution schedule table shown in FIG.
Then, if the start date and time have not passed, this process is performed again (step 702). If the start date has passed, the transmission of the target software to the target distribution destination is started. The software name 301, the distribution destination 302, and the end date and time 304 are read from the distribution schedule table of FIG. 4 (step 703). The data corresponding to the number of unit data is transmitted to the distribution destination client 7 (step 7).
04). Then, it is checked whether all the data of the software has been transferred (step 705). If all the data has been transferred, the software transmission process ends. The corresponding information is deleted from the distribution schedule table of FIG. 4, and the process returns to step 702 (step 708).
If all data has not been transferred in step 705, the end date and time are compared with the current date and time. If the end date and time have not been reached, the data transfer process of step 704 is continued (step 706). If the end date and time has passed, the software transmission process is interrupted. If the information set in the distribution schedule table in FIG. 4 is significantly different from the actual situation, the information in the distribution schedule table is updated and the process returns to step 702 (step 707).

Next, the operation of receiving the software by the client will be described with reference to the flowchart of FIG.

The client 7 receives the software transmitted from the server 1 (step 801). Install the received software (step 80)
2).

Next, the operation of the receiving process in step 801 will be described in detail with reference to the flowchart of FIG.

The client 7 periodically monitors software transmission from the server 1. If not, the process is performed again (step 902). If there is software transmission, reception of the software is started (step 90).
3) Receive data for the number of unit data (step 90)
4). Then, it is checked whether all data has been received (step 905). If all data has been received, the software reception ends (step 908). Subsequently, the installation process of step 802 is performed, and the process returns to step 902. If all data has not been received in step 905, it is next checked whether distribution has been interrupted. If the distribution has not been interrupted, the process returns to the data receiving process of step 904 (step 906). If the distribution has been interrupted, the reception is interrupted and the process returns to step 902 (step 907).

In the above embodiment, the configuration in which the server manages the priority for each time zone is taken as an example. However, the configuration in which the client manages the priority for each time zone may be used. An example of an operation mode in which a client manages a plurality of time zones and priorities for distribution and installation processing will be described below.

FIG. 11 is a processing time zone table which stores priority information for each time zone for distribution and installation processing, which is managed by the processing time zone management unit 11 of FIG.
The processing time zone table has a start time 1001, an end time 10
02, priority 1003. The start time 1001 represents the start time of the time zone. The end time 1002 indicates the end time of the time zone. The priority 1003 indicates the priority for the distribution of the time zone, and is set as a numerical value. The priority 1003 indicates that the larger the number, the more suitable the time zone for distribution, and the smaller the number, the time zone in which the distribution should not be performed. In particular, when the priority 1003 is “0”, it indicates that the time period is a period during which distribution is prohibited. Information on the processing time zone table
Set automatically or by the client user.

FIG. 12 shows the distribution schedule management unit 3 of FIG.
9 is a distribution schedule table for storing distribution schedule information of software managed by the software. The distribution schedule table includes a software name 1101, a distribution destination 11
02, a start date and time 1103. Software name 1
Reference numeral 101 denotes a name of software to be distributed, which is a character string such as “software A” or “software B”. Distribution destination 11
02 represents information on the client of the distribution destination, and is a character string such as “host A” or “host B”. Start date and time 11
03 represents the date and time when the target software is distributed to the target client. FIG. 16 shows the installation processing unit 1 of FIG.
0 is an installation date and time table that stores information on the installation date and time managed by 0. The installation date and time table includes the software 1501 and the installation start date and time 150.
And 2. The software name 1501 indicates the name of software to be installed, and is a character string such as “software A” or “software B”. Installation start date and time 1
Reference numeral 502 denotes the date and time when the target software is installed.

FIG. 2 shows a software information table for storing software information managed by the software management unit 2 in FIG.

FIG. 5 shows a transfer capacity table for storing transfer capacity information for each time zone managed by the transfer capacity management section 9 in FIG.
Is shown in

Next, based on the flowchart of FIG.
The operation of transmitting software in the server will be described.

In the server 1, as preparation for distribution, the operation manager selects software to be distributed from among the software registered in the software management unit 2, and determines a distribution destination and an installation completion date and time. However, the installation completion date and time need not be set. These pieces of information are set in the installation completion date and time 104 and the distribution destination 105 of the software information table (step 50).
1). The name of the software to be distributed and the information of the distribution destination are set in the distribution schedule table of FIG.
The current date and time information is set in 103 (step 50).
2). The distribution is performed based on the distribution schedule table of FIG. 12 (step 503).

Next, the operation of the transmission process of step 503 will be described in detail with reference to the flowchart of FIG.

The server 1 periodically checks the distribution schedule table shown in FIG.
If the start date and time have not passed, this processing is performed again (step 1202). If there is one whose start date and time has passed, the software name 1101 and the distribution destination 1102 are read from the distribution schedule table of FIG. Also, from the software information table of FIG.
02, the installation completion date and time 104, and the installation time 103 are read. Notify the target client 7 of the information of capacity, installation completion date and time, and installation time,
Inquires whether reception is possible. When the client 7 receives a notification of refusal of reception, the information of the next distribution start date and time that has been notified at the same time is overwritten on the corresponding start date and time 1103 of the distribution schedule table in FIG. 12 and the process returns to step 1202 (step 1203). ). If reception is possible, transmission is started (step 1204). The data corresponding to the number of unit data is transmitted to the distribution destination client 7 (step 1205). Then, it is checked whether all data of the software has been transferred (step 120).
6). If all the data has been transferred, the software transmission process ends. The corresponding information is deleted from the distribution schedule table of FIG. 12, and the process returns to step 1202 (step 1209). If all data has not been transferred in step 1206, it is checked whether there is a request from the client 7 to interrupt reception. If there is no interruption request, the data transfer process in step 1205 is continued again (step 1207). If there is a suspension request, the transmission process is suspended. At this time, the next distribution start date and time received from the client 7 is overwritten on the corresponding start date and time 1103 in the distribution schedule table of FIG.
The process returns to step 2 (step 1208).

Next, the operation of receiving the software in the client will be described with reference to the flowchart of FIG.

The client 7 receives the software transmitted from the server 1 (step 801). Install the received software (step 80)
2).

Next, the operation of the receiving process in step 801 will be described in detail with reference to the flowchart of FIG.

The client 7 periodically monitors a software transmission request from the server 1. If not, this process is performed again (step 1302). If there is a software transmission request, the software capacity, installation completion date and time, and installation time sent from the server 1 together with the request are acquired. From these information, the information of the transfer capability table of FIG. 5 and the information of the processing time table of FIG. 11 in the client 7, a reception schedule for installing the software by the installation completion date and time is obtained. At this time, if there are multiple pieces of software at the same time, the schedule with the earlier installation completion date and time is preferentially received. Based on this schedule, it is determined whether to execute reception from the current time. When performing reception, a transmission request is issued to the server 1. If the reception is not performed immediately, the reception start date and time are transmitted to the server 1 together with the reception rejection notification (step 13).
03). If reception is to be performed immediately, software reception processing is executed (step 1304). Data for the number of unit data is received (step 1305). Then, it is checked whether all data has been received (step 1306).
If all data has been received, the software reception ends. The installation date and time is determined from the installation time and the priority of the processing time zone and the installation completion date and time, and the software name 15 is added to the installation date and time table of FIG.
01 and the installation start date and time 1502 are set. Then, the process returns to step 1302 (step 1309). If it is determined in step 1306 that not all data has been received, it is checked whether the reception end date and time has passed. If the end date and time have not passed, the process returns to the data receiving process of step 1305 (step 1307). If the end date and time have passed, the reception is interrupted and the process returns to step 1302 (step 1308).

Next, the operation of the installation process of step 801 will be described in detail with reference to the flowchart of FIG.

In the client 7, periodically, as shown in FIG.
Examine the installation date / time table. The installation start date and time 1502 in the installation date and time table are compared with the current time. If there is no software whose installation start time has elapsed, this processing is performed again (step 140).
2). If there is software whose installation start date and time has elapsed, install that software. Then, the corresponding information in the installation date and time table of FIG. 16 is deleted, and the process returns to step 1402 (step 140).
3).

[0047]

As described above, according to the present invention, software can be distributed based on the priority for each time zone for processing. It can be reduced and can be distributed at a time when there is no problem in the work of the client user.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a server and a client according to a software distribution method according to the present invention in an embodiment of the present invention.

FIG. 2 is a diagram illustrating a software information table managed by a software management unit in FIG. 1;

FIG. 3 is a diagram showing a distribution time zone table managed by a distribution time zone management unit in FIG. 1;

FIG. 4 is a diagram showing a distribution schedule table managed by a distribution schedule management unit in FIG. 1;

FIG. 5 is a diagram illustrating a transfer capability table managed by a transfer capability management unit in FIG. 1;

FIG. 6 is a flowchart showing a form of software distribution according to the present invention.

FIG. 7 is a flowchart showing a mode for setting a software distribution schedule according to the present invention.

FIG. 8 is a flowchart illustrating a form of software transmission according to the present invention.

FIG. 9 is a flowchart showing a mode of receiving and installing software according to the present invention.

FIG. 10 is a flowchart showing a form of software reception according to the present invention.

FIG. 11 is a diagram showing a processing time zone table managed by a processing time zone management unit in FIG. 1;

FIG. 12 is a diagram showing a distribution schedule table managed by a distribution schedule management unit in FIG. 1;

FIG. 13 is a flowchart illustrating a form of software transmission according to the present invention.

FIG. 14 is a flowchart illustrating a form of software reception according to the present invention.

FIG. 15 is a flowchart showing a software installation mode according to the present invention.

FIG. 16 is a diagram showing an installation date / time table managed by the installation processing unit in FIG. 1;

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Server, 2 ... Software management part, 3 ... Distribution schedule management part, 4 ... Distribution time zone management part, 5 ... Transmission part, 6
... Transfer capability management unit, 7 ... Client, 8 ... Reception unit, 9
... Transfer capacity management unit, 10 ... Installation processing unit, 11 ...
Processing time zone management unit.

Claims (9)

[Claims] 1. A software distribution system for distributing and installing software from a server to a client via a network, wherein the server manages software management means for managing software to be distributed and information on a time zone in which the software can be distributed. Distribution time zone management means, distribution schedule management means for managing time for distributing software, transmission means for transmitting software to the client via a network, and transfer for managing network transfer capability between the server and the client Capacity management means, the client, the receiving means for receiving software transmitted via a network, transfer capacity management means for managing the network transfer capacity between the client and the server,
A software distribution method, comprising: installation processing means for installing distributed software; and processing time zone management means for managing information on a time zone in which processing such as distribution and installation is possible. 2. The software according to claim 1, wherein said distribution time zone management means of said server manages a plurality of time zones and associates them with priorities in software distribution processing. Distribution method. 3. The server according to claim 1, wherein the distribution schedule management unit of the server obtains information of software to be distributed obtained from the software management unit of the server, and obtains information of the distribution time zone management unit of the server. The distribution start date and time and the distribution end date and time are determined from the distribution time zone priority information and the transfer capability information acquired from the transfer capability management means of the server so that the installation is completed by the designated installation completion date and time. A software distribution method characterized by scheduling a distribution date and time including the following. 4. The software distribution according to claim 3, wherein, when distributing a plurality of software, the distribution schedule management means of the server preferentially schedules the one having a designated installation completion date and time earlier. Method. 5. The server according to claim 1, wherein the transmitting unit of the server acquires a distribution end date and time from the distribution schedule management unit of the server, and interrupts software distribution when the distribution end date and time has elapsed. Characterized software distribution method. 6. The method according to claim 1, wherein the processing time zone management means of the client manages a plurality of time zones and associates them with the priorities in receiving and installing software. Software distribution method. 7. The client according to claim 1, wherein the receiving means of the client comprises: information on software to be distributed; information on a processing time zone priority obtained from the distribution time zone managing means on the client; A software distribution method for determining, based on the transfer capability information acquired from the transfer capability management means, that software is to be received on the assumption that the installation is completed by a designated installation completion date and time. 8. The software distribution method according to claim 7, wherein when there are a plurality of pieces of software to be received, the receiving unit of the client preferentially receives a piece of software having a designated installation completion date and time earlier. 9. The client according to claim 1, wherein the receiving means of the client comprises: information on software being received; information on a processing time zone priority obtained from the distribution time zone managing means on the client; A software distribution method, wherein a date and time at which reception is interrupted is obtained from the transfer capability information acquired from the transfer capability management means, and if the date and time has elapsed, the software distribution method is interrupted.