TW202231017A - Management system for iot devices and management method thereof. - Google Patents

Abstract

A management system for IOT (Internet of Things) devices and a management method thereof. 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 with timeliness 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 and management method of Internet of things device

The present invention relates to a management technology of an Internet of Things (Internet of Things, IoT) device, and in particular, to a management system and a management method of the Internet of Things device.

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, IoT devices need to control the access rights of their 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 IoT device leaves the factory, it can directly allow legitimate administrators to access it based on the pre-set identity information. However, such a management mechanism must be set 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 a remote management server to set management authority. However, in practice, there have been examples of hackers using fake device IDs to control other people's IoT devices, so there are concerns about security in use.

The present invention provides a management system and a management method for an Internet of Things device, which can conveniently and safely assign groups and access rights to the Internet of Things device.

Embodiments of the present invention provide a management system for an Internet of Things device, 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 used for: receiving identification information with time-sensitive information from the Internet of Things device via the communication interface; verifying the Internet of Things device according to the identification information; If the IoT device passes the verification, determine whether the IoT device belongs to a preset group according to the group list; and if the IoT device belongs to the preset group, add the IoT device to the preset group to the preset group and grant the administrator of the preset group access rights to the IoT device.

An embodiment of the present invention further provides a management method for an Internet of Things device, which includes: receiving identification information with time-sensitive information from the Internet of Things device; verifying the Internet of Things device according to the identification information; if the Internet of Things device passes Verify, determine whether the IoT device belongs to a preset group according to the group list; and if the IoT device belongs to the preset group, add the IoT device to the preset group and assign the IoT device to the preset group The authority of the administrator of the preset group to access the IoT device.

Based on the above, after the time-sensitive identification information is received from the IoT device through the communication interface, the IoT device can be authenticated according to the identification information. If the IoT device passes the verification, it can be determined whether the IoT device belongs to a preset group according to the group list. If the IoT device belongs to the default group, the IoT device may be added to the default group and an administrator of the default group may be given permission to access the IoT device. In this way, groups and access rights can be assigned to the IoT devices conveniently and securely.

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

The IoT devices 11 to 13 all have networking and data processing capabilities. It should be noted that, in one embodiment, the IoT devices 11 to 13 are respectively exemplified by industrial computers, digital signage and large displays, but the types of the IoT devices 11 to 13 are not limited thereto. In another embodiment, the IoT devices 11 to 13 may further include various electronic devices conforming to the IoT specification, such as a server host, a Kiosk, a cleaning robot, a smart TV, or a smart refrigerator. In addition, the number of IoT devices 11 to 13 may be more or less, which is not limited in the present invention.

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 IoT devices 11 to 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 volatile memory modules and non-volatile memory modules. Volatile memory modules can be used to volatilely store data. Non-volatile memory modules can be used to store data non-volatilely. For example, the volatile memory module may include dynamic random access memory (DRAM), and the non-volatile memory module may include conventional hard disk drives (HDDs) and/or solid state drives Disk (Solid state drive, SSD).

The processor 23 is coupled to the communication interface 21 and the storage circuit 22 . The processor 23 may be used to manage all or part of the operation of the system 10 . For example, the processor 23 may include a central processing unit (CPU), or other programmable general-purpose or special-purpose microprocessors, digital signal processors (DSP), programmable Controllers, Application Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs) or other similar devices or combinations of these devices.

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

In one embodiment, the processor 23 may receive the identification information with time-sensitive information from the IoT device 11 via the communication interface 21 . The processor 23 can authenticate the IoT device 11 according to the identification information. If the IoT device 11 passes the verification, the processor 23 can determine whether the IoT device 11 belongs to a predetermined 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) access authority to the IoT device 11 .

