JP4562372B2 - Update data distribution server and update data distribution system - Google Patents

Description

The present invention relates to a client program or data in the update data distribution server and the update data delivery system for delivering via the network.

  In recent years, with the spread of broadband, an increasing number of servers distribute application programs and data via a network. As an example of this, when a client updates an installed program or data, the Web application server normally transmits the update file as shown in FIG.

Patent Document 1 discloses that software version information and its execution program are associated with each other and managed on a server. Further, Patent Document 2 discloses that a record to be updated on a file server is temporarily downloaded to a client's local disk, provisional update is performed, and the result is fed back to the server.
JP 2002-259128 A Japanese Patent Laid-Open No. 08-272669

  However, in the format in which the file is transmitted from the Web application server, it is necessary to separately have management information such as which client to distribute which program or data, and management of data related to the distribution processing and the distribution processing becomes complicated. .

  In view of such problems, the present invention provides an update data distribution server, an update data distribution system, an update data distribution method, an update data distribution program, which simplify the management of data relating to distribution processing and distribution processing of programs and data, The purpose is to provide distribution data.

In order to solve the above problems, the present invention constitutes an update data distribution system together with a client, and distributes update data for updating a program or data installed in the client in units of RDB records. A server,
A distribution management master for storing user information relating to the client;
The update data distribution system and the update data binarized for each version ,
Update master to store in RDB RLB format ;
The update data that has been binarized be distributed to each of the clients being managed by the distribution management master to said distribution table, one row along with the IP address that identifies the client, a distribution table for storing,
User information registration means for registering the user information in the distribution management master;
Update data registration means for registering the update data in the update master;
Extraction means for extracting the client that distributes the update data stored in the update master;
Update data storage means for storing the update data to be distributed in the distribution table for each of the extracted clients ;
The update data distribution server is an RDB server,
The distribution management master includes, as items, “update data distribution system name” and “IP address” which is an IP address of a PC in which the update data distribution system is installed .

  In order to solve the above-mentioned problem, the present invention is characterized in that the distribution table has update application condition information indicating a time when an update by the update data is executed for each update data.

  In order to solve the above-described problem, according to the present invention, the distribution management master includes version information of the program or data installed in the client, and the client program or data is updated by the update data. And version update means for updating the version.

Further, in order to solve the above-described problem, the present invention provides an update having a client and an update data distribution server that distributes update data for updating a program or data installed in the client in units of RDB records. A data distribution system,
The update data distribution server includes:
A distribution management master for storing user information relating to the client;
An update data distribution system and an update master for storing the update data binarized for each version;
A distribution table that stores the binary-updated data distributed to each of the clients managed by the distribution management master in the distribution table in one row together with an IP address that identifies the client ;
User information registration means for registering the user information in the distribution management master;
Update data registration means for registering the update data in the update master;
Extraction means for extracting the client that distributes the update data stored in the update master;
Update data storage means for storing the update data to be distributed in the distribution table for each of the extracted clients ;
The update data distribution server is an RDB server,
The distribution management master has, as items, “update data distribution system name” and “IP address” which is the IP address of the PC in which the update data distribution system is installed,
The client
Update data acquisition means for acquiring the update data from the update data distribution server;
Update means for updating the installed program or data with the update data;
Update result notifying means for notifying the update data distribution server of an update result.

  In order to solve the above-mentioned problem, the present invention is characterized in that the distribution table has update application condition information indicating a time when an update by the update data is executed for each update data.

  In order to solve the above problem, the present invention is characterized in that the estimation means prints an estimate when the estimated amount is calculated.

  In order to solve the above-described problem, according to the present invention, the distribution management master includes version information of the program or data installed in the client, and the client program or data is updated by the update data. And version update means for updating the version.

  In order to solve the above-mentioned problem, the present invention is characterized in that the distribution table has update application condition information indicating a time when an update by the update data is executed for each update data.

  In order to solve the above-described problem, according to the present invention, the distribution management master includes version information of the program or data installed in the client, and the client program or data is updated by the update data. And a version update stage for updating the version.

