Verification gateway and method applied to credible access of Internet of Things equipment

Abstract

The invention provides a verification gateway and method applied to credible access of Internet of Things equipment. The gateway comprises a TEE module, an authentication code generation module, an analysis authentication module and a storage module. And the TEE module is used for providing a hardware isolation environment for the verification gateway. The authentication code generation module is used for generating an initial authentication code for Internet of Things equipment which leaves a factory or is accessed to the Internet of Things platform for the first time. The analysis and authentication module is used for receiving a network data packet from the Internet of Things equipment, analyzing the equipment identity information in the network data packet, verifying the integrity and legality of the equipment identity information based on a predefined legal range, generating an authentication result, and sending the authentication result to the Internet of Things platform; the device identity information comprises an authentication code of the Internet of Things device. And the storage module is used for storing an authentication result record of the Internet of Things equipment. According to the invention, the centralized processing of authentication is realized, the security, authentication efficiency and expandability of the system are improved, and the burden of the Internet of Things platform is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of identity information authentication of hardware devices of the Internet of Things, and in particular to a verification gateway and method applied to trusted access of devices of the Internet of Things. Background Art

[0002] The existing IoT device authentication solutions mainly include authentication based on certificate management system, authentication based on proxy gateway, edge computing gateway with TEE environment, and decentralized gateway authentication based on blockchain.

[0003] The authentication scheme based on the certificate management system is currently a common way to authenticate the identity of IoT devices. An independent certificate authentication module is used to centrally manage the authentication, key distribution and management, and authorization review of devices. When a device accesses the IoT platform, it first sends an authentication request to the certificate management system. The authentication module confirms the legitimacy of the authentication based on the device's digital certificate or key. Only after the verification is passed will the device be allowed to access the platform and transmit data. The certificate management system can provide devices with global unified identity management and centralized authentication interfaces. It uses standard authentication protocols (such as TLS, SSL, etc.) to complete the device's identity authentication and authorization operations, thereby reducing the authentication burden of the IoT platform and facilitating the centralized management of the platform. However, this centralized authentication mode based on the certificate management system is prone to form performance bottlenecks in large-scale IoT scenarios. The certificate management system needs to handle concurrent authentication requests from a large number of devices. When the number of devices is large or the devices are frequently online, the system may find it difficult to respond to all requests in real time, resulting in increased authentication delays. At the same time, as a key authentication node, the certificate management system is at risk of becoming an attack target. Once it is invaded or attacked, the system may be maliciously exploited or paralyzed, which will lead to a significant decrease in the security and stability of the entire IoT system.

[0004] The proxy gateway-based authentication scheme refers to setting up a gateway between the IoT device and the platform to assume the initial authentication responsibility in a "proxy" manner. When the IoT device accesses the platform, the proxy gateway will first verify the identity of the device before it transmits data, and protect the security of the transmitted data through means such as encrypted channels or data signatures. The proxy gateway provides basic security protection for the platform by integrating authentication algorithms and key management modules, so that the IoT platform does not need to directly handle the authentication work of a large number of devices. The deployment method of the proxy gateway is relatively flexible. It can share the authentication burden through distributed deployment, effectively improve the authentication efficiency and the scalability of the platform, and is especially suitable for scenarios with dense deployment of IoT devices. However, the authentication and security of the proxy gateway mainly rely on software-level protection measures and lack the guarantee of hardware isolation. Therefore, its defense capability is relatively weak when facing complex network attacks (such as man-in-the-middle attacks or malicious tampering). In addition, the proxy gateway usually lacks a mechanism to record and trace the authentication process, which makes it difficult to provide reliable authentication history records and reduces the overall credibility of the system. The authentication depth of the proxy gateway is also limited, which is difficult to meet the high-security IoT application scenarios that require refined management.

[0005] The edge computing gateway solution that introduces TEE (Trusted Execution Environment) uses the security isolation provided by the TEE module in the edge computing device to implement the authentication function. When the IoT device accesses the platform, it first authenticates through the TEE gateway. TEE protects the authentication key, algorithm and sensitive data at the hardware level and ensures that all authentication operations are performed in an isolated environment to avoid external attacks or interference. Typical TEE environments include Intel SGX, ARM TrustZone, etc. They isolate sensitive data and operations from non-trusted applications by implementing security isolation on hardware. TEE edge gateways can provide a highly secure authentication process and are suitable for highly sensitive application scenarios with a small number of devices, such as industrial control or financial payment. Although TEE edge gateways can achieve highly isolated authentication, they are usually limited to device authentication within a local range, which is difficult to meet the centralized and global authentication management requirements in large-scale IoT scenarios. In addition, the authentication function of the TEE gateway mainly focuses on protecting authentication data, but lacks the ability to update the dynamic state changes of the device in real time and trace the authentication, which is insufficient in IoT environments that require continuous authentication and is difficult to meet the dynamic security requirements in complex and changing IoT scenarios.

