JP2010079546A - Program distribution updating system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program distribution updating system capable of updating program distribution to program distribution of a predetermined version which includes program distribution of a first version. <P>SOLUTION: The program distribution updating system includes a distribution updating management server 2 and a client terminal 1 which are mutually communicably connected via a network 4. Client software P1 capable of executing application updating processing is installed in the terminal 1. The distribution updating management server 2 extracts first-version and revised programs D1, D2, detection conditions D3, D4 for these programs D1, D2 and priority relationship and dependence relationship D5 indicating an integration direction of versions from a database 3 based on disclosed information D6 in response to a request from the terminal 1, returns these extracted results to the terminal 1, extracts a necessary program based on a list of programs received by the software P1 and the priority relationship, receives the program by a download request, and installs the downloaded program, based on the dependence relationship. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a program distribution update system capable of transmitting or distributing an initial version program, a revised program, and the like.

  At present, various software packages are commercially available, and the revised program is distributed via a network. In addition to commercial applications, companies may also use custom applications that are created independently, and revision programs may be released for such programs.

  In recent years, there has been a need to unify software environments within a company from the viewpoint of security or internal control. However, if the end user leaves it, software versions, patches, and the like are not properly managed, and internal control and the like are not properly performed. For the end user, it is often difficult to grasp the dependency relationship between the software updated by the revised program, the software environment in the computer, etc., and management may not be performed properly. Alternatively, a heavy work load is generated on the end user. On the other hand, such management is a heavy burden for the administrator.

  In order to solve such a problem, a technique for storing the updated program and the above-mentioned dependency relationship in a database and distributing the latest upgrade-program that makes the end user aware is becoming widespread (for example, patents). Reference 1). The update is performed as necessary by grasping the version information of the program in the client terminal via a network such as the Internet or a LAN (Local Area Network).

  FIG. 12 is a block diagram of such an update program distribution system. The update program distribution system 200 includes a client terminal 201 and an update program distribution server 202 that are communicably connected via the network 4. Client-side update software P21 is installed in the client terminal 201, and the update process on the client terminal side is possible through this. Hereinafter, the client side update software P21 is regarded as a unit constituting the client terminal 201.

  The update program distribution server 202 is connected to an update program management database (hereinafter simply referred to as a management database) 203 that stores data usable for program update. Here, the management database 203 stores an update program D21, an update program detection condition D22, and an update program dependency D23. Here, the update program corresponds to the revised program. In the update program dependency D23, for example, the name of the program that is the premise of the update is set.

  In updating the program, the client-side update software P21 transmits a request for the update program to the server 202. Upon receiving this request, the server 202 transmits the update program detection condition D22 and the update program dependency D23 to the client-side update software P21.

The client side update software P21 determines the necessity of installation based on the received update program detection condition D22 and the update program dependency D23, and determines the required update program. When it is determined that the installation is necessary, the client side update software P21 requests the server 202 for the necessary update program, and installs it. With such a configuration, the end user can install without being aware of the dependency between programs.
JP 2005-222453 A

  However, the conventional update program distribution technique has the following problems. First, it is assumed that the first version of the application is installed for the update. However, the conventional update program distribution technique cannot distribute the first version of the application that is not installed. In such a case, relying on the end user for installation tends to cause the following problems due to inexperience.

  Specifically, problems such as incomplete installation, erroneous installation, postponed installation, and failure to install. As a result, the management objective of unifying application versions is likely not to be achieved.

  In such a case, if the program is simply distributed, the administrator needs to select each target client terminal and distribute the application, and the burden on the administrator is large. Even if the distribution is performed under the burden of the administrator, there is a possibility that it will be uninstalled due to an erroneous operation of the end user, and the human burden such as monitoring will not be lost. In addition, it is not always the case that the latest version is unified. In such a case, it is necessary for the administrator to select a program to be distributed while grasping complicated dependencies, target versions, etc. The work burden increases.

  SUMMARY OF THE INVENTION In view of the above situation, an object of the present invention is to provide a program distribution update system capable of updating to a predetermined version of a program including distribution of an initial version of a program.

