A method for acquiring and managing device status that supports multiple transmission modes

Abstract

This invention discloses a method for acquiring and managing device status using multiple transmission modes, relating to the field of industrial automation technology. The method includes: acquiring a Modbus image file; establishing a Modbus TCP link from the front-end acquisition unit to a local area network server based on the Modbus image file, and uploading records after multi-channel selection and switching according to a stability margin parameter set, generating uploaded message streams and channel scheduling logs; performing anomaly tracing and parameter revision on the operational evaluation result set, and updating the joint policy package. This invention ensures more stable and efficient transmission of device status data under different network conditions, effectively supporting real-time monitoring and anomaly tracing of device status.

Description

Technical Field

[0001] This invention relates to the field of industrial automation technology, and in particular to a method for acquiring and managing equipment status that supports multiple transmission methods. Background Technology

[0002] Traditional equipment status monitoring and data acquisition are typically used in conjunction with a supervisory control and data acquisition architecture. On the field side, sensors acquire equipment operating data, while on the control side, a PLC or DCS reads preset data acquisition point parameters at a fixed sampling period and completes basic control. Simultaneously, the status data is transmitted to the upper-level supervisory control and data acquisition platform via a single communication channel using conventional communication protocols (such as Modbus, CAN, etc.). The platform then centrally aggregates the data, displays trends, manages alarms, and stores historical data. When needed, it sends setpoints, start / stop commands, or process parameters to the control side to achieve supervisory control and collaborative scheduling of equipment operation.

[0003] However, existing single-channel acquisition methods have certain limitations, especially when facing complex environments and large-scale device management, often failing to adapt to changing network conditions and diverse device requirements. First, a single channel may be affected by bandwidth limitations or network fluctuations, leading to compromised data transmission stability and timeliness. Second, in situations with a large number of devices or poor environmental conditions, single-channel acquisition may experience data transmission delays or packet loss, affecting the real-time monitoring of device status. Therefore, traditional methods exhibit significant shortcomings in handling parallel acquisition, transmission, and data fusion across multiple devices. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a device status acquisition and management method that supports multiple transmission modes to solve the problems of poor transmission stability, high latency, and packet loss in complex environments with a single channel.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides a file encryption method, which includes: generating a point register mapping table by calibrating and setting point parameters; simultaneously probing the connectivity and latency of multiple transmission channels; initializing a stability margin parameter set and a transmission channel capability table; generating a state point semantic mapping table and a joint policy package; acquiring a Modbus image file; establishing a Modbus TCP link from the front-end acquisition unit to the local area network server based on the Modbus image file; selecting and switching multiple channels according to the stability margin parameter set and uploading records; generating uploaded message streams and channel scheduling logs; generating an operational evaluation result set; performing anomaly tracing and parameter revision on the operational evaluation result set; and updating the joint policy package.

[0007] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for generating a point register mapping table by calibrating and setting acquisition point parameters are as follows: By setting the sampling period, change threshold and data type, and writing the point identifier associated record, the parameters of the collection point can be obtained; Based on the collected point parameters, the data types are bound to the register addresses in the order of the point identifiers, and then the uniqueness is verified and solidified to generate a point register mapping table.

[0008] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the steps of simultaneously performing connectivity and delay detection on multiple transmission channels and initializing the stability margin parameter set and transmission channel capability table are as follows: Read the register range and payload size from the point register mapping table, and perform connectivity and latency detection to generate a transmission channel capability table; Calculate the basic stability margin value of each transmission channel in the transmission channel capacity table. Based on the connectivity detection results and delay detection results, statistically analyze the delay fluctuation amplitude and delay fluctuation frequency according to the time series, obtain the delay fluctuation characteristics, and write them into the stability margin parameter set.

[0009] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for generating the status point semantic mapping table and the joint policy package are as follows: Based on the point identifier and the semantics of the running status, a binding relationship is established, and the trigger level condition and trigger edge condition are written into the binding table entry and then fixed to generate a state point semantic mapping table. The data acquisition point parameters, point register mapping table, transmission channel capability table, stability margin parameter set, and state point semantic mapping table are encapsulated into a joint strategy package.

[0010] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for obtaining the Modbus image file are as follows: Electrical signals are acquired based on the joint strategy package, and changes in the electrical signals are obtained. The electrical signal changes are processed for de-jittering and edge determination, and the point value corresponding to the point identifier is generated. After writing the timestamp, the status acquisition data frame is obtained. Based on the status acquisition data frame, the register address and data type corresponding to the point identifier are extracted from the point register mapping table, and the point value is written into the register address and then solidified into a Modbus image file.

