JPH0214354A - Control processing system for common data - Google Patents

Abstract

PURPOSE:To eliminate the wasteful transferring of common data by updating the common data which are held by a processing node itself, and counting the updating number of the data with a control node and the processing node. CONSTITUTION:When a processing node 10 updates the common data which are held by the processing node itself, an updating counter is stepped for the value of a local counter 11. The transmission of the common data is executed to a control node 20 and common data 23 in the control node are updated. Then, the control node steps a local counter 21 and a grobal counter 22 only for the stepping part of the local counter in the processing node. The control node 20 steps the value of a grobal counter 12 in the processing node 10,which executes the transmission, and updates the common data of another processing node 10'. Then, the values of the local counter and global counter are stepped.

Description

[Detailed Description of the Invention] [Summary] Regarding a management processing method for common data in a distributed data processing system consisting of a plurality of processing nodes that execute processing according to common data, a management node that manages common data of processing nodes is provided. In order to maintain distributed data processing even if an abnormality occurs in When updating common data that it owns, it increments the count value of its own local counter each time it is updated, and if the communication status with the management node is normal, the updated data is sent via the management node. In addition to processing common data so that it becomes common data for the entire system,
The processing node increments the count values of all counters except its own local counter with the number of updates, and when the communication status returns to normal from the abnormality, the processing node updates its own local counter and the local counter of the management node. Check whether the counted values match, and if they do not match, the common data on the local counter side with the newer counted value is processed as common data for the entire system via the management node, and all local counters are processed as common data for the entire system. The configuration is such that the count value of the global counter is incremented with a difference value so that the count value of the global counter becomes the latest count value.

[Industrial application field]

The present invention relates to a common data management processing method in a distributed data processing system consisting of a plurality of processing nodes that execute processing according to common data.

For example, a building management system employs a distributed data processing system consisting of a plurality of processing nodes, each of which executes a predetermined process. In such a distributed data processing system, each processing node holds common data that is common to all processing nodes and executes its own processing, and at the same time, each processing node performs its own processing by holding common data that is common to all processing nodes. It becomes necessary to update the information from time to time. From now on, such distributed data processing systems will be equipped with a common data management processing method to reflect the common data independently updated in each processing node to all other processing nodes. There is a need to let it happen.

[Conventional technology]

The common data management processing method in conventional distributed data processing systems employs a method in which the management node that manages the processing nodes has mask data for the common data, and the common data is managed using this mask data. It was. In other words, by copying the mask data of the management node to the file of each processing node at the time of initial program loading, each processing node is configured to have a copy of the common data, and each processing node stores this copy that it owns. It refers to the data and executes a predetermined process. Then, when it is necessary to update the common data on each processing node, the management node that received the information updates the mask data, and the updated mask data is transferred to the copy data of all processing nodes. The idea was to manage common data by expanding the system into multiple parts.

[Problem to be solved by the invention]

However, with such conventional technology, if the management node goes down or an abnormality occurs in the line between the management node and the processing node,
This means that the common data cannot be updated. When this happens, there is a problem in that a processing node that should normally be able to process becomes unable to execute the process because it cannot update the common data. That is, the configuration of the prior art has the disadvantage that it does not constitute a distributed data processing system in the event of a failure on the management node side.

The present invention has been made in view of such circumstances, and even if an abnormality occurs in the management node or the line between the management nodes, each processing node continues to update common data and returns to a normal state. The purpose of the present invention is to provide a common data management processing method that allows updated common data to be immediately expanded to other processing nodes when the update occurs.

[Means to solve the problem]

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

In the figure, 10 is a plurality of processing nodes, which execute predetermined processing according to common data that is common to the entire system, and independently update the common data held by itself from time to time, and 20 is a management node. 11 is a local counter provided in the processing node 10 and counts the number of updates of common data executed by the processing node 10; 12 is a global counter provided in the processing node 10; 13 is a common data storage means provided in the processing node 10 for storing common data; 14 is a communication state determination means that the processing node 10 can control; a device that determines whether the communication state with the management node 20 is normal or abnormal and whether it has returned to the normal state;
15 is a data management means provided in the processing node 10, which manages the local counter 11, the global counter I2, and the common data storage means 13; 16 is a counter incrementation means provided in the data management means 15, which manages the local counter 11, the global counter I2, and the common data storage means 13; 11 and a device for incrementing the count values of the global counter 12; and 17, a count value coincidence judgment means provided in the data management means 15, which determines whether the count values of the local counter 11 and the local counter provided in the management node 20 match. 18 is a data management means 15
19 is a common data update requesting means provided in the data management means 15, which updates the common data in the common data storage means 13;
21 is a local counter provided in the management node 20 that counts the instruction value from the processing node 10; 22 is a global counter provided in the management node 20; 23 is a common data storage means provided in the management node 20 for storing common data; 25 is a data management means provided in the management node 20; 26 is a counter incrementing means provided in the data management means 25, which increments the counted values of the local counter 21 and global counter 22. 28 is a common data update means provided in the data management means 25, which updates the common data in the common data storage means 23; 29 is a common data update request means provided in the data management means 25, and 28 is a common data update means provided in the data management means 25; This process requests the node 10 to set common data for the entire system.

