Internet of Things equipment management method and device, computing equipment and storage medium

Abstract

The invention provides an Internet of Things equipment management method, an Internet of Things equipment management device, computing equipment and a computer readable storage medium. The method is applied to an Internet of Things platform, and comprises the following steps: determining Internet of Things equipment needing to be shut down; calling an SIM card shutdown interface of the Internet of Things equipment; and carrying out shutdown processing on the Internet of Things equipment through the SIM card shutdown interface. According to the method and the device, the connection from the Internet of Things equipment to the Internet of Things platform can be managed at the client, and occurrence of massive connection storms is avoided.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to an Internet of Things device management method, an Internet of Things device management apparatus, a computing device, and a computer-readable storage medium. Background Art

[0002] There are technologies for managing IoT devices connected to IoT platforms in this field. In existing IoT device management technologies, the connection between IoT devices and IoT platforms is usually managed on the server side rather than the client side. As a client, IoT devices do not have the ability to actively disconnect. This results in the IoT device continuing to initiate connection requests to the server side after the IoT platform as the server side freezes the connection of the IoT device, resulting in a massive connection request storm, which greatly affects the normal operation of the IoT platform. Therefore, this field urgently needs a technology that can manage the connection between IoT devices and IoT platforms on the client side to avoid the occurrence of massive connection storms. Summary of the invention

[0003] To this end, the present application is committed to providing an IoT device management method, an IoT device management apparatus, a computing device and a computer-readable storage medium, which can manage the connection of IoT devices to the IoT platform on the client side to avoid the occurrence of massive connection storms.

[0004] On the one hand, the present application provides an IoT device management method, which is applied to an IoT platform, and the method includes: determining an IoT device that needs to be shut down; calling a SIM card shutdown interface of the IoT device; and shutting down the IoT device through the SIM card shutdown interface.

[0005] According to this aspect, the SIM card shutdown interface of the IoT device is called to shut down the IoT device, so that the connection between the IoT device and the IoT platform can be managed from the client. By managing the operator network between the IoT device and the IoT platform, once the IoT device is deactivated, the connection with the IoT platform can be immediately disconnected, and because the operator network has shut down the IoT device, the IoT device can no longer initiate a reconnection request to the IoT platform, thus avoiding the occurrence of a massive reconnection storm.

[0006] In a possible implementation of the present application, before determining the IoT device that needs to be shut down, the method also includes: obtaining abnormal connection information of the IoT device.

[0007] According to this implementation, the IoT devices that need to be shut down are determined based on the abnormal connection information of the IoT devices, which can effectively prevent the IoT devices with abnormal connection behavior from successfully connecting to the IoT platform, thereby preventing further adverse effects. By managing the connection of IoT devices with abnormal connection behavior, it is possible to effectively prevent the normal operation of the IoT platform from being disrupted by abnormal connection behavior, resulting in the security operation of the IoT platform and other IoT devices being affected.

[0008] In a possible implementation of the present application, abnormal connection information of the IoT device is obtained, including: finding that the username and / or password of the IoT device is incorrect; or finding that the certificate of the IoT device is incorrect or expired; or finding that the IoT device does not exist; or finding that the security protocol of the IoT device is too low; or finding that the security encryption suite of the IoT device is illegal; or finding that the connection timeout of the IoT device is too short.

[0009] According to this implementation method, a series of specific behaviors of the IoT device are determined as abnormal connection behaviors, and abnormal connection information is sent to the IoT platform, so that the IoT platform can manage these common and quite destructive abnormal connection behaviors and shut down the IoT device that initiates the abnormal connection, so that the safe and stable operation of the IoT platform is guaranteed.

[0010] In a possible implementation of the present application, abnormal connection information of an IoT device is obtained, including: discovering that the IoT device initiates a connection request during a peak connection period of an IoT platform.

[0011] According to this implementation, the behavior of IoT devices initiating connection requests during the peak connection period is defined as abnormal connection behavior, thereby sending abnormal connection information to the IoT platform, which can prevent IoT devices from frequently initiating connection requests during peak periods, resulting in a large occupation of the IoT platform's connection resources, thereby affecting the smooth operation of the IoT platform. Through such management measures, the timing of IoT devices initiating connection requests to the IoT platform can be controlled, making the connection requests received by the IoT platform more stable and orderly, thereby ensuring the normal connection of various IoT devices.

[0012] In a possible implementation of the present application, the method also includes: calling a SIM card reset interface of the IoT device; and allowing the IoT device to re-initiate a connection request to the IoT platform through the SIM card reset interface.

[0013] According to this implementation, after the shutdown operation is performed through the SIM card shutdown interface, the SIM card restart interface can also be called to restart the IoT device, so that it can re-initiate a connection request to the IoT platform. This can enrich the management measures for IoT devices, not only shutting them down, but also re-initiating them, thereby allowing IoT devices to access shutdown measures when conditions permit and re-initiate a connection request to the IoT platform, making the IoT platform's management of IoT devices more scientific and reasonable.

