Data processing method, device, computer equipment and medium based on Internet of Things

Abstract

The embodiment of the present invention discloses a data processing method, device, computer equipment and medium based on the Internet of Things. The data processing method based on the Internet of Things includes: establishing a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application; and establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship. The embodiment of the present invention can break the single binding relationship between the application devices and expand the control scope of the application layer on the device end, thereby improving the flexibility and scalability of Internet of Things data processing and meeting flexible and changeable business needs.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of Internet of Things application technology, and in particular to a data processing method, device, computer equipment and medium based on the Internet of Things. Background Art

[0002] In the architecture of the IoT platform, IoT devices are an important part. The IoT platform can retrieve data from related devices and control related devices based on the acquired data.

[0003] At present, in IoT application scenarios, there is usually a single binding relationship between devices and applications, that is, a certain type of device is only bound to a certain application A, and has no interactive relationship with other applications B and C. Accordingly, the application can only obtain the data of the device with which it has a binding relationship, and perform control operations on the device with which it has a binding relationship.

[0004] In the process of implementing the present invention, the inventor found that the prior art has the following defects: In the actual application of enterprises, cross-application data collection and operation are usually involved. For example, application B wants to obtain the viewing and operation permissions of device a bound to application A; or the same application has the need to manage and collect data for multiple and different devices. However, most current IoT platforms do not support cross-application viewing and operation authorization for devices. Summary of the invention

[0005] The embodiments of the present invention provide a data processing method, device, computer equipment and medium based on the Internet of Things to improve the flexibility and scalability of Internet of Things data processing and meet flexible and changeable business needs.

[0006] In a first aspect, an embodiment of the present invention provides a data processing method based on the Internet of Things, comprising:

[0007] Establishing a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application;

[0008] Data interaction between the subscribing application and the subscribed device is established based on the subscription relationship.

[0009] In a second aspect, an embodiment of the present invention further provides a data processing device based on the Internet of Things, including:

[0010] A subscription relationship establishment module, used to establish a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application;

[0011] A data interaction module is used to establish data interaction between the subscribing application and the subscribed device based on the subscription relationship.

[0012] In a third aspect, an embodiment of the present invention further provides a computer device, the computer device comprising:

[0013] one or more processors;

[0014] A storage device for storing one or more programs;

[0015] When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method based on the Internet of Things provided by any embodiment of the present invention.

[0016] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium on which a computer program is stored, and when the program is executed by a processor, the data processing method based on the Internet of Things provided by any embodiment of the present invention is implemented.

[0017] The embodiments of the present invention solve the problem that the existing Internet of Things platform can only process data for applications and devices with a binding relationship by establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship between the subscribing application and the subscribed device, so as to break the single binding relationship between the application and the devices, expand the application layer's control scope over the device side, thereby improving the flexibility and scalability of Internet of Things data processing and meeting flexible and changeable business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a flow chart of a data processing method based on the Internet of Things provided by Embodiment 1 of the present invention;

[0019] Figure 2 is a flow chart of a data processing method based on the Internet of Things provided by Embodiment 2 of the present invention;

[0020] Figure 3 A schematic diagram of the effect of an Internet of Things platform management application interface provided by Embodiment 2 of the present invention;

[0021] Figure 4 This is a schematic diagram of target device operation type screening provided by Embodiment 2 of the present invention;

[0022] Figure 5 This is a schematic diagram of an interface effect for determining a subscription event type for a target subscription device provided by Embodiment 2 of the present invention;

[0023] Figure 6 A schematic diagram of a target subscription device selection interface provided in the second embodiment of the present invention;

[0024] Figure 7A schematic diagram of a flow chart of data interaction between a subscribing application and a subscribed device by issuing device instructions provided in the second embodiment of the present invention;

[0025] Figure 8 A schematic diagram of a flow chart of information exchange between a subscription application and an associated application by issuing instruction data provided by Embodiment 2 of the present invention;

[0026] Fig. 9 A schematic diagram of a flow chart of data interaction between a subscribing application and a subscribed device by issuing instruction data provided in the second embodiment of the present invention;

[0027] Fig.10 A schematic diagram of a flow chart of data interaction between a subscribing application and a subscribed device through device reporting events provided in the second embodiment of the present invention;

[0028] Fig.11 A schematic diagram of the system architecture of a data processing method for the Internet of Things provided in Embodiment 2 of the present invention;

[0029] Fig.12 is a schematic diagram of a data processing device based on the Internet of Things provided by Embodiment 3 of the present invention;

[0030] Fig.13 A schematic diagram of the structure of a computer device provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0031] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention.

[0032] It should also be noted that, for ease of description, only the part relevant to the present invention but not all content is shown in the accompanying drawings. It should be mentioned before discussing exemplary embodiments in more detail that some exemplary embodiments are described as processing or methods depicted as flow charts. Although the flow chart describes each operation (or step) as sequential processing, many operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. When its operation is completed, the processing can be terminated, but it can also have additional steps not included in the accompanying drawings. The processing can correspond to methods, functions, procedures, subroutines, subprograms, etc.

[0033] Embodiment 1

[0034] Figure 1is a flow chart of a data processing method based on the Internet of Things provided by the first embodiment of the present invention. This embodiment is applicable to the case where the Internet of Things platform realizes data interaction through the subscription relationship between the subscription application and the subscribed device. The method can be executed by a data processing device based on the Internet of Things. The device can be implemented by software and / or hardware and can generally be integrated in a server, such as Figure 1 As shown, the method includes the following operations:

[0035] S110: Establish a subscription relationship between the subscribing application and the subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application.