In one embodiment, the processor 23 can receive time-sensitive identification information from the IoT devices 12 and 13 respectively through the communication interface 21 . The processor 23 can authenticate the IoT devices 12 and 13 according to 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 both 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) access rights to 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 manager 101 can only access the IoT devices belonging to the group G(A) (eg, the IoT device 11 ), but cannot access the IoT devices belonging to the group G(B) (eg, the IoT device 12 and the IoT device 11 ) 13). Likewise, the administrator 102 is not given the right to access the IoT devices belonging to the group G(A). Therefore, the manager 102 can only access the IoT devices (eg, IoT devices 12 and 13 ) belonging to the group G(B), but cannot access the IoT devices (eg, IoT devices) belonging to the group G(A) 11). In the following embodiments, the IoT device 11 will be used as an example to further describe the above-mentioned details of the operations related to verification and grouping.

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

In one embodiment, the IoT device 11 may encode its own device identification code (eg, serial number) and a time parameter to generate the first verification code. This time parameter may reflect the system time of the IoT device 11 when the encoding is performed. In one embodiment, the IoT device 11 may input the device identification code and the time parameter into a time-based one-time password (TOTP) algorithm. For example, such a TOTP algorithm may include performing a hash operation on the device identification code and the time parameter. The IoT device 11 can generate the first verification code according to the output of the TOTP algorithm. Thereby, the generated first verification code can be time-sensitive and can reflect the time parameter. Then, the IoT device 11 can transmit the identification information including the device identification code of the IoT 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 can generate another verification code (also called a verification code) according to the device identification code. 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 IoT device 11 to encode the received device identification code and a time parameter to generate the second verification code. This time parameter may reflect the system time of the processor 23 when the encoding is performed. 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 (eg, the same), the processor 23 may determine that the IoT device 11 has passed the verification. Conversely, if the first verification code and the second verification code are inconsistent (eg, not identical), the processor 23 may determine that the IoT device 11 fails the verification.

In one embodiment, if the IoT device 11 passes the verification, the processor 23 may transmit an authentication message to the IoT device 11 via the communication interface 21 . Thereafter, the authentication information can be used to indicate that the IoT device 11 has been authenticated.

In one embodiment, after determining that the IoT device 11 has passed the verification, the processor 23 can query the group list 201 according to the device identification code. Then, the processor 23 can determine whether the IoT device 11 belongs to a certain preset group according to the query result. For example, if the group list 201 records the correspondence between the device ID of the IoT device 11 and the group G(A), the processor 23 can 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) access rights to 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 re-home the IoT device 11 owned by another person to a group designated by the hacker. At this time, the processor 23 can determine that the IoT device 11 is an illegal device and does not perform grouping on the IoT device 11 , so as to prevent a hacker from obtaining access rights to the IoT device 11 .

In one embodiment, if the corresponding relationship between the device ID 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 homecoming (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. Referring to FIG. 2 and FIG. 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 may operate the IoT device 31 to trigger the IoT device 31 to transmit 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 consisting of a plurality of letters and/or numbers. Then, within a valid time range (eg, 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 may compare the first pairing information with the second pairing information. If the first pairing information is consistent with the second pairing information (eg, 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) (eg, the user 301 ) can be granted the authority to access the IoT device 31 .

In one 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 the authentication code, the display of the IoT device 31 can present the 6 numbers. In one embodiment, the user 301 can view the 6 numbers (ie, the first pairing information) through the display of the IoT device 31 and within a valid time range (eg, 10 minutes), through the input interface ( Such as mouse, keyboard and/or touchpad) to 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) including the six numbers 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 IoT device 31 and the verification code input by the user 301 via the communication device 32 ) identically), indicating that the user 301 has a high probability that he is indeed 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 IoT device 31 is different from the second pairing information) The verification codes input by the user 301 via the communication device 32 are not identical), indicating that a malicious user such as a hacker may be trying to return the IoT device 31 owned by others to the group designated by the hacker. At this time, the processor 23 may not perform grouping on the IoT device 31 to prevent hackers from obtaining access rights to the IoT device 31 .

