Internet of Things data processing method, related device, computing device and storage medium

Abstract

The present application relates to the field of data processing of Internet of Things systems, and discloses an Internet of Things data processing method, related devices, computing equipment and storage medium, the method comprising: obtaining a configuration file for a first acquisition engine to collect Internet of Things data according to an Internet of Things data collection instruction, creating a data acquisition thread corresponding to an Internet of Things device according to the configuration file; using the data acquisition thread, loading multiple acquisition plug-ins respectively to obtain first Internet of Things data corresponding to multiple Internet of Things devices; collecting second Internet of Things data corresponding to a second Internet of Things device through a second fixed acquisition program; processing the first Internet of Things data and the second Internet of Things data to obtain processed Internet of Things data. The present application collects data of different types of protocols for Internet of Things devices in different scenarios, uses multiple acquisition plug-ins and fixed programs to cooperate in collecting data, and performs corresponding denoising and disturbance processing on the collected data to improve the accuracy of Internet of Things data.

Description

Technical Field

[0001] The present application relates to the field of data processing of Internet of Things systems, and more specifically to an Internet of Things data processing method, related devices, computing equipment and storage media. Background Art

[0002] With the development of technology, IoT devices are being used more and more widely. The usage rate of IoT devices is increasing in industry, commerce and family life. In specific application scenarios, in order to achieve efficient control and management of IoT devices, it is necessary to collect and process IoT device data accordingly. Traditional IoT data collection and processing is to directly report data to the IoT data platform through IoT devices. However, due to the large number of data types of IoT devices, different and complex data types, and the characteristics of continuity and large data volume, the data processing methods of existing IoT devices are not efficient. Improving the efficiency of IoT data processing and the accuracy of obtaining IoT data is conducive to improving the overall intelligence of the IoT system. Summary of the invention

[0003] The embodiments of the present application provide an Internet of Things data processing method, related devices, computing equipment and storage medium, which utilize multiple collection plug-ins and fixed programs to collect data, and perform corresponding denoising and disturbance processing on the collected data to improve the accuracy of the Internet of Things data.

[0004] In a first aspect, an embodiment of the present application provides an Internet of Things data processing method, the Internet of Things data processing method is applied to an Internet of Things system, the Internet of Things system includes an Internet of Things platform and an Internet of Things device, multiple data acquisition modules connected to the Internet of Things platform, the multiple data acquisition modules include a first data acquisition module and a second data acquisition module, the first data acquisition module includes a first acquisition engine and multiple acquisition plug-ins communicating with the first acquisition engine, the first acquisition engine is used to collect first Internet of Things data corresponding to multiple Internet of Things devices through the multiple acquisition plug-ins, the multiple Internet of Things devices include multiple different types of first Internet of Things devices, the second data acquisition module is a fixed acquisition program, the second data acquisition module uses the fixed acquisition program to collect second Internet of Things data corresponding to a second Internet of Things device, the Internet of Things data processing method includes:

[0005] Get IoT data collection instructions;

[0006] According to the IoT data collection instruction, obtain a configuration file for the first collection engine to collect IoT data, wherein the configuration file includes information of multiple collection plug-ins for collecting IoT data and information of multiple IoT devices connected to the multiple collection plug-ins;

[0007] According to the configuration file, create multiple data collection threads corresponding to the multiple IoT devices;

[0008] Using the multiple data collection threads, respectively load the multiple collection plug-ins to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices;

[0009] According to the IoT data collection instruction, collect second IoT data corresponding to the second IoT device through the second fixed collection program;

[0010] The first Internet of Things data and the second Internet of Things data are processed to obtain processed Internet of Things data.

[0011] In one embodiment, creating multiple data collection threads corresponding to the multiple IoT devices according to the configuration file includes:

[0012] Determine the number of the plurality of IoT devices according to the information of the plurality of IoT devices connected to the plurality of acquisition plug-ins;

[0013] Create data collection threads corresponding to the number of the multiple Internet of Things devices, and the data collection threads correspond to the multiple Internet of Things devices one by one.

[0014] In one embodiment, using the multiple data collection threads to load the multiple collection plug-ins respectively to obtain the first IoT data corresponding to the multiple IoT devices includes:

[0015] The multiple data collection threads are used to load the multiple collection plug-ins respectively, and the data point lists of the multiple Internet of Things devices are traversed to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices.

[0016] In one embodiment, the step of loading the multiple collection plug-ins respectively and traversing the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the multiple IoT devices includes:

[0017] Determine whether there is a flag bit in the data point list of the plurality of IoT devices;

[0018] If there is a flag bit, determine whether the flag bit meets the preset condition;

[0019] If the conditions are met, load the multiple collection plug-ins to traverse the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the IoT devices.

[0020] In one embodiment, the processing the first IoT data and the second IoT data to obtain processed IoT data includes:

[0021] Merging the first IoT data and the second IoT data to obtain merged IoT data;

[0022] De-noising the merged IoT data to obtain de-noised IoT data;

[0023] The denoised IoT data is subjected to disturbance processing to obtain disturbed IoT data.

[0024] In one embodiment, the merged IoT data includes actual IoT data collected by the IoT device in a target time period, and denoising the merged IoT data to obtain denoised IoT data includes:

[0025] Obtaining historical IoT data of the IoT device;

[0026] Determine the predicted IoT data of the IoT device in the target time period according to the historical IoT data and a preset algorithm,

[0027] Calculating the difference between the actual IoT data and the predicted IoT data;

[0028] If the difference exceeds a preset difference range, the actual IoT data is determined as noise data, and the noise data is removed from the merged IoT data to obtain denoised IoT data.

[0029] In one embodiment, performing disturbance processing on the denoised IoT data to obtain disturbed IoT data includes:

[0030] Performing decentralized processing on the denoised IoT data to obtain decentralized IoT data;

[0031] The disturbed Internet of Things data is obtained according to the dispersed Internet of Things data and a preset disturbance processing formula.

[0032] In a second aspect, an embodiment of the present application provides a device related to an Internet of Things data processing method, which has the function of implementing the Internet of Things data processing method provided in the first aspect above. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, and the modules can be software and / or hardware. In one embodiment, the device related to the Internet of Things data processing method includes:

[0033] The first acquisition module: used to obtain IoT data collection instructions;

[0034] A second acquisition module: used to acquire, according to the IoT data acquisition instruction, a configuration file used by the first acquisition engine to collect IoT data, wherein the configuration file includes information of multiple acquisition plug-ins for collecting IoT data and information of multiple IoT devices connected to the multiple acquisition plug-ins;

