Reporting control method, system and apparatus for internet-of-things device, and medium

Abstract

Disclosed in the present application are a reporting control method, system and apparatus for an Internet-of-Things device, and a storage medium. The method comprises: acquiring the current message count value allocated to the current message among messages reported one by one by an Internet-of-Things device within a unit time period, a first limit value of a built-in limitation policy, the remaining number of permissions allowed by a platform for a user to go beyond the limit, and the maximum limit value for message reporting; when the current message count value is less than the first limit value, receiving and processing the current message; when the current message count value is greater than the maximum limit value, discarding the current message; when the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining number of permissions is greater than 0, receiving and processing the current message, and subtracting 1 from the total remaining number of permissions; and when the remaining number of permissions is less than or equal to 0, discarding the current message corresponding to a message count value. The present application can be widely applied in the technical field of the Internet of Things.

Description

A method, system, device and medium for controlling reporting of IoT devices Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a method, system, device and storage medium for controlling reporting of Internet of Things devices. Background Art

[0002] In related technologies, with the increasing popularity of the Internet of Things (IoT), the number of IoT devices connected to platforms is increasing, and the protocols and business scenarios used by these devices are also diverse. When a device malfunctions, it is very easy to generate a large amount of junk data, resulting in a sharp increase in the amount of reported data, which can affect the stable operation of the platform and cause failures on the application side due to excessive processing of pushed data. Therefore, technical problems still need to be solved in related technologies.

[0003] Summary of the Invention

[0004] The purpose of this application is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0005] To this end, one purpose of the embodiments of the present application is to provide an IoT device reporting control method, system, device and storage medium, which can reduce the generation of uplink message data and improve the stability of the IoT platform.

[0006] To achieve the above technical objectives, the technical solutions adopted by the embodiments of the present application include: a method for controlling reporting of IoT devices, comprising: obtaining a current message count value allocated to current messages reported one by one by IoT devices within a unit time period, a first limit value of a built-in limit policy, the remaining number of releases allowed by the platform for users to exceed the limit, and a maximum limit value for reported messages;

[0007] When the current message count value is less than the first limit value, receiving and processing the current message;

[0008] When the current message count value is greater than the maximum limit value, discard the current message;

[0009] When the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining release times are greater than 0, the current message is received and processed, and the total remaining release times are reduced by 1; when the remaining release times are less than or equal to 0, the current message corresponding to the message count value is discarded.

[0010] In addition, the method for controlling reporting of an IoT device according to the above embodiment of the present invention may also have the following additional technical features:

[0011] Furthermore, in an embodiment of the present application, the method also includes: when the current unit time period ends, generating a reporting restriction detail list; the reporting restriction detail list includes one or more items of product identification, restriction period, restriction trigger time point and restriction policy status.

[0012] Further, in an embodiment of the present application, the first limit value is obtained through the following steps: configuring the first limit threshold of the unit time period of the first level of reporting messages, the second limit threshold of the unit time period of the second level of reporting messages, the first priority weight of the first level, the second priority weight of the second level, the maximum basic authority value set by the platform for the protocol device, and the first basic limit value; determining the first target limit threshold from the first limit threshold and the second limit threshold based on the first priority weight and the second priority weight; determining the second basic limit value based on the first basic limit value and the first target limit threshold; when the second basic limit value is greater than the maximum basic authority value, determining the maximum basic limit value as the first limit value; when the second basic limit value is less than the maximum basic authority value, determining the second basic limit value as the first limit value.

[0013] Furthermore, in an embodiment of the present application, the current message count value is obtained by the following method: the current message count value is incremented one by one starting from 1 in each unit time period, and after the unit time period ends, the count value is cleared to zero; at the beginning of the next unit time period, the current message count value is incremented one by one starting from 1 again.

[0014] Furthermore, in an embodiment of the present application, the step of determining the first target restriction threshold from the first restriction threshold and the second restriction threshold based on the first priority weight and the second priority weight specifically includes: when the first priority weight is greater than the second priority weight, determining the first restriction threshold as the first target restriction threshold; when the first priority weight is less than the second priority weight, determining the second restriction threshold as the first target restriction threshold.