In one embodiment, after determining that the first pairing information is consistent with the second pairing information, the processor 23 can send an interactive verification request to the communication device 32 via the communication interface 21 and send verification action information corresponding to the interactive verification request to IoT device 31. Within a valid time range (eg, 10 minutes) of the interactive verification request, the processor 23 may receive a user behavior information from the communication device 32 via the communication interface 21 . The user behavior information can reflect the operation behavior of the user (eg, the user 301 ) on the communication device 32 . Then, the processor 23 can add 31 the IoT device 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 IoT device 31 may present an interactive guide message on the display of the IoT 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 guide message. For example, the interactive guidance message may include marking some of the 6 numbers of the verification code displayed on the screen or a similar message with guidance of 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 IoT device 31 according to a preset operation behavior of the user 301 on the IoT device 31 . For example, after the IoT device 31 receives the verification action information, the IoT device 31 may temporarily not present the interactive guidance message. Detecting the preset operation behavior performed by the user through the input interface (such as a mouse, a keyboard and/or a touchpad) of the IoT device 31 (such as the user controlling the cursor on the display to slide over the screen includes the aforementioned six After the digital verification code), in response to the preset operation behavior, the IoT device 31 can present the interactive guidance message on the display of the IoT device 31 .

FIG. 8 is a schematic diagram of presenting interactive guidance information according to an embodiment of the present invention. Referring to FIG. 8 , in one embodiment, after the user controls the cursor on the display of the IoT device 31 to slide over the verification code containing the aforementioned six numbers in the screen 81 , the interactive guide message 801 can be displayed on the screen 81 . . The interactive guide message 801 can mark a specific number in the verification code. Take marking the 2nd, 4th and 5th numbers in this verification code as an example, this interactive guidance message 801 can change the background color of the 2nd, 4th and 5th numbers in this verification code .

In one embodiment, the user 301 can operate the input interface ( For example, a mouse, a keyboard and/or a touchpad) perform the corresponding operation behavior (for example, "click the 2nd, 4th and 5th digits of the 6 digits of the entered verification code"). Then, the communication device 32 can transmit the user behavior information reflecting the operation behavior to the management system 10 .

In one embodiment, within the valid 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 If they are consistent, it means that the user 301 has a high probability that he 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 one embodiment, if the user behavior information is not received within the valid time range (for example, 10 minutes) corresponding to the interactive verification request, or the user behavior reflected by the received user behavior information is related to the interactive verification The inconsistent user behavior indicated by the request indicates that a malicious user such as a hacker may try to pass the authentication mechanism of the previous pairing information through a specific method (eg, by a malicious program installed in the IoT device 31 ). At this time, the processor 23 may not perform grouping on the IoT device 31 to prevent hackers from obtaining access rights to the IoT 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 a specific user group G(C), the management system 10 can perform a dual operation on the user 301 verify. For example, the operation of comparing the first pairing information with the second pairing information is a first-stage verification in the two-step verification, and comparing the user behavior reflected by the user behavior information and the user behavior requested by the interactive verification request It belongs to the second stage of verification in two-factor verification. Only when the user 301 passes the double authentication, 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 obtaining the access rights of the IoT devices in the system group G(S) that are not currently homed.

In one embodiment, an agent may be installed in the IoT device after the IoT device is shipped from the factory. After that, 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, receiving an interactive verification request, etc., so as to cooperate with the management system 10 on the IoT device. Authenticate and return home (ie, grouping).

FIG. 4 is a flowchart of a management method of an IoT device according to an embodiment of the present invention. Referring to FIG. 4 , in step S401 , time-sensitive identification information is received from the IoT device. In step S402, the IoT device is verified according to the identification information. In step S403, it is determined whether the IoT device has passed 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 it is not returned to its home (ie, grouped).