[0035] A creation module: used to create multiple data collection threads corresponding to the multiple IoT devices according to the configuration file;

[0036] A first acquisition module: used to use the multiple data acquisition threads to load the multiple acquisition plug-ins respectively to obtain the first IoT data corresponding to the multiple IoT devices;

[0037] A second collection module, configured to collect second IoT data corresponding to a second IoT device through the second fixed collection program according to the IoT data collection instruction;

[0038] Data processing module: used to process the first IoT data and the second IoT data to obtain processed IoT data.

[0039] In one embodiment, the creation module is specifically used to:

[0040] Determine the number of the plurality of IoT devices according to the information of the plurality of IoT devices connected to the plurality of acquisition plug-ins;

[0041] Create data collection threads corresponding to the number of the multiple Internet of Things devices, and the data collection threads correspond to the multiple Internet of Things devices one by one.

[0042] In one embodiment, the first acquisition module is specifically used to:

[0043] The multiple data collection threads are used to load the multiple collection plug-ins respectively, and the data point lists of the multiple Internet of Things devices are traversed to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices.

[0044] In one embodiment, the first acquisition module is specifically used to:

[0045] Determine whether there is a flag bit in the data point list of the plurality of IoT devices;

[0046] If there is a flag bit, determine whether the flag bit meets the preset condition;

[0047] If the conditions are met, load the multiple collection plug-ins to traverse the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the IoT devices.

[0048] In one embodiment, the data processing module is specifically used to:

[0049] Merging the first IoT data and the second IoT data to obtain merged IoT data;

[0050] Denoising unit: used for denoising the merged IoT data to obtain denoised IoT data;

[0051] Perturbation unit: used for performing perturbation processing on the denoised IoT data to obtain disturbed IoT data.

[0052] In one embodiment, the denoising unit is specifically configured to:

[0053] Obtaining historical IoT data of the IoT device;

[0054] Determine the predicted IoT data of the IoT device in the target time period according to the historical IoT data and a preset algorithm,

[0055] Calculating the difference between the actual IoT data and the predicted IoT data;

[0056] If the difference exceeds a preset difference range, the actual IoT data is determined as noise data, and the noise data is removed from the merged IoT data to obtain denoised IoT data.

[0057] In one embodiment, the disturbance unit is specifically used to:

[0058] Performing decentralized processing on the denoised IoT data to obtain decentralized IoT data;

[0059] The disturbed Internet of Things data is obtained according to the dispersed Internet of Things data and a preset disturbance processing formula.

[0060] In a third aspect, an embodiment of the present application provides a computing device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the Internet of Things data processing method described in the first aspect when executing the computer program.

[0061] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions, which, when executed on a computer, enables the computer to execute the Internet of Things data processing method as described in the first aspect.

[0062] This application collects data of different types of protocols from IoT devices in different scenarios, uses multiple collection plug-ins and fixed programs to collect data, and performs corresponding denoising and disturbance processing on the collected data to improve the accuracy of IoT data. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0064] Figure 1 It is a schematic diagram of a scenario of an IoT data processing-related device provided in an embodiment of the present application;

[0065] Figure 2 This is a schematic diagram of a scenario of another embodiment of the method for processing Internet of Things data provided by an embodiment of the present application;

[0066] Figure 3 This is a flow chart of an embodiment of the method for processing Internet of Things data provided in the embodiments of the present application;

[0067] Figure 4 It is a flowchart of another embodiment of the method for processing Internet of Things data provided in the embodiments of the present application;

[0068] Figure 5 This is a schematic diagram of the structure of a device related to the method for processing Internet of Things data according to an embodiment of the present application;

[0069] Figure 6 A schematic diagram of the structure of a content push device according to an embodiment of the present application;

[0070] Figure 7 A schematic diagram of the structure of a mobile phone in an embodiment of the present application;

[0071] Figure 8 A schematic diagram of the structure of a server in an embodiment of the present application.

[0072] In the drawings, the same or corresponding reference numerals represent the same or corresponding parts. DETAILED DESCRIPTION

[0073] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0074] In the following description, the specific embodiments of the present application will be described with reference to the steps and symbols performed by one or more computers, unless otherwise specified. Therefore, these steps and operations will be mentioned several times as being performed by a computer, and the computer execution referred to herein includes the operation of a computer processing unit by an electronic signal representing data in a structured form. This operation converts the data or maintains it at a location in the memory system of the computer, which can be reconfigured or otherwise change the operation of the computer in a manner familiar to testers in the field. The data structure maintained by the data is a physical location in the memory, which has specific characteristics defined by the data format. However, the principles of the present application are described in the above text, which does not represent a limitation, and testers in the field will understand that the various steps and operations described below can also be implemented in hardware.

[0075] The terms "module" or "unit" used herein may be considered as software objects executed on the computing system. The different components, modules, engines and services described herein may be considered as implementation objects on the computing system. The devices and methods described herein are preferably implemented in software, but may also be implemented in hardware, all within the scope of protection of this application.

[0076] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0077] The embodiments of the present application provide an Internet of Things data processing method, related devices and storage media.

[0078] See also Figure 1 , Figure 1The schematic diagram of the scenario of the IoT data processing related device provided in the embodiment of the present application, the IoT data processing related device may include an IoT system 100 and a user terminal 200, the IoT system 100 is connected via a network, and the IoT system 100 is integrated with the IoT data processing method related device. In the embodiment of the present application, the IoT system 100 may be a terminal device or a server, and the IoT system 100 may send IoT data to the user terminal 200.

[0079] In the embodiment of the present application, when the Internet of Things system 100 is a server, the server can be an independent server, or a server network or server cluster composed of servers. For example, the server described in the embodiment of the present application includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud server composed of a plurality of servers. Among them, the cloud server is composed of a large number of computers or network servers based on cloud computing (Cloud Computing). In the embodiment of the present application, communication between the server and the client can be achieved through any communication method, including but not limited to mobile communications based on the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), or computer network communications based on TCP / IP Protocol suite (TCP / IP), User Datagram Protocol (UDP) protocol, etc.

[0080] It is understandable that when the Internet of Things system 100 used in the embodiment of the present application is a terminal device, the terminal device can be a device that includes both receiving hardware and transmitting hardware, that is, a device with receiving and transmitting hardware that can perform two-way communication on a two-way communication link. Such terminal devices may include: cellular or other communication devices, which have a single-line display or a multi-line display or a cellular or other communication device without a multi-line display. The specific Internet of Things system 100 can be a desktop terminal or a mobile terminal, and the Internet of Things system 100 can be one of a mobile phone, a tablet computer, a laptop computer, etc.

