Multi-terminal synchronous industrial control data intelligent analysis and prediction method

Abstract

The application relates to the technical field of industrial control data synchronization processing, in particular to a multi-terminal synchronous industrial control data intelligent analysis and prediction method; the method comprises the following steps: collecting local multi-terminal industrial control data through an industrial control edge node, screening key state records and generating state trace trigger records; generating a state trace record table according to a preset state trace template table and configuring an end-side trace record bit; writing subsequent industrial control data into the corresponding record bit, generating an edge trace write-in table and an edge trace abstract package; and based on a preset industrial control object association table, performing cross-edge merging by a cloud end synchronization server and rewriting the merging result. The application realizes unified recording, cross-edge supplementing and analysis and prediction of the state of multi-terminal industrial control data writing.

Description

Technical Field

[0001] This invention relates to the field of industrial control data synchronization processing technology, specifically to a method for intelligent analysis and prediction of multi-terminal synchronized industrial control data. Background Technology

[0002] With the development of industrial control systems, edge computing, and cloud data synchronization technologies, control command data, execution feedback data, sensor response data, display refresh data, alarm status data, and platform result data during equipment operation are typically generated separately by different data terminals. These data are then collected, aggregated, stored, and analyzed through industrial control edge nodes and cloud synchronization servers. In multi-terminal industrial control data analysis scenarios, the system usually needs to determine the operating status, state transition process, location of anomalies, and subsequent operating trends of the controlled object based on the operating data generated by different data terminals. This enables operators to form a basis for equipment control, process adjustment, and anomaly handling based on multi-terminal data. In the process of synchronous analysis and prediction of multi-terminal industrial control data, there are still problems such as difficulty in closing the data records of the same state switching process and difficulty in participating in the same analysis and prediction of data across edge nodes. Specifically, on the one hand, the control end data, execution end data, sensor end data, display end data, alarm end data and platform end result data generated by the same controlled object during the state switching process usually have different data sources, writing order and arrival time. The platform end may have already formed result data, while the execution end data, sensor end data or alarm end data have not yet formed corresponding records, making it difficult for the system to determine whether the multi-terminal data in this state switching process has been written, whether there are gaps or conflicts. On the other hand, a single industrial control edge node can usually only process the industrial control operation data in the local data source. When the state judgment of the target industrial control object needs to be combined with the data of related industrial control objects, upstream and downstream objects of the process or other edge nodes under the same control batch, the local edge node has difficulty in incorporating cross-edge data into the same writing state judgment process, resulting in abnormal gaps, state conflicts and the lack of cross-edge data support for subsequent state prediction. Summary of the Invention

[0003] The purpose of this invention is to provide a method for intelligent analysis and prediction of multi-terminal synchronous industrial control data, in order to solve the problems mentioned in the background art, such as the difficulty in closing the data records of the same state switching process and the difficulty in participating in the same analysis and prediction of data across edge nodes.

[0004] To achieve the above objectives, the technical solution of the present invention is: a method for intelligent analysis and prediction of multi-terminal synchronous industrial control data, comprising: S1. Collect local multi-terminal industrial control data through industrial control edge nodes, filter key status records based on status change data in local multi-terminal industrial control data, and generate status trace trigger records based on key status records. Among them, the status trace trigger record is a data record generated by the industrial control edge node when it detects a switch in equipment status action or process status action; S2. The industrial control edge node calls the preset state trace template table based on the state change code in the state trace trigger record, generates the state trace record table of the target industrial control object under the current control batch, and configures the end-side trace record bit in the state trace record table. Among them, the preset status trace template table is a preset data table used to describe the status switching process of the target industrial control object under the current control batch; the target industrial control object is the industrial control object whose local multi-terminal industrial control data is collected; the end-side trace record position is a single data carrier position in the status trace record table; S3. After the industrial control edge node records the key status, the local multi-terminal industrial control data that arrives is written into the corresponding edge trace record bit. Based on the writing result of the edge trace record bit, the edge trace writing table and the corresponding edge trace summary package are generated. Among them, the write result of the end-side trace record bit is the data state formed after the local multi-terminal industrial control data enters the end-side trace record bit; the edge trace summary packet is the reporting data packet extracted by the industrial control edge node from the edge trace write table. S4. The cloud synchronization server receives the edge trace summary packet, performs cross-edge merging of the end-side trace record bits in multiple edge trace summary packets according to the preset industrial control object association table, generates cloud trace merging results, and writes the cloud trace merging results back to the corresponding industrial control edge node to update the edge trace writing table and generate industrial control analysis and prediction result data. Among them, the preset industrial control object association table is a manually preset data table that describes the equipment connection relationship, upstream and downstream process relationship and control batch association relationship between industrial control objects; the cloud trace merging result is the write-back data formed by the cloud synchronization server merging the data packets reported by multiple industrial control edge nodes.

[0005] Preferably, in S1, the industrial control edge node is an edge computing device deployed on the industrial control field side; the local multi-terminal industrial control data is a collection of industrial control operation data generated from multiple data sources under the current control batch, including control end data, execution end data, sensor end data, display end data, alarm end data, and platform end result data; the state change data is the data content in the local multi-terminal industrial control data that represents the switching of the controlled object's operating stage; the key state record is the local multi-terminal industrial control data that contains state change data and meets the conditions for generating the state trace record table; the state trace trigger record is the record table generation request data formed by converting the key state record; generating the state trace trigger record based on the key state record specifically includes: the industrial control edge node extracts the target industrial control object, the current control batch, the state change code, and the data timing reference from the key state record, writes the target industrial control object and the current control batch into the trigger attribution field, writes the state change code into the template call field, writes the data timing reference into the trigger timing field, and combines the trigger attribution field, the template call field, and the trigger timing field to form the state trace trigger record.

[0006] Preferably, in step S2, the state change code in the state trace trigger record is coded data extracted from the state change data in the key state record, used to characterize the state switching type of the target industrial control object under the current control batch; the preset state trace template table is a pre-stored, manually preset data table in the industrial control edge node, used to record the trace types and writing sequence formed under multiple terminal types for different state switching types; the current control batch is a data batch that classifies the local multi-terminal industrial control data generated by the target industrial control object under the same control batch; the industrial control edge node retrieves the corresponding template record in the preset state trace template table according to the state change code, and uses the terminal type, trace type and data writing order in the template record as the configuration basis for generating the state trace record table.

[0007] Preferably, in step S2, the status trace record table is a data table established by the industrial control edge node for the status switching process of the target industrial control object under the current control batch. It is used to record the write status of local multi-terminal industrial control data in multiple end-side trace record bits. The specific method for generating the status trace record table of the target industrial control object under the current control batch includes: the industrial control edge node determining the target industrial control object, the current control batch, and the status change code based on the status trace trigger record; calling the template record in the preset status trace template table based on the status change code; generating the end-side trace record bit set based on the template record; and combining the target industrial control object, the current control batch, and... The status change code and the set of edge trace record bits are written into the same data table to obtain the status trace record table; the edge trace record bit is a single data carrier position in the status trace record table, and a single data carrier position refers to the position in the table used to receive local multi-terminal industrial control data corresponding to one type of trace for one type of terminal; the specific method for configuring edge trace record bits in the status trace record table includes: the industrial control edge node generates edge trace record bits according to the terminal type and trace type in the template record, configures the writing order reference for the edge trace record bits according to the data writing order in the template record, and writes the edge trace record bits into the edge trace record bit set.

[0008] Preferably, in S3, the local multi-terminal industrial control data arriving after the critical state record refers to the local multi-terminal industrial control data corresponding to the target industrial control object and the current control batch, and whose data timing reference is later than the data timing reference of the state trace trigger record; the industrial control edge node writes the local multi-terminal industrial control data arriving after the critical state record into the corresponding end-side trace record bit. Specifically, the industrial control edge node reads the end type, trace type, and data timing reference from the local multi-terminal industrial control data, matches the end type with the end type in the end-side trace record bit, matches the trace type with the trace type in the end-side trace record bit, and... The data timing reference is matched with the write timing range in the edge trace record bit. When the edge type, trace type and data timing reference all meet the matching conditions, the local multi-end industrial control data is written to the corresponding edge trace record bit. After the local multi-end industrial control data is written to the corresponding edge trace record bit, the industrial control edge node registers the write status of the edge trace record bit in the edge trace write table. When the original write record identifier already exists in the same edge trace record bit, the industrial control edge node retains the original write record identifier and generates the corresponding supplementary write record identifier, sequence misalignment record identifier and conflict record identifier according to the record relationship between the original write records.