[0011] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the steps of establishing a Modbus TCP link from the front-end acquisition unit to the local area network server based on a Modbus image file, and uploading records after multi-channel selection and switching according to a stability margin parameter set, are as follows: Establish a Modbus TCP connection for the local area network server based on the Modbus image file and the transmission channel capability table. Based on ModbusTCP connection and stability margin parameter set, the stability margin of multiple transmission channels is calculated, and the main channel and backup channel of multiple transmission channels are divided according to the stability margin threshold.

[0012] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for generating the uploaded message stream and channel scheduling log are as follows: Read the upload records of the message stream that has been uploaded to the main channel, and update the stability margin parameter set during the upload record process; When the updated stability margin parameter set is lower than the channel stability margin threshold, the system switches to the backup channel, records the switching time and channel identifier, and generates a channel scheduling log.

[0013] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for generating the operation evaluation result set are as follows: Extract device identifier, location identifier, timestamp, and location value from the uploaded message stream to generate a semantic name association record for the running status; Align the timestamps of the records associated with the semantic names of the running status with the device identifier and the semantic names of the running status to generate a set of records to be merged; Based on the timestamps in the set of records to be merged, the channel scheduling logs are read and matched with the switching time to generate records associated with effective time windows and channel identifiers; The effective time window, channel identifier associated records, and the set of records to be merged are subjected to consistency fusion and conflict resolution to generate a consistency fusion evidence chain. Extract the timestamp and channel identifier of the consistency fusion evidence chain, and combine the switching frequency and channel stability margin threshold triggering status with the channel scheduling log statistics, and summarize them into an operation evaluation result set.

[0014] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the specific steps for performing anomaly tracing on the operation evaluation result set are as follows: Extract the semantic name of the device's operating status, timestamp point value, and strategy evaluation index from the operation evaluation results, and identify the timestamp interval, point identifier, and channel identifier corresponding to the abnormal location. Based on the timestamp interval, location identifier, and channel identifier, a consistent fusion evidence chain is retrieved, and conflict adjudication records are extracted to obtain the adjudication results and triggering conditions.

[0015] As a preferred embodiment of the device status acquisition and management method supporting multiple transmission modes described in this invention, the steps for updating the joint policy package are as follows: Based on the ruling and triggering conditions, parameters such as sampling period, change threshold, point reliability level and channel stability margin threshold are revised, and parameter revision results are generated. Write the parameter results into the federated policy package and update the version information to generate an updated federated policy package.

[0016] The beneficial effects of this invention are as follows: By establishing a Modbus TCP link from the front-end acquisition unit to the local area network server based on the Modbus image file, and performing multi-channel selection and switching, combined with supervision and control and data acquisition methods, the transmission of device status data can be more stable and efficient under different network conditions; by performing consistency fusion and conflict resolution on the uploaded message stream, channel scheduling log and status point semantic mapping table, the data stream can be strictly matched and analyzed, anomalies can be identified and data consistency can be ensured, thereby effectively supporting real-time monitoring and anomaly tracing of device status. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart for a device status acquisition and management method that supports multiple transmission modes.

[0019] Figure 2 This is a flowchart for multi-transmission channel connectivity and delay detection.

[0020] Figure 3 The flowchart shows the process of generating status acquisition data frames and obtaining Modbus image files.

[0021] Figure 4 A flowchart for consistency integration and conflict resolution. Detailed Implementation

[0022] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0023] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0024] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0025] Reference Figures 1-4 This is one embodiment of the present invention, which provides a device status acquisition and management method supporting multiple transmission modes, including the following steps: S1: By calibrating the acquisition points and setting the acquisition point parameters, a point register mapping table is generated. At the same time, connectivity and delay detection are performed on multiple transmission channels, and a stability margin parameter set and transmission channel capability table are initialized to generate a state point semantic mapping table and a joint strategy package. S1.1: By setting the sampling period, change threshold and data type, and writing the point identifier associated record, the parameters of the sampling point can be obtained; Furthermore, in the scripted visual interface, open the point identifier association record maintenance page and load the point identifier list. Select each point identifier in the list sequentially, enter the sampling period in the sampling period input field, enter the change threshold in the change threshold input field, and select the data type in the data type selection field. Write the sampling period, change threshold, and data type corresponding to the point identifier into the point identifier association record table and save the table. After saving, perform field integrity verification on the point identifier association record to confirm that the point identifier, sampling period, change threshold, and data type have all been written and can be parsed. Perform data type consistency verification on the point identifier association record to confirm that the data type is consistent with the selected data type selection result and matches the field format of the point identifier association record. After the field integrity verification and data type consistency verification pass, solidify and export the point identifier association record. Based on the solidified export result, collect and summarize the sampling period, change threshold, and data type by point identifier to form the collection point parameters.

