Data processing method and industrial system

Abstract

The embodiment of the invention discloses a data processing method and an industrial system, and relates to the technical field of industrial computing. The method is applied to an industrial system, and the industrial system comprises a computing device. The method comprises the following steps: acquiring equipment information of first industrial equipment; generating a first protocol mapping rule based on the type of the first industrial protocol and the interface description information; wherein the first protocol mapping rule is different from a second protocol mapping rule corresponding to the type of the second industrial protocol; and obtaining source data, and converting the source data into a target format based on the first protocol mapping rule to obtain corresponding target data. In the application, the first protocol mapping rule is generated based on the type of the first industrial protocol and the interface description information, and the new protocol mapping rule is dynamically generated in response to the newly accessed first industrial protocol in the industrial system, so that dynamic interoperation of multiple protocol devices is realized, the protocol adaptation efficiency is improved, and the user experience is improved. And the overall flexibility of the system is improved.

Description

Technical Field

[0001] This application relates to the field of industrial computing technologies, and in particular, to a data processing method and an industrial system. Background Art

[0002] With the rapid development of intelligent manufacturing and industrial Internet, the demand for interconnection (industrial protocol interoperability) between devices in industrial systems is increasing day by day. This industrial protocol interoperability aims to promote efficient collaboration between different industrial devices to improve the overall production efficiency and resource utilization level.

[0003] However, in actual operation, due to the diversity of protocol standards adopted by industrial devices, such as Modbus, Profibus, OPC UA, EtherCAT, etc., each protocol has its specific data structure and transmission method, resulting in serious protocol difference problems. These protocol difference problems are particularly prominent in complex industrial environments. The difference in protocols between industrial devices has become an obstacle to data communication (interoperability), severely restricting the collaboration ability between industrial devices and the efficiency of system integration. Summary of the Invention

[0004] A data processing method and an industrial system provided by this application achieve dynamic generation of protocol mapping rules to realize dynamic interoperability of multi-protocol devices, improve the protocol adaptation efficiency, and improve the overall flexibility of the system.

[0005] To achieve the above object, this application adopts the following technical solutions:

[0006] In a first aspect, an embodiment of this application provides a data processing method applied to an industrial system. The industrial system includes a computing device. The method includes: obtaining device information of a first industrial device; the device information of the first industrial device includes: the type of a first industrial protocol and interface description information, where the type of the first industrial protocol is different from the types of second industrial protocols of all second industrial devices connected to the industrial system; generating a first protocol mapping rule based on the type of the first industrial protocol and the interface description information; where the first protocol mapping rule is different from the second protocol mapping rule corresponding to the type of the second industrial protocol; obtaining source data, and converting the source data into a target format based on the first protocol mapping rule to obtain corresponding target data. In the embodiment of this application, a first protocol mapping rule is generated based on the type of the first industrial protocol and the interface description information, and the first protocol mapping rule is a mapping rule different from the existing second protocol mapping rules in the industrial system. That is, the embodiment of this application realizes dynamic generation of a new protocol mapping rule in response to a newly connected first industrial protocol in the industrial system to realize dynamic interoperability of multi-protocol devices, improve the protocol adaptation efficiency, and improve the overall flexibility of the system.

[0007] In a possible implementation, the interface description information is used to describe the rules and formats for communication via the first industrial protocol; match the corresponding mapping rule template based on the type of the first industrial protocol; match and map the rules and formats for communication via the first industrial protocol described by the interface description information into the corresponding mapping rule template to generate the first protocol mapping rule. In the embodiments of the present application, the corresponding mapping rule template is matched according to the type of the industrial protocol, and then the relevant information in the interface description information is added to the protocol mapping template to quickly generate the corresponding protocol mapping rule, thereby realizing the dynamic generation of the protocol mapping rule, solving the problem that it is difficult to adapt to dynamic requirements relying on a pre-determined static mapping rule library, supporting the dynamic access of industrial devices with multiple industrial protocols, and being able to meet the requirements for high-efficiency interoperability in a modern multi-protocol and multi-device industrial environment.

[0008] In a possible implementation, perform a consistency check on the first protocol mapping rule to verify whether the first protocol mapping rule conforms to the pre-defined rule specification; when the consistency check on the first protocol mapping rule passes, store the first protocol mapping rule. Through the consistency check, the quality of the mapping rule is guaranteed, thereby supporting the stable operation of the industrial system and the high-efficiency data processing ability.

[0009] In a possible implementation, when receiving the update information reported by the third industrial device, in response to the update information, obtain the device information of the third industrial device; generate a third protocol mapping rule based on the type of the third industrial protocol and the interface description information to implement data format conversion based on the third protocol mapping rule; wherein, the third protocol mapping rule is: the protocol mapping rule that is the updated version of the first protocol mapping rule or the second protocol mapping rule. It can respond to the update information and dynamically generate the updated protocol mapping rule (i.e., the third protocol mapping rule), realizing the dynamic update of the protocol mapping rule, ensuring that as the business requirements change and technology develops, the protocol mapping rule can remain efficient and accurate, thereby ensuring the correctness of the data processing logic. And after generating the third protocol mapping rule, directly apply the third protocol mapping rule to implement the corresponding data format conversion, that is, directly apply the dynamically updated protocol mapping rule, greatly shortening the response time for industrial protocol updates, further improving the protocol adaptation efficiency, and thus improving the adaptability and response speed of the entire industrial system.

[0010] In a possible implementation, the first protocol mapping rule includes: a first uplink mapping rule, where the source data includes: first industrial protocol data; obtaining the first industrial protocol data reported by the first industrial device, and based on the first uplink mapping rule, converting the first industrial protocol data into a standardized format. In the embodiments of the present application, data standardization operations can be implemented, so as to facilitate the subsequent conversion of the standardized data into other formats (formats used by the upper-layer system or target industrial protocol formats), which can greatly reduce the complexity of cross-device data circulation, improve the communication efficiency, and further enhance the interoperability of the industrial system.

[0011] In a possible implementation, the first protocol mapping rule includes: a first downlink mapping rule, where the source data includes: standardized data; obtaining the standardized data, and based on the first downlink mapping rule, converting the standardized data into the first industrial protocol format.

[0012] In a possible implementation, the industrial system includes: multiple computing devices, and each computing device is a blockchain node in the blockchain network; storing the first protocol mapping rule in the blockchain network in the form of a smart contract. The embodiments of the present application construct a decentralized blockchain network, thereby avoiding the limitations of the centralized architecture of the industrial system in the prior art. Specifically, it eliminates the bottleneck and single-point failure risk of the centralized middleware, and improves the reliability and scalability of the industrial system, adapts to the industrial scenario with rapid growth in the number of devices, and further meets the requirements for high-efficiency interoperability in the modern multi-protocol and multi-device industrial environment. And the first protocol mapping rule is stored in the blockchain network in the form of a smart contract. Similarly, the second protocol mapping rule is also stored in the blockchain network in the form of a smart contract. And the smart contract can also be synchronized to all blockchain nodes in the blockchain network to ensure the consistency of the protocol mapping rules in the blockchain network.

[0013] In a possible implementation, call the smart contract corresponding to the first protocol mapping rule to enable the corresponding smart contract to execute the conversion of the source data into the target format to obtain the corresponding target data. The reliability of the execution of the protocol mapping rule is ensured through the smart contract, that is, the reliability and consistency of the data format conversion (data processing) process. And once the smart contract is triggered, it is automatically executed according to the first protocol mapping rule without manual intervention, thereby greatly improving the efficiency and accuracy of data processing.

[0014] In a possible implementation, transaction information on data conversion and rule changes in the industrial system is recorded and stored in the blockchain network in the form of a log; each record in the log includes a corresponding timestamp. Storing the transaction information in the blockchain network in the form of a log provides a solid basis for subsequent auditing and tracing, ensuring data transparency and immutability. Moreover, storing the transaction information in the blockchain network in the form of a log can also achieve distributed storage, enhancing data reliability and security, and ensuring the continuity and stability of the industrial system; furthermore, each record includes a corresponding timestamp, which can support high-precision historical data query and responsibility determination.

[0015] In a possible implementation, identity registration is performed on the first-access industrial devices. A unique identity identifier is generated for each industrial device through the blockchain, and the identity registration and authorization are completed using the public-private key mechanism, ensuring that only verified industrial devices can access the blockchain network and participate in data interaction (data processing) or smart contract execution, thereby guaranteeing the security and reliability of the entire industrial system and preventing unauthorized access.

[0016] In a second aspect, an embodiment of the present application provides an industrial system, including: a first industrial device, a second industrial device, and a computing device. Among them, the types of industrial protocols of the first industrial device and the second industrial device are different, and the computing device is used to implement the data processing method in the first aspect and its various possible implementation manners.

[0017] In a third aspect, an embodiment of the present application provides a computing device, including: a processor and a memory: the processor is coupled to the memory; the memory is used to store computer program instructions; the processor is used to execute the computer program instructions stored in the memory to implement the data processing method in the first aspect and its various possible implementation manners.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions run on a computing device, the computing device is enabled to implement the data processing method in the first aspect and its various possible implementation manners.

[0019] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes computer program instructions. When the computer program instructions run on a computing device, the computing device is enabled to implement the data processing method in the first aspect and its various possible implementation manners. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic structural diagram of the architecture of an industrial system provided by an embodiment of the present application;

[0021] Figure 2 Schematic diagram of a structure of an edge layer provided by an embodiment of the present application;

[0022] Figure 3 Example diagram of a data transmission path implemented by the edge layer provided by an embodiment of the present application;

[0023] Figure 4 Schematic diagram of a structure of a mapping layer provided by an embodiment of the present application;

[0024] Figure 5 Schematic diagram of a structure of a blockchain layer provided by an embodiment of the present application;

[0025] Figure 6 Schematic diagram of a process flow of a data processing method provided by an embodiment of the present application;

[0026] Figure 7 Example diagram of a process flow of data interaction between a source device and a target device provided by an embodiment of the present application;

[0027] Figure 8 Schematic diagram of an update process of a protocol mapping rule provided by an embodiment of the present application;

[0028] Figure 9 Schematic diagram of a registration process of an industrial device provided by an embodiment of the present application;

[0029] Figure 10 Example diagram of a scenario of an industrial system provided by an embodiment of the present application. Detailed implementation manners

[0030] Terms such as "first", "second", and "third" in the description, claims, and drawings of the present application are used to distinguish different objects, rather than to limit a specific order.

[0031] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0032] For the sake of clear and concise description of the following embodiments, a brief introduction to the related technologies is given first:

[0033] Industrial Internet: It refers to a new industrial form that deeply integrates advanced information technology (IT), communication technology (CT), and operational technology (OT) and applies them to multiple industries such as manufacturing, energy, and transportation. Through technologies such as the Internet of Things, big data analysis, cloud computing, and artificial intelligence, it realizes the comprehensive interconnection and intelligent management of devices, production lines, factories, supply chains, and products.

[0034] Industrial equipment: It refers to mechanical equipment, electronic equipment, software systems, etc. used in manufacturing, process industries, and other industrial fields. For example: sensors, which are used to detect physical quantities (such as temperature, pressure, position, etc.) and convert this information into electrical signals; actuators, which are used to perform specific actions according to the received instructions; controllers, which are used to receive data from sensors and control the actions of actuators based on preset logic, such as PLC (Programmable Logic Controller), DCS (Distributed Control System).

[0035] Industrial Protocol: It is the standardized rules and specifications used in industrial automation and control systems to achieve communication between industrial devices such as devices, sensors, controllers, and actuators. It defines how to transmit data between different industrial devices, including data formats, transmission rates, error detection methods, etc. The core goal of the industrial protocol is to ensure that devices of different manufacturers and different types can work together efficiently and reliably in a complex industrial environment, supporting real-time control, data acquisition, status monitoring, and system integration of the production process, that is, devices with the same industrial protocol but from different manufacturers and with different types of functions can cooperate efficiently and reliably in a complex industrial environment.

[0036] The relationship between industrial equipment and industrial protocols can be simply understood as: industrial equipment is the basic unit for realizing automated production and control, while industrial protocols are the "bridges" connecting these units.

[0037] With the rapid development of intelligent manufacturing and the industrial Internet, the types of industrial protocols are increasing day by day. In a more complex industrial environment, various industrial devices may adopt different industrial protocols. Since each industrial protocol has its specific data structure and transmission method, this difference between industrial protocols constitutes the main obstacle to achieving efficient data communication between industrial devices under different industrial protocols.

[0038] A data processing method provided by an embodiment of the present application includes: obtaining device information of a first industrial device; generating a first protocol mapping rule based on the type and interface description information of a first industrial protocol, where the first protocol mapping rule is different from a second protocol mapping rule, and the second protocol mapping rule is a protocol mapping rule corresponding to the type of a second industrial protocol; obtaining source data, and converting the source data into a target format based on the first protocol mapping rule to obtain corresponding target data. In the embodiment of the present application, it is realized that in response to a newly accessed first industrial protocol in an industrial system, a new protocol mapping rule is dynamically generated, without relying on a predetermined static mapping rule library, so as to realize dynamic interoperability of multi-protocol devices, improve protocol adaptation efficiency, and improve the overall flexibility of the industrial system. Further, it is possible to dynamically generate protocol mapping rules corresponding to newly accessed industrial devices or new industrial protocols, solve the problem that it is difficult to adapt to dynamic requirements relying on a predetermined static mapping rule library, support dynamic access of industrial devices with multiple industrial protocols, and meet the requirements for high-efficiency interoperability in a modern multi-protocol and multi-device industrial environment.

[0039] The following combines Figures 1 - 10 to introduce in detail a data processing method provided by an embodiment of the present application.

[0040] First, combine Figures 1 - 5 to introduce in detail an architecture of an industrial system provided by an embodiment of the present application.

[0041] Figure 1 As shown, an architecture of an industrial system provided by an embodiment of the present application includes three layers, which respectively include from the bottom layer to the top layer: an edge layer, a mapping layer, and a blockchain layer.

[0042] In the embodiment of the present application, the industrial system includes: a computing device, and the edge layer, the mapping layer, and the blockchain layer are all deployed on the computing device, so that the computing device can realize the functions of the edge layer, the mapping layer, and the blockchain layer. Further, the industrial system includes: multiple computing devices on which the edge layer, the mapping layer, and the blockchain layer are deployed, so as to provide an industrial system with a decentralized framework, thereby avoiding the limitations of the centralized framework, that is, avoiding the risk of single-point failure and performance bottlenecks, so as to meet the requirements for high-efficiency interoperability in a modern multi-protocol and multi-device industrial environment.

[0043] Further, the architecture of the industrial system further includes an application layer, which directly serves end users or business processes, includes various types of systems and application programs, and mainly complexly processes specific business logics, provides user interfaces, and interacts with users. And the application layer can be deployed on one / each computing device included in the industrial system, or distributedly deployed on multiple computing devices included in the industrial system.

[0044] For a computing device included in an industrial system, the functions of the edge layer, the mapping layer, and the blockchain layer will be introduced in detail below in conjunction with Figures 2 - 5 , and the functions of the edge layer, the mapping layer, and the blockchain layer will be introduced in detail.

[0045] Among them, the edge layer is the bottom layer of the industrial system architecture, directly interacting with industrial devices, and is used to implement multi-protocol device access and management, real-time protocol parsing and data standardization, and two-way communication support.