[0036] Among them, subscription can be any application to establish an association relationship between non-bound devices or other applications. The subscription application can be an application that collects and operates data information on non-bound devices. Among them, the application can be an Internet of Things application, that is, various applications directly used by users, such as intelligent control, security, power meter reading, telemedicine or smart agriculture. In the embodiment of the present invention, the application type is not specifically limited. The subscribed device can be a device subscribed by the subscribed application, and the device is a non-bound device under the subscription application. The so-called non-bound device means that there is no binding relationship between the device and the application. Correspondingly, the subscription application can collect and operate data information on the subscribed device according to the subscribed permissions. The subscription relationship can be an association relationship between the subscription application and the corresponding subscribed device. This association relationship is different from the binding relationship, which only means that the subscription application and the subscribed device can interact with data according to certain permissions. That is, the subscription application has all device operation permissions for the binding device with which it establishes a binding relationship, and the subscription application has partial device operation permissions for the subscribed device with which it establishes a subscription relationship, and the partial device operation permissions can be specified when establishing the subscription relationship. The Internet of Things platform refers to connecting any object to the network through information sensing devices according to the agreed protocol. The objects exchange and communicate information through information transmission media to realize intelligent identification, positioning, tracking, supervision and other functions. The Internet of Things platform can provide devices with secure and reliable connection and communication capabilities, connect to massive devices downward, and support device data collection on the cloud; provide cloud application programming interface (Application Programming Interface, API) upward, and the server sends instructions to the device side by calling the cloud API to realize remote control. At the same time, the Internet of Things platform also provides other value-added capabilities, such as device management, rule engine, etc., to empower various IoT scenarios and industry developers. In an embodiment of the present invention, if an application interacts with data on certain devices with which it has not established a binding relationship, the application needs to be a subscription application, and a subscription relationship between the subscription application and the subscribed device can be established through the Internet of Things platform.

[0037] S120, establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship. Accordingly, after the subscribing application and the subscribed device establish a subscription relationship, the subscribing application and the subscribed device can interact with each other based on the subscription authority. That is, the subscribing application has the operation authority over the subscribed device based on the subscription relationship, the subscribing application can perform data information collection operations on the subscribed device, and the subscribed device can feedback data information to the subscribing application based on the subscription relationship.

[0038] It can be seen that by establishing a subscription relationship between the subscribing application and the subscribed device, the subscribing application can interact with the subscribed device for data, breaking the limitation that applications in traditional IoT platforms can only interact with devices with a binding relationship, making IoT data processing more flexible to meet flexible and changing business needs.

[0039] The embodiments of the present invention solve the problem that the existing Internet of Things platform can only process data for applications and devices with a binding relationship by establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship between the subscribing application and the subscribed device, so as to break the single binding relationship between the application and the devices, expand the application layer's control scope over the device side, thereby improving the flexibility and scalability of Internet of Things data processing and meeting flexible and changeable business needs.

[0040] Embodiment 2

[0041] Figure 2 is a flow chart of a data processing method based on the Internet of Things provided by Embodiment 2 of the present invention. This embodiment is specific based on the above embodiment. In this embodiment, a specific optional implementation scheme for establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship is provided. Accordingly, Figure 2 As shown, the method includes the following operations:

[0042] S210: Establish a subscription relationship between the subscribing application and the subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application.

[0043] In an optional embodiment of the present invention, establishing a subscription relationship between a subscribing application and a subscribed device may include: determining the subscribing application and the subscribed application; filtering the target device operation type from the set of device operation types included in the subscribed application; and establishing a subscription relationship between the subscribing application and the target device operation type.

[0044] Among them, the subscribed application can be an application that has a binding relationship with the subscribed device corresponding to the subscribed application. The device operation type set can be a set of operation types for performing different operation attribute types on the device. The device operation type set can include at least one operation attribute type, and each operation attribute type is associated with multiple devices. Exemplarily, assuming that the operation attribute type is "turn on temperature monitoring", the operation attribute type can turn on the temperature monitoring function for all devices that can perform temperature monitoring. That is, multiple devices that can perform temperature monitoring are associated with the operation attribute type of "turn on temperature monitoring". The target device operation type can be one or more operation attribute types selected from the device operation type set.

[0045] Optionally, when establishing a subscription relationship between a subscribing application and a subscribed device, an optional method is to first determine the subscribing application and the subscribed application. Then, the target device operation type is filtered from the set of device operation types included in the subscribed application to establish a subscription relationship between the subscribing application and the target device operation type. When there is a subscription relationship between the subscribing application and the target device operation type, it is equivalent to a subscription relationship between the subscribing application and the device associated with the target device operation type.

[0046] Figure 3 This is a schematic diagram of the effect of an Internet of Things platform management application interface provided by the second embodiment of the present invention. In a specific example, when a subscription relationship is established through the Internet of Things platform, the "application subscription" function of the Internet of Things platform management application interface can be triggered, and after the triggering, the application subscription new interface is obtained as shown in FIG. Figure 3 As shown. In the new application subscription interface, you can choose the subscribing application and the subscribed application. Assume that the subscribing application is application A and the subscribed application is application B. Device specifications are also a set of device operation types. Accordingly, all specifications can be all device operation types included in the set of device operation types included in application B. Custom specifications can be one or more device operation types selected from the set of device operation types. When all specifications are selected, it means that application A subscribes to the entire set of device operation types included in application B. Accordingly, the devices associated with the entire set of device operation types become the subscribed devices of application A.

[0047] Figure 4 Schematic diagram of target device operation type screening provided by Embodiment 2 of the present invention. Figure 4As shown, the subscribing application is application A, and the subscribed application is application B. Assume that the device operation type set included in application B includes data read type, data deletion type, and data change type. If the target device operation type that application A needs to subscribe to application B is the data read type, then select the data read type through the custom specification. If the target device operation type is the data change type, then application A filters out the data change type from the device operation type set of application B as the target device operation type, and then application A establishes a subscription relationship with the selected target device operation type. If the target device operation type is data change, then application A filters out the data change type from the device operation type set of application B as the target device operation type, and then the subscribing application A establishes a subscription relationship with the selected target device operation type.

