A unified data access method and system for multi-protocol industrial devices

Abstract

This invention discloses a unified data access method and system for multi-protocol industrial equipment. The method includes: constructing a unified equipment information model; establishing communication connections with at least two different types of industrial control protocol equipment through at least two different protocol adapters, and receiving raw data packets from the industrial equipment; enabling the protocol adapters to parse the raw data packets to extract protocol-specific data containing device logical addresses, data values, and status information; mapping the protocol-specific data to the unified equipment information model to generate standardized industrial control data objects conforming to the unified equipment information model specifications; and publishing the standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services. This allows application developers to access and process all device data in a consistent and standardized manner, greatly reducing system integration complexity and improving data fusion efficiency and stability.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a unified data access method and system for multi-protocol industrial equipment. Background Technology

[0002] Currently, with the deepening advancement of Industry 4.0, intelligent manufacturing, and the Industrial Internet, the level of intelligence and networking of equipment in industrial production sites is increasing daily. To achieve centralized monitoring, data analysis, and optimized control of these massive, heterogeneous industrial control devices, the primary task is to build a widely accessible underlying platform that enables seamless data acquisition and exchange. Against this backdrop, industrial data acquisition and monitoring systems have become an indispensable core infrastructure for modern factories.

[0003] Currently, various standard and vendor-specific communication protocols exist in the industrial control field. These protocols differ significantly in their physical layer, data link layer, and application layer designs, with variations in data frame structure, addressing methods, communication models, and semantic expressions. This fragmented nature of protocols has resulted in numerous "information silos" in industrial settings. Existing technologies typically employ traditional SCADA systems or dedicated gateways to achieve multi-protocol access: While traditional monitoring and data acquisition systems or their associated hardware gateways integrate drivers for some commonly used protocols, data points driven by different protocols still exist independently within the system. The lack of a globally unified and standardized device information model means that upper-layer applications still need to pay attention to the underlying protocol details when acquiring data, making data fusion and comprehensive utilization difficult and reducing practicality. Summary of the Invention

[0004] To address the aforementioned problems, this method provides a unified data access method and system for multi-protocol industrial equipment. This solves the problem mentioned in the background art where traditional monitoring and data acquisition systems or their supporting hardware gateways, although integrating drivers for some commonly used protocols, still have data points for different protocol drivers existing independently within the system. The lack of a globally unified and standardized device information model means that upper-layer applications still need to pay attention to the underlying protocol details when acquiring data, making data fusion and comprehensive utilization difficult and reducing practicality.

[0005] A unified data access method for multi-protocol industrial equipment includes the following steps:

[0006] A unified equipment information model is constructed. The model is an abstract model based on metadata, which is used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner.

[0007] Establish communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and receive raw data packets from industrial devices;

[0008] Based on the industrial control protocol corresponding to the original data message, the corresponding protocol adapter is enabled to parse the original data message in order to extract protocol-specific data containing device logical address, data value and status information.

[0009] By using a preset data mapping engine, protocol-specific data is mapped to a unified device information model to generate standardized chemical control data objects that conform to the unified device information model specifications.

[0010] Standardized industrial control data objects are published to the internal data communication bus to achieve unified data supply for upper-layer application services.

[0011] Preferably, the construction of the unified device information model includes:

[0012] Define the device entity layer, which encapsulates the globally unique identifier, device type code, and manufacturer information of industrial equipment;

[0013] Below the device entity layer, a set of data points is constructed, where each data point is fully defined through a point key, a data type enumeration value, a data unit, an access permission attribute, and a protocol-independent logical address;

[0014] The logical address serves as a key mapping basis in the mapping rules, and is used to dynamically associate it with the physical register address, object identifier, or attribute identifier obtained by the protocol adapter during the data mapping process.

[0015] Preferably, the step of establishing communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and receiving raw data packets from industrial devices, includes:

[0016] Obtain the configuration information of at least two industrial devices, and obtain the specified industrial communication protocol type for each industrial device based on the configuration information;

[0017] The specified industrial communication protocol type is passed into the preset protocol adapter factory to dynamically load the protocol adapter with the basic communication parameters configured.

[0018] By using the corresponding set of connection parameters through the protocol adapter, independent communication connections can be established with the two industrial devices respectively;

[0019] After establishing a communication connection, data interaction operations with the corresponding industrial equipment are performed in parallel through two protocol adapters to receive raw data messages from the two industrial devices.

