Data acquisition system, data acquisition method, data acquisition device, equipment and medium

Abstract

The invention provides a data acquisition system, a data acquisition method, a data acquisition device, equipment and a medium. Relates to the field of Internet of Things. The system comprises a group end and a plurality of factory ends, and the group end communicates with the plurality of factory ends in a preset mode; wherein the group end is used for acquiring application attribute information of an Internet of Things application; the application attribute information comprises an application type and a data demand, and the application type is used for indicating whether the Internet of Things application needs to respond in time; the group end is also used for sending a data synchronization instruction to each factory end based on the application attribute information; the data synchronization instruction is used for indicating each factory end to synchronize data to the group end according to a data priority, and the data priority is obtained based on application attribute information; the factory end is used for collecting and storing field data generated by a plurality of field devices in a factory, and is also used for receiving a data synchronization instruction and synchronizing the field data to the group end according to the data synchronization instruction. The system provided by the invention is beneficial to the timely response of each Internet of Things application.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things, and in particular to a data acquisition system and data acquisition method, device, equipment, and medium. Background Art

[0002] Industrial Internet of Things is the application of Internet of Things in the industrial field. It realizes automated production and intelligent management by connecting various industrial equipment and machines. With the increasing application of Industrial Internet of Things, the technology of networking, data collection, data analysis and calculation, intelligent device connection and operation automation in a single factory environment is becoming more and more mature.

[0003] With the maturity of technology and the diversification of business needs, the Industrial Internet of Things is no longer just for the centralized processing of a single factory, and its scope of use has expanded to the linkage of multiple factories and even group management. In the group management scenario, it is necessary to synchronize data between the group end and each factory end to ensure the decision-making accuracy of each IoT application deployed on the group end.

[0004] In the known technology, there is a defect that the data synchronization from the factory end to the group end is not timely, which is not conducive to the timely response of various IoT applications on the group end. Summary of the invention

[0005] The present application provides a data collection system and data collection method, device, equipment, and medium for timely synchronizing data from the factory side to the group side, thereby achieving timely response of various Internet of Things applications on the group side.

[0006] In a first aspect, the present application provides a data acquisition system, the system comprising a group end and a plurality of factory ends, the group end and the plurality of factory ends communicate with each other in a preset manner; wherein:

[0007] The group end is further used to send a data synchronization instruction to each of the factory ends based on the application attribute information; the data synchronization instruction is used to instruct each of the factory ends to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information;

[0008] The factory end is used to collect and store field data generated by multiple field devices within the factory, and is also used to receive the data synchronization instruction and synchronize the field data to the group end according to the data synchronization instruction.

[0009] In a possible design, the factory end integrates the factory real-time database and the factory historical database; the group end integrates the group real-time database and the group historical database; the factory end is specifically used for:

[0010] Cache the collected field data into the factory real-time database, and store the field data in the factory real-time database into the factory historical database at intervals of a preset period;

[0011] For the field data in the factory real-time database, synchronizing the field data to the group real-time database according to the data priority;

[0012] For the field data in the factory historical database, the field data is synchronized to the group historical database according to the data priority.

[0013] In a possible design, the group end integrates a first monitoring function for monitoring the first connection status between each of the factory ends and the group end; the group end is further used for:

[0014] When the first monitoring function monitors that the first connection state between any factory end and the group end is disconnected, the time information is recorded and the factory end is marked as having abnormal connection.

[0015] In a possible design, the group end is also used for:

[0016] For the factory end whose first connection state is disconnected, when the first monitoring function monitors that the first connection state between the factory end and the group end is restored, the data synchronization instruction of the factory end is updated according to the time information to obtain an updated data synchronization instruction, and the updated data synchronization instruction is sent to the corresponding factory end;

[0017] The factory end is specifically configured to: upon receiving the update data synchronization instruction, synchronize the field data after the start time indicated by the time information to the group end according to the data priority.

[0018] In a possible design, the group end is also used for:

[0019] When the first monitoring function monitors that the first connection status between at least two factory ends and the group end is disconnected, first area information of the at least two factory ends is acquired; the first area information is used to indicate the first logical area and the first geographical area of ​​the factory end;

[0020] A first fault source is determined according to the first area information of the at least two factory ends; the first fault source is used to indicate the reason why the factory end is disconnected from the group end.