[Effect]

In the present invention, the processing node 10 includes the common data updating means 1
When updating the common data held by itself according to 8, the counter incrementing means 16 increments the count value of the local counter 11 of the self for each update, and the communication state determining means 14 When determining that the communication state is normal, processing is performed to notify the management node 20 of the updated common data and local counter value according to the common data update request means 19.

The management node 20 receiving this notification stores the common data sent in accordance with the common data updating means 2 in the common data storage means 23, and also stores the common data sent in accordance with the common data updating means 2
6, the count values of the local counter 21 and global counter 22 are incremented by the number of updates so that they become the sent local counter values. Then, according to the common data update requesting means 29, all the processing nodes 10 are notified of this common data and the global counter value together with the identification number of the processing node 10 that is the source of the update request. The processing node 10 that receives this notification,
When determining from the identification number that the response is a response to the update request issued by the user, the counter increment means 16 increments the global counter 12 by the number of updates so that the counted value of the global counter 12 becomes the sent global counter value. Process the digits,
When the identification number belongs to another processing node 10,
The common data sent according to the common data updating means 18 is stored in the common data storage means 13, and the count values of the local counter 11 and global counter 12 are changed according to the sent global counter value according to the counter increment means 16. Increment processing is performed for the number of updates so that

In this way, if the communication state between the processing node 10 and the management node 20 is normal, the same common data is stored in all the corresponding common data storage means 13.23, and the local counter 1121 and global counter 12.22 store the latest count value of the number of updates.

On the other hand, even if the communication state with the management node 20 is abnormal, the processing node 10 executes its own processing by updating the common data held by itself according to the common data updating means 18. At the same time, the counter advancing means 16
Accordingly, the count value of the local counter 11 provided therein is incremented every time it is updated. Then, when the communication state determining means 14 determines that the communication state has returned to normal,
According to the count value coincidence determination means 17, it is checked whether the count values of the local counter 11 provided therein and the local counter 21 provided in the management node 20 match.

When it is determined that there is no match in this process, the same common data is stored in all the common data storage means 13.23 by performing the same process as when the communication state with the management node 20 is normal. Also, all local counters 11.21 and global counters 12°22
The process is performed so that the count value of the counter is incremented with a difference value so that the count value becomes the newer count value.

As described above, according to the present invention, even if the management node 20 goes down, or even if an abnormality occurs in the line between the management node 20 and the processing node 10, the processing node 10 In this case, the common data can be updated, and when the normal state is restored, the updated common data can be immediately deployed to other processing nodes.

〔Example〕

Hereinafter, the present invention will be described in detail according to an embodiment applied to a building management system.

FIG. 2 shows a system configuration diagram of the present invention. The main control system 1 in FIG. mask data will be stored. Each terminal control device 3 is connected to a field device 8 such as a sensor, for example, via a plurality of terminal devices 7.
In addition to collecting the status data and notifying it to the main control system 1, automatic control of the field equipment 8 is executed according to the copy data of the mask data stored in the copy file 4. This main control system 1 corresponds to the management node 20 explained in FIG. 1, and the terminal control device 3 corresponds to the processing node 10 explained in FIG. Therefore, the main control system 1 and the terminal control device 3 each include a local counter and a global counter.

Note that 5 is a display device and 6 is a keyboard.

In this way, the building management system adopts a distributed data processing system in which the terminal control device 3 executes processes such as air conditioning control and disaster prevention management by using copy data as common data and executing each process. However,
Each terminal control device 3, in response to a request from an operator,
In order to reflect this individually updated copy data to other terminal control devices 3 and make it common, which will independently update its own copy data (for example, update seasonal range data, etc.) It is an object of the present invention to provide a method for the following.