[0048] S220: Determine a target subscription device according to the target device operation type.

[0049] The target subscription device may be a device that can perform target device operation type operations, and the target subscription device may be one or more.

[0050] Accordingly, after determining the target device operation type, the device associated with the target device operation type may be further determined according to the target device operation type, and the target subscribing device may be determined from the associated devices as the subscribed device.

[0051] For example, assume that the subscribed application B has three bound devices, namely b1, b2 and b3. Among them, the devices that can perform data read type operations are b1 and b2, the devices that can perform data delete type operations are b1, b2 and b3, and the devices that can perform data change type operations are b2 and b3. If the target device operation type is data read type, since the devices that can perform data read type operations are b1 and b2, then according to the target device operation type, it can be determined that the target subscription device can be b1 and / or b2.

[0052] S230, establishing a subscription relationship between the subscription application and the target subscription device. Specifically, if a specific designated device needs to be subscribed, the target device operation type can be screened out from the device operation type set included in the subscribed application, and then the target subscription device is determined according to the target device operation type, and then the subscription relationship between the subscription application and the target subscription device can be established.

[0053] Exemplarily, assuming that application A is a subscription application, device b1 is a target subscription device, and application B is a subscribed application, the specific process of establishing a subscription relationship between application A and device b1 may include: filtering out the target device operation type from the device operation type set included in application B. When the target device operation type is a data reading type, a subscription relationship between application A and the data reading type is established. Since the devices that can perform data reading type operations are b1 and b2, that is, according to the target device operation type, the target subscription device can be determined to be b1 and / or b2. The subscription relationship between application A and device b1 can be established.

[0054] Accordingly, S230 may specifically include the following operations:

[0055] S231: Determine the subscription event type that matches the subscription application and the target subscription device.

[0056] Among them, an event can be one of the functional models of a device or an event during the operation of a device. An event can generally include notification information that needs to be perceived and processed externally, or it can include multiple output parameters. For example, information about the completion of a task, the temperature when a device fails or alarms, etc. Events can be subscribed to and reported. The subscription event type can be an event type that the subscribing application needs to have operation permissions on the target subscription device.

[0057] Specifically, the IoT platform may first determine the subscription event type that matches the subscription application and the target subscription device. That is, the IoT platform may set the operation authority of the subscription application on the target subscription device.

[0058] S232: Establish a subscription relationship between the subscription application and the target subscription device according to the subscription event type.

[0059] The subscription event types may include, but are not limited to, device alarm events, device attachment upload events, device attachment download events, device status reporting events, device location reporting events, and device activation events.

[0060] Among them, the device alarm event can be an alarm event reported autonomously by the target subscription device. The device attachment upload event can be a device attachment upload event of the target subscription device. The device attachment download event can be a device attachment download event of the target subscription device. The device status report event can be a device status report event of the target subscription device. The device location report event can be a device location report event of the target subscription device. The device activation event can be an activation event of the target subscription device. That is, all information that can be generated by the device can be used as a subscription event type to interact with the subscription application.

[0061] Exemplarily, the subscription event type may further include the following event types:

[0062] Device reporting message events: Messages reported by devices can include custom data and object model data reported by devices (including attribute reporting, event reporting, attribute setting responses, and service call responses). Device status change notification events: refers to the notification message sent by the system when the status of a device under a product changes. For example, device offline and online messages. Device lifecycle change events: including workaround notifications such as notification messages for device creation, deletion, disabling, and enabling. Object model historical data reporting events: that is, device reporting of attribute and event historical data. Firmware upgrade status notification events: that is, notification messages such as reporting of firmware upgrade success or failure. Gateway discovery sub-device reporting events: The gateway can report the discovered sub-device information to the IoT platform. This event requires application support on the gateway and is a gateway product-specific message type. Device topology relationship change events: refers to messages for establishing and releasing the topology relationship between a sub-device and a gateway. Gateway product-specific message types.

[0063] Accordingly, after the IoT platform determines the subscription event type that matches the subscribing application and the target subscribing device, a subscription relationship between the subscribing application and the target subscribing device is established based on the subscription event type. It is understandable that the subscribing application can subscribe to all event types of the subscribed device, or only subscribe to some event types of the subscribed device. In other words, the subscribing application can subscribe to all operating permissions of the subscribed device, or only subscribe to some operating permissions of the subscribed device. Accordingly, after determining the subscription event type that the subscribing application needs to subscribe to, the association relationship between the subscribing application and the target subscribing device can be established based on the subscription event type.

[0064] For example, assuming that the subscription event type determined by the subscribing application and the target subscribing device is a device status reporting event, that is, the subscribing application only has the operation authority for the device status reporting event of the subscribed device, and the association relationship between the subscribing application and the target subscribing device can be established based on the device status reporting event. When the subscribed device needs to report the device status to the bound application, it can report the device status to the subscribing application at the same time.

[0065] Figure 5 1 is a schematic diagram of an interface effect for determining a subscription event type for a target subscription device provided by Embodiment 2 of the present invention. Figure 5 As shown in FIG. 1 , if the target subscription device that needs to establish a subscription relationship with the subscription application is device b1, then device b1 is selected as the target subscription device by selecting a custom device. Figure 5 As shown, after selecting a custom device, you can trigger the virtual function key to add a device, and a pop-up window will appear. Figure 6 The target subscription device selection interface is shown. Figure 6A schematic diagram of the effect of a target subscription device selection interface provided in Embodiment 2 of the present invention. The target subscription device can be searched by keyword. Among them, the keyword can be the target subscription device ID or the target subscription device name. After entering the target subscription device ID or the target subscription device name, you can click Query and check the target subscription device in the query list. For example, you can search for the ID of device b1 and add device b1 as the target subscription device in the query list. If you need to subscribe to all subscription event types for the target subscription device b1, select all event types under the event category. Optionally, the target subscription device can be one or more. If you need to subscribe to some subscription event types for the target subscription device b1, select the custom event type under the event category. One or more subscription event types in the custom event type can be selected. If a certain subscription event type is selected for all devices, it means that a certain subscription event type of all devices will be subscribed to by the subscribing application.