[0026] It should be noted that after selecting a point identifier, the change threshold is obtained by acquiring the continuous acquisition cycle point value and acquisition cycle timestamp of the point identifier during stable operation, calculating the point value difference between adjacent acquisition cycles, forming a point value difference sequence, and removing the state switching interval and retaining the stable segment point value difference sequence according to the trigger level condition and trigger edge condition obtained from the acquisition point calibration. The maximum value of the stable segment point value difference sequence is obtained as the change threshold.

[0027] S1.2: Based on the collected point parameters, bind the data type to the register address according to the point identifier order, and solidify the data after performing a uniqueness check to generate a point register mapping table; Furthermore, based on the collected point parameters, the collected point parameters are sorted according to the point identifier order, and the point identifier and data type are read one by one. A register address is assigned to each point identifier, and the register address of the point identifier data type is written into the point register mapping table record set. After writing, a uniqueness check is performed on the point register mapping table record set to detect duplicate register addresses and output a duplicate register address list. Based on the duplicate register address list, the duplicate records are reassigned register addresses, and the uniqueness check is performed again until the duplicate register address list is empty. After the uniqueness check passes, the version information is written into the point register mapping table and exported in a fixed manner to generate the point register mapping table.

[0028] S1.3: Read the register range and payload size from the point register mapping table, and perform connectivity and delay detection to generate a transmission channel capability table; Furthermore, the point register mapping table records are traversed to summarize the minimum and maximum register address values ​​to obtain the register range. Based on the number of point identifiers, data type distribution, and register address coverage density in the point register mapping table, the load scale is summarized. Using the register range as the detection target and the load scale as the detection intensity, register read / write request sequences are initiated for each of the multiple transmission channels, and the successful return status of the requests is recorded to complete connectivity and latency detection. At the same time, the sending time and return time of each request are recorded and summarized to obtain the latency characteristics and latency fluctuation characteristics of the multiple transmission channels. The connectivity detection results, latency characteristics, latency fluctuation characteristics, and register range load scale are written into the corresponding table entries of the multiple transmission channels. After performing field integrity verification and data type consistency verification, the data is solidified and exported to generate a transmission channel capability table.

[0029] S1.4: Calculate the basic stability margin value of each transmission channel in the transmission channel capacity table, and statistically analyze the delay fluctuation amplitude and delay fluctuation frequency according to the time series based on the connectivity detection results and delay detection results to obtain the delay fluctuation characteristics and write them into the stability margin parameter set; Furthermore, the transmission channel capability table is read line by line according to the multi-transmission channel identifier, and the connectivity detection results, register range, payload scale, latency characteristics, and latency fluctuation characteristics are extracted. The register range determines the coverage of register read / write requests. At the same time, based on the latency characteristics, the average response time of register read / write requests is extracted, and based on the latency fluctuation characteristics, the latency fluctuation level of register read / write request response time is extracted. The register read / write request coverage, register read / write request density, average response time, and response time fluctuation level are normalized and summarized to obtain the stability margin base value. The stability margin base value and latency fluctuation characteristics are written into the multi-transmission channel identifier table entries of the stability margin parameter set. Field integrity verification and data type consistency verification are performed on the stability margin parameter set, and the data is solidified and exported and written into the stability margin parameter set.

[0030] S1.5: Based on the point identifier and the operating status semantics, establish a binding relationship, and write the trigger level condition and trigger edge condition into the binding table entry and then solidify it to generate a status point semantic mapping table; Furthermore, after loading the list of point identifiers and the list of operational status semantics, each point identifier is selected. In the operational status semantics selection area, the operational status semantics are specified for the point identifier, generating a binding entry. At the same time, the trigger level condition and trigger edge condition are filled in in the trigger condition editing area and written into the binding entry field. Field integrity verification and trigger condition format consistency verification are performed on the binding entry, and uniqueness verification is performed on the binding relationship of duplicate point identifiers. After the verification passes, the binding entry is locked, version information is written, and the data is exported and solidified, generating a status point semantic mapping table.

[0031] It should be noted that the list of point identifiers originates from the parameter setting steps for the data acquisition points. The point identifiers are determined during the calibration and parameter setting of the data acquisition points. These parameters include the location, data type, and other associated information of each data acquisition point. By setting these parameters, a list containing all data acquisition point identifiers is generated. Each point identifier corresponds to a specific device status or monitoring data. This list of point identifiers is used in subsequent steps to generate the point register mapping table and ensure data consistency and uniqueness.

[0032] S1.6: Encapsulate the acquisition point parameters, point register mapping table, transmission channel capability table, stability margin parameter set, and status point semantic mapping table into a joint strategy package.

