JP4770242B2 - Software update information distribution system and software update information distribution method - Google Patents

Description

  The present invention relates to version upgrade of software installed in a terminal.

For secondary distribution of software in which an intermediate server is arranged between the distribution server and the target terminal, for example, the software upgrade of many target terminals is made more efficient while reducing the load on the distribution server and saving resources of the intermediate server. Technology is shown.
However, the software version used between the target terminals under the intermediate server is assumed to be the same version, and a case where a different version is used for each target terminal is not disclosed. Also, there is no disclosure of version upgrade by distribution of difference information or a method when software has a multi-component configuration (for example, Patent Document 1).

Also, in software distribution with an intermediate server, sending difference information between versions and files between the distribution server and the intermediate server reduces the network load and prevents other applications from being executed. Techniques to avoid are also shown.
However, the difference information is generated on the distribution server and distributed to the intermediate server, and a technique for creating the difference information on the intermediate server as necessary is not disclosed. In addition, a method in which the software has a multi-component configuration is not disclosed (for example, Patent Document 2).
Japanese Patent Laid-Open No. 9-146861 JP 2003-99297 A

A relatively large-scale software tends to be composed of a plurality of components. Components are provided as a single functional unit, and are often found in large-scale software, etc .. Software is divided into functional units to increase independence, sharing / reusability. This has the advantage that software development and maintenance can be made more efficient.
Software having a plurality of component configurations is released by combining these components.
Note that development of such software composed of a plurality of components is usually performed in units of components, and therefore, the timing of version upgrade is often different among components.

Also, there are often normal version dependencies between components used. In this case, each component may not operate normally unless it is used in an appropriate version combination. In such a case, when upgrading the software, it is necessary to select an appropriate version of the component according to the version dependency of each component, and the operation procedure becomes complicated.
Further, in an operation using a plurality of different versions of software used in terminals under the intermediate server, there may be cases where the new version to be upgraded is not the same between the terminals. Therefore, even in terminals in the same user base, there are cases where there are a plurality of update patterns (combination of old and new software versions) at the time of version upgrade (depending on the terminal), and the operation becomes more complicated.
In addition, software having such a multiple component configuration tends to increase in size. When upgrading, it is sufficient to acquire the necessary components from the distribution server. However, there is a concern that the distribution of software upgrade data composed of multiple components will increase the load on the network from the viewpoint of size. .

The present invention has been made to solve the above-described problems, and the data distributed from the distribution server to the intermediate server is the difference data between the versions of each component, the amount of transfer data is suppressed, and the network load between the two is reduced. To alleviate
In addition, the distribution server only needs to provide and manage the difference information between versions for each component, the necessary components for each software version, and its version information, and any component configuration of the software installed on each terminal. It is not necessary to prepare version upgrade data that considers the above, and the workload of server operations is reduced.

  Furthermore, the intermediate server obtains difference information of only components necessary for the subordinate terminals, creates a new distribution image, and distributes the information to the terminals, thereby saving resources of the distribution server and the intermediate server and reducing the network load. At the same time, it is possible to easily and efficiently carry out version upgrade work in cases where multiple versions of software are used in a mixed manner between terminals and when there are terminals that cannot directly access the distribution server. .

In addition, the inter-version difference data for version upgrade is sent from the intermediate server to the terminal, and a new version distribution image is created and installed by applying the difference on the terminal that has received the data, and distributed from the intermediate server to the terminal. The size of the upgrade data can be suppressed, and the network load between the two can be reduced.
Furthermore, the network load between the intermediate server and the distribution server can be reduced.

The software update information distribution system according to the present invention includes a distribution server in which difference information between new and old software for updating software is stored , and a distribution package received from the intermediate server that transmits an update request for installed software to the intermediate server. the applied to the installed software and the terminal to be updated, the update information holding means past update information used for software update and the difference information held by the past updating information and past difference information, wherein If the past update information corresponding to the update request and the past difference information do not exist in the update information holding means when the update request is transmitted by the terminal, the difference information stored in the distribution server Difference information acquisition means for acquiring difference information corresponding to the update request, and the difference information Update information generating means for generating the update information corresponding to the update request based the difference information acquired by the obtained means and to said last update information, and the update information the update information generated by the generating means the It said having a distribution package generation means and procedures for installing the update information to the terminal to generate a distribution package packaged, the package and distribute transmitting means for transmitting a distribution package generated by the distribution package generating unit to the terminal And an intermediate server.

  The present invention provides a difference between old and new software in which an intermediate server updates software when it does not store past update information and past difference information corresponding to this update request when a software update request is transmitted from a terminal. The difference information corresponding to the update request is acquired from the distribution server storing the information, the update information corresponding to the update request is generated based on the difference information, and the generated update information and the update information are installed in the terminal By generating a distribution package in which procedures are packaged and sending this distribution package to the terminal, the intermediate server transmits information for updating the terminal software to the distribution server or terminal with minimal access and minimum information. Network load can be reduced, and terminal software can be updated in a short time. It is possible to run rate well.

Embodiment 1 FIG.
FIG. 1 is a configuration diagram of a software secondary distribution system according to the first embodiment.
As shown in the figure, the software secondary distribution system includes a distribution server 100 for distributing software and one or more intermediate servers 200 connected to the distribution server 100 via a network. Further, one or more terminals 300 (terminal 300a, terminal 300b, terminal 300c,...) Exist under the intermediate server 200. The intermediate server 200 and the subordinate terminal 300 exist in two types of states: an online state connected via a network and an offline state not connected to a network.

Software distributed by the distribution server 100 is installed in the terminal 300, and the user uses these software.
Although only one intermediate server 200 is shown in the figure, the configuration is one or more, and each intermediate server 200 has one or more terminals 300 in the online state or offline state as described above. It shall be connected with.

Next, a general outline of components will be described.
FIG. 2 is an explanatory diagram of the configuration and update status (update history) of software to be distributed.
The software to be distributed is composed of a plurality of components. In this embodiment, the software is composed of two components named Comp1 and Comp2.
In general, a component is a unit of a program, and is a concept introduced in order to improve software componentization / reusability and improve the efficiency of development / maintenance.

  A program entity corresponding to one component is composed of one or more program files, and may include one or more data files referred to by the program. In addition, the components are upgraded individually, and the timing of performing the upgrade may be different between components. Furthermore, each component has a dependency relationship between components, and each component may not operate normally unless it is a combination of correct versions.

Next, software components of the present embodiment will be described.
In this embodiment, for example, Comp2 is a component that is also used by other software (assumed to be a common component), and Comp1 is a component that has a property of being used only by this software (dedicated component). Also good. Therefore, the common component Comp2 can be combined with a dedicated component other than Comp1 and used as other software.