If the IoT device passes the verification, in step S405, it is determined whether the IoT device belongs to a preset group according to the group list. If the IoT device belongs to a predetermined group, in step S406, add the IoT device to the default group and give the manager of the default group access to the IoT Device permissions. In addition, if the IoT device does not belong to any preset group, in step S407 , the IoT device is added to the system group to wait for homecoming (ie, grouping).

FIG. 5 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. Referring to FIG. 5 , in step S501 , the IoT device 51 can read the device identification code SN from its internal storage space. The IoT device 51 may be any one of the IoT devices 11 to 13 of 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 may 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 on the management system 10 side. In step S505, the management system 10 may compare the verification codes AN(0) and AN(1). If the verification code AN(0) is the same as AN(1) (eg, the same), in step S506 , the management system 10 may transmit the authentication information CT indicating that the IoT device 51 has passed the verification to the IoT device 51 . However, in one embodiment, if the verification codes AN(0) and AN(1) are inconsistent (eg, not identical), step S506 may not be executed.

In addition, after determining that the IoT device 51 has passed the verification, in step S507 , the management system 10 can query the group list (eg, the group list 201 in FIG. 2 ) according to the device identification code SN. In step S508, the management system 10 may add the IoT device 51 to a predetermined group according to the query result. However, in one embodiment, if the group list does not record the grouping information related to the device identification code SN (or the IoT device 51 ), step S508 may not be performed.

FIG. 6 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. Referring 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, the first pairing information). In step S604 , the management system 10 may transmit the pairing information PI( 1 ) to the IoT device 51 . Meanwhile, 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 may present the pairing information PI(1) via the display. In step S607 , the communication device 61 may 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 may compare the pairing information PI(1) and PI(2). If the pairing information PI(1) and PI(2) are identical (eg, 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 (eg, not identical) ), step S609 may not be executed.

FIG. 7 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. Referring to FIG. 7 , following the embodiment of FIG. 6 , in one embodiment, after it is determined that the pairing information PI(1) and PI(2) are consistent (eg, the same), step S609 in FIG. 6 may not be executed. Instead, in step S701 , the management system 10 may transmit an interactive authentication request to the communication device 32 . Meanwhile, in step S702 , the management system 10 may transmit a verification action information to the IoT 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 guide message corresponding to the verification action information. In step S705, the communication device 32 may receive a user operation. For example, the 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 IoT device 51 . In step S706 , the communication device 32 may transmit the user behavior information reflecting the user operation to the management system 10 . If the user behavior information is received within the valid 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 valid 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 should be noted that each step in FIG. 4 to FIG. 7 can be implemented as a plurality of codes or circuits, which is not limited by the present invention. In addition, the methods of FIG. 4 to FIG. 7 can be used in combination with the above embodiments, and can also be used alone, which is not limited in the present invention.

To sum up, after using the time-sensitive identification information 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 returned to the home (ie, grouped). ) to the default group for fully automated homework and access rights assignment. In addition, even if the group information of a certain IoT device is not recorded in the management system, the IoT device can be returned to the user group designated by the user through subsequent single-stage verification or two-step verification. In this way, groups and access rights can be assigned to the IoT devices conveniently and securely.

Although the present disclosure has been disclosed above with examples, it is not intended to limit the present disclosure. Anyone with ordinary knowledge in the technical field may make some changes and modifications without departing from the spirit and scope of the present disclosure. The scope of protection of the present disclosure shall be determined by the scope of the appended patent application.

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 devices S401~S407, S501~S508, S601~S609, S701~S707: Steps 81: Screen 801: Interactive Guidance Message

FIG. 1 is a schematic diagram of managing an IoT device according to an embodiment of the present invention. FIG. 2 is a schematic block diagram of a management system of an IoT 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 management method of an IoT device according to an embodiment of the present invention. FIG. 5 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. FIG. 6 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. FIG. 7 is a sequence diagram illustrating a management operation of an IoT device according to an embodiment of the present invention. FIG. 8 is a schematic diagram of presenting interactive guidance information according to an embodiment of the present invention.