[0066] S240: Determine the instruction sending type that matches the subscription application and the subscription event type; wherein the instruction sending type includes a device status acquisition instruction, a device information acquisition instruction, and a device control instruction.

[0067] Among them, the device status acquisition instruction can be used to obtain the device status, and the device status can be, for example, the device is turned on, the device is running, the device is turned off, or whether the device is running normally. The device information acquisition instruction can be used to obtain device information, and the device information can be, for example, device operation information, device operation information, or specific parameters of the device. In the embodiments of the present invention, the specific content of the device status and device information is not specifically limited. The device control instruction is used to control the function of the device, such as controlling and adjusting the device temperature or the opening time, and the embodiments of the present invention also do not limit the specific type of device function control.

[0068] Specifically, after establishing the subscription relationship between the subscription application and the target subscription device according to the subscription event type, the instruction delivery type that matches the subscription application and the subscription event type can be determined. For example, if the determined instruction delivery type is a device status acquisition instruction, the subscription application can only interact with the subscribed device through the device status acquisition instruction. If the determined instruction delivery type is a device control instruction, the subscription application can control one or more functions of the target subscription device through the device control instruction.

[0069] S250: Establish data interaction between the subscribing application and the subscribed device based on the subscription relationship.

[0070] Exemplarily, the subscribing application establishes a subscription relationship with the subscribed device, obtains device data in the subscribed device that matches the instruction sending type according to the instruction sending type, and the subscribed device sends the device data that matches the instruction sending type to the subscribing application, thereby completing the data interaction between the subscribing application and the subscribed device.

[0071] It should be noted that the subscribing application can interact with all data types generated by the subscribed device based on the subscription relationship. For example, the subscribing application can view the device information of the subscribed device, specifically the basic information of the device, including device certificate information, firmware information, extension information and tag information. The subscribing application can also view the device data of the subscribed device, such as viewing the current attribute value reported by the device, viewing the event record reported by the device, and viewing the device service call record. The subscribing application can also view the device log of the subscribed device, such as viewing the cloud operation log, and the local log of the device. The subscribing application can also view the device grouping of the subscribed device, specifically the grouping information of the device, and can also add this device to the group to add the device to the existing group. In addition to the above-mentioned data interaction function of viewing data, it is also possible to realize device function control, the control of the device by the associated application of the receiving device, and the data actively reported by the receiving device. The embodiment of the present invention does not limit the data interaction type and specific data interaction process between the subscribing application and the subscribed device.

[0072] In an optional embodiment of the present invention, establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship may include: receiving a device sending instruction sent by the subscribing application; and sending the device sending instruction to the subscribed device.

[0073] The device instruction sent may be an instruction sent by the subscription application to the subscribed device. For example, the device instruction sent may be a device status acquisition instruction and / or a device information acquisition instruction.

[0074] In an optional embodiment, the data interaction scenario between the subscribing application and the subscribed device can be: the IoT platform receives the device sending instruction sent by the subscribing application, and then the IoT platform sends the device sending instruction to the subscribed device. For example, if the device sending instruction sent by the subscribing application is a device status acquisition instruction, the device status acquisition instruction will be sent to the subscribed device through the IoT platform.

[0075] In an embodiment of the present invention, before sending the device instruction to the subscribed device, it may also include: determining the application subscription rules that match the subscribed application; performing permission verification on the device instruction according to the application subscription rules; sending the device instruction to the subscribed device may include: if it is determined that the permission verification passes, sending the device instruction to the subscribed device.

[0076] The subscription rule may be a subscription relationship between a subscribing application and a subscribed device, and the permission check may be to determine whether the device instruction sent by the subscribing application has operation permission for the subscribed device according to the subscription rule.

[0077] Specifically, after receiving the device sending instruction sent by the subscription application, the IoT platform performs a permission check on the operation permission of the device sending instruction according to the subscription relationship between the subscription application and the subscribed device, i.e., the subscription rule. If it is determined that the permission check passes, the device sending instruction is sent to the subscribed device; otherwise, if it is determined that the device sending instruction has no operation permission for the subscribed device, the device sending instruction is rejected.

[0078] Figure 7 A flowchart of a subscribing application and a subscribed device performing data interaction by issuing device instructions is provided in the second embodiment of the present invention. In a specific example, Figure 7 As shown, it is assumed that the subscribing application is application A and the subscribed device is device b1. Then one of the data interaction scenarios between application A and device b1 can be: the IoT platform receives the device issuing instruction sent by application A through the application programming interface (Restful API, RestAPI, a rule to be followed when establishing an API) of the Rest architecture specification, and then performs permission verification on the device issuing instruction according to the subscription rules of the subscribing application and the subscribed device, where the subscription rules of the subscribing application and the subscribed device can be referred to as configuration rules. Assuming that the device issuing instruction is a device status acquisition instruction, if device b1 is the target subscription device subscribed by application A, and application A subscribes to the device b1 status acquisition event, it indicates that the permission verification is passed. At this time, the IoT platform can send the device issuing instruction to the open source IoT MQTT message server (Erlang / Enterprise / Elastic MQTT Broker, EMQ) through the message queue telemetry transport (Message Queuing Telemetry Transport, MQTT), so as to send the device issuing instruction to the subscribed device b1 through EMQ. It is understandable that after receiving the device instruction, device b1 can respond to the device instruction and feedback instruction response data to application A, thereby completing the complete data interaction process between application A and device b1.