Next, the release status of the software components of this embodiment will be described.
As shown in FIG. 2, Comp1 and Comp2 released version 8.0A at the same time. Currently, each component version is Comp1 in four versions from 8.0A to 8.3D, and Comp2 is 8.0A. And 8.1B versions have been released.
The dedicated component Comp1 requires the common component Comp2. In addition, both have a dependency relationship between versions, and Comp18.0A was developed on the premise of 8.0A of Comp2.

  Comp1 has been upgraded three times to 8.1B, 8.2C, and 8.3D after the release of 8.0A. Meanwhile, Comp2 has been upgraded only once to 8.1B. For this reason, the version dependency relationship between Comp1 and Comp2 is that Comp1 is 8.0A to 8.1B, Comp2 is 8.0A, and Comp1 is 8.2C, and Comp2 is 8.1B after the release. , Comp2 is assumed to be 8.1B.

Next, a software update pattern according to this embodiment will be described.
An example will be described in which two terminals, the terminal 300a and the terminal 300b shown in FIG. 2, are upgraded. The version timing in this embodiment is as follows.
The terminal 300a is currently in a state where Comp1 is 8.1B and Comp2 is 8.0A due to the previous version upgrade. The terminal 300b is currently in a state where Comp1 is 8.2C and Comp2 is 8.1B due to the previous version upgrade.
This version upgrade will be described by taking as an example a case where both the terminal 300a and the terminal 300b are updated to the latest version of Comp1 is 8.3D and Comp2 is 8.1B.

First, the configuration of the distribution server 100 will be described.
FIG. 3 is a configuration diagram of the distribution server 100.
The distribution server 100 includes a configuration information management unit 101 and a difference information generation unit 102, and the configuration information management unit 101 manages software to be distributed. Specifically, the configuration information 100a in which the correspondence between the configuration of each component of the software and the software version is defined, and the distribution program 100b corresponding to the software program entity are registered and managed. Further, the difference information generation means 102 generates difference information 100c between two versions of the registered distribution program 100b.

Next, the configuration information 100a, the distribution program 100b, and the difference information 100c will be described in detail.
As shown in FIG. 3, the configuration information 100a is table information that defines the correspondence between each version number of software and the version of a component constituting the software.
As described above, when Comp1 is a dedicated component and Comp2 is a common component, the software version number of the software to be upgraded in this embodiment is updated every time the version of Comp1, which is a dedicated component, is upgraded. As a result, a software version upgrade occurs. This is due to the following.

  Comp2 that is a common component may be upgraded on a unique schedule separately from Comp1 that is a dedicated component. However, when Comp2 is upgraded, Comp1 in a dependency relationship also supports this version upgrade. There is a possibility that some modification is required, and even if only Comp2 is upgraded, Comp1 may not operate normally. Also, even if Comp1 is not affected and can operate normally, performing software upgrade in order to individually upgrade only Comp2 is time-consuming and costly for operation, and the burden on the user is large. turn into.

Thus, since Comp1 depends on the version of Comp2, when Comp1 is upgraded, it is necessary to determine which version of Comp2 is targeted and to guarantee the operation. For this reason, when Comp2 is upgraded after the previous release of Comp1, it is usually necessary to support the new Comp2 in the next Comp1 upgrade, that is, to upgrade Comp2 together with Comp1. Think.
Therefore, when the version of Comp1 that is the dedicated component is updated, the version of the software is also updated, and when the version of Comp2 that is the common component is upgraded, it is a common component in accordance with the timing of version upgrade of Comp1 that is the dedicated component. The case where the version upgrade of Comp2 is performed at the same time is considered appropriate.

As described above, the update timing of the configuration information 100a is set when the version of Comp1 is upgraded and the software version is updated.
In this embodiment, Comp1: 8.0A, Comp2: 8.0A are defined as version 1, Comp1: 8.1B, Comp2: 8.0A are defined as version 2,..., And the latest version is version 4. Thus, Comp1 is 8.3D, and Comp2 is 8.1B.

At the same time, the configuration information management unit 101 registers the corresponding distribution program 100b in the distribution server 100. Furthermore, after this registration, the distribution server 100 transmits the updated configuration information 100a to the intermediate server 200 to notify that the version has been upgraded.
The intermediate server 200 holds the received configuration information 100a as the configuration information 200a, and when there is a version upgrade request from the terminal 300, the intermediate server 200 refers to the stored configuration information 200a to determine the version of the necessary component corresponding to the software version. Shall be confirmed.

Next, the distribution program 100b will be described.
FIG. 4 is an explanatory diagram of the distribution program 100b.
The distribution program 100b is generated and registered for each version of each component. The substance of the program itself (execution program files and data files to which it refers) and an installer file for installing this program (an operating environment setting information file such as Windows registry information or an installation script file) These two types are included. These file groups constituting the entity are collectively called a program file.

  The registration timing of the distribution program 100b to the distribution server 100 is performed at the upgrade timing of Comp1, that is, the software upgrade timing. At this time, it is assumed that the configuration information 100a is also updated at the same time, and the distribution program 100b, which is the entity of the correspondence between the configuration of the software component defined in the configuration information 100a and the software version, is always registered.

Next, the difference information 100c will be described.
FIG. 5 is an explanatory diagram of the difference information 100c.
The difference information 100c is generated and registered in units of components by the difference information generation means 102. The generation of the difference information 100c is performed on the program files in the old and new versions of the distribution program 100b.
In addition, as for the generation / registration timing of the difference information 100c, normally, after the distribution program for each component is registered, the difference generation with the immediately previous version is performed. Or it is good also as operation | use produced | generated by the update pattern with most implementation cases according to the operation | use form of upgrade.

Hereinafter, the configuration of the difference information 100c will be described with reference to FIG.
The difference information 100c includes three types of files: an update information file, a binary difference file, and an additional file.
The update information file is a file describing a file update status at the time of version upgrade and installation destination information of each file. Here, the file update status refers to the update status (no update, update, or deletion) of all files in the old version file and information about the files added in the new version (only if there are any). The information is information indicating an installation destination directory on the terminal regarding the update file and the additional file.

The binary difference file is a file that is generated for each updated file among the program files of the distribution program 100b, compares the files between the old and new versions, and outputs the difference data as a result.
The additional file is included only when there is a file added in the new version but not in the old version. The entity is the added file itself.
Of the program files, the installation file is also targeted for binary difference extraction, but is excluded from the binary difference extraction target, and a new version of the installation file is included as it is in the difference information 100b as an installation file separately from the above files. It does not matter.

Next, the configuration of the intermediate server 200 will be described.
FIG. 6 is a configuration diagram of the intermediate server 200.
The intermediate server 200 includes a version confirmation unit 201, a difference information acquisition unit 202, a distribution image generation unit 203, a distribution image holding unit 204, a distribution package generation unit 205, and a distribution package transmission unit 206.
Further, the intermediate server 200 receives the configuration information 100a from the distribution server 100 and holds it as the configuration information 200a. Similarly, the difference information 100b transmitted by the distribution server 100 is held as difference information 200b.

