Multi-source Data Management Method, Device, Equipment and Computer-readable Storage Medium

Abstract

The present application discloses a multi-source data management method, apparatus, device and computer-readable storage medium, belonging to the technical field of industrial protocol data transmission. The multi-source data management method includes the following steps: obtaining a variable list of multi-source data, and generating an instantiated multi-source data variable model based on the variable list of multi-source data; extracting drive information from the instantiated multi-source data variable model, and creating a data transmission link based on the drive information; performing variable management on the multi-source data based on the data transmission link; obtaining the drive name of the variable data in the data transmission link, and creating a drive object corresponding to the variable data based on the drive name; adding the variable data to the device acquisition queue based on the drive object. The present application uniformly schedules multi-source data protocols, links and drive information, realizing serial and parallel link management and efficient integration of multi-source data.

Description

Technical Field

[0001] The present application relates to the technical field of industrial protocol data transmission, and particularly to a multi-source data management method, apparatus, device, and computer-readable storage medium. Background Art

[0002] With the rapid upgrade of the digital transformation of factory enterprises, industrial transmission protocols are also developing rapidly. To support the digital transformation of enterprises, factory control devices support a wide variety of protocol types. Therefore, during the development of digital monitoring software, it is necessary to collect and manage data for devices supporting different protocols.

[0003] The existing multi-source data management solutions mainly rely on database management, that is, corresponding databases are established separately for devices with different protocols for data collection and management. However, the data forms of devices with different protocols are diverse, resulting in large development, management, and maintenance workloads when adding a new protocol device. Moreover, with the diversification of factory control device protocols, various protocol data islands will gradually form during the operation of this solution, making it difficult to achieve data interaction between devices, with low management efficiency. When a device fails, it is impossible to quickly switch to redundant devices with multiple-link data sources, seriously affecting production safety and product quality. Summary of the Invention

[0004] The main purpose of the present application is to provide a multi-source data management method, apparatus, device, and computer-readable storage medium, aiming to integrate and uniformly manage multi-source data from devices with different protocols, achieve data interaction between devices, improve management efficiency, and ensure production safety and product quality.

[0005] To achieve the above object, the present application provides a multi-source data management method, and the multi-source data management method includes the following steps:

[0006] Obtain a variable list of multi-source data, and generate an instantiated multi-source data variable model based on the variable list of the multi-source data;

[0007] Create a data transmission link based on the instantiated multi-source data variable model;

[0008] Perform variable management on the multi-source data based on the data transmission link;

[0009] Obtain the driver name of the variable data in the data transmission link, and create a driver object corresponding to the variable data based on the driver name;

[0010] Add the variable data to the device acquisition queue based on the driver object.

[0011] Optionally, before the step of obtaining the multi-source data variable list, the multi-source data management method further includes:

[0012] Obtain a configuration file corresponding to the multi-source data, and generate a variable list of the multi-source data based on the configuration file.

[0013] Optionally, the step of generating an instantiated multi-source data variable model based on the variable list of the multi-source data includes:

[0014] Obtain the variable attributes of the multi-source data from the variable list of the multi-source data;

[0015] Substitute the variable attributes of the multi-source data into a predefined variable and driver model to obtain an instantiated multi-source data variable model.

[0016] Optionally, after the step of creating a data transmission link based on the instantiated multi-source data variable model, the multi-source data management method further includes:

[0017] Add data transmission links of different link types to a task queue management link;

[0018] Manage the data transmission links by link type and task priority to achieve parallel link communication and serial link communication.

[0019] Optionally, the step of performing variable management on the multi-source data based on the data transmission link includes:

[0020] Schedule and manage the industrial protocol data of the multi-source data by task priority based on different data transmission links.

[0021] Optionally, the step of adding the variable data to the device acquisition queue based on the drive object includes:

[0022] Obtain the device information and variable attributes corresponding to the variable data based on the drive object;

[0023] Obtain a device list based on the device information and variable attributes;

[0024] Traverse the device list and create a device object corresponding to the variable data;