[0021] In a possible design, the factory end integrates a second monitoring function for monitoring the second connection state between each of the field devices and the factory end; the factory end is further used for:

[0022] When the second monitoring function monitors that the second connection state between the field device and the factory end is disconnected, the second connection state is synchronized to the group end in the preset manner.

[0023] In a possible design, the group end is also used for:

[0024] For any factory end, upon receiving at least two second connection states indicating disconnection synchronized by the factory end, acquiring second area information of the corresponding field device;

[0025] A second fault source is determined according to each piece of second area information; the second fault source is used to indicate the reason why the field device is disconnected from the factory end.

[0026] In a second aspect, the present application provides a data collection method, which is applied to the group end as described in any one of the first aspects; the method comprises:

[0027] Obtaining application attribute information of the Internet of Things application; the application attribute information includes an application type and data requirements, and the application type is used to indicate whether the Internet of Things application requires a timely response;

[0028] Based on the application attribute information, a data synchronization instruction is sent to each factory end; the data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information;

[0029] Receive the field data fed back by the factory end based on the data synchronization instruction; the field data is generated by any field device inside the factory corresponding to the factory end.

[0030] In a third aspect, the present application provides a data collection method, which is applied to the factory end as described in any one of the first aspects; the method comprises:

[0031] receiving a data synchronization instruction sent by the group end; the data synchronization instruction is used to instruct each of the factory ends to synchronize data to the group end according to the data priority, and the data priority is obtained by the group end according to the application attribute information of the Internet of Things application;

[0032] In response to the data synchronization instruction, the collected field data generated by any field device within the factory is synchronized to the group end according to the data priority.

[0033] In a fourth aspect, the present application provides a data acquisition device, comprising a module for executing the method as described in the second aspect, or the device comprises a module for executing the method as described in the third aspect.

[0034] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the data collection method described in the second aspect or the third aspect above.

[0035] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the data collection method described in the second aspect or the third aspect above is implemented.

[0036] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the data collection method described in the second aspect or the third aspect above.

[0037] The data acquisition system and data acquisition method, device, equipment, and medium provided by the present application include a group end and multiple factory ends that communicate with the group end in a preset manner. The group end sends a data synchronization instruction to each factory end based on the application attribute information of the Internet of Things application, so that each factory end synchronizes data to the group end according to the data priority. Through the data acquisition system of the present application, for Internet of Things applications that require timely response, the group end sets a higher data priority for the field data required by these Internet of Things applications, so that when the factory end synchronizes data to the group end, it can give priority to synchronizing the corresponding field data, so as to achieve timely response of the corresponding Internet of Things application. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0039] Figure 1 This is an application scenario diagram of a data acquisition system applicable to an embodiment of the present application;

[0040] Figure 2 The architecture of the data acquisition system provided in the embodiment of the present application is shown as follows Figure 1 ;

[0041] Figure 3 The architecture of the data acquisition system provided in the embodiment of the present application is shown as follows Figure 2 ;

[0042] Figure 4A Schematic diagram of the data collection method provided in the embodiment of the present application Figure 1 ;

[0043] Figure 4BSchematic diagram of the data collection method provided in the embodiment of the present application Figure 2 ;

[0044] Figure 5A A schematic diagram of the structure of the data acquisition device provided in the embodiment of the present application Figure 1 ;

[0045] Figure 5B A schematic diagram of the structure of the data acquisition device provided in the embodiment of the present application Figure 2 ;

[0046] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0048] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0049] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0050] The Internet of Things refers to connecting various physical devices, sensors, software and other technologies through the Internet to achieve data collection, exchange and management, so that these devices can work together and be intelligently controlled and managed. The Industrial Internet of Things is the application of the Internet of Things in the industrial field, which realizes automated production and intelligent management by connecting various industrial equipment and machines.

[0051] As the application of industrial Internet of Things becomes more and more extensive, the technology of industrial Internet of Things in networking, data collection, data analysis and calculation, intelligent device connection and operation automation in a single factory environment is becoming more and more mature. At present, with the maturity of technology and the diversified development of business needs, industrial Internet of Things is no longer satisfied with the centralized processing of a single factory, and its scope of use has gradually expanded to the linkage of multiple factories and even group management and control.