[0046] The edge layer is responsible for multi-protocol device access and management, that is, it supports the plug-and-play of multiple industrial protocol devices such as Modbus, OPC UA, EtherCAT, etc., and realizes the access (registration) and dynamic management of industrial devices. Further, the edge layer can obtain the device information of the industrial devices newly connected to the industrial system, and the device information includes: the type of industrial protocol and the interface description information.

[0047] The edge layer can automatically identify and parse multiple industrial protocols (such as Modbus, OPC UA, EtherCAT, etc.), and convert heterogeneous device data (that is, data of different industrial protocols) into a unified format (that is, a standardized data format) to achieve real-time protocol parsing and data standardization, so as to provide standardized input for the upper mapping layer.

[0048] The edge layer provides two-way communication support, that is, it collects the industrial protocol data of industrial devices, converts the industrial protocol data into a format that can be used by upper-layer applications, and uploads it to the topmost application layer; it also supports parsing upper-layer instructions into a format of industrial protocols (that is, recognizable by industrial devices) and sending them to industrial devices.

[0049] In a possible implementation, the edge layer is also used to implement real-time data adaptation and conversion, lightweight edge computing, security communication guarantee, etc.

[0050] The edge layer can obtain protocol mapping rules in real time, realize data format conversion between industrial devices of different industrial protocols point-to-point, and realize data communication between industrial devices of different industrial protocols point-to-point, so as to realize real-time data adaptation and conversion.

[0051] The edge layer can perform lightweight processing on data at the device end, such as: data preprocessing, simple logical operations, etc., so as to reduce the overall latency of the industrial system and reduce the upper-layer load in the architecture of industrial protocol interoperability.

[0052] The edge layer can ensure the security of the connected industrial devices and the security of data interaction through identity authentication, encrypted transmission, and behavior monitoring, so as to achieve security communication guarantee.

[0053] For easy understanding, the module structure of the edge layer provided by the embodiments of the present application will be introduced in detail below in conjunction with Figure 2 , and the module structure of the edge layer provided by the embodiments of the present application will be introduced in detail.

[0054] As Figure 2 shown, the edge layer provided by the embodiment of the present application includes the following modules: a protocol parsing module, a real-time adaptation module, an edge computing module, and a secure access module.

[0055] Among them, the protocol parsing module is used to obtain the device information of industrial devices. The device information includes: the type of industrial protocol and the interface description, and convert the industrial protocol data into a standardized data format, that is, convert the industrial protocol data into a preset system unified format. And the protocol parsing module not only supports the recognition and parsing of mainstream industrial protocols (such as Modbus, OPC UA, EtherCAT, etc.), but also can extend the manufacturer's private protocols.

[0056] In the first aspect, the protocol parsing module is used to automatically identify / judge the industrial protocol used by industrial devices through industrial device detection and protocol library matching, and obtain the device information of industrial devices.

[0057] Among them, the device information of industrial devices includes: the type of industrial protocol used by industrial devices, and the interface description information of industrial devices. The interface description information of industrial devices includes: the definition of the industrial protocol used by industrial devices (that is, used to describe the rules and formats for communication through this industrial protocol) and the communication method.

[0058] Specifically, the protocol parsing module uses network scanning or physical interface detection to identify industrial devices accessing the industrial system and determine the communication method of industrial devices to achieve industrial device detection; and the protocol parsing module compares the data frames of industrial devices captured / collected with the definitions in the built-in protocol library to automatically identify / judge the type of industrial protocol used by industrial devices, and obtain the definition of this industrial protocol from the built-in protocol library, so as to obtain the device information of industrial devices.

[0059] Regarding the protocol parsing module using network scanning or physical interface detection to identify and determine the communication method of industrial devices:

[0060] Among them, network scanning refers to sending specific data packets to each IP address in the target network and analyzing the returned data to collect information, so as to identify the accessed industrial devices and determine their communication methods. For example: ARP (Address Resolution Protocol) scanning and DHCP listening. In the industrial Internet environment, network scanning is mainly used to discover / identify devices using Ethernet-based industrial protocols, such as Modbus TCP / IP, BACnet / IP, etc. Among them, physical interface signal detection refers to directly connecting to a physical communication interface (such as RS-485, RS-232, etc.) and identifying the accessed industrial devices and determining their communication methods through listening or interactive communication.

[0061] Among them, the communication method of industrial devices mainly refers to the physical layer information of industrial devices, which can also be simply understood as the connection method. In the industrial Internet, the physical layer defines the electrical, mechanical, process, and functional characteristics of data transmission, and these characteristics determine how devices are connected and communicate through physical media. Specifically, the communication methods of industrial devices include: interface types (such as Ethernet interfaces, serial interfaces), transmission media (such as twisted pairs, coaxial cables, optical fibers, wireless transmission), electrical characteristics (such as voltage levels, signal waveforms), etc.

[0062] As can be seen from the above description, the parsing protocol module in the edge layer uses network scanning or physical interface detection to identify the accessed industrial devices and determine their communication methods, which can ensure that industrial devices can be correctly connected to the industrial system and ensure efficient and stable data interaction, so that the edge layer can achieve multi-protocol device access and management.

[0063] Regarding that the protocol parsing module identifies the type of industrial protocol used by industrial devices and obtains the definition of this industrial protocol from the built-in protocol library based on the definitions of each industrial protocol in the built-in protocol library:

[0064] Among them, the protocol parsing module has a built-in protocol library, which can be called the built-in protocol library. The built-in protocol library contains the definitions of multiple industrial protocols. The definition of each industrial protocol usually includes: protocol header information (such as start flag, length field), data frame format (such as the arrangement order and meaning of fields), command dictionary (function codes of different instructions and their parameters), and other key elements.

[0065] In a possible implementation, the built-in protocol library in the protocol parsing module adopts a plug-in protocol library management method, that is, each industrial protocol in the built-in protocol library exists as an independent plug-in. And when it is necessary to add the definition of a new industrial protocol to the built-in protocol library, the parsing rule file of the new industrial protocol can be defined and dynamically loaded as a plug-in, and then the definition of the new industrial protocol can be added to the built-in protocol library without modifying the existing system architecture or code, which can greatly improve the flexibility and adaptability of the system, enable the rapid expansion of industrial protocols, and thus quickly respond to new market demands and technological changes. Among them, the parsing rule file of the industrial protocol usually contains the basic information of the industrial protocol (such as name, version), header format, data frame structure, command fields, etc. According to the complexity of the protocol, it may also include specific encoding / decoding logic.

[0066] After the protocol parsing module recognizes the access of an industrial device and determines its communication method, the protocol parsing module compares the data frame of the industrial device with the definitions in the built-in protocol library, that is, it compares / matches based on the data frame features (such as fixed preambles, specific command codes or response patterns) with the definitions in the built-in protocol library. Once a matching item is found in the built-in protocol library, it determines that the industrial protocol of the matching item is the type of industrial protocol used by the industrial device, and obtains the definition of the industrial protocol from the built-in database, so as to obtain the device information of the industrial device.

[0067] In a second aspect, the protocol parsing module is also used to convert the industrial protocol data reported by the industrial device into a standardized format through the corresponding protocol mapping rules, to obtain standardized data, that is, to convert the industrial protocol data into the system unified format.

[0068] The protocol parsing module captures / collects the industrial protocol data reported by the industrial device according to the communication interface type recorded in the communication method of the industrial device, and converts the industrial protocol data into a standardized format through the corresponding protocol mapping rules, to obtain standardized data.

[0069] In a possible implementation, the standardized format is the JSON format, that is, the key-value pair format: {key: value}, and the industrial protocol data reported by the industrial device is converted into the key-value pair format to obtain standardized data. For example: the standardized data is: {"temperature": 36.5, "current": 5.2}, which means that the value of the temperature is 36.5, and the unit may be Celsius (°C) or Fahrenheit (°F); the value of the current is 5.2, that is, the current intensity is 5.2, and the unit may be Ampere (A).

[0070] In a third aspect, the protocol parsing module supports two-way communication, that is, the protocol parsing module is not only used to parse the data from the industrial device (that is, support converting the industrial protocol data into a standardized data format to obtain standardized data for the upper layer of the architecture to use); but also used to receive instructions from the upper layer and convert the instructions into an industrial protocol format that the industrial device can recognize, so as to send the communication frame to the corresponding industrial device.

[0071] The protocol parsing module receives control instructions from the upper layer (such as a cloud platform or a local control system). The control instructions may be used to adjust device working parameters (such as setting the target temperature of a temperature controller), request to perform specific operations (such as starting an industrial device), etc., and the protocol parsing module extracts control instruction information from the control instructions; the protocol parsing module converts the control instructions into an adapted communication frame based on the definition of the industrial protocol (abbreviated as the target industrial protocol) of the target industrial device corresponding to the control instructions in the built-in protocol library, and sends the communication frame to the target device through the interface of the target industrial device.

[0072] Based on the command fields and parameter rules of the target industrial protocol in the built-in protocol library, the protocol parsing module converts the control instructions into adapted communication frames and sends the communication frames to the target device through the interface of the target industrial device.

[0073] Among them, each industrial protocol has a corresponding command dictionary and parameter rules. The command dictionary defines a series of function codes. Each function code corresponds to a specific operation or request type. For example, in the command dictionary of the Modbus RTU / TCP protocol: 0x01 indicates reading coil status, 0x03 indicates reading holding registers, 0x06 indicates writing a single register, etc.; the parameter rules define how to use these function codes and the accompanying data formats. For each function code, additional information may need to be specified, such as the starting address, quantity, etc.

[0074] In a possible implementation, based on the target industrial protocol, a suitable frame structure is determined. According to the command fields and parameter rules of the target industrial protocol, the control instruction information carried by the control instruction is filled into the content of the frame, including but not limited to specifying the device address, function code, any necessary data fields, and check bits, etc., to obtain a communication frame adapted to the target industrial protocol. The constructed communication frame is sent to the target industrial device through an appropriate physical interface.

[0075] Exemplarily, assume there is an industrial device which is a temperature control device. It uses the Modbus RTU protocol and needs to be set to a new target temperature of 36.5 °C. The upper-layer system sends a control instruction containing this new set value to the protocol parsing module in the edge layer. The protocol parsing module receives the control instruction and, according to the command fields and parameter rules of the Modbus RTU protocol in the built-in protocol library, converts the control instruction into an adapted communication frame. This communication frame contains the address of the temperature control device, the function code for the write operation, the address of the target register, and the binary representation of the target temperature after the change, and sends the adapted communication frame to the temperature control device through the interface of the temperature control device.

[0076] Among them, the real-time adaptation module is used for real-time adaptation and data format conversion between industrial devices of different industrial protocols, mainly for real-time adaptation and data format conversion between data of different industrial protocols in a point-to-point manner, to ensure the coordinated operation of point-to-point industrial protocol devices.

[0077] In the first aspect, the real-time adaptation module is used to dock with the mapping layer through an interface, obtain the protocol mapping rules in real time, and locally cache the frequently used protocol mapping rules to avoid repeated requests and improve the adaptation speed.

[0078] Among them, the protocol mapping rule (which can also be called the adaptation rule) defines how to convert data in one format into another format to facilitate data communication between different protocols. The protocol mapping rule includes: input format, output format, and conversion logic. The input format (i.e., the source format) describes the structure and encoding method of the source data; the output format (the target format) describes the structure and encoding method of the target data; the conversion logic describes how to convert the data in the input format into the output format, that is, describes how to convert the source data into the target data, for example: unit conversion, field splicing, etc.

[0079] Furthermore, the real-time adaptation module is also used to execute the protocol mapping rule to convert the source data (source industrial protocol data) into the target industrial protocol format (abbreviated as the target format), that is, to obtain the communication frame / data that conforms to the target device (abbreviated as the target data), so as to send the target data to the target device through the interface of the target device.

[0080] In a possible implementation, the real-time adaptation module adopts an optimized adaptation algorithm to execute the protocol mapping rule to convert the source data into the target format and obtain the target data. The optimized adaptation algorithm can reduce unnecessary calculations and avoid the impact of complex calculations on performance, thereby improving the efficiency of the real-time adaptation module in processing data conversion tasks.

[0081] In a possible implementation, a message queue (such as Kafka, MQTT, etc.) is adopted in the real-time adaptation module as the data channel, that is, the target data is sent to the target device through the message queue. The message queue can reduce the latency. For example, Kafka improves the efficiency through batch processing of messages, compressing network transmission, etc.; MQTT can maintain a relatively low latency due to its lightweight protocol characteristics. And the message queue supports asynchronous communication, which means that the sender (source device) and the receiver (target device) do not need to be online at the same time to complete the information exchange. This method reduces the waiting time in the direct request-response model, thereby further reducing the latency.

[0082] On the second aspect, the real-time adaptation module is also used to automatically detect the legality of the adaptation result, and record the abnormal event when an abnormality is discovered / detected, so as to store it in the blockchain network in the form of a log and report it to the upper layer. That is, after the real-time adaptation module executes the protocol mapping rule to convert the source data into the target format and obtains the target data, it automatically detects the legality of the target data (i.e., the adaptation result).

[0083] Specifically, the real-time adaptation module verifies the target data to ensure that it conforms to the expected format, range, and logical consistency. For example, it checks whether the temperature value is within a reasonable range (such as -50°C to 100°C), determines whether the data type of a certain field is correct, etc. The real-time adaptation module conducts an integrity check on the target data to ensure that all necessary data fields in the target data exist and are complete. For example, if a key piece of information is missing, the target data is considered illegal. The real-time adaptation module compares the consistency between the original data and the target data to ensure that no errors are introduced or important information is lost during the protocol format conversion process.

[0084] Specifically, when the real-time adaptation module detects an anomaly, it records the anomaly event in detail and stores it in the blockchain network in the form of a log. It can be simply understood as recording the information of the anomaly event in detail through the log, including but not limited to the occurrence time, specific devices or protocols involved, anomaly description, etc. And when an anomaly is detected, it reports to the upper layer to indicate that there is an anomaly during the real-time adaptation and data format conversion process of the real-time adaptation module. Exemplarily, the real-time adaptation module reports to the upper management system or relevant personnel through a preset notification mechanism to indicate that there is an anomaly in the protocol conversion.

[0085] Among them, the edge computing module is used to perform lightweight computing tasks at the device end, thereby reducing the overall system latency and the load on the upper-layer system, and thus improving the response speed and processing efficiency.

[0086] In the first aspect, the edge computing module is used to preprocess the data. The preprocessing includes but is not limited to: noise filtering, identifying and removing outliers or noise caused by signal jitter, etc.; data aggregation, summarizing the data according to a specific time window (such as 10 seconds), and calculating key metrics such as the maximum value, minimum value, and average value, which helps to reduce the amount of data to be transmitted while retaining valuable information.

[0087] Exemplarily, the edge computing module filters out the instantaneous temperature peak (such as 100°C) caused by electromagnetic interference, and statistics the maximum value (5.2MPa), minimum value (4.8MPa), and average value (5.0MPa) of the pressure sensor within 10 seconds.

[0088] It should be noted that the edge computing module can preprocess the raw data collected from industrial devices, and can also preprocess the standardized data obtained by converting the raw data into a standardized format.