[0025] Add the variable data to the device acquisition queue based on the device object.

[0026] Optionally, the step of adding the variable data to the device acquisition queue based on the device object includes:

[0027] Add the variable data located in the same data transmission link to the same device object;

[0028] Classify the variable data in the device object according to the variable area and period, and add the classified variable data to the corresponding device acquisition queue.

[0029] In addition, to achieve the above object, the present application further provides a multi-source data management device, which includes:

[0030] A drive management module, which is used to obtain a variable list of multi-source data and generate an instantiated multi-source data variable model based on the variable list of the multi-source data;

[0031] A link management module, which is used to create a data transmission link based on the instantiated multi-source data variable model;

[0032] A variable management module, which is used to manage variables of the multi-source data based on the data transmission link;

[0033] A data mapping module, which is used to obtain the drive name of the variable data in the data transmission link and create a drive object corresponding to the variable data based on the drive name;

[0034] The data mapping module is further used to add the variable data to the device acquisition queue based on the drive object.

[0035] In addition, to achieve the above object, the present application further provides a multi-source data management device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, the steps of the multi-source data management method described above are implemented.

[0036] In addition, to achieve the above object, the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the multi-source data management method described above are implemented.

[0037] The present application provides a multi-source data management method, apparatus, device, and computer-readable storage medium. In the multi-source data management method, first, a variable list of multi-source data is obtained, and an instantiated multi-source data variable model is generated based on the variable list of the multi-source data; then, a data transmission link is created based on the instantiated multi-source data variable model; thereafter, variable management is performed on the multi-source data based on the data transmission link; then, the driver name of the variable data in the data transmission link is obtained, and a driver object corresponding to the variable data is created based on the driver name; then, the device list is traversed based on the driver object, and a device object corresponding to the variable data is created; finally, the variable data is added to the device acquisition queue based on the device object. By integrating and uniformly managing multi-source data, the present application realizes data interaction between different devices, improves management efficiency, and when a device fails, can realize rapid switching of redundant devices of multi-link data sources, ensuring production safety and product quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only a part of the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0039] Figure 1 FIG. is a flowchart of a multi-source data management method provided by an embodiment of the present application;

[0040] Figure 2 FIG. is a schematic diagram of a multi-data source data integration framework involved in a multi-source data management method provided by an embodiment of the present application;

[0041] Figure 3 FIG. is a schematic diagram of a transmission link creation process involved in a multi-source data management method provided by an embodiment of the present application;

[0042] Figure 4 FIG. is a schematic diagram of the structure of a multi-source data management apparatus provided by an embodiment of the present application;

[0043] Figure 5 FIG. is a schematic diagram of the hardware structure of a multi-source data management device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0044] In the following description, specific details such as specific system architectures, technologies, etc. are presented for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the embodiments of the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the embodiments of the present application.

[0045] It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from that in the flowchart. The terms "first", "second", etc. in the specification, claims, and the above-mentioned drawings are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence.

[0046] It should also be understood that the references to "one embodiment" or "some embodiments" etc. described in the specification of the embodiments of the present application mean that specific features, structures, or characteristics described in connection with that embodiment are included in one or more embodiments of the embodiments of the present application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "comprising", "including", "having", and their variants all mean "including but not limited to", unless otherwise specifically emphasized in another way.

[0047] With the rapid upgrade of the digital transformation of factory enterprises, industrial transmission protocols are also developing rapidly. To support the digital transformation of enterprises, the types of protocols supported by factory control devices are diverse. Therefore, in the process of developing digital monitoring software, it is necessary to collect and manage data for devices supporting different protocols.

[0048] In the process of developing digital monitoring software, it is necessary to collect data for devices supporting different protocols. For example, when developing the digital software for the equipment of manufacturer A, if it is necessary to collect data for the equipment of manufacturer B, it is necessary to start from the collection layer and then to the storage and management of variables. The development workload for different types of equipment is large. Managed through a database, the management and maintenance process of multi-source data is complex and it is difficult to adapt to the changes of factory equipment and the integrated management and operational reliability of multi-source data.

