Internet of Things device management method, system, electronic device and storage medium

Abstract

The present application provides an Internet of Things device management method, system, electronic device, and storage medium, which relates to the field of Internet of Things device management technology. The key points of its technical solution are: connecting an Internet of Things device; identifying the identification information of the Internet of Things device; detecting whether the driver file of the Internet of Things device is installed normally; when the driver file is installed normally on the Internet of Things device, backing up the driver file to a first driver library and adding the identification information; or, when the driver file is not installed normally on the Internet of Things device, selecting the corresponding driver file from the first driver library according to the identification information for installation. The method, system, electronic device, and storage medium for Internet of Things device management provided by the present application have the advantage of reducing workload.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things device management, and specifically, to an Internet of Things device management method, system, electronic device and storage medium. Background Art

[0002] With the development of social economy, the use of the Internet of Things is becoming more and more popular. Usually, in an Internet of Things, there are many Internet of Things devices connected. Different types of Internet of Things devices require the installation of different drivers, but the drivers installed for the same type of Internet of Things devices are the same, and there are often multiple Internet of Things devices of the same type. In the existing technology, each time a new device is connected, the corresponding driver installation operation needs to be performed, which makes the operation complicated and tedious and the workload is large.

[0003] Improvements are urgently needed to address the above issues. Summary of the Invention

[0004] The purpose of this application is to provide an Internet of Things device management method, system, electronic device and storage medium, which have the advantage of reducing workload.

[0005] In the first aspect, this application provides an IoT device management method, the technical solution is as follows:

[0006] include:

[0007] Connect IoT devices;

[0008] Identify the identification information of the IoT device;

[0009] Detect whether the driver file of the IoT device is installed normally;

[0010] When the IoT device normally installs the driver file, backing up the driver file to the first driver library and adding the identification information;

[0011] Alternatively, when the IoT device does not have a driver file installed normally, a corresponding driver file is selected from the first driver library for installation according to the identification information.

[0012] By detecting whether the IoT device has installed the driver file normally, if the file is installed normally, the driver file is backed up to the first driver library and the identification information of the identified IoT device is added. When the same IoT device is connected, the identification information of the IoT device can be identified. At this time, if it is detected that the driver is not installed normally for the newly connected IoT device, the driver file with the same identification information will be selected from the first driver library according to the identification information, and then installed. This avoids the need to manually select the driver file for installation every time a new device is connected, thereby having the beneficial effect of reducing workload.

[0013] Furthermore, this application also includes:

[0014] Counting the number of times the same corresponding driver file is continuously selected from the first driver library for installation according to the identification information;

[0015] When the count exceeds a first preset value, continuously selecting the same corresponding driver file from the first driver library for installation is stopped.

[0016] Furthermore, this application also includes:

[0017] Detecting whether the IoT device operates normally after the driver file is properly installed;

[0018] When the IoT device can operate normally after the driver file is normally installed, backing up the driver file to a second driver library and adding the identification information;

[0019] Alternatively, when the IoT device cannot operate normally after the driver file is normally installed, a corresponding driver file is selected from the second driver library for installation according to the identification information.

[0020] Furthermore, this application also includes:

[0021] Counting the number of times the same corresponding driver file is continuously selected from the second driver library for installation according to the identification information;

[0022] When the count exceeds a second preset value, continuously selecting the same corresponding driver file from the second driver library for installation is stopped.

[0023] Furthermore, this application includes:

[0024] Get the delete command;

[0025] The driver file is deleted from the first driver library according to the deletion instruction.

[0026] Furthermore, this application also includes:

[0027] Get classification instructions;

[0028] The Internet of Things devices are classified according to the classification instruction.

[0029] Furthermore, this application also includes:

[0030] Get operation instructions;

[0031] Perform batch operations on the IoT devices of different categories according to the operation instructions;

[0032] The step of performing batch operations on the IoT devices of different categories according to the operation instructions includes:

[0033] Obtaining operation verification instructions for the IoT devices of different categories;

[0034] When the operation verification instruction is a true instruction, batch operations are performed on the IoT devices of different categories.

[0035] In a second aspect, the present application also provides an Internet of Things device management system, comprising:

[0036] Device access module, used to connect IoT devices;

[0037] An information identification module, used to identify the identification information of the IoT device;

[0038] A detection module, used to detect whether the driver file of the IoT device is installed normally;

[0039] An installation module, configured to back up the driver file to the first driver library and add the identification information when the driver file is normally installed on the IoT device;

[0040] Alternatively, when the IoT device does not have a driver file installed normally, a corresponding driver file is selected from the first driver library for installation according to the identification information.

[0041] In a third aspect, the present application further provides an electronic device comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the above method are executed.

[0042] In a fourth aspect, the present application further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method are executed.