[0089] In a second aspect, a rule engine is included in the edge computing module, which is used to perform simple logical operations (such as judgment of switch conditions) at the device end, avoiding frequent uploading of judgment tasks to the upper layer and reducing the pressure on the upper layer. Exemplarily, simple logical operation rules are set in the rule engine. For example, a warning is triggered when the temperature sensor detects that the temperature exceeds 30°C, and the light brightness is automatically adjusted when the ambient light intensity is lower than a certain level.

[0090] Specifically, the edge computing module can receive data from various industrial devices. The rule engine can determine whether the received data meets the simple logical operation rules. If it meets, corresponding actions are immediately executed, such as sending an alarm notification, adjusting device settings, etc., enabling simple logical operations to be completed at the device end, reducing the communication requirements with the upper-layer devices, and not waiting for the response of the upper-layer devices. Thus, while reducing latency, it also reduces the pressure on the upper layer.

[0091] In a third aspect, the edge computing module is used to locally record the corresponding data processing tasks (such as data acquisition, protocol format conversion / adaptation, etc.) performed on the edge layer for later maintenance and fault troubleshooting. Specifically, the edge computing module details all the acquired data and the error information that appears during the processing, and stores them in the corresponding local storage medium of the edge layer, so that the operation and maintenance personnel can obtain / access the acquired data stored locally and the error information that appears during the processing, thereby quickly locating and solving potential problems.

[0092] In a fourth aspect, when the industrial system includes multiple computing devices deployed with an edge layer, a mapping layer, and a blockchain layer, the edge computing module is used to support distributed computing. Distributed computing means splitting a large computing task into multiple small tasks and assigning them to multiple computing devices for simultaneous processing. After each computing device completes its own task, the results are aggregated to form the final task result. Since the edge computing module supports distributed computing, it can improve the processing speed of the industrial system, increase the throughput of industrial protocols, optimize resource utilization, and thus better cope with the impact brought by high-concurrency device access to support the access of high-concurrency devices.

[0093] Exemplarily, in an industrial Internet / industrial system, there are multiple industrial devices and multiple computing devices deployed with an edge layer, a mapping layer, and a blockchain layer. These computing devices can work together to jointly process data from a large number of industrial devices. When monitoring the data of numerous sensors on a large-scale production line, the data in different regions can be preliminarily processed by the nearest edge nodes.

[0094] Among them, the secure access module is used to ensure the security of the interaction between industrial devices and systems, preventing unauthorized access, data leakage, and tampering. The secure access module ensures the security of the interaction between industrial devices and systems through means such as identity authentication, encrypted communication, and behavior detection.

[0095] In the first aspect, the secure access module is used to authenticate the industrial devices accessing the system, ensuring that only authorized devices can access the industrial system (edge layer), and guaranteeing the authenticity and integrity of the data sent by these industrial devices, preventing unauthorized access and data tampering. Specifically, the secure access module is based on the distributed trust mechanism of the blockchain to ensure that the accessing industrial devices are authorized, and uses digital signature technology to verify the authenticity of the data sent by industrial devices.

[0096] Among them, the distributed trust mechanism of the blockchain refers to that the blockchain network stores device identity information, permission rules, operation records, etc. through decentralized distributed ledger technology, ensuring the security, transparency, and immutability of this information. And the distributed trust mechanism of the blockchain network does not rely on a single centralized server, that is, in the industrial system of this application embodiment, there are multiple computing devices deployed with an edge layer, a mapping layer, and a blockchain layer, and the data is distributed and stored in each node of the blockchain network (i.e., each computing device), so as to achieve higher security and reliability.

[0097] Among them, digital signature technology is a method based on public-key cryptography, used to verify the authenticity and integrity of data. In the embodiment of this application, each industrial device has a unique public-private key pair. The private key is securely stored by the industrial device, and the public key is publicly registered / stored in the blockchain network (i.e., distributedly stored in multiple computing devices); when the industrial device (i.e., the sender) sends data, it uses the private key stored by itself to encrypt the data to generate a digital signature; the receiver uses the public key of the sender to decrypt the digital signature to verify the data integrity and source. Specifically, when the industrial device first accesses the industrial system, it needs to obtain a pair of unique public and private keys through a trusted institution (such as a device manufacturer), and this process may also include recording / storing the basic information of the device (such as serial number, model, etc.) and the public key on the blockchain network.

[0098] Exemplarily, assume that in an industrial system, a new PLC needs to be connected to the industrial system (edge layer). The identity information (including the public key) of the PLC will be registered in the blockchain network; each time the PLC sends data, it needs to digitally sign the data with its private key. The digital signature can be generated by combining the data with the private key of the PLC through an encryption algorithm to generate a unique digital signature, which is used to prove that the data is indeed sent by the PLC and has not been tampered with during the transmission process; when the security access module in the edge layer receives the data, it uses the public key of the PLC stored in the blockchain to decrypt the digital signature and verify the authenticity of the signature. If the decryption is successful and the verification is correct, it means that the data is indeed from a registered PLC and has not been tampered with during the transmission process.

[0099] In a second aspect, the security access module is also used to encrypt the transmitted data using an encryption protocol to avoid eavesdropping or tampering.

[0100] In a possible implementation, the security access module uses a symmetric encryption algorithm (such as AES-128) to encrypt the transmission protocol.

[0101] Among them, the key used to encrypt the data and the key used to decrypt the data in the symmetric encryption algorithm are the same, that is, the same key is used for encrypting and decrypting the data. The symmetric encryption algorithm has a fast calculation speed and low resource consumption, and can be applied to resource-constrained edge devices (such as industrial gateways).

[0102] Specifically, when the security access module receives the transmitted data, it uses the symmetric encryption algorithm to encrypt the transmitted data to obtain encrypted data; the encrypted data is sent to the target device, upper layer or system; the receiving party uses the same key to decrypt the received encrypted data to restore the transmitted data.

[0103] Furthermore, the security access module dynamically generates a key using a key agreement algorithm (such as Diffie-Hellman), and encrypts the transmitted data based on the key dynamically generated by the key agreement mechanism. Similarly, the receiving party also uses the dynamically generated key to decrypt the encrypted transmitted data. The security access module dynamically generates a key using the key agreement algorithm, which can further enhance the security of communication and avoid security risks caused by long-term use of a fixed key.

[0104] In a third aspect, the security access module is used to monitor the communication behavior of industrial devices accessing the edge layer in real time, and issue an alarm and restrict the device permissions when an anomaly is found (such as an abnormal increase in the communication frequency). Specifically, a behavior baseline for normal operation is set inside the security access module. For example, a status report is sent once a minute. If an industrial device suddenly starts sending multiple requests per second, it may indicate an anomaly.

[0105] Exemplarily, in the industrial Internet scenario, a temperature sensor usually reports the current temperature every 5 minutes. When the security access module monitors that a temperature sensor accessing the edge layer starts to report a large amount of temperature data per second, this may be due to a software failure or a DDoS attack. The security access module identifies this abnormal behavior (i.e., reporting a large amount of temperature data per second), immediately issues an alarm, and temporarily blocks the temperature sensor from continuing to send temperature data.

[0106] For ease of understanding, the following combines Figure 3 , and gives an example to introduce a data transmission path implemented at the edge layer. Assume that industrial device A and industrial device B access the edge layer and the authentication is passed. Taking the case where the data of industrial device A needs to be transmitted to industrial device B and the industrial protocols of industrial device A and industrial device B are different as an example.

[0107] The protocol parsing module receives the data sent / reported by industrial device A, identifies and parses the industrial protocol of industrial device A (abbreviated as industrial protocol a), and converts the data of industrial protocol a (i.e., the data sent / reported by industrial device A) into a standardized data format to obtain the corresponding standardized data. For example: Industrial device A is a temperature sensor that sends temperature data through the Modbus protocol. After the protocol parsing module receives the temperature data sent by the temperature sensor, it identifies the Modbus protocol, parses the specific temperature value according to the Modbus protocol stored in the built-in protocol library, and converts it into a standardized data format (such as JSON format).

[0108] After receiving the standardized data, the real-time adaptation module obtains the corresponding protocol mapping rule in real time (for example: the protocol mapping rule from the standardized format to the industrial protocol b format), and executes the protocol mapping rule to convert the standardized data into data in the format of the target industrial protocol (industrial protocol b, i.e., the industrial protocol of industrial device B) (abbreviated as adapted data). For example: The real-time adaptation module receives the temperature value in JSON format and converts the temperature value in JSON format into the target industrial protocol format according to the corresponding protocol mapping rule obtained in real time to obtain the adapted data.

[0109] After receiving the adapted data, the edge computing module performs lightweight processing on the adapted data (such as noise filtering and aggregation of the adapted data) to obtain the processed data, so as to reduce the data volume and improve the data quality.

[0110] After receiving the processed data, the secure communication module encrypts the processed data using an encryption algorithm to obtain the encrypted data, ensuring that the data is not eavesdropped or tampered with during transmission.

[0111] The protocol parsing module receives the encrypted data and distributes the encrypted data to Industrial Device B (i.e., the target industrial device) through the interface of Industrial Device B, so that Industrial Device B can decrypt the encrypted data to obtain the valid data, thereby realizing the collaborative work between different industrial protocol devices of Industrial Device A and Industrial Device B in a point-to-point manner.

[0112] The above combination Figure 2 and Figure 3 , has introduced in detail the edge layer in an architecture of industrial protocol interoperability provided by an embodiment of the present application. Next, continue to introduce an architecture of an industrial system provided by an embodiment of the present application in combination with Figure 1 .

[0113] Among them, the mapping layer can also be called the Dynamic Interoperability Protocol Mapping Layer (DIPML), which is used to realize the dynamic adaptation and efficient collaboration (efficient interoperability) between heterogeneous industrial devices by dynamically generating, managing, and executing protocol mapping rules, and simultaneously supporting version control, automatic generation, and verification of protocol mapping rules. Simply put, the mapping layer is the core layer in the architecture of industrial protocol interoperability to achieve seamless communication and adaptive adjustment between industrial devices with multiple protocols.

[0114] The mapping layer supports dynamic parsing and generation of protocol mapping rules, that is, according to the interoperability requirements between different industrial protocols, protocol mapping rules are dynamically generated, so that the mapping layer supports complex adaptation in multiple protocol scenarios, and can also provide real-time feedback and optimization on the adaptation results according to actual needs. Specifically, when different industrial devices use different industrial protocols, the mapping layer can identify the information exchange required between them and automatically generate rules on how to convert the data format of one protocol into the data format of another protocol.

[0115] The mapping layer is responsible for storing and managing all the generated protocol mapping rules in the industrial system, and supports version control and optimization of the protocol mapping rules. Specifically, the mapping layer not only stores the protocol mapping rules, but also continuously optimizes them to adapt to the changing protocol requirements and environmental conditions. Further, whenever the protocol mapping rules are updated or optimized, the mapping layer retains the historical versions, so that the historical versions of the protocol mapping rules can be traced back when needed, thereby realizing the version control of the protocol mapping rules by the mapping layer and ensuring the stability and reliability of the industrial system.

[0116] The mapping layer provides an interface to the smart contract, thereby enabling the automated generation and verification of protocol mapping rules. Specifically, through the interface with the smart contract, the mapping layer can automatically create protocol mapping rules applicable to the interoperability between different industrial protocols according to preset conditions or trigger events, achieving the automated generation of protocol mapping rules, reducing the need for manual intervention, and improving the speed and accuracy of protocol mapping rule generation; the generated protocol mapping rules can also be automatically verified through the smart contract.

[0117] In a possible implementation, the mapping layer can ensure the transparency and traceability of the co-mapping rules throughout their entire life cycle, and support rapid rollback in case of exceptions, thereby ensuring the stability and reliability of the industrial system.

[0118] For ease of understanding, the following combines Figure 4 to introduce in detail the module structure of the mapping layer provided by the embodiments of the present application.

[0119] As Figure 4 shown, the mapping layer provided by the embodiments of the present application includes the following modules: a mapping rule library, a real-time mapping engine, an update adaptation module, and a record rollback module.

[0120] Among them, the Mapping Rules Repository (MRR) is the core component responsible for managing all protocol mapping rules, used to provide a complete set of protocol mapping rules, including field mapping, data format conversion, unit adaptation, etc.; it supports the dynamic generation, update, loading, and distribution of protocol mapping rules.

[0121] First, the mapping rule library supports the dynamic generation and update of protocol mapping rules, that is, the mapping rule library allows new protocol mapping rules to be quickly created through template tools.

[0122] Specifically, the mapping rule library generates corresponding protocol mapping rules based on the device information of industrial devices reported by the edge layer. The device information includes the type of industrial protocol and interface description information, and the interface description information is used to describe the rules and formats for communication through the industrial protocol.

[0123] In a possible implementation, based on the type of industrial protocol in the device information of the industrial device, the corresponding mapping rule template is matched; the rules and formats of the communication described in the interface description information are matched and mapped into the corresponding mapping rule template to generate the corresponding protocol mapping rule. For example: through a template tool, based on the device information of the industrial device, the corresponding protocol mapping rule is generated; the template tool has a built-in mapping rule template library, and the mapping rule template library includes mapping rule templates corresponding to all common industrial protocols; the template tool matches the corresponding mapping rule template through the type of industrial protocol, and then adds relevant information in the interface description information to the protocol mapping template to generate the corresponding protocol mapping rule.

[0124] Exemplarily, based on the mapping rule template corresponding to the Modbus protocol, the corresponding protocol mapping rule is generated. This mapping rule is used to map the register field 40001 of the Modbus protocol to the unified model field "temperature", and additional conversion logic is attached to achieve unit conversion. For example: the source field identifier in the source data is the identifier of the register field 40001, the target field identifier in the target data is the name "temperature" of the target field, the conversion logic defines how to convert the source data into the target format, and it is "value" * 0.1, indicating that the source data is multiplied by 0.1 to obtain the target data, and the unit of the converted target data is defined as degrees Celsius (°C).

[0125] In a possible implementation, the protocol mapping rules generated by the mapping rule library based on the device information of the industrial device include: an upstream protocol mapping rule and a downstream protocol mapping rule.

[0126] Among them, the upstream protocol mapping rule is used to convert the industrial protocol data into a standardized format to obtain standardized data; the downstream protocol mapping rule is used to convert the data in the standardized format into the industrial protocol format to obtain the industrial protocol data.

[0127] Furthermore, the mapping rule library not only supports the initial creation of protocol mapping rules, but also supports adjusting and optimizing existing protocol mapping rules based on the actual operation situation. This ensures that as the business requirements change and technology develops, the protocol mapping rules can remain efficient and accurate.

[0128] Since the mapping rule library supports the dynamic generation and update of protocol mapping rules, it can provide the necessary flexibility and support for both simple one-to-one field mapping and complex multi-field association calculations. For example, in the industrial Internet environment, different sensors may use different communication protocols, and the rule mapping library can seamlessly convert this heterogeneous data into a unified data model (the data format / model used by the upper-layer system), facilitating subsequent analysis and processing. Moreover, it supports the dynamic generation and update of protocol mapping rules, not only simplifying the mapping process between protocols but also improving the adaptability and response speed of the entire industrial system.

[0129] In the second aspect, the mapping rule library supports version control of protocol mapping rules. Specifically, each protocol mapping rule has its corresponding version number for easy historical tracing and recovery. Any modification to the protocol mapping rule will be recorded and stored in the blockchain, ensuring its immutability and auditability.