[0033] Furthermore, the system sequentially imports the acquisition point parameters, point register mapping table, transmission channel capability table, stability margin parameter set, and status point semantic mapping table. It reads the version information and generation flags of these tables and writes them into the joint policy package manifest field. It performs a consistency check between the acquisition point parameter point identifier and the point identifier in the point register mapping table, and simultaneously performs an overwrite check between the register address in the point register mapping table and the register range in the transmission channel capability table. It then performs a consistency check between the multiple transmission channel identifiers in the transmission channel capability table and the multiple transmission channel identifiers in the stability margin parameter set, and finally, a consistency check between the point identifiers in the status point semantic mapping table and the acquisition point parameter point identifiers. After successful checks, the acquisition point parameters, point register mapping table, transmission channel capability table, stability margin parameter set, and status point semantic mapping table are written into the joint policy package candidate record according to the joint policy package encapsulation order. Finally, it generates an integrity check value, solidifies it, and exports it to generate the joint policy package.

[0034] S2: Obtain the Modbus image file; S2.1: Acquire electrical signals according to the joint strategy package and obtain changes in electrical signals; Furthermore, based on the semantic mapping table between the acquisition point parameters and status points in the joint strategy package, the reading relationship between the point identifiers and the electrical signal acquisition interface is established according to the order of the point identifiers in the acquisition point parameters. The point value parsing method is determined according to the data type in the acquisition point parameters and written into the acquisition point parameters. After reading the sampling period and change threshold, the acquisition cycle is started. In each acquisition cycle, the electrical signal acquisition interface is called to read the electrical signal amplitude and level state corresponding to the point identifier one by one. The electrical signal amplitude and level state are written into the point identifier acquisition buffer according to the point identifier to generate the current point value. At the same time, the point value of the previous acquisition cycle and the current point value are read from the point identifier acquisition buffer, the difference between the point values ​​is calculated and the difference judgment is input. The difference judgment uses the sampling period and change threshold as the comparison boundary and outputs the electrical signal change trigger conclusion. When the electrical signal change trigger conclusion is valid, the point identifier and the current point value are written into the electrical signal change record, and the electrical signal change record is collected and summarized according to the acquisition cycle to obtain the electrical signal change.

[0035] S2.2: Perform jitter removal and edge determination on the changes in electrical signals, generate point values ​​corresponding to point identifiers, write the timestamp, and obtain the status acquisition data frame; Furthermore, the semantic mapping table of state points is retrieved one by one according to the point identifier in the electrical signal change record, and the trigger level condition and trigger edge condition are read. The point values ​​in the electrical signal change record are written into the point identifier de-jitter buffer according to the acquisition cycle order, and the difference between point values ​​in adjacent acquisition cycles is calculated. When the difference occurs repeatedly, the de-jitter buffer is kept updated and the point identifier is marked as jittering. When the difference remains consistent within the continuous acquisition cycle and the trigger level condition is met, the stable point value is locked and the point value corresponding to the point identifier is output. The change direction of the previous stable point value and the current stable point value in the de-jitter buffer is used as input and combined with the trigger edge condition to perform edge determination. When the edge determination is successful, the point identifier and point value are written into the state acquisition data frame record, and the local clock is read and written into the timestamp field to generate the state acquisition data frame.

[0036] The expression for calculating the difference in position values ​​between adjacent acquisition beat points is: ; in, Indicates the first The difference in point values ​​for each sampling beat. This indicates the index of the current acquisition cycle. Indicates the first Point values ​​of each sampling beat Indicates the first The point value of each collection cycle, Indicates the first The time interval of each acquisition cycle.

[0037] S2.3: Based on the status acquisition data frame, extract the register address and data type corresponding to the point identifier from the point register mapping table, and write the point value into the register address and then solidify it into a Modbus image file.

[0038] Furthermore, the point identifier and point value are read sequentially according to the data frame recording order of the status acquisition. At the same time, the register address and data type corresponding to the point identifier are retrieved in the point register mapping table, and the write parameter set is extracted. According to the data type, the point value is format converted and length verified to generate the register write value. The register write value is written to the register image area corresponding to the register address and the write result is recorded. The integrity verification of the register address coverage is performed, and the consistency verification of the data type and the register write value is performed. After the verification is passed, the register image area is locked and solidified into a Modbus image file.