[0043] From the above, it can be seen that the present application provides an Internet of Things device management method, system, electronic device and storage medium, which detects whether the Internet of Things device has installed the driver file normally. If the file is installed normally, the driver file is backed up to the first driver library and the identification information of the identified Internet of Things device is added. When the same Internet of Things device is connected, the identification information of the Internet of Things device can be identified. At this time, if it is detected that the newly connected Internet of Things device has not installed the driver normally, the driver file with the same identification information will be selected from the first driver library according to the identification information, and then installed. This avoids the need to manually select the driver file for installation every time a new device is connected, thereby having the beneficial effect of reducing workload. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is a flowchart of a method for managing IoT devices provided in this application.

[0045] Figure 2 This is a schematic diagram of the structure of an Internet of Things device management system provided in this application.

[0046] Figure 3 This is a schematic diagram of the structure of an electronic device provided in this application.

[0047] In the figure: 210, device access module; 220, information identification module; 230, detection module; 240, installation module; 310, processor; 320, memory. DETAILED DESCRIPTION

[0048] The technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. The components of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of this application.

[0049] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and should not be understood as indicating or implying relative importance.

[0050] In an IoT, a large number of IoT devices are usually connected, such as various types of gateways, TVs, air conditioners, air purifiers, etc. In this process, some devices may not only have one, but may be connected to multiple devices, such as connecting the same air conditioner or other IoT devices in different rooms. In traditional existing technologies, after connecting IoT devices, some IoT devices require manual installation of corresponding driver files. If multiple identical IoT devices are connected, multiple corresponding driver files need to be installed, which will lead to cumbersome operations and a large workload.

[0051] For this, please refer to Figure 1 , this application provides an IoT device management method, the technical solution specifically includes:

[0052] S110, connect to IoT devices;

[0053] S120: Identify identification information of the IoT device;

[0054] The identification information may be a product model of the IoT device;

[0055] S130, detecting whether the driver file of the IoT device is installed normally;

[0056] S140. When the IoT device normally installs the driver file, back up the driver file to the first driver library and add identification information;

[0057] Alternatively, when the IoT device does not have a driver file installed normally, a corresponding driver file is selected from the first driver library according to the identification information for installation.

[0058] Through the above technical solution, by detecting whether the IoT device has installed the driver file normally, if the driver file is installed normally, the driver file is backed up to the first driver library and the identification information of the identified IoT device is added. When the same IoT device is connected, the identification information of the IoT device can be identified. At this time, if it is detected that the newly connected IoT device has not installed the driver file normally, the driver file with the same identification information will be selected from the first driver library according to the identification information, and then installed. This avoids the need to manually select the driver file for installation every time a new device is connected, thereby having the beneficial effect of reducing workload.

[0059] Furthermore, in some embodiments, the method further comprises:

[0060] Counting the number of times the same corresponding driver file is continuously selected from the first driver library for installation according to the identification information;

[0061] When the count exceeds a first preset value, continuously selecting the same corresponding driver file from the first driver library for installation is stopped.

[0062] When a certain IoT device is connected to the IoT for the first time, the identification information of the IoT device, such as the product model, is first identified. Then, it is detected that the driver file of the IoT device has not been installed normally. At this time, no corresponding driver file in the first driver library is selected for installation. Therefore, it is necessary to manually install the driver file. After the corresponding driver file is installed, it will be detected that the IoT device has successfully installed the driver file. At this time, the installed driver file is backed up to the first driver library. When the same type of IoT device is installed again subsequently, it will be checked whether the driver file is installed normally. When it is detected that the driver file is not installed normally, the driver file of the same type of IoT device that has been backed up before will be selected from the first driver library according to the identification information of the IoT device, and then installed. This can avoid the problem of manual installation every time.

[0063] However, if an error occurs in identifying the identification information, or an error occurs in the driver file backed up in advance, according to the above solution, the corresponding driver file selected from the first driver library may also not be installed normally on the IoT device, and if it cannot be installed normally, it will be installed in a loop. Therefore, in order to avoid the occurrence of endless loop installation, the number of times the same corresponding driver file is continuously selected from the first driver library for installation according to the identification information is counted. When the count exceeds a first preset value, the continuous selection of the same corresponding driver file from the first driver library for installation is stopped, which can effectively avoid the problem of loop installation caused by backup errors or identification errors.

[0064] Furthermore, in some embodiments, the method further comprises:

[0065] Check whether the IoT device runs normally after the driver file is installed normally;

[0066] When the IoT device is able to operate normally after the driver file is installed normally, the driver file is backed up to the second driver library and identification information is added;

[0067] Alternatively, when the IoT device cannot operate normally after the driver file is not installed normally, a corresponding driver file is selected from the second driver library according to the identification information for installation.