The distribution image generation unit 203 generates a distribution image 200c based on the old version of the distribution program 100b (distribution image 200c on the intermediate server 200) and the difference information 200b. The distribution image 200c is the same as the distribution program 100b of the same component version on the distribution server 100, and serves as update information for updating the software of the terminal 300.
In addition, the distribution package generation unit 205 creates a distribution package 200d corresponding to the upgrade of each terminal 300. The created distribution package 200d is distributed to each terminal 300, and each terminal 300 receives the distribution package 200d and upgrades the software.

Next, the operation of the intermediate server 200 in upgrading the terminal will be described.
FIG. 7 is an explanatory diagram of a version upgrade example of the terminal.
A software distribution procedure at the time of version upgrade will be described according to the version upgrade example in FIG.
Two terminals 300a and 300b exist as terminals under the distribution server 200 in FIG. 1, and different versions of software are used in the two terminals. As shown in FIG. 2, the software version shown in the configuration information 100a in FIG. 3 is version 2 for the terminal 300a (Comp1 is 8.1B, Comp2 is 8.0A), and the terminal 300b is version 3 (Comp1 is 8.2C). , Comp2 uses 8.1B).

Up to now, if the terminal 300b operates the latest version of software, and the terminal 300a is operated to operate one version of software older than the latest version for backup, the terminal 300b is the latest version. Even when an unknown failure that can occur in the terminal 300a occurs, the terminal 300a, which is an old version with an operation record, is always in an operable state.
However, in this version upgrade shown in FIG. 7, the latest version of the software version 4 (Comp1: 8.3D, Comp2: 8.1B) has become stable due to the passage of time after release, etc. This time, the operation of leaving one old version is stopped, and the software is upgraded to the latest version 4 for both the terminal 300a and the terminal 300b.

According to the definition of the configuration information 200a, the component required for the terminal 300a is that the 8.3D of Comp1 needs to be 8.1B, and the terminal 300a is versioned from 8.1B to 8.3D. When upgrading, Comp2 needs to be upgraded from 8.0A to 8.1B.
Therefore, the necessary difference information 200b requires two types of difference information, that is, Comp1 is 8.1B → 8.3D difference information, Comp2 is 8.0A → 8.1B difference information.

On the other hand, according to the definition of the configuration information 200a, the component required in the terminal 300b is a state where Comp1 is 8.2C and Comp2 is 8.1B installed. Therefore, when Comp1 is upgraded to 8.3D Comp2 requires 8.1B, but since Comp2 is already 8.1B, only Comp1 needs to be upgraded.
Therefore, the necessary difference information 200b is only one type of Comp1 from 8.2C to 8.3D.

Next, the upgrade process of the intermediate server 200 will be described.
FIG. 8 is a flowchart showing the processing procedure of the intermediate server 200 when the software of the terminal 300 is upgraded.
With reference to FIG. 8, the version upgrade processing procedure performed by the intermediate server 200 will be described using the version upgrade example of FIG. 7 as an example.
In the present embodiment, a case will be described in which the terminal 300a and the terminal 300b are simultaneously upgraded according to the version upgrade example of FIG.
Here, it is assumed that the intermediate server 200 is in a user base that uses software to be upgraded, and the intermediate server 200 and the two terminals 300a and 300b are connected via a network. .
First, in step S1, the upgrade request receiving unit 201 of the intermediate server 200 receives terminal information (the terminal 300a and the terminal 300) from which the user upgrades from the input device of the terminal 300a, the terminal 300b or directly from the input device on the intermediate server 200. 300b) and an upgrade request issued by inputting the version number to be upgraded are received. Here, the upgrade request by the input to the input devices of the terminals 300a and 300b is transmitted to the intermediate server 200 via the network.

Here, the issue of the upgrade request to the intermediate server 200 may be performed at the individual timing or at the same time from the terminal 300a and the terminal 300b.
Alternatively, a dedicated application may be prepared on the intermediate server 200 so that version upgrade requests for a plurality of terminals and a plurality of update patterns can be issued simultaneously. In this case, the intermediate server 200 analyzes the request, determines the number of necessary update patterns, and the distribution images necessary for each, and further determines and generates a more efficient distribution image and distribution package generation method. As a result, it is possible to perform the user's version upgrade operation easily and efficiently.

Next, in step S2, when the intermediate server 200 receives the upgrade request, the intermediate server 200 confirms the version of software installed in the terminal 300a and the terminal 300b designated as the upgrade target.
The version confirmation for the terminals 300a and 300b is performed by an existing method in which the intermediate server 200 refers to the version information set at the time of setup on the terminals 300a and 300b via the network. Alternatively, it is possible to use an existing method in which installation version information of each terminal is recorded on the intermediate server 200 and referred to each time version upgrade is performed.

In the case of the terminal 300 that is not connected to the network with the intermediate server 200, information on the previous version upgrade is held on the intermediate server 200 and referred to by the user input or the like on the intermediate server 200. It is conceivable to cope with such a method that the user manually inputs the version number currently installed on the server 200.
The version confirmation is performed by checking the version number (version 1 to version 4) as software defined by the configuration information 100a or the configuration information 200a from the terminal 300, or the version number (Comp1) of each configuration component corresponding to each version. , Comp2 version number), or both.
In the present embodiment, in step S2, the current version of terminal 300a is version 2 (Comp1: 8.1B, Comp2: 8.0A), and the current version of terminal 300a is version 3 (Comp1: 8.3C, Comp2: 8 .. 1B) is obtained.

Next, intermediate server 200 performs the following steps S3 to S6 following step S2.
In step S3, the configuration information 200a existing on the intermediate server 200 or the configuration information 100a existing on the distribution server 100 is confirmed to obtain the configuration information. As a result, the version upgrade pattern for each component when the software is upgraded from the current version to the specified version is determined, and necessary component and version information is obtained.
Here, the configuration information 200a on the intermediate server 200 holds the configuration information obtained from the distribution server at the time of upgrading each terminal so far, and this configuration information 200a and the distribution server at the present time are held. With the configuration information 100a, components and version information necessary for the current version upgrade are obtained.

Here, the terminal 300a is upgraded from software version 2 to version 4, and when viewed by component, Comp1 needs to be updated from 8.1B to 8.3D, and Comp2 needs to be updated from 8.0A to 8.1B. Make a judgment.
Further, the terminal 300b is a version upgrade from software version 3 to 4. When viewed by component, Comp1 is determined to be 8.2C → 8.3D, Comp2 remains 8.1B, and no update is necessary. .