[0052] It is understandable that in the group management scenario, data synchronization between the group and each factory needs to be achieved to ensure the decision accuracy of each IoT application deployed on the group. Among them, the IoT application is used to implement corresponding functions based on the field data synchronized by each factory, for example, to achieve intelligent early warning, intelligent prediction, etc.

[0053] In the known technology, when each factory communicates with the group end and synchronizes the collected field data to the group end, due to the huge amount of data, there is a defect that the data required by the group end cannot be synchronized to the group end in time, which is not conducive to the timely response of various IoT applications on the group end.

[0054] Therefore, the present application provides a data collection system and a data collection method, device, equipment, and medium for timely synchronizing the data required by the group end to the group end. Specifically, in the present application, the group end issues data synchronization instructions to each factory end according to the application attribute information of each IoT application, so that each factory end synchronizes the corresponding field data to the group end in a timely manner according to the corresponding data priority, thereby achieving timely response of each IoT application on the group end.

[0055] It can be understood that the system of the present application is applicable to data collection in any group management and control scenario. Figure 1 is an application scenario diagram of a data acquisition system applicable to an embodiment of the present application, such as Figure 1 As shown, the system of the present application is applicable to the data collection scenario of a bank. Banks often need to set up different bank branches in different locations, and some bank applications need to make decisions based on the data collected by each bank branch.

[0056] In the above scenario, the group end includes the bank main server, and the bank sub-server of the bank branch corresponds to a factory end. The bank main server communicates with n bank sub-servers in a preset way. The bank sub-servers synchronize the field data collected by the field devices set up by the bank branch to the bank main server. The bank main server integrates m IoT applications to make corresponding decisions based on the field data synchronized by the bank sub-servers.

[0057] It is understandable that the on-site equipment includes multiple electronic devices deployed at bank branches. For example, it can be a computer used by business personnel at the bank branch, an automatic teller machine set up at the bank branch, or an intelligent robot or monitoring equipment set up at the bank branch. This is not limited in the present application.

[0058] Through the setting of this application, each bank sub-server synchronizes the corresponding field data to the bank main server according to the data priority issued by the bank main server, so that the bank main server can promptly receive the field data required by some IoT applications that require timely response, thereby realizing timely response of these IoT applications.

[0059] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings. It is worth noting that the methods of the following embodiments are described using the data collection scenario of a bank as an example.

[0060] The present application embodiment provides a data acquisition system. Figure 2 The architecture of the data acquisition system provided in the embodiment of the present application is shown as follows Figure 1 .like Figure 2 As shown, the data acquisition system includes a group end and n factory ends. The group end integrates m Internet of Things applications. Multiple factory ends communicate with the group end through a preset method. Specifically, the preset method can be MQTT method, HTTP / HTTPS method, or any other method such as WebSockets. As long as the communication between the group end and the factory end can be achieved, this is not limited in this embodiment.

[0061] In this embodiment, the group end is used to obtain application attribute information of the IoT application. Specifically, the application attribute information includes application type and data requirements, wherein the application type is used to indicate whether the IoT application needs to respond in time, and the data requirement is used to indicate the field data required by the IoT application.

[0062] It can be understood that in this embodiment, the group end integrates the business database, and the application attribute information of the Internet of Things application is stored in the business database, specifically when the corresponding Internet of Things application is configured. The relevant staff configures the application attribute information based on the actual needs of the Internet of Things application, and stores the application attribute information in the business database. Specifically, the identifier of the Internet of Things application and the corresponding application attribute information are stored in the business database together. Based on this setting, when the group end obtains the application attribute information of the Internet of Things application, it first obtains the identifier of the Internet of Things application, and then searches and obtains the corresponding application attribute information in the business database based on the identifier.

[0063] In this embodiment, the group end is also used to send data synchronization instructions to each factory end based on the application attribute information. Specifically, the data synchronization instruction is used to instruct each factory end to synchronize field data to the group end according to the data priority. Among them, the data priority is obtained based on the application attribute information, which is specifically related to the application type of the corresponding Internet of Things application. If the application type of the Internet of Things application that requires the field data is that a timely response is required, the data priority of the corresponding field data is higher.