[0006] The decentralized gateway authentication scheme based on blockchain utilizes the decentralization and immutability of blockchain to store the device's identity information, authentication records and other data on the blockchain. When the device is connected to the IoT platform, the blockchain node is responsible for distributed authentication of the device identity to ensure the uniqueness of the device identity and the transparency of the authentication process. After the device's authentication information is recorded on the blockchain, any authentication operation can be tamper-proof, ensuring the authenticity and credibility of the authentication process. This scheme avoids centralized authentication servers and implements decentralized distributed authentication in authentication nodes, which helps to improve the fault tolerance and transparency of the overall system and is suitable for scenarios that require authentication traceability. Although the blockchain solution has advantages in the security of authentication records, it is difficult to meet the real-time authentication requirements of IoT devices due to its high storage and computing costs. When faced with large-scale concurrent authentication requests, the consensus mechanism of the blockchain may cause high latency in the authentication process, which is difficult to meet the low-latency and real-time IoT scenarios. In addition, the maintenance and operation costs of blockchain nodes are high, and they are not suitable for deployment on resource-constrained IoT devices. At the same time, the flexibility of its authentication updates is also weak, making it difficult to meet the frequent status update requirements in the IoT environment.

[0007] In summary, the existing IoT device authentication solutions cannot simultaneously meet the requirements of large-scale IoT device authentication requests, global authentication management needs, real-time updates of dynamic device status changes, and authentication traceability. Summary of the invention

[0008] The purpose of the present invention is to provide a verification gateway and method for trusted access of Internet of Things devices, so as to solve the problems of centralization bottleneck, security risks and authentication efficiency of the current authentication system, migrate the authentication function from the Internet of Things platform to the verification gateway with hardware isolation, realize centralized processing of authentication, improve the security, authentication efficiency and scalability of the system, and reduce the burden on the Internet of Things platform.

[0009] The present invention proposes a verification gateway for trusted access of IoT devices, which is connected to IoT devices and IoT platforms respectively, and includes:

[0010] A TEE module is used to provide a hardware isolation environment for the verification gateway;

[0011] The authentication code generation module is used to generate an initial authentication code for an IoT device that is shipped from the factory or connected to the IoT platform for the first time, and transmit the initial authentication code to the corresponding IoT device for storage;

[0012] A parsing and authentication module is used to receive network data packets from IoT devices, parse device identity information in the network data packets, verify the integrity and legitimacy of the device identity information based on a predefined legal scope, generate an authentication result, and send the authentication result to the IoT platform. The device identity information includes an authentication code of the IoT device;

[0013] The storage module is used to store the authentication result records of the IoT devices.

[0014] In one embodiment, the initial authentication code is generated based on the factory information, system authorization data, device status data, device call data, and time-space data encryption calculation of the IoT device, and an IoT device has a unique initial authentication code;

[0015] The device identity information also includes system authorization data, device status data, device call data, and time and space data of the IoT device.

[0016] In one embodiment, the verification gateway applied to the trusted access of the Internet of Things device also includes an authentication code update module, which is used to update the authentication code of the Internet of Things device regularly and / or according to the change of the device identity information within the legal scope of the Internet of Things device, and transmit the updated authentication code to the corresponding Internet of Things device for storage;

[0017] The storage module is also used to store the generation and update records of the IoT device authentication code.

[0018] In one embodiment, the generation and update records of the IoT device authentication code and the authentication result records in the storage module are stored in the form of blockchain.

[0019] In one embodiment, the interface design between the verification gateway and the Internet of Things platform adopts a standardized protocol.

[0020] The present invention also proposes a verification method for trusted access of an Internet of Things device, which is applied to the verification gateway for trusted access of an Internet of Things device as described above, and includes the following steps:

[0021] When an IoT device is first connected to the IoT platform, the authentication code generation module of the verification gateway generates an initial authentication code and transmits the initial authentication code to the storage modules of the corresponding IoT device and the verification gateway for storage;

[0022] The IoT device sends a network data packet containing the device identity information to the verification gateway;

[0023] The parsing and authentication module of the verification gateway parses the network data packet to obtain the device identity information, verifies the integrity and legitimacy of the device identity information, and generates an authentication result. The device identity information includes the authentication code of the IoT device;

[0024] The authentication result is sent to the IoT platform. If the authentication is successful, the IoT device is allowed to communicate with the IoT platform. If the authentication fails, the interactive operation of the IoT device is rejected.

[0025] In one embodiment, the initial authentication code is generated based on the factory information, system authorization data, device status data, device call data, and time-space data encryption calculation of the IoT device, and an IoT device has a unique initial authentication code;

[0026] The device identity information also includes system authorization data, device status data, device call data, and time and space data of the IoT device.

[0027] In one embodiment, the verifying the integrity and legitimacy of the device identity information specifically includes:

[0028] First, the parsed authentication code of the IoT device is compared with the authentication code in the storage module. If they are consistent, the next step is carried out. Otherwise, the authentication fails.

[0029] Check one by one whether the system authorization data, device status data, device call data, and spatiotemporal data of the parsed IoT devices comply with the pre-defined legal range. If so, the authentication is passed; otherwise, the authentication fails.

[0030] In one embodiment, during the use of the IoT device, the authentication code of the IoT device is updated periodically and / or according to the change of the device identity information within the legal scope of the IoT device, and the updated authentication code is overwritten and stored in the corresponding IoT device;

[0031] When the IoT device requests to access the IoT again, the parsing and authentication module of the verification gateway parses and verifies the network data packet sent again by the IoT device to generate an authentication result.