[0020] Preferably, the step of enabling the corresponding protocol adapter to parse the original data packet based on the industrial control protocol corresponding to the original data packet, in order to extract protocol-specific data containing device logical address, data value, and status information, includes:

[0021] Receive raw data packets from different industrial control protocols and associate each raw data packet with its source industrial equipment identifier and protocol type identifier;

[0022] Based on the protocol type identifier, a matching protocol adapter is scheduled from the pre-registered protocol adapter library, the scheduled protocol adapter is enabled, and the message structure definition and parsing rules corresponding to the industrial control protocol are loaded.

[0023] Based on the message structure definition and parsing rules, the original data message is decoded to extract a protocol-specific data set containing the device logical address, data value and status information;

[0024] The extracted protocol-specific data set is bound to the source industrial equipment identifier and output to the data mapping engine.

[0025] Preferably, the step of mapping protocol-specific data to a unified device information model using a preset data mapping engine to generate standardized chemical control data objects conforming to the unified device information model specification includes:

[0026] Call the preset data mapping engine and load the unified device information model;

[0027] Based on the device logical address in the protocol-specific data, the matching logical point is searched in the unified device information model, and the complete metadata definition of the matching logical point is obtained.

[0028] Based on the complete metadata definition, the original data values ​​in the protocol-specific data are transformed and encapsulated to generate standardized chemical control data objects that conform to the unified equipment information model specification.

[0029] The standardized industrial control data object includes a unified device identifier, a logical point identifier, a converted standard data value, a data quality stamp, and a data timestamp.

[0030] Preferably, the step of publishing standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services includes:

[0031] Receive standardized industrial control data objects that conform to the unified equipment information model specification. The standardized industrial control data objects include unified equipment identifiers, logical point identifiers, standard data values, data quality stamps, and data timestamps.

[0032] Serialize standardized industrial control data objects into byte streams in a universal data exchange format that is independent of programming languages ​​and platforms;

[0033] Construct an internal data communication bus message, wherein the internal data communication bus message includes at least a byte stream as the message body and a message header containing routing information;

[0034] Messages from the internal data communication bus are published to the internal data communication bus, which uses a publish-subscribe pattern for message routing.

[0035] The control upper-layer application service receives standardized industrial control data objects from the internal data communication bus by subscribing to topics using a unified device identifier or logical point identifier.

[0036] Preferably, before activating the corresponding protocol adapter, a protocol self-discovery step is also included, specifically:

[0037] Capture data frames on the communication link and extract a preset protocol feature vector from the data frames. The protocol feature vector includes port number, function code, message header structure and specific encoding format.

[0038] The protocol feature vector is matched and calculated with the protocol feature knowledge base. Based on the result of the matching calculation, the target industrial control protocol used by the original data message is automatically determined, and the protocol adapter corresponding to the target industrial control protocol is triggered to enter the working state.

[0039] Preferably, before publishing the internal data communication bus message to the internal data communication bus, the method further includes:

[0040] Based on the pre-configured quality of service level, determine whether to provide persistent storage for internal data communication bus messages;

[0041] When configured for persistence, messages are saved to the persistent storage engine until they are acknowledged by all subscribed and online high-reliability application services.

[0042] After publishing the internal data communication bus message to the internal data communication bus, the following is also included:

[0043] Monitor the message publishing rate, number of subscribers, and message latency on the internal data communication bus;

[0044] Provides a management interface for dynamically configuring topic permissions and traffic control policies for the internal data communication bus.

[0045] Preferably, after publishing the standardized industrial control data object to the internal data communication bus, the method further includes:

[0046] Apply data quality enhancement processing to standardized industrial control data objects. The enhancement processing includes at least one of the following: null value filling, data smoothing filtering, and engineering unit conversion.

[0047] The numerical values ​​of standardized industrial control data objects are compared with pre-configured alarm threshold conditions in real time, and when the alarm triggering conditions are met, a standardized alarm event object that follows the definition of a unified equipment information model is generated.

[0048] The method further includes:

[0049] Assign acquisition priority weights and baseline acquisition cycles to each data point in the unified equipment information model;

[0050] Based on the current CPU load and network bandwidth utilization of the system, combined with the acquisition priority weight and the baseline acquisition cycle, an adaptive scheduling algorithm is used to dynamically calculate and adjust the actual acquisition frequency of each data point.

[0051] A unified data access system for multi-protocol industrial equipment, the system comprising:

[0052] The building module is used to build a unified equipment information model, which is an abstract model based on metadata, used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner.

[0053] The module is configured to establish communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and to receive raw data packets from industrial devices.

