JPH09146861A - Remote maintenance data distribution device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To deliver revision data on software which runs on each terminal machines through a line by a multi-layered on-line system wherein plural terminal machines are connected to a host through intermediate nodes. SOLUTION: The host 1 has a delivery file which holds revision data corresponding to the version update of a function operating on a slave station including an intermediate node 2 and a terminal machine 3 and a slave station version management part 10 which confirms the version of the function reported from the slave station and delivers the revision data for updating the version of the function of the slave station up to the latest version. The intermediate node 2 has a terminal machine version management part 30 which holds the latest version data on the terminal machine 3 as the slave station, informs the host 1 that the version reported from the terminal machine 3 can not be processed with the latest revision data in such a case, and distributes the revision data distributed from the host 1 to the terminal machine 3. The terminal machine 3 has a version management part 40 which communicates the current version of the function in itself to a host station which is the host 1 or intermediate node 2 and a version maintenance means 31 which updates the version of the function in the machine with the revision data distributed from the host station.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a multi-layer online system in which a plurality of terminals are connected to a host via an intermediate node, and manages the version number of software running on each terminal, and more particularly, a communication line for revision data. It relates to remote maintenance (remote maintenance) that is distributed by and handles revisions for each terminal.

[0002]

2. Description of the Related Art A multi-layer online system in which a host computer and a terminal are connected by a communication line through an intermediate node has become widespread, and terminals installed in each store or office are of various types and business. It is becoming more diverse (intelligent terminals, personal computers, etc.) and the number of connected devices is increasing. Furthermore, since the functions of the terminal are becoming more sophisticated, the frequency / amount of revision of the software installed in the terminal and the revision / correction in response to the occurrence of a bug tend to increase.

FIG. 5 is a schematic diagram of the connection of a multi-layer online system to which the present invention is applied. A host 1H is connected with a plurality of intermediate nodes 2N (servers, relay hosts, etc.), and individual terminals are subordinate to it. This is a form in which a plurality of machines 3T are connected to each other. Due to the spread of personal computers in recent years, one person has appeared in one person in the office, and in such an online system, the number of connected terminals may reach several thousand depending on the system scale.

[0004] When the software of the terminal unit has a failure, a functional upgrade or a functional change, it is necessary to update the software of all the corresponding terminal units promptly and surely. For this purpose, the updating is performed via the communication line. Remote maintenance is used to deliver the data.

In the conventional system configuration for performing remote maintenance, the host computer on the upper side pairs the revision data managed by the revision number with the revision number table according to the revision history according to the type of each terminal or work. When the software is revised, the revision data is transmitted at the timing when the terminal is opened with the terminal as shown in FIG. 6, which will be described later. Are doing.

FIG. 4 is an explanatory diagram of the structure of revision data held by the host computer. In the figure, 110 is a version number management table, 120 is a revision data storage file, and 12 is a revision data storage file.
Reference numerals 1 to 124 are storage areas for revised data. The structure of the version number management table 110 will be described. In the version number column, a symbol "E01" for identifying the version / level as the version number is ...
"E04" is entered, and the storage address of the revision data (α) for E01 is 100 at the revision data storage address column ... "The storage destination address of the revision data (γ) for E03 is at 300" Are entered respectively, indicating that the latest version number at present is “E03”. Further, the dotted line from the version number management table 110 means a pointer indicating the storage destination of the revision data,
In the storage area 121 from the address, the version number “E01”, the revision data “α”, and the next version number “E02” are stored. In the current state of FIG. 4, the latest version number is “E03”, and the next new version number is “E04”.

As shown in FIG. 6, the terminal station revision procedure by the host station holding such revision data notifies the host 1H which is the host station of the current version number from the terminal 3T at the time of the opening procedure. , Host 1H is version management table 1
It is confirmed by 10 whether the current version number of the terminal 3T should be updated. At this time, if the version number notified from the terminal 3T is the old version number (for example, "E01", the latest version number "E0"
In order to be able to revise up to 3 ”, the“ revised data = β, γ ”is transmitted and updated to the latest version, and the version notified from the terminal 3T may match the latest version (“ E03 ”). For example, it notifies that no revision is required and controls to move to work. On the other hand, when the revision data is transmitted from the host 1H, the terminal 3T updates the version number in its own station to the latest revision number, and if there is a notification that the revision is not necessary, the terminal 3T directly shifts to the work execution.

[0008]

In remote maintenance when the online system is constructed in multiple layers, the host 1H connected to the terminal 3T shown in FIG. 6 is an intermediate node 2N (a relay host or a server). )
And the intermediate node 2N is connected to the host 1H at a higher level. Therefore, the host 1H entrusts the intermediate node 2N with version number management for all terminals 3T under the control of the intermediate node 2N, so that the host 1H holds the version number management table 110 and revisions shown in FIG. It was necessary to hold all the data (121 to 124) in the intermediate node 2N. Further, each time a revision occurs, it is necessary to deliver the revision data to the intermediate node 2N relating to the revision or the intermediate node 2N having the terminal 3T under its control at an appropriate timing. On the other hand, the terminal 3T can confirm the necessity of revision with the direct upper station (intermediate node), and although the load of the host 1H of the highest station is gradually reduced, all intermediate nodes 2N host it. It was necessary to hold the same amount of revision data as 1H, which was a waste of resources.