[0049] The existing multi-source data management solutions mainly focus on database management, that is, corresponding databases are established for devices with different protocols for data collection and data management. However, the data formats of devices with different protocols are diverse, resulting in a large amount of development, management, and maintenance work when adding a new protocol device. Moreover, with the diversification of factory control device protocols, various protocol data islands will gradually form during the operation of this solution, making it difficult to achieve data interaction between devices, with low management efficiency. When a device fails, rapid switching of redundant devices with multi-link data sources cannot be achieved, seriously affecting production safety and product quality.

[0050] Based on this, the embodiments of this application provide a multi-source data management method, device, equipment, and computer-readable storage medium. By integrating and uniformly managing multi-source data, data interaction between different devices is achieved, management efficiency is improved, and when a device fails, rapid switching of redundant devices with multi-link data sources can be realized, ensuring production safety and product quality.

[0051] The multi-source data management method, device, equipment, and computer-readable storage medium provided by the embodiments of this application are specifically described through the following embodiments. First, the multi-source data management method in the embodiments of this application is described.

[0052] The embodiments of this application provide a multi-source data management method. Refer to Figure 1 , Figure 1 which is a schematic flowchart of a multi-source data management method provided by an embodiment of this application. This multi-source data management method can be applied to multi-source data management equipment. As Figure 1 shown, the multi-source data management method provided in this embodiment includes steps S10 to S50.

[0053] Step S10, obtain the variable list of multi-source data, and generate an instantiated multi-source data variable model based on the variable list of the multi-source data;

[0054] It should be noted that in this embodiment, the execution entity is a multi-source data management device. This multi-source data management device can be a monitoring device, which contains a multi-data source data integration framework with an integrated management module as the core. As Figure 2 shown, in this multi-data source data integration framework, the integrated management module efficiently collaborates and integrates through data transmission links, variable management, and multi-source data interfaces, providing a basis for multi-data source integration; the multi-source data interface realizes the scalability and maintainability of device data for multi-source protocols; the data transmission link can integrate devices according to different link types, improving device management efficiency and communication performance, and is the core module for redundant device switching and multi-link collaborative management; variable management provides an effective interaction means for the unified management of heterogeneous data of multi-data sources and the collaborative interaction of control devices.

[0055] As an example, the multi-source data is variable data from different devices, and these devices may use the same protocol or different protocols. For this reason, this embodiment extracts the commonalities of these variable data, that is, variable attribute information such as device type, protocol type, variable area, address, and variable period as templates, generates corresponding variable configuration files, and then unifies the formats of the variable data input by different devices to obtain a variable list of multi-source data.

[0056] Step S20: Create a data transmission link based on the instantiated multi-source data variable model;

[0057] In this embodiment, after the multi-source data management device unifies the multi-source data variable model through the integrated management module, the integrated management module obtains the driver information corresponding to the variable data of different protocols from the instantiated multi-source data variable model according to the loaded configuration information. The driver information includes the variable configuration information and connection configuration information of the variable data. Then, a corresponding data transmission link is created based on the driver information to transmit the corresponding variable data. The data transmission link can include serial communication types and Ethernet communication types.

[0058] As an example, the data streams of different devices select corresponding data transmission links for transmission according to their different protocols. After the variable data passes through the data transmission link, the integrated management module also needs to uniformly manage these variable data.

[0059] Step S30: Perform variable management on the multi-source data based on the data transmission link;

[0060] In this embodiment, after the multi-source data management device completes the link management, it is necessary to distribute different variable data in the variable list of the multi-source data to the corresponding data transmission links according to the corresponding driver protocols. The variable data of different devices will be input into the corresponding data transmission links through the common interface of the driver call provided by the integrated management module. After these variable data enter the data transmission link, the integrated management module will call the variable management module to manage them according to the variable attributes of these variable data, so that the variable attributes to be collected can be transmitted to the corresponding data collection queue.