[0130] Specifically, whenever the protocol mapping rule is updated, a new version number will be generated, and this change will be recorded in the form of a log on the blockchain network to obtain a rule change log. For example, if the conversion logic in the protocol mapping rule is adjusted to "value" * 0.1 + 20 to calibrate the temperature offset, a new version of the protocol mapping rule will be created, assigned a version number, and the old version of the protocol mapping rule will also be saved for tracing or rollback.

[0131] In a possible implementation, whenever the protocol mapping rule is modified, the modification to the protocol mapping rule is recorded in the corresponding rule change log, and all rule change logs are stored based on blockchain network technology, enhancing the security and integrity of the data and ensuring that any modification to the protocol mapping rule is transparent and traceable.

[0132] In the third aspect, the rule mapping library supports the dynamic loading and distribution of protocol mapping rules. Specifically, according to the type of industrial protocol reported by the edge layer, the mapping rule library dynamically loads the corresponding protocol mapping rules and preferentially distributes the rules to the edge layer cache to reduce the load on the mapping layer and improve the response speed.

[0133] When industrial equipment is connected to the edge layer, the edge layer automatically identifies the type of industrial protocol it uses and requests the corresponding protocol mapping rules from the mapping layer. The rule mapping library in the mapping layer dynamically loads the corresponding protocol mapping rules according to the type of industrial protocol provided by the industrial equipment and first distributes them to the edge layer for caching, thus ensuring the efficiency and real-time performance of data processing. For example, when a new device using the Modbus protocol is connected, the system automatically identifies the type of its industrial protocol as the Modbus protocol and loads the protocol mapping rules corresponding to the Modbus protocol from the mapping rule library MRR. Generally, the uplink protocol mapping rules corresponding to the Modbus protocol are recorded in the mapping rule library and are used to convert Modbus protocol data into a standardized format.

[0134] In a possible implementation, the rule mapping library also supports the extension of protocol mapping rules, that is, it supports users to customize protocol mapping rules. Complex protocol mapping rules can be generated through code tools, including but not limited to: multi-field association mapping, conditional judgment logic. This flexibility enables the industrial system to handle various complex scenarios, such as processing the association calculation between different sensor data, and: through a graphical interface or a simple scripting language, even users without a technical background can quickly generate the required mapping rules, greatly improving work efficiency.

[0135] Exemplarily, if a user customizes a protocol mapping rule to associatively map the temperature value and the humidity value to a new field "comfort_index", then its protocol mapping rule is: the input fields (inputs, that is, the source data) are temperature and humidity; the output field (target_field, that is, the target data) is comfort_index; the conversion logic (formula) is 0.5*temperature + 0.5*(100 - humidity), indicating that the comfort index = 0.5 * temperature + 0.5 * (100 - humidity). For example: if the current ambient temperature is 25°C and the humidity is 60%, then the comfort index comfort_index = 0.5 * 25 + 0.5 * (100 - 60) = 12.5 + 20 = 32.5.

[0136] Among them, the real-time mapping engine is one of the core components of the mapping layer (dynamic interoperability protocol mapping layer) and is used to execute protocol mapping rules in real time to convert data from heterogeneous devices into a unified format of the system or a specific format required by the target device.

[0137] In a first aspect, a real-time mapping engine is used for rule compilation, that is, for converting protocol mapping rules stored in a mapping rule library into an executable code form, such as SQL queries, Python scripts, etc. This process enables the logic of complex protocol mapping rules to be quickly understood and executed, improving the response speed and computing efficiency of the entire industrial system.

[0138] Specifically, rule compilation refers to the process of converting protocol mapping rules in a mapping rule library into executable program code. This includes not only simple field renaming or unit conversion, but also more complex logical operations, such as conditional judgment, mathematical calculation, etc. Through rule compilation, protocol mapping rules can be executed in an optimized form, reducing the performance loss caused by interpretation execution.

[0139] Exemplarily, assume that there is a protocol mapping rule requiring the conversion of temperature from Celsius to Fahrenheit. The protocol mapping rule is: the source data (source_field) is the Celsius temperature (temperature_c), the target data (target_field) is the Fahrenheit temperature (temperature_f), and the conversion logic (conversion) is (value * 1.8) + 32, that is, multiply the source data by 1.8 and then add 32 to obtain the corresponding Fahrenheit temperature. The real-time mapping engine performs rule compilation on the above protocol mapping rule to obtain the corresponding Python function (programming language), thereby realizing the conversion of the protocol mapping rule into an executable code form.

[0140] Furthermore, the real-time mapping engine is also used for optimized parsing, that is, for analyzing the dependency relationships between protocol mapping rules, constructing a field dependency graph to identify and generate a minimum dependency set, thereby avoiding unnecessary calculation steps. Through optimized parsing, the speed of data processing and resource utilization can be significantly improved.

[0141] Specifically, optimized parsing refers to identifying the mutual dependency relationships between protocol mapping rules, determining which calculations are necessary and which can be skipped. Through optimized parsing, redundant calculations can be eliminated, improving the overall performance of the industrial system. Especially when there are a large number of conversion tasks (adaptation tasks) of interrelated data, optimized parsing can effectively manage these tasks and ensure that they are executed along the optimal path.

[0142] Exemplarily, assume that it is necessary to calculate the device health status based on the inputs of a temperature sensor and a vibration sensor. If the input data is directly calculated without considering its actual dependency relationships, it may lead to a large number of unnecessary calculations. By constructing a field dependency graph, we can calculate only those inputs that actually affect the final result.

[0143] Exemplarily, assume that the protocol mapping rule is as follows: the input source data is temperature data and vibration data, the output target data is the health status (health_status), and the conversion logic is that when the vibration is greater than 10 and the temperature is greater than 50, the health status is Critical, otherwise the health status is Normal; if the optimization parsing process is not performed, the real-time mapping engine may calculate the temperature data and vibration data input by the temperature sensor and vibration sensor. If the optimization parsing is performed, the real-time mapping engine can identify that only when the vibration is greater than 10 and the temperature is greater than 50, it is necessary to evaluate the health status (health_status). Therefore, after the optimization parsing process is completed, the real-time mapping engine will only execute the relevant calculation logic when the vibration is greater than 10 and the temperature is greater than 50, and skip this part of the calculation logic in other cases, thus saving computing resources.

[0144] Generally speaking, through rule compilation and optimization parsing, the real-time mapping engine realizes the conversion from the protocol mapping rule of high-level abstraction to the efficiently executable code, reduces unnecessary calculations, ensures that the data conversion process (adaptation process) is both fast and accurate, and helps to maintain the high-performance operation of the industrial system.

[0145] In the second aspect, the real-time mapping engine is used to execute the protocol mapping rule to convert the source data into the target format and obtain the target data. Thus, the data from devices with different industrial protocols can be converted into the unified format of the system (that is, the format that can be recognized by the upper-level system) or the specific format required by the target device (target industrial protocol format). Exemplarily, the real-time mapping engine supports single-field mapping and multi-field mapping to adapt to different data processing requirements.

[0146] Specifically, the real-time mapping engine is generally used to execute the downlink protocol mapping rule or the protocol mapping rule for converting the standardized data into the unified format of the system. That is, the real-time mapping engine is used to convert the standardized data into the target format (target industrial protocol format or the format that can be recognized by the upper-level system).

[0147] Among them, the real-time mapping engine supports single-field mapping, that is, the real-time mapping engine executes the corresponding protocol mapping rule to implement simple mapping operations on a single source field, such as name renaming, unit conversion, etc. Single-field mapping is usually used to convert the data formats from different sources into the unified format of the system so that they can be uniformly processed and analyzed within the same system framework.

[0148] Exemplarily, assume that there is a temperature value in the source data (temperature value in the normalized data) in degrees Celsius (°C), but the upper-level system needs to display this temperature in degrees Fahrenheit (°F). Then the corresponding protocol mapping rule is: the source data (source_field) is the temperature in degrees Celsius (temperature_c), the target data (target_field) is the temperature in degrees Fahrenheit (temperature_f), and the conversion logic (conversion) is (value * 1.8) + 32, that is, multiply the source data by 1.8 and then add 32 to obtain the corresponding temperature in degrees Fahrenheit. The real-time mapping engine executes the above protocol mapping rule, and can realize the conversion of the temperature in degrees Celsius to the temperature in degrees Fahrenheit.

[0149] Among them, the real-time mapping engine supports multi-field mapping, that is, the real-time mapping engine executes the corresponding protocol mapping rule to convert the fields of multiple source data into their corresponding associated values according to the predefined rules, that is, calculate the associated values between the fields of multiple source data. Multi-field mapping is usually used in situations where multiple factors need to be considered comprehensively to determine the final result, such as: evaluating the health status of the device, calculating the comfort index, etc.

[0150] Exemplarily, assume that it is necessary to judge the health status of the device according to the vibration level and the current temperature. Then the corresponding protocol mapping rule is: the input source data is the temperature data and the vibration data, and the output target data is the health status (health_status). The conversion logic is that if the vibration is greater than 10 and the temperature is greater than 50, the health status is Critical, otherwise the health status is Normal. The real-time mapping engine executes the above protocol mapping rule, and can realize judging the health status of the device based on the vibration level and the current temperature; if the vibration level exceeds 10 and the current temperature is higher than 50, it is considered that the health status of the device is Critical; otherwise, the default health status of the device is Normal.

[0151] Thirdly, the real-time mapping engine supports bidirectional mapping, that is, the real-time mapping engine not only supports converting the data from heterogeneous devices into the unified format of the system, but also supports converting the control instructions sent by the upper-level system into the format of the target industrial protocol, so as to realize bidirectional mapping.

[0152] Specifically, when the upper-layer system needs to send control instructions to industrial devices with different industrial protocols, the real-time mapping engine is used to convert these control instructions in a unified format into formats that each target device can recognize and execute (i.e., the formats of each target industrial protocol), so that each target device can perform the operations corresponding to the control instructions. For example: Through the protocol mapping rules between the standardized format and the unified format of the upper-layer system, the control instructions are converted into the standardized format, and then according to the protocol mapping rules between the standardized format and the target industrial protocol format, the control instructions in the standardized format are converted into the target industrial protocol format.

[0153] Exemplarily, assume that the industrial system includes two lighting devices using different industrial protocols, namely lighting device A and lighting device B. In order to adjust the brightness of the two lighting devices, the upper-layer system sends a control instruction in a general format of "set brightness to 50%". The real-time mapping engine converts the control instruction into the industrial protocol formats of lighting device A and lighting device B according to the corresponding protocol mapping rules, so that lighting device A and lighting device B can adjust their respective brightness to 50%. For example: For lighting device A (using the Modbus protocol), the converted Modbus protocol instruction may be: write to register 100, value 32768 (representing 50% brightness); for lighting device B (using the Zigbee protocol), the converted Zigbee protocol instruction may be: send a specific data packet containing information representing 50% brightness.

[0154] Furthermore, the real-time mapping engine is also used for conflict handling. Specifically, in the case where multiple protocol mapping rules attempt to map to the same target field, the real-time mapping engine resolves potential conflict problems based on its built-in conflict handling mechanism.

[0155] In a possible implementation, the conflict handling mechanism includes: a priority handling mechanism, a logical merging mechanism, etc.

[0156] Among them, the priority handling mechanism means: determining which protocol mapping rule should be processed first when a conflict occurs through the priority corresponding to the protocol mapping rule. When creating or updating the protocol mapping rules, assign the corresponding priority to each protocol mapping rule.

[0157] Specifically, when multiple protocol mapping rules attempt to map to the same target field, the real-time mapping engine, based on the priority handling mechanism, automatically selects the protocol mapping rule with the highest priority for execution and maps it to the target field, and other low-priority protocol mapping rules will be ignored.

[0158] Among them, the logical merging mechanism refers to combining the effects of multiple protocol mapping rules to form a new comprehensive result. Exemplarily, the logical merging mechanism includes some predefined merging logics, such as "taking the maximum value", "taking the minimum value", "logical OR", "logical AND", etc., specifically depending on the requirements of the application scenario.

[0159] Exemplarily, assume that there are two protocol mapping rules attempting to map to the same target field "health status". The first protocol mapping rule is to judge the health status of the device based on the current temperature, and the second mapping rule is to judge the health status of the device based on the humidity.

[0160] When the conflict handling mechanism is the priority handling mechanism, the first protocol mapping rule is: when the current temperature exceeds 50°C, set the health status of the device to "Critical", and the priority is 10; the second protocol mapping rule is: when the current humidity exceeds 80%, set the health status of the device to "Warning", and the priority is 5. Based on the priority handling mechanism, the real-time mapping engine determines that the priority of the first protocol mapping rule is higher than that of the second protocol mapping rule, and then executes the first protocol mapping rule.

[0161] When the conflict handling mechanism is the logical merging mechanism, based on the merging logic, the above two protocol mapping rules are merged, and the merged protocol mapping rule is: the input source data is temperature data and humidity data, the output target data is the health status (health_status), and the conversion logic is that if the temperature is greater than 50 and the humidity is greater than 80, the health status is "Critical"; if the temperature is greater than 50 or the humidity is greater than 80, the health status is "Warning"; otherwise, the health status is "Normal".

[0162] In the fourth aspect, the real-time mapping engine has the ability to ensure real-time performance. To ensure that it can quickly respond to and process a large amount of data from different devices, the real-time mapping engine has taken a series of optimization measures to achieve the goals of high performance and low latency.

[0163] Specifically, the real-time mapping engine is deployed on high-performance computing nodes. By deploying the real-time mapping engine on high-performance computing nodes, the real-time mapping engine can concurrently execute multiple protocol mapping rules without affecting performance, thereby ensuring efficient data processing capabilities even in high-concurrency scenarios. Moreover, by deploying the real-time mapping engine on high-performance computing nodes, the data processing latency can be controlled at the millisecond level, ensuring that data can be converted and transmitted to the target system or device in the shortest possible time. It can be understood that the computing device with an edge layer, a mapping layer, and a blockchain layer deployed in the embodiments of the present application is a high-performance computing device, thus enabling the real-time mapping engine to be deployed on high-performance computing nodes.

[0164] Furthermore, the real-time mapping engine uses an in-memory database (such as Redis cache) to cache commonly used data and protocol mapping rules. Compared with traditional disk I / O, the memory access speed is much faster, which greatly reduces the time required to search for and apply protocol mapping rules. And by storing commonly used (frequently used) protocol mapping rules and related data in memory, the real-time mapping engine can quickly locate the required protocol mapping rules, further improving the efficiency of data processing (adaptation).

[0165] Among them, the update adaptation module is used to ensure that the industrial system can respond in real time to changes in the industrial protocols of industrial devices or the access of new industrial devices, dynamically update or generate protocol mapping rules, and ensure the accuracy and efficiency of data conversion.

[0166] In a first aspect, the update adaptation module is used to ensure that the industrial system can automatically adapt to updates of the industrial protocols of industrial devices to ensure the latest state of the data processing logic.

[0167] Specifically, when the update adaptation module receives the update information reported by the industrial device, it obtains the device information of the industrial device to generate updated protocol mapping rules, realizing the dynamic update of the protocol mapping rules. For example: in response to the update information, the update adaptation module re-obtains the device information of the industrial device, and based on the re-obtained device information, matches the corresponding mapping rule template and maps the relevant information to the mapping rule template to generate updated protocol mapping rules, thereby realizing the update of the protocol mapping rules, and can directly apply the dynamically updated protocol mapping rules, greatly shortening the response time for industrial protocol updates.

