Communication message data collation apparatus

Abstract

To provide a communication message data collation apparatus which collates received communication message data to a list without requiring any manpower.SOLUTION: A communication message data collation apparatus according to an embodiment of the present invention has an address database and a configuration information database to generate a collation database and a classification database. The address database includes an address database of an apparatus of a control system. The configuration information database includes configuration information of a user region of a communication message data transmitted in the control system. The collation database includes transmission and reception addresses and configuration information data of the communication message data. The classification database is generated by extracting the same header from the collation database. If the extracted communication message data does not have any header, the classification database estimates a header to associate the estimated header with the configuration information data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a communication message data collating device that collates communication message data used in a control system of an industrial plant with a list of given configuration information. [Background technology]

[0002] Industrial plants sometimes undergo equipment upgrades, which often involve updating the control systems that control the various devices and equipment in the plant.

[0003] In such equipment upgrades, in order to achieve the same functionality in the control systems before and after the upgrade, it is necessary to understand the status of communication message data transmission and reception in the control system. The content of the sent and received communication message data is recorded in the specifications of the existing control system, the configuration of the communication message data, and the communication message data list. However, the configuration of the equipment and control system may be changed or modified by the plant owner, and may differ from the status of the equipment and control system that is actually in operation.

[0004] Therefore, in an actually operating control system, it is necessary to collect communication message data and compare it with a list of configuration information for the communication message data. If the collected communication message data is compared with the list manually, it takes a lot of time and there is a risk of oversights or comparison errors.

[0005] A known technology for analyzing communication message data is disclosed in, for example, Patent Document 1. In Patent Document 1, the format of configuration information data is determined, a method for automatically matching communication message data with configuration information data is defined, and the message analysis process is automated. By inputting the configuration information in advance, information such as headers, addresses, and data values ​​can be obtained from the collected communication message data.

[0006] However, if there is even a partial mismatch between the communication message data and the configuration information, the control system designer must manually correct the configuration information corresponding to the collected communication message data, which still makes it difficult to prevent unnecessary man-hours and human errors. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-172747 Summary of the Invention [Problem to be solved by the invention]

[0008] An object of an embodiment of the present invention is to provide a communication message data collating device that collates collected communication message data with configuration information without human intervention. [Means for solving the problem]

[0009] A communication message data collating device according to an embodiment of the present invention includes a device constituting a control system for controlling equipment installed in a plant, an address database associated with the device and including address data of the device in the control system, and a configuration information database circulating through the control system and including configuration information in the user area of ​​packet-formatted communication message data including a destination address, a reception time, a source address, a transmission time, and a user area. The device extracts the destination address of the collected communication message data based on the address database, extracts the source address of the collected communication message data based on the address database, and collates the configuration information in the configuration information database with the configuration information data stored in the user area to generate a collation database. If the header data exists at the storage position at the beginning of the user area, the destination address, the source address, and the configuration information data are associated with the header data to generate a classification database; if the header data does not exist at the storage position at the beginning of the user area, the non-existent header data is estimated based on the destination address, the reception time, the source address, the transmission time, and the configuration information data other than the header, and the estimated header data is associated with the destination address, the source address, and the configuration information data to generate a classification database. [Effects of the Invention]

[0010] According to an embodiment of the present invention, it is possible to provide a communication message data collating device that collates collected communication message data with configuration information without human intervention. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic block diagram illustrating a control system including a communication message data collating device according to an embodiment. [Figure 2] 2 is a schematic diagram illustrating the configuration of communication message data used in the control system. FIG. [Figure 3] 1 is a schematic diagram illustrating an example of an integrated database set in a communication message data collating device. [Figure 4] 4 is a schematic diagram illustrating an address database that constitutes the integrated database of FIG. 3. FIG. [Figure 5] 4 is a schematic diagram illustrating a configuration information database that constitutes the integrated database of FIG. 3. FIG. [Figure 6] 4 is a schematic diagram illustrating a collation database that constitutes the integrated database of FIG. 3. FIG. [Figure 7] FIG. 4 is a schematic diagram illustrating a classification database that constitutes the integrated database of FIG. 3. [Figure 8] 10 is an example of a flowchart for explaining the overall operation of the communication message data collating device. [Figure 9] 10 is an example of a flowchart for explaining a header estimation operation of a communication message data collating device. [Figure 10] 10 is an example of a flowchart for explaining the operation of generating a collation database of a communication message data collating device. [Figure 11] 10 is a flowchart for explaining the operation of generating a classification database of the communication message data collating device. [Figure 12] 10 is a schematic diagram illustrating an example of an output result of the communication message data collating device. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments will be described with reference to the drawings. The drawings are schematic or conceptual, and the relationship between the thickness and width of each part, the size ratio between parts, etc. are not necessarily the same as those in reality. Furthermore, even when the same part is shown, the dimensions and ratios may be different depending on the drawing. In the present specification and the drawings, elements similar to those described above with reference to the previous drawings are designated by the same reference numerals, and detailed descriptions thereof will be omitted as appropriate.

