JP2008171289A - Version update method for software, program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable each of a plurality of information processors to easily perform version-up of a software component of the own information processor without a server for version up. <P>SOLUTION: In the version update method for software component for updating the version by acquiring an update software component, a version information collection part 34 within a PC 1 collects version information of a specific software component operated in each of other PCs 1, a version information display part 35 displays a list of the version information to select one piece of version information therefrom, and a version up part 36 acquires a software component corresponding to the selected version information from the PC 1 that is the providing source of the version information concerned, and updates the version of the software component within the own PC 1. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a version upgrade technology such as application software (program) that operates on an OS (operating system) of an information processing apparatus, and more particularly to a version upgrade technology via a network.

As a method for upgrading a software component (program), there is a method in which a management server connected to a network distributes the latest version of the software component to an information processing apparatus such as a personal computer via the network. Such a version upgrade method is widely used as a method in which an administrator manages the version of a specific software component of each information processing apparatus connected to the network. This is particularly common when the target is a software component that needs to be forcibly upgraded, such as business software.
On the other hand, there are many cases where the user of each information processing apparatus selects the version of the software component used in each information processing apparatus.

The related prior art disclosed in Patent Document 1 will be described below.
In this prior art, a plurality of image forming apparatuses are connected, and they share the printing work. When the software component of the self-image forming apparatus constituting such a group of image forming apparatuses is updated, the version of the same software component used in another image forming apparatus is confirmed, and the version older than the self-image forming apparatus If there is an image forming apparatus using the software component, version upgrade data is transmitted to the image forming apparatus to upgrade the software component.

Specifically, when the software component of the self-image forming apparatus is updated, a version notification request command for requesting transmission of version information indicating the version of the software component is transmitted to the other image forming apparatus, and in response to the command. The version information transmitted from the other image forming apparatus is received, the version information of the self image forming apparatus is compared with the version information acquired from the other image forming apparatus, and the software component of the version older than the self image forming apparatus is used. The upgrade data is transmitted to the other image forming apparatus.
JP 2006-184940 A

However, it is not appropriate to provide a special management server to upgrade software components. This is because the version upgrade process is only performed from time to time, and the management server is mostly unused. The prior art disclosed in Patent Document 1 is intended to upgrade the version of another image forming apparatus, and is different from the present invention, which is intended to upgrade the version of the information processing apparatus.
The present invention is intended to solve such problems of the prior art, and each of a plurality of information processing apparatuses connected to a network and using the same software component prepares a specific version upgrade server. An object of the present invention is to provide a version upgrade technique that can easily upgrade the software components of the information processing apparatus without having to do so.

According to the first aspect of the present invention, in the software version update method for updating the software component version of the information processing apparatus by acquiring the software component via a network, the specification that is operating in each other information processing apparatus Software component version information is collected from each information processing device, one version information is selected from the collected version information, and the software component corresponding to the selected version information is acquired from the information processing device of the version information providing source And updating the version of the software.
According to a second aspect of the present invention, in the software version updating method according to the first aspect, the version information of the information processing apparatus is provided in response to an acquisition request from another information processing apparatus, and the version information provided A corresponding software component is held, and the software component is provided in response to an acquisition request from another information processing apparatus.

According to a third aspect of the present invention, in the software version updating method according to the first or second aspect, one or more pieces of version information collected from another information processing apparatus are displayed, and one version information in the displayed information is displayed. When instructed, the software component corresponding to the instructed version information is acquired from the information processing apparatus of the version information providing source, and the software version is updated.
According to a fourth aspect of the present invention, in the software version update method according to the first, second, or third aspect, the cumulative operating time is measured by measuring the cumulative operating time of the specific software component that is currently operating. The configuration is included in the version information of the software component, and when the version information collected from another information processing apparatus is displayed, the accumulated operation time included in the version information is displayed.

According to a fifth aspect of the present invention, in the software version update method according to the first, second, or third aspect, by counting the number of occurrences of abnormality related to the software component when the specific software component that is currently operating is used. The abnormality occurrence count is included in the version information of the software component, and the abnormality occurrence count is displayed when displaying the version information collected from another information processing apparatus.
According to a sixth aspect of the present invention, in the software version update method according to the first, second, or third aspect, the operating OS type information when the specific software component currently operating is used is included in the version information of the software component. The operating OS type information is displayed when the version information collected from another information processing apparatus is displayed.