[0081] The terminal device involved in the embodiments of the present application may also refer to a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. For example, a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges voice and / or data with a wireless access network. For example, personal communication service (English full name: Personal Communication service, English abbreviation: PCs) phone, cordless phone, session initiation protocol (sIP) phone, wireless local loop (Wireless Local Loop, English abbreviation: WLL) station, personal digital assistant (English full name: Personal Digital Assistant, English abbreviation: PDA) and other devices.

[0082] Those skilled in the art will understand that Figure 1 The application environment shown in the figure is only one application scenario of the present application solution and does not constitute a limitation on the application scenario of the present application solution. Other application environments may also include Figure 1 More or fewer computing devices, or computing device network connection relationships, such as Figure 1 Only one computing device is shown. It can be understood that the IoT data processing-related device may also include one or more other computing devices, or / and one or more other computing devices connected to the IoT system 100 network, which is not specifically limited here.

[0083] In addition, if Figure 1 As shown, the IoT data processing related device may also include a memory 300 for storing data, such as a configuration file, first IoT data, second IoT data, etc.

[0084] In one implementation of this application, please refer to Figure 2 , Figure 2 Another schematic diagram of a scenario of an IoT output processing-related device provided in an embodiment of the present application, the IoT system may include an IoT platform 101, an IoT device 301, and multiple data acquisition modules 201 connected to the IoT platform 101. Optionally, the data acquisition module 201 may also include a first data acquisition module 2011 and a second data acquisition module 2012.

[0085] The first data acquisition module 2011 may also include an acquisition engine and multiple acquisition plug-ins communicating with the acquisition engine; the acquisition engine is integrated with multiple different acquisition plug-ins, and multiple different acquisition plug-ins can implement modules / units with the same functions. The acquisition engine is mainly used to collect first IoT data corresponding to multiple IoT devices through multiple acquisition plug-ins; and the multiple IoT devices may include multiple different types of first IoT devices. The second data acquisition module 2012 may be a fixed acquisition program, and the second data acquisition module uses the fixed acquisition program to collect second IoT data corresponding to the second IoT device.

[0086] It should be noted that Figure 1 and Figure 2 The scenario diagram of the IoT data processing related device shown is only an example. The IoT data processing related device and scenario described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided by the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of IoT data processing related devices and the emergence of new business scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

[0087] This application collects data of different types of protocols from IoT devices in different scenarios, uses multiple collection plug-ins and fixed programs to collect data, and performs corresponding denoising and disturbance processing on the collected data to improve the accuracy of IoT data.

[0088] The following describes it in detail with reference to specific embodiments.

[0089] In this embodiment, the method for processing IoT data will be described from the perspective of the method, which can be specifically integrated in the IoT system 100. The IoT system 100 includes an IoT platform and IoT devices, multiple data acquisition modules connected to the IoT platform, the multiple data acquisition modules include a first data acquisition module and a second data acquisition module, the first data acquisition module includes a first acquisition engine and multiple acquisition plug-ins communicating with the first acquisition engine, the first acquisition engine is used to collect first IoT data corresponding to multiple IoT devices through the multiple acquisition plug-ins, the multiple IoT devices include multiple different types of first IoT devices, the second data acquisition module is a fixed acquisition program, and the second data acquisition module uses the fixed acquisition program to collect second IoT data corresponding to the second IoT device.

[0090] The present application provides an Internet of Things data processing method, which includes:

[0091] Obtain an Internet of Things data collection instruction; according to the Internet of Things data collection instruction, obtain a configuration file for a first collection engine to collect Internet of Things data, the configuration file including information of multiple collection plug-ins for collecting Internet of Things data, and information of multiple Internet of Things devices connected to the multiple collection plug-ins; according to the configuration file, create multiple data collection threads corresponding to the multiple Internet of Things devices; use the multiple data collection threads to load the multiple collection plug-ins respectively to obtain first Internet of Things data corresponding to the multiple Internet of Things devices; according to the Internet of Things data collection instruction, collect second Internet of Things data corresponding to the second Internet of Things device through a second fixed collection program; process the first Internet of Things data and the second Internet of Things data to obtain processed Internet of Things data.

[0092] See also Figure 3 , Figure 3 This is a flow chart of an embodiment of the method for processing Internet of Things data in the embodiment of the present application. The method for processing Internet of Things data includes the following steps 201 to 206:

[0093] 201. Obtain IoT data collection instructions.

[0094] Among them, the IoT data collection instruction is issued by the IoT platform. The IoT system can be set with a data collection cycle. At the beginning of the data collection cycle, the IoT platform generates a data collection instruction and sends it to the data collection module. The data collection module collects data after obtaining the data collection instruction. Specifically, the data collection cycle can be set on the IoT system, and the data collection cycle of different IoT devices can be different. For example: the data collection cycle of some IoT devices with large loss and fast data update can be shorter, and the data collection cycle of IoT devices with slow data update can be longer.

[0095] 202. According to the IoT data collection instruction, obtain the first collection engine for collecting IoT data.

[0096] Among them, the acquisition engine is an intermediate tool that can run on a computer / hardware gateway / Zhongtaiyun gateway, etc., and is mainly responsible for the communication between hardware / system / heterogeneous data and a computer / hardware gateway / Zhongtaiyun gateway. In an embodiment of the present application, the acquisition engine connects the Internet of Things platform and the Internet of Things device. A collection engine can be connected to multiple Internet of Things devices. The data parameters corresponding to the Internet of Things device can be collected through the collection engine, such as the temperature, humidity of the environment, the current and voltage of the power socket, and other data. In an embodiment of the present application, the acquisition engine can be running on a hardware gateway. And the acquisition engine can include multiple acquisition plug-ins, and different acquisition plug-ins support different communication protocols, such as modbus, industrial standard protocols (OLE for Process Control, OPC), bacnet and other standard protocols, as well as non-standard protocols such as sdk. Different acquisition plug-ins can be used to obtain Internet of Things data corresponding to different types of Internet of Things devices.

[0097] At the same time, in the embodiments of the present application, since a collection engine may include multiple collection plug-ins, some common functions in multiple collection plug-ins may be integrated into a fixed program, and each collection plug-in may call the part with the same function integrated in the collection engine to reduce the redundancy of the collection engine code. And since multiple collection plug-ins may call the common functional part integrated in the collection engine, only the necessary communication protocol parameters are configured, that is, different collection plug-ins may be suitable for different business scenarios, and rapid access to IoT devices may be achieved, thereby improving the reusability of the collection engine. Among them, some common functions in different collection plug-ins may include the function of cyclic collection, and the function of realizing cyclic collection may be integrated, and each collection plug-in may call the function of cyclic collection.