[0054] The extraction module is used to parse the original data packet based on the industrial control protocol corresponding to the original data packet, and to extract protocol-specific data containing device logical address, data value and status information.

[0055] The mapping module is used to map protocol-specific data to the unified device information model through a preset data mapping engine to generate standardized chemical control data objects that conform to the unified device information model specifications.

[0056] The publishing module is used to publish standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services.

[0057] Other features and advantages of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description and the accompanying drawings.

[0058] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0059] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof.

[0060] Figure 1 A flowchart illustrating the workflow of a unified data access method for multi-protocol industrial equipment provided by this invention;

[0061] Figure 2 Another flowchart of a unified data access method for multi-protocol industrial equipment provided by the present invention;

[0062] Figure 3 This is another flowchart of a unified data access method for multi-protocol industrial equipment provided by the present invention;

[0063] Figure 4 This is a schematic diagram of the structure of a unified data access system for multi-protocol industrial equipment provided by the present invention. Detailed Implementation

[0064] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0065] A unified data access method for multi-protocol industrial equipment, such as Figure 1 As shown, it includes the following steps:

[0066] Step S101: Construct a unified equipment information model. The model is an abstract model based on metadata, used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner.

[0067] Step S102: Establish communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and receive raw data packets from industrial devices;

[0068] Step S103: Based on the industrial control protocol corresponding to the original data packet, enable the corresponding protocol adapter to parse the original data packet to extract protocol-specific data containing device logical address, data value and status information.

[0069] Step S104: Using a preset data mapping engine, the protocol-specific data is mapped to the unified device information model to generate a standardized chemical control data object that conforms to the unified device information model specification.

[0070] Step S105: Publish standardized industrial control data objects to the internal data communication bus to achieve unified data supply for upper-layer application services.

[0071] The working principle of the above technical solution is as follows: A unified equipment information model is constructed, which is an abstract model based on metadata, used to standardize the description of industrial equipment attributes, data points, and operation commands in a protocol-independent manner; communication connections are established with at least two different types of industrial control protocol devices through at least two different protocol adapters, and raw data packets from the industrial equipment are received; based on the industrial control protocol corresponding to the raw data packet, the corresponding protocol adapter is enabled to parse the raw data packet to extract protocol-specific data containing device logical address, data value, and status information; the protocol-specific data is mapped to the unified equipment information model through a preset data mapping engine to generate standardized industrial control data objects conforming to the unified equipment information model specifications; the standardized industrial control data objects are published to the internal data communication bus to achieve unified data supply to upper-layer application services.

[0072] The beneficial effects of the above technical solution are as follows: By constructing a unified device information model and through protocol adaptation, data mapping, and standard release processes, the complex protocol details of upper-layer applications and underlying heterogeneous devices are completely decoupled. This enables application developers to access and process all device data in a consistent and standardized manner, greatly reducing system integration complexity and subsequent maintenance costs, improving data fusion efficiency and stability. It also solves the problem mentioned in existing technologies that traditional monitoring and data acquisition systems or their supporting hardware gateways, although integrating drivers for some commonly used protocols, still have data points driven by different protocols existing independently within the system. The lack of a globally unified and standardized device information model means that upper-layer applications still need to pay attention to the underlying protocol details when acquiring data, making data fusion and comprehensive utilization difficult and reducing practicality.

[0073] In one embodiment, constructing the unified device information model includes:

[0074] Define the device entity layer, which encapsulates the globally unique identifier, device type code, and manufacturer information of industrial equipment;

[0075] Below the device entity layer, a set of data points is constructed, where each data point is fully defined through a point key, a data type enumeration value, a data unit, an access permission attribute, and a protocol-independent logical address;

[0076] The logical address serves as a key mapping basis in the mapping rules, and is used to dynamically associate it with the physical register address, object identifier, or attribute identifier obtained by the protocol adapter during the data mapping process.

[0077] In this embodiment, the protocol-independent logical address is represented as a string identifier that adopts a hierarchical naming rule. This logical address is globally unique within the unified device information model and serves as a key associated with the physical address.

[0078] The beneficial effects of the above technical solution are as follows: by defining the device entity layer and data point set, a general and standardized digital twin template is established for various industrial devices, realizing an accurate description of device semantics. Furthermore, the engine uses "protocol-independent logical addresses" as the key mapping basis, which, while maintaining the model's universality, provides a core link for the dynamic and flexible binding of downstream physical addresses with various specific protocols, ensuring the model's practicality and scalability.