[0013] FIG. 1 is a schematic block diagram illustrating a control system including a communication message data collating device according to an embodiment. As shown in FIG. 1, the control system 100 includes a communication message data collating device 10, a PLC 20, and computer devices 40 and 50.

[0014] 1, the communication message data collating device 10 and the PLC 20 are connected to each other via a control system network 101b so that they can communicate with each other. In the control system network 101b, for example, as in this example, the communication message data collating device 10 and the PLC are connected via a hub 30.

[0015] The computer device 50 is communicably connected to an information network 101a, and in the example of Fig. 1, is communicable with an output device 60. In the information network 101a, these devices are connected via a hub 70, as in this example. The computer device 50 is, for example, a host computer that manages information related to production plans, quality control, etc. of products manufactured in this plant.

[0016] The information network 101a and the control network 101b are connected to each other so that they can communicate with each other via a computer device 40. The computer device 40 is, for example, a gateway server that handles protocol conversion between different networks. Each of these devices in the control system 100 sends and receives communication message data and executes desired processing.

[0017] In the example of FIG. 1, the communication message data collating device 10 is connected to the control network 101b, but this is not limiting as long as it can collect communication message data transmitted and received within the control system 100. For example, the communication message data collating device 10 may be connected to the information network 101a. Also, FIG. 1 shows an example of the configuration of the control system 100, and various configurations can be used depending on the industrial plant. The control network 101b and the information network 101a may each be composed of multiple networks, and the communication interface may be wireless or wired.

[0018] FIG. 2 is a schematic diagram illustrating the structure of communication message data used in the control system. The communication message data 1 is packet communication data transmitted within the control system 100. As shown in Fig. 2, the communication message data 1 includes a destination address area 1a, a source address area 1b, and a user area 1c. The communication message data collating device 10 updates the integrated database based on the destination address stored in the destination address area 1a, the source address stored in the source address area 1b, and the configuration information data stored in the user area 1c.

[0019] FIG. 3 is a schematic diagram illustrating an integrated database set in the communication message data collating device. As shown in Figure 3, the integrated database (hereinafter referred to as the integrated DB) 8 includes an address database (hereinafter referred to as the address DB) 2, a configuration information database (hereinafter referred to as the configuration information DB) 3, a matching database (hereinafter referred to as the matching DB) 4, and a classification database (hereinafter referred to as the classification DB) 5.

[0020] The data in the address DB2 and the matching DB4 are associated with the IP address and / or MAC address data of each device in the control system 100. In these databases, by specifying an IP address and / or MAC address, data associated with these addresses can be searched and extracted.

[0021] The data in the configuration information DB3 and the collation DB4 are associated with each other by header data stored in the user area 1c of the communication message data 1. In these databases, by specifying header data, it is possible to search for and extract data associated with the header.

[0022] The data in the collation DB 4 and classification DB 5 are associated with classification numbers that identify multiple pieces of data corresponding to configuration information with the same header. In these databases, by specifying a classification number, it is possible to search and extract data associated with that classification number.

[0023] In the communication message data collating device 10 according to the embodiment, even if header data is missing from the configuration information data stored in the user area 1c, the header can be estimated. Therefore, the operator of the communication message data collating device 10 can efficiently collate and classify the communication message data 1 without manually analyzing the communication message data 1 with a missing header.