[0098] The configuration file includes information about multiple collection plug-ins for collecting IoT data, and information about multiple IoT devices connected to the multiple collection plug-ins. The information about the multiple IoT devices includes the plug-in files and directories of the IoT devices, and also includes the hardware connection parameters of the IoT devices. Specifically, the plug-in files of the IoT devices include the collection plug-ins corresponding to the IoT devices. Since the communication protocols of the IoT devices can be different, the corresponding plug-ins can also be different. The hardware connection parameters of the IoT devices are the hardware parameters of the IoT devices connected to the plug-ins or gateways.

[0099] 203. Create multiple data collection threads corresponding to the multiple IoT devices according to the configuration file.

[0100] Specifically, the configuration file includes the hardware parameters of multiple IoT devices connected to the engine, so the configuration file can include the number of IoT devices specifically connected to the collection engine. According to the number of IoT devices specifically connected, threads corresponding to the number can be created. The collection threads correspond to the IoT devices one-to-one, and the data of IoT devices can be collected at the same time, which can improve the efficiency of data collection. Among them, the configuration file also includes plug-in information corresponding to multiple IoT devices. According to the configuration file, the collection thread can load the plug-in corresponding to the IoT device to collect data from the corresponding device. The plug-in and the device can be in a one-to-one correspondence. Since the communication protocol used is the same, the collection plug-in is more efficient in collecting data.

[0101] 204. Use the multiple data collection threads to load the multiple collection plug-ins respectively to obtain first IoT data corresponding to the multiple IoT devices.

[0102] It should be noted that when the collection engine is actually running, the collection engine will establish communication with the IoT device under the action of the configuration file to collect the IoT data corresponding to the IoT device. The collection engine will determine whether a connection is established between the IoT device and the corresponding collection plug-in, that is, whether a communication line is established between the IoT device and the corresponding collection plug-in. For multiple IoT devices connected to the same collection engine, they can communicate directly through the collection engine, that is, multiple IoT devices connected to the same collection engine can access each other. Multiple IoT devices connected to different collection engines need to communicate through the IoT platform. When a connection is established between the IoT device and the corresponding collection plug-in, the communication of the IoT device is initialized so that the communication protocol between the corresponding collection plug-in and the IoT device remains consistent, so that the two can communicate normally.

[0103] Specifically, the number of data acquisition threads is the same as the number of IoT devices connected to the acquisition engine, and each data acquisition thread corresponds to an IoT device. A collection plug-in corresponding to the IoT device will be loaded in each data acquisition thread, and the collection plug-in obtains the first IoT data of the IoT device by traversing the data point list of the IoT device. Among them, the data point is the smallest unit of data of the IoT device. The data point is usually independent, and the storage and access of the data point are also isolated from each other. Multiple data points can constitute a data point list, also known as a data point table, which is a collection of multiple data points. The data point list can also be understood as a collection of attributes, time, and services of IoT devices. In an embodiment of the present application, each IoT device corresponds to a data point list.

[0104] 205. According to the IoT data collection instruction, collect second IoT data corresponding to the second IoT device through the second fixed collection program.

[0105] Specifically, the second data collection module can be a fixed collection program included in the collection engine itself, and the fixed collection program can be used to collect the IoT data corresponding to the IoT device. Multiple IoT devices have fixed overlapping data types, such as basic data such as power consumption and energy consumption of IoT devices. The second collection module can be used to collect common basic data shared by multiple IoT devices. By setting the fixed collection program set as the second data collection module, the collection efficiency of common basic data can be improved.

[0106] 206. Process the first Internet of Things data and the second Internet of Things data to obtain processed Internet of Things data.

[0107] Specifically, after obtaining the first IoT data and the second IoT data, the first IoT data and the second IoT data can be merged according to the data source, that is, according to the IoT device, to obtain a list of data points classified according to the IoT device. Based on the merged IoT data, the IoT data can be denoised and disturbed. The denoising process can remove abnormal values ​​in the IoT data, which will interfere with the monitoring of the operation of the IoT device and are abnormal data. The disturbance process can disturb and encrypt the IoT data, which can improve the security of the IoT device and make it difficult for other attackers to read and use it. It can be understood that "first" and "second" are only used to distinguish here, and no other restrictions are made.

[0108] The embodiments of the present application collect data of different types of protocols from IoT devices in different scenarios, use multiple collection plug-ins and fixed programs to collect data, and perform corresponding denoising and disturbance processing on the collected data to improve the accuracy of IoT data.

[0109] In one implementation of the present application, step 203 creates multiple data collection threads corresponding to the multiple IoT devices according to the configuration file, including:

[0110] According to the information of the multiple IoT devices connected to the multiple acquisition plug-ins, the number of the multiple IoT devices is determined; and data acquisition threads corresponding to the number of the multiple IoT devices are created, and the data acquisition threads correspond to the multiple IoT devices one by one.

[0111] Specifically, since the configuration file includes hardware parameters for connecting multiple IoT devices to the engine, the configuration file may include the number of IoT devices specifically connected to the collection engine. According to the number of IoT devices specifically connected, threads corresponding to the number may be created. Collection threads correspond to IoT devices one-to-one, that is, each IoT device corresponds to one collection thread. Multiple collection threads may be performed simultaneously, which may improve the efficiency of data collection.

[0112] The embodiment of the present application creates collection threads that correspond one-to-one to the IoT devices, so that data can be collected simultaneously in multiple threads, thereby improving the efficiency of data collection.

[0113] In one implementation of the present application, step 204 uses the multiple data collection threads to load the multiple collection plug-ins respectively to obtain the first IoT data corresponding to the multiple IoT devices, including:

[0114] The multiple data collection threads are used to load the multiple collection plug-ins respectively, and the data point lists of the multiple Internet of Things devices are traversed to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices.

[0115] Specifically, the data collection thread loads the collection plug-in corresponding to the IoT device, and traverses the data point list of the IoT device through loop collection, thereby obtaining the first IoT data of the IoT device.

[0116] Optionally, different acquisition plug-ins may include a function module for querying IoT data, or a function module for controlling IoT devices through acquisition plug-ins. Since different acquisition plug-ins may include function modules for implementing the same functions, the function modules for implementing the same functions are integrated to reduce the number of function modules in the acquisition engine. When different acquisition plug-ins need to implement corresponding functions, only the integrated function modules need to be called, and there is no need to set complete function modules for all acquisition plug-ins.