[0064] Optionally, in actual applications, for field data that also needs to be responded to in a timely manner, the data priority is further determined based on the factory priority of the factory to which it belongs and the device priority of the field device to which it belongs, which is not limited in this embodiment. It is understandable that the factory priority and device priority can be configured by relevant staff and stored in the business database on the group side.

[0065] Optionally, in actual applications, the group side monitors the network status in real time and dynamically adjusts the data priority based on the network status.

[0066] In this embodiment, each factory end is used to collect and store field data generated by multiple field devices within the factory, and is also used to receive data synchronization instructions issued by the group end, and synchronize field data to the group end according to the data synchronization instructions.

[0067] Specifically, in this embodiment, the factory side corresponds to a factory that deploys multiple field devices to collect corresponding field data. When the factory side receives the data synchronization instruction, it synchronizes the field data to the group side according to the data priority indicated by the data synchronization instruction.

[0068] It is understandable that, for a production plant, the field equipment may be various sensing devices such as temperature sensors and humidity sensors for monitoring the field data of the factory. For a bank branch, the field equipment may be electronic devices such as business personnel computers and automatic teller machines for obtaining field data in the branch. Accordingly, the field data is specifically the data collected by any of the aforementioned sensing devices or electronic devices.

[0069] In this embodiment, the group end sends the data synchronization instruction to each factory end. When receiving the data synchronization instruction, each factory end responds to the data synchronization instruction and synchronizes the corresponding field data to the group end according to the data priority indicated by the data synchronization instruction.

[0070] It is understandable that the data synchronization instruction is also used to indicate the timing of synchronizing data at the factory end. In this embodiment, once the data synchronization instruction is issued, the factory end responds to the data synchronization instruction and synchronizes the field data to the group end when the field data is collected.

[0071] Optionally, in actual applications, the factory end integrates the factory business database to store the device priority of each field device contained in the factory end, as well as the factory priority. When each factory end obtains the data synchronization instruction, it obtains the device priority and factory priority from the factory business database, updates the data priority according to the device priority and factory priority, and synchronizes the field data to the group end according to the updated data priority.

[0072] Optionally, the relevant staff configures the data collection program on the group side and deploys the data collection program to the corresponding factory side. The data collection program is initialized to pull the latest object model information, collection protocol and configuration information through the interface and store them in the above-mentioned business database.

[0073] It is understandable that when the relevant staff modifies the object model information or other information of any factory end, the modified factory end is notified in a preset manner to synchronize the latest information.

[0074] Through the data acquisition system provided in this embodiment, the group end sends data synchronization instructions to each factory end according to the application attribute information of each Internet of Things application, so that the factory end can synchronize the various field data of each Internet of Things application that needs to be responded to in a timely manner to the group end in priority according to the data priority, thereby facilitating the timely response of the corresponding Internet of Things application.

[0075] In one possible design, Figure 3 The architecture of the data acquisition system provided in the embodiment of the present application is shown as follows Figure 2 Based on the above-mentioned embodiments, this embodiment further explains the group side and the factory side in detail.

[0076] like Figure 3 As shown, in this embodiment, the factory side integrates the factory real-time database and the factory historical database, and the group side integrates the group real-time database and the group historical database.

[0077] On this basis, the factory end is specifically used to: cache the collected field data into the factory real-time database, and store the field data in the factory real-time database into the factory historical database at intervals of a preset period.

[0078] In this embodiment, the setting of the preset period is related to the amount of data received by the factory end and the storage capacity of the factory real-time database. Exemplarily, considering the amount of data received by the factory end and the storage capacity of the factory real-time database, the preset period is set to 2 hours.

[0079] In this embodiment, the factory real-time database is specifically a Redis database, and the factory history database is specifically a MySQL database. In practical applications, the factory real-time database can also use other real-time databases, and the factory history database can also use other history databases, which are not limited in this embodiment.

[0080] In this embodiment, the factory end is specifically used to: when caching the field data into the factory real-time database, obtain the device code of the field device corresponding to the field data, and cache the field data and the corresponding device code into the factory real-time database. The device code includes a device identifier and a factory identifier.

[0081] Through this setting, for at least two field devices with the same device identification from different factories, the group end can determine the source of the field data based on the factory identification contained therein.

