JP2003256212A - Method for managing software - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To establish a technology for updating software by various patterns. <P>SOLUTION: A software updating system shown in Figure 1 updates software stored in a storing part 340 of a personal computer 100. Update data to be used for update are stored in an update data server 200, and the personal computer 100 acquires the update data by transmitting request data. The update data selected according to the request data by the selecting part 430 are transmitted by the update data server 200 so that it is possible to reduce any load related with the preparation and management of the update data, and to realize various software update corresponding to the combination of the update data. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to a technique for updating software.

[0002]

2. Description of the Related Art In an environment in which a plurality of clients share a printer via a network, printer management software is used. For example, such software needs to be appropriately updated in order to expand the function corresponding to the printer of the new product and to correct the defect.

Software is updated by newly installing files that are added or changed. Updates may be taken that replace the entire old version of the software with the new version of the software,
By providing only the difference file corresponding to the difference between the old version and the new version as a package, the file size required at the time of updating can be reduced. When the update data has a large size, a technique for updating using the difference data is used. For example, when the software before update is composed of two files “a, b” and the software after update is “a, β”, the difference data is composed of the element “β” and the designation of the update target “b”. To do. Since the overlapping part between the software before and after the update is unnecessary, the data can be small in size due to the difference.

[0004]

In the usual case, the software update is not completed once but is often repeated many times. Here, not all users always update the software to the latest version. Therefore, it is necessary to prepare many types of update difference file packages according to the version that the user may have.

For example, consider a case where the software version is updated in two stages of 1.0 → 1.01 → 1.02. There are three types of required update packages: version 1.0 → 1.01, version 1.0 → 1.02, and version 1.01 → 1.02. The number of required update packages explodes when used for more stages. Conventionally, the burden of creating and managing such a wide variety of packages has been extremely heavy.

The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to reduce the burden of creating and managing a wide variety of packages regarding software update.

[0007]

Means for Solving the Problems and Their Actions / Effects In order to solve at least a part of the above problems, the present invention adopts the following configuration.

A management device of the present invention is a software management device, and is a storage unit for storing a set of files constituting the software, and update data input for inputting a set of update data for updating the software. Unit and an updating unit for updating the software based on the update data, the update data being prepared and updated for each new file divided into a plurality of groups according to the update content. An update instruction file for specifying the new file to be updated is provided, and the update unit refers to the plurality of update instruction files to perform the update.

In this way, with respect to software update, various packages are constructed and used based on a combination of a plurality of update data, and the complexity of processing such as data creation, delivery, management, etc. It can be reduced.

The new file may be a plurality of separated files or may be integrally configured. Further, the update instruction file may be configured integrally with all or part of the new file.

Here, the input of the update data performed by the update data input unit may be performed via the Internet, a wireless communication network, or another network, or CD (C
Ompact Disk) and DVD (Digital)
It may be performed by using an information storage medium such as a memory card using a Video Disk) or a Flash Memory.

The management apparatus of the present invention may be provided with an update history storage section for storing a previous update history, and the update section may select the update instruction file to be referred to based on the update history.

By doing so, it is possible to avoid repetitively performing the update previously performed again in vain. As a result, it is possible to reduce complicated processing such as delivery of update data.

It is also possible to cancel the previous update and return the software to the state before the update based on the update history.

In the management apparatus of the present invention, the order of updating may be set between the update instruction files, and the updating unit may refer to the update instruction files in accordance with the order.

There are two ways to update software: one is to add many kinds of functions in parallel, and the other is to improve the functions stepwise. According to the above aspect, in the latter case, appropriate updating can be realized.

The management apparatus of the present invention is connected to a server for supplying the update data via a network, and includes a request unit for requesting the server to send the update data, The data input unit may perform the input from the server.

By doing so, it is possible to easily supply / acquire new update data.

Note that the request unit may continue to issue a request periodically, or may issue a request on a one-off basis in accordance with a user's instruction or other conditions.

Here, the network includes both wide area networks such as the Internet and limited networks such as local area networks and intranets. The network is wireless LA
It may be a network using N or mobile wireless telephone communication technology.

In the management apparatus of the present invention, the request section may transmit information for selecting update data used for the update to the server based on the software to be updated.