In the present embodiment, since it is assumed that the update request is received at the same time in the terminal 300a and the terminal 300b, the necessary component version is collectively determined from both the old version and the new version. In the present embodiment, there are two necessary components, ie, component distribution images 200c, in which Comp1 is 8.3D and Comp2 is 8.1B.
Also, if this distribution image 200c is generated from the difference information 200b, the necessary difference information 200b is Comp1 with 8.1B → 8.3D and 8.2C → 8.3D, and Comp2 with 8.0A. → 8.1B is a total of three.

  Even when a plurality of terminals 300 require the same distribution program 100b and difference information 200b, the number of distribution programs 100b and difference information 200b required for the intermediate server need not be equal to the number of terminals. For example, if there is another terminal 300x in addition to the terminals 300a and 300b, and the three terminals 300x have the same upgrade pattern as the terminal 300a or the terminal 300b, the difference required by the intermediate server 200 Only one piece of information 100b and difference information 200b are required.

Next, in step S4, the intermediate server 200 confirms whether or not the distribution image 200c obtained by the configuration information confirmation in step S3 exists on the intermediate server 200.
If it does not exist, it is necessary to generate the distribution image 200c, and for this purpose, the difference information 200b is required. For this reason, first, in step S5, it is confirmed whether or not the desired difference information 200b exists on its own intermediate server 200. As a result, if it does not exist on the intermediate server, the difference information acquisition unit 203 acquires the desired difference information 100c from the distribution server 100 in step S6.

In this system, the intermediate server 200 creates a distribution image 200c of each component of a specific version corresponding to a desired software version for the terminal 300 to be upgraded, and distributes this to distribute the version of the terminal 300. Up.
The distribution image 200c is generated by the distribution image generation unit 203. For generation, the difference information 100c generated by binary difference extraction between the old version of the distribution program 100b and the desired version or the difference information 200b is generated. is required.
For this reason, first, it is checked in step S4 whether the distribution image 200c, which is a completed product, has already been generated on the intermediate server 200.
On the other hand, if it does not exist, it is checked in step S5 whether the difference information 200b exists on its own intermediate server 200. Only if it does not exist, the difference information 100c is acquired from the distribution server 100 in step S6.

In this way, the intermediate server 200 performs data generation / distribution relay processing for upgrading a plurality of subordinate terminals 300. Here, if the intermediate server 200 has generated and distributed the distribution image 200c that is the same as the version upgrade of the terminal 300 to be executed this time in another terminal 300 in the past, the intermediate server 200 or the distribution image 200c used in the past or this It has a function of storing difference information 200b for generating a distribution image 200c.
Accordingly, if the intermediate server 200 holds the distribution image 200c and the difference information 200b, the intermediate server 200 can reuse and generate the distribution image 200c. This can be said to be an advantage of introducing the intermediate server 200 in the case where a plurality of terminals 300 exist in the user base as described above.

As a result, the information (configuration information 100a, distribution program 100b, difference information 100c) necessary for upgrading the terminal 300 is not acquired from the distribution server 100 as in step S4 and step S5, but on the intermediate server 200. It is checked whether the distribution image 200c and the difference information 200b necessary for upgrading the terminal 300 are stored, and only when the distribution image 200c and the difference information 200b are not stored, the information necessary for upgrading the terminal 300 from the distribution server 100 as in step S6. I am going to do the acquisition.
As a result of step S4, if the necessary distribution image 200c among the necessary upgrade data exists on the intermediate server 200, the processing of step S5 and step S6 is skipped and the process proceeds to step S7. Alternatively, when there is no distribution image 200c on the intermediate server 200 but the difference information 200b exists, the process of step S6 is skipped and the process proceeds to step S7.

Next, details of steps S4 to S6 described above will be described according to the version upgrade example of the terminal in FIG.
By step S3, two components (component distribution image 200c) required in the version upgrade example of FIG. 7 are Comp1 with 8.3D and Comp2 with 8.1B. Further, when the distribution image 200c is generated from the difference information 200b, the necessary difference information 200b includes Comp1 of 8.1B → 8.3D (for the terminal 300a) and 8.2C → 8.3D (for the terminal 300b). ) And Comp2 is 8.0A → 8.1B (common to both terminal 300a and terminal 300b), which is three in total, as described above.

In the present embodiment, it is assumed that the intermediate server 200 has the following distribution image 200c by the distribution image holding unit 204 in accordance with the previous version upgrade history of the subordinate terminals 300a and 300b.
Comp1: 8.0A, 8.1B, 8.2C (3 types)
Comp2: 8.0A, 8.1B (2 types)
Further, the intermediate server 200 has the following as the difference information 200b for generating the distribution image 200c.
Comp1: 8.0A → 8.1B, 8.1B → 8.2C (2 types)
Comp2: 8.0A → 8.1B (3 types)

Regarding Comp1, first, in step S4, the presence / absence of the distribution image 200c is checked. Here, there are two necessary distribution images 200c, Comp1 8.3D and Comp2 8.1B, but the intermediate server 200 does not have Comp1 8.3D, and Comp2 8.1B exists. Obtain the judgment result.
Thereafter, the process proceeds to step S5, and the presence / absence of difference information 200b (8.2C → 8.3D) necessary for generating the 8.3D distribution image 200c that did not exist in step S4 is checked.
Since Comp2 has a desired distribution image 200c of 8.1B in step S4, step S5 and step S6 are skipped, and the process proceeds to step S7.

  In the present embodiment, the difference information 200b of Comp1 required in the simultaneous version upgrade case of the terminal 300a and the terminal 300b is described as two in the above-described manner, 8.1B → 8.3D and 8.2C → 8.3D. Nevertheless, in step S5, the type is 8.2C → 8.3D. This is because there is an 8.3D distribution image 200c generated from the 8.2C → 8.3D difference information 200b for the terminal 300b, which can also be used for the terminal 300a. This is because the information 200b (8.1B → 8.3D) becomes unnecessary.

Since the intermediate server 200 has already been upgraded from Comp1 to 8.1B → 8.2C, the intermediate server 200 holds the 8.2C distribution image 200c for the terminal 300b. Therefore, the difference information for upgrading from 8.2C of Comp1 for terminal 300b to 8.3D can be obtained from the distribution server, and based on this, the 8.3D distribution image 200c of Comp1 can be created. Since the 8.3D distribution image 200c of Comp1 necessary for the terminal 300a can use this, the difference information of 8.1B → 8.3D of Comp1 that is necessary for the terminal 300a becomes unnecessary.
Since Comp2 is already 8.1B at the terminal 300b, it is determined in step S4 that the desired 8.1B distribution image 200c exists on the intermediate server 200, and the processing from step S5 to step S7 is performed. Is unnecessary, and the existing 8.1B distribution image 200c may be reused and sent to the terminal 300a.

  In this way, the intermediate server 200 can efficiently acquire the difference information 100b necessary for upgrading the terminal from the distribution server 100 with a minimum access to the distribution server 100, thereby reducing the load on the network. Effects such as saving resources such as CPU / disk capacity and shortening execution time can be obtained.