According to the present invention, the update data distribution server and the update data delivery system to simplify the management of data relating to the delivery process and delivery process of the program or data is obtained.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is an overall view of the apparatus configuration of this embodiment. FIG. 1 shows a distribution server 10 corresponding to an update data distribution server, a development server 11, and clients 12, 13, and 14.

  The development server 11 is used when a system development company conducts program and data development work. The distribution server 10 is an RDB (Relational Database) server that stores developed programs and data and distributes them. An example of this distribution server is WING DIRECT (registered trademark). The clients 12, 13, and 14 are computers on which programs and data are installed, in which a system that is sold or used by a system development company has already been installed. Hereinafter, when explaining these clients 12, 13, and 14, the client 12 is used.

  The distribution server 10, the development server 11, and the client 12 described above are connected by communication means such as the Internet or a dedicated line.

  Next, an outline of processing in the apparatus configuration shown in FIG. 1 will be described with reference to FIG. FIG. 2 shows a state in which a program or data is distributed as one record 15 to the client 12 in FIG. In the following description, a program and data that are update data to be distributed are referred to as distribution material.

  The distribution server 10 has an RDB that converts the developed distribution material into binary data and sets it as one record. From this RDB, as shown in FIG. 2, the distribution material is distributed to each client.

  As described above, since the apparatus configuration of this embodiment can manage the status of distribution and client programs and data versions with a single RDB server, a distribution mechanism can be constructed at low cost. . Also, without setting the association between the distribution material and management information one by one, all of the backup and recovery in the event of a failure can be performed collectively by a DBMS (Database Management System), which will be described later, by inputting an SQL command. it can.

  Next, a hardware configuration diagram of the distribution server 10, the development server 11, and the client 12 described above will be described with reference to FIG. These servers and clients have the same configuration as a general personal computer or workstation. As shown in FIG. 3, a CPU (Central Processing Unit) 20, a ROM 21, a RAM 22, an input device 23, and an output are provided. It has the apparatus 24, the communication apparatus 25, HD26, and the bus | bath B which connects them.

  The CPU 20 executes various programs and performs arithmetic processing. The ROM 21 stores programs necessary for startup. RAM22 memorize | stores the process in CPU20 temporarily, or memorize | stores data. The input device 23 is a keyboard or a mouse. The output device 24 is a display, a printer, or the like. The communication device 25 communicates with other computers. The HD 26 stores various data and programs.

  Next, the software block of the distribution server 10 and each master and table will be described with reference to FIG. The distribution server 10 includes an overall control unit 30, a communication unit 31, a master update unit 32, a distribution material registration unit 33, a user registration unit 34, a distribution target extraction unit 35, a screen generation unit 36, and a DBMS 37. The distribution management master 38, the update master 39, and the distribution table 40 are included.

  The overall control unit 30 is a main thread of each software shown in FIG. The DBMS 37 manages the distribution management master 38, the update master 39, and the distribution table 40, and also performs processing in response to requests from each software.

  The master update unit 32 corresponding to the version update unit updates the distribution management master that has finished distributing the distribution material. The distribution material registration unit 33 corresponding to the update data registration unit registers the distribution material received from the development server 11 in the distribution server 10. The user registration unit 34 corresponding to the user information registration unit registers information about the client.

  The distribution target extraction unit 35 corresponding to the extraction unit and the update data storage unit extracts to which client the distribution material received from the development server 11 is distributed, and stores it in a distribution table to be described later. The screen generation unit 36 generates a screen serving as a user interface when the distribution material received from the development server 11 is registered in the distribution server 10 and acquires input information.

  The communication unit 31 has a driver for communicating via a network and functions corresponding to various protocols. For example, the communication unit 31 has a function corresponding to TCP / IP (Transmission Control Protocol / Internet Protocol), a function corresponding to HTTP (Hyper Text Transfer Protocol), and the like, and performs processing related to the entire communication function.

  Next, the software block of the client 12 will be described with reference to FIG. The client 12 includes an overall control unit 60, a communication unit 64, an update data acquisition unit 63 corresponding to the update data acquisition unit, a system update control unit 62 corresponding to the update unit, and an update result corresponding to the update result notification unit. It is comprised so that the notification part 61 may be included. The overall control unit 60 is a main thread of each software shown in FIG. The update data acquisition unit 63 downloads the distribution material. The system update control unit 62 updates a program or data. The update result notifying unit 61 notifies the distribution server 10 of the updated result.

  The distribution server 10 and the client 12 described above correspond to the update data distribution system.

  Next, the distribution management master 38, the update master 39, and the distribution table 40 will be described with reference to the drawings. In this description, the items of each master and table are described, but the same name indicates the same content, so the description of the name described above is omitted.

  FIG. 6 is a diagram showing a distribution management master. In this distribution management master, system user information is mainly registered. In addition, the distribution management master includes, as items, “user name”, “system name”, “current version”, “PG distribution condition”, “data maintenance month”, “communication environment”, and “IP address”. It has.

  “User name” is the name or name of the user. “System name” is the name of the system installed by the user. “Current version” is the current version of the system installed on the user's PC. “PG distribution condition” represents the extent to which the system update is guaranteed by the contract at the time of system introduction.

  In “Data maintenance month”, the update month of the database to be installed in the system is registered. The item “data maintenance month” is used when, for example, the contract is different in how many times maintenance is performed per year for each user or system. “Communication environment” is a communication connection environment of a user.

  “IP address” is the IP address of the PC in which the system is installed. In this embodiment, an IP address is used to identify a PC, but a method that can identify a client on the network by means in addition to or in place of this may be used.

  In FIG. 6, for example, when “user name” is Tsubasa Motor Corporation, “system name” is SF-Pegasus, “current version” is 2.3a, and “PG distribution condition” is all Pegasus. “Data maintenance month” is from January to December, “Communication environment” is ADSL12M, and “IP address” is 192.168.100.0.

  Next, the update master will be described with reference to FIG. The update master shown in FIG. 7 is a master that registers a distribution material that has been developed for distribution. Further, the update master has “system name”, “version”, “type”, “application condition”, and “content” as items.

  “Version” indicates which version if “Type” is a program, and what version of data is “Data”. In this embodiment, data maintenance is basically performed once a month 12 times a year, and can be selected three times a year or six times a year for the convenience of the user.

  “Type” indicates that “PG” is a program and “DATA” is database update data. The “applicable condition” indicates a time when the update is executed. This “applicable condition” indicates an update date for updating, for example, when the system is updated in accordance with a legal revision. In particular, when updating the same day without setting an update date, a null value is set.

  “Content” is the distribution material itself to be distributed. Specifically, a program or update data that is a distribution material is stored in a binary format. In this embodiment, the RDB data type is a BLOB format. This BLOB format can handle binary data having a file size up to 4G. When distributing a plurality of distribution materials in a single distribution, a plurality of “contents” and “application conditions” are set.

  In FIG. 7, “system name” is SF-Pegasus “version” is the September version, “type” is DATA, “application condition” is null, and “content” is 1011. Has been.

  “Content” is binary data (binary number) in the program execution format, and the data type in the RDB is handled as the BLOB type. The BLOB type is a readable / writable data type stored on the RDB server and can handle binary data up to 4G.

  On the other hand, there is a data type called BFILE type as a large-capacity data format. In this method, data is not directly stored in the RDB server but is stored in a physical file of the OS and an external file is read from the reference information. Since the BFILE type is a read-only data type, it is not possible to perform update processing directly from the DBMS or to deal with a failure. Therefore, the BLOB type is preferable in this embodiment.

  Next, the distribution table will be described with reference to FIG. This distribution table is for distributing distribution materials to clients. Therefore, the distribution table includes “IP address”, “content 1”, “application condition 1”, “content 2”, and “application condition 2” as its items. The “content 1”, “content 2”, “application condition 1”, and “application condition 2” are application conditions for two distribution materials and each distribution material.

  The distribution table shown in FIG. 8 is a specific example, but a general distribution table is composed of one or more sets of “content” and “application conditions” and an IP address. The combination of contents and application conditions is determined by the number of distribution materials.

  Among the descriptions above, the IP address corresponds to the client specifying information. The content corresponds to the update data. The content corresponds to the update application condition information. The distribution table corresponds to distribution data. Also, as shown in FIG. 8, in the distribution data, client identification information and one or more update data are stored in one row.

  In FIG. 8, the content 1 distributed to the client whose “IP address” is 192.168.100.0 is distributed after January 1, 2004, and the content 2 is distributed on the same day because the application condition is null. Is shown.

  The above is the configuration of the present embodiment. Next, specific processing will be described. First, processing performed by the development server 11, the distribution server 10, and the client 12 will be described using the sequence diagram of FIG. The overall processing outline will be described with reference to the sequence diagram of FIG. 9, and then the processing of the distribution server 10 and the client will be described.

  In step S101 corresponding to the user information registration stage, user registration is performed. As a result, information about the client is input to the distribution management master (see FIG. 6). The screen displayed to the operator at this time will be described later.

  In step S102, the distribution material is transmitted from the development server 11 to the distribution server. The distribution material received by the distribution server 10 is registered in the update master (see FIG. 7) in step S103 corresponding to the update data registration stage.

  Next, the distribution server 10 extracts a distribution target in step S104 corresponding to the extraction stage and the update data storage stage. This distribution target extraction is processing for extracting a client that distributes the developed distribution material. The distribution material extracted by this processing is stored in a distribution table (see FIG. 8).

  The next step S105 is a connection from the client 12. By this step S105, the distribution server 10 can take in the IP address of the client 12. If the distribution material for the connected client 12 is in the distribution table, the client 12 downloads the distribution material in step S106.

  The client 12 creates an update file from the downloaded distribution material in step S107. In step S107, the client 12 updates the system with the update file. The client 12 notifies the distribution server of the update result in step S109. Based on the update result, the distribution server 10 updates the distribution management master in step S110.

  The above is the overall processing overview. Next, individual processing of the distribution server 10 and the client will be described.

  First, processing of the distribution server 10 will be described using the flowchart of FIG. This process is a process from user registration to extraction of a client to be distributed. In step S201, the distribution server 10 performs user registration processing by an operator on a user registration screen described later.

  Next, the distribution server 10 receives the distribution material from the development server 11 in step S202. Then, the distribution material received in step S203 is registered in the update master. When registered in the update master, the distribution server 10 extracts clients targeted for the received distribution material in step S204.

  Details of steps S201, 203, and 204 of the processing described above will be described. First, the user registration screen in step S201 will be described with reference to FIG.

  The user registration screen 50 shown in FIG. 11 includes a system name input field 51, a user name input field 52, a version input field 53, a data maintenance number input field 54, a communication environment input field 55, and an IP address input. A column 56 and a registration button 57 are displayed.

  The system name input field 51 is a field for inputting a system name. The user name input field 52 is a field for inputting a user name. The version input field 53 is a field for inputting the version of what is installed on the client. The version input here is recorded in the “current version” of the distribution management master (see FIG. 6). The communication environment input field 55 is a field for inputting a communication environment. The IP address input column 56 is a column for inputting an IP address. The registration button 57 is pressed by the operator when registering the input content in the distribution management master. Information about the user registered on the user registration screen is registered in the distribution management master.

  Next, the distribution material registration in step S203 will be described. An SQL image of this registration method is "insert into'update master'values'SF-Pegasus" 3.2 "PG" 2004/1/1 "c: \ SF-Pegasusu3.2.exe ' Is. This statement states that version 3.2 of the program SF-Pegasus stored in the C drive with the file name SF-Pegasus3.2exe is registered in the update master and the update is applied from January 1, 2004. Represents.

  Registered in this way is SF-Pegasus version 3.2 shown in FIG.

  The above exe file is binary data, but it is possible to set meanings such as “content”, for example, if the first bit from the left is “1”, “0” means program, and “0” means program. . The “content” shown in FIG. 7 is set as such, and the first bit from the left of the “content” of the type PG is 0, and the first bit from the left of DATA is 1. In addition, data used for the purpose of security and data integrity confirmation can be added.

  Next, the distribution target extraction in step S204 will be described using a SQL image. In the distribution target extraction process, a search is performed from the distribution management master by “select“ column to be acquired ”from“ table name ”where“ record condition to be acquired ”.

  For example, a case where “ver.3.2” of the system name “SF-Pegasus” is distributed will be described as an example. “Select” IP address “from” distribution management master “where” system name ”=“ SF-Pegasus'and ” With PG distribution condition '≧ Pegasus3.2', the IP address "192.168.100.0" of Tsubasa Co., Ltd. including SF-Pegasus ver3.2 in the distribution condition is acquired. As a result, it is possible to extract clients that deliver “ver.3.2” of “SF-Pegasus”.

  Next, processing of the distribution server 10 when a client is connected will be described with reference to FIG. In step S301, the distribution server 10 captures the IP address of the client 12. In this case, if the connection is TCP / IP, the IP address can be taken in just by being connected.

  In the next step S <b> 302, the distribution server 10 transmits the distribution material to the client 12. At this time, since the communication environment of the user's client is input in the first user registration, for example, in the case of a low-speed line, the distribution material can be divided and transmitted. Alternatively, the connection status when connected from the client may be determined based on a measurement result obtained by a known speed measurement method to determine whether or not to perform data division, and may be transmitted.

  In the next step S304, the distribution server 10 receives the update result from the client 12. Based on the update result, the distribution server 10 updates the distribution management master in step S305, and ends the process. Specifically, the “current version” data of the distribution management master is updated.

  The above is the details of the processing of the distribution server 10. Next, the processing of the client 12 will be described using the flowchart of FIG.

  In step S <b> 401, the client 12 connects to the distribution server 10. The connection timing may be regular connection such as 2 am every day, or may be performed by an operator's operation.

  If there is a distribution material, the client 12 connected to the distribution server 10 downloads the distribution material in step S402. The client 12 accumulates the distribution material in the HD 26, and when the accumulation ends, the client 12 creates an update file in step S403. Then, the update file is delivered to a system update control program that is a program for updating the system.

  In step S404, the system update control program expands the update file and performs system update processing or database update processing. At this time, if there is a date in the “applicable conditions”, update processing is performed on that date. When the update process ends, the client 12 notifies the distribution RDB server of the end of the update in step S404.

  As described above, in this embodiment, the three databases of the distribution management master, the update master, and the distribution table are sufficient, and it is not necessary to have management information separately.