[0061] Step S40: Obtain the driver name of the variable data in the data transmission link, and create a driver object corresponding to the variable data based on the driver name;

[0062] In this embodiment, after the multi-source data management device completes variable management by invoking the variable management module, it can classify the managed variable data into corresponding data acquisition queues to complete the distribution of variable data. Specifically, a driver object for accessing the device needs to be created based on the variable data. The creation of the driver object is based on the driver name in the variable attributes of the variable data. After the creation of the driver object is completed, the driver object can be invoked based on the interface of the integrated management module for invoking the driver.

[0063] Step S50: Add the variable data to the device acquisition queue based on the driver object.

[0064] In this embodiment, after the multi-source data management device completes the creation of the driver object, it can obtain the device list of the corresponding data transmission link based on the device and variable information for invoking the driver object through the multi-source data interface. After obtaining the device list, it can traverse the device list and create corresponding device objects as the mapping of the device in the data acquisition queue.

[0065] In this embodiment, after the multi-source data management device completes the construction of the device object, it is necessary to add variables of the same channel to the same device object, classify the variable data in the device object according to the variable area and period, and after the classification is completed, package the variable data into data packets and put the data packets into the data acquisition queue to complete the integration and management of the entire multi-source data.

[0066] This embodiment proposes a multi-source data management method. First, obtain the variable list of the multi-source data, and generate an instantiated multi-source data variable model based on the variable list of the multi-source data; then create a data transmission link based on the instantiated multi-source data variable model; then perform variable management on the multi-source data based on the data transmission link; then obtain the driver name of the variable data in the data transmission link, and create a driver object corresponding to the variable data based on the driver name; then traverse the device list based on the driver object and create a device object corresponding to the variable data; finally, add the variable data to the device acquisition queue based on the device object. This embodiment realizes data interaction between different devices through the integration and unified management of multi-source data, improves the management efficiency, and when a device fails, it can realize the rapid switching of redundant devices of multi-link data sources, ensuring production safety and product quality.

[0067] Further, in some feasible embodiments, the step of generating an instantiated multi-source data variable model based on the variable list of the multi-source data in step S10 includes:

[0068] Step S101: Obtain the variable attributes of the multi-source data from the variable list of the multi-source data.

[0069] As an example, the variable list of multi-source data includes variable data of different protocols. Since the protocol types corresponding to these variable data are different, the variable models of these variable data are also different. Protocols and device objects registered through the same multi-source data interface for different protocols.

[0070] Step S102, substitute the variable attributes of the multi-source data into a predefined variable and driver model to obtain an instantiated multi-source data variable model.

[0071] In this embodiment, according to the loaded configuration information, the multi-source data variable model is unified through an integrated management module. The integrated management module provides a common interface for driver invocation and an interface for the integrated module to invoke the driver. For example, for protocols and device objects registered through the data interface for Siemens S7 protocol and general Modbus protocol respectively, the integrated management module instantiates driver information and acquisition variable attributes based on the variables and driver models already defined inside the framework, thereby realizing the integration and unification of variable models of multi-source data of different protocols.

[0072] In some feasible embodiments, before step S10, the multi-source data management method further includes:

[0073] Step S01, obtain a configuration file corresponding to the multi-source data, and generate a variable list of the multi-source data based on the configuration file.

[0074] In this embodiment, the configuration file includes a variable configuration file and a connection configuration file. The variable configuration file at least includes variable attributes such as device type, protocol type, variable area, variable address, and variable period. The variable configuration file can be generated by other software and sent to the integrated management module, or can be generated by the integrated management module after writing the received multi-source data into a preset configuration file framework; the connection configuration file is used to save connection configuration information, and certain attributes of the application program can be updated without recompiling the application program.

[0075] In some feasible embodiments, after step S20, the multi-source data management method further includes:

[0076] Step S21, add data transmission links of different link types to the task queue management link;

[0077] Step S22, manage the data transmission links through link type and task priority to achieve parallel link communication and serial link communication.