Next, following the processing of steps S4 to S6, the intermediate server 200 performs the processing of step S7 by the distribution image generation means 203. In step S7, the distribution image generation means 203 generates a distribution image 200c required by the terminal 300 that needs to be upgraded.
Further, in step S8, the distribution package generation means 205 uses a combination of distribution images 200c (newly generated distribution images and existing distribution images) necessary for each update pattern, and further install scripts for starting up these installation processes. A distribution package 200d is generated.
Thereafter, in step S9, the distribution package transmitting means selects the distribution package 200d corresponding to the update pattern of each terminal and distributes it to the version upgrade target terminal 300.

  The distribution image generation unit 203 first generates the distribution image 200c by applying the difference information 200b on the intermediate server 200, and the distribution image generation unit 203 uses the difference information in the past to generate a distribution image. Difference information is newly applied to the distribution image 200c stored by the means 204, and a new distribution image 200c is generated.

Next, an overview of the distribution image generation process in step S7 and the distribution package generation process in step S8 will be described.
As described above, among the distribution images 200c required when upgrading the terminal 300a and the terminal 300b at the same time, 8.3D of Comp1 is not in the intermediate server 200, so it is newly generated, and 8.1B of Comp2 is intermediate. Since it was in the server 200, this is to be diverted.
First, the distribution image generation unit 203 newly generates an 8.3D distribution image 200c of Comp1 in the distribution image generation processing in step S7.

Subsequently, in step S8, the distribution package generation unit 205 performs the following process in the distribution package generation process.
(1) For each update pattern, an install script for installing the necessary distribution image 200c is generated.
(2) A distribution package 200d in which the installation script generated in (1) and a desired distribution image 200c are packaged is generated.
Here, it is necessary to generate the installation script according to the number of update patterns (combination of distribution images 200c to be installed).
In the version upgrade example of FIG. 7, since the update patterns are different between the terminal 300a and the terminal 300b, it is necessary to generate two types of distribution packages 200d for the two terminals.

Next, the distribution image generation process in step S7 and the distribution package generation process in step S8 will be described in more detail.
First, a process in which the distribution image generation unit 203 generates the 8.3D distribution image 200c of Comp1 in step S7 will be described.
In the 8.3D distribution image 200c of Comp1, the difference information 200b of 8.2C → 8.3D acquired from the distribution server 100 in step S6 is already stored on the intermediate server 200 as the distribution image 200c by the distribution image holding unit 204. It is generated by applying to the 8.2C program file.
The process of generating the new version (8.3D here) program file by applying the difference information 200b to the old version (8.2C here) distribution image 200c is performed by the difference application program prepared on the intermediate server 200. Shall be done.

Further, the difference application program is based on the existing method, and details are omitted here, but the following processing is performed. In other words, the difference application program checks the version information of Comp1 corresponding to the difference information and the old version, and if the version is matched, the additional file is added to the 8.2C program file of the old version Comp1 according to the contents of the update information file. Copy, update and analyze the difference information of the binary difference file with respect to the update file, delete the deleted file, and rewrite the new version 8.3D program file.
Further, the distribution image 200c that needs to be newly generated by using the difference information 100c has only one 8.3D of Comp1 in the case of the version upgrade example in FIG. The generation process of the distribution image 200c is continued.

Next, in the case of the version upgrade example shown in FIG. 7, the process in which the distribution package generation unit 205 generates the distribution package 200d in step S8 will be described.
FIG. 9 is a configuration diagram of the distribution package 200d.
First, generation of an installation script for a distribution package performed by the distribution package generation unit 205 in the distribution package generation processing in step S8 will be described.
The contents of the installation script are the same. Based on the old version (current version) and new version of each of Comp1 and Comp2 described above, version check processing before installation execution, and installation programs for Comp1 and Comp2 as necessary In the example of the update pattern in the version upgrade example shown in FIG. 7, the update pattern differs between the terminal 300a and the terminal 300b as described above. It is necessary to generate two types for each terminal.

Next, generation of the distribution package 200d performed by the distribution package generation unit 205 in step S8 will be described.
The update pattern of the terminal 300a is a case of software version 2 → version 4. For this reason, as shown in FIG. 9, as the update pattern distribution package 200d of the terminal 300a, an installation script and a distribution image 200c of Comp1 8.3D and Comp2 8.1B are generated.
In addition, since it is necessary to update the version information of the old version (current version) and the new version of Comp1 and Comp2, respectively, and to upgrade both Comp1 and Comp2, the installation script includes a process including starting each installer. Describe it.

The update pattern of the terminal 300b is a case of software version 3 → version 4. For this reason, as shown in FIG. 9, as the update pattern distribution package 200d of the terminal 300b, a combination of the installation script and the 8.3D distribution image 200c of Comp1 is generated.
In addition, since it is necessary to give version information of the old version (current version) and new version of Comp1 and Comp2 respectively and to upgrade only Comp1 in the install script, a process for starting the installer of Comp1 is described.
Further, the distribution package 200d may be distributed in a compression / self-decompression / self-execution format like a normal installer for distribution to the terminals 300a and 300b in order to reduce the size during distribution and improve operability. desirable.

Next, the distribution package distribution process in step S9 will be described.
In step S9, the distribution package transmission means 206 sends the distribution package 200d generated as described above to the terminals 300a and 300b via the network.
Each of the terminal 300a and the terminal 300b receives the distribution package, and the user executes this application to upgrade the software to version 4.

If the terminal 300c is in an offline state not connected to the intermediate server 200 via a network, the distribution package 200d generated in step S7 is copied to a storage medium such as a CD-ROM and distributed to the terminal 300c. But it ’s okay.
In the case of this method, in particular, in a case where the user base does not have or does not want to have the intermediate server 200 for reasons such as simplifying the operation or reducing the cost, a computer outside the base is used as the intermediate server 200 in the user base. It is also possible to generate and distribute version upgrade media according to the terminal 300.
In addition, according to such a system, for example, a version upgrade service performed as a part of a maintenance service by a software sales agent or the like can be efficiently performed.

Next, a more efficient processing method in steps S5 and S6 will be described.
Here, the case of the version upgrade example shown in FIG. 7 will be described as an example in which the terminal 300a and the terminal 300b issue a version upgrade request to the intermediate server 100 at different timings, not at the same time. Specifically, a case will be described in which an upgrade request for terminal 300b is made after an upgrade request for terminal 300a.

  First, in the terminal 300a, the required distribution image 200c is 8.3D for Comp1 and 8.1B for Comp2, and Comp2 is already in the terminal 300b as in the case of the simultaneous update of the terminal 300a and the terminal 300b described above. Since it is 8.1B, 8.1B already exists on the intermediate server 200, so it may be reused. That is, the process skips from step S4 to step S8.