[0032] In one embodiment, during the process of the IoT device requesting to access the IoT platform, the storage module of the verification gateway stores the generation, update record and authentication result record of the IoT device authentication code in the form of blockchain;

[0033] When the verification gateway fails to authenticate the IoT device, an abnormal alarm notification is sent to the IoT platform.

[0034] Compared with the prior art, the verification gateway and method for trusted access of IoT devices of the present invention have the following beneficial effects:

[0035] 1) The present invention transfers the authentication function from the IoT platform to the verification gateway with TEE (Trusted Execution Environment), providing hardware-level isolation environment and security protection for authentication operations, ensuring the security and credibility of authentication data. TEE can prevent unauthorized access and malicious interference, ensure that the generation, storage, parsing and verification of authentication codes are all carried out in a highly secure environment, effectively isolate authentication data from sensitive calculations, and reduce the risk of authentication information leakage, tampering and illegal access. Especially when dealing with advanced persistent threats (APT) or other complex attack scenarios, the verification gateway provides additional security protection for IoT devices.

[0036] 2) The verification gateway of the present invention has the function of centralized processing and diverting authentication requests, forming a centralized authentication management architecture, which can better cope with the access needs of large-scale IoT devices. In terms of authentication processing, it no longer relies on a single authentication module, but adapts to the ever-changing device environment and expansion needs through the multi-layer protection and dynamic management of TEE.

[0037] 3) The present invention transfers the authentication responsibility from the IoT platform to the verification gateway, so that the IoT platform does not need to directly perform the identity authentication work of IoT devices, and no longer needs to deal with the identity authentication issues of various types of devices. It only needs to make trust judgments based on the authentication results of the verification gateway to make decisions on data communication, which can greatly reduce the burden of the IoT platform in terms of device access and status inspection, allowing the platform to focus on data transmission and business logic processing, thereby achieving higher concurrency efficiency and response speed in large-scale IoT systems, improving system performance and security, avoiding performance bottlenecks, and improving authentication efficiency. This role separation makes the platform more flexible, the authentication more professional, and easy to expand, and can adapt to more complex scenarios and device diversity.

[0038] 4) The present invention dynamically updates the authentication code, so that the verification gateway can flexibly adapt to the state changes of the IoT device and possible security threats, preventing attackers from cracking the authentication code through long-term monitoring or analysis methods to obtain valid authentication information, thereby improving the anti-attack ability of the authentication system, enhancing the security and flexibility of the authentication process, and making the entire IoT system more secure and reliable. In addition, the authentication code update process can be combined with multiple conditions such as the operating status and geographical location of the device to ensure that the update of the authentication information is both secure and flexible, further enhancing the reliability of device authentication.

[0039] 5) The present invention records the detailed operation information of the authentication code and the authentication result in the form of blockchain, so that all authentication histories can be traced and cannot be tampered with, which enhances the transparency, integrity and traceability of the authentication process, facilitates subsequent review and management, and is especially valuable in IoT application scenarios with high compliance requirements or historical record requirements.

[0040] 6) The present invention performs multi-level legitimacy checks on data ranging from the authentication code of the IoT device to system authorization data, device status data, device call data, spatiotemporal data, etc., ensuring that the device is authenticated under preset states and conditions, greatly reducing the access risk of unauthorized devices, ensuring the dynamic compliance of authentication, and enhancing the reliability of authentication.

[0041] 7) The interface design between the verification gateway and the Internet of Things platform in the present invention adopts a standardized protocol, which ensures that the platform can conveniently and flexibly receive the authentication results generated by the gateway and quickly respond to the devices that have passed the authentication. It is convenient to integrate the verification gateway with various Internet of Things platforms, so that it can adapt to different deployment scales and business needs. It also provides good compatibility for subsequent system expansion and access to different types of devices, and has high versatility and scalability.

[0042] 8) The verification gateway of the present invention strictly checks the device status and behavior during the authentication process, so that abnormal devices can be quickly identified. If the device's authentication code or status data fails the legitimacy check, the gateway immediately sends an alarm signal to the platform and can deny its continued access. This instant detection and response mechanism can not only effectively isolate abnormal or potentially dangerous devices to prevent them from posing security threats to the IoT platform and other devices, but also improve the security emergency response capabilities of the entire system. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A schematic diagram of the structure of a verification gateway applied to trusted access of IoT devices according to an embodiment of the present invention;

[0044] Figure 2 A flowchart of a verification method for trusted access of an Internet of Things device according to an embodiment of the present invention;

[0045] Figure 3 A schematic diagram of the process of the authentication phase in a verification method for trusted access of an Internet of Things device according to an embodiment of the present invention;

[0046] Figure 4 The present invention is a flowchart of updating an authentication code in a verification method for trusted access of an Internet of Things device according to an embodiment of the present invention.

[0047] Reference numerals

[0048] 101. TEE module, 102. authentication code generation module, 103. authentication code update module, 104. parsing and authentication module, 105. storage module. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the present invention more understandable, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments of the specification. It should be noted that many specific details are set forth in the following description to facilitate a full understanding of the present invention, but the present invention can also be implemented in other ways different from those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present invention, so the present invention is not limited by the specific embodiments disclosed below.

