JP2001086133A - Cooperation management method in different kinds of systems and cooperation management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method and a system where system cooperation management is distributed so as to operate the system without giving effect of one fault onto the entire system and autonomous cooperation management corresponding to the quality of each system is attained in the case of functioning different kinds of systems through cooperation. SOLUTION: Grouped contents codes are assigned to the processing quality of the systems and contents codes are given to data sent/received for the processing over the systems and a repeater 100 interconnecting the systems manages the cooperation on the basis of the contents codes given to passing data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an autonomous decentralized system for performing content code communication, and more particularly to a cooperative management method and a cooperative management system for heterogeneous systems when systems of different qualities are connected and function in association. Things.

[0002]

2. Description of the Related Art In recent years, various types of systems have been required to cooperate in order to respond to diversification and changes in market and customer needs. For example, in the field of manufacturing, an integrated production system in which processes are linked in a factory has been realized. In recent years, this alone is not sufficient, and an integrated production and sales system that links production and sales is being realized. As a result, the end user needs can be quickly responded, and cost and quality are improved. Furthermore, with the globalization of companies, it is trying to realize flexible procurement of materials and production.

In order to realize such a manufacturing system, it is necessary to integrate a control system and an information system. However, the control system and the information system have completely different properties as described below.

In a control system, real-time performance, reliability and fault tolerance are strictly required. Since several bits of sensor-based data are required to be communicated and processed in the system in real time, a delay of more than a certain time renders useless. For this reason, the communication process is often repeatedly executed at a constant cycle. This is related to reliability, because even if data cannot be received, or data that is being processed is lost or destroyed, new data can be received and processed immediately after a certain period of time. Needless to say, even if a certain part becomes a permanent failure instead of such a transient failure, the system must continue to operate safely, and the demand for fault tolerance is strong. In addition, production methods and the like are routinely improved in order to improve efficiency and quality. However, since the downtime of equipment is short, online expandability and maintainability must be satisfied.

On the other hand, in an information system, a large amount of data (or a file) is sent, and processing is also performed in dialogue, simulation, recording, statistics, planning, etc., and the real-time property of a control system is not so severe. Since communication is performed when some kind of event occurs, the processing is often performed aperiodically. In some cases, the reliability of the data itself is strongly required, but it is possible to proceed while confirming whether communication and processing have been executed normally. Due to changes in business and production methods, the processing content of the information system may change or expand. However, this is rarely a situation that must be performed while the system is running.

[0006] There is a need to function those constructed as separate application systems by linking them together. However, in this way, the departments that build and use each application system are different,
Each application has different missions. Even if it is assumed that application systems having such heterogeneous properties are integrated from the beginning, it is not efficient to construct the entire system with the same level of index. In a situation where environmental changes are severe and you need to decide in advance what services and operations will be required,
There is a need for a technology that can build a closely related application as one system, and can flexibly connect, relate, and integrate with other types of heterogeneous systems.

In the prior art, for example, Japanese Patent Application Laid-Open
As described in Japanese Patent No. 9306, when processes are related to each other across two or more systems, a system for centrally monitoring those systems is provided, and this system manages the process progress of the entire system. As for the monitoring method, only uniform monitoring was possible even if the monitoring system was different.

Further, when processes are related to each other across two or more systems, as described in Japanese Patent Application Laid-Open No. Hei 10-143480, data exchange between these different systems and coordination of processes are performed by connecting the systems. A technique is known in which data having a content code registered in the relay device among the data in the data fields of the respective systems is simply passed through each other via the relay device.

[0009]

In the conventional centralized management system, the centralized management system had to know in advance all the relationships between the systems to be managed. In addition, due to an abnormality in the centralized management system, all systems had to perform erroneous processing or stop processing.

Further, in the prior art, the cooperative management between the systems can be performed only by a uniform method. Therefore, when there are different types of systems, the quality of each system is different, but the quality of each system is different. However, there is a problem that management processing and management information become redundant or insufficient depending on the system.

[0011] An object of the present invention is to disperse the cooperative management of systems when heterogeneous systems are made to function in cooperation with each other so that operation can be performed so that a single failure does not affect the entire system. An object of the present invention is to provide a cooperation management method and a cooperation management system that enable autonomous cooperation management corresponding to the quality of each system.

[0012]

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method for connecting between heterogeneous systems by assigning a content code for identifying the quality of processing to data passing between systems when performing processing between systems. This is achieved by means for a relay device that manages the processing for each content code assigned to the passing data or executes the processing for the passing data to which the code is assigned.

[0013] By the above means, the management of system cooperation is distributed and operation without spreading to the entire system due to a single failure is enabled, and the cooperation management of heterogeneous systems is performed in a method corresponding to the quality of each system. Can be performed autonomously.

[0014]