[0117] Therefore, in the embodiment of the present application, multiple acquisition plug-ins are obtained by filling in the function code through the preset general acquisition plug-in template. Specifically, the preset general acquisition plug-in template has integrated some functional modules required by each acquisition plug-in, including but not limited to: communication initialization module, control module and query module. The acquisition engine can also include an acquisition module, which is mainly used to actively call the interface in the IoT device, or access the data on the IoT device, and actively report it to the IoT platform.

[0118] In the embodiment of the present application, the acquisition module in the acquisition engine is the acquisition plug-in, and the functional modules that implement the same functions in different acquisition plug-ins are integrated in the acquisition engine; different acquisition plug-ins can call these functional modules to implement corresponding functions. Therefore, different acquisition plug-ins only need to modify the code corresponding to the acquisition module to obtain different acquisition plug-ins; that is, different functional codes are filled in the preset universal acquisition template to obtain different acquisition plug-ins.

[0119] The embodiment of the present application realizes that multiple plug-ins collect IoT data at the same time by using a modular writing method for the collection plug-in, which can reduce the load of the IoT data collection engine and improve the efficiency of data collection.

[0120] In one implementation of the present application, loading the multiple collection plug-ins respectively, traversing the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the multiple IoT devices specifically includes:

[0121] 1. Determine whether there is a flag bit in the data point list of the multiple IoT devices.

[0122] Specifically, the data point list may include a collection flag, which is mainly used to determine whether it is necessary to obtain IoT data corresponding to the IoT device. That is, the collection flag is set for a single data point or a single data point list, and the collection flag indicates whether it is necessary to collect IoT data.

[0123] In a specific embodiment of the present application, the collection flag can be startCollect, and the value of the collection flag can be True / False; when the value of the collection flag is True, the collection plug-in collects the corresponding data point or IoT data in the data point list to realize the collection of IoT data corresponding to the IoT device.

[0124] In some embodiments of the present application, an IoT device may correspond to one collection flag or multiple collection flags. When there are multiple collection flags, the IoT data corresponding to the same IoT device also includes multiple different types of data; and different collection flags correspond to different types of IoT data. The collection flags corresponding to each type of IoT data can be judged separately to determine whether it is necessary to obtain the IoT data of that type. When there is only one collection flag, it can be determined whether it is necessary to obtain all the IoT data in the IoT device or to obtain a specific type of data in the IoT data by judging the value of the unique collection flag.

[0125] Optionally, in some embodiments of the present application, the data point list of the IoT device may also include different data points, and multiple different data points correspond to different types of IoT data; and each of the multiple data points also corresponds to a collection flag, and whether the corresponding data point needs to be obtained is determined by judging the value of the collection flag, that is, whether the corresponding type of IoT data needs to be collected.

[0126] 2. If there is a flag bit, determine whether the flag bit meets a preset condition; if so, load the multiple acquisition plug-ins to traverse the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the IoT device.

[0127] Specifically, the preset condition may be that when the value of the flag is true, the data point data corresponding to the flag is collected. For example, the collection flag may be a collection flag corresponding to IoT devices such as a hot water pump and a distribution box. And the value of each collection flag may be true or false. For the distribution box, the corresponding collection flag may be 1601, and the value of the collection flag is false; that is, there is no need to obtain the IoT data corresponding to the distribution box. For the hot water pump, the corresponding collection flag is 1264, and the value of the collection flag is true, and the IoT data corresponding to the hot water supply pump needs to be collected. It is understandable that the flags of the distribution box and the hot water pump are only examples. It is understandable that in other embodiments, different IoT devices may be used, and the specifics are not limited here.

[0128] In some other embodiments of the present application, the flag bit may not be set. At this time, using the data acquisition thread, loading the target acquisition plug-in to obtain the IoT data corresponding to the target IoT device may include:

[0129] Determine whether the data acquisition thread is in the running state; if the data acquisition thread is in the running state, directly load the target acquisition plug-in to obtain the IoT data corresponding to the target IoT device.

[0130] That is, in the above embodiment, when the data collection thread is started, since there is no flag bit in the data / data table, there is no need to judge the flag bit, and the target collection plug-in is directly loaded to obtain the Internet of Things data.

[0131] The embodiment of the present application can selectively collect data from some IoT devices or collect partial data from some IoT devices through the establishment of flag bits according to actual conditions and actual application scenarios, thereby improving the efficiency of collecting data from IoT devices.

[0132] In one implementation of this application, please refer to Figure 4 , Figure 4 This is another example flow chart of the method for processing IoT data in the embodiment of the present application. Step 206 processes the first IoT data and the second IoT data to obtain processed IoT data, which specifically includes the following steps 2061-2063:

[0133] 2061. Merge the first Internet of Things data and the second Internet of Things data to obtain merged Internet of Things data.

[0134] Specifically, after obtaining the first IoT data and the second IoT data, the first IoT data and the second IoT data may be merged according to data sources, that is, according to IoT devices, to obtain a list of data points classified according to IoT devices.

[0135] 2062. De-noise the merged IoT data to obtain de-noised IoT data.

[0136] Specifically, the merged IoT data may contain noise data, which refers to data that obviously contains errors and deviates from the expected value. The existence of noise data may affect the subsequent analysis process using the collected IoT data and affect the accuracy of the analysis results. Therefore, the removal of noise data can improve the accuracy of IoT data. Specifically, the historical data and preset algorithms of IoT devices can be used to predict the data of IoT devices within a preset time period, and the predicted value can be compared with the actual value collected. When the difference exceeds the preset range, it can be understood that the IoT data has deviations and errors, and can be judged as noise data. Removing it can improve the accuracy of IoT device data.

[0137] 2063. Perform disturbance processing on the denoised IoT data to obtain disturbed IoT data.

[0138] Specifically, the accuracy of denoised IoT data is high. Using denoised IoT data for data analysis can fully tap the value of IoT data and provide a basis for decision-making. To this end, the denoised IoT data is perturbed. The perturbation process is equivalent to encryption, that is, the real denoised IoT data is perturbed by an algorithm. When an external attacker accesses it, there is a certain probability that the real denoised IoT data will be displayed, and there is also a certain probability that the perturbed data will be displayed. Through perturbation processing, the security of IoT data is enhanced.

[0139] The embodiments of the present application utilize merging, denoising and disturbance processing to integrate IoT data, remove outliers and perform disturbance processing, thereby improving the security of IoT data.

[0140] In one implementation of the present application, the step 2062 of denoising the merged IoT data to obtain denoised IoT data includes:

[0141] 1. Obtain historical IoT data of the IoT device.

[0142] Specifically, the merged IoT data includes the actual IoT data collected by the IoT devices during the target time period, that is, the merged IoT data includes the real IoT data during the target time period. For example, the merged IoT data includes the energy consumption data of the distribution box during 14:00-15:00.

[0143] Specifically, the historical IoT data of IoT devices can be obtained from the database, and the database can be integrated in the IoT platform. For example, the energy consumption data of the distribution box from 14:00 to 15:00 in the past 30 days can be obtained.

[0144] 2. Determine the predicted IoT data of the IoT device in the target time period based on the historical IoT data and a preset algorithm.

[0145] Optionally, the preset algorithm can be a prediction algorithm in the prediction model, and the historical IoT data is input into the IoT data prediction model. Based on the historical IoT data, the model will output the predicted IoT data for the target time period. For example, based on the input distribution box energy consumption data from 14:00 to 15:00 in the past 30 days, the prediction model can output the predicted energy consumption data of the distribution box in the current time period, i.e., 14:00 to 15:00.

[0146] 3. Calculate the difference between the actual IoT data and the predicted IoT data; if the difference exceeds a preset difference range, determine the actual IoT data as noise data, remove the noise data from the merged IoT data, and obtain denoised IoT data.

[0147] Specifically, based on the predicted IoT data and the actual IoT data, the difference between the two can be calculated. Based on multiple calculations, a preset difference range can be obtained, that is, when the difference is within the preset difference range, it means that the actual IoT data is within the normal fluctuation range and belongs to normal IoT data; when the difference exceeds the preset difference range, it means that the actual IoT data is abnormal or wrong, and the actual IoT data can be determined to be noise data, and it is removed from the data point list. For example: when the actual energy consumption data of the distribution box from 14:00 to 15:00 is 300, and the predicted energy consumption data of the distribution box from 14:00 to 15:00 is 100, the difference between the two is 200, and the preset difference range is -100 to 100, then the difference exceeds the preset difference range, which means that the actual energy consumption data is noise data, and it is removed from the data point list.

[0148] The embodiment of the present application can remove abnormal or erroneous IoT data by performing denoising on the merged IoT data, thereby improving the accuracy of the IoT data.

[0149] In one implementation of the present application, step 2063 performs disturbance processing on the denoised IoT data to obtain disturbed IoT data, including:

[0150] 1. Performing decentralized processing on the denoised IoT data to obtain decentralized IoT data.

[0151] Specifically, the denoised IoT data is grouped. The denoised IoT data has a numerical interval, and the value range is [0, x]. The denoised IoT data is divided into n-1 sub-intervals, and the interval of each sub-interval is h = x / (n-1). Each sub-interval is: [0, h), [h, 2h) ... [(n-2) h, x], where x is the maximum value of the denoised IoT data, and n is the type of data value after dispersion, where n = [3e θ +2], where [] represents rounding up, and θ is the corresponding preset dispersion parameter.

[0152] Specifically, the formula for decentralized processing of denoised IoT data is:

[0153]

[0154] Among them, a k represents the kth IoT data in the IoT data with dispersion parameter θ, Represents the scattered data, Indicates in a k Based on The conditional probability of s = [a k / h]×h,r=[a k / h]×h, where [] means rounding up, s, r∈W, s and r are elements in the boundary value set W of the subinterval, and satisfy sr=h.

[0155] 2. Obtain disturbed IoT data based on the dispersed IoT data and a preset disturbance processing formula.

[0156] Specifically, the formula for perturbation processing of decentralized IoT data is:

[0157]

[0158] in, represents the decentralized data, a i Indicates that k The corresponding perturbed data is Indicated in Based on a i The conditional probability is that according to the disturbance processing formula, the IoT data will be The probability of keeping the original value is The probability perturbation output is the boundary value set W except That is, when the attacker accesses the data, the perturbed data will be obtained.

[0159] The embodiments of the present application can prevent attackers from accessing the real denoised IoT data by performing decentralized processing and disturbance processing on the denoised IoT data, thereby improving the security of the IoT data.

[0160] In order to facilitate better implementation of the IoT data processing method provided in the embodiment of the present application, the embodiment of the present application also provides a related device based on the IoT data processing method. The meanings of the terms are the same as those in the IoT data processing method, and the specific implementation details can refer to the description in the IoT data processing method embodiment.

[0161] The device related to the IoT data processing method in the embodiment of the present application has the function of implementing the IoT data processing method provided in the above embodiment. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, and the modules can be software and / or hardware.

[0162] See also Figure 5 , Figure 5 The schematic diagram of the structure of the device related to the Internet of Things data processing method provided in the embodiment of the present application, the device related to the Internet of Things data processing method can be applied to a computing device in a scenario where content push is required. Specifically, the device 400 related to the Internet of Things data processing method may include a first acquisition module 401, a second acquisition module 402, a creation module 403, a first acquisition module 404, a second acquisition module 405, and a data processing module 406, which are as follows:

[0163] The first acquisition module 401 is used to acquire IoT data collection instructions;

[0164] The second acquisition module 402 is used to acquire, according to the IoT data acquisition instruction, a configuration file used by the first acquisition engine to collect IoT data, wherein the configuration file includes information of multiple acquisition plug-ins for collecting IoT data and information of multiple IoT devices connected to the multiple acquisition plug-ins;

[0165] Creation module 403: used to create multiple data collection threads corresponding to the multiple IoT devices according to the configuration file;

[0166] The first acquisition module 404 is used to use the multiple data acquisition threads to load the multiple acquisition plug-ins respectively to obtain the first IoT data corresponding to the multiple IoT devices;

[0167] The second collection module 405 is used to collect second IoT data corresponding to the second IoT device through the second fixed collection program according to the IoT data collection instruction;

[0168] Data processing module 406: used to process the first IoT data and the second IoT data to obtain processed IoT data.

[0169] In one embodiment, the creation module 403 is specifically used to:

[0170] Determine the number of the plurality of IoT devices according to the information of the plurality of IoT devices connected to the plurality of acquisition plug-ins;

[0171] Create data collection threads corresponding to the number of the multiple Internet of Things devices, and the data collection threads correspond to the multiple Internet of Things devices one by one.

[0172] In one embodiment, the first acquisition module 404 is specifically configured to:

[0173] The multiple data collection threads are used to load the multiple collection plug-ins respectively, and the data point lists of the multiple Internet of Things devices are traversed to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices.

[0174] In one embodiment, the first acquisition module 404 is specifically configured to:

[0175] Determine whether there is a flag bit in the data point list of the plurality of IoT devices;

[0176] If there is a flag bit, determine whether the flag bit meets the preset condition;

[0177] If the conditions are met, load the multiple collection plug-ins to traverse the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the IoT devices.

[0178] In one embodiment, the data processing module 406 is specifically configured to:

[0179] Merging the first IoT data and the second IoT data to obtain merged IoT data;

[0180] It also includes a denoising unit 4061: used to denoise the merged IoT data to obtain denoised IoT data;

[0181] The disturbance unit 4062 is used to perform disturbance processing on the denoised IoT data to obtain disturbed IoT data.

[0182] In one implementation, the denoising unit 4061 is specifically configured to:

[0183] Obtaining historical IoT data of the IoT device;

[0184] Determine the predicted IoT data of the IoT device in the target time period according to the historical IoT data and a preset algorithm,

[0185] Calculating the difference between the actual IoT data and the predicted IoT data;

[0186] If the difference exceeds a preset difference range, the actual IoT data is determined as noise data, and the noise data is removed from the merged IoT data to obtain denoised IoT data.

[0187] In one embodiment, the disturbance unit 4062 is specifically used to:

[0188] Performing decentralized processing on the denoised IoT data to obtain decentralized IoT data;

[0189] The disturbed Internet of Things data is obtained according to the dispersed Internet of Things data and a preset disturbance processing formula.

[0190] In the embodiment of the present application, according to the IoT data collection instruction, a configuration file for the first collection engine to collect IoT data is obtained, and according to the configuration file, multiple data collection threads corresponding to multiple IoT devices are created; using multiple data collection threads, multiple collection plug-ins are loaded respectively to obtain the first IoT data corresponding to multiple IoT devices; the second IoT data corresponding to the second IoT device is collected through the second fixed collection program; the first IoT data and the second IoT data are processed to obtain processed IoT data. The present application collects data of different types of protocols for IoT devices in different scenarios, uses multiple collection plug-ins and fixed programs to cooperate in collecting data, and performs corresponding denoising and disturbance processing on the collected data to improve the accuracy of IoT data.

[0191] The above describes the related devices of the Internet of Things data processing method in the embodiment of the present application from the perspective of modular functional entities. The following describes the related devices of the Internet of Things data processing method in the embodiment of the present application from the perspective of hardware processing.

[0192] It should be noted that Figure 5 The physical devices corresponding to the first acquisition module 401 and the second acquisition module 402 shown may be transceivers, radio frequency circuits, communication modules, and input / output (I / O) interfaces, etc., and the physical device corresponding to the data processing module 406 may be a processor.

[0193] Figure 5 The devices shown can all have Figure 6 The structure shown, when Figure 6 The device related to the Internet of Things data processing method shown has the following features: Figure 6 When the structure shown is Figure 6 The processor and the transceiver in the device can realize the same or similar functions as the data processing module 406, the first acquisition module 401 and the second acquisition module 402 provided in the device embodiment corresponding to the device. Figure 6 The memory in the storage processor is used to store a computer program that needs to be called when executing the above-mentioned Internet of Things data processing method.

[0194] When the computing device in the embodiment of the present application is a terminal device, the embodiment of the present application also provides a terminal device, such as Figure 7 For the sake of convenience, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present application. The terminal device can be any terminal device including a mobile phone, a tablet computer, a personal digital assistant (PDA), a point of sales (POs), a car computer, etc., taking the terminal device as a mobile phone as an example:

[0195] Figure 7 FIG. 1 is a block diagram showing a partial structure of a mobile phone related to a terminal device provided in an embodiment of the present application. Figure 7 The mobile phone includes: a radio frequency (RF) circuit 1010, a memory 1020, an input unit 1030, a display unit 1040, a sensor 1050, an audio circuit 1060, a wireless fidelity (WiFi) module 1070, a processor 1080, and a power supply 1090. Those skilled in the art will understand that Figure 7 The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0196] Combine the following Figure 7 A detailed introduction to the various components of the mobile phone:

[0197] The RF circuit 1010 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 1080 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1010 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, etc. In addition, the RF circuit 1010 can also communicate with the network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to Global system of mobile communication (Global system of mobile communication, GSM), General Packet Radio service (General Packet Radio service, GPRs), Code Division Multiple Access (Code Division Multiple Access, CDMA), Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), Long Term Evolution (Long Term Evolution, LTE), email, short messaging service (sMs), etc.

[0198] The memory 1020 can be used to store software programs and modules. The processor 1080 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1020. The memory 1020 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 1020 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0199] The input unit 1030 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 1030 may include a touch panel 1031 and other input devices 1032. The touch panel 1031, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1031 or near the touch panel 1031 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 1031 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 1080, and can receive and execute commands sent by the processor 1080. In addition, the touch panel 1031 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1031, the input unit 1030 may further include other input devices 1032. Specifically, the other input devices 1032 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

[0200] The display unit 1040 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1040 may include a display panel 1041. Optionally, the display panel 1041 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 1031 may cover the display panel 1041. When the touch panel 1031 detects a touch operation on or near it, it is transmitted to the processor 1080 to determine the type of touch event. Subsequently, the processor 1080 provides a corresponding visual output on the display panel 1041 according to the type of touch event. Although in Figure 7 In the embodiment, the touch panel 1031 and the display panel 1041 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 1031 and the display panel 1041 can be integrated to realize the input and output functions of the mobile phone.

[0201] The mobile phone may also include at least one sensor 1050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1041 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1041 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0202] The audio circuit 1060, the speaker 1061, and the microphone 1062 can provide an audio interface between the user and the mobile phone. The audio circuit 1060 can transmit the received audio data to the speaker 1061 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 1062 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1060 and converted into audio data, and then the audio data is output to the processor 1080 for processing, and then sent to another mobile phone through the RF circuit 1010, or the audio data is output to the memory 1020 for further processing.

[0203] Wi-Fi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages, and access streaming media through the Wi-Fi module 1070. It provides users with wireless broadband Internet access. Figure 7 A Wi-Fi module 1070 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0204] The processor 1080 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. It executes various functions of the mobile phone and processes data by running or executing software programs and / or modules stored in the memory 1020, and calling data stored in the memory 1020, so as to monitor the mobile phone as a whole. Optionally, the processor 1080 may include one or more processing units; optionally, the processor 1080 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 1080.

[0205] The mobile phone also includes a power supply 1090 (such as a battery) for supplying power to various components. Optionally, the power supply can be logically connected to the processor 1080 through a power management system, thereby managing functions such as charging, discharging, and power consumption management through the power management system.