[0014] In a possible implementation of the present application, before calling the SIM card resetting interface of the IoT device, the method further includes: predicting the traffic trend of the IoT platform and calculating the best time for the IoT device to re-initiate the connection request. Among them, calling the SIM card resetting interface of the IoT device includes: calling the SIM card resetting interface of the IoT device at the best time.

[0015] According to this implementation method, by predicting the traffic trend of the Internet of Things platform, the optimal time for the Internet of Things device to re-initiate a connection request can be calculated, so that the Internet of Things device can initiate a connection request when the traffic is relatively low, thereby avoiding the peak period for initiating connection requests, so that the connection resources or bandwidth resources of the Internet of Things platform can be reasonably used, avoiding congestion of connection requests.

[0016] In a possible implementation of the present application, before calling the SIM card shutdown interface of the Internet of Things device, the method also includes: requesting authorization to access the SIM card shutdown interface of the network operator from the Internet of Things application; and obtaining the authorization certificate sent by the Internet of Things application.

[0017] According to this implementation method, by requesting authorization to access the SIM card shutdown interface from the IoT application and then performing the shutdown operation according to the technical solution of this application after obtaining authorization, it is helpful to implement the IoT device management technology of this application in a legal manner permitted by the network operator, thereby improving the security and legality of the technology of this application, avoiding destructive factors to the management mechanisms of existing IoT devices and operator networks, and ensuring the safe operation of devices and networks.

[0018] On the other hand, the present application provides an Internet of Things device management device, characterized in that the device is used to implement the functions of the Internet of Things platform, and the device includes: a determination module, used to determine the Internet of Things device that needs to be shut down; a calling module, used to call the SIM card shutdown interface of the Internet of Things device; and a shutdown module, used to shut down the Internet of Things device through the SIM card shutdown interface.

[0019] In a possible implementation of the present application, the device further includes: an acquisition module, configured to acquire abnormal connection information of the IoT device.

[0020] In a possible implementation of the present application, the acquisition module is further configured to: discover that the username and / or password of the IoT device is incorrect; or discover that the certificate of the IoT device is incorrect or expired; or discover that the IoT device does not exist; or discover that the security protocol of the IoT device is too low; or discover that the security encryption suite of the IoT device is illegal; or discover that the connection timeout of the IoT device is too short.

[0021] In a possible implementation of the present application, the acquisition module is further configured to: discover that the IoT device initiates a connection request during a peak connection period of the IoT platform.

[0022] In a possible implementation of the present application, the device is further configured to: call the SIM card reset interface of the IoT device; and allow the IoT device to re-initiate a connection request to the IoT platform through the SIM card reset interface.

[0023] In a possible implementation of the present application, the device is further configured to: predict the traffic trend of the IoT platform and calculate the best time for the IoT device to re-initiate a connection request. The device is further configured to: call the SIM card reset interface of the IoT device at the best time.

[0024] In a possible implementation of the present application, the device is further configured to: request authorization from the Internet of Things application to access the SIM card shutdown interface of the network operator; and obtain the authorization certificate sent by the Internet of Things application.

[0025] On the other hand, the present application provides a computing device, which includes a processor and a memory, and the processor is used to execute a computer program stored in the memory to implement the above-mentioned Internet of Things device management method.

[0026] On the other hand, the present application provides a computer-readable storage medium, which stores a computer program, and the computer program is used to execute the above-mentioned Internet of Things device management method.

[0027] On the other hand, the present application provides a computer program product, including program code, which enables a computer to implement the above-mentioned Internet of Things device management method when the computer runs the computer program product.

[0028] Any of the IoT device management devices, computing devices, computer-readable storage media or computer program products provided above are used to execute the IoT device management method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding schemes in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The specific implementation of the present application is described in detail below with reference to the accompanying drawings, wherein:

[0030] Figure 1 A system architecture diagram showing an IoT device management method according to an embodiment of the present application;

[0031] Figure 2a A schematic diagram showing a flow chart of an Internet of Things device management method in a first scenario according to an embodiment of the present application is shown;

[0032] Figure 2b Show according to Figure 2a A schematic diagram of a flow chart of the IoT device management method of an embodiment in a second scenario;

[0033] Figure 2c Show according to Figure 2a A schematic diagram of a flow chart of the IoT device management method of an embodiment in a third scenario;

[0034] Figure 3 A schematic block diagram showing the process of an Internet of Things device management method according to an embodiment of the present application is shown;

[0035] Figure 4 A schematic block diagram showing a process of an Internet of Things device management method according to another embodiment of the present application;

[0036] Figure 5 A schematic diagram showing the structure of an IoT device management device according to an embodiment of the present application is shown;