Embodiments of the present invention will be described below with reference to the drawings. Note that the following embodiments are merely examples embodying the present invention, and do not limit the technical scope of the present invention.

FIG. 2 shows a configuration diagram of an embodiment of the present invention. This embodiment is an example of an autonomous decentralized system that performs content code communication via a data field in data transfer between computers and processes in an information control system.

The configuration of the present embodiment comprises systems S1, S
2 and S3. In these systems, a plurality of computers (nodes 11 to 13, 21 to 22, 31...) Are connected via a network, and each computer communicates with content code using a packet format shown in FIG. The system has data fields (hereinafter, referred to as DFs) 400, 500, and 600 in which content code data flows in each system. Connect one DF to another DF
The relay system 100, 200, and 300 that perform data transfer to and the cooperative management of processing are provided to constitute a system.

FIG. 1 shows the configuration of a relay device for connecting DFs. The relay device connects to a plurality of DFs, takes in content code data from each DF, and relays the content code data to another DF. In the present embodiment, the relay device 100 is a DFA and a DFB
The case where the DF is connected to the two DFs will be described.

The relay devices 100, 200, and 300 are provided with a management table 140 in which processing contents of content code data passing through the relay device are registered in advance, and the management table 14
Only data that matches the content code registered in DF
A, a DFA-side relay data receiving unit 111 to be fetched from A, a relay data management unit 130 for processing the content code data fetched according to the registration in the management table 140, and a content code data
B, and the DFB-side relay data receiving unit 1 that takes in only the data that matches the content code registered in the management table from the DFB.
21; a DFA-side relay data transmission unit 11 for sending the content code data to the DFA by the relay data management unit 130
2 The relay data management unit 130 includes a relay data monitoring unit 131 that monitors the content code captured according to the registration in the management table 140, and a data relay control unit that relays the content code data captured according to the registration in the management table 140. 132, a relay data error check unit 13 for checking the error of the content code data fetched in accordance with the registration in the management table 140
3

The following is a description of each of the above-mentioned systems and the concrete cooperation between the systems. In FIG. 2, S1
Is a travel reservation system which performs a travel reservation process for reserving a restaurant at an airplane, a hotel, or a destination. S2 is a bank system for performing a withdrawal process. In step S3, the restaurant service system performs a restaurant reservation process. As described above, S1, S2, and S3 are constructed as separate systems, and function with enhanced effects by cooperation.

These systems perform cooperative processing as follows. The bank system S2 receives a request from the travel reservation system S1 for withdrawal of the travel price and performs a withdrawal process. Although the travel reservation system S1 accepts a restaurant reservation at the destination, the actual reservation processing is requested to the restaurant service system S3. The restaurant service system S3 receives a request for restaurant reservation at a travel destination from the travel reservation system S1, and performs restaurant reservation processing.

Here, in order to terminate the travel reservation processing of the travel reservation system S1, the debit processing in the bank system S2 must be completed, and in order to terminate the debit processing in the bank system S2. ,
The travel reservation processing in the travel reservation system S1 must also end. When the travel reservation processing in the travel reservation system S1 ends, the restaurant reservation processing in the restaurant service system S3 proceeds. However, even if the restaurant reservation processing in the restaurant service system S3 does not end, the travel reservation system S1 does not. It is assumed that the travel reservation process can be completed.

A travel reservation system S1 and a bank system S
2, and DF of restaurant service system S3 (data
field) is DF1 (400) and DF2 (50
0), DF3 (600). There is a relay device between the DFs. That is, DF1 (400) and DF2 (500)
Between the relay device 12 (100), DF1 (400) and D
During F3 (600), the relay device 13 (200), DF2
(500) and the relay device 23 (3)
00). At this time, the relay device relays the data flowing on each DF based on the content code, monitors the process based on the content code related to the progress of the process flowing on each DF, and connects as necessary. The content code data for controlling the cooperation between the performed systems is transmitted. Content codes generated and relayed on each DF are shown in FIGS. FIG. 7 shows the content codes generated by the relay device.

1. 8, 9, 10, 11, 12, 13, and 1 illustrate the cooperative operation of S 1, S 2, and S 3 in a normal state.
This will be described with reference to FIGS.

(1) In the travel reservation system S1, FIG.
A travel reservation is generated and a reservation start instruction is issued according to the flowchart of FIG.
Proceed to. In step 1402, the data of the content code 1010 of the start of the travel reservation process is transmitted to the DF1 (400). Airplane reservation in step 1403, step 140
At 4, the hotel is reserved. In step 1405, to request the restaurant service S3 to make a restaurant reservation, the restaurant reservation information data is attached to the content code 1330 of the restaurant reservation request and transmitted to the DF1. In step 1406, in order to request the bank system S2 to withdraw the money, the money information information 1220 is attached to the money withdrawal information data and transmitted to the DF1. Steps 1402 to 1406 proceed to step 1407 if all of them can be processed normally in parallel processing. Step 140
7, the content code 101 of the temporary termination of the travel reservation processing indicating that a series of processing by the travel reservation system alone has been completed.
1 is transmitted to DF1. At step 1408,
Wait for the provisional termination of the debit processing that needs to be synchronized.

