A data collection method between devices supporting unified collection of multiple protocols

Abstract

A method for collecting data between devices that supports unified collection of multiple protocols, including a node browser, a protocol library, a node model, a protocol encapsulation interface and a data container; wherein the node model includes a root node, a protocol node and a data item node; the present invention constructs an overall node model based on a three-layer node model architecture, thereby realizing unified collection and management of device data; the system first represents the device through a root node, automatically matches and connects to the corresponding protocol; the protocol node encapsulates different protocols supported by different devices, and realizes the connection of the protocols through dynamic loading; the data item node defines the specific collection items of the device data, and collects them in a unified data format; a data container is also constructed to realize unified format storage of the collected data; by adopting an innovative node model design, an integrated multi-protocol collection solution is realized, which can simplify device access, improve data collection efficiency, and ensure data consistency and efficient storage.

Description

Technical Field

[0001] The present invention relates to communication technology for heterogeneous devices in a digital twin intelligent workshop, and specifically to a data collection method between devices that supports unified collection of multiple protocols. Background Art

[0002] In the context of the digital transformation of manufacturing, digital twin smart workshops play a vital role as a vehicle for integrating infrastructure and high-tech. Digital twin smart workshops contain a wide variety of heterogeneous devices, each with its own distinct communication protocols and corresponding data collection methods. Prior research on data collection for CNC machine tools has established a device information model based on the MTConnect protocol and proposed a data collection method based on FOCAS. This method achieves real-time data collection and storage management for CNC machine tools by developing a data collection adapter and client. However, this method primarily targets CNC machine tools, lacks support for other types of equipment, and does not provide a unified node model construction method. Research on multi-protocol data collection methods and processes has proposed a multi-protocol data collection method. This method involves selecting the appropriate data communication protocol for device data collection based on the data communication protocol used by the automated equipment, and standardizing the data format of the collected data to obtain a unified data format. This method aims to improve data collection compatibility, but does not involve the construction of a unified node model. Instead, it focuses primarily on standardizing data formats and lacks comprehensive support for device diversity.

[0003] Existing technologies have some limitations in multi-protocol data collection and node model construction, especially in multi-protocol compatible configuration, unified format collection, and node model construction. The following are the main shortcomings of existing technologies:

[0004] 1. Defects or deficiencies in multi-protocol compatibility configuration

[0005] Existing technologies typically rely on writing independent adaptation layers or data acquisition modules for each protocol, lacking the ability to configure compatibility with multiple protocols. In many industrial devices, different brands and models use different communication protocols, such as OPC UA, FOCAS, and MQTT. The interfaces of these protocols are often incompatible, resulting in data collection and processing requiring separate development and configuration for each protocol. As a result, existing systems are often cumbersome and inefficient in multi-protocol configuration and management, and are unable to quickly respond to changes in different devices and protocols.

[0006] 2. Defects or deficiencies in unified format data collection

[0007] Existing technologies for multi-protocol data collection typically store and process data from different protocols in their own formats, resulting in inconsistent data storage structures and increasing the difficulty of data analysis and application. Further analysis and processing of the data, especially cross-protocol data analysis, often requires complex format conversion and preprocessing, resulting in inefficient data storage and processing.

[0008] 3. Problems with node model construction

[0009] Traditional multi-protocol data acquisition systems often lack a unified node model design. Each protocol and device typically uses independent interfaces and methods, making it difficult to effectively coordinate data acquisition and display across different protocols within the same system. This is especially true when faced with a large number of devices and complex data. Existing technologies struggle to provide a clear, standardized data acquisition structure, leading to complexity and inflexibility in data management. Summary of the Invention

[0010] In response to the problems in the existing technology, the present invention provides a data collection method between devices that supports unified collection of multiple protocols, aiming to achieve real-time collection, unified processing and storage of multi-protocol data of heterogeneous devices, and provide reliable data support for digital management and intelligent decision-making in workshops.

[0011] A data collection method between devices supporting unified collection of multiple protocols includes a node browser and the following steps:

[0012] Step 1: Build the protocol library, node model, protocol encapsulation interface and data container;

[0013] Step 2: Display several devices and the protocols corresponding to the devices on the node browser through the node model;

[0014] Step 3: Receive the device and protocol selected by the user;

[0015] Step 4: Call the protocol and corresponding configuration items from the protocol library to connect to the corresponding device; if the connection is successful, go to step 5; otherwise, go to step 2;