[0037] Figure 6 A schematic diagram of the structure of a computing device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0038] In order to make those skilled in the art understand the concept and thought of the present application more clearly, the present application is described in detail below in conjunction with specific embodiments. It should be understood that the embodiments provided herein are only a part of all embodiments that the present application may have. After reading the specification of the present application, those skilled in the art have the ability to make improvements, transformations, or replacements to part or all of the following embodiments, and these improvements, transformations, or replacements are also included in the scope of the present application.

[0039] In this document, the terms "one", "an" and other similar words are not intended to indicate that there is only one of the things described, but rather that the relevant description is only for one of the things described, and the things described may have one or more. In this document, the terms "comprises", "includes" and other similar words are intended to indicate logical relationships, and cannot be regarded as indicating spatial structural relationships. For example, "A includes B" is intended to indicate that B logically belongs to A, but does not mean that B is spatially located inside A. In addition, the meanings of the terms "comprises", "includes" and other similar words should be regarded as open, rather than closed. For example, "A includes B" is intended to indicate that B belongs to A, but B does not necessarily constitute the whole of A, and A may also include other elements such as C, D, and E.

[0040] In this document, the terms "first", "second" and other similar words are not intended to imply any order, quantity and importance, but are only used to distinguish different elements. In this document, the terms "embodiment", "present embodiment", "one embodiment" and "an embodiment" do not mean that the relevant description is only applicable to a specific embodiment, but rather that these descriptions may also be applicable to one or more other embodiments. Those skilled in the art should understand that in this document, any description made for a certain embodiment can be replaced, combined, or otherwise combined with the relevant description in one or more other embodiments, and the new embodiment produced by the replacement, combination, or other combination is easily conceivable by those skilled in the art and belongs to the scope of protection of this application.

[0041] In the embodiments of the present application, the Internet of Things may refer to a technology that uses various devices and technologies such as various information sensors, radio frequency identification technology, global positioning systems, infrared sensors, laser scanners, etc. to collect various required information such as sound, light, heat, electricity, mechanics, chemistry, biology, and location of any object or process that needs to be monitored, connected, and interacted with in real time, so as to achieve ubiquitous connection between objects and objects, and between people and objects through various possible network accesses, thereby intelligently identifying, locating, tracking, monitoring, and managing objects.

[0042] In each embodiment of the present application, an IoT device may refer to a physical entity that has the functions of perception, communication, and data processing, can access the IoT, and exchange information with other devices or systems. They achieve intelligent management and efficient operation through interconnection. For example, any terminal that accesses the IoT platform through the IoT protocol for uplink and downlink communication can be called an IoT device. An IoT device can be a terminal device directly connected to the IoT platform, or a gateway that connects to the IoT platform through a proxy sub-device, or a server that accesses the IoT platform through the IoT protocol.

[0043] In each embodiment of the present application, the Internet of Things platform may refer to an integrated software system, which plays a key connection and management role in the Internet of Things ecosystem; the Internet of Things platform can receive and integrate data from numerous Internet of Things devices, and uniformly store and manage these fragmented data; the Internet of Things platform can serve as a device management console to remotely manage Internet of Things devices; the Internet of Things platform can also use data analysis technology to perform in-depth processing on the massive amounts of data collected, and provide users with valuable information by analyzing the correlation and patterns between the data.

[0044] In various embodiments of the present application, IoT device management may refer to the implementation of a series of operations and strategies such as comprehensive and systematic monitoring, configuration, maintenance, optimization, and security assurance of various types of devices in the IoT. For example, IoT device management includes the initial deployment and registration of devices, to real-time monitoring and analysis of operating status, including monitoring of device performance indicators, energy consumption, connection stability, etc., and includes remote configuration and parameter adjustment to ensure that the device can operate efficiently in accordance with predetermined rules and requirements. In some embodiments, IoT device management may refer to the operations or behaviors of the IoT platform to monitor, connect, disconnect, configure, maintain, etc. the IoT devices connected to it.

[0045] In each embodiment of the present application, the connection of an IoT device may refer to an IoT device (such as smart home devices, industrial automation equipment, etc.) being connected to the Internet through an operator network, accessing an IoT platform using an IoT protocol, and maintaining a TCP (Transmission Control Protocol) long connection between the device and the platform so that the device can perform data transmission and remote control.

