System for registering and deleting software distributed destination

Description: TECHNICAL FIELD [Detailed description of the invention]

【0001】

[Technical field to which the invention belongs]

The present invention relates to a software distribution destination registration and deletion system that manages such registration and deletion as appropriate according to the usage status of a distribution destination that distributes software via a network or the like.

【0002】

[Conventional technology]

When distributing various programs and data necessary for the business to a large number of information processing devices connected via LAN (local area network), etc., complete the list of distribution destinations and complete the list of the programs and data. Management including version etc. is performed on a certain terminal. This terminal device is hereinafter referred to as a distribution source device. In addition, other terminal devices that receive distribution of programs and data will be referred to as distribution destination devices. In addition, the objects to be distributed, such as programs and data, will be collectively referred to as software.

【0003】

In such a system, the distribution source device distributes the software to the distribution destination device as needed or periodically. For this purpose, the distribution source device stores the distribution destination list, software version, and other information in the storage device. The distribution destination devices connected to such a network may be newly installed or disconnected depending on the usage status. In such a case, the distribution source device updates and corrects the distribution destination list each time.

【0004】

[Problems to be Solved by the Invention]

By the way, in the conventional system as described above, the management of registration and deletion of the distribution destination is exclusively entrusted to the operator who operates the distribution source device. Therefore, there is a problem that the amount of work of the operator increases as the number of distribution destinations increases. If the number of distribution destinations increases too much, mistakes are likely to occur in such registration deletion processing, and improvement in management has been required.

【0005】

[Means for solving problems]

The present invention adopts the following configuration in order to solve the above points. <Configuration 1> A distribution source device that manages software and distributes the software through the network and a distribution destination device that receives the distribution of the software through the network are provided, and each distribution destination device is equipped with the above distribution source at startup. A message including an identifier for distinguishing its own device from other devices is sent to the device, and the distribution source device registers the identifier included in the received message in the software distribution destination register and the corresponding identifier. A software distribution destination registration system characterized in that a distribution destination device having the above is set as a software distribution destination.

【0006】

<Explanation> Software includes programs and data, and distribution includes the case of distributing new software and the case of updating software. The identifier is uniquely assigned to each device to distinguish each distribution destination device. The telegram may include various communication telegrams in addition to the identifier of the distribution destination device. The telegram is not necessarily for the purpose of registering the distribution destination, but may be for the purpose of another information communication. In the software distribution destination register, an identifier of the distribution destination device to which the software is distributed and a list of distribution programs, data, and the like are registered. As a result, the distribution source device can automatically extract and manage the identifier of the distribution destination device from the received telegram, and keep the software distribution destination register up-to-date without inquiring to the distribution destination device. it can.

【0007】

<Structure 2> In Configuration 1, the distribution source device registers the received date and time in the software distribution destination register together with the identifier included in the telegram received from the distribution destination device, and does not transmit the telegram beyond the preset valid period. A software distribution destination deletion system characterized by deleting a distribution destination from a software distribution destination register.

【0008】

<Explanation> The non-use period of the distribution destination device can be found by taking the difference between the received date and time, that is, the last access date and time and the current date and time, and comparing it with the valid period. As a result, unused terminals can be automatically deleted from the distribution destination target.

【0009】

<Structure 3> In Configuration 2, the distribution source inquires whether the distribution source is in use or not to the distribution destination that does not send the telegram for the valid period or longer, and if it is in use, the inquiry date and time is set to the corresponding distribution destination. A software distribution destination registration and deletion system characterized in that both identifiers are registered in the software distribution destination register.

【0010】

<Explanation> A distribution destination device that sends a telegram to the distribution source device at startup and is continuously used thereafter is indistinguishable from an unused distribution destination device. Therefore, when the distribution source device tries to exclude a certain distribution destination device from the software distribution target, it decides to inquire whether it is continuously used or not before that. As a result, it is possible to prevent deregistration of the device during continuous use.

【0011】

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to specific examples. <Specific Example> FIG. 1 is a block diagram of a software distribution destination registration / deletion system of the present invention. In the system shown in the figure, a plurality of distribution destination devices 3 are connected to the distribution source device 1 via the network 2. Each device is configured by an arbitrary information processing device. A database 4 is provided in the distribution source device 1 for managing the distribution destination of the software. The software distribution destination register 5 is stored here.

【0012】

FIG. 2 shows an explanatory diagram of this software distribution destination register. In the software distribution destination register 5, an identifier for individually distinguishing each distribution destination device 3 and the last access date and time when a telegram including the identifier is received from the distribution destination device are written.

【0013】

FIG. 3 shows an explanatory diagram of the contents of the telegram transmitted by the distribution destination device 3 to the distribution source device 1. This telegram 6 is composed of a telegram type and an identifier, and other information. This telegram does not necessarily have to be used only to notify the distributor device 1 of the identifier. That is, it suffices if the identifier is included in the normal data transmission / reception telegram, and when the distribution source device 1 receives the identifier, it may be recognized and the registration process may be performed. That is, the distribution source device 1 detects some access operation of each distribution destination device 3, extracts an identifier from the telegram used in the access operation, and performs registration processing.

【0014】