[0050] Secondly, "one embodiment" or "an embodiment" in this application refers to a specific feature, structure or characteristic that can be included in at least one implementation of the present invention. The "in one embodiment" and "an embodiment" that appear in different places in this specification do not all refer to the same embodiment, nor are they separate or selective embodiments that are mutually exclusive with other embodiments. The terms "including" and "comprising" indicate the presence of the claimed features, but do not exclude the presence of one or more other features. The term "and / or" used in this application includes any and all combinations of one or more of the relevant listed items.

[0051] The present invention proposes a verification gateway for trusted access of IoT devices, which is connected to IoT devices and IoT platforms respectively, including a TEE module 101, an authentication code generation module 102, an authentication code update module 103, a parsing and authentication module 104, and a storage module 105. Figure 1 .

[0052] The TEE module 101 is used to provide a hardware isolation environment for the verification gateway, forming the "security border inspection" role of the Internet of Things system, ensuring that device authentication is performed in a hardware isolation environment, protecting the security of authentication data and algorithms, preventing external attacks, ensuring the credibility of authentication results, and providing device identity authentication and authentication result support for the Internet of Things platform. TEE (Trusted Execution Environment) is a set of software and hardware components that can provide necessary facilities for applications.

[0053] The authentication code generation module 102 is used to generate an initial authentication code for an IoT device that is shipped from the factory or accesses the IoT platform for the first time, and transmits the initial authentication code to the secure storage area of ​​the corresponding IoT device for storage. Among them, the initial authentication code is generated by a custom combination of encryption calculations based on the factory information, system authorization data, device status data, device call data, spatiotemporal data and other factors of the IoT device, and an IoT device has a unique initial authentication code. Factory information refers to the factory code of the IoT device, etc. System authorization data refers to the information that the IoT device is authorized to use, which determines which system resources the device can access and use, and which specific operations it can perform. Device status data refers to the working status data of the IoT device, such as the device's opening and closing, operating mode, power or power percentage, health status of each component, whether the sensor is working properly, and other information. Device call data refers to the history and current status of the IoT device's call to other related devices, services, and resources. Spatiotemporal data refers to the time and space information of the IoT device. It should be noted that the authentication code is used to identify the identity of the IoT device to ensure that the device is legal and authorized. The present invention does not limit the encryption method of the authentication code, and the authentication code can be generated by encrypting each part of the string using encryption algorithms such as string concatenation and hash algorithm.

[0054] The parsing and authentication module 104 is used to receive network data packets from IoT devices, parse the device identity information in the network data packets, verify the integrity and legality of the device identity information based on a predefined legal scope, generate an authentication result, and send the authentication result to the IoT platform. Among them, the setting of the legal scope needs to be based on the specific considerations of the device. The device identity information includes the authentication code, system authorization data, device status data, device call data, spatiotemporal data, etc. of the IoT device.

[0055] The authentication code update module 103 is used to update the authentication code of the IoT device regularly and / or according to the changes of the device identity information within the legal scope of the IoT device, that is, to update the authentication code of the IoT device based on the changes of the system authorization data, device status data, device call data, spatiotemporal data and other factors of the IoT device within the legal scope, and transmit the updated authentication code to the secure storage area of ​​the corresponding IoT device for storage, to ensure that the authentication code is dynamically updated to cope with environmental changes and security threats.

[0056] The storage module 105 is used to store the generation and update records of the authentication codes of the IoT devices and the authentication result records. The authentication result records include information such as the timestamp of the authentication operation, the device ID, and the update data. In the storage module of an embodiment of the present invention, the generation and update records of the IoT device authentication codes and the authentication result records are stored in the form of a blockchain to ensure that the records cannot be tampered with and to provide reliable evidence for the device authentication history. The storage module can also be provided with a cache unit and a blockchain storage unit, respectively. The cache unit is used to cache recent authentication results and authentication codes in a common format; the blockchain storage unit stores the generation and update records of the IoT device authentication codes and the authentication result records in the form of a blockchain.

[0057] The verification gateway can also add an abnormal alarm module. If an illegal device or abnormal status is found during the authentication process, the abnormal alarm module can immediately send an alarm notification to the IoT platform to ensure the security of the device authentication process. The verification gateway can also regularly generate authentication status reports for the platform to analyze and make decisions.

[0058] The interface design between the verification gateway and the Internet of Things platform of one embodiment of the present invention adopts a standardized protocol. For example, different data APIs (such as authentication result data, blockchain evidence data, etc.), network interaction protocols, data interaction interface protocols, etc. can be customized and developed according to different data interaction rules of different Internet of Things platforms. The network interaction protocol can be MQTT protocol, HTTPS protocol, TLS protocol, etc., and the data interaction format can be JSON, etc.

[0059] The present invention also proposes a verification method for trusted access of an IoT device, which is applied to the verification gateway for trusted access of an IoT device as described above, see Figure 2 , including the following steps:

[0060] Step S1, authorization stage: When the IoT device leaves the factory or first accesses the IoT platform, the IoT platform generates an initial authentication code through a custom combination encryption calculation by the authentication code generation module of the verification gateway based on the factory information of the IoT device (such as factory code), system authorization data, device status data, device call data, spatiotemporal data and other factors, and transmits the initial authentication code to the storage module of the corresponding IoT device and the verification gateway for storage. An IoT device has a unique initial authentication code. The IoT device will also generate device identity information through a corresponding combination calculation method and package it into a network data packet to ensure that the device can confirm its legitimacy through parsing and verification of the authentication code when accessing the platform.