[0046] In a typical IoT platform architecture service, directly connected IoT devices or gateways are usually connected to the cloud platform server by assigning an IP address (Internet Protocol Address) through a SIM (Subscriber Identity Module) card, and then upload business data and device status information to the cloud platform, which performs visual and transparent device business (data) management and analysis. When the IoT device establishes a link with the IoT platform, the logic is usually to back off and reconnect infinitely until the connection is successful. In the scenario of massive IoT device connection, there are several scenarios where it is necessary to control the online access of devices to prevent the connection storm caused by massive reconnection from affecting the stability of the platform. These scenarios include special business demands of customers to stop IoT device services. These business scenarios include, for example, the manufacturer's customer equipment is in arrears and needs to stop providing equipment services (freezing the device), and the connection retry storm occurs after the equipment rushes to establish a link and is flow controlled. The repeated failure to reconnect the frozen device will cause the normal device to be unable to go online normally due to the platform's link protection capability (connection flow control).

[0047] In some embodiments of the present application, the platform freezes related devices. When the frozen devices are connected to the platform, the platform recognizes the frozen devices and disconnects them. The problem is that this solution will cause the devices to communicate with the platform when connected. The platform will have to bear the performance consumption of connection storms and protocol parsing caused by repeated reconnection of devices, which may affect the normal device link establishment.

[0048] In some embodiments of the present application, the platform freezes related devices, and when the frozen device requests a connection, the device IP of the frozen device is included in the blacklist. The problem is that although the consumption of application layer protocol parsing is reduced, the device still needs to bear the network connection traffic consumption and DoS (Denial of Service) attack behaviors caused by repeated link establishment behaviors.

[0049] In some embodiments of the present application, the platform estimates the future platform connection congestion level through the current and historical network connection conditions, negotiates with the device for the next link establishment time, and the device goes online and reports data at the next time according to the platform negotiated time point. The problem is that although this solution can solve the connection storm and network congestion problems, the mainstream protocol basically does not provide such contract interfaces, and application layer service interface negotiation is required. However, device services may not be adapted to the platform's negotiation logic, which may result in this capability not being universally applicable.

[0050] To this end, in some embodiments of the present application, when devices swarm to establish links in a certain period of time and cause massive connection attacks on the platform, the IoT platform can manage this behavior so that the connections can be effectively dispersed to establish links with the platform at other idle times, avoiding the swarming of links resulting in no normal connections to establish links or process business, thereby causing business impact. When a device is forced to disconnect from the platform due to business needs or when the device is regarded as an attack, the device can be effectively frozen so that it cannot establish a link with the platform to process business. At the same time, it can be avoided that such devices are repeatedly re-established after being frozen by the platform, consuming platform resources, causing a reconnection storm that affects the business of normal devices.

[0051] In some embodiments of the present application, the platform can effectively and reasonably manage device connections by combining the operator's control ability over the network, plus the platform's ability to estimate device connections and detect abnormal connections, and reasonably control the timing of device connections to avoid connection storms, retry storms, and other services that affect normal devices. When a user needs to freeze an overdue or invalid device, the platform can freeze the device normally, and the retry of such devices will not affect the user's normal device connection. When the platform detects that the device has abnormal connection behavior (wrong username and password, wrong or expired certificate, device does not exist, security protocol is too low, security encryption suite is illegal, connection timeout is too short), it needs to be frozen to avoid affecting normal device connections, and the retry of such devices will not affect the user's normal device connection. When the device is swarming and connected, it may be flow controlled. At this time, when the device repeatedly retries to cause a massive connection storm, the platform can manage the massive device connection through network control and future connection traffic prediction to avoid affecting normal business.

[0052] In some embodiments of the present application, the IoT platform obtains the user's authorization to call the operator's shutdown and restart interface through the user's consent, and controls the network access capability of the user's device SIM card by calling the shutdown and restart interface to achieve the purpose of device connection management. When the user needs to freeze the device due to arrears or invalid equipment, the platform calls the shutdown interface to stop the device's SIM card from accessing the Internet, so as to prevent the device from repeatedly reconnecting and causing pressure on the platform's connection concurrency. When the platform detects that the device has abnormal connection behavior (incorrect username and password, wrong or expired certificate, non-existent device, too low security protocol, illegal security encryption suite, too short connection timeout), the platform freezes the device and calls the shutdown interface to stop the device's SIM card from accessing the Internet, so as to prevent the repeated retries of such devices from affecting the normal device connection on the platform. When a large number of devices are connected, they may be flow controlled. If the devices repeatedly retry and cause a massive connection storm, the platform can control the network of such devices by calling the shutdown interface and manage the connections of massive devices. The platform predicts future connection traffic and calls the recovery interface to restore the network of such devices when the traffic is predicted to be idle. Such devices can connect to the platform within a reasonable time through the retry capability, effectively managing the impact of the massive connection storm on the platform and ensuring the normal connection of users.

[0053] Figure 1 A system architecture diagram of an Internet of Things device management method according to an embodiment of the present application is shown.

