TWM615402U - Management system for iot devices - Google Patents

Abstract

A management system for IOT (Internet of Things) devices. The management system includes a communication interface, a storage device and a processor. The storage device stores a group list. The processor is configured to: receive identification information carrying a timestamp from an IOT device through the communication interface; authenticate the IOT device according to the identification information; if the IOT device passes the authentication, determine whether the IOT device belongs to a predetermined group according to the group list; and if the IOT device belongs to the predetermined group, group the IOT device to the predetermined group and assign an authority for accessing the IOT device to a manager of the predetermined group.

Description

Management system for IoT devices

This new creation relates to a management system for Internet of Things devices.

With the advancement of technology, the use of IoT devices has become more and more popular. For example, common IoT devices range from airplanes or cars to industrial computers, TVs, or air conditioners. Generally speaking, before or after leaving the factory, the Internet of Things device needs to control the access rights of its legal administrators. For example, the easiest way is to set the administrator's identity information in the IoT device before the IoT device leaves the factory. After the Internet of Things device leaves the factory, it can be accessed by legal administrators directly based on the preset identity information. However, such a management mechanism must make relevant settings for access permissions before the IoT device leaves the factory, and it lacks flexibility in the use of the IoT device after it leaves the factory.

In addition, after some types of IoT devices are shipped from the factory, the administrator can use the device identification code of the IoT device to request a download certificate from the remote management server to set the management authority. However, in practice, there have been instances of hackers using forged device identification codes to control other people's IoT devices, so there are concerns about security.

The novel creation provides a management system and management method for Internet of Things devices, which can conveniently and safely allocate groups and access permissions to Internet of Things devices.

The embodiment of the present invention provides a management system for Internet of Things devices, which includes a communication interface, a storage device, and a processor. The storage device stores a group list. The processor is coupled to the communication interface and the storage device and is used to: receive time-sensitive identification information from an Internet of Things device via the communication interface; verify the Internet of Things device according to the identification information; If the Internet of Things device passes the verification, determine whether the Internet of Things device belongs to a preset group based on the group list; and if the Internet of Things device belongs to the preset group, add the Internet of Things device to To the preset group and grant the administrator of the preset group the permission to access the Internet of Things device.

The embodiment of the present invention also provides a method for managing the Internet of Things device, which includes: receiving time-sensitive identification information from the Internet of Things device; verifying the Internet of Things device according to the identification information; if the Internet of Things device After verification, determine whether the Internet of Things device belongs to a preset group according to the group list; and if the Internet of Things device belongs to the preset group, add the Internet of Things device to the preset group and The administrator of the preset group is given the authority to access the Internet of Things device.

Based on the above, after receiving time-sensitive identification information from the Internet of Things device via the communication interface, the Internet of Things device can be verified according to the identification information. If the Internet of Things device passes the verification, it can be determined whether the Internet of Things device belongs to a preset group according to the group list. If the Internet of Things device belongs to the preset group, the Internet of Things device can be added to the preset group and the administrator of the preset group is given the permission to access the Internet of Things device. In this way, it is possible to conveniently and safely assign groups and access permissions to IoT devices.

FIG. 1 is a schematic diagram of managing an Internet of Things device according to an embodiment of the creation of the present invention. Fig. 2 is a schematic block diagram of a management system of an Internet of Things device according to an embodiment of the present invention. 1 and 2, the management system 10 can be used to manage the Internet of Things devices 11-13. The management system 10 can be implemented as various types of computer devices such as a desktop computer, a notebook computer, a tablet computer, a server host, or an industrial computer.

The Internet of Things devices 11-13 all have networking and data processing capabilities. It should be noted that, in one embodiment, the IoT devices 11-13 are industrial computers, digital signage, and large displays respectively as examples, but the types of the IoT devices 11-13 are not limited to this. In another embodiment, the Internet of Things devices 11-13 may also include various electronic devices that comply with the Internet of Things specifications, such as a server host, a Kiosk, a sweeping robot, a smart TV, or a smart refrigerator. In addition, the number of Internet of Things devices 11-13 can also be more or less, and the creation of this new type is not limited.