According to a seventh aspect of the present invention, in the software version update method according to the first, second, or third aspect, version down history information indicating that the specific software component that is currently operating is downgraded. The version down history information is included in the version information of the software component, and the version down history information is displayed when displaying the version information collected from another information processing apparatus. And
The invention according to claim 8 is the software version update method according to claim 1 or 2, wherein when the version information of the other information processing apparatus is collected, the information processing apparatus having the latest version of the collected version information The software component of the version is acquired from the software, and the version is upgraded to the software component.

According to a ninth aspect of the present invention, in the software version update method according to the eighth aspect, the upgrade condition is designated, the upgrade condition information is retained, and the specific software component currently in operation is retained. Version information including performance information is collected from each information processing device, and when the performance information satisfying the upgrade condition specified in the collected version information exists, the software component of the latest version from the information processing device And upgrading to the software component.
According to a tenth aspect of the present invention, in the software version updating method according to the ninth aspect, a minimum operation time is designated as the upgrade condition, the minimum operation time is retained, and the currently operating specification is performed. Version information including the cumulative operating time of the software component is collected from each information processing apparatus, and the collected version information has the latest version and the cumulative operating time exceeds the minimum operating time. The latest version of the software component is acquired from the information processing apparatus, and the version is upgraded to the software component.

The invention according to claim 11 is the software version update method according to claim 9, wherein the maximum abnormality occurrence count is designated as the upgrade condition, the maximum abnormality occurrence count is held, and the software is currently operating. Version information including the number of occurrences of abnormality when using the specific software component is collected from each information processing apparatus, the collected version information has the latest version, and the number of occurrences of abnormality is equal to or less than the maximum number of occurrences of abnormality. When there is something, the latest version of the software component is acquired from the information processing apparatus, and the version is upgraded to the software component.
According to a twelfth aspect of the invention, in the software version updating method according to the ninth aspect, when an operating OS type is specified as the upgrade condition, version information including the operating OS type is collected from each information processing apparatus. When the collected version information has the latest version and the operating OS type is the same as the operating OS type of the information processing apparatus, the latest version of the software component is acquired from the information processing apparatus. The software component is upgraded to a new version.

  According to a thirteenth aspect of the present invention, in the software version update method according to the ninth aspect, each information processing apparatus indicates the version information as the version information when the specific software component in operation is downgraded. Down-history information is stored, and when version-down history is specified as the version-up condition, when version information including the version-down history information is collected from each information processing apparatus, When there is one having the latest version and not having the version down information, the latest version of the software component is acquired from the information processing apparatus, and the version is upgraded to the software component.

The invention described in claim 14 is the software version update method according to any one of claims 8 to 13, wherein there are a plurality of pieces of version information collected that satisfy the set version upgrade conditions. The software component corresponding to the version information with the longest accumulated operation time or the version information with the minimum number of occurrences of the abnormality is acquired, and the version is upgraded to the software component.
According to a fifteenth aspect of the present invention, there is provided a program for causing an information processing apparatus to perform a version update of the method according to any one of the first to fourteenth aspects.
The invention described in claim 16 is a recording medium readable by an information processing apparatus in which the program described in claim 15 is recorded.

  According to the present invention, the version information of a specific software component operating in each other information processing apparatus is collected from each information processing apparatus, one version information is selected from the collected version information, and the selected version The software component version of the local information processing device can be updated by acquiring the software component corresponding to the information from the information processing device that provides the version information, so that the local information can be updated without preparing a specific upgrade server. Software components of processing devices can be easily upgraded. In addition, since the version can be automatically upgraded according to the version upgrade conditions designated by the user, the user's hand is not troubled.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. However, the components, types, combinations, shapes, relative positions, and the like described in this embodiment are not merely intended to limit the scope of this description unless otherwise specified, but are merely illustrative examples. .