1 is an overall view of a device configuration of a present embodiment. It is a figure which shows the outline | summary of a process. It is a hardware block diagram of a server and a client. It is a figure which shows the software block of a delivery server, and each master and table. It is a figure which shows the software block of a client. It is a figure which shows a delivery management master. It is a figure which shows an update master. It is a figure which shows a delivery table. It is a sequence diagram which shows the whole process outline | summary. It is a flowchart which shows the process of a delivery server. It is a figure which shows a user registration screen. It is a flowchart which shows the process of a delivery server. It is a flowchart which shows a process of a client. It is a figure which shows a prior art example.

Explanation of symbols

10 Distribution Server 11 Development Server 12, 13, 14 Client 20 CPU
21 ROM
22 RAM
23 Input device 24 Output device 25 Communication device 26 HD
30, 60 Overall control unit 31, 64 Communication unit 32 Master update unit 33 Distribution material registration unit 34 User registration unit 35 Distribution target extraction unit 36 Screen generation unit 37 DBMS
38 Distribution management master 39 Update master 40 Distribution table 51 System name input field 52 User name input field 53 Version input field 54 Data maintenance count input field 55 Communication environment input field 56 IP address input field 57 Registration button input field 61 Update result notification part 62 System update control unit 63 Update data acquisition unit

