A domain-based internet of things device authentication management method

Abstract

This invention provides a domain-based IoT device authentication management method in the field of IoT device management technology, comprising: Step S10, a maintenance terminal obtains programming data from an authentication server and sends it to a manufacturer terminal; Step S20, the manufacturer terminal programs the programming data into the IoT device and sends the device information to the authentication server; Step S30, the maintenance terminal sends user information to the authentication server for verification; Step S40, the IoT device performs an interface activation operation to obtain a mid and a key; Step S50, the IoT device performs an interface authentication operation to obtain a token, a din code, and a code validity period; Step S60, the domain management server maintains a device management table and sets user permissions; Step S70, the IoT device accesses the device management table through the token; Step S80, the device management table is updated based on the din code, code validity period, and user permissions. The advantages of this invention are: it greatly improves the security and convenience of IoT device authentication management.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) device management technology, and in particular to a domain-based IoT device authentication management method. Background Technology

[0002] The Internet of Things (IoT) refers to the use of various information sensors, RFID technology, GPS, infrared sensors, laser scanners, and other devices and technologies to collect real-time data on any object or process that needs to be monitored, connected, or interacted with. This data includes information on sound, light, heat, electricity, mechanics, chemistry, biology, location, and other parameters. Through various possible network access methods, it enables ubiquitous connectivity between things and between things and people, achieving intelligent perception, identification, and management of objects and processes. With the rapid development of the IoT, various IoT devices are emerging in large numbers. To fully realize the value of these devices, authentication and management of IoT devices is necessary.

[0003] However, traditional IoT devices only use simple account passwords for authentication. When account passwords are leaked or brute-forced, it will lead to a series of security problems. Furthermore, the lack of differentiated management for IoT devices in different fields (application scenarios) has brought great inconvenience to the management of IoT devices.

[0004] Therefore, how to provide a domain-based IoT device authentication management method to improve the security and convenience of IoT device authentication management has become an urgent technical problem to be solved. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a domain-based IoT device authentication management method to improve the security and convenience of IoT device authentication management.

[0006] This invention is implemented as follows: a domain-based IoT device authentication management method, comprising the following steps:

[0007] Step S10: After the manufacturer terminal and maintenance terminal register with the authentication server, the maintenance terminal obtains the burning data including the root key, validity period, appId and appSecret from the authentication server, and forwards the burning data to the manufacturer terminal.

[0008] Step S20: The manufacturer's terminal burns the data to the IoT device and sends the device information of the IoT device to the authentication server;

[0009] Step S30: The maintenance terminal sends the user information of the IoT device to the authentication server, and the authentication server verifies the received user information.

[0010] Step S40: The IoT device performs an interface activation operation based on the root key, appId, and appSecret to obtain mid and key;

[0011] Step S50: The IoT device performs interface authentication based on the device information and the current timestamp to obtain the token, din code and code validity period, and completes the identity authentication of the IoT device.

[0012] Step S60: The domain management server maintains a device management table and sets the user permissions for the device management table;

[0013] Step S70: The IoT device uses the token to call the access interface of the domain management server, and then accesses the device management table;

[0014] Step S80: Based on the DIN code, code validity period, and user permissions, the IoT device updates the device information and operating data to the device management table according to the domain. The IoT device or the domain management server performs add, delete, modify, query, and filter management on the device management table.

[0015] Furthermore, step S10 specifically includes:

[0016] Step S11: The manufacturer's terminal and the maintenance terminal each send a registration request carrying manufacturer information to the authentication server;

[0017] Step S12: The authentication server forwards the received registration request to the management terminal for review, receives the first review result returned by the management terminal, and forwards it to the manufacturer terminal and the maintenance terminal.

[0018] Step S13: The manufacturer terminal and maintenance terminal parse the first review result. If the first review result is successful registration, proceed to step S14; if the first review result is unsuccessful registration, modify the manufacturer information and proceed to step S11.

[0019] Step S14: The maintenance terminal sends a burning data acquisition request to the authentication server. Based on the received burning data acquisition request, the authentication server sends burning data including the root key, validity period, appId, and appSecret to the maintenance terminal. The maintenance terminal forwards the received burning data to the manufacturer terminal in real time.

[0020] Furthermore, step S20 specifically includes:

[0021] The manufacturer's terminal burns the data to the IoT device, and after the burning is completed, it sends the device information of the IoT device, including at least SN, IMEI, MAC, cardNo, production information and manufacturer information, to the authentication server in real time through the maintenance terminal. The authentication server binds the device information and appId; the maintenance terminal stores the device information.

[0022] The authentication server maintains several device status identifiers. Upon receiving the device information, it updates the device status identifier corresponding to the SN to "inactive".

[0023] Furthermore, step S30 specifically includes:

[0024] Step S31: The maintenance terminal sends the user information of the IoT device to the authentication server based on the SN. The authentication server forwards the received user information to the management terminal for review, receives the second review result returned by the management terminal, and forwards it to the maintenance terminal.

[0025] Step S32: The maintenance terminal parses the second audit result. If the second audit result is successful, the device status identifier is updated to authorized based on the SN, and the process proceeds to step S40. If the second audit result is unsuccessful, the user information is modified, the device status identifier is updated to denied authorization based on the SN, and the process proceeds to step S31.

[0026] Furthermore, step S40 specifically includes:

[0027] Step S41: The IoT device encrypts the SN using the appSecret to obtain the first encrypted data, and sends an interface activation request to the authentication server based on the appId and the first encrypted data.

[0028] Step S42: The authentication server parses the received interface activation request to obtain the appId and the first encrypted data. It uses the appSecret to parse the first encrypted data to obtain the SN. It determines whether the SN matches the appId. If they match, the interface activation is successful. Based on the SN, the device status identifier is updated to activated. The server sends the second encrypted data obtained by encrypting the mid and key using the root key to the IoT device and proceeds to step S43. If not, the interface activation fails and the process ends.

[0029] Step S43: The IoT device uses the root key to decrypt the received second encrypted data to obtain mid and key.

[0030] Furthermore, step S50 specifically includes:

[0031] Step S51: The IoT device uses the key to encrypt the current timestamp to obtain third encrypted data, signs the device information and the third encrypted data to obtain first signature data, and sends the first signature data and the third encrypted data to the authentication server based on the mid.

[0032] Step S52: The authentication server receives the first signature data and the third encrypted data, decrypts the third encrypted data using the key to obtain a timestamp, and verifies the validity period of the timestamp based on the preset authentication period.

[0033] Step S53: The authentication server signs the device information and the third encrypted data to obtain the second signature data, and determines whether the first signature data and the second signature data are consistent. If they are consistent, the interface authentication is successful. Based on the SN, the device status identifier is updated to authenticated, and the token, din code and code validity period are sent to the IoT device to complete the identity authentication of the IoT device. If not, the interface authentication fails and the process ends.

[0034] Furthermore, in step S60, the device management table includes at least the domain, field code, field name, display type, allowed null status, description, sorting, and operation;

[0035] The field name includes at least device information and operating data; the display type can be a checkbox, text box, drop-down list, radio button, time, or switch; the allowed empty state can be either yes or no; the operation is used to edit the domain, field code, field name, display type, allowed empty state, description, and sorting.

[0036] The user permissions include at least the permissions to add, delete, modify, query, and filter, and are bound to the SN of the IoT device.

[0037] Furthermore, step S80 specifically includes:

[0038] The IoT device verifies the validity of the DIN code based on its validity period. If the DIN code expires, it reapplies for a new DIN code and its validity period. If the DIN code is valid, the device information and operating data carrying the DIN code are updated to the device management table based on the domain, according to the user's permissions. The IoT device or the domain management server performs CRUD operations on the device management table based on the user's permissions.

[0039] Furthermore, it also includes:

[0040] Step S90: Perform an authorization extension operation based on the validity period of use.

[0041] Furthermore, it also includes:

[0042] Step S100: The management terminal performs authorization management for IoT devices by stopping and resuming authorization.

[0043] The advantages of this invention are:

[0044] 1. After registering with the authentication server via the manufacturer's terminal and maintenance terminal, the maintenance terminal obtains the burning data, including the root key, validity period, appId, and appSecret, from the authentication server and forwards the burning data to the manufacturer's terminal for burning to the IoT device. It also sends the IoT device's device information to the authentication server. Next, the maintenance terminal sends the IoT device's user information to the authentication server, which verifies the user information. Then, the IoT device performs interface activation based on the root key, appId, and appSecret, obtaining the mid and key. Finally, the IoT device performs interface authentication based on the device information and the current timestamp, obtaining the token, din code, and code validity period, completing the IoT device's identity authentication. During operation, the SN uses appSecret for encryption instead of plaintext transmission. A locally burned root key is used to decrypt the second encrypted data to obtain the mid and key. This process eliminates the need for root key transmission, preventing root key leakage. During interface authentication, a third encrypted data point, obtained by encrypting the timestamp using the key, is added to the original signature data. Authentication fails if the time is incorrect, the validity period has expired, the original signature data is incorrect, or the signature algorithm is incorrect, thus preventing replay attacks. At least five security measures are implemented (1. Registration verification of manufacturer and maintenance terminals; 2. User information verification; 3. Interface activation operation; 4. Interface authentication operation; 5. Usage validity period), ultimately greatly improving the security of IoT device identity authentication.

[0045] 2. By maintaining a device management table on the domain management server, including domain, field code, field name, display type, allowed null state, description, sorting, and operation, IoT devices can access the device management table through a token and update the device information and operating data to the device management table using a valid DIN code. Subsequently, based on user permissions, the relevant data of IoT devices can be added, deleted, modified, queried, and filtered according to the domain, thereby greatly improving the convenience of IoT device authentication management. Attached Figure Description

[0046] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0047] Figure 1 This is a flowchart of a domain-based IoT device authentication management method according to the present invention. Detailed Implementation

[0048] The overall approach of the technical solution in this application is as follows: It enhances the security of IoT device identity authentication by implementing five layers of security measures, including registration verification of manufacturer terminals and maintenance terminals, user information verification, interface activation operation, interface authentication operation, and validity period verification. Furthermore, it improves the convenience of IoT device authentication management by maintaining a device management table on the domain management server, which includes domain, field code, field name, display type, allowed null state, description, sorting, and operation. This allows for the addition, deletion, modification, querying, and filtering of relevant data for IoT devices based on the domain.

[0049] Please refer to Figure 1 As shown, a preferred embodiment of the domain-based IoT device authentication management method of the present invention includes the following steps:

[0050] Step S10: After the manufacturer terminal and maintenance terminal register with the authentication server, the maintenance terminal obtains the burning data including the root key, validity period, appId and appSecret from the authentication server, and forwards the burning data to the manufacturer terminal.

[0051] Step S20: The manufacturer's terminal burns the data to the IoT device and sends the device information of the IoT device to the authentication server;

[0052] Step S30: The maintenance terminal sends the user information of the IoT device to the authentication server, and the authentication server verifies the received user information.

[0053] Step S40: The IoT device performs an interface activation operation based on the root key, appId, and appSecret to obtain mid and key;

[0054] Step S50: The IoT device performs interface authentication based on the device information and the current timestamp to obtain the token, din code and code validity period, and completes the identity authentication of the IoT device.

[0055] Step S60: The domain management server maintains a device management table and sets the user permissions for the device management table; the device management table is used to uniformly manage various IoT devices by domain.

[0056] Step S70: The IoT device uses the token to call the access interface of the domain management server, and then accesses the device management table;

[0057] Step S80: Based on the DIN code, code validity period, and user permissions, the IoT device updates the device information and operating data to the device management table according to the domain. The IoT device or the domain management server performs add, delete, modify, query, and filter management on the device management table.

[0058] Step S10 specifically includes:

[0059] Step S11: The manufacturer's terminal and the maintenance terminal each send a registration request carrying manufacturer information to the authentication server;

[0060] Step S12: The authentication server forwards the received registration request to the management terminal for review, receives the first review result returned by the management terminal and forwards it to the manufacturer terminal and maintenance terminal; the authentication server saves the manufacturer information.

[0061] Step S13: The manufacturer terminal and maintenance terminal parse the first review result. If the first review result is successful registration, proceed to step S14; if the first review result is unsuccessful registration, modify the manufacturer information and proceed to step S11. Only manufacturer terminals and maintenance terminals that have passed registration can perform subsequent operations.

[0062] Step S14: The maintenance terminal sends a data acquisition request to the authentication server. Based on the received data acquisition request, the authentication server sends data acquisition data, including a root key, validity period, appId (vendor ID), and appSecret (vendor key), to the maintenance terminal. The maintenance terminal forwards the received data acquisition data to the vendor terminal in real time. The root key is used for encryption and decryption of the first encrypted data; the validity period is used to limit the usage period of the IoT device. When it expires, an authorization extension operation can be performed, that is, the validity period is reapplied for; the appId and appSecret are used for interface activation operation.