By doing so, the server can use the update data based on the information of the software to be updated. It is possible to avoid re-uselessly repeating the update performed previously, and it is possible to reduce the amount of update data transmitted. For example, the management device may select necessary update data, send information specifying the same to the server, and based on this, the server may select and send the necessary update data.

The update data supply server of the present invention is
An update data supply server which is connected to a client via a network and supplies update data for updating software stored in the client, wherein the update data is a new file divided into a plurality of groups according to the update content. And an update instruction file that is provided for each group and that specifies the new file to be updated, and a storage unit that stores a plurality of the update data in association with each other, and request data that requests the update data. An acquisition unit that acquires the update data from the client, a selection unit that analyzes the request and selects a plurality of the update data based on the association, and an output unit that outputs the selected update data. Is the gist.

By doing so, the update data selected based on the request of the client can be sent, and the data amount can be reduced.

In the update data supply server of the present invention,
For example, it is assumed that the request data includes information about the software to be updated, and the selection unit determines what is excluded from the selection by comparing the information with information related to the update data. Good.

By doing so, it is possible to avoid wasteful renewal of the previously performed renewal. As a result, it is possible to reduce complicated processing such as delivery of update data.

In the update data supply server of the present invention,
The storage unit stores multiple update data including the contents of the plurality of update data, and the sending unit stores the plurality of update data when the corresponding multiple update data does not exist, The multiple update data may be output.

By doing so, it becomes possible to simply instruct an update realized by a plurality of update data with a single data. For example, the update instruction file may form multiple update data by specifying a plurality of update data.

The present invention can be configured as a software management device and an update data supply server, as well as a software management method using a computer and a update data supply method using a computer. . Further, it can be configured in various modes such as a computer program for causing a computer to manage software and a computer program for causing a computer to supply update data. Furthermore, it may be configured as a computer program for causing a computer to perform software management or a signal that can be regarded as a signal similar to the computer program for causing the computer to supply update data, or a recording medium recording these computer programs May be configured as.

Here, as the storage medium, a flexible disk, a CD-ROM, a magneto-optical disk, an IC card,
Various computer-readable media such as ROM cartridges, punched cards, printed materials on which codes such as bar codes are printed, internal storage devices (memory such as RAM and ROM) of computers, and external storage devices can be used.

[0031]

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in the following order based on Examples. A. First Example: A1. System configuration: A2. Processing: A3. Modification: B. Second embodiment:

A. First embodiment: A1. System Configuration: FIG. 1 is an explanatory diagram showing the overall configuration of the software updating system. The software update system includes a personal computer 100 and an update data server 200. The network INT is a network that connects the personal computer 100 and the update data server 200. The personal computer 100 corresponds to the software management device of the present invention. The update data server 200 corresponds to the update data supply server in the present invention.

The update data server 200 is a server that supplies update data for upgrading the software installed in the personal computer 100. The personal computer 100 sends the request data to the update data server 200. The update data server selects and returns the update data based on the request data acquired. This enables the personal computer 100
Can update the software it holds.

The personal computer 100 sends request data to the update data server 200 to update the software held by the personal computer 100. The software can be updated by acquiring the update data from the update data server 200 by sending the request data.

FIG. 1 also shows the functional block configurations of the personal computer 100 and the update data server 200. The personal computer 100 and the update data server 200 each include a control unit configured as a microcomputer including a CPU, a memory, and the like. The illustrated functional blocks are configured as software as the functions of the respective control units. However, each functional block may be configured by hardware.

First, the functional blocks of the update data server 200 will be described. The acquisition unit 410 acquires request data for software update from the personal computer 100. The storage unit 420 stores update data. Here, the data are stored in association with each other according to the version stage of the software to be updated (details of this aspect will be described later). Selector 430
Selects the update data by analyzing the request data. At this time, the analysis is performed by referring to the association in the storage. The output unit 440 sends the selected update data to the personal computer 100.

Next, the functional blocks of the personal computer 100 will be described. The storage unit 340 holds software to be updated (details of this software will be described later). The history storage unit 330 is
Store the history of updates. The request unit 350 uses the history storage unit 3
The update history stored in 30 is referenced, and the request data is sent to the update data server 200. The update data input unit 310 acquires and inputs update data from the update data server 200 via the Internet INT. The update unit 320 updates the software stored in the storage unit 340 based on the update data input by the update data input unit 310, and stores the update content in the history storage unit 330.