In order to solve the above problems, the present invention provides the following configurations.
The invention according to claim 1 includes a distribution update management server and a client terminal that are communicably connected to each other via a network, and the client terminal executes the installation of the first or revised program on itself. Program distribution is installed, and the distribution update management server can access a program distribution update management database storing data usable for distribution of the program to the client terminal. An update system, wherein the program distribution update management database includes an application as a first edition program, a revised program, a component ID for identifying each, a dependency relationship between the programs, a priority relationship regarding unification of versions, and disclosure Before The application, the revised program, which stores public information that makes it possible to specify a program, and in which the distribution update management server is released based on the public information in response to a list request from the client software The component ID, the dependency relationship, and the priority relationship are read out from the program distribution update management database and returned as a list of installed update releaseware, and in response to a download request from the client software, the requested application and The revised program is returned, and the client software can make the list request for requesting the distribution update management server for a list of the application and the revised program, and after the list request, the distribution update management server. Waiting for and receiving the introduction update publicware list from the server, detecting the component IDs of the application and the revised program that are not installed in the received introduction update publicware list, and detecting each of the detected From the component ID, the component ID of the version of the program after the version prioritized based on the priority relationship is excluded to obtain a compatible wear list, and the download to the distribution update management server with the compatible wear list attached It is characterized in that it can be requested and downloaded, and the downloaded program can be installed in the client terminal based on the dependency relationship.

  According to the first aspect of the present invention, the distribution update management server and the client terminal are connected so as to be communicable with each other via a network, and the client terminal installs the first version or the revised program on itself. Program distribution update system in which executable client software is installed and the distribution update management server can access a program distribution update management database storing data usable for program distribution to client terminals The program distribution update management database includes an application as a first edition program, a revised program, a component ID for identifying each, a dependency relationship between each program, a priority relationship regarding unification of versions, and a published program Specific The distribution update management server responds to the list request from the client software, and is released based on the public information, the application, the revised program, the component ID, the dependency relationship, and the priority relationship Is read from the program distribution update management database and returned as a list of introduced update publicware, and in response to a download request from the client software, the requested application and the revised program are returned, and the client software is updated to the application and revised version. A list request for requesting a list of installed programs to the distribution update management server is possible. After the list is requested, a list of installation update release software is received from the distribution update management server and installed in the received installation update release software list. The component IDs of the applications that have not been updated and the revised programs are detected, and the component IDs of the versions of the programs later than the versions that are prioritized based on the priority relationship are excluded from the detected component IDs. And a download request to the distribution update management server with a list of compatible wear attached, and the downloaded program can be installed on the client terminal based on the dependency relationship. It is possible to realize a program distribution update system capable of updating to a predetermined version of a program.