[0079] In an optional embodiment of the present invention, establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship may include: receiving the issuing instruction data of the associated application of the subscribed device; and feeding back the issuing instruction data to the subscribing application.

[0080] Among them, the associated application can be an application that has a binding relationship with the subscribed device. The issued instruction data can be the instruction data sent by the associated application to the subscribed device, which can include but is not limited to the issued instruction operation data and the issued instruction response data. The issued instruction operation data can be a kind of instruction operation data sent by the associated application to the bound device, and the issued instruction operation data can include the acquisition device status acquisition instruction and / or the device information acquisition instruction, etc. The embodiment of the present invention does not limit the specific content of the issued instruction operation data. The issued instruction response data can be the instruction response data that the bound device feeds back to the associated application in response to the issued instruction operation data, that is, the execution result of the issued instruction data of the associated application by the subscribed device. The embodiment of the present invention does not limit the specific content of the issued instruction response data.

[0081] Accordingly, the IoT platform can receive the issuing instruction operation data sent by the associated application, and feed back the issuing instruction operation data to the subscribing application that has a subscription relationship with the subscribed device. At the same time, when the subscribed device generates issuing instruction response data for the issuing instruction operation data and sends it to the IoT platform, the IoT platform can also feed back the issuing instruction response data to the subscribing application. In other words, as long as the subscribing application has the corresponding permissions, the data interaction between the associated application and the subscribed device can be obtained through the IoT platform.