[0009] Preferably, in S3, the write result of the end-side trace recording bit refers to the recording bit state formed after the end-side trace recording bit receives local multi-terminal industrial control data, including the actual recording state, the silent recording state, the gap recording state, and the conflict recording state; wherein, the actual recording state is the writing state formed after the end type, trace type, and data timing reference all meet the matching conditions; the silent recording state is the writing state formed after the silent trace recording bit has not received abnormal event data and has received online status data at the end of the corresponding writing timing range; the gap recording state is the writing state formed after the end-side trace recording bit has not received matching local multi-terminal industrial control data at the end of the corresponding writing timing range; and the conflict recording state is the writing state formed after the same end-side trace recording bit receives multiple local multi-terminal industrial control data with inconsistent recording content.

[0010] Preferably, in step S3, the edge trace writing table is a local record bit status table formed by the industrial control edge node based on the writing results of the end-side trace record bits, used to store the writing status of each end-side trace record bit in the status trace record table; the data structure of the edge trace writing table is an association table structure with the status trace record table as the index, the end-side trace record bits as row records, the writing status as the classification label, and the original write record identifier and the supplementary write record identifier as association labels; the edge trace summary package is used to submit the record bit writing status of the target industrial control object under the current control batch to the cloud synchronization server, including the record table identifier, the target industrial control object, the current control batch, and the record bit status set; the method for generating the edge trace summary package specifically includes: the industrial control edge node extracts the record table identifier, the target industrial control object, the current control batch, and the writing status of each end-side trace record bit corresponding to the status trace record table from the edge trace writing table, groups the end-side trace record bits according to the writing status, generates a record bit status set, and encapsulates the record table identifier, the target industrial control object, the current control batch, and the record bit status set into an edge trace summary package.

[0011] Preferably, in step S4, the preset industrial control object association table is used to record the cross-edge merging reference between the target industrial control object and the associated industrial control object, and to determine the merging objects, merging ranges, and record bit writing relationships between edge trace summary packages for the cloud synchronization server; the device connection relationship between the industrial control objects is the correspondence formed between the target industrial control object and the associated industrial control object through device connection, control linkage, and data response; the upstream and downstream process relationship is the pre- and post-processing relationship between the target industrial control object and the associated industrial control object in the same process flow; the control batch association relationship is the data ownership relationship formed between the target industrial control object and the associated industrial control object under the same control batch; the cross-edge merging is the process by which the cloud synchronization server extracts edge traces uploaded by multiple industrial control edge nodes. The method for processing record bit correspondence and write status merging of the package is used to use the write status of the record bits of the associated industrial control object as a reference for the supplementation of the target industrial control object; the method for cross-edge merging of end-side trace record bits in multiple edge trace summary packages according to the preset industrial control object association table includes: the cloud synchronization server determines the associated industrial control object and associated edge node from the preset industrial control object association table according to the target industrial control object, filters the edge trace summary package according to the associated edge node, filters the record bit status set according to the associated industrial control object, determines the end-side trace record bits to be merged according to the mergeable record bit type in the preset industrial control object association table, and writes the end-side trace record bits to be merged and their write status to the cloud trace merging result corresponding to the target industrial control object.

[0012] Preferably, in step S4, the cloud trace merging result includes a merging result identifier, a source summary package identifier, a cross-edge supplementary record bit set, a gap merging record bit set, a conflict merging record bit set, and a prediction reference record bit set; wherein, the cross-edge supplementary record bit set is used to record the write status of record bits provided by the associated industrial control object for supplementary reference, the gap merging record bit set is used to record end-side trace record bits that are still in the gap recording state after cross-edge merging, the conflict merging record bit set is used to record end-side trace record bits that are still in the conflict recording state after cross-edge merging, and the prediction reference record bit set is used to record end-side trace record bits that participate in the generation of industrial control analysis prediction result data; the specific method for updating the edge trace writing table includes: the corresponding industrial control edge node receives the cloud trace merging result, merges the cloud traces... The set of record bits in the result is matched with the end-side trace record bits in the edge trace writing table. The set of cross-edge supplementary record bits is associated with the corresponding end-side trace record bits. The end-side trace record bits corresponding to the set of gap merge record bits are updated to the gap record state. The end-side trace record bits corresponding to the set of conflict merge record bits are updated to the conflict record state. The original write record identifier and supplementary write record identifier already existing in the edge trace writing table are retained. The industrial control analysis prediction result data is the status result data generated by the updated edge trace writing table. It is used to represent the multi-end data writing status and record bit generation reference of the target industrial control object in the current control batch. The industrial control analysis prediction result data includes status analysis data, gap record data, conflict record data, cross-edge supplementary data, and predicted record bit data.

[0013] Compared with the prior art, the above-mentioned technical solution of the present invention has the following beneficial technical effects: 1. In this invention, based on the status trace record table and the end-side trace record bit, industrial control data generated by different data terminals under the same control batch can be written to the corresponding position, making the correspondence between control actions, execution feedback, sensor response, alarm status and platform results clearer and reducing status misjudgment caused by asynchronous data from multiple terminals; 2. In this invention, data across edge nodes are merged through edge trace summary packages and preset industrial control object association tables, thereby achieving unified merging of associated industrial control objects and upstream and downstream process data, and providing cross-edge data support for gap recording, conflict recording and subsequent state prediction. Attached Figure Description

[0014] Figure 1 This is a flowchart of one embodiment of the present invention. Detailed Implementation

[0015] like Figure 1 As shown, the present invention proposes a multi-terminal synchronous industrial control data intelligent analysis and prediction method, the specific implementation steps of which are as follows: S1. Collect local multi-terminal industrial control data through industrial control edge nodes, filter key status records based on status change data in local multi-terminal industrial control data, and generate status trace trigger records based on key status records. Among them, the status trace trigger record is a data record generated by the industrial control edge node when it detects a switch in equipment status action or process status action; S2. The industrial control edge node calls the preset state trace template table based on the state change code in the state trace trigger record, generates the state trace record table of the target industrial control object under the current control batch, and configures the end-side trace record bit in the state trace record table. Among them, the preset status trace template table is a preset data table used to describe the status switching process of the target industrial control object under the current control batch; the target industrial control object is the industrial control object whose local multi-terminal industrial control data is collected; the end-side trace record position is a single data carrier position in the status trace record table; S3. After the industrial control edge node records the key status, the local multi-terminal industrial control data that arrives is written into the corresponding edge trace record bit. Based on the writing result of the edge trace record bit, the edge trace writing table and the corresponding edge trace summary package are generated. Among them, the write result of the end-side trace record bit is the data state formed after the local multi-terminal industrial control data enters the end-side trace record bit; the edge trace summary packet is the reporting data packet extracted by the industrial control edge node from the edge trace write table. S4. The cloud synchronization server receives the edge trace summary packet, performs cross-edge merging of the end-side trace record bits in multiple edge trace summary packets according to the preset industrial control object association table, generates cloud trace merging results, and writes the cloud trace merging results back to the corresponding industrial control edge node to update the edge trace writing table and generate industrial control analysis and prediction result data. Among them, the preset industrial control object association table is a manually preset data table that describes the equipment connection relationship, upstream and downstream process relationship and control batch association relationship between industrial control objects; the cloud trace merging result is the write-back data formed by the cloud synchronization server merging the data packets reported by multiple industrial control edge nodes.

[0016] In this embodiment S1, the industrial control edge node is an edge computing device deployed on the industrial control field side; the local multi-terminal industrial control data is a collection of industrial control operation data generated from multiple data sources under the current control batch, including control end data, execution end data, sensor end data, display end data, alarm end data, and platform end result data; the state change data is the data content in the local multi-terminal industrial control data that represents the switching of the controlled object's operating stage; the key state record is the local multi-terminal industrial control data that contains state change data and meets the conditions for generating the state trace record table; the state trace trigger record is the record table generation request data converted from the key state record; the generation of the state trace trigger record based on the key state record specifically includes: the industrial control edge node extracts the target industrial control object, the current control batch, the state change code, and the data timing reference from the key state record, writes the target industrial control object and the current control batch into the trigger attribution field, writes the state change code into the template call field, writes the data timing reference into the trigger timing field, and combines the trigger attribution field, the template call field, and the trigger timing field to form the state trace trigger record.