[0079] In one embodiment, such as Figure 2 As shown, the process of establishing communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and receiving raw data packets from industrial devices, includes:

[0080] Step S201: Obtain configuration information for at least two industrial devices, and obtain the specified industrial communication protocol type for each industrial device based on the configuration information;

[0081] Step S202: Pass the specified industrial communication protocol type into the preset protocol adapter factory to dynamically load the protocol adapter with the basic communication parameters configured.

[0082] Step S203: Using the corresponding connection parameter set of the protocol adapter, establish independent communication connections with the two industrial devices respectively;

[0083] Step S204: After establishing a communication connection, data interaction operations with the corresponding industrial equipment are performed in parallel through two protocol adapters to receive raw data packets from the two industrial devices.

[0084] In this embodiment, the protocol adapter factory is implemented based on the Service Provider Interface (SPI) mechanism. The factory maintains a registry of protocol types and adapter implementation classes. When a protocol type is passed in, the factory dynamically loads and instantiates the implementation class in the corresponding protocol adapter package located in the classpath through Java or a similar mechanism.

[0085] In this embodiment, the specified industrial communication protocol types include Modbus, OPC-UA, DNP3, and BACnet;

[0086] In this embodiment, when the protocol type is Modbus TCP, the connection parameter set includes the target device's IP address, port number, and slave address. The steps for establishing a communication connection are as follows:

[0087] Initialize a TCP socket;

[0088] Establish a TCP connection with the target device using the IP address and port number;

[0089] Verify the connection status and store the slave address in the adapter context for subsequent packet assembly;

[0090] When the protocol type is OPC-UA, the connection parameter set includes the endpoint URL, security policy, and user credentials. The steps for establishing a communication connection are as follows:

[0091] Create an OPC-UA client instance;

[0092] Establish communication with the OPC-UA server using the endpoint URL;

[0093] Based on security policies and user credentials, a secure session is negotiated and established with the server, thereby creating a logically persistent session.

[0094] In this embodiment, the step of performing data interaction operations in parallel to receive raw data packets includes two modes:

[0095] Polling acquisition mode: The protocol adapter actively sends request commands to the corresponding industrial equipment according to the predefined acquisition cycle, and synchronously or asynchronously receives the returned response messages as raw data messages;

[0096] Subscription Listening Mode: The protocol adapter subscribes to specified data items or events from the corresponding industrial equipment, and passively receives notification messages actively pushed by the industrial equipment as the original data messages when the industrial equipment data changes or events occur.

[0097] The beneficial effects of the above technical solution are as follows: the protocol adapter factory enables unified management and on-demand dynamic loading of different protocol adapters, which improves the flexibility and scalability of the system. Support for new protocols can be achieved by registering new adapters without modifying the core architecture. Furthermore, it supports establishing independent connections and parallel interaction with multiple devices, which significantly improves the system's data throughput and acquisition efficiency, and meets the high real-time requirements of industrial sites.

[0098] In one embodiment, such as Figure 3As shown, the step of enabling the corresponding protocol adapter to parse the original data packet based on the industrial control protocol corresponding to the original data packet, in order to extract protocol-specific data containing device logical address, data value and status information, including:

[0099] Step S301: Receive raw data packets from different industrial control protocols and associate each raw data packet with its source industrial equipment identifier and protocol type identifier.

[0100] Step S302: Based on the protocol type identifier, schedule a matching protocol adapter from the pre-registered protocol adapter library, enable the scheduled protocol adapter, and load the message structure definition and parsing rules corresponding to the industrial control protocol.

[0101] Step S303: Based on the message structure definition and parsing rules, decode the original data message and extract the protocol-specific data set containing the device logical address, data value and status information;

[0102] Step S304: Bind the extracted protocol-specific data set with the source industrial equipment identifier and output it to the data mapping engine.

[0103] In this embodiment, scheduling a matching protocol adapter from a pre-registered protocol adapter library based on the protocol type identifier includes:

[0104] Construct a protocol adapter registry that binds protocol type identifiers to the calling interfaces of protocol adapter instances;

[0105] Based on the protocol type identifier of the received raw data packet, a query is performed in the protocol adapter registry to locate the corresponding protocol adapter instance.

[0106] In this embodiment, the scheduled protocol adapter is enabled, and the message structure definition and parsing rules corresponding to the industrial control protocol are loaded, including:

[0107] A protocol description file is pre-configured for each industrial control protocol. This protocol description file defines the message hierarchy, field semantics, field start position, field length, data type, and encoding method in a machine-readable format.