FIG. 1 is a system configuration diagram showing a schematic configuration of a network system as an embodiment of the present invention. As shown in the figure, a plurality of personal computers (hereinafter referred to as PCs, which corresponds to the information processing apparatus described in the claims) 1 are connected to a data communication network (network) 2.
FIG. 2 is a block diagram showing a schematic configuration of hardware of the PC 1. As illustrated, the PC 1 includes a CPU 11 that operates according to a program (software), a ROM 12 in which a basic program is written, a RAM 13 that temporarily stores programs and data, and a hard disk storage device that stores programs and data. (Hereinafter referred to as an HDD) 14, an HDD control unit (hereinafter referred to as an HDC) 15 that controls reading and writing of data with respect to the HDD 14, a keyboard, a mouse, and the like to input data and input instruction information An input device 16, a display device 17, an input / output interface unit 18 that controls the input device 16 and the display device 17, a network interface unit 19 that controls communication with another PC 1 or the like performed via the data communication network 2, Read and write to the removable recording medium 23 A media (recording medium) drive device (hereinafter referred to as MDD) 20, a media drive control unit (hereinafter referred to as MDDC) 21 that controls reading and writing of data with respect to the MDD 20, and the current time managed by the PC 1 A clock circuit 22 that counts and outputs (hereinafter referred to as system time) is provided.
Examples of the present invention will be described below.

  FIG. 3 is a block diagram showing a configuration of a version upgrade processing unit realized in each PC 1. The upgrade processing unit 30 is realized by the CPU 11 and the program read into the RAM 13 (see FIG. 2). As illustrated, the upgrade processing unit 30 includes a version upgrade condition setting unit 31 that allows the user to set a version upgrade condition prior to version upgrade, and a specific software component (hereinafter simply referred to as a PC 1a). Version information storage unit 32 that manages and stores version information (referred to as a software component), version information disclosure unit 33 that provides stored version information to another PC 1 (for example, PC 1b) upon request, and other information such as PC 1b A version information collection unit 34 that collects version information provided by the version information disclosure unit 33 of the PC 1, a version information display unit 35 that displays a list of version information collected by the version information collection unit 34, and in the displayed version information list Instructed Version upgrade unit 36 that acquires the software component of the version information from the PC 1 corresponding to the version information and upgrades the software component of the own PC, and software that provides the software component to another PC 1 (for example, PC 1b) upon request A disclosure unit 37 and the like are provided. As shown in FIG. 3, each version of the software component C and each version information is stored in the HDD 14.

FIG. 4 is an operation flow of the upgrade process executed by the upgrade processor 30. Hereinafter, this operation flow will be described.
First, the version information collection unit 34 activated by the user's version upgrade instruction connects the version information of the operating software component to the data communication network 2 by transmitting a version information request message using the broadcast communication function. Collect from each PC 1 that has been made (step 1). Then, the version information display unit 35 displays a list of the collected version information on the display device 17 (step 2).

A display example is shown in FIG. As shown in the figure, each record consisting of one line is version information collected from another PC 1 and includes the IP address of the PC, the version number of the software component, the cumulative operation time of the software component, and the use of the software component. The number of occurrences of abnormality at the time, presence / absence of version down history The reason why the accumulated operation time, the number of occurrences of abnormality, the presence / absence of a version down history, and the like are provided as version information is that such information is effective in determining the reliability of the software component.
Information about the OS type running on each PC may be provided as version information. This is because whether or not a software component operating on another PC 1 operates reliably on its own PC largely depends on the operating OS type. Note that the number of occurrences of abnormality is counted as one occurrence, for example, when the target software component is used and the software component does not end normally. The version down is to return the version to the old version.

The version information display unit 35 allows the user to select one from such a list (step 3), and when the selection is made, the version upgrade unit 36 selects the software component of the selected version information as its version. Obtained from the PC 1 that sent the information (step 4).
Subsequently, the version upgrade unit 36 stores the acquired software component in the HDD 14 and installs the software component to upgrade (step 5).
Further, version information of the software component is created, and the initial value is stored in the HDD 14 as a version upgrade history (step 6). An example of the initial value is shown below.
Version: Version 3
Operating OS type: Operating OS type of own PC Operating time: 0
Abnormal frequency: 0
Version down history: No