[0016] Step 5: Display the data item list on the node browser through the node model;

[0017] Step 6: After the user selects a data item and sets the sampling information, the sampling information and data item ID are returned to the node model;

[0018] Step 7: The node model calls the protocol encapsulation interface;

[0019] Step 8: The protocol encapsulation interface collects data based on the sampling information and data item ID; if the collection is successful, execute step 9; otherwise, execute step 7;

[0020] Step 9: Store the collected data in batches into a data container;

[0021] Step 10: Convert the data format;

[0022] Step 11: Store the converted data into the time status table and display it in real time on the node browser.

[0023] Furthermore, the protocol library includes several protocols, and the configuration items include configuration files of corresponding protocols and required connection parameters.

[0024] Further: the node model includes a root node, a protocol node and a data item node. The root node is used to store device information and user information; the protocol node is used to encapsulate protocol types and data items as well as all protocol operations related to device connection and data acquisition. In step 7, the protocol encapsulation interface is called through the protocol node; the data item node is used to encapsulate the metadata of the device's data items; wherein, the mapping relationship between the protocol node and the data item node is: the protocol node carries the corresponding device protocol data item.

[0025] Further: Step 5 specifically includes the following steps:

[0026] Step 5.1: The root node matches the device and protocol;

[0027] Step 5.2: The root node initializes the protocol node and data item node;

[0028] Step 5.3: The protocol node provides a list of data items;

[0029] Step 5.4: The data item list is displayed on the node browser.

[0030] Furthermore, the protocol encapsulation interface is used to encapsulate the data collection method of each protocol, and enables the protocol node to collect and store data through the protocol encapsulation interface.

[0031] Furthermore, the data container is used to uniformly store data from different protocols into the same data structure.

[0032] Further: the data container includes a data item layer, a device information layer and a device category layer. The data item layer is used to store the value of the data item, the unit of the data item, and the timestamp; the device information layer is used to store the device ID, device model, and device status; and the device category layer is used to store the category of the device.

[0033] Further: In step 10, the data format is converted by a data format conversion function.

[0034] Beneficial effects of the present invention: The present invention constructs an overall node model based on a three-layer node model architecture, thereby realizing unified collection and management of device data; the system first represents the device through the root node, automatically matches and connects to the corresponding protocol; the protocol node encapsulates different protocols supported by different devices, and realizes the connection of the protocol through dynamic loading; the data item node defines the specific collection items of the device data, and collects them in a unified data format; a data container is also constructed to realize unified format storage of the collected data; by adopting an innovative node model design, an integrated multi-protocol collection solution is realized, which can simplify device access, improve data collection efficiency, and ensure data consistency and efficient storage. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 is a flow chart of the present invention;

[0036] Figure 2 It is the structural diagram of the node model;

[0037] Figure 3 It is a structural diagram of the data container;

[0038] Figure 4 It is the module interaction diagram of the node model. DETAILED DESCRIPTION

[0039] The present invention will be described in detail below with reference to the accompanying drawings. The embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and are not to be construed as limiting the present invention. The directional terms such as left, center, right, top, and bottom in the embodiments of the present invention are merely relative concepts or are based on the normal use state of the product, and should not be considered as restrictive.

[0040] A data collection method between devices that supports unified collection of multiple protocols, combined with Figure 1 and Figure 4 As shown, it includes the node browser and the following steps:

[0041] Step 1: Build the protocol library, node model, protocol encapsulation interface and data container;

[0042] The protocol library includes several protocols, and the configuration items include the corresponding protocol configuration files and required connection parameters. Through these configuration items, the protocol node can be automatically loaded to complete the connection with the device. The key to this step is to achieve dynamic selection and automatic configuration of protocols through the protocol library, ensuring that users can easily select and configure devices and protocols, and ensure the correct matching of devices and protocols. Next, the corresponding data item list will be automatically loaded and provided according to the protocol selected by the user.

[0043] like Figure 2 As shown in the figure, the node model includes a root node, a protocol node, and a data item node. The root node is used to store device information and user information and automatically match the protocol node through the selection of the device protocol. The protocol node is used to encapsulate the protocol type and data items as well as all protocol operations related to device connection and data acquisition. Each protocol type of node has a set of corresponding interfaces and data items. The data item node is used to encapsulate the metadata of the specific data items of the device. Among them, the mapping relationship between the protocol node and the data item node is: the protocol node carries the corresponding device protocol data item. The advantage of this three-layer structure design is that the hierarchical structure separates the protocol management, device data item management, and data acquisition process from each other, which is convenient for expansion, management and maintenance. The hierarchical relationship between the protocol node and the data item node ensures that data items of different protocols can be uniformly processed by the system. At the same time, to ensure the multi-protocol compatibility of the system, the configuration file of each protocol (such as the OPCUA protocol library, the FOCAS protocol library, etc.) needs to be installed and configured before use to ensure that the protocol interface can be correctly loaded and called.