[0039] S3: Based on the Modbus image file, establish a Modbus TCP link from the front-end acquisition unit to the local area network server, and upload records after multi-channel selection and switching according to the stability margin parameter set, generating the uploaded message stream and channel scheduling log. S3.1: Establish a Modbus TCP connection for the local area network server based on the Modbus image file and the transmission channel capability table; Furthermore, the register address coverage range in the Modbus image file is read to generate a register access list. Simultaneously, the transmission channel capability table is imported, and available multiple transmission channels are filtered according to the connectivity probe records in the transmission channel capability table. The connection priority is selected and the connection parameters are loaded according to the latency probe records in the transmission channel capability table. At the same time, a ModbusTCP connection establishment request is sent to the local area network server to complete the connection handshake. Based on the register access list, a register read / write probe request is sent to the local area network server, and a response is received to confirm the connection availability. After the connection availability is confirmed, the connection session is locked and a ModbusTCP connection to the local area network server is established.

[0040] It should be noted that if the connectivity probe log shows four successful Modbus TCP connection establishments out of the last five probes, and the most recent probe is successful, and there are no consecutive failure records in the probe window, the corresponding multi-transmission channel can be determined as an available multi-transmission channel; if the connectivity probe log shows two consecutive Modbus TCP connection establishment failures out of the last three probes, and the most recent probe fails, the corresponding multi-transmission channel should be determined as an unavailable multi-transmission channel.

[0041] S3.2: Based on ModbusTCP connection and stability margin parameter set, calculate the stability margin of multiple transmission channels, and divide the main channel and backup channel of multiple transmission channels according to the stability margin threshold; Furthermore, based on the multi-transmission channel identifiers in the stability margin parameter set, the basic stability margin value and latency fluctuation characteristics are read one by one. Simultaneously, through the ModbusTCP connection, register access probes are initiated for each multi-transmission channel, and the probe response results and probe time are recorded. The deviation between the probe time and latency fluctuation characteristics is calculated, and the deviation results are mapped to stability correction amounts. The stability correction amounts and the basic stability margin values ​​are aggregated and calculated to generate the multi-transmission channel stability margin. The multi-transmission channel stability margins are sorted, and according to the sorting results, the multi-transmission channel corresponding to the highest stability margin is designated as the primary channel, while the remaining multi-transmission channels are designated as backup channels.

[0042] Furthermore, register access probing involves initiating read / write requests to the register address of the local area network server via a ModbusTCP connection and recording the return results and response time to confirm the accessibility of the register address and the availability of the link.

[0043] S3.3: Read the upload records of the message stream that has been uploaded to the main channel, and update the stability margin parameter set during the upload record process; Furthermore, the uploaded message stream is filtered according to the main channel identifier, and the uploaded records are read one by one in chronological order. By reading the timestamp and upload result in the uploaded records, the upload time is recorded synchronously. The upload time is compared with the latency fluctuation characteristics in the stability margin parameter set to generate a latency fluctuation update value. The latency fluctuation update value is then summarized and calculated with the stability margin base value in the stability margin parameter set to generate a stability margin base value update value. The latency fluctuation update value and the stability margin base value update value are written into the stability margin parameter set. After performing field integrity verification and data type consistency verification, the stability margin parameter set is solidified.

[0044] S3.4: When the updated stability margin parameter set is lower than the channel stability margin threshold, switch to the backup channel, and record the switching time and channel identifier to generate a channel scheduling log.

[0045] Furthermore, when the updated stability margin parameter set is lower than the channel stability margin threshold, the operation of the current primary channel is stopped and the backup channel is immediately switched. At the same time, the switching time is recorded and the backup channel identifier is written into the channel scheduling log. The channel status and switching information are solidified and archived to generate the channel scheduling log.

[0046] S4: Generate the runtime evaluation result set; S4.1: Extract device identifier, location identifier, timestamp, and location value from the uploaded message stream to generate a semantic name association record for the running status; Furthermore, the device identifier, location identifier, timestamp, and location value of each record are read one by one from the uploaded message stream. The corresponding operating status semantic name is extracted from the status location semantic mapping table according to the location identifier. The device identifier, location identifier, timestamp, and location value are combined with the corresponding operating status semantic name to generate an operating status semantic name associated record.

[0047] S4.2: Align the timestamps of the records associated with the semantic names of the running status according to the device identifier and the semantic names of the running status, and generate a set of records to be merged; Furthermore, the records associated with the semantic name of the running status are grouped according to the device identifier and the semantic name of the running status. Within each group, the records are sorted in order of timestamp and the timestamps of adjacent records are aligned. The timestamps of each record are uniformly mapped to ensure that records with each timestamp in the same group are aligned. The aligned records are merged into a set of records to be merged, and the timestamps, device identifiers and semantic names of all records are consistent to generate a set of records to be merged.

[0048] S4.3: Based on the timestamps in the set of records to be merged, read the channel scheduling logs and match them with the switching time to generate a record associated with the effective time window and the channel identifier; Furthermore, timestamps are extracted one by one from the set of records to be merged, and time matching is performed with the switching times in the channel scheduling log according to the timestamp order. When a timestamp matches a switching time, the start and end times of the effective time window are determined based on the matching result, and this time window is recorded. The corresponding channel identifier is associated with the effective time window, the start and end times of the time window are recorded, and the effective time window and the channel identifier are written into the association record to generate the association between the effective time window and the channel identifier.