[0024] Furthermore, in the communication message data collating device 10 according to the embodiment, if the configuration information data stored in the user area 1c differs from the configuration information set in the configuration information DB 3, a collation comment indicating this fact is associated before classification is performed. Therefore, after the integrated DB 8 is finally updated, the collation result can be confirmed on the assumption that there was a mismatch in the configuration information data.

[0025] The operator of the communication message data collating device 10 can search and extract desired data using any query they create from the timely and appropriately generated and updated integrated DB 8. The operator can then update the control system 100 based on the extracted data.

[0026] FIG. 4 is a schematic diagram illustrating an address database that constitutes the integrated database of FIG. As shown in Fig. 4, the address DB2 stores address data for each device connected to the information network 101a and the control network 101b. In the example of Fig. 4, a serial number is assigned to each device constituting the control system 100, and the serial number is associated with device name and IP address data. In this example, MAC addresses can be stored in addition to IP addresses. For example, if the communication message data collating device 10 acquires a MAC address when generating the collation DB4, it can input the acquired MAC address to update the address DB2.

[0027] FIG. 5 is a schematic diagram illustrating a configuration information database that constitutes the integrated database of FIG. The configuration information DB3 includes the configuration information of the communication message data 1. The configuration information is a framework set in the user area 1c of the communication message data 1. In the configuration information, in addition to the header, the location where multiple pieces of information relating to the content of processing in the plant process are stored, the data format, etc. are set in the user area 1c.

[0028] The example in Figure 5 shows an example of configuration information in communication message data 1 for a process in a steel plant in which preceding and succeeding materials are welded together before heat treatment. In this example, 60 bytes of configuration information data are stored in user area 1c. The header is data stored at the beginning of user area 1c. In this example of configuration information, the header occupies 4 bytes. In order to identify the configuration information, for example, a serial number is set in the header. Following the header, data such as the fact that it is a preceding material, coil number data (12 bytes), and steel type (2 bytes) are set as the framework for the configuration information, along with data such as the storage location and data format specification.

[0029] Note that specific data such as coil numbers and steel types are input and set into the configuration information framework of the communication message data 1 circulating within the control system 100, and devices such as the PLC 20 set parameters for a control program or generate control signals according to this data. In other words, there can be multiple pieces of configuration information with the same header data, and in the example of a steel plant, there are as many pieces of communication message data 1 as there are steel materials that have passed through the welding process.

[0030] Note that the framework of each item of configuration information in the configuration information DB3, as shown in Figure 5, is called "configuration information," and data in which data is set for the items of configuration information in the communication message data 1 circulating within the control system 100 is called "configuration information data." Configuration information is set in the configuration information DB3, and the configuration information data is stored in the user area 1c of the communication message data 1 as specific data for the framework of the configuration information. In the communication message data 1, the configuration information is identified by a header.

[0031] The configuration information in the configuration information DB3 consists of multiple pre-defined items. Preferably, as in this example, in the configuration information DB3, each item of the configuration information is defined by its relative position from the header and / or its data length. That is, following the header, the coil number and steel type are set by their data length, and the necessity of welding is set by their bit position from the header. In the example of FIG. 5, multiple bit positions relative to the header are set for the necessity of welding, making it possible to verify the location of the information even if the format of the communication message data 1 changes after the initial configuration information was set.

[0032] FIG. 6 is a schematic diagram illustrating a collation database that constitutes the integrated database of FIG. As shown in Fig. 6, the collation DB 4 stores address data and configuration information data of the communication message data 1. The stored data is sequentially assigned a serial number and a classification number for the collected data (indicated as "collected data" in Fig. 6). The collected multiple communication message data 1 can be identified by the serial number and / or classification number. In the following description, each data item in the collected communication message data 1 is described as being associated with a classification number.

[0033] Among the items in the collation DB 4, FlagA represents a flag that determines whether header data exists in the communication message data 1 having that classification number. For example, if header data exists in the communication message data 1, FlagA is set to "1," and if header data does not exist, FlagA is set to "0."

[0034] If header data does not exist in the collected communication message data 1, the communication message data matching device 10 performs a header estimation operation, applies the estimated header, and stores the data in the matching DB 4. Preferably, when a header estimation is performed, the communication message data matching device 10 outputs in the integrated database 8 a message indicating that the header data is an estimated value in a manner that makes it identifiable.