[0061] Step S2: The IoT device sends a network data packet containing device identity information to a verification gateway.

[0062] Step S3, authentication phase: the parsing authentication module of the verification gateway parses the network data packet to obtain the device identity information, verifies the integrity and legitimacy of the device identity information, and generates an authentication result, wherein the device identity information includes the authentication code of the IoT device, system authorization data, device status data, device call data, spatiotemporal data, etc.

[0063] Step S4, authentication result notification phase: The verification gateway will send the authentication result to the IoT platform through the protocol interface. The platform only needs to determine the credibility of the device based on the authentication result, without the need for additional identity authentication. If the authentication is successful, the IoT device is allowed to communicate with the IoT platform. If the authentication is not successful, the interaction of the IoT device is rejected.

[0064] like Figure 3 As shown, in step S3, in the authentication phase, the specific operation steps for verifying the integrity and legitimacy of the device identity information include:

[0065] Step S301: First, compare the parsed authentication code of the IoT device with the authentication code in the storage module. If they are consistent, proceed to the next step; otherwise, the authentication fails.

[0066] Step S302: Check one by one whether the system authorization data, device status data, device call data, and spatiotemporal data of the parsed IoT devices comply with the predefined legal range. If so, the authentication is passed; otherwise, the authentication is failed.

[0067] The verification method for trusted access of IoT devices of the present invention is also provided with a dynamic update mechanism of the authentication code to cope with security threats during the use of the device, see Figure 4 , the specific operations are as follows:

[0068] Step S501: During the use of the IoT device, the IoT authentication code update module will update the IoT device authentication code periodically and / or according to changes in device identity information within the legal scope of the IoT device.

[0069] Step S502: The updated authentication code is overwritten and stored in the secure storage area of ​​the corresponding IoT device and separately stored in the storage module of the verification gateway to ensure that the updated authentication code is consistent on both the device and the gateway. At the same time, the update record is stored in the form of blockchain so that each update has an unalterable evidence.

[0070] Step S503: When the IoT device requests to access the IoT again, the parsing and authentication module of the verification gateway parses and authenticates the network data packet sent again by the IoT device to generate an authentication result.

[0071] When an IoT device requests to access the IoT platform, the storage module of the verification gateway will store the generation, update records and authentication result records of the IoT device authentication code in the form of blockchain.

[0072] In order to reduce the delay caused by repeated authentication, the verification gateway can cache recent authentication results so that the trusted results can be directly used in multiple interactions with the device in a short period of time, improving data transmission efficiency. At the same time, the IoT platform can query the authentication history of the device through the API (Application Programming Interface) to trace the device authentication status.

[0073] In addition, when the verification gateway fails to authenticate an IoT device, that is, an illegal device or abnormal status is found, an abnormal alarm notification can be immediately sent to the IoT platform to ensure the security of the device authentication process. The gateway will also regularly generate authentication status reports for the platform to analyze and make decisions.

[0074] The following is a detailed description of the implementation scenarios of the present invention and the main authorization, authentication, authentication code update and other stages in the above verification method through specific examples. However, it should be noted that the following example is only one application scenario, and the verification gateway and method of the present invention can be adapted to many other industrial scenarios.

[0075] If there is a manufacturing factory, in response to the national carbon neutrality strategy, it is preparing to build an energy consumption monitoring system to monitor the energy consumption data of each production line equipment in its production department, and then adjust the output value of the year in accordance with the annual carbon index of the factory. Then, in the architecture of this energy consumption monitoring system, it is generally based on the Internet of Things system, and then through multiple data monitoring Internet of Things devices (such as smart meters, smart sockets, etc.) to achieve the energy consumption monitoring effect of production line equipment.

[0076] However, there are many situations in the process of energy consumption monitoring that will affect the accuracy and credibility of the monitoring data. The following two scenarios are listed, but there are still many other situations): (1) There are commercial spies in the factory who deliberately disrupt the factory's output value control plan and transfer the monitoring equipment to other low-energy consumption equipment in the factory, resulting in a large deviation between the actual energy consumption of the factory and the monitored energy consumption, which in turn leads to excessive use of carbon indicators and faces fines from relevant departments. In this scenario, if the energy consumption monitoring equipment (such as smart sockets) is originally used for machine tool processing equipment, but is transferred to office computers for use, although the energy consumption monitoring equipment itself has not been tampered with or damaged, the data can still be collected and monitored normally, and the equipment still has integrity and security, but the data it monitors does not match its original purpose, that is, the monitored data loses credibility. (2) The factory overproduced for profit and found hackers to invade the IoT devices and IoT platforms for energy consumption monitoring, and then tampered with the data, causing a large deviation between the actual energy consumption of the factory and the monitored energy consumption. The problem of excessive carbon index use was attributed to the IoT device manufacturer or third-party institutions such as the power company, interfering with the implementation of the local carbon index control plan. In this scenario, the energy consumption monitoring equipment itself was tampered with and destroyed, and the equipment itself lacked integrity and security, that is, the equipment connected to the IoT platform itself was no longer trustworthy.