[0017] In this embodiment S1, the industrial control edge node is deployed on the industrial control field side. As an edge-side computing device, the industrial control edge node connects to multiple data sources under the same control batch and performs local reception, local caching, field reading, and record generation of industrial control operation data generated by multiple data sources. The local multi-terminal industrial control data is a set of industrial control operation data formed around the same controlled object under the current control batch. The local multi-terminal industrial control data includes control-end data, execution-end data, sensor-end data, display-end data, alarm-end data, and platform-end result data. Control-end data represents the control commands, control states, control stages, and control output records generated by the control system, controller, control program, and control interface under the current control batch. Execution-end data represents the action positioning, action holding, action switching, and execution feedback records generated by the actuator, execution device, drive component, and action feedback unit during the execution of control commands. Sensor-end data represents the sensors and detectors that collect the operating response of the controlled object. The table and measuring devices record pressure, temperature, flow rate, current, vibration, position, liquid level, speed, and other operating parameters generated under the current control batch; the display terminal data represents the status refresh records and display status records formed by the human-machine interface, monitoring interface, configuration screen, and status display terminal under the current control batch; the alarm terminal data represents the alarm triggering, alarm recovery, alarm holding, and alarm silence records formed by the alarm system, alarm interface, and alarm recording unit under the current control batch; the platform terminal result data represents the task results, operation confirmations, status settlements, and batch result records formed by the upper-level platform, business system, task management system, and production management system for the current control batch; when the industrial control edge node collects local multi-terminal industrial control data, it assigns the industrial control operation data generated by each data source according to the current control batch, writes the data belonging to the same controlled object into the same edge-side cache range, and retains the data source, data content, data timing reference, and status fields in each data record.

[0018] In this embodiment S1, the state change data is the data content in the local multi-terminal industrial control data that represents the switching of the operating stage of the controlled object. The state change data is used to indicate that the controlled object enters the state action of start-up, stop, open, close, switch, confirm, recover, complete, and other state actions with stage change significance under the current control batch. The state change data includes state action type, state field, state change code, and data timing reference. The state action type is used to indicate the action category corresponding to the local multi-terminal industrial control data. The state field is used to record the operating stage of the controlled object in the corresponding data source. The state change code is used to convert the operating stage switch into searchable coded data. The data timing reference is used to indicate the order of the local multi-terminal industrial control data under the current control batch. The industrial control edge node reads the state field and state change code in the local multi-terminal industrial control data, and converts the state change data into the state action type. Data records showing segment switching are used as candidate state records, and these candidate state records are matched against the conditions for generating the state trace record table. The conditions for generating the state trace record table include: the state change code belongs to the preset range of key state change codes; the candidate state record belongs to the current control batch; the candidate state record corresponds to the same controlled object; and the data timing reference of the candidate state record is within the data timing range of the current control batch. Key state records are local multi-terminal industrial control data that contain state change data and meet the conditions for generating the state trace record table. Key state records are used as the source for generating state trace trigger records. After determining the key state records, the industrial control edge node performs a corresponding verification between the key state records and the trigger records already formed under the same current control batch, and uses the state change codes recorded in the key state records as the basis for the subsequent generation of state trace trigger records.

[0019] In this embodiment S1, the state trace trigger record is the record table generation request data formed by converting key state records. The state trace trigger record is used to form the trigger basis for the record table generation process within the industrial control edge node, and is used to carry the attribution information, action information, and timing information required for subsequent calls to the preset state trace template table. When the industrial control edge node generates the state trace trigger record based on the key state record, it extracts the target industrial control object, the current control batch, the state change code, and the data timing reference from the key state record. The target industrial control object refers to the industrial control object whose local multi-terminal industrial control data is collected. The current control batch refers to the attribution range of the local multi-terminal industrial control data in the same batch control process. The state change code refers to the encoding content corresponding to the switching of the controlled object's running stage. The timing reference indicates the order of key status records in the current control batch; the industrial control edge node writes the target industrial control object and the current control batch into the trigger attribution field, which records the object range and batch range corresponding to the status trace trigger record; the industrial control edge node writes the status change code into the template call field, which records the status action type corresponding to the status trace trigger record; the industrial control edge node writes the data timing reference into the trigger timing field, which records the timing reference corresponding to the status trace trigger record; the industrial control edge node writes the trigger attribution field, template call field, and trigger timing field into the same data record to form a status trace trigger record, and establishes a record source relationship between the status trace trigger record and the key status record.

[0020] In this embodiment S1, the trigger attribution field, template call field, and trigger timing field jointly define the usage boundary of the status trace trigger record; the target industrial control object in the trigger attribution field is used to determine the controlled object corresponding to the subsequent record table, and the current control batch in the trigger attribution field is used to determine the data batch corresponding to the subsequent record table; the status change code in the template call field is used to map the equipment status action and process status action corresponding to the key status record to the template retrieval entry. The status change code can correspond to start action, stop action, valve opening action, valve closing action, conveying start action, conveying end action, pressure establishment action, pressure release action, alarm recovery action, task completion action, and other actions with stage switching meaning in the industrial control field. The status action is defined; the data timing reference in the trigger timing field is used to determine the writing judgment benchmark of local multi-terminal industrial control data after the key status record. The data timing reference can be composed of sampling sequence number, upload sequence number, database entry sequence number, batch sequence number and edge node local record sequence number; when the industrial control edge node forms a status trace trigger record, it associates and saves the original data record of the key status record with the status trace trigger record, so that the status trace trigger record retains a traceable source relationship; after the status trace trigger record is generated, the industrial control edge node caches the status trace trigger record as an internal data record in the edge side data processing flow, and establishes an index relationship according to the trigger attribution field, template call field and trigger timing field.

[0021] In this embodiment S2, the state change code in the state trace trigger record is coded data extracted from the state change data in the key state record, used to characterize the state switching type of the target industrial control object under the current control batch; the preset state trace template table is a pre-stored artificial preset data table in the industrial control edge node, used to record the trace type and writing sequence formed under multiple terminal types for different state switching types; the current control batch is a data batch that classifies the local multi-terminal industrial control data generated by the target industrial control object under the same control batch; the industrial control edge node retrieves the corresponding template record in the preset state trace template table according to the state change code, and uses the terminal type, trace type and data writing order in the template record as the configuration basis for generating the state trace record table.

[0022] In this embodiment S2, the state change code in the state trace trigger record originates from the state change data in the critical state record. The state change data includes state fields, state action types, and data timing references. When the critical state record already contains state change codes, the industrial control edge node directly reads the state change codes from the critical state record. When the critical state record contains state fields and state action types, the industrial control edge node generates state change codes based on the state fields, state action types, and a preset state code lookup table. The state change code is used to characterize the state switching type of the target industrial control object in the current control batch. The state switching types include start state switching, stop state switching, open state switching, close state switching, run confirmation state switching, alarm recovery state switching, task completion state switching, process segment entry state switching, and process segment exit state switching. Start state switching indicates that the target industrial control object has entered the run stage from the stop stage. The following states are considered as follows: Stop state switching indicates that the target industrial control object has moved from the running phase to the stop phase; Open state switching indicates that valves, switches, channels, and execution entry points within the target industrial control object have moved from the closed phase to the open phase; Close state switching indicates that valves, switches, channels, and execution entry points within the target industrial control object have moved from the open phase to the closed phase; Run confirmation state switching indicates that the target industrial control object has completed execution feedback and entered the stable operation phase; Alarm recovery state switching indicates that the target industrial control object has moved from the alarm phase to the recovery phase; Task completion state switching indicates that the platform-side result data forms the completion record for the current control batch; Process segment entry state switching indicates that the target industrial control object has entered the process processing phase of the current control batch; Process segment exit state switching indicates that the target industrial control object has exited the process processing phase of the current control batch; The industrial control edge node uses the state change code as a retrieval field to search for template records matching the state switching type in the preset state trace template table.