Hereinafter, embodiments of the present invention will be described with reference to the drawings showing examples.
FIG. 1 is a block diagram schematically showing an embodiment of a program distribution update system according to the present invention. As shown in FIG. 1, the program distribution update system 100 includes a distribution update management server 2 and a client terminal 1 that are communicably connected to each other via a network 4.

  The client terminal 1 has client software P1 installed. Here, by executing the client software P1, an application update process for installing or updating a predetermined version of the program on the client terminal 1 can be executed. Hereinafter, the client software P1 is regarded as a unit constituting the client terminal 1. Therefore, the client software P1 forms a unit that can perform predetermined processing, communication, and the like. Here, the application is, for example, a document creation tool, a table creation tool, or the like, and is an object to be unified.

  Here, in response to the request from the client terminal 1, the distribution update management server 2 performs a program distribution update management process for program distribution and update. The distribution update management server 2 is connected to a program distribution update management database (hereinafter referred to as P distribution update management DB) 3 that stores information usable for program distribution update management processing. The management console 21 serves as an input / output unit for the distribution update management server 2.

  First, the P distribution update management DB 3 stores an application D1 that is a candidate for installation in the client terminal 1 and a revised program D2 thereof. The P distribution update management DB 3 also stores a detection condition D3 for detecting an application D1 that is not installed, and a detection condition D4 for detecting updated.

  The P distribution update management DB 3 further stores dependency information D5 between programs related to the update of the target program, and public information D6 that can specify the public status of the application D1 and the revised program D2. Here, the release means that the application D1 and the revised program D2 can be installed in the client terminal 1 under appropriate conditions.

  FIG. 2 is an explanatory diagram of an application detection table stored in the P distribution update management DB. As shown in FIG. 2, an application name T22, its detection condition T23, and binary data T24 are set in the application detection table T2 in association with the component ID (T21).

  Here, an ID capable of uniquely identifying the application is set in the component ID (T21), and the name of the application is set in the application name T22. In the detection condition T23, a condition for detecting an application that is not installed in the client terminal is set. Although binary data of the corresponding application is set in the binary data T24, a storage location of the binary data may be set.

  FIG. 3 is an explanatory diagram of the revised program detection table stored in the program distribution update management database. In the revised program detection table T3, as shown in FIG. 3, a revised program name T32, its detection condition T33, and binary data T34 are set in association with the component ID (T31).

  Here, an ID for uniquely identifying the revised program is set in the component ID (T31), and the name of the revised program is set in the revised program name T32. In the detection condition T33, a condition for detecting that the corresponding revised program has been installed in the client terminal is set. In the binary data T34, binary data of the corresponding revised program is set, but a storage location of binary data may be set.

  FIG. 4 is an explanatory diagram of the dependency relationship table stored in the program distribution update management database. As shown in FIG. 4, a dependency component ID (T41) and its dependent component ID (T42) are set in the dependency relationship table T4. Here, the dependent component ID (T41) is set with an ID that can uniquely identify the immediately upper program (hereinafter referred to as a dependent program) that depends on a program (hereinafter referred to as a dependent program) to be installed. The In the dependent component ID (T42), an ID capable of uniquely identifying the corresponding dependent program is set.

  FIG. 5 is an explanatory diagram of the priority relationship table stored in the program distribution update management database. The priority relationship is information that forms a part of the dependency relationship and can set the unification direction of the version and the like, and the target version can be specified based on the priority relationship table. As shown in FIG. 5, a priority component ID (T51) and its priority component ID (T52) are set in the priority relationship table T5. Here, in the priority component ID (T51), an ID capable of uniquely identifying a program that is prioritized in the update (hereinafter referred to as a priority program) is set. In the priority component ID (T52), an ID capable of uniquely identifying a program having a priority immediately below the corresponding priority program (hereinafter referred to as a priority program) is set.

  FIG. 6 is an explanatory diagram of the public information table stored in the program distribution update management database. In the public information table T6, as shown in FIG. 6, the component ID (T61) and the public setting (T62) are set. Here, IDs corresponding to the component IDs (T21, T31, T41, T51) of the tables T2 to T5 are set in the component ID (T61). In addition, the same thing is set to component ID (T21, T31, T41, T51) which specifies the same program or component between each table T2-T6. Also, in the public setting (T62), whether or not the corresponding program is already public is set.