In this embodiment, a method for updating software will be described by taking as an example a case where management software for managing various devices connected to the LAN is installed in the storage unit 340.

FIG. 2 is an explanatory diagram showing the function of the management software. Personal computer 100
The storage unit 340 stores a set of files constituting the management software. FIG. 2 shows a schematic configuration of a device management system mainly composed of management software. The function of the management software will be described below with reference to FIG.

The management software of the embodiment is
Personal computer 100 for network LAN
Also, it is used in an environment where various devices and clients are connected. The network LAN is an external Internet IN via the personal computer 100.
Connect with T. In FIG. 2, the printer PR is used as a device.
A computer P using T1 to PRT4 as clients
C1 to PC3 are shown as examples. However, it may have a larger number of devices and clients.

Each of the clients PC1 to PC3 can print using the printers PRT1 to PRT4 by specifying the output destination and inputting the print job to the network LAN. In order to print, it is necessary to install a printer driver compatible with the printers PRT1 to PRT4 in the client. The printer driver is stored in the personal computer 100. The users of the clients PC1 to PC3 can use the personal computer 1 when a printer driver is required.
00 can be accessed to install the printer driver.

The management software stores a set of printer drivers required on the network LAN and supplies the printer drivers in response to requests from the clients PC1 to PC3. The printer driver is provided by the manufacturer of the printers PRT1 to PRT4, but it often undergoes complicated and complicated version upgrades.
The updated printer driver is supplied by the printer driver data server (not shown) via the Internet INT. The management software accesses the printer driver data server and acquires / holds the printer driver.

The management software also has a function of managing the printers PRT1 to PRT4. Management software is printer PR
The status information of T1 to PRT4 is acquired and used for management. The status information includes the execution status of the ongoing print job, the status of consumables such as printing paper and ink, the status of the power supply, and the like. The management software stores such information in a user operating the personal computer 100 or the clients PC1 to PC3.
Can be provided to the user who operates.

Further, the user operating the personal computer 100 can change the operation settings and network settings of the printers PRT1 to PRT4 and rewrite the installed software by using the management software.

The management software is updated according to the release of a new model printer in order to expand the function of the manageable printer. In addition, updates will be made to add, change, or delete management functions.

FIG. 3 is an explanatory diagram showing the structure of the update data. The update data is used to update the management software.

The update data includes an instruction file. The instruction file specifies the update content while specifying another file in the update data. The personal computer 100 is
The management software can be updated by referring to the instruction file.

The update processing is performed while the update software provided in the personal computer 100 reads the content of the update data. The update software may be included in the update data and supplied by the update data server 200.

In FIG. 3, the structure of the update data is shown by arranging the file name, the directory name and the like. In the figure, the file “MK — 1010C.ini” is an instruction file. As shown in the figure, the instruction file indicates the update content by specifying the image data and the like included in the update data. In the example of FIG. 3, the file “LQ — 9820.etf” is used.
And "mk1010c.gif,""mk1010c.gif."
The update contents are instructed while specifying "dll".
Here, the file “LQ — 9820.etf” is a template file indicating the option installation state of the printer, and the file “mk1010c.gif” is a file of the external image of the printer.

In the embodiment, the case where the plurality of files in the update data are configured as a plurality of separated files with a directory structure is illustrated. These files may be separated for each file or may be integrally configured.

FIG. 4 is an explanatory diagram showing the structure of data stored in the storage unit 420. The storage unit 420 includes an update data storage unit 422 and a related information storage unit 424.

The update data storage section 422 stores a plurality of update data shown in FIG. Each update data is prepared for each version upgrade of the management software.

The related information storage section 424 stores related information for associating the update data with each other. In particular,
The relationship between the update pattern that is a set of version numbers before and after the update and the update data that realizes the update pattern is stored. In the figure, the update pattern "Version 1.30 →
1.31 ”is associated with the update data 5 and 6, and the association between the update pattern“ version 1.31 → 1.32 ”and the update data 7 and 8 is stored.

The personal computer 100 can use the update pattern “version 1.30 → 1.31” by using the update data 5 and 6. The same applies when the update pattern “version 1.31 → 1.32” is used.