Thereafter, the version information storage unit 32 periodically records the history of the current version. FIG. 6 shows an operation flow of the operating time history recording (logging) of this software component as one of them. Hereinafter, this operation flow will be described.
First, as shown in FIG. 6A, when the target software component is activated, the version information storage unit 32 acquires the current system time from the clock circuit 22 and stores it in the RAM 13 as an internal value ( (Step 11).
Thereafter, when the operation of the software component ends, as shown in FIG. 6B, the version information storage unit 32 acquires the system time at that time again (step 15). Then, the operating time is calculated by subtracting the system time saved at the time of startup from the system time (step 16).
Subsequently, the version information storage unit 32 acquires the accumulated operating time so far from the latest version (current version) information record in the version information table in the HDD 14 (step 17). Then, the current operating time is added to the value to calculate a new cumulative operating time (step 18), and the cumulative operating time is written in the latest version information record to update the cumulative operating time (step 19).

Regarding the number of occurrences of abnormalities, the target software component sets a predetermined flag (variable) at the time of activation and lowers the flag at the end, while the version information storage unit 32 periodically checks the flag, and the software component If the flag is set even though is not activated, the number of occurrences of abnormality so far is acquired from the latest version information record in the version information table in the HDD 14, and 1 is added to the value. Write the value to the latest version information record and update it. Note that the version information storage unit 32 drops the flag when the flag is confirmed.
When the target operating software component is returned to the old version, the version information storage unit 32 writes a value indicating “Yes” in the version down history portion in the latest version information record.

  FIG. 7 shows an example of the version information table. In FIG. 7, each row is a version information record corresponding to each version. Note that the top line written with records on the left side is for explanation purposes and does not actually exist. As is apparent from FIG. 7, the record increases by one each time the version is changed. In this example, the version 1.2 is incorporated, but since the frequency of occurrence of abnormalities is high, the version has been downgraded to the version 1.1, and is currently operating with the version 1.1.

FIG. 8 is an embodiment showing a data construction method of each version of the software component. In FIG. 8A, each version has all the data necessary for execution individually, whereas in FIG. Only the differences (different parts) for the version of. Version upgrade is performed mainly for function addition, so the latter is also effective. The example of FIG. 8B has a difference with respect to version 1.0. In this case, for example, when executing version 1.2, both version 1.0 and version 1.2 are used.
Thus, according to this embodiment, each of a plurality of information processing apparatuses using the same software component can easily upgrade the software component of its own information processing apparatus without preparing a specific version upgrade server. .

In the second embodiment, the version upgrade processing unit 30 having the configuration shown in FIG. 3 performs automatic version upgrade by setting the upgrade conditions in advance. Hereinafter, this embodiment will be described in accordance with the operation flow shown in FIGS.
FIG. 9 is an operation flow for determining whether or not to upgrade, and the upgrade condition setting unit 31 allows the user to specify the upgrade condition in advance and obtains it (step 21). For example, the software component to be updated is designated to be upgraded to that version if the cumulative operation time of the version of the current version of the own PC is more than several hours.

FIG. 11 is a user interface screen displayed when the upgrade condition setting is executed by the upgrade condition setting unit 31. As is apparent from the figure, in this embodiment, it is possible to set the automatic upgrade timing and automatic upgrade conditions. The timing is “execute now”, when the PC starts, when the PC ends, or at a specified time. As the upgrade conditions, the cumulative operation time, the number of occurrences of an abnormality, the same OS, the absence of version down history, and the like can be set.
Thereafter, the corresponding software running from each PC 1 connected to the data communication network 2 by the transmission of the version information request message using the broadcast communication function by the version information collection unit 34 activated by the user's version upgrade instruction Component version information is collected (step 22). Note that the version information collection unit 34 may be automatically activated periodically instead of an instruction from the user.

When version information is collected from another PC 1, the version information collecting unit 34 activates the version upgrading unit 36, and the version number in the collected version information indicates the current version of its own PC. It is determined whether it is greater than the number, that is, whether it is newer than the current version (step 23). If there is no new version in the version numbers indicated by all the collected version information (No in step 23), it is determined that the version is not upgraded, and the operation flow is exited.
On the other hand, if at least one of the collected version information is newer than the current version (Yes in step 23), if the operating time limit is valid as an upgrade condition (in step 24) Yes), it is determined from the collected version information of the new version whether or not the cumulative operation time of the software component exceeds the limit operation time set as the upgrade condition (step 25). If there is no excess (No in step 25), it is determined that the version is not upgraded, and the operation flow is exited.