[0082] Figure 8 The following is a flow chart of information exchange between a subscription application and an associated application by issuing instruction data provided by the second embodiment of the present invention. Figure 8 As shown, the IoT platform receives the command data sent by application B through RestAPI, and the outbound processor in the IoT platform sends the command data (i.e. Figure 8 The outbound processor may be a module for the IoT platform to send messages outward. The issued instruction data sent by the IoT platform to application A may be the issued instruction operation data sent by application B to the IoT platform and the issued instruction response data fed back by the subscribed device to the issued instruction operation data. At the same time, the IoT platform feeds back the issued instruction response data fed back by the subscribed device to the issued instruction data of application B to application B.

[0083] In an embodiment of the present invention, if the issued instruction data is issued instruction response data, then before the issued instruction data is fed back to the subscribing application, it may also include: performing data filtering processing on the issued instruction response data to obtain filtered instruction response data; determining target instruction response data based on the application subscription rules and the filtered instruction response data; and feeding back the target instruction response data to the subscribing application according to the data communication protocol.

[0084] Among them, data filtering processing can be a filtering operation of the Internet of Things platform on the sent instruction response data for erroneous data or invalid data. The filtered instruction response data can be the data obtained after the sent instruction response data is subjected to data filtering processing. The target instruction response data can be the filtered instruction response data that matches the subscription rule. The data communication protocol can be a series of agreements stipulated to ensure that the communicating parties in the data communication network can communicate effectively and reliably. These agreements may include the format, sequence and rate of data, confirmation or rejection of data transmission, error detection, retransmission control and inquiry and other operations. The embodiment of the present invention does not specifically limit the content of the data communication protocol.

[0085] In an optional embodiment, a data interaction scenario between the subscribing application and the subscribed device can be: the IoT platform receives the issuing instruction data sent by the associated application of the subscribed device, the subscribed device responds to the issuing instruction, performs data filtering processing on the instruction response data of the subscribed device, obtains the filtered instruction response data, and determines the filtered instruction response data that matches the subscription rule, i.e., the target instruction response data. Then, the IoT platform can feed back the target instruction response data to the subscribing application according to the data communication protocol and the subscription rule.

[0086] Fig. 9 The following is a flow chart of a subscribing application and a subscribed device performing data interaction by issuing instruction data provided in the second embodiment of the present invention. Fig. 9 As shown, it is assumed that the subscribing application is application A, the associated application is application B, and the subscribed device is device b1. The IoT platform receives the issuing instruction operation data sent by application B through RestAPI, and sends the issuing instruction operation data to device b1 through EMQ. When device b1 generates issuing instruction response data for the issuing instruction operation data, it sends the issuing instruction response data to the IoT platform through EMQ. After receiving the issuing instruction response data, the IoT platform uses the outbound processor to process it. Specifically, the outbound processor can perform data filtering on the issuing instruction response data to obtain filtered instruction response data. Data decentralization is performed on the filtered instruction response data. The so-called data decentralization means that applications with different permissions can access or query different data. Among them, the data decentralization process can be based on subscription rules, that is, Fig. 9The configuration rules shown determine which data in the issued instruction response data are the data that the subscribing application has access or query permissions to, and then send the data that the subscribing application has access or query permissions to the subscribing application. Assuming that there is a subscription relationship between application A and device b1, and application A has all operation permissions on device b1, it is determined that the permission check is passed, and application A has access permissions to the issued instruction response data sent by device b1. Therefore, all filtered instruction response data can be used as target instruction response data. Assuming that there is a subscription relationship between application A and device b1, but application A has partial operation permissions on device b1, at this time, the configuration rules of application A are subjected to permission verification. When part or all of the data in the filtered instruction response data matches the subscription event type of application A to device b1, it is determined that the permission verification is passed, and the part of the data that matches the subscription event type of application A to device b1 is filtered out from the filtered instruction response data as the target instruction response data. After determining the target instruction response data, the Internet of Things platform can convert the data format of the target instruction response data according to the data communication protocol, where the data communication protocol is referred to as the data protocol. Then, the target instruction response data after data format conversion is fed back to application A. Since there is a binding relationship between application B and device b1, and the instruction response data is the corresponding data of the instruction operation data sent to application B, the Internet of Things platform can directly send all the filtered instruction response data to application B after data format conversion.

[0087] In an optional embodiment of the present invention, establishing data interaction between a subscribing application and a subscribed device based on a subscription relationship may include: receiving a device reporting event sent by the subscribed device; and feeding back the device reporting event to the subscribing application.

[0088] The device reporting event may be an event reported by the subscribed device to the subscribed application. For example, the device reporting event may include a device alarm event, a device status reporting event, and a device location reporting event.

[0089] Correspondingly, the IoT platform can receive device-reported events sent by subscribed devices, and then feed back the device-reported events to the subscribing application according to the subscription rules.

[0090] In an embodiment of the present invention, before feeding back the device reported event to the subscribing application, it may also include: performing data filtering processing on the device reported event to obtain filtered reported event data; determining target reported event data based on application subscription rules and filtered reported event data; and feeding back the target reported event data to the subscribing application according to the data communication protocol.

[0091] The target reported event data may be filtered reported event data that matches the subscription rule.

[0092] In an optional embodiment, a data interaction scenario between a subscribing application and a subscribed device may be: the Internet of Things platform receives device reported events sent by the subscribed device, performs data filtering on the device reported events to obtain filtered reported event data, and feeds back the filtered reported event data that matches the subscription rules, i.e., the target reported event data, to the subscribing application through a data communication protocol.

[0093] Fig.10 A schematic diagram of a process for data interaction between a subscribing application and a subscribed device through device reporting events provided in the second embodiment of the present invention. Fig.10 As shown, it is assumed that the subscribing application is application A, and device b1 is the target subscribing device subscribed by application A. Device b1 sends a device reporting event to application A. The specific process may include: device b1 sends the device reporting event to EMQ, EMQ sends the device reporting event to the IoT platform through the MQTT protocol, and the IoT platform performs data filtering on the device reporting event through the outbound processor to obtain the filtered reporting event data. Then, data decentralization is performed on the filtered reporting event data. Since application A has access rights to the filtered reporting event data, i.e., the target reporting event data, that matches the subscription rules of device b1, it is determined that the permission check has passed, and further the data format conversion is performed on the target reporting event data according to the data communication protocol, and the conversion result is fed back to the subscribing application.

[0094] Fig.11 A schematic diagram of the system architecture of a data processing method for the Internet of Things provided by Embodiment 2 of the present invention. Fig.11 As shown, the application layer communicates with the IoT platform by calling the RestAPI interface, and the IoT platform communicates with EMQ through MQTT. The device side can receive the application layer's command data, issue device commands, or send device reporting events to the application layer through EMQ. Among them, the IoT platform, as a transit station for connecting communications, can allocate permissions for issuing command data, issuing device commands, and device reporting events to the applications and devices involved in the subscription according to the subscription rules. The IoT platform filters and decentralizes the data fed back by the device side according to the subscription rules, that is, the configuration rules, and finally feeds back to the application layer. Among them, the EMQ subscription topic can be multiple topics subscribed by a device side to the server through EMQ. The subscription topic can be the information corresponding to the issued command data or the issued device command received by the device side, or it can be different device reporting events sent by the device side.

[0095] It can be seen that by establishing a subscription relationship between the subscribing application and the subscribed device, the subscribing application can interact with the subscribed device for data, expanding the scope of application layer permissions, where the scope of permissions can include authorization between two applications, authorization between different applications under the same user, and authorization between different applications under two users. The expansion of the scope of application layer permissions makes IoT data processing more flexible to meet flexible and changing business needs.

[0096] The embodiment of the present invention allocates device permissions to the subscribed device according to the subscription rules through the subscription application, and the subscribed application has partial operation permissions on the subscribed device, for example, issuing device instructions, viewing the response data of the issued instructions, filtering and viewing the target device operation type and the device reporting events, etc. The problem that the existing Internet of Things platform can only process data for applications and devices with binding relationships is solved, so as to break the single binding relationship between the application and the device and expand the application layer's control scope over the device side. It realizes cross-application device operation, cross-application viewing of the issued instruction data sent to the device, the device can upload and report event data across applications, the viewing and operation permissions of the specified device can be subscribed, and the specified reporting event data of the device side can be subscribed, so as to improve the flexibility and scalability of Internet of Things data processing, meet flexible and changeable business needs, make the processing process more convenient, more secure, and lower the cost when the application side changes are small.

[0097] Embodiment 3

[0098] Fig.12 is a schematic diagram of a data processing device based on the Internet of Things provided by Embodiment 3 of the present invention, such as Fig.12 As shown, the device includes: a subscription relationship establishment module 310 and a data interaction module 320, wherein:

[0099] The subscription relationship establishment module 310 is used to establish a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application;

[0100] The data interaction module 320 is used to establish data interaction between the subscribing application and the subscribed device based on the subscription relationship.

[0101] The embodiments of the present invention solve the problem that the existing Internet of Things platform can only process data for applications and devices with a binding relationship by establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship between the subscribing application and the subscribed device, so as to break the single binding relationship between the application and the devices, expand the application layer's control scope over the device side, thereby improving the flexibility and scalability of Internet of Things data processing and meeting flexible and changeable business needs.

[0102] Optionally, the subscription relationship establishing module 310 is specifically used to determine the subscribing application and the subscribed application; filter the target device operation type from the device operation type set included in the subscribed application; and establish a subscription relationship between the subscribing application and the target device operation type.

[0103] Optionally, the subscription relationship establishing module 310 is further configured to determine a target subscription device according to the target device operation type; and establish a subscription relationship between the subscription application and the target subscription device.

[0104] Optionally, a subscription relationship establishment module is specifically used to determine the subscription event type that matches the subscription application and the target subscription device; establish a subscription relationship between the subscription application and the target subscription device according to the subscription event type; wherein the subscription event type includes device alarm events, device attachment upload events, device attachment download events, device status reporting events, device location reporting events and device activation events.

[0105] Optionally, the device further includes: an instruction sending type module, used to determine the instruction sending type that matches the subscription application with the subscription event type; wherein the instruction sending type includes a device status acquisition instruction, a device information acquisition instruction and a device control instruction.

[0106] Optionally, the data interaction module 320 is used to receive a device sending instruction sent by the subscription application; and send the device sending instruction to the subscribed device.

[0107] Optionally, the data interaction module 320 is specifically used to determine the application subscription rules that match the subscribed application; perform permission verification on the device instruction to be issued according to the application subscription rules; if it is determined that the permission verification passes, the device instruction to be issued is issued to the subscribed device.

[0108] Optionally, the data interaction module 320 is specifically configured to receive the sending instruction data of the associated application of the subscribed device; and feed back the sending instruction data to the subscribing application.

[0109] Optionally, the sent instruction data includes sent instruction operation data and sent instruction response data.

[0110] Optionally, if the issued instruction data is issued instruction response data, the data interaction module 320 can also be used to perform data filtering on the instruction response data to obtain filtered instruction response data; determine target instruction response data according to application subscription rules and the filtered instruction response data; and feed back the target instruction response data to the subscribing application according to the data communication protocol.

[0111] Optionally, the data interaction module 320 is specifically configured to receive a device-reported event sent by the subscribed device; and feed back the device-reported event to the subscribing application.

[0112] Optionally, the data interaction module 320 is specifically used to perform data filtering processing on the device reported events to obtain filtered reported event data; determine target reported event data according to application subscription rules and the filtered reported event data; and feed back the target reported event data to the subscribing application according to the data communication protocol.

[0113] The data processing device of the Internet of Things can execute the data processing method of the Internet of Things provided by any embodiment of the present invention, and has the functional modules and beneficial effects corresponding to the execution method. For technical details not described in detail in this embodiment, please refer to the data processing method of the Internet of Things provided by any embodiment of the present invention.

[0114] Since the data processing device of the Internet of Things introduced above is a device that can execute the data processing method of the Internet of Things in the embodiment of the present invention, based on the data processing method of the Internet of Things introduced in the embodiment of the present invention, the technical personnel in the field can understand the specific implementation of the data processing device of the Internet of Things in this embodiment and its various variations, so how the data processing device of the Internet of Things implements the data processing method of the Internet of Things in the embodiment of the present invention is not introduced in detail here. As long as the technical personnel in the field implement the device used by the data processing method of the Internet of Things in the embodiment of the present invention, it belongs to the scope of protection of this application.

[0115] Embodiment 4

[0116] Fig.13 A schematic diagram of the structure of a computer device provided in Embodiment 4 of the present invention. Fig.13 A block diagram of a computer device 412 suitable for use in implementing embodiments of the present invention is shown. Fig.13 The computer device 412 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0117] like Fig.13 As shown, the computer device 412 is in the form of a general-purpose computing device. The components of the computer device 412 may include, but are not limited to: one or more processors 413, a storage device 428, and a bus 418 connecting different system components (including the storage device 428 and the processor 416).