The management system 10 includes a communication interface 21, a storage circuit 22 and a processor 23. The communication interface 21 can be used to communicate with the Internet of Things devices 11-13. For example, the communication interface 21 may include a wired network interface card to support wired communication protocols such as Ethernet and/or a wireless network interface card to support wireless communication protocols such as WiFi.

The storage circuit 22 may include a volatile memory module and a non-volatile memory module. Volatile memory modules can be used to store data volatilely. The non-volatile memory module can be used to store data non-volatile. For example, volatile memory modules may include dynamic random access memory (Dynamic Random Access Memory, DRAM), and non-volatile memory modules may include traditional hard disk drives (Hard Disk Drive, HDD) and/or solid state hard disks. Disk (Solid state drive, SSD).

The processor 23 is coupled to the communication interface 21 and the storage circuit 22. The processor 23 can be used to manage the whole or part of the operation of the system 10. For example, the processor 23 may include a central processing unit (Central Processing Unit, CPU), or other programmable general-purpose or special-purpose microprocessors, digital signal processors (DSP), and programmable Controller, Application Specific Integrated Circuits (ASIC), Programmable Logic Device (PLD) or other similar devices or a combination of these devices.

In one embodiment, the storage circuit 22 stores a group list 201. The group list 201 is used to record information about whether one or more IoT devices have been pre-allocated to a specific group. When any one of the Internet of Things devices 11-13 is connected to the management system 10 via a network (such as the Internet) after being shipped from the factory, the management system 10 may first verify the Internet of Things devices. If the IoT device passes the verification, the management system 10 can determine whether to add the IoT device to a group based on the information in the group list 201.

In an embodiment, the processor 23 may receive time-sensitive identification information from the Internet of Things device 11 via the communication interface 21. The processor 23 can verify the IoT device 11 based on the identification information. If the IoT device 11 passes the verification, the processor 23 can determine whether the IoT device 11 belongs to a certain preset group according to the group list 201. In one embodiment, it is assumed that the group list 201 reflects that the IoT devices 11 have been pre-grouped into the group G(A). Therefore, the processor 23 can add the IoT device 11 to the group G(A) according to the group list 201 and grant the administrator 101 of the group G(A) the permission to access the IoT device 11.

In an embodiment, the processor 23 may receive time-sensitive identification information from the Internet of Things devices 12 and 13 via the communication interface 21, respectively. The processor 23 can verify the IoT devices 12 and 13 based on the identification information. If both the IoT devices 12 and 13 pass the verification, the processor 23 can determine whether the IoT devices 12 and 13 belong to one or more preset groups according to the group list 201. In one embodiment, it is assumed that the group list 201 reflects that the IoT devices 12 and 13 have been pre-grouped into the group G(B). Therefore, the processor 23 can add the IoT devices 12 and 13 to the group G(B) according to the group list 201 and grant the administrator 102 of the group G(B) the permission to access the IoT devices 12 and 13.

It should be noted that in the foregoing embodiment, the administrator 101 is not given the authority to access the IoT devices belonging to the group G(B). Therefore, the administrator 101 can only access the Internet of Things devices (such as the Internet of Things device 11) belonging to the group G (A), but cannot access the Internet of Things devices (such as the Internet of Things device 12 and the Internet of Things device 12) belonging to the group G (B). 13). Similarly, the administrator 102 is not given the permission to access the IoT devices belonging to the group G(A). Therefore, the administrator 102 can only access the IoT devices belonging to group G(B) (such as IoT devices 12 and 13), but cannot access the IoT devices belonging to group G(A) (such as IoT devices). 11). In the following embodiments, the IoT device 11 will be taken as an example to further illustrate the aforementioned verification and grouping related operations.

In one embodiment, the identification information from the Internet of Things device 11 includes the device identification code of the Internet of Things device 11 and a verification code (also referred to as a first verification code). The device identification code of the Internet of Things device 11 may be a unique identification code unique to the Internet of Things device 11, for example, the serial number of the Internet of Things device 11. In addition, this first verification code is a time-based one-time password.