[0044] The protocol encapsulation interface is used to encapsulate the data collection method of each protocol and enables the protocol node to collect and store data through the protocol encapsulation interface. That is, the protocol node obtains real-time data from the device through the data collection method encapsulated by the protocol encapsulation interface. The protocol encapsulation interface can not only complete the unified management of different protocols, but also generate a list of data items related to the protocol for users to select the specific data items to be collected. Through this method, the collectible data items supported by different protocols can be dynamically generated in the user interface, simplifying the user's operation process and improving the ease of use of the system. The system's collection interface and data flow processing logic are unified, which enables the system to flexibly respond to the data collection needs of different protocols and ensure that the data collection, storage and processing processes are unified and efficient.

[0045] like Figure 3As shown, the data container is used to uniformly store data from different protocols in the same data structure to ensure the consistency and compatibility of data storage; the data container includes a three-layer hierarchical structure, namely the data item layer, the device information layer, and the device category layer. The data item layer is used to store information such as the value of the data item, the unit of the data item, and the timestamp, that is, the information of the data item itself; the device information layer is used to store information such as the device ID, device model, and device status of the device that collects the data item, that is, information describing the additional status of the data item; the device category layer is used to store the category of the device, that is, whether it is an independent device or a production line control system containing multiple devices; the key to the data container design is to provide a unified interface, so that data collected by different protocols can be processed in this three-layer hierarchical data container and flexibly called and stored according to user needs;

[0046] Step 2: Display several devices and the protocols corresponding to the devices on the node browser through the node model;

[0047] Step 3: Receive the device and protocol selected by the user;

[0048] Step 4: Call the protocol and corresponding configuration items from the protocol library to connect to the corresponding device; if the connection is successful, go to step 5; otherwise, go to step 2;

[0049] Step 5: Display the data item list on the node browser through the node model;

[0050] The specific steps include:

[0051] Step 5.1: The root node matches the device and protocol;

[0052] Step 5.2: The root node initializes the protocol node and data item node;

[0053] Step 5.3: The protocol node provides a list of data items;

[0054] Step 5.4: The data item list is displayed on the node browser;

[0055] When a user selects a data item, the protocol node will present all data items related to that protocol for the user to choose from. At this point, the data item ID selected by the user is matched with the protocol node, and the data collection process is ready to begin. This structure eliminates the need for users to worry about specific protocols or the underlying implementation of data collection. Users only need to select the target data item from the node browser, which automatically handles protocol matching and data item selection. This design improves user convenience and provides a stable foundation for subsequent data collection.

[0056] Step 6: After the user selects a data item and sets the sampling information, the sampling information and data item ID are returned to the node model;

[0057] Step 7: The node model calls the protocol encapsulation interface, specifically calling the protocol encapsulation interface through the protocol node

[0058] Step 8: The protocol encapsulation interface collects data based on the sampling information and data item ID; if the collection is successful, execute step 9; otherwise, execute step 7;

[0059] Step 9: Store the collected data in batches into a data container;

[0060] Step 10: Convert the data format. Specifically, use the data format conversion function to convert the data format and convert the information stored in the data container into CSV or JSON format.

[0061] Step 11: Store the converted data into the time status table and display it in real time on the node browser.

[0062] Among them, the operation design of the node model is generally divided into three stages: connection, collection, and storage; combined with Figure 4 As shown, during the connection phase, a real-time connection to the target device is preconfigured through physical and network connections. The user selects the corresponding protocol for connection and matches the root node to the device. During the collection phase, the root node initializes the protocol node and data item node. The user selects the target data item and sets parameters such as the collection frequency. The protocol node calls the corresponding encapsulation interface for real-time collection. During the storage phase, the collected data is stored in memory and then placed into a data container for unified storage. The data in the data container can undergo format conversion for further storage or output.

[0063] By building a node model that supports unified multi-protocol data collection, this invention not only addresses existing issues such as poor compatibility and inconsistent data formats, but also significantly improves data collection efficiency and system flexibility. Furthermore, it significantly enhances system scalability and user-friendliness.