[0118] Bus 418 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0119] The computer device 412 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer device 412, including volatile and non-volatile media, removable and non-removable media.

[0120] The storage device 428 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 430 and / or cache memory 432. The computer device 412 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 434 may be used to read and write non-removable, non-volatile magnetic media ( Fig.13 not shown, usually called a "hard drive"). Although Fig.13 Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a read-only optical disk (Compact Disc-ReadOnly Memory, CD-ROM), a digital video disk (Digital Video Disc-Read Only Memory, DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 418 via one or more data medium interfaces. The storage device 428 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0121] A program 436 having a set (at least one) of program modules 426 may be stored, for example, in a storage device 428, such program modules 426 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may include an implementation of a network environment. Program modules 426 generally perform the functions and / or methods of the embodiments described herein.

[0122] The computer device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, camera, display 424, etc.), may also communicate with one or more devices that enable a user to interact with the computer device 412, and / or communicate with any device that enables the computer device 412 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 422. In addition, the computer device 412 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through a network adapter 420. As shown, the network adapter 420 communicates with other modules of the computer device 412 through a bus 418. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in conjunction with the computer device 412, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems.

[0123] The processor 416 executes various functional applications and data processing by running the program stored in the storage device 428, for example, implementing the data processing method based on the Internet of Things provided by the above-mentioned embodiment of the present invention: establishing a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application; and establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship.

[0124] The technical solution of this embodiment establishes a subscription relationship between a subscribing application and a subscribed device through a data processing method based on the Internet of Things; wherein the subscribed device is a non-bound device corresponding to the subscribing application; and data interaction between the subscribing application and the subscribed device is established based on the subscription relationship. This solves the problem that the existing Internet of Things platform can only process data for applications and devices with a binding relationship, breaks the single binding relationship between the application and the device, and expands the application layer's control scope over the device end, thereby improving the flexibility and scalability of Internet of Things data processing and meeting flexible and changeable business needs.

[0125] Embodiment 5

[0126] Embodiment 5 of the present invention further provides a computer storage medium storing a computer program, wherein the computer program, when executed by a computer processor, is used to execute the Internet of Things-based data processing method described in any of the above embodiments of the present invention: establishing a subscription relationship between a subscribing application and a subscribed device; wherein the subscribed device is a non-bound device corresponding to the subscribing application; and establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship.

[0127] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, a device or a device or used in combination with it.

[0128] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0129] The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