[0077] In situations like the above, the key to ensuring that the monitoring data is accurate and reliable is to ensure that the devices connected to the IoT platform are reliable and that the monitored data is reliable when the devices are reliable. The verification gateway and method for trusted access of IoT devices proposed in the present invention improve the security of authentication by transferring the authentication function from the IoT platform to the verification gateway with TEE (trusted execution environment), and reduce the risk of IoT devices and data being tampered with through self-created concepts such as authentication codes.

[0078] Before authorization, it is necessary to clarify the detailed information of the device and the specific usage scenario to help the gateway formulate trusted rules. The trusted rules are implemented through authentication codes and device identity information.

[0079] 1. Assume that the factory code of the energy consumption monitoring equipment is 2024122201 (it is the first one to leave the factory on December 22, 2024, so this is the factory code).

[0080] 2. This energy consumption monitoring equipment is authorized to be used in the production department of a certain factory to monitor the energy consumption of processing machine tool No. 05, and will take effect on December 23, 2024, with a validity period of 1 year (at the same time, it is known from the Internet of Things platform or other business platforms that the factory number is 15 and its production department number is 1501).

[0081] 3. The working voltage of the machine tool is 380V, and the voltage fluctuation is ±10%. That is, when monitoring the energy consumption data of the processing machine tool, the reasonable fluctuation range of the voltage should be: 342 (Min) ~ 418 (Max). Therefore, when the energy consumption monitoring device uploads data, the monitored voltage data should also be between 342 (Min) and 418 (Max) to be considered reliable.

[0082] 4. The frequency of data upload and call of the energy consumption equipment during data collection is once every 300 seconds, and the allowable deviation range is ±10%. The reasonable fluctuation range of the data is "270 (Min) ~ 330 (Max)".

[0083] 5. The working location of the equipment is fixed at longitude 118.3487384° and latitude 29.2707676°, and the working hours are 24 hours a day without interruption.

[0084] Assuming that the above is the specific information clarified before the authorization operation, the system authorization data, device status data, device call data, time and space data, etc. can be formulated based on these data.

[0085] From 1, we know that the factory code of the device is: 2024122201.

[0086] From 2, we know that the system authorization data of the device is: 1501-05-20241223-1. (Here, a simple string concatenation method is used as the formulation method of the system authorization data. In actual production, there are many formulation methods.)

[0087] From 3, we know that the device status data is: 380.

[0088] From 4, we know that the device calls data: 300.

[0089] From 5, we know that the device's time-space data is: 118.3487384-29.2707676-24. (Here, a simple string concatenation method is used as the formulation method of system authorization data. In actual production, there are many formulation methods.)

[0090] (1) Authorization is performed as follows:

[0091] When the device leaves the factory or is first connected to the platform, the gateway authentication code generation module starts to generate the authentication code. Assuming that the authentication code is formulated as follows: string concatenation method, and the order is connected and sorted according to the factory code, system authorization data, device status data, device call data, and time and space data (this is just an example, in actual production, there are many formulation methods), the authentication code can be obtained as follows: 2024122201-1501-05-20241223-1-380-300-118.3487384-29.2707676-24. The authentication code is stored in the IoT device, IoT platform, and gateway, and is also stored in the form of blockchain. In addition, the IoT platform and gateway will also record the legal change range of system authorization data, device status data, call data, and time and space data to facilitate the work of the authentication code update module.

[0092] In this example, the legal range of changes recorded is as follows:

[0093] 1. System authorization data: Within one year from December 23, 2024, the system authorization data is 1501-05-20241223-1, and it will remain unchanged during this period.

[0094] 2. Equipment status data: 342 (Min) ~ 418 (Max).

[0095] 3. Equipment call data: 270 (Min) ~ 330 (Max).

[0096] 4. Equipment time and space data: 118.3487384-29.2707676-24, fixed and unchanged.

[0097] After that, the device is connected to the platform and starts working. When the device interacts with the IoT platform and gateway, the authentication code and the monitored data are combined into a network data packet containing the device identity information and sent to the verification gateway.

[0098] (2) Entering the authentication phase: The parsing authentication module of the verification gateway parses the network data packet, obtains the device identity information, verifies the integrity and legitimacy of the device identity information, and generates an authentication result.

[0099] In this example, the device authentication code is 2024122201-1501-05-20241223-1-380-300-118.3487384-29.2707676-24, and the authentication is successful.

[0100] The verification gateway sends the authentication result to the IoT platform. If the authentication is successful, the IoT device is allowed to communicate with the IoT platform. If the authentication fails, the interactive operation of the IoT device is rejected.

[0101] (3) Update phase: During the use of IoT devices, the IoT authentication code update module updates the IoT device authentication code periodically or based on changes in the device identity information within the legal scope of the IoT device.

[0102] In this example, it is assumed that the data sent by the device after normal operation is as follows:

[0103] 1. System authorization data: 1501-05-20241223-1.

[0104] 2. Equipment status data: 357.

[0105] 3. Device call data: 281.

[0106] 4. Equipment time and space data: 118.3487384-29.2707676-24.

[0107] At this time, the data monitored by the device is actual data, and has changed compared to the initial settings. Then the parsing authentication module runs to check whether the data is within the legal and credible change range. If it is not legal, the update task fails, an alarm is issued to indicate untrustworthy risks, and the device is disconnected. If it is legal, the authentication code update module performs an update overwrite, and the updated authentication code is: 2024122201-1501-05-20241223-1-357-281-118.3487384-29.2707676-24. After the authentication code is updated, bilateral storage and blockchain evidence are performed.