[0054] like Figure 1As shown, the IoT device may refer to a terminal that accesses the IoT platform through the IoT protocol for uplink and downlink communications. The IoT device may be a terminal device directly connected to the IoT platform, or a gateway that connects the IoT platform to the IoT platform through a proxy sub-device, or a server that accesses the IoT platform through the IoT protocol. The device gateway may refer to a device that has a sub-device management function and directly connects the IoT platform to the sub-device through a proxy sub-device. An operator may refer to a company or institution that provides Internet access services. These companies usually provide broadband services to consumers or enterprises, including fixed network connections, mobile network services, etc. The shutdown interface may refer to a service interface provided by an operator. When the interface is called, the SIM card service is suspended, and the user cannot use the card for network communication services. The restart interface may refer to a service interface provided by an operator. When the interface is called, the SIM card service is restored, and the user can resume using the card for network communication services. In some cases, a SIM card may refer to an IoT SIM card, which is a SIM card specially provided for IoT devices, used to connect the device to the mobile network to ensure that the device can interact with the outside world efficiently. The application side (business system / IoT application) generally refers to an application system built by the user based on his own business, which is used to connect to the IoT platform to control the device and obtain relevant information about the device. The IoT platform can refer to a system platform that receives data collected and reported by devices and opens it to IoT applications. The IoT platform controls the online time of devices by calculating and calling the shutdown and resumption interface provided by the operator, and then the operator's core network handles the shutdown and resumption. Figure 1 In the example, the device gateway may include a data acquisition gateway and a vehicle-mounted gateway, and the sensors may include lane cameras, temperature detectors, etc.; the device gateway, sensors, and directly connected IoT devices all belong to the device side.

[0055] Figure 2a A schematic diagram of the process of an Internet of Things device management method in a first scenario according to an embodiment of the present application is shown.

[0056] like Figure 2a As shown in the figure, in this scenario, the user needs to deactivate the IoT device. The IoT platform obtains authorization from the application side and obtains the permission and credentials to call the operator customer's SIM card shutdown and restart interface. The platform controls the device's online timing by controlling the device's network access capability. The application side customer freezes the device that is in arrears, and the IoT platform shuts down the SIM card shutdown interface of the relevant device and stops the device's network communication capability.

[0057] Figure 2b Show according to Figure 2a A schematic diagram of the flow chart of the IoT device management method of an embodiment in the second scenario.

[0058] like Figure 2bAs shown, in this scenario, the IoT platform will be invalid or the attacking device will be forced to freeze by shutting down. When it is detected that an IoT device cannot successfully establish a link due to abnormal connection (wrong username and password, wrong or expired certificate, non-existent device, too low security protocol, illegal security encryption suite, too short connection timeout), and repeatedly establishes a link, the IoT platform calls the operator's SIM card shutdown interface to block the network, and calls the SIM card recovery interface to restore the network after the IoT device is repaired.

[0059] Figure 2c Show according to Figure 2a A schematic flow chart of the IoT device management method of an embodiment in a third scenario.

[0060] like Figure 2c As shown in the figure, in this scenario, the platform estimates future traffic. When IoT devices are connected in large numbers, it shuts down some devices and restores the network of such devices at a planned reasonable time. The IoT platform counts historical network connection traffic and estimates future connection traffic. When IoT devices are connected in large numbers, the SIM card of the flow-controlled device is shut down. When the network connection is idle, the SIM card of such device is restored to the network. The IoT device reconnects to the IoT platform through the reconnection mechanism. This effectively enhances the stability of the IoT platform and prevents normal business losses caused by connection storms.

[0061] Figure 3 A flow chart of a method for managing an IoT device according to an embodiment of the present application is shown.

[0062] According to this embodiment, the method is applied to an Internet of Things platform, including steps S310 to S330, each of which is described in detail below.

[0063] S310: Determine the IoT devices that need to be shut down.

[0064] In this embodiment, the shutdown of the IoT device may refer to stopping the IoT device's ability to access the Internet or send connection requests, so that it can no longer initiate connection requests to, for example, the IoT platform. In some embodiments, the shutdown of the IoT device may refer to making the IoT device no longer have the function of sending data sensed by the sensor, so that it can no longer perform the normal functions of the IoT device, and is separated from the entire IoT system or application environment, and no longer continues to operate as part of the entire IoT system.

[0065] In this embodiment, the IoT devices that need to be shut down can be determined by calculation or planning to find those IoT devices that no longer need to continue to operate, have malfunctions, owe fees (for example, owe fees to operators), or are of little value. If such IoT devices can continue to initiate connection requests to the IoT platform, they will occupy the connection resources of the IoT platform, reducing the operating efficiency of the entire IoT system. Therefore, IoT devices that need to be shut down can be determined from a large number of IoT devices based on various reasons, and then shut down can be performed on them.

[0066] As an example, before S310, abnormal connection information of the IoT device may also be obtained.