[0078] As an example, in this embodiment, the link is initialized according to the drive information, and the link information at least includes the communication type, device, communication configuration, and device driver, which are used to load and instantiate the data transmission link. In this embodiment, the multi-source data management device manages the link channels according to the link type and task priority to achieve concurrent and serial link communication. For example, for different link types such as serial ports and Ethernet, as Figure 3 shown, different types of transmission links are created and added to the task queue to manage the link.

[0079] In some feasible embodiments, step S30 includes:

[0080] Step S301, scheduling and managing the industrial protocol data of the multi-source data through the task priority based on different data transmission links

[0081] As an example, the industrial protocol data of multiple data sources is scheduled and managed through task priority based on different communication links. The information of the integration management module at least includes: a collection engine for implementing the cycle and priority queue, link session and driver management, and protocol adapter.

[0082] In some feasible embodiments, step S50 includes:

[0083] Step S51, obtaining the device information and variable attributes corresponding to the variable data based on the drive object;

[0084] Step S52, obtaining the device list based on the device information and variable attributes;

[0085] Step S53, traversing the device list and creating a device object corresponding to the variable data;

[0086] Step S54, adding the variable data to the device collection queue based on the device object.

[0087] It should be noted that after the multi-source data management device completes the creation of the drive object, it can obtain the device list of the corresponding data transmission link based on the device and variable information of the drive object called through the multi-source data interface. After obtaining the device list, it can traverse the device list and create a corresponding device object as the mapping of the device in the data collection queue.

[0088] It can be understood that before traversing the device list, it is necessary to initialize the drive object first and obtain the channel device list based on the device and variable information of the drive object.

[0089] In some feasible embodiments, step S54 includes:

[0090] Step S541: Add the variable data in the same data transmission link to the same device object;

[0091] As an example, to save storage space and speed up the data collection process, after the construction of the device object is completed, it is necessary to add the variables in the same channel to the same device object.

[0092] Step S542: Classify the variable data in the device object according to the variable area and period, and add the classified variable data to the corresponding device collection queue.

[0093] As an example, the multi-source data management device classifies the variable data in the device object according to the variable area and period. After classification, the data is packaged, and then the packaged data packet is put into the data collection queue to complete the integration and management of the entire multi-source data.

[0094] In addition, the embodiment of the present application also proposes a multi-source data management device. Refer to Figure 4 , Figure 4 which is a schematic structural diagram of a multi-source data management device provided by an embodiment of the present application. As shown in Figure 4 , in this embodiment, the multi-source data management device includes: a drive management module 100, a link management module 200, a variable management module 300, and a data mapping module 400.

[0095] The drive management module 100 is used to obtain the variable list of multi-source data and generate an instantiated multi-source data variable model based on the variable list of the multi-source data;

[0096] The link management module 200 is used to create a data transmission link based on the instantiated multi-source data variable model;

[0097] The variable management module 300 is used to perform variable management on the multi-source data based on the data transmission link;

[0098] The data mapping module 400 is used to obtain the drive name of the variable data in the data transmission link and create a drive object corresponding to the variable data based on the drive name;

[0099] The data mapping module 400 is further used to add the variable data to the device collection queue based on the drive object.

[0100] In some feasible embodiments, the multi-source data management device further includes:

[0101] A data input module, which is used to obtain a configuration file corresponding to multi-source data and generate a variable list of the multi-source data based on the configuration file.

[0102] In some feasible embodiments, the drive management module 100 is further configured to obtain variable attributes of the multi-source data from the variable list of the multi-source data;

[0103] Substitute the variable attributes of the multi-source data into a predefined variable and drive model to obtain an instantiated multi-source data variable model.

[0104] In some feasible embodiments, the link management module 200 is further configured to add data transmission links of different link types to a task queue management link;

[0105] Manage the data transmission links by link type and task priority to achieve parallel link communication and serial link communication.

[0106] In some feasible embodiments, the variable management module 300 is further configured to schedule and manage the industrial protocol data of the multi-source data based on different data transmission links by task priority.