[0023] In this embodiment S2, the preset state trace template table is a pre-stored, manually preset data table stored in the industrial control edge node. The preset state trace template table records the trace types and writing sequences that should be formed under multiple terminal types for different state switching types. The preset state trace template table can be written to the industrial control edge node during system initialization, industrial control object configuration, control batch configuration, and process flow configuration. The preset state trace template table establishes a retrieval entry based on the state change code and records the state switching type, terminal type, trace type, and writing sequence according to the template record. The terminal type represents the data source category of local multi-terminal industrial control data, including control terminal, execution terminal, sensor terminal, display terminal, alarm terminal, and platform terminal result terminal. The trace type represents the data record category that should be formed by each terminal type during the state switching process. The types include control command traces, execution feedback traces, sensor response traces, display refresh traces, alarm silence traces, and platform result traces; the write timing indicates the data writing order of each trace type during the state transition process, including the control command write timing, execution feedback write timing, sensor response write timing, display refresh write timing, alarm silence write timing, and platform result write timing; the template record is a data record item in the preset state trace template table that matches a state change code; the template record records the trace type, data writing order, and end-side trace record bit configuration basis for a state transition type under multiple end types; after the industrial control edge node matches the template record according to the state change code, it uses the end type, trace type, and data writing order in the template record as the configuration basis for generating the state trace record table.

[0024] In this embodiment S2, the current control batch is a data batch that classifies the local multi-terminal industrial control data generated by the target industrial control object during the same batch control process. The current control batch can be determined by the control task number, process batch number, equipment action cycle number, platform task number, and edge node local batch number. The target industrial control object is the industrial control object whose local multi-terminal industrial control data is collected. The target industrial control object can be a controlled device, a controlled facility, a controlled process unit, or a controlled execution object. The industrial control edge node generates a status trace record table of the target industrial control object under the current control batch in order to record the control terminal data, execution terminal data, sensor terminal data, display terminal data, and alarm terminal data related to the status switching type during the same batch control process. Data and platform-side result data are confined to the same data ownership scope; each current control batch forms an independent data ownership boundary; each status trace record table is bound to the target industrial control object, the current control batch, and the status change code; the industrial control edge node determines the data ownership scope of the status trace record table based on the current control batch, the data object scope of the status trace record table based on the target industrial control object, and the status switching type scope of the status trace record table based on the status change code; when the industrial control edge node calls the preset status trace template table, it uses the status change code as the retrieval field, the current control batch as the data ownership field, and the target industrial control object as the object ownership field, and converts the retrieved template record into the basis for generating the status trace record table.

[0025] In this embodiment S2, the state trace record table is a data table established by the industrial control edge node for the state switching process of the target industrial control object under the current control batch. It is used to record the writing status of local multi-terminal industrial control data in multiple end-side trace record bits. The data structure of the state trace record table includes a record table identifier, target industrial control object, current control batch, state change code, end-side trace record bit set, and record table generation timing data. The specific method for generating the state trace record table of the target industrial control object under the current control batch includes: the industrial control edge node determines the target industrial control object, current control batch, and state change code according to the state trace trigger record; calls the template record in the preset state trace template table according to the state change code; generates the end-side trace record bit set according to the template record; and sets the target industrial control object, current control batch, and state change code together with the state trace record table. The encoding and the set of edge trace record bits are written into the same data table to obtain the status trace record table. The edge trace record bit is a single data carrier position in the status trace record table. A single data carrier position refers to the position in the table used to receive local multi-terminal industrial control data corresponding to one type of trace for one type of end. The data structure of the edge trace record bit includes record bit identifier, end type, trace type, write timing range, write status, original write record identifier, supplementary write record identifier, and conflict record identifier. The specific method for configuring edge trace record bits in the status trace record table includes: the industrial control edge node generates edge trace record bits according to the end type and trace type in the template record, configures the write order reference for the edge trace record bits according to the data write order in the template record, and writes the edge trace record bits into the edge trace record bit set.

[0026] In this embodiment S2, the status trace record table is a data table established by the industrial control edge node for the status switching process of the target industrial control object under the current control batch; the status trace record table is used to record the writing status of local multi-terminal industrial control data in multiple terminal trace record bits; the data structure of the status trace record table includes a record table identifier, target industrial control object, current control batch, status change code, terminal trace record bit set, and record table generation timing identifier; the record table identifier is used to identify the status trace record table; the target industrial control object is used to identify the industrial control object corresponding to the status trace record table; the current control batch is used to identify the data belonging range corresponding to the status trace record table; the status change code is used to identify the status trace record. The table corresponds to the state switching type; the end-side trace record bit set is used to carry multiple end-side trace record bits; the record table generation timing identifier is used to identify the generation order of the state trace record table in the industrial control edge node; the industrial control edge node determines the target industrial control object, the current control batch, and the state change code based on the state trace trigger record, calls the template record in the preset state trace template table based on the state change code, generates the end-side trace record bit set based on the template record, and writes the target industrial control object, the current control batch, the state change code, and the end-side trace record bit set into the same data table to obtain the state trace record table; when the state trace record table is generated, it provides the table's internal ownership boundary and a unified record table identifier for the end-side trace record bits.

[0027] In this embodiment S2, the end-side trace record bit is a single data carrying position in the status trace record table; the single data carrying position is the table position used to receive local multi-terminal industrial control data corresponding to one trace type for one end type; the relationship between the end-side trace record bit and the status trace record table is that of a table and a record position within the table; the status trace record table carries the state switching process of the target industrial control object under the current control batch, and the end-side trace record bit carries the local multi-terminal industrial control data formed under one end type and one trace type during the state switching process; a status trace record table may include multiple end-side trace record bits; each end-side trace record bit has an independent end type, trace type, write timing range, and The status record table includes: control trace record bit for recording control command traces in control terminal data; execution trace record bit for recording execution feedback traces in execution terminal data; response trace record bit for recording sensor response traces in sensor terminal data; display trace record bit for recording display refresh traces in display terminal data; silence trace record bit for recording alarm silence traces in alarm terminal data; and result trace record bit for recording platform result traces in platform terminal result data. By configuring the end-side trace record bit in the status trace record table, the industrial control edge node can write multi-terminal industrial control data during the same status switching process to the corresponding table positions, and provide the table record basis for subsequent status judgment.

[0028] In this embodiment S2, the data structure of the end-side trace recording bit includes a record bit identifier, end type, trace type, write order reference, write status, original write record identifier, supplementary write record identifier, and conflict record identifier; the record bit identifier is used to identify the end-side trace recording bit; the end type is used to identify the data source category corresponding to the end-side trace recording bit; the trace type is used to identify the data record category corresponding to the end-side trace recording bit; the write order reference is used to identify the write order and write timing range of the end-side trace recording bit during the state switching process; the write status is used to identify the recording status of the end-side trace recording bit after receiving local multi-terminal industrial control data; the original write record identifier is used to identify the local multi-terminal industrial control data first written to the end-side trace recording bit; The supplementary record identifier is used to identify local multi-terminal industrial control data that will be subsequently supplemented and written to the end-side trace record bit; the conflict record identifier is used to identify local multi-terminal industrial control data that conflicts with the existing record content in the end-side trace record bit; when the industrial control edge node configures the end-side trace record bit in the status trace record table, it generates the end-side trace record bit according to the end type and trace type in the template record, configures the write order reference for the end-side trace record bit according to the data write order in the template record, and writes the end-side trace record bit into the end-side trace record bit set; the end-side trace record bit forms a pending write state when the write state is initialized, and the original write record identifier, supplementary record identifier, and conflict record identifier form a pending fill state when the end-side trace record bit is generated.

[0029] In this embodiment S3, the local multi-terminal industrial control data arriving after the critical state record refers to the local multi-terminal industrial control data that corresponds to the target industrial control object and the current control batch, and whose data timing reference is later than the data timing reference of the state trace trigger record; the industrial control edge node writes the local multi-terminal industrial control data arriving after the critical state record into the corresponding end-side trace record bit. The specific method includes: the industrial control edge node reads the end type, trace type, and data timing reference in the local multi-terminal industrial control data, matches the end type with the end type in the end-side trace record bit, matches the trace type with the trace type in the end-side trace record bit, and then... Matching the timing reference with the write timing range in the endpoint trace record bit, and writing local multi-end industrial control data to the corresponding endpoint trace record bit when the endpoint type, trace type, and data timing reference all meet the matching conditions; after writing local multi-end industrial control data to the corresponding endpoint trace record bit, the industrial control edge node registers the write status of the endpoint trace record bit in the edge trace write table; when the same endpoint trace record bit already has an original write record identifier, the industrial control edge node retains the original write record identifier and generates the corresponding supplementary write record identifier, sequence misalignment record identifier, and conflict record identifier according to the record relationship between the original write records.