[0015] Furthermore, in an embodiment of the present application, the step of determining the second basic limit value based on the first basic limit value and the first target limit threshold specifically includes: summing the first basic limit value and the first target limit threshold to obtain a first sum value; and using the first sum value as the second basic limit value.

[0016] Furthermore, in an embodiment of the present application, the current messages reported one by one by the IoT device within a unit time period include: publish messages reported one by one by the MQTT protocol device or notify messages reported one by one by the LwM2M protocol device.

[0017] On the other hand, an embodiment of the present application also provides an Internet of Things device reporting control system, including: a current message count value allocated to the current messages reported one by one by the Internet of Things devices within a unit time period, a first limit value of the built-in restriction policy, the remaining number of releases allowed by the platform for users to exceed the limit, and the maximum limit value of the reported messages; a first processing unit, for receiving and processing the current message when the current message count value is less than the first limit value; discarding the current message when the current message count value is greater than the maximum limit value; or receiving and processing the current message when the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining number of releases is greater than 0, and the total remaining number of releases is reduced by 1; when the remaining number of releases is less than or equal to 0, discarding the current message corresponding to the message count value.

[0018] On the other hand, the present application also provides an IoT device reporting control device, comprising:

[0019] at least one processor;

[0020] at least one memory for storing at least one program;

[0021] When the at least one program is executed by the at least one processor, the at least one processor implements a reporting control method for an Internet of Things device as described in any one of the invention contents.

[0022] In addition, the present application also provides a computer-readable storage medium, which stores processor-executable instructions. When the processor executes the instructions, the processor-executable instructions are used to execute an IoT device reporting control method as described in any one of the above items.

[0023] The advantages and benefits of this application will be partially given in the following description, and partially become apparent from the following description, or learned through practice of this application:

[0024] This application can determine whether the current messages reported one by one should be released by the platform through the current message count value assigned by the platform to the current messages reported one by one by the IoT device within a unit time period, the first limit value of the built-in limit policy, the remaining number of releases allowed by the platform for the user to exceed the limit, and the maximum limit value of the reported message. When the current message count value is less than the first limit value, the current message can be released. When the current message count value is greater than the first limit value and less than the maximum limit value of the message, the remaining release times can be calculated by the message sequence number and the total number of releases allowed to exceed the limit, and whether to release the reported message with the current sequence number can be determined based on the remaining release times. When the current message has a remaining release time greater than 0 when it is reported, the platform can receive and process the current message. When the current message has a remaining release time less than or equal to 0 when it is reported, the platform can discard the current message and subsequent reported messages to reduce the platform's reception of reported messages. This application can reduce the platform's reception of uplink message data, reduce platform garbage, and improve the stability of the IoT platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] FIG1 is a schematic diagram of the steps of a method for controlling reporting of an Internet of Things device according to a specific embodiment of the present invention;

[0026] FIG2 is a schematic diagram of the steps of a reporting control method for an IoT device in another specific embodiment of the present invention;

[0027] FIG3 is a schematic diagram of the structure of a detailed list of reporting restrictions in a specific embodiment of the present invention;

[0028] FIG4 is a schematic diagram of the steps of obtaining a first limit value in a specific embodiment of the present invention;

[0029] FIG5 is a schematic diagram of the steps of calculating the remaining release times corresponding to the current message according to the total release times and the message sequence number in a specific embodiment of the present invention;

[0030] 6 is a schematic diagram of steps for determining a first target limit threshold from a first limit threshold and a second limit threshold according to a first priority weight and a second priority weight in another specific embodiment of the present invention;

[0031] FIG7 is a schematic diagram of steps for determining a second basic limit value based on a first basic limit value and a first target limit threshold in a specific embodiment of the present invention;

[0032] FIG8 is a schematic diagram of a process for determining a first limit value in a specific embodiment of the present invention;

[0033] FIG9 is a flow chart of a method for controlling reporting of IoT devices in accordance with a specific embodiment of the present invention;