[0035] Among the items in the collation DB 4, Flag B is a flag that determines whether the configuration information data of the communication message data 1 having the classification number is the same as the configuration information in the configuration information DB 3. For example, if all the configuration information data in the communication message data 1 matches all the configuration information in the configuration information DB 3, Flag B is set to "1," and if there is any item that does not match, Flag B is set to "0."

[0036] Among the items in the collation DB4, the collation comment is a comment in text data about a mismatched item when FlagB is "0." The communication message data collation device 10 selects appropriate text data about the difference for an item that does not match between the configuration information data of the communication message data 1 and the configuration information item in the configuration information DB3, associates it with a classification number, and stores it in the collation comment field of the collation DB4. The text data to be stored in the collation comment is set in advance.

[0037] FIG. 7 is a schematic diagram illustrating a classification database that constitutes the integrated database of FIG. As shown in Fig. 7, the classification DB 5 is made up of multiple tables 5a. Each table 5a stores data having multiple classification numbers (in Fig. 7, these are represented as "actual data 1") associated with one header. In the case of a steel plant, for example, there are as many communication message data 1 with one header as there are coils, and the coil numbers are associated with the classification numbers and stored in one table 5a.

[0038] The plurality of tables 5a includes not only data of communication message data 1 having header data, but also data of communication message data 1 to which a header estimated by the estimation operation has been added.

[0039] The operation of the communication message data collating device 10 according to the embodiment will be described with reference to a flowchart. FIG. 8 is an example of a flowchart for explaining the overall operation of the communication message data collating device.

[0040] 8, in step S10, the communication message data collating device 10 generates a collation DB 4. For example, the communication message data collating device 10 refers to the address DB 2 and the configuration information DB 3 for all collected communication message data 1, extracts necessary data, and stores it in a predetermined location in the collation DB 4. The data stored in the collation DB 4 is associated with a classification number.

[0041] In generating the collation DB4, the communication message data matching device 10 determines whether header data is present in the communication message data 1. If header data is present in the communication message data 1, the communication message data matching device 10 sets the value of FlagA to "1", and if header data is not present in the communication message data 1, the communication message data matching device 10 sets the value of FlagA to "0". The communication message data matching device 10 associates the set value of FlagA with a classification number and stores it in the collation DB4.

[0042] The communication message data matching device 10 also determines whether the configuration information data of the communication message data 1 differs from the configuration information of the configuration information DB3. If the configuration information data of the communication message data 1 matches the configuration information of the configuration information DB3, the communication message data matching device 10 sets the value of FlagB to "1." If the configuration information data of the communication message data 1 does not match the configuration information of the configuration information DB3, the communication message data matching device 10 sets the value of FlagB to "0." The communication message data matching device 10 associates the set value of FlagB with a classification number and stores it in the matching DB4.

[0043] In step S11, the communication message data collating device 10 generates a classification DB 5. For example, the communication message data collating device 10 extracts multiple pieces of configuration information data associated with classification numbers having the same header data from the generated collation DB 4. The communication message data collating device 10 assembles these pieces of configuration information data into a table 5a that constitutes the classification DB 5.

[0044] In step S12, if the value of FlagA of the configuration information data associated with each classification number is "1", the communication message data collating device 10 transitions the process to step S14. If the value of FlagA of the configuration information data is "0", the communication message data collating device 10 transitions the process to step S13.

[0045] When the process advances to step S13 in step S12, the communication message data collating device 10 starts the header estimation operation.

[0046] In step S13, the communication message data collating device 10 estimates the header of the communication message data 1 for which no header data exists, associates the estimated header with a classification number corresponding to the header, and stores the association in the collation DB 4. The communication message data collating device 10 returns the process to step S10 and repeats the above-mentioned operations.

[0047] When the process is shifted to step S14 in step S12, the communication message data matching device 10 checks the value of Flag B. In step S14, if the value of Flag B is "1", the communication message data matching device 10 shifts the process to step S15. In step S15, the communication message data matching device 10 displays the classification DB 5 and ends the process.