Next, the communication status between the main control system 1 and the terminal control device 3 is determined according to the flowchart shown in FIG. 3 executed by each terminal control device 3 and the flowchart shown in FIG. 4 executed by the main control system 1. The processing contents when the condition is normal will be explained.

Each terminal control device 3 determines whether or not an update request for common data (copy data) has been received from the operator, as shown in step 30 of the flowchart in FIG. The terminal control device 3 that received the update request proceeds to step 31.
It updates its own common data according to instructions from the operator.

Then, in the following step 32, the local counter provided by itself is incremented by one. next,
In step 33, an abnormality flag that is set when the communication state between the main control system 1 and the terminal control device 3 is abnormal is checked.

When it is determined that the abnormality flag is set, communication with the main control system 1 cannot be executed, so the process is terminated and the process returns to step 30 to wait for the next common data update request from the operator. It turns out. In this way, even if the communication state between the main control system 1 and the terminal control device 3 is abnormal, the terminal control device 3 continues to execute predetermined processing by continuing to update the common data. Then, the count value of the local counter is counted up according to the number of updates.

On the other hand, if it is determined in step 33 that the abnormality flag is not set, the process proceeds to step 34, where the main control system requests the main control system to make its own updated common data the common data of the system. It turns out. At the time of this request, the count value of the local counter that has counted up by one is notified together with the updated common data. In response to this request processing, the main control system 1 sends new common data, a new global counter value, and the identification number of the terminal control device 3 that is the source of the update request, according to the processing shown in the flowchart of FIG. 4, which will be described later. will be sent back as an update request notification.

From now on, in step 35, the system waits for this update request notification to be sent back.