[0034] FIG10 is a schematic diagram of the structure of an Internet of Things device reporting control system in another specific embodiment of the present invention;

[0035] FIG11 is a schematic structural diagram of a reporting control device for an Internet of Things device in a specific embodiment of the present invention. DETAILED DESCRIPTION

[0036] The following describes the embodiments of the present invention in detail with reference to the accompanying drawings to illustrate the principles and processes of the Internet of Things device reporting control method, system, device and storage medium in the embodiments of the present invention.

[0037] First, let’s explain the terms used in this application:

[0038] MQTT protocol: MQTT (Message Queuing Telemetry Transport) is a "lightweight" communication protocol based on the publish / subscribe model.

[0039] Publish message: A publish message is an application message transmitted from the client to the server or from the server to the client. The publish message consists of a fixed header, a variable header, and a limited payload.

[0040] LwM2M protocol: LwM2M (Lightweight M2M), proposed by the Open Mobile Alliance (OMA), is a lightweight, standard and universal IoT device management protocol that can be used to quickly deploy IoT services in a client / server model.

[0041] Notify message: The notify message is similar to a "measurement report" or "information response" in the radio protocol. It can convey the information requested by the SUBSCRIBE message.

[0042] Secondly, in related technologies, with the increasing popularity of the Internet of Things (IoT), the number of IoT devices connected to the platform is increasing, and the protocols and business scenarios used by these devices are also diverse. When a device malfunctions, it is very easy to generate a large amount of garbage data, resulting in a sharp increase in the amount of reported data, which affects the stable operation of the platform and causes failures on the application side due to excessive processing of pushed data. Therefore, there are still problems in related technologies that need to be solved urgently.

[0043] In view of the above-mentioned defects of the prior art, referring to Figure 1, which is a schematic diagram of the steps of a method for controlling reporting of an IoT device provided by an embodiment of the present application, the method for controlling reporting of an IoT device may include but is not limited to steps S101 to S103.

[0044] S101. Obtain a current message count value allocated to current messages reported one by one by IoT devices within a unit time period, a first limit value of a built-in limit policy, a remaining number of releases allowed by the platform for the user to exceed the limit, and a maximum limit value for reported messages.

[0045] It is understandable that the IoT device can report multiple messages one by one within a unit time period. Each reported message can correspond to a count value. The count value of the messages reported within a unit time period starts from 1. The first limit value of the built-in restriction policy can be calculated according to the built-in algorithm. When the message is reported, the platform can call the first limit value from the database. The remaining number of times the platform allows the user to release in excess of the quota can be the number of remaining messages that can be released for the IoT system configured by the user according to actual needs. When no message has been released at the beginning, the remaining number of releases can be equal to the total number of times the platform allows the user to release in excess of the quota. The maximum limit value for the reported message is the maximum limit value that the IoT system configured by the platform can reach.

[0046] In some feasible embodiments of the application, the platform's processor can establish a wired or wireless connection with the terminal through the platform's acquisition module, and obtain from the acquisition module through the data transmission protocol the current message count value of the current message allocation reported one by one by the IoT device within a unit time period, the first limit value of the built-in restriction policy, the remaining number of times the platform allows the user to exceed the limit, and the maximum limit value of the reported message.

[0047] It should be noted that the aforementioned wired connection method may include a connection between a mobile device and a processing module, and may also include a connection between a processing module and a hardware device, and a wired connection between other currently known or future-developed devices and the processing module; and the aforementioned wireless connection method may include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (Ultra Wide Band) connection, and other currently known or future-developed wireless connection methods. The specific value of the first limit value of the built-in limit policy and the specific value of the maximum limit value of the reported message can be configured and adjusted differently according to user needs.

[0048] S102: When the current message count value is less than the first limit value, receive and process the current message.

[0049] S103: When the current message count value is greater than the maximum limit value, the current message is discarded.

[0050] S104. When the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining release times are greater than 0, receive and process the current message, and reduce the total remaining release times by 1; when the remaining release times are less than or equal to 0, discard the current message corresponding to the message count value.