Update pattern "version 1.30 → 1.3
2 ”, the update patterns“ version 1.30 → 1.31 ”and“ version 1.31 → 1.
32 ”is required for the updated data. At this time, the update data must be used based on the order of version upgrades. Specifically, it is applied in the order of 5, 6 → 7, 8. The application order of the update data 5, 6 and the update data 7, 8 is not limited.

A2. Update process: FIG. 5 is a flowchart showing the software update process. Here, the update data output process performed by the update data server 200 and the software update process performed by the personal computer 100 are shown together.

In the personal computer 100,
In step S101, the request unit 350 causes the history storage unit 3
By referring to the content stored in 30, the version information of the management software currently stored in the storage unit 340 is acquired. In step S102, the request unit 350
Sends the request data including the version information to the update data server 200.

In the update data server 200, the acquisition unit 410 acquires the request data in step S002.
This is performed in synchronization with the process of step S102 in the personal computer 100. Step S00
In 3, the selection unit 430 prepares update data to be returned. Here, the selection unit 430 reads the update data from the update data storage unit 422 while comparing the acquired request data with the content of the related information storage unit 424. Step S00
At 4, the prepared update data is sent to the personal computer 100.

Here, the update data to be sent is the update data necessary for updating the management software in the personal computer 100 to the latest version. Based on the current version information, the update pattern of version upgrades up to the latest version is specified, and the corresponding update data is retrieved from the update data storage unit 422.

In the personal computer 100,
In step S104, the update data input unit 310 acquires update data. This is the update data server 200
The processing is performed in synchronization with the processing of step S004. The acquired update data is sequentially installed in update data units based on the loop processing in steps S105 to S107. In the loop process including steps S105 to S107, update data is installed according to the order of version upgrade. For example, in the case of the update pattern “version 1.30 → 1.32” shown in FIG.
The update data 5 and 6 are installed before the update data 7 and 8.

In step S105, the update section 320 performs update data installation processing. The storage unit 340 is accessed to perform processing such as rewriting of management software and additional storage. In step S106,
The contents of the installation process are stored in the history storage unit 330. For example, it stores information about file deletion and addition / replacement. In step S107, it is checked whether the installation of the acquired update data has been completed. If all the updates are completed, the software update process ends, but if there is any update data left, the loop process continues.

According to the software update system of the present embodiment, it is possible to reduce the burden of creating and managing various packages when updating software. A wide variety of update patterns can be realized using a package based on a combination of a plurality of update data.

Here, since the process of selecting the update data used for the update is collectively performed on the server side, the load on the client side can be reduced.

The storage section 420 may store inclusive update data containing the contents of a plurality of update data. For example, the update data including the update data 5, 6, 7, and 8 shown in FIG. 4 may be independently held to realize the update pattern “version 1.31 → 1.32”.

A3. Modified Example: FIG. 6 is an explanatory diagram showing a modified example relating to selection of update data. In the embodiment, the request data includes version information, and the update data is selected by comparing the version information with related information. In this modified example, the request data includes categories 1 and 2.
The more flexible request content is indicated by including the information of the two categories.

FIG. 6 shows an example of data stored in the related information storage section 424a in this modification. The request data includes information of two categories, categories 1 and 2. Category 1
Then, specify the upgrade sequence. As shown in the figure, in addition to the management software series, PM
A series of printer series can be specified.

When the management software series is designated in category 1, the same processing as that of the embodiment is performed based on the version information designated in category 2.

When the PM printer series series is designated in category 1, the PM printer series can be installed. By designating the version information of PM200, PM220, PM240, etc. of the PM printer series in category 2, it is possible to install the update data related to the subsequent model.

By using the update data server which uses the data structure shown in FIG. 6, it is possible to meet various requests for update data. At this time, by using the update data in combination to meet various requests,
It is possible to reduce the burden of creating / managing update data.

FIG. 7 is an explanatory diagram showing a modification of the structure of the storage section. Update data 1, 2, and 3 are shown in the figure. The instruction file “LP — 1010 included in the update data 1
C. "ini" includes a description for specifying the update data 2 and 3 in the content of the instruction file.

The update data 2 and 3 are stored independently of the update data 1. The personal computer that performs the update can acquire the update data 1 to 3 and use the update data 2 and 3 together according to the contents of the instruction file of the update data 1. At this time, by using the instruction file included in the update data 2 and 3, respectively,
Install 3.