[0108] Let's review the two scenarios mentioned above: In the first scenario, if the energy consumption monitoring device (such as a smart socket) is originally used for machine tool processing equipment, but is transferred to an office computer for use, although the energy consumption monitoring device itself has not been tampered with or damaged, the data can still be collected and monitored normally, and the device still has integrity and security, but the data it monitors does not match its original purpose, that is, the monitored data loses credibility. For this scenario, when the authentication code is updated, the gateway will recognize that the collected data does not meet the legal scope regulations, so the authentication code update fails, and the risk identification of this scenario is successful. In the second scenario, the energy consumption monitoring device itself is tampered with and damaged, and the device itself does not have integrity and security, that is, the device connected to the Internet of Things platform itself is no longer trustworthy. If the device is tampered with, if it is simply the monitoring end data tampering, it will be the same as the first scenario. If it is implanted by a virus or other means, since the gateway is a TEE environment, and the combination of identity information leaves a safe space for the actual production environment, the data can be restricted by customizing the combination calculation method of various identity information, and only the encryption method of the device end and the corresponding decryption method need to be known by the gateway (asymmetric encryption).

[0109] From the above examples, we can also see that the specific conditions for updating the authentication code correspond to the conditions for generating the authentication code. The update is based on the generation and is not limited to a certain update rule. Similarly, the legal scope also requires specific settings for specific devices.

[0110] In summary, on the first aspect, the present invention transfers the authentication function from the IoT platform side to the verification gateway with TEE (Trusted Execution Environment), provides a hardware-level isolation environment and security protection for the authentication operation, and ensures the security and credibility of the authentication data. TEE can prevent unauthorized access and malicious interference, ensure that the generation, storage, parsing and verification of the authentication code are all carried out in a highly secure environment, effectively isolate the authentication data from sensitive calculations, and reduce the risk of authentication information leakage, tampering and illegal access, especially when dealing with advanced persistent threats (APT) or other complex attack scenarios, the verification gateway provides additional security protection for IoT devices. On the second aspect, the verification gateway of the present invention has the function of centralized processing and diversion of authentication requests, forming a centralized authentication management architecture, which can better cope with the access needs of large-scale IoT devices, and no longer relies on a single authentication module in terms of authentication processing, but adapts to the ever-changing device environment and expansion needs through the multi-layer protection and dynamic management of TEE. In the third aspect, the present invention transfers the authentication responsibility from the IoT platform to the verification gateway, so that the IoT platform does not need to directly perform the identity authentication of IoT devices, and does not need to deal with the identity authentication issues of various types of devices. It only needs to make trust judgments based on the authentication results of the verification gateway to make decisions on data communication, which can greatly reduce the burden of the IoT platform on device access and status inspection, so that the platform can focus on data transmission and business logic processing, thereby achieving higher concurrency efficiency and response speed in large-scale IoT systems, improving system performance and security, avoiding performance bottlenecks, and improving authentication efficiency. This role separation makes the platform more flexible, the authentication more professional, and easy to expand, and can adapt to more complex scenarios and device diversity. In the fourth aspect, the present invention dynamically updates the authentication code, so that the verification gateway can flexibly adapt to the state changes of IoT devices and possible security threats, prevent attackers from cracking the authentication code through long-term monitoring or analysis methods, and obtain valid authentication information, thereby improving the anti-attack ability of the authentication system, enhancing the security and flexibility of the authentication process, and making the entire IoT system have higher security and reliability. In addition, the authentication code update process can be combined with various conditions such as the operating status and geographical location of the device to ensure that the update of the authentication information is both secure and flexible and controllable, further enhancing the reliability of device authentication. Fifthly, the present invention records the detailed operation information of the authentication code and the authentication result in the form of blockchain, so that all authentication histories can be traced and cannot be tampered with, which enhances the transparency, integrity and traceability of the authentication process, and is conducive to subsequent review and management. It is especially valuable in IoT application scenarios with high compliance requirements or historical record requirements.In the sixth aspect, the present invention performs multi-level legitimacy checks from the authentication code of the IoT device to the system authorization data, device status data, device call data, spatiotemporal data and other data, ensuring that the device is authenticated under the preset state and conditions, greatly reducing the access risk of unauthorized devices, ensuring the dynamic compliance of authentication, and enhancing the reliability of authentication. In the seventh aspect, the interface design of the verification gateway and the IoT platform in the present invention adopts a standardized protocol, ensuring that the platform can conveniently and flexibly receive the authentication results generated by the gateway, and quickly respond to the authenticated devices, facilitating the integration of the verification gateway with various IoT platforms, so that it can adapt to different deployment scales and business needs, and also provides good compatibility for subsequent system expansion and access of different types of devices, with high versatility and scalability. In the eighth aspect, the strict verification of the device status and behavior by the verification gateway of the present invention during the authentication process enables abnormal devices to be quickly identified. If the device's authentication code or status data fails the legitimacy check, the gateway immediately sends an alarm signal to the platform and can refuse its continued access. This instant detection and response mechanism can not only effectively isolate abnormal or potentially dangerous devices, prevent them from posing security threats to the IoT platform and other devices, but also improve the security emergency response capabilities of the entire system.