When the update request notification is sent back, in the next step 36, the counted value of the global counter provided by itself is changed to the sent global counter value (in this case, 1
The count is incremented so that it reaches the value that is being counted up, and the process ends. In the process of step 36, the count value of the global counter of the terminal control device 3 that is the source of the update request matches the count value of the local counter that has been incrementing in accordance with the update of the common data. Note that the common data sent back is the same as the common data held by itself, so it is not used.

On the other hand, if it is determined in step 30 that there is no update request for the common data from the operator, the process proceeds to step 37 and it is determined whether or not there is an update request notification from the main control system 1. If there is an update request notification in this judgment, the process proceeds to step 38. The existence of such an update request notification means that another terminal control device 3 has made an update request process for the updated common data to the main control system 1. In the update request notification from the main control system 1 in step 37, as explained in step 35, the new common data, the new global counter value, and the identification number of the terminal control device 3 that made the update request are notified. It will be done. Therefore, in step 38, the terminal control device 3 updates its own common data file so that it corresponds to the sent common data, and in the subsequent step 39, the terminal control device 3 updates the count values of its own local counter and global counter with the transmitted common data. The global counter value is counted up to reach the global counter value that has been set, and the process ends.

In the processing of steps 38 and 39, the common data of the terminal control device 3 that is not the update request source is matched with the common data of the terminal control device 3 that is the update request source, and the local counter of the terminal control device 3 that is not the update request source is adjusted. And the count value of the global counter will be adjusted to that of the terminal control device 3 that is the source of the update request.

Next, the flowchart shown in FIG. 4 will be explained. This flowchart represents the processing content executed by the main control system 1 that receives a common data update request from the terminal control device 3.

That is, when it is determined in step 40 that there is a common data update request from the terminal control device 3, the process proceeds to step 4.
In step 1, the common data (mask data) provided by the device is updated to match the sent common data, and in the subsequent step 42, the count values of the local counter and global counter provided by the device are updated to match the received global counter. Count up until the value is reached. Then, in the next step 43, all terminal control devices 3 are notified of the updated new common data, the new incremented global counter value, and the identification number of the terminal control device 3 that has requested the update. Then the process will end.

Through the process explained above, if the communication status between the terminal control device 3 and the main control system 1 is normal, the common data updated in any terminal control device 3 is shared between the main control system 1 and the other terminal control device 3. It will be sent to all terminal control devices 3 immediately. and,
All local and global counters in the system will be set to the same count value. Fifth
The figure diagrammatically shows the contents of the processing in the flowcharts of FIGS. 3 and 4 when the communication state is normal. Write the corresponding step number in the diagram.

Next, according to the flowchart shown in FIG. 6, which is executed by the terminal control device 3, a description will be given of the processing contents when the communication state between the main control system 1 and the terminal control device 3 is abnormal. This flowchart is, for example, 1
It is activated periodically at minute intervals to perform the processing described below.

When activated, each terminal control bag W3 first determines whether the communication status between the main control system 1 and the terminal control device 3 is normal and correct, as shown in step 60. If the communication state is abnormal in this judgment, the process proceeds to step 61, sets an abnormality flag, and ends the process.

The processing under this abnormal condition was explained in step 33 of the flowchart of FIG. On the other hand, if the communication state is normal, the process advances to step 62 and it is determined whether the abnormality flag is set. If the abnormality flag is not set in this judgment, the communication state is normal following the previous time, and the process ends immediately. The processing under this normal state is as explained in the flowchart of FIG. 3. On the other hand, in the judgment at step 62,
When it is determined that the abnormality flag is set, it indicates that the communication state has returned to normal from an abnormality.

In this case, the process proceeds to step 63, and the terminal control device 3 performs processing to read the count value of the local counter provided in the main control system 1. Then, in the subsequent step 64, a comparison is made between this count value and the count value of its own local counter.

If the count values of both local counters are equal in this judgment, it means that the common data of the system was not updated while the communication state was abnormal, so the process is immediately terminated. On the other hand, when the count value of the local counter of the terminal control device 3 is larger, the common data held by that terminal control device 3 has been updated more, so the process advances to step 65 and the common data held by the terminal control device 3 is updated. A request is processed to the main control system 1 to make the data common to the system. The request processing performed at this time is exactly the same as step 34 in the flowchart of FIG. Then, in subsequent steps 66 and 67, the common data held by the terminal control device 3 is added to the common data of the entire system by executing the same processing as steps 35 and 36 in the flowchart of FIG. , the count values of all counters are set to the count values of the local counters of that terminal control device 3. After this process, the abnormality flag is reset in step 68 and the process ends.

Conversely, when the count value of the local counter of the terminal control device 3 is smaller, the common data held by the main control system 1 is more updated, so the process proceeds to step 69 and the common data held by the main control system 1 is updated. A request process is made to the main control system 1 to make the data common data for the terminal control device 3. and,
In the following steps 70, 71, and 72, steps 37, 38, and 38 in the flowchart of FIG.
By executing the same process as step 39, the common data held by the main control system 1 is set as the common data of the terminal side '4Tj device 3, and the count values of the local counter and global counter of the terminal control device 3 are set. is set to the count value of the global counter of the main control system l. After this process, the process proceeds to step 68, where the abnormality flag is reset and the process ends.

When the communication state between the terminal control device 3 and the main control system 1 returns to normal from the abnormality through the processing explained above, the terminal control device 3 including the terminal control device 3 which was unable to communicate with the main control system 1 until then, Common data will be updated throughout the system. All local and global counters in the system will then be cented to the same count. FIG. 7 diagrammatically shows the contents of the process in the flowchart of FIG. 6 when the communication state returns to normal from an abnormality (this is the case where the local counter value of the terminal control device is larger). Write the corresponding step number in the diagram.

The present invention is configured to have two counters, a local counter and a global counter, as a pair. The reason why two counters are provided in this way is to cope with the connection of a large number of terminal control devices 3. Next, the reason for this will be explained in detail with reference to FIG. This eighth
In the figure, while the main control system 1 whose local counter value is "1" is down, the terminal control device 3 'A' updates the common data twice, and the terminal control device 3 'B' updates the common data. It is assumed that it has been updated three times.From now on, as shown in (a) in the figure, "A"'
The local counter value of "B" becomes "3", and the local counter value of "B" becomes "°4". All global counter values remain "1" because the main control system 1 is down. .

An abnormality in the main control system l is indicated by (a) in the diagram.
Assume that it has returned to normal. As a result, in response to the request from the terminal control device 3 of "A", the local counter value and global counter value of the main control system 1 are set to "°3" as shown in (b).Subsequently, In response to a request from the main control system 1, as shown in (c), the global counter values of the terminal control bags W3 of "A" and "B" are set to "3", and
Two local counter values of the terminal control device 3 of "B" are added and set to "6". Next, “
In response to the request from the terminal control device 3 of "B", the local counter value and global counter value of the main control system 1 are set to "6', as shown in (e). Then, in response to a request from the main control system l, as shown in (to), the terminals of "A" and "B"? The local counter value and global counter value of 2Il ``A gl 3'' are set to ``6'', and the process ends.

In this way, since two counters, a local counter and a global counter, are provided, the number of updates performed when the communication status is abnormal can be stored, and this makes it possible to handle two or more terminal control devices 3. It will become.

Next, in order to determine whether or not the common data has been updated when the communication status is abnormal, the main control system l The reason for using the local counter value will be explained with reference to FIG.

In this Figure 9, main control system 1 and
The terminal control device 3 named “A” updates the common data twice while the main control system l is down due to an abnormality in the line between it and the uncontrolled device 3 at the end of “B” and the local counter value is “1”. However, it is assumed that the terminal control device 3 named "B" does not update the common data.From now on, as shown in (a) in the figure, the local counter value of 'A' becomes '3'. , the local counter value of “B” is “
1”.

An abnormality in main control system 1 is indicated by (a) in the diagram.
Assume that it has returned to normal. As a result, the local counter value and global counter value of the main control system 1 are set to 3 as shown in (b) in response to the request from the terminal control device 3 at A. In response to requests from main control system 1, (
As shown in c), the global counter value of the terminal control device 3 of "A" is set to "3". At this time, the main control system 1 and the terminal control device 3 of "B"
Since the line between the
As shown in (d), it remains "1". As is clear from this example, if it is determined whether or not the common data has been updated when the communication state is abnormal, by comparing the local counter value and the global counter value of the terminal control device 3. In the terminal control device 3 of "B", since the local counter value and the global counter value match, it means that the common data updated by the terminal control device 3 of "A" cannot be taken in.

As described above, in the present invention, since the presence or absence of updating of common data is determined based on the difference between the local counter value of the main control system 1 and the local counter value of the terminal control device 3, the main control system 1 and the terminal control It is also possible to deal with abnormalities in the line between the device 3 and the device 3.

Although the illustrated embodiments have been described above, the present invention is not limited thereto. For example, the increment of the counter is not limited to the method of increasing it, but it is also possible to adopt a method of decreasing it from the initial value. Furthermore, the present invention is not limited in its application to building management systems, but can be applied to all distributed data processing systems.

〔Effect of the invention〕

As described above, according to the present invention, even if the main control system goes down or an abnormality occurs in the line between the main control system and the terminal control device, the terminal control device In addition to being able to update the common data, when the normal state returns, the updated common data can be immediately deployed to other terminal control devices, so that distributed data processing can be maintained even in abnormal situations. It becomes. Moreover, since the presence or absence of transfer of common data is determined by comparing the local counter values when returning to normal, there is no need for unnecessary data loading time as in the conventional case.

[Brief explanation of the drawing]

Figure 1 is a diagram of the principle of the present invention; Figure 2 is a system diagram of the present invention; Figure 3 is a flowchart executed by the terminal control device; Figure 4 is a flowchart executed by the main control system; Figure 5 is a flowchart executed by the main control system. FIG. 6 is a flowchart executed by the terminal control device; FIG. 7 is an explanatory diagram of the processing in the sixth flowchart; FIGS. 8 and 9 are 3 is a time chart of processing according to the present invention. In the figure, ■ is the main control system, 2 is the mask file, 3 is the terminal control device, 4 is the copy file, 5 is the display device, 6 is the keyboard, 7 is the terminal device, 8
10 is a field device, 10 is a processing node, 11 is a local counter, 12 is a global counter, 13 is a common data storage means, 14 is a communication state judgment means, 20 is a management node, 2
1 is a local counter, 22 is a global counter, 2
3 is a common data storage means.

Claims (1)

[Claims] Consisting of a plurality of processing nodes (10) and a management node (20) that manages them, these processing nodes (10) execute predetermined processing according to common data that is common to the entire system. At the same time, in a distributed data processing system that performs processing such that common data held by its own node is updated at any time, the processing node (10) and the management node (20) have a pair of local counters (11, 21). ) and global counters (12, 22), and when the processing node (10) updates common data held by itself, it updates its own local counter (11, 22).
) is incremented each time it is updated, and the above management node (
20), the updated common data is processed as common data for the entire system via the management node (20), and its own local counter (11) is processed. The processing node (10) increments the counts of all counters except for the number of updates, and the processing node (10)
20) returns to normal from the abnormality, it is checked whether the counted values of the local counter (11) of the management node (20) and the local counter (21) of the management node (20) match. , when there is no match,
Through the management node (20), the common data on the local counter (11, 21) side having a newer count value is processed as common data for the entire system, and all local counters (11, 21) and the global A common data management processing method characterized in that the count value of the counter (12, 22) is processed so that the count value of the counter is incremented by the difference value as much as possible to become the newer count value.