[0082] Furthermore, when the factory end synchronizes data with the group end, the factory end is specifically used to: synchronize the field data in the factory real-time database to the group real-time database according to the data priority. For the field data in the factory historical database, synchronize the field data to the group historical database according to the data priority.

[0083] Specifically, in this embodiment, for the field data in the factory history database, the factory side starts a new thread, and synchronizes the latest received field data to the group history database according to the data priority at every preset time interval.

[0084] Correspondingly, the group end is specifically used for: upon receiving the field data in the factory historical database synchronized by each factory end, obtaining the data type of the field data, and storing the field data in the group historical database according to the data type.

[0085] Specifically, the group uses columnar storage technologies such as Parquet and ORC, as well as object storage systems, to perform tiered storage on the field data synchronized from the factory side according to the data type and data access type of different field data, optimize data storage and access efficiency, and improve resource utilization and query performance.

[0086] This setting can avoid the complex data synchronization process between the group and the factory, and improve the data transmission efficiency. In addition, the factory stores the collected field data through the factory historical database, which can ensure the data consistency between the group and the factory when the factory real-time database cannot synchronize the field data to the group.

[0087] like Figure 3 As shown, in this embodiment, the group end is also integrated with a first monitoring function for monitoring the first connection status between each factory end and the group end.

[0088] On this basis, the group end is also used to: when the first monitoring function monitors that the first connection state between any factory end and the group end is disconnected, record the time information and mark the factory end as abnormally connected.

[0089] In this embodiment, the group end and the factory end communicate via MQTT. Specifically, the group end integrates the MQTT service center, and each factory end integrates the MQTT client. When any factory end crashes or encounters other problems, the MQTT client integrated in the factory end and the MQTT service center integrated in the group end are disconnected. At this time, the first monitoring function monitors that the first connection state between the factory end and the group end is disconnected.

[0090] In this embodiment, when the group end receives the first connection status, it marks the corresponding factory end as abnormal connection to remind the relevant staff. At the same time, the group end records the time information at this time, that is, the time when the factory end is disconnected from the group end.

[0091] Furthermore, in this embodiment, the group end is also used for: for a factory end whose first connection state is disconnected, when the first listening function monitors that the first connection state between the factory end and the group end is restored connection, updating the data synchronization instruction of the factory end according to the time information, obtaining the updated data synchronization instruction, and sending the updated data synchronization instruction to the corresponding factory end.

[0092] Correspondingly, the factory end is specifically used to: upon receiving the update data synchronization instruction, synchronize the field data after the start time indicated by the time information to the group end according to the data priority.

[0093] In this embodiment, the first listening function integrated in the group end monitors the first connection status between the factory end and the group end, and when the first connection status is the recovery connection, updates the data synchronization instruction for the factory end according to the previously recorded time information, and obtains the updated data synchronization instruction, so that the factory end synchronizes the field data after the start time indicated by the time information to the group end according to the data priority according to the updated data synchronization instruction.

[0094] It is understandable that, for the factory end whose first connection state with the group end is monitored by the first monitoring function as being a normal connection, it still synchronizes data to the group end according to the data synchronization instruction initially issued by the group end.

[0095] Optionally, when the factory end and the group end are connected again and respond to the update data synchronization instruction to synchronize data, the group end uses error correction code technology such as Reed-Solomon to ensure data integrity. The Bloom filter is optimized through an intelligent optimization algorithm to reduce the false alarm rate and increase the detection speed, thereby speeding up the data recovery process.

[0096] In actual applications, when the group integrates a new IoT application, or when the application attribute information of an existing IoT application is changed, the data synchronization instruction is changed synchronously according to the application attribute information of the current IoT application and sent to multiple factory ends.

[0097] With this setting, when the factory side is unable to synchronize field data to the group side, when the connection between the factory side and the group side is restored, the field data during the disconnection period can also be synchronized to the group side, thereby ultimately achieving data consistency between the group side and the factory side.

[0098] Furthermore, in the present embodiment, the group end is also used for: when the first monitoring function monitors that the first connection state between at least two factory ends and the group end is disconnected, obtaining the first area information of at least two factory ends; the first area information is used to indicate the first logical area and the first geographical area of ​​the factory end; determining the first fault source according to the first area information of at least two factory ends; the first fault source is used to indicate the reason for the disconnection between the factory end and the group end.