[0206] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be described in detail here.

[0207] In the embodiment of the present application, the processor 1080 included in the mobile phone also has the function of controlling and executing the IoT data processing method flow executed by the IoT data processing method related devices.

[0208] The present application also provides a server. Figure 8 , Figure 8 1 is a schematic diagram of a server structure provided in an embodiment of the present application. The server 1100 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (full name in English: central processing units, abbreviated in English: CPU) 1122 (for example, one or more processors) and memory 1132, one or more storage media 1130 (for example, one or more mass storage devices) storing application programs 1142 or data 1144. Among them, the memory 1132 and the storage medium 1130 can be short-term storage or permanent storage. The program stored in the storage medium 1130 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the central processing unit 1122 can be configured to communicate with the storage medium 1130 to execute a series of instruction operations in the storage medium 1130 on the server 1100.

[0209] The server 1100 may also include one or more power supplies 1126, one or more wired or wireless network interfaces 1150, one or more input and output interfaces 1158, and / or one or more operating systems 1141, such as Windows server, Mac Os X, Unix, Linux, FreeBsD, etc.

[0210] The steps in the IoT data processing method in the above embodiment can be based on the Figure 8 The structure of the server 1100 is shown.

[0211] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0212] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0213] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components 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.

[0214] 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 modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0215] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium.

[0216] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0217] The computer program product includes one or more computer instructions. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction may be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DsL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state hard disk solid state Disk (ssD)), etc.

[0218] The technical solutions provided in the embodiments of the present application are introduced in detail above. The principles and implementation methods of the embodiments of the present application are explained by using specific examples in the embodiments of the present application. The description of the above embodiments is only used to help understand the methods and core ideas of the embodiments of the present application. At the same time, for those skilled in the art, according to the ideas of the embodiments of the present application, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of the present application.

Claims

1. A method for processing Internet of Things data, characterized in that: The Internet of Things data processing method is applied to an Internet of Things system, the Internet of Things system includes an Internet of Things platform and an Internet of Things device, and multiple data acquisition modules connected to the Internet of Things platform, the multiple data acquisition modules include a first data acquisition module and a second data acquisition module, the first data acquisition module includes a first acquisition engine and multiple acquisition plug-ins communicating with the first acquisition engine, the first acquisition engine is used to collect first Internet of Things data corresponding to multiple Internet of Things devices through the multiple acquisition plug-ins, the multiple Internet of Things devices include multiple different types of first Internet of Things devices, the second data acquisition module is a fixed acquisition program, and the second data acquisition module uses the fixed acquisition program to collect second Internet of Things data corresponding to a second Internet of Things device. The Internet of Things data processing method includes: Get IoT data collection instructions; According to the IoT data collection instruction, obtain a configuration file for the first collection engine to collect IoT data, wherein the configuration file includes information of multiple collection plug-ins for collecting IoT data and information of multiple IoT devices connected to the multiple collection plug-ins; According to the configuration file, create multiple data collection threads corresponding to the multiple IoT devices; Using the multiple data collection threads, respectively load the multiple collection plug-ins to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices; According to the IoT data collection instruction, second IoT data corresponding to the second IoT device is collected through the fixed collection program, wherein the second IoT data is common basic data shared by multiple second IoT devices; Merging the first IoT data and the second IoT data to obtain merged IoT data; De-noising the merged IoT data to obtain de-noised IoT data; The denoised IoT data is subjected to disturbance processing to obtain disturbed IoT data.

2. The method for processing Internet of Things data according to claim 1, characterized in that: The step of creating a plurality of data collection threads corresponding to the plurality of IoT devices according to the configuration file includes: Determine the number of the plurality of IoT devices according to the information of the plurality of IoT devices connected to the plurality of acquisition plug-ins; Create data collection threads corresponding to the number of the multiple Internet of Things devices, and the data collection threads correspond to the multiple Internet of Things devices one by one.

3. The method for processing Internet of Things data according to claim 1, characterized in that: The using the multiple data collection threads to load the multiple collection plug-ins respectively to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices includes: The multiple data collection threads are used to load the multiple collection plug-ins respectively, and the data point lists of the multiple Internet of Things devices are traversed to obtain the first Internet of Things data corresponding to the multiple Internet of Things devices.

4. The method for processing Internet of Things data according to claim 3, characterized in that: The step of loading the plurality of collection plug-ins respectively and traversing the data point lists of the plurality of IoT devices to obtain the first IoT data corresponding to the plurality of IoT devices includes: Determine whether there is a flag bit in the data point list of the plurality of IoT devices; If there is a flag bit, determine whether the flag bit meets the preset condition; If the conditions are met, load the multiple collection plug-ins to traverse the data point lists of the multiple IoT devices to obtain the first IoT data corresponding to the IoT devices.

5. The method for processing Internet of Things data according to claim 1, characterized in that: The merged IoT data includes actual IoT data collected by the IoT device in a target time period, and denoising the merged IoT data to obtain denoised IoT data includes: Obtaining historical IoT data of the IoT device; Determine the predicted IoT data of the IoT device in the target time period according to the historical IoT data and a preset algorithm, Calculating the difference between the actual IoT data and the predicted IoT data; If the difference exceeds a preset difference range, the actual IoT data is determined as noise data, and the noise data is removed from the merged IoT data to obtain denoised IoT data.

6. The method for processing Internet of Things data according to claim 1, characterized in that: The performing disturbance processing on the denoised IoT data to obtain the disturbed IoT data includes: Performing decentralized processing on the denoised IoT data to obtain decentralized IoT data; According to the dispersed IoT data and the preset disturbance processing formula, the disturbed IoT data is obtained, wherein the preset disturbance processing formula is: Where n is the type of data value after distributed processing, n = [3e θ +2], [] indicates rounding up, θ is the preset corresponding dispersion parameter, a k represents the kth IoT data in the IoT data with dispersion parameter θ, represents the decentralized IoT data, a i Indicates that k The corresponding perturbed data is Indicated in Based on a i The conditional probability of .

7. A device related to an Internet of Things data processing method, characterized in that: It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the Internet of Things data processing method as claimed in any one of claims 1 to 6 when executing the computer program.

8. A computing device, characterized in that It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the Internet of Things data processing method as claimed in any one of claims 1 to 6 when executing the computer program.

9. A computer-readable storage medium, characterized in that: It includes instructions, which, when executed on a computer, enable the computer to execute the Internet of Things data processing method as claimed in any one of claims 1 to 6.

Images