[0108] When the protocol adapter is enabled, it loads the protocol description file.

[0109] In this embodiment, decoding the original data packet includes:

[0110] For byte / bit mapping-based protocols, the value of the target field is extracted by calculating the byte offset and bit mask according to the message structure definition;

[0111] For protocols based on tagging or encoding structures, the nodes or elements in the message are traversed according to the parsing rules, and the data content is extracted through deserialization.

[0112] In this embodiment, the message structure definition and parsing rules are stored in an external YAML format protocol description file. This file explicitly defines the message hierarchy, the byte offset of each field, length, data type, byte order, and the scaling factor and offset used to parse data values.

[0113] The beneficial effects of the above technical solution are as follows: by associating messages with device and protocol identifiers and scheduling matching adapters for parsing, a precise and automated protocol parsing pipeline is established, ensuring the traceability of data sources. Furthermore, based on predefined message structures and decoding rules, unstructured raw messages are transformed into structured, semantically rich protocol data, laying a solid foundation for subsequent data standardization mapping.

[0114] In one embodiment, the step of mapping protocol-specific data to a unified device information model using a preset data mapping engine to generate standardized chemical control data objects conforming to the unified device information model specification includes:

[0115] Call the preset data mapping engine and load the unified device information model;

[0116] Based on the device logical address in the protocol-specific data, the matching logical point is searched in the unified device information model, and the complete metadata definition of the matching logical point is obtained.

[0117] Based on the complete metadata definition, the original data values ​​in the protocol-specific data are transformed and encapsulated to generate standardized chemical control data objects that conform to the unified equipment information model specification.

[0118] The standardized industrial control data object includes a unified device identifier, a logical point identifier, a converted standard data value, a data quality stamp, and a data timestamp.

[0119] In this embodiment, the preset data mapping engine consists of a rule driver and a mapping configuration file. The mapping configuration file is in CSV or XML format, which clearly records the mapping relationship between protocol-specific addresses and model logical addresses, as well as data conversion rules. The mapping engine performs data lookup and conversion operations by querying the configuration file.

[0120] In this embodiment, based on the complete metadata definition, data transformation is performed on the original data values ​​in the protocol-specific data, including:

[0121] Data type conversion: Converts raw data values ​​from the current data type specific to the industrial control protocol to the standard data type specified in the complete metadata definition;

[0122] Based on the scaling factor and offset configured in the complete metadata definition, the original data values ​​are converted from raw values ​​into physically meaningful engineering values.

[0123] The specific status information of the industrial control protocol is mapped to the unified data quality status code defined in the unified device information model.

[0124] In this embodiment, the step of generating standardized industrial control data objects is as follows:

[0125] Create an empty data object instance that conforms to the Uniform Device Information Model;

[0126] Fill the unified device identifier and logical point identifier into the standard address field of the data object;

[0127] Fill the value field of the data object with the converted standard data value;

[0128] Fill the mapped Uniform Data Quality Status Code into the Quality Field of the Data Object;

[0129] Combine the time information generated by the data to create a standard format data timestamp, which is then filled into the timestamp field of the data object.

[0130] The beneficial effects of the above technical solution are as follows: by finding matching points in the unified model through logical addresses, intelligent conversion from protocol-dependent physical space to protocol-independent logical space is realized. Furthermore, data type, engineering value conversion and quality status mapping are performed according to metadata definitions, and finally a standard data object containing complete context information is generated, so that data has a consistent meaning and format when flowing between different systems and applications, and true semantic interoperability is achieved.

[0131] In one embodiment, the step of publishing standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services includes:

[0132] Receive standardized industrial control data objects that conform to the unified equipment information model specification. The standardized industrial control data objects include unified equipment identifiers, logical point identifiers, standard data values, data quality stamps, and data timestamps.

[0133] Serialize standardized industrial control data objects into byte streams in a universal data exchange format that is independent of programming languages ​​and platforms;

[0134] Construct an internal data communication bus message, wherein the internal data communication bus message includes at least a byte stream as the message body and a message header containing routing information;

[0135] Messages from the internal data communication bus are published to the internal data communication bus, which uses a publish-subscribe pattern for message routing.

[0136] The control upper-layer application service receives standardized industrial control data objects from the internal data communication bus by subscribing to topics using a unified device identifier or logical point identifier.