[0168] Among them, the industrial device itself can recognize whether there is an update in the industrial protocol it uses (such as adding fields, deleting fields, etc.). When the industrial device itself recognizes that there is an update in the industrial protocol it uses, it will report the update information to indicate that there is an update in the industrial protocol of the industrial device.

[0169] Exemplarily, in the industrial Internet, a "device_state" field has been added to the industrial protocol of the already connected industrial devices, and this field represents the current working state of the device (such as running, standby or fault). In order to integrate this new field into the existing protocol mapping rules, the update adaptation module obtains the device information of the industrial device, matches the corresponding mapping rule template based on the industrial protocol in the device information, and matches and maps the interface description information in the device information to the corresponding mapping rule template, generating the updated protocol mapping rule as follows: The source data (source_field) is the original field name "device_state" from the industrial device, the target data (target_field) is the field name "state" used to represent the industrial device state in the unified format (i.e., the standardized format), and the conversion logic is simple value passing, that is, directly copying the original field name in the source data to the target data.

[0170] Among them, in the case of newly connected industrial devices existing in the edge layer, the update adaptation module will automatically scan the industrial protocols of the newly added industrial devices, and according to the scanning results, call the protocol parsing module in the edge layer to obtain the definitions of the industrial protocols of the newly added industrial devices; based on the definitions of the industrial protocols of the newly added industrial devices, automatically generate the corresponding initial protocol mapping rules; when the corresponding initial protocol mapping rules are generated, store the initial protocol mapping rules in the mapping rule library for immediate processing of data from the newly added industrial devices.

[0171] Furthermore, after the update adaptation module generates the updated protocol mapping rules, update the updated protocol mapping rules to the mapping rule library, and send a version update notification of the protocol mapping rules to the edge layer. So that after the edge layer receives the version update notification of the protocol mapping rules, it reloads the updated protocol mapping rules to ensure that subsequent relevant data processing is based on the updated (latest version) protocol mapping rules, that is, directly applying the dynamically updated protocol mapping rules, greatly shortening the response time of industrial protocol updates and further improving the protocol adaptation efficiency.

[0172] On the second aspect, the update adaptation module supports a combination of automatic verification tools and manual review to ensure the quality of the mapping rules, thus supporting the stable operation of the system and the efficient data processing ability.

[0173] Among them, the update adaptation module is built-in / equipped with an automated verification tool, which can perform consistency checks on the newly generated / updated protocol mapping rules to verify whether the protocol mapping rules conform to the expected defined rule specifications. That is, before the protocol mapping rules are applied, the automated verification tool automatically verifies whether these protocol mapping rules conform to the expected logical structure, whether there are potential errors or inconsistencies, etc. Automated verification greatly improves the speed of protocol mapping rule review, reduces delays caused by human factors, and enables the newly generated / updated protocol mapping rules to be applied quickly.

[0174] Among them, the update adaptation module also supports manual review of the newly generated / updated protocol mapping rules. When facing complex business logics or high-risk scenarios, the automated verification tool may require in-depth analysis and judgment by humans. For example: in cases involving multiple conditional judgments and complex data conversion formulas, manual review can help discover problems that the automated tool may overlook.

[0175] Exemplarily, based on the protocol mapping rules described below, an example is given to illustrate how to perform automated verification and manual review on the protocol mapping rules.

[0176] Suppose the protocol mapping rule is: the input source data is temperature data (temperature) and vibration data (vibration), the output target data is health status (health_status), and the conversion logic is that if the vibration is greater than 10 and the temperature is greater than 50, the health status is Critical, otherwise the health status is Normal; the update adaptation module performs consistency checks on the protocol mapping rule through an automated verification tool: the automated verification tool will verify whether the input fields (such as vibration and temperature) are correctly defined, whether the formula syntax is correct, and whether the output target field (such as health_status) is reasonable. Manually check whether the selection of the vibration level threshold (10 units) and the temperature threshold (50) is reasonable, and whether the classification criteria of "Critical" and "Normal" are applicable to all types of devices. In addition, humans may also consider other factors affecting health, such as humidity, to decide whether to adjust the existing rules or add additional parameters.

[0177] In the third aspect, the update adaptation module is also used to attach a priority label to the transmitted data and store it. The priority label can be used to guide the subsequent data transmission and processing processes. Thereby ensuring that the industrial system can reasonably allocate resources according to the importance and urgency of the data when facing a large number of concurrent requests, thereby optimizing the operation efficiency and service quality of the entire system.

[0178] Exemplarily, in a complex industrial system / Industrial Internet, the amount of data generated by industrial devices may be extremely large, and different types of data have different requirements for real-time performance. By attaching priority tags to the data, the industrial system can manage resources more intelligently. For some transmission data that requires immediate response (such as alarm signals or fault reports), attaching a higher priority tag can ensure that these transmission data can be quickly identified and processed, avoiding the exacerbation of problems caused by delays.

[0179] Among them, the record rollback module is used to record all modification records of protocol mapping rules into the rule change log, ensuring the transparency and traceability throughout the entire life cycle of protocol mapping rules, and supporting a one-key quick rollback to the historical version in case of anomalies, thereby guaranteeing the stable operation of the industrial system.

[0180] Specifically, the record rollback module will record all modification (such as creation, update, deletion) operations of protocol mapping rules, and store these records in the blockchain network as a log to form an immutable rule change log. Through the rule change log, the historical changes of each protocol mapping rule and its executor can be clearly traced, enhancing the transparency of industrial system operations, and the rule change log helps to meet the transparency and security requirements of industry standards and regulations for the data processing process.

[0181] Exemplarily, assume that an update operation is performed on the protocol mapping rule with the ID "1234". At this time, the record rollback module will automatically generate a rule change log in the following format, which includes: the unique identifier (rule_id) of the protocol mapping rule, the type of operation performed (operation), the timestamp of the operation (timestamp), and the user who performed the operation (user). All such rule change logs are permanently stored on the blockchain network, ensuring the security and immutability of the data.

[0182] Furthermore, the record rollback module supports users to select the historical version of the protocol mapping rule through the rule change log and roll back to the specified version with one key; send a rollback notification to the edge layer, so that in response to the rollback notification, the edge layer can reload the historical version of the protocol mapping rule.

[0183] For the convenience of understanding, briefly describe the update protocol mapping rule implemented by the mapping layer and the transmission path used.

[0184] The update adaptation module responds to the update information reported by the connected industrial device, obtains the device information of the industrial device, and generates an updated protocol mapping rule based on the device information of the industrial device; sends the updated protocol mapping rule to the mapping rule library for storage; the mapping rule library not only stores these protocol mapping rules, but also manages their version control, historical traceability, and ensures the auditability and immutability of the rules.

[0185] The mapping protocol library provides the updated protocol mapping rule to the real-time mapping engine (i.e., the real-time mapping engine obtains the updated protocol mapping rule from the mapping rule library); the real-time mapping engine receives the updated protocol mapping rule from the mapping rule library and executes the updated protocol mapping rule, thereby implementing data processing / transformation based on the updated protocol mapping rule, such as: converting standardized data into the unified format of the system or the specific format required by the target device.

[0186] The above combination Figure 4 , introduced in detail the mapping layer in the architecture of an industrial system provided by the embodiments of the present application. Next, continue to combine Figure 1 to introduce the architecture of an industrial system provided by the embodiments of the present application.

[0187] Among them, the blockchain layer is used to build a decentralized blockchain network, and combined with smart contracts, distributed ledger storage, and security management mechanisms, it provides transparent and secure data management and protocol mapping rule execution capabilities for the interoperability between industrial devices.

[0188] Specifically, the blockchain layer aims to provide a decentralized framework for managing the interaction data, protocol mapping rules, and operation logs between different industrial devices. It ensures that the data exchange between all participating parties is transparent and immutable, and realizes automated and flexible protocol adaptation through smart contracts. In addition, the blockchain layer also supports multi-node collaborative work, uses consensus algorithms to ensure the consistency and integrity of data, and enhances the scalability and robustness of the system. By recording detailed transaction information and change history, the blockchain layer enables the industrial system to have strong audit and traceability capabilities, further improving the overall security and credibility.

[0189] For ease of understanding, next, combine Figure 5 to introduce in detail the module structure of the blockchain layer provided by the embodiments of the present application.

[0190] As Figure 5 shown, the mapping layer provided by the embodiments of the present application includes the following modules: blockchain network module, smart contract module, storage traceability module, and security management module.

[0191] Among them, the blockchain network module is the infrastructure of the entire blockchain layer, which is used to build a decentralized blockchain network, so as to ensure that the interaction data, mapping rules, and logs among all industrial devices in the industrial system can be securely stored and shared, while ensuring the scalability and robustness of the industrial system.

[0192] On the first hand, the blockchain network module is used to build corresponding blockchain nodes for each participant (such as device manufacturers, users, integrators), that is, each participant has its own blockchain node. These blockchain nodes jointly maintain the blockchain network.

[0193] Among them, the blockchain nodes include: accounting nodes and ordinary participating nodes. The accounting nodes are responsible for maintaining the integrity and consistency of the blockchain ledger and undertake key tasks such as verifying transactions and packaging blocks; ordinary participating nodes can submit transaction requests but do not directly participate in the maintenance of the ledger.

[0194] Exemplarily, assume there is an industrial Internet environment with multiple participants, including device manufacturers A and B, system integrator C, and end user D. Each participant has at least one of its own blockchain nodes. For example, the blockchain node owned by device manufacturer A is both an accounting node and an ordinary participating node. It not only submits data of its own devices but also helps verify the data submitted by other nodes. While user D may only have ordinary participating nodes, which are used to query device status or submit service requests.

[0195] Specifically, the industrial system includes multiple computing devices deployed with an edge layer, a mapping layer, and a blockchain layer. Each computing device is a blockchain node in the blockchain network, and the blockchain node of the computing device is an accounting node. Further, the multiple industrial devices included in the industrial equipment are also blockchain nodes in the blockchain network, and the blockchain node of the industrial equipment is an ordinary participating node.

[0196] On the second hand, the blockchain network module is used to implement a consensus mechanism by adopting lightweight consensus algorithms (such as PBFT or Raft) to reduce the demand for computing resources in industrial scenarios while ensuring the immutability and consistency of blockchain data.

[0197] Among them, PBFT (Practical Byzantine Fault Tolerance): is applicable to application scenarios that require high throughput and low latency and can still keep the system operating normally in the presence of a small number of malicious nodes.

[0198] Among them, Raft: provides a more understandable and implementable method to reach a consensus. It is relatively simple and easy to implement and is suitable for small-scale network deployments.

[0199] Furthermore, the blockchain network module ensures the consistency of ledger copies on all nodes through a consensus mechanism and prevents any single node or a small number of nodes from maliciously modifying the ledger content, thus guaranteeing the immutability and integrity of the data.

[0200] Thirdly, the blockchain network module uses the P2P protocol to achieve the dynamic management of the distributed network, that is, the dynamic management of the blockchain network, supports the dynamic joining and exiting of blockchain nodes, thereby enhancing the scalability and robustness of the system. Specifically, the blockchain network module supports new nodes to join the blockchain network at any time and synchronize the existing data, and also supports existing nodes to exit without affecting the overall performance of the blockchain network.

[0201] Exemplarily, with the growth of the business, a new device supplier E hopes to join the existing blockchain network. The blockchain network module sets up corresponding nodes for the device supplier E according to the standard process and can complete the registration by connecting to any existing node in the blockchain network through the P2P protocol. Once the connection is successful, the node of the device supplier E will automatically synchronize historical data from other nodes and start participating in the daily data exchange and consensus process. Similarly, if a node needs to be offline temporarily for maintenance or other reasons, it can disconnect at any time without affecting the stability of the entire blockchain network.

[0202] Generally speaking, the blockchain network module not only ensures the secure sharing of data among different participating parties, but also enhances the reliability and scalability of the system through an efficient consensus mechanism and a flexible network topology. Whether new devices are added or existing configurations are adjusted, a smooth transition can be achieved, ensuring the effective satisfaction of complex interoperability requirements in the industrial environment.

[0203] Among them, the smart contract module is used to implement the core rule logic of the dynamic interoperability protocol mapping layer (i.e., the mapping layer). Specifically, by defining and managing smart contracts to handle device protocol parsing, real-time adaptation, and the execution management of mapping rules, it ensures the transparency, automation, and response speed of device interactions.

[0204] Firstly, the smart contract module defines an independent smart contract for each protocol mapping rule. A smart contract is an automatically executable contract clause directly written into the code lines. It is usually deployed on the blockchain network so that once the contract conditions are met, the corresponding operations can be automatically executed. That is, the smart contract module is used to store the protocol mapping rules in the form of smart contracts in the blockchain network.

[0205] Among them, the smart contract contains protocol conversion logic and device adaptation logic, that is, the smart contract itself contains specific protocol mapping rule content, including how to perform protocol conversion and how to adapt to the data formats of different devices. Among them, the protocol conversion logic refers to a series of rules and methods for converting data formats, structures, or semantics between different industrial protocols; the device adaptation logic focuses more on customized adjustment according to the characteristics and requirements of specific devices to ensure that data can be correctly understood and processed between the source device and the target device / target application, which not only involves the conversion of data formats, but also includes the understanding of device behaviors and the execution of corresponding operations.

[0206] When a new device is connected or the industrial protocol is updated, the smart contract module recognizes the connection of the new device or the change of the existing industrial protocol, triggers the process of automatically generating a new smart contract or updating the smart contract, and automatically stores these newly added or updated protocol mapping rules in the form of smart contracts in the blockchain network and synchronizes them to all blockchain nodes in the blockchain network to ensure the consistency of the protocol mapping rules in the blockchain network.

[0207] Furthermore, when a new device is connected or the industrial protocol is updated, the smart contract module realizes the addition or update of protocol mapping rules by the administrator actively updating the smart contract, and the smart contract module automatically synchronizes the newly added or updated protocol mapping rules (smart contracts) to all nodes in the blockchain network to ensure the consistency of the protocol mapping rules in the blockchain network.

[0208] On the second hand, the smart contract module supports the execution of instructions between industrial devices, ensuring the transparency and automation of instruction logic. That is, the instructions between devices are executed through smart contracts to ensure the transparency and automation of instruction logic. Furthermore, since the smart contract is deployed on the blockchain network and has the characteristics of immutability and high availability, the interactive instructions executed based on the smart contract are not only safe and reliable, but also can effectively prevent security risks such as man-in-the-middle attacks, further improving the overall security of the system.

[0209] Specifically, the smart contract module is used to call the corresponding smart contract to implement the execution of instructions between devices. When devices need to interact or a certain device needs to process specific instructions (such as data conversion requests, status query requests, etc.), these instructions will be executed by the smart contract module calling the corresponding smart contract. Specifically, the smart contract module automatically selects and calls the corresponding smart contract according to the predefined logic and rules to ensure that the instructions can be executed transparently and automatically according to the predetermined logic.

[0210] Exemplarily, an industrial device or component initiates an instruction; the smart contract module recognizes the requirements of this instruction and selects an appropriate smart contract to process the instruction according to the instruction type and the designed device / protocol; the smart contract module calls this smart contract, executes the operation steps defined therein, and after completion, returns the processing result to the industrial device or component that initiated the instruction. In this process, all operations are transparent and automated, ensuring efficiency and accuracy.