[0051] It is understood that the remaining release count can vary as the count value of each message reported one by one changes. During the process of reporting messages one by one, each message exceeding the first limit value can be assigned a remaining release count. As the message count value increases, the remaining release count decreases. Specifically, the remaining release count can continuously decrease as the count value of each message reported one by one increases. The remaining release count can represent the number of messages remaining for release by the platform. After each message exceeding the first limit value is released to the platform, the remaining release count decreases by 1.

[0052] In some embodiments of the present application, when the current message count value is less than a first limit value, the platform receives and processes the current message. When the current message count value is greater than a maximum limit value, the platform discards the current message. When the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining release count is greater than 0, the platform receives and processes the current message, and the total remaining release count is reduced by 1. When the remaining release count is less than or equal to 0, the platform discards the current message corresponding to the message count value.

[0053] It is understood that the maximum limit can be less than the total number of passes allowed to exceed the user's limit. For example, when the maximum limit is 200 and the total number of passes is 250, and the current message count reported by the IoT device within a unit time period is 1-200, the platform receives and processes the current message. When the current message count reaches 201, although 201 is not greater than the total number of passes (250), it exceeds the maximum limit of 200, so the platform can discard the message with the count of 201.

[0054] In summary, this embodiment can determine whether the current messages reported one by one should be released by the platform through the count value assigned to the current messages reported one by one by the IoT devices within a unit time period, the first limit value of the built-in limit policy, the total number of releases allowed for the user to exceed the limit, and the maximum limit value of the reported messages. When the count value of the current message is less than the first limit value, the current message can be released. When the sequence number of the current message is greater than the first limit value and less than the maximum limit value of the message, the message policy can be judged by the remaining number of releases allowed for the user to exceed the limit, and whether to release the current message can be determined based on the remaining number of releases. When the remaining number of releases of the current message is greater than 0 when it is reported, the platform can receive and process the current message. When the remaining number of releases of the current message is less than or equal to 0 when it is reported, the platform can discard the current message and subsequent reports within the unit time period to reduce the reception of reported messages by the platform. This application can reduce the reception of uplink message data on the platform, reduce platform garbage, and improve the stability of the IoT platform.

[0055] Further, referring to Figure 2, which is a schematic diagram of steps of another method for controlling reporting of IoT devices, the control method may further include step S105.

[0056] S105. When the current unit time period ends, generate a detailed restriction report list; the detailed restriction report list includes one or more items of product identification, restriction period, restriction triggering time point, and restriction policy status.

[0057] In some feasible embodiments of the present application, after the platform discards the corresponding current message, the platform successfully triggers the message restriction policy. After the message restriction policy is triggered, after the unit time period ends, the platform can generate a corresponding reporting restriction detail list; the reporting restriction detail list includes one or more items of product identification, restriction period, restriction triggering time point and restriction policy status. For example, with reference to Figure 3, the reporting restriction detail list may include: tenant identification (first level identification), product identification (second level identification), device identification, restriction period, number of times limit (first limit value), restriction time, recovery time, number of messages (the total number of messages reported one by one within the unit time period) and release policy.

[0058] Further, referring to Figure 4, Figure 4 is a schematic diagram of the steps of obtaining the first limit value in an embodiment of the present application. In Figure 4, the steps may specifically include steps S201 to S205.

[0059] S201: Configure a first limit threshold for reporting messages at the first level per unit time period, a second limit threshold for reporting messages at the second level per unit time period, a first priority weight for the first level, a second priority weight for the second level, a maximum basic authority value set by the platform for the protocol device, and a first basic limit value;

[0060] S202: Determine a first target limit threshold from the first limit threshold and the second limit threshold according to the first priority weight and the second priority weight;

[0061] S203, determining a second basic limit value according to the first basic limit value and the first target limit threshold;

[0062] S204: When the second basic limit value is greater than the maximum basic authority value, determine the maximum basic limit value as the first limit value;