[0099] In this embodiment, when the first connection status between at least two factory terminals and the group terminal is disconnected, the group terminal obtains the first logical area and the first geographical area of ​​at least two factory terminals. It can be understood that the first logical area is used to indicate the area divided according to the function, purpose or other logical standards such as the network architecture and field equipment model adopted by the factory terminal. The first geographical area is the area obtained by dividing based on the physical location.

[0100] Specifically, the group end determines the first fault source according to the regionalized fault detection algorithm based on the first logical area and the first geographical area of ​​the at least two factory ends.

[0101] Through this setting, when at least two factory ends are disconnected from the group end, the group end determines the first fault source based on the first logical area and the first geographical area. On the one hand, it can enable relevant personnel to know the reason why the factory end is disconnected from the group end. On the other hand, the use of a regionalized fault detection algorithm to determine the first fault source can reduce the complexity of fault detection.

[0102] like Figure 3 As shown, each factory end is also integrated with a second monitoring function for monitoring the second connection status between each field device and the factory end.

[0103] On this basis, the factory end is also used to: when the second monitoring function monitors that the second connection state between the field device and the factory end is disconnected, synchronize the second connection state to the group end in a preset manner.

[0104] Correspondingly, the group end is also used for: for any factory end, upon receiving at least two second connection states indicating disconnection synchronized by the factory end, obtaining the second area information of the corresponding field equipment; determining the second fault source based on each second area information; the second fault source is used to indicate the reason why the field equipment is disconnected from the factory end.

[0105] In this embodiment, the second monitoring function is specifically used to monitor the acquisition protocol of the field device and the corresponding factory end. When the acquisition protocol connection is disconnected, the second monitoring function monitors that the second connection state between the field device and the factory end is disconnected. At this time, the factory end synchronizes the second connection state to the group end through the integrated MQTT client to enable the group end to monitor the acquisition protocol. Optionally, when the group end receives the second connection state, it marks the corresponding field device of the corresponding factory end as disconnected to make the relevant staff aware of the state.

[0106] In this embodiment, for at least two disconnected second connection states of the same factory end, the group end obtains the second area information of the corresponding field device. It can be understood that the second area information includes the second logical area and the second geographical area, and its specific meaning can be found in the above content for the definition of the first logical area and the first geographical area, which will not be repeated here.

[0107] The group uses machine learning algorithms such as decision trees or random forests to analyze the historical field data of the corresponding field equipment, and combines it with a regionalized fault detection algorithm to determine the second fault source of the field equipment based on the second logical area and second geographical area of ​​the field equipment, so that relevant personnel can promptly know the reason why the corresponding field equipment is disconnected from the factory end.

[0108] Optionally, in actual applications, the data acquisition system of the present application also includes edge computing devices deployed in each factory, which are used to complete some computing tasks locally to reduce the bandwidth requirements for data transmission and reduce the load pressure on the group end.

[0109] Exemplarily, the data classification task can be completed on the edge computing device. Specifically, the edge computing device uses any deep learning model such as convolutional neural network, recurrent neural network, etc. to classify the field data to obtain more accurate data types.

[0110] For example, the data compression task can be placed on the edge computing device. Specifically, the edge computing device uses a lightweight compression algorithm such as LZ4 or Snappy to further reduce the bandwidth requirement for data transmission while ensuring data integrity and transmission speed.

[0111] The present application provides a data collection method, which is applied to the group end in the aforementioned embodiment. Figure 4ASchematic diagram of the data collection method provided in the embodiment of the present application Figure 1 . Specifically, Figure 4A As shown, the following steps are included:

[0112] S401A, obtaining application attribute information of an IoT application.

[0113] Among them, the application attribute information includes application type and data requirements. The application type is used to indicate whether the IoT application needs to respond in a timely manner.

[0114] It is understandable that the IoT application is a service provided by the group end for realizing corresponding functions based on the group end data. For example, the IoT application may be a temperature warning service. Specifically, the definition of the IoT application and application attribute information may refer to the definition in the aforementioned system embodiment, which will not be repeated here.

[0115] S402A, based on the application attribute information, send a data synchronization instruction to each factory end.

[0116] The data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information.

[0117] S403A, receiving the field data fed back by the factory based on the data synchronization instruction.