[0107] In some feasible embodiments, the data mapping module 400 is further configured to obtain device information and variable attributes corresponding to the variable data based on the drive object;

[0108] Obtain a device list based on the device information and variable attributes;

[0109] Traverse the device list and create a device object corresponding to the variable data;

[0110] Add the variable data to a device acquisition queue based on the device object.

[0111] In some feasible embodiments, the data mapping module 400 is further configured to add the variable data located in the same data transmission link to the same device object;

[0112] Classify the variable data in the device object according to variable area and period, and add the classified variable data to the corresponding device acquisition queue.

[0113] The multi-source data management device provided in this embodiment and the multi-source data management method provided in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the multi-source data management method.

[0114] In addition, an embodiment of the present application further provides a multi-source data management device. The multi-source data management method applied to the multi-source data management device can be executed by a multi-source data management device. The multi-source data management device can be implemented in a software and / or hardware manner and integrated in the multi-source data management device. The multi-source data management device can be a mobile device such as a PC (Personal Computer), a mobile phone, a smart wearable device, etc. that can communicate with the network side.

[0115] Referring to Figure 5 , Figure 5 FIG. 1 is a schematic hardware structure diagram of a multi-source data management device provided in an embodiment of the present application. As Figure 5 shown, the multi-source data management device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to implement connection communication between these components. The user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard). Optionally, the user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wireless-Fidelity (WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the foregoing processor 1001.

[0116] Those skilled in the art can understand that Figure 5 the structure shown in FIG. 1 does not constitute a limitation on the multi-source data management device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0117] As Figure 5 shown, the memory 1005, as a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and a computer program.

[0118] In Figure 5In the multi-source data management device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with users; in this embodiment, the processor 1001 and the memory 1005 can be set in the multi-source data management device, and the multi-source data management device calls the computer program stored in the memory 1005 through the processor 1001 and performs the following operations:

[0119] Obtain the variable list of the multi-source data, and generate an instantiated multi-source data variable model based on the variable list of the multi-source data;

[0120] Create a data transmission link based on the instantiated multi-source data variable model;

[0121] Perform variable management on the multi-source data based on the data transmission link;

[0122] Obtain the driver name of the variable data in the data transmission link, and create a driver object corresponding to the variable data based on the driver name;

[0123] Add the variable data to the device acquisition queue based on the driver object.

[0124] Further, the processor 1001 can call the computer program stored in the memory 1005 and also perform the following operations:

[0125] Obtain the configuration file corresponding to the multi-source data, and generate the variable list of the multi-source data based on the configuration file.

[0126] Further, the processor 1001 can call the computer program stored in the memory 1005 and also perform the following operations:

[0127] Obtain the variable attributes of the multi-source data from the variable list of the multi-source data;

[0128] Substitute the variable attributes of the multi-source data into the predefined variable and driver model to obtain an instantiated multi-source data variable model.

[0129] Further, the processor 1001 can call the computer program stored in the memory 1005 and also perform the following operations:

[0130] Add data transmission links of different link types to the task queue management link;

[0131] Manage the data transmission link through the link type and task priority to achieve parallel link communication and serial link communication.

[0132] Further, the processor 1001 may call the computer program stored in the memory 1005 and further perform the following operations:

[0133] Schedule and manage the industrial protocol data of the multi-source data based on different data transmission links through task priorities.

[0134] Further, the processor 1001 may call the computer program stored in the memory 1005 and further perform the following operations:

[0135] Obtain the device information and variable attributes corresponding to the variable data based on the drive object;

[0136] Obtain a device list based on the device information and variable attributes;

[0137] Traverse the device list and create a device object corresponding to the variable data;

[0138] Add the variable data to the device acquisition queue based on the device object.

[0139] Further, the processor 1001 may call the computer program stored in the memory 1005 and further perform the following operations:

[0140] Add the variable data located in the same data transmission link to the same device object;

[0141] Classify the variable data in the device object according to the variable area and period, and add the classified variable data to the corresponding device acquisition queue.