[0211] For example, when the edge layer sends a device data conversion request, the smart contract module calls an appropriate smart contract, which parses the industrial protocol according to its corresponding protocol mapping rules, converts the original data into a standardized format to obtain standardized data, and returns the standardized data to the edge layer.

[0212] Thirdly, the smart contract module supports an event-triggering mechanism, that is, the smart contract supports an event-based triggering mode, allowing certain operations to be automatically executed under specific conditions. Specifically, the smart contract module automatically triggers the corresponding alarm smart contract through preset conditions and notifies relevant industrial devices or systems to perform response operations, thereby achieving automated response and processing.

[0213] Among them, the alarm smart contract can be understood as a special smart contract dedicated to monitoring the corresponding preset conditions and triggering corresponding response operations when the corresponding preset conditions are met. Specifically, the alarm smart contract usually defines a set of monitored preset conditions or thresholds, and triggers corresponding response operations when the preset conditions are met or exceed the thresholds.

[0214] Exemplarily, assume there is an industrial Internet environment. If the temperature of a certain key industrial device exceeds the normal range, this may indicate a potential fault. The smart contract module creates an alarm contract. In the alarm smart contract, a temperature threshold of 50°C is defined. Once the temperature is detected to exceed the threshold (such as 50°C), a series of predefined operations are triggered / automatically executed, such as: recording abnormal events, starting emergency measures (shutting down the device or adjusting working parameters, etc.). Further, the operations predefined in the alarm smart contract also include sending an alarm notification to relevant personnel or systems. For example, the alarm notification may instruct the relevant cooling system to increase power or take other preventive measures to avoid more serious faults.

[0215] Generally speaking, the smart contract module realizes efficient and secure data interaction among industrial devices by defining and managing smart contracts. Whether it is dealing with complex protocol conversions, implementing real-time data adaptation, or handling emergencies, the smart contract module provides strong support. Through smart contracts, not only can the tasks of developers be simplified, but also the flexibility and reliability of the system can be improved, making device interoperability in the industrial Internet of Things environment smoother and more intelligent. This design not only improves work efficiency but also provides a solid guarantee for the safe and stable operation of the industrial Internet.

[0216] For the sake of easy understanding, the core rule logic of the mapping layer implemented by the smart contract module will be described in detail.

[0217] For the mapping rule library, all protocol mapping rules stored in the mapping rule library are stored in the form of smart contracts on the blockchain network. Smart contracts are uniquely identified by blockchain addresses. Therefore, the protocol mapping library stores the blockchain addresses of smart contracts to facilitate indexing protocol mapping rules through these blockchain addresses, so as to call the corresponding smart contracts (i.e., protocol mapping rules) in real time, ensuring the immutability and global traceability of protocol mapping rules. Exemplarily, the mapping rule library stores the smart contract address (0x123456), and this smart contract defines the protocol mapping rule from the Modbus protocol to the standardized format.

[0218] Furthermore, each smart contract is uniquely identified by a blockchain address, and the version of the protocol mapping rule is bound to the blockchain address of the smart contract, thus supporting version tracing.

[0219] For the real-time mapping engine, the real-time mapping engine calls the smart contract corresponding to the protocol mapping rule through the smart contract interface to achieve data adaptation. That is, it calls the smart contract corresponding to the protocol mapping rule to make the corresponding smart contract execute the conversion of source data into the target format to obtain the corresponding target data. For example: The real-time mapping engine receives the vibration data in JSON format output by the edge layer, calls the smart contract to execute the conversion of the vibration data into the format of the target industrial protocol, obtains the target data, and returns the target data.

[0220] For the update and adaptation module, when a new industrial device is connected or the industrial protocol changes, the update and adaptation module obtains the device information of the industrial device (including: the type of industrial protocol and interface description information), generates corresponding protocol mapping rules based on the device information of the industrial device, and sends them to the smart contract module; the smart contract module deploys the protocol mapping rules as new smart contracts, deploys the new smart contracts to the blockchain through the consensus mechanism, that is, stores the protocol mapping rules in the form of smart contracts on the blockchain network, and updates the rule registry on the blockchain network; the update and adaptation module obtains the blockchain address of the smart contract corresponding to the device by querying the rule registry on the blockchain and stores it in the local mapping rule library.

[0221] Among them, the storage and traceability module is used to record the transaction information of the operations performed by industrial devices, data conversion / processing, and protocol mapping rule changes in the industrial system, and store the transaction information in the form of logs in the blockchain network, providing a solid basis for subsequent auditing and tracing, and ensuring the transparency and immutability of data. For example: the transaction information of the operations performed by industrial devices includes: timestamps, operation types, operation results, etc. of operations such as starting, stopping, and status querying of industrial devices; the transaction information of data conversion / processing includes: source data, target data, called protocol mapping rules, conversion time, etc.; the transaction information of protocol mapping rule changes includes: change time, change type, version number of the updated protocol mapping rules, etc.

[0222] In the first aspect, the storage and traceability module supports distributed ledger storage, that is, the logs obtained from the transaction information of the operations performed by industrial devices, data conversion / processing, and protocol mapping rule changes in the industrial system are recorded in the distributed ledger of the blockchain, ensuring the immutability and persistence of data.

[0223] Among them, a distributed ledger (Distributed Ledger) is a database that is shared, synchronized, and replicated among multiple nodes in a network. The distributed ledger does not rely on a single central institution to maintain and manage data, but is jointly maintained by each participating node in the network. Each node stores a copy of the ledger, and these copies are updated synchronously.

[0224] Specifically, the storage and traceability module uses the characteristics of blockchain technology to add each piece of transaction information (including but not limited to data exchange between devices, changes in mapping rules, etc.) to the blockchain in the form of blocks, and ensures the security and integrity of these records through encryption algorithms.

[0225] Exemplarily, when a new industrial device is connected to the edge layer, the edge layer generates a transaction containing the initialization information of the industrial device and broadcasts it to the accounting nodes in the network; once this transaction is confirmed and added to the blockchain, it becomes a permanent and unchangeable historical record (i.e., log), which includes not only the basic information of the industrial device (such as model number, serial number), but also the timestamp of the first connection and the relevant protocol mapping rules (e.g., how to parse the data format sent by the device).

[0226] Furthermore, each record in the log stored in the storage and traceability module includes a corresponding precise timestamp, that is, the transaction information of the operations performed by the industrial device, data conversion / processing, and protocol mapping rule changes in the industrial system is accompanied by a precise timestamp, which is used to determine the exact time and order of data generation and supports high-precision historical data query and liability determination.

[0227] Specifically, whenever a new transaction is generated or an existing protocol mapping rule changes, the system automatically generates a timestamp accurate to the second or even millisecond level, and the storage and traceability module records this timestamp as part of this record. This mechanism helps to track the exact order of events and is crucial for post-event analysis and liability division.

[0228] In the second aspect, the storage and traceability module provides a blockchain-based traceability query interface that allows users to retrieve by device ID, rule ID, or time range, helping to quickly locate the source of problems or trace back the system operation process.

[0229] Specifically, the storage and traceability module provides an API interface or a user node that enables users to query the log stored in the blockchain according to different query conditions (such as device ID, rule ID, or time range), which greatly simplifies the auditing work and improves the efficiency of problem troubleshooting.

[0230] When the query condition is the device ID, the storage and traceability module allows users to find all the logs of the device according to the specific device ID (all logs include all the historical records of the device), including but not limited to: status changes, data interactions, application of protocol mapping rules, etc. When the query condition is the rule ID, the storage and traceability module allows users to find all the logs of the corresponding protocol mapping rule according to the rule ID (all logs include all the historical records of the protocol mapping rule), including but not limited to: historical versions of the protocol mapping rule and their change records. When the query condition is the time range, the storage and traceability module allows users to find all the logs within this time range (time interval).

[0231] Generally speaking, the storage traceability module provides strong technical support for the interoperability between industrial devices through distributed ledger storage, timestamp mechanism, and traceability query interface. It not only ensures the security and immutability of data but also greatly enhances the transparency and traceability of industrial systems.

[0232] Among them, the security management module is used to ensure the security of data transmission, smart contract execution, and ledger storage, prevent data leakage, tampering, and malicious node attacks, and ensure the security and reliability of the entire system. Specifically, the security management module ensures the security and reliability of the entire industrial system through a series of technical means, such as device identity registration, encrypted communication, permission control, and malicious node detection.

[0233] On the first hand, the security management module supports device identity registration, which is used to generate a unique identity identifier (such as DID, Decentralized Identifier) for each industrial device through the blockchain, and complete identity registration and authorization with the public-private key mechanism, ensuring that only verified devices can access the blockchain network and participate in data exchange or smart contract execution, thus guaranteeing the security and reliability of the entire industrial system and preventing unauthorized access.

[0234] Specifically, when a new industrial device first connects to the blockchain network, the security management module generates a unique identity identifier for the new industrial device. The DID is generated based on blockchain technology and has high security and immutability, thus ensuring the authenticity and uniqueness of industrial devices. Moreover, a new industrial device generates a pair of public-private keys during registration. The private key is held by the industrial device and is used to sign information; the public key is publicly released, that is, publicly stored in the blockchain for other nodes to verify the authenticity of messages (verify signatures).

[0235] On the second hand, the security management module supports encrypted communication, that is, uses end-to-end encryption to ensure the security of data transmission from industrial devices to blockchain nodes. Specifically, the TLS protocol or a blockchain-based distributed key exchange mechanism is adopted to protect the data transmitted from industrial devices to blockchain nodes from being stolen or tampered with, ensuring the integrity and security of data.

[0236] On the third hand, the security management module is used for permission control, that is, controls the access permissions of different participants through smart contracts. For example, it controls that device manufacturers can update rules, while ordinary users can only query and execute rules. Specifically, the smart contract defines various roles and their permission levels, and the security management module restricts the scope of executable operations according to the different roles in the smart contract. By clearly defining the operation permissions of each participant through the smart contract, the possibility of misoperation or malicious behavior is reduced, and only authorized participants can execute specific types of operations.

[0237] In a possible implementation, different roles and their corresponding permissions are defined in the smart contract. For example, the smart contract defines that the device manufacturer has the updateRules permission, while the ordinary user has the queryRules and executeRules permissions. When a certain party attempts to perform an operation, the smart contract will first check the role and permissions of the party. If its permissions allow, the operation will be allowed to continue. If its permissions do not allow, the operation will be refused to continue and the relevant event will be recorded.

[0238] Exemplarily, the smart contract defines that the device manufacturer has the highest permissions and can update the device firmware version or modify the operation parameters through the smart contract. The ordinary user can only view the current settings or send simple control instructions (such as turning the light on or off). The security management module restricts the scope of executable operations based on the role-based access control (RBAC) mechanism, effectively preventing unauthorized personnel from accessing or modifying key system functions and reducing potential risks.

[0239] Fourthly, the security management module is used to detect malicious nodes, that is, by using the consensus mechanism of the blockchain, identify and isolate abnormal nodes or nodes with malicious behaviors to ensure network security and data integrity.

[0240] Specifically, the security management module can detect malicious nodes that attempt to disrupt the system stability through the consensus mechanism, and mark these nodes as suspicious and temporarily isolate them through a specific algorithm to prevent them from causing further damage to the blockchain network. By continuously monitoring the behaviors of all nodes, any behavior deviating from the normal operation mode will be discovered and processed in a timely manner, which greatly improves the anti-attack ability of the system.

[0241] Generally speaking, the security management module significantly improves the security and credibility of the blockchain network by implementing strict device identity registration, encrypted communication, permission control, and malicious node detection measures.

[0242] By adding a blockchain layer to the architecture of an industrial system, industrial devices and computing devices in the industrial system act as blockchain nodes to construct a decentralized blockchain network, avoiding the limitations of the centralized architecture in the prior art. The architecture of the industrial system in the current technology is a centralized architecture, that is, it relies on a centralized middleware or server, resulting in the limitations of the centralized architecture, the risk of single-point failure, and performance bottlenecks. For example: when the centralized middleware fails (such as hardware failure, software failure, etc.), all data exchanges through this middleware will be terminated, or even cause the entire industrial system to fail; in the scenario of processing a large number of industrial devices and high-frequency communications, since all data needs to be processed by the centralized middleware, it not only increases the latency, but may also exceed the processing capacity of the middleware, forming a performance bottleneck, making it difficult to meet the requirements of the industrial Internet for real-time performance and large-scale device access. Further, due to the performance bottleneck, it is difficult to expand the industrial system. In the embodiments of the present application, a decentralized blockchain network is constructed, eliminating the bottleneck and single-point failure risk of the centralized middleware, and improving the reliability and scalability of the industrial system, adapting to the industrial scenario with a rapid increase in the number of devices, and further meeting the requirements for high-efficiency interoperability in the modern multi-protocol and multi-device industrial environment.

[0243] Furthermore, transaction information recording the operations performed by industrial devices in the industrial system, data conversion / processing, and changes in protocol mapping rules is recorded and stored in the blockchain network in the form of a log, that is, recorded in the distributed ledger of the blockchain network, ensuring the transparency and credibility of the data, and ensuring the data security and trust foundation in the cross-protocol collaboration environment. And the protocol mapping rules are stored in the blockchain network in the form of smart contracts, which can ensure the reliability of the execution of the protocol mapping rules.

[0244] An architecture of an industrial system provided by an embodiment of the present application introduces dynamic protocol mapping technology to achieve dynamic parsing, real-time adaptation, and seamless conversion of device protocols, and supports automatic identification and parsing of multiple industrial protocols, reducing the dependence on static rule configuration, being able to quickly respond to protocol changes and device upgrade requirements, improving the overall flexibility, and meeting the requirements for high-efficiency interoperability in the modern multi-protocol and multi-device industrial environment.

[0245] The above combination Figures 2 - 5 has introduced in detail an architecture of an industrial system provided by an embodiment of the present application. Next, continue to combine Figures 6 - 10, A data processing method provided by an embodiment of the present application will be introduced in detail. This method is applied to the industrial system described above, and the industrial system includes: a computing device on which an edge layer, a mapping layer, and a blockchain layer are deployed. Briefly speaking, a data processing method provided by an embodiment of the present application is executed by a computing device on which an edge layer, a mapping layer, and a blockchain layer are deployed.

[0246] As Figure 6 shown, a data processing method provided by an embodiment of the present application includes the following steps:

[0247] S601. Obtain the device information of the first industrial device.

[0248] Among them, the device information of the first industrial device includes: the type of the first industrial protocol and the interface description information. Moreover, the type of the first industrial protocol is different from the types of the second industrial protocols of all the second industrial devices connected to the industrial device.

[0249] Among them, the first industrial device refers to: an industrial device newly connected to the industrial system. The second industrial device refers to: the industrial devices other than the first industrial device among all the industrial devices connected to the industrial system, and the type of the first industrial protocol is different from the types of the second industrial protocols of all the second industrial devices. It can be understood that there is no protocol mapping rule corresponding to the first industrial protocol in the industrial system.

[0250] Exemplarily, assume that the industrial system includes: a computing device N1, the computing device N1 is connected to an industrial device N2 and an industrial device N3. The type of the industrial protocol of the industrial device N2 is the Modbus protocol, and the type of the industrial protocol of the industrial device N3 is the OPC UA protocol. When a new industrial device N4 is connected to the computing device N1, and the type of the industrial protocol of the industrial device N4 is the EtherCAT protocol, then the industrial device N4 is called the first industrial device, and the industrial devices N2 and N3 are called the second industrial devices, and the type of the first industrial protocol (such as the EtherCAT protocol) is different from the types of the second industrial protocols (such as the Modbus protocol and the OPC UA protocol).