[0137] In this embodiment, the internal data communication bus messages are implemented using the MQTT protocol. Standardized industrial control data objects are serialized into JSON format byte streams and published with the topic {Unified Device Identifier} / {Logical Point Identifier}. Upper-layer application services obtain data by subscribing to the corresponding topic pattern.

[0138] The beneficial effects of the above technical solution are as follows: by serializing into a universal format and adopting a publish-subscribe model, a loosely coupled and highly cohesive internal data communication bus is constructed. Data producers and users are isolated from each other, the system architecture is clearer, and furthermore, upper-layer applications obtain data by subscribing to a unified identifier, which completely shields the protocol differences and physical locations of underlying devices, so that the development of application functions is no longer constrained by the complexity of device access, greatly improving development efficiency and system maintainability.

[0139] In one embodiment, before enabling the corresponding protocol adapter step, a protocol self-discovery step is also included, specifically:

[0140] Capture data frames on the communication link and extract a preset protocol feature vector from the data frames. The protocol feature vector includes port number, function code, message header structure and specific encoding format.

[0141] The protocol feature vector is matched and calculated with the protocol feature knowledge base. Based on the result of the matching calculation, the target industrial control protocol used by the original data message is automatically determined, and the protocol adapter corresponding to the target industrial control protocol is triggered to enter the working state.

[0142] The beneficial effects of the above technical solution are as follows: by capturing and analyzing the feature vectors of data frames and matching them with the knowledge base, the system has the ability to automatically identify the protocols used by unknown devices. This greatly reduces the manual configuration work during system deployment and improves the system's intelligence level in terms of automated deployment and plug-and-play functionality.

[0143] In one embodiment, before publishing the internal data communication bus message to the internal data communication bus, the method further includes:

[0144] Based on the pre-configured quality of service level, determine whether to provide persistent storage for internal data communication bus messages;

[0145] When configured for persistence, messages are saved to the persistent storage engine until they are acknowledged by all subscribed and online high-reliability application services.

[0146] After publishing the internal data communication bus message to the internal data communication bus, the following is also included:

[0147] Monitor the message publishing rate, number of subscribers, and message latency on the internal data communication bus;

[0148] Provides a management interface for dynamically configuring topic permissions and traffic control policies for the internal data communication bus.

[0149] The beneficial effects of the above technical solution are as follows: by using the engine to persist the data, it ensures that critical data will not be lost when the system is abnormal or the network is fluctuating, thus meeting the needs of high reliability applications. Furthermore, it provides monitoring interfaces and dynamic configuration capabilities, enabling the system to have the ability to visualize and monitor internal data flow and manage it in a refined manner, thus ensuring the stability and maintainability of the system under large-scale data throughput.

[0150] In one embodiment, after publishing the standardized industrial control data object to the internal data communication bus, the method further includes:

[0151] Apply data quality enhancement processing to standardized industrial control data objects. The enhancement processing includes at least one of the following: null value filling, data smoothing filtering, and engineering unit conversion.

[0152] The numerical values ​​of standardized industrial control data objects are compared with pre-configured alarm threshold conditions in real time, and when the alarm triggering conditions are met, a standardized alarm event object that follows the definition of a unified equipment information model is generated.

[0153] The method further includes:

[0154] Assign acquisition priority weights and baseline acquisition cycles to each data point in the unified equipment information model;

[0155] Based on the current CPU load and network bandwidth utilization of the system, combined with the acquisition priority weight and the baseline acquisition cycle, an adaptive scheduling algorithm is used to dynamically calculate and adjust the actual acquisition frequency of each data point.

[0156] In this embodiment, the adaptive scheduling algorithm is implemented based on a dynamic weight priority queue. The system calculates a real-time acquisition weight for each data point, including:

[0157] ;

[0158] in, This represents the real-time acquisition weight for the i-th data point. This represents the preset priority of the i-th data point. Let C represent the time taken to collect the i-th data point most recently, and let C represent the system CPU load.

[0159] The beneficial effects of the above technical solution are as follows: by processing such as null value filling, filtering and unit conversion, the availability and accuracy of the original data are improved, providing a higher quality data foundation for upper-level analysis. Furthermore, by using an adaptive scheduling algorithm based on system load and priority, intelligent and dynamic allocation of acquisition resources among different data points is realized, ensuring that high-priority data can be acquired in a timely manner under limited resources, thus optimizing the overall system performance and resource utilization.

[0160] In one embodiment, this embodiment also discloses a unified data access system for multi-protocol industrial equipment, such as... Figure 4 As shown, the system includes:

[0161] Module 401 is used to build a unified equipment information model. The model is an abstract model based on metadata, which is used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner.