[0030] In this embodiment S3, the local multi-terminal industrial control data arriving after the critical status record is the industrial control operation data received, cached, read, and classified into the same current control batch by the industrial control edge node after the status trace trigger record is formed. The local multi-terminal industrial control data arriving after the critical status record needs to simultaneously satisfy the target industrial control object attribution, current control batch attribution, and data timing reference attribution. The target industrial control object attribution is used to ensure that the data entering the write process corresponds to the target industrial control object recorded in the status trace record table. The current control batch attribution is used to ensure that the data entering the write process corresponds to the current control batch recorded in the status trace record table. The data timing reference attribution is used to ensure that the data entering the write process is within the timing range after the status trace trigger record is formed. Data timing reference is a data reference information that indicates the sequential order of local multi-terminal industrial control data within the current control batch. Data timing reference includes at least one of sampling sequence number, upload sequence number, storage sequence number, and edge local record sequence number. Data timing reference that is later than the data timing reference of the status trace trigger record means that the data timing reference of local multi-terminal industrial control data is located after the data timing reference of the status trace trigger record in the sequence chain of the same current control batch. The industrial control edge node uses the data timing reference as the basis for timing judgment of the entry end-side trace record bit, so that control end data, execution end data, sensor end data, display end data, alarm end data, and platform end result data enter the corresponding write processing range according to the sequential relationship in the state switching process.

[0031] In this embodiment S3, when the industrial control edge node writes the local multi-terminal industrial control data that arrives after recording the key status into the corresponding end-side trace record bit, it first reads the end type, trace type, and data timing reference in the local multi-terminal industrial control data. The end type is used to indicate the data source category corresponding to the local multi-terminal industrial control data. End types include control end, execution end, sensing end, display end, alarm end, and platform end result end. The trace type is used to indicate the data record category formed by the local multi-terminal industrial control data during the state switching process. Trace types include control command traces, execution feedback traces, sensor response traces, display refresh traces, alarm silence traces, and platform result traces. The industrial control edge node matches the end type in the local multi-terminal industrial control data with the end type in the end-side trace record bit, matches the trace type in the local multi-terminal industrial control data with the trace type in the end-side trace record bit, and matches the data timing reference in the local multi-terminal industrial control data. The reference is matched with the write timing range in the endpoint trace record bit. After the endpoint type, trace type, and data timing reference all meet the corresponding matching relationship, the industrial control edge node writes the local multi-end industrial control data to the corresponding endpoint trace record bit and registers the write status of the endpoint trace record bit in the edge trace write table. When the endpoint trace record bit already has an original write record identifier, the industrial control edge node retains the original write record identifier and generates a supplementary write record identifier, a sequence misalignment record identifier, and a conflict record identifier based on the record relationship between the subsequent incoming data and the original write record. The supplementary write record identifier is used to mark the subsequent write data that provides supplementary information to the same endpoint trace record bit. The sequence misalignment record identifier is used to mark the subsequent write data that has a sequence deviation between the data timing reference and the endpoint trace record bit write timing range. The conflict record identifier is used to mark the subsequent write data that has a conflict relationship with the original write record in terms of record content.

[0032] In this embodiment S3, the write result of the end-side trace recording bit refers to the recording bit state formed after the end-side trace recording bit receives local multi-terminal industrial control data, including the actual recording state, the silent recording state, the gap recording state, and the conflict recording state. Among them, the actual recording state is the writing state formed after the end type, trace type, and data timing reference all meet the matching conditions; the silent recording state is the writing state formed after the silent trace recording bit has not received abnormal event data and has received online status data at the end of the corresponding writing timing range; the gap recording state is the writing state formed after the end-side trace recording bit has not received matching local multi-terminal industrial control data at the end of the corresponding writing timing range; and the conflict recording state is the writing state formed after the same end-side trace recording bit receives multiple local multi-terminal industrial control data with inconsistent recording contents.

[0033] In this embodiment S3, the writing result of the end-side trace recording bit is the recording bit state formed after the end-side trace recording bit receives local multi-terminal industrial control data; the writing result is used to indicate the data arrival status, silent retention status, gap formation status, and content conflict status of the end-side trace recording bit under the current control batch; the writing result includes actual recording status, silent recording status, gap recording status, and conflict recording status; actual recording status indicates that local multi-terminal industrial control data enters the end-side trace recording bit according to the end type, trace type, and writing timing range configured by the end-side trace recording bit; silent recording status indicates that the silent trace recording bit forms an online retention at the end of the corresponding writing timing range. The system includes records for holding records, heartbeat holding records, communication holding records, and empty records for abnormal events. A gap record status indicates that the end-side trace record bit remains empty at the end of its corresponding write timing range, or that the end-side trace record bit receives local multi-terminal industrial control data with the same data source but whose trace type and data timing reference do not meet the matching conditions. A conflict record status indicates that the same end-side trace record bit receives multiple local multi-terminal industrial control data with inconsistent record content. The industrial control edge node forms the write status in the edge trace write table based on the write results of the end-side trace record bits, ensuring that each end-side trace record bit has an archiveable, reportable, and mergeable record bit status during the status switching process.

[0034] In this embodiment S3, the actual recording state, silent recording state, gap recording state, and conflict recording state correspond to different writing scenarios during the state switching process. The actual recording state indicates that any of the following trace types—control command traces, execution feedback traces, sensor response traces, display refresh traces, alarm silent traces, and platform result traces—has been entered into the state trace record table according to the configuration of the end-side trace record bit. The silent recording state indicates that the alarm end and the state monitoring end remain online within the writing timing range, and the abnormal event data remains in an empty record state. The gap recording state indicates that a certain end-side trace record bit in the state switching process still lacks a local multi-terminal industrial control that can meet the matching conditions after the end of the writing timing range. Data; Conflict record status is used to indicate inconsistencies in status, action results, and platform results and execution feedback among multiple records in the same end-side trace record position; When the industrial control edge node classifies the write results, it writes the record position identifier, write status, original write record identifier, supplementary write record identifier, and conflict record identifier of the end-side trace record position into the edge trace write table; Sequential misalignment record identifier is stored in the end-side trace record position as a record relationship identifier. The sequential misalignment record identifier is used to explain the temporal deviation relationship between subsequent incoming data and the original write record. The sequential misalignment record identifier is associated with the actual record status, gap record status, or conflict record status in the edge trace write table.

[0035] In this embodiment S3, the edge trace writing table is a local record bit status table formed by the industrial control edge node based on the writing results of the end-side trace record bits, used to store the writing status of each end-side trace record bit in the status trace record table; the data structure of the edge trace writing table is an association table structure with the status trace record table as the index, the end-side trace record bits as row records, the writing status as the classification label, and the original write record identifier and the supplementary write record identifier as association labels; the edge trace summary package is used to submit the record bit writing status of the target industrial control object under the current control batch to the cloud synchronization server, including the record table identifier, the target industrial control object, the current control batch, and the record bit status set; the method for generating the edge trace summary package specifically includes: the industrial control edge node extracts the record table identifier, the target industrial control object, the current control batch, and the writing status of each end-side trace record bit corresponding to the status trace record table from the edge trace writing table, groups the end-side trace record bits according to the writing status, generates the record bit status set, and encapsulates the record table identifier, the target industrial control object, the current control batch, and the record bit status set into an edge trace summary package.