[0067] In this example, before determining the IoT devices that need to be shut down, it is possible to determine which IoT devices or devices have abnormal phenomena when connected to the IoT platform, so as to determine that the devices with abnormal connection phenomena are the IoT devices that need to be shut down. Abnormal connection information of IoT devices can refer to phenomena that indicate that the IoT devices have different connection processes and connection procedures from the normal, legal, and secure ones when connected to the IoT platform, such as connection timeout, illegal connection protocol, etc. In view of these abnormal phenomena, it can be determined that the IoT devices to be connected at this time should not be connected to the IoT platform, otherwise there will be security risks or risks of abnormal operation, so these IoT devices need to be shut down.

[0068] As an example, the specific operation method for obtaining abnormal connection information of an IoT device may be: discovering that the username and / or password of the IoT device is incorrect; or discovering that the certificate of the IoT device is incorrect or expired; or discovering that the IoT device does not exist; or discovering that the security protocol of the IoT device is too low; or discovering that the security encryption suite of the IoT device is illegal; or discovering that the connection timeout of the IoT device is too short.

[0069] In this example, the username and password of the IoT device may refer to, for example, the username and password required for the IoT device to log in to the IoT platform. The certificate of the IoT device may be, for example, a certificate that proves identity and other information that the IoT device needs to provide when logging in to the IoT platform. The IoT device does not exist may refer to the phenomenon that the IoT device initiates a connection request but does not receive feedback from the IoT device during the connection process. The security protocol of the IoT device is too low, which may be that the version of the security protocol used by the IoT device to log in to the IoT platform is too low. The security encryption suite of the IoT device is illegal, which may mean that the security encryption suite required for the IoT device to log in to the IoT platform does not comply with the configuration or settings of the IoT platform. The connection timeout of the IoT device is too short, which may mean that the IoT device is judged to have timed out in a short time when logging in to the IoT platform, thereby initiating a request to reconnect, resulting in too many reconnection requests.

[0070] As an example, a specific operation method for obtaining abnormal connection information of an IoT device may be: discovering that the IoT device initiates a connection request during a peak connection period of the IoT platform.

[0071] In this example, the connection peak period of the IoT platform may refer to the situation where many IoT devices associated with the IoT platform simultaneously initiate connection requests to the IoT platform, resulting in an increase in the computing load of the IoT platform and a large occupation of connection resources. Initiating a connection request during the connection peak period of the IoT platform may refer to the situation where, when an IoT device initiates a connection request, many other IoT devices associated with the IoT platform simultaneously initiate connection requests, resulting in the connection request initiated by the IoT device being difficult to process in a timely manner, and encountering a long wait or freeze. Initiating a connection request during the connection peak period may cause the IoT platform to fail to operate normally. Therefore, it is necessary to manage the timing of IoT devices initiating connection requests to the IoT platform, try to avoid the peak period, and initiate connection requests during off-peak or off-peak periods, so as to ensure the smooth and efficient operation of the IoT platform.

[0072] S320: Call the SIM card shutdown interface of the IoT device.

[0073] In this embodiment, the SIM card shutdown interface may refer to an interface provided by the operator to the user for managing the SIM card shutdown. In some embodiments, the SIM card shutdown interface may be provided to the user or management system for calling via an API (Application Programming Interface), and the user may use a specific programming language and development tool to call this interface by sending an HTTP (Hypertext Transfer Protocol) request, calling a command line tool, or using a dedicated SDK (Software Development Kit). When calling the SIM card shutdown interface of an IoT device, the IoT platform may initiate a shutdown interface call request to the operator, and start executing the call operation after the operator responds to the request.

[0074] S330: Shut down the IoT device through the SIM card shutdown interface.

[0075] In this embodiment, the designated IoT device can be shut down through the SIM card shutdown interface, that is, the Internet access capability of the IoT device into which the SIM card is inserted is stopped through the SIM card shutdown interface, so that it can no longer connect to the IoT platform through the network provided by the operator. In this way, the ability of the IoT device to access the Internet or initiate a connection request is stopped from the client, thereby preventing the IoT device from repeatedly re-initiating a connection request, occupying the connection resources or network bandwidth of the IoT platform, and causing the IoT platform to fail to operate normally and efficiently.

[0076] Figure 4 A flow chart of a method for managing an IoT device according to an embodiment of the present application is shown.

[0077] According to this embodiment, the method is applied to an Internet of Things platform, including steps S410 to S480, each of which is described in detail below.

[0078] S410: Determine the IoT device that needs to be shut down.

[0079] For details about S410, see the above Figure 3 The detailed description of S310 in the embodiment is not repeated here.

[0080] S420: Request authorization to access the SIM card shutdown interface of the network operator from the IoT application program.