[0068] After the IoT device installs the driver file normally, it will back up its driver file. Then, an error may occur during the backup process, or the wrong driver file may be selected from the first driver library for installation due to an error in the recognition of the IoT device's identification information. In the above cases, the IoT device will be installed using an incorrect driver file. However, even if an incorrect driver file is used for installation, it is possible that the driver file is installed normally, but the IoT device may not work properly.

[0069] Therefore, after the IoT device has installed the driver file normally, it is also necessary to detect whether the IoT device operates normally after the driver file is installed normally. If the IoT device can operate normally after the driver file is installed normally, the driver file is backed up to the second driver library and identification information is added. If the IoT device cannot operate normally after the driver file is installed normally, the corresponding driver file is selected from the second driver library according to the identification information for installation. This ensures that the installed driver file can enable the IoT device to operate normally.

[0070] Furthermore, in some embodiments, the method further comprises:

[0071] Counting the number of times the same corresponding driver file is continuously selected from the second driver library for installation according to the identification information;

[0072] When the count exceeds a second preset value, continuously selecting the same corresponding driver file from the second driver library for installation is stopped.

[0073] Similarly, when selecting the corresponding driver file from the second driver library for installation, there may be a problem of driver file error. If the driver file error causes the IoT device to still not work properly after installing the corresponding driver file, then the corresponding driver file will be selected from the second driver library for installation in a loop. Therefore, the number of times the same corresponding driver file is continuously selected from the second driver library for installation according to the identification information is counted. When the count exceeds the second preset value, the continuous selection of the same corresponding driver file from the second driver library for installation is stopped, which can effectively avoid the problem of cyclic installation caused by driver file errors.

[0074] Furthermore, in some embodiments, including:

[0075] Get the delete command;

[0076] The driver file is deleted from the first driver library according to the deletion instruction.

[0077] Through the above technical solution, the user can delete the driver files in the first driver library according to the deletion instruction. Usually, the driver library will be set in a memory with a certain capacity. If the storage space of the memory is full, it will be impossible to back up new driver files. Therefore, after the capacity reaches a certain level, the user needs to delete some unimportant driver files from the first driver library through the deletion instruction.

[0078] Furthermore, in the first driver library, the number of times each driver file is used by the above method to be installed in a newly connected IoT device will be displayed. Users can select driver files with fewer uses to delete based on the number of times each driver file is used.

[0079] Furthermore, in some embodiments, the method further comprises:

[0080] Get classification instructions;

[0081] Classify IoT devices according to classification instructions.

[0082] Through the above technical solution, IoT devices are classified through classification instructions to facilitate unified management. Usually, there are many IoT devices connected to an IoT. If they are not classified, it will be difficult for users to identify each IoT device.

[0083] Taking a home as an example, the IoT devices in each room can be classified, that is, classified into Room 1, Room 2, Room 3, etc. Each room classification includes the connected IoT devices, which makes it easier to manage the IoT devices in each room and confirm the usage status of the IoT devices in each room.

[0084] In addition, IoT devices can also be classified according to their types, for example, they can be classified according to air conditioners, televisions, air purifiers, etc. Each category includes all IoT devices of that type connected to the Internet of Things, so that IoT devices of the same type can be quickly controlled.

[0085] Furthermore, in some embodiments, the method further comprises:

[0086] Get operation instructions;

[0087] Perform batch operations on IoT devices of different categories according to operation instructions;

[0088] The steps for performing batch operations on IoT devices of different categories according to the operation instructions include:

[0089] Obtain operational verification instructions for different categories of IoT devices;

[0090] When the operation verification instruction is a real instruction, batch operations are performed on IoT devices of different categories.

[0091] Through the above technical solution, batch operations can be performed on the classified IoT devices. For example, taking the above-mentioned family as an example, the IoT devices in each room can be classified, that is, classified into Room 1, Room 2, Room 3, etc. Each room classification includes the connected IoT devices, and batch operations can be performed on each room. For example, all IoT devices in Room 1 can be directly controlled to start up, or all IoT devices in Room 1 can be directly controlled to shut down.

[0092] In addition, different operation verification instructions, i.e., passwords, can be set for different categories. When performing the same batch operation on all IoT devices under each category, it is necessary to enter the operation verification instruction and then verify the operation verification instruction. If the operation verification instruction is correct, the operation can be performed according to the operation instruction. Different operation verification instructions can be set separately for each different category.

[0093] Secondly, refer to Figure 2 , this application also provides an Internet of Things device management system, including:

[0094] Device access module 210, used to connect to IoT devices;

[0095] An information identification module 220 is used to identify identification information of an IoT device;

[0096] The detection module 230 is used to detect whether the driver file of the IoT device is installed normally;

[0097] The installation module 240 is used to back up the driver file to the first driver library and add identification information when the IoT device normally installs the driver file;

[0098] Alternatively, when the IoT device does not have a driver file installed normally, a corresponding driver file is selected from the first driver library according to the identification information for installation.