[0049] S4.4: Perform consistency fusion and conflict resolution on the effective time window, channel identifier associated records, and the set of records to be fused to generate a consistency fusion evidence chain; Furthermore, the effective time window and channel identifier associated records are matched one by one with the set of records to be merged. The records are sorted according to the device identifier, timestamp, and channel identifier. Consistency checks are performed on records with similar timestamps to ensure that the point value and channel identifier are consistent within the same time window. When conflicts are found between records, conflict resolution is performed. Valid records are selected to be retained and conflicting records are removed based on priority and stability. The results of consistency checks and conflict resolution are summarized into a consistency fusion evidence chain to ensure that each fused record meets the consistency requirements and generate a consistency fusion evidence chain.

[0050] It should be noted that conflict resolution refers to the process of selecting a final point value from multiple candidate point values ​​in the consistency fusion process when multiple inconsistent point values ​​appear in the same effective time window for the same device identifier and the same semantic name of the same operating state in the consistency fusion record set. This is based on the channel priority relationship and time alignment results given by the channel identifier association record, and the selection basis and selection result are written into the consistency fusion evidence chain.

[0051] S4.5: Extract the timestamp and channel identifier of the consistency fusion evidence chain, and combine it with the channel scheduling log to count the switching frequency and the triggering of the channel stability margin threshold, and summarize them into an operation evaluation result set.

[0052] Furthermore, the timestamp and channel identifier of each record are extracted from the consistency fusion evidence chain. The records are matched with the channel scheduling log in the order of timestamps. Based on the matching results, the switching frequency of each channel is counted. The switching records in the channel scheduling log are used as the basis for locating the switching time. The switching time given by the switching record is associated with the channel identifier. The updated stability margin parameter set value corresponding to the same channel identifier in the stability margin parameter set at the switching time is read. At the same time, the channel stability margin threshold is extracted. The updated stability margin parameter set value is compared with the channel stability margin threshold. When the comparison result is lower than the channel stability margin threshold, it is determined that the switching time triggers the channel stability margin threshold. When the comparison result is higher than the channel stability margin threshold, it is determined that the switching time does not trigger the channel stability margin threshold. By comparing the switching frequency and the channel stability margin threshold triggering, the stability margin status of each channel is generated, and these statistical information are summarized into an operational evaluation result set.

[0053] It should be noted that the channel stability margin threshold is determined by analyzing the connectivity detection records and delay detection results in the transmission channel capacity table, calculating the basic stability margin value and delay fluctuation characteristics of each channel, setting the maximum tolerable fluctuation range, and thus determining the stability margin threshold. S5: Perform anomaly tracing and parameter revision on the runtime evaluation result set, and update the joint policy package.

[0054] S5.1: Extract the semantic name of the device identification operation status, timestamp point value and strategy evaluation index from the operation evaluation results, and identify the timestamp interval, point identifier and channel identifier corresponding to the abnormal location; Furthermore, the equipment identifier, semantic name of the operating status, timestamp, location value, and strategy evaluation index are extracted from the operation evaluation results one by one. These are grouped by equipment identifier and semantic name of the operating status, and the timestamps are sorted sequentially to form a timestamp sequence. Based on the timestamp sequence, location values ​​are aligned one by one, and the difference between location values ​​corresponding to adjacent timestamps is calculated and statistically analyzed to obtain the normal fluctuation reference range for location values. Simultaneously, based on the timestamp sequence, strategy evaluation indexes are aligned one by one, and the difference and fluctuation amplitude of strategy evaluation indexes corresponding to adjacent timestamps are calculated. The difference and fluctuation amplitude of strategy evaluation indexes are statistically analyzed to obtain the normal fluctuation reference range for strategy evaluation indexes. When the difference in location values ​​exceeds the normal fluctuation reference range, the corresponding timestamp is marked as an abnormal timestamp. When the difference in strategy evaluation indexes exceeds the normal fluctuation reference range, the corresponding timestamp is also marked as an abnormal timestamp. The corresponding location identifier and channel identifier within the timestamp interval are located to ensure that each abnormal event can be clearly associated with a specific location and channel. The timestamp interval, location identifier, and channel identifier for each abnormal event are recorded.