Next, processing related to Comp1 will be described.
In step S4, among the necessary distribution images 200c, 8.3D of Comp1 does not exist on the intermediate server 200. For this reason, since it is necessary to generate a distribution image based on the difference information, the process proceeds to step S5.
In step S5, the necessary difference information 100c is changed from 8.1B of Comp1 to 8.3D. However, this difference is a difference between two versions. That is, 8.1B → 8.3D of Comp1 of the necessary difference information 100c is composed of two version upgrades of 8.1B → 8.2C and 8.2C → 8.3D.

  As described above, in the case where the difference information 100c that can be generated / distributed by the distribution server 100 is only for one version (one version upgrade), the necessary Comp1 is displayed on the distribution server 100. The difference information 100c of 8.1B → 8.3D does not exist. Therefore, the difference information acquisition unit 202 of the intermediate server 200 manages to generate the 8.3D distribution image 200c of the desired Comp1 on the intermediate server 200 without the 8.1B → 8.3D difference information 100c. In addition, as a method of avoiding access to the distribution server 100 as much as possible, the existing difference information 200b on the intermediate server 200 is used to check whether a desired version of the distribution image 200c can be generated.

In this example, first, the latest version of Comp1 held by the distribution image holding unit 204 is checked on the intermediate server 200, and it is confirmed that there is an 8.2C distribution image 200c used for upgrading the terminal 300b. To do.
Since the 8.2C of the distribution image 200c is only one different from the 8.3D version required by the terminal 300a, the difference information of 8.2C → 8.3D is obtained, and the 8.3D from the difference information is obtained. Consider generating a distribution image 200c.
Therefore, first, it is confirmed whether or not the difference information 200b exists on the intermediate server 200. However, since there is no record of generating the 8.3D distribution image 200c, it naturally does not exist, and the process proceeds to step S6.

In step S6, the difference information 100c of 8.2C → 8.3D is acquired from the distribution server 100.
Subsequently, in step S7, the distribution image generation unit 203 applies the 8.2C → 8.3D difference information 200b acquired above to the already existing 8.2C distribution image 200c, and is required by the terminal 300a. An 8.3D distribution image 200c is generated. Thereafter, the distribution image holding unit 204 stores an 8.3D distribution image 200c on the intermediate server 200.
As described above, 8.3D of Comp1 and 8.1B of Comp2 of the distribution image 200c necessary for the terminal 300a can be prepared on the intermediate server 200. In step S8, the distribution package generation unit 205 stores the Comp1 of the distribution image 200c. The distribution package 200d is generated using 8.1B of 8.3D and Comp2. Thereafter, in step S9, the distribution package transmission unit 206 transmits the distribution package 200d generated by the distribution package generation unit 205 to the terminal 300a.

Next, in the version upgrade of the terminal 300b performed following the processing of the terminal 300a described above, the required distribution image 200c is 8.3D1 of Comp1, but this is for the upgrade of the previous terminal 300a. Since it has been generated, it is sufficient to generate the distribution package 200d in step S8 by reusing it.
As shown in this example, only the difference information 100b between one version needs to be generated on the distribution server 100, and the distribution server 100 stores the difference information 100c of every update pattern twice or more in advance or dynamically. There is no need to generate and distribute.

  This is because the distribution image generation unit 203 and the distribution image holding unit 204 of the intermediate server 200 and the existing distribution image 200c generated by upgrading the other terminal 300 under the control of the intermediate server 200 and the existing image acquired from the distribution server 100 are used. Since the desired distribution image 200c can be generated from the difference information 100b for one version, such an operation can be performed.

  As described above, according to the present embodiment, the intermediate server 200 acquires the difference information 100b necessary for the software upgrade of the terminal 300 from the distribution server 100, and the distribution image 200c for the software upgrade of the terminal 300 is obtained. By distributing to the terminal 300, the intermediate server 200 can efficiently perform information for updating the software installed in the terminal 300 with minimum access to the distribution server 100 and the terminal 300 and a minimum amount of information. Therefore, effects such as reduction of network load, resource saving such as CPU / disk capacity, and reduction of execution time can be obtained. Accordingly, the software upgrade of the terminal 300 can be performed in a short time, and the terminal software can be efficiently upgraded.

Embodiment 2. FIG.
In the first embodiment, as a method for upgrading the terminal 300, a method for generating and distributing a new distribution image 200c necessary for the terminal 300 on the intermediate server 200 has been described. Instead of the image 200c, the intermediate server 200 distributes the difference information 200b for upgrading to a new version to each terminal 300, so that the software installed on each terminal 300 can be upgraded. Hereinafter, in this embodiment, a method based on the distribution of the difference information 200b will be described.
Here, the configuration of the software secondary distribution system of the present embodiment is almost the same as that of the first embodiment, but the intermediate server 200 of the present embodiment stores the distribution difference information distributed to the terminal 300. Difference information generating means 207 (see FIG. 6) for generating is added.
In order to distinguish from the method of the first embodiment, the method of the first embodiment is a distribution image method, and the method of the present embodiment is a differential method.

The difference method of the present embodiment is suitable for a case where a large number of terminals 300 are connected to the intermediate server 200 via a network, but the bandwidth is narrow and the number of terminals 300 is large.
If you do not want to apply a network load due to network restrictions, there is a method of preparing offline distribution media and manually performing version upgrade work one by one on the terminal 300, but it is necessary to perform the work one by one. There is a problem that it takes time and effort for this. In such a case, if the version upgrade method based on differential distribution according to the present embodiment is used, an effect is obtained that it is possible to efficiently distribute version upgrade data online without imposing a load on the network.

Hereinafter, details of the difference method will be described.
FIG. 10 is a flowchart showing the processing procedure of the intermediate server 200 in the present embodiment. A version upgrade processing procedure performed by the intermediate server 200 will be described with reference to FIG.
Since the processing operation before step S10 is the same as that in FIG. 8 of the first embodiment, the description thereof is omitted here.
First, in step S10, it is confirmed whether or not the difference information 200b necessary for generating the distribution image 200c in the distribution image method already exists on the intermediate server 200. If it exists, it can be reused, and the process proceeds to step S16.

On the other hand, if the difference information 200b does not exist, it is checked whether or not the difference information 100c corresponding to the difference information 200b exists on the distribution server 100. If the difference information 100c exists on the distribution server 100, the distribution server The difference information 100c is acquired from 100, and the process proceeds to step S16 (not shown). If the difference information 100c does not exist in the distribution server 100, the process proceeds to step S11.
In step S11, it is confirmed whether or not there is a new version of the distribution image 200c to be upgraded on the intermediate server 200. When it exists, it progresses to step S15. On the other hand, if it does not exist, the process proceeds to step S12 because it is necessary to generate a new distribution image 200c.

In step S12, it is confirmed whether or not the difference information 200b necessary for generating the new distribution image 200c exists on the intermediate server 200. If it exists, it can be used, and the process proceeds to step S14. On the other hand, if it does not exist, it is necessary to obtain the difference information 100c from the distribution server 100, so the process proceeds to S13.
In step S13, the difference information 100c necessary for generating the new distribution image 200c is acquired from the distribution server 100.