[0162] Module 402 is configured to establish communication connections with at least two different types of industrial control protocol devices via at least two different protocol adapters, and to receive raw data packets from industrial devices.

[0163] The extraction module 403 is used to enable the corresponding protocol adapter to parse the original data message based on the industrial control protocol corresponding to the original data message, so as to extract protocol-specific data containing device logical address, data value and status information.

[0164] The mapping module 404 is used to perform mapping operations on protocol-specific data to the unified device information model through a preset data mapping engine to generate standardized chemical control data objects that conform to the unified device information model specifications.

[0165] The publishing module 405 is used to publish standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services.

[0166] The working principle and beneficial effects of the above technical solution have been explained in the method embodiments, and will not be repeated here.

[0167] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0168] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A unified data access method for multi-protocol industrial equipment, characterized in that, Includes the following steps: A unified equipment information model is constructed. The model is an abstract model based on metadata, which is used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner. Establish communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and receive raw data packets from industrial devices; Based on the industrial control protocol corresponding to the original data message, the corresponding protocol adapter is enabled to parse the original data message in order to extract protocol-specific data containing device logical address, data value and status information. By using a preset data mapping engine, protocol-specific data is mapped to a unified device information model to generate standardized chemical control data objects that conform to the unified device information model specifications. Standardized industrial control data objects are published to the internal data communication bus to achieve unified data supply to upper-layer application services; The construction of the unified device information model includes: Define the device entity layer, which encapsulates the globally unique identifier, device type code, and manufacturer information of industrial equipment; Below the device entity layer, a set of data points is constructed, where each data point is fully defined through a point key, a data type enumeration value, a data unit, an access permission attribute, and a protocol-independent logical address; The logical address serves as a key mapping basis in the mapping rules, and is used to dynamically associate it with the physical register address, object identifier, or attribute identifier obtained by the protocol adapter during the data mapping process. After publishing standardized industrial control data objects to the internal data communication bus, the following is also included: Apply data quality enhancement processing to standardized industrial control data objects. The enhancement processing includes at least one of the following: null value filling, data smoothing filtering, and engineering unit conversion. The numerical values ​​of standardized industrial control data objects are compared with pre-configured alarm threshold conditions in real time, and when the alarm triggering conditions are met, a standardized alarm event object that follows the definition of a unified equipment information model is generated. The method further includes: Assign acquisition priority weights and baseline acquisition cycles to each data point in the unified equipment information model; Based on the current CPU load and network bandwidth utilization of the system, combined with the acquisition priority weight and the baseline acquisition cycle, an adaptive scheduling algorithm is used to dynamically calculate and adjust the actual acquisition frequency of each data point.

2. The unified data access method for multi-protocol industrial equipment according to claim 1, characterized in that, The process of establishing communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters and receiving raw data packets from industrial devices includes: Obtain the configuration information of at least two industrial devices, and obtain the specified industrial communication protocol type for each industrial device based on the configuration information; The specified industrial communication protocol type is passed into the preset protocol adapter factory to dynamically load the protocol adapter with the basic communication parameters configured. By using the corresponding set of connection parameters through the protocol adapter, independent communication connections can be established with the two industrial devices respectively; After establishing a communication connection, data interaction operations with the corresponding industrial equipment are performed in parallel through two protocol adapters to receive raw data messages from the two industrial devices.

3. The unified data access method for multi-protocol industrial equipment according to claim 1, characterized in that, The process involves using the corresponding protocol adapter to parse the original data packet based on the industrial control protocol, extracting protocol-specific data containing device logical addresses, data values, and status information, including: Receive raw data packets from different industrial control protocols and associate each raw data packet with its source industrial equipment identifier and protocol type identifier; Based on the protocol type identifier, a matching protocol adapter is scheduled from the pre-registered protocol adapter library, the scheduled protocol adapter is enabled, and the message structure definition and parsing rules corresponding to the industrial control protocol are loaded. Based on the message structure definition and parsing rules, the original data message is decoded to extract a protocol-specific data set containing the device logical address, data value and status information; The extracted protocol-specific data set is bound to the source industrial equipment identifier and output to the data mapping engine.