[0063] Step S20 specifically involves:

[0064] The manufacturer's terminal programs the data to the IoT device. After programming, it sends device information, including at least the SN (Serial Number), IMEI (International Mobile Equipment Identity), MAC (Hardware Address), cardNo (Network Card Number), production information, and manufacturer information, to the authentication server in real time via the maintenance terminal. The authentication server stores the received device information and binds it to the appId for subsequent interface activation. The maintenance terminal stores the device information. The production information includes at least the production time, manufacturer, batch number, and box number. The manufacturer information includes at least qualifications, authorization letter, contact address, and contact information. The authentication server maintains several device status identifiers. Upon receiving the device information, it updates the device status identifier corresponding to the SN to "inactive." The device status identifier indicates the current status of the IoT device, and its values ​​include at least "inactive," "activated," "authorization denied," "authorized," and "authenticated."

[0065] Step S30 specifically includes:

[0066] Step S31: The maintenance terminal sends the user information of the IoT device to the authentication server based on the SN. The authentication server forwards the received user information to the management terminal for review, receives the second review result returned by the management terminal and forwards it to the maintenance terminal. The authentication server saves the user information. The user information includes at least the user, contact address, contact information and unified social credit code.

[0067] Step S32: The maintenance terminal parses the second audit result. If the second audit result is successful, the device status identifier is updated to authorized based on the SN, and the process proceeds to step S40. If the second audit result is unsuccessful, the user information is modified, the device status identifier is updated to denied authorization based on the SN, and the process proceeds to step S31.

[0068] Step S40 specifically includes:

[0069] Step S41: The IoT device encrypts the SN using the appSecret to obtain the first encrypted data, and sends an interface activation request to the authentication server based on the appId and the first encrypted data.

[0070] Step S42: The authentication server parses the received interface activation request to obtain the appId and the first encrypted data. It uses the appSecret to parse the first encrypted data to obtain the SN. It determines whether the SN matches the appId. If they match, the interface activation is successful. Based on the SN, the device status identifier is updated to activated. The server sends the second encrypted data obtained by encrypting the mid (device unique identifier) ​​and key using the root key to the IoT device and proceeds to step S43. If not, the interface activation fails and the process ends.

[0071] Step S43: The IoT device uses the root key to decrypt the received second encrypted data to obtain mid and key.

[0072] During the interface activation process, a triple security measure was adopted: encrypting the SN with appSecret, determining whether the SN matches the appId, and decrypting the second encrypted data using the root key.

[0073] Step S50 specifically includes:

[0074] Step S51: The IoT device uses the key to encrypt the current timestamp to obtain third encrypted data, signs the device information and the third encrypted data to obtain first signature data, and sends the first signature data and the third encrypted data to the authentication server based on the mid; the signature algorithm combines the SM3 algorithm and the SM4 algorithm to ensure security.

[0075] Step S52: The authentication server receives the first signature data and the third encrypted data, decrypts the third encrypted data using the key to obtain a timestamp, and verifies the validity period of the timestamp based on the preset authentication period.

[0076] Step S53: The authentication server signs the device information and the third encrypted data to obtain the second signature data, and determines whether the first signature data and the second signature data are consistent. If they are, the interface authentication is successful. Based on the SN, the device status identifier is updated to authenticated, and the token, din code, and code validity period are sent to the IoT device to complete the identity authentication of the IoT device. If not, the interface authentication fails and the process ends.

[0077] The token is used for API calls; the din code is used for data reporting; the code validity period is the validity period of the din code. When the code validity period expires, data cannot be reported using the din code and it needs to be obtained again.

[0078] During the interface authentication process, a triple security measure is adopted, which includes key-to-timestamp encryption, signature, and two signature algorithms.

[0079] In step S60, the device management table includes at least the domain, field code, field name, display type, allowed null status, description, sorting, and operation;

[0080] The field name includes at least device information and operating data; the display type can be a checkbox, text box, drop-down list, radio button, time, or switch; the allowed empty state can be either yes or no; the operation is used to edit the domain, field code, field name, display type, allowed empty state, description, and sorting.

[0081] The user permissions include at least the permissions to add, delete, modify, query, and filter, and are bound to the SN of the IoT device.