On the other hand, if the operation time limit is not effective (No in step 24) and if the operation time limit is exceeded (Yes in step 25), the abnormality occurrence frequency limit is enabled as a version upgrade condition. If yes (Yes in step 26), whether the number of occurrences of abnormalities during the operation of each software component exceeds the limit occurrence number of faults set as the version upgrade conditions from the version information that has passed the previous version upgrade conditions. It is determined whether or not (step 27). If all items have been exceeded (Yes in step 27), it is determined that the version is not upgraded, and the operation flow is exited.
On the other hand, if the limit on the number of occurrences of abnormalities is not effective (No in step 26) and if the limit number of occurrences of abnormalities is not exceeded (No in step 27), the operating OS type is set as the upgrade condition. If the designation is valid (Yes in step 28), whether or not the operating OS type of each software component is the same as the operating OS type of its own PC from the version information that has passed the previous upgrade conditions. Determine (step 29). If there is no same operating OS type (No in step 29), it is determined that the version is not upgraded, and the operation flow is exited.
On the other hand, if the designation of the operating OS type is not valid (No in step 28), and if there is an identical operating OS type (Yes in step 29), it is determined that the version is to be upgraded, and this operation flow is exited. .

Next, the operation flow of the upgrade process executed by the upgrade unit 36 will be described with reference to FIG.
Here, the version upgrade determination shown in FIG. 9 is performed (step 31), and if it is determined that the version upgrade is not performed (No in step 32), this operation flow is exited and the version upgrade is determined (step 31). In step 32, the software component is acquired from the PC 1 that owns the corresponding latest version of the software component (step 33). If there are a plurality of corresponding versions, for example, the software component is acquired from the PC 1 that provided the version information with the longest accumulated operation time or the version information with the minimum number of occurrences of abnormality.
Subsequently, the acquired latest version of the software component is stored in the HDD 14 (step 34). Further, version information of the software component is created, and the initial value is stored in the HDD 14 as a version upgrade history (step 35).
Thus, according to this embodiment, the same effects as those of the first embodiment can be obtained, and since it is fully automatic, it is not necessary to bother the user.

  As described above, the software upgrade method of the present invention has been described with respect to one embodiment. However, a program (software) programmed according to the upgrade method as described above is recorded on a removable recording medium, and the recording medium has been described so far. In such an information processing apparatus, by installing it in an information processing apparatus such as a personal computer that could not be upgraded according to, or by transferring such a program to such an information processing apparatus via a network The software version can be upgraded according to the present invention.

1 is a system configuration diagram showing a schematic configuration of a network system as an embodiment of the present invention. 1 is a block diagram showing a schematic configuration of hardware of a personal computer as an embodiment of the present invention. It is a block diagram which shows the structure of the version-up process part implement | achieved in each personal computer as 1st Example of this invention. It is a flowchart which shows the operation | movement flow of a version upgrade process as 1st Example of this invention. It is a screen figure which shows the example of a display of a version information list as 1st Example of this invention. It is a flowchart which shows the operation | movement flow of operation time history recording as 1st Example of this invention. It is a data block diagram which shows the structural example of a version information table as 1st Example of this invention. It is explanatory drawing which shows the data construction method of the software component of each version as 1st Example of this invention. It is a flowchart which shows the operation | movement flow which determines whether it upgrades as 2nd Example of this invention. It is a flowchart which shows the operation | movement flow of a version upgrade process as 2nd Example of this invention. It is a screen figure which shows the upgrade condition setting screen as 2nd Example of this invention.

Explanation of symbols

1 Personal computer 11 CPU
14 Hard disk storage device 17 Display device 19 Network interface unit 22 Clock circuit 30 Version upgrade processing unit 31 Version upgrade condition setting unit 32 Version information storage unit 33 Version information disclosure unit 34 Version information collection unit 35 Version information display unit 36 Version upgrade unit 37 Software disclosure department