Next, in step S14, the distribution image generation means 203 generates a new version of the distribution image 200c. Here, the new distribution image 200c is generated by using the difference information 200b that has already been confirmed to exist on the intermediate server 200 in step S12 or the difference information 200b newly acquired in step S13 on the intermediate server 200. Are applied to the old version of the distribution image 200c.
Note that the difference application method performed here is the same as the method by the distribution image generation unit 203 described in the first embodiment.

In step S <b> 15, the difference information generation unit 207 generates distribution difference information 200 b ′ distributed to the terminal 300. The distribution difference information 200b 'is generated by extracting the binary difference between the two versions since the distribution images 200c of the new version and the old version are prepared at this point.
Note that the distribution difference information 200b ′ generated in step S15 is retained on the intermediate server 200 and can be reused, like the distribution image 200c.

In step S16, the distribution package generation means 205 generates a distribution package 200d ′ for the terminal 300 for each update pattern. Although details of the configuration will be described later, there are two differences in configuration between the distribution package 200d and the distribution package 200d ′.
The first point is that the distribution package 200d sent the distribution image 200c of the necessary component, but the distribution package 200d ′ is a difference information distribution package obtained by replacing the distribution image 200c with the distribution difference information 200b ′. As a result, the latter can achieve the effect of greatly reducing the size of information transmitted to the terminal 300 compared to the former.
The second point is that a processing procedure for generating a new distribution image 200c by applying the packaged distribution difference information 200b ′ to the old distribution image 200c on the terminal 300 is added to the installation script. It is a content.
As the distribution package 200d ′ generated in step S16, a package that matches the update pattern of the target terminal is selected and sent to the terminal 300, like the distribution package 200d.

Next, the configuration of a distribution when distributing difference information to a terminal will be described.
FIG. 11 is a configuration diagram of the distribution package 200d ′ generated in step S16 by the distribution package generation unit 205.
First, the distribution package 200d ′ for the differential method is generated according to the following procedure.
(A) For each update pattern, an install script for updating the software with the necessary difference information 200b ′ is generated.
(B) A distribution package 200d ′ in which the difference information 200b for necessary difference update and the installation script generated in (A) is packaged is generated.
Note that the installation script (A) needs to be generated according to the number of update patterns (combinations of distribution images 200c to be installed) as described in step S8 of the first embodiment.
In the case of the version upgrade example in FIG. 7, since the update patterns differ between the terminal 300a and the terminal 300b, the distribution package 200d ′ needs to be generated for each of the two terminals.

In generating the distribution package 200d ′, the contents of the installation script generated in (A) above are obtained by adding the following processing to the installation script generated in step S8 of the first embodiment.
That is, before installing the new version of the distribution image 200c, a difference application process for generating the new version of the distribution image 200c from the old version distribution image 200c on the terminal and the difference information 200b ′ in the distribution package 200d ′ by difference application is performed. It is described in addition.
Note that the difference application process is performed by preparing a difference application program (not shown). The method of providing the difference application program is performed by attaching to the distribution package 200d ′ or by distributing and preparing the program on each terminal 300 in advance.

Next, the method of Case 1 for distributing difference information to terminals will be described with reference to the flowchart of FIG. 10 by taking the version upgrade example of FIG. 7 as an example.
Specifically, the operation when two terminals, the terminal 300a and the terminal 300b, issue a version upgrade request to the intermediate server 200 will be described.
In this case, the difference information 200b ′ required for the two units is as follows.
(X) 8.1B of Comp1 → 8.3D (for terminal 300a)
(Y) Comp1 8.2C → 8.3D (for terminal 300b)
(Z) Comp2 8.0A → 8.1B (for terminal 300a)
Next, a procedure for preparing the necessary difference information 200b for the above (X) to (Z) will be described.
A case where the operations of Steps S10 to S15 are executed in the order of the above (X) to (Z) will be described.

First, in the case of (X) to be executed first, since the 8.3D version upgrade of Comp1 has never been performed on the subordinate terminal 300, the difference information 200b does not exist on the intermediate server 200.
In step S10, the difference information acquisition unit 202 determines that the distribution difference information 200b of (Z) does not exist.
In step S11, the difference information acquisition unit 202 confirms whether or not there is a new 8.3D distribution image 200c for creating (Z), and determines that it does not exist here.
In step S12, the difference information acquisition unit 202 determines the difference information 8.2C → 8.3D difference information 200b necessary to create the new version 8.3D distribution image 200c determined not to exist in step S11. Is present on the intermediate server 200. Here, since there is no track record of generating a new version 8.3D distribution image 200c in the past, it is determined that it does not exist.

Next, in step S <b> 13, the difference information acquisition unit 202 acquires 8.2C → 8.3D difference information 100 c from the distribution server 100.
In step S14, the distribution image generation means 203 generates a new version 8.3D distribution image 200c ′. The new version 8.3D distribution image 200c ′ is generated by applying the difference information acquired in step S13 to the existing old version 8.2C distribution image 200c.
In step S15, the difference information generating means 206 generates (Z) distribution difference information 200b ′ from the new distribution image 200c ′ created in step S14 and the existing old distribution image 200c.

Next, in the case of the second execution (Y), the difference information 100c of 8.2C → 8.3D acquired from the distribution server 100 in step S13 of (X) is reused.
In the case of the third execution (Z), since the update of 8.0A → 8.1B has already been executed in the terminal 300b in the past, the difference information 200b remains on the intermediate server 200. This shall be reused.

  As a result, in the generation of the distribution package 200d ′ in step S16, the difference information 200b ′ packaged for the terminal 300a is newly generated locally on the intermediate server as described above for Comp1, for Comp2. You can choose an existing one. Moreover, what is necessary is just to select as reusing what was acquired from the distribution server 100 by said step S133 for the terminal 300b.

Next, a case 2 method for distributing difference information to terminals different from the method described in case 1 will be described.
Specifically, for example, an operation when two terminals, the terminal 300a and the terminal 300b, issue an upgrade request to the intermediate server 200 in this order at different timings will be described.
First, it is assumed that the difference information 200b necessary for the terminal 300a is (X) and (Z) in Case 1, which is a case where the two terminals issue a version upgrade request at the same time.
Also, as in case 1 above, (Z) is already on the intermediate server and can be reused.
Further, as in case 1 above, (X) is not on the intermediate server 200 or on the distribution server 100.

As a result, a new version 8.3D distribution image 200c ′ is generated in the same procedure of step S10 to step S14 as in case 1 above, and the above two terminals issue version upgrade requests at the same time. Similarly, a distribution package 200d ′ for the terminal 300a may be generated.
Also, since the difference information 200b necessary for the terminal 300b is (Y) in the above case 1, it exists on the intermediate server 20 as described above, so that it may be reused.
Further, the distribution package 200d ′ may be generated in the same manner as in the case 1 described above.