[0118] Specifically, the field data is generated by any field device inside the factory corresponding to the factory end.

[0119] In this embodiment, the group end sends a data synchronization instruction to each factory end based on the application attribute information, and receives the field data fed back by the factory end. Specifically, the way the group end obtains the data synchronization instruction according to the application attribute information, the way the data synchronization instruction is sent, and the way the field data is received can all refer to the limitations of the aforementioned system embodiment, and will not be repeated here.

[0120] Through the method of this embodiment, the group end can promptly receive the field data that needs to be obtained in a timely manner, thereby achieving timely response of the Internet of Things application.

[0121] The present application provides a data collection method, which is applied to the factory side in the aforementioned embodiment. Figure 4B Schematic diagram of the data collection method provided in the embodiment of the present application Figure 2 . Specifically, Figure 4B As shown, the following steps are included:

[0122] S401B, receiving a data synchronization instruction sent by the group end.

[0123] Among them, the data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority. The data priority is obtained by the group end based on the application attribute information of the Internet of Things application.

[0124] S402B, responding to the data synchronization instruction, synchronizes the collected field data generated by any field device inside the factory to the group end according to the data priority.

[0125] The data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information.

[0126] In this embodiment, the factory side receives the data synchronization instruction sent by the group side based on the application attribute information of each IoT application, and responds to the data synchronization instruction, and synchronizes the field data generated by each field device to the group side according to the data priority indicated by the data synchronization instruction. Specifically, the factory side receives the data synchronization instruction and synchronizes the field data, the limitation of the data synchronization instruction, etc., all of which can be referred to the limitation of the aforementioned system embodiment, and will not be repeated here.

[0127] Through the method of this embodiment, the factory side can synchronize field data according to data priority, so that the group side can promptly receive the field data that needs to be obtained in a timely manner, thereby achieving timely response of the Internet of Things application.

[0128] The above embodiments introduce a data acquisition method from the perspective of method flow, and the following embodiments introduce a data acquisition device from the perspective of a virtual module or a virtual unit. Please refer to the following embodiments for details.

[0129] An embodiment of the present application provides a data collection device for executing a method applied to a group end. Figure 5A A schematic diagram of the structure of the data acquisition device provided in the embodiment of the present application Figure 1 .like Figure 5A As shown, the data acquisition device includes: an acquisition module 51, a sending module 52 and a first receiving module 53;

[0130] The acquisition module 51 is used to acquire application attribute information of the Internet of Things application; the application attribute information includes application type and data requirements, and the application type is used to indicate whether the Internet of Things application needs to respond in a timely manner;

[0131] The sending module 52 is used to send a data synchronization instruction to each factory end based on the application attribute information; the data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information;

[0132] The first receiving module 53 is used to receive the field data fed back by the factory end based on the data synchronization instruction; the field data is generated by any field device inside the factory corresponding to the factory end.

[0133] An embodiment of the present application provides a data acquisition device for executing a method applied to a factory. Figure 5B A schematic diagram of the structure of the data acquisition device provided in the embodiment of the present application Figure 2 .like Figure 5B As shown, the data acquisition device includes: a second receiving module 54 and a response module 55.

[0134] The second receiving module 54 is used to receive a data synchronization instruction sent by the group end; the data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained by the group end according to the application attribute information of the Internet of Things application;

[0135] The response module 55 is used to respond to the data synchronization instruction and synchronize the collected field data generated by any field device inside the factory to the group end according to the data priority.

[0136] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0137] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the electronic device may include: a transceiver 61 , a processor 62 , and a memory 63 .

[0138] The processor 62 executes the computer execution instructions stored in the memory, so that the processor 62 executes the scheme in the above embodiment. The processor 62 can be a general-purpose processor, including a central processing unit CPU, a network processor (NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0139] The memory 63 is connected to the processor 62 via a system bus and completes communication between them. The memory 63 is used to store computer program instructions.

[0140] The transceiver 61 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.

[0141] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0142] An embodiment of the present application also provides a chip for running instructions, which is used to execute the technical solution of the business data collection method in the above embodiment.

[0143] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the business data collection method of the above embodiment.

[0144] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, it can implement the technical solution of the business data collection method in the above embodiment.