Claims (16)

  In the software version update method for updating the software component version of the information processing apparatus by acquiring the software component via the network, the version information of the specific software component operating on each other information processing apparatus The information is collected from the information processing apparatus, one version information is selected from the collected version information, the software component corresponding to the selected version information is acquired from the information processing apparatus of the version information providing source, and the software version is updated. A software version updating method.   2. The software version update method according to claim 1, wherein the version information of the information processing apparatus is provided in response to an acquisition request from another information processing apparatus, and a software component corresponding to the provided version information is held. And providing the software component in response to an acquisition request from another information processing apparatus.   3. The software version update method according to claim 1 or 2, wherein one or more version information collected from another information processing apparatus is displayed, and one of the displayed version information is instructed. A software version update method, comprising: obtaining a software component corresponding to version information from an information processing apparatus of the version information provider and updating the software version.   4. The software version updating method according to claim 1, wherein the accumulated operating time is included in the version information of the software component by measuring the accumulated operating time of the specific software component currently operating. A software version update method, characterized in that, when displaying version information collected from another information processing apparatus, the accumulated operation time included in the version information is displayed.   4. The software version update method according to claim 1, 2, or 3, wherein the abnormality occurrence count is calculated by counting the abnormality occurrence count associated with the software component when the specific software component currently in operation is used. A software version update method characterized in that the number of occurrences of abnormality is displayed when displaying version information collected from another information processing apparatus, which is included in the component version information.   4. The software version update method according to claim 1, wherein the operating OS type information when the specific software component currently operating is used is included in the version information of the software component, and other information processing is performed. A software version update method, wherein the operating OS type information is displayed when displaying version information collected from a device.   The software version update method according to claim 1, 2, or 3, wherein when the specific software component currently operating is downgraded, the version down history information indicating the fact is retained, thereby maintaining the version. A software version update method characterized in that down history information is included in the version information of the software component, and the version down history information is displayed when the version information collected from another information processing apparatus is displayed.   3. The software version update method according to claim 1, wherein when the version information of the other information processing apparatus is collected, the software component of the version is acquired from the information processing apparatus having the latest version among the collected version information. And updating the software component to update the software component.   9. The software version update method according to claim 8, wherein version upgrade conditions are designated, the version upgrade condition information is held, and version information including performance information of the specific software component currently operating is When the performance information that satisfies the upgrade conditions specified in the collected version information is collected from each information processing device, the latest version of the software component is acquired from the information processing device, and the software component is stored in the software component. A software version update method characterized by upgrading.   10. The software version update method according to claim 9, wherein a minimum operation time is designated as the upgrade condition, the minimum operation time is retained, and an accumulated operation time of the specific software component currently operating is determined. Version information is collected from each of the information processing devices, and when the collected version information has the latest version and the cumulative operation time exceeds the minimum operation time, the latest information from the information processing device A software version update method, comprising: obtaining a version of a software component and upgrading the software component.   The software version update method according to claim 9, wherein a maximum abnormality occurrence number is designated as the upgrade condition, the maximum abnormality occurrence number is held, and when the specific software component currently in operation is used. Version information including the number of occurrences of abnormality is collected from each information processing apparatus, and the information processing is performed when the collected version information has the latest version and the number of occurrences of abnormality is equal to or less than the maximum number of occurrences of abnormality. A software version update method, comprising: obtaining the latest version of a software component from an apparatus, and upgrading the software component to the version.   10. The software version update method according to claim 9, wherein when an operating OS type is designated as the upgrade condition, version information including the operating OS type is collected from each information processing apparatus, and the version information is collected. The latest version of the software component is acquired from the information processing apparatus, and the version is upgraded to the software component. A software version updating method.   10. The software version update method according to claim 9, wherein each information processing apparatus holds version down history information indicating that as the version information when the specific software component in operation is downed. When a version down history is designated as the version up condition, when version information including the version down history information is collected from each information processing apparatus, the collected version information has the latest version and When there is a device that does not have the version down information, the latest version of the software component is acquired from the information processing apparatus, and the software version is updated to the software component. Method.   14. The software version update method according to claim 8, wherein when there are a plurality of pieces of version information collected in the collected version information satisfying the set version upgrade conditions, the version having the longest cumulative operation time is used. A software version update method comprising: obtaining a software component corresponding to information or version information with the smallest number of occurrences of abnormality, and upgrading to the software component.   A program for causing an information processing apparatus to perform version update of the method according to any one of claims 1 to 14.   A recording medium readable by an information processing apparatus on which the program according to claim 15 is recorded.

Images