[0055] S5.2: Based on the timestamp interval, location identifier and channel identifier, retrieve the consistency fusion evidence chain, extract the conflict adjudication record, and obtain the adjudication result and triggering conditions; Furthermore, based on the timestamp range, location identifier, and channel identifier, the records in the consistency fusion evidence chain are queried, and the timestamps in each record are checked to see if they are within the specified timestamp range. At the same time, the location identifier and channel identifier are matched. When a matching record is found, the conflict resolution result and trigger condition fields in each record are extracted. Based on the trigger condition, it is determined whether an anomaly has been triggered or a resolution is required. The resolution result and trigger condition are recorded together to obtain the resolution result and trigger condition.

[0056] It should be noted that the triggering condition refers to the triggering level condition and triggering edge condition written into the binding entry of the state point semantic mapping table. It is used to limit the point value corresponding to the point identifier to reach and maintain the target level state within the continuous acquisition cycle before locking the stable point value. The triggering edge condition is used to limit the direction of change of the stable point value from the previous stable point value to the current stable point value. Only after the target edge type is met can the edge be determined and written into the state acquisition data frame.

[0057] S5.3: Based on the adjudication results and triggering conditions, perform parameter revisions on the sampling period, change threshold, point reliability level, and channel stability margin threshold, and generate parameter revision results; The adjudication results are aggregated according to point identifiers and channel identifiers, and the revision scope is determined by the timestamp interval in the triggering conditions. Within the timestamp interval, the distribution of retained point values ​​and the distribution of removed point values ​​are statistically analyzed, and the revision criteria are generated by combining the trend of strategy evaluation indicators. When the point value corresponding to the point identifier is frequently triggered and accompanied by multiple conflict adjudications, the sampling period and change threshold are revised. At the same time, when the point value corresponding to the point identifier is continuously removed in the conflict adjudication, the point reliability level is downgraded, and when it is continuously retained in the conflict adjudication, the point reliability level is upgraded. When the conflict adjudication associated with the channel identifier is concentrated and accompanied by dense channel stability margin threshold triggering records, the channel stability margin threshold is revised. The revised values ​​of the sampling period, change threshold, point reliability level, and channel stability margin threshold are written into the parameter revision results to generate parameter revision results.

[0058] S5.4: Write the parameter results into the federated policy package and update the version information to generate an updated federated policy package.

[0059] Furthermore, after importing the parameter revision results and the joint strategy package, the sampling period revision value, change threshold revision value, point reliability level revision value, and channel stability margin threshold revision value are read one by one from the parameter revision results, and an index is created and written according to the point identifier and channel identifier. Then, the joint strategy package is parsed and the fields of the collection point parameters, stability margin parameter set, and joint strategy package version information are located. The sampling period revision value and change threshold revision value are merged and written into the point identifier table corresponding to the collection point parameters, and the point reliability level revision value is written into the point identifier table corresponding to the collection point parameters. At the same time, the channel stability margin threshold revision value is written into the channel identifier table corresponding to the stability margin parameter set, and simultaneously written into the joint strategy package list field. Field integrity verification and data type consistency verification are performed on the collection point parameters and stability margin parameter set, and the integrity verification value of the joint strategy package is recalculated and verified. After the verification passes, the version information of the joint strategy package is updated and solidified and exported to generate the updated joint strategy package.

[0060] In summary, this invention establishes a Modbus TCP link from the front-end acquisition unit to the local area network server based on Modbus image files, performs multi-channel selection and switching, and combines monitoring control and data acquisition methods to ensure more stable and efficient transmission of device status data under different network conditions. By performing consistency fusion and conflict resolution on the uploaded message stream, channel scheduling logs, and status point semantic mapping table, it can strictly match and analyze the data stream, identify anomalies, and ensure data consistency, thereby effectively supporting real-time monitoring and anomaly tracing of device status.

[0061] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for acquiring and managing device status supporting multiple transmission modes, characterized in that: include, By calibrating the acquisition points and setting the acquisition point parameters, a point register mapping table is generated. At the same time, connectivity and latency detection are performed on multiple transmission channels, and a stability margin parameter set and transmission channel capability table are initialized to generate a state point semantic mapping table and a joint strategy package. Obtain the Modbus image file; Based on the Modbus image file, a Modbus TCP link is established from the front-end acquisition unit to the local area network server. After multi-channel selection and switching according to the stability margin parameter set, the records are uploaded, generating the uploaded message stream and channel scheduling log. The uploaded message stream, channel scheduling log, and status point semantic mapping table are fused for consistency and conflict resolution to generate an operational evaluation result set. Perform anomaly tracing and parameter revision on the operational evaluation result set, and update the joint policy package.

2. The device status acquisition and management method supporting multiple transmission modes as described in claim 1, characterized in that: The process of generating a point register mapping table by calibrating and setting the point parameters is as follows: By setting the sampling period, change threshold and data type, and writing the point identifier associated record, the parameters of the collection point can be obtained; Based on the collected point parameters, the data types are bound to the register addresses in the order of the point identifiers, and then the uniqueness is verified and solidified to generate a point register mapping table.