[0036] In this embodiment S3, the edge trace writing table is a local record bit status table formed by the industrial control edge node based on the writing results of the end-side trace record bits; the edge trace writing table and the status trace record table are linked by an index; the status trace record table provides a record table identifier, the target industrial control object, the current control batch, and the set of end-side trace record bits; the edge trace writing table records the writing status of each end-side trace record bit in the end-side trace record bit set after the writing process; the data structure of the edge trace writing table is based on the status trace record table as the index, the end-side trace record bits as row records, the writing status as the classification label, and the original write record identifier and the supplementary write record identifier as the classification label. The association table structure of the association marker; the status trace record table is used as an index to determine the record table belonging to the edge trace write table; the end-side trace record bit is used as a row record to save the data write status of each record bit item by item; the write status is used as a classification marker to divide the end-side trace record bit into the status groups corresponding to the actual record status, silent record status, gap record status and conflict record status; the original write record identifier and the supplementary write record identifier are used as association markers to maintain the source relationship between the end-side trace record bit and the written data; after the edge trace write table is formed, the industrial control edge node extracts the reporting content to the cloud synchronization server based on the edge trace write table.

[0037] In this embodiment S3, the edge trace summary packet is a reporting data packet extracted and encapsulated by the industrial control edge node from the edge trace write table. The edge trace summary packet is used to submit the record bit write status of the target industrial control object under the current control batch to the cloud synchronization server. The edge trace summary packet includes a record table identifier, the target industrial control object, the current control batch, and a set of record bit states. The record table identifier enables the cloud synchronization server to identify the status trace record table corresponding to the edge trace summary packet. The target industrial control object enables the cloud synchronization server to identify the industrial control object corresponding to the edge trace summary packet. The current control batch enables the cloud synchronization server to identify the batch belonging to the edge trace summary packet. The set of record bit states enables the cloud synchronization service to... The device acquires the status grouping results of the end-side trace record bits; when the industrial control edge node generates the edge trace summary packet, it extracts the record table identifier, target industrial control object, current control batch, and write status of each end-side trace record bit from the edge trace write table, and groups the end-side trace record bits according to the actual record status, silent record status, gap record status, and conflict record status to form a record bit status set; the industrial control edge node writes the record table identifier, target industrial control object, current control batch, and record bit status set into the same reporting data packet to form the edge trace summary packet; the edge trace summary packet saves the record bit status information and provides record bit-level data reference for the cloud synchronization server to perform cross-edge merging.

[0038] In this embodiment S4, a preset industrial control object association table is used to record cross-edge merging references between the target industrial control object and associated industrial control objects, and to determine the merging objects, merging ranges, and record bit writing relationships between edge trace summary packages for the cloud synchronization server; the device connection relationship between the industrial control objects is the correspondence formed between the target industrial control object and associated industrial control objects through device connection, control linkage, and data response; the upstream and downstream process relationship is the pre- and post-processing relationship between the target industrial control object and associated industrial control objects in the same process flow; the control batch association relationship is the data ownership relationship formed between the target industrial control object and associated industrial control objects under the same control batch; the cross-edge merging is the edge trace summary uploaded by the cloud synchronization server to multiple industrial control edge nodes. The method for processing record bit correspondence and write status merging is used to use the write status of the record bits of the associated industrial control object as a reference for the supplementation of the target industrial control object; the method for cross-edge merging of end-side trace record bits in multiple edge trace summary packets according to the preset industrial control object association table includes: the cloud synchronization server determines the associated industrial control object and associated edge node from the preset industrial control object association table according to the target industrial control object, filters the edge trace summary packets according to the associated edge node, filters the record bit status set according to the associated industrial control object, determines the end-side trace record bits to be merged according to the mergeable record bit type in the preset industrial control object association table, and writes the end-side trace record bits to be merged and their write status to the cloud trace merging result corresponding to the target industrial control object.

[0039] In this embodiment S4, the process of the cloud synchronization server receiving the edge trace summary packet includes edge trace summary packet access, summary packet ownership verification, summary packet parsing, and summary packet caching. Edge trace summary packet access refers to the cloud synchronization server receiving the edge trace summary packet through the data communication channel established with the industrial control edge node. Summary packet ownership verification refers to the cloud synchronization server reading the record table identifier, target industrial control object, current control batch, and record bit status set in the edge trace summary packet, and using the record table identifier, target industrial control object, and current control batch as the basis for determining the ownership of the edge trace summary packet. Summary packet parsing refers to the cloud synchronization server extracting the record bits from the edge trace summary packet. The cloud-side cache records are established according to the state set of the edge trace record bits, write status, and record bit source corresponding to the record bit state set. The digest packet cache refers to the cloud synchronization server grouping and saving edge trace digest packets from different industrial control edge nodes according to the current control batch, target industrial control object, and industrial control edge node. When the cloud synchronization server receives the edge trace digest packet, the core object processed by the cloud synchronization server is the record bit state set in the edge trace digest packet. The cloud synchronization server obtains the end-side trace record bit write status that has been formed by each industrial control edge node through the record bit state set, and uses the end-side trace record bit write status as the data basis for subsequent cross-edge merging.

[0040] In this embodiment S4, the preset industrial control object association table is a manually preset data table pre-stored on the cloud synchronization server; the preset process of the preset industrial control object association table includes object relationship registration, edge node registration, control batch registration, and mergeable record bit type registration; object relationship registration refers to writing the equipment connection relationship, upstream and downstream process relationship, and control batch association relationship between the target industrial control object and the associated industrial control object into the preset industrial control object association table; edge node registration refers to writing the industrial control edge nodes that collect local multi-terminal industrial control data of the target industrial control object and the industrial control edge nodes that collect local multi-terminal industrial control data of the associated industrial control object into the preset industrial control object association table; control batch registration refers to writing the data ownership relationship formed by the target industrial control object and the associated industrial control object under the same control batch into the preset industrial control object association table; mergeable record bit type registration refers to writing the end-side trace record bit type that is allowed to participate in cross-edge merging into the preset industrial control object association table. The associated industrial control object is an industrial control object that has a device connection relationship, upstream and downstream process relationship, and control batch relationship with the target industrial control object. The device connection relationship indicates the data correspondence between the target industrial control object and the associated industrial control object through device connection, control linkage, and data response. The upstream and downstream process relationship indicates the pre-processing relationship between the target industrial control object and the associated industrial control object in the same process flow. The control batch relationship indicates the data ownership correspondence between the target industrial control object and the associated industrial control object in the same control batch. When the cloud synchronization server determines whether there is a relationship between industrial control objects according to the preset industrial control object association table, the cloud synchronization server reads the target industrial control object, associated industrial control object, associated edge node, device connection relationship, upstream and downstream process relationship, control batch relationship, and mergeable record bit type, and determines the data object that meets the relationship recorded in the preset industrial control object association table as the cross-edge merging object.

[0041] In this embodiment S4, cross-edge merging is the process by which the cloud synchronization server performs record bit mapping and write status merging on edge trace summary packets uploaded by multiple industrial control edge nodes. Record bit mapping refers to the cloud synchronization server establishing a correspondence between the end-side trace record bits uploaded by different industrial control edge nodes based on the target industrial control object, associated industrial control object, associated edge node, and mergeable record bit type in the preset industrial control object association table. Write status merging refers to the cloud synchronization server using the write status of the record bits corresponding to the associated industrial control object as the supplementation reference, gap reference, and conflict reference for the end-side trace record bits corresponding to the target industrial control object. When the cloud synchronization server performs cross-edge merging, the cloud synchronization server first determines the target industrial control object based on the write status of the record bits corresponding to the associated industrial control object. The system determines associated industrial control objects and associated edge nodes from a preset industrial control object association table. Then, it filters the corresponding edge trace summary package based on the associated edge node, and then filters the record bit status set in the edge trace summary package based on the associated industrial control object. Finally, it determines the end-side trace record bits to be merged based on the mergeable record bit type. The cloud synchronization server writes the write status corresponding to the end-side trace record bits to be merged into the cloud trace merging result corresponding to the target industrial control object. Cross-edge merging uses the write status and record bit status set of the end-side trace record bits. Cross-edge merging forms the cloud-side merging reference of the target industrial control object, enabling the record bit write status of the associated industrial control object to participate in the edge trace write table update of the target industrial control object.