[0063] S205: When the second basic limit value is less than the maximum basic authority value, determine the second basic limit value as the first limit value.

[0064] It can be understood that the first target limit threshold can be any one of the limit thresholds determined from the first limit threshold and the second limit threshold, and the second basic limit value can be a value obtained by summing the first basic limit value and the first target limit threshold.

[0065] In some feasible embodiments of the present application, the platform processor may first configure a first limit threshold for a first level (such as tenant level) of reported messages per unit time period (such as per minute), a second limit threshold for a second level (such as product level) of reported messages per unit time period (such as per minute), a first priority weight of the first level (such as tenant level), a second priority weight of the second level (such as product level), a maximum basic authority value set by the platform for the protocol device, and a first basic limit value; then, based on the first priority weight and the second priority weight, determine a first target limit threshold from the first limit threshold and the second limit threshold; then, based on the first basic limit value and the first target limit threshold, determine a second basic limit value; then, when the second basic limit value is greater than the maximum basic authority value, determine the maximum basic limit value as the first limit value; and when the second basic limit value is less than the maximum basic authority value, determine the second basic limit value as the first limit value.

[0066] Further, referring to Figure 5, Figure 5 is a schematic diagram of the steps for calculating the remaining release times corresponding to the current message based on the total release times and the message count value in an embodiment of the present application. In Figure 5, this step may specifically include but is not limited to steps S301-S302.

[0067] S301, the current message count value is incremented by 1 in each unit time period, and the count value is reset to zero after the unit time period ends;

[0068] S302: The next unit time period begins, and the current message count value starts to increase from 1 again.

[0069] In some feasible embodiments of the present application, the platform processor can judge the total number of releases and the message count value. When the message count value is greater than the first limit value and less than the maximum limit value, and the total number of releases is greater than 0, the total number of releases is reduced by 1 one by one as the first difference; then the first difference is used as the remaining number of releases.

[0070] Further, referring to Figure 6, Figure 6 is a schematic diagram of the steps of determining the first target limit threshold from the first limit threshold and the second limit threshold according to the first priority weight and the second priority weight in an embodiment of the present application. In Figure 6, this step may specifically include but is not limited to steps S401-S402.

[0071] S401: When the first priority weight is greater than the second priority weight, determine the first limit threshold as the first target limit threshold;

[0072] S402: When the first priority weight is less than the second priority weight, determine the second limit threshold as the first target limit threshold.

[0073] In some feasible embodiments of the present application, the platform processor may first compare the size relationship between the first priority weight and the second priority weight. When the first priority weight is greater than the second priority weight, the first limit threshold is determined as the first target limit threshold; when the first priority weight is less than the second priority weight, the second limit threshold is determined as the first target limit threshold.

[0074] Further, referring to Figure 7, Figure 7 is a schematic diagram of the steps of determining the second basic limit value based on the first basic limit value and the first target limit threshold in an embodiment of the present application. In Figure 7, the method may include steps S501 and S502.

[0075] S501, summing a first basic limit value and a first target limit threshold value to obtain a first sum value;

[0076] S502: Use the first sum value as the second basic limit value.

[0077] In some feasible embodiments of the present application, the platform may sum the first basic limit value and the first target limit threshold, that is, add the first basic limit value and the first target limit threshold to obtain a first sum value; and use the obtained first sum value as the second basic limit value.

[0078] Furthermore, in some feasible embodiments of the present application, the current messages reported one by one by the IoT device within a unit time period include: publish messages reported one by one by the MQTT protocol device or notify messages reported one by one by the LwM2M protocol device.

[0079] In some feasible embodiments of the application, the messages reported one by one by the IoT devices may be publish messages reported one by one by the MQTT protocol devices, or may be notify messages reported one by one by the LwM2M protocol devices.

[0080] The specific implementation principle of this application is described below with reference to the accompanying drawings:

[0081] Referring to Figures 8 and 9, in this embodiment, the IoT device reporting control method can calculate the final effective device restriction policy based on unit time reporting control policies of different levels and priorities. Users can set unit time reporting control policies of different levels (such as first level (such as tenant level) and second level (such as product level)) and different priorities (such as unit time period (such as per minute)) based on the device protocol and the device's actual business scenario. The platform calculates the minimum level (such as the second level (such as product level)) reporting policy based on the different levels and priorities. If a priority is configured, the configured priority prevails; if no priority is configured, the minimum level configuration has the highest priority. The platform presets a base unit time limit value for each protocol (such as 30 times per minute for the MQTT protocol and 10 times per minute for the LwM2M protocol), as well as a maximum limit value for each protocol (such as 600 times per minute for the MQTT protocol and 300 times per minute for the LwM2M protocol).

[0082] The device's final restriction policy is the sum of the protocol's base limit and the calculated reporting control policy. If no reporting policy is configured, the device's base limit is applied. If the final reporting policy exceeds the protocol's maximum limit, the maximum limit of each protocol is applied.

[0083] For example, if a user needs to configure a reporting control policy for a certain protocol device. The basic permission value set by the platform for the protocol device is z times per unit time period (such as per minute), and the maximum value is w times per unit time period (such as per minute) (z, w are not 0, and w is not less than z). The first-level (such as tenant-level) control policy configured by the user is x times per unit time period (such as per minute) and the priority weight is a. The second-level (such as product-level) control policy is y times per unit time period (such as per minute) and the priority weight is b. (a, b, x, y can all be 0, indicating that the item is not configured). The calculation method of the restriction policy n that finally takes effect includes formula 1 and formula 2.

[0084] Formula 1: m = z + ((a>b)?x:y);

[0085] Formula 2: n = m <w?m:w;

[0086] Formula 1 indicates that the customized second basic limit value m is the sum of the larger of z, a, and b, and Formula 2 indicates that the final effective restriction strategy n can be the smaller of the customized second basic limit value m and the maximum value w.

[0087] The IoT device reporting control method of this embodiment can implement optimal reporting restrictions and output detailed lists based on different device protocol types. According to the specifications of each IoT protocol, filter out the uplink messages that need to be restricted by the device (such as publish messages of MQTT protocol devices, notify messages of LwM2M protocol devices, etc.), and implement restrictions based on the calculated final reporting strategy. Start timing and counting with the number of the first uplink message that needs to be restricted from the device. When the device triggers the restriction, discard the subsequent uplink messages and output the trigger restriction detailed list.