The operation of the program distribution system configured as described above will be described below.
FIG. 7 is a sequence diagram for explaining program distribution update processing performed by the client software and the server. In the program distribution update process, first, the client software P1 makes a request for a list of applications and revised programs (hereinafter referred to as “introduction update release software”) published to the server 2 (S101). Here, this list request is made periodically, for example.

  Next, in response to the list request from the client software P1, the server 2 creates a list of the above-described information related to the installation update releaseware (hereinafter referred to as the introduction update releaseware list) and returns a list request. Response processing is performed (S110). Next, the client software P1 receives the introduction update releaseware list, and based on the list, introduces update update releaseware (hereinafter referred to as “adaptive wear”) suitable for installation (S120).

  In the compatible wear extraction process, detection of the first version of the application that has not been installed and detection of a revised program suitable for the priority relationship and the dependency relationship are performed. In the adaptive wear extraction process, determination of compatible wear based on these detection results, a download request for requesting the server 2 to download the determined compatible wear, and the like are performed. Here, the download request is accompanied by a list of compatible wear made up of a list of compatible wear.

  Next, in response to the download request, the server 2 reads and returns the binary data T24 and T34 of the program listed in the compatible wear list (S130). Hereinafter, the process in step S130 is referred to as a download request response process. Next, the client software P1 performs installation processing of the binary data T24 and T34 of the compatible wear (S140).

  FIG. 8 is a flowchart illustrating list request response processing performed by the server. In the list request response process, first, the server 2 receives a list request for introductory update publicware from the client software P1 (S111). Next, the server 2 accesses the P distribution update management DB 3 and extracts the component ID (T61) whose public setting (T62) in the public information table T6 is public (S112).

  Next, the server 2 extracts information in the tables T2 and T3 corresponding to the component ID (T61) (S113), and creates a publicware condition list including these (S114). In step S113, the application name T22 and the detection condition T23 are extracted from the application detection table T2, and the revised program name T32 and the detection condition T33 are extracted from the revised program detection table T3.

  Next, the server 2 retrieves the dependency component ID (T41) from the dependency relationship table T4 using each component ID (T61) as a key, and creates a dependency relationship list including the corresponding part (S115). The dependency list includes the detected dependency component ID (T41) and the dependent component ID (T42). Note that in step S115, it is not necessary to search for a dependency relationship for obvious items such as the component ID (T61) of the first version program. If the dependency relationship table T4 is not detected in step S115, the dependency relationship list has no entry.

  Next, the server 2 searches for the priority component ID (T51) from the priority relationship table T5 using the component ID (T61) as a key, and creates a priority relationship list including the corresponding parts (S116). The priority relationship list includes the detected priority component ID (T51) and the prioritized component ID (T52). If the priority relationship table T5 is not detected in step S116, the priority relationship list has no entries.

  Next, the server 2 returns an introduction update publicware list including the publicware condition list created in step S114, the dependency relation list created in step S115, and the priority relation list created in step S116 (S117).

  FIG. 9 is a flowchart for explaining the adaptive wear extraction process performed by the client software. In the compatible wear extraction process, first, the client software P1 receives a list of introductory update publicware from the server 2 (S121). Next, based on the received detection condition T23 in the list, the client software P1 detects an application that is not installed among the applications in the list and marks it in the list (S122). In step S122, those that have not been installed are marked as installation candidates, and the remaining ones are marked as unnecessary in the list.

  Next, the client software P1 detects the installed program among the revised programs in the list based on the detection condition T33 in the introduction update publicly available software list, and marks it in the list (S123). In step S123, those that have been installed are marked as installation unnecessary, and the remaining ones are marked as installation candidates in the list.

  Next, the client software P1 detects the prioritized component T52 in the publicware condition list based on the priority relationship list in the introduction update publicware list, and marks it in the list (S124). In step S124, the prioritized component T52 is marked as not requiring installation in the list.

  Next, the client software P1 searches for an installation candidate that is marked as an installation candidate in the introduction update publicware list (S125), and when it is not detected, the process ends. What is marked as an installation candidate in step S125 is the above-mentioned compatible wear. When what is marked as an installation candidate in step S125 is detected, the client software P1 extracts its component ID and creates a compatible wear list made up of these (S126). Next, the client software P1 makes a download request to the server 2 with the list of compatible wears attached (S127).

  FIG. 10 is a flowchart illustrating the download request response process performed by the server. In the download request response process, first, the server 2 receives a download request (S131). Next, the server 2 extracts each component ID in the attached compatible wear list, and searches and reads the corresponding binary data from the tables T2 and T3 using each as a key (S132). Next, the server 2 returns the binary data of the read compatible wear to the client software (S133), and the download request response process ends.

  FIG. 11 is a flowchart for explaining an installation process performed by the client. In the installation process, the client software P1 downloads from the server 2 the binary data of the compatible wear that has been requested for download in step S127 (S141). Next, the client software P1 installs binary data in the client terminal 1 (S142). Here, the installation is performed based on the dependency list in the introduction update publicware list received in step S121.

  The program distribution update system according to the present invention is used as a system including a server and a client in a company or the like, and can be used in an information equipment manufacturing industry, a software manufacturing industry, etc., and manages applications and tools of administrators and end users. Increase the usefulness of such products in reducing the burden.