3. The device status acquisition and management method supporting multiple transmission modes as described in claim 2, characterized in that: The simultaneous connectivity and delay detection of multiple transmission channels, and the initialization of the stability margin parameter set and transmission channel capacity table, are described in the following steps. Read the register range and payload size from the point register mapping table, and perform connectivity and delay detection to generate a transmission channel capability table; Calculate the basic stability margin value of each transmission channel in the transmission channel capacity table. Based on the connectivity detection results and delay detection results, statistically analyze the delay fluctuation amplitude and delay fluctuation frequency according to the time series, obtain the delay fluctuation characteristics, and write them into the stability margin parameter set.

4. The device status acquisition and management method supporting multiple transmission modes as described in claim 3, characterized in that: The specific steps for generating the semantic mapping table of state points and the joint policy package are as follows: Based on the point identifier and the semantics of the running status, a binding relationship is established, and the trigger level condition and trigger edge condition are written into the binding table entry and then fixed to generate a state point semantic mapping table. The data acquisition point parameters, point register mapping table, transmission channel capability table, stability margin parameter set, and status point semantic mapping table are encapsulated into a joint strategy package.

5. The device status acquisition and management method supporting multiple transmission modes as described in claim 4, characterized in that: The specific steps for obtaining the Modbus image file are as follows. Electrical signals are acquired based on the joint strategy package, and changes in the electrical signals are obtained. The electrical signal changes are processed for de-jittering and edge determination, and the point value corresponding to the point identifier is generated. After writing the timestamp, the status acquisition data frame is obtained. Based on the status acquisition data frame, the register address and data type corresponding to the point identifier are extracted from the point register mapping table, and the point value is written into the register address and then solidified into a Modbus image file.

6. The device status acquisition and management method supporting multiple transmission modes as described in claim 5, characterized in that: The process involves establishing a Modbus TCP link between the front-end acquisition unit and the local area network server based on the Modbus image file, and then uploading records after selecting and switching multiple channels according to the stability margin parameter set. The specific steps are as follows: Establish a Modbus TCP connection for the local area network server based on the Modbus image file and the transmission channel capability table. Based on ModbusTCP connection and stability margin parameter set, the stability margin of multiple transmission channels is calculated, and the main channel and backup channel of multiple transmission channels are divided according to the stability margin threshold.

7. The device status acquisition and management method supporting multiple transmission modes as described in claim 6, characterized in that: The specific steps for generating the uploaded message stream and channel scheduling log are as follows: Read the upload records of the message stream that has been uploaded to the main channel, and update the stability margin parameter set during the upload record process; When the updated stability margin parameter set is lower than the channel stability margin threshold, the system switches to the backup channel, records the switching time and channel identifier, and generates a channel scheduling log.

8. The device status acquisition and management method supporting multiple transmission modes as described in claim 7, characterized in that: The specific steps for generating the runtime evaluation result set are as follows: Extract the device identifier, location identifier, timestamp, and location value from the uploaded message stream to generate a semantic name association record for the running status; Align the timestamps of the records associated with the semantic names of the running status with the device identifier and the semantic names of the running status to generate a set of records to be merged; Based on the timestamps in the set of records to be merged, the channel scheduling logs are read and matched with the switching time to generate records associated with effective time windows and channel identifiers; The effective time window, channel identifier associated records, and the set of records to be merged are subjected to consistency fusion and conflict resolution to generate a consistency fusion evidence chain. Extract the timestamp and channel identifier of the consistency fusion evidence chain, and combine the switching frequency and channel stability margin threshold triggering status with the channel scheduling log statistics, and summarize them into an operation evaluation result set.

9. The device status acquisition and management method supporting multiple transmission modes as described in claim 8, characterized in that: The specific steps for performing anomaly tracing on the operational evaluation result set are as follows: Extract the semantic name of the device's operating status, timestamp point value, and strategy evaluation index from the operation evaluation results, and identify the timestamp interval, point identifier, and channel identifier corresponding to the abnormal location. Based on the timestamp interval, location identifier, and channel identifier, a consistent fusion evidence chain is retrieved, and conflict adjudication records are extracted to obtain the adjudication results and triggering conditions.

10. The device status acquisition and management method supporting multiple transmission modes as described in claim 9, characterized in that: The specific steps for updating the federated policy package are as follows: Based on the ruling and triggering conditions, parameters such as sampling period, change threshold, point reliability level and channel stability margin threshold are revised, and parameter revision results are generated. Write the parameter results into the federated policy package and update the version information to generate an updated federated policy package.

Images