[0111] It should be noted that, in the present application, unless otherwise clearly specified and limited, "connection" and similar terms should be understood in a broad sense. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, an indirect connection through an intermediate medium, or the internal connection of two components. Technical personnel in the field can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0112] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0113] The construction and arrangement of the present application shown in a plurality of different exemplary embodiments are only illustrative. Although only a few embodiments are described in detail in this disclosure, it should be readily understood by those who refer to this disclosure that many modifications are possible (e.g., parameter values, installation arrangements, etc.) without substantially departing from the novel teachings and advantages of the subject matter described in the application. Therefore, all such modifications are intended to be included within the scope of the present invention. The order or sequence of any process or method steps can be changed or reordered according to alternative embodiments. In the claims, any "device plus function" clause is intended to cover the structure of performing the function described herein, and is not only structurally equivalent but also equivalent structures. Without departing from the spirit and essence of the present invention, those skilled in the art may make various corresponding modifications and changes according to the present invention, but these corresponding modifications and changes should all fall within the scope of protection of the present invention.

Claims

1. A verification gateway for trusted access of IoT devices, connected to IoT devices and IoT platforms respectively, characterized in that: include: A TEE module is used to provide a hardware isolation environment for the verification gateway; The authentication code generation module is used to generate an initial authentication code for an IoT device that is shipped from the factory or connected to the IoT platform for the first time, and transmit the initial authentication code to the corresponding IoT device for storage; A parsing and authentication module is used to receive network data packets from IoT devices, parse device identity information in the network data packets, verify the integrity and legitimacy of the device identity information based on a predefined legal scope, generate an authentication result, and send the authentication result to the IoT platform. The device identity information includes an authentication code of the IoT device; The storage module is used to store the authentication result records of the IoT devices.

2. The verification gateway for trusted access of IoT devices according to claim 1, characterized in that: The initial authentication code is generated based on the factory information, system authorization data, device status data, device call data, and time-space data encryption calculation of the IoT device. An IoT device has a unique initial authentication code. The device identity information also includes system authorization data, device status data, device call data, and time and space data of the IoT device.

3. The verification gateway for trusted access of IoT devices according to claim 1, characterized in that: It also includes an authentication code update module, which is used to update the authentication code of the Internet of Things device regularly and / or according to the change of the device identity information within the legal scope of the Internet of Things device, and transmit the updated authentication code to the corresponding Internet of Things device for storage; The storage module is also used to store the generation and update records of the IoT device authentication code.

4. The verification gateway for trusted access of IoT devices according to claim 3, characterized in that: The generation and update records of the IoT device authentication code and the authentication result records in the storage module are stored in the form of blockchain.

5. The verification gateway for trusted access of IoT devices according to claim 1, characterized in that: The interface design between the verification gateway and the Internet of Things platform adopts a standardized protocol.

6. A verification method for trusted access of IoT devices, characterized in that: The verification gateway for trusted access of an Internet of Things device according to any one of claims 1 to 5 comprises the following steps: When an IoT device is first connected to the IoT platform, the authentication code generation module of the verification gateway generates an initial authentication code and transmits the initial authentication code to the storage modules of the corresponding IoT device and the verification gateway for storage; The IoT device sends a network data packet containing the device identity information to the verification gateway; The parsing and authentication module of the verification gateway parses the network data packet to obtain the device identity information, verifies the integrity and legitimacy of the device identity information, and generates an authentication result. The device identity information includes the authentication code of the IoT device; The authentication result is sent to the IoT platform. If the authentication is successful, the IoT device is allowed to communicate with the IoT platform. If the authentication fails, the interactive operation of the IoT device is rejected.

7. The verification method for trusted access of IoT devices according to claim 6 is characterized in that: The initial authentication code is generated based on the factory information, system authorization data, device status data, device call data, and time-space data encryption calculation of the IoT device. An IoT device has a unique initial authentication code. The device identity information also includes system authorization data, device status data, device call data, and time and space data of the IoT device.

8. The verification method for trusted access of IoT devices according to claim 7 is characterized in that: The integrity and legality of the verification device identity information specifically includes: First, the parsed authentication code of the IoT device is compared with the authentication code in the storage module. If they are consistent, the next step is carried out. Otherwise, the authentication fails. Check one by one whether the system authorization data, device status data, device call data, and spatiotemporal data of the parsed IoT devices comply with the pre-defined legal range. If so, the authentication is passed; otherwise, the authentication fails.

9. The verification method for trusted access of IoT devices according to claim 8 is characterized in that: During the use of the IoT device, update the authentication code of the IoT device regularly and / or according to the changes of the device identity information within the legal scope of the IoT device, and overwrite and store the updated authentication code in the corresponding IoT device; When the IoT device requests to access the IoT again, the parsing and authentication module of the verification gateway parses and verifies the network data packet sent again by the IoT device to generate an authentication result.

10. The verification method for trusted access of IoT devices according to claim 9, characterized in that: When an IoT device requests to access the IoT platform, the storage module of the verification gateway stores the generation, update and authentication result records of the IoT device authentication code in the form of blockchain. When the verification gateway fails to authenticate the IoT device, an abnormal alarm notification is sent to the IoT platform.

Images