[0048] In step S14, if the value of FlagB is "0," the communication message data matching device 10 selects an appropriate matching comment based on the configuration information data of the communication message data 1 and the configuration information of the configuration information DB3. The communication message data matching device 10 associates the selected matching comment with a classification number, stores it in the classification DB5, displays the classification DB5, and ends the process. Note that in the above specific example, all of the data in the communication message data 1 is matched and associated with the classification number to generate the matching DB4, and then the classification DB5 is generated, but this is not limited to this. For example, the data in the communication message data 1 may be matched one by one, and each time it is matched, the data may be classified by header to generate a classification DB.

[0049] An example of the header estimation operation in step S13 of FIG. 8 will be described. FIG. 9 is an example of a flowchart for explaining the header estimation operation of the communication message data collating device. As shown in FIG. 9, in step S20, the communication message data collating device 10 estimates the header using a learning model.

[0050] Specifically, the learning model set in the communication message data collating device 10 learns the relationship between the header and other constituent information data in the process of generating the collation DB4.

[0051] For example, in the case of the same header, configuration information data associated with multiple classification numbers will have the same configuration information. If the header of communication message data 1 is lost for some reason during the data transmission process, configuration information data associated with different classification numbers that have the same configuration information will often have the same header.

[0052] Furthermore, the time when the communication message data 1 was sent from the sending device and the time when it was received by the receiving device are associated as timestamps. Therefore, communication message data 1 having the same or similar configuration information data often have consecutive timestamps, so it may be possible to assume that such communication message data 1 have the same header. Also, if the steel type is the same and the timestamps are consecutive, it is highly likely that the header is the same.

[0053] In this way, by having the learning model learn the plant characteristics, it is possible to estimate the header of communication message data 1 that does not have header data, and apply appropriate header data.

[0054] In step S21, the communication message data matching device 10 preferably sets a flag value so that if the header is estimated by an estimation operation, it displays that fact, and displays that the header data is an estimated value obtained by an estimation operation according to the flag value.

[0055] In step S22, the communication message data matching device 10 determines whether or not to update the configuration information in the configuration information DB3. If the communication message data matching device 10 updates the configuration information DB3, it updates the configuration information DB3 and transitions the process to step S10. If the communication message data matching device 10 does not update the configuration information DB3, it simply ends the process. Note that in this example, updating the configuration information is a process in which, if header data does not exist in all communication message data 1 having the same configuration information, an estimated header is set and stored in the configuration information DB3.

[0056] The data estimation operation using the learning model is not limited to the estimation of headers, but can also be applied to missing configuration information data. For example, if there is no configuration information data corresponding to the relative position assumed when pre-setting the configuration information DB3, it is possible to estimate which configuration information the configuration information data corresponds to. In such cases, by updating the configuration information DB3 itself, the communication message data matching device 10 can perform matching operations appropriately and quickly.

[0057] FIG. 10 is an example of a flowchart for explaining the operation of generating a collation database of the communication message data collating device. FIG. 10 shows a more detailed example of the operation of generating the collation DB4 in step 10 of FIG.

[0058] FIG. 10 shows the operation of identifying the sender and receiver of communication message data 1, which is one of the operations for generating the collation DB4. In this example, in the collation DB4, data for identifying the sender and receiver is further associated with the configuration information data associated with the classification number. In this example, the receiver address and sender address of communication message data 1 are compared with the address DB, and the IP addresses of the sender and receiver are associated with the classification number (steps S101 to S104). If there are no IP addresses, MAC addresses are associated (steps S102, S105 to S107). In this way, the collation DB4 is generated (steps S108 to S111).

[0059] FIG. 11 is a flowchart for explaining the operation of generating a classification database of the communication message data collating device. FIG. 11 shows a detailed example of the operation of generating the classification DB 5.

[0060] 11, the communication message data collating device 10 generates a classification DB 5 based on the collation DB 4. Specifically, the communication message data collating device 10 extracts header data associated with the classification number in the collation DB 4 and stores it in a table 5a for each header.

[0061] In the example of Figure 11, for data where the value of FlagA is "1", the configuration information data associated with the classification number is extracted to show differences with the configuration information in the configuration information DB (steps S201 to S207), and a comparison comment is selected and associated (steps S208 to S210).

[0062] The communication message data collating device 10 ends the process when it has classified the configuration information data associated with all the classification numbers in the collation DB 4 (steps S211 to S215).