In an embodiment, the IoT device 11 may encode its own device identification code (such as a serial number) and a time parameter to generate the first verification code. This time parameter can reflect the system time of the IoT device 11 when executing this encoding. In one embodiment, the IoT device 11 can input the device identification code and the time parameter into a Time-based One-Time password (TOTP) algorithm. For example, the TOTP algorithm may include performing a hash operation on the device identification code and the time parameter. The Internet of Things device 11 can generate the first verification code according to the output of the TOTP algorithm. In this way, the generated first verification code can be time-sensitive and can reflect the time parameter. Then, the Internet of Things device 11 can transmit the identification information including the device identification code of the Internet of Things device 11 and the first verification code to the management system 10.

In one embodiment, after receiving the identification information including the device identification code of the IoT device 11 and the first verification code, the processor 23 of the management system 10 may generate another verification code (also referred to as the device identification code) according to the device identification code. The second verification code). For example, the second verification code is also a time-based one-time password. For example, the processor 23 may use the same TOTP algorithm as the Internet of Things device 11 to encode the received device identification code and a time parameter to generate the second verification code. This time parameter can reflect the system time when the processor 23 is executing this encoding. Then, the processor 23 may compare the first verification code with the second verification code. If the first verification code is consistent with the second verification code (for example, the same), the processor 23 may determine that the IoT device 11 is verified. Conversely, if the first verification code and the second verification code are inconsistent (for example, they are not the same), the processor 23 may determine that the IoT device 11 has not passed the verification.

In one embodiment, if the IoT device 11 passes the verification, the processor 23 may send a piece of authentication information to the IoT device 11 via the communication interface 21. Thereafter, this certification information can be used to indicate that the IoT device 11 has been certified.

In one embodiment, after determining that the IoT device 11 is verified, the processor 23 may query the group list 201 according to the device identification code. Then, the processor 23 can determine whether the Internet of Things device 11 belongs to a certain preset group according to the query result. For example, assuming that the corresponding relationship between the device identification code of the IoT device 11 and the group G(A) is recorded in the group list 201, the processor 23 may determine that the IoT device 11 should belong to the group G(A). Therefore, the processor 23 can add the IoT device 11 to the group G(A) and grant the administrator 101 of the group G(A) the right to access the IoT device 11.

In one embodiment, if the IoT device 11 fails the verification, it means that the device identification code of the IoT device 11 may be stolen. For example, a malicious user such as a hacker may be trying to return an IoT device 11 owned by another person to a group designated by the hacker. At this time, the processor 23 can determine that the Internet of Things device 11 is an illegal device and does not perform grouping on the Internet of Things device 11 to prevent hackers from obtaining access rights to the Internet of Things device 11.

In one embodiment, if the corresponding relationship between the device identification code of the IoT device 11 and any group is not recorded in the group list 201, the processor 23 may temporarily add the IoT device 11 to a system group G( S), to wait for return (ie grouping).

Fig. 3 is a schematic diagram of grouping IoT devices belonging to a system group according to an embodiment of the present invention. 2 and 3, in one embodiment, it is assumed that the IoT device 31 has been added to the system group G(S).

At a certain point in time, the user 301 can operate the Internet of Things device 31 to trigger the Internet of Things device 31 to send a pairing request to the management system 10. According to the pairing request, the processor 23 can transmit the pairing information (also referred to as the first pairing information) to the IoT device 31 via the communication interface 21. For example, the first pairing information may include an authentication code composed of multiple letters and/or numbers. Then, within a valid time range (for example, 10 minutes) of the first pairing information, the processor 23 can receive another pairing information (also referred to as second pairing information) from a communication device 32 via the communication interface 21. The processor 23 can compare the first pairing information with the second pairing information. If the first pairing information is consistent with the second pairing information (for example, the same), the processor 23 can add the IoT device 31 to the user group G(C) designated by the communication device 32 (or the user 301). At the same time, the administrator of the user group G(C) (for example, the user 301) can be given the authority to access the Internet of Things device 31.