(2) On the other hand, in the relay device 12 (100), the contents shown in FIG. It is assumed that DFA is DF1 and DFB is DF2. The data of the content codes 1010 and 1020 are transmitted to the DF1 in the order of the steps 1401 and 1402.

The operation of the relay device 12 (100) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, DFA
Among the content code data transmitted to DF1 in the relay data receiving unit 111, the relay content code of DF1 registered in the management table 140 (FIG. 8)
First, 1010 is taken. Since the content code 1010 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. Since the content code 1010 fetched in step 1203 does not need to be monitored in the management table 140 (FIG. 8), the process proceeds to step 1204. Since the content code 1010 fetched in step 1204 is not monitored in the management table 140 (FIG. 8), the process proceeds to step 1205. Since the content code 1010 fetched in step 1205 is to be relayed to DF2 in the management table 140 (FIG. 8), the data relay unit 132
0 data from the DFB side relay data transmission unit 122 to DF2
Relay transmission.

Next, the relay device 12 (100)
In 201, DFA side relay data receiving section 111
Of the content code data transmitted to F1, 1020 of the relay content code of DF1 registered in the management table 140 (FIG. 8) is fetched. The content code 1020 fetched in step 1202 is stored in the management table 140
Since the error check is necessary in (FIG. 8), the process proceeds to step 1206. In step 1206, the relay data error check unit 133 checks the data of the content withdrawal information of the content code 1020 for errors. In step 1211, since there is no data error, the process proceeds to step 1203. Content code 102 captured in step 1203
0 indicates that processing monitoring is required in the management table 140 (FIG. 8), and the process proceeds to step 1207. Step 1207
Then, the relay data monitoring unit 131 creates the monitoring table No. 1 in FIG. 10 according to the management table 140 (FIG. 8), starts a monitoring timer, and starts monitoring the processing. Since the content code 1020 fetched in step 1204 is not monitored in the management table 140 (FIG. 8), the process proceeds to step 1205. The content code 1020 fetched in step 1205 is stored in the management table 140 (FIG. 8) in the DF.
2 is to be relayed to the data relay unit 13
2 relays the content code 1020 data from the DFB-side relay data transmission unit 122 to DF2.

(3) The relay device 12 (10
0) are transmitted in the order of 1010 and 1020.

The processing in the bank system S2 will be described with reference to the flowchart of FIG.

When the data of the content code 1020 in the DF2 is found, YES is determined in step 1501 and step 1
Go to 502. In step 1502, the content code 1220 of the start of the payment withdrawal process is transmitted to the DF2 (500). In step 1503, a travel fee withdrawal process is performed based on the fee withdrawal information in the data section. Step 1
In 504, the data of the content code 1221 of the temporary termination of the travel charge withdrawal process indicating that the series of processes in the bank system S2 alone has been completed is transmitted to the DF2. In step 1505, the process waits for the provisional end of the travel reservation process that needs to be synchronized.

(4) On the other hand, in the relay apparatus 13 (200), the contents shown in FIG. It is assumed that DFA is DF1 and DFB is DF3. The data of the content codes 1010 and 1030 are transmitted to DF1 in the order of steps 1401 and 1402.

The operation of the relay device 13 (200) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, DFA
Among the content code data transmitted to DF1 in the relay data receiving unit 111, the relay content code of DF1 registered in the management table 140 (FIG. 9)
First, 1010 is taken. Since the content code 1010 fetched in step 1202 does not require an error check in the management table 140 (FIG. 9), the process proceeds to step 1203. Since the content code 1010 fetched in step 1203 does not need to be monitored in the management table 140 (FIG. 9), the process proceeds to step 1204. Since the content code 1010 fetched in step 1204 is not monitored in the management table 140 (FIG. 9), the process proceeds to step 1205. Since the content code 1010 fetched in step 1205 is to be relayed to DF3 in the management table 140 (FIG. 9), the data relay unit 132
0 data from the DFB side relay data transmission unit 122 to DF3
Relay transmission.