4. The unified data access method for multi-protocol industrial equipment according to claim 1, characterized in that, The step of mapping protocol-specific data to a unified device information model using a preset data mapping engine to generate standardized chemical control data objects conforming to the unified device information model specification includes: Call the preset data mapping engine and load the unified device information model; Based on the device logical address in the protocol-specific data, the matching logical point is searched in the unified device information model, and the complete metadata definition of the matching logical point is obtained. Based on the complete metadata definition, the original data values ​​in the protocol-specific data are transformed and encapsulated to generate standardized chemical control data objects that conform to the unified equipment information model specification. The standardized industrial control data object includes a unified device identifier, a logical point identifier, a converted standard data value, a data quality stamp, and a data timestamp.

5. The unified data access method for multi-protocol industrial equipment according to claim 1, characterized in that, The step of publishing standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services includes: Receive standardized industrial control data objects that conform to the unified equipment information model specification. The standardized industrial control data objects include unified equipment identifiers, logical point identifiers, standard data values, data quality stamps, and data timestamps. Serialize standardized industrial control data objects into byte streams in a universal data exchange format that is independent of programming languages ​​and platforms; Construct an internal data communication bus message, wherein the internal data communication bus message includes at least a byte stream as the message body and a message header containing routing information; Messages from the internal data communication bus are published to the internal data communication bus, which uses a publish-subscribe pattern for message routing. The control upper-layer application service receives standardized industrial control data objects from the internal data communication bus by subscribing to topics using a unified device identifier or logical point identifier.

6. The unified data access method for multi-protocol industrial equipment according to claim 1, characterized in that, Before enabling the corresponding protocol adapter, a protocol self-discovery step is also included, specifically: Capture data frames on the communication link and extract a preset protocol feature vector from the data frames. The protocol feature vector includes port number, function code, message header structure and specific encoding format. The protocol feature vector is matched and calculated with the protocol feature knowledge base. Based on the result of the matching calculation, the target industrial control protocol used by the original data message is automatically determined, and the protocol adapter corresponding to the target industrial control protocol is triggered to enter the working state.

7. The unified data access method for multi-protocol industrial equipment according to claim 5, characterized in that, Before publishing internal data communication bus messages to the internal data communication bus, the following steps are also included: Based on the pre-configured quality of service level, determine whether to provide persistent storage for internal data communication bus messages; When configured for persistence, messages are saved to the persistent storage engine until they are acknowledged by all subscribed and online high-reliability application services. After publishing the internal data communication bus message to the internal data communication bus, the following is also included: Monitor the message publishing rate, number of subscribers, and message latency on the internal data communication bus; Provides a management interface for dynamically configuring topic permissions and traffic control policies for the internal data communication bus.

8. A unified data access system for multi-protocol industrial equipment, characterized in that, The system includes: The building module is used to build a unified equipment information model, which is an abstract model based on metadata, used to standardize the description of the attributes, data points and operation commands of industrial equipment in a protocol-independent manner. The module is configured to establish communication connections with at least two different types of industrial control protocol devices through at least two different protocol adapters, and to receive raw data packets from industrial devices. The extraction module is used to parse the original data packet based on the industrial control protocol corresponding to the original data packet, and to extract protocol-specific data containing device logical address, data value and status information. The mapping module is used to map protocol-specific data to the unified device information model through a preset data mapping engine to generate standardized chemical control data objects that conform to the unified device information model specifications. The publishing module is used to publish standardized industrial control data objects to the internal data communication bus to achieve unified data supply to upper-layer application services. The construction of the unified device information model includes: Define the device entity layer, which encapsulates the globally unique identifier, device type code, and manufacturer information of industrial equipment; Below the device entity layer, a set of data points is constructed, where each data point is fully defined through a point key, a data type enumeration value, a data unit, an access permission attribute, and a protocol-independent logical address; The logical address serves as a key mapping basis in the mapping rules, and is used to dynamically associate it with the physical register address, object identifier, or attribute identifier obtained by the protocol adapter during the data mapping process. After publishing standardized industrial control data objects to the internal data communication bus, the following is also included: Apply data quality enhancement processing to standardized industrial control data objects. The enhancement processing includes at least one of the following: null value filling, data smoothing filtering, and engineering unit conversion. The numerical values ​​of standardized industrial control data objects are compared with pre-configured alarm threshold conditions in real time, and when the alarm triggering conditions are met, a standardized alarm event object that follows the definition of a unified equipment information model is generated. The system is also used for: Assign acquisition priority weights and baseline acquisition cycles to each data point in the unified equipment information model; Based on the current CPU load and network bandwidth utilization of the system, combined with the acquisition priority weight and the baseline acquisition cycle, an adaptive scheduling algorithm is used to dynamically calculate and adjust the actual acquisition frequency of each data point.

Images