[0130] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data processing method based on the Internet of Things, characterized in that: Applied to IoT platforms, including: Determine a subscribing application and a subscribed application; wherein the subscribed application is an application that has a binding relationship with a subscribed device corresponding to the subscribing application; and the subscribed device is a non-binding device corresponding to the subscribing application; Filtering a target device operation type from a device operation type set included in the subscribed application; wherein the device operation type set is a set of operation types for performing different operation attribute types on a device, the device operation type set includes at least one operation attribute type, and each operation attribute type is associated with multiple devices; the device operation type set includes a data read type, a data delete type, and a data change type; Establishing a subscription relationship between the subscription application and the target device operation type; Determine a target subscription device according to the target device operation type; Determine the subscription event type that matches the subscription application with the target subscription device; wherein the subscription event type includes device alarm event, device attachment upload event, device attachment download event, device status reporting event, device location reporting event, device activation event, device message reporting event, device life cycle change event, object model historical data reporting event, firmware upgrade status notification event, gateway discovery sub-device reporting event and device topology relationship change event; Establishing a subscription relationship between the subscription application and the target subscription device according to the subscription event type; Determine the instruction delivery type that matches the subscription application with the subscription event type; wherein the instruction delivery type includes a device status acquisition instruction, a device information acquisition instruction, and a device control instruction; Establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship includes: receiving the issuing instruction data of the associated application of the subscribed device; feeding back the issuing instruction data to the subscribing application; receiving the device reporting event sent by the subscribed device; feeding back the device reporting event to the subscribing application; wherein the associated application is an application that has a binding relationship with the subscribed device; the issuing instruction data includes issuing instruction operation data and issuing instruction response data; Wherein, the data interaction includes: the subscribing application viewing the device information, device data, device log and device grouping of the subscribed device; Wherein, if the issued instruction data is issued instruction response data, before feeding back the issued instruction data to the subscribing application, the method further includes: Performing data filtering processing on the instruction response data to obtain filtered instruction response data; wherein the data filtering processing is a filtering operation performed by the Internet of Things platform on the instruction response data to filter out erroneous data or invalid data; Determine target instruction response data according to the application subscription rule and the filtering instruction response data; Feeding back the target instruction response data to the subscribing application according to a data communication protocol; Before feeding back the device reported event to the subscribing application, the method further includes: Performing data filtering processing on the device reported events to obtain filtered reported event data; Determine target reported event data according to the application subscription rule and the filtered reported event data; Feeding back the target reported event data to the subscribing application according to a data communication protocol; Wherein, establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship further includes: Receiving a device sending instruction sent by the subscription application; Determine an application subscription rule that matches the subscribed application; wherein the application subscription rule is a subscription relationship between the subscribed application and the subscribed device; Performing a permission check on the issued device instruction according to the application subscription rule; wherein the permission check is to determine whether the issued device instruction sent by the subscribed application has operation permission on the subscribed device according to the application subscription rule; If it is determined that the authority check is passed, the sending device instruction is sent to the subscribed device.

2. A data processing device based on the Internet of Things, characterized in that: Configured on the IoT platform, including: Subscription relationship establishment module, used for: Determine a subscribing application and a subscribed application; wherein the subscribed application is an application that has a binding relationship with a subscribed device corresponding to the subscribing application; and the subscribed device is a non-binding device corresponding to the subscribing application; Filtering a target device operation type from a device operation type set included in the subscribed application; wherein the device operation type set is a set of operation types for performing different operation attribute types on a device, the device operation type set includes at least one operation attribute type, and each operation attribute type is associated with multiple devices; the device operation type set includes a data read type, a data delete type, and a data change type; Establishing a subscription relationship between the subscription application and the target device operation type; Determine a target subscription device according to the target device operation type; Determine the subscription event type that matches the subscription application and the target subscription device; wherein the subscription event type includes device alarm event, device attachment upload event, device attachment download event, device status reporting event, device location reporting event, device activation event, device message reporting event, device life cycle change event, object model historical data reporting event, firmware upgrade status notification event, gateway discovery sub-device reporting event and device topology relationship change event; establish a subscription relationship between the subscription application and the target subscription device according to the subscription event type; An instruction issuing type module, used to determine the instruction issuing type that matches the subscription application with the subscription event type; wherein the instruction issuing type includes a device status acquisition instruction, a device information acquisition instruction, and a device control instruction; A data interaction module, used to establish data interaction between the subscribing application and the subscribed device based on the subscription relationship; The data interaction module is specifically used to: receive the issuing instruction data of the associated application of the subscribed device; feed back the issuing instruction data to the subscribing application; receive the device reporting event sent by the subscribed device; feed back the device reporting event to the subscribing application; wherein the associated application is an application that has a binding relationship with the subscribed device; the issuing instruction data includes issuing instruction operation data and issuing instruction response data; Wherein, the data interaction includes: the subscribing application viewing the device information, device data, device log and device grouping of the subscribed device; Wherein, if the issued instruction data is issued instruction response data, before feeding back the issued instruction data to the subscribing application, the method further includes: Performing data filtering processing on the instruction response data to obtain filtered instruction response data; wherein the data filtering processing is a filtering operation performed by the Internet of Things platform on the instruction response data to filter out erroneous data or invalid data; Determine target instruction response data according to the application subscription rule and the filtering instruction response data; Feeding back the target instruction response data to the subscribing application according to a data communication protocol; Before feeding back the device reported event to the subscribing application, the method further includes: Performing data filtering processing on the device reported events to obtain filtered reported event data; Determine target reported event data according to the application subscription rule and the filtered reported event data; Feeding back the target reported event data to the subscribing application according to a data communication protocol; Wherein, establishing data interaction between the subscribing application and the subscribed device based on the subscription relationship further includes: Receiving a device sending instruction sent by the subscription application; Determine an application subscription rule that matches the subscribed application; wherein the application subscription rule is a subscription relationship between the subscribed application and the subscribed device; Performing a permission check on the issued device instruction according to the application subscription rule; wherein the permission check is to determine whether the issued device instruction sent by the subscribed application has operation permission on the subscribed device according to the application subscription rule; If it is determined that the authority check is passed, the sending device instruction is sent to the subscribed device.

3. A computer device, characterized in that: The computer device comprises: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method based on the Internet of Things as described in claim 1.

4. A computer storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the data processing method based on the Internet of Things as claimed in claim 1 is implemented.

Images