[0251] Among them, the interface description information is used to describe the rules and formats for communication through the first industrial protocol. Specifically, the interface description information includes: the communication method (such as the communication interface type, transmission medium, electrical characteristics), and the definition of the first industrial protocol includes: key elements such as protocol header information (for example: start flag, length field), data frame format (for example: the arrangement order and meaning of fields), command dictionary (function codes of different instructions and their parameters), etc.

[0252] Specifically, the edge layer uses network scanning or physical interface detection to identify industrial devices accessing the industrial system and determine the communication methods of the industrial devices to achieve industrial device detection. Moreover, by comparing the data frames of the industrial devices captured / collected with the definitions in the built-in protocol library, the type of industrial protocol used by the industrial devices is automatically identified / judged, and the definition of this industrial protocol is obtained from the built-in protocol library, thereby obtaining the device information of the industrial devices.

[0253] S602. Generate a first protocol mapping rule based on the type and interface description information of the first industrial protocol.

[0254] Among them, the first protocol mapping rule is different from the second protocol mapping rule, and the second protocol mapping rule is the protocol mapping rule corresponding to the type of the second industrial protocol. That is to say, the generated first protocol mapping rule corresponding to the type of the first industrial protocol is different from the existing protocol mapping rule (i.e., the second protocol mapping rule), realizing the automatic generation of the protocol mapping rule.

[0255] Specifically, based on the type of industrial protocol in the device information of the industrial device, the corresponding mapping rule template is matched; according to the interface description information in the device information of the industrial device, the communication format and rules described by the interface description information are matched and mapped into the corresponding mapping rule template to generate its corresponding protocol mapping rule. For example: through a template tool, based on the device information of the industrial device, its corresponding protocol mapping rule is generated; the template tool has a built-in mapping rule template library, and the mapping rule template library includes mapping rule templates corresponding to all common industrial protocols; the template tool matches the corresponding mapping rule template through the type of industrial protocol, and then adds the relevant information in the interface description information to the protocol mapping template to generate the corresponding protocol mapping rule.

[0256] In a possible implementation manner, the first protocol mapping rule includes: a first uplink mapping rule and a first downlink mapping rule.

[0257] Among them, the first uplink mapping rule is used to convert the first industrial protocol data into a standardized format (such as JSON format); the first downlink mapping rule is used to convert the data in the standardized format into the first industrial protocol format. That is, in the embodiments of the present application, a first uplink mapping rule and a first downlink mapping rule are generated based on the type and interface description information of the first industrial protocol.

[0258] In a possible implementation, a mapping rule template corresponding to the type of the first industrial protocol is matched; according to the interface description information, the interface description information is matched and mapped into the corresponding mapping rule template to generate a first protocol mapping rule. For example: The template tool has a built-in mapping rule template library, and the mapping rule template library includes mapping rule templates corresponding to all common industrial protocols. Through the template tool, the mapping rule template corresponding to the type of the first industrial protocol is matched, and then the relevant information in the interface description information is added to the corresponding protocol mapping template to generate the corresponding protocol mapping rule.

[0259] In a possible implementation, after generating the first protocol mapping rule based on the type of the first industrial protocol and the interface description information, a consistency check is performed on the first protocol mapping rule to verify whether the first protocol mapping rule conforms to the predefined rule specifications; when the consistency check of the first protocol mapping rule passes, the first protocol mapping rule is stored.

[0260] S603. Obtain the source data, and based on the first protocol mapping rule, convert the source data into the target format to obtain the corresponding target data.

[0261] In a possible implementation, the source data includes: first industrial protocol data, and the first protocol mapping rule includes: a first uplink mapping rule; then obtain the first industrial protocol data, and based on the first uplink mapping rule, convert the first industrial protocol data into a standardized format to obtain the corresponding standardized data, thereby realizing the data standardization operation, so as to facilitate the subsequent conversion of the standardized data into other formats (the format used by the upper-level system or the target industrial protocol format), which can greatly reduce the complexity of cross-device data circulation, improve the communication efficiency, and further improve the interoperability of the industrial system.

[0262] Specifically, generally, the edge layer obtains the generated first uplink mapping rule from the mapping layer, and based on the first uplink mapping rule, converts the first industrial protocol data into a standardized format to obtain the corresponding standardized data.

[0263] In a possible implementation, the source data includes: standardized data (that is, data in a standardized format), and the standardized data is to be converted into the first industrial protocol format, and the first protocol mapping rule includes: a first downlink mapping rule; then obtain the standardized data, and based on the first downlink mapping rule, convert the standardized data into the first industrial protocol format to obtain the corresponding first industrial protocol data.

[0264] For ease of understanding, the following combines Figure 7 , combined with the edge layer and the mapping layer in the architecture of the industrial system, to introduce an example of the process of data interaction between a source device and a target device. Among them, the types of industrial protocols of the source device and the target device are different.

[0265] S701. The edge layer receives source data from a source device, and converts the source data into a standardized format to obtain standardized data.

[0266] Specifically, the protocol parsing module of the edge layer receives source data from the source device, identifies and parses the type of the source industrial protocol of the source device; the edge layer obtains / loads an uplink mapping rule corresponding to the type of the source industrial protocol from the mapping layer, and uses the corresponding uplink mapping rule to convert the source data into a standardized format to obtain corresponding standardized data.

[0267] In a possible implementation, the edge layer performs lightweight processing on the standardized data, thereby reducing the data volume and improving the data quality.

[0268] Furthermore, the edge layer can also encrypt the standardized data using an encryption algorithm to obtain encrypted standardized data, ensuring that the data is not eavesdropped or tampered with during transmission.

[0269] S702. The edge layer uploads the standardized data to the mapping layer.

[0270] S703. The mapping layer converts the standardized data format into a target industrial protocol format based on the corresponding protocol mapping rule to obtain target data.

[0271] Wherein, the target format is the format of the industrial protocol of the target device.

[0272] Specifically, the mapping layer converts the standardized data into a target industrial protocol format based on the downlink mapping rule corresponding to the type of the target industrial protocol to obtain target data. Exemplarily, the corresponding downlink mapping rule is converted into a directly executable code form, and the code corresponding to the corresponding downlink mapping rule is executed to implement the conversion of the standardized data format into a target industrial protocol format to obtain target data.

[0273] In a possible implementation, the mapping layer calls the smart contract corresponding to the downlink mapping rule through the smart contract interface, so that the smart contract executes the downlink mapping rule thereof, and converts the standardized data format into a target industrial protocol format, thereby ensuring the reliability of the execution of the protocol mapping rule.

[0274] S704. The mapping layer returns the target data to the edge layer.

[0275] S705. The edge layer distributes the target data to the target device through the interface of the target device.

[0276] It should be noted that for the process of data interaction between a source device and a target device point-to-point, the data interaction between the source device and the target device can be achieved through the edge layer. Specifically: The edge layer receives the source data from the source device, identifies and parses the industrial protocol of the source device, and obtains the uplink mapping rule corresponding to the type of the source industrial protocol, converts the source data into a standardized format to obtain the corresponding standardized data; The edge layer also obtains the downlink mapping rule corresponding to the type of the target industrial protocol and executes the downlink mapping rule to convert the standardized data into the target industrial protocol format to obtain the target data; The edge layer sends the target data to the target device through the interface of the target device, thus completing the data interaction between the source device and the target device.

[0277] In the embodiments of the present application, the corresponding protocol mapping rules can be dynamically generated according to the type of the industrial protocol and the interface description information in the device information, without relying on a pre-determined static mapping rule library, so as to achieve the dynamic interoperability of multi-protocol devices, improve the protocol adaptation efficiency, and improve the overall flexibility of the industrial system.

[0278] Furthermore, the protocol mapping rules corresponding to newly connected industrial devices or new industrial protocols can be dynamically generated, solving the problem that it is difficult to adapt to dynamic requirements relying on a pre-determined static mapping rule library, supporting the dynamic access of industrial devices with multiple industrial protocols, and meeting the requirements for high-efficiency interoperability in the modern industrial environment with multiple protocols and multiple devices.

[0279] In a possible implementation manner, the industrial system includes: multiple computing devices (computing devices deployed with an edge layer, a mapping layer, and a blockchain layer), each computing device is a blockchain node in the blockchain network, that is, each computing device serves as a blockchain node, and the multiple blockchain nodes corresponding to the multiple computing devices jointly constitute the blockchain network corresponding to the industrial protocol, constructing a decentralized blockchain network, thus avoiding the limitations of the centralized architecture of the industrial system in the prior art. Specifically, it eliminates the bottleneck and single-point failure risk of the centralized middleware, and improves the reliability and scalability of the industrial system, adapting to the industrial scenario with a rapid increase in the number of devices, and further meeting the requirements for high-efficiency interoperability in the modern industrial environment with multiple protocols and multiple devices.

[0280] In the scenario of the blockchain network, in the embodiments of the present application, the first protocol mapping rule is stored in the blockchain network in the form of a smart contract. Similarly, the second protocol mapping rule is also stored in the blockchain network in the form of a smart contract. And the smart contract can be synchronized to all blockchain nodes in the blockchain network to ensure the consistency of the protocol mapping rules in the blockchain network.

[0281] Further, when the first protocol mapping rule is stored in the blockchain network in the form of a smart contract, the smart contract corresponding to the first protocol mapping rule is invoked to enable the corresponding smart contract to execute the conversion of the source data into the target format, thereby obtaining the corresponding target data. The reliability of the protocol mapping rule execution, that is, the reliability and consistency of the data format conversion (data processing) process, is ensured through the smart contract. Moreover, once the smart contract is triggered, it is automatically executed according to the first protocol mapping rule without manual intervention, thus greatly improving the efficiency and accuracy of data processing.

[0282] Further, due to the immutability of the blockchain, once the smart contract and the protocol mapping rule stored on the blockchain are determined, they cannot be arbitrarily changed, which further enhances the reliability and security of data processing.

[0283] In a possible implementation, to ensure the correctness of the data processing logic, when the industrial protocol of the industrial device is updated (such as adding fields, deleting fields, etc.), it is necessary to make the current protocol mapping rule applicable to the updated industrial protocol. For ease of understanding, the following describes in detail the method for updating the protocol mapping rule in the embodiments of the present application in conjunction with Figure 8 , and details the way to update the protocol mapping rule in the embodiments of the present application.

[0284] S801. Monitor whether the industrial device in the industrial system reports update information.

[0285] Among them, the update information is used to indicate that there is an update in the industrial protocol of the industrial device.

[0286] Specifically, the industrial device itself can identify whether there is an update in the industrial protocol it uses (such as adding fields, deleting fields, etc.). When the industrial device itself identifies that there is an update in the industrial protocol it uses, it will report update information to indicate that there is an update in the industrial protocol of the industrial device.

[0287] S802. When receiving the update information reported by the third industrial device, in response to the update information, obtain the device information of the third industrial device.

[0288] Among them, the update information is specifically used to indicate that there is an update in the third industrial protocol of the third industrial device.

[0289] Among them, the third industrial device includes: the first industrial device and the second industrial device. That is, the third industrial device can be the first industrial device or the second industrial device. Simply put, the third industrial device is the industrial device in all industrial devices of the industrial system whose industrial protocol has been updated.

[0290] Among them, the device information of the third industrial device includes: the type of the third industrial protocol and the interface description information. The third industrial device can be the first industrial device or the second industrial device; similarly, the type of the third industrial protocol includes: the type of the first industrial protocol and the type of the second industrial protocol, that is, the third industrial protocol can be the first industrial protocol or the second industrial protocol. Simply put, the third industrial protocol is the industrial protocol updated from the first industrial protocol and the second industrial protocol.

[0291] S803. Generate a third protocol mapping rule based on the type and interface description information of the third industrial protocol, so as to implement data format conversion based on the third protocol mapping rule.

[0292] Among them, the third protocol mapping rule is: the protocol mapping rule that is the updated version of the first protocol mapping rule or the second protocol mapping rule. That is, the third protocol mapping rule may be the updated version of the first protocol mapping rule or the updated version of the second protocol mapping rule.

[0293] In the embodiment of the present application, it is possible to dynamically generate an updated protocol mapping rule (i.e., the third protocol mapping rule) in response to the update information, realizing the dynamic update of the protocol mapping rule, ensuring that as the business requirements change and technology develops, the protocol mapping rule can remain efficient and accurate, thereby ensuring the correctness of the data processing logic.

[0294] Furthermore, after generating the third protocol mapping rule, directly apply the third protocol mapping rule to implement the corresponding data format conversion, that is, directly apply the dynamically updated protocol mapping rule, which greatly shortens the response time of the industrial protocol update, further improves the protocol adaptation efficiency, and thus improves the adaptability and response speed of the entire industrial system.

[0295] In a possible implementation manner, record the transaction information of data conversion and rule change in the industrial system, and store the transaction information in the blockchain network in the form of a log, where each record in the log includes the corresponding timestamp.

[0296] Storing the transaction information in the blockchain network in the form of a log provides a solid basis for subsequent auditing and tracing, ensuring the transparency and immutability of the data. And storing the transaction information in the blockchain network in the form of a log can also achieve distributed storage, enhancing the reliability and security of the data. Even if a certain blockchain node fails, other nodes can still completely save and access the transaction information, thus ensuring the continuity and stability of the industrial system. At the same time, through the consensus mechanism of the blockchain network, the authenticity and validity of the transaction information can be ensured, avoiding malicious tampering or forgery of the data, and providing a strong guarantee for the data security and credibility of the industrial system.

[0297] Furthermore, transaction information of operations performed by industrial devices in the industrial system is also recorded and stored in the blockchain network in the form of a log.

[0298] Exemplarily, for transaction information of rule changes, each generated protocol mapping rule (including addition and update) is version numbered, and the transaction information of the protocol mapping rule change is recorded and stored in the blockchain network in the form of a change log; wherein, the change log includes: the unique identifier of the protocol mapping rule, the version number, the operation type (add field, delete field, etc.), and the timestamp. Subsequently, users can roll back to the historical version of the protocol mapping rule with one key according to the version number.

[0299] In the embodiments of the present application, through the distributed ledger technology of the blockchain network, the entire process of operations performed by industrial devices, data conversion, and rule changes is recorded and traced, which ensures the transparency, immutability, and reliability of data. While improving data security, the log records provide a reliable basis for operation and maintenance management, enabling quick location of problem causes and improving the operation and maintenance efficiency of the system.

[0300] Furthermore, when each industrial device accesses the industrial system, that is, when each industrial device accesses the edge layer, namely when the industrial device accesses the computing device, the blockchain layer deployed on the computing device generates a unique digital identity identifier (DID) for the industrial device and completes the identity registration in combination with the public-private key encryption mechanism.

[0301] For ease of understanding, the following combines Figure 9 to introduce in detail how to implement the registration process of industrial devices in the embodiments of the present application.

[0302] As Figure 9 shown, the registration of industrial devices in the embodiments of the present application includes the following steps:

[0303] S901. The edge layer obtains the basic information of the industrial device and transmits it to the blockchain layer.

[0304] Among them, the basic information of the industrial device includes: device model, device serial number (SN), manufacturer, industrial protocol, communication method, etc.