In an embodiment, the first pairing information from the management system 10 may be presented on the display of the IoT device 31. For example, assuming that the first pairing information includes 6 numbers used as authentication codes, the display of the Internet of Things device 31 can present these 6 numbers. In one embodiment, the user 301 can view these 6 numbers (i.e. the first pairing information) via the display of the IoT device 31 and within a valid time range (for example, 10 minutes) via the input interface of the communication device 32 ( For example, a mouse, a keyboard and/or a touchpad) input these 6 numbers (ie, the second pairing information). According to the input of the user 301, the communication device 32 can transmit the verification code (ie, the second pairing information) containing these 6 digits to the management system 10.

In one embodiment, if the first pairing information is consistent with the second pairing information received within the valid time range (for example, the verification code displayed on the display of the Internet of Things device 31 is the same as the verification code entered by the user 301 via the communication device 32 Exactly the same), which means that the user 301 has a high probability of actually being the owner of the IoT device 31 and the communication device 32. Therefore, the IoT device 31 can be added (or updated) to the user group G(C) designated by the communication device 32 (or the user 301) for the user 301 to access.

In one embodiment, if the second pairing information is not received within the valid time range, or the first pairing information is inconsistent with the received second pairing information (for example, the verification code displayed on the display of the Internet of Things device 31 and The verification code entered by the user 301 via the communication device 32 is not exactly the same), indicating that a malicious user such as a hacker may be trying to return an IoT device 31 owned by another person to the group designated by the hacker. At this time, the processor 23 may not perform grouping of the Internet of Things device 31 to prevent hackers from obtaining access rights to the Internet of Things device 31.

In one embodiment, after determining that the first pairing information is consistent with the second pairing information, the processor 23 may send an interactive verification request to the communication device 32 via the communication interface 21 and send the verification action information corresponding to the interactive verification request to IoT device 31. Within a valid time range (for example, 10 minutes) of the interactive verification request, the processor 23 can receive user behavior information from the communication device 32 via the communication interface 21. The user behavior information may reflect the operation behavior of the user (for example, the user 301) on the communication device 32. Then, the processor 23 can add 31 IoT devices to the user group G(C) designated by the communication device 32 (or the user 301) according to the user behavior information.

In one embodiment, the Internet of Things device 31 may present an interactive guidance message on the display of the Internet of Things device 31 according to the verification action information, so as to instruct the user 301 to operate the communication device 32 according to the interactive guidance information. For example, the interactive guidance message may include marking some of the 6 digits of the verification code displayed on the screen or similar related messages with guidance for interactive verification actions. For example, the interactive guidance message may include a graphical interactive guidance message.

In one embodiment, the interactive guidance message may be presented on the display of the Internet of Things device 31 according to a preset operation behavior of the user 301 on the Internet of Things device 31. For example, after the Internet of Things device 31 receives the verification action information, the Internet of Things device 31 may temporarily not present this interactive guidance message. The input interface (e.g., mouse, keyboard and/or touchpad) of the IoT device 31 is used to detect the user's preset operation behavior (e.g., the user controls the cursor in the display to slide across the screen, including the aforementioned 6 After the digital verification code), in response to the preset operation behavior, the Internet of Things device 31 can present the interactive guidance message on the display of the Internet of Things device 31.

FIG. 8 is a schematic diagram of presenting interactive guidance messages according to an embodiment of the creation of the present invention. Referring to FIG. 8, in one embodiment, after the user controls the cursor on the display of the Internet of Things device 31 to slide over the verification code containing the aforementioned 6 digits in the screen 81, the interactive guidance message 801 may be displayed on the screen 81 . The interactive guide message 801 can mark the specific number in the verification code. Take marking the second, fourth and fifth digits of the verification code as an example. This interactive guide message 801 can change the background color of the second, fourth and fifth digits in the verification code .