[0088] When the unit timer expires, the timer and count value are restored. If the restriction is triggered within the period (that is, the number of releases is equal to 0 or the message sequence number exceeds the system's maximum limit), a restriction restoration detail list is output. The restriction restoration detail list may include, but is not limited to: device identification, restriction period (unit time length), restriction restoration time, restriction policy, and the total number of messages actually reported within the unit time.

[0089] This embodiment of the IoT device reporting control method can be used to implement appropriate release policies when devices trigger restricted behavior, targeting business scenarios requiring additional times. For different device business scenarios, such as those requiring remote upgrades or busy / idle interaction, the total number of releases can be set to allow devices to be released when reporting limits are triggered. After setting the number of releases, the release policy is marked as true.

[0090] When a device triggers a reporting restriction: If the release policy is true and the total number of reports per unit time does not exceed the maximum limit set by the protocol, the uplink message is not discarded and business processing proceeds normally. If the release policy is true and the total number of reports per unit time exceeds the maximum limit set by the protocol, the uplink message is discarded. If the release policy is false, the uplink message is discarded. Based on the control details output when the device restores the restriction, the platform calculates the remaining number of released messages in real time by subtracting the number of messages actually released outside the restriction policy from the set number of released messages. It should be noted that when the remaining number of released messages is greater than 0, the release policy is marked as true; when the remaining number of released messages returns to 0, the release policy is marked as false.

[0091] In addition, referring to FIG10 , corresponding to the method of FIG1 , an embodiment of the present application further provides an IoT device reporting control system. The system may include: an acquisition unit 1001 and a first processing unit 1002. The acquisition unit 1001 may be configured to acquire a current message count value allocated to current messages reported one by one by IoT devices within a unit time period, a first limit value of a built-in limit policy, a remaining number of releases allowed by the platform for users to exceed the limit, and a maximum limit value for reported messages. The first processing unit 1002 may be configured to receive and process the current message when the current message count value is less than the first limit value; or discard the current message when the current message count value is greater than the maximum limit value; or receive and process the current message when the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining number of releases is greater than 0, and the total remaining number of releases is reduced by 1; and discard the current message corresponding to the message count value when the remaining number of releases is less than or equal to 0.

[0092] It should be noted that the acquisition unit can be any integrated circuit unit or microprocessor unit obtained by integrating a chip having processing functions and its peripheral circuits using existing integration technology. The first processing unit and the second processing unit can also be any integrated circuit module or microprocessor module obtained by integrating a chip having processing functions and its peripheral circuits using existing integration technology. The first processing unit and the second processing unit can also include one or more memories. One or more memories can be used to store the specific algorithm used for compression adjustment processing in this application.

[0093] In some embodiments of the present application, the acquisition unit 1001 and the processing unit 1002 may be provided in the same gateway or device having a processor. The specific device connection method and device configuration of the acquisition unit 1001 and the first processing unit 1002 are not limited.

[0094] It should be noted that the contents of the above-mentioned Internet of Things device reporting control method embodiment are all applicable to the present Internet of Things device reporting control system embodiment. The functions specifically implemented by the present Internet of Things device reporting control system embodiment are the same as those of the above-mentioned Internet of Things device reporting control method embodiment, and the beneficial effects achieved are also the same as those achieved by the above-mentioned Internet of Things device reporting control method embodiment.

[0095] Corresponding to the method of FIG1 , the embodiment of the present application further provides an IoT device reporting control device, the specific structure of which can be referred to FIG11 , including:

[0096] at least one processor 1011;

[0097] at least one memory 1012, configured to store at least one program;

[0098] When the at least one program is executed by the at least one processor, the at least one processor implements the Internet of Things device reporting control method.

[0099] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0100] Corresponding to the method of Figure 1, an embodiment of the present application also provides a computer-readable storage medium, which stores processor-executable instructions. When the processor executes the processor, the processor-executable instructions are used to execute the IoT device reporting control method.

[0101] The contents of the above-mentioned Internet of Things device reporting control method embodiment are all applicable to the present storage medium embodiment. The functions specifically implemented by the present storage medium embodiment are the same as those of the above-mentioned Internet of Things device reporting control method embodiment, and the beneficial effects achieved are also the same as those achieved by the above-mentioned Internet of Things device reporting control method embodiment.

[0102] In some optional embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the boxes can sometimes be executed in reverse order. In addition, the embodiments presented and described in the flow chart of the present application are provided in an exemplary manner for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operations and logical flows presented herein. Optional embodiments are contemplated in which the order of the various operations is changed and the sub-operations described as a part of a larger operation are performed independently.

[0103] In addition, although the present application is described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in separate physical devices or software modules. It is also understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present application. More specifically, given the properties, functions, and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the module will be understood within the routine skills of an engineer. Therefore, a person skilled in the art can implement the present application as set forth in the claims using ordinary techniques without undue experimentation. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present application, which is determined by the full scope of the appended claims and their equivalents.

[0104] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several programs for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0105] The logic and / or steps represented in a flowchart or otherwise described herein, for example, may be considered as an ordered list of executable programs for implementing the logical functions, and may be embodied in any computer-readable medium for use by, or in conjunction with, a program execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can retrieve and execute a program from a program execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" may be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, a program execution system, apparatus, or device.

[0106] More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic devices), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering, or processing in another suitable manner as necessary, and then stored in a computer memory.

[0107] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable program execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0108] In the above description of this specification, reference to the terms "one embodiment / example," "another embodiment / example," or "certain embodiments / examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples.

[0109] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions, and variations may be made to the embodiments without departing from the principles and intent of the present application, and that the scope of the present application is defined by the claims and their equivalents.