Next, the relay device 13 (200)
In 201, DFA side relay data receiving section 111
Fetch 1030 of the relay content code of DF1 registered in the management table 140 (FIG. 9) among the content code data transmitted to F1. The content code 1030 fetched in step 1202 is stored in the management table 140
Since the error check is unnecessary in FIG. 9 (step 1203)
Proceed to. Content code 10 fetched in step 1203
The process 30 advances to step 1207 because the process monitoring is necessary in the management table 140 (FIG. 9). Step 120
7, in the relay data monitoring unit 131, the management table 140
According to (FIG. 9), the monitoring table shown in No. 1 of FIG. 11 is created, the monitoring timer is started, and the monitoring of the process is started. Since the content code 1030 fetched in step 1204 is not monitored in the management table 140 (FIG. 9), the process proceeds to step 1205. Since the content code 1030 captured in step 1205 is to be relayed to DF3 in the management table 140 (FIG. 9), the data relay unit 132 relays this content code 1030 data from the DFB-side relay data transmission unit 122 to DF3. Send.

(5) The relay device 13 (20
The content codes relayed in (0) are transmitted in the order of 1010 and 1030.

The processing in the restaurant service system S3 will be described with reference to the flowchart of FIG. If the data of the content code 1030 is found in the DF3,
It becomes ES and proceeds to step 1602. Step 1602
Then, the content code 1330 of the restaurant reservation process start is D
Transmit to F3 (600). In step 1603, restaurant reservation processing is performed based on the restaurant reservation information in the data section. In step 1604, the data of the content code 1331 of the temporary termination of the restaurant reservation process indicating that the series of processes in the restaurant service system S3 alone has been completed is transmitted to the DF3. In step 1605, the process waits for the provisional termination of the travel reservation process that needs to be synchronized.

(6) Here, the DF2 has the above-mentioned step 1
At 502, the data of the content code 1220 is transmitted.

The operation of the relay device 12 (100) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, the DFB
Of the content code data transmitted to DF2 in the side relay data receiving unit 121, the relay content code of DF2 registered in the management table 140 (FIG. 8)
First, 1220 is taken. Since the content code 1220 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. Since the processing of the content code 1220 fetched in step 1203 is required in the management table 140 (FIG. 8), the process proceeds to step 1207. In step 1207, the relay data monitoring unit 131 sets the No. in FIG. 10 according to the management table 140 (FIG. 8). Create additional monitoring table shown in 2
Start the monitoring timer and start monitoring the process. Step 12
04 is stored in the management table 1
Since it is not a monitoring target at 40 (FIG. 8), the process proceeds to step 1205. Since the content code 1220 captured in step 1205 is to be relayed to DF1 in the management table 140 (FIG. 8), the data relay unit 132 relays this content code 1220 data from the DFA-side relay data transmission unit 112 to DF1. Send.

(7) Here, the DF3 has the above-mentioned step 1
At 602, the data of the content code 1330 is transmitted.

The operation of the relay device 13 (200) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, the DFB
Of the content code data transmitted to DF3 in the side relay data receiving unit 121, of the relay content codes of DF3 registered in the management table 140 (FIG. 9),
First, 1330 is taken. Since the content code 1330 fetched in step 1202 does not require an error check in the management table 140 (FIG. 9), the process proceeds to step 1203. Since the content code 1330 fetched in step 1203 needs to be monitored in the management table 140 (FIG. 9), the process proceeds to step 1207. In step 1207, the relay data monitoring unit 131 according to the management table 140 (FIG. 9) performs No. Create additional monitoring table shown in 1
Start the monitoring timer and start monitoring the process. Step 12
04 is the content table 1330
Since it is not a monitoring target at 40 (FIG. 9), the process proceeds to step 1205. Since the content code 1330 fetched in step 1205 is to be relayed to DF1 in the management table 140 (FIG. 9), the data relay unit 132 relays this content code 1330 data from the DFA-side relay data transmission unit 112 to DF1. Send.

(8) At this timing, the data of the content code 1011 is transmitted to the DF1 in the step 1407, and the data of the content code 1221 is transmitted to the DF2 in the step 1504.

The operation of the relay device 12 (100) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, DFA
Among the content code data transmitted to DF1 in the relay data receiving unit 111, the relay content code of DF1 registered in the management table 140 (FIG. 8)
First, 1011 is taken. Since the content code 1011 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. The content code 1011 fetched in step 1203 does not need to be monitored in the management table 140 (FIG. 8). Since the content code 1011 captured in step 1204 is a monitoring target in the management table 140 (FIG. 8), the process proceeds to step 1208. In step 1208, the relay data monitoring unit 131
No. of the monitoring table in FIG. 1, No. The flag for detecting the DF2 content code 1011 of No. 2 is set. In step 1209, the monitoring table No. in FIG. 1, No.
Since the monitoring content code detection flag has not yet been set in step 2, this content code data is not relayed but is buffered in the relay data monitoring unit 131, and the processing of this content code ends.

Next, the relay device 12 (100)
In 201, DFB side relay data receiving section 121
Of the content code data transmitted to F2, 1221 of the relay content code of DF2 registered in the management table 140 (FIG. 8) is fetched. Since the content code 1221 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. Content code 1221 fetched in step 1203
Since the process monitoring is unnecessary in the management table 140 (FIG. 8), the process proceeds to step 1204. Step 1204
Then, the fetched content code 1221 is stored in the management table 14
0 (FIG. 8), which is a monitoring target, and therefore, step 12
Proceed to 08. In step 1208, the relay data monitoring unit 131 sets the monitoring table No. in FIG. 1, No. 2D
The F2 content code 1221 detection flag is set. In step 1209, the monitoring table No. in FIG. 1,
No. Since all the monitoring content code detection flags have been set in step 2, the corresponding monitoring timer is released, and step 121 is executed.
Go to 0. In step 1210, the relay data monitoring unit 1
No. 31 in which the monitoring content code detection flags are all set in the management table 140 (FIG. 8) in No. 31 of FIG. 1 and No.
2 is relayed to the relay destination DF registered in the management table 140 (FIG. 8). That is, the data of the content code 1011 buffered in the step 1209 is transferred from the DFB side relay data transmitting unit 122 to the DF2,
The data of the content code 1221 is relay-transmitted from the DFA-side relay data transmission unit 112 to DF1.

(9) At this timing, the data of the content code 1011 is transmitted to the DF1 in the step 1407, and the data of the content code 1331 is transmitted to the DF3 in the step 1604.

The operation of the relay device 13 (200) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, DFA
Among the content code data transmitted to DF1 in the relay data receiving unit 111, the relay content code of DF1 registered in the management table 140 (FIG. 9)
First, 1011 is taken. Since the content code 1011 fetched in step 1202 does not require an error check in the management table 140 (FIG. 9), the process proceeds to step 1203. The content code 1011 fetched in step 1203 does not need to be monitored in the management table 140 (FIG. 9). Since the content code 1011 fetched in step 1204 is monitored in the management table 140 (FIG. 9), the process proceeds to step 1208. In step 1208, the relay data monitoring unit 131 sets the monitoring table No. DF3 content code of 1 10
11 Set the detection flag. In step 1209, the monitoring table No. in FIG. Since all the monitoring content code detection flags have been set in 1, the corresponding monitoring timer is released, and the process proceeds to step 1210. Step 1210
Then, the relay data monitoring unit 131 uses the management table 140
When all the monitoring content code detection flags are set in FIG. 1 monitoring content code in management table 1
It relays to the relay destination DF registered in 40 (FIG. 9).
That is, the data of the content code 1011 is relay-transmitted from the DFB-side relay data transmission unit 122 to DF3.

Next, since the relay content code 1331 of the DF3 is not registered in the management table 140 (FIG. 9) of the relay device 13 (200), it is not taken into the relay device 13 (200) and is not relayed.

(10) At this timing, the content code 1221 relayed by the relay device 12 (100) is stored in the DF1.
Is transmitted, and the content code 1331 relayed by the relay device 13 (200) is transmitted. In step 1408 of the travel reservation system S1, the DF1 waits for only the data of the content code 1221 of the provisional end of the payment withdrawal process, and since this was detected, the process proceeds to step 1409. In step 1409, the process ends normally in synchronization with the withdrawal processing of the bank system S2, so that the process ends normally.

The relay device 12 (100) is provided in the DF2.
Has been transmitted. In step 1505 of the bank system S2, the data of the content code 1011 of the temporary termination of the travel reservation process is detected by the DF2, and the process proceeds to step 1506. In step 1506, the process ends normally with synchronization with the travel reservation process of the travel reservation system S1.

The relay device 13 (200) is provided in the DF3.
Has been transmitted. In step 1605 of the restaurant service system S3, the content code 101 of the provisional end of the travel reservation processing in DF3
Then, the process proceeds to step 1606. In step 1606, the process ends normally in synchronization with the travel reservation process of the travel reservation system S1, so that the process ends normally.

The above is an explanation of the coordination processing of S1 and S2 when the operation is normal.

2. Here, the cooperative operation of S1, S2, and S3 at the time of abnormality is an example in the case where an abnormality occurs after the start of the withdrawal processing in the bank system S2 and the bank system goes down, and FIG. 8, FIG. 9, FIG. This will be described with reference to FIGS. 12, 13, 14, 15, and 16.

The operations (1) and (2) are the same as those in the normal state.

(3) The relay device 12 (10
0) are transmitted in the order of 1010 and 1020.

The processing in the bank system S2 will be described with reference to the flowchart of FIG. If the data of the content code 1020 is found by the DF2, YES is determined in the step 1501 and the process proceeds to the step 1502. In step 1502, the content code 1220 of the start of the payment withdrawal processing is set to DF2 (500).
Send to In step 1503, the travel charge withdrawal processing is started based on the charge information in the data section. However, the bank system S2 goes down and stops at this step, and the content code of the temporary termination of the travel charge withdrawal processing is not transmitted to the DF2. Let it be.

The operations (4) and (5) are the same as those in the normal state.

(6) Here, the DF2 has the above-mentioned step 1
At 502, the data of the content code 1220 is transmitted.

The operation of the relay device 12 (100) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, the DFB
Of the content code data transmitted to DF2 in the side relay data receiving unit 121, the relay content code of DF2 registered in the management table 140 (FIG. 8)
First, 1220 is taken. Since the content code 1220 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. Since the processing of the content code 1220 fetched in step 1203 is required in the management table 140 (FIG. 8), the process proceeds to step 1207. In step 1207, the relay data monitoring unit 131 sets the No. in FIG. 10 according to the management table 140 (FIG. 8). Create additional monitoring table shown in 2
Start the monitoring timer and start monitoring the process. Step 12
04 is stored in the management table 1
Since it is not a monitoring target at 40 (FIG. 8), the process proceeds to step 1205. Since the content code 1220 captured in step 1205 is to be relayed to DF1 in the management table 140 (FIG. 8), the data relay unit 132 relays this content code 1220 data from the DFA-side relay data transmission unit 112 to DF1. Send.

The operation (7) is the same as the normal operation.

(8) At this timing, only the data of the content code 1011 has been transmitted to the DF1 in step 1407.

The operation of the relay device 12 (100) is shown in FIG.
This will be described with reference to the flowchart of FIG. In step 1201, DFA
Among the content code data transmitted to DF1 in the relay data receiving unit 111, the relay content code of DF1 registered in the management table 140 (FIG. 8)
First, 1011 is taken. Since the content code 1011 fetched in step 1202 does not require an error check in the management table 140 (FIG. 8), the process proceeds to step 1203. The content code 1011 fetched in step 1203 does not need to be monitored in the management table 140 (FIG. 8). Since the content code 1011 captured in step 1204 is a monitoring target in the management table 140 (FIG. 8), the process proceeds to step 1207. In step 1208, the relay data monitoring unit 131
No. of the monitoring table in FIG. 1, No. A flag for detecting the DF2 content code 1221 is set. In step 1209, the monitoring table No. in FIG. 1, No.
Since the monitoring content code detection flag has not yet been set in step 2, this content code data is not relayed but is buffered in the relay data monitoring unit 131, and the processing of this content code ends.

Here, since the data of the content code 1221 is not transmitted to the DF2 because the bank system S2 has gone down, the detection flag of the monitoring content code 1221 of the DF2 in the monitoring table of the relay device 12 (100) is changed. It is not set and the watch timer remains running. Accordingly, in step 1301, the monitoring table of the relay data monitoring unit 131 is no. 1, No. The value of the monitoring timer corresponding to 2 becomes longer than the set monitoring time, and the process proceeds to step 1302. In step 1302, the monitoring table shown in FIG. 1, No. Since 1221 is not detected among the monitoring target content codes of No. 2, the process proceeds to step 1303. In step 1303, the relay data monitoring unit 131
In the monitoring table in FIG. 1, No. Inform the generated DF of the content code for which the monitoring of step 2 has been requested to notify the processing abnormality. No. 1, the relay data monitoring unit 1
At 31, the monitoring content codes 1221 and 1011 are stored in the data portion, a packet with a content code 9999 indicating a processing error is created, and the packet is transmitted to the DF 1 via the DFA-side relay data transmission unit 112. No. With regard to 2, for the relay data monitoring unit 131, the monitoring content codes 1221 and 1011 are stored in the data part, and the content code 9999 indicating a processing error is stored.
Is created and transmitted to the DF2 via the DFB-side relay data transmission unit 122.

(9) Here, DF1 includes the relay device 12
The content code 9999 has been transmitted from (100).
In step 1408 of the travel reservation system S1, DF1
Since the data of the content code 1221 of the provisional termination of the charge withdrawal process cannot be detected, the process proceeds to 1410. Step 1
At 410, the content code 9999 indicating the processing abnormality report is detected, and the content code 122
Since it is known that 1 has been stored, there is an abnormality in the withdrawal processing, and the process proceeds to step 1411. At step 1411, since the money could not be debited, at step 1405 the restaurant service system S3
Code 998 to cancel the restaurant reservation requested to
9 to the DF1, cancels the reservation processing performed in 1403 and 1404, and returns to step 11401 in the initial state.

(10) The relay device 13 (200) relays the content code 9989 transmitted to the DF1 to the DF3 according to the registration in the management table, and the content code 99 relayed in step 1609 of the restaurant service system S3.
If 89 is detected, the process proceeds to step 1608 to cancel the restaurant reservation already processed, and returns to the initial state.

The above is a description of the cooperative processing of S1, S2, and S3 when an abnormality occurs.

3. A case where a failure has occurred in any one of the relay devices will be described.

For example, in the present embodiment, the relay device 12 (10
Even when the operation cannot be performed due to a failure in 0), the processing can be performed as usual if the cooperation processing is performed only between the travel reservation system S1 and the restaurant service system S3.

4. In this embodiment, a method of changing the handling according to the quality of the system will be described. In this embodiment, since the bank system S2 requires higher data reliability than other systems, data relayed from another system to the bank system S2 is required. Performs a reliability check. The operation will be described.

Since the travel reservation system S1 sends data to the banking system S2 in this embodiment, the management table 140 in the relay device 12 (100) stores the debit information as shown in FIG.
Only when the content code 1020 is sent is registered as an error check required.

(1) and (2) correspond to 1. S1, S at normal time
This is the same as the cooperative operation of S2 and S3.

(3) The relay device 12 (100) executes step 12 only when this content code 1020 is fetched.
02 is the management table 1
Since the error check is necessary at 40 (FIG. 8), the process proceeds to step 1206. In step 1206, the relay data error check unit 133 checks the data of the content withdrawal information of the content code 1020 for errors. If there is a data error in step 1211, step 1212
The process proceeds to step 1203 if there is no data error. In step 1212, without relaying the erroneous content code data, the content code and the data are stored in the data portion, a content code 9989 of the data error / discard report is attached, and the DF1 in which the erroneous data is captured is added. DFA
The data is transmitted from the side relay data transmission unit 112, and the process is terminated without relaying the data.

(4) If there is an error in the content code 1020, the content code 9989 of the data error / discard report is transmitted to the DF1 in step 1212 described above. In the travel reservation system S, the content code 9989 of the data error / discard report is detected in step 1412, and since the stored content of the data portion indicates that the information is the debit information transmitted earlier, the content code 1020 is added to the information. And sends it to DF1 again.

(5) In the relay device 12 (100), the DF
(1) The data of the resent content code 1020 is taken in according to the management table 140 and a series of processing is performed.

In this way, only data relay to a system requiring reliability can be strictly handled.

4. In the above-described embodiment, all processes in the relay device for each content code are registered in the relay device in advance, but only the content code that the relay device takes in for relaying is registered in the relay device. The processing in the apparatus can be stored in the data portion of the content code data and transmitted, and the relay apparatus can read out the processing information stored in the fetched data and perform the processing.

5. Also, instead of registering the processing in the relay device in the management table, a processing program for each content code to be relayed to the relay device is registered. It is also possible to activate the processing program registered in the.

[0075]

According to the present invention, the following effects can be obtained.

(1) The coordination of the processing across different systems can be achieved, and there is an effect that fault tolerance can be achieved.

(2) Even when systems of different qualities cooperate, there is an effect that consistency between the systems can be obtained without each system consciously adjusting to the quality of other systems.

(3) Each system has the effect that the processing can proceed without knowing the association with other systems.

(4) Since the processing management can be distributed, there is an effect of suppressing the influence of a failure that has occurred in a certain place on the whole.

[Brief description of the drawings]

FIG. 1 is a diagram showing main components of an embodiment of the present invention.

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

FIG. 3 is a diagram showing a packet format of content code communication.

FIG. 4 is a diagram showing a content code generated in DF1.

FIG. 5 is a diagram showing a content code generated in DF2.

FIG. 6 is a diagram showing a content code generated in DF3.

FIG. 7 is a diagram showing a content code generated in the relay device.

FIG. 8 is a diagram showing the contents of a management table in the relay device 12.

FIG. 9 is a diagram showing the contents of a management table in the relay device 13.

FIG. 10 is a diagram showing the contents of a monitoring table in the relay device 12.

FIG. 11 is a diagram showing the contents of a monitoring table in the relay device 13;

FIG. 12 is a flowchart showing main processing in the relay device.

FIG. 13 is a flowchart showing timer monitoring processing in the relay device.

FIG. 14 is a flowchart showing processing in the travel reservation system S1.

FIG. 15 is a flowchart showing processing in the bank system S2.

FIG. 16 is a flowchart showing processing in the restaurant service system S3.

[Explanation of symbols]

100: Relay device 12, 111: DFA-side relay data receiving unit, 112: DFA-side relay data transmitting unit, 121: D
FB-side relay data receiving unit, 122: DFB-side relay data transmitting unit, 130: relay data management unit, 131: relay data monitoring unit, 132: data relay control unit, 133: relay data error check unit, 140: management table, 200 ...
Relay devices 13, 300: Relay devices 23, 400: DF
1, 411... Nodes 11, 412... Nodes 12, 413
… Node 13, 500 DF2, 511… node 21,
512 ... node 22, 600 ... DF3, 611 ... node 31.

Continued on the front page (72) Inventor Yoshiaki Adachi 5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture Inside the Omika Plant, Hitachi, Ltd. (72) Inventor Hideki Tooka 5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture Inside Hitachi, Ltd. Omika Plant (72) Inventor Tomoaki Nakamura 5-2-1, Omikacho, Hitachi City, Ibaraki Prefecture Inside Hitachi, Ltd. Omika Plant (72) Inventor Kinji Mori 2-oka Ookayama, Meguro-ku, Tokyo 12-1 F-term in Tokyo Institute of Technology 5B049 AA00 AA01 CC06 CC36 EE51 5B089 GB02 JB24 KA12 KC15 KC47 MC08 5K033 AA05 AA09 CC01 DB18

Claims (9)

[Claims] 1. A method for managing different types of systems in which systems having different qualities are connected to function in cooperation with each other are assigned content codes grouped according to the quality of processing performed by the systems, and transmitted / received for processing across systems. A method for cooperative management in a heterogeneous system, wherein the content code is added to data, and a relay device connecting the systems manages the content code based on the content code added to the passing data. 2. A system for managing different types of systems in which systems of different qualities are connected to function in cooperation with each other, wherein content codes grouped according to the quality of processing by the systems are assigned and transferred for processing across systems. A relay table that connects the content codes to the data, and a relay device that connects the systems includes a management table that registers processing contents for each of the content codes added to the passage data, and performs processing of the passage data in accordance with the registration of the management table A cooperative management method in a heterogeneous system, characterized in that: 3. A method for managing a heterogeneous system in which systems of different qualities are connected to function in cooperation with each other, wherein content codes grouped according to the qualities of processing by the systems are assigned and transferred for processing across systems. A management table for assigning the content code to data, and a relay device connecting the systems to register a program for performing a process for each of the content codes assigned to the passing data, wherein the content code assigned to the passing data is provided. A cooperation management method in a heterogeneous system, characterized in that the registration program is activated at the time of importing to process the passing data. 4. In a cooperative management method of heterogeneous systems in which systems of different qualities are connected and function in cooperation with each other, content codes grouped according to the quality of processing by the systems are assigned and transferred for processing across systems. Attach the content code and the processing information in the relay device to the data,
A link management method in a heterogeneous system, characterized in that a relay device connecting the systems performs processing based on the processing information added to the passing data. 5. In a cooperative management system of heterogeneous systems in which systems of different qualities are connected and function in cooperation with each other, a plurality of computers are connected via a network, and each computer functions while exchanging data by content code communication. System, and a data field that is a flow field of the content code data possessed by each system, and a connection between the plurality of data fields, and a transfer of data from one data field to another data field and coordination of processing. A cooperation management system in a heterogeneous system, comprising a relay device for performing management. 6. The relay device fetches, from one data field DFA, a management table in which processing contents of passing content code data are registered in advance, and only data that matches the content code registered in the management table. DF
An A-side relay data receiving unit, a relay data management unit for processing the content code data taken in accordance with the registration in the management table, and a DF for sending the content code data to the other data field DFB by the relay data management unit
B-side relay data transmission unit, DFB-side relay data reception unit that takes in only data that matches the content code registered in the management table from the DFB, and DFA that sends content code data to the DFA by the relay data management unit 6. The cooperation management system in a heterogeneous system according to claim 5, further comprising a side relay data transmission unit. 7. The relay data management unit monitors a content code data fetched according to the registration of the management table, and a data relay control that relays the content code data fetched according to the registration of the management table. 7. A relay data error checking unit for performing an error check on content code data fetched in accordance with registration in the management table.
The cooperation management system in the heterogeneous system described in the above. 8. The relay device fetches, from one data field DFA, a management table for registering at least the content code of the passing content code data, and only data that matches the content code registered in the management table. A relay data receiving unit on the DFA side, a relay data management unit for processing the content code data fetched according to the processing information stored in the content code data, and a content code data stored in the other data field DFB by the relay data management unit A DFB-side relay data transmitting unit to send out,
A relay data receiving unit for receiving only data matching the content code registered in the management table from the DFB; and a relay data transmitting unit for transmitting the content code data to the DFA by the relay data management unit. 6. The cooperation management system in a heterogeneous system according to claim 5, wherein 9. The relay device fetches, from one data field DFA, a management table in which a processing program for passing content code data is registered in advance, and only data matching the content code registered in the management table. A DFA-side relay data receiving unit, a relay data management unit that processes the content code data fetched in accordance with the registration program in the management table, and a content code data that is transferred to the other data field DF by the relay data management unit.
B; a DFB-side relay data transmitting unit that sends out the data to the B; a DFB-side relay data receiving unit that fetches only data matching the content code registered in the management table from the DFB;
6. A cooperative management system in a heterogeneous system according to claim 5, further comprising: a DFA-side relay data transmission unit that sends content code data to the DFA by the relay data management unit.