In one embodiment, the user 301 can operate the input interface of the communication device 32 according to the interactive guidance message displayed on the IoT device 31 within the valid time range (for example, 10 minutes) corresponding to the interactive verification request ( For example, a mouse, keyboard, and/or touchpad) perform corresponding operation behaviors (for example, "click the second, fourth, and fifth digits of the 6 digits of the entered verification code"). Then, the communication device 32 can transmit the user behavior information reflecting this operation behavior to the management system 10.

In one embodiment, within the effective time range (for example, 10 minutes) corresponding to the interactive verification request, if the user behavior reflected by the user behavior information from the communication device 32 is the same as the user behavior required by the interactive verification request Consistent, it means that the user 301 has a high probability that it is indeed the owner of the IoT device 31. Therefore, the IoT device 31 can be added to the user group G(C) designated by the communication device 32 (or the user 301) for the user 301 to access.

In an embodiment, if the user behavior information is not received within the effective time range (for example, 10 minutes) corresponding to the interactive verification request, or the user behavior reflected by the received user behavior information is consistent with the interactive verification The user behavior indicated by the request is inconsistent, which means that a malicious user such as a hacker may try to pass the previous verification mechanism of the pairing information through a specific method (for example, by a malicious program installed in the IoT device 31). At this time, the processor 23 may not perform grouping of the Internet of Things device 31 to prevent hackers from obtaining access rights to the Internet of Things device 31.

In other words, in one embodiment, when the user 301 tries to add the IoT device 31 that currently belongs to the system group G(S) to the specific user group G(C), the management system 10 can perform the dual operation on the user 301 verify. For example, the operation of comparing the first pairing information with the second pairing information belongs to the first stage verification in two-step verification, and the user behavior reflected by the user behavior information is compared with the user behavior requested by the interactive verification request It belongs to the second stage of two-step verification. Only when the user 301 passes the two-step verification, the processor 23 will add the IoT device 31 to the user group G(C) designated by the user 301. In this way, malicious users such as hackers can be effectively prevented from gaining access rights to IoT devices in the system group G(S) that have not yet returned to their homes.

In one embodiment, after the IoT device is shipped from the factory, an agent can be installed in the IoT device. Thereafter, the agent can automatically perform operations such as sending the time-sensitive identification information, sending a pairing request, receiving and presenting the first pairing information, and receiving an interactive verification request, etc., so as to cooperate with the management system 10 for the Internet of Things device Perform verification and return (ie grouping).

Fig. 4 is a flowchart of a method for managing an Internet of Things device according to an embodiment of the creation of the present invention. Referring to FIG. 4, in step S401, time-sensitive identification information is received from the Internet of Things device. In step S402, the IoT device is verified according to the identification information. In step S403, it is determined whether the Internet of Things device passes the verification. If the Internet of Things device fails the verification, in step S404, it is determined that the Internet of Things device is an illegal device, and the Internet of Things device is not homed (ie, grouped).

If the Internet of Things device passes the verification, in step S405, it is determined whether the Internet of Things device belongs to a preset group according to the group list. If the Internet of Things device belongs to a certain preset group, in step S406, the Internet of Things device is added to the preset group and the administrator of the preset group is given access to the Internet of Things Device permissions. In addition, if the Internet of Things device does not belong to any preset group, in step S407, the Internet of Things device is added to the system group to wait for return (ie, grouping).

FIG. 5 is a schematic diagram of a sequence diagram of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. 5, in step S501, the Internet of Things device 51 can read the device identification code SN from its internal storage space. The Internet of Things device 51 may be any one of the Internet of Things devices 11 to 13 in FIG. 1. In step S502, the IoT device 51 can generate the verification code AN(0) (ie, the first verification code) according to the device identification code SN and the time parameter T(0). The time parameter T(0) can reflect the current system time of the IoT device 51. In step S503, the IoT device 51 may transmit the device identification code SN and the verification code AN(0) to the management system 10. In step S504, the management system 10 can generate the verification code AN(1) (ie, the second verification code) according to the device identification code SN and the time parameter T(1). The time parameter T(1) can reflect the current system time at the end of the management system 10. In step S505, the management system 10 can compare the verification codes AN(0) with AN(1). If the verification code AN(0) and AN(1) are the same (for example, the same), in step S506, the management system 10 may transmit the authentication information CT indicating that the Internet of Things device 51 has passed the verification to the Internet of Things device 51. However, in one embodiment, if the verification codes AN(0) and AN(1) are not identical (for example, they are not the same), step S506 may not be executed.