[0064] The present invention supports the connection and acquisition of multiple protocols, and to a certain extent realizes the integration of heterogeneous equipment in digital twin intelligent workshops, and realizes the compatibility between different protocols and the unification of data acquisition; the constructed node model structure realizes the unification of data acquisition in terms of acquisition method, protocol interface and storage format, simplifies the data acquisition process, improves the stability and consistency of the system when switching between protocols, and also simplifies the data storage and query process; through modular design of class diagrams and data structures, and adopts a dynamic loading mechanism for node modules, the system can quickly adapt to the access of new devices and new protocols without large-scale modifications to the existing system, which greatly improves the adaptability, compatibility and scalability of the system.

[0065] This invention utilizes a unified interface and modular design, enabling all required configurations to be implemented during software development. Users can conveniently select target devices and data items through a node browser interface, and the system automatically completes protocol matching and data collection tasks. Compared to the tedious manual configuration of each protocol and data item in traditional systems, this invention significantly enhances the user experience, offering simple and intuitive operation. Users do not need to deeply understand the details of different protocols; they simply select devices and data items through a simple interface, and the system automatically handles data collection and storage.

[0066] The basic principles, main features, and advantages of the present invention are shown and described above. Those skilled in the art should understand that the present invention is not limited to the foregoing embodiments. The foregoing embodiments and descriptions are merely illustrative of the principles of the present invention. Various changes and modifications may be made to the present invention without departing from the spirit and scope of the present invention. Such changes and modifications are intended to fall within the scope of the present invention. The scope of protection claimed in the present invention is defined by the appended claims and their equivalents.

Claims

1. A data collection method between devices supporting unified collection of multiple protocols, characterized in that: Includes the node browser and the following steps: Step 1: Build the protocol library, node model, protocol encapsulation interface and data container; The node model includes root nodes, protocol nodes, and data item nodes. The root node is used to store device information and user information; the protocol node is used to encapsulate protocol types and data items as well as all protocol operations related to device connection and data collection. Step 2: Display several devices and the protocols corresponding to the devices on the node browser through the node model; Step 3: Receive the device and protocol selected by the user; Step 4: Call the protocol and corresponding configuration items from the protocol library to connect to the corresponding device; if the connection is successful, proceed to step 5; Otherwise, go to step 2; Step 5: Display the data item list on the node browser through the node model; The specific steps include: Step 5.1: The root node matches the device and protocol; Step 5.2: The root node initializes the protocol node and data item node; Step 5.3: The protocol node provides a list of data items; Step 5.4: The data item list is displayed on the node browser; Step 6: After the user selects a data item and sets the sampling information, the sampling information and data item ID are returned to the node model; Step 7: The node model calls the protocol encapsulation interface. Specifically, the protocol encapsulation interface is called through the protocol node. The data item node is used to encapsulate the metadata of the device's data item. The mapping relationship between the protocol node and the data item node is: the protocol node carries the corresponding device protocol data item. Step 8: The protocol encapsulation interface collects data based on the sampling information and data item ID; if the collection is successful, execute step 9; otherwise, execute step 7; Step 9: Store the collected data in batches into a data container; Step 10: Convert the data format; Step 11: Store the converted data into the time status table and display it in real time on the node browser.

2. The method for collecting data between devices supporting unified collection of multiple protocols according to claim 1, characterized in that: The protocol library includes several protocols, and the configuration items include the configuration files of the corresponding protocols and the required connection parameters.

3. The method for collecting data between devices supporting unified collection of multiple protocols according to claim 1, characterized in that: The protocol encapsulation interface is used to encapsulate the data collection method of each protocol and enable the protocol node to collect and store data through the protocol encapsulation interface.

4. The method for collecting data between devices supporting unified collection of multiple protocols according to claim 1, characterized in that: Data containers are used to store data from different protocols in the same data structure.

5. The method for collecting data between devices supporting unified collection of multiple protocols according to claim 4, characterized in that: The data container includes a data item layer, a device information layer, and a device category layer. The data item layer is used to store the value of the data item, the unit of the data item, and the timestamp; The device information layer is used to store device ID, device model, and device status; the device category layer is used to store device categories.

6. The method for data collection between devices supporting unified collection of multiple protocols according to claim 1, characterized in that: In step 10, the data format is converted by a data format conversion function.

Images