Claims (6)

An update data distribution system that configures an update data distribution system together with a client and distributes update data for updating a program or data installed in the client in units of RDB records ,
A distribution management master for storing user information relating to the client;
The update data distribution system and the update data binarized for each version ,
An update master to store in the RDB BLOB format ;
A distribution table that stores the binary-updated data distributed to each of the clients managed by the distribution management master in the distribution table in one row together with an IP address that identifies the client ;
User information registration means for registering the user information in the distribution management master;
Update data registration means for registering the update data in the update master;
Extraction means for extracting the client that distributes the update data stored in the update master;
Update data storage means for storing the update data to be distributed in the distribution table for each of the extracted clients ;
The update data distribution server is an RDB server,
The distribution management master has, as items, “update data distribution system name” and “IP address” which is the IP address of the PC in which the update data distribution system is installed.
An update data distribution server characterized by that.   2. The update data distribution server according to claim 1, wherein the distribution table includes update application condition information indicating a time at which an update by the update data is executed for each update data. The delivery management master includes version information of the program or data installed in the client,
The update data distribution server according to claim 1, further comprising a version update unit configured to update the version when the client program or data is updated by the update data. An update data distribution system comprising a client and an update data distribution server that distributes update data for updating a program or data installed in the client in units of RDB records ,
The update data distribution server includes:
A distribution management master for storing user information relating to the client;
An update data distribution system and an update master for storing the update data binarized for each version;
A distribution table that stores the binary-updated data distributed to each of the clients managed by the distribution management master in the distribution table in one row together with an IP address that identifies the client ;
User information registration means for registering the user information in the distribution management master;
Update data registration means for registering the update data in the update master;
Extraction means for extracting the client that distributes the update data stored in the update master;
Update data storage means for storing the update data to be distributed in the distribution table for each of the extracted clients ;
The update data distribution server is an RDB server,
The distribution management master has, as items, “update data distribution system name” and “IP address” which is the IP address of the PC in which the update data distribution system is installed,
The client
Update data acquisition means for acquiring the update data from the update data distribution server;
Update means for updating the installed program or data with the update data;
An update data distribution system comprising: update result notification means for notifying the update data distribution server of an update result.   5. The update data distribution system according to claim 4, wherein the distribution table includes update application condition information indicating a time at which an update by the update data is executed for each update data. The delivery management master includes version information of the program or data installed in the client,
6. The update data distribution system according to claim 4, further comprising version update means for updating the version when the client program or data is updated by the update data.

Images