[0305] Specifically, the protocol parsing module of the edge layer uses network scanning or physical interface detection to identify the accessed industrial device and determine the communication method of the industrial device. At the same time, the protocol parsing module can obtain information such as the device model, device serial number, and manufacturer through network scanning; and the protocol parsing module compares the captured / data collected data frames of the industrial device with the definitions in the built-in protocol library to automatically identify / determine the type of industrial protocol of the industrial device, thereby obtaining the basic information of the industrial device.

[0306] It should be noted that in addition, after identifying the industrial protocol, the protocol parsing module can also read information such as the device model, device serial number, and manufacturer of the industrial device based on the industrial protocol.

[0307] In a possible implementation, the edge layer encapsulates the basic information of the industrial device obtained into a standardized format (such as JSON format) and sends it to the blockchain layer to request the generation of a DID.

[0308] S902. The blockchain layer generates a unique DID based on the basic information of the industrial device.

[0309] Specifically, the security management module of the blockchain layer generates a unique DID corresponding to the industrial device based on the basic information of the industrial device using a predefined algorithm or smart contract.

[0310] Specifically, after receiving the basic information of the industrial device, the blockchain layer queries the blockchain ledger by the device serial number to check if it has been registered; when it has not been registered, a unique DID is generated based on the basic information of the industrial device to avoid duplicate registration.

[0311] Exemplarily, the security management module of the blockchain layer processes the basic information of the industrial device using a hash algorithm to generate a unique string of a fixed length as its corresponding DID. The security management module of the blockchain layer can also combine the basic information of the industrial device to generate a UUID (Universally Unique Identifier) as its corresponding DID. The security management module of the blockchain layer can also call the corresponding smart contract, which can generate the corresponding DID by comprehensively considering the basic information of the industrial device according to specific rules and logic.

[0312] In a possible implementation, after receiving the basic information of the industrial device sent by the edge layer, the blockchain layer verifies the basic information of the industrial device to ensure the integrity and accuracy of the industrial information and prevent error messages or malicious information from entering the system.

[0313] In a possible implementation, in addition to generating a unique DID based on the basic information of the industrial device, the blockchain layer can also generate a pair of public and private keys for the device using a preset algorithm.

[0314] It should be noted that before the industrial device is connected, the industrial device itself generates a pair of public and private keys and transmits the public key of the industrial device to the blockchain layer.

[0315] S903. The blockchain layer writes the DID and the public key into the blockchain network and returns the DID to the edge layer.

[0316] Specifically, the blockchain layer records the DID and public key in the blockchain ledger to ensure that they cannot be tampered with and are permanently preserved; at the same time, the blockchain layer returns the DID to the edge layer for use in subsequent data interaction and registration processes.

[0317] Furthermore, the DID, basic information of industrial equipment, public key, registration timestamp and other information are recorded in the blockchain ledger to form an unalterable device identity file.

[0318] In one possible implementation, when the blockchain layer generates a pair of public and private keys for industrial equipment, the blockchain layer returns the private key to the edge layer for digitally signing the data.

[0319] The edge layer stores the DID in a secure area (such as an encrypted database) and associates the DID with the communication interface of the industrial equipment in the protocol parsing module of the edge layer. When the industrial equipment uploads data later, the edge layer automatically attaches the DID to the data and uses the private key to generate a digital signature for the blockchain layer to verify the authenticity of the data source.

[0320] For example: when an industrial device sends data, the edge layer uses the private key of the industrial device to digitally sign the data (such as the vibration amplitude value) and sends it to the blockchain layer; the blockchain layer queries the public key of the industrial device through the DID and verifies the authenticity of the digital signature based on the public key. If the verification passes, it means that the data is indeed from a registered industrial device and has not been tampered with during transmission.

[0321] For ease of understanding, first combine Figure 10 , a data processing method provided in an embodiment of the present application is introduced with examples in combination with specific scenarios.

[0322] like Figure 10 An industrial system is shown, the industrial system includes: industrial equipment A, industrial equipment B and a computing device, the computing device is deployed with an edge layer, a mapping layer and a blockchain layer. The types of industrial protocols of industrial equipment A and industrial equipment B are different, and a new industrial equipment C is connected, and the type of industrial protocol of industrial equipment C is different from the type of industrial protocol of industrial equipment A and industrial equipment B.

[0323] Industrial equipment A is a PLC (programmable logic controller) that supports the Modbus protocol, which is used for temperature monitoring and transmits temperature data through the Modbus RTU protocol; industrial equipment B is an industrial robot that supports the OPC UA protocol and is used for robotic arm operation; industrial equipment C is an intelligent sensor that supports the EtherCAT protocol and is used for vibration detection and transmits vibration amplitude data through the EtherCAT protocol.

[0324] First, the computing device obtains the device information of industrial device C, including: the type of industrial protocol (i.e., EtherCAT protocol) and interface description information, and generates protocol mapping rule 1000 (including: upstream mapping rule 1001 and downstream mapping rule 1002) based on the type of industrial protocol being EtherCAT protocol and interface description information. This protocol mapping rule 1000 is different from the protocol mapping rule 1010 corresponding to the Modbus protocol and the protocol mapping rule 1020 corresponding to the OPC UA protocol.

[0325] Industrial device C sends vibration data to the edge layer via the EtherCAT protocol. The edge layer parses the EtherCAT protocol, calls the upstream mapping rule 1001 to convert the vibration data into a standardized format (JSON format), obtains the standardized data, and transmits the standardized data to the mapping layer. The mapping layer, based on the downstream mapping rule 1012 in the protocol mapping rule 1010 corresponding to the Modbus protocol, converts the standardized data into the Modbus protocol format, obtains the Modbus protocol data, and transmits the Modbus protocol data to industrial device A through the edge layer; at the same time, the mapping layer, based on the downstream mapping rule 1022 in the protocol mapping rule 1020 corresponding to the OPC UA protocol, converts the standardized data into the OPC UA protocol format, obtains the OPC UA protocol data, and transmits the OPC UA protocol data to industrial device B through the edge layer. After receiving the Modbus protocol data, industrial device A adjusts the temperature according to the Modbus protocol data; after receiving the OPC UA protocol data, industrial device B pauses operation and waits for a recovery instruction.

[0326] With the data interaction between industrial device C and industrial device A, and between industrial device C and industrial device B, the operation of the industrial device and the transaction information of data conversion are recorded and stored in the blockchain layer in the form of a log. Exemplarily, the following are stored in the form of a log: the vibration data uploaded by industrial device C and its timestamp, the edge layer invoking the uplink mapping rule 1001 to convert the vibration data into standardized data and its timestamp, the mapping layer invoking the downlink mapping rule 1012 to convert the standardized data into Modbus protocol data and its timestamp, the mapping layer invoking the downlink mapping rule 1022 to convert the standardized data into OPC UA protocol data and its timestamp, etc., the specific instruction content and its execution result (success / failure) of the Modbus protocol data received by industrial device A, the specific instruction content and its execution result of the OPC UA protocol data received by industrial device B, and other transaction information. For example, the records in the log regarding the invocation of protocol mapping rules include: the first one, the invoked uplink mapping rule 1001, the execution timestamp, the vibration data in EtherCAT protocol format as input, and the standardized data as output; the second one, the invoked downlink mapping rule 1012, the execution timestamp, the standardized data as input, and the Modbus protocol data as output; the third one, the invoked downlink mapping rule 1022, the execution timestamp, the standardized data as input, and the OPC UA protocol data as output.

[0327] A data processing method provided by an embodiment of the present application includes: obtaining device information of a first industrial device; generating a first protocol mapping rule based on the type and interface description information of the first industrial protocol; wherein, the first protocol mapping rule is different from the second protocol mapping rule, and the second protocol mapping rule is the protocol mapping rule corresponding to the type of the second industrial protocol; obtaining source data, and converting the source data into a target format based on the first protocol mapping rule to obtain corresponding target data. In the embodiment of the present application, it is possible to dynamically generate a new protocol mapping rule in response to a newly connected first industrial protocol in an industrial system, without relying on a predetermined static mapping rule library, so as to achieve dynamic interoperability of multi-protocol devices, improve the protocol adaptation efficiency, and improve the overall flexibility of the industrial system. Further, it is possible to dynamically generate a protocol mapping rule corresponding to a newly connected industrial device or a new industrial protocol, solve the problem that it is difficult to adapt to dynamic requirements relying on a predetermined static mapping rule library, support the dynamic access of industrial devices with multiple industrial protocols, and be able to meet the requirements for high-efficiency interoperability in a modern industrial environment with multiple protocols and multiple devices.

[0328] Further, the embodiment of the present application performs a standardization operation on the data reported by the industrial device, that is, converts the industrial protocol data into a standardized format, which can greatly reduce the complexity of cross-device data circulation and improve the communication efficiency.

[0329] Furthermore, the industrial system includes multiple computing devices, each of which is a blockchain node in the blockchain network, thus forming a decentralized blockchain network. This eliminates the bottleneck of the centralized middleware and the risk of single-point failure, and improves the reliability and scalability of the industrial system, adapting to the industrial scenarios with a rapid increase in the number of devices, and further meeting the requirements for efficient interoperability in modern multi-protocol and multi-device industrial environments.

[0330] The protocol mapping rules are stored in the blockchain network in the form of smart contracts. The reliability of the execution of the protocol mapping rules is ensured through smart contracts, that is, the reliability and consistency of the data format conversion (data processing) process. Moreover, once the smart contracts and protocol mapping rules stored on the blockchain are determined, they cannot be arbitrarily changed, which further enhances the reliability and security of data processing. And the smart contract can automatically execute its corresponding operations, reducing the dependence on manual configuration and lowering the system maintenance cost.

[0331] Furthermore, through the distributed ledger technology of the blockchain network, a full-process record and trace of the operations performed on industrial devices, data conversion, and rule changes are realized, that is, ensuring the transparency, immutability, and reliability of data. While improving data security, the recorded logs provide a reliable basis for operation and maintenance management, enabling quick location of the problem causes, reducing the time consumed for troubleshooting, and improving the operation and maintenance efficiency of the industrial system.

[0332] In addition, the embodiment of the present application also provides an industrial system, which includes: a first industrial device, a second industrial device, and a computing device. Among them, the types of industrial protocols of the first industrial device and the second industrial device are different, and the computing device is used to implement the data processing method in the above embodiment.

[0333] The embodiment of the present application also provides a computing device, which includes a processor and a memory. The processor is coupled to the memory, and the memory stores computer-executable instructions. When the processor executes the computer-executable instructions, the data processing method in the above embodiment is implemented.

[0334] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program runs on a computer, the computer is enabled to execute the data processing method in the above embodiment.

[0335] For the explanations and beneficial effects descriptions of the relevant content in any of the above-provided computer-readable storage media, reference can be made to the corresponding above embodiments, and details are not repeated here.

[0336] The embodiments of the present application also provide a computer program product including instructions. When the instructions run on a computer, the computer is caused to execute any one of the data processing methods in the above embodiments. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more media integrated therein. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as an SSD), etc.

[0337] It should be noted that the devices for storing computer instructions or computer programs provided in the embodiments of the present application, such as but not limited to, the above-mentioned memory, computer-readable storage medium, and communication chip, etc., are all non-transitory.

[0338] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that contains one or more media integrated therein. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0339] Although the present application has been described in conjunction with various embodiments herein, however, in the process of implementing the claimed present application, those skilled in the art can understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "one" does not exclude a plurality. A single processor or other unit can implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0340] Although the present application has been described in conjunction with specific features and their embodiments, it is obvious that various modifications and combinations can be made without departing from the spirit and scope of the present application. Accordingly, the present specification and the drawings are merely exemplary illustrations of the present application defined by the appended claims, and are considered to have covered any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A data processing method, characterized in that: Applied to an industrial system, the industrial system includes a computing device, the method is executed by the computing device, and the method includes: Acquire device information of a first industrial device; wherein the device information of the first industrial device includes: a type of a first industrial protocol and interface description information; the type of the first industrial protocol is different from the type of a second industrial protocol of a second industrial device connected to the industrial system; Based on the type of the first industrial protocol and the interface description information, a first protocol mapping rule is generated; wherein the first protocol mapping rule is different from a second protocol mapping rule, and the second protocol mapping rule is a protocol mapping rule corresponding to the type of the second industrial protocol; The source data is acquired, and based on the first protocol mapping rule, the source data is converted into a target format to obtain corresponding target data.

2. The method according to claim 1, characterized in that The interface description information is used to describe the rules and format of communication through the first industrial protocol; the generating of the first protocol mapping rule based on the type of the first industrial protocol and the interface description information includes: Matching a corresponding mapping rule template based on the type of the first industrial protocol; The communication rules and formats described in the interface description information are matched and mapped to the corresponding mapping rule template to generate a first protocol mapping rule.

3. The method according to claim 1, characterized in that: After generating the first protocol mapping rule based on the type of the first industrial protocol and the interface description information, the method further includes: Performing a consistency check on the first protocol mapping rule to verify whether the first protocol mapping rule complies with a predefined rule specification; When the consistency check passes, the first protocol mapping rule is stored.

4. The method according to claim 1, characterized in that: The method further comprises: When receiving update information reported by a third industrial device, in response to the update information, obtaining device information of the third industrial device; wherein the update information is used to indicate that there is an update to a third industrial protocol of the third industrial device, the third industrial device includes: the first industrial device and the second industrial device, and the device information of the third industrial device includes: the type and interface description information of the third industrial protocol; Based on the type of the third industrial protocol and the interface description information, a third protocol mapping rule is generated to implement data format conversion based on the third protocol mapping rule; wherein the third protocol mapping rule is: a protocol mapping rule of an updated version of the first protocol mapping rule or the second protocol mapping rule.

5. The method according to claim 1, characterized in that The first protocol mapping rule includes: a first uplink mapping rule, the source data includes: first industrial protocol data; the acquiring the source data and converting the source data into a target format based on the first protocol mapping rule includes: First industrial protocol data reported by the first industrial device is obtained, and based on the first uplink mapping rule, the first industrial protocol data is converted into a standardized format.

6. The method according to claim 1, characterized in that The first protocol mapping rule includes: a first downlink mapping rule, the source data includes: standardized data; the acquiring the source data and converting the source data into a target format based on the first protocol mapping rule includes: Standardized data is acquired, and based on the first downlink mapping rule, the standardized data is converted into a first industrial protocol format.

7. The method according to claim 1, characterized in that The industrial system includes: a plurality of computing devices, each of which is a blockchain node in a blockchain network; the method further includes: The first protocol mapping rule is stored in the blockchain network in the form of a smart contract.

8. The method according to claim 7, characterized in that The converting the source data into a target format based on the first protocol mapping rule to obtain corresponding target data includes: Call the smart contract corresponding to the first protocol mapping rule so that the corresponding smart contract executes to convert the source data into a target format to obtain corresponding target data.

9. The method according to claim 6, characterized in that The method further comprises: Record transaction information of data conversion and rule changes of the industrial system, and store the transaction information in the form of a log in the blockchain network; wherein each record in the log includes a corresponding timestamp.

10. An industrial system, characterized in that: include: A first industrial device, a second industrial device and a computing device; wherein the types of industrial protocols of the first industrial device and the second industrial device are different, and the computing device is used to implement the data processing method as described in any one of claims 1-9.

Images