[0081] In this embodiment, the IoT platform needs to obtain authorization from the IoT application program in order to access the operator's SIM card shutdown interface. The IoT application program may refer to a software application that is mainly used to connect, manage, and interact with various devices and systems in the IoT to achieve intelligent data collection, processing, and operation. The IoT application program can establish a connection with the IoT device through a variety of communication protocols, can configure and manage the IoT device, collect a large amount of data from each device, and provide users with an intuitive interface to view and operate the IoT device. Through the authorization of the IoT application program, the IoT platform can manage the connection behavior of the IoT device through the SIM card shutdown interface, so that a specific IoT device can be shut down on the client side rather than the server side, avoiding repeated connection requests to the IoT platform.

[0082] S430: Obtain the authorization certificate sent by the IoT application.

[0083] In this embodiment, the authorization credential may refer to a digital credential that can be sent by the IoT application to the IoT platform and can be used to call the SIM card shutdown interface. The IoT platform obtains the authorization credential sent by the IoT application and can use the authorization credential to request the operator to call the SIM card shutdown interface, thereby enabling the IoT platform to manage the connection of a specific SIM card or an IoT device equipped with the SIM card and perform shutdown operations on it.

[0084] S440: Call the SIM card shutdown interface of the IoT device.

[0085] S450: Shut down the IoT device through the SIM card shutdown interface.

[0086] For details on S440 and S450, see the above Figure 3 The detailed description of S320 and S330 in the embodiment is not repeated here.

[0087] S460, predicting the traffic trend of the IoT platform, and calculating the best time for the IoT device to re-initiate a connection request.

[0088] In this embodiment, the traffic trend of the Internet of Things platform may refer to the changing trend of the number of devices accessing the Internet of Things platform or initiating connection requests to the Internet of Things platform. If the traffic trend of the Internet of Things platform is on the rise, it means that more and more Internet of Things devices will request to connect to the Internet of Things platform or send data to the Internet of Things platform. If the traffic trend of the Internet of Things platform is on the decline, it means that fewer and fewer Internet of Things devices will request to connect to the Internet of Things platform or send data to the Internet of Things platform. Predicting the traffic trend of the Internet of Things platform is a calculation or judgment process based on historical data or device connection conditions to determine whether the number of Internet of Things devices associated or connected to the Internet of Things platform will increase or decrease in the future. By predicting the traffic trend of the Internet of Things platform, the best time for the Internet of Things device to re-initiate a connection request can be determined. The best time is usually during the time when the traffic of the Internet of Things platform decreases or a trough occurs.

[0089] S470: At the best time, call the SIM card recovery interface of the IoT device.

[0090] In this embodiment, the SIM card restoration interface may refer to an interface provided by the operator to the user or management program for enabling the IoT device equipped with the SIM card to reconnect to the network provided by the operator (such as the Internet, 5G network, etc.), thereby initiating a connection request to the IoT platform. By calling the SIM card restoration interface of the IoT device, the IoT platform can restore the Internet access capability of a specific IoT device, so that it is able to re-request a connection from the IoT platform. Calling the SIM card restoration interface of the IoT device at the best time can enable the IoT device to re-access the Internet or request a connection during a period of low traffic or trough traffic on the IoT platform, thereby avoiding the IoT device from re-initiating a connection during peak traffic periods, causing congestion on the IoT platform and inability to operate normally.

[0091] S480: Allow the IoT device to re-initiate a connection request to the IoT platform through the SIM card recovery interface.

[0092] In this embodiment, the IoT platform can operate the SIM card recovery interface to enable a specific IoT device to have the ability to re-initiate a connection request to the IoT platform, so that the IoT device can reconnect to the IoT platform after troubleshooting or resuming operation. By giving IoT devices the ability to re-request a connection, IoT devices can be managed flexibly to avoid excluding specific IoT devices from the IoT system, so that once a problem occurs, they cannot reconnect to the IoT platform, which will cause the device resources to be ineffectively utilized, resulting in waste.

[0093] Based on the aforementioned Figure 3 The present application also provides a method embodiment, and provides an Internet of Things device management device, and its structural diagram is as follows Figure 5 The device is used to perform the above Figure 3 The various steps in .

[0094] According to this embodiment, the IoT device management device 500 is used to implement the functions of the IoT platform, and the device includes a determination module 510, a call module 520 and a shutdown module 530. The determination module 510 is used to determine the IoT device that needs to be shut down. The call module 520 is used to call the SIM card shutdown interface of the IoT device. The shutdown module 530 is used to shut down the IoT device through the SIM card shutdown interface.

[0095] It should be noted that Figure 5The IoT device management device 500 provided in the embodiment shown in the figure only uses the division of the above-mentioned functional modules as an example when executing the method. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Figure 3 The IoT device management method embodiments shown belong to the same concept, and their specific implementation processes are detailed in the method embodiments, which will not be repeated here.

[0096] Figure 6 It is a schematic diagram of the hardware structure of a computing device 600 provided in an embodiment of the present application.