It is a block block diagram which shows typically one Example of the program delivery update system by this invention. It is explanatory drawing about the application detection table stored in P delivery update management DB. It is explanatory drawing about the revision program detection table stored in the program delivery update management database. It is explanatory drawing about the dependency relationship table stored in the program delivery update management database. It is explanatory drawing about the priority relationship table stored in the program delivery update management database. It is explanatory drawing about the public information table stored in the program delivery update management database. It is a sequence diagram explaining the program delivery update process which a client software and a server perform. It is a flowchart explaining the list request | requirement response process which a server performs. It is a flowchart explaining the suitable wear extraction process which client software performs. It is a flowchart explaining the download request response process which a server performs. It is a flowchart explaining the installation process which a client performs. It is a block block diagram of the conventional update program delivery system.

Explanation of symbols

1,201 Client terminal 2 Distribution update management server 3 Program distribution update management database (P distribution update management DB)
4, 204 Network 21 Management Console 100 Program Distribution Update System 200 Update Program Distribution System 202 Update Program Distribution Server 203 Update Program Management Database (Management Database)
D1 application D2 revised program D3 application detection condition D4 revised program detection condition D5 dependency D6 public information D21 update program D22 update program detection condition D23 update program dependency P1 client software P21 client side update software T2 application detection table T3 revised program Detection table T21, T31 Component ID
T22 Application name T23, T33 Detection condition T24, T34 Binary data T32 Revised program name T4 Dependency relationship table T41 Dependent component ID
T42 Dependent component ID
T5 priority relationship table T51 priority component ID
T52 Preferred component ID
T6 Public information table T61 Component ID
T62 release settings

Claims (1)

A distribution update management server and a client terminal, which are connected to be communicable with each other via a network, are installed with client software capable of executing installation of an initial version or a revised program on the client terminal. The distribution update management server is capable of accessing a program distribution update management database that stores data that can be used for distribution of the program to the client terminal.
The program distribution update management database is
Stores the application as the first version of the program, the revised program, the component ID that identifies each, the dependency between each of the programs, the priority relationship regarding the unification of the versions, and the public information that enables the identification of the published program And
The delivery update management server is
In response to the list request from the client software, the application, the revised program, the component ID, the dependency relationship, and the priority relationship that are disclosed based on the disclosure information are displayed in the program distribution update management database. Read from and reply as a list of introduced update publicware,
In response to the download request from the client software, the requested application and the revised program are returned.
The client software is
The list request for requesting the distribution update management server for a list of the application and the revised program is possible, and after receiving the list request, waiting for and receiving the list of installed update releaseware from the distribution update management server,
The component IDs of the application that has not been installed and the revised program in the received introduction / update publicware list are detected, and the version that is prioritized based on the priority relationship from the detected component IDs A version of a later version of the program excluding the component IDs is used as a compatible wear list, the compatible wear list is attached, the download request is sent to the distribution update management server, and the downloaded program is set as the dependency relationship. Can be installed on the client terminal based on
A program distribution update system characterized by the above.

Images