[0099] Through the above technical solution, by detecting whether the IoT device has installed the driver file normally, if the file is installed normally, the driver file is backed up to the first driver library and the identification information of the identified IoT device is added. When the same IoT device is connected, the identification information of the IoT device can be identified. At this time, if it is detected that the driver is not installed normally for the newly connected IoT device, the driver file with the same identification information will be selected from the first driver library according to the identification information, and then installed. This avoids the need to manually select the driver file for installation every time a new device is connected, thereby having the beneficial effect of reducing workload.

[0100] Thirdly, refer to Figure 3 The present application also provides an electronic device, including a processor 310 and a memory 320, wherein the memory 320 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 310, the steps in the above method are executed.

[0101] Through the above technical solution, the processor 310 and the memory 320 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanisms (not marked). The memory 320 stores a computer program executable by the processor 310. When the electronic device is running, the processor 310 executes the computer program to execute the method in any optional implementation method of the above embodiment to achieve the following functions: connecting to the Internet of Things device; identifying the identification information of the Internet of Things device; detecting whether the Internet of Things device has installed the driver file normally; when the Internet of Things device has installed the driver file normally, backing up the driver file to the first driver library and adding identification information; or, when the Internet of Things device has not installed the driver file normally, selecting the corresponding driver file from the first driver library according to the identification information for installation.

[0102] In a fourth aspect, the present application also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method are executed.

[0103] Through the above technical solution, when the computer program is executed by the processor, the method in any optional implementation method of the above embodiment is executed to achieve the following functions: connecting to the Internet of Things device; identifying the identification information of the Internet of Things device; detecting whether the driver file is installed normally on the Internet of Things device; when the driver file is installed normally on the Internet of Things device, backing up the driver file to the first driver library and adding identification information; or, when the driver file is not installed normally on the Internet of Things device, selecting the corresponding driver file from the first driver library according to the identification information for installation.

[0104] The storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0105] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0106] In addition, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0107] Furthermore, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0108] The above description is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, various modifications and variations of the present application are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for managing IoT devices, characterized in that: include: Connect IoT devices; Identify identification information of the IoT device; Detect whether the driver file of the IoT device is installed normally; When the IoT device normally installs the driver file, backing up the driver file to the first driver library and adding the identification information; Or, when the IoT device does not have a driver file installed normally, select a corresponding driver file from the first driver library according to the identification information for installation; Detecting whether the IoT device operates normally after the driver file is properly installed; When the IoT device can operate normally after the driver file is normally installed, backing up the driver file to a second driver library and adding the identification information; Alternatively, when the IoT device cannot operate normally after the driver file is normally installed, a corresponding driver file is selected from the second driver library for installation according to the identification information.

2. The method for managing IoT devices according to claim 1, wherein: Also includes: Counting the number of times the same corresponding driver file is continuously selected from the first driver library for installation according to the identification information; When the count exceeds a first preset value, continuously selecting the same corresponding driver file from the first driver library for installation is stopped.

3. The method for managing IoT devices according to claim 1, wherein: Also includes: Counting the number of times the same corresponding driver file is continuously selected from the second driver library for installation according to the identification information; When the count exceeds a second preset value, continuously selecting the same corresponding driver file from the second driver library for installation is stopped.

4. The method for managing IoT devices according to claim 1, wherein: Also includes: Get the delete command; The driver file is deleted from the first driver library according to the deletion instruction.

5. The method for managing IoT devices according to claim 1, wherein: Also includes: Get classification instructions; The Internet of Things devices are classified according to the classification instruction.

6. The method for managing IoT devices according to claim 5, wherein: Also includes: Get operation instructions; Perform batch operations on the IoT devices of different categories according to the operation instructions; The step of performing batch operations on the IoT devices of different categories according to the operation instructions includes: Obtaining operation verification instructions for the IoT devices of different categories; When the operation verification instruction is a true instruction, batch operations are performed on the IoT devices of different categories.

7. An Internet of Things device management system, characterized in that: include: Device access module, used to connect IoT devices; An information identification module, used to identify the identification information of the IoT device; A detection module, used to detect whether the driver file of the IoT device is installed normally; An installation module, configured to back up the driver file to the first driver library and add the identification information when the driver file is normally installed on the IoT device; Or, when the IoT device does not have a driver file installed normally, a corresponding driver file is selected from the first driver library according to the identification information for installation; Detecting whether the IoT device operates normally after the driver file is properly installed; When the IoT device can operate normally after the driver file is normally installed, backing up the driver file to a second driver library and adding the identification information; Alternatively, when the IoT device cannot operate normally after the driver file is normally installed, a corresponding driver file is selected from the second driver library for installation according to the identification information.

8. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the method according to any one of claims 1 to 6 are executed.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are executed.

Images