[0097] See also Figure 6 The computing device 600 includes a processor 610, a memory 620, a communication interface 630, and a bus 640, wherein the processor 610, the memory 620, and the communication interface 630 are connected to each other via the bus 640. The processor 610, the memory 620, and the communication interface 630 may also be connected in other connection modes besides the bus 640.

[0098] Among them, the memory 620 can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, optical storage, hard disk, etc.

[0099] The processor 610 may be a general-purpose processor, which may be a processor that performs specific steps and / or operations by reading and executing the contents stored in a memory (e.g., the memory 620). For example, the general-purpose processor may be a central processing unit (CPU). The processor 610 may include at least one circuit to perform Figure 3 All or part of the steps of the method for managing an Internet of Things device provided in the illustrated embodiment.

[0100] Among them, the communication interface 630 includes input / output (I / O) interfaces, physical interfaces, and logical interfaces for interconnecting devices within the computing device 600, as well as interfaces for interconnecting the computing device 600 with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, an optical fiber interface, an ATM interface, etc. The communication interface 630 can be connected to an external input device and an output device. For example, the input device can be a microphone or a microphone array for capturing voice input signals; it can be a communication network connector for receiving collected input signals from the cloud or other devices; it can also include, for example, a keyboard, a mouse, etc. The output device can output various information to the outside, including determined distance information, direction information, etc. The output device can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, etc.

[0101] The bus 640 may be any type of communication bus for interconnecting the processor 610 , the memory 620 , and the communication interface 630 , such as a system bus.

[0102] The above devices may be arranged on independent chips, or at least partially or completely on the same chip. Whether to arrange each device independently on different chips or to integrate them on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the specific implementation form of the above devices.

[0103] Figure 6 The computing device 600 shown is merely exemplary. During implementation, the computing device 600 may further include other components, which are not listed one by one herein.

[0104] An embodiment of the present application may also be a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, enables the processor to execute the steps of the IoT device management method according to various embodiments of the present application described above in this specification.

[0105] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is 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 readable storage media include: an electrical connection with one or more wires, a portable 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.

[0106] The concepts, principles and ideas of the present application are described in detail above in conjunction with specific implementation methods (including embodiments and examples). Those skilled in the art should understand that the implementation methods of the present application are more than the several forms given above. After reading the application documents, those skilled in the art can make any possible improvements, replacements and equivalent forms to the steps, methods, devices and components in the above-mentioned implementation methods, and these improvements, replacements and equivalent forms should be deemed to fall within the scope of the present application. The scope of protection of the present application shall be subject only to the claims.

Claims

1. A method for managing IoT devices, characterized in that: The method is applied to an Internet of Things platform, and the method comprises: Identify IoT devices that require downtime; Calling the SIM card shutdown interface of the IoT device; The Internet of Things device is shut down through the SIM card shutdown interface.

2. The method according to claim 1, characterized in that: Before determining the IoT device that needs to be shut down, the method further includes: Obtain abnormal connection information of the IoT device.

3. The method according to claim 2, characterized in that The obtaining of abnormal connection information of the IoT device includes: The username and / or password of the IoT device is found to be incorrect; or It is found that the certificate of the IoT device is wrong or expired; or It is found that the IoT device does not exist; or The security protocol of the IoT device is found to be too low; or The security encryption suite of the IoT device is found to be illegal; or It is found that the connection timeout period of the IoT device is too short.

4. The method according to claim 2, characterized in that The obtaining of abnormal connection information of the IoT device includes: It is found that the IoT device initiates a connection request during a peak connection period of the IoT platform.

5. The method according to claim 4, characterized in that The method further comprises: Calling the SIM card reset interface of the IoT device; Through the SIM card reset interface, the IoT device is allowed to re-initiate a connection request to the IoT platform.

6. The method according to claim 5, characterized in that Before calling the SIM card reset interface of the Internet of Things device, the method further includes: Predicting the traffic trend of the IoT platform and calculating the best time for the IoT device to re-initiate a connection request; The calling of the SIM card reset interface of the IoT device includes: At the optimal time, call the SIM card reset interface of the Internet of Things device.

7. The method according to claim 1, characterized in that Before calling the SIM card shutdown interface of the Internet of Things device, the method further includes: Request authorization from the IoT application to access the network operator's SIM card shutdown interface; Get the authorization credentials sent by the IoT application.

8. An IoT device management device, characterized in that: The device is used to implement the functions of the Internet of Things platform, and the device includes: A determination module, used to determine the IoT devices that need to be shut down; A calling module, used to call the SIM card shutdown interface of the Internet of Things device; The shutdown module is used to shut down the Internet of Things device through the SIM card shutdown interface.

9. A computing device, characterized in that The computing device includes a processor and a memory, and the processor is used to execute a computer program stored in the memory to implement the Internet of Things device management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to execute the Internet of Things device management method according to any one of claims 1 to 7.

Images