FIG. 4 is an operation sequence chart of the system of the present invention. The specific operation of the apparatus of the present invention will be described with reference to this sequence chart. First, the distribution destination device 3 transmits a telegram to the distribution source device 1 after the startup, for example, when the power is turned on and the startup process is performed (step S1 and step S2). This telegram contains the identifier of the distribution destination device 3. The message at the time of startup is, for example, a content that notifies the distribution source device 1 that preparations for performing various processes have been completed. When the distribution source device 1 receives this telegram, it registers it in the software distribution destination register in step S3.

【0015】

FIG. 5 shows a flowchart illustrating this registration process in detail. First, in step S1, the telegram received from the distribution destination is read, and the identifier is acquired from the telegram. Next, in step S2, the software distribution destination register 5 is searched. Then, it is determined whether or not it has already been registered. If it is not registered, the process proceeds to step S4, and the identifier of the distribution destination is newly registered in the distribution destination register. If it has already been registered, the identifier registration process passes and the process proceeds to step S5. In step S5, the current date and time is acquired in association with the identifier in any case, and in step S6, the current date and time is set in the field of the last access date and time. That is, as a result, the identifier read from the telegram and the date and time when the telegram was received are recorded in the software distribution destination register 5. Next, in step S7, various necessary information is registered and set in the software distribution destination register 5. Examples of this include, for example, the distribution destination program, the version of each data, and other states.

【0016】

As described above, when the power is turned on and the startup process is performed by each distribution destination device 3 connected to the network 2, the identifier is always recognized by the distribution source device 1 and registered as the software distribution destination. Therefore, the operating distribution destination device is always set as the software distribution destination, and manual input management by an operator or the like becomes unnecessary.

【0017】

Next, the process for deleting the distribution destination will be described. FIG. 6 shows an explanatory diagram of system parameters for deleting such a distribution destination. This system parameter includes, for example, a valid period, a startup interval, and the like. Generally, if there is a terminal device that is connected to a network but is not used for a long period of time, it is not always necessary to distribute software to the terminal device. Therefore, the access interval of the distribution destination device is measured, and when the access interval exceeds a certain validity period, the registration of the distribution destination terminal is automatically deleted.

【0018】

FIG. 7 is a flowchart of the distribution destination deletion process. In step S1, the distribution source device acquires the current date and time. Then, in step S2, the software distribution destination register 5 is referred to, and the distribution destination identifiers are extracted in order from the first entry. Then, in step S3, it is determined whether or not the processing has been completed for all distribution destinations, and if it has not been completed, the process proceeds to step S4, and the current date and time and the final distribution destination terminal device of the extracted entry are used. Read the access date and time and calculate the difference from the current date and time. Then, in step S5, it is determined whether or not the difference is larger than the valid period. That is, if the time from the most recently accessed date and time to the present exceeds the valid period, the process proceeds to step S6 and proceeds to the deletion process of the distribution destination corresponding to the entry.

【0019】

In this specific example, the distribution destination is not unconditionally deleted, and it is inspected whether the distribution destination is currently in use. This can be achieved by making inquiries through network 2. As a result, if it is in use, the process proceeds to step S7, and the current date and time is set as the last access date and time. That is, even if the distribution source device is accessed at startup, a telegram is sent, and the identifier is registered, the distribution destination device that has been continuously used without turning off the power is the distribution source for a long period of time. May not access the device. Since it is unreasonable to delete such a terminal device from the distribution destination, such a process is provided. On the other hand, in step S6, if it is determined that the distribution destination beyond the valid period is not used, the process proceeds to step S8, and the identifier of the distribution destination is deleted from the software distribution destination register 5. In this way, the distribution of the software to the distribution destination is stopped. If the distribution destination device requests distribution of a program or the like, a telegram may be sent to the distribution source device 1 again to register the identifier.

【0020】

If you set the validity period and delete the distribution destination device that has not been accessed during that period, the software distribution destination register 5 that automatically registers only the distribution destination device in use as the distribution destination is created. Can be generated. Also, if you inquire whether the distribution destination device that has exceeded the valid period is in use and decide whether to delete it, compared to the method of inquiring all the distribution destination devices. The burden on the distribution source device is lightened, and optimal registration and deletion management is automatically possible.

【0021】

In the above specific example, an example of sending a telegram to the distribution source during the start-up process of the distribution destination device has been described, but after the start-up, the telegram is periodically transmitted at regular intervals and is in use. There is no problem even if the configuration is such that the distribution source device is informed of the fact. In addition, the above makes it possible to automatically manage the registration and deletion of software distribution destinations, and also has the effect of preventing data errors due to operational mistakes.

[Simple explanation of drawings]

[Figure 1]

It is a registration and deletion system block diagram of the software distribution destination by this invention.

[Figure 2]

It is explanatory drawing of the software distribution destination register.

[Fig. 3]

It is explanatory drawing of the contents of a transmission telegram.

[Fig. 4]

It is an operation sequence chart of the system of this invention.

[Fig. 5]

It is a distribution destination registration process flowchart.

[Fig. 6]

It is explanatory drawing of a system parameter.

[Fig. 7]

It is a distribution destination deletion processing flowchart.

[Explanation of symbols]

1 Distributor device 2 network 3 Distribution destination device 4 database 5 Software distribution destination register