[0063] In this way, the communication message data collating device 10 can generate a collation DB 4 from the collected communication message data 1 based on the address DB 2 and the configuration information DB 3. Based on the generated collation DB 4, the communication message data collating device 10 can generate a classification DB 5 consisting of tables 5a for each header, and can build an integrated DB.

[0064] FIG. 12 is a schematic diagram illustrating an output result of the communication message data collating device. As shown in FIG. 12, the communication message data collating device 10 can output the collation DB 4 and / or classification DB 5 that have been generated from the constructed integrated DB 8.

[0065] The output result 8a shows an example in which there is no missing header or difference in configuration information data in the communication message data 1. The output result 8a is an output example of the table 5a of the classification DB 5.

[0066] Output result 8b shows an example of a case where there is a difference in the configuration information data of communication message data 1. In output result 8b, a comparison comment indicating the difference is displayed. In output result 8b, the "Data Length" column also indicates that the length of the data in user area 1c differs from the configuration information in configuration information DB3.

[0067] The output result 8c shows the result in which the header data does not exist, and the header is estimated and output together with the configuration information data.

[0068] The effects of the communication message data collating device 10 according to the embodiment will be described. The communication message data collating device 10 according to the embodiment can compare and contrast the destination addresses, source addresses, their timestamps, and the attributes of the configuration information data stored in the user area 1c of the collected communication message data 1. This makes it possible to estimate the header data even if the communication message data 1 does not have a header. Since the configuration information data is arranged after the header position in the user area 1c of the communication message data 1, the header can be estimated by the header estimation operation even for communication message data 1 that does not have a header, making it possible to collate the configuration information data after the header.

[0069] As a result, in the communication message data collating device 10, the operator of the communication message data collating device 10 does not need to manually analyze communication message data 1 that does not have a header, making it possible to make update engineering work more efficient and faster.

[0070] The communication message data collating device 10 sets each piece of configuration information in the configuration information DB 3 in a relative position and format. Therefore, when a header is set in an appropriate position and in an appropriate format in the user area 1c, even if other configuration information data differs from the configuration information in the configuration information DB 3, the configuration information data can be reliably collated.

[0071] Furthermore, if there is a difference in the configuration information data, the communication message data collating device 10 associates a pre-set collation comment that can be output and displayed with the classification number associated with that data. Therefore, update engineering work can be performed while referring to the collation comment for items with differences in the configuration information data, allowing for efficient work that takes differences into consideration.

[0072] In this way, a communication message data collating device can be realized that collates collected communication message data with the list without human intervention.

[0073] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0074] 1...communication message data, 1a...recipient address area, 1b...source address area, 1c...user area, 2...address DB, 3...configuration information DB, 4...matching DB, 5...classification DB, 5a...table, 8...integrated DB, 8a to 8c...output results, 10...communication message data matching device, 20...PLC, 30, 70...hub, 40, 50...computer device, 60...output device, 100...control system

Claims

1. an address database including devices constituting a control system for controlling equipment installed in a plant and address data of the devices in the control system, the address database being associated with the devices; a configuration information database that circulates through the control system and contains configuration information in the user area of ​​packet-formatted communication message data that includes a destination address, a receiving time, a source address, a sending time, and a user area; Equipped with extracting the destination address of the collected communication message data based on the address database; extracting the sender address of the collected communication message data based on the address database; generating a collation database by comparing the configuration information in the configuration information database with the configuration information data stored in the user area; If the header data exists at the top storage position of the user area, the destination address, the source address, and the configuration information data are associated with the header data to generate a classification database; If header data does not exist in the storage position at the beginning of the user area, the communication message data collating device estimates the non-existent header data based on the destination address, the reception time, the source address, the transmission time, and data other than the header among the configuration information data, and associates the estimated header data with the destination address, the source address, and the configuration information data to generate a classification database.

2. 2. The communication message data matching device of claim 1, wherein estimating the non-existent header data includes estimating the non-existent header data using a learning model trained based on the destination address, the source address, and the configuration information data associated with the header data when the header data exists.

3. 3. The communication message data collating device according to claim 1, wherein when said configuration information and said configuration information data are compared, if there is a difference, a flag is associated with said configuration information data that is different.

Images