According to the description in the instruction file of the update data 1, the update data 1 and the update data 2 and 3 may be merged or may be separately sent. Also, the update data server initially sends only the update data 1 and the personal computer sends the update data 1
The update data 2 and 3 may be requested in accordance with the instruction file.

Here, update data 2 and 3 are stored in the storage unit.
Is also specified from the instruction file in update data other than update data 1. Further, the update data 2 and 3 themselves are targets for sending independently. For example, update data 2,
3 may be common update data for a plurality of printers or common update data for specific general-purpose processing.

By using the update data configured as described above, the storage capacity in the storage section can be reduced. In addition, when it is desired to use a new update pattern, it is possible to easily realize the update while using the existing update data as it is.

B. Second Embodiment: FIG. 8 is an explanatory diagram showing a system configuration in the second embodiment. In this embodiment, the personal computer 100b is the update data storage device 2
00b and the network INT to connect to read the update data. The update data storage device 200b has the update data selection function described above in that it does not have the update data selection function.
Different from 00. However, in this embodiment, the personal computer 100b has a function of selecting update data. The update data storage device 200b outputs summary information of the update data to be stored, and the personal computer 10
0b requests the update data by performing a selection process using the summary information.

FIG. 8 shows a personal computer 100b.
The functional block configuration of is also shown. In the following, the functional blocks shown in the figure will be described, paying attention to the points different from the case of the first embodiment.

First, the request unit 350b requests summary information. The update unit 320b compares the acquired summary information with the storage content of the history storage unit 330b, and selects update data as in the update data server 200 of the first embodiment. Here, the summary information includes information in which a list of update data to be stored is tabulated and information in a table in which the update data and the update pattern are associated with each other.

The request unit 350b issues a request for update data based on the selection process of the update unit 320b. The update data input unit 310b inputs the update data based on the request. The update unit 320b updates the software stored in the storage unit 340b using the update data according to the selection result, and the history storage unit 330b according to the update content.
Revision history information.

FIG. 9 is a flow chart showing the processing in the second embodiment. This is a personal computer 1
This is the process performed by 00b.

In step S301, the summary information is read. The request unit 350b issues a request, and the update data input unit 310b performs reading. In step S302,
The update data is selected by comparing the summary information with the storage content of the history storage unit 330b. In step S303,
The update data is actually read based on the selection result. After this, the loop processing in steps S105 to S107 shown in FIG. 5 is performed to perform processing such as installation.

According to the software updating system of this embodiment, the software updating system can be realized by using the update data storage device having a simple structure.
Since only the update data selected in advance based on the summary information is communicated, the update data amount can be reduced.

The request unit 350b may retrieve all update data having a predetermined attribute without requesting the summary information. The update unit 320b may install all of the read update data, or may perform the selection process and then install based on the result.

The update data server 20 of the first embodiment
It is also possible that the personal computer 100b of the second embodiment is connected to 0. At this time, selection processing is provided on both the server side and the client side. Two
The selection may be performed by selecting the stages, or only one of the selection processes may be used according to the user input of the user who operates the client-side computer and other conditions.

Here, the instruction file is, for example, ".in
It may be specified in the update data as a file having a specific extension such as "i". Further, it may have a fixed file name, or may be specified as the file located at the beginning of the update data, and various configurations can be used.

Although the present invention has been described above based on the embodiments, the embodiments of the present invention described above are intended to facilitate understanding of the present invention and are not intended to limit the present invention. . For example, the present invention can be applied not only to updating management software but also to updating various software. The present invention can be modified or improved without departing from the spirit and scope of the claims.

[Brief description of drawings]

FIG. 1 is an explanatory diagram showing an overall configuration of a software update system.

FIG. 2 is an explanatory diagram showing functions of device management software.

FIG. 3 is an explanatory diagram showing a structure of update data.

FIG. 4 is an explanatory diagram showing a configuration of data stored in a storage unit.

FIG. 5 is a flowchart showing a software update process.

FIG. 6 is an explanatory diagram showing a modified example related to selection of update data.

FIG. 7 is an explanatory diagram showing a modified example of the configuration of the storage unit.

FIG. 8 is an explanatory diagram showing a system configuration in a second embodiment.