[0110] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the embodiments. Those skilled in the art may make various equivalent modifications or substitutions without violating the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A method for reporting and controlling an Internet of Things device, characterized in that, It includes the following steps: Obtain the current message count value assigned to the current message reported item by item by the Internet of Things device within a unit time period, the first limit value of the built-in limit policy, the remaining release times allowed by the platform for users to exceed the limit, and the maximum limit value of the reported messages; When the current message count value is less than the first limit value, receive and process the current message; When the current message count value is greater than the maximum limit value, discard the current message; When the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining release times are greater than 0, receive and process the current message, and subtract 1 from the total remaining release times; when the remaining release times are less than or equal to 0, discard the current message corresponding to the message count value.

2. The method for reporting and controlling an Internet of Things device according to claim 1, wherein The first limit value is obtained through the following steps: Configure the first limit threshold for the first level of the reported message in a unit time period, the second limit threshold for the second level of the reported message in a unit time period, the first priority weight of the first level, the second priority weight of the second level, the maximum basic permission value set by the platform for the protocol device, and the first basic limit value; Determine the first target limit threshold from the first limit threshold and the second limit threshold according to the first priority weight and the second priority weight; Determine the second basic limit value according to the first basic limit value and the first target limit threshold; When the second basic limit value is greater than the maximum basic permission value, determine the maximum basic limit value as the first limit value; When the second basic limit value is less than the maximum basic permission value, determine the second basic limit value as the first limit value.

3. The method for reporting and controlling an Internet of Things device according to claim 2, wherein, The step of determining the first target limit threshold from the first limit threshold and the second limit threshold according to the first priority weight and the second priority weight specifically includes: When the first priority weight is greater than the second priority weight, determine the first limit threshold as the first target limit threshold; When the first priority weight is less than the second priority weight, determine the second limit threshold as the first target limit threshold.

4. The method for reporting and controlling an Internet of Things device according to claim 2, wherein The step of determining the second basic limit value according to the first basic limit value and the first target limit threshold specifically includes: Add the first basic limit value and the first target limit threshold to obtain a first sum value; Use the first sum value as the second basic limit value.

5. The reporting control method for an Internet of Things device according to claim 1, wherein, The current message count value is obtained through the following method: The current message count value starts incrementing item by item from 1 within each unit time period. After the unit time period ends, the count value is cleared; At the start of the next unit time period, the current message count value starts incrementing item by item again from 1.

6. The method for reporting and controlling an Internet of Things device according to claim 1, wherein The method further includes: When the current unit time period ends, generate a detailed report limit list; the detailed report limit list includes one or more items such as product identification, limit period, limit trigger time point, and limit policy status.

7. The method for reporting and controlling an Internet of Things device according to claim 1, characterized in that, The current messages reported item by item by the Internet of Things devices within a unit time period include: the publish messages reported item by item by the MQTT protocol devices or the notify messages reported item by item by the LwM2M protocol devices.

8. An Internet of Things device reporting control system, characterized in that, Including: An obtaining unit, configured to obtain the current message count value assigned to the current messages reported item by item by the Internet of Things devices within a unit time period, the first limit value of the built-in limit policy, the remaining release times allowed for the platform to allow users to exceed the limit, and the maximum limit value of the reported messages; A first processing unit, configured to receive and process the current message when the current message count value is less than the first limit value; When the current message count value is greater than the maximum limit value, discard the current message; or when the current message count value is greater than the first limit value and less than or equal to the maximum limit value, and the remaining release times are greater than 0, receive and process the current message, and subtract 1 from the total remaining release times; when the remaining release times are less than or equal to 0, discard the current message corresponding to the message count value.

9. An Internet of Things device reporting control device, characterized in that Including: At least one processor; At least one memory, configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements an Internet of Things device reporting control method according to any one of claims 1-7.

10. A computer-readable storage medium storing instructions executable by a processor, characterized in that, The instructions executable by the processor are used to execute an Internet of Things device reporting control method according to any one of claims 1-7 when executed by the processor.

Images