10: Management System

11~13: IoT Devices

101, 102: Managers

G(A),G(B): group

Claims (14)

A management system for an Internet of Things device, comprising: a communication interface; a storage device storing a group list; and a processor coupled to the communication interface and the storage device for: Receive a time-sensitive identification information from an IoT device via the communication interface; Authenticate the IoT device based on the identification information; If the IoT device passes the verification, determining whether the IoT device belongs to a preset group according to the group list; and If the IoT device belongs to the default group, the IoT device is added to the default group and a manager of the default group is given permission to access the IoT device. The management system of an IoT device according to claim 1, wherein the identification information includes a device identification code and a first verification code of the IoT device, and the first verification code is a time-based one-time password. The management system of an IoT device according to claim 2, wherein the first verification code is generated by the IoT device based on encoding the device identification code and a time parameter. The management system of the Internet of Things device as claimed in claim 2, wherein the processor is further configured to: generating a second verification code according to the device identification code; comparing 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 IoT device has passed the verification. The management system of the Internet of Things device as claimed in claim 1, wherein the processor is further configured to: query the group list according to a device identification code in the identification information; and It is determined whether the IoT device belongs to the preset group according to a query result. The management system of the Internet of Things device as claimed in claim 1, wherein the processor is further configured to: If the IoT device does not belong to the default group, receive a pairing request from the IoT device via the communication interface; According to the pairing request, send a first pairing information to the IoT device via the communication interface; receiving a second pairing information from a communication device via the communication interface within a valid time range of the first pairing information; and If the first pairing information is consistent with the second pairing information, the IoT device is added to a user group designated by the communication device. The management system of an Internet of Things device as claimed in claim 6, wherein the processor is further configured to: After determining that the first pairing information is consistent with the second pairing information, send an interactive verification request to the communication device through the communication interface; Receive a user behavior information from the communication device via the communication interface within a valid time range of the interaction verification request; and The Internet of Things device is added to the user group designated by the communication device according to the user behavior information. A management method for an Internet of Things device, comprising: Receive time-sensitive identification information from an IoT device; Authenticate the IoT device based on the identification information; If the IoT device passes the verification, determining whether the IoT device belongs to a preset group according to a group list; and If the IoT device belongs to the default group, the IoT device is added to the default group and a manager of the default group is given permission to access the IoT device. The management method of an IoT device according to claim 8, wherein the identification information includes a device identification code and a first verification code of the IoT device, and the first verification code is a time-based one-time password. The method for managing an IoT device according to claim 9, wherein the first verification code is generated by the IoT device based on encoding the device identification code and a time parameter. The management method of the Internet of Things device according to claim 9, wherein the step of authenticating the Internet of Things device according to the identification information comprises: generating a second verification code according to the device identification code; comparing 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 IoT device has passed the verification. The method for managing an IoT device according to claim 8, wherein the step of judging whether the IoT device belongs to the preset group according to the group list comprises: query the group list according to a device identification code in the identification information; and It is determined whether the IoT device belongs to the preset group according to a query result. The management method for an Internet of Things device as claimed in claim 8, further comprising: If the IoT device does not belong to the preset group, receive a pairing request from the IoT device; sending a first pairing information to the IoT device according to the pairing request; receiving a second pairing information from a communication device within a valid time range of the first pairing information; and If the first pairing information is consistent with the second pairing information, the IoT device is added to a user group designated by the communication device. The method for managing an IoT device according to claim 13, wherein the step of adding the IoT device to the user group designated by the communication device comprises: After determining that the first pairing information is consistent with the second pairing information, sending an interactive verification request to the communication device; Receive a user behavior information from the communication device within a valid time frame of the interaction verification request; and The Internet of Things device is added to the user group designated by the communication device according to the user behavior information.

Images