[0145] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0146] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0147] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0148] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0149] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0150] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0151] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0152] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0153] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0154] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0155] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data acquisition system, characterized in that: The system includes a group end and multiple factory ends, and the group end and the multiple factory ends communicate with each other in a preset manner; wherein, The group end is used to obtain application attribute information of the Internet of Things application; the application attribute information includes application type and data requirements, and the application type is used to indicate whether the Internet of Things application needs to respond in time; The group end is further used to send a data synchronization instruction to each of the factory ends based on the application attribute information; the data synchronization instruction is used to instruct each of the factory ends to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information; The factory end is used to collect and store field data generated by multiple field devices within the factory, and is also used to receive the data synchronization instruction and synchronize the field data to the group end according to the data synchronization instruction.

2. The system according to claim 1, characterized in that The factory end integrates the factory real-time database and the factory historical database; the group end integrates the group real-time database and the group historical database; the factory end is specifically used for: Cache the collected field data into the factory real-time database, and store the field data in the factory real-time database into the factory historical database at intervals of a preset period; For the field data in the factory real-time database, synchronizing the field data to the group real-time database according to the data priority; For the field data in the factory historical database, the field data is synchronized to the group historical database according to the data priority.

3. The system according to claim 1 or 2, characterized in that: The group end integrates a first monitoring function for monitoring the first connection status between each of the factory ends and the group end; the group end is also used for: When the first monitoring function monitors that the first connection state between any factory end and the group end is disconnected, the time information is recorded and the factory end is marked as having abnormal connection.

4. The system according to claim 3, characterized in that The group end is also used for: For the factory end whose first connection state is disconnected, when the first monitoring function monitors that the first connection state between the factory end and the group end is restored, the data synchronization instruction of the factory end is updated according to the time information to obtain an updated data synchronization instruction, and the updated data synchronization instruction is sent to the corresponding factory end; The factory end is specifically configured to: upon receiving the update data synchronization instruction, synchronize the field data after the start time indicated by the time information to the group end according to the data priority.

5. The system according to claim 3, characterized in that The group end is also used for: When the first monitoring function monitors that the first connection status between at least two factory ends and the group end is disconnected, obtaining first area information of the at least two factory ends; The first area information is used to indicate a first logical area and a first geographical area of ​​the factory end; Determining a first fault source according to the first area information of the at least two factory terminals; The first fault source is used to indicate the reason why the factory end is disconnected from the group end.

6. The system according to claim 1 or 2, characterized in that: The factory end integrates a second monitoring function for monitoring the second connection status between each of the field devices and the factory end; the factory end is also used for: When the second monitoring function monitors that the second connection state between the field device and the factory end is disconnected, the second connection state is synchronized to the group end in the preset manner.

7. The system according to claim 6, characterized in that The group end is also used for: For any factory end, upon receiving at least two second connection states indicating disconnection synchronized by the factory end, acquiring second area information of the corresponding field device; Determining a second fault source according to each of the second area information; The second fault source is used to indicate the reason why the field device is disconnected from the factory end.

8. A data collection method, characterized in that: Applied to the group end according to any one of claims 1 to 7; the method comprises: Obtaining application attribute information of the Internet of Things application; the application attribute information includes an application type and data requirements, and the application type is used to indicate whether the Internet of Things application requires a timely response; Based on the application attribute information, a data synchronization instruction is sent to each factory end; the data synchronization instruction is used to instruct each factory end to synchronize data to the group end according to the data priority, and the data priority is obtained based on the application attribute information; Receive the field data fed back by the factory end based on the data synchronization instruction; the field data is generated by any field device inside the factory corresponding to the factory end.

9. A data collection method, characterized in that: Applied to the factory end as described in any one of claims 1 to 7; the method comprises: receiving a data synchronization instruction sent by the group end; the data synchronization instruction is used to instruct each of the factory ends to synchronize data to the group end according to the data priority, and the data priority is obtained by the group end according to the application attribute information of the Internet of Things application; In response to the data synchronization instruction, the collected field data generated by any field device within the factory is synchronized to the group end according to the data priority.

10. A data acquisition device, characterized in that: The device comprises a module for executing the method of claim 8, or the device comprises a module for executing the method of claim 9.

11. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to claim 8 or 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to claim 8 or 9 when executed by a processor.

13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to claim 8 or 9 when being executed by a processor.

Images