[0042] In this embodiment S4, the cloud trace merging result includes a merging result identifier, a source summary package identifier, a cross-edge supplementary record bit set, a gap merging record bit set, a conflict merging record bit set, and a prediction reference record bit set. The cross-edge supplementary record bit set records the write status of record bits provided by the associated industrial control object for supplementary reference. The gap merging record bit set records end-side trace record bits that remain in a gap recording state after cross-edge merging. The conflict merging record bit set records end-side trace record bits that remain in a conflict recording state after cross-edge merging. The prediction reference record bit set records end-side trace record bits that participate in the generation of industrial control analysis prediction result data. The specific method for updating the edge trace writing table includes: receiving the cloud trace merging result from the corresponding industrial control edge node; matching the record bit set in the cloud trace merging result with the end-side trace record bits in the edge trace writing table; associating the cross-edge supplementary record bit set with the corresponding end-side trace record bits; updating the end-side trace record bits corresponding to the gap merging record bit set to a gap recording state; and updating the conflict merging record bits. The corresponding end-side trace record bits are updated to conflict record status, while retaining the original write record identifier and supplementary write record identifier already present in the edge trace write table. The industrial control analysis prediction result data is the status result data generated by the updated edge trace write table, used to represent the multi-terminal data write status and record bit generation reference of the target industrial control object in the current control batch. The industrial control analysis prediction result data includes status analysis data, gap record data, conflict record data, cross-edge supplementary data, and predicted record bit data. Among them, the status analysis data is used to represent the summary result of the write status of each end-side trace record bit in the updated edge trace write table; the gap record data is used to represent the position and record bit type of the end-side trace record bit in the gap record status; the conflict record data is used to represent the position and conflict source of the end-side trace record bit in the conflict record status; the cross-edge supplementary data is used to represent the supplementary reference content written back from the cloud trace merging result to the corresponding industrial control edge node; the predicted record bit data is used to represent the record bit setting content that undertakes the local multi-terminal industrial control data writing during the status switching process.

[0043] In this embodiment S4, the cloud trace merging result is the write-back data generated by the cloud synchronization server based on the preset industrial control object association table and multiple edge trace summary packages. The cloud trace merging result includes a merging result identifier, a source summary package identifier, a cross-edge supplementary record bit set, a gap merging record bit set, a conflict merging record bit set, and a prediction reference record bit set. The merging result identifier is used to identify the merged data formed by a cloud cross-edge merging process. The source summary package identifier is used to identify the edge trace summary package participating in this cross-edge merging. The cross-edge supplementary record bit set is used to record the write status of the record bits provided by the associated industrial control object for supplementary reference. The gap merging record bit set is used to record the gap records that are retained after cross-edge merging. The recording status includes edge trace record bits; the conflict merging record bit set is used to record edge trace record bits that maintain the conflict record status after cross-edge merging; the prediction reference record bit set is used to record edge trace record bits that participate in the generation of prediction result data in industrial control analysis; the cloud trace merging result is sent as write-back data to the corresponding industrial control edge node, and the write-back target is the industrial control edge node where the target industrial control object is located; the purpose of writing back the cloud trace merging result to the corresponding industrial control edge node is to enable the industrial control edge node where the target industrial control object is located to obtain cross-edge fill reference, gap merging result and conflict merging result, and enable the industrial control edge node where the target industrial control object is located to form the same edge trace write table based on the local write status and the cloud merging status.

[0044] In this embodiment S4, when the corresponding industrial control edge node updates the edge trace writing table based on the cloud trace merging result, the corresponding industrial control edge node first reads the merging result identifier and source summary packet identifier from the cloud trace merging result, and then reads the cross-edge supplementary record bit set, gap merging record bit set, conflict merging record bit set, and prediction reference record bit set from the cloud trace merging result; the corresponding industrial control edge node matches the record bit set in the cloud trace merging result with the end-side trace record bit in the edge trace writing table; the corresponding industrial control edge node associates the cross-edge supplementary record bit set with the corresponding end-side trace record bit, so that the edge trace writing table records the supplementary reference content provided by the associated industrial control object; the corresponding industrial control edge node associates the end-side trace corresponding to the gap merging record bit set with the corresponding end-side trace record bit. The record bit is updated to the gap record state, so that the edge trace write table records the record bit that still has the gap after cross-edge merging; the corresponding industrial control edge node updates the end-side trace record bit corresponding to the conflict merge record bit set to the conflict record state, so that the edge trace write table records the record bit that still has the conflict after cross-edge merging; the corresponding industrial control edge node retains the original write record identifier and the supplementary write record identifier that already exist in the edge trace write table, so that the local original write source and the local supplementary write source continue to be stored in the edge trace write table; the purpose of updating the edge trace write table is to unify the local record bit write state and the cloud cross-edge merging result into the same edge-side state table, so that the edge trace write table simultaneously has the local write state, cross-edge supplementary reference, gap merging result and conflict merging result.

[0045] In this embodiment S4, the industrial control analysis prediction result data is the status result data generated by the corresponding industrial control edge node based on the updated edge trace writing table; the industrial control analysis prediction result data is used to represent the multi-terminal data writing status of the target industrial control object under the current control batch and the reference for subsequent record bit generation; the industrial control analysis prediction result data includes status analysis data, gap record data, conflict record data, cross-edge supplementation data, and predicted record bit data; the status analysis data is used to represent the summary result of the writing status of each end-side trace record bit in the updated edge trace writing table, and the status analysis data can classify the end-side trace record bits according to the actual recording status, silent recording status, gap recording status, and conflict recording status; the gap record data is used to represent the position and record of the end-side trace record bit in the gap recording status. Bit types: Gap record data corresponds to record bits that have not yet formed a valid write reference after cross-edge merging; Conflict record data is used to indicate the position of end-side trace record bits in conflict record state and the source of conflict. Conflict record data corresponds to record bits where there is inconsistency between local write content and between cross-edge supplementary reference and local write content; Cross-edge supplementary data is used to indicate the supplementary reference content written back from the cloud trace merging result to the corresponding industrial control edge node. Cross-edge supplementary data corresponds to the record bit write status provided by the associated industrial control object; Predicted record bit data is used to indicate the record bit setting content that will take over the local multi-terminal industrial control data writing during subsequent state switching. Predicted record bit data is generated based on the predicted reference record bit set and is used to provide record bit setting reference for subsequent control batches or subsequent state switching processes.

[0046] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited thereto. Various changes can be made within the scope of knowledge possessed by those skilled in the art without departing from the spirit of the present invention.

Claims

1. A method for intelligent analysis and prediction of multi-terminal synchronous industrial control data, characterized in that, Includes the following steps: S1. Collect local multi-terminal industrial control data through industrial control edge nodes, filter key status records based on status change data in local multi-terminal industrial control data, and generate status trace trigger records based on key status records. Among them, the status trace trigger record is a data record generated by the industrial control edge node when it detects a switch in equipment status action or process status action; S2. The industrial control edge node calls the preset state trace template table based on the state change code in the state trace trigger record, generates the state trace record table of the target industrial control object under the current control batch, and configures the end-side trace record bit in the state trace record table. Among them, the preset status trace template table is a preset data table used to describe the status switching process of the target industrial control object under the current control batch; the target industrial control object is the industrial control object whose local multi-terminal industrial control data is collected; the end-side trace record position is a single data carrier position in the status trace record table; S3. After the industrial control edge node records the key status, the local multi-terminal industrial control data that arrives is written into the corresponding edge trace record bit. Based on the writing result of the edge trace record bit, the edge trace writing table and the corresponding edge trace summary package are generated. Among them, the write result of the end-side trace record bit is the data state formed after the local multi-terminal industrial control data enters the end-side trace record bit; the edge trace summary packet is the reporting data packet extracted by the industrial control edge node from the edge trace write table. S4. The cloud synchronization server receives the edge trace summary packet, performs cross-edge merging of the end-side trace record bits in multiple edge trace summary packets according to the preset industrial control object association table, generates cloud trace merging results, and writes the cloud trace merging results back to the corresponding industrial control edge node to update the edge trace writing table and generate industrial control analysis and prediction result data. Among them, the preset industrial control object association table is a manually preset data table that describes the equipment connection relationship, upstream and downstream process relationship and control batch association relationship between industrial control objects; the cloud trace merging result is the write-back data formed by the cloud synchronization server merging the data packets reported by multiple industrial control edge nodes.

2. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 1, characterized in that: In S1, the industrial control edge node is an edge computing device deployed on the industrial control field side; the local multi-terminal industrial control data is a collection of industrial control operation data generated by multiple data sources under the current control batch, including control end data, execution end data, sensor end data, display end data, alarm end data, and platform end result data; the status change data is the data content in the local multi-terminal industrial control data that represents the switching of the operating stage of the controlled object. Key status records are local multi-terminal industrial control data that contain status change data and meet the conditions for generating a status trace record table; status trace trigger records are request data for generating a record table formed by converting key status records. The process of generating a status trace trigger record based on the key status record includes: the industrial control edge node extracts the target industrial control object, the current control batch, the status change code, and the data timing reference from the key status record; writes the target industrial control object and the current control batch into the trigger attribution field; writes the status change code into the template call field; writes the data timing reference into the trigger timing field; and combines the trigger attribution field, the template call field, and the trigger timing field to form the status trace trigger record.

3. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 2, characterized in that: In S2, the state change code in the state trace trigger record is encoded data extracted from the state change data in the key state record, used to characterize the state switching type of the target industrial control object under the current control batch; the preset state trace template table is a pre-stored artificial preset data table in the industrial control edge node, used to record the trace types and writing sequence formed by different state switching types under multiple terminal types; the current control batch is a data batch that classifies the local multi-terminal industrial control data generated by the target industrial control object under the same control batch. The industrial control edge node retrieves the corresponding template record from the preset status trace template table based on the status change code, and uses the terminal type, trace type and data writing order in the template record as the configuration basis for generating the status trace record table.

4. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 3, characterized in that: In S2, the status trace record table is a data table established by the industrial control edge node for the status switching process of the target industrial control object under the current control batch. It is used to record the writing status of local multi-terminal industrial control data in multiple end-side trace record bits. The process of generating a status trace record table for a target industrial control object under the current control batch includes: the industrial control edge node determining the target industrial control object, the current control batch, and the status change code based on the status trace trigger record; calling a template record in a preset status trace template table based on the status change code; generating a set of end-side trace record bits based on the template record; and writing the target industrial control object, the current control batch, the status change code, and the set of end-side trace record bits into the same data table to obtain the status trace record table. The end-side trace record bit is a single data carrier position in the status trace record table, where a single data carrier position refers to the table position used to receive local multi-terminal industrial control data corresponding to one trace type for one end type. The process of configuring end-side trace record bits in the status trace record table includes: the industrial control edge node generating end-side trace record bits according to the end type and trace type in the template record; configuring a writing order reference for the end-side trace record bits according to the data writing order in the template record; and writing the end-side trace record bits into the end-side trace record bit set.

5. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 4, characterized in that: In S3, the local multi-terminal industrial control data that arrives after the key status record refers to the local multi-terminal industrial control data that corresponds to the target industrial control object and the current control batch, and whose data timing reference is later than the data timing reference of the status trace trigger record. After recording the critical status, the industrial control edge node writes the local multi-terminal industrial control data that arrives into the corresponding end-side trace record bit. The specific method includes: the industrial control edge node reads the end type, trace type, and data timing reference from the local multi-terminal industrial control data; matches the end type with the end type in the end-side trace record bit; matches the trace type with the trace type in the end-side trace record bit; matches the data timing reference with the write timing range in the end-side trace record bit; and writes the local multi-terminal industrial control data into the corresponding end-side trace record bit when the end type, trace type, and data timing reference all meet the matching conditions. After the local multi-terminal industrial control data is written into the corresponding end-side trace record bit, the industrial control edge node registers the write status of the end-side trace record bit in the edge trace write table. When an original write record identifier already exists in the same end-side trace record bit, the industrial control edge node retains the original write record identifier and generates corresponding supplementary write record identifiers, sequence misalignment record identifiers, and conflict record identifiers according to the record relationship between the original write records.

6. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 5, characterized in that: In S3, the write result of the end-side trace record bit refers to the record bit state formed after the end-side trace record bit receives local multi-terminal industrial control data, including the actual record state, silent record state, gap record state, and conflict record state. Among them, the actual record state is the write state formed after the end type, trace type, and data timing reference all meet the matching conditions; the silent record state is the write state formed after the silent trace record bit has not received abnormal event data and has received online status data at the end of the corresponding write timing range; the gap record state is the write state formed after the end-side trace record bit has not received matching local multi-terminal industrial control data at the end of the corresponding write timing range; and the conflict record state is the write state formed after the same end-side trace record bit receives multiple local multi-terminal industrial control data with inconsistent recording content.

7. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 6, characterized in that: In S3, the edge trace writing table is a local record bit status table formed by the industrial control edge node based on the writing results of the end-side trace record bits, used to store the writing status of each end-side trace record bit in the status trace record table; the data structure of the edge trace writing table is an association table structure with the status trace record table as the index, the end-side trace record bits as the row records, the writing status as the classification label, and the original write record identifier and the supplementary write record identifier as the association label; the edge trace summary package is used to submit the record bit writing status of the target industrial control object under the current control batch to the cloud synchronization server, including the record table identifier, the target industrial control object, the current control batch, and the record bit status set; The method for generating an edge trace summary package specifically includes: the industrial control edge node extracts the record table identifier, target industrial control object, current control batch, and writing status of each end-side trace record bit from the edge trace write table; the end-side trace record bits are grouped according to the writing status to generate a record bit status set; and the record table identifier, target industrial control object, current control batch, and record bit status set are encapsulated into an edge trace summary package.

8. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 7, characterized in that: In step S4, a preset industrial control object association table is used to record cross-edge merging references between target industrial control objects and associated industrial control objects, and to determine the merging objects, merging ranges, and record bit writing relationships between edge trace summary packages for the cloud synchronization server; the device connection relationship between industrial control objects is the correspondence formed between target industrial control objects and associated industrial control objects through device connection, control linkage, and data response; the upstream and downstream process relationship is the pre- and post-processing relationship between target industrial control objects and associated industrial control objects in the same process flow; the control batch association relationship is the data ownership relationship formed between target industrial control objects and associated industrial control objects under the same control batch; the cross-edge merging is a processing method of the cloud synchronization server for recording bit correspondence and writing status merging of edge trace summary packages uploaded by multiple industrial control edge nodes, used to use the record bit writing status of associated industrial control objects as the supplementary reference for target industrial control objects; According to the preset industrial control object association table, the edge trace record bits in multiple edge trace summary packages are merged across edges. The specific method includes: the cloud synchronization server determines the associated industrial control object and associated edge node from the preset industrial control object association table based on the target industrial control object, filters the edge trace summary package based on the associated edge node, filters the record bit status set based on the associated industrial control object, determines the edge trace record bits to be merged based on the mergeable record bit type in the preset industrial control object association table, and writes the edge trace record bits to be merged and their writing status to the cloud trace merging result corresponding to the target industrial control object.

9. The intelligent analysis and prediction method for multi-terminal synchronous industrial control data according to claim 8, characterized in that: In step S4, the cloud trace merging result includes a merging result identifier, a source summary package identifier, a cross-edge supplementary record bit set, a gap merging record bit set, a conflict merging record bit set, and a prediction reference record bit set. The cross-edge supplementary record bit set records the write status of record bits for which supplementary references are provided by associated industrial control objects. The gap merging record bit set records end-side trace record bits that remain in a gap recording state after cross-edge merging. The conflict merging record bit set records end-side trace record bits that remain in a conflict recording state after cross-edge merging. The prediction reference record bit set records end-side trace record bits that participate in the generation of prediction result data for industrial control analysis. The specific method for updating the edge trace writing table includes: the corresponding industrial control edge node receives the cloud trace merging result, and the cloud trace merging result... The set of record bits in the result is matched with the end-side trace record bits in the edge trace writing table. The set of cross-edge supplementary record bits is associated with the corresponding end-side trace record bits. The end-side trace record bits corresponding to the set of gap merge record bits are updated to the gap record state. The end-side trace record bits corresponding to the set of conflict merge record bits are updated to the conflict record state. The original write record identifier and supplementary write record identifier already existing in the edge trace writing table are retained. The industrial control analysis prediction result data is the status result data generated by the updated edge trace writing table. It is used to represent the multi-end data writing status and record bit generation reference of the target industrial control object in the current control batch. The industrial control analysis prediction result data includes status analysis data, gap record data, conflict record data, cross-edge supplementary data, and predicted record bit data.

Images