In addition, after determining that the IoT device 51 passes the verification, in step S507, the management system 10 can query the group list (for example, the group list 201 in FIG. 2) according to the device identification code SN. In step S508, the management system 10 may add the Internet of Things device 51 to a predetermined group according to the query result. However, in one embodiment, if the grouping information related to the device identification code SN (or the Internet of Things device 51) is not recorded in the group list, step S508 may not be executed.

FIG. 6 is a schematic diagram of a time sequence of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. Please refer to FIG. 6, in step S601, the IoT device 51 may trigger a pairing procedure. In step S602, in response to the pairing procedure, the IoT device 51 may transmit a pairing request to the management system 10. In step S603, in response to the pairing request, the management system 10 may generate pairing information PI(1) (ie, first pairing information). In step S604, the management system 10 may transmit the pairing information PI(1) to the IoT device 51. At the same time, in step S605, the management system 10 may start a timer.

On the other hand, after receiving the pairing information PI(1), in step S606, the IoT device 51 can present the pairing information PI(1) via the display. In step S607, the communication device 61 can transmit the pairing information PI(2) (ie, the second pairing information) to the management system 10. For example, the communication device 61 may be the communication device 32 of FIG. 3. If the management system 10 receives the pairing information PI(2) within the valid time range of the pairing information PI(1), in step S608, the management system 10 can compare the pairing information PI(1) and PI(2). If the pairing information PI(1) and PI(2) are the same (for example, the same), in step S609, the management system 10 can add the IoT device 51 to the user group designated by the communication device 61 (or its user). However, in one embodiment, if the management system 10 does not receive the pairing information PI(2) within the valid time range of the pairing information PI(1) or the pairing information PI(1) and PI(2) are inconsistent (for example, they are not the same) ), step S609 may not be executed.

FIG. 7 is a time sequence diagram of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. Please refer to FIG. 7, which is continued from the embodiment of FIG. 6. In one embodiment, after determining that the pairing information PI(1) and PI(2) are consistent (for example, the same), step S609 of FIG. 6 may not be performed. Instead, in step S701, the management system 10 may send an interactive verification request to the communication device 32. At the same time, in step S702, the management system 10 may send a verification action information to the Internet of Things device 51. Next, in step S703, the management system 10 may start a timer.

After receiving the verification action information, in step S704, the IoT device 51 may present an interactive guidance message corresponding to the verification action information. In step S705, the communication device 32 may receive a user operation. For example, this user operation may be an operation behavior performed by the user on the communication device 32 according to the interactive guidance message presented by the Internet of Things device 51. In step S706, the communication device 32 may transmit user behavior information reflecting the user operation to the management system 10. If the user behavior information is received within the effective time range of the interactive verification request, and the user behavior reflected by the user behavior information is consistent with the user behavior requested by the interactive verification request, in step S707, the management system 10 The IoT device 51 can be added to a user group designated by the communication device 61 (or its user). However, in one embodiment, if the user behavior information is not received within the effective time range of the interactive verification request or the user behavior reflected by the user behavior information is inconsistent with the user behavior requested by the interactive verification request, then Step S707 may not be executed.

However, each step in FIG. 4 to FIG. 7 has been described in detail as above, and will not be repeated here. It is worth noting that each step in FIG. 4 to FIG. 7 can be implemented as multiple program codes or circuits, and the creation of the present invention is not limited. In addition, the methods in FIGS. 4 to 7 can be used in conjunction with the above embodiments, or can be used alone, and the creation of the present invention is not limited.