[0082] Step S80 specifically involves:

[0083] The IoT device verifies the validity of the DIN code based on its validity period. If the DIN code has expired, it reapplies for a new DIN code and its validity period. If the DIN code is valid, the device information and operational data carrying the DIN code are updated to the device management table based on the user's permissions. The IoT device or the domain management server then manages the device management table by adding, deleting, modifying, querying, and filtering data based on the user's permissions. By managing the validity of the DIN code through its validity period and uploading data based on the DIN code, the device management table is prevented from being updated by unauthorized users, further ensuring security.

[0084] Also includes:

[0085] Step S90: Perform an authorization extension operation based on the validity period of use.

[0086] When the remaining validity period is less than the preset duration, the authentication server sends an expiration warning to the maintenance terminal. Based on the received expiration warning, the maintenance terminal sends an authorization extension application to the authentication server. The authentication server forwards the received authorization extension application to the management terminal for review.

[0087] Also includes:

[0088] Step S100: The management terminal performs authorization management for IoT devices by stopping and resuming authorization.

[0089] The management terminal queries the corresponding device status identifier on the authentication server through the SN, and performs authorization management for IoT devices by updating the device status identifier to stop and restore authorization.

[0090] In summary, the advantages of this invention are as follows:

[0091] 1. After registering with the authentication server via the manufacturer's terminal and maintenance terminal, the maintenance terminal obtains the burning data, including the root key, validity period, appId, and appSecret, from the authentication server and forwards the burning data to the manufacturer's terminal for burning to the IoT device. It also sends the IoT device's device information to the authentication server. Next, the maintenance terminal sends the IoT device's user information to the authentication server, which verifies the user information. Then, the IoT device performs interface activation based on the root key, appId, and appSecret, obtaining the mid and key. Finally, the IoT device performs interface authentication based on the device information and the current timestamp, obtaining the token, din code, and code validity period, completing the IoT device's identity authentication. During operation, the SN uses appSecret for encryption instead of plaintext transmission. A locally burned root key is used to decrypt the second encrypted data to obtain the mid and key. This process eliminates the need for root key transmission, preventing root key leakage. During interface authentication, a third encrypted data point, obtained by encrypting the timestamp using the key, is added to the original signature data. Authentication fails if the time is incorrect, the validity period has expired, the original signature data is incorrect, or the signature algorithm is incorrect, thus preventing replay attacks. At least five security measures are implemented (1. Registration verification of manufacturer and maintenance terminals; 2. User information verification; 3. Interface activation operation; 4. Interface authentication operation; 5. Usage validity period), ultimately greatly improving the security of IoT device identity authentication.

[0092] 2. By maintaining a device management table on the domain management server, including domain, field code, field name, display type, allowed null state, description, sorting, and operation, IoT devices can access the device management table through a token and update the device information and operating data to the device management table using a valid DIN code. Subsequently, based on user permissions, the relevant data of IoT devices can be added, deleted, modified, queried, and filtered according to the domain, thereby greatly improving the convenience of IoT device authentication management.

[0093] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A domain-based IoT device authentication management method, characterized in that: Includes the following steps: Step S10: After the manufacturer terminal and maintenance terminal register with the authentication server, the maintenance terminal obtains the burning data including the root key, validity period, appId and appSecret from the authentication server, and forwards the burning data to the manufacturer terminal. Step S20: The manufacturer's terminal burns the data to the IoT device and sends the device information of the IoT device to the authentication server; Step S30: The maintenance terminal sends the user information of the IoT device to the authentication server, and the authentication server verifies the received user information. Step S40: The IoT device performs an interface activation operation based on the root key, appId, and appSecret to obtain mid and key; Step S50: The IoT device performs interface authentication based on the device information and the current timestamp to obtain the token, din code and code validity period, and completes the identity authentication of the IoT device. Step S60: The domain management server maintains a device management table and sets the user permissions for the device management table; Step S70: The IoT device uses the token to call the access interface of the domain management server, and then accesses the device management table; Step S80: Based on the DIN code, code validity period, and user permissions, the IoT device updates the device information and operating data to the device management table according to the domain. The IoT device or the domain management server performs add, delete, modify, query, and filter management on the device management table.

2. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S10 specifically includes: Step S11: The manufacturer's terminal and the maintenance terminal each send a registration request carrying manufacturer information to the authentication server; Step S12: The authentication server forwards the received registration request to the management terminal for review, receives the first review result returned by the management terminal, and forwards it to the manufacturer terminal and the maintenance terminal. Step S13: The manufacturer terminal and maintenance terminal parse the first review result. If the first review result is successful registration, proceed to step S14; if the first review result is unsuccessful registration, modify the manufacturer information and proceed to step S11. Step S14: The maintenance terminal sends a burning data acquisition request to the authentication server. Based on the received burning data acquisition request, the authentication server sends burning data including the root key, validity period, appId, and appSecret to the maintenance terminal. The maintenance terminal forwards the received burning data to the manufacturer terminal in real time.

3. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S20 specifically involves: The manufacturer's terminal burns the data to the IoT device, and after the burning is completed, it sends the device information of the IoT device, including at least SN, IMEI, MAC, cardNo, production information and manufacturer information, to the authentication server in real time through the maintenance terminal. The authentication server binds the device information and appId. The maintenance terminal stores the device information; The authentication server maintains several device status identifiers. Upon receiving the device information, it updates the device status identifier corresponding to the SN to "inactive".

4. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S30 specifically includes: Step S31: The maintenance terminal sends the user information of the IoT device to the authentication server based on the SN. The authentication server forwards the received user information to the management terminal for review, receives the second review result returned by the management terminal, and forwards it to the maintenance terminal. Step S32: The maintenance terminal parses the second audit result. If the second audit result is successful, the device status identifier is updated to authorized based on the SN, and the process proceeds to step S40. If the second audit result is unsuccessful, the user information is modified, the device status identifier is updated to denied authorization based on the SN, and the process proceeds to step S31.

5. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S40 specifically includes: Step S41: The IoT device encrypts the SN using the appSecret to obtain the first encrypted data, and sends an interface activation request to the authentication server based on the appId and the first encrypted data. Step S42: The authentication server parses the received interface activation request to obtain the appId and the first encrypted data. It uses the appSecret to parse the first encrypted data to obtain the SN. It determines whether the SN matches the appId. If they match, the interface activation is successful. Based on the SN, the device status identifier is updated to activated. The server sends the second encrypted data obtained by encrypting the mid and key using the root key to the IoT device and proceeds to step S43. If not, the interface activation fails and the process ends. Step S43: The IoT device uses the root key to decrypt the received second encrypted data to obtain mid and key.

6. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S50 specifically includes: Step S51: The IoT device uses the key to encrypt the current timestamp to obtain third encrypted data, signs the device information and the third encrypted data to obtain first signature data, and sends the first signature data and the third encrypted data to the authentication server based on the mid. Step S52: The authentication server receives the first signature data and the third encrypted data, decrypts the third encrypted data using the key to obtain a timestamp, and verifies the validity period of the timestamp based on the preset authentication period. Step S53: The authentication server signs the device information and the third encrypted data to obtain the second signature data, and determines whether the first signature data and the second signature data are consistent. If they are consistent, the interface authentication is successful. Based on the SN, the device status identifier is updated to authenticated, and the token, din code and code validity period are sent to the IoT device to complete the identity authentication of the IoT device. If not, the interface authentication fails and the process ends.

7. The domain-based IoT device authentication management method as described in claim 1, characterized in that: In step S60, the device management table includes at least the domain, field code, field name, display type, allowed null status, description, sorting, and operation; The field name includes at least device information and operating data; the display type can be a checkbox, text box, drop-down list, radio button, time, or switch; the allowed empty state can be either yes or no; the operation is used to edit the domain, field code, field name, display type, allowed empty state, description, and sorting. The user permissions include at least the permissions to add, delete, modify, query, and filter, and are bound to the SN of the IoT device.

8. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Step S80 specifically involves: The IoT device verifies the validity of the DIN code based on the code's validity period. If the DIN code expires, it reapplies for the DIN code and its validity period. If the validity period has not expired, the device information and operating data carrying the DIN code will be updated to the device management table based on the user permissions. The IoT device or the domain management server will then perform add, delete, modify, query, and filter operations on the device management table based on the user permissions.

9. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Also includes: Step S90: Perform an authorization extension operation based on the validity period of use.

10. The domain-based IoT device authentication management method as described in claim 1, characterized in that: Also includes: Step S100: The management terminal performs authorization management for IoT devices by stopping and resuming authorization.

Images