In general, the terminal software is managed in a unified manner for each terminal of the same type, and operates with the same version number. For example, in FIG. 5, the intermediate node (1) 2N-
All terminals (3T-1, 3T- connected under the control of 1
The version number of 2,3T-3) is operating at "E03".

However, sometimes, due to a hardware failure, the software after failure recovery must be started from initial installation. At this time, regarding the terminal, first, using the storage medium for initial installation (floppy disk, magnetic disk, optical disk, etc.), the software version of the terminal 3T is set to "E00", and then, Revised data “E01 =
“α”, “E02 = β”, and “E03 = γ” are distributed from the upper station, and the work of sequentially updating the version number is performed.

The occurrence of such a hardware failure is not expected, and the connected intermediate node must always hold the revision data of all the software of the subordinate terminals, and for this reason However, there is a problem that the resources of the intermediate node are unnecessarily occupied.

In view of the above points, an object of the present invention is to provide a means for performing remote maintenance of intermediate nodes and terminals in a multi-layer online system promptly and reliably without wasting resources.

[0013]

The above problems can be solved by the remote maintenance data distribution device according to the present invention, which is constructed as shown in FIG.

FIG. 1 is a principle view of the present invention, in which a host 1 and a terminal 3 are connected via an intermediate node 2 in multiple layers via communication lines. In the figure, 1 is a host that is the core of the online system, and has a lower station version management unit 10 and distribution file 11, and 2 is an intermediate node that has a terminal version management unit 20. Further, 3 is a terminal, which has a version number management unit 30 and a version number maintenance means 31, respectively.

The distribution file 11 in the host 1 holds revision data corresponding to version number updates of the functions operating in the intermediate node 2 and the terminal 3 which are subordinate stations, and the subordinate station version number The management unit 10 confirms the version number of the function notified from the subordinate station, and distributes the revision data for updating the version number of the function of the subordinate station to the latest version number. The terminal 3 includes a terminal version management unit 20 that distributes the revision data addressed to the terminal 3 delivered from the host 1 to the subordinate terminals 3, and the terminal 3 is the current version number of the function in the terminal 3. And a version number maintenance unit 31 for updating the version number of the function in the terminal 3 with the revision data distributed from the upper station.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 2 is a block configuration diagram of an embodiment of the present invention. In the figure, 1 is a host which is the highest station of a multi-layer online system, 2 is a line connected to a host 1, and a plurality of terminals 3 are subordinate to it. Intermediate nodes 3 such as connected relay computers or servers are terminals.

In the host 1, reference numeral 100 connects the distribution file 111 storing the revision data for the intermediate node and the distribution file 112 storing the revision data for the terminal, and the inside of the intermediate node 2 and the terminal 3 under it. A version number management unit that manages the version number of the software that operates in 1.30 is a business processing unit that processes the business in cooperation with the intermediate node 2 and the terminal 3, and 140 is a host control unit that includes a line control unit.

In the intermediate node 2, 200 is a version number management relay that cooperates with the version number management unit 100 of the host 1 and manages the version numbers of the software of its own station (intermediate node 2) and its subordinate terminals 3. Part, 201 is a storage file that holds the revision data for the intermediate node 2, 202 is an intermediate node version maintenance unit that processes version updates based on the revision data in the storage file 201, and 203 is delivered from the host 1. A delivery file storing revision data for the subordinate terminals 3, 204 is a subordinate terminal version management unit, 205 is a relay control unit including a line control unit, and 206 is a revision data management unit.

Next, in the terminal 3, 300 is a business processing unit for performing business with the latest version of software, 3
Reference numeral 01 is a revision data management unit, 302 is a storage file that holds the version number distributed from the upper station, 303 is a terminal version maintenance unit that reads the revision data from the storage file 302 and updates the software of the business processing unit 300, A terminal control unit 304 includes a line control unit.

The operation of the system having the above configuration will be described with reference to FIG.
Will be described together with. FIG. 3 is a flowchart of the revision process of the present invention. Step S1: Pre-delivery, which is an irregular process performed only when the version number is revised on the host 1 side. The host 1 activates the version number management unit 100 when the software revised by the revision work (not shown) is written in the distribution file 111 or 112. The version number management unit 100 reads the latest version numbers and revision data for the intermediate node 2 and the terminal 3 from the distribution files 111 and 112, respectively, and distributes them to the intermediate node 2 via the host control unit 140. The relay control unit 205 determines whether or not the delivered intermediate node 2 is received, and sends the revision data to the version management relay unit 200 so that the revision data addressed to the own station is stored in the accumulation file 201, and the revision data addressed to the terminal 3 is revised. The data is held in the distribution file 203.