Next, a case 3 method for distributing difference information to terminals different from the methods described in case 1 and case 2 will be described.
For example, an operation when the terminals 300b and 300a issue a version upgrade request to the intermediate server 200 at different timings in this order will be described.
First, the difference information 200b necessary for the previous terminal 300b is (Y) as described in the cases 1 and 2 above.
However, since there is no track record of upgrading 8.3D of Comp1, it does not exist on the intermediate server 200. Also, there is no difference information 200b of 8.2C → 8.3D for upgrading to 8.3D of Comp1.
This difference is obtained from the distribution server 100 because it is a difference for one version upgrade.
As a result, the necessary distribution difference information 200b is prepared, and a distribution package 200d ′ in which this is packaged may be generated.

Next, for the terminal 300a, the necessary difference information 200b is (X) and (Z) as described in cases 1 and 2 above.
Since (Z) is already on the intermediate server 200 as in the cases 1 and 2, it can be reused.
Further, (X) is neither on the intermediate server 200 nor on the distribution server 100. For this reason, what is necessary is just to produce | generate by the procedure of step S10-step S14 similarly to the case where said 2 units | sets are the same. However, the difference information 100b of 8.2C → 8.3D acquired in step S13 is only acquired on the intermediate server for the previous terminal 300b, so that the process skips from step S12 to step S14.
As described above, the distribution package 200d ′ for the terminal 300a may be generated by packaging (X) and (Z) as in the previous simultaneous case.

In the present invention, the distribution image distribution method described in the first embodiment and the difference distribution method described in the second embodiment may be used in combination. By doing so, it is possible to operate the distribution image 200c already generated on the intermediate server 200 or the difference information 200b and the difference information 200b ′ as much as possible, reducing the load on the intermediate server 200, and distributing the server 100. You can expect the effect of reducing communication with.
For example, even if there is no distribution image 200c required for version upgrade, if there is difference information 200b for generating the distribution image 200c, it is possible to generate and distribute a difference distribution package 200d ′.

    As described above, according to the present embodiment, the intermediate server 200 distributes the difference information necessary for upgrading the software version of the terminal 300 to the terminal 300, so that the intermediate server 200 can upgrade the version of the terminal 300. Since the information distributed to the terminal 300 can be efficiently performed with the minimum access and the minimum amount of information, it is possible to obtain the effects of reducing the load on the network, saving resources such as CPU / disk capacity, and shortening the execution time. . Accordingly, the software upgrade of the terminal 300 can be performed in a short time, and the terminal software can be efficiently upgraded.

1 is a configuration diagram of a software secondary distribution system according to Embodiment 1. FIG. FIG. 3 is an explanatory diagram of the configuration and update status of software to be distributed in the first embodiment. 1 is a configuration diagram of a distribution server 100 according to Embodiment 1. FIG. Explanatory drawing of the distribution program 100b in Embodiment 1. FIG. Explanatory drawing of the difference information 100c in Embodiment 1. FIG. FIG. 2 is a configuration diagram of an intermediate server 200 in the first embodiment. Explanatory drawing about the version upgrade example of the terminal in Embodiment 1. FIG. 3 is a flowchart showing a processing procedure of the intermediate server 200 in the first embodiment. The block diagram of the distribution package 200d in Embodiment 1. FIG. 9 is a flowchart illustrating a processing procedure of the intermediate server 200 according to the second embodiment. The block diagram of distribution package 200d 'produced | generated by the distribution package production | generation means 205 in Embodiment 2. FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Distribution server 101 Configuration information management means 102 Difference information generation means 200 Intermediate server 201 Version confirmation means 202 Difference information acquisition means 203 Distribution image generation means 204 Distribution image holding means 205 Distribution package generation means 206 Distribution package transmission means, 207 difference information generation means, 300 terminal.

Claims (8)

A distribution server that stores the difference information between the old and new software that updates the software;
A terminal that transmits an update request for the installed software to the intermediate server, and updates the distribution package received from the intermediate server by applying to the installed software ;
Update information holding means for the used in the past software updates were the update information and the difference information held by the past updating information and past difference information,
Among the difference information stored in the distribution server when the update request is transmitted by the terminal and the past update information corresponding to the update request and the past difference information do not exist in the update information holding unit. Difference information acquisition means for acquiring difference information corresponding to the update request from,
Update information generation means for generating the update information corresponding to the update request based on the difference information acquired by the difference information acquisition means and the past update information ;
Distribution package generation means for generating a distribution package in which the update information generated by the update information generation means and a procedure for installing the update information in the terminal are packaged;
It said intermediate server and a distribution package transmission means for transmitting a distribution package generated by the distribution package generating means to said terminal,
A software update information distribution system comprising:   The distribution server includes configuration information management means for managing configuration information in which a correspondence relationship between a plurality of components constituting software and software versions is defined, and difference information generation for generating the difference information based on the configuration information The software update information distribution system according to claim 1, further comprising: means. The configuration information management means registers a distribution program indicating the actual state of software programs in the distribution server,
The distribution server transmits the configuration information to the intermediate server when the distribution program is registered by the configuration information management means,
The said intermediate | middle server confirms the component and software version which are updated based on the said configuration information transmitted by the said distribution server, when the said update request | requirement is transmitted from the said terminal. Software update information distribution system.   The update information generation means, when the update request is transmitted by the terminal, when the past update information corresponding to the update request exists in the update information holding means, 2. The software update information distribution system according to claim 1, wherein the corresponding update information is generated. The update information generation means includes the past difference information and the past update information when the past difference information corresponding to the update request exists in the update information holding means when the update request is transmitted by the terminal. 2. The software update information distribution system according to claim 1, wherein the update information corresponding to the update request is generated based on the update request.   2. The software update information distribution system according to claim 1, wherein the intermediate server copies the distribution package generated by the distribution package generation means to a storage medium for use by the terminal. The intermediate server includes difference information generation means for generating distribution difference information to be transmitted to the terminal based on the update information generated by the update information generation means,
The distribution package generation unit generates a difference information distribution package in which the difference information for distribution generated by the difference information generation unit and a procedure for applying the distribution difference information to software installed on the terminal are packaged. And
2. The software update information distribution system according to claim 1, wherein the distribution package transmission unit transmits the difference information distribution package generated by the distribution package generation unit to the terminal. The intermediate server runs,
Update information holding step of holding the past software updates and difference information used to update the historical update information and past difference information,
When the update request of the software installed in this terminal is transmitted by the terminal, the difference information of the old and new software that updates the software is stored when the past update information corresponding to the update request and the past difference information do not exist. A difference information acquisition step of acquiring difference information corresponding to the update request from the distribution server;
An update information generation step for generating the update information corresponding to the update request based on the difference information acquired by the difference information acquisition step and the past update information ;
A distribution package generation step of generating a distribution package in which the update information generated by the update information generation step and a procedure for installing the update information in the terminal are packaged;
A distribution package transmission step of transmitting the distribution package generated by the distribution package generation step to the terminal;
A software update information distribution method characterized by comprising:

Images