In summary, after the identification information with timeliness is used to verify the IoT device, if the grouping information of the IoT device has been recorded in the management system in advance, the IoT device can be automatically assigned (ie grouped) ) To the preset group to complete the fully automated home assignment and access permission assignment. In addition, even if the grouping information of a certain Internet of Things device is not recorded in the management system, the Internet of Things device can be assigned to the user group designated by the user through subsequent single-phase verification or double verification. In this way, it is possible to conveniently and safely assign groups and access permissions to IoT devices.

Although the present disclosure has been disclosed in the above embodiments, it is not intended to limit the present disclosure. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of this disclosure. Therefore, The scope of protection of this disclosure shall be subject to those defined by the attached patent scope.

10: Management system 11~13, 31, 51: IoT devices 101, 102: managers G(A), G(B), G(C), G(S): group 21: Communication interface 22: storage circuit 23: processor 201: Group List 301: User 32, 61: Communication device S401~S407, S501~S508, S601~S609, S701~S705: steps 81: Screen 801: Interactive Guidance Message

FIG. 1 is a schematic diagram of managing an Internet of Things device according to an embodiment of the creation of the present invention. Fig. 2 is a schematic block diagram of a management system of an Internet of Things device according to an embodiment of the present invention. Fig. 3 is a schematic diagram of grouping IoT devices belonging to a system group according to an embodiment of the present invention. Fig. 4 is a flowchart of a method for managing an Internet of Things device according to an embodiment of the creation of the present invention. FIG. 5 is a schematic diagram of a sequence diagram of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. FIG. 6 is a schematic diagram of a time sequence of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. FIG. 7 is a time sequence diagram of the management operation of the Internet of Things device according to an embodiment of the creation of the present invention. FIG. 8 is a schematic diagram of presenting interactive guidance messages according to an embodiment of the creation of the present invention.

10: Management system

11~13: IoT devices

101, 102: managers

G(A), G(B): group

Claims (7)

A management system for Internet of Things devices, including: A communication interface; A storage device to store a group list; and A processor coupled to the communication interface and the storage device and used to: Receiving time-sensitive identification information from an IoT device via the communication interface; Verify the Internet of Things device according to the identification information; If the Internet of Things device passes the verification, determine whether the Internet of Things device belongs to a preset group according to the group list; and If the Internet of Things device belongs to the preset group, the Internet of Things device is added to the preset group and an administrator of the preset group is given the permission to access the Internet of Things device. The management system of the Internet of Things device according to claim 1, wherein the identification information includes a device identification code and a first verification code of the Internet of Things device, and the first verification code belongs to a time-based one-time password. The management system of the Internet of Things device according to claim 2, wherein the first verification code is generated by the Internet of Things device based on encoding the device identification code and a time parameter. The management system of the Internet of Things device according to claim 2, wherein the processor is further used for: Generate a second verification code according to the device identification code; Compare the first verification code with the second verification code; and If the first verification code is consistent with the second verification code, it is determined that the Internet of Things device passes verification. The management system of the Internet of Things device according to claim 1, wherein the processor is further used for: Query the group list according to a device identification code in the identification information; and According to a query result, it is determined whether the Internet of Things device belongs to the preset group. The management system of the Internet of Things device according to claim 1, wherein the processor is further used for: If the Internet of Things device does not belong to the preset group, receive a pairing request from the Internet of Things device through the communication interface; According to the pairing request, transmitting a first pairing information to the Internet of Things device via the communication interface; Within a valid time range of the first pairing information, receiving a second pairing information from a communication device via the communication interface; and If the first pairing information is consistent with the second pairing information, the Internet of Things device is added to a user group designated by the communication device. The management system of the Internet of Things device according to claim 6, wherein the processor is further used for: After determining that the first pairing information is consistent with the second pairing information, send an interactive verification request to the communication device via the communication interface; Receive a user behavior information from the communication device via the communication interface within a valid time range of the interactive verification request; and Add the Internet of Things device to the user group designated by the communication device according to the user behavior information.

Images