FIG. 9 is a flowchart showing a process in the second embodiment.

[Explanation of symbols]

100 ... Personal computer 200 ... Update data server 310 ... Update data input section 320 ... Update unit 330 ... History storage unit 340 ... Storage unit 350 ... request section 410 ... Acquisition unit 420 ... Accumulation section 422 ... Update data storage unit 424 ... Related information storage unit 430 ... Selector 440 ... Output unit 424a ... Related information storage unit 100b ... Personal computer 310b ... Update data input section 320b ... Update unit 330b ... History storage unit 340b ... Storage unit 350b ... Requesting unit

Claims (13)

[Claims] 1. A software management apparatus, comprising: a storage unit for storing a set of files constituting the software; an update data input unit for inputting a set of update data for updating the software; An update unit for updating the software based on data, wherein the update data includes a new file divided into a plurality of groups according to update contents, and a new file prepared for each group and to be updated. An update instruction file that identifies the management apparatus, wherein the update unit refers to the plurality of update instruction files and performs update. 2. The management device according to claim 1, further comprising an update history storage unit that stores a previous update history, wherein the update unit selects the update instruction file to be referred to based on the update history. Management device. 3. The management apparatus according to claim 1, wherein an order in which the update instruction files should be updated is set between the update instruction files, and the update unit refers to the update instruction files according to the order. apparatus. 4. The management device according to claim 1, wherein the management device is connected to a server for supplying the update data via a network, and requests the server to send the update data. A management unit that performs the input from the server. 5. The management device according to claim 4, wherein the request unit transmits information for selecting update data used for the update to the server based on the software to be updated. apparatus. 6. An update data supply server, which is connected to a client via a network and supplies update data for updating software stored in the client, wherein the update data is divided into a plurality of groups according to update contents. A storage unit that stores a divided new file and an update instruction file that is prepared for each group and that specifies the new file to be updated, and a storage unit that stores a plurality of the update data in association with each other; An acquisition unit that acquires request data for requesting from the client, a selection unit that analyzes the request and selects a plurality of the update data based on the association, and an output that outputs the selected update data. And an update data supply server including a unit. 7. The update data supply server according to claim 6, wherein the request data includes information on the software to be updated, and the selection unit stores information related to the information and the update data. An update data supply server that determines what is excluded from the selection by comparing 8. The update data supply server according to claim 6, wherein the storage unit stores multiple update data including contents of the plurality of update data, and the sending unit corresponds to the multiple update. An update data supply server that outputs the plurality of update data when the data does not exist, and outputs the multiple update data when the data exists. 9. A method of managing software, comprising the steps of storing a set of files constituting the software, inputting a set of update data for updating the software, and based on the update data. An update step of updating the software, wherein the update data is a new file divided into a plurality of groups according to the update content, and an update instruction for specifying the new file to be updated that is prepared for each group A file, and the updating step refers to the plurality of update instruction files to perform updating. 10. An update data supply method for supplying update data for updating software stored in the client using a server connected to the client via a network, wherein the update data is A new file that is divided into a plurality of groups according to the group, and an update instruction file that is prepared for each group and that identifies the new file that is to be updated, and stores a plurality of the update data in association with each other; Acquiring the request data requesting the update data from the client, analyzing the request and selecting a plurality of the update data based on the association, and outputting the plurality of selected update data And a step of performing. 11. A computer program for causing a computer to manage software, a function of storing a set of files constituting the software, and a function of inputting a set of update data for updating the software. And a computer program for causing the computer to realize an update function of updating the software based on the update data, wherein the update data is a new file divided into a plurality of groups according to update content, A computer program, comprising: an update instruction file that is prepared for each group and that identifies the new file to be updated, wherein the update function refers to the plurality of update instruction files and performs update. 12. A computer program for causing a server connected to a client via a network to supply update data for updating software stored in the client, wherein the update data corresponds to update content. A new file that is divided into a plurality of groups, and an update instruction file that is prepared for each group and that identifies the new file to be updated, and a function of storing a plurality of the update data in association with each other; A function of obtaining request data requesting update data from the client, a function of analyzing the request and selecting a plurality of update data based on the association, and a function of outputting the plurality of selected update data. And a computer program for causing the computer to realize. 13. A computer-readable recording medium on which the computer program according to claim 11 is recorded.