Step S2: The power supply of the host and the intermediate node is turned on, and the open communication between the host 1 and each of the subordinate intermediate nodes 2 is performed by exchanging the ID (identification code) of the station. The version management relay unit 200 of the intermediate node 2 requests the revision data management unit 206 to read the current version number of its own station from the storage file 201, sets the current version number information in the open message, and relays it. It is transmitted from the control unit 205 to the host control unit 140.

Step S3: The host control unit 140 extracts the version number information in the message and notifies the version number management unit 100 of the version information, and collates the version number with the distribution file 111 for the intermediate node 2. If the current version number of the received intermediate node 2 is old, the process branches to step S4, and if the version numbers match, the process waits at start B (step S6).

Step S4: The version number management unit 100 collates the received version number with the latest version number in the distribution file 111 to determine the total version number required to update the current version number of the intermediate node 2 to the latest version number. Read the revised data from the distribution file 111,
It is distributed to the relay control unit 205 via the host control unit 140.

Step S5: The version management relay unit 200 uses the modified data delivered from the host 1 to the modified data management unit 2.
Then, the intermediate node version number maintenance unit 202 updates the version number of the software of its own station to the latest version number by using the revised data, and then starts B (step B). Stand by at S6).

Step S6: When the power of the terminal 3 is turned on, the open communication between the terminal 3 and the intermediate node 2 is performed by exchanging IDs (identification codes), and the revision data management unit 301 of the terminal 3 Reads the current version number of its own station from the accumulation file 302, sets the current version number information in the open message, and transmits it to the intermediate node 2 via the terminal control unit 304.

Step S7: The relay control unit 205 of the intermediate node 2 receives the open message, extracts version number information from the message, and notifies the terminal version number managing unit 204 of it. The terminal version number management unit 204 reads out the version number held in the distribution file 203 (the latest version number has been distributed in step S1) and collates it, and as a result, reads the version number from step S8 to step S1.
Branch to any one up to zero.

Step S8: The current version number of the terminal matches the latest version number, and the business process is performed as it is (step S1).
Branch to 2). Step S9: The current version number of the terminal device 3 is the version number immediately before the latest version number, and since the revision process can be handled by the revision data held in the distribution file 203, the terminal version management unit 20
Reference numeral 4 reads the revision data stored in the distribution file 203 and distributes it to the terminal device 3 via the relay control unit 205.
The terminal control unit 304 inputs the received version number and revision data to the revision data management unit 301, stores the revision data in the accumulated file 302, and branches to step S11.

Step S10: The current version number of the terminal device 3 is the old version number which is several steps before, and the revision data cannot be processed only by the revision data held in the distribution file 203 in the intermediate node 2. Therefore, the relay control unit Notify the host 1 via 205. The host control unit 140 sends this notification to the version number management unit 100.
Then, the required revision data stored in the delivery file 112 is read and delivered to the intermediate node 2. The relay control unit 205 of the intermediate node 2 notifies the revision management data to the version number management relay unit 200 and temporarily stores it in the distribution file 203. Then, the terminal version management unit 204 distributes the revision data read from the distribution file 203 to the revision data management unit 301 via the terminal control unit 304 of the terminal 3, and stores it in the storage file 302.

Step S11: Terminal version number maintenance unit 303
Reads the revision data from the storage file 302 and updates the software version of the business processing unit 300 to the latest version. Step S12: The work processing unit 300 executes the work with the updated latest version number, and performs the closing process upon completion of the work.

In the above description, the version number update work of the version number maintenance units (202, 303) in the intermediate node 2 and the terminal 3 is a well-known technique, and is not particularly mentioned in the embodiment of the present invention. .

[0031]

As described in detail above, according to the present invention, in remote maintenance of intermediate nodes and terminals in a multi-layer online system, the load on the host is gradually reduced and the resources of the intermediate nodes are wasted. This has the special effect that the efficient version update work can be performed quickly and reliably on each terminal.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a principle configuration of the present invention.

FIG. 2 is a block diagram showing an embodiment of the present invention.

FIG. 3 is a flowchart of a revision process.

FIG. 4 is a diagram illustrating the structure of revised data.

FIG. 5 is a schematic diagram of multi-tier online system connection.

FIG. 6 is an explanatory diagram of a conventional version number maintenance procedure.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 host 2 intermediate node 3 terminal 10 lower station version management section 11 distribution file 20 terminal version management section 30 version management section 31 version maintenance means

Claims (1)

[Claims] 1. In an online system in which a host and a terminal are connected in multiple layers via an intermediate node, the host corresponds to version update of a function operating in a subordinate station including the intermediate node and the terminal. A distribution file holding revision data and a lower station that confirms the version number of the function notified from the lower station and updates the version number of the function of the lower station to the latest version And a version management unit, the intermediate node holds the latest revision data of the terminal as a subordinate station, when the update of the version notified from the terminal cannot be processed by the latest revision data The terminal has a terminal version management unit that notifies the host and distributes the revision data distributed from the host to the terminal, and the terminal determines the current version of the function in the terminal as the host or the previous version. It is configured to have a version number management unit that communicates with an upper node that is an intermediate node, and a version number maintenance unit that updates the version number of the function in the terminal with revision data distributed from the upper station. Remote maintenance data distribution device characterized by.