[0142] The multi-source data management device proposed in this embodiment and the multi-source data management method applied to the multi-source data management device proposed in the above embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be referred to in any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the multi-source data management method.

[0143] In addition, an embodiment of the present application also proposes a computer-readable storage medium, which is applied to a computer. The computer-readable storage medium may be a non-volatile computer-readable storage medium. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements the multi-source data management method of any of the above embodiments.

[0144] Those of ordinary skill in the art will understand that all or some of the steps and systems disclosed in the above methods can be implemented as software, firmware, hardware, and their appropriate combinations. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or can be implemented as hardware, or can be implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, a communication medium typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0145] The above has specifically described the preferred implementation of the embodiments of the present application. However, the embodiments of the present application are not limited to the above-described implementation manners. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of the embodiments of the present application. These equivalent deformations or substitutions are all included within the scope defined by the claims of the embodiments of the present application.

Claims

1. A multi-source data management method, characterized in that, the multi-source data management method includes the following steps: Obtain a variable list of multi-source data, obtain the variable attributes of the multi-source data from the variable list of the multi-source data, and substitute the variable attributes of the multi-source data into a predefined variable and drive model to obtain an instantiated multi-source data variable model; Obtain the drive information corresponding to the variable data of different protocols from the instantiated multi-source data variable model, and create a corresponding data transmission link based on the drive information; Perform variable management on the multi-source data based on the data transmission link; Obtain the drive name of the variable data in the data transmission link, and create a drive object corresponding to the variable data based on the drive name; Add the variable data to the device acquisition queue based on the drive object.

2. The multi-source data management method according to claim 1, characterized in that, before the step of obtaining the multi-source data variable list, the multi-source data management method further includes: Obtain a configuration file corresponding to the multi-source data, and generate a variable list of the multi-source data based on the configuration file.

3. The multi-source data management method according to claim 1, characterized in that, after the step of creating a corresponding data transmission link based on the drive information, the multi-source data management method further includes: Add data transmission links of different link types to the task queue management link; Manage the data transmission link through link type and task priority to achieve parallel link communication and serial link communication.

4. The multi-source data management method according to claim 1, characterized in that, the step of performing variable management on the multi-source data based on the data transmission link includes: Schedule and manage the industrial protocol data of the multi-source data through task priority based on different data transmission links.

5. The multi-source data management method according to claim 1, characterized in that, the step of adding the variable data to the device acquisition queue based on the drive object includes: Obtain the device information and variable attributes corresponding to the variable data based on the drive object; Obtain a device list based on the device information and variable attributes; Traverse the device list and create a device object corresponding to the variable data; Add the variable data to the device acquisition queue based on the device object.

6. The multi-source data management method according to claim 5, characterized in that, the step of adding the variable data to the device acquisition queue based on the device object includes: Add the variable data located in the same data transmission link to the same device object; Classify the variable data in the device object according to the variable area and period, and add the classified variable data to the corresponding device acquisition queue.

7. A multi-source data management device, characterized in that, the multi-source data management device includes: A driver management module, which is used to obtain a variable list of multi-source data, obtain variable attributes of the multi-source data from the variable list of the multi-source data, and substitute the variable attributes of the multi-source data into a predefined variable and driver model to obtain an instantiated multi-source data variable model; A link management module, which is used to obtain driver information corresponding to variable data of different protocols from the instantiated multi-source data variable model and create a corresponding data transmission link based on the driver information; A variable management module, which is used to perform variable management on the multi-source data based on the data transmission link; A data mapping module, which is used to obtain the driver name of the variable data in the data transmission link and create a driver object corresponding to the variable data based on the driver name; The data mapping module is further used to add the variable data to the device acquisition queue based on the driver object.

8. A multi-source data management device, characterized in that, the multi-source data management device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the computer program is executed by the processor, the steps of the multi-source data management method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that, a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the multi-source data management method according to any one of claims 1 to 6 are implemented.

Images